PCS 7 FoundationFieldbus en en-US

Security information 1
Introduction 2
Basics of the FOUNDATION
Fieldbus 3
SIMATIC
System planning 4
Process control system PCS 7
FOUNDATION Fieldbus
Engineering 5
Commissioning 6
Commissioning Manual
Redundancy and system
changes during operation 7
Valid for the Process Control System software

package; SIMATIC PCS 7 as of V9.0 SP1 including
SIMATIC PDM V9.1
10/2017
A5E39550932-AB
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
Siemens AG A5E39550932-AB Copyright © Siemens AG 2017.

Division Process Industries and Drives Ⓟ 12/2017 Subject to change All rights reserved
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents
1 Security information......................................................................................................................................5
2 Introduction...................................................................................................................................................7
3 Basics of the FOUNDATION Fieldbus..........................................................................................................9
3.1 Device integration with EDD..................................................................................................11
3.2 Device addresses...................................................................................................................12
3.3 Block model of device parameters.........................................................................................13
3.4 Capability levels (device variants)..........................................................................................16
3.5 Contact partner......................................................................................................................18
4 System planning.........................................................................................................................................19
4.1 Nodes in the FOUNDATION Fieldbus....................................................................................19
4.2 Configuration..........................................................................................................................20
5 Engineering................................................................................................................................................23
5.1 Prepare..................................................................................................................................24
5.1.1 How to integrate a device description....................................................................................24
5.2 Configuring.............................................................................................................................25
5.2.1 How to prepare a FOUNDATION Fieldbus for FF devices....................................................25
5.2.2 How to place FF devices on the FOUNDATION Fieldbus.....................................................27
5.2.3 Checking the bus parameters................................................................................................31
5.2.4 Additional notes on configuration...........................................................................................32
5.2.5 How to configure FF-internal interconnections (Control in the field)......................................33
5.2.6 "Interconnection Editor" dialog box........................................................................................35
5.2.7 Adding deleted default blocks................................................................................................37
5.2.8 How to replace an FF device.................................................................................................37
5.3 Parameter assignment...........................................................................................................38
5.3.1 How to assign parameters of the FF devices.........................................................................38
5.3.2 Bus parameters......................................................................................................................40
5.3.3 How to assign bus parameters...............................................................................................45
5.3.4 How to plan the macrocycle...................................................................................................47
5.4 Using the applications............................................................................................................50
5.4.1 Overview................................................................................................................................50
5.4.2 Identifying FF devices with SIMATIC PDM............................................................................51
5.4.3 Specifying the device identification of the FF devices (TAG name and address)..................53
5.4.4 Editing symbols (symbolic names).........................................................................................54
5.4.5 Configuring interconnections to the FF devices.....................................................................55
5.4.6 Configuring the operator station.............................................................................................56
6 Commissioning...........................................................................................................................................57
6.1 Compile and download...........................................................................................................57
6.1.1 Introduction............................................................................................................................57
FOUNDATION Fieldbus
Commissioning Manual, 10/2017, A5E39550932-AB 3
Table of contents
6.1.2 Downloading objects in the FF segment................................................................................58

6.2 Diagnostics.............................................................................................................................61
6.2.1 "Modes" and "Status" menu commands.................................................................................61
6.2.2 Performing diagnostics...........................................................................................................63
7 Redundancy and system changes during operation..................................................................................65
7.1 Redundancy...........................................................................................................................65
7.2 System changes during operation..........................................................................................66
Index...........................................................................................................................................................69
FOUNDATION Fieldbus
4 Commissioning Manual, 10/2017, A5E39550932-AB
Security information 1
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 constitute one element of such a concept.
Customers are responsible for preventing unauthorized access to their plants, systems,
machines and networks. Such systems, machines and components should only be connected
to an enterprise network or the internet if and to the extent such a connection is necessary
and only when appropriate security measures (e.g. firewalls and/or network segmentation) are
in place.
For additional information on industrial security measures that may be implemented, please
visit:
https://www.siemens.com/industrialsecurity
Siemens’ products and solutions undergo continuous development to make them more secure.
Siemens strongly recommends that product updates are applied as soon as they are available
and that the latest product versions are used. Use of product versions that are no longer
supported, and failure to apply the 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.
FOUNDATION Fieldbus
Security information
FOUNDATION Fieldbus
Introduction 2
SIMATIC PCS 7 provides the option of integrating field devices on FOUNDATION Fieldbus
H1 (hereafter referred to simply as FF). FF devices are generally connected to a SIMATIC
station via a bus link on PROFIBUS DP. Bus links are gateways between bus systems and
enable the communication connection of the bus systems.
The following bus link is typically used for the communication between PROFIBUS DP and
FOUNDATION Fieldbus in PCS 7 systems.
● Compact FF Link
Examples for configuration of FF segments in PCS 7

The display shows an example of the connection of FF devices to the automation system. The
additional use of the active field distributor enables mutual decoupling in case of FF device
faults.
(WKHUQHW
352),%86'3
))VHJPHQW
%XVOLQN %XVOLQNV
&RPSDFW))OLQN
))VHJPHQW
$FWLYHILHOGGLVWULEXWRUV
)LHOGGHYLFHV
SIMATIC PCS 7 supports the connection of FF devices

