1 / 25

Chapter 6 Application Structures

Chapter 6 Application Structures. Course T314. Application Structures. Overview. Objectives After this chapter you should be able to : Navigate in the Project Explorer Describe application structures Describe the POU editor Reference Documentation

clea
Download Presentation

Chapter 6 Application Structures

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. Chapter 6Application Structures Course T314

  2. Application Structures Overview • Objectives After this chapter you should be able to: • Navigate in the Project Explorer • Describe application structures • Describe the POU editor • Reference Documentation • 3BSE041880 IndustrialIT 800xA - Control and I/O Getting Started • 3BSE035980 IndustrialIT 800xA - Control and I/O Basic Control Software - Introduction and Configuration

  3. Application Structures Application Structures • Automation Solution • Project Explorer • Program Organization Unit (POU) Editor • Test Mode / Control Structure – Project Explorer

  4. AutomationSolution Automation Solution 800xA System Plant Explorer / Engineering Workplace Control Builder M Project Explorer Handles one Control Project Handles many Control Projects Control Project administration Control Project configuration Synchronization Faceplates and Alarm Lists Download and testing AC 800M Controller Operator Workplace

  5. AutomationSolution Control Network / Control Project • An automation system might contain a number of Control Networks representing different parts of a large plant. • Within each Control Network, you can create a number of Control Projects. A Control Project contains the configuration data for libraries, applications, connected hardware, etc. • Each application contains programs and additional objects (data types, function block types, control module types) that are used within the application. • Each program is connected to a task, which decides how often the program is executed.

  6. AutomationSolution Start Control Builder M

  7. Application Structures Application Structures • Automation Solution • Project Explorer • Program Organization Unit (POU) Editor • Test Mode / Control Structure – Project Explorer

  8. Project Explorer Overview and Online Help

  9. Project Explorer Toolbar Buttons

  10. Project Explorer Libraries / Applications / Controllers • Max 64 programs per application • Max 256 applications per Control Project • Max 8 applications per controller • Max 32 tasks per controller • Max 32 controller per Control Project

  11. Project Explorer Structured Text Sequential Function Chart Instruction List Step 1 N FILL LD A ANDN B ST C C:= A AND NOT B; Transition 1 Function Block Diagram Step 2 S Empty AND A C B Ladder Diagram Transition 2 A B C -| |--|/|----------------( ) Step 3 Languages according IEC 61131-3

  12. Project Explorer Control Modules and Programs Application Control Module 1 Control Module 2 Control Module N Program 1 Program 2 Program N

  13. Project Explorer Multi-User Engineering

  14. Application Structures Application Structures • Automation Solution • Project Explorer • Program Organization Unit (POU) Editor • Test Mode / Control Structure – Project Explorer

  15. POU Editor Application Function Block Function Function Function Block Program Program Function Block Code Code Code Code Code Code Code Program Organization Units

  16. POU Editor Editor Overview

  17. POU Editor Declaration Pane • The variables in the program are the holders of values. They are declared by giving each a name and by assigning a data type. Variables can be written in Microsoft Excel and then copied and pasted to the declaration pane of the POU editor. • Function blocks must be declared in the “Function Blocks” tab before they are used in the ST or IL languages (not necessary in the FBD or LD editors)

  18. POU Editor Message Pane

  19. POU Editor Code Pane

  20. Application Structures Application Structures • Automation Solution • Project Explorer • Program Organization Unit (POU) Editor • Test Mode / Control Structure – Project Explorer

  21. Test Mode Test (Simulation) Mode To simulate a project without using any physical hardware

  22. Synchronization Tag Shown on Both Places

  23. Synchronization Different Places • Libraries are handled in Library Structure and Object Structure. • Connected libraries are in the Application aspect of a specific application (such as Sxx_ReactorApp) in the Control Structure. • Data types, function block types and control module types are handled in the Object Structure.

  24. Synchronization Automatic Update

More Related