SIMATIC. Process Control System PCS 7 FOUNDATION Fieldbus. Introduction 1. Basics of the FOUNDATION Fieldbus 2. System planning 3.

Transcription

1 Introduction 1 Basics of the FOUNDATION Fieldbus 2 SIMATIC Process Control System PCS 7 Commissioning Manual System planning 3 Engineering 4 Commissioning 5 Redundancy and system changes in operation 6 Requirement: SIMATIC PDM V8.0 SP1 03/2012 A5E

2 Legal information Warning notice system This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger. DANGER indicates that death or severe personal injury will result if proper precautions are not taken. WARNING indicates that death or severe personal injury may result if proper precautions are not taken. CAUTION 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 be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage. Qualified Personnel The product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems. Proper use of Siemens products Note the following: Trademarks 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. All names identified by are registered trademarks of Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner. Disclaimer of Liability We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions. Siemens AG Industry Sector Postfach NÜRNBERG GERMANY A5E P 04/2012 Technical data subject to change Copyright Siemens AG All rights reserved

3 Table of contents 1 Introduction Basics of the Basic knowledge of Device integration with EDD Device addresses Block model of device parameters System planning Nodes in the Configuration Engineering Prepare How to integrate a device description Configuring How to place FF devices on the Additional notes on configuration How to assign addresses for FF device signals Interconnection Editor" dialog box How to configure FF internal interconnections (Control in the field) Parameter assignment How to assign parameters of the FF devices Bus parameters How to set the bus parameters How to plan the macrocycle Using the applications Overview How to identify FF devices with SIMATIC PDM How to define the device ID of the FF devices (TAG name and address) How to edit the symbols How to configure interconnections to the FF devices Configuring the OS Commissioning Compile and download How to download objects in the FF segment Diagnostics options How to perform diagnostics Redundancy and system changes in operation Redundancy...51 Commissioning Manual, 03/2012, A5E

4 Table of contents 6.2 Changing the system in run...52 Index Commissioning Manual, 03/2012, A5E

5 Introduction 1 SIMATIC PCS 7 enables the integration of field devices in 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 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 Commissioning Manual, 03/2012, A5E

6 Introduction 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 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 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. Scope of the documentation This documentation is valid for the software package Process Control System; SIMATIC PCS 7, V8.0 Update 1 or higher including SIMATIC PDM V8.0 service pack 1. 6 Commissioning Manual, 03/2012, A5E

7 Basics of the Basic knowledge of (FF) and PROFIBUS PA operate according to IEC 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 Kbps. The most important distinctions between PROFIBUS PA and 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 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 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 (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. Commissioning Manual, 03/2012, A5E

8 Basics of the 2.2 Device integration with EDD Communication types Two types of communication are used with FF: cyclic communication Cyclic communication is defined in the Schedule. It includes tasks such as controlling process variables (control functions) and operating and monitoring functions. acyclic communication Acyclic 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. Macrocycle The 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. 2.2 Device integration with EDD Standardized device descriptions Standardized device descriptions enable intelligent field devices from different manufacturers to be integrated in different control systems. The IEC 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). 8 Commissioning Manual, 03/2012, A5E

9 Basics of the 2.3 Device addresses Information in device descriptions Device descriptions contain all information required for correct interpretation of device data. Pre-defined device descriptions (standard DDs) describe the key parameters. These standard DDs are available from the user organizations, for example, through the Fieldbus FOUNDATION. FF devices can interpret and display the data and functions of this standard DD. The basic functions of the user interface are stored in the standard DD. Device-specific functions and parameters can be stored in an extended device description. Additional information IEC IEC 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 : 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 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 devices that are only temporarily connected. Commissioning Manual, 03/2012, A5E

10 Basics of the 2.4 Block model of device parameters 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 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 addresses Connected FF devices will be detected automatically at the FF segment. In case of an address conflict, a recently connected FF device will automatically be assigned a temporary address during operation. 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. 2.4 Block model of device parameters The 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 Note Parameter assignment with SIMATIC PDM The application SIMATIC PDM is used in PCS 7 for assigning parameters to the FF devices. 10 Commissioning Manual, 03/2012, A5E