SIMATIC PCS 7 supports the connection of FF devices by way of the following functions:
● Central engineering without additional tools
● Import of the electronic device descriptions (EDD) of FF devices
(you can find additional information about this in the section "Device integration with EDD
(Page 11)")
● Channel blocks of the PCS 7 Advanced Process Library (APL)
● PCS 7 Asset Management
FOUNDATION Fieldbus
Introduction
Basic knowledge required

This documentation is intended for personnel working in the fields of configuration,
commissioning, and service.
Basic knowledge of the general use of the PC/programming device and of the use of the
Windows operating system is required.
Knowledge of the functions and configurations of the following products is required:
● SIMATIC PCS 7
● SIMATIC S7 (S7-400, STEP 7)
● SIMATIC NET
● SIMATIC PDM
Basic knowledge of the FOUNDATION Fieldbus is required.
An understanding of the operating instructions of the bus link is required.
Information for FF users

Users who have configured only FF up to now can acquire the necessary knowledge of PCS
7 with the help of the PCS 7 documentation. You can find an introduction to working with PCS 7
in the SIMATIC PCS 7 Process Control System; PCS 7 - Getting Started documentation.
Conventions
Some of the information in this documentation applies to several components. To ensure that
the products to which such information applies are clearly identifiable, we have used the
following designations:
Designation Validity
Bus link The associated information pertains to the components you can order as a
gateway from PROFIBUS DP to the FOUNDATION Fieldbus for an automa‐
tion system.
Compact FF Link The associated information pertains to the Compact FF Link. The following
module is used in this bus link: Compact FF Link (IM 655-5 FF)
The Compact FF Link can be configured redundantly.
Changes compared to previous versions

Below, you can find an overview of the most important changes in the documentation compared
to the previous version:
As of PCS 7 V8.1 SP1 or higher
● Use of the "Compact FF Link (IM 655-5 FF)" bus link
FOUNDATION Fieldbus
Basics of the FOUNDATION Fieldbus 3
FOUNDATION Fieldbus (FF) and PROFIBUS PA operate according to IEC 61158-2. The
communication on the fieldbus and the voltage supply of the bus nodes are combined in one
shielded two-wire cable. Up to 32 bus nodes are possible on one FF segment (bus link +
maximum of 31 field devices). Data packets are modulated and transmitted on the supply
voltage for the fieldbus nodes. The transfer rate is 31.25 Kbps.
The most important distinctions between PROFIBUS PA and FOUNDATION Fieldbus
Licensing
● You need the "PDM Foundation Fieldbus" license key to work with SIMATIC PDM.
Operating mode
● PROFIBUS PA devices are operated in master/slave mode.
● FF devices are operated in publisher/subscriber mode.
Connection to PROFIBUS DP
● PROFIBUS PA devices are connected to up to five FDC 157 DP/PA couplers via DP/PA-
Link (redundancy with 2 fieldbus couplers possible).
● FF devices are connected to the automation system via a bus link. The following bus links
are approved for PCS 7:
– Compact FF Link
Configuration with Compact FF Link (redundancy with 2 Compact FF Link possible)
Communication with the automation system

● PROFIBUS PA devices only communicate via the automation system. An exception to this
rule is the direct access to a PA device.
● FF devices can communicate on the FF segment without involvement of the automation
system. The name of this function is "Control in the field" (CiF). CiF enables technological
function between FF devices.
Terms used for FOUNDATION Fieldbus (FF)
Publisher and Subscriber

In the time period during which an FF device sends data to the FF, it is referred to as the
Publisher.
In the time period during which an FF device reads data from the FF, it is referred to as the
Subscriber.
The schedule defines when a Publisher sends data and when a Subscriber receives data.
FOUNDATION Fieldbus
Basics of the FOUNDATION Fieldbus
Client and Server

The client-server principle is used for acyclic services.
Communication types
Two types of communication are used with FF:
● Cyclic communication
Cyclic communication is defined in the schedule. It includes tasks such as closed-loop
control of process values (control functions) and operator control and monitoring functions.
● Acyclic communication
Acyclic communication is used for transmitting unscheduled information. Examples of this
information are:
– Maintenance/diagnostic data
– Configuration data
– Parameter assignment data
Schedule and LAS (Link Active Scheduler)

With FF, the schedule defines when an FF device sends or reads cyclic data. The schedule
prevents conflicts on the FF segment during communication. A bus link performs the LAS
function in PCS 7 during normal operation.
As long as the FF segment has a power supply, suitable FF devices (Link Masters) can assume
the LAS function.
Note
Compact FF Link
When the Compact FF Link is used, it is not possible for the field devices to take over the LAS
function.
Macro cycle
The macro cycle is a time period that must be defined for each system. The following tasks
must be performed during this time period:
● All FF devices must be processed.
● Information must be transmitted by means of acyclic communication.
The FF specification recommends that at least 50% of the bus time be kept free for acyclic
communication.
FOUNDATION Fieldbus
3.1 Device integration with EDD
3.1 Device integration with EDD

FF devices are integrated in the control system in PCS 7 using the application SIMATIC PDM.
Note
Integrating FF device descriptions
Device descriptions of FF devices that you do not find on the "Device Library..." DVD provided
with SIMATIC PDM must be modified before the integration. Please speak with your contact
(Page 18) about this.
Liability
Siemens explicitly declines any liability for damages resulting from the use of the following
device description files and use in conjunction with the associated devices:
● For device-specific device description files for non-Siemens devices, the Siemens warranty
only applies up to the interface.
● For device description files integrated through catalogs
NOTICE
Important note on the device description files included with the SIMATIC PDM
The device description files of non-Siemens field devices have not been developed by
Siemens and are included with the shipped products free of charge. The licensee is entitled
to use the device description files of these devices in the same manner as a trial license
in accordance with the general terms and conditions for the supply of software for
automation and drive technology. This right of use may be exercised by the licensee as
long as the right of use for the PDM software is in effect.
Standardized device descriptions

Standardized device descriptions enable intelligent field devices from different manufacturers
to be integrated in different control systems. The IEC 61804-3 standard governs the structure
of device descriptions (DD). This standard was developed in cooperation with the following
organizations:
● PROFIBUS User Organization (PNO)
● Hart Communication Foundation (HCF)
● Fieldbus FOUNDATION
● OPC Foundation
The device descriptions are based on the EDDL (Electronic Device Description Language).
FOUNDATION Fieldbus
3.2 Device addresses
Information in device descriptions

Device descriptions contain all information required for correct interpretation of device data.
● Pre-defined device descriptions (standard DDs) describe the key parameters. These
standard DDs are available from the user organizations, for example, through the Fieldbus
FOUNDATION.
FF devices can interpret and display the data and functions of this standard DD. The basic
functions of the user interface are stored in the standard DD.
● Device-specific functions and parameters can be stored in an extended device description.
● The device description specifies the rules for the instantiation of blocks:
– Number and type of the initially automatically created, deletable blocks (default blocks)
– Maximum of all instantiable blocks
– Maximum of the instantiable blocks of a certain type
– Hardware-dependent, type-specific limitations of the maximum number of blocks
Additional information
● IEC 61804-2
● IEC 61804-3
● Section "Block model of device parameters (Page 13)"
3.2 Device addresses
Address ranges in PCS 7

The following table shows the distribution of address ranges for the FF segment:
Address range Information on the address range

0 to 15 Reserved by the system (use not permitted)
16 to 19 Reserved range for bus link:
Address Compact FF Link (IM 655‑5 FF with integrated Field Device Coupler)
16 Compact FF Link
(with redundant configuration: left Compact FF Link)
17 with redundant configuration: right Compact FF Link
20 to 35 SIEMENS Polled Range:
reserved for cyclical data exchange with FF devices (optional expansion up to 50)
36 to 231 SIEMENS Unpolled Range:
FF devices in this address range are only recognized if the "standard range" has been extended.
You can find information on this in the section "Specifying the device identification of the FF
devices (TAG name and address) (Page 53)".
232 to 247 SIEMENS reserve range:
Reserved address range for new FF devices or FF devices that are not in operation, and for
FF devices that are only temporarily connected
FOUNDATION Fieldbus
3.3 Block model of device parameters
Address range Information on the address range

248 to 251 Range for temporary FF devices
● Devices that are made available and that require a device address.
● Devices that are moved to this range by the automatic address conflict resolution (up to four
FF devices)
● Devices that were removed from processing (using the "Reset address" function)
You will find information on this in the online help of SIMATIC PDM
Note for users:
Make sure that there are always free addresses in this range. This enables automatic assign‐
ment of a temporary address to new FF devices. Some actions of SIMATIC PDM are based on
the availability of this address range (e.g., "Assign address and TAG").
252 to 255 Range for LAS-compliant temporary FF devices
Automatic address conflict resolution for device addresses

Connected FF devices will be detected automatically at the FF segment.
In the case of an address conflict, one of the FF devices affected by the address conflict will
automatically be assigned a temporary address during runtime. The procedure is repeated
automatically until the existing address conflicts are resolved.
The device addresses 248 to 251 have been reserved for automatic address conflict resolution
at the FF segment.
Note
The device address that was assigned to an FF device by automatic address conflict resolution
will not be saved in the FF device.
Note the following when you use automatic address conflict resolution:
● You may not connect or switch on for the first time more than 4 new FF devices with the
same address at the FF segment.
● You have to change the device addresses of FF devices that have been assigned to one
of the temporary addresses.

The parameters (functions and data of an FF device) are assigned to block types in the device
descriptions of the FF devices:
Block type Note

Resource block One resource block per FF device.
Function block Multiple function blocks are possible for an FF device
Transducer block Multiple transducer blocks are possible for an FF device.
FOUNDATION Fieldbus
Note
Parameter assignment with SIMATIC PDM
The SIMATIC PDM application is used in PCS 7 for parameter assignment of the FF devices.
Block types
Resource block
The resource block contains device-specific information of the manufacturer.
Examples of this are:
● Manufacturer
● Device type
● Device number
● Serial number
● Hardware version
● Firmware version
Function block
Function blocks provide information about the functions available in an FF device as well as
their tasks. The schedules of the clocked data transmission defined in the schedule are based
on these function blocks. Access to the functions and their inputs and outputs is defined via
the function blocks. Each FF device has at least one function block.
Standard profiles for function blocks are defined in the FF specification. A description of the
basic functions is possible with the help of these standard profiles.
Table 3-1 Examples of the most important standard profiles for function blocks:
Block designation Function

AI Analog input
AO Analog output
B Offset (bias)
CS Control selector
DI Digital input
DO Digital output
ML Manual loader
PD PD controller (proportional/derivative)
PID PID controller (proportional/integral/derivative)
RA Ratio controller
Transducer block
Transducer blocks make it possible to influence the input and output variables of a function
block.
FOUNDATION Fieldbus
Examples of this are:

● Calibration and conversion of measured and control data
● Linearization of characteristic curves
● Conversion of physical quantities using other process data
Multiple capability levels

Some manufacturers offer FF devices in variants with a scalable scope of function and
transducer blocks. These variants are designated as capability levels in FOUNDATION
Fieldbus.
You can find information on this in the section "Capability levels (device variants) (Page 16)".
Block types in HW Config and in SIMATIC PDM

In the device catalogs of HW Config and SIMATIC PDM, you will find the following groups of
device-specific blocks:
Property Permanent blocks Default blocks Instantiable blocks

(only for devices with capabil‐
ity level)
Identifier in the configuration in FB FB ● FB TYPE
HW Config ● TB TYPE
Font in the configuration in Italic Not italic Not italic
HW Config
Section with attributes in the Per instance Per instance Per block type
device description
Visibility in the catalog Not visible Visible Visible
Configuration Automatically created Automatically created Must be inserted manually
Deletion capability Cannot be deleted Can be deleted and re-inser‐ Can be deleted
ted
Objects of the block model

In PCS 7, applications in the PC stations assume the functions of FF-specific objects:
Engineering station
● Configuration of the FOUNDATION Fieldbus
● Interconnection of the FF devices
– Interconnections for the process image
You can find information on this in the section "How to replace an FF device (Page 37)".
– Interconnections within the FF devices
You can find information about this in the following sections:
- Section ""Interconnection Editor" dialog box (Page 35)"
- Section "How to configure FF-internal interconnections (Control in the field) (Page 33)"
FOUNDATION Fieldbus
3.4 Capability levels (device variants)
Operator stations and Maintenance Station

● Output of signals
– Alarms
– Events
● Monitoring
– Process control
– Maintenance
● Long-term archiving
3.4 Capability levels (device variants)

Some manufacturers offer FF devices in device variants with a scaled scope of functions.
These device variants are designated as "capability levels" in FOUNDATION Fieldbus.
Common features and differences based on capability level

Common features
● The devices use the same device description.
● The general device properties defined in the device description are identical.
Differences
● Within the capability level, the following types of function and transducer blocks are defined:
– Permanent blocks
– Initially created, deletable default blocks
– Instantiable blocks (for devices with capability level)
● The type and number of blocks can be different.
● Instantiable blocks can only be selected if at least one capability level is defined for a device.
Selecting the capability level in the device catalogs

In the device catalogs of HW Config and SIMATIC PDM, you will find capability levels at the
following place:
In the tree view as a hierarchy level below the device revision of the FF devices.
FOUNDATION Fieldbus
3.5 Contact partner
Examples
Device without capability level Device with capability level Device with instantiable blocks
Device Device Device
● Device revision ● Device revision ● Device revision
● Device revision ● Device revision ● Device revision
– Capability level 1 – Capability level 1
– Capability level 2 – Capability level 2
- Instantiable block FB TYPE <...>
- Instantiable block FB TYPE <...>
Configuring the capability level

1. In the hardware configuration, select the capability level supported by your device.
2. Configure the blocks for the device (add/delete).
Observe the following sections:
– You can find information about the properties of the blocks in the section "Block model
of device parameters (Page 13)".
– You can find information about the device description in the section "Device integration
with EDD (Page 11)".
Communication and downloading of FF devices with capability level

When the FF segment is downloaded, the instantiated blocks are created in the devices. You
can find additional information about downloading in the section "Downloading objects in the
FF segment (Page 58)".
The automation system (host) can only communicate with the device if the capability level of
the device matches the configured capability level.
3.5 Contact partner
Your contact partner (not for demo version)
Questions on SIMATIC STEP 7 / SIMATIC PCS 7 / hardware / SIMATIC PDM / problems with
S7 communication
Mailing address: SIEMENS AG

Customer Support
D-90475 Nuremberg, Germany
E-mail: online-support.industry@siemens.com
Internet: Siemens Industry Online Support (http://support.industry.siemens.com/)
FOUNDATION Fieldbus
3.5 Contact partner
Questions on devices and GSD files

Please get in touch with your contact partner at the device manufacturer.
For more information, refer to the "List of integrated devices". You can find this in the \_manuals
folder on the SIMATIC PDM Device Library 1#2017 DVD.
Follow-up installations and additional information on SIMATIC PDM are available on the
Internet at "http://www.siemens.com/simatic-pdm (http://www.siemens.com/simatic-pdm)".
FOUNDATION Fieldbus
System planning 4
4.1 Nodes in the FOUNDATION Fieldbus
An FF segment contains all nodes communicating via the FOUNDATION Fieldbus. The
following information is used for the system-specific optimization of FF segments.
Size of the process image

An FF segment is restricted to the size of the process image of the bus link (max. 244 bytes I/
O in each case).
The 244 bytes for inputs can be divided among the FF devices:
● Digital inputs (2 bytes per value, however maximum 40 DI)
● Analog inputs (5 bytes per value, however maximum 40 AI)
The 244 bytes for outputs can be divided among the FF devices:
● Digital outputs (2 bytes per value, however maximum 40 DO)
● Analog outputs (5 bytes per value, however maximum 40 AO)
A maximum of 64 bytes can be used for outputs and 64 bytes for inputs for each FF device.
Nodes in an FF segment
The maximum number of nodes in an FF segment depends on the requirements of a plant
regarding update times.
Typical number of FF devices that are integrated in a plant in an FF segment: 8 to 10 (maximum
number 31)
The time for a macro cycle is influenced primarily by the share of cyclic communication. This
share depends on the following factors:
● Properties of the FF devices used in the FF segment
● Number of input values and output values of all components connected to the FF segment
You can specify a target value for the macro cycle as well as for the ratio between the cyclic
and acyclic share. The schedule is calculated for these conditions.
If a mean time of approximately 30 ms is assumed for the output of a value from FF devices,
and the block run time is considered as acyclic bus time, then the minimum macro cycle for
15 transmitted values will be approximately one second. The time for output of a value depends
on the device in question.
Example calculation
● 15 x 30 ms = 450 ms, corresponds to the cyclic bus time
● Reserved bus time for acyclic communication
1050 ms (recommended 70%), 450 ms (recommended, at least 50%)
● Recommended macro cycle = between 1500 ms and 9000 ms
FOUNDATION Fieldbus
System planning
4.2 Configuration
Current consumption
The permissible current consumption of all components on an FF segment depends on the

type of bus link:
Compact FF Link: Maximum 500 mA
I/O data
The parameters, inputs and outputs of FF devices are distributed over function blocks. An FF
device can have several function blocks. Only configure the required I/O data of an FF device.
The number of processed function blocks has an effect on the macro cycle.
4.2 Configuration
Hardware
Always connect an FF segment to the automation system via PROFIBUS DP. You need a
suitable bus link for the transition between PROFIBUS DP and the FF segment.
The bus link can be operated on the integrated line of the CPU if the CPU supports the data
record gateway.
The table shows possible CPU versions:
CPU type As of version

SIMATIC S7 41x V5.1
SIMATIC S7 41xH V6.0
WinAC RTX V4.6
Network configuration
The following structures are typical for the configuration of FF segments in PCS 7:
● Line
● Redundant configuration (see also section "Redundancy (Page 65)")
FOUNDATION Fieldbus
System planning
4.2 Configuration
Line lengths
An FF segment can be up to 1900 m long when the appropriate bus cable (type A) is used.
NOTICE
FF segment running into hazardous areas of zones 0 or 20 (Ex ia)
If spur lines from an FF segment run into these hazardous areas, the maximum allowed length
of the FF segment amounts to 1000 m.
When components suitable for hazardous areas are used, greater distances may be possible
(for example Active Field Distributor intrinsic Safety). Check the technical specifications of
the components.
Spur lines
● If possible, only one device should be connected to each spur line.
● You need to include the lengths of spur lines to the FF devices in the calculation of the FF
segment length.
The permissible length of each spur line depends on the number of spur lines and
connected devices. If more than one device is connected to a spur line, the permissible
length of the spur line is reduced. Each additional connected device reduces the maximum
length of the spur line by 30 m.
Number of spur lines Permissible length of a spur line (length in meters)

(longer than 1 m) Spur line outside Ex ia Spur line in Ex ia
1-12 120 30
13-14 90 30
15-18 60 30
19-24 30 30
25-31 1 1
SIMATIC Fieldbus Calculator

The SIMATIC Fieldbus Calculator provides support for the calculation and design of fieldbus
segments with an active field distributor. You enter the relevant physical data (cable lengths,
base current of the devices, topology, etc.) for every fieldbus segment. The electrical variables
are calculated based on the specified configuration and limit violations are reported. You can
find additional information on this topic on the Internet (https://support.industry.siemens.com/
cs/us/en/view/53842953).
● Operating Instructions SIMATIC; Bus Link; Compact FF Link
● Function Manual Process Control System PCS 7; High Availability Process Control Systems
● Application description SIMATIC; PCS 7; Calculation and Design of Fieldbus Segments
with the SIMATIC Fieldbus Calculator
FOUNDATION Fieldbus
System planning
4.2 Configuration
FOUNDATION Fieldbus
Engineering 5
Overview
You configure the FOUNDATION Fieldbus and create the FF devices in HW Config.
You configure a bus link suitable for the connection of an FF segment on the PROFIBUS DP .
A "Foundation Fieldbus: FF subsystem" object with standard bus parameters is created
automatically with the bus link.
You assign the parameters of the FF devices with SIMATIC PDM.
Basic procedure
If you want to connect an FF device to an automation system in a PCS 7 project, the following
steps are required:
1. Integrating device descriptions (Page 24)
2. Create a bus link with FOUNDATION Fieldbus (FF subsystem) on the DP master system
(Page 25)
3. Insert FF device (Page 27)
– Insert an FF device and assign the address on the FF segment
– Assign addresses in the I/O range and symbolic names for signals
– Specify the device name and object properties
4. How to configure FF-internal interconnections (Control in the field) (Page 33)
5. Configure the bus parameters (Page 45)
6. Generate a schedule and load it into the FF segment (Page 58)
Details about the individual steps are given in the following sections.
See also
How to replace an FF device (Page 37)
How to assign parameters of the FF devices (Page 38)
"Interconnection Editor" dialog box (Page 35)
FOUNDATION Fieldbus
Engineering
5.1 Prepare
5.1 Prepare
5.1.1 How to integrate a device description
Requirements
SIMATIC PDM is installed.
All SIMATIC programs on the engineering station are closed.
Procedure
1. In the Windows Start menu, select the menu command SIMATIC PDM > Device Integration
Manager under Siemens SIMATIC programs.
To be able to use the Device Integration Manager, you must accept the license agreement.
2. Select the File > Read device descriptions from source directory....
If the device descriptions are compressed, select the menu command File > Read device
descriptions from compressed source ... .
3. In the tree view, navigate to the directory with the device descriptions. Select the drive
containing the DVD "Device Library".
Note
DVD "Device Library"
The "Device Library" DVD is supplied with SIMATIC PDM.
4. Click "OK".
The device descriptions found are displayed in the "Devices" list.
FOUNDATION Fieldbus
Engineering
5.2 Configuring
5. Select the check boxes for the devices whose device descriptions are to be integrated. On
the devices that are not yet integrated or have been integrated with an older version, the
check box is automatically selected.
The "Fieldbus Foundation" directory contains all FF devices (device library of the Fieldbus
Foundation and other individual devices).
You can work with a split device list window.
Note
Integrating device descriptions
Many FF devices require information that is stored in other device descriptions.
Recommendation:
Integrate all device descriptions that provided with the SIMATIC PDM "Device Library" DVD.
6. Select the Catalog > Integration... menu command.

The device descriptions are transferred to the PC.
Note
During the device description integration
Do not open any SIMATIC programs until the device description integration has completed.
Online help for SIMATIC PDM
5.2 Configuring
5.2.1 How to prepare a FOUNDATION Fieldbus for FF devices

An example of a plant configuration can be found in section "Introduction (Page 7)".
Recommendation for using symbolic names

Assign symbolic names to the signals of the FF devices. Symbolic names facilitate the
configuration and documentation of the automation task. The use of symbolic names is
considered below.
Requirements
● SIMATIC PCS 7 is installed.
● SIMATIC PDM is installed with the add-on package "SIMATIC PDM Communication
FOUNDATION Fieldbus" (standard for PCS 7).
FOUNDATION Fieldbus
Engineering
5.2 Configuring
● A project has been created in the SIMATIC Manager. An automation system with a
PROFIBUS DP master system has been created in HW Config.
Additional information is available in the manual SIMATIC; Process Control System PCS
7; Getting Started Part 1; section "First Steps in the Project".
● The device descriptions of the FF devices have been imported.
You can find information about this in the section "How to integrate a device description
(Page 24)".
● You know the functions and signals required by the FF device.
You can find additional information about this in the documentation for the FF device.
● The following option has been enabled for at least one AS in SIMATIC Manager > Options
> SIMATIC PDM > Settings...> "General" tab in the "Project" section:
Select type when device is inserted in HW Config
Bus link with FOUNDATION Fieldbus: Create FF subsystem

1. In the component view, select the SIMATIC station and double-click the "Hardware" object
in the detail window.
HW Config opens.
2. If the hardware catalog is not visible, select the menu command View > Catalog.
The hardware catalog opens.
3. Drag-and-drop the module to be used as a bus link on PROFIBUS DP onto the PROFIBUS
DP master system:
– IM 655-5 FF (for Compact FF Link)
4. Enter the node address for the PROFIBUS DP in the "Parameters" tab of the Properties
dialog.
A free address is suggested by the system.
Note
"Configuration via PDM" option
You configure the bus link and the FF devices using SIMATIC PDM in PCS 7. If the
"Configuration with PDM" option is selected, you can open SIMATIC PDM by double-
clicking the bus link.
FOUNDATION Fieldbus
Engineering
5.2 Configuring
5. Optional steps for redundant FOUNDATION Fieldbus:

These steps depend on the bus link that is used as the interface to PROFIBUS DP:
Step Compact FF Link (IM 655-5 FF)

a Select the IM 655-5 FF.
b Double-click on the slot of the first "Field Device Coupler" in the table.
The "Properties - Coupler" dialog box opens.
c Select the "Parameters" tab.
d Select the redundancy mode in the "Value" column:
● No redundant configuration (default)
● Coupler redundancy
● Ring redundancy
Information If you want to use ring redundancy, the "RING" DIP switch must be set to the "ON"
on the position.
"RING" DIP ● OFF: Coupler redundancy or non-redundant configuration
switch
● ON: Ring redundancy
During operation, the position of the "RING" DIP switch must match the configura‐
tion of the integrated field device coupler for both Compact FF Links.
6. Click "OK".
The interface module (IM ...) is created with a FOUNDATION Fieldbus: FF subsystem.
5.2.2 How to place FF devices on the FOUNDATION Fieldbus
Setting/changing the device name for an FF device

The following applies to FF devices in a PCS 7 plant:
● The length of the device name is 32 characters (will be automatically filled with empty
spaces).
● The following characters are not permitted:
"&?*<>|%§€'.\][
Use SIMATIC PDM to set the device name.
Requirements
● The following option has been enabled for at least one AS in SIMATIC Manager > Options
> SIMATIC PDM > Settings...> "General" tab in the "Project" section:
Select type when device is inserted in HW Config
● The device descriptions of the required field devices are integrated in SIMATIC PDM.
● HW Config is open
● A bus link with FOUNDATION Fieldbus (FF subsystem) has been created
FOUNDATION Fieldbus
Engineering
5.2 Configuring
Insert an FF device and assign the address on the FF segment

1. Double-click the FOUNDATION FIELDBUS in the current PCS 7 profile.
2. Insert FF device
Select the FF device in the folder <Manufacturer> > <Device Group> > <Device Type>.
Note
Devices with capability level
Note the following changes in the folder structure for devices with one or more capability
levels:
● One or more "Capability level ..." folders are located below the "Revision ..." folder.
● Select the appropriate folder for the device.
3. Drag-and-drop the required FF device to FF subsystem.

The "Properties FF interface FF device" dialog box opens.
4. Assign address on the FF segment
In the "Parameter" tab, enter the address of the FF device on the FF segment of the plant.
You can find information on this in the section "Device addresses (Page 12)".
5. Click "OK".
– You may receive the message that changes have to be made.
– Observe any device-specific limitations and properties of the blocks in the section "Block
model of device parameters (Page 13)".
Note
Instantiable blocks for devices with capability level
For devices with capability level, you can add instantiable blocks from the hardware catalog.
Select the blocks below the "Capability level ..." folder. You can find information on this in
the section "Capability levels (device variants) (Page 16)".
NOTICE
Deleting and adding default blocks
If the resources for additional blocks are used up, you can delete unneeded default blocks
in order to free up resources.
Read the section "Adding deleted default blocks (Page 37)".
FOUNDATION Fieldbus
Engineering
5.2 Configuring
Assign addresses in the I/O range and symbolic names for signals
You need to assign addresses in the I/O range of the CPU for required signals of FF devices.
1. Select the FF device.
2. Select signals and assign addresses in I/O range:
Select the required signals for all block types in the address table of the FF device.
You can use the typical Windows method for multiple selection.
Note
You can find information about the block types in the section "Block model of device
parameters (Page 13)". The following block types are used by default:
● Resource block
● Function blocks
● Transducer blocks
Refer to the documentation of the device manufacturer for information about the required
blocks and any necessary CiF interconnections.
– In the shortcut menu, select the menu command Assign Address.

The dialog box "Properties <signal>" opens.
– Click "OK".
The addresses in the I/O range are assigned for the selected signals.
3. Recommendation: Assign symbolic names
This measure makes configuration easier:
Assign symbolic names for all addresses.
– Select a required row (function) again in the address table.
– Select the menu command Edit symbols....
The "Edit symbols - …" dialog box opens.
– Assign a name in the "Symbol" list. You can automatically add the symbols.
– Click "OK".
– Repeat this step for all required functions of the FF device.
4. Select Station > Save and Compile from the menu.
Note
Macro cycle
If messages on the macro cycle are output when saving, settings are required.
You can find information on this in the section "How to plan the macrocycle (Page 47)".
FOUNDATION Fieldbus
Engineering
5.2 Configuring
NOTICE
Symbolic address assignment has to be checked
You may receive the following message if you change addresses at a later time:
"You are assigning parameters that will change the I/O address range of the module. Check
the symbolic address assignment afterwards."
It is imperative that you perform this check and make any necessary corrections.
Specifying the device name and object properties

1. Double-click on the inserted FF device in HW Config.
SIMATIC PDM opens.
2. Select the top node in the tree view.
3. Select the Device > Object Properties menu command.
4. In the "Object name" text box of the "General" tab, enter the following:
<the plant-specific device name (TAG)>
5. For devices to be operated as Backup Link Master :
– Select the Device > Object Properties menu command.
– Select the "Parameters" tab.
– Activate the "Backup Link Master" check box.
6. Click "OK".
7. Select the menu command File > Save.
8. Open SIMATIC PDM.
Notes on downloading
Download when "Address" and "TAG" match
● The FF device can be downloaded if the "Address" and "TAG" in the configuration match
the settings of the FF device.
Downloading when device address of the device in the system is unknown
1. Select the following menu command in SIMATIC Manager to find the FF device in the
system: Edit > SIMATIC PDM > Start LifeList.
2. When you find the desired device, do the following:
– Select the Device > Assign address and TAG menu command.
– Transfer the correct address and TAG to the FF device.
Note: Changing the address will restart the device.
– Download the configuration to the device.
FOUNDATION Fieldbus
Engineering
5.2 Configuring
● Manufacturer information of the FF device.
● Section "How to assign parameters of the FF devices (Page 38)"
● Section "Nodes in the FOUNDATION Fieldbus (Page 19)"
● Section "How to configure FF-internal interconnections (Control in the field) (Page 33)"
● SIMATIC; SIMATIC PDM documentation; chapter "Working with the LifeList"
5.2.3 Checking the bus parameters

HW Config checks whether the bus parameters have to be changed when a new FF device
has been inserted. If changes are required, the message "Change bus parameters" will be
displayed.
You can then decide if you want to change the bus parameters.
Changing bus parameters: NO

The new FF device will not be transferred.
Changing bus parameters: YES

The bus parameters are changed on all FF devices and marked as "for download" in the project.
The following bus parameters are affected:
● Slot Time
● Maximum Response Delay
● Minimum Inter DLPDU Delay
● Macro cycle
Note
Checking the macro cycle
Check the settings of the macro cycle.
NOTICE
System changes during operation
When the bus parameters are changed, the CPU remains in RUN and the communication
on the FF segment goes to STOP.
● Section "Bus parameters (Page 40)"
● Section "How to assign bus parameters (Page 45)"
FOUNDATION Fieldbus
Engineering
5.2 Configuring
5.2.4 Additional notes on configuration
Device-specific number of interconnections

The number of interconnections available as Backup Link Master for an FF device is device-
specific.
Make sure that the permissible number of interconnections on the FF segment is not exceeded
during configuration. The configured interconnections are added:
● Interconnections with the process image
● CiF interconnections
You can find additional information about this in the section ""Interconnection Editor" dialog
box (Page 35)"
Capability level
The automation system can only communicate with the device if the capability level of the
device matches the configured capability level.
Changing the configuration

Separating FOUNDATION Fieldbus from PROFIBUS DP
If you separate the interface module for the FOUNDATION Fieldbus from PROFIBUS DP in
HW Config, this has the following effects:
● The bus system is orphaned with all FF devices.
● The FF devices and CiF interconnections will be retained.
● The addresses will be released.
● The interconnections between the FF and the automation system will be retained.
● This bus system is disregarded during compiling and downloading of the automation
system.
Changing interconnections - Impact on communication

● The FF device must be restarted when you change (device-internal) interconnections. The
FF device is not available during the restart period.
Connecting the separated FOUNDATION Fieldbus to an automation system (behind
PROFIBUS DP)
● When you connect an interface module for the FOUNDATION Fieldbus that was separated
from PROFIBUS DP to an automation system (behind PROFIBUS DP), observe the
following:
– Interconnections between the FOUNDATION Fieldbus and the automation system can
be restored.
– Address conflicts caused by interim configuration will be detected. A dialog box shows
options for resolving the address conflicts.
FOUNDATION Fieldbus
Engineering
5.2 Configuring
Deleting FF segment
● When you delete an FF segment in HW Config, observe the following:
– The FF segment and all FF devices configured there will be removed.
– The interconnections with the I/O blocks of the bus link will be removed.
Deleting blocks
● If you want to delete blocks in HW Config, observe the properties of the blocks in the section
"Block model of device parameters (Page 13)".
NOTICE
Deleting default blocks or instantiable blocks
The interconnections to these blocks are removed. Ensure that the desired function is
achieved in the process.
5.2.5 How to configure FF-internal interconnections (Control in the field)
Note
For information about required CiF interconnections, refer to the documentation of the device
manufacturer.
Requirements
● FF devices have been created in the project.
● The signals from the function blocks of the FF devices that you want to interconnect via
CiF are not locked.
Locked inputs or outputs

Inputs or outputs can be locked for the interconnection. Causes:
● The input or output is interconnected internally.
● An I/O address from the process image is already assigned in HW Config for the input or
output. You can find information on this in the section "How to replace an FF device
(Page 37)".
Example of the representation:

The symbol indicates a locked input.
FOUNDATION Fieldbus
Engineering
5.2 Configuring
Procedure
1. Open the configuration in HW Config.
2. Select the module of the bus link that implements the connection to PROFIBUS DP:
– For the Compact FF Link: IM 655-5 FF module
3. Select the SIMATIC PDM > Start Interconnection Editor menu command in the shortcut
menu.
The "Interconnection Editor" dialog opens.
You can find information about the symbols in the section ""Interconnection Editor" dialog
box (Page 35)".
4. Search for the following for each interconnection:
– In the "Outputs" tree view, search for the source of the interconnection
– In the "Input" tree view, search for the destination of the interconnection
5. Once you have selected an interconnection, click "Add interconnection".
The FF-internal interconnection is entered in the "Interconnection" column.
6. To create additional interconnections, repeat steps 4 and 5.
7. Click "Save".
The interconnections are saved in the project.
Delete interconnection
To delete an interconnection, select the desired line in the "Inputs and interconnections" list
and click the "Delete interconnection" button.
Download
The schedule for the FOUNDATION Fieldbus is calculated automatically during downloading
of the FF devices.
NOTICE
System changes during operation
When the connections between FF devices are changed, the CPU remains in RUN and the
communication on the FF segment goes to STOP.
● Online help for SIMATIC PDM
FOUNDATION Fieldbus
Engineering
5.2 Configuring
5.2.6 "Interconnection Editor" dialog box
Note
Menu command "Start Connection Editor"
The "Start Connection Editor" menu command is only enabled in HW Config for the bus link
(Compact FF Link) if the "PDM Foundation Fieldbus" license key is available.
You organize the interconnections for internal FOUNDATION Fieldbus communication in this
dialog. The automation system does not participate in this communication. The name of this
function is "Control in the Field" (CiF). CiF can be used to execute technological functions in
an FF segment.
Configure each CiF interconnection (hereafter referred to simply as interconnection) in the
"Connection Editor" dialog.
Internal device interconnections

FF devices have internal device blocks, such as measuring sensor, controller. The internal
device interconnection of these blocks means that there is no communication load on the FF
segment.
Structure
The "Connection Editor" dialog box is divided into the following columns:
"Inputs and interconnections" area
● "Input" column
This column shows the FF devices and the available inputs in the network view of the FF
segment. Inputs are the target of an interconnection.
● "Internal interconnection" column
This column displays a list of interconnections that were configured for the FF segment.
Layout: Output of the FF device > Function Block > Signal
"Outputs" area
● "Output" column
This column shows the FF devices in the network view of the FF segment and the available
outputs. Outputs are the source of an interconnection.
Buttons
Button Function
Add interconnec‐ Click this button to add an interconnection to the column "Interconnections".
tion
Delete intercon‐ Click this button to delete an interconnection.
nection
Close Click this button to close the dialog box.
A message informs you if changes have not yet been saved.
FOUNDATION Fieldbus
Engineering
5.2 Configuring
Button Function
Save Click this button to save configured interconnections in the SIMATIC project.
Download Click this button to open the CiF interconnection.
NOTICE!
Use this button only if no other changes have been made to the FF segment since
the last download of the device.
Icons
Icon Displayed object

FF segment
Bus link (Compact FF Link)
FF device
Block within an FF device
Inputs and outputs Status

Analog input Not interconnected
Analog input Interconnected
Digital input Not interconnected
Digital input Interconnected
Analog output Not interconnected
Analog output Interconnected
Digital output Not interconnected
Digital output Interconnected
Locked inputs or outputs

Inputs or outputs can be locked for the interconnection. Causes:
● The input or output is interconnected internally.
● An I/O address from the process image is already assigned in HW Config for the input or
output.
You can find information about this in the Process Control System PCS 7, FOUNDATION
Fieldbus documentation; section "How to replace an FF device".
Example of the representation:

The symbol indicates a locked input.
See also
How to configure FF-internal interconnections (Control in the field) (Page 33)
How to replace an FF device (Page 37)
FOUNDATION Fieldbus
Engineering
5.2 Configuring
5.2.7 Adding deleted default blocks
NOTICE
Re-commissioning of the FF device required
You should only perform the following steps if the system status permits this.
Requirements
● Default blocks of an FF device have been deleted and the configuration has been
downloaded to the FF device.
● Deleted default blocks are to be downloaded to the FF device again.
● An online connection to the FF device is possible.
Procedure
1. Open the device in SIMATIC PDM.
2. Select the resource block of the FF device.
3. Select the Device > Status menu command.
The "Status" dialog box opens.
4. In the "Restart" list, select the function that restores the original status of the FF device.
You can find information about this in the device-specific online help and information of the
device manufacturer.
NOTICE
Re-commissioning of the FF device required
Ensure that the state of the plant permits re-commissioning of the FF device.
5. Click "Transfer".
● Information of the device manufacturer
5.2.8 How to replace an FF device

During a device replacement, it may occur that you connect a device with an unknown device
address to the FF segment.
The device addresses are checked when FF devices are connected to an active FF segment.
In the case of an address conflict, the new FF devices causing the address conflict
automatically receive an address from the temporary range.
FOUNDATION Fieldbus
Engineering
5.3 Parameter assignment
Example:
You want to replace a defective FF device in process mode.
Recommendation:
Set the device address and the device parameters in a test environment before physically
connecting these FF devices to an active FF segment in process mode.
Requirements
● The FF device has been created in HW Config.
● The configuration for the FF device is complete.
● The FF device has been connected to the FF segment.
Procedure
1. Open SIMATIC Manager in the process device view.
2. Select a PDM object that contain the FF devices.
3. If you want to find an FF device with an unknown device address in the plant, select the
following command in SIMATIC Manager: Edit > SIMATIC PDM > Start LifeList.
4. When you find the desired device, do the following:
– Select the Device > Assign address and TAG menu command.
– Transfer the correct address and TAG to the FF device.
Note: Changing the address will restart the device.
– Download the configuration to the device.
5.3.1 How to assign parameters of the FF devices

You configure FF devices in PCS 7 systems with SIMATIC PDM.
Note
Device-specific menu commands and help in SIMATIC PDM
Device-specific menu commands and the Help for them are derived from the device description
assigned to the object. Device-specific information can be found in the online help and
documentation of the device manufacturer.
FOUNDATION Fieldbus
Engineering
Requirements
● SIMATIC PDM is installed together with the licenses.
● The device descriptions of the FF devices have been integrated.
● The FF devices have been created in the PCS 7 project.
● The Engineering Station has a communication connection with the FF devices.
Reading device data
Note
Default values are not entered for device data of the FF devices in EDD files.
Before you assign the parameters of the FF devices for the first time, you will have to read out
the device data directly from the FF device once.
1. Select the following object in HW Config:

– The FF device if you want to read the device data from one FF device.
– The bus link (Compact FF Link) if you want to read the device data from all FF devices.
2. Select the following menu command: Edit > SIMATIC PDM > Upload to PG/PC.
The "Upload to PG/PC" dialog opens.
3. Select one of the following options:
– If you want to read the device data of an FF device:
"Object with all subordinate objects" option.
– If you want to read the device data of all FF devices on the FF segment:
"Object with all subordinate objects and networks" option
4. Click "Start".
Procedure in SIMATIC PDM

1. Select an FF device in one of the following views:
– In SIMATIC Manager in HW Config
– In the Process device plant view
– In the process device network view
2. Double-click the FF device in HW Config, or select the Edit > Open object menu command
in the process device plant view or process device network view.
SIMATIC PDM starts.
FOUNDATION Fieldbus
Engineering
3. In the structure view, select the function block in which you want to change parameters and
make the desired changes in the parameter table.
4. Select the Station > Save menu command.
These changes are applied to the PCS 7 project.
Note
Offline parameter assignment data
SIMATIC PDM enables offline parameter assignment data to be downloaded to one or
more FF devices (download to devices) or enables device parameters to be uploaded from
the FF devices to the computer and saved on request (upload to PG/PC).
● Manufacturer information of the FF device.
● Online help for SIMATIC PDM
5.3.2 Bus parameters
Note
Changing bus parameters
Faultless operation of the components on the FF subsystem is only ensured if the parameters
for the bus profile are compatible with each other. You should therefore only change the default
values if you are familiar with parameter assignment of the bus profile for FF.
FOUNDATION Fieldbus
Engineering
The bus parameters can be set depending on the bus profile.

● Bus parameters that cannot be changed are grayed out.
● Bus parameters are displayed only as offline values, even if there is an online connection
to the target system.
The displayed parameters apply to the entire FF subsystem and are briefly explained below.
"System Management Timer" area

FOUNDATION Fieldbus is a clocked bus system.
Three timers (T1, T2, T3) are integrated in the System Management Information for monitoring
purposes. These timers are used to control the schedule on the FF segment; they ensure that
each FF device has sufficient time available for actions and data transmission.
In PCS 7, by default, timers T1 and T3 operate on the interface module (LAS).
FOUNDATION Fieldbus
Engineering
Timer T2 operates on the FF devices.
Bus parameters Setting range (default Meaning and limiting values

setting)
T1 - The parameter T1 specifies the number of clock cycles that an interface module
Inter Sequence (480 000 (or an LAS) waits for a response from an FF device.
Timer corresponds to approxi‐ If the set number of clock cycles is exceeded, the service for this FF device will
mately 15 s) terminate with an error message.
T2 Rule: T2 >= T3 + 3*T1 The parameter T2 specifies the number of clock cycles that is available to an
Set Addr Se‐ (host) FF device for actions and data transfer. Any unperformed actions and data
quence Timer (2880000 transmissions are cancelled.
corresponds to approxi‐ FF devices newly connected to the FF segment can only be detected if the value
mately 90 s) T2 is sufficiently dimensioned.
T3 - The parameter T3 corresponds to the number of clock cycles that are available
Set Addr Wait (1 440 000 as waiting time.
Timer corresponds to approxi‐ On expiration of this waiting time the interface module (or LAS) checks the FF
mately 45 s) devices that are recognized as new on the FF.
"Node Polling" area
Bus parameters Setting range (default Meaning and limiting values

setting)
First Unpolled 20 < FUN < 232 FirstUnpolledNodeId (FUN)
Node Default setting in SIMATIC PCS 7FUN = 36:
This parameter specifies the first device address that is not processed (not pol‐
led) by the LAS.
Number of Con‐ NUN = 232 - FUN NumConsecUnpolledNodeId (NUN)
secutive Unpol‐ Default setting: NUN = 232 - 36 = 196
led Node
Range of consecutive device addresses not in the polled range.
In SIMATIC PCS 7 (Unpolled Bereich):
Default setting of 36 - 231
"Other bus parameters" area

Select the option for setting the parameters:
● "Automatic calculation"
The bus parameters are automatically set on the basis of the current configuration.
● "Manual entry" option
You can change the following parameters for each specific system.
FOUNDATION Fieldbus
Engineering
Bus parameters Setting range (de‐ Meaning and limiting values

fault)
Slot Time 1 - 512 This parameter specifies how fast the FF device can reply upon receipt of a
(8) PDU. The required setting can be derived from the EDD of the FF devices.
Assign parameters to this value in such a way that the minimum value is
greater than the maximum Slot Time of every FF device on the FF segment.
ST >= ST of each FF device of the segment.
Per DLPDU PhL Over‐ 2 - 63 The parameter defines the delay between the following data records of a
head (2) connection to the FF segment:
● End of the last octet
● Beginning of the first octet of other data records
Maximum Response 1 - 11 This parameter specifies how fast the FF device can reply upon receipt of a
Delay (10) PDU. The required setting can be derived from the EDD of the FF devices.
● Determine requirement for each FF device:
MRD(FF device)=MRDST/ST
Assign parameters to this value in such a way that the minimum value is
greater than the ratio of Maximum Response Delay Slot Time and Slot Time
of every FF device on the FF segment.
● MRD(FF segment):
MRD >= MRD of each FF device of the segment
Minimum Inter DLPDU 0 - 120 This parameter specifies the minimum interval between two frames on the FF
Delay (16) segment. Each FF device has a minimum value of MinInterPDUDelay. This
value is stored in the EDD.
Assign parameters to this value in such a way that it corresponds to at least
the maximum value of Minimum inter DLPDU Delay of all the FF devices on
the FF segment.
Minimum inter DLPDU Delay (segment) > max Minimum inter DLPDU Delay
(FF device)
The minimum value for this parameter is determined by the maximum value
of all the FF devices in the FF segment.
Preamble Extension 0-7 Each data record of an FF connection starts with a preamble octet which is
(2) used by the FF devices (receiving nodes) for clock synchronization. The num‐
ber of preambles (s) can be extended when setting this parameter. The default
value in PCS 7 is 2. Higher values may be required in networks with repeaters.
Time Sync Class 0-7 This parameter defines the quality of the clock accuracy of an FF device. Thus
(4) it also defines the periods for time synchronization of an FF device.
The maximum value supported by an FF device is stored in the EDD.
Set this value to the lowest common class of all FF devices on the FF segment
(slowest time).
The value 4 corresponds to 1 ms.
FOUNDATION Fieldbus
Engineering

fault)
Maximum Scheduling 16 This parameter extends the time that may be used by the LAS for processing
Overhead the schedule. The parameters unit is the transmission duration of one octet.
The following times should be included in the duration:
● The time allocated for each scheduled activity
● The time to determine whether a device on the FF segment can serve as
an LAS.
● The time for the organization of the schedule.
The parameter will be checked based on the value configured in the LAS
during downloading of the FF segment.
of all the LAS-capable devices in the FF segment.
Max Inter Chan Signal 0-7 This parameter indicates the maximum permitted time offset of the data that
Skew (0) a device receives from several ports (redundant routes) via an H1 connection.
Select a value between 0 and 7 4-bit transmission times.
The value range is (0 .. 7) * 4 * Tb.
Post Trans Gap Exten‐ 0 - 7 There will be an interruption of the signal transmission in 4-bit transmission
sion (0) times after each transmission.
Use this parameter to increase this interruption in signal transmission by ad‐
ditional 4-bit transmission times. The value range is (0 .. 7) * 4 * Tb.
A value greater than 0 increases PerDlpduPhlOverhead.
Default Minimum To‐ 32 - 32767 The time required for an FF device to process all tasks. The parameters unit
ken Delegation Time (86) is the transmission duration of one octet.
Keeping to the schedule (controlled by LAS ) has the highest priority on the
FF. The time available for an FF device should be sufficiently dimensioned
(greater than Default Token Holding Time).
An FF device can only be processed if it keeps the token for longer than
stipulated by the "Default Minimum Token Delegation Time" parameter.
Default Token Holding 276 - 65000 Time period assigned to an FF device by the LAS for the following tasks:
Time (276) ● acyclic bus traffic
● System Management
● Alarms and events
Target Token Rotation 1 - 60000 Within this time all FF devices must have received the token for acyclic data
Time (60000) transfer once. If the actual token rotation time is higher than the configured
value for Target Token Rotation Time, the LAS will increase the token priority.
A Target Token Rotation Time value that is too small causes the failure of low-
priority services. The following are low-priority services:
● System Management
● acyclic bus traffic (client-server connections)
Link Maintenance To‐ 292 - 65000 Period of time which the LAS uses within a token rotation for checking a link.
ken Holding Time (336) This time period contains the following processes:
● find new FF devices
● send LAS status telegrams
Time Distribution Peri‐ 10 - 55000 Time period for forwarding time service telegrams (in milliseconds)
od (5000) Time distribution PDU's will be sent on the bus in 95% or less of that time
period.
FOUNDATION Fieldbus
Engineering

fault)
Maximum Inactivity to 1 - 4095 Delay time (device-internal)
claim LAS Delay (100) Time which an LAS-capable FF device needs from the detection of the failure
of the LAS until a request is sent for takeover of the LAS (ClaimLAS).
of all the LAS-capable FF devices in the FF segment.
LAS Database Distri‐ 100 - 55000 Time period for distribution of the LAS database (in milliseconds)
bution Period (5000) This time period covers the times for the following processes:
● Establishment of the connection to LAS-capable FF devices in the FF
segment
● Distribution of the LAS database to FF devices in the FF segment
Recommendation: Set a value between 1000 and 5000.
Ap Clock Sync Interval 0..255 "Application Clock Synchronisation Interval" is a specific parameter for devi‐
(10) ces that can execute this time synchronization (date and time) on the FF
segment. It is not necessary that this device is LAS on the FF segment. Only
one device may actively perform time synchronization on the FF segment.
Set the parameter according to the specifications of the device manufacturer.
Start-up time 20 s Time period for start-up of all devices on the FF segment (in seconds)
Selection: 20 to 180 seconds (levels: every 20 seconds)
Stale Count Limit 0 - 255 Maximum number of failed communication attempts
(3) When the value is exceeded, the device in question terminates communica‐
tion with the FF segment.
0: Checking is turned off in the device.
5.3.3 How to assign bus parameters

