Configuration Manual

Migration V1.9/V2 ->V7

A&D CC Cement
 Configuration Manual_V7 Migration V2 -> V7

Migration V1.9/V2 -> V7

Contents
Migration V1.9/V2 -> V7 1
General Information ................................................................................................. 2
Overview ..................................................................................................................3
Installation Notes for PCS 7.....................................................................................4
PG/PC Interface..........................................................................................4
Installing the CEMAT Software ................................................................................ 5
Settings for alarm logging and annunciation system like Cemat V6.0 ....... 5
Installation of Cemat S5 Migration Files ..................................................... 5
Extra Settings in the WinCC Project ........................................................................ 6
Setting Parameters for Tag Management ..................................................6
Process Picture Symbols ............................................................................7
Picture Tree ................................................................................................7
Generating and loading of the Server Data ................................................ 7
Synchronizing the Time of Day (only on the primary server) ..................... 8
Import from CEMAT V1.9 / V2.0 ............................................................................10
Export the alarm formats and text formats from COROS LSC ................. 10
Export of the message format pointer and scaling factors F, K, DEZ from
the OS PLC. ..............................................................................................11
USER variables COROS LSC ..................................................................11
PID controller data blocks.........................................................................11
Regional settings ......................................................................................11
Import to Excel ..........................................................................................12
PLC names ...............................................................................................13
Object list (TAG list) ..................................................................................13
Adjustments on the TAG list .....................................................................13
Creating Object Structures and PLCs in WinCC ...................................... 14
PMC Message Numbers...........................................................................15
WinCC Text Library...................................................................................17
WinCC Process Tags ...............................................................................19
Generating Messages...............................................................................21
Group messages (Area) ...........................................................................23
Adapting the PLCs ....................................................................................24
Project Additional Objects......................................................................................26
Order for project additional objects........................................................... 26
Improvement of the performance of the status call ...............................................28
Problem.....................................................................................................28
Solution .....................................................................................................28

Copyright © Siemens AG. All rights reserved. 3-1

Release : 03.03.08
N:\Cemat\DOKU\V70\English\Migration\CEMAT_V2_V70_009.DOC
Migration V2 -> V7 Configuration Manual_V7

General Information
This chapter describes the creation of a WinCC project on an engineering station (ES) and
taking over the data from a V1.9/V2 project.
To be able to take over the data, the following requirements must be met:
V1.9/V2.0:
• You must have a COROS LSC machine with MS DOS and the actual alarm formats and
the text formats. On older COROS LSC machines exists only the operating system iRMX.
If you have only a machine with iRMX, you have to save your alarm formats and text
formats on a floppy disk and copy the alarm formats and text formats to a machine with
iRMX and MS-DOS.
• The PLC software of the OS PLCs and the SMR PLCs.
• The latest version of the PLC standard blocks of Cemat V2.0 is available and the PLCs
are updated to the latest version of V2.0. A PLC with V1.9 must be updated to V2.0
(Cemat object function blocks).
• The EXCEL file MIG_V19_V7.XLS / MIG_V2_V7.XLS for generating the import files for
WinCC.
• The import tools "VAR_EXIM.EXE" (PLCs, structures and tags) and
"Address List Import PMC.exe" (message numbers and raw data tags for the message
system). VAR_EXIM.EXE is on the PCS 7 DVD in Smarttools.
"Address List Import PMC.exe" will be delivered with the Communication channel
"S5-PMC Industrial Ethernet". After Installation of the channel, the "Address List Import
PMC.exe" will be found in C:\SIMATIC\WinCC\Bin.
• You have the SIMATIC S5 PMC Ethernet WinCC channel driver.
• License for SIMATIC S5 PMC Ethernet exists.
• Structure import list "MIG_V2_V7_dex.csv" for creating the structure tags exists.
• CEMAT V7 CD and CEMAT OSRT licenses (per server) and CEMAT MC licenses (per
multi client)
Limitations:
• Area specific rights are not possible. I. E. a user is able to operate all areas. Restrictions
are only possible by functions, e. g. controller parameter.
• The help button is not working in the S5 migration. There are no PDF files for S5 versions
available.

3-2 Copyright © Siemens AG. All Rights Reserved.

 Configuration Manual_V7 Migration V2 -> V7

Overview
COROS LSC EXCEL TAG Export Import WinCC
with VAR_EXIM.EXE
Text formats
xytext_x.pd/.pdi MELDUNGEN Import to Alarm
Alarm formats Logging
xyform_x.pd/.pdi i ti
TAG TEXTE Add to text
library
MFORMATE.TXT hi fü
= _VEX (variables) Import with
TEXTFORM.TXT S5_VAR_WINCC split in CTyp > 1000 VAR_EXIM.EXE to
and CTyp < 1000 iTag Management
AG_WINCC = _CEX (connections) and Structure Tag
MVERVE.S5A

