PCS 7 FoundationFieldbus en en-US

Introduction 1
Basics of the FOUNDATION

Fieldbus 2
System planning 3
SIMATIC
Engineering 4
Process Control System PCS 7
FOUNDATION Fieldbus
Commissioning 5
Redundancy and system
changes during operation 6
Commissioning Manual
Valid for the SIMATIC PCS 7 Process Control System

software package as of V8.1 including SIMATIC PDM
V8.2
11/2014
A5E32711026-AA
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 A5E32711026-AA Copyright © Siemens AG 2014.

Industry Sector Ⓟ 09/2014 Subject to change All rights reserved
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents
1 Introduction...................................................................................................................................................5
2 Basics of the FOUNDATION Fieldbus..........................................................................................................7
2.1 Device integration with EDD....................................................................................................9
2.2 Device addresses...................................................................................................................11
2.3 Block model of device parameters.........................................................................................13
2.4 Capability levels (device variants)..........................................................................................16
2.5 Contact partner......................................................................................................................18
3 System planning.........................................................................................................................................19
3.1 Nodes in the FOUNDATION Fieldbus....................................................................................19
3.2 Configuration..........................................................................................................................21
4 Engineering................................................................................................................................................23
4.1 Prepare..................................................................................................................................24
4.1.1 How to integrate a device description....................................................................................24
4.2 Configuring.............................................................................................................................25
4.2.1 How to place FF devices on the FOUNDATION Fieldbus.....................................................25
4.2.2 Additional notes on configuration...........................................................................................30
4.2.3 How to assign addresses for FF device signals.....................................................................32
4.2.4 How to configure FF-internal interconnections (Control in the field)......................................33
4.2.5 “Interconnection Editor" dialog box........................................................................................34
4.2.6 Adding deleted default blocks................................................................................................36
4.3 Parameter assignment...........................................................................................................38
4.3.1 How to assign parameters of the FF devices.........................................................................38
4.3.2 Bus parameters......................................................................................................................39
4.3.3 How to assign bus parameters...............................................................................................44
4.3.4 How to plan the macrocycle...................................................................................................46
4.4 Using the applications............................................................................................................50
4.4.1 Overview................................................................................................................................50
4.4.2 Identifying FF devices with SIMATIC PDM............................................................................50
4.4.3 Specifying the device identification of the FF devices (TAG name and address)..................52
4.4.4 Editing symbols (symbolic names).........................................................................................53
4.4.5 Configuring interconnections to the FF devices.....................................................................54
4.4.6 Configuring the operator station.............................................................................................55
5 Commissioning...........................................................................................................................................57
5.1 Compile and download...........................................................................................................58
5.1.1 Downloading objects in the FF segment................................................................................58
5.2 Diagnostics.............................................................................................................................62
5.2.1 "Modes" and "Status" menu commands.................................................................................62
5.2.2 Performing diagnostics...........................................................................................................64
FOUNDATION Fieldbus
Commissioning Manual, 11/2014, A5E32711026-AA 3
Table of contents
6 Redundancy and system changes during operation..................................................................................67

6.1 Redundancy...........................................................................................................................67
6.2 System changes during operation..........................................................................................69
Index...........................................................................................................................................................71
FOUNDATION Fieldbus
4 Commissioning Manual, 11/2014, A5E32711026-AA
Introduction 1
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 the FF Link.
(WKHUQHW
352),%86'3
))/LQN
)281'$7,21)LHOGEXV
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 9)")
● Channel blocks of the PCS 7 library: Advanced Process Library (APL)
● PCS 7 Asset Management
Required basic knowledge

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)
FOUNDATION Fieldbus
Introduction
● SIMATIC NET
● SIMATIC PDM
Basic knowledge of the FOUNDATION Fieldbus is required.
Knowledge of the FF Link operating instructions 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.
Changes compared to older versions