Settings of the FOUNDATION Fieldbus are assigned in PCS 7 systems using HW Config or
NetPro.
The necessary bus parameters can be determined automatically or set individually. Set the
bus parameters using the "Properties - FOUNDATION Fieldbus" dialog box.
Meaning of the S7 subnet ID

The S7 subnet ID comprises two numbers separated by a hyphen:
● Number for the project
● Number for the subnet
If you want to go online with a PG/PC without a consistent project, you must know the S7
subnet ID. When you print the network configuration, the S7 subnet ID will also be printed.
FOUNDATION Fieldbus
Engineering
Connecting a link master (LAS) to an active FF segment

Before you connect a field device or the bus link (Compact FF Link), assign the bus parameters
in a separate action.
Note
Compact FF Link
When the Compact FF Link is used, it is not possible for the field devices to take over the LAS
function.
Requirements
● The FF devices have been created in the PCS 7 project.
● Interconnections via the FF have been configured.
Procedure
1. Select the FOUNDATION Fieldbus in the SIMATIC Manager in HW Config.
2. Select the Edit > Object Properties menu command.
The "FF subsystem properties" dialog box opens.
3. Set the FF subsystem number of the FF segment, if required.
Modifications are usually not necessary.
4. Click "Properties...".
The "Properties - Foundation Fieldbus" dialog box opens.
5. Select the "Bus parameter" tab. Make the settings.
You can find information about this in the section "Bus parameters (Page 40)".
Note
Identification of all FF devices on the FF segment
Set the value "First Unpolled Node" to 232 (default = 36).
● For performance reasons, no addresses in the address range 36 to 231 should be
assigned to FF devices in a system.
● Following a scan of the "Unpolled Bereiches", you should set the default value (36) again.
6. Select the File > Save command.

