General Data Protection

Regulation (GDPR) 1

Security information 2
Security Information for
Industrial Edge App 3
Introduction to SIMATIC S7
Connector 4
SIMATIC S7 Connector User Interface for SIMATIC
Configurator V1.4 S7 Connector Configurator 5
Home Page

Working with SIMATIC S7

Operating Manual
Connector Configurator 6

Additional Information 7

10/2021
A5E50594971-AC
Legal information
Warning notice system
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.

DANGER
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.
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.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
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.
Proper use of Siemens products
Note the following:

WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance
are required to ensure that the products operate safely and without any problems. The permissible ambient
conditions must be complied with. The information in the relevant documentation must be observed.

Trademarks
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.
Disclaimer of Liability
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.

Siemens AG A5E50594971-AC Copyright © Siemens AG 2021.

Digital Industries Ⓟ 10/2021 Subject to change All rights reserved
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents

1 General Data Protection Regulation (GDPR).......................................................................................... 5

2 Security information.............................................................................................................................. 7
3 Security Information for Industrial Edge App........................................................................................ 9
4 Introduction to SIMATIC S7 Connector ................................................................................................ 11
5 User Interface for SIMATIC S7 Connector Configurator Home Page .................................................... 13
6 Working with SIMATIC S7 Connector Configurator.............................................................................. 17
6.1 Managing Data Sources ..................................................................................................... 17
6.1.1 Configure S7-Protocol (S7-300/400/1200/1500) Data Source .............................................. 17
6.1.2 Configure Optimized S7-Protocol (S7-1200/1500) Data Source............................................ 20
6.1.3 Configure OPC-UA Data Source........................................................................................... 22
6.1.4 Edit Data Source ................................................................................................................ 26
6.1.5 Delete Data Source ............................................................................................................ 27
6.2 Managing Tags/Data Points ................................................................................................ 28
6.2.1 Add Tags............................................................................................................................ 28
6.2.2 Edit Tags ............................................................................................................................ 34
6.2.3 Import Tags ....................................................................................................................... 35
6.2.4 Browse Tags....................................................................................................................... 37
6.2.5 Bulk Publish Tags ............................................................................................................... 40
6.2.6 Delete Tags ........................................................................................................................ 41
6.3 Managing Project............................................................................................................... 42
6.3.1 Configure Settings.............................................................................................................. 42
6.3.2 Deploy Project.................................................................................................................... 43
6.3.3 Start Project ....................................................................................................................... 46
6.3.4 Stop Project ....................................................................................................................... 46
6.3.5 Verify Configuration ........................................................................................................... 47
6.4 Import/Export Configuration............................................................................................... 47
7 Additional Information ........................................................................................................................ 49
7.1 How to Write Tags?............................................................................................................. 49
7.2 Topic Structure for Data and Metadata................................................................................ 50
7.2.1 JSON structure for Alarms and Tags Data ............................................................................ 51
7.2.2 JSON structure for Alarms and Tags Metadata..................................................................... 57
7.2.3 Connector and Connection Status ...................................................................................... 60
7.3 How to Export Tags from TIA Portal? ................................................................................... 62
7.3.1 Export Tags for S7-Protocol (S7-300/400/1200/1500) and Optimized S7-Protocol
(S7-1200/1500) Connection............................................................................................... 62
7.3.2 Export Tags for OPC-UA Connection.................................................................................... 67
7.4 How to Configure String Datatype in S7-Protocol (S7-300/400/1200/1500)? ........................ 68
7.5 How to Generate OPC-UA Client and Server Certificates? ..................................................... 69

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 3
Table of contents

7.6 How to Configure Access Password? ................................................................................... 77

7.7 How to Configure S7-1200 PLC FW version 4.5? .................................................................. 80
7.8 Configuration Version 1.1 vs 1.2......................................................................................... 81
7.9 Data Types ......................................................................................................................... 81
7.10 Notes on use...................................................................................................................... 99
7.11 Known issues................................................................................................................... 102

SIMATIC S7 Connector Configurator V1.4

4 Operating Manual, 10/2021, A5E50594971-AC
General Data Protection Regulation (GDPR) 1
Siemens adheres to the principles of data protection, in particular the principles of data
minimization (Privacy by Design).
For this product, SIMATIC S7 Connector Configurator, this means:

Personal data
There is no personal data* collected but following data is stored to allow machine to machine
communication:
• Industrial Edge Databus credentials
• S7+ legitimization credentials
• OPC-UA server login credentials
• OPC-UA server certificates for encryption and signing
• Tags data and metadata from field devices
• Timestamp
• Smart device information and app usage data
If the customer links the data mentioned above to other data (e.g., shift plans) or if the customer
saves personal information on the same medium (e.g. hard disk) and thus creates a personal
reference, the customer has to ensure that the guidelines regarding data protection are
observed.

Note
* This section refers to any personal data processed by the Application other than the personal
data contained in log-files / tracking data (if any). "Personal data" are any information relating to
an identified or identifiable natural person. Please note that IP-addresses, device identifiers such
as IMEI, UDID, IMSI, MAC-address, MSISDN, location data or machine data (if machine data
tracks events triggered by user interaction with the machine) usually qualify as personal data.

Purposes
The data mentioned above is required for the following purposes:
• Access protection and security measures
• Message system for traceability and availability
• For app diagnosis
Storage of the data is affected for a suitable purpose and is limited to what is strictly necessary,
as the information is indispensable in order to identify the authorized operators.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 5
General Data Protection Regulation (GDPR)

Securing of data
The above data will not be stored anonymously or pseudonymized, as the purpose
(identification of the operating personnel) cannot be achieved otherwise.
The following data will be used only within the product and within the Edge eco-system and will
not be automatically passed on to third parties or unauthorized persons:
• Industrial Edge Databus credentials
• S7+ legitimization credentials
• OPC-UA server login credentials
• OPC-UA server certificates
The above data is secured by adequate technical measures, such as storing and encryption of
process data in databases.
The tags data and metadata from field devices data will be used only within the product and will
not be automatically passed on to third parties or unauthorized persons.
The customer must ensure the access protection as part of his process configuration.

Deletion policy
This product does not provide an automatic deletion for the databus or PLC credentials already
provided by the user. In case the user provides a different databus or PLC credentials, the
previous credentials will be overwritten. Since there is no explicit delete option, the user could
provide junk databus or PLC credentials to delete the existing valid credentials.
If the user deletes a connection or tag, then the credentials information and other details would
also be deleted.
In short, the collected log data will be automatically deleted once the limit is reached (oldest
entries first).

Data configuration
The customer can configure the data collected via the product as follows:
• Using the App Configurator

SIMATIC S7 Connector Configurator V1.4

6 Operating Manual, 10/2021, A5E50594971-AC
Security information 2
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, systems, machines, and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is necessary
to implement – and continuously maintain – a holistic, state-of-the-art industrial security
concept. Siemens’ products and solutions form one element of such a concept.
Customers are responsible for preventing unauthorized access to their plants, systems,
machines and networks. These systems, machines and components should only be connected
to the enterprise network or the Internet if and only to the extent necessary and with appropriate
security measures (firewalls and/or network segmentation) in place.
You can find more information on protective measures in the area of industrial security by
visiting:
https://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more secure.
Siemens strongly recommends performing product updates as soon as they are available and
using only the latest product versions. Use of product versions that are no longer supported, and
failure to apply latest updates may increase customer’s exposure to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed
under
https://www.siemens.com/industrialsecurity.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 7
Security information

SIMATIC S7 Connector Configurator V1.4

8 Operating Manual, 10/2021, A5E50594971-AC
Security Information for Industrial Edge App 3
Security information (assumption/constraint) for Industrial Edge Apps are as follows:
• Only authorized internal operators will have access to Industrial Edge Device with-in secure
network using VPN connection.
• Perimeter firewall configuration responsibility lies with end customer.
• Security guidelines for usage of USB sticks within shop floor are applied.
• Creating users with appropriate access rights needs to be done during commissioning and it
is the responsibility of the operator.
• Customer is responsible for configuring the application as per the installation/user manual,
based on system requirements and technical capabilities of app documented so that the
Automation System performance is not impacted.
• The system is installed in an environment that ensures physical access is limited to authorized
maintenance personnel only. Managing unauthorized attachment of removable devices is
the responsibility of the operator.
• The platform including hardware, firmware and operating system is securely configured and
maintained by the operator.
• The operator is capable of protecting the environment from malware infection.
• Centralized IT security components (Active Directory, Centralized IT Logging Server) are
provided and well secured by the operator and can be trusted.
• The operator personnel accessing the system is well trained in the usage of the system and
general information security aspects like password handling, removable media, etc. are in
place.
• Operator is responsible for the Confidentiality, Integrity, and Availability (CIA) of data stored
outside the Industrial Edge Device.
• Operator is responsible for configuring the PLCs with appropriate read/write access levels
(Legitimization) and configure Industrial Edge Apps with appropriate passwords for data
collection from PLC's.
• Customer takes care about time sync of Industrial Edge Management and Industrial Edge
Device.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 9
Security Information for Industrial Edge App

SIMATIC S7 Connector Configurator V1.4

10 Operating Manual, 10/2021, A5E50594971-AC
Introduction to SIMATIC S7 Connector 4
The SIMATIC S7 Connector connects your Industrial Edge Device to a S7-Protocol
(S7-300/400/1200/1500) controller, Optimized S7-Protocol (S7-1200/1500) controller, or an
OPC UA (OPC Server). You can configure these connections using the SIMATIC S7 Connector
Configurator. You can use the configured connections to transfer the measured value series of
selected data points to the Industrial Edge Runtime of the respective Industrial Edge Device. The
Industrial Edge Runtime sends this data to the Industrial Edge Databus. You can then use the
data collected via the Industrial Edge Databus for your Industrial Edge App or other applications.
The SIMATIC S7 Connector provides easy connectivity with SIMATIC PLCs (S7-300, S7-400,
S7-1200, S7-1500) via communication channel for tags and alarms data acquisition.
The SIMATIC S7 Connector consists of the following two components:
1. SIMATIC S7 Connector Configurator in Industrial Edge Management
The SIMATIC S7 Connector Configurator in the Industrial Edge Management provides its own
user interface that you can use to manage the SIMATIC S7 Connector on the respective
Industrial Edge Device.
2. SIMATIC S7 Connector
The SIMATIC S7 Connector is an application that runs on the individual Industrial Edge
Device. You can install the SIMATIC S7 Connector on all Industrial Edge Devices that you want
to connect to your controllers. The SIMATIC S7 Connector sends the data point values
imported from the controllers to the Industrial Edge Databus through the Industrial Edge
Runtime.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 11
Introduction to SIMATIC S7 Connector

SIMATIC S7 Connector Configurator V1.4

12 Operating Manual, 10/2021, A5E50594971-AC
User Interface for SIMATIC S7 Connector
Configurator Home Page 5
Prerequisite
• SIMATIC S7 Connector app must be installed and running on the Industrial Edge Device.
• SIMATIC S7 Connector Configurator must be installed and running on the Industrial Edge
Management.

Home page
When you launch SIMATIC S7 Connector Configurator, the home page is displayed as follows:

3 5
1 4 10 6
2
7 8 9

① Add Data Source Button

② Delete Button
③ S7 Connector Tab
④ OPC-UA Connector Tab
⑤ Data Source Table
⑥ Deploy Button
⑦ Start/Stop Project Button
⑧ Import/Export Icons
⑨ Settings Icon
⑩ Connection status of Bus Adapter

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 13
User Interface for SIMATIC S7 Connector Configurator Home Page

UI Elements
The following table lists the different UI elements in the "Configure" section page:

Symbol Description
Add Data Source Button Enables to add a new data source.
Delete Button Enables to delete the data source and data points.
S7 Connector Tab Area to display S7-Protocol (S7-300/400/1200/1500) and Optimized S7-Pro‐
tocol (S7-1200/1500) data source connections.
OPC-UA Connector Tab Area to display OPC UA (OPC Server) data source connections.
Data Source Table Displays the data source connections and data points and their information
as follows:
• "Name": Displays the name of the data point. You can use to align the
data point name. By default, the data point name is left aligned.
• "Comments": Displays the given comments.
• "Address": Displays the address of the data point.
• "Data Type": Displays the data point type.
• "Acquisition Cycle": Displays the acquisition cycle with which the data is
sent to the Databus.
• "Acquisition Mode": Displays the acquisition mode with which the data is
sent to the Databus.
• "Access Mode": Displays the access permission.
• "Actions": Displays the "Edit Data Source", "Add Tags", "Import Tags", and
"Browse" options. For more information, refer Managing Tags/Data Points
(Page 28).
Deploy Button Enables to deploy the project. If you close the SIMATIC S7 Connector Config‐
urator, then all the unsaved configurations are lost. The "Deploy" button saves
the configuration on the Industrial Edge Runtime of the SIMATIC S7 Connec‐
tor.
Start/Stop Project Button Enables to start and stop the project.
Import/Export Icons Enable to import and export the configuration. For more information,
refer Import/Export Configuration (Page 47).
Settings Icon Enables to perform the following tasks:
1. You can edit IE Databus service name.
2. You can specify SIMATIC S7 Connector user credentials which you define
in Industrial Edge Databus Configurator.
3. You can specify configuration version of the SIMATIC S7 Connector Con‐
figurator.
4. You can specify browse timeout.
For more information, refer Configure Settings (Page 42).

The following indicators indicate the connection status of Bus Adaptor connection with TagData/
Metadata and AlarmData MQtt clients:

Color Status

TagData, Metadata and AlarmData client is connec‐

ted to Bus Adaptor

SIMATIC S7 Connector Configurator V1.4