Starting from V8.1, SIMATIC PCS 7, together with SIMATIC PDM as of V8.2, is certified for
Class 61 hosts (Host Interoperability Support Test, Host: Profile Classes 61a / 61b).
Examples of the FF functions implemented as a result are:
● Cross block references (device level access)
● Multiple capability levels
● Instantiable blocks
FOUNDATION Fieldbus
Basics of the FOUNDATION Fieldbus 2
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. A maximum of 32 bus nodes is possible on one fieldbus segment (FF
Link + maximum 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‑0 DP/PA couplers via DP/PA-
Link (redundancy with 2 fieldbus couplers possible).
FF devices are connected to an FDC-157 fieldbus coupler via FF Link (IM 153-2 FF)
(redundancy with 2 fieldbus couplers 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 via the FF segment without participation 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.
Client and Server

The client-server principle is used for acyclic services.
FOUNDATION Fieldbus
Basics of the FOUNDATION Fieldbus
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. Use the Schedule
to prevent communication conflicts. An FF Link assumes the LAS function in normal operation.
If there is no FF Link online on the FF segment, suitable FF devices (Link Master) can assume
the LAS function.
Macrocycle
The macrocycle 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
2.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
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)"
FOUNDATION Fieldbus
2.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 area for FF Link (IM 153-2) and FDC 157
● 16: IM for PROFIBUS DP (with redundant configuration of the FF Link: left IM)
● 17: with redundant configuration of the FF Link: right IM
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 52)".
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
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 assignment 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.
FOUNDATION Fieldbus
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.
FOUNDATION Fieldbus
2.3 Block model of device parameters

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.
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 2-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
FOUNDATION Fieldbus
Block designation Function

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.
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:
FOUNDATION Fieldbus
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 assign addresses for FF device
signals (Page 32)".
– Interconnections within the FF devices
You can find information about this in the following sections:
- Section "“Interconnection Editor" dialog box (Page 34)"
- Section "How to configure FF-internal interconnections (Control in the field) (Page 33)"
Operator stations and Maintenance Station

● Output of signals
– Alarms
– Events
● Monitoring
– Process control
– Maintenance
● Long-term archiving
FOUNDATION Fieldbus
2.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.
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 9)".
FOUNDATION Fieldbus
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 host can only communicate with the device if the capability level of the device matches
the configured capability level.
FOUNDATION Fieldbus
2.5 Contact partner
2.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: [email protected]
Internet: http://www.siemens.com/automation/service&support (http://
www.siemens.com/automation/service&support)
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 will find this on the "SIMATIC
PDM Device Library 1#2014" DVD in the "\_manuals" directory.
Follow-up installations and additional information on SIMATIC PDM are available on the
Internet at "http://www.siemens.com/simatic-pdm (www.siemens.de/simatic-pdm)".
FOUNDATION Fieldbus
System planning 3
3.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 FF 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 system requirements with
regard to update times.
Typically, 3 to 7 FF devices (maximum 31) are integrated in an FF segment.
The time for a macrocycle 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 macrocycle 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 macrocycle for 15
transmitted values will be approximately one second. The time for output of a value depends
on the device in question.
Sample 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 macrocycle = between 1500 ms and 9000 ms
FOUNDATION Fieldbus
System planning
3.1 Nodes in the FOUNDATION Fieldbus
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 macrocycle.
FOUNDATION Fieldbus
System planning
3.2 Configuration
3.2 Configuration
Hardware
Always connect an FF segment to the automation system via PROFIBUS DP .
You need an FF Linkfor the transition between PROFIBUS DP and the FF segment.
You can operate an FF Link at the integrated chain of the CPU if the CPU supports the data
record gateway. Possible CPU versions:
● Standard CPU as of V5.1
● H-CPU as of V6.0
● WinAC RTX as of V4.6
Network configuration
The configuration of FF segments in the following topologies is common in PCS 7:
● Line
● Redundant configuration (see also section "Redundancy (Page 67)")
Line lengths
An FF segment is limited to 1900 m. These figures only apply when you use suitable cables.
Branch lines should also be taken into account when calculating the bus line to the FF devices.
The maximum permitted length of a branch line is 120 m. The length depends on the cable
type.
Recommendation:
You can optimize performance by using shielded bus cables (type A) as this reduces the
sensitivity to interference.
Number of branch lines (longer than 1 m) Maximum length of a branch line

