PCS 7 in-practice FoundationFieldbus

7/21/2019 PCS 7 in-practice FoundationFieldbus

1/54

SIMATIC

Process Control System PCS 7

FOUNDATION Fieldbus

Commissioning Manual

Requirement: SIMATIC PDM V8.0 SP1

03/2012

A5E03880935-01

Introduction

1

Basics of the FOUNDATION

Fieldbus

2

System planning

3

Engineering

4

Commissioning

5

Redundancy and system

changes in operation

6


2/54

Legal information

Warning notice system

This manual contains notices you have to observe in order to ensure your personal safety, as well as to preventdamage to property. The notices referring to your personal safety are highlighted in the manual by a safety alertsymbol, notices referring only to property damage have no safety alert symbol. These notices shown below aregraded according to the degree of danger.

DANGER

indicates that death or severe personal injury willresult if proper precautions are not taken.

WARNING

indicates that death or severe personal injury mayresult if proper precautions are not taken.

CAUTION

with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.

CAUTION

without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.

NOTICE

indicates that an unintended result or situation can occur if the relevant information is not taken into account.

If more than one degree of danger is present, the warning notice representing the highest degree of danger will beused. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to propertydamage.

Qualified Personnel

The product/system described in this documentation may be operated only bypersonnel qualified

for the specifictask in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualifiedpersonnel are those who, based on their training and experience, are capable of identifying risks and avoidingpotential 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 technicaldocumentation. If products and components from other manufacturers are used, these must be recommended orapproved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation andmaintenance are required to ensure that the products operate safely and without any problems. The permissibleambient 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 publicationmay 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 inthis publication is reviewed regularly and any necessary corrections are included in subsequent editions.

Siemens AGIndustry SectorPostfach 48 4890026 NRNBERGGERMANY

A5E03880935-01 04/2012 Technical data subject to change

Copyright Siemens AG 2012.All rights reserved


3/54

Table of contents

1 Introduction...................................................................................................................................................5

2 Basics of the FOUNDATION Fieldbus..........................................................................................................7

2.1 Basic knowledge of FOUNDATION Fieldbus................................................................................7

2.2 Device integration with EDD..........................................................................................................8

2.3 Device addresses..........................................................................................................................9

2.4 Block model of device parameters..............................................................................................10

3 System planning.........................................................................................................................................133.1 Nodes in the FOUNDATION Fieldbus.........................................................................................13

3.2 Configuration...............................................................................................................................14

4 Engineering................................................................................................................................................17

4.1 Prepare........................................................................................................................................17

4.1.1 How to integrate a device description..........................................................................................17

4.2 Configuring..................................................................................................................................18 4.2.1 How to place FF devices on the FOUNDATION Fieldbus...........................................................18 4.2.2 Additional notes on configuration................................................................................................22 4.2.3 How to assign addresses for FF device signals..........................................................................23

4.2.4 Interconnection Editor" dialog box..............................................................................................24 4.2.5 How to configure FF internal interconnections (Control in the field)............................................25

4.3 Parameter assignment................................................................................................................26 4.3.1 How to assign parameters of the FF devices..............................................................................26 4.3.2 Bus parameters...........................................................................................................................28 4.3.3 How to set the bus parameters....................................................................................................33 4.3.4 How to plan the macrocycle........................................................................................................36

4.4 Using the applications.................................................................................................................38 4.4.1 Overview......................................................................................................................................38 4.4.2 How to identify FF devices with SIMATIC PDM..........................................................................39 4.4.3 How to define the device ID of the FF devices (TAG name and address)..................................40 4.4.4 How to edit the symbols..............................................................................................................41 4.4.5 How to configure interconnections to the FF devices .................................................................42 4.4.6 Configuring the OS......................................................................................................................43

5 Commissioning...........................................................................................................................................45

5.1 Compile and download................................................................................................................45

5.1.1 How to download objects in the FF segment...............................................................................46

5.2 Diagnostics options.....................................................................................................................48 5.2.1 How to perform diagnostics.........................................................................................................48

6 Redundancy and system changes in operation..........................................................................................51

6.1 Redundancy................................................................................................................................51

FOUNDATION FieldbusCommissioning Manual, 03/2012, A5E03880935-01 3


4/54

6.2 Changing the system in run.........................................................................................................52

Index...........................................................................................................................................................53

Table of contents

FOUNDATION Fieldbus4 Commissioning Manual, 03/2012, A5E03880935-01


5/54

Introduction

1

SIMATIC PCS 7 enables the integration of field devices in FOUNDATION Fieldbus H1(hereinafter referred to simply as FF). FF devices are generally connected to a SIMATIC stationvia the FF Link.

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

Channel blocks of the PCS 7 library: Advanced Process Library (APL)

PCS 7 Asset Management



6/54

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:

SIMATIC PCS 7

SIMATIC S7 (S7-400, STEP 7)

SIMATIC NET

SIMATIC PDM

Basic knowledge of the FOUNDATION Fieldbus is required.

Knowledge of the structure of the FF Link operating instructions

Information for FF users

Users who have configured only FF up to now can acquire necessary knowledge of PCS 7using the PCS 7 documentation. You can find an introduction to working with PCS 7 in theSIMATIC; Process Control System PCS 7;

PCS 7 - Getting Startedmanual.

Scope of the documentation

This documentation is valid for the software package Process Control System; SIMATIC PCS7, V8.0 Update 1 or higher including SIMATIC PDM V8.0 service pack 1.

Introduction



7/54

Basics of the FOUNDATION Fieldbus

2

2.1 Basic knowledge of FOUNDATION Fieldbus

FOUNDATION Fieldbus (FF) and PROFIBUS PA operate according to IEC 61158-2. Thecommunication on the fieldbus and the voltage supply of the bus nodes are combined in oneshielded two-wire cable. A maximum of 32 bus nodes is possible on one fieldbus segment (FFLink + maximum 31 field devices). Data packets are modulated and transmitted on the supplyvoltage for the fieldbus nodes. The transfer rate is 31.25 Kbps.

