SIMATIC Engineering 4 FOUNDATION Fieldbus Process …...Basics of the FOUNDATION Fieldbus 2 2.1...

SIMATIC

Process Control System PCS 7FOUNDATION Fieldbus

Commissioning Manual

Requirement: SIMATIC PDM V8.0 SP1

Valid for the software package Process Control System; SIMATIC PCS 7 as of V8.0 Update 1 including SIMATIC PDM V8.0 SP1

03/2013A5E03880935-02

Introduction 1

Basics of the FOUNDATION Fieldbus

2

System planning 3

Engineering 4

Commissioning 5

Redundancy and system changes in operation

6

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

NOTICEindicates 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 PersonnelThe 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 productsNote 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.

TrademarksAll 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 LiabilityWe 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 AGIndustry SectorPostfach 48 4890026 NÜRNBERGGERMANY

A5E03880935-02Ⓟ 02/2013 Technical data subject to change

Copyright © Siemens AG 2013.All rights reserved

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..........................................................................................................9 2.3 Device addresses........................................................................................................................11 2.4 Block model of device parameters..............................................................................................13 2.5 Contact partner............................................................................................................................16

3 System planning.........................................................................................................................................17 3.1 Nodes in the FOUNDATION Fieldbus.........................................................................................17 3.2 Configuration...............................................................................................................................19

4 Engineering.................................................................................................................................................21 4.1 Prepare........................................................................................................................................22 4.1.1 How to integrate a device description..........................................................................................22 4.2 Configuring..................................................................................................................................23 4.2.1 How to place FF devices on the FOUNDATION Fieldbus...........................................................23 4.2.2 Additional notes on configuration................................................................................................27 4.2.3 How to assign addresses for FF device signals..........................................................................28 4.2.4 “Interconnection Editor" dialog box..............................................................................................29 4.2.5 How to configure FF internal interconnections (Control in the field)............................................31 4.3 Parameter assignment................................................................................................................33 4.3.1 How to assign parameters of the FF devices..............................................................................33 4.3.2 Bus parameters...........................................................................................................................34 4.3.3 How to set the bus parameters....................................................................................................39 4.3.4 How to plan the macrocycle........................................................................................................42 4.4 Using the applications.................................................................................................................45 4.4.1 Overview......................................................................................................................................45 4.4.2 How to identify FF devices with SIMATIC PDM..........................................................................45 4.4.3 How to define the device ID of the FF devices (TAG name and address)..................................46 4.4.4 How to edit the symbols..............................................................................................................47 4.4.5 How to configure interconnections to the FF devices .................................................................48 4.4.6 Configuring the OS......................................................................................................................49

5 Commissioning...........................................................................................................................................51 5.1 Compile and download................................................................................................................52 5.1.1 How to download objects in the FF segment...............................................................................53 5.2 Diagnostics options.....................................................................................................................56 5.2.1 "Mode" and "Status" menu command.........................................................................................56 5.2.2 How to perform diagnostics.........................................................................................................57

FOUNDATION FieldbusCommissioning Manual, 03/2013, A5E03880935-02 3

6 Redundancy and system changes in operation..........................................................................................59 6.1 Redundancy................................................................................................................................59 6.2 Changing the system in run.........................................................................................................61

Index...........................................................................................................................................................63

Table of contents

FOUNDATION Fieldbus4 Commissioning Manual, 03/2013, A5E03880935-02

Introduction 1SIMATIC 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 station via the FF Link.

SIMATIC PCS 7 supports the connection of FF devicesSIMATIC 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 (read section "Device integration with EDD (Page 9)")

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

● PCS 7 Asset Management


Required basic knowledgeThis 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 usersUsers who have configured only FF up to now can acquire necessary knowledge of PCS 7 using the PCS 7 documentation. You can find an introduction to working with PCS 7 in the SIMATIC; Process Control System PCS 7; PCS 7 - Getting Started manual.

Introduction


Basics of the FOUNDATION Fieldbus 22.1 Basic knowledge of FOUNDATION Fieldbus

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 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 fieldbus couplers possible) via FF Link (IM 153-2 FF) .

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


● Communication typesTwo types of communication are used with FF:

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

– acyclic communicationAcyclic communication is used for transmitting unscheduled information. Examples include 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 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.