1-12 120 m
13-14 90 m
15-18 60 m
19-24 30 m
25-31 1m
Intrinsically safe configuration

For an intrinsically safe configuration, the length of a branch line is limited to 60 m.
● Operating instructions SIMATIC; Bus links; FF Link bus link
● Function manual Process Control System PCS 7; Fault-tolerant Process Control Systems
FOUNDATION Fieldbus
System planning
3.2 Configuration
FOUNDATION Fieldbus
Engineering 4
Overview
You configure the FOUNDATION Fieldbus and create the FF devices in HW Config.
You configure an FF Link on PROFIBUS DP . FF Link will automatically create a "Foundation
Fieldbus: FF subsystem" object with standard bus parameters.
You assign the parameters of the FF devices with SIMATIC PDM.
FOUNDATION Fieldbus
Engineering
4.1 Prepare
4.1 Prepare
4.1.1 How to integrate a device description
Requirements
SIMATIC PDM is installed.
Procedure
1. In the Windows start menu, select the menu command SIMATIC PDM > Device Integration
Manager under Siemens SIMATIC programs.
In order to use the Device Integration Manager, you must accept the license agreement.
2. Select the menu command File > Read device descriptions ... .
3. In the tree view, navigate to the directory with the device descriptions.
Note on the "Device Library" DVD: The "Device Library" DVD is supplied with SIMATIC
PDM. Select the drive containing the DVD.
Click "OK".
The device descriptions in the directory are displayed in the "Devices" list.
4. Select the check boxes for the devices whose device descriptions are to be integrated.
All FF devices (device library of the Fieldbus Foundation and other individual devices) are
located below the "Fieldbus Foundation" directory.
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.
5. Click "Integrate".
The device descriptions are transferred to the computer.
Online help for SIMATIC PDM
FOUNDATION Fieldbus
Engineering
4.2 Configuring
4.2 Configuring
4.2.1 How to place FF devices on the FOUNDATION Fieldbus
Example of an FF configuration
(WKHUQHW
352),%86'3
))/LQN
)281'$7,21)LHOGEXV
Recommendation for using symbolic names

Assign symbolic names to the signals of the FF devices. Symbolic names facilitate
configuration and documentation of the automation task.
The use of symbolic names is taken into account in the following.
Requirements
● SIMATIC PCS 7 is installed.
● SIMATIC PDM is installed with the "SIMATIC PDM FF Option" (default setting for PCS 7).
● 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 on this in the section "How to integrate a device description
(Page 24)".
● You are familiar with the functions and signals required by the FF device.
You can find additional information about this in the documentation of the FF device.
FOUNDATION Fieldbus
Engineering
4.2 Configuring
Changing device name with SIMATIC PDM

Always use SIMATIC PDM to change the device name.
● The length of the device name is 32 characters (will be automatically filled with empty
spaces).
● The following characters are not permitted:
"&?*<>|%§€'.\][
Procedure
The general procedure for placing an FF device on a FOUNDATION Fieldbus consists of the
following steps:
1. Create interface module with FOUNDATION Fieldbus: Create FF subsystem
2. Insert FF device
3. Name FF device
4. Assign device addresses and symbolic names
Details about the individual steps are given in the following sections.
Creating an interface module 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 View > Catalog menu command.
The hardware catalog opens.
3. Open the PROFIBUS DP > FF Link folder in the current PCS 7 profile.
4. Drag the IM 153-2 FF interface module to the PROFIBUS DP master system.
5. 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
In PCS 7, you configure the FF Link and FF devices via SIMATIC PDM. If the "Configuration
via PDM" option is activated, you can open SIMATIC PDM by double-clicking FF Link .
6. Click "OK".
The interface module is created with a FOUNDATION Fieldbus: FF subsystem.
FOUNDATION Fieldbus
Engineering
4.2 Configuring
Naming the FF device

