Professional Documents
Culture Documents
Introduction
Content
Introduction
General ........................................................................
...........................................2
Documentation structure.........................................................
................................3
Guide...........................................................................
............................................5
Copyright Siemens AG. All Rights Reserved. 1 - 1
Ausgabe: 30.09..2005
N:\Cemat\DOKU\V70\English\Engineering\01_Introduction_009.doc
Check list......................................................................
..........................................20
Copyright Siemens AG. Alle Rechte vorbehalten. 2 -1
Ausgabe : 08.03..2006
N:\Cemat\DOKU\V70\English\Engineering\02_Preparations_009.doc
=
=
=
=
=
=
=
=
=
=
CEMAT
Holcim
Dyckerhoff
Heidelberger Zement
Vigier
Bushehr
Caima
Alsen
Lafarge
Rossi
The main difference between the project standards are the change of operation mo
de and the
evaluation of the local switch. Make sure that the selected project standard fit
s to the
requirements of the plant (MCC / Plausibility, Local switch, Operation modes).
The name of the project standard is often derived from the Company or Group for
which the
project version was designed. In some cases it is just the name of the first pla
nt where it was
used.
!
Important: Please consider that in case of a Project standard for a Group this d
oes not
automatically mean that each plant of this group uses this version. Some plants
were bought
by a group when there were already running Cemat installation. For the sake of c
ompatibility
it may be better to continue with the existing Cemat Version.
!
Caution: In some occasions, additional adaptations may be needed for the evaluat
ion of the
signals. These adaptations have to be achieved through a specific logic in the a
pplication
program.
On the following pages you find a description of the project standards with its
main
distinguishing characteristics.
If you furthermore have questions regarding project versions, please don't hesit
ate to ask in
the Competence Center.
Copyright Siemens AG. All Rights Reserved. 2 - 3
Alsen
Local mode is enabled through Operator
Station (Faceplate buttons)
027 Lafarge *) Local mode is enabled through Operator
station.
*) Lafarge has a completely different operating philosophy and different block n
ames and can
not be compared with other project standards.
2 - 4 Copyright Siemens AG. All Rights Reserved.
C_VALVE
C_ANNUNC
C_ANNUN8
C_PROFB
C_ROUTE
C_GROUP
C_SILOP
C_ADAPT
Copyright Siemens AG. All Rights Reserved. 2 - 7
C_VALVE
2 - 8 Copyright Siemens AG. All Rights Reserved.
C_AIB
C_SSB
C_SSDB
C_BPB
028 Rossi Waiting time for single start-up-warning
- In single-start-mode, the drives are switched on after the
horn is off and the waiting time has elapsed (as it is in the group).
Alarms for xBM and xSB in local mode
- In the normal standard, in local mode no alarm will be generated
for xBM and xSB.
In Rossi Standard, alarms will be generated also in local mode.
C_DRV_1D
C_DRV_2D
Copyright Siemens AG. All Rights Reserved. 2 - 9
card 192.168.2.10
card 192.168.2.11
on card 192.168.2.20
on card 192.168.2.21
on card 192.168.2.22
on card 192.168.2.23
OSC01
OSC02
OSC03
OSC04
....
192.168.1.101
192.168.1.102
192.168.1.103
192.168.1.104
Buttons in the
Overview Range and for the assignation of Access Right.
Example:
The first hierarchy folder was selected as OS Area
olders
Crusher, RawMill, Kiln, CementMill and Packing.
In the Overview Area of the Runtime System you will see the buttons: Crusher, Ra
wMill, Kiln,
CementMill and Packing for direct Picture calls.
If an Operator has only the Authorization for the areas Crusher and Raw Mill, he
is only
permitted to watch and to operate these areas.
The Messages in the Alarm line and the acknowledgement function is filtered in t
he same way
via the OS Area.
!
Caution: The CEMAT Message system can handle up to 32 Areas!
Copyright Siemens AG. All Rights Reserved. 2 - 13
Engineering Cemat V7
Preparations
Engineering Rules
Per plant the responsible engineering department must determine the project defi
nitions.
Henceforth these unique definitions are valid for all AS of the plant.
Especially if the engineering is done at different locations and for supplementa
ry plant
extensions it has to be insured that the original project definitions are used.
Definitions for the Engineering:
Name of the PC Stations
Definition of AS Numbers
Addressing of the AS and PC Stations (MAC Addresses, TCP/IP Addresses, Profibus)
Definition of the Project Standard and Version
The designation system of the plant tags (charts, modules, signals)
Definition of the message texts (Event)
Variable names
Names of the WinCC pictures
Rules for the generation of scripts and actions
Engineering rules (Customer standards, Teamwork)
Definitions for the documentation of a project
Definitions for the Runtime-Project:
The operation surface (Division of the screen, Font style and size, Language in R
untime,
Representation of the objects)
The operation concept (Picture hierarchy, operating philosophy, user rights, per
mitted
keys)
The color definition for the annunciations, Limit values, Status, Font etc.
The communication (Communication type, Actualization cycles)
The volume of project data (Quantity of alarms, Archive values, Curves, Clients
etc.)
Message and archiving procedure (Archive size and Export Concept)
Archive names per Area
Preparations
Engineering Cemat V7
What is shown WHERE and HOW?
Complete plant overview
Representation: Schematic representation of the complete plant
Content: Overview of the production plant with global status display from the ru
nning
plant sections
Operation: Selection of a production section / a sub-plant
System monitoring, plant configuration diagrams
Representation: Schematic representation of the complete control system
Content: Overview of the network connection of the individual control system dev
ices
with global status display of the individual components.
Operation: Selection of an individual component for detailed analysis
Plant sections:
Representation: Material flow of a complete production plant without secondary a
ggregates
and details
Content:
Display of all physical variables relevant for the process control.
Operation:
Start and stop of the plant
Specification of set points
Assignment of recipes
Invoke overviews for flow diagrams, measured values, closed-loop
controllers, curves
Tabular measured value listing
Process Pictures:
Representation: Representation of the plant sections with all aggregates
Content:
Display of the operational modes, measured values, states, curves, filling
levels
Operation:
Selection, operation of individual aggregates and diagnosis, information and
object parameter invocations
Detail Pictures:
Representation: Representation of the individual aggregates
Content: Display of the operational modes, measured values, states
Operation: Selection, operation of individual aggregates and diagnosis, informat
ion and
object parameter invocations
Help:
Representation: User s guide for the CEMAT system
User s guide for the plant
User key assignment
Content:
Explanations and examples of the system handling.
2 - 18
Copyright Siemens AG. All Rights Reserved.
OS Compile......................................................................
.........................46
OS Configuration (Single-User System)...........................................
.....................47
Project Properties .............................................................
........................47
OS Project Editor...............................................................
.......................48
Computer properties.............................................................
....................51
Tag Management..................................................................
....................53
General changes in the alarm logging............................................
..........54
Tag logging ....................................................................
...........................57
User Archives...................................................................
.........................58
Add User rights.................................................................
........................61
Selection of area specific rights...............................................
.................65
Horn configuration..............................................................
.......................66
CEMAT specific preparations.....................................................
..............68
Generation of the Template Pictures.............................................
...........69
OS Configuration (Server) ......................................................
...............................70
Project Properties .............................................................
........................70
OS Project Editor...............................................................
.......................71
Computer properties.............................................................
....................73
Tag Management..................................................................
....................75
General changes in the alarm logging............................................
..........77
Tag logging ....................................................................
...........................80
User Archives...................................................................
.........................81
Copyright Siemens AG. Alle Rechte vorbehalten. 3 -1
Ausgabe : 09.03.2006
N:\Cemat\DOKU\V70\English\Engineering\03_PCS7_Project_009.doc
AS
Engineering Station
redundant Server-Pair
OS Clients.
!
Note: In our Example the Engineering Station has two Network Cards (1 internal C
P and one
3COM) but no CP1613. In the Hardware Configuration of the PC only one Network Ca
rd for
the connection to the Plant Bus can be configured!
Copyright Siemens AG. All Rights Reserved. 3 - 5
Switch off the Power saving system (for all Devices like Hard Disk, Monitor etc.
) in BIOS and
in the Control Panel
Domain controller
The installation of a Domain controller is not released for Cemat!
Installation of the software for PCS7
Please, always use the actual installation instructions, which are delivered wit
h the PCS7
installation CD. As installation language please select the language in which th
e system is
finally delivered. (Some system messages are only displayed in the installation
language!)
The installation is described in the document PCS7 PC Configuration and Authoriza
tion .
3 - 8 Copyright Siemens AG. All Rights Reserved.
=
=
=
=
=
=
=
=
=
CEMAT
Holcim
Dyckerhoff
Heidelberger Zement
Vigier
Bushehr
Caima
Alsen
Rossi
Master
es must
be merged. In the SIMATIC Manager you will find the merge function if you select
the
Multiproject and use right mouse button option Multiproject
Adjust Projects.
3 - 32 Copyright Siemens AG. All Rights Reserved.
OK
!
Caution: If for any reason you have to run the OS-Project Editor again, make sur
e that all
files mentioned under CEMAT Specific Preparations are deselected in Folder Base D
ata .
Otherwise the CEMAT Settings are overwritten with the delivery state of PCS7.
.. See chapter CEMAT Specific Preparations!
3 - 50 Copyright Siemens AG. All Rights Reserved.
-> Properties
in the sam
rchive (Size of
the archive, archiving duration, default values for archiving cycles) and to con
figure the
archive later, because at this moment no measures exist and therefore no archive
variables
can be created.
Copyright Siemens AG. All Rights Reserved. 3 - 57
is allowed to:
operate
Raw Mill
The area System is disabled for Operator1.
Messages are only shown for areas which are enabled for operation. Operator_1 wi
ll get only
the messages from the Raw Mill area and he can acknowledge only these messages.
Copyright Siemens AG. All Rights Reserved. 3 - 65
Horn
-> Properties
in the sam
At this step it is probably more convenient, only to prepare the process value a
rchive (Size of
the archive, archiving duration, default values for archiving cycles) and to con
figure the
archive later, because at this moment no measures exist and therefore no archive
variables
can be created.
3 - 80 Copyright Siemens AG. All Rights Reserved.
OK
!
Caution: If for any reason you have to run the OS-Project Editor again, make sur
e that all
files mentioned under CEMAT Specific Preparations are deselected in Folder Base D
ata .
Otherwise the CEMAT Settings are overwritten with the delivery state of PCS7.
.. See chapter CEMAT Specific Preparations!
3 - 92 Copyright Siemens AG. All Rights Reserved.
If the preferred Server is stopped the Client automatically switches to the Part
ner-Server.
Once the preferred Server runs again, the Client automatically switches back to
the preferred
Server.
Copyright Siemens AG. All Rights Reserved. 3 - 99
is allowed to:
operate
Raw Mill
The area System is disabled.
Only messages from areas which are enabled for operation
Messages are only shown for areas which are enabled for operation. Operator_1 wi
ll get only
the messages from the Raw Mill area and he can acknowledge only these messages.
3 - 100 Copyright Siemens AG. All Rights Reserved.
The following Archive configuration has to be set up in "Tag Logging" and is typ
ical for a
cement plant.
Tag Logging Fast and Slow:
4. Archive size: Timeframe over all segments: 6 months.
5. Maximum size over all segments: 7 Gbyte.
The Process Value Archive contains stored values of variables that have been cre
ated in the
Process Value Archive.
The Process Value Archive is configured as a cyclic archive. Storage location is
the hard
drive.
Copyright Siemens AG. All Rights Reserved. 3 - 105
single ope
Engineering Examples
Engineering Cemat V7
Measured Values, Calculated Values
Certain values are calculated during the plant configuration, e.g. total amounts
from subamounts, temperature or pressure average values.
The values and measured values that are read using Analog Inputs are analog valu
es for
which a measuring value module must be programmed.
To improve the readability, the calculation should be performed before the invoc
ation of the
measuring value module.
The measuring value module permits a simple inclusion of the calculated values i
n the HMI
system.
Measured Values, Limit Value Evaluation
The limit value signals are often used for start or operation interlocks of grou
ps.
The following points should be observed:
To prevent interlocks appearing on the group fault lamp, interconnect UMZS.
If, for example, the alarm interlock is interconnected with GVG, the measuring v
alue
module provides alarm messages only for a running group.
The status call-up can at any time be used to request pending annunciations (als
o for a
stationary group).
Example:
Silo full
Warning for H
Switch-off for HH
UMZS UAMV
UM
G
H HH
GEVG GBVG
>1
GVG
5 - 10
Copyright Siemens AG. All Rights Reserved.
Engineering Examples
Engineering Cemat V7
Measured Values, Supervision of the Motor Current
Motor Current, Pressure or Flow shall not create any alarm message if the associ
ated motor
is not running. During the startup of the motor the alarm message must be suppre
ssed for
some second.
The following description shows a solution example, considering the following ta
sks:
The upper limits H and HH are enabled 5 seconds after the motor is running. This
is made
through interfaces RA_H and RA_HH.
The lower limits L and LL are enabled as soon as the motor is running. This is m
ade
through the connection of RA_L and RA_LL with the running signal EVS of the moto
r.
During the startup no Life Zero Message shall be generated. See OR function at R
A_LZ.
If the motor has to be switched off by protection interlock when the high limit
is reached, an
additional time delay has to be programmed because the Limit Overshoot bits are
set
independent of the enable bits.
5 - 12
Copyright Siemens AG. All Rights Reserved.
Engineering Examples
Engineering Cemat V7
Group Feedback Off GRAZ
A signal that uniquely specifies that the group is stationary (negated feedback
of the group
drives).
a) Group without routes
GRAZ
E04/EVS
E05/EVS
E09/EVS
&
b) Group with routes
WRA=0 means:
Route is not selected or route has been selected but all associated
drives are off.
W01/WRA
&
GRAZ
W02/WRA
5 - 16
Copyright Siemens AG. All Rights Reserved.
Engineering Examples
Engineering Cemat V7
Group Feedback On GREZ
This signal indicates that the group is operating completely.
a) Group without route
Feedback of the last drive in the connection sequence,
if all drives are started in parallel: each the feedbacks of the last drives.
Example:
&
GREZ
E01/EVS
E02/EVS
E07/EVS
b)
Group with routes
WRE=1 means: Route has been selected and is operating
Example:
&
GREZ
> 1 > 1
W01/WRE
W02/WRE
W17/WRE
W19/WRE
W20/WRE
5 - 18
Copyright Siemens AG. All Rights Reserved.
Engineering Cemat V7
Engineering Examples
Annunciation Modules
Below you find three different applications for Annunciation Modules:
a) Drive failures
All Protection Interlocks which lead to a stop of a motor (e. g. belt drift, pul
l rope, bearing
temperature) have to create an alarm message simultaneously with the motor stop.
The alarm message shows the operator which signal has lead to the drive stop and
only
with a present alarm message in the alarm line the fault can be acknowledged via
acknowledge button in the alarm line.
In order to create the alarm message at the same time as the drive stops, the ou
tput
MAU of the Annunciation block has to be connected to the protection interlock of
the
drive.
In order to re-trigger the alarm message with every drive fault (also with each
start
attempt while the fault already exists), the alarm activation MAAT of the annunc
iation
block must be connected with the dynamic fault of the drive.
Interconnect the annunciation release from drive and annunciation module with th
e
same control voltage.
M
1
EST
ESVG
MAU
MST0
1
E
MAAT
pull-rope
control voltage
EMFR
MMFR
Copyright Siemens AG. All Rights Reserved.
5 - 27
Engineering Examples
Engineering Cemat V7
b)
Process signal annunciations (interlocks)
Report process signals, such as silos level and other interlocks.
Please observe the following points:
Interlocks should not be transmitted to the group as a fault , i.e. they should not
be
indicated at the group summarizing fault indication and the group start GBE shou
ld
not be interrupted in case of an alarm, caused by this signal.
This is achieved by connecting a LOG1 signal to interface MMZS.
To ensure annunciation and interlocks occur concurrently, use the annunciation
module output MAU for the interlock.
If the alarm interlock is interconnected with, for example, GVG, the annunciatio
n
module provides an alarm message only for a running group.
The status call-up can at any time be used to request pending messages (also for
a
stationary group).
Silo full
LOG1
G
M
1
GDE *)
GBVG
MAU
MAMV MST0 MMZS
1
*)
Refer to Alarm Interlock
c)
Additional information which never creates an alarm message (for group status ca
ll)
An operating conditions like "no route selected" shall be shown to the operator
in the
group or route status call function. The missing operating condition shall never
create an
alarm message.
The programming is similar to the example above, only the alarm interlock MAMV i
s
connected with a steady 0-Signal.
The output MAU of the annunciation module is used as interlocking condition for
the
group.
5 - 28
Copyright Siemens AG. All Rights Reserved.
st
Engineering Examples
Engineering Cemat V7
The connection example becomes clearer by considering the individual functions t
hat must
satisfy a change of routes without interrupt.
The route change can only take place when the group is stationary or runs comple
tely
. refer to WHVR
If a route was pre-selected and the pre-selection of another route is added, the
n the own
pre-selection must be removed.
. refer to WVWL and WUUS
In case of a route change without interrupt the group has
is
completely running (because the drives of the old route
To permit the group to give the start command again, the
e
feedback On must be removed. This is done by linking the
with
the drive feedbacks.
. refer to WREZ
to be started while it
are still running).
group feedback On / rout
route pre-selection WVE
The old route is deselected automatically once the newly started route runs comp
letely.
. refer to WVWA
The de-selection of the old route stops the drives that are no longer required.
. refer to EBVG from E02 and E03
The disconnection of the complete group is performed only for group stop (use GD
A
signal) or for a fault if the switching has not been performed within a specifie
d time.
. refer to EBFA from E01
5 - 34
Copyright Siemens AG. All Rights Reserved.
on an in the
only help.
All other blocks from the PCS7 standard library can be used as well.
Copyright Siemens AG. All Rights Reserved. 6 - 3
AS Engineering
Engineering Cemat V7
Acknowledgement mode
In CEMAT V7 two acknowledgement modes exist: The fault acknowledgment can be car
ried
out either for the complete AS or group-wise (refer to Reference Manual, System)
.
By default the fault acknowledgement is carried out per AS. If the fault acknowl
edgement
shall be carried out per group, this requires a modification of the settings in
the system chart
and some additional programming for each object.
Group-wise acknowledgement
In the System chart at block C_FB_PLC you have to change the setting for paramet
er
AKC_GR at block to 1-Signal.
In order to acknowledge the objects by the corresponding group you have to link
the output
ACK of the group with the interfaces EQIT, VQIT, KQT1 etc. of all objects belong
ing to the
Example for a Motor:
G1 M1
C_GROUP MAIN_TASK C_DRV_1D MAIN_TASK
Transport Group 1/5 Motor 1 1/2
ACK BO BO EQIT
G_LINK I
I GR_LINK1
I GR_LINK2
I MUX_LINK
group.
6 - 18 Copyright Siemens AG. All Rights Reserved.
In sequence test mode, for all Drive and Annunciation blocks the output SIM_ON i
s set. If
module drivers are used, the output SIM_ON can be connected to input SIM_ON of t
he driver
block in order to use the Simulation Value. See also Using driver blocks with CEM
AT .
In case of the Motor, the feedback of the contactor and eventually a speed monit
or are
simulated. In case of damper or valve, the limit switches are simulated.
All further hardware inputs are still active and must be simulated via test prog
ram at the
beginning of OB1 Cycle.
If module drivers are used, the output SIM_ON of the CEMAT block can be connecte
d to
input SIM_ON of the driver block in order to use the simulation value.
Using driver blocks with CEMAT
Driver blocks are not necessary for Cemat. As before, the block inputs and outpu
ts can be
directly connected to the periphery (process image). The only exceptions are the
Analog
outputs (e. g. from a PID controller), where the calculation from REAL value to
card value is
carried out by the driver block CH_AO.
Some customers use driver blocks for Analog Inputs as well. (The driver block de
tects the
Card type and converts the Card Value into REAL format.)
Caution: Through the driver wizard a lot of additional charts and blocks are gen
erated which
require additional resources (Communication jobs). This can especially be critic
al if ET200S
periphery is used.
!
From Cemat V6, connecting the Cemat blocks to the driver blocks is possible. If
you wish to
use driver blocks in your project, please pay attention to the following enginee
ring rules:
Copyright Siemens AG. All Rights Reserved. 6 - 19
Engineering Cemat V7
AS Engineering
OS Compile
With the OS Compile the following steps are carried out:
From the CFC blocks all Variables with Attribute 'Operator Control and Monitorin
g' are
transferred into the Tag Management of WinCC. The Messages, defined in the CFC
blocks are transferred to the Alarm Logging.
In the background the Archive variables are generated. (This function cannot be
used in
Cemat because all automatically generated Archives are created in the SystemArch
ive. In
Cemat the Archives have to be located in the ProcessValueArchive or in an Area s
pecific
Archive.
Also in the background the Block Icons are generated and/or actualized. In order
to
prevent the automatic generation you have to deselect the option in the Object p
roperties
of the Process picture.
The SFC Visualization is generated. (This is not needed on Cemat.)
Based on the Plant view of the SIMATIC Manager the Picture Tree is created and/o
r
actualized. This is essential because in this step also the Group Display get ac
tualized.
Start the OS Compile from the SIMATIC through selection of the OS with right mou
se button
and option 'Compile'.
In the Introduction Window say 'Next >'
In the following window you see the assignment of the areas to the operation sta
tion:
Continue with 'Next >'
Copyright Siemens AG. All Rights Reserved.
6 - 27
AS Engineering
Engineering Cemat V7
Project-Download
After new plant objects or pictures were added the Servers and the Client have t
o be updated
as well. This requires a Project Download to the OS PCs.
If there was no structural change and as long as an OS Compile for changes is po
ssible the
OS Stations can remain in Runtime mode during the Project Download. After a comp
lete OS
compilation the destination Project has to be deactivated during the Download pr
ocedure.
!
Note: The modifications in the OS-Projects for the Server, Standby-Server, and T
erminals are
never carried out directly on the OS Stations. Any modification has to be carrie
d out on the
Engineering station and then being downloaded are different OS Stations.
The update procedure can be performed manually (step by step) or automatically u
sing the
Compile and Download Objects Dialog in the SIMATIC Manager.
Manual update procedure for changes (The AS is running and both Servers are acti
vated):
1.
Compilation for changes of the AS-Program (from CFC)
2.
Download for changes of the CFC
3.
Compile the OS Project(s)
The compilation of the OS must be carried out for each Server and single station
.
At the end of the OS Compile procedure the Server Data is automatically updated
by the
system and the updated package is automatically loaded into the Client Projects.
4.
For the Download for changes in a Server Project, select the OS in the SIMATIC M
anager
and press the Download Button. The Download for changes is carried out first to
the
Standby-Server. The 'Successful completed' message must be confirmed. After that
the
Download is carried out to the primary Server. The Clients get automatically act
ualized as
well (the new package is loaded).
5.
For the download into the Single User Station use the same procedure.
6 - 30
Copyright Siemens AG. All Rights Reserved.
AS Engineering
Engineering Cemat V7
Structural changes (e. g. the format of a variable was modified for an existing
object or a
variable was added) result in an interface conflict and require the stop of the
Runtime System
during the Project Download. This is still no problem because of redundant Serve
rs but the
Download Procedure is slightly different:
1.
To actualize the Tag Management an OS Compile has to be performed.
The OS Compile must be carried out into the OS-Projects of ES and Server.
At the end of the OS Compile procedure the Server Data is automatically updated
by the
system and the updated package is automatically loaded into the Client Projects.
2.
After that you must close the OS-Project on the primary Server Station. First cl
ose the
WinCC Explorer (if it is not already closed) and second the Runtime.
The Standby-Server will be MASTER, the Clients will be switched to the Standby-S
erver.
!
Important: After closing the WinCC Project on the Server Station, you have to wa
it for
at least 2 minutes. During this time the project is still used .
3.
Now you can carry out the Project-Download from the Engineering Station to the p
rimary
Server Station. The Server-Project on the Engineering Station must remain closed
. The
Download is carried out from the SIMATIC Manager.
4.
Wait for the Download successfully completed
Message before you continue.
5.
After both Servers are running again, the Redundancy Manager starts actualising
the
Server data. If possible wait until the procedure is finished.
6.
Now you can close the OS-Project on the Standby Server Station. First close the
WinCC
Explorer (if it is not already closed) and second the Runtime.
The primary Server will be MASTER, the Clients will be switched to the primary S
erver.
!
Important: After closing the WinCC Project on the Server Station, you have to wa
it for
at least 2 minutes. During this time the project is still used .
7.
Now you can carry out the Project-Download from the Engineering Station to the
Standby-Server Station. The Download is carried out from the SIMATIC Manager.
8.
After the Download successfully completed
Message the Project Download is finished
!
9.
If it is necessary to update the Clients as well (may not always be required), u
se the same
procedure for each Client.
6 - 32
Copyright Siemens AG. All Rights Reserved.
Engineering Cemat V7
AS-AS Coupling
Send with SEND_BO
With block SEND_BO up to 128 BOOL values can be sent. If more than 128 BOOL valu
es
are needed, the block can be called multiple times. The different orders are ide
ntified by
Parameter R_ID. In the destination AS a block REC_BO must be called which has th
e same
R_ID as in the corresponding send call.
The ID of the S7 connection you find in the connection programming in NETPRO.
Example: PLC02 sends data to PLC01:
According to the NETPRO connections above the Send call in the AS PLC02 must hav
e the
ID "A1". The corresponding Receive call in the AS PLC01 must have the ID "A2".
The send job will be triggered by the (invisible) parameter "COM". To trigger th
e send job
each second then there are two possibilities:
1.
Keep the parameter "COM" at default value "1" and call the block SEND_BO in OB32
(each second).
2.
Change parameter "COM" to "visible" and connect it to a pulse (one pulse each se
cond).
The block SEND_BO must be called at least every second (corresponding OB).
See the help function of SEND_BO.
Copyright Siemens AG. All Rights Reserved.
7 - 3
Engineering Cemat V7
AS-AS Coupling
Send with SEND_R
With block SEND_R up to 32 BOOL values and 32 REAL values can be sent. If more t
han 32
BOOL values or more than 32 REAL values are needed, the block can be called mult
iple
times. The different orders are identified by Parameter R_ID. In the destination
AS a block
REC_R must be called which has the same R_ID as in the corresponding send call.
The ID of the S7 connection you find in the connection programming in NETPRO.
Example: PLC02 sends data to PLC01:
According to the NETPRO connections above the Send call in the AS PLC02 must hav
e the
ID "A1". The corresponding Receive call in the AS PLC01 must have the ID "A2".
The send job will be triggered by the (invisible) parameter "COM". To trigger th
e send job
each second then there are two possibilities:
1.
Keep the parameter "COM" at default value "1" and call the block SEND_R in OB32
(each second).
2.
Change parameter "COM" to "visible" and connect it to a pulse (one pulse each se
cond).
The block SEND_R must be called at least every second (corresponding OB).
See the help function of SEND_R.
Copyright Siemens AG. All Rights Reserved.
7 - 5
BE ;
See example function block FB SEND_CFC_EXAMPLE (FB 1601)!
For each SEND_CFC_EXAMPLE you have to create the appropriate function block
RECEIVE_CFC_EXAMPLE for receiving the data with exactly the same parameters. But
on
the receive side these are output parameters. See chapter with RECEIVE_CFC_EXAMP
LE.
The function block BSEND_CALL (FB 1603) is a simple call of the system function
block
SFB12 BSEND. Up to 65534 byte could be send with the function block BSEND.
Attention: Max. 400 bytes can be transferred in one telegram as a consistent dat
a block. If
you have to transfer more data and the consistency is important you have to take
care of this
at the receive side. See consistency at the receiving!
Copyright Siemens AG. All Rights Reserved. 7 - 7
The function block BRCV_CALL (FB 1604) is a simple call of the system function b
lock
SFB13 BRCV. Up to 65534 byte could be send with the function block BSEND.
Copyright Siemens AG. All Rights Reserved. 7 - 9
Engineering Cemat V7
AS-AS Coupling
Performance Data
20 SMR-PLCs and 4 third-party PLCs (CEMAT V1.9, V2.0, V3.0 / V4.0 other control
system or third-party system).
Transmission of CEMAT user data blocks (DB599 >= DB => DB 400).
Max. transmission length = 600 Bytes.
Initiation of the individual transmissions by setting the initiation bit TRIGGER
in the send
PLC.
Signalling of the successful transmissions through a set message bit RECEIVED in
the
receive PLC.
Coupling monitoring in case of parameterized coupling request.
Individual user telegram monitoring for each of the 24 couplings:
If the monitoring time is exceeded the receive DB can be deleted on request comp
letely or
partially.
Diagnostics interfaces like:
Global display for bus A and bus B from the point of view of each individual PLC
:
Bus is OK.
Receipt OK (bus A or bus B) for each parameterized coupling job.
Parameterization error for each parameterized coupling job.
Status (bus A or bus B) for each parameterized coupling job.
Copyright Siemens AG. All Rights Reserved.
7 - 13
Project network
Engineering Cemat V7
AS-AS Coupling
Diagnosis Variable for Users
A fault-free coupling is only possible if the parameterization error bits and fa
ult bits have the
value 0. Otherwise one must search for the fault and correct it using the additi
onal
information.
Diagnosis SEND in the parameter-set of FB C_PLC_SEND:
BUS_A_FT = Fault during SEND on bus A to PLC x
BUS_B_FT = Fault during SEND on bus B to PLC x
ENG_ERR = Parametrize failure on SEND to PLC x
COM_ERR = dynamic fault during SEND to PLC x
E_ERR_CO = Error code for engineering failure for SEND to PLC x
A_ERR_CO = Error code for SEND on bus A to PLC x
B_ERR_CO = Error code for SEND on bus B to PLC x
Diagnosis RECEIVE in the parameter-set of FB C_PLC_ RECEIVE:
BUS_A_FT = Fault during RECEIVE on bus A to PLC x
BUS_B_FT = Fault during RECEIVE on bus B to PLC x
ENG_ERR = Parametrize failure on RECEIVE to PLC x
COM_ERR = dynamic fault during RECEIVE to PLC x
E_ERR_CO = Error code for engineering failure for RECEIVE to PLC x
A_ERR_CO = Error code for RECEIVE on bus A to PLC x
B_ERR_CO = Error code for RECEIVE on bus B to PLC x
R_LENGTH = Received telegram length in bytes
COUNT_T = telegram counter
Additional informationen for parameterization error in ENG_ERR_CODE:
0
1
2
3
4
5
6
7
=
=
=
=
=
=
=
=
No error!
Illegal DB (only > 400)!
DB does not exist!
1st DW is not permitted!
Send-DB is too short!
Sending length is not permitted (max. 238 bytes)!
Receive-DB for block delete during absence of user telegram is too short!
Block length for block delete during absence of user telegram is not
permitted!
8 = Receive-DB is too short for received length!
9 = A send-DB is entered in the parameter-set for your own PLC!
10 = A receive-DB is entered in the parameter-set for your own PLC!
Error codes in case of a communication fault:
"AG_AG_KOMMUNIKATION".VERBINDUNG_x.FEHL_SEND_A
Error code SEND Bus A
"AG_AG_KOMMUNIKATION".VERBINDUNG_x.FEHL_SEND_A
Error code SEND Bus B
"AG_AG_KOMMUNIKATION".VERBINDUNG_x.ANZW_REC_A
Error code RECEIVE
Bus A
"AG_AG_KOMMUNIKATION".VERBINDUNG_x.ANZW_REC_A
Error code RECEIVE
Bus B
Additional information regarding error codes is available in the help (mark bloc
k and press
F1 ) of FC50 (SEND) and FC60 (RECEIVE) or in the NCM S7 manual for Industrial Ether
net.
Copyright Siemens AG. All Rights Reserved.
7 - 17
16372 =
e. g. adress of
Bus B CP
16376 =
e. g. adress of
Bus A CP
7 - 24 Copyright Siemens AG. All Rights Reserved.
the adresses of th
AS-AS Coupling
Engineering Cemat V7
System Description
Diagnosis
The variables table AG_AG_KOM_Diagnose provides an aid for the diagnosis of the
PLCPLC
coupling.
Remedies in Case of Faults
If the coupling does not work properly or not as expected one has to check the f
ollowing:
Is the bus interface CP443-1 inserted for bus A and bus B, respectively?
Check: The bits 0.0 to 0.3 must be set to "0" in DB "00PLC_PLC_ENG"!
Are the addresses of the CP443-1 correctly configured?
The S7 hardware configuration and parameterization on FB C_PLC_PLC (FB1054) must
be identical. The FB C_PLC_PLC (FB1054) must be called in the cycle (OB1) and du
ring
AS restart (OB 100)!
Check: The bits 0.0 to 0.3 must be set to "0" in DB "00PLC_PLC_ENG"!
Check the bus cable connection (Is the plug loose? Bus A or B mixed up?)
Is the connection engineered and loaded to the PLC?
Check the parameters on C_PLC_SEND (FB1052) and C_PLC_RECEIVE (FB1053).
The output parameter ENG_ERR must be 0 . If the is a 1 , check the E_ERR_CO.
(For error numbers refer to page 6)
Check using the variables table "AG_AG_KOM_Projektierung":
If there is no parameterization error, then check status of the connection!
Check using the variables table
AG_AG_KOM_Diagnose:
(For error numbers refer to page 6) The status information must be 0!
If no parameterization error exists and the corresponding connection is OK, then
one must
couple user telegrams.
Check using the variables table
AG_AG_KOM_Diagnose:
Receive bit should be set to 1 and/or initiation bit should be blinking.
Check : Is the initiation bit set?
7 - 26
Copyright Siemens AG. All Rights Reserved.
.
Your template picture should only contain the symbols which are really used. (If
your template
picture contains many unused block icons, the generation of the block icons takes
unnecessary long because always the complete picture is scanned!)
!
Note: With Cemat V7 no Cemat Template Picture @Template.pdl for manual Generatio
n of
Block Icons (with Property 'type' without index) is delivered any more. The @Tem
plate.pdl can
easily be created by the plant engineer, after the template picture @PCS7Typical
s.pdl is
completed.
In the following description you can find the attributes, which are important fo
r CEMAT.
8 - 2 Copyright Siemens AG. All Rights Reserved.
e.pdl (or
@Template1.pdl, @Template2.pdl, ) with symbols without Index or you take the norm
al
Block Icons (from @PCS7Typicals.pdl) and delete the Index after copying.
!
Note: If the block icon has an Index, during the next automatic generation it wi
ll be
"actualized" and eventually the block icon will be deleted.
After that you can adapt the symbol properties (e.g. TooltipText, Formats, Windo
w Position
when opening the faceplate).
Copyright Siemens AG. All Rights Reserved. 8 - 3
OS Engineering
Engineering Cemat V7
Name definitions
Picture Names
For the picture names there are no fixed rules. The maximum length is 24 charact
ers.
Object names
The object names are created in the Engineering of the CFC. In the OS only selec
tion of
existing objects is possible.
Properties of the Block Icons for CEMAT
Most of the CEMAT objects are available as Customized object (all objects, excep
t TE_CTRL
and TE_VSLCT). They can be generated automatically using template picture
@PCS7Typicals.pdl or linked manually using templates from @Template.pdl.
The following description explains the most important properties of each block t
ype:
In Property Miscellaneous you find the attributes regarding Authorization and Pa
ssword
Level and regarding the Faceplate coordinates (at which position the faceplate s
hould be
displayed in the picture).
For all objects which can create an alarm you also find here the color definitio
n for
highlighting the object in case the picture is opened via loop-in-alarm function
.
In Property General the main attributes for the object are defined, such as Tag,
Type,
Tagname, Servername, Version and the Tooltip-Text. Tag and Tagname will be repla
ced
by the Object Tag during automatic generation of block Icons. The other attribut
es, except
Tooltip-Text are standard and don t have to be modified.
The Tooltip-Text is not automatically generated and must be entered manually.
In Property Styles the appearance of the block icon or the faceplate can be modi
fied. The
possible settings you will find in the description of the object types below.
In Property Links the symbol is connected to a number variables of each object.
The
connection is carried out automatically during automatic generation of block ico
ns.
In Property User Text (for groups, routes and selections) a text can be defined
which will
be displayed in the symbol instead of the Tagname.
!
Note: The screenshot shows the properties in template picture
C_@PCS7Typicals_CemV7.pdl. For the manual connection the attribute 'type' has to
be
replaced by 'C_DRV_1D'.
Property General of object type C_DRV_1D: Type: @C_DRV_1D/500 for Subcontrols
Copyright Siemens AG. All Rights Reserved. 8 - 7
Subcontrol Button
The first three new attributes are protected against overwriting with the functi
on
@PCS7Typicals.cfg.
To get the Group Display and the Loop in Alarm function you have to add a WinCC
Group
Display. Set the display to NO.
Group value = Connect to variable 'EventState' of the Subcontrol block.
The invisible Group Display you can move behind the block icon of the drive.
8 - 10 Copyright Siemens AG. All Rights Reserved.
The display of the tagname can be switched on/off in the Runtime system, using t
he internal
variable C_VIEW_TAG_D. To enable this, the attribute View_Tag of Property Styles
has to
be linked to the variable C_VIEW_TAG_D:
Copyright Siemens AG. All Rights Reserved. 8 - 11
Button Text
Via two additional IO-Fields BText1 and BText2 in the Customized Objects for C_D
RV_2D,
C_DAMPER and C_VALVE, the Button text of the faceplate can be modified.
An example for this can be found in the following symbols of the template pictur
es:
For the additional function Button text it is required to open the faceplate via
function
PCS7_OpenGroupDisplay_V6_CEMAT :
8 - 12 Copyright Siemens AG. All Rights Reserved.
!
Note: The screenshot shows the properties in template picture
C_@PCS7Typicals_CemV7.pdl. For the manual connection the attribute 'type' has to
be
replaced by 'C_ANNUNC'.
8 - 14 Copyright Siemens AG. All Rights Reserved.
!
Note: The screenshot shows the properties in template picture
C_@PCS7Typicals_CemV7.pdl. For the manual connection the attribute 'type' has to
be
replaced by 'C_GROUP'.
8 - 18 Copyright Siemens AG. All Rights Reserved.
Start_Stop_Automatic_Local_Single (default)
Buttons_Invisible
Start_Stop_Automatic_Local_Single_QuickStop
Start_Stop
Start_Stop_Automatic_Local
Start_Stop_Automatic_Single
Start_Stop_Automatic_Local_QuickStop
Start_Stop_Automatic_Single_QuickStop
Start_Stop_Automatic_QuickStop (only for Project Standard 006 Dyckerhoff)
Select_Deselect (default)
Buttons_Invisible
Select_Deselect (default)
Buttons_Invisible
OS Engineering
Engineering Cemat V7
Property Links
For each group in Property Links all Attributes must be connected as follows to
the variables
of the corresponding object. (They will be connected automatically in case of au
tomatic
generation of Block Icons):
CollectValue to .EventState
for Group Display in the overview Range
(the group display is normally not shown at the
object itself)
G_Operation to .STA2_OS to show the Operation status (Auto/Single/Local)
G_Status to .STATUS to show the Group Status (Stopped, running, .....)
G_Fault to .STATUS to show the Fault Status
G_Interlock to .STA2_OS to show the Interlock Status
Property Links of C_GROUP:
8 - 20
Copyright Siemens AG. All Rights Reserved.
!
Note: The screenshot shows the properties in template picture
C_@PCS7Typicals_CemV7.pdl. For the manual connection the attribute 'type' has to
be
replaced by 'C_MEASUR'.
Copyright Siemens AG. All Rights Reserved. 8 - 23
Engineering Cemat V7
OS Engineering
Including a Measured Value into a Process Value Archive
The faceplate of the measuring value shows the trend curve. If an archive curve
is available
for the measure, via button Curve the Archive Curve can be called.
In the Engineering for the Process Value Archive, certain rules have to be follo
wed, in order to
enable the call-up of the Archive curve.
1.
The archive tag name must be derived from the tag name of the measure. This impl
ies
the following:
a) The object tag of the measure must not contain any special character, because
the in
the archive tag name, special characters are not allowed and will be removed by
the
system.
b) The archive tag name, automatically given by the System must not be modified.
2.
The name of the process value archive must be ProcessValueArchive. This means th
at
all process values, which shall be shown in the Measuring Value Faceplate, are l
ocated in
the same Archive.
Restrictions for the Archive names up to CEMAT V6 SP2:
The name of the process value archive must be ProcessValueArchive. This means th
at
all process values, which shall be shown in the Measuring Value Faceplate, are l
ocated in
the same Archive.
Restrictions for the Archive names from CEMAT V6 SP3:
From SP3 it is possible to use different process value archives with any name (w
ithout
special characters) by entering an Archive name in the symbol properties of the
measure
symbol (under Styles, Attribute ReturnPath ).
Exception: For motor currents which are displayed via Analog button in the facepla
te of
the corresponding motor, the archive must be located in ProcessValueArchive.
If Attribute Return Path
arched
in this Archive.
RawMill
8 - 25
!
Note: The screenshot shows the properties in template picture
C_@PCS7Typicals_CemV7.pdl. For the manual connection the attribute 'type' has to
be
replaced by 'C_COUNT'.
Copyright Siemens AG. All Rights Reserved. 8 - 27
Engineering Cemat V7
OS Engineering
Window Position of the Faceplates in V7
Equal to CEMAT V6.1 the Positioning of the Faceplates in CEMAT V7 is carried out
through
Property Miscellaneous via the Attributes topPos, leftPos and defaultPos. Using
this method,
the positions don't get overwritten in case of the repetition of the generation
of block icons.
For the Positioning you have the following possibilities:
a) The Faceplate appears at the Curser-Position for
TopPos = 0
leftPos = 0
DefaultPos = no
b) The Faceplate appears at the set Position for
TopPos = Wert > 0
leftPos = Wert > 0
DefaultPos = no
c) The Faceplate appears at the Default Position
TopPos = irrelevant
leftPos = irrelevant
DefaultPos = yes
Window Position of the Faceplates (CEMAT V6.0 Method)
The new positioning function requires the new block icons (the block icons of CE
MAT V6.0
did not have the attributes topPos, leftPos and defaultPos).
In case of an existing plant you may not want to generate the block icons again,
using the
new templates. In this case the CEMAT V6.0 Method for the positioning or the Fac
eplates can
be used.
Also in CEMAT V6.0 from SP2 there was the possibility to define the window posit
ion for the
Faceplates. To enable this, for opening faceplate the function
PCS7_OpenGroupDisplay_V6_CEMAT must be used.
The window position is entered via parameter iX and iY. The following parameteri
sations are
possible:
-1, -1
Faceplate will not be positioned (default)
with this setting the attributes topPos, leftPos und defaultPos are evaluated!
<-1, <-1
(wrong entry) Faceplate will be positioned at 0,0
0, 0
Faceplate will be displayed at the upper left corner of the actual mouse positio
n
>0, >0
If x or x are bigger than 0, the faceplate will be displayed at this coordinates
.
Example:
PCS7_OpenGroupDisplay_V6_CEMAT(lpszPictureName, lpszObjectName, -1,-1);
The symbols delivered with the template pictures of CEMAT V6.0 SP2 already conta
in the
new faceplate calls.
The new function PCS7_OpenGroupDisplay_V6_CEMAT replaces the function
PCS7_OpenGroupDisplay_V6 as well as function PCS7_OpenGroupDisplay_V6_Ew.
Copyright Siemens AG. All Rights Reserved.
8 - 35
Engineering Cemat V7
OS Engineering
Instance specific Authorizations
The Authorizations are defined in the User Administrator of WinCC. Beside the au
thorizations
of WinCC during the generation of the project additional authorizations have bee
n defined for
CEMAT (see chapter 3). There, you also find a list which explains which authoriz
ation is
needed for which operation.
Defining different user groups and users you can enable or disable specific func
tions. This is
possible per OS-Area.
In addition for some Operations it is possible to define instance specific right
s. The settings
have to be carried out at the block icon under Miscellaneous. The two attributes
Processcontrolling_backup and HigherProcesscontrolling_backup are variables which ar
e
used in order to transmit free definable authorizations to the faceplate.
In the table in chapter 3 you can see for which operations instance specific rig
hts are
possible.
Extraction of the table of authorizations from chapter 3 (example for C_DRV_1D):
Object type Operation Right/ default right Instance specific settings
possible via Attribute
Project
Code
C_DRV_1D Start/Stop 05: Process controlling Processcontrolling_backup all
Process parameter 22: Object Parameters all
Reset Operation 23: System Operations all
Bypass speed monitor 24: Interlocking Signals HigherProcesscontrolling_backup al
l
Maintenance functions 29: Maintenance all
auto/man. Interl./man.
non Interl.
05: Process controlling Processcontrolling_backup 006
non interl. single mode
Rel.
23: System Operations 007
non interl. single mode
on/off
24: Interlocking Signals HigherProcesscontrolling_backup 004/007
The first 5 operation functions in the list are possible for all project version
s:
1.
The Operations Start and Stop are assigned to authorization 5 Process controlling .
In
this case it is not fix assignment, the authorization is transmitted via variabl
e
Processcontrolling_backup.
2.
The Operations for the modification of the Process parameters is assigned fix to
authorization 22 "Object parameters .
3.
The Rest Operation has a fix assignment to 23 "System Operations .
4.
The Operation Bypass Speed Monitor is assigned to authorization 24 "Interlocking
Signals . In this case it is not a fix assignment, the authorization is transmitte
d via variable
HigherProcesscontrolling_backup.
5. The Maintenance functions are assigned to authorization 29 "Maintenance".
Some Operations are only available in Project Versions.
6.
In Project Version "006" the Operation auto/manual Interlocked/manual non
Interlocked is assigned to authorization 5 "Process controlling . The assignment i
s
carries out via variable Processcontrolling_backup.
!
Please keep in mind that the operations Start and Stop and the Operations for au
to/manual
Interlocked/manual non Interlocked are always linked to the same right.
Copyright Siemens AG. All Rights Reserved.
8 - 37
!
Caution: Do not use the SIMATIC Manager function Archive . PCS 7 automatically
creates the required archive tags when the Compile OS function executes, assuming
you have set this option but it creates an archive with standard name SystemArchi
ve .
8 - 38 Copyright Siemens AG. All Rights Reserved.
Engineering Cemat V7
OS Engineering
User Archives
During the installation of the Project (chapter 3) two user archives have been c
reated.
Through the import of the files DriveList.uap and C_INFO.uap the data base struc
ture was
already created in the correct format.
The group instance list C_DriveList does not need any further engineering. The d
ata will be
provided online.
The User Archive C_INFO is empty and must be filled with data, in order to provi
de it for the
Info Dialog of the Objects.
We recommend to create the Info-Data with Excel (CSV-File) and to import it afte
rwards into
the user archive. An example for the CSV-File you find in directory D:\Cemat_CS\
ua. File
C_INFO.csv contains one line with example data (only headers).
Structure of the Info data base
The structure of the Info data base is already explained in chapter 2. Subsequen
tly you find
some additional remarks regarding the particular data fields.:
The content of fields ID, Obj_ID and C_TAG must be unique. ID and Obj_ID contain
a
consecutive number and C_TAG contains the tagname of the object.
The rest of the fields are grouped by subject under which you will find the info
rmation later
on in the Information Dialog. You can identify the subject on it s prefix.
GL_ = General Locations
G_ = Register Service
I_ = Register Input/Output
M_ = Register MCC Data
H_ = AS Hardware / Software
The fields LastUser and LastAccess can remain empty. They are used by the system
itself.
The entry in field G_LoopA serves as a reference to the process picture to be op
ened if
the loop-in-Alarm Button is pressed.
If this field remains empty, the system looks into the 'Component list Editor' o
f WinCC in
order to open the 'Entry point picture'.
By entering the file name for manuals and video files, these documents can be op
ened
from the Info-Dialog by additional buttons.
Important notes for the import:
1.
ID and Obj_ID must be numbered consecutively.
2.
Via Import function only new records can be imported, i. e. if you want to modif
y existing
data records you have to export these records, and to delete it before you can i
mport it
again.
Copyright Siemens AG. All Rights Reserved.
8 - 39
Engineering Cemat V7
OS Engineering
4.
Select the file C_INFO.CSV, which was created by the Excel macro. Select the Arc
hive
C_INFO . If there are already runtime data in the archive, this data records must b
e
deleted before the import. If you like to keep some data from the already existi
ng records,
please export the runtime data and copy them into the import file C_INFO.CSV.
If you import data records with an already existing ID, you will get an error me
ssage. The
import will be then aborted.
Copyright Siemens AG. All Rights Reserved.
8 - 41
!
Note: The Map Name and the Manual are case sensitive!
8 - 44 Copyright Siemens AG. All Rights Reserved.
Engineering Tools
Engineering Cemat V7
User Archive C_INFO
With CEMAT V7 an Excel Macro is available, which can be used to create the Info
Data from
the PCS7 Engineering Data (Hardware Configuration, Process Object view). The Exc
el Macro
generates a file C_INFO.csv, which can be imported into the User Archive.
The procedure how to generate the Info-Data is described in the following chapte
r.
Generation of the user archive C_INFO
This chapter describes the generation of the user archives C_INFO from the data
of the PCS7
Project. For this purpose necessary excel file C_INFO_V70.xls are available in t
he directory
D:\CEMAT_CS\ua.
For the generation of the User Archive C_INFO from the process object view and t
he
hardware configuration of the PLCs the following requirements must be met:
The hardware configuration of each PLC must be exported as CFG files.
The symbol tables of each PLC must be exported as SDF files.
The content of the process objects views General and Picture objects must be copied
into text files.
-The I/Os of the process objects view must be exported into text files.
The following columns are filled during this procedure:
ID -> will be numbered continuously.
C_TAG = TAG
GL_Complex = Complex = Manual input = identically for all objects.
GL_Plant = Project = Manual input = identically for all objects.
GL_Plant_zone = Plant zone = 1. Hierarchy folder.
G_LoopA = Process mimic = from process object view picture objects .
H_PLC_Name = PLC = from process object view General or hardware configuration.
9 - 2
Copyright Siemens AG. All Rights Reserved.
Engineering Cemat V7
Engineering Tools
Export from the process object view
Process object view General
Copy the process object view General
1.
Select process object view.
2.
Select the topmost hierarchy folder
(from the project with the PLCs, not the multi project folder).
3.
Refresh the view (F5).
4.
Select in all lines all fields, except the line numbers.
5.
Copy with CTRL-C all lines into the clipboard.
6.
Start the text editor (notepad) and insert all lines with CTRL-V.
7.
Save the text file, e.g. as GENERAL PO.txt.
If the AS devices are stored in different single projects of a multi project, th
en you have to
select each single project and copy the General view of each single project into f
iles, e. g.
GENERAL PO.txt. The specific file names must be entered in the sheet Presettings o
f the
Excel tool.
Copyright Siemens AG. All Rights Reserved.
9 - 5
Engineering Tools
Engineering Cemat V7
Process object view Picture objects
Copy the process object view picture objects
t.
1.
Select process object view Picture objects .
2.
Select the topmost hierarchy folder
(from the project with the PLCs, not the multi project folder).
3.
Refresh the view (F5).
4.
Select all lines.
5.
Copy with CTRL-C all lines into the clipboard.
6.
Start the text editor (notepad) and insert all lines with CTRL-V.
7.
Save the text file, e.g. as PO picture.txt.
If the AS devices are stored in different single projects of a multi project, th
en you have to
select each single project and copy the process object view Picture objects of eac
h single
project into files, e. g. PO_picture.txt. The specific file names must be entere
d in the sheet
Presettings of the Excel tool.
9 - 6
Copyright Siemens AG. All Rights Reserved.
Engineering Cemat V7
Engineering Tools
Update the interface definition (parameter or signal) in the process object view
.
Some interfaces of the blocks in the Cemat library are defined as parameter or a
s signal. If
the AS program is updated from an older Cemat version (e. g. V5.x, V6.0), it cou
ld be, that a
interface of a block in a CFC chart is not defined as signal, even though in the
actual block
the interface is defined as signal. E. g. the interface ESB or K (Holcim) of the
actual block
C_DRV_1D is defined as signal. In an updated CFC chart of a particular motor it
could be,
that the interface ESB / K (Holcim) is not defined as signal. In this case the i
nterface ESB / K
(Holcim) would not be listed in the process object view Parameter / Signals. So t
hat the
process objects view works with the actual definitions of the block interfaces t
he following
procedure is recommended:
1.
Select process object view Parameters.
2.
Select the topmost hierarchy folder
(from the project with the PLCs, not the multi project folder).
3.
Refresh the view (F5).
4.
Select with the right mouse button the menu Process objects -> Select I/Os .
Select All and acknowledge with OK .
Copyright Siemens AG. All Rights Reserved.
9 - 7
Default .
With the button Default all I/O definitions ( Parameter or Signal ) from the blocks are
transferred into the block calls in the CFC charts and all I/Os with Parameter or S
ignal
definition are listed now in the process object view. Before the definitions are
transferred a
hint box appears. See above. The changed I/O definitions are shown with tick mar
ks on a
yellow back ground. With OK you return to the normal process object view Parameter o
r
Signal .
9 - 8 Copyright Siemens AG. All Rights Reserved.
Engineering Cemat V7
Engineering Tools
5.
If you use the channel driver block CH_DO , you should do the following definition
change. In this case the output periphery for Cemat drives will be found. Select
with the
right mouse button the menu Process objects -> Select I/Os .
Set as filter Blocktype = CH_AO and Connection = I .
Copyright Siemens AG. All Rights Reserved.
9 - 9
Result: The tick mark in the column Parameter is now set for all connections I for a
ll block
types CH_DO . Now the connection I is listed in the process object view and the assoc
iated
Cemat-object could be found.
9 - 10 Copyright Siemens AG. All Rights Reserved.
Engineering Cemat V7
Engineering Tools
Process objects view Export I/Os
Export the block I/Os into a text file, e.g. into LS01_PS.csv.
1.
Select process object view Parameters.
2.
Select the topmost hierarchy folder
(from the project with the PLCs, not the multi project folder).
3.
Refresh the view (F5).
4.
Select with the right mouse button the menu Process objects -> Export I/Os .
5.
Save the export file, e.g. as LS01_PS.csv.
If the AS devices are stored in different single projects of a multi project, th
en you have to
select each single project and the process object view Parameter of each single pr
oject
must be stored in a separate file. The specific file names must be entered in th
e sheet
Presettings of the Excel tool.
Copyright Siemens AG. All Rights Reserved.
9 - 11
picture o
for E
Engineering Cemat V7
Engineering Tools
If all necessary files are present, you can start the Excel macro CINFO .
Wait until "Ready" appears again in the status bar of Excel.
For a complete line the macro could run very long., maybe up to one hour runtime
.
Check:
The file C_INFO.CSV should be created by the macro. Attention: An existing file
C_INFO.CSV will be overwritten without a query. Import this file as runtime data
with
the user archive editor from WinCC. A detailed description of the Runtime data i
mport
you will find in chapter 08_OS_Engineering.
For every tag there should be created a text file in the subdirectory Periphery .
These text files contain the I/O information of the tag. Also this files will be
overwritten
without a query.
Copy these files to D:\CEMAT_CS\MULTIMEDIA\Periphery\. In this case, the I/O
information will be shown in the object faceplate Info -> I/O Info .
Copyright Siemens AG. All Rights Reserved.
9 - 13
file
file
file
file
V6
V6
V7
V7
Copy all runtime data files into the same directory like the Excel file C_INFO_V
70.xls.
Run the macro "READ_UA_V7" -> A sheet "UA" will be created (a existing sheet "UA
" will be
deleted). As import file the file name from "B15" = "Import file V7 for edit" wi
ll be used. Wait
until "Ready" appears again in the status bar of Excel.
The user archive "C_INFO" could now be edited in the sheet "UA".
Run the macro "SAVE_UA_V7" -> The sheet "UA" will be saved into the file listed
in "B16" =
"Export file V7 for edit". Wait until "Ready" appears again in the status bar of
Excel.
If the file already exists, the file will be overwritten without a query.
With this tool you can also convert or edit the user archive "C_INFO" with the v
ersion 6
structure. For editing use the macros "READ_UA_V6" and "SAVE_UA_V6". For convert
ing to
the V7 structure use the macros "READ_UA_V6" and "SAVE_UA_V7".
9 - 14 Copyright Siemens AG. All Rights Reserved.
Engineering Cemat V7
Tips&Tricks
Replace standard PCS7 INTERLOCK by CEMAT INTERLOCK
The Interlock block from the PCS7 standard library needs 33 OS variables. The nu
mber of
OS variables are reduced to 11 variables, if the CEMAT Interlock block is used.
If the
Interlock block from the PCS7 standard library is used and this block should be
replaced by
the CEMAT Interlock and all existing CFC connections should remain, then follow
the listed
sequence. Attention! In this case the PLC must be completely reloaded:
1.
Delete FB 75 = INTERLOK from the PCS7 standard library from the block container.
Don not delete the entry in the symbol list FB75 = INTERLOK.
2.
Copy FB1075 = C_INTERL as FB75 (symbol = INTERLOK).
3.
Copy @PG_C_INTERL.PDL as @PG_INTERLOK.PDL.
Copy @PG_C_INTERL.PDL_OVERVIEW as @PG_INTERLOK_OVERVIEW.PDL.
Copy @PG_C_INTERL.PDL_VIEWLIST as @PG_INTERLOK_VIEWLIST.PDL.
Copy @PG_C_INTERL.PDL_STANDARD as @PG_INTERLOK_ STANDARD.PDL.
4.
Change the properties of the objects in the copied file @PG_INTERLOK.PDL as
follows.
Object @Faceplate -> Texts -> Firstview = @PG_INTERLOK_ STANDARD.PDL.
Object BlockType -> Output/Input -> Output Value = INTERLOK.
Object Viewlist -> Miscellaneous -> Picture Name =
@PG_INTERLOK_VIEWLIST.PDL.
5.
Invert all inverting bits for all connected inputs in the CFC.
Please check the logic!!!!!
Copyright Siemens AG. All Rights Reserved. 14 - 5
Edition: 30.09..2005
N:\Cemat\DOKU\V70\English\Engineering\14_Tips_Tricks_009.doc
Update Information
Engineering Cemat V7
Update CEMAT V6.1 to CEMAT V7.0
You have a CEMAT V6.1 project (based on PCS7 V6.1) and want to upgrade to CEMAT
V7.0
(based on PCS7 V7 SP1). The following description explains the necessary steps.
Requirements
Before the installation of Cemat V7.0 you have to upgrade your PC to Win XP / Se
rver 2003
with PCS7 V7 SP1. The installation of the operating system and PCS7 is explained
in the
PCS7 manuals and in the readme and therefore not part of this description.
!
Caution: The update to CEMAT V7 requires a complete reloading of the PLC and
consequently cannot be carried out while the plant is running.
Follow the Manual "PCS7 Software Update with utilization of the new functions" f
rom the
PCS7 V7 Documentation, especially chapter 7.2 "General Adaptations". The followi
ng
description refers to this manual.
Please also pay attention to the hints for the OS-Migration in chapter 7.2.2. Th
e Server
Projects have to be migrated on the Server-PCs directly in order to maintain the
runtime data
(curves and messages).
Install CEMAT V7 before you upgrade you project. If you have OS projects with mi
grated S5
PLCs (CEMAT V2, V3, V4), you have to install all parts for the S5 migration on y
our PC and
register all necessary OCX controls before you start the update to CEMAT V7. If
you convert
PDL files to PCS7 V7 and the PDL files contain OCX controls which are not regist
ered, then
the PDL files are destroyed! Save all your standard PDLs for the S5 migration an
d all process
mimics with S5 connections.
Consider also the project rules from the CEMAT V6.1 SP2 manual
PCS7
Project = 03_PCS7_Project_009.pdf
Installation of a
Save Modifications
Save your project data. Beside the MultiProject this comprises all settings whic
h you have
carried out in the CEM_V6 Directory, as well as modifications in the block libra
ry ILS_CEM or
PRO_CEM.
-
Update Information
Engineering Cemat V7
Installation of CEMAT V7.0
Start the Setup program from the CD CEMAT V7.0 and follow the instructions.
The Installation path is 'D:\CEMAT_CS'. This can not be changed!
Keys for project standards 000 = CEMAT
004 = Holcim
006 = Dyckerhoff
007 = Heidelberger Zement
023 = Vigier
024 = Bushehr
025 = Caima
026 = Alsen
027 = Lafarge
028 = Rossi
After the installation, for all PC stations (ES, OS SERVER and OS CLIENT) the fo
llowing
steps have to be carried out:
1.
During the installation of PCS7 V7 SP1 the Siemens directory has been updated.
For this reason copy all files under d:\CEMAT_CS\WinCC\Siemens to c:\....\Siemen
s.
2.
The config files contain the default settings, which means if you changed them f
or your
project you have to make this adaptations again.
3.
Probably you also added for your project some files under 'Multimedia' or 'Sound
s'. After
the CEMAT installation these files can be can be restored from the backup direct
ories
and copied into the new CEMAT directories.
4.
If you use the S5 CEMAT migration, then you have to install the CEMAT S5 OS part
(OCX files, PDLs, scripts, CFG files) before you migrate your PCS7 Project. Othe
rwise
the standard S5 PDLs (@PG_C_S5??????.PDL) will be wrong converted and can not be
used any more.
- Copy from the old CEM_V6 directory all OCX files (must be unregistered before!
), CFG
files and all files under GraCS.
- The scripts (files under Library) must not be copied from the old CEM_V6 direc
tory.
Instead of this, copy from the CEMAT V7 CD under
Alarmline_MessageSelection_V60\WinCC\Library the complete directory
Cemat_V60MessageSelection to D:\CEMAT_CS\WinCC\Library.
- The OCX files must be registered, using the BAT file. Refer to the S5 migratio
n manual.
Please, if exists, delete the file "pcs7_opengroupdisplay_v6_EwS5.fct from
C:\.....\Siemens\WinCC\aplib\FaceplateDesignerV6.
5.
If you want to use the PTE-Controller Function, then you have to install the PTE
Controller OS part (OCX files, PDLs, scripts, CFG files) before you migrate your
PCS7
Project. Otherwise the standard PDLs (@PG_C_??????.PDL) will be wrong converted
and can not be used any more.
Copy all necessary files for the PTE-Controller function to D:\CEMAT_CS\ into th
e
corresponding directories. Register the OCX files using the BAT file. Refer to t
he PTEController instructions.
15 - 4
Copyright Siemens AG. All Rights Reserved.
Engineering Cemat V7
Update Information
Update of S7 Program
Please refer to the chapter 7 of the manual "PCS 7 - Software Update with utiliz
ation of the
new functions .
New CEMAT Libraries
With the installation of CEMAT V7.0 a new Version of the CMEAT Library ILS_CEM h
as been
installed in directory C:\....\Siemens\Step7\S7libs.
This library contains the current CEMAT symbol list, blocks and the system chart
.
In case of a project standard (project key other than 000 ) the library PRO_CEM is
also
transferred into C:\...\Siemens\Step7\S7libs directory. This library contains al
l blocks which
differ from the normal CEMAT standard.
The blocks of the CEMAT libraries must be used completely. The system chart has
not
modification since CEMAT V6.1.
New PCS7 Libraries
With the installation of PCS7 V7 also some new block libraries were installed. W
e recommend
you to update in your project all blocks from the PCS7 libraries with the new bl
ocks. Please
consider that especially for the driver blocks you can not use blocks from diffe
rent versions.
For the update of your S7-Programs please carry out the following steps:
Symbol list
Open the CEMAT Library ILS_CEM in the SIMATIC Manager and export the symbols fro
m
the CEM_ALL S7 program.
After that open in your project the symbol list of the project library and impor
t the actual
standard symbols. Analyze the error list of the import editor and correct any er
rors (e.g. nonunique symbols).
Repeat this step for the Symbol lists of each AS.
Blocks
Actualize the project library first:
1.
Copy all blocks from the S7 program of the CEMAT ILS_CEM library into the block
folder
of your project library and each PLC (overwrite = yes).
In case of a project standard copy after that also all blocks from PRO_CEM libra
ry into
the block folder of your project library and each PLC (overwrite = yes).
2.
Delete block FB128 (including the symbol). It is not needed any more and the sam
e FBNumber is used by driver block of PCS7 V7.
3.
The project library must not contain blocks with Author ES_MAP. If you find thos
e blocks
you have to delete them.
4.
Double-check if there are other blocks in your block folder which have to be upd
ated as
well.
These are e. g. the blocks with Author BAISIS61, TECHN61, DRIVER61. Upgrade thes
e
blocks to the current version by copying the blocks from the new PCS7 libraries.
Copyright Siemens AG. All Rights Reserved.
15 - 5
Update Information
Engineering Cemat V7
5.
If the system attributes or the message configuration has been changed in the st
andard
blocks for your project, these modifications have to be carried out in the block
folder after
the upgrade again.
6.
Open the CFC editor by opening any chart.
7.
You must now use Options -> Block Types to update all blocks of the chart folder
with
"New Version".
After actualizing the project library (master library) you have to upgrade your
AS:
1.
Copy all blocks from the project library into the program folder of your AS (ove
rwrite =
yes). After this all CEMAT blocks should be actualized.
2.
Delete also in each AS the block FB128 (including the symbol) in order to avoid
collision
with the driver block from PCS7 V7
3.
If your project library is maintained well there should be no additional "old" b
locks in the
block folders of the AS. Check the block list, if all PCS7 blocks with family co
de BASISxx,
TECHNxx and DRIVERxx have the actual version.
4.
Open the CFC editor by opening any chart.
5.
In order to update the chart folder use Options -> Block Types, select all block
s in the
chart folder (right window) and press "New Version".
6.
Compile the CFC
7.
After the actualization of the blocks a complete download to the AS is required.
15 - 6
Copyright Siemens AG. All Rights Reserved.
Engineering Cemat V7
Update Information
Update of the OS-Projects
OS-Migration
Again refer to the OS-Migration in the Manual "PCS 7 - Software Update with util
ization of
the new functions".
You have to migrate all OS Projects in your MultiProject. This is carried out un
der::
Start .. SIMATIC .. WinCC .. Tools .. Project Migrator.
CEMAT Update
After the CEMAT installation, the D:\CEMAT_CS\WinCC directory contains the curre
nt
version of the global scripts and the system pictures. These must be transferred
to the WinCC
project.
We assume that in your project the picture tree was derived from the plant view
and that the
standard message selection of PCS7 is used, which is also used since V6.1 of CEM
AT.
If your picture tree was nevertheless generated manually you have to use the mes
sage
selection of CEMAT V6.0.
In this case we refer to the additional documentation "Message selection window
of CEMAT
V6.0"
In all WinCC Projects carry out the following steps:
1.
Open the WinCC Explorer.
2.
Open the OS Project Editor. Check the settings according to the Engineering Manu
al
Chapter 3 "Installation of a PCS7 Project".
Close the OS Project Editor with "OK". All standard pictures (Overview, buttons,
alarm
line, etc.) are replaced by the new standard PDLs of PCS7 V7 SP1.
3.
Close WinCC Explorer.
4.
Delete all CEMAT standard scripts in your PCS7 project '<OS>\Library'. Keep your
own
scripts in PCS7 project '<OS>\Library'.
Copy all global scripts from 'D:\CEMAT_CS\WinCC\Library' into PCS7 project
'<OS>\Library' (incl. subdirectories).
5.
Delete the VBS Action 'Cem_Tags.bac' from the PCS7-Project '<OS>\ScriptAct'.
It is no longer required.
6.
The CEMAT standard global scripts in PCS7 project '<OS>\Pas are not longer used
and
can be deleted.
7.
From directory D:\CEMAT_CS\WinCC\WScripts copy all files into the PCS7 Project
under 'wincproj\<OS>\WScripts'.
8.
From directory 'D:\CEMAT_CS\WinCC\PRT copy file 'C_TrendReport.RPL' into the
PCS7-Project under wincproj\<OS>\PRT.
9.
Copy all files from ''D:\CEMAT_CS\WinCC\GraCS' into the PCS7 project '<OS>\GraCS
'.
10. Delete from the GraCS directory all files with file extension '.sav'.
Copyright Siemens AG. All Rights Reserved.
15 - 7
17. Correct the settings in the alarm logging. During the migration the CEMAT sp
ecific
settings (texts, columns, color definitions, Acknowledge mode) get lost and must
be
configured again. For the correct settings refer to the Engineering Manual, chap
ter 3,
"Installation of a PCS7 Project".
18. Open 'Global Script' and regenerate the header. (Menu/Options/Regenerate Hea
der)
19. If you have modified for your project system PDL s and scripts you have to do
the
modification again in the new system files. Refer to your backup.
20. Open the User Administrator.
Add right 29 (Maintenance).
Right 8 is not used any more and can be removed.
15 - 8 Copyright Siemens AG. All Rights Reserved.
start the
conversion of the die PDL files again. After that the PTE-Controllers are integr
ated correctly.
Copyright Siemens AG. All Rights Reserved. 15 - 9
Update Information
Engineering Cemat V7
Compile and Download
1.
For all PLCs: Compile CFC (complete program).
2.
For all Single Stations and primary Servers: OS Compile (complete OS with memory
reset). In the background the Server data (package) will be automatically create
d and
loaded into the OS Client Project. Please double-check!
3.
Load the complete program into the PLC.
4.
Actualize the Server and OS Clients with Project Download.
15 - 10
Copyright Siemens AG. All Rights Reserved.