The most important distinctions between PROFIBUS PA and FOUNDATION Fieldbus

LicensingYou 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 a maximum of five FDC 157-0 DP/PA couplers(redundancy with 2 fieldbus couplers possible) via DP/PA-Link .

FF devices are connected to an FDC 157 fieldbus coupler (redundancy with 2 fieldbuscouplers possible) via FF Link (IM 153-2 FF) .

Communication with the automation system

PROFIBUS PA devices only communicate via the automation system. An exception tothis rule is the direct access to a PA device.

FF devices can communicate via the FF segment without participation of the automationsystem. The name of this function is "Control in the field" (CIF). CIF enablestechnological function between FF devices.

Terms used for FOUNDATION Fieldbus (FF)

Publisher and Subscriber

In the time period during which an FF device sends its data to the FF, it is referred toas the Publisher.

In the time period during which an FF device reads data from the FF, it is referred to asthe Subscriber. The Schedule defines when a Publisher sends data and when aSubscriber receives data.

Client and Server

The client-server principle is used for acyclic services.



8/54

Communication typesTwo types of communication are used with FF:

cyclic communicationCyclic communication is defined in the Schedule. It includes tasks such as controllingprocess variables (control functions) and operating and monitoring functions.

acyclic communicationAcyclic communication is used for transmitting unscheduled information. Examplesinclude the following information:* Maintenance/diagnostic data* Configuration data* Parameterization data

Schedule and LAS (Link Active Scheduler)

With FF, the Schedule defines when an FF device sends or reads cyclic data. Use theSchedule to prevent communication conflicts. An FF Link assumes the LAS function innormal operation. If there is no FF Link online on the FF segment, suitable FF devices (LinkMaster) can assume the LAS function.

Macrocycle

The macrocycle is a time period which must be defined for each system. The followingtasks must be performed during this time period:

All FF devices must be processed.

Information must be transmitted by means of acyclic communication.

The FF specifications recommend that at least 50% of the bus time is kept free for acycliccommunication.

2.2 Device integration with EDD

Standardized device descriptions

Standardized device descriptions enable intelligent field devices from different manufacturersto be integrated in different control systems. The IEC 61804-3 standard governs the structureof device descriptions (DD). This standard was developed in cooperation with the followingorganizations:

PROFIBUS User Organization (PNO)

Hart Communication Foundation (HCF)

Fieldbus FOUNDATION

OPC Foundation

The device descriptions are based on the EDDL (Electronic Device Description Language).


2.2 Device integration with EDD



9/54

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. Thesestandard DDs are available from the user organizations, for example, through the FieldbusFOUNDATION.FF devices can interpret and display the data and functions of this standard DD. The basicfunctions of the user interface are stored in the standard DD.

Device-specific functions and parameters can be stored in an extended device description.

Additional information

IEC 61804-2

IEC 61804-3

Section "Block model of device parameters (Page 10)"

2.3 Device addresses

Address ranges in STEP 7 and PCS 7

The following table shows the distribution of address ranges at the FF segment:

Addresses 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 (left IM with redundant configuration of the FF Link)

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. Youcan find information on this in section "How to define the device ID of the FF devices (TAG name andaddress) (Page 40)".

232 to 247 SIEMENS Reserve Range:Reserved address range for new FF devices or FF devices that are not in operation, and for FF devicesthat are only temporarily connected.


2.3 Device addresses



10/54

Addresses Information on the address range

248 to 251 Range for temporary FF devices

Devices that will be 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. Otherwise, FF devices can no longer bereached by certain actions (for example, "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 case of an addressconflict, a recently connected FF device will automatically be assigned a temporary addressduring operation. The device addresses 248 to 251 have been reserved for automatic addressconflict resolution at the FF segment.

Note

The device address that was assigned to an FF device by automatic address conflictresolution 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 thesame address at the FF segment.

You have to change the device addresses of FF devices that have been assigned to oneof the temporary addresses.

2.4 Block model of device parameters

The parameters (functions and data of an FF device) are assigned block types in the devicedescriptions of the FF devices:

Resource block

Function block - several function blocks are possible for an FF device

Transducer block - several transducer blocks are possible for an FF device

Note

Parameter assignment with SIMATIC PDM

The application SIMATIC PDM is used in PCS 7 for assigning parameters to the FFdevices.





11/54

Block types

Resource block

The resource block contains device-specific information from the manufacturer.Examples 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 wellas their tasks. The schedules of the clocked data transmission defined in the Schedule arebased on these function blocks. Accesses to the functions and their inputs and outputs aredefined via the function blocks. Each FF device has at least one function block.Standard function blocks are defined in the FF specifications. The basis functions can bedescribed using these standard function blocks.Examples are:

AI: Analog input

AO: Analog output

B Offset (bias)

CS Control selector

DI: Digital input

DO: Digital output

ML: Manual loader

PD: PD controller (proportional/derivative)

PID: PID controller (proportional/integral/derivative)

RA: Ratio controller

Transducer blockYou use transducer blocks to manipulate the input and/or output variables of a function

block.Examples are:

Calibration and conversion of measured and control data

Linearization of characteristic curves

Conversion of physical quantities using other process data

Objects of the block model

In PCS 7, applications in the PC stations assume the functions of FF-specific objects:

Engineering station





12/54

Configuration of the FOUNDATION Fieldbus

Interconnection of the FF devices

Interconnections between the FF devices

Interconnection across fieldbuses

Operator stations or maintenance station

Output of signals

Alarms

Events

Monitoring

Process control

Maintenance Long-term archiving





13/54

System planning

3

3.1 Nodes in the FOUNDATION Fieldbus

An FF segment contains all nodes communicating via the FOUNDATION Fieldbus. Thefollowing 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 bytesI/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)

Nodes in an FF segment