FKD_S5.S5A
MIG_V18_V5_dex.csv = _DEX (Structures)
Scaling factors MIG_V19_V5_dex.csv
MIG_V2_V5_dex.csv
Alarm format links

S5 OS-AG

Copyright © Siemens AG. All Rights Reserved. 3-3

Migration V2 -> V7 Configuration Manual_V7

Installation Notes for PCS 7

Install the stations (engineering station, server, single user stations and multiclients)
according to the CEMAT V7 Manual.
A underscore „_“ is not allowed in computer names and WinCC project names. The computer
names and project names are used for the server packages. The separator in the package
name ist he underscore. There is only one underscore allowed in the name of the server
package!
In addition to this, install the smart tool "VarEXIM". Check the PCS 7 installation manual for
information on installing this tool. In PCS 7 V7, the smart tools were on the DVD in
CD:\20_WinCC__V6.2+SP2\WinCC\setup\Products\SC_SMARTTOOLS\Setup.exe.

PG/PC Interface
Open the Control Panel and select "Set PG/PC Interface" and then set the access point
"CP_H1_1" to the communications adapter:
for example for the CP 1613 to CP1613(ISO) or with Softnet to "ISO Ind. Ethernet"
.

3-4 Copyright © Siemens AG. All Rights Reserved.

 Configuration Manual_V7 Migration V2 -> V7

Installing the CEMAT Software

Run the Setup from the CEMAT V7 CD. Create a WinCC project according to the CEMAT V7
Manual.

Settings for alarm logging and annunciation system like

Cemat V6.0
If you use the S5 Migration , you have to use the alrm line and area selection of Cemat V6.0.
For the necessary settings in WinCC refer the manual
D:\CEMAT_CS\Docu\Reference\ADD ONs\ 04_Alarmline_MessageSelection.pdf.
The necessary install files you will find on the Cemat CD in the directory
CD:\Alarmline_MessageSelection_V60.

Installation of Cemat S5 Migration Files

The necessary files for the migration are delivered separately as ZIP file per Email. Copy the
supplied files from CEMAT_CS (BIN, CONFIG) to the corresponding folders of
D:\CEMAT_CS. If there are OCX files in the delivered BIN directory, please register this OCX
files with the file "S5_RegCtrls.bat". During running the BAT file please close all WinCC
applications. We recommend to run the BAT after a reboot of the PC.
Copy the supplied files from WinCC (GraCS, Library, PAS) to the corresponding folders of the
WinCC project. For Client projects copy only the @ files from GraCS, the bitmap files BMP
and EMF, the files from Library and PAS. Regenerate the header in Scripts for all WinCC
projects.
Copy the supplied file Windatit.axv from Windows\System32\ to C:\WINNT\System32\. If your
operating system is not installed in C:\WINNT, then copy the file Windatit.axv to System32 of
your Windows installation.

Copyright © Siemens AG. All Rights Reserved. 3-5

Migration V2 -> V7 Configuration Manual_V7

Extra Settings in the WinCC Project

Setting Parameters for Tag Management

As of WinCC Version V5, the "SIMATIC S5 PMC Ethernet" channel is no longer included.
This channel must be ordered separately. Install the channel (generally this means copying
the supplied files to the BIN folder of WinCC). The channel can then be added.
- Select Tag Management
Right-click -> Add New Driver
Select SIMATIC S5 PMC Ethernet.CHN.

The "SIMATIC S5 PMC ETHERNET" channel must then be visible. For test purposes, the
channel can also be selected without a license. For system operation, however, a license
must be installed. Otherwise, WinCC will constantly be interrupted by a license reminder.

3-6 Copyright © Siemens AG. All Rights Reserved.

 Configuration Manual_V7 Migration V2 -> V7

Process Picture Symbols

For objects use only the corresponding UDOs from the template picture
"PP_CEMAT_DEFAULT_V2 for V7.PDL".
The connection to the TAGs do with the “Dynamic wizard” --> “Standard dynamics” -->
“Link a prototype to a structure or rename an existing link”.
The help button is not working in the S5 migration. There are no PDF files for S5 versions
available.

Picture Tree
The picture tree could else created automatically, like under PCS7 V7 or the picture tree must
be created manually in the picture tree editor. Create for the automatically generating a
technological hierarchy which contains only process mimics. The block icons in the process
mimics could not be generated. Create these icons manually with the dynamic wizard.