● MacrocycleThe macrocycle is a time period which 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 specifications recommend that at least 50% of the bus time is kept free for acyclic communication.

Basics of the FOUNDATION Fieldbus2.1 Basic knowledge of FOUNDATION Fieldbus


2.2 Device integration with EDDFF devices are integrated in the control system in PCS 7 using SIMATIC PDM.

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

Please speak with your contact (Page 16) about this.

LiabilitySiemens 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 the import catalog

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

Basics of the FOUNDATION Fieldbus2.2 Device integration with EDD


Information in device descriptionsDevice 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.

Additional information● IEC 61804-2

● IEC 61804-3

● Section "Block model of device parameters (Page 13)"

Basics of the FOUNDATION Fieldbus2.2 Device integration with EDD


2.3 Device addresses

Address ranges in STEP 7 and PCS 7The following table shows the distribution of address ranges at the FF segment:

Addresses Information on the address range0 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. You can find information on this in section "How to define the device ID of the FF devices (TAG name and address) (Page 46)".

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 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 PDMNote for users: Make sure that there are always free addresses in this range. Otherwise, FF devices can no longer be reached 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 addressesConnected FF devices will be detected automatically at the FF segment.

In case of an address conflict, one of the FF device 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.

Basics of the FOUNDATION Fieldbus2.3 Device addresses


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.

Basics of the FOUNDATION Fieldbus2.3 Device addresses


2.4 Block model of device parametersThe parameters (functions and data of an FF device) are assigned block types in the device descriptions 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

NoteParameter assignment with SIMATIC PDM

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

Basics of the FOUNDATION Fieldbus2.4 Block model of device parameters


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 blockFunction 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. Accesses to the functions and their inputs and outputs are defined 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 be described 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 modelIn PCS 7, applications in the PC stations assume the functions of FF-specific objects:

Engineering station



● Configuration of the FOUNDATION Fieldbus

● Interconnection of the FF devices

– Interconnections between the FF devices

– Interconnection across fieldbuses

Operator stations or maintenance station

● Output of signals

– Alarms

– Events

● Monitoring

– Process control

– Maintenance

● Long-term archiving



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 AGCustomer SupportD-90475 Nuremberg, Germany

E-mail: [email protected] 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. See "List of integrated devices". This is available on the "SIMATIC PDM Device Library 1#2012" DVD in the \Manuals directory.

● Post-installations and additional information on SIMATIC PDM are available on the Internet at http://pcs.khe.siemens.com/pdm (http://pcs.khe.siemens.com/pdm)

Basics of the FOUNDATION Fieldbus2.5 Contact partner


http://www.siemens.com/automation/service&support

http://www.siemens.com/automation/service&support

http://pcs.khe.siemens.com/pdm

System planning 33.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 imageAn 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 can be used for inputs for each FF device.

Nodes in an FF segmentThe maximum number of nodes in an FF segment depends on the system requirements with regard to update times. Typically, 3 to 7 FF devices are integrated in an FF segment (maximum 31).

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 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 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 1 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 communication1050 ms (recommended 70 %), 450 ms (recommended, at least 50 %)

– recommended macro cycle = between 1500 ms and 9000 ms

I/O dataThe parameters, inputs and outputs of FF devices are distributed over function blocks. An FF device can have several function blocks. Only configure the required I/O data of an FF device. The number of processed function blocks has an effect on the macro cycle.

System planning3.1 Nodes in the FOUNDATION Fieldbus


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

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

● Line

● Redundant configuration (see also section "Redundancy (Page 59)")

Line lengths● An FF segment is limited to 1900 meters. 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 meters. The length depends on the cable type.

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

Number of branch lines (longer than 1 m) Maximum length of a branch line1-12 120 m13-14 90 m15-18 60 m19-24 30 m25-31 1 m

Intrinsically safe configuration

Note

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

System planning3.2 Configuration


Additional information● Operating instructions SIMATIC; Bus links; FF Link bus link● Manual Process Control System PCS 7; Fault-tolerant Process Control Systems

System planning3.2 Configuration


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.

Procedure1. Open 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 command File > 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 the DVD.

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 integrate.The default directory is "Foundation Fieldbus". All subfolders must remain activated for the "Foundation Fieldbus" directory.

NoteIntegrating device descriptions

Many FF devices require information that is stored in other device descriptions.