The changes are saved to the PCS 7 project.
Field device as Link Master

If field devices are to be used as Link Master , the following settings are necessary:
● Slot Time > 13
● Bus address of the field device (Link Master) > 32
FOUNDATION Fieldbus
Engineering
Schedule calculation canceled

If the schedule calculation could not be completed successfully, you receive an error message.
Check the settings of the bus parameters.
Note
Error message "Cancel Schedule Calculation: Error at bus parameter"
The error message "Cancel Schedule Calculation: Error at bus parameter" is issued by
SIMATIC PDM if there are too many configured interconnections.
You can find additional information about this in the section "Additional notes on
configuration (Page 32)".
Checking the bus parameters

1. In the "Properties - Foundation Fieldbus" dialog box, select the "Bus parameters" tab.
2. In the "Bus parameters" area, select the "Automatic calculation" radio button.
The default values are set.
3. Switch to the "Macro cycle" tab.
4. Click "Calculate Schedule".
If your bus parameters deviate from the default values, you can adapt the values in the
input boxes ("Acyclical percentage" and "Macro cycle").
Run the schedule calculation every time you make a change.
Requirements for downloading

First, configure all interconnections.
If you have inserted new FF devices in the FF segment or want to use new parameters, online
changes are not possible.
If necessary, correct the macro cycle settings.
5.3.4 How to plan the macrocycle

