1 / 262

Unity Application Generator

Unity Application Generator. Technical Training. Contents. Options 14 Structured Data 15 Import Export 16 PLC PLC Communication 17 Net Partner Communication 18 Profibus IO HMI System Extensions 19 Generating for Vijeo Citect 20 Generating for ArchestrA 21 Generating for Monitor Pro

palmer-duncan
Download Presentation

Unity Application Generator

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Unity Application Generator Technical Training

  2. Contents Options 14 Structured Data 15 Import Export 16 PLC PLC Communication 17 Net Partner Communication 18 Profibus IO HMI System Extensions 19 Generating for Vijeo Citect 20 Generating for ArchestrA 21 Generating for Monitor Pro 22 Generating for iFix 01 System Overview 02 System Requirements 03 Physical Model 04 Generating the PLC 05 Generating the HMI 06 Generation 07 Variable Properties 08 Template Types 09 Ethernet IO 10 Customization 11 From DFB to SCoD 12 SCoD Editor 13 Workflow

  3. UAG V3.2 Technical Training 01 System Overview

  4. Unity Application GeneratorAs part of the solution approach • SoCollaborative Engineering • Based upon the customers standard • For multiple PLCs /SCADA • With documentation

  5. Unity Application GeneratorCustomer focused System Software from Schneider Electric • Reduced Cost & Project Schedules • System implementation cost savings • Reduced risk and improved project schedules. • Improved time to market by allowing the project to go live and give return on investment sooner • Improved Quality • Improved software quality. • Improved maintainability. • Continuous Performance Improvement • Standardized design and systematic improvement. • Reuse of Customer best practices. Save 20-35% on project schedules

  6. Process Design – Think Process not PLC Standardized approach Application function oriented Automation Architecture Automation equipment and networks Mapping to “Control Modules”/Library objects Single data source, consistent data Automatic Incremental Application Generation PLC, HMI, Networking & Communications Reuse and Continuous Improvement Application functions Library management System Software for AutomationThe UAG approach… Define • Customer Specification • Process libraries Deploy • Process description • Automation architecture Generate • PLC • SCADA • Documentation

  7. GAMP Life Cycle Model Support by Unity Application Generator User Requirement Specification Performance Qualification related to Functional Specification Operational Qualification related to Software Design Specification Process control system documentation Validation Qualification FAT SAT Design Specification Installation Qualification related to PLC/HMI Application Software System Build Unity Application Generator Unity Application Generator GAMP 4.0 Supplier Guide Good Automation Manufacturing Practice

  8. UAG Value Propositionfor System Integrators and End Users System Integrator End User … how can I reduce my engineering efforts… … how do I keep my schedules and operational efficiency… • Re-using existing DFB and SCADA design elements • One project environment with structured approach. • Offering one common database for the whole project. • Incremental generation and network configuration. • Providing a guided system that forces system consistency and checks for errors. • Using pre-developed and tested libraries • Structured and uniform programming method applying EU standards. • Incremental modification of the applications. • Generation of consistent project documentation. • Import and export using xml formats providing flexibility of an open system.

  9. For the Process Engineer 1: Assign process functions to the UAG physical model 2: Choose the library object for each process function For the Automation Engineer 3: Design the automation architecture in the topological model 4: Assign each process function to the relevant automation device 5: Generate the application – automatically Unity Application Generator Linking Process Design and Automation Design 5 Step Design Process From process design to physical model

  10. Site Area Process Cell Unit Equipment Module Control Module Process Design Standardized Design Approach Process – P&ID UAG – Physical Model From process design to physical model Created by the Process Engineer Based on ISA-88 standard (flexibility to customize)

  11. Standard Functional Libraries Control Module UAG Library Element (SCoD) Library element contains: • PLC part • Control logic • Variables • Interconnections • Interlocking • HMI / SCADA part • Symbol • Status Display • Operator control • Logging, trends, alarms, ... • Documentation • Manuals • Data Sheets • … Reflecting the needs of the process Created by the Automation & SCADA Engineer Motor Application function

  12. Automation ArchitectureEquipment and Networks Automation Objects UAG: Topological Model • Multiple PLC • Multiple SCADA / HMI • Network Topology • Network Devices (Partners) Reflecting the needs of the process Created by the Automation Engineer

  13. Automation ArchitectureIntegrated Device Configuration UAG: Topological Model • Network configuration • Address management for Ethernet and Modbus Plus • PLC, PC, Panel and 3rd party devices • PLC Configuration • Unity Pro and Concept PLC platforms • PLC IO configuration including Hot Standby • Ethernet & Profibus IO configuration

  14. Automation ArchitectureLink the Control Module Physical Model Topological Model Define where the functionality is located: - PLC - Data Server - HMI - Network

  15. Generate the Application • Single entry type for PLC/HMI database • Synchronized, consistent PLC / HMI databases • Use and re-use application objects from the library • Apply process context by parameterization • Incremental generation for PLC/HMI • Global resource mapping • PLC application (code, variables, configuration, communication…) • HMI application (mimics, faceplates, variables, attributes, alarms…) • Communication management (Ethernet, MB+)

  16. UAG Project SCADA Project Unity Pro Project Result of the GenerationExample HMI Network Communication PLC

  17. UAG libraries Built your application: using what is available! Standard Libraries shipped with UAG Customer-Specific Libraries Process Application Library focused mainly on WWW with 32 Blocks Chengdu Water Library CSPEL Water Library Enhanced Process Library 1 focused mainly on thermal applications with 50 Blocks Denizli Cimento Cement Library Lafarge Cement Library Device & Process Library 1 focussed mainly on device integration with 50 Blocks South Africa Mining Library Many others.. Standard Libraries are available for the country organizations 1 Will be available in Q3 2009 Customer- Specific Libraries are developed by Schneider Electric project teams

  18. UAG V3.2 Technical Training 02 System Requirements

  19. What you learn in this chapter • UAG Installation • Hardware and software requirements • Installation procedure • UAG Installed Package • Single Tools: UAG, Customization, SCoD Editor • Folder Structure • Important File Types • Set Up a New Project • Procedure • Files belonging to a project

  20. UAG Hardware Requirements • Hardware • Pentium Processor 2 GHz or higher • 2048 MB RAM • 1 GB free space on hard disk • DVD-ROM drive • SVGA higher-resolution monitor with high color (24 bits) • TCP/IP compatible network adapter • Optional Hardware • Modbus Plus Adapter (PCI85)

  21. UAG Supported Software Platforms • Operating System • Microsoft Windows XP • Microsoft Windows Vista Business • PLC Programming Software • Schneider Electric Unity Pro V4.1 (S, M, L, XL) • HMI & SCADA Software • Vijeo Citect V6.1a, V7.0 or V7.1 • Monitor Pro V7.6 • iFix Intellution V3.5 or V4.1 • Wonderware ArchestrA V3.0 • PCVue (driven by Schneider Electric France)

  22. UAG Software Add On • Remote IO • Advantys Configuration Software V4.5 • Profibus Fieldbus • Sycon System Configurator V2.9 (Premium PLC) • ProSoft Configuration Builder V2.1.6.7 (Quantum PLC) • Additional Software • Microsoft Word 97, 2000 or 2003 to create UAG project documentation • Acrobat Reader for reading documentation • Tools as needed for displaying information, e.g. CAD etc. • XML viewer or editor for Import and Export files

  23. Installation and Configuration Workflow • Basic Installation • Install Unity Pro • Install HMI / SCADA system, e.g. Vijeo Citect • Install Unity Application Generator • Install optional packages (as needed) • Other HMI generator than Vijeo Citect, e.g. ArchestrA • Library Packages, e.g. Process Application Library (PAL) • Remote IO and Fieldbus configuration, e.g. Prosoft • Configure the system • Restore the library projects for Vijeo Citect

  24. Folder Structure & Important Folders • Default installation path • \Programs\Schneider Electric\Unity Application Generator • Unity Application Generator • Root folder with the UAG programs • Default Customization Files (*.osc) • Db • Default folder for SCoD-libraries (*.osl) • Default folder for XML stylesheets (*.xsl) • Vijeo Citect • Archived libraries for Vijeo Citect (*.ctz) • Use these for restoring the libraries in Vijeo Citect

  25. Single Tools of UAG • Unity Application Generator • Application Design • Code Generation • Template Libraries • SCoD Editor • Library Definition • Customization Editor • Project settings • Library Selection

  26. File Types of UAG • SCoD libraries (*.osl) • Contain all the information about the library objects for PLC and HMI • Template Types libraries (*.ost) • Contain all the information about template objects (combined SCoDs) • Customization file (*.osc) • Defines which SCoD libraries are used • Defines the naming rules for objects and variables • Defines the hardware to be used • UAG project file (*.osp) • Contains the project itself • A customization with the same name is attached to it

  27. Setting up a new UAG Project • Define a new project • Start Unity Application Generator • Select “New” icon or chose from menu • Choose a Customization File • Should contain the required libraries and project settings • See chapter 10 for details, how to configure • Example: UAGProcessLibVCV2.0.osc • Save the new project • Save is only required after defining a new project • Once project is saved, UAG executes automatic save of the project • On save the Customization File is copied and stored together with project • The Customization File gets the same name as the Project File

  28. Summary System Requirements • Unity Application Generator • Generating Code for Unity Pro • Generating HMI application for Vijeo Citect, Monitor Pro, iFix & ArchestrA • Three tools • SCoD Editor for Libraries • Customization for Project Settings • UAG Tool for Application Design • UAG Projects • Libraries are global (Multiple Projects) • Customization and Project are bound to an Application

  29. UAG Technical Training 03 Physical Model

  30. What you learn in this chapter • UAG Physical Model • Modeling and structuring the process • Hierarchy Levels in ISA S88 • Types and Instances • Defining the Process Model • Equipment, Control Modules and Templates • Interlocks and Links • Variables • Representation in the PLC

  31. Physical and Topological Model • Physical Model • Defines the structure according to the process • Default model based on ISA S88.01 hierarchy • Site, Area, Process Cell, Unit, … • Model can be defined in Customization • Levels according to project’s needs • Topological Model • contains the automation hardware and structure • PLC, HMI, Network

  32. Hierarchy Levels in Physical Model ISA S88 Structure Example Site Softdrinks Area Production Process Cell Ingredients Unit 01Sugar Equipment Tank01A Control Module VA21

  33. Structuring Levels in ISA S88 • Site • Concern the organization of the enterprise • Area • Concern the organization of the enterprise • Sublevel of the Site • Process Cell • Contains all the Units, Equipment and Control Modules required for batch processing • Unit • Processing activities are concentrated in a Unit • Used for a recipe

  34. Equipment Module Equipment Module Describes a functional group Holds Control Modules Level of Template instantiation Variables can be declared Linking to the physical Model Allocation of the PLC Linked to the HMI and a picture Non ISA S88 models Functionality of an Equipment can be set up for each hierarchy level Control Modules can be placed all over the Physical Model

  35. Control Module • Single Function of the Process • Physical : motors, valves, sensors, … • Logical: PID loops, counters, ... • Contains all aspects of the automation • PLC (DFB, EFB) • HMI (Symbols, Faceplates) • Communication relationship • Variables and their behaviour in the HMI • Alarming, Trending, Historical Data • Physical Model • Linked to one Equipment • Interaction with other Control Modules linked to the same or other Equipment

  36. Template Instance • Higher Level Function of the Process • Multiple pre-wired Control Modules • e.g. PID, Sequence • Instantiation in Physical Model • Template is instantiated as • Equipment Module • Couple of Control Modules • HMI link can be a common symbol • Control Modules and variables can be added to instance • Details see Chapter 8

  37. Instantiation from Types • SCoD as Type for Control Modules • SCoD: Smart Control Device • Type definition of a Control Module • Member of a Library • Designed in the SCoD-Editor • based on a DFB or EFB • contains an HMI representation (symbol, behaviour) • definition of variables and pin usage • definition of communication, alarming etc. • After design the SCoD is committed for use

  38. Process Application Library • SCoDs from the standard UAG Process Application Library • Motor & Valves • CRKBRK_P20 Circuit Breaker • VALMO_P20 Monostable Valve • VALBI_P20 Bistable Valve • VALPRO_P20 Proportional Valve • MCCDOL_P20 Direct Online Starter • MOT1D1S_P20 Motor 1 Direction 1 Speed • MOT1D2S_P20 Motor 1 Direction 2 Speed • MOT1DVS_P20 Motor 1 Direction 2 Speed • MOT2D1S_P20 Motor 2 Direction 1 Speed • MOT2D2S_P20 Motor 2 Direction 2 Speed • MOT2DVS_P20 Motor 1 Direction 2 Speed • Standard Functions • COUNTER_P20 Counter • HOURMET_P20 Hour Meter • INTERLCK_P20 Interlock • ADD4_P20 Math - Adding • MUL4_P20 Math - Multiplying • OPMODE_P20 Operation Mode • TIMER Timer • Inputs & Outputs • DIGIN_P20 Digital Input • DIGOUT_P20 Digital Output • ANAIN_P20 Analog Input • ANAOUT_P20 Analog Output

  39. Process Application Library • SCoDs from the standard UAG Process Application Library • Control Functions • DIGICONT_P20 Digital Controller • PIDCTRL_P20 PID Controller • PIDCTRLAD_P20 Advanced PID Ctrl. • SCHEDULER_P20 Scheduler • RCONBAT_P20 Batch Ratio Ctrl. • RCONCON_p20 Continuous Ratio Ctrl. • SEQUENCE_P20 Sequencer • TOTALIZER_P20 Totalizer • Process Specific • PUMSEL_P20 Pump Selection • TANKCTRL_P20 Tank Control • Schneider Devices • MOTATV_P20 ATV31/61/71 • PM700S_P20 Power Meter • ION73_P20 Energy Meter • TESUIO_P20 TeSys U • PLCSTAT_P20 PLC Diagnostics

  40. Representation of Physical Model • Representation of Area, Process Cell, Unit • PLC: groups in the Unity Pro project browser(same structure as in UAG) • HMI: no equivalent • Representation of Equipment and Control Modules • PLC • One Equipment = One Section • One Equipment and all its Control Modules are usually assigned to the same PLC • HMI • An Equipment can be freely assigned to a picture of the HMI • One picture can contain more than one Equipment • The equipment and all its Control Modules are usually assigned to the same picture

  41. Create a Level in the Physical Model • Area, Process Cell & Unit • Select “New …” from context menu • Enter a (unique) name • Enter a description

  42. Create an Equipment Module • Equipment Module • Select “New …” from context menu • Enter a name and a description • Section name is derived from Name • PLC and HMI link is set after the Topological Model is defined

  43. Create a Control Module • Control Module • Select “New …” from context menu • Select needed SCoD-Type form Pop Up • Enter a name and a description • Instead of using the context menu, drag & drop the SCoD from the library Window

  44. Interactions of Control Modules • Links • connection to variables or other Control Modules • represented by link lines in the PLC program(in the same section only) • used on unconnected input pins • simply created by drag and drop of variables • Interlocks • definition of interlock logic for a single input pin • only for Control Modules with interlock input pin defined in the SCoD Editor (e.g. MOT1D1S) • device can have one or more interlocks • created by defining a logical condition of variables

  45. Definition of an Interlock • Define an Interlock • Select “Open Interlock” from context menu • Place Function Blocks as needed • Link blocks as needed • Open Variable Browser from context menu • Drag & drop variables to pins • Connect last output to the Interlock Input • Apply interlock

  46. Interlock representation • Interlock representation • generated code in Unity Pro similar to the code in UAG • indicated as Comment box in front of the function block

  47. Variables in UAG • Come along with the Control Module • they are automatically generated during instantiation • Additional Variables can be defined in UAG for • Equipment Modules • Control Modules

  48. Variable Representation in PLC and HMI • Standard Name Creation Rule • Control Module Level • Concatenation of the variable and two parent objects • EQname_CMname_VARname • Equipment Module Level • Concatenation of the variable and one parent objects • EQname_VARname • Other Name Creation Rules • Naming rules can be set up in the Customization using all levels of the Physical Model, either the complete name or a part of it • Maximum length of 32 characters in Unity has to be respected Declaration : EQ – Equipment Module, CM – Control Module,VAR – Variable

  49. Variable Declaration • Variables can be defined in UAG for • Equipment Modules • Control Modules • Declare a variable • Select “Open Variable” from context menu • Select “New” from context menu in the variable browser • Define properties for new variable (see next slide) • Apply new variable

  50. Variable Basic Properties • Name • Name of the variable • Data Type • must be defined for each variable,e.g. Bool, Word, Byte, Int, Real, Time, User defined DDTs,.. • Connection Type • part of the application, where the variable is used (see next slide) • Initial Value / Update initial Value • an initial value can be assigned • Update Initial Value • Graphic representation of the variable in the SCADA (HMI variables only)

More Related