14 Operating Manual, 10/2021, A5E50594971-AC
User Interface for SIMATIC S7 Connector Configurator Home Page

Atleast one of the TagData, Metadata and Alarm‐

Data client is disconnected from Bus Adaptor

No connection state with Bus Adaptor. This is a

warning

The following indicators indicate the connection status of the PLC’s:

Color Status

The connection is good and established.

The connection is bad and not established.

No state. This will be the default value if project is

not running or if connection is new.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 15
User Interface for SIMATIC S7 Connector Configurator Home Page

SIMATIC S7 Connector Configurator V1.4

16 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator 6
The SIMATIC S7 Connector Configurator allows you to add field devices to Industrial Edge Device
and create data point lists. It supports multiple user access with the following scenarios:
• One user can access SIMATIC S7 Connector Configurator on multiple Industrial Edge Device
(IED).
But the user cannot access SIMATIC S7 Connector Configurator on the same IED in multiple
tabs of same browser or multiple browsers.
• Two users can access SIMATIC S7 Connector Configurator on two different IEDs
simultaneously.
When the two users access SIMATIC S7 Connector Configurator on the same IED, a message
is displayed to the second user that the IED is in use already. Therefore, the second user
cannot access SIMATIC S7 Connector Configurator.

Note
When you perform
• add, edit, or delete of a data source,
• add, edit, import, or delete of a tag,
you must click "Deploy" button to save the changes on the Industrial Edge Runtime of the
SIMATIC S7 Connector.

6.1 Managing Data Sources

A data source is a field device which provides the data. You can configure the SIMATIC S7
Connector to the field devices to consume the acquired data in the Industrial Edge Device for
value creation.
The SIMATIC S7 Connector Configurator supports the following three communication channels:
1. S7-Protocol (S7-300/400/1200/1500)
2. Optimized S7-Protocol (S7-1200/1500)
3. OPC UA (OPC Server)

6.1.1 Configure S7-Protocol (S7-300/400/1200/1500) Data Source

You can configure S7-Protocol (S7-300/400/1200/1500) controller data source in the SIMATIC S7
Connector Configurator. The Configurator allows you to configure the S7-Protocol
(S7-300/400/1200/1500) communication channel to the SIMATIC PLCs for data acquisition.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 17
Working with SIMATIC S7 Connector Configurator
6.1 Managing Data Sources

Example Scenario
A Plant Administrator or Industrial Edge Box Operator would like to configure the data
acquisition from the S7-Protocol (S7-300/400/1200/1500) controller, and subsequently would
like to create value from the acquired data.

Prerequisite
The SIMATIC S7 Connector Configurator must be running.

Procedure
To configure S7-Protocol (S7-300/400/1200/1500) controller data source, follow these steps:
1. Launch the SIMATIC S7 Connector Configurator.
The Configurator home page is displayed.
2. Click "Add Data Source" in the upper-left corner under the "S7 Connector" tab.
The "Add" dialog box is displayed as follows:

SIMATIC S7 Connector Configurator V1.4

18 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.1 Managing Data Sources

3. Select the S7-Protocol (S7-300/400/1200/1500) data source type from the "Data Source
Type" drop-down.
The fields are displayed as follows:

4. Complete the following fields:

Field Name Definition

Name Defines the name of the data source. It must be unique.
IP Address Defines the IP address of the S7-Protocol (S7-300/400/1200/1500) con‐
troller with the desired data points.
Rack Number Defines the rack of the S7-Protocol (S7-300/400/1200/1500) controller.
The default value is 0.
Slot Number Defines the slot of the S7-Protocol (S7-300/400/1200/1500) controller.
The default value is 1.
PLC Type Specifies the PLC type.
Full Text Alarms Enables the full text alarms. This field is displayed when you select "PLC
Type" as 300/400.
This checkbox is enabled only when project runtime is not running.
*All the fields are mandatory.
5. Click "Add".
The data source is added and displayed in the "Data Source" table.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 19
Working with SIMATIC S7 Connector Configurator
6.1 Managing Data Sources

6.1.2 Configure Optimized S7-Protocol (S7-1200/1500) Data Source

You can configure Optimized S7-Protocol (S7-1200/1500) controller data source in the SIMATIC
S7 Connector Configurator. The Configurator allows you to configure the Optimized S7-Protocol
(S7-1200/1500) communication channel to the SIMATIC PLCs for data acquisition.

Example Scenario
A Plant Administrator or Industrial Edge Box Operator would like to configure the data
acquisition from the Optimized S7-Protocol (S7-1200/1500) controller, and subsequently would
like to create value from the acquired data.

Prerequisite
The SIMATIC S7 Connector Configurator must be running.

Procedure
To configure Optimized S7-Protocol (S7-1200/1500) controller data source, follow these steps:
1. Launch the SIMATIC S7 Connector Configurator.
The Configurator home page is displayed.
2. Click "Add Data Source" in the upper-left corner under the "S7 Connector" tab.
The "Add" dialog box is displayed as follows:

SIMATIC S7 Connector Configurator V1.4

20 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.1 Managing Data Sources

3. Select the Optimized S7-Protocol (S7-1200/1500) data source type from the "Data Source
Type" drop-down.
The fields are displayed as follows:

4. Complete the following fields:

Field Name Definition

Name Defines the name of the data source. It must be unique.
PLC Type Specifies the PLC type.
IP Address Defines the IP address of the Optimized S7-Protocol (S7-1200/1500) con‐
troller with the desired data points.
Access Level Specifies the access level. The available options are as follows:
1. No Access(complete protection)
2. Full Access(no protection)
Access Password Defines the access password. This field is enabled when you select "Access
Level" as No Access(complete protection).
For more information, refer How to Configure Access Password?
(Page 77)
*All the fields are mandatory.
5. Click "Add".
The data source is added and displayed in the "Data Source" table.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 21
Working with SIMATIC S7 Connector Configurator
6.1 Managing Data Sources

6.1.3 Configure OPC-UA Data Source

You can configure OPC-UA server data source in the SIMATIC S7 Connector Configurator. The
Configurator allows you to configure the OPC-UA communication channel for data acquisition
using different OPC-UA messaging modes.

Example Scenario
A Plant Administrator or Industrial Edge Box Operator would like to configure the data
acquisition from the PLC's OPC-UA Server, and subsequently would like to create value from the
acquired data.

Prerequisite
The SIMATIC S7 Connector Configurator must be running.

Procedure
To configure OPC-UA server data source, follow these steps:
1. Launch the SIMATIC S7 Connector Configurator.
The Configurator home page is displayed.
2. Click "Add Data Source" in the upper-left corner under the "OPC-UA Connector" tab.
The "Add" dialog box is displayed as follows:

SIMATIC S7 Connector Configurator V1.4

22 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.1 Managing Data Sources

3. Select the OPC UA (OPC Server) data source type from the "Data Source Type" drop-down.
The fields are displayed as follows:

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 23
Working with SIMATIC S7 Connector Configurator
6.1 Managing Data Sources

4. Complete the following fields:

Field Name Definition

Name Defines the name of the data source. It must be unique.
OPC-UA URL Defines the IP address of the OPC-UA server with the desired data points.
Port number Defines the port number of the IP address of the OPC UA server.
Authentication Mode Specifies the authentication. The available options are as follows:
1. "Anonymous": On selecting this option, you do not need any authen‐
tication.
2. "UserID & Password": On selecting this option, you must enter the
username and password that you used when configuring the OPC-UA
server in the TIA Portal.
User ID Defines the username that you used when configuring the OPC-UA server
in the TIA Portal. This field appears when authentication mode is selected
as "UserID & Password".
Password Defines the password that you used when configuring the OPC-UA server
in the TIA Portal. This field appears when authentication mode is selected
as "UserID & Password".
Messaging Mode Specifies the messaging mode. The available options are as follows:
1. "None": It specifies no security.
2. "Sign": It specifies secure communication with signed client and server
certificates.　
3. "Sign and Encrypt": It specifies secure communication with signed cli‐
ent and server certificates with additional security where the data is
encrypted from server application and sent to the client.
Security Policy Specifies the security policies. The available options are as follows:
1. Basic128Rsa15
2. Basic256
3. Basic256Sha256
You must ensure that your selected security policy matches the algorithm
that was used to generate the certificates from the TIA portal.
This field appears when messaging mode is selected as "Sign" or "Sign and
Encrypt".
Client PKCS12 file Specifies the client certificate which is exported from the TIA portal.
This field appears when a security policy is selected in "Security Policy" field.
You can protect the Project by selecting the "Project Protection" option in
the TIA portal. Subsequently, the "Certificate Manager" is enabled to ex‐
port the certificate in '.p12' format.
When you export the "Client PKCS12 file" from the TIA portal, a password
window is displayed. You can define your own password. The same pass‐
word is used in "PKCS12 Import Password" field in the SIMATIC S7 Connec‐
tor Configurator.

SIMATIC S7 Connector Configurator V1.4

24 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.1 Managing Data Sources

Field Name Definition

PKCS12 Import Pass‐ Defines the password that you used when exporting the "Client PKCS12
word file" from the TIA portal. This is used to extract the client certificate data in
the backend.
This field appears when a file is selected in "Client PKCS12 file" field.
Server DER certificate Specifies the server certificate which is exported from the TIA portal.
This field appears when a security policy is selected in "Security Policy" field.
You can protect the Project by selecting the "Project Protection" option in
the TIA portal. Subsequently, the "Certificate Manager" is enabled to ex‐
port the certificate in '.der' format.
*All the fields are mandatory.
5. Click "Add".
The data source is added and displayed in the "Data Source" table.
For more information on client and server certificates, refer How to Generate OPC-UA Client and
Server Certificates? (Page 69)

Note
• It is not mandatory to sync time between IED and PLC with UTC. By default, the IED time is
published in case of OPC-UA Tags.
• To ensure there is no data loss PLC cycle should be lower than or equal to the Acquisition cycle
in the Configurator.
• If you configure secure OPC-UA connection using certificates, you must ensure that the
certificates generated in the PLC must not be of future time. (PLC/OPC-UA server time should
not be future time.)
• User has to ensure the sampling and publishing interval should be less than or equal to the
Acquisition cycle configured in OPCUA for no data loss.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 25
Working with SIMATIC S7 Connector Configurator
6.1 Managing Data Sources

Note
OPC-UA Support for Non-Siemens PLC
SIMATIC S7 Connector Configurator supports reading of the tag values from non-Siemens PLC for
OPC-UA connection. It supports PLC Type: OMRON NX102-1200 with Firmware version: V1.31.
When you configure non-Siemens PLCs for example OMRON, you must provide the address of
the tag in following format:
ns=urn:OMRON:NxOpcUaServer:FactoryAutomation;s="<Tag_name>"
OPC-UA connection with authentication and messaging mode is not supported for OMRON PLC.

6.1.4 Edit Data Source

You can edit a data source in the SIMATIC S7 Connector Configurator and update the required
details. The updated details are configured for the data source.

Prerequisite
• The SIMATIC S7 Connector Configurator must be running.
• A data source must be available.

SIMATIC S7 Connector Configurator V1.4

26 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.1 Managing Data Sources

Procedure
To edit a data source, follow these steps:
1. Launch the SIMATIC S7 Connector Configurator.
The Configurator home page is displayed.
2. Click under the "Actions" column of the data source that you want to edit.
The "Edit Data Source" dialog box is displayed.
3. Modify the relevant details.
Note
You cannot edit the "Connection Name" and "IP Address" for a data source once it is at
Industrial Edge Runtime (project deployed and started).

4. Click "Save".
The data source is modified and displayed in the "Data Source" table.

6.1.5 Delete Data Source

You can delete a data source in the SIMATIC S7 Connector Configurator. The "Data Source" table
is updated with the updated list of the data sources. You must deploy the project using "Deploy"
button to reflect the deleted configuration.
You cannot delete data sources while 'start project', 'stop project', or 'deploy project' operation
is running.

Prerequisite
• The SIMATIC S7 Connector Configurator must be running.
• A data source must be available.

Procedure
To delete a data source, follow these steps:
1. Launch the SIMATIC S7 Connector Configurator.
The Configurator home page is displayed.
2. Select the data source records that you want to delete.
3. Click "Delete" in the upper-left corner.
A confirmation message is displayed.
4. Click "OK".
The data sources are deleted and removed from the "Data Source" table.
The deleted data is hidden and only after click on "Deploy" it is deleted from the Industrial
Edge Runtime.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 27
Working with SIMATIC S7 Connector Configurator
6.2 Managing Tags/Data Points

6.2 Managing Tags/Data Points

6.2.1 Add Tags

You can add a data point or tag from a data source in the SIMATIC S7 Connector Configurator.

Prerequisite
• The SIMATIC S7 Connector Configurator must be running.
• A data source must be available.

SIMATIC S7 Connector Configurator V1.4

28 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.2 Managing Tags/Data Points

Procedure
To add data points from a data source, follow these steps:
1. Launch the SIMATIC S7 Connector Configurator.
The Configurator home page is displayed.
2. Click under the "Actions" column of the data source to which you want to add a tag.
The "Add Tags" dialog box is displayed based on the data source as follows:
For S7-Protocol (S7-300/400/1200/1500):

Note
• Only the 'Char' data type supports the array feature for S7-Protocol
(S7-300/400/1200/1500) data source in the configurator, but the data is published as
simple scalar values for each array elements.
• If you have configured string datatype in TIA Portal, then you need to provide the length
of the string when configuring the tag in S7 Connector or by default the string length is
set to 210 for S7-Protocol (S7-300/400/1200/1500). For more information, refer
section Fixed Length String (Page 81).
With "Configurator Version" as 1.2, all the array elements are published as scalar Char value.
Any value change notification of one child element results in publishing of only that child tag
value.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 29
Working with SIMATIC S7 Connector Configurator
6.2 Managing Tags/Data Points