Recommendation:Integrate all device descriptions that provided with the SIMATIC PDM "Device Library" DVD.

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

Additional informationOnline help for SIMATIC PDM

Engineering4.1 Prepare


4.2 Configuring

4.2.1 How to place FF devices on the FOUNDATION Fieldbus

Example of an FF configuration

Recommendation for using symbolic namesAssign 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.

Requirement● SIMATIC PCS 7 is installed.

● SIMATIC PDM is installed.

● 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 section "How to integrate a device description (Page 22)".

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

Engineering4.2 Configuring


Avoid address conflicts by externally assigned device addressesIn 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 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.

Changing device name with SIMATIC PDMAlways 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 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 participant 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 with a double-click on the FF Link .

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

7. Select the inserted FF Link.



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

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

10.Double-click the FOUNDATION FIELDBUS in the current PCS 7 profile.

11.Select the FF device in the folder <Manufacturer> > <Device Group> > <Device Type>.

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

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

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

15.Double-click on the inserted FF device. SIMATIC PDM opens.

– Select the top node in the tree structure.

– Select the menu command Edit > Object Properties.

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

16.Select the inserted FF device.

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

18.Select the inserted FF device.



19.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 on the block types in the section "Block model of device parameters (Page 13)". The following block types are used by default:● Resource blocks ● Function blocks ● Transducer blocks

Refer to the documentation of the device manufacturer for information about the required blocks and any necessary CiF interconnections.

20.Select the menu command Assign 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 11)".

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

22.Select Station > Save and Compile from the menu.

NoteDownload when "Address" and "TAG" match

You can download to the FF device, provided that the "Address" and "TAG" in the configuration correspond the settings of the FF device.

NoteDownload with unknown device address of the device in the plant

Select the following menu command in SIMATIC Manager to find the FF device in the plant: Edit > SIMATIC PDM > Start LifeList.

When you find the desired device, do the following:1. Select the menu command Devices > Assign address and TAG.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.



Checking the bus parametersHW Config checks whether the bus parameters have to be changed when you add a new FF device. 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: YesThe 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

NoteChecking the macro cycle

Check the settings of the macro cycle.

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

● Section "Bus parameters (Page 34)"

● Section "How to set the bus parameters (Page 39)"

Additional information● Manufacturer information of the FF device.

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

● Section "Nodes in the FOUNDATION Fieldbus (Page 17)"

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

● SIMATIC; SIMATIC PDM documentation; chapter "Working with the LifeList"

4.2.2 Additional notes on configuration

Device-specific number of interconnectionsThe 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 segment during configuration. The configured interconnections are added:

● Interconnections with the process image

● CiF interconnections



Changing the configurationSeparating FOUNDATION Fieldbus from PROFIBUS DP

If you want to separate the interface module for the FOUNDATION Fieldbus from PROFIBUS DP 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 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.

4.2.3 How to assign addresses for FF device signalsYou need to assign addresses to the FF device signals that you want to process further with the automation system.

Requirements● FF devices have been created in HW Config.

● The necessary FF device signals are known.



Changing the configuration1. 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 "<Signal> Properties" dialog box opens.You can edit the entries, if necessary.

4. Click "OK".

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 “Interconnection Editor" dialog box

NoteMenu 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 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 "Interconnection Editor" dialog.

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



StructureThe "Interconnection Editor" dialog box is divided into the following columns:

● "Inputs and interconnections" area

– "Input" columnThis column shows the FF devices and the available inputs in the network view of the FF 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" columnThis column shows the FF devices and the available outputs in the network view of the FF segment. Outputs are the source of an interconnection.

Buttons

Button Function"Add interconnection"

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

"Delete interconnection"

Click this button to delete an interconnection.

"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 StatusAnalog input Not interconnected

Analog input Interconnected

Digital input Not interconnected



Icon Displayed object Digital input Interconnected

Analog output Not interconnected

Analog output Interconnected

Digital output Not interconnected

Digital output Interconnected

See alsoHow to configure FF internal interconnections (Control in the field) ()

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

NoteRequired CiF interconnections

Refer to the documentation of the device manufacturer for information about any required CiF interconnections.

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

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

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

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

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

DownloadThe schedule for the FOUNDATION Fieldbus is calculated automatically during the download to the FF devices.