1. Double-click on the inserted FF device.
SIMATIC PDM opens.
– Select the top node in the tree view.
– Select the Edit > Object Properties menu command.
– In the "Name" text box in the "General" tab, enter plant-specific device name in the
"Object name" box.
– Click "OK".
– Select the menu command File > Save.
– Open SIMATIC PDM.
2. Select the inserted FF device.
3. For devices to be operated as Backup Link Master :
– Select the Edit > Object Properties menu command.
– Select the "Parameters" tab.
– Activate the "Backup Link Master" check box.
– Click "OK".
Inserting the FF device

1. Select the inserted FF Link.
2. Optional steps for a redundant FOUNDATION Fieldbus:
– Select the IM 153-2 FF.
– Double-click the slot of the first "FDC 157" in the table.
The "Properties - Coupler" dialog box opens.
– Select the "Parameters" tab.
– Select the redundancy type in the "Value" column:
- No redundant configuration (default)
- Coupler redundancy
- Ring redundancy
3. Click "OK".
The settings are applied.
4. Double-click the FOUNDATION FIELDBUS in the current PCS 7 profile.
5. 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.
FOUNDATION Fieldbus
Engineering
4.2 Configuring
6. Drag the required FF device to the FF subsystem.

The "Properties FF interface FF device" dialog box opens.
7. Enter the address of the FF device in the system in the "Parameter" tab.
8. 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.
Observe the section "Adding deleted default blocks (Page 36)"
Assigning device addresses and symbolic names

1. Select the inserted FF device.
2. Select the required I/O data in the address table of all block types.
Multiple selection is typical for Windows.
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.
3. Select the menu command Assign address from the shortcut menu.
Addresses are assigned for the selected functions.
If necessary, adapt the start address.
You can find information on this in the section "Device addresses (Page 11)".
FOUNDATION Fieldbus
Engineering
4.2 Configuring
4. Assign symbolic names for all addresses.

This measure makes for easier configuration:
– 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.
5. Select Station > Save and Compile from the menu.
Note
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.
Note
Downloading when device address of the device in the system is unknown
Select the following menu command in SIMATIC Manager to find the FF device in the
system: Edit > SIMATIC PDM > Start LifeList.
When you find the desired device, do the following:
1. Select the Device > Assign address and TAG menu command.
2. Transfer the correct address and TAG to the FF device.
Note: Changing the address will restart the device.
3. Download the configuration to the device.
FOUNDATION Fieldbus
Engineering
4.2 Configuring
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 will be changed on all FF devices and will be marked as "for download"
in the project. The following bus parameters are affected:
– Slot Time
– Maximum Response Delay
– Minimum Inter DLPDU Delay
– Macrocycle
Note
Checking the macrocycle
Check the settings of the macrocycle.
You can find additional information about this in the following sections:
● Section "Bus parameters (Page 39)"
● Section "How to assign bus parameters (Page 44)"
● 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"
4.2.2 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.
FOUNDATION Fieldbus
Engineering
4.2 Configuring
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 34)")
Capability level
The host 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 disconnect 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, which is 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.
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 FF Link will be removed.
FOUNDATION Fieldbus
Engineering
4.2 Configuring
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.
4.2.3 How to assign addresses for FF device signals

You need to assign addresses to the FF device signals that you want to process further with
the automation system.
Avoid address conflicts by externally assigned device addresses