11 Basics of the 2.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 block Function blocks provide information about the functions available in an FF device as well as their tasks. The schedules of the clocked data transmission defined in the Schedule are based on these function blocks. 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 block You 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 Commissioning Manual, 03/2012, A5E

12 Basics of the 2.4 Block model of device parameters Configuration of the 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 12 Commissioning Manual, 03/2012, A5E

13 System planning Nodes in the An FF segment contains all nodes communicating via the. The following information is used for the system-specific optimization of FF segments. Size of the process image An FF segment is restricted to the size of the process image of the FF Link (max. 244 bytes I/O in each case). The 244 bytes for inputs can be divided among the FF devices: Digital inputs (2 bytes per value, however maximum 40 DI) Analog inputs (5 bytes per value, however maximum 40 AI) The 244 bytes for outputs can be divided among the FF devices: Digital outputs (2 bytes per value, however maximum 40 DO) Analog outputs (5 bytes per value, however maximum 40 AO) Nodes in an FF segment The maximum number of nodes in an FF segment depends on the system requirements with regard to update times. Typically, 3 to 7 FF devices (maximum 31) are integrated in an FF segment. The time for a macrocycle is influenced primarily by the share of cyclic communication. This share depends on the following factors: Properties of the FF devices 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. Commissioning Manual, 03/2012, A5E

14 System planning 3.2 Configuration Sample calculation 15 x 30 ms = 450 ms, corresponds to the cyclic bus time reserved bus time for acyclic communication 1050 ms (recommended 70 %), 450 ms (recommended, at least 50%) recommended macrocycle = between 1500 ms and 900 ms I/O data The parameters, inputs and outputs of FF devices are distributed over function blocks. An FF device can have several function blocks. Only configure the required I/O data of an FF device. The number of processed function blocks has an effect on the macrocycle. 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 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 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. 14 Commissioning Manual, 03/2012, A5E

15 System planning 3.2 Configuration Number of branch lines (longer than 1 m) Maximum length of a branch line m m m m m Intrinsically safe configuration NOTICE The maximum length of a branch line is limited to 60 meters. Additional information Operating instructions SIMATIC; Bus links; FF Link bus link Manual Process Control System PCS 7; Fault-tolerant Process Control Systems Commissioning Manual, 03/2012, A5E

16

17 Engineering 4 Overview You configure the (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 How to integrate a device description Requirement SIMATIC PDM is installed. Procedure 1. Go to the Windows start menu and select the menu command SIMATIC PDM > Device Integration Manager under Siemens SIMATIC programs. To be able to use the Device Integration Manager, you must accept the license agreement. 2. Select the menu command File > Read device descriptions 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 import. The default directory is "Foundation Fieldbus". 6. Click "Integrate". The device descriptions are transferred to the computer. Additional information Online help for SIMATIC PDM Commissioning Manual, 03/2012, A5E

18 Engineering 4.2 Configuring 4.2 Configuring How to place FF devices on the Example of an FF configuration Recommendation for using symbolic names Assign symbolic names to the signals of the FF devices. Symbolic names facilitate configuration and documentation of the automation task. The use of symbolic names is taken into account in the following. 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 17)". You are familiar with the functions and signals required by the FF device. Information must be contained in the FF device documentation. 18 Commissioning Manual, 03/2012, A5E

19 Engineering 4.2 Configuring 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 FF devices 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 without redundant 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 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 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 doubleclick on the FF Link. 6. Click "OK". The interface module is created with a Foundation Fieldbus: FF subsystem. Commissioning Manual, 03/2012, A5E

20 Engineering 4.2 Configuring 7. Optional steps for a redundant Foundation Fieldbus: Select the IM 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 the FOUNDATION FIELDBUS in the current PCS 7 profile. 10.Select the FF device in the folder <Manufacturer> > <Device Group> > <Device Type>. 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 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 9)". 20 Commissioning Manual, 03/2012, A5E