Additional information● Online help for SIMATIC PDM



4.3 Parameter assignment

4.3.1 How to assign parameters of the FF devicesYou configure FF devices in PCS 7 systems with SIMATIC PDM.

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

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. This step is necessary because the EDD 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/PC menu 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".

Engineering4.3 Parameter assignment


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

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

– Make your changes in the parameter table.

3. Select the Station > Save command.These changes are applied to the PCS 7 project.

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

Additional information● Manufacturer information of the FF device.

● Online help for SIMATIC PDM

4.3.2 Bus parametersFaultless 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.



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 online connection to the PLC.

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

"System Management Timers" areaFF 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 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



Bus parameters Setting range (default setting)

Meaning and limiting values

T1 Inter Sequence Timer

-(480 000 corresponds to approximately 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 will terminate with an error message.

T2Set Addr Sequence Timer

T2 >= T3 + 3*T1 (host)(2880000 corresponds to approximately 90 s)

The parameter T2 specifies the number of clock cycles that is available to an FF device for actions and data transfer. Any unperformed actions and data transmissions are cancelled.FF devices newly connected to the FF segment can only be detected if the value T2 is sufficiently dimensioned.

T3 Set Addr Wait Timer

- (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 FF devices that are recognized as new on the FF.

"Node Polling" area

Bus parameters Setting range (default setting)

Meaning and limiting values

First Unpolled Node

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 (not polled) by the LAS.

Number of Consecutive Unpolled 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" areaSelect 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.



Bus parameters Setting range (default) Meaning and limiting valuesSlot 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 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 Overhead

2 - 63(2)

The parameter defines the delay between the following data records of a connection to the FF segment:● End of the last octet● Beginning of the first octet of other data records

Maximum Response Delay

1 - 11(10)

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. ● Determine requirement for each FF device:

MRD(FF device)=MRDST/STAssign 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 Selection: 1 to 11

Minimum Inter DLPDU Delay

0 - 120(16)

This parameter specifies the minimum interval between two frames on the FF segment. Each FF device has a minimum value of MinInterPDUDelay. This value is stored in the EDD. Assign parameters to this value in such a way that it corresponds to at least the maximum value of Minimum inter DLPDU Delay of all the FF devices on the FF segment.Minimum inter DLPDU Delay (segment) > max Minimum inter DLPDU Delay (FF device)The minimum value for this parameter is determined by the maximum value of all the FF devices in the FF segment.

Preamble Extension

0 - 7(2)

Each data record of an FF connection starts with a preamble octet which is used by 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.Selection: 0 to 7

Time Sync Class 0 - 7(4)

This parameter defines the quality of the clock accuracy of an FF device. Thus it also defines the periods for time synchronization of an FF device. The maximum value supported by an FF device is stored in the EDD. Set this value to the lowest common class of all FF devices on the FF segment (slowest time).Class: 0 to 7 (4 equal to 1 ms)



Bus parameters Setting range (default) Meaning and limiting valuesMaximum Scheduling Overhead

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 an

LAS.● The time for the organization of the schedule.The parameter will be checked with the configured value in the LAS domain during downloading of the FF segment.The minimum value for this parameter is determined by the maximum value of all the LAS-capable FF devices in the FF segment.

Max Inter Chan Signal Skew

0 - 7(0)

This parameter indicates the maximum permitted time offset of the data that a device receives from several ports (redundant routes) via an H1 connection.Select a value between 0 and 7 4-bit transmission times.The value range is (0 .. 7) * 4 * Tb.Selection: 0 to 7

Post Trans Gap Extension

0 - 7(0)

There will be an interruption of the signal transmission in 4-bit transmission times 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.Selection: 0 to 7

Default Minimum Token Delegation Time

32 - 32767(86)

The time required for an FF device to process all tasks. The parameters unit is the transmission duration of one octet.Keeping to the schedule (controlled by LAS ) has the highest priority on the FF. The time available for an FF device should be sufficiently dimensioned (greater than Default Token Holding Time).An FF device can only be processed if it keeps the token for longer than stipulated by the "Default Minimum Token Delegation Time" parameter.

Default Token Holding 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 Token Rotation Time

1 - 60000(60000)

Within this time all FF devices must have received the token for acyclic data transfer once. If the actual token rotation time is higher than the configured value for Target Token Rotation Time, the LAS will increase the token priority. A Target Token Rotation Time value that is too small causes the failure of low-priority services. The following are low-priority services:● System Management● acyclic bus traffic (client-server connections)

Link Maintenance Token Holding Time

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

Time Distribution Period

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.



Bus parameters Setting range (default) Meaning and limiting valuesMaximum Inactivity to claim LAS Delay

1 - 4095(100)

Delay time (device-internal)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 minimum value for this parameter is determined by the maximum value of all the LAS-capable FF devices in the FF segment.

LAS Database Distribution Period

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 FF

segment● Distribution of the LAS database to FF devices in the FF segmentRecommendation: Set a value between 1000 and 5000.

Ap Clock Sync Interval

0..255(10)

Application Clock Synchronisation Interval is a special parameter for those devices 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(3)

Maximum number of failed communication attempts. If 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 set the bus parametersSettings of the FOUNDATION Fieldbus are configured via HW Config or NetPro in PCS 7 systems. 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 IDThe S7 subnet ID comprises two numbers separated by a hyphen:

● One number for the project

● One number for the subnet

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



Connecting a Linkmaster (LAS) to an FF segment in operationPlease 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 segment are 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.

Procedure1. Select the FF subsystem in the SIMATIC Manager in HW Config.

2. Select the menu command Edit > 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 34)".

NoteIdentification of all FF devices on the FF segment

Set the value "First Unpolled Node" to 232 (default = 36).● For performance reasons, no addresses in the address range 36 to 231 should be

assigned to FF devices in a system.● Following a scan of the "Unpolled Bereiches", you should set the default value (36)

again.

6. Select the File > Save menu command.These changes are applied to the PCS 7 project.



Field device as Link MasterIf 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" cancelledIf the schedule calculation could not be executed successfully, you receive an error message. Check the settings of the bus parameters.

NoteError 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 on this in the section "Additional notes on configuration (Page 27)".

Checking the bus parameters1. 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

Note

Observe the following if you have added new FF devices to the FF segment or if you want to use new parameters.● Online changes are not possible in these cases.● First, you have to configure all the interconnections.● If required, correct the macrocycle settings.



4.3.4 How to plan the macrocycleA macro cycle 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 macro cycle and the percentage of acyclic communication. The FF specifications recommend that at least 50% of the bus time is kept free for acyclic communication.

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

"Macrocycle" tabWhether the configuration is consistent is determined on the basis of the output values and the required interconnections. The result is displayed graphically.

"Calculate Schedule" button"

● Click this button to calculate the time for cyclic communication.

"Optimize macro cycle" button

● Click this button to set the macro cycle as follows:Depending on the cyclical component (depending on the configured hardware), a minimum macro cycle 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 areaThe 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 lineThe 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 areaThe colored area on the right side indicates the percentage of cyclic communication.

Meaning of the colored areas

● YellowPercentage of acyclic communication

● Dark greenPercentage of cyclic communication Configuration is free from errors.



● Light green and dark greenConfiguration is free from errors. The percentage of cyclic communication is displayed in dark 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 macro cycle 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 the recommendations 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 the recommendations of the Fieldbus Foundation.

Note

Since there may be be errors in the acyclic communication, this configuration cannot be downloaded.

Setting the macro cycle1. 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 > Save menu command.These changes are applied to the PCS 7 project.



Adapting the macro cycleIf the macro cycle 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 following actions:

● Adding FF devices

● Adding new interconnections with the Interconnection Editor

● Using new connections via the CPU

● Using new I/O data

NoteAdjusting the macro cycle requires a STOP of the FF segment

A STOP of the FF segment is associated with adjusting the macro cycle.

Recommendation for commissioning:

Configure a CiR object and a sufficiently long macro cycle at the FF segment.

Calculate scheduleThe 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" in the "Macrocycle" tab.

Including device-internal blocks● The following blocks are considered when diagnosing FF devices:

– Interconnected function blocks

– Resource blocks

– Transducer blocks

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

● Changes made with SIMATIC PDM become effective only for interconnected function blocks.



4.4 Using the applications

4.4.1 OverviewIn 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. The created 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 on the operator station.

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

4.4.2 How to identify FF devices with SIMATIC PDMWith 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 LifeList1. 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 > Start LifeList .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, device numbers, and manufacturers.

Engineering4.4 Using the applications


NoteStatus

If the data has not been updated, see the following:● The tree structure has been deleted and will be rebuilt.● The symbols will change.

Additional informationOnline help for SIMATIC PDM

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

NoteUnpolled range

In SIMATIC STEP 7 / 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 on this step in section "How to set the bus parameters (Page 39)".

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 command Open Object.The "SIMATIC PDM" dialog box opens.

5. Select the FF Link.

6. Select the menu command Edit > SIMATIC PDM > Start LifeList .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.

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

NoteRestart

Changing the address will restart the device.

NoteAddress or tag occupied

If the address or TAG is occupied, then the action will not be performed. An appropriate message will be displayed.

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

DownloadingTo ensure that all configured parameters and connections are available for the FF device, you will have to download the FF device.

4.4.4 How to edit the symbolsYou can easily adapt the symbolic names and comments for signals.



Requirements● The project is open in SIMATIC Manager in the component view.

● Symbolic names were assigned for the inputs and outputs during configuration of the FF devices.

Procedure1. Select the folder <ProjectAS> > <CPU> > <S7 Program> 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 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 devicesUse the channel blocks of the PCS 7 Advanced Process Library (APL) to interconnect the signals of FF devices.

One channel block should be used for each I/O address.

Block type Address range Block name Function block Block I/OAnalog Input FbAnIn FB 1813 PV

Output FbAnOu FB 1814 SPDigital Input FbDiIn FB 1815 PV

Output FbDiOu FB 1816 SP



Requirements● FF devices have been configured.

● Symbols have been created.

ProcedureYou have the following options for configuring interconnections:

● Configure the interconnections in the PCS 7 Import/Export Assistant using templates.

● Create your own CFC charts.

Additional informationYou 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 OSInformation about the configuration of process pictures and diagnostics with operator stations is available in the Process Control System PCS 7; Operator Station Configuration Manual.



Commissioning 5

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

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

Additional informationRefer 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 system with the engineering station.

CompileThe central function for this can be obtained by selecting the menu command PLC > Compile and Download Objects... in the SIMATIC Manager.

Options for compiling and downloading the ASThe 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 53)".