In the case of FF devices (including FF Link) which are able to assume the LAS function (Link
Master), the following applies:
Note
Set the correct bus parameters in a separate action before physically connecting these FF
devices to an active FF bus in process mode.
Example:
You want to replace a defective FF device or a defective FF Link in process mode. No
redundant FF Linkis installed on the FOUNDATION Fieldbus . Bus operation is to be
maintained with an external LAS.
Requirements
● FF devices have been created in HW Config.
● The necessary FF device signals are known.
Changing the configuration

1. Select an FF device in HW Config.
2. Select the signal "slot" in the list.
3. Select the Assign address menu command in the shortcut menu.
The "<Signal> Properties" dialog box opens.
Make the changes.
4. Click "OK".
FOUNDATION Fieldbus
Engineering
4.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.
4.2.4 How to configure FF-internal interconnections (Control in the field)
Note
Required CiF interconnections
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 assign addresses for FF
device signals (Page 32)".
Example of the representation:
The lock symbol indicates a locked input.
Procedure
1. Open the configuration in HW Config.
2. Select the interface module for the FF Link (IM 153-2 FF).
FOUNDATION Fieldbus
Engineering
4.2 Configuring
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 34)".
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.
Deleting an interconnection
To delete an interconnection, select the desired line in the "Inputs and interconnections" list
and click the "Delete interconnection" button.
Downloading
The schedule for the FOUNDATION Fieldbus is calculated automatically during downloading
of the FF devices.
● Online help for SIMATIC PDM
4.2.5 “Interconnection Editor" dialog box
Note
Menu command "Start Connection Editor"
The "Start Connection Editor" menu command is only enabled in HW Config for an 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.
FOUNDATION Fieldbus
Engineering
4.2 Configuring
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 were not saved.
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
FF Link
FF device
Block within an FF device
Inputs and outputs Status
FOUNDATION Fieldbus
Engineering
4.2 Configuring
Icon Displayed object

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 and outputs

Inputs or outputs can be locked for the interconnection. Causes:
● The input or output is interconnected internally.
● An I/O address is already assigned to the input or output in HW Config from the process
image. You can find information on this in the section "How to assign addresses for FF
device signals (Page 32)".
Example of the representation:
The lock icon indicates a locked input.
See also
How to configure FF-internal interconnections (Control in the field) (Page 33)
4.2.6 Adding deleted default blocks
NOTICE
Recommissioning 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.
FOUNDATION Fieldbus
Engineering
4.2 Configuring
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
Recommissioning of the FF device required
Ensure that the system status permits recommissioning of the FF device.
5. Click "Transfer".
● Information of the device manufacturer
FOUNDATION Fieldbus
Engineering
4.3 Parameter assignment
4.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.
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 of an FF device.
– The FF Link if you want to read the device data of all FF devices on the FF segment.
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".
FOUNDATION Fieldbus
Engineering
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.
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
4.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 7: FUN = 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 Meaning and limiting values

range (de‐
fault)
Slot Time 1 - 512 This parameter specifies how fast the FF device can reply upon receipt of a PDU.
(8) 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 connection
head (2) 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 PDU.
Delay (10) 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 seg‐
Delay (16) ment. 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 used by
(2) the FF devices (receiving nodes) for clock synchronization. The number of preambles
(s) can be extended when setting this parameter. The default value in PCS 7 is 2;
networks including digital repeaters may require larger values.
Time Sync Class 0-7 This parameter defines the quality of the clock accuracy of an FF device. Thus it also
(4) 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

range (de‐
fault)
Maximum Scheduling 16 This parameter extends the time that may be used by the LAS for processing the
Overhead 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.
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 a device
Skew (0) 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 times
sion (0) after each transmission.
Use this parameter to increase this interruption in signal transmission by additional
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 is the
ken Delegation Time (86) 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 transfer
Time (60000) 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. This
ken Holding Time (336) 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

range (de‐
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).
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 those devices
(10) 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 communication with
the FF segment.
0: Checking is turned off in the device.
4.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.
Connecting a link master (LAS) to an active FF segment