A macrocycle lasts for a number of bus clock cycles. The duration of the cyclic communication
depends on the configured hardware. You can define the time for a macrocycle and the
percentage of acyclic communication. The FF specification recommends that at least 50% of
the bus time be kept free for acyclic communication.
For additional information, refer to the section "Nodes in the FOUNDATION Fieldbus
(Page 19)".
"Macrocycle" tab
Whether the configuration is consistent is determined on the basis of the output values and
the required interconnections. The result is displayed graphically.
FOUNDATION Fieldbus
Engineering
"Calculate Schedule" button"

● Click this button to calculate the time for cyclic communication.
"Optimize macrocycle" button
● Click this button to set the macrocycle as follows:
Depending on the cyclical component (depending on the configured hardware), a minimum
macrocycle is set with a specified acyclical percentage.
Graphical display
Before downloading, click the "Calculate schedule" button. With the help of the display you
can check whether the configuration is consistent. The result is displayed graphically.
Display from left to right:
Left area
The colored area on the left side indicates the percentage of acyclic communication.
Left thin dividing line (50% of the bus load)
The lower limit of the percentage of acyclic communication of the bus load recommended in
the FF specifications.
Thick dividing line
The limiting value set in the entry field "Percentage of acyclic communication".
Right thin dividing line (70% of the bus load)
The upper limit of the percentage of acyclic communication of the bus load recommended in
the FF specifications.
Right area
The colored area on the right side indicates the percentage of cyclic communication.
Meaning of the colored areas
Color Meaning Recommendation/notes