SIMATIC S7 Connector Configurator V1.4

30 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.2 Managing Tags/Data Points

For Optimized S7-Protocol (S7-1200/1500):

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 31
Working with SIMATIC S7 Connector Configurator
6.2 Managing Tags/Data Points

Note
• Optimized S7-Protocol (S7-1200/1500) data source does not support the array feature.
• If you have configured string datatype in TIA Portal, then you need to provide the length
of the string when configuring the tag in S7 Connector or by default the string length is
set to 254 for Optimized S7-Protocol (S7-1200/1500). For more information, refer section
Fixed Length String.
For OPC UA (OPC Server):

Note
• The array data for OPC UA (OPC Server) data source is published as simple scalar value as
String and Pipe separated.
• OPC UA (OPC Server) data source does not support the "String Length" field.

SIMATIC S7 Connector Configurator V1.4

32 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.2 Managing Tags/Data Points

3. Complete the following fields:

Field Name Definition

Name Defines the name of the data point. It must be unique.
Comments Defines the comments.
Address Defines the address of the data point in the controller or on the server.
For an OPC-UA server connection, the address must have the following syn‐
tax: ns=3; s=<DATA_BLOCK>.<TAG>
Replace the "<DATA_BLOCK>" and "<TAG>" placeholders with the correspond‐
ing address of the data point.
Data Type Specifies the data point type. For more information on the data types,
refer Data Types (Page 81).
The "Data Type" drop-down displays the data type options based on the data
source as follows:
• S7-Protocol (S7-300/400/1200/1500) supports Bool, Int, Byte, Dint, Real,
String, Word, USInt, Uint, UDInt, Dword, Date, Time, Char, DateTime, and
Char Array.
For more information on String data type, refer How to Configure String
Datatype in S7-Protocol (S7-300/400/1200/1500)? (Page 68)
• Optimized S7-Protocol (S7-1200/1500) supports Bool, Int, Byte, Dint, Re‐
al, String, Word, Lint, Sint, USInt, Uint, UDInt, ULInt, Lreal, Dword, Lword,
Date, Time, TOD, Ltime, LTOD, Char, and DateTime.
The 'DateTime' data type is not supported for S7-1200 PLCs.
• OPC UA (OPC Server) supports Bool, Int, Byte, Dint, Real, String, Word,
Lint, Sint, USInt, Uint, UDInt, ULInt, Lreal, Dword, Lword, Char, Bool Array,
Int Array, Dint Array, String Array, Word Array, Lint Array, Sint Array, Uint
Array, Udint Array, ULInt Array, Real Array, Dword Array, LWOrd Array, and
Lreal Array.
String Length Defines the string length to read the correct tag value.
If you have configured fixed length string datatype in TIA Portal, then you
must enter the correct string length in this field to read the correct tag value.
Array Enables the array feature. Array feature is used to accumulate different PLC
values in one array as required.
Array Size Defines the size of the array.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 33
Working with SIMATIC S7 Connector Configurator
6.2 Managing Tags/Data Points

Field Name Definition

Acquisition Cycle Specifies the acquisition cycle with which the data is sent to the Databus. The
available options are as follows:
• 10 milliseconds
• 50 milliseconds
• 100 milliseconds
• 250 milliseconds
• 500 milliseconds
• 1 second
• 2 second
• 5 second
• 10 second
As a rule, the '1 second' acquisition cycle is used.
Only OPC-UA supports highspeed acquisition cycle support of 10 milliseconds
and 50 milliseconds.
Acquisition Mode Specifies the acquisition mode of the data. The available options are as fol‐
lows:
• CyclicContinuous
• CyclicOnChange
OPC-UA and Optimized S7 Protocol (S7-1200/1500) data source type support
only "CyclicOnChange".
Access Mode Specifies the access mode of the tags. You can configure the tags as readable,
writable, or both readable-writable. The available options are as follows:
• "Read": This access mode is applicable only for 'Read' configured tags.
• "Read and Write": With this access mode, the value can be 'Read' and
'Write'.
*All the fields are mandatory.
You can add multiple data points as required by clicking under the "Actions" column.
4. Click "Add Tags".
The data points are added below the data source.

6.2.2 Edit Tags

You can edit a data point or tag in the SIMATIC S7 Connector Configurator and update the
required details. The updated details are configured for the data source.

Prerequisite
• The SIMATIC S7 Connector Configurator must be running.
• A data source and a data point must be available.

SIMATIC S7 Connector Configurator V1.4

34 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.2 Managing Tags/Data Points

Procedure
To edit a data point, follow these steps:
1. Launch the SIMATIC S7 Connector Configurator.
The Configurator home page is displayed.
2. Click under the "Actions" column of the data point that you want to edit.
The "Edit Tag" dialog box is displayed.
Note
You cannot edit the "Tag Name", "Acquisition Mode", "Data Type", and "Access Mode" for a tag
once it is at Industrial Edge Runtime.

3. Modify the relevant details.

4. Click "Save".
The data point is modified and displayed in the "Data Source" table.

6.2.3 Import Tags

The SIMATIC S7 Connector Configurator allows you to import multiple data points or tags
simultaneously from a TIA Portal project. You can select a file with the datapoints from the TIA
Portal and export it from the TIA Portal and import it to the SIMATIC S7 Connector Configurator.
The file must correspond to the '.xml' file type.
In addition, S7-Protocol (S7-300/400/1200/1500) data source supports import of '.xls' file. The
'.xls' format support is not from TIA Portal but from TagConverter Tool.
For more information, refer How to Export Tags from TIA Portal? (Page 62)

Prerequisite
• The SIMATIC S7 Connector Configurator must be running.
• The required data points file must be available.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 35
Working with SIMATIC S7 Connector Configurator
6.2 Managing Tags/Data Points

Procedure
To import the data points, follow these steps:
1. Launch the SIMATIC S7 Connector Configurator.
The Configurator home page is displayed.
2. Click under the "Actions" column of the data source to which you want to import the data
points.
The "Open" dialog box is displayed as follows:

3. Select the required file and click "Open".

The "Import" dialog box is displayed as follows:

It displays the valid tags in ‘success’ section, duplicate tags and existing tags already loaded
in the configurator in ‘warning’ section, and tags having invalid data types in ‘failure’ section.
You can click "Details" hyperlink to view the invalid datatype tags details.

SIMATIC S7 Connector Configurator V1.4

36 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.2 Managing Tags/Data Points

4. Click "OK".
The "Import Tags" dialog box is displayed as follows:

Note
• You can use in "Name" column to align the tag name. By default, the tag name is left
aligned.
• The duplicate tags are displayed in the red box. You can edit the tag name using .

5. Specify the acquisition cycle, acquisition mode, and access mode using "Acquisition Cycle",
"Acquisition Mode", and "Access Mode" drop-down respectively.
6. Mark true against the tags that you want to import and click "Add Tags".
The tags are added below the data source.

6.2.4 Browse Tags

The SIMATIC S7 Connector Configurator allows you to browse the data points or tags from a PLC
and add them to the data source. Only OPC-UA and Optimized S7-Protocol (S7-1200/1500) data
source types support the Browse Tags functionality.

Prerequisite
• The SIMATIC S7 Connector Configurator must be running.
• A data source must be available.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 37
Working with SIMATIC S7 Connector Configurator
6.2 Managing Tags/Data Points

Procedure
To browse the data points, follow these steps:
1. Launch the SIMATIC S7 Connector Configurator.
The Configurator home page is displayed.
2. Click under the "Actions" column of the data source of which you want to browse the data
points.
The "Browse" dialog box is displayed as follows:

It displays the valid tags in ‘success’ section and duplicate tags and existing tags already
loaded in the configurator in ‘warning’ section.

SIMATIC S7 Connector Configurator V1.4

38 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.2 Managing Tags/Data Points

3. Click "OK".
The "Browsed Tags" dialog box is displayed as follows:

You can use Datablock and tag filters to filter the required tags. A datablock is an array of tags.
The "Datablock Filter" drop-down field lists all the datablocks available in the PLC. You can use
the "Datablock Filter" drop-down to select the required datablocks. Once you select the
datablocks and click , the tags that are present in the selected datablocks are displayed. In
addition, you can use "Tag Filter" field to further filter the tags.
Note
• Only Optimized S7-Protocol (S7-1200/1500) supports "Datablock Filter" and "Tag Filter"
fields.
• Browsing data is cached for already browsed Optimized S7-Protocol (S7-1200/1500)
connection. But only the last browsed data depending on filters is cached.
• You can use in "Name" column to align the tag name. By default, the tag name is left
aligned.
• The duplicate tags are displayed in the red box. You can edit the tag name using .

4. Specify the acquisition cycle, acquisition mode, and access mode using "Acquisition Cycle",
"Acquisition Mode", and "Access Mode" drop-down respectively.
5. Mark true against the tags that you want to add and click "Add Tags".
The tags are added below the data source.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 39
Working with SIMATIC S7 Connector Configurator
6.2 Managing Tags/Data Points

6.2.5 Bulk Publish Tags

The SIMATIC S7 Connector Configurator allows you to group the data points or tags from the PLCs
and publish them together as a group using the "Bulk Publish" functionality. When any tag value
is updated in a group, then only the updated tag is published. All tags in same connection fall
under one group and the group name is 'default'.
The "Bulk Publish" feature is enabled by default. Click in the upper-right corner. The "Settings"
dialog box is displayed as follows:

You cannot update the "Bulk Publish" checkbox as single publish is not supported.

Supported Quantity Structure

The Supported Quantity Structure for SIMATIC S7 Connector is as follows:

Connection Type Acquisition Cycle Publish Mode Maximum Configurable

(ms) Tags
S7-Protocol 1000 Bulk 6000
(S7-300/400/1200/1500)
Optimized S7-Protocol 1000 Bulk 6000
(S7-1200/1500)
OPC UA (OPC Server) 1000 Bulk 4000
S7-Protocol 100 Bulk 600
(S7-300/400/1200/1500)
Optimized S7-Protocol 100 Bulk 600
(S7-1200/1500)
OPC UA (OPC Server) 10 Bulk 50

SIMATIC S7 Connector Configurator V1.4

40 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.2 Managing Tags/Data Points

The maximum connection supported by each driver is as follows:

• S7-Protocol (S7-300/400/1200/1500): 20
• Optimized S7-Protocol (S7-1200/1500): 8
• OPC UA (OPC Server): 20

Note
Test conditions
Mqtt Clients: The benchmarking result was obtained using one MQTT publisher client
(S7 Connector) and one lightweight MQTT subscriber client (open source MQTT Node.js client)
in a test run of five hours. For a higher number of publishers or subscribers, the supported tags
will be lower.
Connections: The benchmarking result was obtained with below mentioned number of
connections:
• S7-Protocol (S7-300/400/1200/1500): 4
• Optimized S7-Protocol (S7-1200/1500): 8
• OPC UA (OPC Server): 6
Above quantity structure can be achieved by keeping number of connections less in the Bulk
Publish mode. For higher number of connections, the supported tags will be lower.
Optimized S7-Protocol (S7-1200/1500) NFR was performed with all unique PLCs to get the
optimal result.

6.2.6 Delete Tags

You can delete a tag/data point in the SIMATIC S7 Connector Configurator. The "Data Source"
table is updated with the updated list of the data points. You must deploy the project using
"Deploy" button to reflect the deleted configuration.
You cannot delete data points while 'start project', 'stop project', or 'deploy project' operation is
running.

Prerequisite
• The SIMATIC S7 Connector Configurator must be running.
• A data source and data point must be available.

Procedure
To delete a data point, follow these steps:
1. Launch the SIMATIC S7 Connector Configurator.
The Configurator home page is displayed.
2. Select the tag/data point records that you want to delete.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 41
Working with SIMATIC S7 Connector Configurator
6.3 Managing Project

3. Click "Delete" in the upper-left corner.

A confirmation message is displayed.
4. Click "OK".
The data points are deleted and removed from the "Data Source" table.
The deleted data is hidden and only after click on "Deploy" it is deleted from the Industrial
Edge Runtime.

6.3 Managing Project

6.3.1 Configure Settings

When you click in the upper-right corner. The "Settings" dialog box is displayed as follows:

You can perform the following tasks:

Define IE Databus Service Name

You can define the IE Databus service name in this field.

Specify Username and Password

You can connect the SIMATIC S7 Connector Configurator to Industrial Edge Databus to publish
the data. The Industrial Edge Databus allows you to create a user and topics to this user. You must

SIMATIC S7 Connector Configurator V1.4

42 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.3 Managing Project

create topics for alarms and tags data to the user in the Industrial Edge Databus. The topic name
must be as follows:
• "ie/m/j/simatic/v1/s7c1/dp" for tags metadata
where ie: industrial edge, m: metadata, j: json, s7c1: SIMATIC S7 Connector instance 1, dp:
datapoint.
• "ie/d/j/simatic/v1/s7c1/dp/r/#" for tags data
where ie: industrial edge, d: data, j: json, s7c1: SIMATIC S7 Connector instance 1, dp:
datapoint
• "ie/m/j/simatic/v1/s7c1/ev" for alarms metadata
where ie: industrial edge, m: metadata, j: json, s7c1: SIMATIC S7 Connector instance 1, ev:
event.
• ie/d/j/simatic/v1/s7c1/ev/# for alarms data
where ie: industrial edge, d: data, j: json, s7c1: SIMATIC S7 Connector instance 1, dp:
datapoint
• ie/s/j/simatic/v1/s7c1/status for Connector and Connector diagnostic
status
where ie: industrial edge, s: status, j: json, s7c1: SIMATIC S7 Connector instance 1
When you create a user in Industrial Edge Databus, you define a username and password for the
user. You must specify this username and password combination in the "UserName" and
"Password" fields. Using this credential, the SIMATIC S7 Connector Configurator establishes
connection to Industrial Edge Databus.