The maximum number of nodes in an FF segment depends on the system requirements withregard to update times. Typically, 3 to 7 FF devices (maximum 31) are integrated in an FFsegment.

The time for a macrocycle is influenced primarily by the share of cyclic communication. Thisshare depends on the following factors:

Properties of the FF devices which are used on the FF segment.

Number of input values and output values of all components connected to the FF segment.

You may indicate a target value for the macrocycle as well as the ratio between cyclical andacyclic 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 15transmitted values will be approximately 1 second. The time for output of a value depends onthe device in question.



14/54

Sample calculation

15 x 30 ms = 450 ms, corresponds to the cyclic bus time

reserved bus time for acyclic communication1050 ms (recommended 70 %), 450 ms (recommended, at least 50%)

recommended macrocycle = between 1500 ms and 900 ms

I/O data

The parameters, inputs and outputs of FF devices are distributed over function blocks. An FFdevice 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.

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 thedata record gateway. Possible CPU versions:

Standard CPU as of V5.1

H-CPU as of V6.0

Network configuration

The configuration of FF segments in the following topologies is common in PCS 7:

Line

Redundant configuration (see also section "Redundancy (Page 51)")

Line lengths

An FF segment is limited to 1900 meters. These figures only apply when you use suitablecables. Branch lines should also be taken into account when calculating the bus line to theFF devices.

The maximum permitted length of a branch line is 120 meters. The length depends on thecable type.

Recommendation:You can optimize performance by using shielded bus cables (type A) as this reducessensitivity to interference.

System planning

3.2 Configuration



15/54

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

1-12 120 m

13-14 90 m15-18 60 m

19-24 30 m

25-31 1 m

Intrinsically safe configuration

NOTICE

The maximum length of a branch line is limited to 60 meters.


Operating instructions SIMATIC; Bus links; FF Link bus link

Manual Process Control System PCS 7; Fault-tolerant Process Control Systems

System planning

3.2 Configuration



16/54


17/54

Engineering

4

Overview

You configure the FOUNDATION Fieldbus (FF) and set up 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.

Set the parameters of the FF devices with SIMATIC PDM.

4.1 Prepare

4.1.1 How to integrate a device description

Requirement

SIMATIC PDM is installed.

Procedure

1. Go to the Windows start menu and select the menu commandSIMATIC PDM > Device

Integration Manager

under Siemens SIMATIC programs.To be able to use the Device Integration Manager, you must accept the license agreement.

2. Select the menu commandFile > Read device descriptions ...

.

3. Navigate to the folder with the device descriptions in the tree structure.Note on Device Library DVD:The "Device Library" DVD is supplied with SIMATIC PDM. Select the drive containing theDVD.

4. Click "OK".The device descriptions in the folder are displayed in the "Devices" list.

5. Select the check box for the devices whose device descriptions you want to import.The default directory is "Foundation Fieldbus".

6. Click "Integrate".The device descriptions are transferred to the computer.


Online help for SIMATIC PDM



18/54

4.2 Configuring

4.2.1 How to place FF devices on the FOUNDATION Fieldbus

Example of an FF configuration

Recommendation for using symbolic names

Assign symbolic names to the signals of the FF devices. Symbolic names facilitateconfiguration and documentation of the automation task.The use of symbolic names is taken into account in the following.

Requirement

SIMATIC PCS 7 is installed.

SIMATIC PDM is installed.

A project has been created in the SIMATIC Manager. An automation system with aPROFIBUS DP master system has been created in HW Config.Additional information is available in the manual SIMATIC; Process Control System PCS7; 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 section "How to integrate a device description(Page 17)".

You are familiar with the functions and signals required by the FF device.Information must be contained in the FF device documentation.

Engineering

4.2 Configuring



19/54

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 process before physically connecting these FFdevices to an active FF bus in process mode.

Example:

You wish to replace a defective FF device or a defective FF Link in a configuration withoutredundant FF Link while maintaining bus operation by an external LAS.

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 emptyspaces).