Yellow Percentage of acyclic communication -
Dark green Percentage of cyclic communication -
Configuration is free from errors.
Light green and dark Configuration is free from errors. You can reduce the time for the mac‐
green The cyclic communication portion is rocycle of a specified acyclic portion.
shown in dark green.
The light green portion identifies the
time that is reserved for cyclic commu‐
nication but is not needed.
FOUNDATION Fieldbus
Engineering
Color Meaning Recommendation/notes

Amber Downloading the configuration with the Change the value marked in orange to
selected settings results in a high bus modify the configuration in accord‐
load. ance with the recommendations of the
Fieldbus Foundation.
Note
Restrictions to acyclic communication
are possible.
Red Downloading the configuration with the Change the value marked in red to
selected settings results in a very high modify the configuration in accord‐
bus load. ance with the recommendations of the
Fieldbus Foundation.
Note
Errors during acyclic communication
are possible. This configuration can‐
not be downloaded.
Setting the macrocycle

1. Select the FOUNDATION Fieldbus in the SIMATIC Manager in HW Config.
The "FF subsystem properties" dialog box opens.
3. Set the FF subsystem number of the FF segment, if required.
Modifications are usually not necessary.
4. Click "Properties...".
The "Properties - Foundation Fieldbus" dialog box opens.
5. Open the "Macrocycle" tab.
6. Enter the system-specific settings.
7. Click "Calculate Schedule".
This step checks the consistency of the set parameters. The result is displayed graphically.
8. Select the Station > Save command.
The changes are saved to the PCS 7 project.
Adapting the macrocycle
Note
An adaptation of the macrocycle requires a STOP of the FF segment.
If an adaptation of the macrocycle is needed after the downloading all FF devices, then all FF
devices must be downloaded again. Observe the following especially after the following actions:
● Adding FF devices
● Adding new interconnections with the Interconnection Editor
FOUNDATION Fieldbus
Engineering
5.4 Using the applications
● Using new connections via the CPU

● Using new I/O data
Recommendation for commissioning

Configure a CiR object and a sufficiently long macrocycle at the FF segment.
Calculate schedule
To calculate the schedule, click the "Calculate schedule" button on the "Macrocycle" tab of the
"Properties - Foundation Fieldbus" dialog.
The schedule is automatically calculated when you download the configuration.
Including device-internal blocks

The following blocks are considered when diagnosing FF devices:
● Interconnected function blocks
● Resource block
● Transducer blocks
Only interconnected function blocks are processed and included in the schedule calculation.
Changes made with SIMATIC PDM become effective only for interconnected function blocks.
5.4.1 Overview
In HW Config you have reproduced the configuration of the FF segment in the system.
Interconnect the signals of the function blocks individually for FF devices. The created symbolic
names facilitate further configuration.
Create the charts for the automation system in CFC.
In order for the signals to be available on the operator station, interconnect the signals to
technological blocks.
You can then commission them. After the compiling and downloading of all components, the
functions of the FF devices are available on the operator station.
FOUNDATION Fieldbus
Engineering
5.4.2 Identifying FF devices with SIMATIC PDM

You can obtain the following information about an FF segment with the LifeList of SIMATIC
PDM:
● Which FF devices are connected to the FF segment and are available?
● What is the status of the FF devices?
● What addresses and names were assigned for FF devices?
Note
Devices with different capability level
The capability level cannot be determined from the device information. If you are using FF
devices for which multiple capability levels are available in the device catalog, you must select
the capability level when the FF device is first opened.
Requirements
● SIMATIC PDM including the required license keys is installed on a computer.
● The computer is connected to an automation system.
● There is a communication connection between the automation system and the FF segment.
● A project with field devices is available on the computer.
Starting LifeList
If the project is open in SIMATIC Manager, you can start the LifeList from the following views:
● Starting from HW Config
– Select a PDM object containing the field devices.
– Select the SIMATIC PDM > Start LifeList command in the shortcut menu.
SIMATIC PDM starts. The LifeList is opened.
● Starting from the process device network view
– Select a PDM object containing the field devices.
– Select the Edit > SIMATIC PDM > Start LifeList menu command.
● Starting from SIMATIC PDM
– Requirement: A PDM object containing the field devices is selected.
– To open the LifeList , select the View > Start LifeList menu command.
FOUNDATION Fieldbus
Engineering
Note
Status
If the data has not been updated, you will observe the following:
● The tree view has been deleted and will be rebuilt.
● The symbols will change.
After the network scan, all detected FF devices are displayed in the table. The TAG (name) is
depicted in the tree structure. Additional columns show, for example, the following data of the
FF device:
● Address
● Manufacturer
● Device type
● Device ID
● Hardware revision
● Software revision
The "Start Scan" function is used to start a new scan operation.
Setting the address range for scan operation