Specify Configuration Version

You can specify the configuration version of the SIMATIC S7 Connector Configurator as required.
The available options are as follows:
• 1.1 (Deprecated)
• 1.2
For more information, refer Configuration Version 1.1 vs 1.2 (Page 81).

Bulk Publish
By default, the bulk publish is always enabled. You cannot update the "Bulk Publish" checkbox as
single publish is not supported. For more information, refer Bulk Publish Functionality (Page 40).

Specify Browse Timeout

You can specify the browse timeout in this field.

6.3.2 Deploy Project

Once you configure the data sources and tags/data points, you can deploy the project to the
Industrial Edge Runtime. You can select the required data points of each data source that you
want to deploy, and only the selected data points are deployed. When you deploy the data points
to the Industrial Edge Runtime, the configuration is saved and loaded to the Industrial Edge
Runtime.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 43
Working with SIMATIC S7 Connector Configurator
6.3 Managing Project

The SIMATIC S7 Connector Configurator allows you to edit or delete the data points or import the
new data points without stopping the Industrial Edge Runtime. When you deploy and start the
project using "Deploy" and "Start Project" buttons respectively, you can again use the "Deploy"
button to deploy the changes while the Industrial Edge Runtime is still running.
When you deploy the changes, Connector birth message and Connector status data is published
along with the metadata. For more information on metadata publish, refer JSON structure for
Alarms and Tags Metadata? (Page 57)
While the Industrial Edge Runtime is running, you cannot perform the following tasks:
• Configuring OPC UA (OPC Server) data source with Authentication and Messaging Mode
connection
• Configuring Full Text Alarms

Prerequisite
• The SIMATIC S7 Connector Configurator must be running.
• A data source and a data point must be available.

Procedure
To deploy a data point, follow these steps:
1. Launch the SIMATIC S7 Connector Configurator.
The Configurator home page is displayed.
2. Mark true against the data points that you want to deploy.

SIMATIC S7 Connector Configurator V1.4

44 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.3 Managing Project

3. Click "Deploy" in the upper-right corner.

The "Deploy" dialog box is displayed as follows:

4. Select the required Industrial Edge Devices on which you want to deploy the changes.
5. Click "Deploy".
The Configurator takes a while to deploy the project, and a success message is displayed
subsequently. The data points are deployed and downloaded, and a green check mark is
displayed next to the selected data points.

Note
1. You can deploy the changes only when the Industrial Edge Devices are in "Online" state.
2. Mass deployment feature (deploying to multiple Industrial Edge Devices) is available only
when Industrial Edge Runtime for the selected Industrial Edge Devices is not running.
3. You must manually start, configure project when Industrial Edge Runtime is started, and stop
the project by launching the UI of that Industrial Edge Device.
4. Before performing mass deployment, you must ensure that same user credentials and topic
are already added in the IE Databus Configurator for all the selected Industrial Edge Devices
where you want to perform the mass deployment.
5. After deploy operation is successful, state of metadata client will be visible under Bus Adaptor
icon.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 45
Working with SIMATIC S7 Connector Configurator
6.3 Managing Project

6.3.3 Start Project

Once you successfully deploy the project to the Industrial Edge Runtime, the "Start Project"
button is enabled. You can start the project using this button. When you start the project, you
start the Industrial Edge Runtime. The Industrial Edge Runtime reads the data point values and
sends this data to the Industrial Edge Databus.
Once you start the Industrial Edge Runtime, the applications that have access to the Industrial
Edge Databus can evaluate this data and use it for their own purposes.
When Industrial Edge Runtime is started, Connector 　and Connection status is published along
with the Tag and Event data to the broker (IE Databus).

Prerequisite
• The SIMATIC S7 Connector Configurator must be running.
• A data source and a data point must be available.
• A data point must be deployed to the Industrial Edge Runtime as described in Deploy Project
(Page 43).

Procedure
To start a project, follow these steps:
1. Launch the SIMATIC S7 Connector Configurator.
The Configurator home page is displayed.
2. Click "Start Project" in the upper-right corner.
The Configurator takes a while to start the project and a success message is displayed
subsequently.
After completion of start operation , state of Tagdata and Alarmdata client will be visible
under Bus Adaptor icon.
Connection state of PLC’s that are deployed under runtime will be visible under Connection
state icon.

6.3.4 Stop Project

Once you successfully start the project, and the Industrial Edge Runtime starts the data transfer
to the Industrial Edge Databus, the SIMATIC S7 Connector Configurator converts the "Start
Project" button to "Stop Project" button.
The "Stop Project" button allows you to stop the data transfer to the Industrial Edge Databus. You
can use the "Stop Project" button anytime to stop the Industrial Edge Runtime.
When Industrial Edge Runtime is stopped, the 'will' message of Connector is published to the
broker (IE Databus) indicating that clients are disconnected from the broker.
A new start of the project is only possible after new deploy.

SIMATIC S7 Connector Configurator V1.4

46 Operating Manual, 10/2021, A5E50594971-AC
Working with SIMATIC S7 Connector Configurator
6.4 Import/Export Configuration

Prerequisite
• The SIMATIC S7 Connector Configurator must be running.
• A data source and a data point must be available.
• The Industrial Edge Runtime must be running as described in Start Project (Page 46).

Procedure
To stop a project, follow these steps:
1. Launch the SIMATIC S7 Connector Configurator.
The Configurator home page is displayed.
2. Click "Stop Project" in the upper-right corner.
The Configurator takes a while to stop the project, and a success message is displayed
subsequently. The Industrial Edge Runtime stops the data transfer to the Industrial Edge
Databus.
After Stop operation is completed, state of clients under Bus Adapter icon and connection
state of PLC will be set to default state.

6.3.5 Verify Configuration

You can create a data flow using SIMATIC Flow Creator application to verify the configurations
of the SIMATIC S7 Connector Configurator. The values can be displayed using the MQTT Broker
Node. SIMATIC S7 Connector sends the data to the IE Databus using the following topic:
• For tags data: ie/d/j/simatic/v1/s7c1/dp/r/#
• For tags metadata: ie/m/j/simatic/v1/s7c1/dp
• For alarms data: ie/d/j/simatic/v1/s7c1/ev/#
• For alarms metadata: ie/m/j/simatic/v1/s7c1/ev
• For Connector and Connection status: ie/s/j/simatic/v1/s7c1/status

6.4 Import/Export Configuration

The SIMATIC S7 Connector Configurator allows you to import and export the configuration. This
functionality is helpful when you want to use an existing configuration of one Industrial Edge
Device (IED) in other IEDs. This enables to take the back-up of the configuration and restore it as
required. You can export the configuration file from the required IED and import this
configuration file in the desired IED where you want to use this configuration. The configuration
file is a JSON file, and is exported in .json format.
You can modify the configuration file to update the connection and datapoints details and
import the file in the configurator. You must modify the config data as per the schema. You can

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 47
Working with SIMATIC S7 Connector Configurator
6.4 Import/Export Configuration

find the schema file -https://signin.siemens.com/idp/profile/SAML2/Redirect/SSO? execu-

tion=e1s1&_eventId_proceed=1.

Note
• You must not modify the SystemData and checksum key.
• You cannot add Optimized S7 Connection (1200/1500) with legitimization enabled.
• You cannot add OPC UA Connection with authentication or messaging mode enabled.
• You cannot add Optimized S7 Tags with symbolic address.
• You cannot change "isBrowse" key value in Optimized S7 and OPC UA connection.

To import and export the configuration, you can use and icons respectively present in the
upper-right corner.

Note
You can import configuration files of V1.1 and V1.2. When you import V1.1 configuration file in
V1.2, the payload is applied as per V1.1 settings. Single mode is changed to Bulk and tag Id is
published in tag data payload.

SIMATIC S7 Connector Configurator V1.4

48 Operating Manual, 10/2021, A5E50594971-AC
Additional Information 7
7.1 How to Write Tags?
SIMATIC S7 Connector supports the 'Tag Write' functionality. This enables you to write a tag. You
must add a topic in IE Databus in following format to write a tag:
ie/d/j/simatic/v1/s7c1/dp/w/<connection-name>
For example, ie/d/j/simatic/v1/s7c1/dp/w/s7plus
The JSON payload structure for Bulk subscribe is as follows:

Where, seq: unique sequence number of the payload.

vals: array of data points published in the payload.
id: unique identification of data point. You must fetch the tag ID from metadata payload based
on the tag name.
qc: quality code. It is an optional field. It provides specific integer value to indicate the quality of
the data point value.
ts: timestamp of the data point. It is an optional field. it is in ISO 8601 Zulu format.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 49
Additional Information
7.2 Topic Structure for Data and Metadata

val: value of the Tag. Based on the data type of the data point, the value can be simple scalar
value.

Note
You can use the metadata to get the tag id published from the SIMATIC S7 connector for 'Tag
Write' functionality. You can use this tag Id in the Publisher (MQTT) to write value for that tag.
If you have configured fixed length string datatype in TIA Portal, then you need to provide the
length of the string when configuring the tag in S7 Connector or by default the string length is
set to 210 for S7-Protocol (S7-300/400/1200/1500). For more information, refer section Fixed
String Length (Page 81).
If you have configured fixed length string datatype in TIA Portal, then you need to provide the
length of the string when configuring the tag in S7 Connector or by default the string length is
set to 254 for Optimized S7-Protocol (S7-1200/1500). For more information, refer section Fixed
String Length.

For more information on Bulk Publish, refer Bulk Publish Tags. (Page 40)
For more information on topic format structure, refer Topic Structure for Data and Metadata
(Page 50).

7.2 Topic Structure for Data and Metadata

This section describes the topic structure for Data and Metadata. The recommended structure of
topic naming is as follows:
ie/{payloadType}/{encoding}/{msgStructureScheme}/
{msgStructureSchemeVersion}/{provideAppInstanceId}/{payloadMsgType}
and it is made of the following elements:
ie/{payloadType}/{encoding}/{msgStructureScheme}/
{msgStructureSchemeVersion}/{provideAppInstanceId}/{payloadMsgType}/
{accessmode}/{connectionname}/{collectionname}
The following table explains the above elements:

Element Description Possible Values

payloadType This indicates what the payload contains. 'd' for data
'm' for metadata
encoding This indicates payload encoding. 'j' for JSON
msgStructureScheme This indicates payload format schema model. simatic
msgStructureScheme‐ This indicates payload format schema version v1
Version number
provideAppInstanceId This indicates unique id of provider app. 's7c1' for SIMATIC S7 Connector
instance 1
payloadMsgType This indicates payload message content. 'dp': DataPoints for PLC Varia‐
bles (process image)
'ev': Events for PLC Fulltext
Alarms, HMI Alarms

SIMATIC S7 Connector Configurator V1.4

50 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.2 Topic Structure for Data and Metadata

Element Description Possible Values

accessmode This is an app specific element. This indicates 'r' for Read from Connectors
the purpose of the payload for SIMATIC S7 'w' for write to Connectors
Connector as it would support both read and
write of Data Points.
connectionname This is an app specific element. This indicates Paintshop1PLC
unique name provided in Connector for a con‐
nection to a PLC in SIMATIC S7 Connector.
collectionname This is an app specific element. This indicates 'default' for Tags published in
the collection name. bulk mode

7.2.1 JSON structure for Alarms and Tags Data

You can create a topic in IE Databus to publish the alarms and tags data.

Tags Data
With the "Bulk Publish" feature, all tags data is published under single group with topic name as:
ie/d/j/simatic/v1/s7c1/dp/r/<connection-name>/default
The JSON structure is as follows:

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 51
Additional Information
7.2 Topic Structure for Data and Metadata

Where, seq: unique sequence number of the payload.

vals: array of data points published in the payload.
id: unique identification of data point. You must fetch the tag ID from metadata payload based
on the tag name.
qc: quality code. It provides specific integer value to indicate the quality of the data point value.
qc value will be published in decimal which represents the sixth and seventh bit in the quality
data.

Value Meaning Description

0 BAD The value is not useful for reasons indicated by the sub-status.
1 UNCERTAIN The quality of the value is less than normal, but the value may still be useful. The reason
is indicated by the sub-status.
2 GOOD (non-cascade) The quality of the value is good.
3 GOOD (cascade) The quality of the value is good and may be used in control.

SIMATIC S7 Connector Configurator V1.4

52 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.2 Topic Structure for Data and Metadata

16-bit quality is defined as below:

Extended quality code

With "Configurator Version" as 1.2, along with qc, qx is published which holds all the bits data:
quality code, sub status, extended sub status, flags, and limit. qx is published in decimal value,
for example,192. You must convert it into binary to get the bit information.
Only if when any of the bits '0 to 5' and '8 to 15' is 1, the qx field is published.
With Configurator version 1.2, along with qc, qx is published if and only if when any of the bits
'0 to 5' and '8 to 15' is 1.

Limits (bits 0,1)

Sub-status "BAD" (sub-status bits 2..5)

Value Meaning Description

0 Non-specific There is no specific reason why the value is BAD.
1 Configuration error The value is not useful because of some inconsistency regarding the
configuration.
2 Not connected The value is not reliable because the connection to the provider has
been disconnected at consumer-side. For example, a communication
driver actively disconnects from a PLC on user request or by design.
4 Sensor failure The value is not useful because it cannot be converted. A value from the
device (PLC) cannot be converted to the corresponding HMI tag.
5 No communica‐ The value is not useful because the communication to the data source
tion, with last usa‐ failed, however a last known value is available.
ble value
6 No communica‐ The value is not useful because the communication to the data source
tion, no usable val‐ failed or has never been established since it was last out of service and
ue a last known value is not available.
7 Out of service The value is not reliable because the provider side has been disabled or
shutdown. For example, a PLC is in stop mode or a tag is disabled for
maintenance purposes.