The following characters are not permitted: [ ' ] [ . ] [ % ] [ \ ] [ * ] [ ? ] [ : ].

Procedure

1. In the component view, select the SIMATIC station and double-click the "Hardware" objectin 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 thePROFIBUS 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 participant address for the PROFIBUS DP in the "Parameters" tab of theProperties 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 with a double-click on the FF Link .

6. Click "OK".The interface module is created with a Foundation Fieldbus: FF subsystem.

Engineering

4.2 Configuring



20/54

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

8. Click "OK".The settings are applied.

9. Double-click theFOUNDATION FIELDBUS

in the current PCS 7 profile.

10.Select the FF device in the folder > > .

11.Drag the required FF device to the FF subsystem.The "Properties FF interface FF device" dialog box opens.

12.Enter the address of the FF device in the system in the "Parameter" tab.

13.Click "OK".You may receive the message that changes have to be made.

14.Select the inserted FF device.

15.For devices to be operated as Backup Link Master :

Select the menu command Edit > Object Properties.

Select the "Parameters" tab.

Activate the "Backup Link Master" check box.

Click "OK".

16.Select the inserted FF device.

17.Select the required I/O data in the address table of all function blocks.Multiple selection is typical for Windows.

18.Select the menu commandAssign address

from the shortcut menu.Addresses are assigned for the selected functions.You may have to change the start address.

You can find information on this in section "Device addresses (Page 9)".

Engineering

4.2 Configuring



21/54

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

20.Select Station > Save and Compilefrom the menu.

Note

Downloading

The device can be downloaded, provided that the "Address" and "TAG" in the configurationcorrespond the settings of the FF device.

Checking the bus parameters

HW Config checks whether the bus parameters have to be changed when you add a new FFdevice. If changes are required, the message "Change bus parameters" will be displayed. Youcan 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

Makrozyklus

Note

Checking the macrocycle

Check the settings of the macrocycle.

You can find additional information on this in the following sections:

Section "Bus parameters (Page 28)"

Section "How to set the bus parameters (Page 33)"

Engineering

4.2 Configuring



22/54


Manufacturer information of the FF device.

Section "How to assign parameters of the FF devices (Page 26)"

Section "Nodes in the FOUNDATION Fieldbus (Page 13)"

Section "How to configure FF internal interconnections (Control in the field) (Page 25)"

SIMATIC; SIMATIC PDMdocumentation; 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.

Make sure that you do not exceed the permitted number of interconnections at the FF segmentduring configuration. The configured interconnections are added:

Interconnections with the process image

CiF interconnections

Changing the configuration

SeparatingFOUNDATION Fieldbus from PROFIBUS DPIf you want to separate the interface module for the FOUNDATION Fieldbus from PROFIBUSDP in HW Config, observe the following:

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 not taken into account when you compile and download the automationsystem.

Changing interconnections - Impact on communication

The FF device must be restarted when you change (device-internal) interconnections. TheFF 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 separatedfrom PROFIBUS DP, to an automation system (behind PROFIBUS DP), observe the following:

Engineering

4.2 Configuring



23/54

Interconnections between the FOUNDATION Fieldbus and the automation system can berestored.

Address conflicts caused by interim configuration will be detected. A dialog box showsoptions 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.

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 withthe automation system.

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 menu command "Assign address" in the shortcut menu.The " Properties" dialog box opens.You can edit the entries, if necessary.

4. Click "OK".

CAUTION

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. Checkthe symbolic address assignment afterwards."

It is imperative that you perform this check and make any necessary corrections.

Engineering

4.2 Configuring



24/54

4.2.4 Interconnection Editor dialog box

Note

Menu command Start Interconnection Editor

This menu command is 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 (FF) communication inthis dialog. The automation system does not participate in this communication. The name ofthis function is "Control in the field" (CiF). CiF can be used to execute technological functionsin an FF segment.Configure each CiF interconnection (hereafter referred to simply as interconnection) in the"Interconnection Editor" dialog.

Note

Internal device interconnections

FF devices have internal device blocks, such as measuring sensor, controller. The internaldevice interconnection of these blocks means that there is no communication load on the FFsegment.

Structure

The "Interconnection 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 theFF segment. Inputs are the target of an interconnection.

Interconnection columnThis 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 and the available outputs in the network view of theFF segment. Outputs are the source of an interconnection.

Buttons

Button Function

"Addinterconnection"

Click this button to add an interconnection to the column "Interconnections".

"Deleteinterconnection"

Click this button to delete an interconnection.

Engineering

4.2 Configuring



25/54

Button Function

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

Icons

Icon Displayed object

FF segment

FF Link

FF device

Block within an FF device

Inputs and outputs Status

Analog input Not interconnected

Analog input Interconnected

Digital input Not interconnected

Digital input Interconnected

Analog output Not interconnected

Analog output Interconnected

Digital output Not interconnected

Digital output Interconnected

See also

How to configure FF internal interconnections (Control in the field) (Page 25)

4.2.5 How to configure FF internal interconnections (Control in the field)

Requirements

FF devices have been created in the project.

Addresses were assigned for signals required from the function blocks of the FF devices.

Procedure

1. Open configuration in HW Config.

2. Select the interface module for the FF Link (IM 153-2 FF).

Engineering

4.2 Configuring



26/54

3. Select the SIMATIC PDM > Start Interconnection Editorcommand from the shortcut menu.The "Interconnection Editor" dialog opens.

4. Search for the source of an interconnectionfor each interconnection in the tree structure"Outputs" and search for the targetin the tree structure "Input".

5. When you have selected an interconnection, click "Add interconnection".The FF-internal interconnection is added to the "Interconnection" column.

Note

Deleting an interconnection

Select a row in the "Inputs and interconnections" list.Click "Delete interconnection".

6. Repeat steps 4 and 5 for other interconnections.

7. When you have created all interconnections, click "Save".The interconnections will be saved in the project.

Downloading

The schedule for the FOUNDATION Fieldbus is calculated automatically during the downloadto the FF devices.



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 devicedescription assigned to the object. Device-specific information can be found in the OnlineHelp 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.

Engineering




27/54

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

Before you assign the parameters of the FF devices for the first time, you will have to readout the device data directly from the FF device once. This step is necessary because theEDD files do not contain standard values for the device data of the FF devices.

Proceed as follows:

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. Execute the Edit > SIMATIC PDM > Upload to PG/PCmenu command.

3. Activate the following check box in the "Upload to PG/PC" dialog box:

If you want to read the device data of an FF device:"Object with all subordinate objects" check box.

If you want to read the device data of all FF devices on the FF segment:"Object with all subordinate objects and networks" check box

4. Click "Start".

Engineering




28/54

Procedure

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 theEdit > Open object

menu commandin the process device plant view or process device network view.SIMATIC PDM starts.

In the structure view, select the function block in which you want to change theparameters.

Make your changes in the parameter table.

3. Select the Station > Savecommand.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 ormore FF devices (download to devices) or enables device parameters to be uploadedfrom the FF devices to the computer and saved on request (upload to PG/PC).


Manufacturer information of the FF device.


4.3.2 Bus parameters

Faultless operation of the components on the FF subsystem is only ensured if the parametersfor the bus profile are compatible with each other. You should therefore only change the defaultvalues if you are familiar with parameter assignment of the bus profile for FF.

Engineering




29/54

The bus parameters can be set depending on the bus profile.

Bus parameters that cannot be changed are grayed out.

Bus parameters are always displayed only as offline values, even if there is an onlineconnection to the PLC.

The displayed parameters apply to the entire FF subsystem and are briefly explained below.

System Management Timers area

FF is a clocked bus system.

Three timers (T1, T2, T3) are integrated in the System Management Information for monitoringpurposes. These timers are used to control the schedule on the FF segment; they ensure thateach FF device has sufficient time for actions and data transmission.

In PCS 7, by default, timers T1 and T3 operate on the interface module (LAS).

Timer T2 operates on the FF devices.

Rule

: T2 >= T3 + 3*T1

Engineering




30/54

Bus parameters Setting range (default

setting)

Meaning and limiting values

T1Inter SequenceTimer

-(480 000

corresponds toapproximately 15 s)

The parameter T1 specifies the number of clock cycles that an interface module(or an LAS) waits for a response from an FF device.

If the set number of clock cycles is exceeded, the service for this FF device willterminate with an error message.

T2

Set AddrSequence Timer

T2 >= T3 + 3*T1 (host)

(2880000

corresponds toapproximately 90 s)

The parameter T2 specifies the number of clock cycles that is available to anFF device for actions and data transfer. Any unperformed actions and datatransmissions are cancelled.

FF devices newly connected to the FF segment can only be detected if the valueT2 is sufficiently dimensioned.

T3

Set Addr WaitTimer

-

(1 440 000

corresponds to

approximately 45 s)

Parameter T3 corresponds to a waiting time (number of clock cycles).

On expiration of this waiting time the interface module (or LAS) checks the FFdevices that are recognized as new on the FF.

Node Polling area

Bus parameters Setting range (default

setting)

Meaning and limiting values

First UnpolledNode

20 < FUN < 232 FirstUnpolledNodeId (FUN)

(Default setting in SIMATIC STEP 7 / PCS 7: FUN = 36)

This parameter specifies the first device address that is not processed (notpolled) by the LAS.

Number ofConsecutiveUnpolled Node

NUN = 232 - FUN

NumConsecUnpolledNodeId (NUN)(Default setting: NUN = 232 - 36 = 196)

Range of consecutive device addresses not in the polled range.

In SIMATIC STEP 7 / PCS 7 (Unpolled Bereich):

Default setting of 36 - 231

Other bus parameters area

Select the checkbox to set the parameters:

Checkbox "Automatic calculation"The bus parameters are automatically set on the basis of the current configuration.

Checkbox "Manual entry"You can change the following parameters for each specific system.

Engineering




31/54

Bus parameters Setting range (default) Meaning and limiting values

Slot Time 1 - 512

(8)

This parameter specifies how fast the FF device can reply upon receipt of a

PDU. The required setting can be derived from the EDD of the FF devices.Assign parameters to this value in such a way that the minimum value is greaterthan the maximum Slot Time of every FF device on the FF segment.

ST >= ST of each FF device of the segment

Per DLPDU PhLOverhead

2 - 63

(2)

The parameter defines the delay between the following data records of aconnection to the FF segment:

End of the last octet

Beginning of the first octet of other data records

MaximumResponse Delay

1 - 11

(10)

This parameter specifies how fast the FF device can reply upon receipt of aPDU. 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 greaterthan the ratio of Maximum Response Delay Slot Time and Slot Time of everyFF device on the FF segment.

MRD(FF segment):MRD >= MRD of each FF device of the segmentSelection: 1 to 11

Minimum InterDLPDU Delay

0 - 120

(16)

This parameter specifies the minimum interval between two frames on the FFsegment. Each FF device has a minimum value of MinInterPDUDelay. Thisvalue is stored in the EDD.

Assign parameters to this value in such a way that it corresponds to at least themaximum value of Minimum inter DLPDU Delay of all the FF devices on the FFsegment.

Minimum inter DLPDU Delay (segment) > max Minimum inter DLPDU Delay(FF device)

The minimum value for this parameter is determined by the maximum value ofall the FF devices in the FF segment.

PreambleExtension

0 - 7

(2)

Each data record of an FF connection starts with a preamble octet which is usedby the FF devices (receiving nodes) for clock synchronization. The number ofpreambles (s) can be extended when setting this parameter. The default valuein PCS 7 is 2; networks including digital repeaters may require larger values.

Selection: 0 to 7

Time Sync Class 0 - 7

(4)

This parameter defines the quality of the clock accuracy of an FF device. Thusit also defines the periods for time synchronization of an FF device.

The maximum value supported by an FF device is stored in the EDD.

Set this value to the lowest common class of all FF devices on the FF segment(slowest time).

Class: 0 to 7 (4 equal to 1 ms)

Engineering




32/54


Maximum

SchedulingOverhead

16 This parameter extends the time that may be used by the LAS for processing

the schedule. The parameters unit is the transmission duration of one octet.The following times should be included in the duration:

The time allocated for each scheduled activity

The time to determine whether a device on the FF segment can serve as anLAS.

The time for the organization of the schedule.

The parameter will be checked with the configured value in the LAS domainduring downloading of the FF segment.

The minimum value for this parameter is determined by the maximum value ofall the LAS-capable FF devices in the FF segment.

Max Inter ChanSignal Skew

0 - 7(0)

This parameter indicates the maximum permitted time offset of the data that adevice 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.

Selection: 0 to 7

Post Trans GapExtension

0 - 7(0)

There will be an interruption of the signal transmission in 4-bit transmission timesafter each transmission.

Use this parameter to increase this interruption in signal transmission byadditional 4-bit transmission times. The value range is (0 .. 7) * 4 * Tb.

A value greater than 0 increases PerDlpduPhlOverhead.

Selection: 0 to 7

DefaultMinimum Token

Delegation Time

32 - 32767

(86)

The time required for an FF device to process all tasks. The parameters unit isthe 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 (greaterthan Default Token Holding Time).

An FF device can only be processed if it keeps the token for longer thanstipulated by the "Default Minimum Token Delegation Time" parameter.

Default TokenHolding Time

276 - 65000

(276)

Time period assigned to an FF device by the LAS for the following tasks:

acyclic bus traffic

System Management

Alarms and events

Target TokenRotation Time

1 - 60000

(60000)

Within this time all FF devices must have received the token for acyclic datatransfer once. If the actual token rotation time is higher than the configured valuefor 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)