Generating and loading of the Server Data

If in the Tag Management, in the Text Library or in the Alarm Logging a change is imported or
a manual change is done, then the project looses the ability for a download (changes only). In
this case you have to create a new server package. The new server project has to be
downloaded completely, i. E. the servers has to be stopped, one after the other one. On the
clients you have to load the new server package.
This is unfortunately not the same comfort like under a pure PCS 7V 6.0 / V6.1 / V7.0
solution.

Copyright © Siemens AG. All Rights Reserved. 3-7

Migration V2 -> V7 Configuration Manual_V7

Synchronizing the Time of Day (only on the primary server)

For the time-of-day synchronization, the following entry must be made in the global action
"TimeSync_to_AS" for each PLC:

3-8 Copyright © Siemens AG. All Rights Reserved.

 Configuration Manual_V7 Migration V2 -> V7

6 lines must be added per PLC. The following example implements the time synchronization
for PLC1 and PLC4.

To ensure that this action is activated only on the time master server, the computer name of
the time master must be entered in the action. In the following example, "E5118273D" must
be entered as the computer name.

As time basis must be set UTC (GMT) in the file ......WinCC\BIN\S5PMCNRM.INI

SPS_Time = 2
;2 = PLC always returns GMT (UTC) // SPS liefert immer GMT (UTC)

Copyright © Siemens AG. All Rights Reserved. 3-9

Migration V2 -> V7 Configuration Manual_V7

Import from CEMAT V1.9 / V2.0

Please make a backup of your OS project before you start a import. If an import fails
and destroy your project you can easely try it again!!!

Export the alarm formats and text formats from COROS LSC
You must have a COROS LSC machine with MS DOS and the actual alarm formats and the
text formats. On older COROS LSC machines exists only the operating system iRMX. If you
have only a machine with iRMX, you have to save your alarm formats and text formats on a
floppy disk and copy the alarm formats and text formats to a machine with iRMX and MS-
DOS.

Menu for Backup and Restore:

The menu texts are not the exact one. For this manual weh ad only a German version
available. Please imagine the corect expression in the menu!
„F1“ Project
„F5“ Organisation
„F2“ Backup
„F7“ Select message formats or „Fx“ message texts
„F5“ Select foppy disk
„F7“ Select Export = Backup or „F8“ Import = Restore
„F6“ Select Submit
Start the transfer with „F10“
If you have the data on a machine with a MS DOS partition, you can copy the data with the
program RMXDISK.EXE to MS DOS.
Procedure:
• Create a directory EXPORT.
• Create a text file EXPORT.DAT in C:\EXPORT with the following content:
ad c: as :w:
af :w:anlage/sof7 as :x:
copy :x:xyform.x.pd over c:\export\xyform_x.pd
copy :x:xyform.x.pdi over c:\export\xyform_x.pdi
copy :x:xytext.x.pd over c:\export\xytext_x.pd
copy :x:xytext.x.pdi over c:\export\xytext_x.pdi
• Create a batch file EXPORT.BAT with the following content:
cd c:\export
rmxdisk< c:\export\export.dat
• Start the batch file EXPORT.BAT. After a successful execution you will find in the directory
C:\EXPORT the following files:
xyform_x.pd
xyform_x.pdi
xytext_x.pd
xytext_x.pdi
If the files in the MS DOS partition already exists, please rename the files to names listed
before.
Convert the exported files with the program PDCONV_X into the dBASE format.
Commands:
pdconv_x –t8 MFORMATE
pdconv_x –t7 TEXTFORM
After this procedure the two files MFORMATE.DBF and TEXTFORM.DBF
should exist.

3 - 10 Copyright © Siemens AG. All Rights Reserved.

 Configuration Manual_V7 Migration V2 -> V7

Export of the message format pointer and scaling factors F, K,

DEZ from the OS PLC.
V1.9: Copy the data blocks DB91 to DB106 into the file MVERWEST.S5D.
V2.0: Copy the data block DB91 into the file MVERWEST.S5D.
Convert the S5D file MVERWEST.S5 with the program S5ASM.EXE into a ASCII file.
Command: „S5ASM.EXE –d MVERWEST.S5D“.
Copy the data blocks DB188 to DB203 into the file FKD_S5ST.S5D. In this data blocks
(DB188 to DB203) there are pointer to data blocks with scaling factors (DW130 to DW140).
Normally the data blocks with scaling factors are
V1.9: DX151 to DX 180 (please check DW130 to DW140 in DB188 to DB203)
V2.0: DX151 to DX 180 (please check DW130 to DW140 in DB188 to DB203)
Copy this data blocks also into the file FKD_S5ST.S5D.
Convert the S5D file FKD_S5ST.S5D with the program S5ASM.EXE into a ASCII file.
Command: „S5ASM.EXE –d FKD_S5ST.S5D“.