Sub-status "UNCERTAIN" (sub-status bits 2..5)

Value Meaning Description

0 Non-specific There is no specific reason why the value is UNCERTAIN.
1 Last usable value The connection to the data source is still established, however, the data
source stopped updating the value for some reason.
2 Substitute value A predefined value is used in case of an invalid value due to communi‐
cation issues with the data source or a range violation. The reason for
providing substitute values is configurable.
3 Initial value A predefined value intended for the startup of the HMI system (or a sub-
ordinate device) is used while not being able to provide values from the
data source.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 53
Additional Information
7.2 Topic Structure for Data and Metadata

Value Meaning Description

5 Range violation The value lies outside the range defined by minimum value and maxi‐
mum value. The limits define which direction (min or max) has been
exceeded.
6 Sub-normal A value derived from multiple values has less than the required number
of good sources. This includes data aggregation by means of data com‐
pression algorithms.

Sub-status "GOOD (cascade)" (sub-status bits 2..5)

Value Meaning Description

0 Non-specific No error or special condition is associated with this value.
6 Local override The value has been overridden by the user or some logic in to continue
operation. Typically, the input has been disconnected and a manually
entered value has been 'forced', or a value has been corrected.

Quality (bits 6,7)

Value Meaning Description

0 BAD The value is not useful for reasons indicated by the sub-status.
1 UNCERTAIN The quality of the value is less than normal, but the value may still be
useful. The reason is indicated by the sub-status.
2 GOOD (non-cas‐ The quality of the value is good.
cade)
3 GOOD (cascade) The quality of the value is good and may be used in control.

Extended sub-status "BAD" (sub-status (bits 8..11))

Value Meaning Description

0 Non-specific No CHROM specific extended bad sub-status is associated with this val‐
ue.
1 Aggregated value The value has been calculated out of multiple values with less than the
required number of good sources. This includes data aggregation by
means of data compression algorithms. The corresponding sub-status is
set to 'non-specific'.
3 Unusable value A (logged) value has been identified to be incorrect, but a respective
correction value is not available. The corresponding sub-status is set to
'non-specific'.
7 Disabled The provider of the value (logging tag for logged value) has been disa‐
bled and the previous value was BAD. The corresponding sub-status is
taken from the last (previous) sub-status.

SIMATIC S7 Connector Configurator V1.4

54 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.2 Topic Structure for Data and Metadata

Extended sub-status "UNCERTAIN" (sub-status (bits 8..11))

Value Meaning Description

0 Non-specific No CHROM specific extended uncertain sub-status is associated with
this value.
1 Aggregated value The value has been calculated out of multiple values with less than the
required number of good sources to be GOOD as well as less than re‐
quired number of bad sources to be BAD. This includes data aggregation
by means of data compression algorithms. The corresponding sub-sta‐
tus is set to 'non-specific'.
7 Disabled The provider of the value (logging tag for logged value) has been disa‐
bled and the previous value was GOOD or UNCERTAIN. In case of GOOD,
the corresponding sub-status is set to 'last usable value'. In case of UN‐
CERTAIN, the corresponding sub-status is taken from the last (previous)
sub-status.

Extended sub-status "GOOD (cascade)" (sub-status (bits 8..11))

Value Meaning Description

0 Non-specific No CHROM specific extended good sub-status is associated with this
value.
1 Aggregated value The value has been calculated out of multiple (good) values. This in‐
cludes data aggregation by means of data compression algorithms. The
corresponding sub-status is set to 'non-specific'.
2 Manual input A (logged) value has been created manually. The corresponding sub-
status is set to 'non-specific'.
3 Corrected value A (logged) value has been corrected. The corresponding sub-status is
set to 'non-specific'.
4 Last usable value The local data source has been initialized with the last usable value if
present inside a local persistency. The corresponding sub-status is set to
'non-specific'.
6 Initial value The local data source has been initialized with the configured initial
value. The corresponding sub-status is set to 'non-specific'.

Flags (bit 12..15)

Value Meaning Description

Bit 12 Source quality The data quality has been determined and assigned by external data
source.
Bit 13 Source time The data timestamp has been produced and assigned by external data
source.
Bit 14 Time corrected The data timestamp applied by external data source has been corrected
by the system. Thus, Bit 13 "Source time" is not set.
Time correction happens if the external timestamp is older than the
timestamp of the last known value.

ts: timestamp of the data point. it is in ISO 8601 Zulu format.

val: value of the Tag. Based on the data type of the data point, the value can be simple scalar
value.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 55
Additional Information
7.2 Topic Structure for Data and Metadata

Alarms Data
On the other hand, the 'Bulk Publish Functionality' does not apply for alarms data. The topic
format for alarms data is as follows:
ie/d/j/simatic/v1/s7c1/ev/<connection-name>/FullText
The JSON structure is as follows:

Where, evs: array of events published in the payload.

area: string containing the configured area information of the event.
clsName: name of the class of the event.
evTxt: event text. This may contain array of objects based on the event source.
evTxtExt: array of string containing additional texts of the events.
id: unique identification of the event.
modificationTime: event's last modified timestamp in UTC format.
name: name of the event.

SIMATIC S7 Connector Configurator V1.4

56 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.2 Topic Structure for Data and Metadata

origin: string containing the origin of the event.

params: array of parameters of the event.
raisedTime: event's raised timestamp in UTC format.
state: integer that indicates the state of the event (provider specific).

Value Description
0 Normal
1 Alarm is raised.
2 Raised and cleared.

seq: unique sequence number of the payload.

7.2.2 JSON structure for Alarms and Tags Metadata

When you deploy a project as described in Deploy Project (Page 43), the metadata is also
published.

Note
You must discover the tag information from the metadata payload.

Tags Metadata
The topic format for tags metadata is as follows:
ie/m/j/simatic/v1/s7c1/dp
where ie: industrial edge, m: metadata, j: json, s7c1: SIMATIC S7 Connector instance 1, dp:
datapoint.
With the "Bulk Publish" feature, the JSON structure for tags metadata is as follows:

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 57
Additional Information
7.2 Topic Structure for Data and Metadata

Alarms Metadata
The topic format for alarms metadata is as follows:
ie/m/j/simatic/v1/s7c1/ev
where ie: industrial edge, m: metadata, j: json, s7c1: SIMATIC S7 Connector instance 1, ev:
event.
The JSON structure for alarms metadata is as follows:

SIMATIC S7 Connector Configurator V1.4

58 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.2 Topic Structure for Data and Metadata

Note
Alarms metadata is published only when you deploy S7 Connection with 'Full Text Alarm'
checkbox enabled before starting the project.
Once you start the Industrial Edge Runtime, you cannot configure 'Full Text Alarms' checkbox.
Therefore, the alarms metadata is not published in this case.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 59
Additional Information
7.2 Topic Structure for Data and Metadata

7.2.3 Connector and Connection Status

When you successfully deploy a project, the Connector birth message, connector status
message and the metadata are published as follows:

When you successfully start a project, the Connector and Connection status are published with
tag and alarm data packet as follows:

SIMATIC S7 Connector Configurator V1.4

60 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.2 Topic Structure for Data and Metadata

When you successfully stop a project, the Connector Will message is published by the broker as
follows:

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 61
Additional Information
7.3 How to Export Tags from TIA Portal?

Note
• In Connector status data – status: “available” indicates connector is up and started. status:
“unavailable” indicates connector is down.
• In Connector status data – status: “bad” indicates at least one of the connector clients is not
connected to the IE Databus. More information will be provided in the reason field of
Connector data.
• In Connector status data – status: “good” indicates all the connector clients are connected to
the IE Databus.
• In Connection status data – status: “bad” indicates connection to target device could not be
established.
• In Connection status data – status: “good” indicates connection with target device is
established.

7.3 How to Export Tags from TIA Portal?

7.3.1 Export Tags for S7-Protocol (S7-300/400/1200/1500) and Optimized S7-

Protocol (S7-1200/1500) Connection
PLC Tag Tables can be exported from TIA Portal for S7-Protocol (S7-300/400/1200/1500) and
Optimized S7-Protocol (S7-1200/1500) connection. To export the XML file, follow these steps:
1. Go to TIA Portal where PLC is configured.
2. Go to PLC Tags folder.
3. Click on Tag Table.

SIMATIC S7 Connector Configurator V1.4

62 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.3 How to Export Tags from TIA Portal?

4. Click on "Export" icon.

The "Export" dialog box is displayed. Specify the file name with .xml extension as follows:

5. Click "OK".
The XML file is exported.
From TIA Portal, only XML file format is supported in the SIMATIC S7 Connector Configurator.
Tags in Data Blocks cannot be exported from the TIA Portal. This can be done in SIMATIC
Manager. You can configure a 'Project' for S7 Classic PLC in STEP 7 SIMATIC Manager and can use
this 'Project' to create an excel sheet or XML file which can be imported in S7-Protocol

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 63
Additional Information
7.3 How to Export Tags from TIA Portal?

(S7-300/400/1200/1500) connection in SIMATIC S7 Connector Configurator. The procedure

steps are as follows:
1. Create a project in SIMATIC Manager and save the project.

2. Open SIMATIC WinCC Tag Converter Tool.

SIMATIC S7 Connector Configurator V1.4

64 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.3 How to Export Tags from TIA Portal?

3. Click on "Create a new converter template" to create the template file. Select the Path to save
template file and choose s7p (*.s7p) project created from SIMATIC Manager.

4. Click "Create".
5. Select the Tags from data Block and Symbols that you want to be added in the excel sheet or
XML file.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 65
Additional Information
7.3 How to Export Tags from TIA Portal?

6. Provide Connection Name and choose the output format as .xlsx or .xml as required.

7. Click "Convert".
The file is exported.

SIMATIC S7 Connector Configurator V1.4

66 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.3 How to Export Tags from TIA Portal?

7.3.2 Export Tags for OPC-UA Connection

You can export both PLC Tags and Datablock tags from TIA Portal for OPC-UA. To export the XML
file, follow these steps:
1. Go to TIA portal where PLC is configured.
2. Right-click on PLC and click "Properties" as follows:

3. Click "OPC UA" > "Server" > "Export" section in "Properties" window as follows:

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 67
Additional Information
7.4 How to Configure String Datatype in S7-Protocol (S7-300/400/1200/1500)?

4. Click "Export OPC UA XML file" button.

5. Provide the file name to store the tags in XML file and click "Save".
The file is exported.
The exported file may look as follows:

7.4 How to Configure String Datatype in S7-Protocol

(S7-300/400/1200/1500)?
To configure string datatype in S7-Protocol (S7-300/400/1200/1500), you must specify the
address based on offset formed in TIA Portal. The format is as follows:
<DataBlock>. <DataBlock Offset>
For example, Tag 11 < string Type> in Data Block 1 (DB1)

Off set of Tag 11 (String tag) is 22 as depicted in the above image. The address format for Tag11
(String tag) is 'DB1.DBB22'.

SIMATIC S7 Connector Configurator V1.4

68 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.5 How to Generate OPC-UA Client and Server Certificates?

You can configure the string tag data type in S7-Protocol (S7-300/400/1200/1500) as follows:

You can monitor string value in TIA Portal to cross check Data Block offsets.

7.5 How to Generate OPC-UA Client and Server Certificates?

SIMATIC S7 Connector Configurator provides the following two messaging modes for secure
communication in OPC-UA:
1. Sign
2. Sign & Encrypt
"Sign & Encrypt" messaging mode enables you to encrypt the data that is sent after establishing
the communication.
For secure communication, you must create OPC-UA client and server certificates using TIA
Portal using the following steps:

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 69
Additional Information
7.5 How to Generate OPC-UA Client and Server Certificates?

Step 1: Protect the Project by selecting the "Project protection" option in TIA Portal.
1. Click on "Security settings" > "Settings".
A new window is displayed for project as follow:

2. Click "Protect this project".

The "Protect project" dialog box is displayed as follows:

SIMATIC S7 Connector Configurator V1.4

70 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.5 How to Generate OPC-UA Client and Server Certificates?

3. Enter the Project Credentials.

4. Ensure the "Certificate manger" option is enabled for the project.

Note
You must ensure the sampling and publishing interval should be less than or equal to the
Acquisition cycle configured in OPCUA with no data loss.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 71
Additional Information
7.5 How to Generate OPC-UA Client and Server Certificates?

Step 2: Enable Global Security Setting and prepare server and client certificates.
1. Select the device properties, click "Protection & Security" > "Certificate manager", and mark
true against "Use global security for certificate manager" checkbox.

2. In the "Device certificates", configure new security, and click "Add new" to add new certificate.

The "Create a new certificate" dialog box is displayed.

SIMATIC S7 Connector Configurator V1.4

72 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.5 How to Generate OPC-UA Client and Server Certificates?

3. Complete the following fields to create 'Server Certificate'.

– Select "Self signed" radio button.
– Define the "Common Name of Subject" as 'ServerCert'.
– Set the "Signature" as 'sha1RSA'.
– Specify the "Usage" as "OPC UA server" for server certificate.
– In "Subject Alternative Name (SAN)" field, define "IP" as IP of PLC. Delete all other fields of
SAN.

4. Complete the following fields to create 'Client Certificate'.

– Select "Self signed" radio button.
– Define the "Common Name of Subject" as 'ClientCert'.
– Set the "Signature" as 'sha1RSA'.
– Specify the "Usage" as "OPC UA client" for client certificate.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 73
Additional Information
7.5 How to Generate OPC-UA Client and Server Certificates?