21 Engineering 4.2 Configuring 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 Compile from the menu. Note Downloading The device can be downloaded, provided that the "Address" and "TAG" in the configuration correspond 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 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: 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)" Commissioning Manual, 03/2012, A5E

22 Engineering 4.2 Configuring Additional information Manufacturer information of the FF device. Section "How to assign parameters of the FF devices (Page 26)" Section "Nodes in the (Page 13)" Section "How to configure FF internal interconnections (Control in the field) (Page 25)" SIMATIC; SIMATIC PDM documentation; chapter "Working with the LifeList" Additional notes on configuration Device-specific number of interconnections The number of interconnections available as Backup Link Master for an FF device is devicespecific. 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 configuration Separating from PROFIBUS DP If you want to separate the interface module for the 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 to an automation system (behind PROFIBUS DP) When you connect an interface module for the, which is separated from PROFIBUS DP, to an automation system (behind PROFIBUS DP), observe the following: 22 Commissioning Manual, 03/2012, A5E

23 Engineering 4.2 Configuring Interconnections between the 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 How to assign addresses for FF device signals You need to assign addresses to the FF device signals that you want to process further with the automation system. 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 "<Signal> 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. Check the symbolic address assignment afterwards." It is imperative that you perform this check and make any necessary corrections. Commissioning Manual, 03/2012, A5E

24 Engineering 4.2 Configuring 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 (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. Note Internal device interconnections FF devices have internal device blocks, such as measuring sensor, controller. The internal device interconnection of these blocks means that there is no communication load on the FF segment. Structure The "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 the FF segment. Inputs are the target of an interconnection. "Interconnection" column This column displays a list of interconnections that were configured for the FF segment. Layout: Output of the FF device > Function Block > Signal "Outputs" area "Output" column This column shows the FF devices and the available outputs in the network view of the FF segment. Outputs are the source of an interconnection. Buttons Button "Add interconnection" "Delete interconnection" Function Click this button to add an interconnection to the column "Interconnections". Click this button to delete an interconnection. 24 Commissioning Manual, 03/2012, A5E

25 Engineering 4.2 Configuring Button "Close" "Save" Function Click this button to close the dialog box. A message informs you if changes were not saved. 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 Analog input Analog input Digital input Digital input Analog output Analog output Digital output Digital output Status Not interconnected Interconnected Not interconnected Interconnected Not interconnected Interconnected Not interconnected Interconnected See also How to configure FF internal interconnections (Control in the field) (Page 25) 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 FF). Commissioning Manual, 03/2012, A5E

26 Engineering 4.3 Parameter assignment 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. 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 is calculated automatically during the download to the FF devices. Additional information Online help for SIMATIC PDM 4.3 Parameter assignment How to assign parameters of the FF devices You configure FF devices in PCS 7 systems with SIMATIC PDM. Note Device-specific menu commands and help in SIMATIC PDM Device-specific menu commands and the Help for them are derived from the device description assigned to the object. Device-specific information can be found in the Online Help and documentation of the device manufacturer. Requirements SIMATIC PDM is installed together with the licenses. The device descriptions of the FF devices have been integrated. 26 Commissioning Manual, 03/2012, A5E

27 Engineering 4.3 Parameter assignment 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". Commissioning Manual, 03/2012, A5E

28 Engineering 4.3 Parameter assignment 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 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. Note Offline parameter assignment data SIMATIC PDM enables offline parameter assignment data to be downloaded to one or more FF devices (download to devices) or enables device parameters to be uploaded from the FF devices to the computer and saved on request (upload to PG/PC). Additional information Manufacturer information of the FF device. Online help for SIMATIC PDM Bus parameters Faultless operation of the components on the FF subsystem is only ensured if the parameters for the bus profile are compatible with each other. You should therefore only change the default values if you are familiar with parameter assignment of the bus profile for FF. 28 Commissioning Manual, 03/2012, A5E

29 Engineering 4.3 Parameter assignment 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" area FF 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 Commissioning Manual, 03/2012, A5E