Result two ASCII files: MVERWE.S5A and FKD_S5.S5A

USER variables COROS LSC

Fill the table ANW_BEREICHE to get the COROS LSC user variables type DBIT, SBYTE,
DBYTE, SINT, DINT, SFLO, DFLO. If you have old PACOS list, you can take the data to fill
the tables DBIT, SBYTE, DBYTE, SINT, DINT, SFLOAT, DFLOAT. In this case you will get
the variable names from the PACOS list additionally to the variable type. Please check for
double TAGs.

PID controller data blocks

Enter the cross reference „PID controller ÅÆ data block“ into the table ODAT. For the
controllers 1 to 16 this are normally the data blocks 240 to 255. Please check this reference.

Regional settings
If the are problems during import, lease change during the complete import your reginal
settings in control panel:
Control panel -> Regional and language options -> Customize -> Numbers.
Decimal symbol = "." = dot
Digit grouping symbol = "," = Comma
List separator = ";" = Semikolon
Change back to your original settings after a succesful import.

Copyright © Siemens AG. All Rights Reserved. 3 - 11

Migration V2 -> V7 Configuration Manual_V7

Import to Excel
Copy the Excel file MIG_V19_V7.XLS / MIG_V2_V7.XLS and the files MFORMATE.DBF,
TEXTFORM.DBF, MVERWE.S5A and FKD_S5.S5A into the same directory and start the
macro „Import_LSC“.

Wait until "Ready" appears again in the status bar of Excel.

Could run up to 20 minutes!
Check: The tables „MFORMATE“, „TEXTFORM“, „MVERWE“ and „FKD_S5“ should be filled
with the corresponding text files.

3 - 12 Copyright © Siemens AG. All Rights Reserved.

 Configuration Manual_V7 Migration V2 -> V7

PLC names
Please enter in the table „AG_NAMEN“ the PLC names.

Object list (TAG list)

Start the Excel macro „TAG_V2“. In the status bar of Excel there will each found TAG and
parameter be listed. Afterwards the macro tries fo find the event texts for each TAG. This
could run maybe up to 20 minutes. Wait until "Ready" appears again in the status bar of
Excel.
Check: The table „TAG“ should be filled with the data of the existing TAGs. The tables „AG“
and „AG_WINCC“ should be filled with the data of the existing PLCs.

Adjustments on the TAG list

Please check the tables „TAG“, „AG“ and „AG_WINCC“.
Change , delete or add wrong, incomplete, missing Tags!!!!!!!!!!!!
Change , delete or add wrong, incomplete, missing PLC names!!!!!!!!!!!!
Please consider the design of the tables and do not change the design of the
tables!!!!!!
Excample: If a UM is added, please fill out the fields TAG, AG-Name (=PLC name),
AG-Nr. (= PLC no.), Typ = 6 (type = 6), Objekt.-Nr. (object number), ASCII-TYP = UM,
SKA (= SCB), SKE (=SKE), Dimension, Anlage (plant)!
After the editing of the table TAG is finished, please check the consistency with the
macro „Konsistenz“. The macro checks, are there double tags or double objects (PLC,
type and number are the same).

Copyright © Siemens AG. All Rights Reserved. 3 - 13

Migration V2 -> V7 Configuration Manual_V7

Creating Object Structures and PLCs in WinCC

Save the Excel file MIG_V19_V7.xls / MIG_V2_V7.xls.
Save the "AG_WINCC" table as text file AG_WINCC.CSV.
Rename the supplied file MIG_V2_V7_dex.csv (structure list) to XXX_dex.csv: XXX can be
any name, for example the project name SOLNHOFEN. Rename the table saved as text file
AG_WINCC.CSV to XXX_cex.csv (connection list).
Copy these two files (SOLNHOFEN _cex.csv, SOLNHOFEN _dex.csv) to the WinCC station.
Open the WinCC project. Start the supplied file VAR_EXIM.EXE.
In VAR_EXIM, select the folder with the two CSV files and select one of the two files. Select
"Import overwrite" and click "Execute". The structures and the PLCs are now created.

3 - 14 Copyright © Siemens AG. All Rights Reserved.

 Configuration Manual_V7 Migration V2 -> V7