– In "Subject Alternative Name (SAN)" field, define "URI" as 'urn:<hostname>:WCCILopcua'.

Delete all other fields of SAN.

SIMATIC S7 Connector Configurator V1.4

74 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.5 How to Generate OPC-UA Client and Server Certificates?

Note
• For client certificate, the hostname of the container is required where OPC-UA application
is running. Provide hostname as 's7connector' for client certificate.
• While creating the certificates, you must ensure that PLC/OPC-UA server time is not in
future time. As the certificates with future time will not be activated in SIMATIC S7
Connector Configurator when configured.

Step 3: Add the Server Certificate and Ciient Certificate in OPC-UA Security options.
1. In OPC UA Device properties section, enable the "Activate OPC UA server" option by marking
true against the checkbox.

2. In "Server certificate" option, upload the created server certificate.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 75
Additional Information
7.5 How to Generate OPC-UA Client and Server Certificates?

3. Select the following security policies for server functionality which corresponds 128-bit
encryption algorithms.

4. Add the client certificate in Trusted Client Certificate option.

5. Save the TIA Project and download the project to PLC.

SIMATIC S7 Connector Configurator V1.4

76 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.6 How to Configure Access Password?

Step 4: Export the certificate to use in SIMATIC S7 Connector Configurator.

1. Click "Security settings" > "Certificate manager".
The list of certificates is displayed as follows:

2. Right-click on the "servercert" and export the certificate in .der format.

3. Right-click on the "Clientcert" and export the certificate in ".p12" format.
When you export client PKCS12 file, the password window is displayed. Define your own
password. The same password must be entered in the "PKCS12 Import Password" field in SIMATIC
S7 Connector Configurator as this is used to extract the client certificate data in the backend.

Note
You can follow the above steps to create certificates with 'sha256RSA' signature value as well.

7.6 How to Configure Access Password?

SIMATIC S7 Connector Configurator supports the following two access levels in which a PLC can
be configured for Optimized S7-Protocol (S7-1200/1500) connection:
1. No Access (complete protection)
2. Full Access (no protection)
The 'Access Password' is required for 'No Access' access level.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 77
Additional Information
7.6 How to Configure Access Password?

To configure the access password, follow these steps:

1. Go to TIA portal where PLC is configured.
2. Right-click on PLC and click "Properties" as follows:

SIMATIC S7 Connector Configurator V1.4

78 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.6 How to Configure Access Password?

3. Click "Protection & Security" > "Access Level" section in "Properties" window as follows:

4. Select "No access" level and provide password for any of the above "Access level".

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 79
Additional Information
7.7 How to Configure S7-1200 PLC FW version 4.5?

7.7 How to Configure S7-1200 PLC FW version 4.5?

To support Tag read, write, and browsing function for Optimized S7-Protocol (S7-1200/1500)
connection for S7-1200 PLC with firmware version 4.5, you must ensure that TLS security is
disabled.

SIMATIC S7 Connector Configurator V1.4

80 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.9 Data Types

7.8 Configuration Version 1.1 vs 1.2

The SIMATIC S7 Connector Configurator provides you two configuration versions' support. You
can select configuration version 1.1 or 1.2 as required.
The following table provides you the comparative view of the functionalities which differ in
configuration version 1.1 and 1.2.

Functionality Configuration Version 1.1 Configuration Version 1.2

Metadata payload for S7 Char Data type of individual element is published Data type of individual element is published as
array as 'Char Array' in tag metadata payload. 'Char' in tag metadata payload.
Tag data payload for S7 Char With publish mode 'Bulk Publish', all elements The individual child elements data is publish‐
array are grouped together and published in a ed separately. Any change in notifications of
group. Any change in notification of any one one child element results in publishing of only
tag results in publishing of all the elements. that child tag value.
Quality code in tag data pay‐ Quality code with enum value {0,1,2, or 3} is Quality code with enum value {0,1,2, or 3} is
load published in tag data payload. published in tag data payload. But along
with qc, there is a new field qx which holds all
the bits data: quality code, sub status, exten‐
ded substatus, flag, and limit.
• Limits bits 0,1
• Sub-status bits 2..5
• Quality bits 6,7
• Extended sub-status 8..11
• Flags 12..15
Value in tag data payload Value is published as 'String'. Value is published as per the data type and not
in 'String'. For more information, refer Data
Types (Page 81).
Value in tag data payload for Value is published in 'String' while making a Value is published as per the data type while
tag write feature in mqtt pub‐ 'write' request to SIMATIC S7 Connector. making a 'write' request to SIMATIC S7 Con‐
lisher node nector.

Other functionalities for configuration version 1.1 remain same as configuration version 1.2 as
described in this manual.

7.9 Data Types

This section provides the information on the data types that are used in adding the tags. For
more information about the address formatting of data types, you must refer "TIA Portal
Documentation".

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 81
Additional Information
7.9 Data Types

The following table describes how the tag data is published:

Siemens Data Type Standard DataType JSON Data Type

BOOL Boolean INTEGER INTEGER
INT Int16
DINT Int32
USINT
UINT UInt16
UDINT UInt32
BYTE Byte
WORD
DWORD
SINT SByte
REAL Float REAL REAL
LREAL Double DOUBLE DOUBLE
LINT Int64 STRING STRING
ULINT UInt64
STRING String
LTIME LTIME is a 64 bit signed in‐
teger which represents a
duration in 100 nano-sec‐
ond intervals
TIME TIME is a 64 bit signed in‐
teger which represents a
duration in 100 nano-sec‐
ond intervals
TOD TIME_OF_DAY is a 64 bit
signed integer which rep‐
resents a duration in 100
nano-second intervals
LTOD LTOD is a 64 bit signed in‐
teger which represents a
duration in 100 nano-sec‐
ond intervals
Char
CHAR Array in S7
DynArray in OPCUA
DATETIME STRING (ISO 8601 Zulu
DATE (UTC) Format)

BOOL (bit)
An operand of data type BOOL represents a bit value and contains one of the following values:
• TRUE
• FALSE

SIMATIC S7 Connector Configurator V1.4

82 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.9 Data Types

The following table shows the properties of data type BOOL:

Length Format Value range Examples of value input

(bits)
1 Boolean FALSE or TRUE TRUE
BOOL#0 or BOOL#1 BOOL#1
BOOL#FALSE or BOOL#TRUE BOOL#TRUE
Unsigned integers (decimal system) 0 or 1 1
Binary numbers 2#0 or 2#1 2#0
Octal numbers 8#0 or 8#1 8#1
Hexadecimal numbers 16#0 or 16#1 16#1

Note
Applies to CPUs of the S7-1500 series
For a block with the block property "Optimized block access", the bit has a length of 1 byte.

BYTE
An operand of data type BYTE is a bit string of 8 bits.
The following table shows the properties of data type BYTE:

Length Format Value range Examples of value input

(bits) Constants Absolute and symbolic ad‐
dresses
8 Integers1) (decimal sys‐ Signed integers: -128 to • 15 • IB2
tem) +127 • BYTE#15 • MB10
Unsigned integers: 0 to 255
• BYTE#10#15 • DB1.DBB4
• B#15 • Tag_Name
Binary numbers 2#0 to 2#1111_1111 • 2#0000_1111
• BYTE#2#0000_ 1111
• B#2#0000_1111
Octal numbers 8#0 to 8#377 • 8#17
• BYTE#8#17
• B#8#17
Hexadecimal numbers 16#0 to 16#FF • 16#0F
• BYTE#16#0F
• B#16#0F
1)
The value range depends on the relevant interpretation or conversion.

Note
The BYTE data type cannot be compared for more than or less than. It can only be supplied with
the same decimal data that can be processed by the SINT and USINT data types.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 83
Additional Information
7.9 Data Types

CHAR
A tag of the CHAR (Character) data type has a length of 8 bits and occupies one BYTE of memory.
The CHAR data type stores a single character in ASCII coding. You can find information on the
encoding of special characters under "STRING".
The following table shows the value range of the CHAR data type:

Length Format Value range Example of value inputs

(bits)
8 ASCII characters ASCII character set 'A', CHAR#'A'

DATE
The DATE data type saves the date as an unsigned integer. The representation contains the year,
the month, and the day.
The contents of an operand of DATE data type correspond in hexadecimal format to the number
of days since 01-01-1990 (16#0000).
The following table shows the properties of data type DATE:

Length Format Value range Example of value inputs

(bytes)
2 IEC date D#1990-01-01 to D#2169-06-06 D#2009-12-31, DATE#2009-12-31
(Year-Month-Day)

DINT (32-bit integers)

An operand of data type DINT (Double INT) has a length of 32 bits and consists of two
components: a sign and a numerical value in the two's complement. The signal states of bits 0
to 30 represent the number value. The signal state of bit 31 represents the sign. The sign may
assume "0" for the positive, or "1" for the negative signal state.
An operand of data type DINT occupies four BYTE in the memory.

SIMATIC S7 Connector Configurator V1.4

84 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.9 Data Types

The following table shows the properties of data type DINT:

Length Format Value range Examples of value input

(bits)
32 Signed integers (decimal system) -2_147_483_648 to +2_147_483_647 • +125_790
• DINT#+125_790
• DINT#10#+125_790
• L#275
Binary numbers (only positive) 2#0 to • 2#0000_0000_0000_0001_
2#0111_1111_1111_1111_111 1110_1011_0101_1110
1_1111_1111_1111
• DINT#2#0000_0000_0000_
0001_1110_1011_0101_11
10
• DINT#2#10
Octal numbers (only positive) 8#0 to 8#177_7777_7777 • 8#36_5536
• DINT#8#36_5536
Hexadecimal numbers 16#0 to 16#7FFF_FFFF • 16#0001_EB5E
• DINT#16#0001_EB5E

Example
The following figure shows the integer +125790 as a binary number:

DWORD
An operand of data type DWORD is a bit string of 32 bits.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 85
Additional Information
7.9 Data Types

The following table shows the properties of data type DWORD:

Length Format Value range Examples of value input

(bits) Constants Absolute and symbolic ad‐
dresses
32 Integers (decimal sys‐ Signed integers: • +15_793_935 • MD10
tem) -2_147_483_647 to • DWORD# • DB1.DBD8
+2_147_483_647
+15_793_935 • Tag_Name
Unsigned integers: 0 to
• DWORD#10#
4_294_967_295
+15_793_935
• DW#+15_793_935
Binary numbers 2#0 to • 2#0000_0000_1111
2#1111_1111_1111_1 _0000_1111_1111_
111_1111_1111_1111_ 0000_1111
1111
• DWORD#2#0000_0
000_1111_0000_11
11_1111_0000_111 1
• DW#2#0000_0000_
1111_0000_1111_1
111_0000_1111
Octal numbers 8#0 to 8#37_777_777_777 • 8#74_177_417
• DWORD#8#74_177
_417
• DW#8#74_177_417
Hexadecimal numbers 16#0000_0000 to • 16#00F0_FF0F
16#FFFF_FFFF • DWORD#16#00F0_
FF0F
• DW#16#00F0_FF0F
Decimal sequence B#(0, 0, 0, 0) to B#(255, B#(127, 200, 127, 200)
255, 255, 255)

Note
The DWORD data type cannot be compared for more than or less than. It can only be supplied
with the same decimal data that can be processed by the DINT and UDINT data types.

INT (16-bit integers)

An operand of data type INT has a length of 16 bits and consists of two components: a sign and
a numerical value in the two's complement. The signal states of bits 0 to 14 represent the
number value. The signal state of bit 15 represents the sign. The sign may assume "0" for the
positive, or "1" for the negative signal state.
An operand of data type INT occupies two BYTE in the memory.

SIMATIC S7 Connector Configurator V1.4

86 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.9 Data Types

The following table shows the properties of data type INT:

Length Format Value range Examples of value input

(bits)
16 Signed integers (decimal system) -32_768 to +32_767 • +3_785
• INT#+3_785
• INT#10#+3_785
Binary numbers (only positive) 2#0 to 2#0111_1111_1111_1111 • 2#0000_1110_1100_1001
• INT#2#0000_1110_1100_
1001
• INT#2#10
Octal numbers (only positive) 8#0 to 8#7_7777 • 8#7311
• INT#8#7311
Hexadecimal numbers (only posi‐ 16#0 to 16#7FFF • 16#0EC9
tive) • INT#16#0EC9

LINT (64-bit integers)

An operand of data type LINT (Long INT) has a length of 64 bits and consists of two components:
a sign and a numerical value in the two's complement. The signal states of bits 0 to 62 represent
the number value. The signal state of bit 63 represents the sign. The sign may assume "0" for the
positive, or "1" for the negative signal state.
An operand of data type LINT occupies eight BYTE in the memory.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 87
Additional Information
7.9 Data Types

The following table shows the properties of data type LINT:

Length Format Value range Examples of value input

(bits)
64 Signed integers (decimal system) -9_223_372_036_854_775_808 to • +154_325_790_816_159
+9_223_372_036_854_775_807 • LINT#
+154_325_790_816_159
• LINT#10#
+154_325_790_816_159
Binary numbers (only positive) 2#0 to • 2#0000_0000_0000_0000_
2#0111_1111_1111_1111_1111 1000_1100
_1111_1111_1111_1111_1111_1 _0101_1011_1100_0101_1
111_1111_1111_1111_1111_11 11 111_0000_
1111_0111_1001_1111
• LINT#2#0000_0000_0000_0
000_1000
_1100_0101_1011_1100_0
101_1111_
0000_1111_0111_1001_11
11
• LINT#2#10
Octal numbers (only positive) 8#0 to • 8#4305_5705_7417_3637
8#7_7777_7777_7777_7777_77 77 • LINT#8#4305_5705_7417_3
637
Hexadecimal numbers (only posi‐ 16#0 to 16#7FFF_FFFF_FFFF_FFFF • 16#0000_8C5B_C5F0_F79F
tive) • LINT#16#0000_8C5B_C5F0_
F79F

