PCS_7移植指导

SIMATIC
PCS 7 V4.x to PCS 7 V5.0 Migration Guide
03/2000
A5E00064939
Edition 01
Copyright © Siemens AG 2000 All rights reserved
The reproduction, transmission or use of this document or its
contents is not permitted without express written authority.
Offenders will be liable for damages. All rights, including rights
created by patent grant or registration of a utility model or design,
are reserved.Siemens AG
Bereich Automatisierungs- und Antriebstechnik
Geschaeftsgebiet Industrie-Automatisierungssysteme
Postfach 4848, D- 90327 Nuernberg Disclaimer of Liability We have checked the contents of this manual for agreement with the hardware and software described. Since deviations cannot be precluded entirely, we cannot guarantee full agreement. However,the data in this manual are reviewed regularly and any necessary corrections included in subsequent editions. Suggestions for
improvement are welcomed.
©Siemens AG 2000Technical data subject to change.
Siemens Aktiengesellschaft A5E00064939
Safety Guidelines
This manual contains notices which you should observe to ensure your own personal safety, as well as to
protect the product and connected equipment. These notices are highlighted in the manual by a warning
triangle and are marked as follows according to the level of danger:
Danger indicates that death, severe personal injury or substantial property damage will result if proper
precautions are not taken.Warning indicates that death, severe personal injury or substantial property damage can result if proper
precautions are not taken.Caution indicates that minor personal injury or property damage can result if proper precautions are not taken.
draws your attention to particularly important information on the product, handling the product, or to a particular part of the documentation.
Qualified Personnel
Only qualified personnel should be allowed to install and work on this equipment. Qualified persons are
defined as persons who are authorized to commission, to ground, and to tag circuits, equipment, and
systems in accordance with established safety practices and standards.
Correct Usage
Note the following:
Warning
This device and its components may only be used for the applications described in the catalog or the
technical descriptions, and only in connection with devices or components from other manufacturers
which have been approved or recommended by Siemens.
This product can only function correctly and safely if it is transported, stored, set up, and installed correctly, and operated and maintained as recommended.
Trademarks
SIMATIC®, SIMATIC HMI® and SIMATIC NET® are registered trademarks of SIEMENS AG.
Some of other designations used in these documents are also registered trademarks; the owner’s rights may
be violated if they are used by third parties for their own purposes.
Migration from PCS7 V4.x to PCS7 V5.0
A5E00064939-01iii
Contents
1
Remarks concerning migration.................................................................................1-1
1.1
Extent of migration........................................................................................1-11.2Backup before migration................................................................................1-22
Migration without using the new functions..............................................................2-13Complete migration using new functions.................................................................3-1
3.1
Hardware update...........................................................................................3-13.1.1
Updating the operating system on the S7-CPU(s) 416-2DP...........................3-13.1.2
Updating your IM153-1 and IM153-2 (ET200M).............................................3-23.1.3
Handling GSE files........................................................................................3-33.2
PCS 7 libraries..............................................................................................3-43.2.1
Backup when reusing V4.02 PCS7 libraries...................................................3-43.3
Converting the PLC.......................................................................................3-53.3.1
SIMATIC Manager: Converting the Plant Hierarchy.......................................3-53.3.2
HW Config: Adjust hardware .........................................................................3-53.3.3
SIMATIC Manager: Integrate and adapt the blocks from the new libraries....................................................................................3-63.3.4
CFC: Integrating and adapting blocks from new libraries................................3-73.3.5
CFC: Migration to value labels.......................................................................3-93.3.6
CFC: Migration from text attributes to block I/Os..........................................3-103.3.7
CFC: Run sequence after changing block types..........................................3-103.3.8
SIMATIC Manager: Migrating from CFC library blocks to basic operations (optional)..........................................................................3-113.3.9
Converting a project to the new driver blocks (optional)...............................3-133.3.10Updating the sampling interval (option)........................................................3-16
Contents
Migration from PCS7 V4.x to PCS7 V5.0
iv A5E00064939-01
3.3.11
SFC: Non-latching behavior........................................................................3-163.3.12
SFC: SFCs in runtime groups......................................................................3-173.3.13
SIMATIC Manager TH: Checking PLC-OS assignment................................3-173.3.14
CFC or SFC: Compile and load...................................................................3-183.3.15
SIMATIC Manager TH: Checking OS area identifier before transferring data to the OS..........................................................................3-183.4
Import-Export Wizard (IEW)........................................................................3-193.5
PLC-OS Engineering...................................................................................3-203.6
Information on the new driver concept.........................................................3-213.6.1
General.......................................................................................................3-213.6.2
Partial process images................................................................................3-213.6.3
Power up delay by n cycles.........................................................................3-223.6.4
Effect of dynamic response on closed-loop control......................................3-223.6.5
Operator interface capability........................................................................3-233.6.6
Process interrupts.......................................................................................3-233.6.7
Redundancy in the I/Os...............................................................................3-233.6.8
V4.02 blocks at the same time as new blocks in a CPU...............................3-233.7
WinCC: Converting the OS .........................................................................3-243.7.1
Customizing the computer name in the WinCC data....................................3-243.7.2
Checking the system parameters for the communication driver...................3-243.7.3
Libraries......................................................................................................3-253.7.4
Converting Global Script.............................................................................3-253.7.5
Base Data...................................................................................................3-253.7.6
Lifebeat Monitoring .....................................................................................3-263.7.7
Alarm Logging.............................................................................................3-263.7.8
Converting images......................................................................................3-273.7.9
Picture Tree Manager .................................................................................3-273.7.10
Time synchronization..................................................................................3-273.7.11
Signal module.............................................................................................3-273.7.12
Chipcard.....................................................................................................3-27
Contents
Migration from PCS7 V4.x to PCS7 V5.0
A5E00064939-01v
3.7.13
User archive conversion from V4.x to V5.0..................................................3-283.7.14
Migration from Client to MultiClient..............................................................3-293.7.15
The ProjectConverter – Tool........................................................................3-324Quick description - Migration steps..........................................................................4-1
4.1
Converting the PLC data...............................................................................4-14.2Converting the OS data.................................................................................4-2
Contents
Migration from PCS7 V4.x to PCS7 V5.0 vi A5E00064939-01
1 Remarks concerning migration
1.1 Extent of migration
When upgrading from PCS 7, version 4.x, to V5.0 you can judge for yourself the
extent to which you will use the new functions and how much time you will devote
to them. You can vary the extent of the migration accordingly. Some likely
situations are listed below:
Migration, situation 1
You have a project, version 4.x, and wish to upgrade just the OS to V5.0 so that
you can use the new OS blocks, but without immediately updating or upgrading the
PLC in your project. When upgrading your system in this way no PLC-OS transfer
is permissible.
You would rather choose a later and more convenient moment at which to update
the PLC data in your project so that you can utilize the many corrections and
improvements.
In that case, see Section 3.7 (except Sections 3.7.14 and 3.7.15).
Migration, situation 2
You have a project, version 4.x, and want to use the new V5.0 ES software (CFC,
SFC, PH, IEW). You prefer to acquire the current functional scope now, so that
operations will not be interrupted for long at the time of migration. The new V5.0
functions will only be used when the system is upgraded later on, at which time it
will also be used to carry out new project planning.
In this instance you will need to make some small adjustments, compile the whole
program, put the CPU in STOP mode and carry out a full download. It will also be
necessary to transfer the PLC-OS connection data. If you have already performed
situation 1, not all the steps of Section 3.7 will be necessary.
For this situation, see Section 1, Migration without using the new functions.
Migration form PCS 7 V4.x to PCS 7 V5.0
A5E00064939-011-1
Remarks concerning migration
Migration, situation 3
You have a project, version 4.x, and want to upgrade your system. You wish not
only to implement the new V5.0 ES and OS software, but also to use the full scope
of the new functions (or possibly just certain options) including the new block
libraries. This upgrade can also include bringing new CPUs into use and updating
the operating system.
For this situation, see Section 1, Migration including the use of the new functions.
You should also note in this connection that when you migrate from Client to
MultiClient certain functions can only be used in a restricted form. For more
information see 3.7.14
Quick description
The quick descriptions for converting the PLC and OS are intended for users who
have already converted projects from V4.x to V5.0 and only need a "checklist" of
some kind for further conversions.
For converting PLC data, see Section 4.1.
For converting the OS data, see Section 4.2.
1.2 Backup before migration
Before migration you should take a backup of all your existing data if you have not
already done so. This means:
•Create a backup copy of the whole project or create an image of the hard disk (produce documentation for the project).
•Save your old V4.02 or customized project libraries (see also Section 3.2.1).
Also refer to "Data integrity and consistency" in PLC-OS Engineering 3.5.
Migration form PCS 7 V4.x to PCS 7 V5.0 1-2A5E00064939-01
Migration form PCS 7 V4.x to PCS 7 V5.0
A5E00064939-012-1
2 Migration without using the new functions
(Situation 2) You have installed the V5.0 software (ES and OS) and wish to
continue using your old project for the time being. Program adaptations need to be
kept to the absolute essentials. You must now set the CPU to STOP :
1. Convert the Plant Hierarchy. For information on this procedure: see
Section 3.3.1.
2. Open a CFC or SFC in your project and write something to the chart
concerned (e.g. change the value for a connection).
The result is that the data in the chart folder is converted to the new format.
3. Copy the new FB300 (SFC_INTP) from library SFCLIB into the block folder for
the project.
The result is that the sequential control system takes on a different runtime
behavior ("non-latching behavior", i.e. consecutive termination and initialization
actions are executed within a single cycle).
From then on an update compilation and online download can no longer be carried out.
If you need information on adapting SFCs, see Section 3.3.11
4. Place the MSG_CSF block (FB44) in a new chart. It is used to generate control
and instrumentation technology messages that are not generated in drivers or
function modules. Please refer to the online Help for further information.
5. Check whether your project includes SFCs that
- contain runtime attributes which differ from the default "scan rate = 1",
"phase offset = 0". You need to install charts of this kind in runtime groups that exhibit these attributes. For information on this procedure: see
Section 3.3.12
-
are not installed in the run sequence. You will need to install charts of this
kind, otherwise the program cannot be compiled.6. Compile the whole program.
7. Download the program to the CPU (full download: CPU at STOP).
8. Bring the CPU up to RUN mode (complete restart).
9. Carry out a PLC-OS data transfer (Options > PLC-OS connection data >
Transfer...).
Migration without using the new functions
10. Converting the OS (see Section 3.7).
This includes starting ProjectConverter (see Section 3.7.15). In this case, the
pictures do not have to be converted (see Section 3.7.8), since this is also
done by ProjectConverter.
If you have already performed situation 1, the following sections are not
necessary:
- 3.7.1 Customizing the computer name in the WinCC data
- 3.7.2 Checking the system parameters for the communication driver
- 3.7.3 Libraries
- 3.7.6 Lifebeat Monitoring
- 3.7.8 Converting images
- 3.7.13 User archive conversion from V4.x to V5.0.
Migration form PCS 7 V4.x to PCS 7 V5.0 2-2A5E00064939-01
3 Complete migration using new functions
(Situation 3) The sections that follow cover all the migration steps for the new
functions complete with the measures for upgrading to V5.0. Not every step is
mandatory, since some of them are optional. You are assumed to have already
carried out the steps described in Situation 2.
3.1 Hardware update
3.1.1 Updating the operating system on the S7-CPU(s) 416-2DP
You need the following application:
A PG 720/740/760 programming device with STEP7 >= V3.1 installed and a CD-
ROM drive or alternatively a PC of the same type with a multipoint interface and
external PROMMER installed. Use it to program a 2 MB S7 Memory Card (6ES7
952-1KL00-0AA0).
•Install the latest firmware (version A2) from the Internet to a directory on your computer. Address: www.ad.siemens.de /-> Support, Training & Services ->
Simatic -> Product Support -> Simatic S7 -> General -> S7-400 -> Downloads -
> Operating system update for the S7-400 CPUs as of 3/98.
• Note:
Not all new functions can be achieved by means of a firmware update.
Replacement of hardware may be inevitable - for example, for the new driver
concept described in Section 3.3.9. After downloading the desired CPU file,
extract it by double-clicking on the file name.
•Erase your S7 Memory Card by selecting the following menu command in SIMATIC Manager: File > S7 Memory Card > Clear.
•Now program your S7 Memory Card. To do this, go to SIMATIC Manager and select:
PLC > Update operating system.
•Select the appropriate firmware update for your CPU by switching to the
directory with the new firmware and selecting file Cpu_hd_.upd.
•Click on "Open" to start programming your Memory Card. Wait until the
standard mouse pointer reappears. When this happens the programming is
complete and your Memory Card is ready for the update of your CPU operating
system.
Caution
The next steps will irretrievably delete all the data in your CPU!
Complete migration using new functions
•Turn the mains switch on your CPU power supply (PS4xx) to OFF and remove the Memory Card from your CPU.
•Insert the Memory Card you have just prepared into the CPU and turn the mains switch back to ON. The operating system is now transferred from the
Memory Card to the internal Flash EPROM. During this process all the display
LEDs on the CPU light up (INTF, EXTF, FRCE, CRST, RUN, STOP). The
download procedure takes about 2 minutes to come to an end. When this
happens, the STOP LED on the CPU flashes slowly => system-generated
memory reset request.
•Turn the mains switch on your CPU power supply to OFF, exchange the Memory Card with the update for the original Memory Card and turn the mains
switch back to ON. The CPU carries out an automatic memory reset after
which it is operational once again.
3.1.2 Updating your IM153-1 and IM153-2 (ET200M)
Before you can upgrade the driver blocks for the ET 200M modules to V5.0, you
need to check their compatibility with the IM 153 modules in your system and if
necessary do an exchange to make sure they are compatible. In order to operate
the PLC driver blocks with ET 200M on-line (S7-300 SM modules),the firmware
release number of the IM 153-1 must be greater than or equal to Z05, or in the
case of the IM 153-2 it must be greater than or equal to Z03. You can find out the
product version of your IM by looking on the front panel, lower right. There you will
find the following information:
X5
67
The cross specifies the current product version. The IM 153 cards will have to be
exchanged in their entirety. Please contact your Siemens sales partner to arrange
this.
Complete migration using new functions
3.1.3 Handling GSE files
With STEP 7 version 5, stricter checks are carried out on GSE files (i.e. device
master files). In the case of GSE files from an earlier project, syntax errors or
unknown errors may be reported. If the following measures do not succeed,
contact the manufacturer of the device and ask for a new GSE file. The following
errors may be displayed:
•Install new *.GSE files
The GSE file (path\file name) contains syntax errors. This makes it
impossible to interpret.
- Create a backup copy of the file and open it with a text editor (such as
Wordpad)
- Check Vendor_Name. A maximum of 32 characters and no special
characters are allowed between the double quote marks.
- Correct the name, save the file and restore it to the system again.
•Insert
In the ’SIMATIC 400(1)’ station, transmission rate ’187.5 kbit/s’ is not
supported by node ’MBK-P’.
- Find out the GSE file name and path via the object properties of the DP
slave
- Create a backup copy of the file and open it with a text editor (such as
Wordpad)
- The decimal separator for the transmission rate must be entered as a
point, not a comma (change ’187,5_supp = 1’ to ’187.5_supp = 1’)’
- Start HWCONFIG and choose menu command Options > Update
Catalog.
Note: If an entry reading ’187,5_supp = 1’ is not present, it means the
transmission rate is not supported in reality and you will need to contact the
manufacturer of the device.
•Path\EXTRP.GSD contains syntax error. This makes it impossible to interpret.
- Open the file with a text editor (such as Wordpad) and check whether there is a diagnostic data length entry for the DP slave. For safety’s sake you
should enter the highest possible value for this:
Max_Diag_Data_Len = 244
- Start HWCONFIG and choose menu command Options > Update
Catalog.
Complete migration using new functions
3.2 PCS 7 libraries
In the case of the PCS 7 libraries, certain changes have been made (some blocks
have been amended, some moved to other libraries and some new ones added).
The "PCS 7 Basis Blocks" library has been omitted and a new PCS 7
Communication Blocks library has been added.
Comprehensive details on the changes in V5.0 compared with V4.x can be found
in the README file for the PCS 7 libraries.
Note: When using the new Technological Blocks, please be aware that with these
blocks message texts 6 to 10 and associated values 8 to 10 are omitted and in the
case of the instance data blocks are lost when migration takes place.
3.2.1 Backup when reusing V
4.02 PCS7 libraries
At the time of installing V5.0 PCS 7 libraries, the previous state is automatically
deleted during setup in each case.
If you want to continue having the PLC blocks from the previous version available
for a limited period, go to Windows Explorer and copy the directories:
...Siemens\Step7\S7libs\PCS7 Technological Blocks or \PCS7 Basis Blocks or
\PCS7 Fielddevice Blocks or \PCS7 Driver Blocks to a directory other than the
Siemens directory and rename the copied directories, e.g. by adding V402. Then
open the libraries in SIMATIC Manager and enter the new library names in the
Object Properties (max. 24 characters).
So that you still have access to the online help for the previous states, copy the
following:
...Siemens\Step7\S7hlp\S7jtec_a.hlp, S7jtec_t, S7jtec_b.hlp, S7jtec_t,
S7jtec_c.hlp, S7jtec_t
to ...Directory\PCS7 Technological Blocks V402
...Siemens\Step7\S7hlp\S7jbab_a.hlp, S7jbab_t, S7jbab_b.hlp, S7jbab_t,
S7jbab_c.hlp, S7jbab_t
to ...Directory\PCS7 Basis Blocks V402
...Siemens\Step7\S7hlp\S7jfdb_a.hlp, S7jfdb_t, S7jfdb_b.hlp, S7jfdb_t,
S7jfdb_c.hlp, S7jfdb_t
to ...Directory\PCS7 Fielddevice Blocks V402
...Siemens\Step7\S7hlp\S7jdrv_a.hlp, S7jdrv_t, S7jdrv_b.hlp, S7jdrv_t,
S7jdrv_c.hlp, S7jdrv_t
to ...Directory\PCS7 Driver Blocks V402
Complete migration using new functions 3.3 Converting the PLC
Note:
Before migration it is important to check whether there are enough free resources
in the PLC for the migration to take place. This concerns the memory for the code
and the data including number locations, local data and run time.
3.3.1 SIMATIC Manager: Converting the Plant Hierarchy
This conversion requires no project planning measures.
For information on this procedure:
•Open SIMATIC Manager
•Open the project
•When Component View is displayed, use View > Plant View to go to the Plant View dialog. The following message is displayed:
•Click "Yes" to confirm conversion of the Plant Hierarchy.
3.3.2 HW Config: Adjust hardware
•Customize the hardware configuration for the project, save/compile it and download it to the SIMATIC station.
Complete migration using new functions
3.3.3 SIMATIC Manager: Integrate and adapt the blocks from the new
libraries
•Create a separate library specifically for the project.
•From the new libraries, copy all the blocks that are being used in your project into this library.
•The symbolic name of a block must not exceed 16 characters. If the name is longer than 16 characters, proceed as follows:
- Go to Component View, click on "S7 program" and double-click on
"Symbols" in the right hand window.
- Symbol editor: Shorten the names to max. 16 characters and then save the symbol table.
•Perform the necessary project-specific changes in the separate library you created specifically for the project:
- Check the values for the attributes in the FB parameters for changes
between your V4.x project and the new V5.0 library blocks. Double-click on
the FB in the block folder (offline) to display the declaration table for the
FB. If you click the little symbol in the same row as the parameter
concerned, the "Properties - Parameters" dialog box is displayed:
Example:
Complete migration using new functions
- Change your values as necessary if you wish to keep the parameter
properties.
- Caution: By default, many attributes are set to "false" or are not present.
In this way, you can delete connections from the CFCs, for example, if the
"S7_link" attribute then has "false" as its value. You must therefore check
the block attributes carefully.
- The value of the attributes - for example, "S7_shortcut" - must not exceed
16 characters.
- Due to the new message attribute, "S7_alarm_ui" (in the message concept for EDC), message text for operator input messages is no longer
displayed. In other words, you can no longer generate you own operator
input messages with the message block, as with all the other message-
compatible blocks in the PCS7 libraries.
It became necessary to use the "S7_alarm_ui" message attribute for
message blocks owing to the message concept for EDC.
•From your own library, copy all the blocks that will be used in the project into the block folder for the program.
•If necessary, check by the last modification date (in the block folder in View: Details) whether all the blocks to be updated have been copied.
•Now insert a CFC ("Dummy") in the chart folder for your project.
3.3.4 CFC: Integrating and adapting blocks from new libraries
•Double-click on the chart to open it.
A message is displayed (if conversion has not already been carried out, for
instance at the time of a CPU change in the HW configuration), to the effect
that the data was created with CFC version 4.x and that editing is only possible
after conversion.
•Click "Yes" to confirm and the charts will be converted.
•In the chart, select menu command Options > Block Types... and import all the blocks into the chart folder (in the left hand window "Block folder offline",
select the blocks and click the "Å" button).
•Rename the CFC called "Dummy" to "MSG_CSF" and place in it the block called MSG_CSF (FB44).
It is used to generate control and instrumentation technology messages that
are not generated in drivers or function modules. Please refer to the online
Help for further information.
Complete migration using new functions
Note:
In the case of large projects (>30K PowerTags) use the WinNT Task Manager in
the "Processes" register during block-type importing for process S7JCFCAX.EXE
to note the number of handles you are using.
If the number rises above 10000, cancel type importing once the current block has
been processed and exit the CFC. Restart the CFC and continue type importing
from the next block. Otherwise in some circumstances there could be an
exception error on accessing the project database.
If the new versions of the blocks have different properties than the current version
in the CFC, the following dialog box is displayed:。