Options for compiling and downloading the OSThe 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 their own.

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

Additional informationYou 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

Commissioning5.1 Compile and download


5.1.1 How to download objects in the FF segmentYou 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 devicesYou have the following 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

RequirementYou 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 parameters of additional function blocks.● The FF segment is stopped briefly during loading if it is downloaded completely (option

at the FF Link: "Always download FF Link and FF devices"). ● The FF segment continues running during loading if it is downloaded in increments (option

at the FF Link: "Download FF Link and FF devices only in case of change").● First, you have to configure all the interconnections.● If required, correct the macro cycle settings.

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



Download 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 always download the hardware configuration to HW Config. PLC > Download to Module

Hardware configuration is downloaded

Downloading -

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

Program and connections are downloaded

- -

In SIMATIC PDM, select the FF Link Device > Download to Devices Select the "Object with all subordinate objects and networks" check box in the "Download to devices" dialog.

- - All FF devices will be downloaded.

Select the FF device in SIMATIC PDM Device > Download to devicesSelect the "Object with all subordinate objects" check box in the "Download to devices" dialog.

- -Only when replacing a device with one of the same type: Select the check box "Load Schedule to Device".

The FF device is downloaded

Note

You can download changes to the automation system in "RUN" mode (CIR). Note the settings for "Load FF Segment".

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.