When the LifeList is opened, the scan range is set to the complete address range according
to the protocol of the network on which the LifeList was started.
Address range for FF: Address 20 to 251
Recommendation:
Limit the address range for the scan operation.
A scan operation across a large address range takes longer.
The address range is set via the toolbar or via the "Settings" dialog in the "Options" menu.
This setting cannot be stored centrally since it is network-specific. The setting must be made
again each time the LifeList is opened.
Stopping LifeList
When the LifeList is open, click "Close".
Online help for SIMATIC PDM
FOUNDATION Fieldbus
Engineering
5.4.3 Specifying the device identification of the FF devices (TAG name and address)
With SIMATIC PDM, you can use the Start LifeList menu command to find the FF devices that
are connected to the FF segment. Use the "Assign address and TAG..." button to change the
following parameters for device identification:
● Address (device address).
● TAG (device designation in the system).
Use this procedure, for example, to detect a connected backup device after replacement of a
device. Then, assign the parameters for device identification to this FF device.
Requirements
● FF devices have been created.
● An online connection to the FF segment is possible.
● The bus parameters may be set in such a way that all addresses are in the "polled range"
(FUN = 232).
Note
Unpolled range
In SIMATIC PCS 7, the FF devices with addresses from 36 to 231 are not processed by
default (unpolled range). This range can be reduced by changing the bus parameters.
You can find information about this in the section "How to assign bus parameters
(Page 45)".
Procedure
Note
Restart
Changing the address will restart the device.
1. Open the project in the process devices network view.

2. Open the network view of the automation system.
3. Select the bus link of the FF segment in the tree view.
4. Select the shortcut menu command Open Object.
The "SIMATIC PDM" dialog box opens.
5. Select the bus link.
6. Select the menu command View > Start LifeList .
The "LifeList" dialog window opens.
FOUNDATION Fieldbus
Engineering
7. Select one of the following functions:

– Start Scan
– Start Scan with diagnostics
The accessible devices of the network on which the LifeList was started are determined.
All detected FF devices are displayed in the table.
You can find additional information about these functions in the online help of SIMATIC
PDM.
8. Select the FF device (replacement device) in the tree view.
9. Click the "Assign address and TAG ..." button.
Input boxes for the current and new parameters are displayed in the dialog.
10.Enter the current and new address and the current and new device designation (TAG) of
the FF device in the system configuration.
11.Click "Transfer".
Note
Address or TAG assigned
If the address or TAG is assigned, then the action will not be performed. An appropriate
message will be displayed.
LifeList
The changes to the parameters for device identification are only online changes.
Changes are not applied to the PCS 7 project.
Example:
You have moved an FF device in the LifeList from address 25 to address 30 . The configuration
is only consistent if the FF device also has address 30 in HW Config.
Download
To ensure that all configured parameters and connections are available for the FF device, the
FF device must be downloaded.
5.4.4 Editing symbols (symbolic names)

You can easily adapt the symbolic names and comments for signals.
Requirements
Symbolic names were assigned for the inputs and outputs during configuration of the FF
devices.
FOUNDATION Fieldbus
Engineering
Procedure
1. Open the project in the component view of SIMATIC Manager.
2. Select the "ProjectAS" > "CPU" > "S7 Program" folder in the tree view.
3. Select the "Symbols" object in the list.
4. Select the Edit > Open Object menu command.
The "Symbol Editor" dialog box opens.
5. Make your changes.
Note
A maximum of 24 characters is permitted for a symbol.
Example: Symbol = "Status_Measurement"
6. Select the Table > Save menu command.
5.4.5 Configuring interconnections to the FF devices

PCS 7 supports you during the configuration of FF devices by providing prepared templates
for different functions. In the CFC Editor, you will find the templates in catalog > "Libraries" >
tab, folder "PCS 7 AP Library V..."\Blocks+Templates\Templates.
You can find information about this in the context-sensitive help for the templates and in the
Process Control System PCS 7; Advanced Process Library documentation.
Channel blocks for FF devices

Use the channel blocks of the PCS 7 Advanced Process Library (APL) to interconnect the
signals of FF devices.
Use one channel block for each I/O address.
Block type Address range Block name Function block Block I/O
Analog Input FbAnIn FB 1813 PV
Output FbAnOu FB 1814 SP
Digital Input FbDiIn FB 1815 PV
Output FbDiOu FB 1816 SP
Requirements
● FF devices have been configured.
● Symbols have been created.
FOUNDATION Fieldbus
Engineering
Procedure
You have the following options for configuring interconnections:
● Configure the interconnections in the PCS 7 Import/Export Assistant using templates.
● Create your own CFC charts.
You can find additional information and step-by-step instructions in the configuration manual
Process Control System PCS 7; Engineering System.
5.4.6 Configuring the operator station

Information about the configuration of process pictures and diagnostics with operator stations
is available in the Process Control System PCS 7; Operator Station Configuration Manual.
FOUNDATION Fieldbus
Commissioning 6
Commissioning begins with the connecting and the downloading of the hardware. You then
perform the connection and function test. Finally, the system is optimized.
Values have to be simulated for some tasks. Information that supports you in these tasks can
be found below.
Refer to the device-specific documentation for information on connecting the FF devices.
6.1 Compile and download
6.1.1 Introduction
In a PCS 7 system you compile and download the entire program of the process control system
with the engineering station.
Compiling
You access the central function for compiling and downloading in SIMATIC Manager via the
PLC > Compile and Download Objects... menu command.
Compiling and downloading the AS

The following options are available for compiling and downloading programs:
● You can run the functions for a single SIMATIC station.
● You can compile and download multiple SIMATIC stations using a single function.
● You download the device parameters independently of the AS.
You can find information on this in the section "Downloading objects in the FF segment
(Page 58)".
Compiling and downloading the OS

The following options are available for compiling and downloading the operator station(s):
● You can individually compile and individually download an operator station.
● You can simultaneously compile multiple operator stations and download them individually.
● You can simultaneously compile and download multiple operator stations.
FOUNDATION Fieldbus
Commissioning
You can find additional information and detailed step-by-step instructions in the following
documentation:
● Configuration manual Process Control System PCS 7; Engineering System
● Configuration Manual Process Control System PCS 7; Operator Station
6.1.2 Downloading objects in the FF segment