LinkMaintenanceToken HoldingTime

292 - 65000

(336)

Period of time which the LAS uses within a token rotation for checking a link.This time period contains the following processes:

find new FF devices

send LAS status telegrams

TimeDistributionPeriod

10 - 55000

(5000)

Time period for forwarding time service telegrams (in milliseconds)

Time distribution PDU's will be sent on the bus in 95% or less of that time period.

Engineering




33/54


Maximum

Inactivity toclaim LAS Delay

1 - 4095

(100)

Delay time (device-internal)

Time which an LAS-capable FF device needs from the detection of the failureof the LAS until a request is sent for takeover of the LAS (ClaimLAS).

The minimum value for this parameter is determined by the maximum value ofall the LAS-capable FF devices in the FF segment.

LAS DatabaseDistributionPeriod

100 - 55000

(5000)

Time period for distribution of the LAS database (in milliseconds)

This time period covers the times for the following processes:

Establishment of the connection to LAS-capable FF devices in the FFsegment

Distribution of the LAS database to FF devices in the FF segment

Recommendation

: Set a value between 1000 and 5000.

Ap Clock SyncInterval

0..255(10)

Application Clock Synchronisation Interval is a special parameter for thosedevices 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. Onlyone 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 CountLimit

0 - 255

(3)

Maximum number of failed communication attempts.

