1/23/2019 11:25 PM | |
Joined: 9/27/2006 Last visit: 10/8/2024 Posts: 12285 Rating: (2685) |
Hello carlos; My first question is: why would you want to do so? If your plant is controlled with a S7-300 and a SCADA at this moment, what kind of increase in production or complexity would require PCS 7? There is a steep step between PCS 7 and Step 7 + SCADA programming. Working with PCS 7 requires a complete change in programming methods and the integration of new tools, CFC charts for the logic, SFC charts for the sequencing of the CFC control blocks. There is some programming in SCL, but none in KOP and AWL. Just as an example of the difference with step 7, OB1 is not used in the PCS 7 environment. In iots place, you must use "runtime groups" linked to various cyclic OBs, in the range OB 31-OB 37, to integrate your CFC charts. One more mportant difference: you do not program your SCADA alarms in WinCC. Rather, the CFC blocks contain links to the WinCC screens, and as you create the logic, you add alarms and messages directly in the CFC charts so they appear in the WinCC screens. Have a look at the Getting Started manual for PCS 7 v9.0, it will give you a first glance at the PCS 7 environment and the adaptation required for a Step 7 + WinCC programmer. Your learning curve will be steep, and it is highly recommended that you start with basic training on PCS 7 from Siemens. SIMATIC Process Control System PCS 7 Getting Started - Part 1 (V9.0 with APL) https://support.industry.siemens.com/cs/ww/en/view/109756196 Note: Profibus and Profinet are still the main I/O networks with PCS 7, but I do not knpw f the IM 153-1 slave is still supported by the newest versions of PCS 7. Hope this helps, Daniel Chartier |
This contribution was helpful to2 thankful Users |
Follow us on