3. Select the "Load FF Segment" tab.

4. Make the settings in accordance with the table below:

Check box Application Download FF Link and FF devices only in case of change

Exclude FF segment during AS downloadYou configure no changes for the FF segment, for example

The FF segment continues running during loading if only changes are downloaded.

Always download FF Link and FF devices

Complete download of an FF segment

The FF segment is stopped when it is downloaded completely.RecommendationAfter a complete download of an FF segment, select the option "Download FF Link and FF devices only in case of change".

Exclude FF Link and FF devices from download

FUNCTION for COMMISSIONING ONLY

This function support you during commissioning of other FF links on the same PROFIBUS.NOTICE! Undefined states may occur in the FF segment when you use this setting. A STOP of the FF segment is possible.

See alsoHow to assign parameters of the FF devices (Page 33)



5.2 Diagnostics options

Diagnostics on the FF in PCS 7PCS 7 uses staggered diagnostics.

● With the maintenance stationStatus overview and status messages for FF Link and FF devicesDetailed 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 PDM

– Detailed diagnostics for FF Link and FF devices

– Use the "Mode" dialog box only and FF Link and FF devices

– Use the "Status" dialog box only and FF Link and FF devices

● LED displays on the FF LinkStatus of FF

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

Additional information● Configuration Manual Process Control System PCS 7; Operator Station● Section "How to identify FF devices with SIMATIC PDM (Page 45)"