Check: Have the PLCs been created?

Check: Have the CEMAT structures been created?

Finally, select "Export" and click "Execute" again. Rename the resulting XXX_dex.csv to
strukturexp.csv and copy it to the folder with the Excel file MIG_V3_V5.XLS and then run the
"Struktur_ID" macro. When you create the structures in WinCC, each structure is given an ID.
This ID is entered into the model structures with this macro.

PMC Message Numbers

Start the "M_MRN" macro. The status bar lists each TAG found and the corresponding PLC
one after the other. Wait until "Ready" appears again in the status bar of Excel.
Check: The "M-NR" table should be filled with the PMC message no. 1 for each PLC.
Save the file MIG_V19_V7.xls / MIG_V2_V7.xls !!!
The table "M-NR" is saved by the macro as the text file MNR.TXT.
Copy this text file MNR.TXT to the WinCC project and open it with the
"Address List Import PMC.exe" tool. The tool is located in C:\SIEMENS\WinCC\Bin after
installing the PMC channel.

Copyright © Siemens AG. All Rights Reserved. 3 - 15

Migration V2 -> V7 Configuration Manual_V7

After checking the list, a box appears that queries whether the WinCC project is open and
whether the PMC channel driver is installed. If the answer is yes to both queries, confirm with
"OK".

The message "Closing System" and the reference to the log file means that the message
number import is completed.
Check: One raw data tag should have been created per PLC and the messages (without
comment and message type) should exist in Alarm Logging.
If you cannot see the messages in Alarm Logging, close the WinCC project and open it again.

3 - 16 Copyright © Siemens AG. All Rights Reserved.

 Configuration Manual_V7 Migration V2 -> V7

WinCC Text Library

Attention: Before you continue with this step, you should save in any case your PCS7 /
WinCC project. During the import of wrong text (forbidden characters, empty text strings, etc.)
your WinCC project could be destroyed!!!!!!!!!
Open the text library in WinCC:

Export the text library from WinCC:

Find out the highest text number in the text library, for example 1807. Then start the "Texte"
macro. The macro asks for the start number, which is the first free number for CEMAT. In our
example, you would enter the number 1808. The status bar indicates the TAGs and message
types for which the texts will be stored. Wait until "Ready" appears again in the status bar of
Excel.

Check: The "TEXTE" table should be filled with the message types, TAGs, and comments.
Save the file MIG_V19_V7.xls / MIG_V2_V7.xls !!!
The macro "Texte" saves the table "TEXTE" as text file TEXTLIB.CSV.
Add the text file TEXTLIB.CSV to the saved WinCC text library (append it to the end).
Then import the text library into WinCC again. During import, a warning appears that you can
acknowledge with "CONTINUE". If the text library was correctly exported earlier and is now
imported again, all text references are retained.
If there are problems during text library import, e. g. there is no text number betwwen 1 and
10000, then replace all empty text entries by according texts from the other languages.
E. g. as English text there is „User Name“ and the German and French entry is empty.Please
copy „User Name“ as German and French entry or enter the translation. Try to import again.

Copyright © Siemens AG. All Rights Reserved. 3 - 17

Migration V2 -> V7 Configuration Manual_V7

Check: The message types, TAGs, comments etc. should now be in the text library.
The text numbers must be complete. No gaps!!!!

3 - 18 Copyright © Siemens AG. All Rights Reserved.

 Configuration Manual_V7 Migration V2 -> V7

WinCC Process Tags