LREAL
Operands of the data type LREAL have a length of 64 bits and are used to represent floating-
point numbers. An operand of the LREAL data type consists of the following three components:
• Sign: The sign is determined by the signal state of bit 63. The bit 63 assumes the value "0"
(positive) or "1" (negative).
• 11-bit exponents to base 2: The exponent is increased by a constant (base, +1023), so that
it has a value range of 0 to 2047.
• 52-bit mantissa: Only the fraction part of the mantissa is shown. The integer part of the
mantissa is always 1 with normalized floating-point numbers and is not stored.
The LREAL data type is processed with a precision of 15 digits.

SIMATIC S7 Connector Configurator V1.4

88 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.9 Data Types

The following table shows the properties of data type LREAL:

Length Format Value range Examples of value input

(bits)
64 Floating-point numbers according to -1.7976931348623157e+308 to 1.0e-5; LREAL#1.0e-5
IEEE754 -2.2250738585072014e-308
Floating-point numbers ±0.0 1.0; LREAL#1.0
+2.2250738585072014e-308 to
+1.7976931348623157e+308

Note
With floating-point numbers, only the precision defined by the IEEE754 standard is stored.
Additionally specified decimals are rounded off according to IEEE754.
The number of decimal places may decrease for frequently nested arithmetic calculations.
If more decimal places are specified than can be stored by the data type, the number is rounded
to the corresponding value of the precision allowed by this value range.

LTIME (IEC time)

The contents of an operand of data type LTIME is interpreted as nanoseconds. The
representation contains information for days (d), hours (h), minutes (m), seconds (s) and
milliseconds (ms), microseconds (us), and nanoseconds (ns).
The following table shows the properties of data type LTIME:

Length Format Value range Examples of value input

(bits)
64 Signed duration LT#-106751d_23h_47m_16s_854 LT#11350d_20h_25m_14s_830
ms_775us_808ns to LT# ms_652us_315ns,
+106751d_23h_47m_16s_854ms LTIME#11350d_20h_25m_14s_
_775us_807ns 830ms_652us_315ns

It is not necessary to specify all time units. LT#5h10s is therefore a valid entry, for example. If
only one unit is specified, the absolute value of days, hours, and minutes must not exceed the
high or low limits. When more than one time unit is specified, the value must not exceed 106751
days, 23 hours, 59 minutes, 59 seconds, 999 milliseconds, 999 microseconds, or 999
nanoseconds.

Note
In SIMATIC S7 Connector Configurator, LTIME value is published in nanoseconds which
represents a duration in 100 nanosecond intervals.

LTOD (LTIME_OF_DAY)
Data type LTOD (LTIME_OF_DAY) occupies two double words and stores the number of
nanoseconds since the beginning of the day (0:00 h) as unsigned integer.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 89
Additional Information
7.9 Data Types

The following table shows the properties of data type LTOD:

Length Format Value range Examples of value input

(bytes)
8 Time-of-day (hours:minutes: sec‐ LTOD#00:00:00.0000000 00 to LTOD#10:20:30.400_365_21 5,
onds.nanoseconds) LTOD#23:59:59.9999999 99 LTIME_OF_DAY#10:20:30.4
00_365_215

You always need to specify the hours, minutes, and seconds. The specification of nanoseconds
is optional.

Note
In SIMATIC S7 Connector Configurator, LTOD value is published in nanoseconds which
represents a duration in 100 nanosecond intervals.

LWORD
An operand of data type LWORD is a bit string of 64 bits.

SIMATIC S7 Connector Configurator V1.4

90 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.9 Data Types

The following table shows the properties of data type LWORD:

Length Format Value range Examples of value input

(bits)
64 Integers (decimal system) Signed integers: • +26_123_590_360_715
-9_223_372_036_854_775_808 to • LWORD#
+9_223_372_036_854_775_807
+26_123_590_360_715
Unsigned integers: 0 to
• LWORD#10#
18_446_744_073_709_551_615
+26_123_590_360_715
• LW#+26_123_590_360_715
Binary numbers 2#0 to • 2#0000_0000_0000_0000_
2#1111_1111_1111_1111_1111_11 0000_
1 1011_1110_0001_0010_11
1_1111_1111_1111_1111_1111_11 11_01
1 1_1111_1111_1111_1111 01_0010_1101_1110_1000
_1011
• LWORD#2#0000_0000_000
0_00
00_0000_1011_1110_0001
_0010
_1111_0101_0010_1101_1
110_1 000_1011
• LW#2#0000_0000_0000_00
00_0
000_1011_1110_0001_001
0_111
1_0101_0010_1101_1110_
1000_ 1011
Octal numbers 8#0 to • 8#13_724_557_213
8#1_777_777_777_777_777_777_7 • LWORD#8#13_724_557_21
77
3
• LW#8#13_724_557_213
Hexadecimal numbers 16#0000_0000 to • 16#0000_0000_5F52_DE8B
16#FFFF_FFFF_FFFF_FFFF • LWORD#16#0000_0000_5F
52_D E8B
• LW#16#0000_0000_5F52_D
E8B
Decimal sequence B#(0, 0, 0, 0, 0, 0, 0, 0) to B#(255, 255, B#(127, 200, 127, 200, 127,
255, 255, 255, 255, 255, 255) 200, 127, 200)

Note
The LWORD data type cannot be compared for more than or less than. It can only be supplied
with the same decimal data that can be processed by the LINT and ULINT data types.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 91
Additional Information
7.9 Data Types

REAL
Operands of the data type REAL have a length of 32 bits and are used to represent floating-
point numbers. An operand of the REAL data type consists of the following three components:
• Sign: The sign is determined by the signal state of bit 31. The bit 31 assume the value "0"
(positive) or "1" (negative).
• 8-bit exponents to basis 2: The exponent is increased by a constant (base, +127), so that it
has a value range of 0 to 255.
• 23-bit mantissa: Only the fraction part of the mantissa is shown. The integer part of the
mantissa is always 1 with normalized floating-point numbers and is not stored.
The REAL data type is processed with a precision of 6 digits.

Note
With floating-point numbers, only the precision defined by the IEEE754 standard is stored.
Additionally specified decimals are rounded off according to IEEE754.
The number of decimal places may decrease for frequently nested arithmetic calculations.
If more decimal places are specified than can be stored by the data type, the number is rounded
to the value corresponding to the precision allowed by this value range.

The following table shows the properties of data type REAL:

Length Format Value range Examples of value input

(bits)
32 Floating-point numbers according to -3.402823e+38 to -1.175495e-38 1.0e-5; REAL#1.0e-5
IEEE754 ±0.0
Floating-point numbers +1.175495e-38 to +3.402823e+38 1.0; REAL#1.0

SINT (8-bit integers)

An operand of data type SINT (Short INT) has a length of 8 bits and consists of two components:
a sign and a numerical value in the two's complement. The signal states of bits 0 to 6 represent
the number value. The signal state of bit 7 represents the sign. The sign may assume "0" for the
positive, or "1" for the negative signal state.
An operand of data type SINT occupies one BYTE in the memory.

SIMATIC S7 Connector Configurator V1.4

92 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.9 Data Types

The following table shows the properties of data type SINT:

Length Format Value range Examples of value input

(bits)
8 Signed integers (decimal system) -128 to +127 • +44
• SINT#+44
• SINT#10#+44
The value range extends to a
maximum of SINT#255 when us‐
ing the type SINT#. This value is
interpreted as an integer with -1.
Binary numbers (only positive) 2#0 to 2#0111_1111 • 2#0010_1100
• SINT#2#0010_1100
• SINT#2#10
Octal numbers (only positive) 8#0 to 8#177 • 8#54
• SINT#8#54
Hexadecimal numbers (only posi‐ 16#0 to 16#7F • 16#2C
tive) • SINT#16#2C
The value range extends to a
maximum of SINT#16#FF when
using the type SINT#. This value
is interpreted as an integer with
-1.

STRING
An operand of the STRING data type saves several characters in a character string that can consist
of up to 254 characters. In a character string, all characters of the codepage created on the
system are permitted. The characters are specified in single quotation marks.
A character string can also contain special characters. The escape character $ is used to identify
control characters, dollar signs, and single quotation marks.

Note
Different code pages
Please note that the special characters are coded using the code page currently set in Windows.
This means that a string that contains special characters can be displayed differently on a
different operating system with a different code page.
The dependency of the codepage on the created system makes an international use of the user
program more difficult. Only the characters from the 7-bit ASCII coding are internationally valid.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 93
Additional Information
7.9 Data Types

The following table shows the properties of a STRING tag:

Length Format Value range Examples of value input

(bytes)
n + 2 1) ASCII character string incl. special 0 to 254 characters • 'Name'
characters • STRING#'NAME'
• STRING#'Na... (The actual
length of the string is longer
than the space available on
the screen.)
• STRING#'' (The string is emp‐
ty.)
1)
An operand of the STRING data type occupies two bytes more than the specified maximum length in the memory.

Fixed Length STRING

An operand of the STRING data type saves several characters in a character string that can consist
of up to 254 characters. In a character string, all characters of the codepage created on the
system are permitted. The characters are specified in single quotation marks.
A character string can also contain special characters. The escape character $ is used to identify
control characters, dollar signs, and single quotation marks.

Note
Different code pages
Please note that the special characters are coded using the code page currently set in Windows.
This means that a string that contains special characters can be displayed differently on a
different operating system with a different code page.
The dependency of the codepage on the created system makes an international use of the user
program more difficult. Only the characters from the 7-bit ASCII coding are internationally valid.

The following table shows the properties of a STRING tag:

SIMATIC S7 Connector Configurator V1.4

94 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.9 Data Types

TIME (IEC time)

The contents of an operand of the data type TIME are interpreted as milliseconds. The
representation contains information for days (d), hours (h), minutes (m), seconds (s), and
milliseconds (ms).
The following table shows the properties of data type TIME:

Length Format Value range Examples of value input

(bits)
32 Signed duration T#-24d_20h_31m_23s_648ms to T# T#10d_20h_30m_20s_630ms,
+24d_20h_31m_23s_647ms TIME#10d_20h_30m_20s_630
ms

It is not necessary to specify all time units. T#5h10s is a valid entry, for example. If only one unit is
specified, the absolute value of days, hours, and minutes must not exceed the high or low limits.
When more than one time unit is specified, the value must not exceed 24 days, 23 hours, 59
minutes, 59 seconds, or 999 milliseconds.

Note
In SIMATIC S7 Connector Configurator, TIME value is published in nanoseconds which represents
a duration in 100 nanosecond intervals.

TIME_OF_DAY (TOD)
Data type TOD (TIME_OF_DAY) occupies a double word and stores the number of milliseconds
since the beginning of the day (0:00 h) as unsigned integer.
The following table shows the properties of data type TOD:

Length Format Value range Examples of value input

(bytes)
4 Time-of-day (hours:minutes: sec‐ TOD#00:00:00.000 to TOD#10:20:30.400,
onds.milliseconds) TOD#23:59:59.999 TIME_OF_DAY#10:20:30.40 0

You always need to specify the hours, minutes, and seconds. The specification of milliseconds
is optional.

Note
In SIMATIC S7 Connector Configurator, TOD value is published in nanoseconds which represents
a duration in 100 nanosecond intervals.

UDINT (32-bit integers)

An operand of data type UDINT (Unsigned Double INT) has a length of 32 bits and contains
unsigned numerical values.
An operand of data type UDINT occupies four BYTE in the memory.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 95
Additional Information
7.9 Data Types

The following table shows the properties of data type UDINT:

Length Format Value range Examples of value input

(bits)
32 Unsigned integers (decimal system) 0 to 4_294_967_295 • 4_042_322_160
• UDINT#4_042_322_160
• UDINT#10#4_042_322_160
Binary numbers 2#0 to 2#1111_1111_1111_1111 • 2#1111_0000_1111_0000_
_1111_1111_1111_1111 111 1_0000_1111_0000
• UDINT#2#1111_0000_1111
_0
000_1111_0000_1111_000
0
• UDINT#2#10
Octal numbers 8#0 to 8#377_7777_7777 • 8#360_7417_0360
• UDINT#8#360_7417_0360
Hexadecimal numbers 16#0 to 16#FFFF_FFFF • 16#F0F0_F0F0
• UDINT#16#F0F0_F0F0

UINT (16-bit integers)

An operand of data type UINT (Unsigned INT) has a length of 16 bits and contains unsigned
numerical values.
An operand of data type UINT occupies two BYTE in the memory.
The following table shows the properties of data type UINT:

Length Format Value range Examples of value input

(bits)
16 Unsigned integers (decimal system) 0 to 65_535 • 65_295
• UINT#65_295
• UINT#10#65_295
Binary numbers 2#0 to 2#1111_1111_1111_1111 • 2#1111_1111_0000_1111
• UINT#2#1111_1111_0000_
1 111
• UINT#2#10
Octal numbers 8#0 to 8#17_7777 • 8#17_7417
• UINT#8#17_7417
Hexadecimal numbers 16#0 to 16#FFFF • 16#FF0F
• UINT#16#FF0F

ULINT (64-bit integers)

An operand of data type ULINT (Unsigned Long INT) has a length of 64 bits and contains
unsigned numerical values.

SIMATIC S7 Connector Configurator V1.4

96 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.9 Data Types

An operand of data type ULINT occupies eight BYTE in the memory.

The following table shows the properties of data type ULINT:

Length Format Value range Examples of value input

