Simatic Net PC Software Commissioning PC Stations - Manual and Quick Start
Simatic Net PC Software Commissioning PC Stations - Manual and Quick Start
Preface
2
SIMATIC NET Getting started
DCOM security 3
PC software
Commissioning PC Stations - 4
Examples
Manual and Quick Start
Tools 5
Configuration Manual
05/2021
C79000-G8976-C156-21
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.
This manual…
… supports you when commissioning your SIMATIC NET PC modules in a PC station and helps
you to use them successfully.
… introduces all the tools made available by the SIMATIC NET software for solving your
communication tasks.
... answers your questions about communication together with the supplied OPC
documentation:
References /.../
References to other manuals and documentation are indicated by numbers in slashes /.../.
These numbers refer to the titles of manuals listed in the References section at the end of the
manual.
Trademarks
The following and possibly other names not identified by the registered trademark sign ® are
registered trademarks of Siemens AG:
SIMATIC NET, HARDNET, SOFTNET, CP 1612, CP 1613, CP 5612, CP 5613, CP 5614, CP 5622
(http://support.automation.siemens.com/WW/llisapi.dll?func=cslib.csinfo2&aktprim=99&lang
=en)
Apart from news, there you will also find:
• Project information: Manuals, FAQs, downloads, application examples etc.
• Contacts, Technical Forum
• The option submitting a support query:
(https://support.automation.siemens.com/WW/llisapi.dll?func=cslib.csinfo&lang=en&objid
=38718979&caller=view)
• Our service offer:
Right across our products and systems, we provide numerous services that support you in
every phase of the life of your machine or system - from planning and implementation to
commissioning, through to maintenance and modernization.
You will find contact data on the Internet at the following address:
(http://www.automation.siemens.com/partner/guiwelcome.asp?lang=en)
Security information
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).
Security recommendations
To prevent unauthorized access, note the following security recommendations.
General
• You should make regular checks to ensure that the software meets these
recommendations and/or other security guidelines.
• The "SIMATIC NET PC Software" undergoes continuous development to make it more
secure. We strongly recommend that product updates are applied as soon as they are
available and that the latest product versions are used. In addition, we recommend
installing the latest security updates of the Microsoft .NET Framework and the Microsoft
SQL Server 2019 on your PC systems.
• When using the "SIMATIC NET PC Software" make sure that you have sufficient system
resources for their use. Required resources and configuration of the PC station must match
your specific application/configuration limit. General notes from Microsoft regarding
memory usage and CPU load must be taken into account. If system resources are no
longer available, error-free operation of the "SIMATIC NET PC Software" can no longer be
guaranteed.
• When the internal and external network are disconnected, an attacker cannot access
internal data. Therefore, operate the software only within a protected network area.
• We strongly recommend that you do not connect communication modules
– without an activated firewall
– without a VPN connection
directly to the Internet. Without suitable protective measures there is a risk of
unauthorized access to the module.
Physical access
Restrict physical access to the device to qualified personnel.
Preface ................................................................................................................................................... 3
1 The SIMATIC PC-Station ....................................................................................................................... 13
1.1 Overview ........................................................................................................................... 13
1.2 A brief introduction to tools and utilities............................................................................. 16
1.3 Guide to installation and commissioning ............................................................................ 17
1.3.1 PG mode or configured mode - Considerations ................................................................... 17
1.3.2 Commissioning for PG mode - Overview ............................................................................. 19
1.3.3 Commissioning for configured mode - Overview ................................................................ 20
2 Getting started .................................................................................................................................... 23
2.1 "Configured mode" ............................................................................................................ 23
2.1.1 Steps in project engineering............................................................................................... 24
2.1.2 Steps for initial configuration ............................................................................................. 26
2.1.2.1 Case a) Initial configuration via remote configuration with STEP 7 ...................................... 27
2.1.2.2 Case b) Initial configuration with XDB file ........................................................................... 30
2.1.2.3 Case c) Initial configuration using the "Station Configuration Editor" ................................... 32
2.2 "PG mode" ......................................................................................................................... 35
2.2.1 Configuration for PG mode - HMI stations........................................................................... 36
2.3 Using additional functions - points to note ......................................................................... 37
2.3.1 Checking the configuration and diagnostics ....................................................................... 37
2.3.2 Testing with OPC Scout V10 ............................................................................................... 37
2.3.2.1 Detecting communication errors with OPC Scout V10 ......................................................... 37
2.3.3 Further functions / special features..................................................................................... 39
2.3.3.1 Applying the configuration, symbols and SIMOTION Scout.................................................. 39
2.3.3.2 Points to note with SOFTNET Industrial Ethernet modules ................................................... 40
2.4 Configuring the OPC server ................................................................................................ 41
2.4.1 Significance of project engineering .................................................................................... 42
2.4.2 Configuring the properties of the OPC server ...................................................................... 43
2.4.3 Specifying connection properties for the OPC server in project engineering ........................ 44
2.4.4 Using symbols for S7 connections ...................................................................................... 45
2.4.5 Configuring OPC properties for SNMP in project engineering .............................................. 45
2.4.5.1 Significance in SIMATIC NET ............................................................................................... 45
2.4.5.2 SNMP traps ........................................................................................................................ 46
3 DCOM security ..................................................................................................................................... 47
3.1 Enabling network discovery (as of Windows 7) ................................................................... 48
3.2 Enabling the DCOM Configuration for OPC Client/Server Operation ..................................... 49
3.3 Configuration of the "SIMATIC NET" User Group .................................................................. 50
3.4 Turning off a COM server ................................................................................................... 52
3.5 Functions of the "dcomcnfg" system program for the computer workstation ....................... 55
3.5.1 General settings for the workstation................................................................................... 56
Note
Be careful not to confuse this "index" with a hardware slot, for example on the PCI bus of the
PC. The slot on the PCI bus is not relevant for commissioning and is not used at any point.
Basic tools:
• "Station Configuration Editor"
Use this tool to plug modules and components into the virtual slots of the PC station and
assign addresses and parameters to them.
• STEP 7 Professional configuration tool (TIA Portal)
With STEP 7 Professional (TIA Portal), you can perform most PC configuration tasks,
among other things. A STEP 7 Professional license is not required for PC configuration.
You can find an introduction to PC configuration with STEP 7 Professional (TIA Portal) in
the section ""STEP 7 Professional (TIA Portal)" (Page 186)" or in the documentation of STEP
7 Professional (TIA Portal).
The primary use of your PC station is: Resulting area of Selectable mode:
application:
• For diagnostics and maintenance and for Programming device
(PG/PC) PG mode (default)
programming and project engineering
(STEP 7).
• Case b) Initial configuration with existing project engineering data (XDB file)
This procedure assumes that the PC stations and their components and applications are
initially configured in STEP 7. This produces a database (XDB file) that is then made
available to the commissioning engineer of the PC stations for the initial configuration.
The advantage of this is that the project engineering data and the PC configuration are
consistent and the total effort is minimal.
Result
Once the project engineering data has been downloaded to or imported into the PC station,
the applications can communicate over the established communication networks with the
stations reachable over the network.
Initial situation
• Case a) Initial configuration via remote configuration with STEP 7
In order to be able to perform the initial configuration at the PC station accessible online
in the next step, you must first configure the PC station with STEP 7.
• Case b) An XDB file is available for initial configuration
To be able to make the initial configuration in the next step, you must first create the
configuration data for the PC station with NCM PC / STEP 7 and then make this data
available in an XDB file.
• Case c) The initial configuration has already been made on the PC station
Configuration data is downloaded or imported as an XDB file to the PC station following
initial configuration.
Note
If STEP 7 Professional (TIA Portal) and the SIMATIC NET PC software are installed on the
same PC, you must load the configuration data locally. To do this, select "PC internal" as
access.
Summary
In the "Configuration" step described here, you were shown the following actions:
• Creating a STEP 7 project or using an existing STEP 7 project.
• Creating a PC station in the STEP 7 project
• Inserting and networking PC modules in the PC station
• Creating applications
• Configuring connections for the applications
• Storing the project engineering data in an XDB database
The XDB database is then available for offline mode and can be used to import the
engineering data on the PC station.
Result
When you start the PC station, the PC module of the PC station is initially in PG mode.
By adding the communications module in the "Station Configuration Editor", the module is
automatically switched to "configured mode" and the index (the "virtual slot number") of the
module is set.
Selecting the network adapter for the remote configuration ("SIMATIC Shell")
Requirement
The network adapter for remote configuration only needs to be selected if several network
adapters are installed in one PC. The selection may be required both in the destination
computers and in the configuration station.
If only one network adapter is available in the PC, it is automatically used as the PC module
for the remote configuration.
Selection of the network adapter
With the "SIMATIC Shell" program, you can make settings for remote configuration with STEP
7. The program is called via the Explorer extension "Simatic Shell" (in the Windows Explorer
under "This PC" > "Simatic Shell"). Open the "SIMATIC Shell" shortcut menu and click on
"Settings ...".
Proceed as follows to select a network adapter using the "SIMATIC Shell" program:
1. Select the "Remote Communication" check box. This enables remote configuration.
2. Enter the password for the STEP 7 communication.
3. Select the desired network adapter.
Note
The "SIMATIC Shell" program is automatically started on startup of the PC station if no
settings have been made yet.
Note
For security reasons, clear the "Remote Communication" check box if you do not need remote
configuration.
Note
Alternatively, the network adapter can be selected and "Remote Communication" can be
enabled/disabled using the "Communication Settings" tool.
Note
The "SIMATIC NET PC Software" must be installed on the configuration station to be able to
configure via STEP 7.
3. Follow the instructions in the online help of the dialog to create and complete the remote
configuration.
Result: The PC station with PC modules and applications are configured and ready to receive
configuration data.
3. To prevent project engineering data from being transferred online at a later point in time,
select the "Work offline..." option. With the default setting (option is disabled by default),
you ensure that configuration data can be transferred online.
Note
You can also follow this procedure in the example "OPC Configuration for Industrial
Ethernet" in this manual; refer to the section "OPC application for Industrial Ethernet
(Page 117)".
Note
You also have the option of importing the configuration data of the initial configuration into
STEP 7. This makes it extremely simple to create a configuration in STEP 7 that matches the
configuration on the real PC station.
Note
If there are several SOFTNET PROFIBUS modules, only one can be configured in project
engineering.
Result: The PC station with PC modules and applications are configured and ready to receive
configuration data (select online mode!).
Note
You will also find this procedure in our example "Configuration Example for PROFIBUS"; refer
to the section "OPC application for PROFIBUS DP (Page 123)".
Introduction
The OPC Scout V10 shows you the status of the communication connections. To do this, it
makes use of the properties of the process variables or uses information variables. You can
then recognize when a partner device is not accessible.
Note
The settings (OPC protocol selection and certificates) mentioned above are described in the
section ""Communication Settings" (Page 205)".
Note
The settings (OPC protocol selection and certificates) mentioned above are described in the
section ""Communication Settings" (Page 205)".
Transfer the created symbol file to your PC station. You can specify the required symbol file in
the "Communication Settings" configuration program.
To use symbols for SIMOTION Scout, the PC module and thus the subnet via which the
SIMOTION partner stations are connected must also be selected. You make this setting in an
extra dialog when selecting the symbol file in "Communication Settings".
You can check the selected module with the "Communication Settings" program using the
"Access points" function:
• Fixed access point SIMOTION CP_SM_1: e.g. "CP_SM_1:" > "CP5623.PROFIBUS.1"
For more information on SIMOTION, refer to the documentation of the SIMOTION Scout
engineering program.
Introduction
Modules operated with the "SOFTNET Industrial Ethernet" software product are integrated in
Windows just like a standard network adapter but with additional protocols. The station
parameters for such modules can only be set with the standard mechanisms of Windows.
Parameter
The parameters to be set with Windows mechanisms are as follows:
• IP address
• Subnet mask
• Gateway address
Even when changing the station parameters during the initial configuration, the Windows
configuration program must be used. During the initial configuration, you are prompted to
start this tool.
Note
Make sure that the network parameters of the PC station match the information entered in
the configuration in your project. If this is not the case, it is not possible to establish
connections.
When a configuration is transferred from the project engineering system to a PC station and
the transferred configuration contains different network parameters from those configured
locally on the PC station, a warning is displayed. In this case, you will need to adapt the
project engineering configuration in your project or set the local parameters according to the
project engineering configuration.
OPC server
With the SIMATIC NET OPC Server described here, SIMATIC NET offers you a convenient tool
with which your PC applications can write and read process data and receive notification of
process events.
By creating a project engineering database, you can specify the behavior of the OPC Server.
Load the configuration data into the PC station with STEP 7.
This section introduces the available options for configuring the OPC server with the STEP 7
configuration tool.
• Using default settings or project engineering parameters
The parameters that can be set with STEP 7 are fully supplied with default settings, which
ensures smooth communication in most cases.
This section is only relevant for you if you want to change settings.
Parameter / Possible settings / signifi- Can be set for a specific protocol ...
function cance DP FDL S7 ISO/TCP DP class 2 SNMP
Scan cycle time Here, you make the settings x x x x x x
to control updating by the
OPC Server.
The scan cycle time decides
how often the OPC server
updates the values the OPC
items.
Access protec- You can specify the access x x x x x x
tion rights to individual variables
or variable groups for each
specific protocol. You can, for
example, prevent variables
calculated internally by the
controller from being over-
written. As default, no access
protection is activated.
Connection Here, you can make the - - x - - -
parameters communication settings for
services that do not require
specific connections to be
configured in project engi-
neering.
Segmentation Special settings for providing - - x - -
the data buffers independent
of specific connections.
Use symbols The symbols of the STEP 7 - - x - - -
project are used for the OPC
server.
2.4.3 Specifying connection properties for the OPC server in project engineering
If you use OPC, communication connections are established and managed by the OPC Server.
As a result, you create the communication connections only for the "OPC Server" application.
If a connection is created for the OPC Server, the properties dialog for the connection
includes an additional tab, "OPC - Properties".
NOTICE
Configuration of the default parameter assignments
Only qualified personnel should change the default parameter assignments. Changes can
lead to unexpected situations and cause major system disruption. After changing
parameters, they must be downloaded or exported and the import of an XDB started.
Note
You need STEP 7 V5.5 or higher for the configuration. OPC SNMP cannot be configured with
STEP 7 Professional (TIA Portal). For more detailed information on the use of SNMP over the
OPC Server, refer to the documentation on OPC /1/ or the Quick Start in the section "SNMP
communication with OPC (Page 136)".
You will also find valuable information on the Internet at:
SNMP OPC server: (http://www.automation.siemens.com/mcms/industrial-
communication/en/ie/software/network-management/snmp-opc-server/Pages/snmp-opc-
server.aspx)
Note
Note also the detailed parameter description in the online help of the dialog in STEP 7.
Introduction
Traps are messages that can be sent to the OPC Server without it requesting them. There are
seven generic traps available on every SNMPcompliant device. There are also devicespecific
traps that are described in the MIB file.
Generic traps
Parameter Meaning
warmStart This is sent after a warm restart on the device.
coldStart This is sent after a cold restart on the device.
linkDown This is sent when a connection from the device was terminated.
linkUp This is sent when a connection from the device was established.
authenticationFailure This is sent when there was unauthorized access to the device.
egpNeighborLoss The EGP neighbor (EGP = Exterior Gateway Protocol) of the device
is not operational. The Exterior Gateway Protocol is used to ex-
change routing information between two neighboring gateway
hosts.
enterpriseSpecific This is sent when a devicespecific trap was sent.
In this section, you will also find information on, for example, configuring the OPC client PC
and configuring the PC with the OPC server for the situation where exactly one OPC client
connects to an OPC server that is running on a different PC.
If you want to use multiple OPC servers from one OPC client, refer to the DCOM
documentation for more information.
Note
Note that DCOM access is now potentially possible for other applications also. For security
reasons, only enable it if necessary.
6. Add the required DCOM users to the group, here, for example user "Alpha", member of the
"Administrators" group and user "Beta" member of the "Users" group.
The group can now be selected by the COM server for launch and access permissions for
DCOM configuration.
3. Select the "Everyone" user group and set the selection for "Local Launch", "Remote Launch",
"Local Activation" and "Remote Activation" to "Deny".
4. Click the "OK" button and answer the prompt for confirmation the with "Yes".
5. Then confirm the following properties dialog box with "OK". The launch and activation of the
COM server is now explicitly denied for every user.
Note
Explicit "Deny" settings are also not overwritten by the OPC security settings with the
"Communication Settings" program. These settings can only be reset using the "dcomcnfg"
system program. To do this, set the settings in the "Everyone" user group to "Allow" or
remove the "Everyone" user group. Then make the required OPC security settings with the
"Communication Settings" program.
NOTICE
Adapting security settings
It is the responsibility of the user to adapt the security settings to meet requirements.
Note
The "General", "Options" and "MSDTC" tabs are not required for commissioning the
DCOM protocol and not discussed further here.
Note
The settings made in the DCOM configuration depend on whether the computer with the
OPC Server is logged on in a domain or is operated within a workgroup.
If it operates within a domain, the server computer can check the configured rights of other
accounts over the network (authentication). This is only possible when the accounts of the
user are created with this domain.
If there is a domain controller, it is advisable to work in a domain.
Note
The settings listed in this description guarantee simple installation and startup of the DCOM
protocol. Some of the security settings of the operating system are reduced. To meet stricter
security requirements, you must increase the settings according to the DCOM guidelines.
The settings are different if you use domains and workgroups.
Note
If you change the security settings, the system must be restarted to activate the changes.
The settings are described in sections "Example - Windows domain operation (Page 82)",
"Example - Windows workgroup operation (Page 101)" and "Example - Client computer
operation only (Page 108)".
These permissions can be set individually for each object and the default properties are then
ignored.
Note
The Data Access OPC server for SIMATIC NET is listed as "OPC.SimaticNET".
Note
The following description also applies analogously to the other OPC servers from SIMATIC
NET listed below.
If you select the "Security" tab with this authentication level, you can adapt the permissions in
the "Properties of OPC.SimaticNET - Security" dialog.
See also
"Security" tab (Page 75)
To operate as pure OPC client computer, see "Example - Client computer operation only
(Page 108)", a remote PC with SIMATIC NET OPC server can also be selected. To do this, select
the "Run application on the following computer:" check box and use the "Browse..." button to
select the desired PC or enter the PC name directly.
Setting Meaning
"The interactive user" The account of the user currently logged on at the PC is used.
If, however, no user uses the computer, there is no interactive user
and the COM object cannot be created. If you operate without a
logged-on user, use the "This user" setting.
"The interactive user" is the default setting for the OPC server for
SIMATIC NET.
"The Launching User" The account of the user that launched the OPC client is used.
This user must then also have the required permissions; in other
words, must be entered in the "Security" tab. The user must also
have the default permissions entered in the user group on this PC,
in other words must belong to the user group.
Note:
This mode must not be used with the OPC server for SIMATIC NET,
since the OPC server would otherwise be started more than once
by different user accounts and this is not permitted.
"This User" The account of a specified user is used. This user must have the
required permissions; in other words, must be entered in the "Secu-
rity" tab. The user must also have the default permissions entered
in the user group on this PC, in other words must belong to the
user group.
This setting must be used to operate the OPC server for SIMATIC
NET if more than one user is logged on (multi-terminal operation)
or server operation if no interactive user is logged on.
Multiterminal server mode, service or server mode with the identity "This user" of the OPC server
In multiterminal-server mode or service or server mode in which the OPC server is started
with the identity of a certain user ("This user"), you assign access, launch and activation
permissions to this user.
2. Add the account of the user under which the OPC server will start.
Access must be permitted for the "SYSTEM" account to allow use of the SIMATIC NET system
services.
Note
The default is "Everyone".
2. Add the account of the user under which the OPC server will start. It is advisable to manage
the user in the SIMATIC NET user group and to add the group here.
Note
The default is "Everyone".
Note
Requirements for the examples
• The user must have extensive knowledge of computer administration.
• The domain controller must be set up.
• The terminal services must be working on the computers.
4. Adapt the security access and launch settings in the "Security" tab.
5. In the "Launch and Activation Permissions" group box, click the "Edit..." button.
Note
Do not add the "NETWORK" and local "Administrators" entries for the access and launch
permissions otherwise all members of the domain will have access rights.
Use the domain group SIMATIC NET (with users Alpha and Beta) for the launch and access
permissions. Further users such as "Gamma" are denied access even with domain
administrator permissions.
The following launch permissions are also required for the ANONYMOUS LOGON:
– "Local Launch"
– "Remote Launch"
– "Local Activation"
– "Remote Activation"
7. "Identity" tab
In this application example, the identity remains "The interactive user".
2. "Launch and Activation Permissions" and "Access Permissions" dialog boxes with the
"Security" tabs
Use the domain group SIMATIC NET (with users Alpha and Beta) for the launch, activation
and access permissions. Further users such as "Gamma" are denied access even with
domain administrator permissions.
Note
OPC security settings when changing domains
In the "Communication Settings" configuration program, you can enable the OPC security
settings for the Windows firewall and DCOM. Remember that the settings for the Windows
firewall and DCOM configuration depend on the Windows logon. If, for example, you later
join a Windows domain with the PC, it may be necessary to enable the OPC security
settings for the Windows firewall and DCOM again in "Communication Settings".
3.7.2 Example of a non logged-on user in the domain - server mode, service mode
In this situation, the computer has booted but no user is logged on.
The system displays the logon dialog.
The OPC server can:
• then be operated as a server to which one or more remote OPC clients with users with
differing permissions have access over DCOM ⇒ server mode.
• also be launched and executed by a local service that is started automatically even without
a logged-on user when the PC boots ⇒ service mode.
Set the DCOM configuration of the OPC server "OPC.SimaticNET" using the "dcomcnfg"
program.
1. Select the "This user" check box in the "Identity" tab of the "OPC.SimaticNET Properties"
dialog of the OPC server.
2. Click the "Browse..." button and select a user with adequate launch and access permissions
for the OPC server and enter the password and password confirmation.
This does not need to be one of the logged-on users. With the "This user", setting, the OPC
server is launched and executed only in this user context (even when several users are
logged on).
3. In the "Default Protocols" tab, you specify the network protocols that are available for DCOM.
The "Connection-oriented TCP/IP" protocol must be set at the top.
Setting Meaning
"Launch and activation permis- Allow launch and activation for administrators, everyone, network,
sions" system, ANONYMOUS LOGON and interactive (if not already set) -
local!
"Access permission" Allow access for administrators, everyone, network, system,
ANONYMOUS LOGON and interactive (if not already set) - local!
Setting Meaning
"Launch and activation permis- Allow launch and activation for administrators, everyone, net-
sions" work, system, ANONYMOUS LOGON and interactive (if not al-
ready set) - local!
"Access permission" Allow access for administrators, everyone, network, system,
ANONYMOUS LOGON and interactive (if not already set) - local!
With these extensive default permissions, every OPC client in the workgroup can now access
the OPC server over DCOM. This also applies to non-registered DCOM clients.
First test DCOM access with the registered client "OPC Scout V10" and then with your OPC
client.
You can now replace the general user "everyone" with the users or user groups you require.
Note
Recommendation: Replace "Everyone" with the "SIMATIC NET" group.
Overview
When operating with DCOM, the OPC server runs on a different PC from the OPC clients
(applications). This is why no process for the OPC server is visible in the Windows Task
Manager of the client computer.
To allow the OPC clients to access the OPC server, the following requirements must be met
for this mode:
• Registering the OPC server
The OPC server and its location must be registered on the client computer.
This registration is necessary so that the COM library knows the required object making
configuration possible.
Specify the user account that will be used to access the OPC server.
• Registering the OPC client
When necessary access permissions and security settings must be made for the OPC
clients.
NOTICE
Higher security requirements
As shown below in the example of the OPC Scout V10, the default setting assumes an
open system and assumes that the user will adapt the settings when higher security is
required.
Make the required settings analogous to the description of configuring the server
computer in the section "Functions of the "dcomcnfg" system program for DCOM
configuration of OPC servers (Page 66)".
Below, you will find instructions on registering, for example the OPC Scout V10 as a client.
• Providing "OPC proxy" libraries
The OPC Proxy libraries ("OPC Core Components") provided by the OPC Foundation are
required on the client computer. These libraries are used to convert the COM calls to a
data stream so that they can be transferred over the network.
If you display the properties of the OPC Scout V10 application in DCOM, "None" is displayed as
the authentication level.
The default setting therefore assumes an open system and assumes that the user will adapt
the settings when higher security is required.
Register other OPC clients as DCOM objects. The advantage of this is that you can configure
the security settings with "dcomcnfg" without needing to modify systemwide settings.
Note
Remember that the security settings made in the user program have priority over the settings
made in the DCOM dialog!
Note
If the "SIMATIC NET PC Software" installation program is started automatically, end it with
"Cancel", since the installation of the entire "SIMATIC NET PC Software" is not required for
the OPC client installation.
4. In the Explorer, open the drive and start the "Setup.exe" program in the "\sw\OPC_Scout"
folder.
Follow the instructions in the installation dialogs.
After successful installation of the software, if required set the DCOM configuration for the
OPC client computer as described in the manual.
4. When asked "What type of rule would you like to create", select the "Port" button.
5. Click the "Next" button.
6. In answer to the question "Does this rule apply to TCP or UDP?", click the "TCP" button.
7. In the "Specific local ports" text box, enter the port with number 135.
8. Click the "Next" button.
9. In answer to the question "What action should be taken when a connection meets the
specified conditions?", click the "Allow the connection" button.
10.Click the "Next" button.
11.In this dialog, select the buttons "Domain", "Private" and "Public".
12.Click the "Next" button.
13.Enter a name for your inbound rule in the input field, e.g. the name "DCOM".
14.Click the "Finish" button.
Making the settings to restrict the access permissions for COM security
Follow the steps below:
1. Go to the COM security settings as described in the section "Enabling the DCOM
Configuration for OPC Client/Server Operation (Page 49)".
2. Click on the "Add User" button.
3. Add the "ANONYMOUS LOGON" user.
4. Check the "Local Access" and "Remote Access" boxes.
Make the settings for launch and activation permission for OPC.SimaticNET
Note
As of Windows 7, the step "Launch and Activation Permission for OPC.SimaticNET" is no
longer necessary.
4.1.1 Overview
Requirements
If you want to try out the example yourself, you require the following:
• A PC with "SIMATIC NET PC Software" installed and a CP 1623 communication processor
plugged in
• An S7 device with CPU 1516-3 PN/DP and CP 1543-1
• Industrial Ethernet cabling between communication processor and S7 device
For the S7 device and the PC station, you need a STEP 7 project (license is required), which
was created on an engineering station. In the project, you specify the hardware configuration
and the programs and data blocks and define a symbol table.
PC station
Proceed as follows to configure the PC station in STEP 7:
1. In a new STEP 7 project, create a "SIMATIC PC station" from the hardware catalog via "PC
Systems" > "PC General".
2. Insert an OPC server in the hardware catalog via "PC systems" > "User applications".
3. Configure the generation of an XDB file for the PC station via "Properties" > "General" > "XDB
Configuration".
4. Insert a CP 1623 communication processor into the PC station from the hardware catalog via
"PC Systems" > "Communication Modules" > "PROFINET/Ethernet".
S7 station
Proceed as follows to configure the S7 station in STEP 7:
1. In the STEP 7 project, create an additional S7-1516-3 PN/DP from the hardware catalog via
"Controller" > "SIMATIC S7-1500" > "CPU" and ensure that the firmware versions of the
configured device and your S7-1500 match.
2. Insert a CP 1543-1 communication processor into the S7 station from the hardware catalog
via "Controller" > "SIMATIC S7-1500" > "Communication Modules" > "PROFINET/Ethernet".
3. Create a new variable table with one variable for the S7 CPU.
4. Also create a new data block.
5. Set up a suitable access protection for the S7 CPU and a suitable display protection via
"Properties" > "General" > "Protection & Security" or "Display".
Networking
Proceed as follows to network the stations in STEP 7:
1. Network the two stations by dragging a line from the Ethernet interface of the CP 1623 to
the Ethernet interface of the CP 1543-1 with the mouse.
2. In the network view, switch to connection configuration and select "S7 connection" as the
connection type. Create an S7 connection between the two stations by dragging a line from
the OPC server to the S7 CPU with the mouse.
3. The two stations are thus networked and prepared for communication via a configured S7
connection, which can be operated via the OPC server.
The picture shows the created and networked configuration:
Symbols
Proceed as follows to configure access to symbolic variables in STEP 7:
1. Finally, configure access to symbolic variables for the OPC server. For this example, select
the symbols pre-configured for the S7 connection in the OPC server properties, via
"Properties" > "General" > "S7" > "OPC Symbols".
2. Select the "Configured" option. Clicking on the "Configure …" button opens a configuration
window, which in the symbol selection shows the variable and the data block you have
previously configured with the respective symbolic name and makes them configurable for
symbolic access.
This provides you a fully functional system that you can compile and load into the
appropriately equipped stations (alternatively load the PC station by importing the generated
XDB file).
When the stations are loaded, the namespace of the OPC server contains the configured S7
connection with access to the data of the S7-1500 and all configured symbolic names in the
"SYM:" namespace.
4.2.1 Overview
S7-REDCONNECT enables a PC station to connect to an S7-400H station, i.e. a high-availability
S7 automation system. This example shows the creation of a corresponding STEP 7
configuration. You will need the following components and software:
• A PC with "SIMATIC NET PC Software" installed and two CP 1623 communication
processors plugged in
• An S7-400H automation system with redundant CP 443-1 communication processor and
redundant CPU 417-5H
• STEP 7 version 5.5 or higher, usually installed on another PC. You need a license for STEP
7. Note that "STEP 7 Professional (TIA Portal)" cannot be used for configuring S7-
REDCONNECT.
You can find additional information on high-availability S7 connections in the document
"Industrial Communication with PG/PC - Basics" /1/, which is supplied with the "SIMATIC NET
PC Software".
PC station
Proceed as follows to configure the PC station in STEP 7:
1. In a new STEP 7 project, create a "SIMATIC PC station" from the hardware catalog via "PC
Systems" > "PC General".
2. Insert an OPC server in the hardware catalog via "PC systems" > "User applications".
3. Configure the generation of an XDB file for the PC station via "Properties" > "General" > "XDB
Configuration".
4. Insert two CP 1623 communication processors into the PC station from the hardware
catalog via "PC Systems" > "Communication Modules" > "PROFINET/Ethernet".
5. Network each of these two communication processors to a newly created subnet.
S7 station
Proceed as follows to configure the S7 station in STEP 7:
1. Create a "SIMATIC H-Station" with redundant rack in the STEP 7 project, in the hardware
catalog via "SIMATIC 400".
2. Insert a redundant CPU 417-5H PN/DP communication processor and a redundant CP 443-1
communication processor into each of the redundant S7 stations from the hardware catalog
via "SIMATIC 400".
The figure shows the device configuration created:
Networking
Proceed as follows to network the stations in STEP 7:
1. Network the two CPs of the S7 station so that you get a network as shown in the following
figure and make sure that the stations are wired accordingly:
2. Insert a new connection with the type "S7 connection fault tolerant" into the connection
table of the OPC server.
3. The two stations are thus networked and prepared for communication via a configured
high-availability S7 connection, which can be operated via the OPC server in the same way
as a standard S7 connection.
This provides you a fully functional system that you can compile and load into the
appropriately equipped stations (alternatively load the PC station by importing the generated
XDB file).
When the stations are loaded, the namespace of the OPC server contains the configured S7
connection with access to the data of the S7 station.
4.3.1 Overview
Requirements
If you want to try out the example yourself, you require the following:
• A PC
• A CP 5623 communication processor
• "SIMATIC NET PC Software"
• An ET 200S DP slave.
• PROFIBUS cabling between communication processor and ET 200S
PC station
Proceed as follows to configure the PC station in STEP 7:
1. In a new STEP 7 project, create a PC station from the hardware catalog via "PC Systems" >
"PC General" and insert an OPC server from the hardware catalog via "PC Systems" > "User
Applications".
2. Configure the creation of an XDB file for the PC station, "Properties" > "XDB Configuration".
3. Insert a CP 5623 communication processor into the PC station from the hardware catalog via
"PC Systems" > "Communication Modules" > "PROFIBUS".
ET200S
Proceed as follows to configure the ET200S in STEP 7:
1. In the STEP 7 project, additionally create a DP slave ET 200S PROFIBUS from the hardware
catalog via "Distributed I/O" >"ET 200S" > "Interface modules" > "PROFIBUS".
2. Switch to the device view by double-clicking on the module. The hardware catalog now
offers context-sensitive modules that you can insert into the DP slave.
3. Insert one of the power supplies in slot 1 from the hardware catalog via "PM".
4. Also insert an I/O module, for example.
5. Finally, switch back to the network view.
Networking
Proceed as follows to network the modules in STEP 7:
Connect the DP slave to the CP 5623 by drawing a line between the PROFIBUS interfaces of
these modules with the mouse. The result is as follows:
• The CP 5623 is now in DP master mode, a corresponding DP master system has been
created automatically.
• The relevant devices are networked via PROFIBUS.
• The DP slave is connected to the DP master system of the CP 5623.
The figure shows the configuration created:
This gives you a fully functional system that you can compile and load into the appropriately
equipped PC station.
When the PC station is loaded, the namespace of the OPC server contains the corresponding
DP items with access to the CP 5623 as DP master and the I/O modules of the DP slave.
4.4.1 Overview
There is communication between two devices or modules. The communication with an S7-
400 station via the S7 protocol with unspecified S7 connection is described in detail below.
Requirements
To understand this example, you need the following:
• A PC with "SIMATIC NET PC Software" installed and a CP 1623 communication module
plugged in.
• A SIMATIC S7-400 with a CPU-400 in slot 3, the CPU has the IP address 140.101.10.3,
netmask 255.255.0.0.
PC station
Proceed as follows to configure the PC station in STEP 7:
1. In a new STEP 7 project, create a "PC station" from the hardware catalog via "PC Systems" >
"PC General".
2. Insert an OPC server in the hardware catalog via "PC systems" > "User applications".
3. Insert a CP 1623 communication processor into the PC station from the hardware catalog via
"PC Systems" > "Communication Modules" > "PROFINET/Ethernet".
4. Configure the generation of an XDB file for the PC station via "Properties" > "General" > "XDB
Configuration".
5. Network the CP 1623 with a newly created subnet.
S7 connection
Proceed as follows to configure an unspecified S7 connection for the PC station:
1. In the network view, switch to connection configuration and select "S7 connection" as the
connection type.
2. Select the OPC server and create an S7 connection (shortcut menu of the OPC server > "Add
new connection"). The newly created S7 connection appears in the connection list of the
network view.
3. Select this connection and click on "Properties".
4. Enter the IP address of the partner station in the general properties. Leave the "TCP/IP"
protocol activated.
5. Go to the page with the address details and enter the rack and slot of the S7 CPU, rack: 0,
slot in this case: 3.
Overview
Below, you will find three examples of configurations in which an unconfigured S7
connection is established:
• Industrial Ethernet via TCP/IP (Page 130)
Unconfigured S7 connection with a CP 1623 to a SIMATIC S7-400 with a CPU 414-3 DP.
• Industrial Ethernet via ISO (Page 134)
Unconfigured S7 connection with a general communications module for Industrial
Ethernet to a SIMATIC S7-400 with a CPU 414-3 DP.
• PROFIBUS (Page 135)
Unconfigured S7 connection with CP 5624 to a SIMATIC S7-400 with CP 414-3 DP.
Requirements
To understand this example, you need the following:
• A PC with "SIMATIC NET PC Software" installed and a CP 1623 communication module
plugged in.
• A SIMATIC S7-400
Connecting to a server
Drag the COM server "OPC.SimaticNET" ("Server Explorer" > "COM Server" > "OPC.simaticNET")
onto the worksheet, specifically there into the directory "Project …" > "Server" > "COM Server".
The OPC Scout V10 connects automatically to the OPC DA server.
Description
This example shows you how to connect a SIMATIC AS S7-400 with a CPU 414-3 DP with CP
443-1/CP 443-1 Advanced using an unconfigured S7 connection via Industrial Ethernet (via
ISO).
Requirement
If you want to try out the example yourself, you require the following:
• A PC with "SIMATIC NET PC Software" installed and an Ethernet communication module
plugged in.
• A SIMATIC automation system S7 (e.g. S7 1200, S7 1500, S7 300, S7 400)
• Industrial Ethernet cabling between the communication module and the SIMATIC AS.
• SIMATIC AS 400-S7-OPC used in this example has the station address "00.1B.1B.47.EF.5A",
a remote TSAP of "02.03" and the data element "MB1".
Procedure
Proceed in the same way as described in Example 1, with the following changes:
• Assign the "CP_H1_1:" access point to an ISO interface configuration of the
communication module used.
• IP address settings are not required
• The OPC item ID to be used contains the MAC address of one of the S7-400 CPs (in this
example "00.1B.1B.47.EF.5A"), the data element is MB1:
S7:[ConnNew_1|VFD1|CP_H1_1:|02.00,00.1B.1B.47.EF.5A,02.03,1]MB1
4.5.3 PROFIBUS
Description
This example shows you how to couple an AS S7-400 with a CPU 414-3 DP via CP 443-5 using
an unconfigured S7 connection via PROFIBUS.
Requirement
If you want to try out the example yourself, you require the following:
• A PC with "SIMATIC NET PC Software" installed and a CP 5624 communication module
plugged in.
• A SIMATIC AS 400-S7-OPC is coupled with a CPU 414-3 DP via a CP 443-5 and CP 443-5
Advanced.
• PROFIBUS cabling between the PC module and S7 device.
• The SIMATIC AS 400-S7-OPC used in this example has station address "4", a remote TSAP
of "02.03" and the data element "MB1".
Procedure
Proceed in the same way as described in Example 1, with the following changes:
• Assign the access point "CP_L1_1:" to a PROFIBUS interface configuration of the
communication module used.
• The OPC item ID to be used contains the PROFIBUS address of one of the S7-400-CPs (in
this example 4), the data element is MB1:
S7:[ConnNew_1|VFD1|CP_L2_1:02.00,4,02.03,1]MB1
Introduction
This section describes how you couple network components and nodes with an SNMP agent
with a PC station over an SNMP OPC server. You will learn which tools to use to configure a
PC station to implement the interfacing of a device with SNMP capability and how make the
SNMP variables and SNMP traps available on the OPC interface.
You will find information about the SNMP OPC server on the Internet at:
Link to the SNMP OPC server: (http://www.automation.siemens.com/mcms/industrial-
communication/en/ie/software/network-management/snmp-opc-server/Pages/snmp-opc-
server.aspx)
Requirements
If you want to try out the example yourself, you need the following:
• A PC with "SIMATIC NET PC Software" installed
• An SNMP-compliant device (for example SIMATIC NET OSM/ESM)
• A network connection between the OPC SNMP server and the SNMP-compliant device
SNMP communication with OPC is configured via STEP 7 as of version 5.5.
Writing values
You set the trap recipient of an OSM/ESM by assigning suitable values to two OPC items. The
procedure described here is also an example of how to write values for OPC items using the
OPC Scout V10.
6. Enter "2" to activate the trap recipient and click the "OK" button.
Note
You can drag items from the information area to the view area.
Device profile
A device profile contains the SNMP objects (OPC items) required for the SNMP interface of the
OPC server. It maps SNMP variables and SNMP traps on the OPC interface. Device profiles are
stored in profile files.
3. Double-click on the "OPC Server" field in the section "(0) PC" to configure the OPC server.
4. Select the "SNMP" tab and click on the "Edit Plant Configuration..." button.
Reaction: A dialog box appears in which all the SNMPcompliant devices registered with
the OPC server are listed.
5. Select the device for which you want to create a profile and click the "Edit ..." button to
display the dialog box with the node data of the device.
Under the "Edit" button, you can modify node data.
6. Click the "Create Profile ..." button to open the dialog box of the MIB compiler.
8. Select the MIB objects for the profile in the structure tree on the left and drag them to the
profile area of the dialog box. You can also select a node and drag it to the righthand area.
In this case, all the SNMP variables belonging to the node are adopted as OPC variables.
9. Structuring of the variables in the profile area is possible in keeping with the OPC
specification by creating groups. To do this, click the "Create Group" button.
10.Check whether or not the adopted SNMP variables still include unspecified instances of
variables. Such elements are indicated by a "!".
Double-click on such elements to open the "Enter Instances" dialog box.
(For example, for an 8port switch, the object "ifOperStatus" must be assigned the instances
1-8 so that the OPC items "ifOperStatus.1" to "ifOperStatus.8" can be formed).
11.Save the profile by clicking on the "Save" button. You can select the newly created profile in
the "Device profile" list box of the "Add nodes" dialog box.
General
Note
This section describes the communication processors
• CP 5603
• CP 5613 A2/CP 5613 A3
• CP 5623
are called simply CP 56x3. The following instructions apply the same to all three
communications processors.
The example shows the configuration of CP 56x3 and CP 5622 as DP slaves, with a CP 5624
as DP master with STEP 7 Professional (TIA Portal) as of V14 SP1. You do not need a license
for the example, since only PC stations are configured.
Note
• A DP configuration created for a CP 56x3 is not compatible with a CP 5614 A2/A3 or CP
5624 slave and vice versa. For this reason, the configuration must be adapted and
reloaded if a CP 5614 is to be physically replaced by a CP 56x3 or vice versa.
• If you want to connect the CP 56x3 as a DP slave to a DP master of a third-party
manufacturer, you must use the supplied GSD files, "SLV80b4.GSD" or "SLV180b4.GSD".
• If you want to use the CP 5614 or CP 5624 as DP slave, import the GSD file,
"siem80b4.gsd" or "siv180b4.gsd" (DPV1). You can find these components in the hardware
catalog under "Other field devices" > "PROFIBUS DP" > "General" > "SIEMENS AG".
Configuration
1. Create a STEP 7 project with two PC stations from the hardware catalog under "PC Systems"
> "PC General" and insert an OPC server in each of these PC stations (in the hardware catalog
under ""PC Systems" > "User Applications").
2. Configure the generation of XDB files for both PC stations (tag "Properties" > "General" >
"SIMATIC PC Station" > "XDB Configuration").
3. Insert a CP 5624 in the first PC station (hardware catalog under "PC Systems" >
"Communication Modules" > "PROFIBUS") and configure it as a DP master (tab "Properties" >
"General" > "Operating mode").
4. Plug a CP 5623 and a CP 5622 into the second PC station from the hardware catalog and
configure them as DP slaves with assignment to the previously created DP master. In order
to operate the CP 5623 slave via SIMATIC NET OPC, it must be set to "DPV0 compatible" DP
mode, which is also configurable under "Operating mode".
Result: The communication processors were networked automatically via PROFIBUS and the
DP master system was created. OPC access with the OPC server is also possible.
The DP slaves must now be configured with the desired transfer ranges (tab "Properties" >
"Operating mode" > "I-slave communication"). You can configure the transfer areas as soon as
you have selected the type "MS" under "Transfer areas" on the configuration page. Other
configurations such as "Bidirectional address mapping" are possible if you select one of the
created transfer areas in the navigation.
This gives you a fully functional DP system that you can compile and load into the
correspondingly equipped PC stations, alternatively by importing the XDB files that have now
been created.
When the PC stations are loaded, the namespace of the OPC server contains the
corresponding additional elements and the OPC server can be operated as a DP master
application or DP slave application. With OPC Scout V10, you can select the corresponding
OPC items from the namespace and make first attempts with your DP configuration. Some
OPC item definitions are available by default.
Note
As of STEP 7 V5.3 SP3, the CP 1616 is part of the hardware library.
If you want to operate the CP 1616 with an earlier version of STEP 7, you can install an HSP
update.
You will find information on this in the online help of STEP 7 under the keyword "Hardware
update".
Note
No simultaneous operation
Parallel operation of a PCI board CP 1616 or a PCI 104 board CP 1604 with a communication
processor CP 1616 onboard the Microbox 427 B / 427 C is not possible.
Introduction
The CP 1616 communications processor is a PCI module for connecting PCs or SIMATIC
PGs/PCs to PROFINET IO.
Its essential characteristics are:
• Optimized for PROFINET IO
• With Ethernet realtime ASIC ERTEC 400
• 4 x RJ45 ports
• Integrated 4port realtime switch
(If used with an external power supply, the integrated realtime switch can also operate
when the PC is turned off.)
• Relieves the PC due to event mechanisms
(automatic detection of data changes)
• Automatic hardware detection is supported.
• Extensive diagnostics options
The chapter describes the configuration of the CP 1616 for the following four use cases:
• IO controller
• IO device
• Use as IO controller and IO device at the same time
• IO router
CP 1616 as IO controller
A PC communicates over Industrial Ethernet with PROFINET IO devices.
In the following example, the user program runs on the PC. Data traffic is handled over the CP
1616 with several SIMATIC S7 PROFINET IO devices (for example the ET 200S) over Industrial
Ethernet.
CP 1616 as IO device
In this example, the IO Base device user program runs on a PC with a CP 1616 installed in it.
The data exchange with the controller is handled over the CP 1616 and Industrial Ethernet.
Note
If the CP 1616 was configured previously as a controller, you must first run a complete
memory reset before the device name can be changed.
Following every complete memory reset, the CP must be restarted (from STEP 7) otherwise
device mode is not possible!
Note
When loading the firmware or commissioning the module, please remember that the CP
1616 has two MAC addresses (always consecutive).
The first address printed on the module is used for layer 2 communication, the second for the
PROFINET protocol (the first address plus one).
Example:
The address "08.00.06.93.DA.76" printed on the communications processor is the address for
layer 2 communication. This means that "08.00.06.93.DA.77" is the MAC address for
Ethernet/PROFINET communication.
Note
Remember the version!
In the procedure described below, for example, the CP 1616 Version 1.0 (V1.0) is used. The
configuration procedure is illustrated here using STEP 7 (not TIA Portal) as an example.
9. Select the CP 1616 and, if necessary, select the "Insert" > "PROFINET IO System" menu
command.
Reaction: Following your confirmation, the PROFINET IO system is inserted automatically.
10.Now configure the IO devices in the PROFINET IO system to meet your requirements.
Note
Remember the version!
In the procedure described below, for example, the CP 1616 Version 1.0 ("V1.0") is used.
Note
If the CP 1616 was configured previously as an IO controller, you must first run a complete
memory reset before the device name can be changed.
Following every complete memory reset, the CP must be restarted (from STEP 7) otherwise IO
device mode is not possible!
The CP 1616 in the PC station is an IO controller; the two ET 200S are IO devices. The same CP
1616 is in the PC station "SOFTNET" IO device of a CP 1612 IO controller.
Note
Remember the version!
In the procedure described below, for example, the CP 1616 Version 1.0 ("V1.0") is used.
6. In the "PROFINET" tab, you can set the mode of the CP 1612.
Select the "PROFINET IO Controller" mode. The inserted OPC server is automatically
assigned to the CP 1612 as a user application.
Then confirm your entries with "OK". This inserts a PROFINET IO system.
7. With "PROFINET IO" > "I/O" > "SIMATIC PC CP" in the hardware catalog, select the CP 1616
(V1.0) and position it in the network (PROFINET IO system).
Result: This configures the CP 1616 as an IO device in the network.
Note
Readme file
You will find information on the combinations of controller and device one module in the
readme file of the DK-16xx product.
8. Select the CP 1616 and then select "Edit" > "Object Properties".
9. Enter the device name in the "Device name" input box.
Requirements
The following description assumes that you are familiar with the basic functions of the IO
router as described in the operating instructions "CP 1616/CP 1604".
Note
Whenever possible, you should configure bit-oriented writing sparingly. It makes the
configuration complicated and increases the likelihood of application errors.
The data path from the IO device "DeviceX1" through the IO router to the "SIMATIC 400"
automation system is indicated at the bottom of the schematic by a red arrow (the red arrow
simply illustrates the text in this document and is not visible in the original STEP 7 view).
3. Select the 1 byte DI transfer module and place it on the first slot of the IO device "(1)
Router".
Catalog "PROFINET IO" > "I/O" > "SIMATIC PC-CP" > "CP 1616" > "Migration" > "V2.1" >
"Transfer module" > "DI" > "1 Byte".
Reaction: The transfer module is given the "I-address" (input address) "0".
Note
The IO modules in the "Migration" folder are intended for use with PROFINET Version V1.0
IO controllers. You will find the possible combinations in the readme file.
4. Interconnect the transfer module with the real IO module in the IO system for the robot
level:
Open the "Properties" dialog of the 1-byte module, for example by double clicking on the
row of slot 1.
Reaction: The "Properties - 1 byte - (R-/S1)" dialog appears.
5. Open folder "0.0-0.7" of the transfer module in the "PROFINET IO Transfer Module" tab. The
folder name corresponds to the I/O address being used.
6. Open the drop-down list box in the "Device name" column in byte 0 and select the
"DeviceX2" IO device.
7. Open the "Module (slot)" drop-down list box in byte 0 and select the "4DI DC24V HF" module
in slot 2.
You can see that bits 0 to 3 of the transfer module were assigned to the four bits of this
module.
8. In the "Transfer update time [ms]" drop-down list box in the lower part of the dialog, set the
interval at which the data of this module is transferred to the IO controller of the
management level. The default is 72 ms which means that a change at an input of the "4DI
DC24V HF" module is detected in the IO controller of the management level at the latest
after 72 ms.
Select a value less than 72 ms if you want the IO system for the control level to access the
IO system for the robot level faster.
Note
Note that the time must not be shorter than the following times:
• Update times of the PROFINET IO systems in the IO system for the control level and IO
system for the robot level.
• A CP 1616-specific transfer time of 8 ms.
When you have completed the configuration, the project must be compiled and downloaded
(to the CP 1616 with "Download to Module - Target System").
Note
Remember that the configuration must also be downloaded to the automation system
"SIMATIC 400" (IO controller of the IO system for the control level).
The input data of the "4DI DC24V HF" module in the "DeviceX2" IO device of the IO system for
the robot level can now be read by the IO controller of the management level at address 0.
Note
Whenever possible, you should configure bit-oriented writing sparingly. It makes the
configuration complicated and application errors are more likely to occur.
3. Select the 1 byte DI transfer module and place it on the first slot of the IO device "(1)
Router".
Catalog "PROFINET IO" > "I/O" > "SIMATIC PC-CP" > "CP 1616" > "Migration" > "V2.1" >
"Transfer module" > "DI" > "1 Byte".
Reaction: The transfer module is given the "O address" (output address) 100.
Note
The IO modules in the "Migration" folder are intended for use with PROFINET Version V1.0
IO controllers. You will find the possible combinations in the readme file for PROFINET IO.
4. Interconnect the transfer module with the real IO module in the IO system for the robot
level:
Open the "Properties" dialog of the 1-byte module, for example by double clicking on the
row of slot 1.
Reaction: The "Properties - 1 byte - (R-/S1)" dialog appears.
5. Open the "0.0-0.7" folder of the transfer module in the "PROFINET IO Transfer Module" tab
and select "DeviceX1" in the drop-down list box of the "Device name" column in byte 0.
You will see that all four bits of the "4DO DC24V/0.5A ST (3)" module have automatically
been assigned to the transfer module.
6. To control only the first bit of the module from the IO controller of the management level,
enter the address 100.0 in the "End" box of the "Byte 0" row.
You will see that only bit 0 of the "4DO DC24V/0.5A ST (3)" module has been assigned to
the transfer module. As a result, bits 1 to 3 of the module are controlled by the IO
controller of the process level.
7. In the "Transfer update time [ms]" drop-down list box below the large table, set the interval
at which the data of this module is transferred to the IO controller of the management level.
The default is 72 ms which means that a change at an input of the "4DI DC24V HF" module
is detected in the IO controller of the management level at the latest after 72 ms.
Select a value less than 72 ms if you want the IO system for the control level to access the
IO system for the robot level faster.
Note
Note that the time must not be shorter than the sum of the following times:
• Update time of the PROFINET IO systems in the IO system for the management level;
• Update time of the PROFINET IO system for the robot level;
• A CP 1616-specific transfer time of 8 ms.
When you have completed the configuration, the project must be compiled and downloaded
(to the CP with "PLC - Download to Module").
Note
Remember that the configuration must also be downloaded to the automation system
"SIMATIC 400" (IO controller of the IO system for the control level).
The first bit of the "4DO DC24V/0.5A ST (3)" module in the "DeviceX2" IO device of the IO
system for the robot level can now be written by the IO controller of the management level at
address 100.
Note
• Although the IO controller of the process level writes in bytes, its bit 0 is irrelevant for the
output status of the "4DO DC24V/0.5A ST (3)" module because it is assigned to the IO
controller of the management level.
• Although the IO controller of the management level writes byte-oriented, bits 1 to 7 are
irrelevant for the output status of the "4DO DC24V/0.5A ST (3)" module. They can be
written by the IO controller of the process level.
Purpose
If you are already using a router, you can copy this along with its entire functionality.
Requirement
The following description is based on the example described in the previous section "Using
the CP 1616 as a PROFINET IO router (Page 158)".
Procedure
Copying a PROFINET IO router involves 3 steps:
1. Copying the PC station (in this example: "Router").
2. Copying the IO device (in this example: "Router").
3. Coupling the new PC station with the new IO device.
Functions
• Prioritized startup is used in fast processes when IO devices change quickly, for example
changing the tools of a robot. A CP 1616 communications processor supports prioritized
startup of SIMATIC S7 IO devices in RT or IRT communication. Depending on the device,
this allows a time < 0.5 s to be achieved following completion of a restart to the beginning
of user data exchange.
Note
To achieve short communiction times, the Ethernet connections must have fixed settings
so that no time is lost in "negotiation" when establishing the connection.
To achieve a stable Ethernet connection, both ports of an Ethernet connection must be set
to "100 Mbps full duplex" and autonegotiation disabled (click on the port -> "Object
Properties" -> "Options").
Configuration
Prioritized startup planning in STEP 7 is only required and possible for SIMATIC S7-IO devices.
Follow the steps below:
1. Open the hardware configuration (HW Config) of the PROFINET IO system.
2. Select the relevant IO device in the PROFINET IO system.
3. Open the object properties of slot "X1".
4. In the "General" tab, select the "Prioritized Startup" option.
For more detailed information on configuration, and, in particular, on the cabling rules, refer
to the STEP 7 online help for the "General" tab described above.
After reconfiguring an IO device for prioritized startup, the first startup takes place in the
normal time without being prioritized. All subsequent startups will then be completed in the
reduced time of < 0.5 s.
Note
Including an IO device with prioritized startup in a ring with media redundancy serves no
practical purpose since the ring is interrupted at each IO device change.
Functions
You can use the CP 1616 communications processor in a media redundancy ring topology. As
PROFINET IO controller, the CP 1616 itself can be the redundancy manager.
If you use IRT communication, media redundancy is not supported.
Configuration
Configuration is performed in STEP 7 in the "Media redundancy" tab of the CP 1616
("HW Config" > Select "CP 1616" IO Controller > Open "Index X1" in the "Object properties"
shortcut menu > "Media redundancy" tab). Then configure the required properties:
• Domain - Name of the IRT domain
• Role
– Not node in the ring - media redundancy is disabled.
– Manager - the CP 1616 as a PROFINET IO controller is redundancy manager.
– Client - the CP 1616 as a PROFINET IO device is redundancy client.
For more detailed information on configuration, refer to the online help of the "Media
Redundancy" tab.
If a CP 1616 is used as an IO device in the media redundant ring topology, the media
redundancy is handled in the same way.
Note
The driver is stopped again with the "make unload" command.
Setting
const PNIO_UINT32 g_deviceInputCount=3; ▶ Number of input modules
volatile PNIO_IOXS g_deviceInputState[g_deviceInputCount]= ▶ One PNIO_S_BAD per
{PNIO_S_BAD,PNIO_S_BAD,PNIO_S_BAD}; input module
PNIO_UINT32 g_deviceInputLength[g_deviceInputCount] ={ 1, 1, 1}; ▶ One "1" per input module
PNIO_ADDR g_deviceInputAddress[g_deviceInputCount]=
{
{ PNIO_ADDR_LOG, PNIO_IO_IN, 0}, ▶ Address 1st input module
{ PNIO_ADDR_LOG, PNIO_IO_IN, 1}, ▶ Address 2nd input module
{ PNIO_ADDR_LOG, PNIO_IO_IN, 2} ▶ Address 3rd input module
};
Note
You will find more information on the meaning of the display boxes and the buttons in the
integrated help system.
Note
The components in the configuration list you can edit here must be entered in exactly the
same order as in the component image you created in STEP 7 with HW Config. If the
configuration differs from the list, the configuration data that you download from STEP 7 to
the PC station will not be adopted correctly.
The status display constantly informs you whether the component you have created matches
the current hardware configuration and whether it matches any project engineering data that
has already been downloaded.
Note
Remember that you have the option of a partial download if you have set the properties of
the "Station Configuration Editor" accordingly.
For more detailed information, refer to the next section "Setting the "Station Configuration
Editor": "Properties" dialog (Page 185)".
Disable/enable station
As an administrator, you have the option of protecting the station configuration against
changes ("Disable Station" button). In the disabled state, the configuration cannot be
changed; XDB import, remote configuration and loading of the station as well as changes to
the station in the "Station Configuration Editor" itself are disabled. The disable can be
released again by pressing the "Enable Station" button. The current status is displayed in the
"Operating mode" field:
• RUN: The PC station is locked against changes.
• RUN_P: The PC station is unlocked for changes.
How it works
The "Station Configuration Editor" manages a diagnostic buffer in which the PC station
components (hardware and software) enter event information.
You can use this list to analyze configuration or communication problems.
Note
You will find more information on the meaning of the display boxes and the buttons in the
integrated help system.
Note
The diagnostic buffer entries that you can read from the "Diagnostics" tab in the "Station
Configuration Editor" can also be read remotely via STEP 7 Diagnostics.
Note
You need STEP 7 V5.5 or higher for specific use cases (configuring high-availability S7
connections, plant configuration for OPC SNMP).
Note
If you want to use symbols with optimized data blocks (S7-1200 and S7-1500), you need to
use STEP 7 Professional as of V12.01. For the PC station, you need to configure the OPC
server as of V12.
Functions
To create the configuration and project engineering data of a PC station, use the following
functions:
• Create and configure components of the PC station.
• Configure the communication properties of the SIMATIC NET OPC server.
• Configure connections.
• Adopt the symbols from the SIMATIC S7 configuration.
• Configure DP operation.
• Set network parameters for PROFIBUS and Ethernet operation.
• Configure the PC station remotely.
• Download configuration data to the PC stations.
• Store configuration and project engineering data in an XDB file.
• Monitor the communication to connected S7 stations with diagnostic functions.
Initial configuration
You can generate the initial configuration of your PC station in STEP 7 Professional (TIA
Portal):
• Configuration with STEP 7 Professional (TIA Portal)
• Transfer of configuration and project data via the XDB file
See also
Commissioning for configured mode - Overview (Page 20)
Aims
You want to create configuration and project engineering data for communication services
for individual PC stations. This database will then be downloaded to the PC station. After this,
the PC applications can use the communications services.
You can use this in the following ways:
• On a local station, in other words, when your engineering station is the PC station at the
same time, the parameters specified in the initial configuration with the "Station
Configuration Editor" tool can be transferred later to the local project engineering system.
• For transferring the data to an engineering station
To allow the information from the project engineering to be transferred from an
engineering system to the PC station, the local configuration must match the
configuration data entered in the project engineering. To make sure of this, you can
create project engineering data locally on the PC station and then download it to the
target PC station or import it using an XDB file.
Within a project, objects are arranged in the "Network view". For each PC station, a separate
object of the type "PC station" is created. The configuration and parameter assignment data
of the hardware and software is located within these objects. These objects are then used to
assign the communications services.
Note
The name of the PC station you select here identifies the PC configuration.
• If you configure on the local station with STEP 7 Professional (TIA Portal), select the name
identical to the name in the local configuration.
• If you configure a remote PC station, the name you select must not be identical to the
local PC configuration! When you download, you would otherwise overwrite the local
configuration.
Tip: You can also adapt names, when necessary, in the Station Manager using the "Station
Configuration Editor".
This procedure corresponds to the one already described for the "Station Configuration
Editor" tool.
Note
Be careful not to confuse this "index" with a hardware slot, for example on the PCI bus of the
PC station. The slot on the PCI bus is not relevant for commissioning and is not used at any
point.
Note
Please note the following if you are transferring data by downloading:
Make sure you arrange the components exactly the same as in the configuration list of the
"Station Configuration Editor" (refer to the section "Managing components: "Components" tab
(Page 180)"). If the configuration differs, the configuration data that you download from
STEP 7 Professional (TIA Portal) to the PC station will not be adopted correctly.
Note
You will find information on configuring the DP slave in the section "Configuring a PC
station as a DP slave (Page 194)".
Meaning
During operation, configured connections are established either implicitly or on request,
depending on the parameter assignment. They are then available to the OPC server or the PC
application for communication.
Procedure
Regardless of the application type, the general rules for connection configuration apply:
• Communication connections are always assigned to an application.
• In the PC station, the CP that supports the type of connection is used for the data transfer.
• If there is more than one CP with this capability, you can use Routing to select the
transmission path.
Examples/model
Note
Remember that a SOFTNET DP slave operated with OPC must have the PNO identification
number 0x9001.
5.2.7 Downloading the project engineering data to the PC station (after the initial
configuration)
To allow applications to exchange information over configured communication connections,
the project engineering data created with STEP 7 Professional (TIA Portal) must be loaded on
the PC station.
If the initial configuration was performed with XDB import of the project engineering data,
"loading" is already completed with the initial configuration.
Refer to the explanations relating to initial configuration in the section "Steps for initial
configuration (Page 26)".
The section below describes how project engineering data can be downloaded to the PC
station after the initial configuration. This is necessary when the project engineering data is
not yet available at the time of the initial configuration, or to make changes to the project
engineering data.
Note
Downloading as described below only results in successful installation of the communications
services on your PC station if the arrangement of the components in the configuration data is
identical to that of the configuration data on the PC station.
The online mode allows you to download the configuration data directly to a PC station
attached to the network (MPI, PROFIBUS or Ethernet), or to load the data on the local PC
station if you are using this as the configuration station.
This situation occurs when the configuration system is installed on the PC station
(engineering station).
In this case, the configuration data is transferred directly over an internal PC connection.
Within the configuration system, you still use the known mechanisms for accessing the target
system.
Procedure for the step "downloading project engineering data to the PC Tool
station"
- online - local
1. Make sure that the following requirement is met: STEP 7 Profession-
The access point of the application must be set as follows: al (TIA Portal)
S7ONLINE (STEP 7) → PC internal (local)
2. Select the station you want to download to in the STEP 7 Professional STEP 7 Profession-
project. al (TIA Portal)
3. Download the engineering data with Online → Download to device STEP 7 Profession-
al (TIA Portal)
5.2.7.2 Offline mode (engineering station and runtime PC separate) - XDB import
If you are working offline, you will require an XDB file to transfer the data. The project
engineering system generates an XDB file for each configured PC station.
The storage location of the configuration file can be found in the properties of the "PC
Station" object in the configuration system. On the PC station, this file can be imported with
the "Station Configuration Editor".
Note
If the PC station cannot be reached online, the initial configuration can also be performed
offline in the PC station by importing an XDB file.
Requirements
• You are in the network view.
• On the target PC station, at least the "Remote basic communication" setting must be
selected in the "Security" menu in the "Communication Settings" configuration program.
Procedure
Follow the steps outlined below to configure a PC station:
1. From "PC systems" in the hardware catalog, drag a device for a PC station to the network
view.
2. Select the PC station.
3. Under "Properties > General" in the Inspector window, change the name of the PC station to
suit your application.
4. Drag-and-drop other required components from the hardware catalog into the PC station.
An inserted component is placed on a new index.
5. Select the PC station in the network view.
6. Select "Configure PC station online" in the shortcut menu to be able to perform the initial
configuration of the PC station.
7. In the "Configure" dialog, you can make various settings for your local area network, the
reachable computers and the target PC station.
8. Click "Configure...". You obtain an overview of the configuration to be adopted.
9. Click "OK" to download the configuration to the target PC station.
Structure
In the "Communication Settings" configuration program, you navigate as in the Windows
Explorer, for example. Navigate on the left side (navigation area). On the right side
(input/output area), you see the properties of the selected element (property object). The
elements in the navigation area are grouped as follows:
⑦ LLDP/DCP > Select communication modules for LLDP and DCP protocol
⑧ SOFTNET-IE RNA (optional) > Set RNA configuration
⑨ SIMATIC SHELL > Select communication module for WinCC communication and remote configuration
⑩ System information > Display version numbers of installed SIMATIC software
These elements are hierarchical. Clicking the arrow icon displays additional subfolders or elements.
You will find the following elements in the menu bar above:
• File > Refresh view and module list
• Language > Set interface language
• Help > Open online help, display program information
5.4.1 Overview
The following table and the following sections provide an overview of the available property
pages in the navigation area. The property pages of the modules listed in the table are only
available if a corresponding CP is available in the PC. For a detailed description of the property
pages, refer to the online help for "Communication Settings". You can open the online help
via the "Help" menu command or in the respective property page by clicking the"?" icon in the
input/output area.
Note
A restart is only possible if the module is not communicating and when it is not in configured
mode.
Note
The OPC UA servers for which "OPC UA" is enabled in the protocol selection are started
automatically. However, they can also be closed and restarted via the "Exit OPC server"
property object.
NOTICE
Impaired execution speed possible
The default setting of the traces must be used in normal operation, since changes can
significantly reduce the execution speed of programs. Note that unexpected timeouts
may occur as a result of the slowdown caused by the trace.
Therefore, switch off all protocol traces again after performing the test/diagnostics.
SIMATIC NET notification service signals changes to trace settings so that you can
immediately see that the above-mentioned operating restrictions may occur.
Proceed as follows to set the traces for the OPC server or the protocol bindings:
1. Go to "Trace settings" > "OPC trace" in the tree structure.
Reaction: The table lists the possible traces for the protocols and the OPC servers in the
display area.
2. Follow the instructions in the online help.
Follow the steps below if you want to create traces of the protocol libraries:
1. Go to "SIMATIC NET Configuration" > "Trace settings" > "Protocol trace" in the tree structure.
2. Click the "Call TraceConcept" button in the input/output area.
3. In "TraceConcept", select the tree structure whose trace is to be enabled and make your
settings. Click on "View Trace File" to view the results.
Note
The settings made in "Trace Settings" are active immediately and do not need to be confirmed
with a button.
Updating the "View Trace File" window (if several are displayed, further tabs are shown at the
top) takes up computing time and the window should only be displayed if you want to track
an error online.
Traces whose default setting has been changed are highlighted with a red exclamation mark.
Note
Do not use the Windows "Autostart" function for applications and services that are that
require PC functionality. In Windows, the function is not synchronized with the PC station
startup.
To automatically start applications or services after the PC station has started, follow these
steps:
1. Open the "SIMATIC NET Configuration" folder in the navigation area.
2. Select the "Autostart" folder.
The applications to be started are shown in the upper list, the services to be started in the
lower list. As default, both lists are empty.
3. Follow the instructions in the online help.
Application example
…
HANDLE hUp = OpenEvent(SYNCHRONIZE, FALSE,
"Global\\SimaticNetPcStationUpEvent");
DWORD dwResult;
dwResult = MsgWaitForMultipleObjects(1, &hUp, FALSE, INFINITE,
QS_ALLINPUT);
// evaluate dwResult
Note
If you change the PC name after installing the "SIMATIC NET PC Software", the certificates
installed for OPC UA are invalid and OPC UA will no longer work.
Remedy: Create a new OPC UA configuration using the link "Recreate the OPC UA
configuration".
5.4.3 Configuration
For configured communication, you require a corresponding TIA configuration for your PC
station.
The menu item "Help" > "SIMATIC NET Configuration" opens a collection of examples and
instructions. These explain how you can create such a configuration with the "STEP 7
Professional (TIA Portal)" configuration tool.
Overview
Among other things, you have the following configuration options available:
• Change the mode of the module and set the index
• Set the Industrial Ethernet network parameters for the CP 1613
• Set the Industrial Ethernet station addresses for HARDNET Ethernet modules
• Set the PROFIBUS station addresses and network parameters
• Set the PROFIBUS station addresses and network parameters for the "AUTO" and "MPI"
profiles
• Set the IE PG access for SOFTNET IE modules
• Set parameters for the memory card
• Set the LLDP/DCP protocol
• Assign the application access points to the individual modules
• Set the PROFIBUS DP slave mode
• Set and edit the COML S7 connection lists
• Configure the PC station
• Select module for "SIMATIC SHELL"
These options are described in the following sections.
5.4.3.2 COML S7
General
With COML S7, you can configure S7 connections to an S7-1500 automation system, for
example. The advantage is that existing TIA configurations do not need to be adapted for this
purpose (one-sided S7 connection configuration of the PC station). This configuration is
performed by creating a COML S7 connection list for the affected module of the PC station.
Note
Remember that enabled COML S7 connection lists cannot be modified.
Note
S7 connections can be configured using STEP 7/STEP 7 Professional (TIA Portal) or COML S7.
Simultaneous operation of these differently configured S7 connections is not possible. They
are interlocked. After enabling the COML S7 connection lists, you cannot create any new
components in the "Station Configuration Editor". This means that neither XDB import nor the
downloading of a configuration in STEP 7/STEP 7 Professional (TIA Portal) is possible.
Display of the COML S7 connections to the partner stations S7-300/400 and S7-PC via the
OPC COM interface:
1. Open the directory of the "OPC.SimaticNET" OPC server under "Local COM servers" in the
navigation area of OPC Scout V10.
2. Now in the "\S7" folder, you will see all created S7 connections via which the OPC server
communicates with the partner stations.
Display of the COML S7 connections to the partner stations S7-300/400 and S7-PC via the
OPC UA interface:
1. Open the directory "UA servers" in the navigation area of the OPC Scout V10 and select the
OPC UA server "OPC.SimaticNET.S7".
2. Now in the "Objects > S7" folder, you will see all created S7 connections via which the OPC
UA server communicates with the partner stations.
Display of the COML S7 connections to the partner stations S7-1200, S7-1500 and S7-
1500S (only reachable via the OPC UA interface):
1. Open the directory "UA servers" in the navigation area of the OPC Scout V10 and select the
OPC UA server "OPC.SimaticNET.S7OPT".
2. Now in the "Objects > S7OPT:" folder, you will see all created S7 connections via which the
OPC UA server communicates with the partner stations.
After an S7 connection has been established to the partner device, you can then read, write
or monitor the process variables with the OPC Scout V10.
Note
Note on the selection of the file format
The preferred file format for exporting the COML S7 connection lists is ".lcx". This format
contains the configuration of the earlier and newer generation of S7 CPUs (S7-300/400 or S7-
1200, S7-1500, S7-1500S).
The ".lcc" file format only contains the configuration of the earlier generation of S7 CPUs (S7-
300/400). This guarantees compatibility with older versions of "Communication settings" that
only support the ".lcc" format.
Note
Note on password protected S7 connections
In COML S7 it is possible to configure S7 connections to partner stations protected by a
password (S7-1200, S7-1500, S7-1500S).
Note that when exporting the COML S7 connection lists, these access passwords are not
stored for reasons of data security.
Note
If a COML S7 connection list contains one or more S7 connections to partner stations that
are protected by an access password, the following message appears:
"You have imported one or more password protected connections. These must be enabled
by entering the password. Follow these steps to enable a password protected connection:
1. Select the CP with the protected connections under "Modules".
2. Select "COML S7" in the structure tree.
3. Select the password-protected connection.
4. Enter the password in the "OPC" tab.
5. Click on the "Apply" button.
This message means that after importing the COML S7 connection list you need to enter
the access password again for the corresponding S7 connections to enable access
protection. If you do not enter a password, this connection is configured without access
protection.
Follow the steps below if you want to change the operating mode of a module:
1. Open the "Modules" folder in the navigation area.
2. Select the required module and click on the "General" property object.
3. Select the mode you want to use for the module:
– Configured mode:
The parameters for the module are set in the project engineering.
– PG mode
The parameters for the module are set in the "Set PG/PC Interface" or "Communication
Settings" program.
4. Follow the instructions in the online help.
5.4.3.4 Displaying and setting Industrial Ethernet network parameters for CP 1613 A2
The current settings for the following functions are displayed for the CP 1613 A2 Industrial
Ethernet module and can be changed:
• Duplex mode (half duplex, full duplex, automatic)
• Medium type (AUI, TP, automatic)
• Transmission rate (10 Mbps, 100 Mbps, automatic)
Three sets of option buttons are available with which the user can select the duplex mode
(half duplex, full duplex, automatic), the type of transmission medium (AUI, TP, automatic)
and the transmission rate (10 Mbps, 100 Mbps, automatic). The default for all boxes is
"automatic". After changing the defaults, you are requested to perform a restart.
Note
If you select AUI as the medium type, you can no longer change the options for the
transmission rate and duplex mode. In this case, 10 Mbps and half duplex are set. If, on the
other hand, 100 Mbps or full duplex are selected, AUI can no longer be selected as the
transmission medium.
Current setting
Transmission parameters (current setting)
Once the CP 1613 A2 has been restarted, the current transmission parameters are displayed
in the respective fields. As long as no valid link to the partner is detected, the output box
displays "unknown".
Proceed as follows if you want to display and set the Industrial Ethernet network parameters of
the CP 1613 A2:
1. Open the "Modules" folder in the navigation area.
2. Select the Ethernet module "CP 1613" and click the "Network Parameters" property object.
3. Follow the instructions in the online help.
Note
The modules for SOFTNET Industrial Ethernet are managed by the Windows operating
system. Therefore, the station addresses of these modules must be set using the standard
mechanisms of Windows.
Proceed as follows if you want to set the Industrial Ethernet station addresses of the CP 1613 A2,
CP 1623 or CP 1628:
1. Open the "Modules" folder in the navigation area.
2. Select a module of the type "CP 1613", "CP 1623" or "CP 1628" and click on the "Address"
property.
3. Follow the instructions in the online help.
Note
The CP 1613 A2 has an adjustable MAC address which is for both NDIS and Industrial
Ethernet.
In contrast, the CP 1623 and CP 1628 have separate MAC addresses for NDIS and
Industrial Ethernet. Only the Industrial Ethernet address can be set using the
configuration.
5.4.3.6 Setting the PROFIBUS station address and network parameters in the "PROFIBUS"
profile
Proceed as follows to set the PROFIBUS station address and network parameters in the
"PROFIBUS" profile:
1. Open the "Modules" folder in the navigation area.
2. Select the relevant PROFIBUS module and the "PROFIBUS" interface profile and click on the
"Address" property object.
3. Depending on the mode set for the module, you can modify or only check the address
parameters.
– Configured mode
The parameters are set in the project engineering and cannot be changed.
– PG mode
The parameters can be changed.
4. Follow the instructions in the online help.
5.4.3.7 Setting the PROFIBUS station address and network parameters in the "AUTO"
profile
Follow the steps below if you want to set PROFIBUS station addresses and network parameters
in the "Auto" profile:
1. Open the "Modules" folder in the navigation area.
2. Select the relevant PROFIBUS module with the "AUTO" interface profile and click on the
"Address" property object.
3. Depending on the mode set for the module, you can modify or only check the address
parameters.
– Configured mode
The parameters are set in the project engineering and cannot be changed.
– PG mode
The parameters can be changed.
4. Follow the instructions in the online help.
5.4.3.8 Setting the PROFIBUS station address and network parameters in the "MPI" profile
Follow the steps below if you want to set PROFIBUS station addresses and network parameters
in the "MPI" profile:
1. Open the "Modules" folder in the navigation area.
2. Select the relevant PROFIBUS module with the "MPI" interface profile and click on the
"Address" property object.
3. Depending on the mode set for the module, you can modify or only check the address
parameters.
– Configured mode
The parameters are set in the project engineering and cannot be changed.
– PG mode
The parameters can be changed.
4. Follow the instructions in the online help.
Follow the steps below if you want to set an IE PG access for SOFTNET IE modules:
1. Open the "Modules" folder in the navigation area.
2. Select the relevant SOFTNET IE module with the "TCPIP.Auto" profile and click on the "IE PG
access" properties object.
3. Follow the instructions in the online help.
This section describes how the access point used by the application is assigned to the desired
log device.
Note
To operate the OPC server and for applications that handle their communication over
configured connections, it is not necessary to assign access points.
Follow the steps below if you want to assign an access point of an interface parameter
assignment to a module:
1. Open the "Access points" folder in the navigation area.
2. Follow the instructions in the online help.
Note
Access points must not be changed during operation.
Note
Important for PROFIBUS modules:
With PROFIBUS modules, only one interface parameter assignment can be activated at any
one time. If you select an interface configuration other than the active one by assigning
an access point, it is activated and the new interface configuration is assigned to all access
points to which interface configurations of this module are assigned!
Follow the steps below if you want to create a new access point:
1. Open the "Access points" folder in the navigation area.
2. In the right-hand window, right-click and select "New access point" in the displayed menu.
3. Follow the instructions in the online help.
Note
The PC must be rebooted after enabling or disabling the LLDP/DCP function of a module.
Overview
In diagnostics with "Communication Settings", you can, for example, do the following
• Display the operability of the modules
• Display the PROFIBUS network parameters
• Display the Industrial Ethernet network parameters
• Display the available network nodes
• Display the LSAP list of individual modules
• Display the bus statistics of individual modules
• Read out the diagnostics data of the firmware of individual modules
• Display the operating data of individual modules
• Display the USB connector data of USB modules
• Display the version information of hardware and software
These options are described in the following sections.
• Hardware identifier
Shows the ID of the device.
• Service
Shows the service used by the device.
5.4.4.11 PC configuration
This property page displays the components of the PC station in an overview table. The
following components are available:
• OPC server
• Application
• Module
Components describe the structure of a PC station. They are assigned to virtual slots. The
assignment of components to slots may be required to enable loading of TIA Portal
configurations.
Note
If you are configuring the local PC, i.e. the TIA Cloud Connector connection is not active, you
can use the "Station Configuration Editor" tool as an alternative.
If you want to configure a remote PC via the TIA Portal Cloud Connector connection, this can
only be done via this property page.
5.4.5.1 Overview
As of "SIMATIC NET PC Software V15 SP1", "Communication Settings" supports TIA Portal
Cloud Connector mode.
TIA Portal Cloud Connector operation offers the advantage that the SIMATIC NET
configuration of one or more remote PCs (PC station) can be performed from a central
location. SIMATIC NET configuration is preferably performed with a virtual machine (VM)
located in the company cloud.
The following two figures show an example of using the "TIA Portal Cloud Connector" in a
virtual environment to configure the "SIMATIC NET PC Software" of a remote PC station, e.g.
an IPC with connected production cell. The TIA Portal Cloud Connector tunnel is a TCP
connection between the VM and the remote PC.
Figure 5-1 Remote Desktop Connection (RDP) to TIA Portal via separate PG/PC
Figure 5-2 Remote Desktop Connection (RDP) to TIA Portal via IPC
Software requirements
Note the following software requirements for operation between "SIMATIC NET PC Software"
and "TIA Portal Cloud Connector":
• A TIA Portal product is installed on the VM, which contains the "TIA Portal Cloud
Connector" tool including "PC Identifier" as a component. The "Communication Settings"
tool is installed via "PC Identifier", "Communication Settings" can be found in the
"C:\Program Files\Common Files\Siemens" folder.
• The "SIMATIC NET PC Software" including the required SIMATIC NET licenses and
additionally the "TIA Portal Cloud Connector" is installed on the remote PC. The "TIA Portal
Cloud Connector" can be copied from the TIA Portal Setup, for details see the document
"Instructions on the TIA Portal Cloud Connector" on the Siemens support pages.
Additional requirements
Note the following additional requirements for using the TIA Portal Cloud Connector
connection:
• VM:
– "SIMATIC NET PC Software" must not be installed on the VM, otherwise the "TIA Portal
Cloud Connector" cannot be started as a "remote device".
– On the VM, "PC Identifier" must have a version number that is compatible (equal to or
higher) with the "PC Identifier" of the SIMATIC NET installation of the remote PC.
• Remote PC (IPC):
– "SIMATIC NET PC Software" as of version V15 SP1 must be installed on the remote PC.
– To use the "TIA Portal Cloud Connector" as a "User Device", you need a corresponding
TIA Portal Cloud Connector license. You can find detailed information on this license in
the document "Instructions on the TIA Portal Cloud Connector" on the Siemens support
pages.
Note
You can find detailed information on this topic in the document "Instructions on the TIA
Portal Cloud Connector".
Note
Actions performed in "Communication Settings" for TIA Portal Cloud Connector operation may
take longer than you are used to in local mode.
Also note the notes and restrictions in the online help of "Communication Settings" on the
topic of TIA Portal Cloud Connector operation.
Article numbers
• The part numbers for the above-mentioned SIEMENS documentation are contained in the
catalogs "SIMATIC NET Industrial Communication, Catalog IK PI" and "SIMATIC Automation
Systems SIMATIC S7 / M7 / C7 - Components for Fully Integrated Automation, Catalog
ST70".
• You can order these catalogs and obtain further information from your local SIEMENS
office or national head office.
You can find further information on catalogs and ordering details in the Siemens Industry
Mall
(https://mall.industry.siemens.com/goos/WelcomePage.aspx?regionUrl=/de&language=en)
.
The initial configuration of a PC station using STEP 7 Professional (TIA Portal) involves several key steps: 1. Start by creating a PC station in a new or existing STEP 7 project . 2. Configure the device by adding required PC modules and software applications, such as an OPC server if needed . 3. Drag components from the hardware catalog into the PC station in the network view, ensuring the setup matches the configuration list in the "Station Configuration Editor" . 4. Set network parameters for PROFIBUS and Ethernet, and configure the communication properties of the SIMATIC NET OPC server . 5. Save the configuration and project engineering data, and store them in an XDB file if necessary for offline configuration . 6. Perform the initial configuration online or offline: for online, ensure that remote basic communication is enabled, and for offline, use an XDB file . 7. Transfer the configuration data to the PC station via the network or import via the XDB file, completing the configuration by downloading the data to make it operational .
To configure the CP 1616 as both a PROFINET IO controller and IO device, start by setting it up as an IO controller in the PC station using the SIMATIC Manager . Select the CP 1616 and access "Object Properties" to enable both the "PROFINET IO Controller" and "Enable PROFINET IO device operation" options in the "PROFINET" tab . Next, ensure the device name is entered in the "Device name" input box and uncheck the "Assign IP address via IO Controller" option; the IP address will be assigned during compilation . The CP 1616 can then function in dual mode within a PROFINET IO system as specified, enabling it to act as an IO controller for connected devices and as an IO device for higher-level controllers .
To configure OPC server permissions in a Windows domain environment, you must use the "dcomcnfg" tool to set DCOM security settings. These include specifying access, launch, and activation permissions in the "Security" tab of the "OPC.SimaticNET Properties" dialog box. You should add the account of the user for which the OPC server will execute, ensuring it has adequate launch and access permissions. Typically, managing users in the SIMATIC NET user group is advisable, and permissions for "ANONYMOUS LOGON" such as "Local Launch," "Remote Launch," "Local Activation," and "Remote Activation" are required . Use domain groups like SIMATIC NET for permissions and avoid granting network or local administrator rights indiscriminately to prevent unauthorized access . Additionally, configure the "Identity" tab by selecting "This user" to ensure the OPC server operates under the specified user context .
The "SIMATIC NET user group" plays a crucial role in managing OPC server access permissions. It is recommended to use this group to manage the access and start permissions of the OPC server, particularly in a domain setup, as it simplifies the management of user permissions by fetching them directly from the domain server . Users who require access to the OPC server are added as members of this group, which allows them the necessary launch and activation permissions . The SIMATIC NET user group ensures that users have the appropriate access levels for DCOM operations, facilitating secure and streamlined management across different configurations . In configuring the access permissions, launch, and activation permissions, it is advisable to include the user who will run the OPC server in the SIMATIC NET user group . This configuration not only simplifies administration but also prevents unauthorized access by ensuring only specified group members can start and access the OPC server . Additionally, the "dcomcnfg" system program must be used to adjust these settings, and the security settings may need adjustments based on domain or workgroup environments . Overall, the SIMATIC NET user group centralizes and secures the management of OPC server permissions, ensuring that only authorized users can interact with the server according to their assigned permissions and network environment .
Windows domain mode is recommended for OPC with DCOM because it centralizes user account management through a common domain server, allowing for coherent management of permissions and enhancing security across connected systems .
The "Station Configuration Editor" assists in troubleshooting PC station configuration issues by allowing administrators to evaluate diagnostic messages through the "Diagnostics" tab, which manages a buffer where PC station components log event information. This helps analyze configuration or communication problems . Additionally, it provides a breakdown of assigned indexes, making it easier to detect configuration mismatches between the local PC station and the project engineering settings in STEP 7 . By adjusting indexes or switching modules to configured mode, administrators can align configurations accurately. Inline diagnostics and status displays within the editor aid in verifying whether the hardware configuration and project engineering data match, facilitating the detection of any discrepancies .
To import engineering data to a PC station using an XDB file, first create the configuration data for the PC station with STEP 7 or NCM PC, and store it in an XDB file. This file contains data such as settings for PC modules, software applications, and network connections . Next, ensure that the PC station's configuration matches the data in the XDB file. Use the "Station Configuration Editor" to import the XDB file into the PC station, which allows the PC station to be configured for communication as per the project engineering needs . The import is possible even offline and the configuration can be adapted to match the real hardware setup using the "Station Configuration Editor" .
The critical steps involved in setting launch and activation permissions for an OPC server using DCOM include using the "dcomcnfg" system program to open the "DCOM Configuration" folder, selecting the COM object such as "OPC.SimaticNET," and then accessing the "Properties" dialog. In the "Security" tab, you must edit both "Launch and Activation Permissions" and "Access Permissions". You should grant the necessary permissions to specific user accounts or groups, like the SIMATIC NET group, instead of using default entries like "Everyone" to ensure controlled access . Additionally, permissions such as "Local Launch" and "Remote Launch", and "Local Activation" and "Remote Activation" should be specifically set for users or groups such as "ANONYMOUS LOGON" if required for OPC communication . In workgroup environments, ensure that the same user accounts exist with the same passwords on both the client and server PCs .
Enabling or disabling remote configuration for a network adapter using the "SIMATIC Shell" program is done by accessing the "SIMATIC Shell" in Windows Explorer. To enable remote configuration, select the "Remote Communication" check box in the settings menu and enter the required password for STEP 7 communication. To disable it, clear the "Remote Communication" check box .
To modify a PC station's configuration that does not match the project engineering setup, you can either: 1. Adapt the assignment in the project engineering by changing the index assignment of the modules on the PC using STEP 7 Professional (TIA Portal) to match the 'Station Configuration Editor' indices . 2. Change the configuration directly on the PC station by using the 'Station Configuration Editor' to assign different indices to components and switch modules not set for configured mode to the configured mode . Additionally, in both methods, ensure that the module arrangements and names are consistent between the PC station and project engineering data to prevent incorrect adoption of configurations .