Start the "VAR_LISTE" macro. The status bar lists each TAG found and the corresponding
PLC one after the other. Wait until "Ready" appears again in the status bar of Excel.
Check: The "S5_VAR_WINCC" table should be filled with the structure and single tags of the
existing tags.
The macro "VAR_LISTE" saves the table “S5_VAR_WINCC" into 2 text files: VEXstruc.txt
and VEXvariables.txt.
If the "S5_VAR_WINCC" table overflowed, in other words, more than 65536 rows, further
tables will be created (S5_VAR_WINCC2, S5_VAR_WINCC3, S5_VAR_WINCC4, etc.). This
tables are also saved by the macro into text files VEXstruc2.txt, VEXstruc3.txt, etc. and
VEXvariables2.txt, VEXvariables3.txt, etc. With a suitable editor (Notepad, Word) put all these
text files together as the files VEXstruc.txt and VEXvariables.txt.
VAR_EXIM.EXE of version V6 can no longer read in the tag list at one time. XXX_vex.csv
must therefore be divided up into structure tags and single tags. To do this, the XXX_vex.csv
file must be sorted according to CType. Therefore the macro saves the rows with CType
higher than 1000 into VEXstruc.txt and the rows with CType less than 1000 are saved by the
macro into VEXvariables.txt. The import into WinCC must then be performed twice. Firstly
with the structure tag list and then again with the single tag list.
Creating structure tags:
Rename the structure tag file VEXstruc.txt, for example as PROJECT_vex.csv (to match the
structure list PROJECT_dex.csv and connection list PROJECT_cex.csv) and copy it to the
WinCC station.
Open the WinCC project. Start the supplied file VAR_EXIM.EXE.
In VAR_EXIM.EXE, select the folder with the 3 CSV files (_cex, _dex, _vex) and select one of
the three files. Select "Import" and click "Execute". The structure tags and single tags are
now created. The single tags do not yet have a start value and/or are not scaled.
Create and modify the single tags (start value, scaling etc.):
Rename the single tags file VEXvariables.txt , for example to PROJECT_vex.csv (to match
the structure list PROJECT_dex.csv and connection list PROJECT_cex.csv) and copy it to
the WinCC station.
Open the WinCC project. Start the supplied file VAR_EXIM.EXE.
In VAR_EXIM.EXE, select the folder with the 3 CSV files (_cex, _dex, _vex) and select one of
the three files. Select "Import overwrite" and click "Execute". The process variables are now
created.
This can take several hours!!!!!!!!!!!!!!

Check: Have the process variables been created? Check the log file of VAR_EXIM.EXE.
There should be no error messages in the LOG file DIAG.TXT between point 4.2 and 5.0. The
messages after 2.0 (connections still exist) and 3.0 (structure definitions already exist) are
normal.
If you have more than one text pair, e.g. VEXstruc2.txt and VEXvariables2.txt, and do not
combine them, create the structure variables and single variables like before for each text file
pair.

Copyright © Siemens AG. All Rights Reserved. 3 - 19

Migration V2 -> V7 Configuration Manual_V7

User variables
With the tool VAREXIM.EXE you could create additional user defined variables which could
be connected to user DB or user flags.
Do not connect these user variables to periphery (e. g. Q 5.3). If a variable is connected to a
switched of periphery, the OS AS communication is temporary interrupted. After the
communication link is again established, the AS sends all still existing alarms to the OS. The
OS displays these alarms with slashed date and time. This communication interrupt happens
cyclic until the process mimic with the not existing periphery variable is displayed. In this
status, the process mimic could nearly not operated. Therefore use only DB, DX and flags as
data source for variables. Please route periphery with STL into DB’s or DX and link your
variables to these DB’s or DX.

3 - 20 Copyright © Siemens AG. All Rights Reserved.

 Configuration Manual_V7 Migration V2 -> V7

Generating Messages
Export messages from WinCC so that the WinCC message numbers per PLC for message
generation are known:
If in the row „PMC message no.“ / PMC Meldenummer“ (originally Charge Nummer / Batch
number) there is no text like „User msg. nnn“ or „Zustand nnn“, then set the language in View
Æ Language to „Deutsch“. Do the next export step only, if you see a text like „User msg. nnn“
or „Zustand nnn“ in the row „PMC message no.“ / PMC Meldenummer“.
Open Alarm Logging, find out the lowest and highest user message number

for example

for example

Select Messages -> Export Single Messages... .

Select the file: meldexp.txt

Copyright © Siemens AG. All Rights Reserved. 3 - 21

Migration V2 -> V7 Configuration Manual_V7

Click on "Selection" and enter the lowest and highest user message number:

Click on the "Export" button to start the message export.

Copy the generated file meldexp.txt to the folder with the Excel file MIG_V3_V5.XLS and run
the "Meldungen" macro. The status bar lists each TAG found and the corresponding PLC one
after the other. Wait until "Ready" appears again in the status bar of Excel.
Check: The "Meldungen" table should be filled with the messages of the existing TAGs.
The macro “MELDUNGEN” saves the table "MELDUNGEN" as text file MELDUNGEN.TXT.
Following this, import the messages to WinCC. Set the language in View Æ Language to your
favorite language e. g. „English“.
For the import, select "Overwrite Messages and Import New Messages" and select the file
MELDUNGEN.TXT.

3 - 22 Copyright © Siemens AG. All Rights Reserved.

 Configuration Manual_V7 Migration V2 -> V7

Save the messages, close Alarm Logging and close and then reopen the WinCC project.
Check: In Alarm Logging, the messages should now have TAGs (HID) and comments.

Group messages (Area)