If the value is exceeded, the device in question terminates communication withthe FF segment.

0: Checking is turned off in the device.

4.3.3 How to set the bus parameters

Settings of the FOUNDATION Fieldbus are configured via HW Config or NetPro in PCS 7systems. The necessary bus parameters can automatically be determined 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:

One number for the project

One number for the subnetIn case you want to go online with a PG/PC without a consistent project, you need to know theS7 subnet ID. When you print the network configuration, the S7 subnet ID will also be printed.

Engineering




34/54

Connecting a Linkmaster (LAS) to an FF segment in operation

Please note the following if you want to physically connect a device capable of operating as

Linkmaster (LAS) to an FF segment that is currently in operation.

Note

Set the bus parameters separately before you connect this device (field device or FF Link).

Typical situation:

Replacement of an FF Link in a non-redundant configuration. The functions on the FF segmentare maintained by a field device that can operate as Linkmaster (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 menu commandEdit > Object Properties

.The "Properties FF Subsystem" 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 section "Bus parameters (Page 28)".

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 beassigned to FF devices in a system.

Following a scan of the "Unpolled Bereiches", you should set the default value (36)again.

6. Select theFile > Save

menu command.These changes are applied to the PCS 7 project.

Engineering




35/54

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

Calculate schedule cancelled

If the schedule calculation could not be executed successfully, you receive an error message.Check the settings of the bus parameters.

NOTICE

Error message Cancel Schedule Calculation: Error at bus parameter

The error message "Cancel Schedule Calculation: Error at bus parameter" is issued bySIMATIC PDM if there are too many configured interconnections.

You can find additional information on this in the section "Additional notes on configuration(Page 22)".

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 theinput boxes ("acyclical percentage" and "macrocycle").Run the schedule calculation every time you make a change.

Requirements for downloading

Note

Observe the following if you have added new FF devices to the FF segment or if you want touse new parameters.

Online changes are not possible in these cases.

First, you have to configure all the interconnections.

If required, correct the macrocycle settings.

Engineering




36/54

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 thepercentage of acyclic communication. The FF specifications recommend that at least 50% ofthe bus time is kept free for acyclic communication.

For additional information, refer to the section "Nodes in the FOUNDATION Fieldbus(Page 13)".

Macrocycle tab

Whether the configuration is consistent is determined on the basis of the output values andthe required interconnections. The result is displayed graphically.

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 minimummacrocycle is set with a specified acyclical percentage.

Graphical display

Before downloading, click the "Calculate schedule" button. With the help of the display youcan check whether the configuration is consistent. The result is displayed graphically.

Display from left to right:

Left-hand areaThe colored area on the left-hand 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 recommendedin 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 recommendedin the FF specifications.

Right-hand areaThe colored area on the right-hand side indicates the percentage of cyclic communication.

Meaning of the colored areas

Yellow

Percentage of acyclic communication

Dark green

Percentage of cyclic communication Configuration isfree from errors.

Engineering




37/54

Light green and dark greenConfiguration is

free from errors

. The percentage of cyclic communication is displayed indark green. The light green percentage indicates the time that has been reserved for cyclical

communication but is not required.

You can reduce the time for the macrocycle of a specified acyclic portion.

Amber

Downloading the configuration with the selected settings results in a high bus load.

Recommendation:Change the value marked in orange to modify the configuration in accordance with therecommendations of the Fieldbus Foundation.

Note

Restrictions to acyclic communication are possible.

RedDownloading the configuration with the selected settings results in a very high bus load.

Recommendation:Change the value marked in red to modify the configuration in accordance with therecommendations of the Fieldbus Foundation.

Note

Acyclic communication errors are possible.

Do not download this configuration.

Setting the macrocycle

1. Select the FOUNDATION Fieldbus in the SIMATIC Manager in HW Config.

2. Select the menu command Edit > Object Properties.The "Properties - FF subsystem" dialog window opens.

3. Set the 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. 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 > Savemenu command.These changes are applied to the PCS 7 project.

Engineering




38/54

Adjusting the macrocycle

If the macrocycle has to be adjusted after all the FF devices have been downloaded, then all

FF devices have to be downloaded again. Observe the following especially after the followingactions:

Adding FF devices

Adding new interconnections with the Interconnection Editor

Using new connections via the CPU

Using new I/O data

Calculate schedule

The schedule is calculated in PCS 7 with the following actions:

The schedule is automatically calculated when you download the configuration.

When you click the "Calculate schedule" button in the "Properties - Foundation Fieldbus"on the "Macrocycle" tab.

Interconnection dependency

Only interconnected function blocks are edited and added to the schedule calculation.

Changes made with SIMATIC PDM become effective only for interconnected functionblocks.

The following blocks are considered when diagnosing FF devices:

Resource blocks

Transducer blocks

Interconnected function blocks

4.4 Using the applications

4.4.1 Overview

In HW Config you have reproduced the configuration of the FF segment in the system.

With FF devices, you have to interconnect the signals of the function blocks individually. Thecreated symbolic names facilitate further configuration.

Create the charts for the automation system in CFC.

You have to interconnect the signals to technological blocks so that they are available onthe operator station.

You can then commission them. When all the components have been compiled anddownloaded, the functions of the FF devices are available on the operator station.

Engineering




39/54

4.4.2 How to identify FF devices with SIMATIC PDM

With the SIMATIC PDM Lifelist, you can determine the following information about an FF

segment without a project being present on the computer: 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?

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.

Working with SIMATIC PDM LifeList

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

4. Select the menu command Edit > SIMATIC PDM > StartLifeList .The "LifeList" dialog window opens.

5. Select the "Start" menu command.

The network is scanned. All detected FF devices are displayed in the table. The TAG (name)is depicted in the tree structure. Additional columns list addresses, device types, devicenumbers, and manufacturers.

Note

Status

If the data has not been updated, see the following:

The tree structure has been deleted and will be rebuilt.

The symbols will change.



Engineering




40/54

4.4.3 How to define the device ID of the FF devices (TAG name and address)

With SIMATIC PDM, you can find the FF devices that are connected to the FF segment with

the Start LifeList menu command. Use the "Assign address and TAG..." button to change thefollowing 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 adevice. Then assign the parameters for device identification to the FF device.

Requirement

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 STEP 7 / PCS 7 , the FF devices with addresses from 36 to 231 are notprocessed by default (unpolled range). This range can be reduced by changing the busparameters.You can find information on this step in section "How to set the bus parameters(Page 33)".

Procedure

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

4. Select the shortcut menu commandOpen Object

.The "SIMATIC PDM" dialog box opens.

5. Select the FF Link.

6. Select the menu command Edit > SIMATIC PDM > StartLifeList .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 (backup device) in the tree structure.

Engineering




41/54

9. Click the "Assign address and TAG ..." button.Input boxes for the current and new parameters are displayed in the dialog.

Enter the current and new address of the FF device in the plant configuration. Enter the current and new device designation (TAG) of the FF device in the system

configuration.

10.Click "Transfer".

Note

Restart

Changing the address will restart the device.

Note

Address or tag occupied

If the address or TAG is occupied, then the action will not be performed. An appropriatemessage 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 has address 30 in HW Config.

Downloading

To ensure that all configured parameters and connections are available for the FF device, youwill have to download the FF device.

4.4.4 How to edit the symbols

You can easily adapt the symbolic names and comments for signals.

Requirements

The project is open in SIMATIC Manager in thecomponent view

.

Symbolic names were assigned for the inputs and outputs during configuration of the FFdevices.

Engineering




42/54

Procedure

1. Select the folder > >

in the tree structure.

2. Select the "Symbols" object in the list.

3. Select the menu command Edit > Open Object.The "Symbol Editor" dialog box opens.

4. Make your changes.

Note

A maximum of 24 characters is permitted for a symbol.

Example: Symbol = "Status_Measurement"

5. After editing, select the menu command Table > Save.

4.4.5 How to configure interconnections to the FF devices

PCS 7 supports you during the configuration of FF devices by providing prepared templatesfor 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 theProcess Control System PCS 7; Advanced Process Librarydocumentation.

Channel blocks for FF devices

Use the channel blocks of the PCS 7 Advanced Process Library (APL) to interconnect thesignals of FF devices.

One channel block should be used 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.

Engineering




43/54

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 manualProcess Control System PCS 7; Engineering System.

4.4.6 Configuring the OS

Information about the configuration of process pictures and diagnostics with operator stationsis available in the Process Control System PCS 7; Operator StationConfiguration Manual.

Engineering




44/54


45/54

Commissioning

5

Commissioning begins with connecting and downloading the hardware. Next, carry out theconnection and function test. Finally, the system is optimized. Values have to be simulated forsome tasks.

Information which supports you in these tasks is available found below.


Refer to the device-specific documentation for information on connecting the FF devices.

5.1 Compile and download

In a PCS 7 system you compile and download the entire program of the process control systemwith the engineering station.

Compile

The central function for this can be obtained by selecting the menu command PLC > Compileand Download Objects...

in the SIMATIC Manager.

Options for compiling and downloading the AS

The following options are available for compiling and downloading programs:

You can use the commands for a single SIMATIC station.

You can compile and download multiple SIMATIC stations with a single command.

You download the device parameters independently of the AS.

You can find additional information about this in Section "How to download objects in the FF

segment (Page 46)".

Options for compiling and downloading the OS

The following options are available for compiling and downloading the operator station(s):

You can compile and download operator stations one-by-one.

You can compile several operator stations at the same time and download them on theirown.

You can compile and download several operator stations at the same time.



46/54


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 How to download 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)