You have to download the following data for the function of the FF devices in a system:
● CPU data
– Hardware configuration of a CPU with connected FF segment (to the CPU)
– Program and connections (to the CPU)
● Schedule, bus parameters and interconnections (to the FF segment)
● Device parameters (to all FF devices)
Note
Downloading function blocks
It is not necessary to download an entire device if there are only minor changes.
You can download a group of function blocks or one individual function block for an FF device.
Replacing devices
You have the following options for replacing devices with SIMATIC PDM:
● Replacement of a device with one of the same type
● Replacing a device with a similar one
FOUNDATION Fieldbus
Commissioning
Requirements
You will have to read in the device parameters to the Engineering System before you assign
the parameters of the FF devices for the first time.
Note
Observe the following if you have inserted new FF devices on the FF segment or if you want
to use the parameters of additional function blocks:
● First, configure all interconnections.
● If the complete FF segment is loaded (option for bus link: "Always load FF devices"), loading
is briefly stopped.
● If the FF segment is being loaded incrementally (option for bus link: "Only load FF devices
when modified"), the loading continues.
● If necessary, correct the macro cycle settings.
Download
Use the following menu commands to download the respective data to the system:
Menu command CPU data Schedule, bus parameters and intercon‐ Device pa‐
nections rameters
Always download the hardware configuration Hardware con‐ Downloading -
in HW Config for the selected CPU: figuration is Note:
PLC > Download to Module downloaded Downloading FF segments can only be
carried out via HW Config.
The menu command PLC > Compile and Down‐ Program and - -
load Objects... in the SIMATIC Manager. connections
are downloa‐
ded
Select the bus link in SIMATIC PDM Device > - - All FF devi‐
Download to device ces are down‐
Select the following check box in the "Down‐ loaded.
load to device" dialog:
"Object with all subordinate objects and net‐
works".
Select the bus link in SIMATIC PDM Device > - - The FF de‐
Download to device Only when replacing a device with one of vice is loaded
Select the following check box in the "Down‐ the same type:
load to device" dialog: Select the check box "Load Schedule to
"Object with all subordinate objects". Device".
Note
You can download changes to the automation system in "RUN" mode.
Read the following paragraph: Settings for "Load FF Segment"
FOUNDATION Fieldbus
Commissioning
Settings for "Load FF segment"

In HW Config, you can adapt the object properties of the bus link that are taken into
consideration when loading the AS.
Perform the following steps:
1. Open the hardware configuration in SIMATIC Manager.
2. Open the object properties of the bus link.
3. Select the "Load FF Segment" tab.
4. Make the settings in accordance with the following table:
Note
Bus link - downloading changes after the "Calculate schedule" action
If you have configured the setting "Only load FF devices when modified" in the bus link,
you must observe the following:
● Only a complete download is possible after executing the action "Calculate Schedule"
in "Properties - Foundation Fieldbus -> Macro cycle".
● A complete download is made possible by changing the bus link parameter assignment
to "Always load FF devices".
Check box Application Effect

Only load FF de‐ Exclude FF segment during If only changes are downloaded, the FF segment
vices when AS loading continues running during loading.
modified Example: You configure no
changes for the FF seg‐
ment.
Always load FF Complete download of an The FF segment is stopped when it is downloaded
devices FF segment completely.
Recommendation
After a complete download of an FF segment, se‐
lect the option "Only load FF devices when modi‐
fied".
Exclude FF devi‐ Function for commissioning This function supports you during commissioning
ces from loading only of other bus links on the same PROFIBUS.
NOTICE!
STOP of the FF segment possible
Undefined states may occur in the FF segment
when you use this setting.
Section "How to assign parameters of the FF devices (Page 38)".
Section "System changes during operation (Page 66)"
FOUNDATION Fieldbus
Commissioning
6.2 Diagnostics
6.2 Diagnostics
Diagnostics for the FF in PCS 7

PCS 7 uses graduated diagnostics.
With the Maintenance Station

● Status overview and status messages for bus link and FF devices
● Detailed diagnostics for bus link and FF devices with SIMATIC PDM
● Configured maintenance information
In SIMATIC Manager
● Status overview for bus link and FF devices
In HW Config
● Status overview for bus link and FF devices
With SIMATIC PDM

● Detailed diagnostics for bus link and FF devices
● Use of the "Mode" dialog box only for FF devices
● Use of "Status" dialog box only for FF devices
LED displays on the bus link

● Status of FF
Displays on the FF devices
● Read the device manufacturer information on this.
● Configuration Manual Process Control System PCS 7; Operator Station
● Section "Identifying FF devices with SIMATIC PDM (Page 51)"
● FF devices documentation
6.2.1 "Modes" and "Status" menu commands

You can find the "Modes" and "Status" menu commands for blocks of FF devices in the
"Device" menu in SIMATIC PDM. You use these menu commands to open dialog boxes that
support you in the commissioning of FF devices. Since these dialogs are specific to the
respective FF device, only general information is provided here.
For detailed information, refer to the online help dialog.
FOUNDATION Fieldbus
Commissioning
6.2 Diagnostics
"Modes" dialog box

This dialog box shows information about a block of an FF device.
You can change the current settings for the block if the FF device and current settings permit
this:
Object "Modes" menu command selected for "Modes" menu command selected for
FF device a block
Block list Setting can be configured: Not available
The "Block" list shows the currently
selected block of the FF device.
Select the block of the FF device in
the list.
Current block mode Shows the current block mode for the Shows the current block mode for the
block of the FF device. block of the FF device.
Target block mode Setting can be configured: Setting can be configured:
You can set the block mode that the You can set the block mode that the
block should assume after the setting block should assume after the setting
is transferred to the FF device. is transferred to the FF device.
Allowed block mode Setting can be configured: Shows the currently permissible block
You can set the block mode that the mode for the block of the FF device.
block may assume after the setting is
transferred to the FF device.
Normal mode block Setting can be configured: Shows the block mode that the block
mode You can set the block mode that the should assume after the schedule
block should assume after the sched‐ download.
ule download.
Note:
The selected setting must always be
included in the "Allowed block mode".
Error block mode Not available Indicates current errors in the FF de‐
vice.
Note
Possible block modes
There may be dependencies between the blocks of the device.
Example:
Settings for the resource block often prevent settings for other blocks.
"Status" dialog box

In this dialog box, you can perform the following actions for the resource block of the FF device:
● Retrieve status information
● Enable/disable status information
FOUNDATION Fieldbus
Commissioning
6.2 Diagnostics
● Simulate status information

● Run restart functions
NOTICE
Restart functions
Read the device manufacturer information on this.
6.2.2 Performing diagnostics

An example of diagnostics in the SIMATIC Manager and detailed diagnostics with SIMATIC
PDM is shown below.
Requirements
● FF devices have been created
● An online connection to the FF device can be established
Diagnostics in the SIMATIC Manager

1. In SIMATIC Manager, open the project in the process device network view.
The "<Device name> – Properties" dialog box opens.
4. Open the "Diagnostics" tab.
5. Click the "Update Diagnostics" button.
An attempt is made to establish a connection to the FF device. The status of the FF device
is determined and displayed. The following information on FF device communication is
displayed:
– Communication
– Device status
– Last check
– Message text
Note
Offline status
The last updated status of the FF devices are shown in the following views in SIMATIC
Manager:
● Process device network view
● Process device plant view
FOUNDATION Fieldbus
Commissioning
6.2 Diagnostics
Detailed diagnostics with SIMATIC PDM

1. Select one of the following views:
– Process device network view
– Process device plant view
3. Select the Edit > Open Object menu command.
The "SIMATIC PDM" dialog box opens.
4. Select the Diagnostics > Update diagnostics menu command.
An attempt is made to establish an online connection to the FF device.
The diagnostics status of the selected object is updated.
For more information, refer to the SIMATIC PDM online help.
FOUNDATION Fieldbus
Redundancy and system changes during operation 7
7.1 Redundancy
The basic configuration of redundant FF segments corresponds to the configuration for
PROFIBUS PA.
● Connection to a redundant DP master system is required for operation with Compact FF
Link at a SIMATIC S7-400H.
Configuration with active field distributors enables the following connections of the FF segment
to a bus link:
● Ring redundancy with active field distributor (AFD)
● Coupler redundancy with active field splitter (AFS)
Assembling the bus link

● Ensure you use the correct type-specific bus module for the installation:
– Bus module for Compact FF Link
● Possible redundant components on the FF segment:
Type of bus link Component of the bus link which is connected to the FF segment:
Compact FF Link Compact FF Link (IM 655)
● When setting up redundant operation (ring redundancy and coupler redundancy) ensure
that the following is the same at the components of every single bus link pair:
– Article number of the respectively redundant component
– Hardware version of the respectively redundant component
– Firmware version of the respectively redundant component
● Connect the following module to the DP master system in Rack 0 of the SIMATIC S7-400H:
– The left Compact FF Link of the bus link.
Additional information can be found in the following documents:
● Product overview Process Control System PCS 7; Released Modules
● SIMATIC; Process Control System PCS 7; High Availability Process Control Systems;
section "Redundant PROFIBUS PA".
FOUNDATION Fieldbus
Redundancy and system changes during operation
7.2 System changes during operation
Configuring
You configure the following:
● Bus link on PROFIBUS DP
During configuration, the couplers for the FF segment are always part of the bus link.
● FF devices on FF segment (FF subsystem in HW Config)
The necessary configuration steps are described in section "How to prepare a FOUNDATION
Fieldbus for FF devices (Page 25)".
S7-400H as DP master
The following AS components operate as DP master:
● CP 443-5 ext.
● PROFIBUS DP connection of the CPU
The following requirements are met for the DP master systems:
● The DP masters process the same user program.
● The DP masters have the same parameter assignment and configuration for the interface
modules.
● You can find more information on redundant design of the PROFIBUS PA in the
documentation SIMATIC; Process Control System PCS 7; High Availability Process Control
Systems chapter "Redundant PROFIBUS PA".
● You can find information on the hardware design of the FOUNDATION Fieldbus in the
following documentation:
– Operating Instructions SIMATIC; Bus Link; Compact FF Link
● Information regarding the configuration of the redundant fieldbus with AFD/AFS can be
found in the following documentation:
SIMATIC; Bus Links; DP/PA Coupler, Active Field Distributors, DP/PA-Link and Y-Link

The following changes are possible:
● Changing the DP master system
● Changing parameters in FF devices
● Inserting or removing entire FF segments
● Inserting or removing FF devices
Observe the rules for modifying the system during operation using CiR.
FOUNDATION Fieldbus
Making changes during operation

In the case of the following actions, the CPU remains in RUN and communication on the FF
segment goes to STOP:
● Changing interconnections between FF devices (Page 33)
● Changing of bus parameters (Page 31)
NOTICE
STOP of CPU required
A STOP of the CPU is required if you insert a new address in HW Config for an FF device
that is configured and downloaded in the system.
Remedy:
1. Remove the device from the configuration.
2. Load the configuration.
3. Configure the device again.
4. Load the configuration.
Information about the sequence of this system modification and the requirements that must
be met can be found in the documentation SIMATIC; Modifying the System during Operation
via CiR.
FOUNDATION Fieldbus
FOUNDATION Fieldbus
Index
Function blocks, 14
A
Address, 53
H
HW Config, 15
Start Connection Editor, 35
B
Block
Function block, 14
I
Resource block, 14 Insert
Transducer block, 14 FF device, 28
Block model Integrate, 53
Objects, 15 Field device in SIMATIC PDM, 53
Block types, 14 PROFIBUS device in SIMATIC PDM, 23, 27
C L
Capability level, 15, 28 Load FF segment
Change Tab, 60
Download, 60
CiF
Configuring, 34 M
CiF interconnections, 29
Multiple capability levels, 15
Configuration via PDM, 26
Connection Editor, 34
Starting, 35
N
Name, 53
D
Device catalog, 15
Device description, 15
O
Download, 59 Option
Change, 60 Configuration via PDM, 26
Downloading changes, 60
Downloading changes, 60
P
PROFIBUS device in SIMATIC PDM, 27
F Integrate, 23, 27
FF device Publisher, 9
CIF interconnections, 29
I/O range, 29
Insert, 28 R
Object properties, 30
Resource block, 14
Setting name, 27
Field device in SIMATIC PDM
Integrate, 53
Function block, 14
FOUNDATION Fieldbus
Index
S
Schedule, 9
SIMATIC Manager
SIMATIC PDM, 15
Integrate field device, 53
Integrating a PROFIBUS device, 23, 27
Subscriber, 9
T
Tab
Load FF segment, 59
TAG, 53
Transducer block, 14
Transducer blocks, 14
FOUNDATION Fieldbus

PCS 7 FoundationFieldbus en en-US

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PCS 7 FoundationFieldbus en en-US

Uploaded by

Copyright:

Available Formats

Security information 1

Valid for the Process Control System software

Siemens AG A5E39550932-AB Copyright © Siemens AG 2017.

6.1.2 Downloading objects in the FF segment................................................................................58

Examples for configuration of FF segments in PCS 7

SIMATIC PCS 7 supports the connection of FF devices

Basic knowledge required

Information for FF users

Changes compared to previous versions

The most important distinctions between PROFIBUS PA and FOUNDATION Fieldbus

Communication with the automation system

Terms used for FOUNDATION Fieldbus (FF)

Publisher and Subscriber

Client and Server

Schedule and LAS (Link Active Scheduler)

3.1 Device integration with EDD

Standardized device descriptions

Information in device descriptions

3.2 Device addresses

Address ranges in PCS 7

Address range Information on the address range

Address range Information on the address range

Automatic address conflict resolution for device addresses

3.3 Block model of device parameters

Block type Note

Block designation Function

Examples of this are:

Multiple capability levels

Block types in HW Config and in SIMATIC PDM

Property Permanent blocks Default blocks Instantiable blocks

Objects of the block model

Operator stations and Maintenance Station

3.4 Capability levels (device variants)

Common features and differences based on capability level

Selecting the capability level in the device catalogs

Configuring the capability level

Communication and downloading of FF devices with capability level

3.5 Contact partner

Your contact partner (not for demo version)

Mailing address: SIEMENS AG

Questions on devices and GSD files

Size of the process image

The permissible current consumption of all components on an FF segment depends on the

CPU type As of version

Number of spur lines Permissible length of a spur line (length in meters)

SIMATIC Fieldbus Calculator

5.1.1 How to integrate a device description

6. Select the Catalog > Integration... menu command.

5.2.1 How to prepare a FOUNDATION Fieldbus for FF devices

Recommendation for using symbolic names

Bus link with FOUNDATION Fieldbus: Create FF subsystem

5. Optional steps for redundant FOUNDATION Fieldbus:

Step Compact FF Link (IM 655-5 FF)

5.2.2 How to place FF devices on the FOUNDATION Fieldbus

Setting/changing the device name for an FF device

Insert an FF device and assign the address on the FF segment

3. Drag-and-drop the required FF device to FF subsystem.

– In the shortcut menu, select the menu command Assign Address.

Specifying the device name and object properties

5.2.3 Checking the bus parameters

Changing bus parameters: NO

Changing bus parameters: YES

5.2.4 Additional notes on configuration