For the alarm selection to “Area” the “Area” must be entered as a user defined group
message in alarm logging.

Copyright © Siemens AG. All Rights Reserved. 3 - 23

Migration V2 -> V7 Configuration Manual_V7

Adapting the PLCs

Restrictions:
The route module can not display all modes from the status words 1 and 2.
Reason: The dynamic and static faults was difficult comprehensible for the user (WSA, WAS,
OAS etc.).
Order of configuration:
1. Before you update the PLC with the migration blocks, you have to update the PLC to the
latest version of V2.0. I. e. the standard function blocks of the files A11020ST.S5D,
B11020ST.S5D, C11020ST.S5D, F11020ST.S5D, H11020ST.S5D, KF1020ST.S5D,
RS1020ST.S5D, S11020ST.S5D and / or S21020ST have to be copied into the PLC
program (depends on your configuration). A V1.9 must be updated to V2.0. Please check
the function change because of an update from V1.9 to V2.0. Contact the Cemat
developing department if necessary.
2. Change settings in DB31!!!

V1.9 / V2.0:
DW30 = 0 Number of OS PLCs
DW252,253=0 max. VDU and processor no.
3. V1.9 / V2.0
Settings in the send buffers DB170-DB185
DW11-DW16 Release bits for communication – set all to 0 exept 11.3 =
dynamic user data blocks and 12.3 = sporadic user data blocks
Check: Do you need all communication data blocks? (compare DB31,DW94), otherwise
delete the data blocks; memory space!
4. Delete the following blocks:

V1.9 /V2.0:
FB44-FB53 VISU_FBs
DB226 (message texts)
FB21.
5. V1.9 / V2.0:
Remove the interconnection to COROS-BIT-DB for UM moduls or all bits in DB28
(service bits COROS LSC to UM) must be 0.
For your information: 1 signal to interface F 218.5 UWFR (service) has a higher priority
than commands.

Extend all controller data blocks. DW 185 must exist!!!!

Which controllers exist, you can check in DB 234 ODAT = adress last controller.
6. Transfer UPNO20ST.S5D (V1.9 / V2.0) and overwrite all existing blocks.
If weighers exist, then transfer all blocks from file Waaglfst.s5d and overwrite all existing
blocks.
7. Check the standard communication blocks. If you use a CPU948, you have to use the
blocks for CPU948.
8. Check in DB KONF (check PMC manual) the settings fort he interface number of the
Ethernet controller (CP143 or CP1430). The setting must be identical with the jumbers on
the CP143 or with the settings im COM1430 for CP1430.

3 - 24 Copyright © Siemens AG. All Rights Reserved.

 Configuration Manual_V7 Migration V2 -> V7

9. ATTENTION:
You need 3 pairs (SEND/RECEIVE) of communication jobs on CP143/CP1430. 1 pair for
Server1, Server2 and ES. For each communikation you need around 4KW memory space
in the PLC. If there is a memory problem, you can remove the settings and data blocks for
the communication to the ES (check DB KONF).
10.Project work on the CP:
Add 3 pairs of communication jobs (simple links, no full duplex connections).
Server1:
SEND ANR=65 TSAP AG_WINCC
RECEIVE ANR=66 TSAP WINCC_AG
Server2:
SEND ANR=67 TSAP AG_WINCC
RECEIVE ANR=68 TSAP WINCC_AG
Engineering:
SEND ANR=69 TSAP AG_WINCC
RECEIVE ANR=70 TSAP WINCC_AG

Overview:

S5 CP143 WinCC
CP1430 Tag Management
UPNO20.S5D PMC channel
MLFB 2XV9450-1WC43-0JX0

entire S5 program e. g. PLC1:

DB PMC configuration ANR 66 RECEIVE RECEIVE

= DB 42 (V2.0) Own TSAP = WINCC_AG Own TSAP = WINCC_AG
or DB151 (V1.8) Remote TSAP = WINCC_AG Remote TSAP = WINCC_AG
DW52 = ANR RECEIVE 1.OS = 66
DW53 = ANR SEND 1.OS = 65 ANR 65 SEND SEND
DW72 = ANR RECEIVE 2.OS = 68 Own TSAP = AG_WINCC Own TSAP = AG_WINCC
DW73 = ANR SEND 2.OS = 67 Remote TSAP = AG_WINCC Remote TSAP = AG_WINCC
DW92 = ANR RECEIVE 3.OS = 70
DW93 = ANR SEND 3.OS = 69
DW112 = ANR RECEIVE 4.OS = 72
DW113 = ANR SEND 4.OS = 71

