Ch2 v70 config_overview_en
•Als PPT, PDF herunterladen•
1 gefällt mir•773 views
TREINAMENTO EM AUTOMAÇÃO INDUSTRIAL SIEMENS PCS7
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (19)
Andere mochten auch
Andere mochten auch (20)
Ähnlich wie Ch2 v70 config_overview_en
Ähnlich wie Ch2 v70 config_overview_en (20)
Mehr von confidencial
Mehr von confidencial (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Ch2 v70 config_overview_en
- 1. Date: 15.11.2006 File: ST-PCS7SYS_V70_üb_pro.1 SIMATIC PCS 7 Siemens AG 2003. All rights reserved. SITRAIN Training for Automation and Drives ConfigOverview
- 2. Date: 15.11.2006 File: ST-PCS7SYS_V70_üb_pro.2 SIMATIC PCS 7 Siemens AG 2003. All rights reserved. SITRAIN Training for Automation and Drives M TICA 1T101 TI 1T102 EI 1E101 UV 1U102 UV 1U101 UV 1U103 LAH 1L101 LAL 1L102 Heating 1E101 Group No. Group No. Unit No.: 1 : Unit A 2 : Unit B 3 : Unit C 4 : Unit D Unit No.: 1 : Unit A 2 : Unit B 3 : Unit C 4 : Unit D Convention for tag names Example
- 3. Date: 15.11.2006 File: ST-PCS7SYS_V70_üb_pro.3 SIMATIC PCS 7 Siemens AG 2003. All rights reserved. SITRAIN Training for Automation and Drives PCS Hardware DP (ET 200M) DP (ET 200M) AS (S7 417-4) OS (PC with WinCC) AS (S7 414-3) MPI/PROFIBUS/Ind. Ethernet PROFIBUS DP HMI system Automating - Closed-loop control - Open-loop control - Monitoring - Signaling Distributed process signal converters Sensors and actuators Plant bus DP bus ES (PC) IM IM S7ONLINE
- 4. Date: 15.11.2006 File: ST-PCS7SYS_V70_üb_pro.4 SIMATIC PCS 7 Siemens AG 2003. All rights reserved. SITRAIN Training for Automation and Drives Solution Principle (AS) AI DI DO Diagnostic and module drivers CPU load measurement (System performance) SFC CTRL_PID REACTOR Process (Reactor) AO etc. Hardware Software (Module drivers with diagnostics are generated automatically by CFC) (Other) Possible process simulation Library Graphic config. tool Program. SCL (I/O modules) CH_AI CH_DO Library Library (Channel drivers are connected to the process tag individually in the CFC)
- 5. Date: 15.11.2006 File: ST-PCS7SYS_V70_üb_pro.5 SIMATIC PCS 7 Siemens AG 2003. All rights reserved. SITRAIN Training for Automation and Drives
- 6. Date: 15.11.2006 File: ST-PCS7SYS_V70_üb_pro.6 SIMATIC PCS 7 Siemens AG 2003. All rights reserved. SITRAIN Training for Automation and Drives Configuration Steps (AS) Create project (SM*) Create resources (SM view -> Component view) * SM* - SIMATIC Manager Create plant hierarchy (SM view -> Plant hierarchy or SM view -> Process object view) Assign resources (SM both views PH or PO) Configure hardware (SM view -> Component view) * Configure SW (CFC, SFC, SCL, messages, archive tags) Test+commission (configuration tools) Select block libraries /create project-specific library Document
- 7. Date: 15.11.2006 File: ST-PCS7SYS_V70_üb_pro.7 SIMATIC PCS 7 Siemens AG 2003. All rights reserved. SITRAIN Training for Automation and Drives Project Environment Factory 1 Basic materials Factory 2 Dyes
- 8. Date: 15.11.2006 File: ST-PCS7SYS_V70_üb_pro.8 SIMATIC PCS 7 Siemens AG 2003. All rights reserved. SITRAIN Training for Automation and Drives Our Plant (Factory 2) Tank Farm North Group1 Tank Farm East Shipping Control building Group 4 Group 3 Group 7 Group 2 Group 1 incl. - Unit A - Unit B - Unit C - Unit D. Group 5 Group 6 Mixed plant Tank farm Shipping AS8 AS7 AS6 AS5 AS4 AS3 AS2 AS1 Tank Farm South Factory 1 Factory 2 Group2 Group3 Group4 Group5 Group6 Group7
- 9. Date: 15.11.2006 File: ST-PCS7SYS_V70_üb_pro.9 SIMATIC PCS 7 Siemens AG 2003. All rights reserved. SITRAIN Training for Automation and Drives Configuration Steps (OS) Setup OS/project editor (optional) Create OS objects via plant hierarchy or process object view SM* - SIMATIC Manager Compile and download OS Test+commission (configuration tools) Edit individual objects (pictures, reports) Create resources (SM view -> Component view) * Document
- 10. Date: 15.11.2006 File: ST-PCS7SYS_V70_üb_pro.9 SIMATIC PCS 7 Siemens AG 2003. All rights reserved. SITRAIN Training for Automation and Drives Configuration Steps (OS) Setup OS/project editor (optional) Create OS objects via plant hierarchy or process object view SM* - SIMATIC Manager Compile and download OS Test+commission (configuration tools) Edit individual objects (pictures, reports) Create resources (SM view -> Component view) * Document
Hinweis der Redaktion
- ContentPage Example...........................................................................................................................................2 PCS Hardware.................................................................................................................................3 Solution Principle (AS).....................................................................................................................4 Project Environment.........................................................................................................................7 Our Plant (Factory 2)........................................................................................................................8
- Process description (using the equipment in Group 1, Unit A1 as an example): Component XThe reactor must first be empty and cold. Valve 1U101 is used to fill this component up to the L1=20% Lmax level. MixerThe mixer motor 1E101 is turned on. Component Y Valve 1U102 is used to mix this second component until the L2=80% Lmax level is reached. HeatingThe mixture is heated up to 90°C. The temperature controller 1T101 must maintain this temperature for at least two minutes. DrainingAfter the heating is turned off, product Z must be drained completely, and the mixer 1E101 must be turned off. In additionThe fill level is monitored (1L101 and 1L102). The inlet valves 1U101 and 1U102 must be closed when the upper level limit (Lmax) is reached. The drain valve must be closed when the reactor is empty. There must be a signal when the level monitor responds. Both the temperature controller and the mixer must be operated and monitored in the control room.
- Info FlowSensors, transducers, and DP process signal converters modules acquire process information. The AS processes this information and uses the same path to pass it on to the actuator. In parallel, commands are sent from the OS to the AS. AS information is displayed graphically on the OS. ET 200MThe IM 153-2 interface module converts the process signal converter (I/O module) information into message frames for and from the AS. DP busThe bus (PROFIBUS DP) transports the message frames between the AS (DP master interface) and the ET 200M interfaces. AS (S7 417-4)The DP master interface reads in the message frames in the AS. The driver blocks convert and process the message frames into process values. That is, open-loop control algorithms and closed-loop control algorithms convert the message frames into commands and send the commands back to the I/O using the same path. The values are also monitored, and messages are sent to the OS when defined events occur. Plant busThe plant bus can be MPI (Multi-Point-Interface), PROFIBUS or Industrial Ethernet. The plant bus is used for communication between the AS-OS, AS-AS, as well as between the ES and the above mentioned nodes for the purpose of configuring and commissioning. OS (WinCC)Data coming from the AS - embedded in process displays- are displayed graphically as measured values with a time-based sequence and as messages with classification. The plant operator's commands are passed on to the relevant AS and the response information displayed. The configuring and commissioning steps shown on the following pages are structured on this basis. ES (STEP 7)The entire project is carried out on the Engineering Station (ES). The software accesses the plant bus via "S7ONLINE". Access can be established via different hardware components and is settable.
- AS solutionThe block libraries contain different blocks that form individual parts of the solution. Drivers, operator control blocks and technological blocks (closed-loop controllers, motors) are used. Inputting/outputting process signals The single-channel drivers (CH_AI, CH_AO, CH_DI and CH_DO) are located in the PCS 7 library. These drivers are inserted in the CFC in which the process value is needed. The symbolic name of the value is used to select the connection to the process value (via the symbol table). The name is assigned to the individual hardware channel during the hardware configuration. No additional parameters must be set, except for the measuring range. After CPU selection, the CFC generates the necessary module drivers during compilation, along with all of the necessary parameter settings (which are read from HW Config). With V7.0 and higher, the CFC also inserts the CPU_RT block, which can carry out runtime measurements and avoid a CPU stop in the event of an overload. RemarkWith V5.2 and higher, you can also use universal drivers (CH_U_AI, CH_U_AO, CH_U_DI and CH_U_DO). They can be used for S7-400, ET 200M or Profibus PA field devices. If you want to configure an older CPU (from V4) using PCS 7 V6.0, you must continue to use the V4 libraries, or the CPU will be upgraded. Temperature controlYou can implement temperature control, for example, by using the CTRL_PID block from the same library. This block also has the faceplate necessary for operator control and monitoring (for WinCC). SignalingYou can use the MEAS_MON block, for example, for this. This block monitors the level and signals a limit violation to the OS. The controller block itself can also monitor its own process variable and signal limit violations to the OS.
- OperationIf you also want to open/close the valves manually, you can use simple operator control blocks for digital values (OP_D) or the valve blocks (VALVE) with built-in operator control and monitoring. Plant simulation You can simulate the plant using the REACTOR block (in a user library). Sequential controlUse the SFC Editor for this. This editor can only access data that were configured previously, such as with the CFC Editor.
- IntroductionThe steps described below are a simplified representation. For more detailed information about the sequences and what needs to be taken into account at the outset, please refer to the "PCS 7 - Engineering System Configuration Manual", Chapter 3 "Planning the Plant Engineering". Block librariesThe libraries that are not used should be hidden via the SIMATIC Manager file management function. It can be advantageous to create a separate library for each project in the same project directory (master data library). To start, the blocks that will be used later in the project are collected there. If in the future the software is upgraded, this library can be updated across all subprojects. Create projectUse the SIMATIC Manager to create the new project. The Manager handles all of the data generated during configuration. ResourcesResources include the ASs in the project (with their hardware), the S7 programs (with blocks in the user program and with chart containers and the blocks imported to these chart containers via CFC), networks, as well as the ES/OS PCs. HardwareWithin the project, the AS/PC hardware components (CPU, CP, and I/O modules) must be configured in accordance with the hardware structure. This configuration is downloaded to the AS and assigns the parameters for the modules. Plant hierarchy(PH) A hierarchy (with a maximum of eight levels) is used to display the configured plant in the project. This hierarchy can correspond to the HID system (comparable to a directory tree). Assign resourcesOne AS and/or one OS can be assigned to each hierarchy level. The subordinate levels can inherit the assignment. CFC/SFC charts, OS displays, reports or documents belonging to the assigned AS/OS can be inserted in each level (as "leaves" on the "branch"). SoftwareAS-specific or OS-specific tools are used to configure the software as needed. From the AS, you open the object in the plant hierarchy to start the software. Test + CommissionThe software must be loaded onto the configured hardware for this. Each configuration tool you use provides testing opportunities for online operation.
- Project EnvironmentOur project is part of a dye manufacturing plant. The basic materials are manufactured in Factory 1 and are transported from there to Factory 2. In Factory 2, the basic materials are stored in dedicated storage tanks. After undergoing the manufacturing process, the end product is stored in a different section of the tank farm for transport purposes.
- Plant OverviewThe plant to be automated is part of Factory 2 and is broken down into several different zones (see above): Tank Farms North, South and East Shipping Control building Groups 1, 2, 3, 4, 5, 6, 7Each configured with the following reactor units: Unit A, Unit B, Unit C, Unit D You can specify this breakdown in the plant view (on additional pages) and retrieve it again later. Automation systems Eight automation systems are used to carry out the automation tasks. The task assignment is displayed in the picture at the top right. Only part of this plant will be automated in our exercise, using one AS and one OS. NoteTasks that were originally assigned to an AS or OS can be reallocated over the plant hierarchy in a later project phase with minor configuration effort.Each participant takes on/configures a group in accordance with the training station number..
- NoteThe OS is created as a SIMATIC PC. The PC is also set up using the HW Config tool (like an AS). The basic data for a PCS 7 OS are configured using the project editor (within WinCC). Individual objects are inserted via the plant hierarchy or process object view and then completed in the appropriate editors (of WinCC). The OS must also be compiled and downloaded (like an AS). The OS PC must be networked with the ES PC for the download to work.You can find details about this in the section "HMI/Operator Control and Monitoring".