Professional Documents
Culture Documents
Migration V4 ->V7
A&D CC Cement
Configuration Manual_V7 Migration V4 -> V7
Migration V4 -> V7
Contents
Migration V4 -> V7 1
General Information ................................................................................................. 3
Overview ..................................................................................................................4
Installation Notes for PCS 7.....................................................................................5
PG/PC Interface..........................................................................................5
Installing the CEMAT Software ................................................................................ 6
Settings for alarm logging and annunciation system like Cemat V6.0 ....... 6
Installation of Cemat S5 Migration Files ..................................................... 6
Extra Settings in the WinCC Project ........................................................................ 7
Setting Parameters for Tag Management ..................................................7
Process Picture Symbols ............................................................................8
Picture Tree ................................................................................................8
Generating and loading of the Server Data ................................................ 8
Synchronizing the Time of Day (only on the primary server) ..................... 9
Importing from CEMAT V4.....................................................................................11
Export data from the SQL server 6.5 to text files...................................... 11
Regional settings ......................................................................................13
Importing to Excel .....................................................................................14
Adjustments on the TAG list .....................................................................15
Creating Object Structures and PLCs in WinCC ...................................... 16
PMC Message Numbers...........................................................................18
WinCC Text Library...................................................................................20
WinCC Process Tags ...............................................................................22
Generating Messages...............................................................................24
Group messages (Area) ...........................................................................26
User Archive .............................................................................................26
Adapting the PLCs ....................................................................................27
Project Additional Objects......................................................................................28
Sequence for engineering of additional objects........................................28
Structure table TAG ..................................................................................30
Improvement of the performance of the status call ...............................................31
Problem.....................................................................................................31
Solution .....................................................................................................31
Object variable defintion forCEMAT V4-->V7 ........................................................32
Object variable defintion forCEMAT V4-->V7 E module.......................... 32
Object variable defintion forCEMAT V4-->V7 Damper .............................35
Object variable defintion forCEMAT V4-->V7 Valve ................................ 39
Object variable defintion forCEMAT V4-->V7 M-module......................... 42
Object variable defintion forCEMAT V4-->V7 Select module .................. 43
Object variable defintion for CEMAT V4-->V7 Route .............................. 44
Object variable defintion forCEMAT V4-->V7 Group............................... 47
Object variable defintion forCEMAT V4-->V7 Silopilot ............................ 50
Object variable defintion forCEMAT V4-->V7 Runtime-module .............. 53
Object variable defintion forCEMAT V4-->V7 Counter module ............... 53
Object variable defintion forCEMAT V4-->V7 Measuring module UM .... 54
Object variable defintion forCEMAT V4-->V7 Controller ......................... 57
General Information
This chapter describes the creation of a WinCC project on an engineering station (ES) and
taking over the data from a V4 project.
To be able to take over the data, the following requirements must be met:
V4:
• SQL-Server V6.5 is with actual database available (get from the plant the actual database
backup).
• EXPORT.EXE for reading the SQL data and write into text files.
• The PLC software is available.
• The latest version of the PLC standard blocks of Cemat V4.12 is available and the PLCs
are updated to the latest version of V4.12. A PLC with V4.10 / V4.11 must be updated to
V4.12 (Cemat object function blocks).
• The EXCEL file MIG_V4_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.
• License for SIMATIC S5 PMC Ethernet exists.
MLFB-Nr.: 2XV9450-1WC43-0JX0.
• Structure import list "MIG_V4_V6_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.
• Communication to EOS/EMS via MIS-DP is not possible.
• Communication to QCS via MIS-DP is not possible.
• E-module:
Parameter display – no RUN lamp display.
• Damper-module:
Parameter display - Smoothing Value and X-Faktor are not longer available.
Modul flags TST1 and TST2 are not longer available.
• M-module:
Modul flags – no MELD lamp display.
• Valve:
Parameter display – no RUN lamp display.
• UM measured value:
Normal work space could not longer be set (ABO, ABU).
Parameter Xfactor is not longer available.
• Route module:
Display of module flags WAS and WOS are not longer available.
Only the static and dynamic fault in the diagnosis window.
• Group module:
Extension: Display of Operating message.
• Silopilot::
Measured value „Empty“ is not longer available.
• The help button is not working in the S5 migration. There are no PDF files for S5 versions
available.
Overview
MS SQL 6.5 EXCEL TAG Export Import WinCC
with VAR_EXIM.EXE
Import to
EXPORT.EXE MELDUNGEN Alarm Logging
Add to text
TAG TEXTE library
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 BCE to "ISO Ind. Ethernet"
.
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.
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.
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.
Enter PLC numbers and click one by one to all buttons („TAG“, „M1_M2, M type“, „Locations“,
IO“, „MCC“, „PLC“, „Sound“. „AG“ and „BINT“).
Select for all buttons the ODBC data Source:
After this procedure there should by created 10 text files. The location of the text files is the
location of the EXPORT.EXE:
TAG.TXT, M1_M2_M.TXT, M_ART.TXT, GEN_LOC.TXT, IO_LOC.TXT, MCC_LOC.TXT
PLC_LOC.TXT, SOUND.TXT, AG.TXT, BINTRACK.TXT
Maybe there are some problems with the tool EXPORT.EXE, e. g. to much data and too less
memory. In this case you could create the text files with the attached SQL scripts.
Please save the data from the result window as RPT file. Use the corresponding name to the
SQL script. Copy the Excel file MIG_V4_V7.XLS and the report files TAG.RPT,
M1_M2_M.RPT, M_ART.RPT, GEN_LOC.RPT, IO_LOC.RPT, MCC_LOC.RPT,
PLC_LOC.RPT, SOUND.RPT, AG.RPT, BINTRACK.RPT into the same folder and start the
macro “convert_rpt“. The report files RPT are converted into TXT files separated by tab stops
(like the files created by EXPORT.EXE).
This way the files TAG.TXT, M1_M2_M.TXT, M_ART.TXT, GEN_LOC.TXT, IO_LOC.TXT,
MCC_LOC.TXT, PLC_LOC.TXT, SOUND.TXT, AG.TXT and BINTRACK.TXT also can be
produced.
Regional settings
If the are problems during import, lease change during the complete import your regional
settings in control panel:
Control panel -> Regional and language options -> Customize -> Numbers.
Decimal symbol = "." = dot
Digit grouping symbol = "," = Comma
List separator = ";" = Semicolon
Change back to your original settings after a successful import.
Importing to Excel
Copy the Excel file MIG_V4_V7.XLS and the text files TAG.TXT, M1_M2_M.TXT,
M_ART.TXT, GEN_LOC.TXT, IO_LOC.TXT, MCC_LOC.TXT, PLC_LOC.TXT, SOUND.TXT,
AG.TXT, BINTRACK.TXT into the same folder and start the macro „Import_sql“.
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_V4_V7.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.
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 one message per PLC
(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.
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_V4_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.
Check: The message types, TAGs, comments etc. should now be in the text library.
The text numbers must be complete. No gaps!!!!
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.
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.
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
Click on "Selection" and enter the lowest and highest user message number:
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.
User Archive
Start the "User" 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 "USER" table should be filled with the data of the existing TAGs.
Install the user archive and import data according to the CEMAT V7 description.
S5 CP143 WinCC
CP1430 Tag Management
UPNOV4.S5D PMC-Kanal
MLFB 2XV9450-1WC43-0JX0
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.
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.
VISU_OS decimal hex Status for symbol and texts in faceplate DR1
white 1 1 off
red blinking 2 2 fault not acknowledged
red 3 3 Fault acknowleged
green 4 4 running
yellow 101 65 local mode
yellow blinking 104 68 local mode running
blue 201 C9 single mode
blue blinking 204 CC single mode running
ment CEBASS
VISU_OS decimal hex Status for symbol and texts in faceplate DR1
white 1 1 MV OK
red blinking 2 2 MV > upper limit 2 and not acknowledged
red 3 3 MV > upper limit 2
yellow blinking 4 4 MV > upper limit 1 and not acknowledged
yellow 5 5 MV > upper limit 1
yellow blinking 6 6 MV < lower limit 1 and not acknowledged
yellow 7 7 MV < lower limit 1
red blinking 8 8 MV < lower limit 2 and not acknowledged
red 9 9 MV < lower limit 2
yellow, black 10 A MV faulty (LZ) and not acknowledged
yellow, black 11 B MV faulty (LZ)
white, magenta 12 C Positive gradient overshot
white, magenta 13 D Negative gradient overshot
white, blue 14 E Measuring channel blocked
C_641_BINT1
Assign- rel. address
Variable name ment Bit Designation english CEBASS
BIT1 1 Binary track 1 D 1.1
#areaname Area internal tag
#blocktype Block type = BINT internal tag
#comment Comment internal tag
C_641_BINT2
Assign- rel. address
Variable name ment Bit Designation english CEBASS
BIT2 2 Binary track 2 D 1.2
#areaname Area internal tag
#blocktype Block type = BINT internal tag
#comment Comment internal tag
C_641_BINT3
Assign- rel. address
Variable name ment Bit Designation english CEBASS
BIT3 3 Binary track 3 D 1.3
#areaname Area internal tag
#blocktype Block type = BINT internal tag
#comment Comment internal tag
C_641_BINT4
Assign- rel. address
Variable name ment Bit Designation english CEBASS
BIT4 4 Binary track 4 D 1.4
#areaname Area internal tag
#blocktype Block type = BINT internal tag
#comment Comment internal tag
C_641_BINT5
Assign- rel. address
Variable name ment Bit Designation english CEBASS
BIT5 5 Binary track 5 D 1.5
#areaname Area internal tag
#blocktype Block type = BINT internal tag
#comment Comment internal tag
C_641_BINT6
Assign- rel. address
Variable name ment Bit Designation english CEBASS
BIT6 6 Binary track 6 D 1.6
#areaname Area internal tag
#blocktype Block type = BINT internal tag
#comment Comment internal tag