Replacing devices

Note that you have several options for replacing devices with SIMATIC PDM.

Replacement of a device with one of the same type

Replacement of a device with a similar one

Replacement via address change

Requirement

You will have to read in the device parameters to the Engineering System before you assignthe 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 wantto use parameters of additional function blocks.

The FF segment is stopped for a short time during download.

First, you have to configure all the interconnections.

If required, correct the macrocycle settings.

Note

Downloading function blocks

It is not necessary to download an entire device if there are only minor changes. You candownload a group of function blocks or one individual function block for an FF device.

Commissioning




47/54

Downloading

Use the following menu commands to download the respective data to the system.

Menu Command CPU data Schedule, bus

parameters and

interconnections

Device parameters

For a CPU with FF Link , you alwaysdownload thehardware configuration to HW Config.

PLC > Download to Module

Hardware

configuration is

downloaded

Downloading -

The menu command PLC > Compile and DownloadObjects...in the SIMATIC Manager.

Program and

connections are

loading

- -

In SIMATIC PDM, select the FF LinkDevice > Download to devices

Select the "Object with all subordinate objects andnetworks" check box in the "Download to devices"dialog.

- - All FF devices will bedownloaded.

Select the FF device in SIMATIC PDM Device >Download to devices

Select the "Object with all subordinate objects" checkbox in the "Download to devices" dialog.