Before you connect this device (field device or FF Link), assign the bus parameters in a
separate action.
Example:
FOUNDATION Fieldbus
Engineering
Replacement of an FF Link in the non-redundant configuration. The functions on the FF

segment are maintained by a field device that can operate as a link master (LAS).
Requirements
● The FF devices have been created in the PCS 7 project.
● Interconnections via the FF have been configured.
Procedure
1. Select the FF subsystem 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 necessary.
A modification is usually not required.
4. Click "Properties...".
The "Properties - Foundation Fieldbus" dialog box opens.
5. Select the "Bus parameter" tab. Enter the settings.
You can find information on this in the section "Bus parameters (Page 39)".
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 menu command File > Save.

These changes are applied 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 30)".
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 "Macrocycle" tab.
4. Click the "Calculate schedule" button.
If your bus parameters deviate from the default values, you can adapt the values in the
input boxes ("acyclical percentage" and "macrocycle").
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 macrocycle settings.
4.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 HW Config of SIMATIC Manager.
The "FF subsystem properties" dialog window opens.
3. Specify the subsystem number of the FF segment, if necessary.
A change is generally not needed.
4. Click "Properties...".
The "Properties - Foundation Fieldbus" dialog box opens.
5. Open the "Macrocycle" tab.
6. Enter the system-specific settings.
7. Click the "Calculate schedule" button.
The consistency of the set parameters is checked. The result is displayed graphically.
8. Select the Station > Save menu command.
The changes are applied 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
● 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.
FOUNDATION Fieldbus
Engineering
4.4 Using the applications
4.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.
4.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.
FOUNDATION Fieldbus
Engineering
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.
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 16 to 251
Recommendation:
Limit the address range for the scan operation.
A scan operation across a large address range takes longer.
FOUNDATION Fieldbus
Engineering
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
4.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 44)".
Procedure
Note
Restart
Changing the address will restart the device.
FOUNDATION Fieldbus
Engineering
1. Open the project in the process devices network view.

2. Open the network view of the automation system.
3. Select the FF Link in the tree view.
4. Select the shortcut menu command Open Object.
The "SIMATIC PDM" dialog box opens.
5. Select the FF Link.
6. Select the Edit > SIMATIC PDM > Start LifeList menu command.
The "LifeList" dialog window opens.
7. Select the "Start" menu command.
All detected FF devices are displayed in the table.
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.
Downloading
To ensure that all configured parameters and connections are available for the FF device, the
FF device must be downloaded.
4.4.4 Editing symbols (symbolic names)

