2. Date: 20.12.2006
File:ST-PCS7SYS_V70_mp.2
SIMATIC PCS 7
Siemens AG 2003. All rights reserved.
SITRAIN Training for
Automation and Drives
PCS 7 Multiproject
PC
Server ES
Terminal bus
Plant bus
PC
ES1
AS
01
C
P
U
C
P
P
S
AS
02
C
P
U
C
P
P
S
PC
ES2
PC
OS
Multiproject
Project1 Project2 Project3
Master data
library
3. Date: 20.12.2006
File:ST-PCS7SYS_V70_mp.3
SIMATIC PCS 7
Siemens AG 2003. All rights reserved.
SITRAIN Training for
Automation and Drives
Creating Multiprojects
ES server
or +
MP P1
P2
LIB
ES server
MP P1
LIB
ES-x
P2
MP = Multiproject, stored on the hard disk of the server ES
P1 = Project within the MP, stored on the server ES
P2 = Project within the MP, stored (alternatively) on the server ES or on the distributed ES
LIB = Master data library, within the MP
4. Date: 20.12.2006
File:ST-PCS7SYS_V70_mp.4
SIMATIC PCS 7
Siemens AG 2003. All rights reserved.
SITRAIN Training for
Automation and Drives
Multiproject (Moving and Editing the Project)
ES server
MP P1
P2
LIB
ES-x
P2
ES server
MP P1
Link
LIB
ES-x
P2
P2-
old
Save as:
•Without reorganization
•Insert in MP
•Select current MP
•Replace current project
•UNC path
1. Move
2. Edit
5. Date: 20.12.2006
File:ST-PCS7SYS_V70_mp.5
SIMATIC PCS 7
Siemens AG 2003. All rights reserved.
SITRAIN Training for
Automation and Drives
Multiproject (Save/Archive MP - 1)
ES server
MP P1
P2 link
LIB
ES server
Save as:
•Without / with
reorganization
Save
Archive
MP1 P1
P2
LIB
ES server
MP P1
P2 link
LIB
P2 link
ES server
MP.ZIP
P1
P2
LIB
7. Date: 20.12.2006
File:ST-PCS7SYS_V70_mp.7
SIMATIC PCS 7
Siemens AG 2003. All rights reserved.
SITRAIN Training for
Automation and Drives
Multiproject (Restoring an Individual Project)
ES server
MP P1
P2
LIB
ES-x
P2
ES server
MP P1
P2 link
LIB
ES-x
P2
P2-
old
3. Save as:
•Without reorganization
•Insert in MP
•Select current MP
•Replace current project
•UNC path
4. Result
1. Close P22. Delete P2-old (not the link in the MP!)
8. Date: 20.12.2006
File:ST-PCS7SYS_V70_mp.8
SIMATIC PCS 7
Siemens AG 2003. All rights reserved.
SITRAIN Training for
Automation and Drives
Multiproject (Update Projects)
PC1
ES1
AS
01
C
P
U
C
P
P
S
AS
02
C
P
U
C
P
P
S
PC2
ES2
Multiproject
Project 1 Project 2
Network 1 Network 2
System bus (universal subnet due to update)
Connection 1
Refer.: XYZ
Connection 1
Refer.: XYZ
9. Date: 20.12.2006
File:ST-PCS7SYS_V70_mp.9
SIMATIC PCS 7
Siemens AG 2003. All rights reserved.
SITRAIN Training for
Automation and Drives
Description of Task
Terminal bus
AS
01
C
P
U
C
P
P
S
PLC
SIM
C
P
U
C
P
P
S
PC
ES/OS
Multiproject
PRO_ASi PRO_OSi PRO_SIMMaster data
library
Plant bus
MPI bus
COURSE_V7 COURSE_V7 ES_Distributed
Share
11. Date: 20.12.2006
File:ST-PCS7SYS_V70_mp.11
SIMATIC PCS 7
Siemens AG 2003. All rights reserved.
SITRAIN Training for
Automation and Drives
Multiproject: Prepare Distributed Working
ES
MP
PRO_ASi
LIB
ESE:
Course_V7
D:
Course_V7
ES
MP
LIB
E:
Course_V7
Retrieve projects Insert project in multiproject
PRO_OSi
MP
PRO_ASi
LIB
PRO_OSi
PRO_ASi
PRO_OSi
PRO_SIM
PRO_SIM
PRO_SIM
PH Update
PH Update
ES_Distributed
E:
Course_V7
ES
MP
LIB
PRO_ASi
PRO_OSi
PRO_SIM
Shift project
3 4
5 6
12. Date: 20.12.2006
File:ST-PCS7SYS_V70_mp.12
SIMATIC PCS 7
Siemens AG 2003. All rights reserved.
SITRAIN Training for
Automation and Drives
Multiproject: Distributed Working
E:
Course_V7
ES_Distributed
ES
MP
LIB
PRO_ASi
PRO_OSi
PRO_SIM
8
7
9
13. Date: 20.12.2006
File:ST-PCS7SYS_V70_mp.13
SIMATIC PCS 7
Siemens AG 2003. All rights reserved.
SITRAIN Training for
Automation and Drives
Multiproject: Restoring the Distributed Project
E:
Course_V7
ES_Distributed
ES
MP
LIB
PRO_ASi
PRO_OSi
PRO_SIM
10
11
16. Date: 20.12.2006
File:ST-PCS7SYS_V70_mp.16
SIMATIC PCS 7
Siemens AG 2003. All rights reserved.
SITRAIN Training for
Automation and Drives
Multiproject: Updating the Networks
Updating MPI networks in the multiproject
PLC
SIM
C
P
U
C
P
P
S
PC
ES/OS
PRO_OSi PRO_SIM
MPI_OS MPI_SIM
16
18. Date: 20.12.2006
File:ST-PCS7SYS_V70_mp.18
SIMATIC PCS 7
Siemens AG 2003. All rights reserved.
SITRAIN Training for
Automation and Drives
Multiproject: OS Test with PLCSIM
Requirements: The OS Runtime has previously communicated
with your AS.
Close PLCSIM (if still open)
Activate OS.
If a communication fault is displayed, do not acknowledge, but move the
message window away from center
Start PLCSIM.
Acknowledge previous error message
Download saved project from PLCSIM, possibly download PLCSIM from CFC
Set PLCSIM to RUN.
Now log on to OS Runtime, and test. The two connections should
function (named connection to your AS and MPI to the PLCSIM)
Editor's Notes
ContentPage
PCS 7 Multiproject............................................................................................................................2
Creating Multiprojects.......................................................................................................................3
Multiproject (Moving and Editing the Project)....................................................................................4
Multiproject (Save/Archive MP - 1)...................................................................................................5
Multiproject (Save/Archive MP - 2)...................................................................................................6
Multiproject (Restoring an Individual Project)....................................................................................7
Multiproject (Update Projects)..........................................................................................................8
Description of Task .........................................................................................................................9
Multiproject: Preparation..................................................................................................................10
Multiproject: Prepare Distributed Working.........................................................................................11
Multiproject: Distributed Working......................................................................................................12
Multiproject: Restoring the Distributed Project..................................................................................13
Multiproject: Test AS Program with PLCSIM.....................................................................................14
Multiproject: Prepare OS Test with PLCSIM (1)................................................................................15
Multiproject: Updating the Networks.................................................................................................16
Multiproject: Insert Picture into PH and Compile OS.........................................................................17
Multiproject: OS Test with PLCSIM...................................................................................................18
MultiprojectThe folder where all the projects and libraries are stored for an automation solution is called a multiproject; it contains one or more STEP 7 projects and optionally also libraries. The projects within the multiproject can contain objects with cross-project relationships (e.g. cross-project S7 connections).
Benefits of Multiproject
If projects are part of a multiproject, they can be created with a smaller size and clearer structure. Using multiprojects, you can e.g. create one project for each operator and divide the stations among the operators for distributed execution. Cross-project functions allow you to handle a multiproject almost like one single project.
Examples of Cross-Project Functions
Cross-project functions in STEP 7 (basic package):
- Save as (store multiproject with all projects at another location)
- Archive (multiproject with all projects)
- Match cross-project networking (e.g. merge subnets)
- Update view (all projects of a multiproject)
Other cross-project functions (with PCS 7, SIMATIC BATCH)
- Compile OS (transfer AS-OS connection data)
- Export SIMATIC BATCH plant data
Creating MultiprojectsThere are two ways to create a multiproject:
1. On the ES that is used as the server ES, you can create the multiproject with the individual projects and the master data library. All folders are saved on the hard disk of the server ES (MP, P1, P2 and LIB)
2. The multiproject and part of the projects are created on the server ES. The folders MP, P1 and LIB are saved here. Another project (P2) is created on another ES (ES-x) and later included in the multiproject.
NoticeBefore creating the multiproject and associated projects, create a directory on each local hard disk of the participating ESs and enable it for sharing with all the participating configuring engineers. All other access paths are handled via the Windows network environment, the computer name and share name for the directories.
Each project can contain an AS, OS or a combination of several ASs and OSs. The combination is created in such a way that the individual projects can later be distributed among the individual ESs (configuring engineers). The library remains on the server ES so it can be accessed by all.
The server ES should be entered in one project of the multiproject; this allows you to perform compiling and downloading centrally.
As long as the PC interface of the respective ES is set in PG operation in the distributed, individual projects (via "Set PC Station" and "Set PG/PC Interface"), there is no need for the explicit presence of an ES in these projects. The final network configuration is performed later in the multiproject after the projects have been synchronized.
RemarkImmediately after creating the projects in the multiproject, set the display language for each project/library via
Options -> Language for Display Devices
MoveOn the server ES, go to the multiproject and select the project (P2), then select
File -> Save as...
to copy it to the distributed ES x. In doing so, please apply the settings shown on the slide.
The purpose of the procedure is to store a copy of the project on the hard disk of the distributed ES x (P2). The selected options set up a link in the multiproject to the project on the distributed ES x. The multiproject version is updated via this link. The old version of the project remains on the hard disk of the server ES under its original name (P2 old version).
In the event of an error occurring on the ES x, this older version can be used as the backup for project P2.
EditProject P2 which is saved on the distributed ES x can be locally processed. Here, you can also access the master data library and the charts of the other projects from SIMATIC Manager across MPs.
RemarkIf a project that was started on another ES is to be included in a multiproject, this is possible from the multiproject itself as described below.
Select the MP, then
right-click and select Multiproject -> Insert in multiproject (Browse if necessary)
The selected project is now included in the multiproject.
Save MP asFor backup purposes, you can also save a multiproject explicitly. In the SIMATIC Manager, open the multiproject and select its icon.
Select
File -> Save as... Option with (without) reorganization
to copy the multiproject to another directory of your choice and open it there.
Note 1If you use this procedure, the projects are also saved in the same directory and the links to the distributed ESs are removed!
This means that you then need to use "Save as..." again to distribute the individual ESs (see previous slide).
Archiving MPsAfter closing the multiproject, select
File -> Archive
to initiate archiving. First, you must select the multiproject you want to archive. Next, select the directory you want so save the archive to and enter a name for the archive.
The result is a "zip" file containing the entire MP contents.
Retrieving MPsYou first need to prepare (share) the directory or, alternatively, empty the old directory (delete MP).
Select
File -> Retrieve
First, you select the multiproject to be retrieved, then the target directory where you want to save the retrieved file.
Note 1 applies here too, i.e. links are removed.
Note 2If when trying to save, reorganize or archive the multiproject, a message is displayed "...being processed by another application. Close and restart...", one of the following tips may help:
- For archiving, you must first close the multiproject and each project. Then exit the SIMATIC Manager and launch it again. Now start archiving again.
- If the information about existing access operations indicate an OS (WinCC), the "emergency brake" can be pulled using the "Reset_WinCC.vbs" script. In a typical installation, you can find this script under
C:Program FilesSIEMENSWINCCinReset_WinCC.vbs
The script stops all WinCC processes and services that work with WinCC. Access to the project database is enabled.
You must subsequently restart the SIMATIC Manager.
Restoring an Individual Project
To restore a project that was decentrally edited to the server ES (e.g. to distribute it to another ES), proceed as follows:
First, delete the old project (P2-old) - either using the SIMATIC Manager, as a single project or via the Windows Explorer)
Select the current project (P2) in the MP and select
File -> Save as... (see options in the slide)
to copy it to the location where the deleted project stood in the multiproject directory. The previous project version (P2) remains on the distributed ES-x and can either be deleted or used as an additional backup copy until the process is completed.
Now the Server ES can redistribute the projects among the decentralized ESs.
.
Project 1If project 1 on ES1 is not yet included in the multiproject, you can use NetPro e.g. to configure "Subnet 1" as system bus. Connections originating from AS01's CPU to a station that is not in the same project are set up as connections to a station in an "unknown project". For this type of connection, you need to enter a "Connection name (reference)" in the Properties dialog box (e.g. "XYZ"). It is called an "open connection".
Project 2If project 2 on ES2 is not yet included in the multiproject, you can use NetPro e.g. to configure "Subnet 2" as system bus. Connections originating from AS02's CPU to a station that is not in the same project 2 are set up as connections to a station in an "unknown project". For this type of connection, you need to enter a "Connection name (reference)" in the Properties dialog box (e.g. "XYZ").
RemarkConnections in different projects that are later merged in the multiproject, must have the same connection names (references="XZY"). The above described procedure is not necessary if the projects were already inserted in the multiproject when the connection was created. If this is the case, when you set up a connection in NetPro, the other station is selected via the multiproject (it is offered for selection in the screen).
Update ProjectsSelect
File -> Multiproject -> Update projects
to merge subnets and connections that were originally created in separate projects - as part of the "project update". The subnets that originally had their own names (e.g. "Subnet 1" and "Subnet 2") are merged under a new name (e.g. "system bus").
"Open connections" from the two projects having the same reference are also made.
Starting pointYour multiproject with the projects PRO_ASi, PRO_OSi and master data library are present in the "Course_V7" folder.
The "ES_Distributed" folder is created for external storage of a project (created for the exercise on your ES, but could also be present on the hard disk of a different PCS 7 ES).
Both folders are shared and accessible under Windows. (If they are present on different ESs, the login name and password of the configuration engineer must be known on both computers.)
A ready-made PRO_SIM project exists for importing into your multiproject (ask your trainer for the storage location).
RemarkThe objective of the exercise is the handling of projects and networks within a multiproject (external storage, editing and restoring).
If the external storage of the project is to the neighboring ES, the configuration engineers there may only observe your operations. They can only process the externally stored project after you have finished swapping it out!
However, with respect to handling, there is no difference whether this project is saved in a directory on your own ES hard disk or moved to a network drive (of another PC).
In order to avoid these delays, a separate directory is shared for the project to be stored externally. PLC_SIM is used to test the additional program (in order to also become acquainted with this test option). Since the PLC_SIM option is installed on every PC, an MPI connection to it can be set up for test purposes. Online tests can then also be carried out.
PreparationsPrepare your ES for the following exercises. On the local hard disk "E", create a directory called "ES_Distributed" and share it using the same share name. It is to be subsequently used for "external storage" of a distributed project, and read and write operations should be possible on it. Also share the folder containing the multiproject (Course_V7 in this case).
---------------------------------------------------------------------------------------------------------
Steps1. Use the Windows Explorer to create the "ES_Distributed" directory on the "E" drive.
2. Share this with full access.
---------------------------------------------------------------------------------------------------------
Create Folder1. Open the Windows Explorer (right-click the START button in the Windows taskbar and select "Explorer").
Select the E drive, click in the right pane,
right-click and select New Folder
Call the new folder "ES_Distributed".
Share Folder2. Point to the new folder,
right-click and select Share... Share this folder
then click the
Permissions button
to ensure the other configuring engineers can access the directory (and subdirectories) from other ESs.
Repeat the procedure for the "Course_V7" directory containing the multiproject.
RemarkYou only set sharing for the main directory. Do not change the permissions for any subdirectories that may be present!
Retrieve project3. Open the SIMATIC Manager, and select
File Retrieve
to retrieve the PRO_SIM (ProSim.ZIP) project to the "Course_V7" directory.
Insert in MP4. Open your multiproject. Select the MP. Select
File Multiproject Insert in multiproject
to search for the previously retrieved PRO_SIM project, and insert it.
PH Update5. Update the plant hierarchy:
The source is PRO_SIM
The target is PRO_OSi.
In a later step, you are to monitor both ASs (ASi and PLC_SIM) from your OS.
Shifting the project (normally to a drive of the distributed ES)
6. Move the PRO_SIM project to the "ES_Distributed" directory (target). First, select the PRO_SIM project to be moved and select
File Save as… and select the options
"Insert in multiproject", "Current multiproject", "Replace current project"
ProcessingFirst close the multiproject in the SIMATIC Manager (it need not be open on the distributed ES).
At this point, normal processing on the distributed ES would be continued. In our exercise, carry out all procedures on your ES.
7. Open just the PRO_SIM project from the "ES_Distributed" directory by selecting
File Open User projects
Do not proceed via the multiproject.
8. Open your master data library from the "Course_V7" directory using
File Open Libraries
Do not proceed via the multiproject.
9. Insert the VAL_MOT and V_SIM_FB blocks from the master data library into the CFC, and interconnect them.
Finally, close both windows (project and library).
RemarkYou can open every project or every library of the multiproject from the distributed ES without these having to be open on the central ES itself.
The central ES server or the directory enabled there need only be accessible over the LAN if something has to be copied from or inserted there.
If all required data/blocks are already on the distributed ES, it is possible to work there without the LAN.
Deleting the old version (of the moved project)
10. According to the multiproject, the "PRO_SIM" component is located on the distributed ES. Delete the PRO_SIM project, which still remains in the "Course_V7"directory (after you have moved it to the ES_Distributed directory using Save as... (only in the editing sense, but actually only copied)).
Restoring to the MP
11. Move the current PRO_SIM project back to the "Course_V7" directory. This updates the status for the MP. Use the same procedure as with "Decentralization".
The "old" state now present in the "ES_Distributed" directory can subsequently be saved or deleted there.
Start PLC_SIM12. Click the icon labeled with 12 (see slide). The PLCSIM desktop is opened. PLCSIM internally converts the programming interface of the SIMATIC Manager to MPI. It represents an S7-300 or S7-400 CPU which is still empty.
Load HW Config13. Load the HW Config of the AS from the PRO_SIM project. The screen forms are called as if the AS were connected via MPI. From the PLCSIM window, you can select
Simulation Save target system as
to save the downloaded station (using HW Config and the program that is still empty)
NoteAn S7-CPU has the default MPI address "2". This should be used when downloading the PLCSIM for the first time. It subsequently has the address defined in the project.
Download charts14. Select the chart folder of the AS and download it using
right-click and select Download PLC
Use the download option
"Download to test CPU (complete program)"
TestCarry out the test in the CFC as usual.
Supplement PC HW Config
Note!Before you supplement the HW Config, you should guarantee that your OS can communicate in runtime with your AS (download the S7 connection if necessary), and then deactivate.
15. Because PLCSIM can only be addressed over MPI, revise the HW Config of your ES/OS to include a PROFIBUS/MPI CP (e.g. 5611 or compatible), even if one is not physically present.
The slot is irrelevant.
In the properties of the CP 5611, convert the interface to MPI and set the MPI address = 0 (PLCSIM has the MPI address = 2 as default).
Network the CP with the MPI network existing in the project.
Do not download to the PC if a CP is not present. Following successful tests, the CP can be removed again.
This addition enables you to select the MPI route when compiling the OS.
Updating networks16. Select the multiproject icon in the SIMATIC Manager and
right-click and select Multiproject Adjust projects
to start combination of the networks.
Combine the MPI networks of the PRO_OSi and PRO_SIM projects.
A route is then present for NetPro between the OS and the PLCSIM.
When compiling the OS later, this path is selected as the connection between OS and PLCSIM.
Add to PH17. The "Tank farm" folder in the PH is assigned to your OS in the PRO_OSi, whereas the AS assignment in the PRO_SIM indicates PLCSIM. Through insertion of a picture (e.g. "BildSim" in the "Pumps" folder in the PH), the VAL_MOT block from the CFC in the PH folder of the same name is recorded when compiling the OS, and an associated block icon is positioned in the picture.
Compile18. When compiling the OS, assign the MPI connection to the "Tank farm" area in the "Compile dialog".
Online test19. For the runtime test of the expansion using PRO_SIM in addition to the existing system, please observe the following sequence of steps (see slide).
If you start with the PLCSIM switched on, you can only test the expansion from PRO_SIM, the link to the real AS is not established. If you subsequently switch PLCSIM off, only communication with the real AS functions.