- -

The FF device is

downloaded

NOTICE

You can download changes to the automation system in "RUN" mode (CIR). The FF segmentwill always be stopped if the schedule or CiF interconnections will be altered by the download.

Downloading

It is not possible to exclude the FF segment when downloading, e.g. if the configuration in theFF segment was not changed. Follow these steps to disable the download function:

1. Open the hardware configuration in SIMATIC Manager.

2. Open the object properties of the FF Link.

3. In the "Load FF segment" tab, select the "Only load FF Link and FF devices when modified"check box.

NOTICE

Check boxes on the Download FF segment tab

Before a complete download of an FF segment, the "Always load FF Link and FF devices"check box must be selected in the "Load FF segment" tab.

Commissioning




48/54

See also

How to assign parameters of the FF devices (Page 26)

5.2 Diagnostics options

Diagnostics on the FF in PCS 7

PCS 7 uses staggered diagnostics.

With the maintenance stationStatus overview and status messages for FF Link and FF devices

Detailed diagnostics for FF Link and FF devices with SIMATIC PDMConfigured maintenance information

In SIMATIC ManagerStatus overview for FF Link and FF devices

In HW ConfigStatus overview for FF Link and FF devices

With SIMATIC PDMDetailed diagnostics for FF Link and FF devices

LED displays on the FF LinkStatus of FF

Displays on the FF devicesRead the device manufacturer information on this.


Configuration Manual Process Control System PCS 7; Operator Station

Section "How to identify FF devices with SIMATIC PDM (Page 39)"

SIMATIC;FF LinkOperating Instructions

FF devices documentation

5.2.1 How to perform diagnostics

An example of diagnostics in the SIMATIC Manager and detailed diagnostics with SIMATICPDM is shown below.

Requirements for diagnostics

FF devices have been created.

An online connection to the FF device can be established.

Commissioning




49/54

Diagnostics in the SIMATIC Manager

1. In SIMATIC Manager, open the project in the process devices network view.

2. Select the FF device.

3. Select the menu command Edit > Object Properties.The " 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 deviceis determined and displayed. The following information on FF device communication isdisplayed:

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 SIMATICManager:

Process devices network view

Process devices plant view

Detailed diagnostics with SIMATIC PDM

1. Select one of the following views:

Process devices network view

Process devices plant view

2. Select the FF device.

3. Select the menu commandEdit > Open Object

.The "SIMATIC PDM" dialog box opens.

4. Select the Diagnostics > Update diagnosticsmenu 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.

Commissioning




50/54


51/54

Redundancy and system changes in operation

6

6.1 Redundancy

The basic configuration of redundant FF segments is the same as the configuration ofPROFIBUS PA. During configuration, the necessary couplers are part of the FF Link.Additional information is available in the SIMATIC; Process Control System PCS 7; Fault-tolerant Process Control Systemsdocumentation in the section "Redundant PROFIBUS PA".Possible redundancy 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 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.

Configuration

You configure only the FF devices and the FF Link on PROFIBUS DP. The necessaryconfiguration steps are described in section "How to place FF devices on the FOUNDATIONFieldbus (Page 18)".

S7-400H as DP Master

The following AS components can operate as DP Master: CP443-5 ext.

PROFIBUS DP connection of the CPU

The following requirements are met regarding DP Master systems:

The DP Masters edit the same user program.

The DP Masters have the same parameter settings and configuration for the interfacemodules.



52/54


You can find more information on redundant design of the PROFIBUS PA in the

documentation SIMATIC; Process Control System PCS 7; Fault-Tolerant Process ControlSystemschapter "Redundant PROFIBUS PA".

Information on the hardware design of the FOUNDATION Fieldbus is available in thedocumentation SIMATIC; Bus links; FF Linkbus link.

Information on the design of the redundant fieldbus with AFD/AFS is available in thedocumentation SIMATIC; Bus links; DP/PA coupler, active field distributors, DP/PA-Linkand Y-Link.

6.2 Changing the system in run

See the following information if you want to make changes to an FF segment in an existingsystem.

Changes in run

The following changes are possible:

Changing the DP Master system

Changing parameters of the FF devices

Inserting or removing entire FF segments

Changes in run

Note

The CPU will stay in RUN with the following actions, but communication with the FF segmentwill be interrupted.

Inserting or removing FF devices

Changing connections between FF devices

Changing bus parameters

CAUTION

STOP of CPU required

Inserting new blocks of an existing FF device.


The whole sequence of a system modification and the requirements that must be met for it aredescribed in detail in the documentation SIMATIC; Modifying the System during Operation viaCiR.

Redundancy and system changes in operation

6.2 Changing the system in run



53/54

Index

Field device in SIMATIC PDMIntegrate, 40

XE \* MERGEFORMAT , 25

A

Address, 40

C

CiF, 25Configuration via PDM, 19

D

Downloading, 47

H

HW ConfigStart Interconnection Editor, 24

I

Integrate, 19, 40Field device in SIMATIC PDM, 40PROFIBUS device in SIMATIC PDM, 19

Interconnection Editor, 25Starting, 24

L

Load FF segmentTab, 47

N

Name, 40

O

OptionConfiguration via PDM, 19

P

PROFIBUS device in SIMATIC PDM, 19Integrate, 19

Publisher, 7

S

Schedule, 7SIMATIC Manager

Start InterconnectionEditor, 24SIMATIC PDM, 19

Integrate field device, 40Integrating a PROFIBUS device, 19Start Interconnection Editor, 24

Subscriber, 7

T

TabLoad FF segment, 47

TAG, 40



54/54

Documents

PCS 7 in-practice FoundationFieldbus