(bits)
64 Unsigned integers (decimal system) 0 to 18_446_744_073_709_551_6 15 • 154_325_790_816_159
• ULINT#154_325_790_816_1
59
• ULINT#10#154_325_790_8
16_159
Binary numbers 2#0 to 2#1111_1111_1111_1111_11 • 2#0000_0000_0000_0000_
11_1111_1111_1111_1111_1 1000_1100_0
111_1111_1111_1111_1111_ 101_1011_1100_0101_111
1111_1111 1_0000_1111
_0111_1001_1111
• ULINT#2#0000_0000_0000
_0000_1000_
1100_0101_1011_1100_01
01_1111_000
0_1111_0111_1001_1111
• ULINT#2#10
Octal numbers 8#0 to 8#17_7777_7777_7777_7777 • 8#4305_5705_7417_3637
_7777 • ULINT#8#4305_5705_7417
_3637
Hexadecimal numbers 16#0 to 16#FFFF_FFFF_FFFF_FFFF • 16#0000_8C5B_C5F0_F79F
• ULINT#16#0000_8C5B_C5F
0_F79F

USINT (8-bit integers)

An operand of data type USINT (Unsigned Short INT) has a length of 8 bits and contains unsigned
numerical values:
An operand of data type USINT occupies one BYTE in the memory.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 97
Additional Information
7.9 Data Types

The following table shows the properties of data type USINT:

Length Format Value range Examples of value input

(bits)
8 Unsigned integers (decimal system) 0 to 255 • 78
• USINT#78
• USINT#10#78
Binary numbers 2#0 to 2#1111_1111 • 2#0100_1110
• USINT#2#0100_1110
• USINT#2#10
Octal numbers 8#0 to 8#377 • 8#116
• USINT#8#116
Hexadecimal numbers 16#0 to 16#FF • 16#4E
• USINT#16#4E

WORD
An operand of data type WORD is a bit string of 16 bits.
The following table shows the properties of data type WORD:

Length Format Value range Examples of value input

(bits) Constants Absolute and symbolic ad‐
dresses
32 Integers (decimal sys‐ Signed integers: -32_768 • 61_680 • MW10
tem) to +32_767 • WORD#61_680 • DB1.DBW2
Unsigned integers: 0 to
• WORD#10#61_6 80 • Tag_Name
65_535
• W#61_680
Binary numbers 2#0 to • 2#1111_0000_1111_
2#1111_1111_1111_111 0000
1
• WORD#2#1111_
0000_1111_0000
• W#2#1111_0000_111
1_0000
Octal numbers 8#0 to 8#177_777 • 8#170_360
• WORD#8#170_360
• W#8#170_360
Hexadecimal numbers 16#0 to 16#FFFF • 16#F0F0
• WORD#16#F0F0
• W#16#F0F0
BCD C#0 to C#999 C#55
Decimal sequence B#(0, 0) to B#(255, 255) B#(127, 200)

SIMATIC S7 Connector Configurator V1.4

98 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.10 Notes on use

Note
The WORD data type cannot be compared for more than or less than. It can only be supplied with
the same decimal data that can be processed by the INT and UINT data types.

7.10 Notes on use

The following restrictions apply with the delivery of the SIMATIC S7 Connector Configurator.

Configuration update
Whenever you change the configuration in the SIMATIC S7 Connector Configurator, the system
app on the respective Industrial Edge Device (IED) gets updated only when you click on the
"Deploy" button.
You can check the status of the configuration update using the tasks icon in the IED UI.

Multiple user access to system configurators

For the system configurators, it is not possible to use the same system configurator of an IED with
two or more users' instances at the same time. When another user launches a system
configurator at the same time while a current user is working with the same system
configurator, the second user will be blocked, and the primary users continues working with the
system configurator. Just when the primary user closes the system configurator, the second user
can launch the same system configurator.

Supported language
When you provide the needed information in input fields, the Industrial Edge Management
(IEM), the system configurators, and other components only support characters from the
English language. For example, when you add a data source and tag name with special
characters like "ö", "ä", or "ü", these characters are not supported and result in error messages.

Updating system configurators

• When you update the system configurators in the IEM, there is no specific defined sequence
for updating the configurators. For the update sequence of other components, refer https://
support.industry.siemens.com/cs/document/10979314
• If you are using IEM version v1.3, then all the system configurators must be updated to
version v1.3.
• When you update the system configurators, you must ensure to select the 'nginx conf' file
during the process. The selected file is displayed with green-check circle.
Before you update the system configurators, take a snapshot of the cluster respectively the VM.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 99
Additional Information
7.10 Notes on use

Job management for system configurators

The job management for all system configurators is not handled by the system configurators
themselves but by the IEM. In case of any job failure, you will be notified by the configurators.
In that case, check the jobs in the IED UI respectively in the IEM and delete the failed or skipped
jobs from the "Job Status" screen.

High speed acquisition cycle support in OPC-UA

You can configure OPC-UA tags with acquisition cycle of 10 milliseconds. You must follow below
criteria to get tags at 10 milliseconds cycle:
PLC Type: PLC with OPC-UA server which supports "Minimum sampling interval" and "Minimum
publishing interval" of 10 milliseconds. For example, CPU 1518-4 PN/DP.

Cycle time: For testing 10 milliseconds acquisition cycle, cycle time must be greater than 5
milliseconds and less than 9 milliseconds.

SIMATIC S7 Connector Configurator V1.4

100 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.10 Notes on use

CPU Spike Issue

Under resource constraints, the tags may be repeated with different timestamps within the
same packet. This behavior can happen temporarily under sudden spike in resource usage of
other processes limiting the resources availability for SIMATIC S7 Connector. To reproduce this
scenario, follow these steps:
1. Configure an IED VM with 1CPU core count and 2GB RAM.
2. Install SIMATIC S7 Connector, IE Databus, IE Flow Creator, and IE Cloud Connector
applications.
3. Configure datapoints in SIMATIC S7 Connector with low acquisition cycle supported by the
connection.
If tags are repeated and you are interested only in the newest data available in the packet, then
follow these steps:
• Parse the tag data packet received from the broker.
• Create a map with "id" as the key to hold the unique tag values.
• In case "id" is repeated, replace the tag data which has maximum "ts" value in the packet.
If tags are repeated and you are interested in all the packets with no data loss, then follow these
steps:
• Parse the tag data packet received from the broker.
• Create a multi-map with "id" as the key to hold the multiple tag values for the same tag.
• Sort the tags with increasing order of timestamp before processing/storage.

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 101
Additional Information
7.11 Known issues

Data Publishing Interval

TIME, LTIM, TOD, and LTOD values are published as nanosecond in 100 nanoseconds intervals.

7.11 Known issues

The following are the known issues:

Issue Troubleshooting
The delta download of S7+ connections for legitimization -
from "NoAccess" to "FullAccess" does not work.
You will get no response from the UI after you click on "De‐ Close and reopen the SIMATIC S7 Connector Configurator. Per‐
ploy", "Start", and "Stop". In that case, the operation remains in form again the required operation.
progress state and buttons are disabled.
S7-1200 PLCs are not supported for OPC-UA connection in the -
S7 Connector Configurator.
The following data types are not supported for the "TagWrite" -
operation:
• S7 data sources: DATE, TIME, and CHAR ARRAY
• S7+ data sources: DATE
• OPC-UA data sources: ARRAY, SInt, and USInt
Editing of "CHAR ARRAY" data types for S7 connections is not -
supported.
The browse feature is provided as preview for ease of config‐ Configure manually the tags or import the exported files from
uration; hence the following issues are known with regard to the TIA Portal.
this feature: The browse feature is provided as beta functionality in V1.2.0,
• When the browsing data source (OPC-UA server or PLC) has the complete feature will be available in V1.3.0.
a large number of tags, it takes approximately 2 minutes to
display the tag list.
• When the browsing data source (OPC-UA server or PLC) has
not responded within 2 minutes, a time out error occurs.
• When you browse S7+ data sources, editing these data
sources and browsed tags are not supported.
Sporadically, the browsing feature may fail due to any reason Configure the tags manually or import the exported files from
after several attempts. the TIA Portal.
Browsing S7+ data sources is not supported for ET200 Open -
Control PLCs.
Manual adding of symbolic addresses for S7+ tags is not sup‐ Symbolic addresses are only supported in browsing S7+ data
ported. sources.
Delta download of full text alarms for S7-300 and S7-400 PLCs Full text alarms are only supported in S7-300 and S7-400 PLCs
is not supported. in the full download configuration. To get full text alarms, stop
the project and download the project with S7-300 or S7-400
PLCs.
When you browse an OPC-UA server from a project in the Configure manually the OPC-UA tags or use the exported
TIA Portal with 1 function block (FB) and several data block "*.xml" file of the DB instances from the TIA Portal.
(DB) instances, only data of 1 DB instance is returned and thus
results in false read data.

SIMATIC S7 Connector Configurator V1.4

102 Operating Manual, 10/2021, A5E50594971-AC
Additional Information
7.11 Known issues

Issue Troubleshooting
Deleting a configuration of the SIMATIC S7 Connector by click‐ -
ing the "Delete Configuration" button under the "My Installed
Apps" menu entry starts a task on the according Edge Device
but fails immediately.
A maximum array size of 999 is supported for the "CHAR AR‐ -
RAY" data type in S7 connections.
If you import a configuration file, which was exported from the Use imported files which are exported from a version ≥ 1.0.6.
IEM through a SIMATIC S7 Connector Configurator version less Browse all S7+ connections and then click "Deploy".
than 1.0.6, into the SIMATIC S7 Connector Configurator, full
downloads fail if there are S7+ tags with symbolic address.
If you import a configuration file, which was exported from the Use imported files which are exported from a version ≥ 1.0.9.
IEM through a SIMATIC S7 Connector Configurator version less Alternatively, you can check data sources again after import‐
than 1.0.9, into the SIMATIC S7 Connector Configurator, full ing and eliminate the duplicate tag names.
and delta downloads fail if you use duplicate tag names in the
same connection or if you use tag names with unsupported
characters.
If column widths were resized previously, the column widths Resize the column widths again.
will be reset to default size due to the following scenarios:
• Browser window is resized
• Browser window is refreshed
• Configurator is relaunched
If the number of tags is more than 4000 or if you import re‐ -
spectively browse tags, the response of resizing columns be‐
comes slow, and you may observe flickering of the UI.
If before completion of the mass deployment operation, you You must wait for the completion of mass deployment opera‐
launch the UI in one of the selected Industrial Edge Devices, tion before launching UI in other Industrial Edge Device which
then new configuration is not reflected in the Industrial Edge was selected as part of the mass deployment.
Device.
Mass deployment feature is available only when Industrial You must manually start, configure project when Industrial
Edge Runtime for the selected Industrial Edge Device is not Edge Runtime is started, and stop the project by launching the
running. UI of that Industrial Edge Device and perform these operations.
If you select Industrial Edge Device where Industrial Edge Run‐ You must explicitly start the Industrial Edge Runtime in those
time is running, then after the mass deployment the project Industrial Edge Device once again.
will be stopped in those Industrial Edge Devices.
SIMATIC S7 Connector Configurator publishes tag data to brok‐ -
er using unreliable Qos policy -Qos0. This may result in some
packet loss.
In SIMATIC S7 Connector Configurator, you can browse maxi‐ This is the NFR limit of OPC-UA browser. If you want to browse,
mum of 2000 tags in OPC-UA connection. If PLC contains more then you must use a PLC Project with less than 2000 tags.
than 2000 Tags, then "Browse Timeout" error is displayed.
S7+ browsing is not supported for following PLC type and FW -
version:
• CPU 1513F-1 PN V2.8
• CPU 1518-4 PN/DP V2.8
• CPU 1518F-4 PN/DP V2.6.1
• CPU 1512SP-1 PN V2.8
S7+ driver supports maximum of eight connections. In the S7 -
Connector project, you can configure maximum eight Opti‐
mized S7-Protocol (S7-1200/1500).

SIMATIC S7 Connector Configurator V1.4

Operating Manual, 10/2021, A5E50594971-AC 103
Additional Information
7.11 Known issues

Issue Troubleshooting
S7 Connector publishes multiple instances of same tag with You must ensure S7 Connector gets enough CPU to process all
different timestamp to broker when IED CPU is overloaded. the packets and send to broker.
This is done to ensure that no data loss happens even if there
is data delay because of low CPU resources.
In Optimized S7-Protocol (S7-1200/1500), filter is supported -
only for Datablocks. Tag filter based on M, Q, and I area is not
yet supported.
In OPC-UA data source, You can edit the exported OPC-UA XML file and Import it in
• Browsing functionality does not support "Browse Filter" SIMATIC S7 Connector Configurator. You can add/modify the
tag name, address namespace, and datatype. For more infor‐
with tag name and datablock.
mation, refer Export Tags for OPC-UA Connection (Page 67).
• Browsing is possible only of tags with namespace greater
than 0.
The download fails for a project with 6000 tags if the tag name It is recommended to use smaller tag names and connection
and connection name are long (200-254 bytes). names, if you want to download large number of tags.
If legitimization is enabled in PLC and the full access is selected -
in the configurator, then you can browse PLC tags but not dat‐
ablocks. There is no protection available for PLC tags regard‐
less of the legitimization level. The PLC tags can always be
browsed.
SIMATIC S7 Connector Configurator V1.3 is incompatible with You must update both SIMATIC S7 Connector Configurator and
previous versions of the run-time application. the run-time application to V1.3.
Total memory limit of SIMATIC S7 Connector Runtime is 920 -
MB.
Connection state of PLC and clients will be displayed after -
10seconds from the actual state.

SIMATIC S7 Connector Configurator V1.4

104 Operating Manual, 10/2021, A5E50594971-AC