Professional Documents
Culture Documents
Content 6
6. Station and Network configuration........................................................................ 3
6.1 Station and network configuration – Principles and relationships ..........................................3
6.1.1 The “classic” way in STEP 7...................................................................................................3
6.1.2 The PCS 7 “fashioned” way....................................................................................................4
6.1.3 Extension of ES by a single OS..............................................................................................8
6.2 PC Station Configuration ......................................................................................................10
6.2.1 PC Station Configuration on the PC .....................................................................................10
6.2.2 PC Station Configuration in the project ................................................................................11
6.2.3 Function “PLC Configure” .....................................................................................................13
6.2.4 Task and checkpoint.............................................................................................................14
6.3 AS Station Configuration in the project.................................................................................15
6.3.1 Basic Steps ...........................................................................................................................15
6.3.2 Inserting a SIMATIC S7-400 Station ....................................................................................15
6.3.3 Editing the station configuration of a SIMATIC S7-400 Station............................................16
6.3.4 Configuring the CPU.............................................................................................................20
6.3.5 Configuring the Ethernet interface ........................................................................................22
6.3.6 Configuring the DP master ...................................................................................................23
6.3.7 Configuring the DP slaves ....................................................................................................28
6.3.8 The final Download ...............................................................................................................31
6.3.9 HW Config - Diagnostics.......................................................................................................32
6.3.10 Task and checkpoint.............................................................................................................33
6.3.11 Comparing PROFIBUS DP and PROFINET IO....................................................................34
6.3.12 Configuring the IO Controller ................................................................................................35
6.3.13 Configuring the IO Devices...................................................................................................37
IE PG/PC Interface:
e.g. MPI or
DP
ISO Industrial Ethernet
Image 1:1
Project ES
Station Configurator
AS ES „virtual“ rack
real existing CP
Plant bus, IE
Configuration of stations:
• Make an “image” 1:1 to the real existing hardware of every station in the project.
• Configuration conforming to slots:
AS hardware is structured by slots in a rack. Each slot is allocated by a hardware
component like power supply, CPU, CP…
Properties of the component in a slot include type, addresses…
Since there is no real existing slot orientation of components in a PC station, a structure
with slots similar to an AS rack is simulated by the Station Configurator.
From this follows, that the PC hardware has to be described in 2 different localizations:
• Hardware of the station, represented by the Station Configurator of the PC station
• Hardware description in the HW config of the PCS 7 project
PG/PC Interface
The interaction of your PC Station with various bus systems for networking of
automation systems (e.g., MPI bus, Industrial Ethernet,…) requires specialized
interfaces. Each of your integrated and installed interfaces is represented by an
interface parameter assignment.
“PC internal”
"PC internal" is a centrally configurable interface, which can be loaded with project-
specific settings for all stations on the plant bus. The settings are made on the ES in the
PCS 7 multiproject and downloaded from the ES.
As soon as "PC internal" is activated, the network adapter begins working in
"configured mode", otherwise it is in "PG mode".
Field-PG
MPI
PG/PC-interface:
target system DIRECT Selection of a „driver-instance“
(CPU) Download
for STEP 7 communication (S7ONLINE)
3COM ISO
ES/PC station
Working in „Configured mode“
MPI
PG/PC-interface: Download
INDIRECT Selection of „driver-instance“
CP1613 ISO
Target system?
Own or other PC „virtual rack“
or AS-CPU?? (Station Configurator)
PC station
configuration
Activating PC internal
Activate the “PC internal” interface via the Dialog “Set PG/PC Interface” in SIMATIC
Manager:
Configuration Console
All communication modules, on this station available for PCS 7, are listed here.
All access point and their assignments are listed here and can be changed
See [102] PCS 7 V8.0 PC Configuration and Authorization - 12_2011, 4.7.7 for more
details about use of SIMATIC NET configuration console as possible alternative
procedure.
Download to ES
ES
AS
„virtual“ interface:
PC internal (local)
PG/PC Interface
Plant bus, IE
The central ES has to be loaded at first with all information to get the capacity for
download to all other station (AS and OS) involved in the PCS 7 project.
The configuration data are checked during the download. Both the configuration in the
PCS 7 project and the configuration in the Station Configurator have to contain the
same information as precondition for a successful download.
Status information about "download successful / unsuccessful" is displayed in the
Station Configuration Editor.
After successful download, the ES has access to the IE network, and within access to
all connected stations:
AS and PC stations (e.g. server) can be reached and loaded via ES-CP and “its
network".
The ES got this information by configuration data of the PCS 7 project!
Download to AS
ES
AS „virtual“ interface:
PC internal (local)
PG/PC Interface
Several WinCC Applications are available being specialized for different types of PC
stations (e.g. OS, OS server or client, Batch…)
An example for single OS stations is the application WinCC Application.
If you want to use the ES also as OS Single Station, then you have to extend the PC
configuration of ES by a WinCC application for single OS stations:
AS OS ES
Plant bus, IE
Image 1:1
PCS 7 Project, administrated in the Engineering System
See [103] PCS 7 V8.0 Engineering System - 12_2011, 8.10 for more details
Rename the PC station so that its name matches that of the computer.
To do this, you can activate the "Computer name identical to PC station name"
option, which means you do not have to make as many entries and the potential for
typing errors is reduced.
A yellow arrow then appears on the PC station icon in the SIMATIC Manager to indicate
the capability of the ES to establish a connection to the plant bus via the "PC internal"
interface.
After renaming its configuration is to be opened:
6 4
7 5
Main components:
1. CPs for high performance applications:
− higher number of communication partners;
− redundant connections
− time synchronization
2. standard network adapter
3. standard object for single or multi user system
4. object for OS Client
5. object for referenced OS client
6. object for central archive server
7. (stby) stands for redundant partner
See [103] PCS 7 V8.0 Engineering System - 12_2011, 8.5 for more details
See [103] PCS 7 V8.0 Engineering System - 12_2011, 8.4.10 for more details
Goal
A configured SIMATIC PC Station, both in the project and the Station Configurator.
Checkpoint
Two questions …
• What additional components can
be added in the Station
Configuration Editor?
• What makes these components to
be listed here?
Opening HW Config
1. In this “empty“ station, all components are to be inserted using the HW config tool
2. Alternative: After creating a multiproject with the wizard, a project with a
preconfigured S7-400 is available then.
Adjusting is always possible using HW Config.
The configuration of an AS station must contain all real placed components and
modules:
User interface
1 2 3
5
6
Main elements:
1. Switching between Offline and Online window
From the HW Config you can read information from modules directly (e.g. for
diagnostics)
2. Save and Compile
After configuration of the components, the data can be saved and compiled.
3. Download to station
After compilation the data can be downloaded to the station.
4. Station window
This area is filled with racks as the main parts of a station. Also objects for
distributed IO and field devices and the required master systems (networks for IO).
5. Window for hardware catalog
To select the required components: e.g. racks, modules, interface modules.
6. Object for distributed IO device
7. Configuration table
Represents the racks and their modules, offers a certain number of slots in the
same way the real racks do.
1
2
Main areas
1. Find field
Entrance possibilities:
− In the Find field you can enter any text, catalog info or order number.
Not case sensitive
− wildcards (*, ?,….) are supported
− you can also enter a part of an key word (e.g. 331)
2. Using the pull down list “Profile“ you can select several catalog profiles.
You can adapt the profiles to your needs.
3. Object for the required module (in this case with a firmware version).
4. Information of the selected component
Versions
Many modules are available in different versions (Firmware versions).
During operation of a plant it may happen that you are forced to replace an older version
of a module by a new one with a higher version. In that case the old version remains in
the HW Config and the new module is placed.
Download
When the consistency check is error free, the required system blocks are created,
without any user interference. After that they can be downloaded into the AS.
The AS contains all the required information to test if the real configuration fits to the by
HW Config created configuration.
I will be hidden for the user that many additional features are activated, so that in the
events of failures the related messages and alarms will be generated.
To download the HW Config data into the AS, the entire communication path from the
ES PC up to the Ethernet CP in the AS must be configured properly.
For the initial download into the AS, a number of configuration steps are to be done
using the tool NetPro. It will be explained in a later stage.
Startup properties
In the Startup properties the most important is the activated option “Warm restart“.
This causes the actual process values not to be reset to the initial values.
It is a default setting for PCS 7 that is not to be changed!
Please note, that a PCS 7 AS is always to be equipped with a buffer battery and a
RAM memory card.
1 2 3
1. List of OBs assigned to cyclic interrupts (grayed out = not available fort his CPU)
2. Interval of the cyclic interrupt
3. Assigned Process image partition (PIP)
Organization blocks (OBs) form the interface between the CPU operating system and
the user program. OBs are called by the operating system and control the cyclic and
acyclic program sequence, the startup behavior of the automation system and the
processing of faults.
Start events triggering some groups of OBs are called interrupts.
Cyclic interrupts do their job with predefined time interval. They are represented by
OB30 – OB38.
OBs also control the sequence of processing the individual program blocks. The
processing of one OB can be interrupted by another OB (determined by the priority).
Before any program run, the CPU loads the signal values of the input modules into a
memory, the Process Image Inputs (PII). Because of this PII, the signal values will be
constant during the program run. During the execution of the user program, output
values are assigned to the Process Image Outputs (PIQ). At the end of the program run,
the values of the PIQ are transferred to the output modules.
To control the update of the PII at the start of a program run triggered by a cyclic
interrupt, and the update of the PIQ at the end of a program run, the so called Process
Image Partitions (PIP) are assigned to the cyclic interrupts in use.
In process automation with PCS 7, the Cyclic Interrupts (OB30-OB38) are to be used
with an assignment to a Process Image Partition.
The Process Image Partitions are required at the configuration of the signal modules.
Automation functions are “inserted” into the run sequence of an (Cyclic Interrupt) OB.
1
2
4
5
1. Device name is not relevant when this module is used for the plant bus only.
2. ISO connections
3. TCP connections, ISO over TCP connections, UDP connections
4. Creating a new subnet object
5. List of available subnet objects
The connection to the plant bus is made by selection of the related subnet object in the
properties of the Ethernet CP.
When a multiproject has been created by the wizard, the project does not contain a
subnet object for Industrial Ethernet. The required subnet can be created in the
properties of the Ethernet interface.
On a with ISO protocol running plant bus, every MAC address can be assigned only
once.
Objects
3 4
1
1. Internal Profibus interface of the CPU, default set with a DP Master system.
2. External Profibus interface: is realized by the CP 443-5 Ext.
The module can be placed to have additional DP master systems.
3. Subnet: object for a Profibus net. In its Properties you can adjust the transmission
rate and the profile. Always assign a useful name (default: PROFIBUS(1)).
4. DP master system: All slaves assigned to a master form together with the master a
master system. A master system is a part of a PROFIBUS subnet.
5. Object for a Profibus slave. Distributed IO devices or field devices are assigned a
master system as a slave object. In case of a ET200M it can be the IM 153-2, for
connecting to the Profibus.
Every node (master and slave) is assigned a Profibus address (0…126)
Orphaned master systems are put into a list that will appear when you want to assign a
master system to a Profibus interface. In that way you can connect an existing master
system, including the included configuration of distributed IO to another Profibus
interface.
Connecting with Profibus subnet and assigning the address to the interface
1
2
3
4 5
For assigning Profibus addresses, only the for that subnet available addresses can be
used.
A Profibus interface must not be assigned as a master system, but can still be
connected to a subnet. I that case the Profibus address is still in use.
Independent from separating the master system, you must disconnect the Profibus
interface from the subnet, before the address can be used by another node (another
Profibus interface).
With the setting DPV1 also DP slaves, not supporting DPV1 can be connected and
operated.
See [403] Source name, for more details on configuring PROFIBUS hardware.
1
2
3
7
5
For use in PCS 7 the racks of ET200M should be equipped with active bus modules.
2
1
Diagnostics enabled
Modules with diagnostic recognize internal and external module faults and generate
diagnostic alarms.
With the enabling of the diagnostic interrupt, the diagnostic alarms will be generated
automatically through the PCS 7 drivers after an OS compilation.
5 6
2 3
1. Measuring type must fit the Position of Measuring Range Selection Module.
2. Active channels
3. Inactive channels
4. Channel group specific Diagnostics settings
5. Enabling the diagnostic alarms for the entire module
6. Not to be set for PCS 7. This function is covered by the channel drivers.
1 2
5
6 7
1. In the tool bar, click on the Offline <-> Online button. This will switch between the
Offline and Online window, not closing the earlier window. Icons represent states
and modes. To have an impression 4 examples:
2. The CPU Stop and Run mode. Run mode is active now in the window.
3. Mismatch between preset and actual configuration: the configured module does not
exist or a different module type is inserted.
4. Diagnostics not possible: No online connection, or the module does not return
diagnostic information.
5. Fault: module has a fault.
Possible causes: diagnostic interrupt, I/O access error, or error LED detected
More diagnostic information is available after double click on the regarding module. The
Module information window allows to read the diagnostic buffer:
3
1
Goal
A configured SIMATIC S7-400 Station, to be used as the AS in the training application.
Checkpoint
Find out:
• What IO address ranges are in use,
set by HW Config?
• Be sure the address range 100 …
299 is not used, it will be used by
the process simulation.
• If used, please modify the
addresses now !
Address Assignment of
PB-Adr. 0...127 Device Name
Equipment
Stations-Nummer Number allocation Device Number
From several participants, possible only Access to Data of a From several participants, possible
reading Field Equipment reading and writing
Only one priority possible Alarms and Diagnosis Can be differently prioritized
Simple designation of Address/Name of
the device at the project (through
Over DIP-Switch or by Telegram Addressing set up Controller with support from Engineering-
Tool)
Max. 12 Mb/s (Token) Baud rate 100 Mb/s (full duplex, i.e. 200 Mb/s)
Typically Line structure; Tree or Ring
Line, Star, Tree, Ring and mixed
possible with restrictions; terminal Topology configuration possible
resistance at the last participant needed
Addressing
Profinet IO: Simple name designation
Profibus DP: Individual
through Controller with support of
addressing in each station
Engineering System
Before the distributed IO can be used by the central station it must have an address:
• For DP slaves: a number: 0 …126
• For IO devices: a device name
The device name can be assigned in different ways, e.g. by the HW Config tool of
STEP 7.
Initial Steps
5
1
4
6
1
2
1. Select in the catalog: the PROFINET IO tree, the required “family” and the Interface
module.
2. Open the device properties
3. Enter the required name. Press the Ethernet button to continue.
4. Enter the required IP address.
After closing the windows the modular IO device is ready to accept the modules.
1 2
1. Select the IO Device. The Configuration tables lists the possible slots.
2. Open the tree under the placed ET200M interface module.
3. Open the folder representing the type of modules.
4. Place the required module on the proper slot.
1. From SIMATIC Managers Options menu, open the Set PG/PC Interface
dialog window, to change the S7ONLINE access point to TCP/IP on the ES
Ethernet interface in use.
2. Create a physical cable connection from your ES to the unused port of the
PROFINET interface module, to be able to access the IO device.
Then, continue in HW Config:
1 3
5
7
4