30 Engineering 4.3 Parameter assignment Bus parameters T1 Inter Sequence Timer T2 Set Addr Sequence Timer T3 Set Addr Wait Timer Setting range (default setting) - ( corresponds to approximately 15 s) T2 >= T3 + 3*T1 (host) ( corresponds to approximately 90 s) - ( corresponds to approximately 45 s) Meaning and limiting values 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. 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. 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 First Unpolled Node Number of Consecutive Unpolled Node Setting range (default setting) Meaning and limiting values 20 < FUN < 232 FirstUnpolledNodeId (FUN) NUN = 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. NumConsecUnpolledNodeId (NUN) (Default setting: NUN = = 196) Range of consecutive device addresses not in the polled range. In SIMATIC STEP 7 / PCS 7 (Unpolled Bereich): Default setting of "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. 30 Commissioning Manual, 03/2012, A5E

31 Engineering 4.3 Parameter assignment Bus parameters Setting range (default) Meaning and limiting values Slot Time Per DLPDU PhL Overhead Maximum Response Delay Minimum Inter DLPDU Delay Preamble Extension (8) 2-63 (2) 1-11 (10) (16) 0-7 (2) Time Sync Class 0-7 (4) 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 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 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/st Assign parameters to this value in such a way that the minimum value is greater than the ratio of Maximum Response Delay Slot Time and Slot Time of every FF device on the FF segment. MRD(FF segment): MRD >= MRD of each FF device of the segment Selection: 1 to 11 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. 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 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) Commissioning Manual, 03/2012, A5E

32 Engineering 4.3 Parameter assignment Bus parameters Setting range (default) Meaning and limiting values Maximum Scheduling Overhead Max Inter Chan Signal Skew Post Trans Gap Extension Default Minimum Token Delegation Time Default Token Holding Time Target Token Rotation Time Link Maintenance Token Holding Time Time Distribution Period 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. 0-7 (0) 0-7 (0) (86) (276) (60000) (336) (5000) 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. 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 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 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. Time period assigned to an FF device by the LAS for the following tasks: acyclic bus traffic System Management Alarms and events 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 lowpriority services. The following are low-priority services: System Management acyclic bus traffic (client-server connections) 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 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. 32 Commissioning Manual, 03/2012, A5E

33 Engineering 4.3 Parameter assignment Bus parameters Setting range (default) Meaning and limiting values Maximum Inactivity to claim LAS Delay LAS Database Distribution Period Ap Clock Sync Interval (100) (5000) (10) 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. 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 segment Recommendation: Set a value between 1000 and 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) Stale Count Limit (3) Selection: 20 to 180 seconds (levels: every 20 seconds) 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 How to set the bus parameters Settings of the 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 - " 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 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. Commissioning Manual, 03/2012, A5E

34 Engineering 4.3 Parameter assignment 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 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. Procedure 1. 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 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 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. 34 Commissioning Manual, 03/2012, A5E

35 Engineering 4.3 Parameter assignment 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 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 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 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. Commissioning Manual, 03/2012, A5E

36 Engineering 4.3 Parameter assignment How to plan the macrocycle A macrocycle lasts for a number of bus clock cycles. The duration of the cyclic communication depends on the configured hardware. You can define the time for a macrocycle and the percentage of acyclic communication. The FF 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 (Page 13)". "Macrocycle" tab Whether the configuration is consistent is determined on the basis of the output values and the required interconnections. The result is displayed graphically. "Calculate Schedule" button" Click this button to calculate the time for cyclic communication. "Optimize macrocycle" button Click this button to set the macrocycle as follows: Depending on the cyclical component (depending on the configured hardware), a minimum macrocycle is set with a specified acyclical percentage. Graphical display Before downloading, click the "Calculate schedule" button. With the help of the display you can check whether the configuration is consistent. The result is displayed graphically. Display from left to right: Left-hand area The 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 recommended in the FF specifications. Thick dividing line The limiting value set in the entry field "Percentage of acyclic communication". Right thin dividing line (70% of the bus load) The upper limit of the percentage of acyclic communication of the bus load recommended in the FF specifications. Right-hand area The 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 is free from errors. 36 Commissioning Manual, 03/2012, A5E