Copyright © Siemens AG. All Rights Reserved. 3 - 25

Migration V2 -> V7 Configuration Manual_V7

Project Additional Objects

Order for project additional objects

Copy the previous Excel file MIG???.XLS and enter only the objects you wish to add in the
"TAG" table. It is important that only a copy of the previous Excel table is used and not a new
migration table. In a new table, the structure and the message import information would be
missing.
Delete in the copied file the following tables completely: S5L, MELD, strukturexp, meldexp.
Delete in the following tables all cells (select all and delete cells): TEXTE, S5_VAR_WINCC,
MELDUNGEN, M-NR, USER.
Delete in table AREA row 25 and all rows > 25.
The Excel file for the new objects will be smaller and more usefull because of the deletings
before.
Export the WinCC text library again. Obtain the next free text ID.
The run the "Objekts" macro. When you run the macro, enter the next free text ID from the
text library.
The macro fills three tables: TEXTE, S5_VAR_WINCC, MELDUNGEN. This 3 tables are
saved by the macro into 4 text files (TEXTLIB.CSV, VEXstruc.txt, VEXvariables.txt,
MELDUNGEN.TXT).
The file TEXTLIB.CSV must be appended to the text library.
The files VEXstruc.txt and VEXvariables.txt must be imported with the VAR_EXIM.EXE tool.
Refer to the section with VAR_EXIM.EXE. The VEX files must be renamed to an
XXX_vex.csv. This must match the existing structure list XXX_dex.csv and the existing
connection list XXX_cex.csv. If the structure list XXX_dex.csv and the connection list
XXX_cex.csv not exists anymore, then run an “Export” with VAR_EXIM.EXE and use for the
import of the new objects the exported structure list XXX_dex.csv and the connection list
XXX_cex.csv.
The file MELDUNGEN.TXT must be imported into Alarm Logging. The export of the alarms
like on the first import of all alarms must not be done for new objects.
For more detailed information when add new objects, please refer to the description of the
initial import.
The sequence for new objects again in a short form:
1. Copy the old Excel file and delete not used tables and cells.
2. Fill table TAG.
3. Export WinCC text library and obtain the next free text ID.
4. Run macro "Objekts"
5. Append file TEXTLIB.CSV to the exported text library and import the text library to
WinCC.
6. Import the structure variables file VEXstruc.txt (CTyp > 1000) with VAREXIM.EXE
(IMPORT).
7. Import the single variables file VEXvariables.txt (CTyp < 1000) with VAREXIM.EXE
(IMPORT OVERWRITE).
8. Import the alarms from file MELDUNGEN.TXT to Alarm Logging.
Attention:
If the text library on the engineering station and on the server is different, then you have to
check for the next free text number for the engineering station and on the server. You need in
this case two Excel files with the new objects. Start in each Excel file the macro “Objects” and
enter there the next free text ID (for engineering station and for server).

3 - 26 Copyright © Siemens AG. All Rights Reserved.

 Configuration Manual_V7 Migration V2 -> V7

Hint:
If e.g. on the engineering station the next free text ID is higher than on the server, enter in the
text library off the server some dummy texts ontill you reach the next free text ID of the
engineering station. In this case the next free text ID for engineering sation and on the server
is the sam text ID. In this case you need only one Excel file for the new objects.

Copyright © Siemens AG. All Rights Reserved. 3 - 27

Migration V2 -> V7 Configuration Manual_V7

Improvement of the performance of the status call

Problem
Sometimes it happens that the status call of groups and routes are aborted without result. In
this case the status call window remains empty. The reason is a overload of the DCOM
interface in Windows or a overload of the PMC S5 channel.

Solution
If this problem appears a additional engineering work could be done to avoid the database
access with DCOM. You have to create a INI file with all structure tags. This INI file =
S5_Tags.ini could be created with the Excel tool Create_stat_ini.xls. For this, you have to
export the WinCC tag management with the smart tool VAREXIM.EXE. The export must be
saved into the files WINCC_cex.csv, WINCC_dex.csv and WINCC_vex.csv. Copy these three
files together with the Excel tool Create_stat_ini.xls into the same directory. Start the macro
"Create_INI". The macro "Create_INI" creates the INI file S5_Tags.ini. Copy the created INI
file S5_Tags.ini to all operating stations (Clients, Single stations, Engineering stations and
Servers with operating interface) to the directory D:\CEMAT_CS\BIN. If you create later on
new tags, you have to create a new INI file and you have to copy again this INI file to all
operator stations.

3 - 28 Copyright © Siemens AG. All Rights Reserved.