Prévia do material em texto
System 800xA Training Chapter 11 - 1 Chapter 11 Function Designer Concepts TABLE OF CONTENTS Chapter 11 Function Designer Concepts ................................................................................................................................. 1 11.1 General Information.................................................................................................................................................... 2 11.1.1 Objectives ............................................................................................................................................................ 2 11.1.2 Legend................................................................................................................................................................. 2 11.1.3 Reference Documentation .................................................................................................................................... 2 11.2 Introduction ................................................................................................................................................................ 3 11.2.1 General ................................................................................................................................................................ 3 11.2.2 Function Designer and Control Builder................................................................................................................. 4 11.2.3 Advantages .......................................................................................................................................................... 4 11.2.4 Intuitive Navigation.............................................................................................................................................. 5 11.2.5 Instant Access and Monitoring.............................................................................................................................. 6 11.2.6 Restrictions .......................................................................................................................................................... 6 11.3 Engineering Workflow................................................................................................................................................ 7 11.3.1 Prerequisites......................................................................................................................................................... 7 11.3.2 Main Workflow.................................................................................................................................................... 7 11.3.3 Configuring Function Diagrams............................................................................................................................ 8 11.3.4 Functional Planning.............................................................................................................................................. 8 11.3.5 Naming Concept .................................................................................................................................................. 9 11.4 Function Diagrams.................................................................................................................................................... 10 11.4.1 Flat and Nested Diagrams................................................................................................................................... 10 11.4.2 Function Diagram Views.................................................................................................................................... 11 11.4.3 Layers in a Diagram ........................................................................................................................................... 12 11.4.4 Description in Footer.......................................................................................................................................... 13 11.4.5 Multiple Pages ................................................................................................................................................... 13 T315F-11 Function Designer Concepts - RevE Chapter 11 - 2 11.1 General Information 11.1.1 Objectives On completion of this chapter you will be able to: Describe advantages and limitations of Function Designer Describe the design workflow Identify the properties and functionalities of function diagrams 11.1.2 Legend > Indicates when you go from one menu to a sub-menu Italic Indicates object and file names “ “ Indicates dialog box buttons, tabs, menus etc. Bold Indicates important topics Indicates start/explanation of student activity 11.1.3 Reference Documentation 3BDS011224 System 800xA Engineering Studio Function Designer 3BSE100968 System 800xA Engineering Studio Function Designer - Getting Started 3BSE041389 System 800xA System Planning System 800xA Training Chapter 11 - 3 11.2 Introduction 11.2.1 General Function Designer is an engineering tool for function oriented planning in System 800xA. Function Designer allows the engineer to create applications using a user friendly graphic environment, in the form of function diagrams. It allows engineering on a single diagram comprising of functions, function blocks, control modules, sequences, I/O channels and field devices. Other components such as bit maps, Active X objects and free text/graphics may be placed on the diagram to give the end user a complete view of the control functionality. The diagram below shows some of the possibilities: Function diagrams can be nested in multiple levels and the signal interconnections between function diagrams are automatically documented and provide built-in navigation. The style of a diagram is similar to the IEC-61131 Function Block Diagram languages. Once a diagram is created, the Function Designer generates the complete code required for that functionality in Control Builder. Field device I/O signal Function Control module T315F-11 Function Designer Concepts - RevE Chapter 11 - 4 11.2.2 Function Designer and Control Builder Function diagrams are usually created in the Functional Structure. A Function aspect is added to objects in the Functional Structure and each diagram is allocated to a particular application in the project. The generated code is created in the Control Structure. NOTE! It is also possible to create function diagrams on object types in a library in the Object Type Structure. Function Designer is an engineering tool that ‘sits’ outside Control Builder, but when it is used to generate configuration data it uses an interface into Control Builder to create the code corresponding to the components and connections on the diagram. Function Designer Diagram 1 Diagram 2 Diagram 3 Control Builder 11.2.3 Advantages Function Designer provides a number of advantages compared to engineering done in the Control Builder: Combinations between control modules and function blocks on one function diagram are possible. Navigation between references to different pages within one function diagram, or between different function diagrams is possible. The objects names within a function diagram can start with a number and the use of a dash is allowed, e.g. 123FIC345-FD. Generation and printing of function oriented documentation in one step to document your control configuration according international standards. Automatic creation of connection variables. Live data display and value forcing in online mode. System 800xA Training Chapter 11 - 5 11.2.4 Intuitive Navigation Multiple diagrams may be linked together either by of diagram references or else by nesting diagrams. Reference to other diagramReference to other diagram Reference to other sheetReference to othersheetReference to other sheetReference to other sheet T315F-11 Function Designer Concepts - RevE Chapter 11 - 6 11.2.5 Instant Access and Monitoring A function diagram is just another aspect of an object. Thus a right click on the component in the diagram gives access to any other aspect of that object. 11.2.6 Restrictions This version of Function Designer does not support: Batch management Safety applications (SIL-2 and SIL-3) System 800xA Training Chapter 11 - 7 11.3 Engineering Workflow 11.3.1 Prerequisites In order to work with Function Designer, there are still some general tasks that have to be done in Control Builder or the Engineering Workplace. Create a Control Network and Control Project(s) Create the controller hardware objects and assign IP address Create the control applications and assign to the controllers Create the control tasks and assign to the applications Assign some sub-libraries to the application or library Download the application Connect the OPC server to the controller(s) Create parent objects in the Functional Structure to “host” the function diagrams 11.3.2 Main Workflow Working with Function Designer requires a particular workflow. First a Control Project must be opened in Control Builder. NOTE! Control Builder must be “offline”. Configure function diagram Define data flow order Generate code Download from Control Builder Allocate diagram to application Enable live data in diagrams Create diagrams and insert control modules, function blocks, variables, references … Define allocated controller and cycle time (task) Define the execution order of all blocks Generate the code to download to controller Download the code to the controller Optional enable live data in diagrams for commissioning or diagnostics Allocate I/O signals Allocate the IO signals to boards Write the I/O allocation to Control Builder T315F-11 Function Designer Concepts - RevE Chapter 11 - 8 11.3.3 Configuring Function Diagrams 1. Create a new diagram based on a diagram template, using a parent object in the Functional Structure. Function Designer will initially store the content in an unassigned application until the appropriate application is selected and assigned. 2. Create different pages, if required. 3. Allocate the diagram to the correct application 4. Drag-and-drop objects to the function diagram from the Object Type Structure 5. Parameterize the signal objects 6. Define the data flow order 7. Generate the code 8. Allocate signal objects to I/O modules 9. Write the I/O allocation to Control Builder 10. Download to controller(s) and go online NOTE! All the code which was generated by the Function Designer is “read only” in the Control Builder. 11.3.4 Functional Planning The definition of how to distribute the objects and logics in the function diagrams is one of the most critical tasks of the project. Function Designer provides enough flexibility to implement a functionality using different philosophies. A specific process can be divided into few complex function diagrams that include many objects, or it can be divided into many simple function diagrams that include few objects. To decide which methodology to use, the design has to be analyzed from different perspectives: Functionality: A diagram has to group components that have a common functionality. Objects that don’t interact with each other in a direct or an indirect way shouldn’t be part of the same diagram Modularization: Each diagram should contain only one main object (normally any object that has a faceplate can be considered as such). The function diagram must then include all the logics and functions required to give the desired functionality to that main object. Reusability: If a specific functionality is repeated many times, a function diagram should be limited to implement this functionality only, since copying a function diagram is well supported. If the repeated functionalities have minor differences or different configuration it is easy to implement these modifications later on. System 800xA Training Chapter 11 - 9 11.3.5 Naming Concept Each aspect object in the Engineering Workplace has a Name aspect. For control objects there is an additional Control Builder Name aspect which gets synchronized with the name in the Project Explorer, and therefore always follow the IEC 61131-3 naming concept (no number in front, like 123FIC456). NOTE! Use the Name aspect for changing a name. Function Designer will take care of the Control Builder Name aspect. If a name is used in a function diagram that does not fit the IEC 61131-3 conventions, then Function Designer changes the Control Builder Name aspect so that it complies. For example, we want to change the name of a particular object: 1. Right click on the Sxx_V2 object and select “Name” to change it. 2. Put numbers at the beginning of the name and click “Apply”. 3. Observe the result in Control Builder and in the Functional Structure. Control Builder Engineering Workplace Note that the object has an “x” at the beginning of the name in Control Builder to avoid naming errors. NOTE! To rename a function diagram, use the Name aspect of the corresponding object. Function designer provides an automatic naming feature which is set in the Functional Settings aspect. Therefore, if the Naming property in the Functional Settings aspect is set to Auto (or a name pattern is not defined), Function Designer does the renaming based on the differences between the source and target name. The names are then split into tokens identifying unmodified/modified substrings and numbers. This is useful for bulk operations as a change of a function diagram name will change all component names as well, providing all components of this function diagram have the function diagram name in front. T315F-11 Function Designer Concepts - RevE Chapter 11 - 10 11.4 Function Diagrams A function diagram can show a complete process control loop with all its function blocks, control modules, field devices, signal objects (I/O signals) and their signal connections. A function diagram is a dynamic document on which components (and other graphics) are drawn: Components on the diagram represent instances of functions, function blocks and control modules. Components may be connected on the diagram graphically or by references to variables or diagrams. Sequences can be included into function diagrams and their steps, transitions and actions can be configured in additional diagrams. Function Designer is used to generate code in Control Builder M, but with the advantage that the diagram can be drawn to graphically represent the functionality that it implements. If a project is built with Function Designer, it will consist of a set of function diagrams. 11.4.1 Flat and Nested Diagrams A set of diagrams may be created independently and then linked to each other by reference to a common set of external references called “off-diagram references”: Diagram 1 Diagram 2 Diagram 3 Diagram 4 Reference Reference Reference This creates a flat structure but allows data to be passed between diagrams. There is no formal relationship between the diagrams until the references are defined. Another alternative is to arrange diagrams within diagrams in a hierarchy. Diagram 1 Diagram 2 Diagram 3 Diagram 4 Diagram 5 These are referred to as nested diagrams. In this case, we refer to parent and child diagrams. The system will allow easy navigation between parent and child diagrams. Also each child diagram is represented as a component within its parent diagram. System 800xA Training Chapter 11 - 11 11.4.2 Function Diagram Views Function Designer offers three different views for a function diagram:Component view To create symbols or templates for function components in the Object Type Structure. Diagram view To create function diagrams and to insert function components in the Functional Structure. Parent Diagram view Alternative to the Diagram view to quickly find and navigate to a component. It is opened in the Functional Structure on the selected component object, and it displays and automatically navigates to the component in its parent diagram. Function Designer offers the possibility to open simultaneously several diagram /component documents. Each diagram/component document is opened in a separate window, such that you can have several windows open at the same time. Function Designer also offers the possibility to open the same diagram in several windows. That can be useful, for example, to display different parts or pages of a diagram/component simultaneously in different windows. T315F-11 Function Designer Concepts - RevE Chapter 11 - 12 11.4.3 Layers in a Diagram The Diagram View allows the user to create logic on several layers: Logic layer Contains the components and connections that form the control logic Master Page layer Contains the header and footer definitions that will be present on all pages. Background layer Can be used to place graphics which will appear on all pages Annotation layer Used to add annotation to a diagram. System 800xA Training Chapter 11 - 13 11.4.4 Description in Footer You can set the descriptions in the footer of the diagram with the aspect called Function Diagram Document. Open the Main View of the aspect and fill in the parts you need. In the example shown ‘Feed water Flow Control’ was added and the title is shown in the diagram footer. 11.4.5 Multiple Pages Some configurations are too complex to fit in one page. In order to make it easier to understand them, diagrams may be spread over two or more pages. To create a new page, select “View > Pages > Insert New Page”. Exercise 11.1 T315F-11 Function Designer Concepts - RevE Chapter 11 - 14 Chapter 11 Function Designer Concepts 11.1 General Information 11.1.1 Objectives 11.1.2 Legend 11.1.3 Reference Documentation 11.2 Introduction 11.2.1 General 11.2.2 Function Designer and Control Builder 11.2.3 Advantages 11.2.4 Intuitive Navigation 11.2.5 Instant Access and Monitoring 11.2.6 Restrictions 11.3 Engineering Workflow 11.3.1 Prerequisites 11.3.2 Main Workflow 11.3.3 Configuring Function Diagrams 11.3.4 Functional Planning 11.3.5 Naming Concept 11.4 Function Diagrams 11.4.1 Flat and Nested Diagrams 11.4.2 Function Diagram Views 11.4.3 Layers in a Diagram 11.4.4 Description in Footer 11.4.5 Multiple Pages