You can easily adapt the symbolic names and comments for signals.
FOUNDATION Fieldbus
Engineering
Requirements
Symbolic names were assigned for the inputs and outputs during configuration of the FF
devices.
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.
4.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.
4.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
Engineering
FOUNDATION Fieldbus
Commissioning 5
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.
FOUNDATION Fieldbus
Commissioning
5.1 Compile and download

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.
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
5.1.1 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)
FOUNDATION Fieldbus
Commissioning
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
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 FF segment is fully downloaded (option at FF Link: "always load FF Link and FF
devices"), the download is briefly stopped.
● If the FF segment is incrementally downloaded (option at FF Link: "Only load FF Link and
FF devices when modified"), the download continues.
● If required, 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 Device parameters

and interconnections
For a CPU with FF Link , you always download Hardware configura‐ Downloading -
the hardware configuration in HW Config. tion is downloaded
PLC > Download to Module
The menu command PLC > Compile and Down‐ Program and connec‐ - -
load Objects... in the SIMATIC Manager. tions are downloaded
FOUNDATION Fieldbus
Commissioning
Menu command CPU data Schedule, bus parameters Device parameters

and interconnections
In SIMATIC PDM, select the FF Link - - All FF devices are
Device > Download to device downloaded.
Select the "Object with all subordinate objects
and networks" check box in the "Download to
device" dialog.
Select the FF device in SIMATIC PDM Device > - - The FF device is
Download to device Only when replacing a de‐ loaded
Select the "Object with all subordinate objects" vice with one of the same
check box in the "Download to device" dialog. type:
Select the check box "Load
Schedule to Device".
Note
You can download changes to the automation system in "RUN" mode (CIR). Note the settings
for "Load FF Segment".
Note
FF Link - Download changes
If you have configured the setting "Only load FF Link and FF devices when modified" in FF
Link , you have to note the following:
● Only a complete download is possible after executing the action "Calculate Schedule" in
"Properties - Foundation Fieldbus -> Macrocycle".
● Complete downloading is made possible by changing the FF Link configuration to "Always
load FF Link and FF devices".
Settings for "Load FF segment"

You can make settings in the object properties of the FF link in HW Config that are taken into
consideration during an AS download.
Perform the following steps:
1. Open the hardware configuration in SIMATIC Manager.
2. Open the object properties of the FF Link.
FOUNDATION Fieldbus
Commissioning
3. Select the "Load FF Segment" tab.

4. Make the settings in accordance with the following table:
Check box Application Effect

Only load FF Link Exclude FF segment during If only changes are downloaded, the FF seg‐
and FF devices AS loading ment continues running during loading.
when modified Example: You configure no
changes for the FF segment.
Always load FF Link Complete download of an FF The FF segment is stopped when it is down‐
and FF devices segment loaded completely.
Recommendation
After a complete download of an FF seg‐
ment, select the option "Only load FF Link
and FF devices when modified".
Exclude FF Link Function for commissioning This function supports you during commis‐
and FF devices only sioning of other FF links on the same PRO‐
from loading FIBUS.
NOTICE!
STOP of the FF segment possible
Undefined states may occur in the FF seg‐
ment when you use this setting.
See also
How to assign parameters of the FF devices (Page 38)
FOUNDATION Fieldbus
Commissioning
5.2 Diagnostics
5.2 Diagnostics
Diagnostics for the FF in PCS 7

PCS 7 uses graduated diagnostics.
With the Maintenance Station

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

● Detailed diagnostics for FF Link and FF devices
● Use of the "Mode" dialog box only for FF Link and FF devices
● Use of "Status" dialog box only for FF Link and FF devices
LED displays on the FF 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 50)"
● SIMATIC;FF Link Operating Instructions
● FF devices documentation
5.2.1 "Modes" and "Status" menu commands

You can find the "Modes" and "Status" menu commands for blocks of FF devices in the
"Devices" 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
5.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
5.2 Diagnostics
● Simulate status information

● Run restart functions
NOTICE
Restart functions
Read the device manufacturer information on this.
5.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.
2. Select the FF device.
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
5.2 Diagnostics
Detailed diagnostics with SIMATIC PDM

1. Select one of the following views:
– Process device network view
– Process device plant view
2. Select the FF device.
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
Commissioning
5.2 Diagnostics
FOUNDATION Fieldbus
Redundancy and system changes during operation 6
6.1 Redundancy
The basic structure of redundant FF segments corresponds to the structure for PROFIBUS
PA. In the configuration, the necessary couplers are an integral component of the FF Link.
You can find additional information about this in the documentation SIMATIC Process Control
System PCS 7; Fault-Tolerant Process Control Systems, section "Redundant PROFIBUS PA".
Possible redundancies when using AFD/AFS:
● Ring redundancy
● Coupler redundancy
Possible redundant components in the FF segment:

● IM 153-2 FF interface module
● FDC 157 fieldbus coupler
● Redundant field bus when using AFD/AFS
Note
Connecting the FF Link to the H system
The left IM 153-2 FF interface module of the FF Link must always be connected to Rack 0
of the H system.
Configuring
You configure only the FF devices and the FF Link on PROFIBUS DP.
The necessary configuration steps are described in section "How to place FF devices on the
FOUNDATION Fieldbus (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.
FOUNDATION Fieldbus
Redundancy and system changes during operation
6.1 Redundancy
● You can find more information on redundant design of the PROFIBUS PA in the
documentation SIMATIC; Process Control System PCS 7; Fault-Tolerant Process Control
Systems chapter "Redundant PROFIBUS PA".
● Information on the hardware design of the FOUNDATION Fieldbus is available in the
documentation SIMATIC; Bus links; FF Link bus link.
● Information on the design of the redundant fieldbus with AFD/AFS is available in the
documentation SIMATIC; Bus links; DP/PA coupler, active field distributors, DP/PA-Link
and Y-Link.
FOUNDATION Fieldbus
6.2 System changes during operation

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.
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 connections between FF devices
● Changing of bus parameters
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.
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
A I
Address, 52 Integrate, 26, 52
Field device in SIMATIC PDM, 52
PROFIBUS device in SIMATIC PDM, 26
B Interconnection Editor, 33
Block
Function block, 13
Resource block, 13
L
Transducer block, 14 Load FF segment
Block model Tab, 60
Objects, 14
Block types, 13
M
Multiple capability levels, 14
C
Capability level, 14, 27
Change N
Download, 60
Name, 52
CiF, 33
CiF interconnections, 28
Configuration via PDM, 26
Connection Editor
O
Starting, 34 Option
Configuration via PDM, 26
D
Device catalog, 14
P
Device description, 14 PROFIBUS device in SIMATIC PDM, 26
Download, 59 Integrate, 26
Change, 60 Publisher, 7
Downloading changes, 60
Downloading changes, 60
R
Resource block, 13
F
Field device in SIMATIC PDM
Integrate, 52 S
Function block, 13
Schedule, 7
Function blocks, 13
SIMATIC Manager
Start Connection Editor, 34
SIMATIC PDM, 14, 26
H Integrate field device, 52
HW Config, 14 Integrating a PROFIBUS device, 26
Start Connection Editor, 34 Start Connection Editor, 34
FOUNDATION Fieldbus
Index
Subscriber, 7
T
Tab
Load FF segment, 60
TAG, 52
Transducer block, 14
Transducer blocks, 14
X
XE \* MERGEFORMAT, 33
FOUNDATION Fieldbus

PCS 7 FoundationFieldbus en en-US

Uploaded by

Copyright:

Available Formats

PCS 7 FoundationFieldbus en en-US

Uploaded by

Document Information

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

Introduction 1

Basics of the FOUNDATION

Valid for the SIMATIC PCS 7 Process Control System

Siemens AG A5E32711026-AA Copyright © Siemens AG 2014.

6 Redundancy and system changes during operation..................................................................................67

SIMATIC PCS 7 supports the connection of FF devices

Required basic knowledge

Information for FF users

Changes compared to older 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)

2.1 Device integration with EDD

Standardized device descriptions

Information in device descriptions

2.2 Device addresses

Address ranges in PCS 7

Address range Information on the address range

Automatic address conflict resolution for device addresses

2.3 Block model of device parameters

Block type Note

Block designation Function

Block designation Function

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

2.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

2.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

Number of branch lines (longer than 1 m) Maximum length of a branch line

Intrinsically safe configuration

4.1.1 How to integrate a device description

4.2.1 How to place FF devices on the FOUNDATION Fieldbus

Recommendation for using symbolic names

Changing device name with SIMATIC PDM

Creating an interface module with FOUNDATION Fieldbus: Create FF subsystem

Naming the FF device

Inserting the FF device

6. Drag the required FF device to the FF subsystem.

Assigning device addresses and symbolic names

4. Assign symbolic names for all addresses.

Checking the bus parameters

4.2.2 Additional notes on configuration

Device-specific number of interconnections

Changing the configuration

Changing interconnections - Impact on communication

Connecting the separated FOUNDATION Fieldbus to an automation system (behind

4.2.3 How to assign addresses for FF device signals