● SIMATIC;FF Link Operating Instructions

● FF devices documentation

5.2.1 "Mode" and "Status" menu commandYou can find the "Mode" and "Status" menu commands for FF devices in the "Devices" menu in SIMATIC PDM. These menu command are used to open the dialog boxes which provide you support during the commissioning of FF devices. Since these dialogs are specific to each FF device, the following only provides basic information.

For detailed information, see the online help dialog.

Commissioning5.2 Diagnostics options


"Mode" dialog boxYou can perform the following for a FF device in this dialog box:

● Show permissible operating modes

● Change the operating mode if the device or the current settings permit it

"Status" dialog boxYou can perform the following for a FF device in this dialog box:

● Retrieve status information

● Enable/disable status information

● Simulate status information

5.2.2 How to perform diagnosticsAn example of diagnostics in the SIMATIC Manager and detailed diagnostics with SIMATIC PDM is shown below.

Requirements for diagnostics● FF devices have been created.

● An online connection to the FF device can be established.

Diagnostics in the SIMATIC Manager1. 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 "<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

NoteOffline status

The last updated status of the FF devices are shown in the following views in SIMATIC Manager:● Process devices network view● Process devices plant view

Detailed diagnostics with SIMATIC PDM1. Select one of the following views:

– Process devices network view

– Process devices plant view

2. Select the FF device.

3. Select the menu command Edit > Open Object.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.



Redundancy and system changes in operation 66.1 Redundancy

The basic configuration of redundant FF segments is the same as the configuration of PROFIBUS 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 Systems documentation 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

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

ConfigurationYou 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 23)".

S7-400H as DP Master The following AS components can operate as DP Master:

● CP 443-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 interface modules.


Additional information● 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.

Redundancy and system changes in operation6.1 Redundancy


6.2 Changing the system in runSee the following information if you want to make changes to an FF segment in an existing system.

Changes in runThe 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 by means of CiR)

Changes in run

Note

The CPU will stay in RUN with the following actions, but communication at the FF segment will go to STOP.

● Changing connections between FF devices

● Changing bus parameters

NOTICE

STOP of CPU required

A STOP of the CPU is required if you add a new address for an FF device in HW Config that is configured and downloaded in the system.

Additional informationThe whole sequence of a system modification and the requirements that must be met for it are described in detail in the documentation SIMATIC; Modifying the System during Operation via CiR.

Redundancy and system changes in operation6.2 Changing the system in run


Index

Field device in SIMATIC PDM

Integrate, 46 XE \* MERGEFORMAT , 31

AAddress, 46

CChange

Download, 54CiF, 31Configuration via PDM, 24

DDelta download, 54Download, 54

Change, 54Delta download, 54

HHW Config

Start Interconnection Editor, 29

IIntegrate, 24, 46

Field device in SIMATIC PDM, 46PROFIBUS device in SIMATIC PDM, 24

Interconnection Editor, 31Starting, 29

LLoad FF segment

Tab, 54

NName, 46

OOption

Configuration via PDM, 24

PPROFIBUS device in SIMATIC PDM, 24

Integrate, 24Publisher, 7

SSchedule, 7SIMATIC Manager

Start Interconnection Editor, 29SIMATIC PDM, 24

Integrate field device, 46Integrating a PROFIBUS device, 24Start Interconnection Editor, 29

Subscriber, 7

TTab

Load FF segment, 54TAG, 46


SIMATIC Engineering 4 FOUNDATION Fieldbus Process …...Basics of the FOUNDATION Fieldbus 2 2.1...

Documents

Transcript of SIMATIC Engineering 4 FOUNDATION Fieldbus Process …...Basics of the FOUNDATION Fieldbus 2 2.1...