Siemens C - Annunc Manual
Siemens C - Annunc Manual
Operating principle 2
Time characteristics 3
PCS 7
Message characteristics 4
CEMAT
Annunciation Module C_ANNUNC 5
Module states
Operator Commands 6
Function Manual
Feature Bits 7
OS Permissions 8
I/O-bar of C_ANNUNC 9
OS-Variable table 10
Variable details 11
07/2016
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
1 Function........................................................................................................................................................5
1.1 General Function description...................................................................................................6
1.2 Change of operation mode.....................................................................................................10
1.3 Configuration state.................................................................................................................11
1.4 Optional features....................................................................................................................12
1.5 Sequence Test.......................................................................................................................13
1.6 Visualization...........................................................................................................................14
2 Operating principle.....................................................................................................................................15
2.1 Input interfaces.......................................................................................................................15
2.1.1 Interfaces for mode change...................................................................................................18
2.1.2 Inputs for testing and as Interface to the OS..........................................................................23
2.1.3 Maintenance...........................................................................................................................24
2.1.4 Process Parameters...............................................................................................................25
2.1.5 Process parameters for Maintenance function:......................................................................27
2.1.6 OS Permissions and Features:..............................................................................................28
2.1.7 Connection to EventTs...........................................................................................................31
2.2 Group and Object links...........................................................................................................32
2.2.1 Example of a circuit:...............................................................................................................35
2.2.2 Object links to master objects................................................................................................36
2.2.3 Object links to a group in a different AS.................................................................................37
2.3 Input/Output interfaces...........................................................................................................40
2.4 Output interfaces....................................................................................................................42
2.4.1 Outputs for testing and as Interface to the OS.......................................................................42
2.4.2 Output status for connection to other blocks..........................................................................44
2.5 Engineering Errors.................................................................................................................48
3 Time characteristics....................................................................................................................................49
4 Message characteristics.............................................................................................................................51
5 Module states.............................................................................................................................................53
6 Operator Commands..................................................................................................................................55
7 Feature Bits................................................................................................................................................57
8 OS Permissions..........................................................................................................................................59
9 I/O-bar of C_ANNUNC................................................................................................................................61
10 OS-Variable table.......................................................................................................................................67
11 Variable details...........................................................................................................................................69
11.1 Variable details COMMAND...................................................................................................69
Calling OBs
All CEMAT Functions must be installed in the same OB, which is preferable OB1. The System
Chart SYSPLCxx contains infrastructure blocks which must be called at the Beginning
(Runtime group OB1_START) and at the End (Runtime group OB1_END) of this OB.
The application program must be called between OB1_START and OB1_END.
Calling of the CEMAT blocks in a cyclic interrupt OB (OB34 or OB35) is possible, but only if
the complete program is called in the same cyclic interrupt OB. In this case the infrastructure
blocks must as well be moved to the cyclic interrupt OB (see Engineering Manual chapter
Tips&Tricks)
Note
Block functions are only active in automatic mode.
If the block is switched to Out of Service, operation of the annunciation block is inhibited, the
outputs are set to "0", all messages are suppressed and only the status words are updated.
Memorized functions like Simulation, etc. are reset.
Note
Exception
In case of warnings only the output Warn is set because warnings should not influence the
process.
All further functions are optional and can be defined through corresponding parameterization
of the Feature bits and block parameters.
Signal evaluation:
The display and alarm behavior of the block can be configured through parameterization. Some
functions need to be enabled or can be modified via Feature bit settings:
● In case of an incoming fault, resetting of output OutSig can be delayed via parameter
OutOnDTi.
● In case of an outgoing fault, setting of output OutSig can be delayed via parameter
OutOfDTi.
● In order to achieve for the protections signals of a drive the same message behavior as for
the faults which are annunciated by the drive itself, the alarms can be triggered via interface
MsgTrigg or via O_LINK connection (if the corresponding Feature bit is set).
● With interface DynFltEn alarms and dynamic faults can be suppressed in general. (In case
of a fault the block shows only static indications).
This behavior can be desired during the start-up or for non running equipment.
● The enable messages interface MsgEn can be used in order to prevent an onrush of
messages in case of power failure. The message generation in the block is frozen and
neither incoming nor outgoing messages are created.
● Via interface GrFltLck the block can be deselected for the summarizing indication in group
and route. In the status call the fault and warnings can still be seen.
● Via interface GrStaLck the block can also be deselected form the summarizing indication
in group and route. In this case the block faults and warnings are not entered in the status
call.
● Important messages can be repeated. This is done through configuration of an annunciation
repeat time RepTi.
● Via configuration of the delay time WarnDelTi in case of a fault the block generates first
a warning message and then an alarm message (after the time has elapsed).
Two-level-alarms can be enabled via interface ActWarn or via O_LINK, depending on the
Feature bit setting.
● Via parameter MemTrip it can be decided to memorize the fault until the acknowledgement.
● Via Feature bit settings, the block can be configured to create a warning message instead
of a fault message. In this case the two-level-alarm function is disabled.
Via interface "Supervision enable" SupOn or via O_LINK connection (depending on the Feature
bit setting) the complete supervision can be enabled or disabled. If the supervision is disabled,
the fault bit is reset.
The enable can be delayed via timer SupOnTi, e. g. suppress faults in the start-up phase of
a motor.
If the block is switched to simulation, instead of the input value the simulation value is displayed
and transferred to the output OutSig. Parameter InSig still shows the input value.
The simulation value ("1" or "0") can be configured via Feature bit settings.
The change to simulation is carried out via diagnosis window or automatically if the AS is
switched to sequence test mode.
OS_Perm.bit15 must be TRUE to enable switching to simulation via OS.
Process parameters
Through process parameters the following values can be configured online:
● SupOnTi (s) Supervision delay time for the evaluation of the process signal
● OutOnDTi (s) OutSig On delay time (after InSig (or InSigB) changes from
"1" to "0")
● OutOfDTi (s) OutSig Off delay time (after InSig (or InSigB) changes from
"0" to "1")
● WaDelTi (s) Warning delay (Delay between warning and fault message)
● RepTi (s) Annunciation repeat time (for re-trigger of the message after a
certain time)
Message Classes:
● Alarm
By default setting the annunciation block creates (red) fault messages (Alarm High).
● Two-level-alarm (Warning before Alarm)
This option exists only for drive faults and only in case the motor is already running. If al
fault occurs a warning is created first and only if the fault stays longer than a specified time
it leads to a fault message + switch off of the drive (e. g. in case of drift switches).
If the fault exists at the moment of drive start, no warning message is created and the fault
message is created immediately.
● Warning
If the warn mode is active, the annunciation block will always create warning messages. In
warn mode no two-level-alarming is possible.
If Feature.bit26 = TRUE the operation mode of the annunciation block is included in the
summarizing indication of the group block icon.
Note
For a running plant this means that for any modification of Feature bits or OS Permissions the
module must be set to Out of Service mode.
Note
If the annunciation block is linked to a drive block, the Fault reset function must be enabled for
the drive and for the C_ANNUNC block.
1.6 Visualization
In the block icon of the annunciation block the most important operation status are displayed
(signal status, fault, warning). Refer to Variable Details. Control functions and detail information
are only available after opening the faceplate.
For status information the following variables exist:
InSig (MST0)
● If Feature.bit29 = FALSE the block will create a fault in case of "not healthy" status
(default setting).
● If Feature.bit29 = TRUE the block will create a warning in case of "not healthy" status.
Note
If the warn mode is active (Feature.bit29 = TRUE), Feature.bit17 and ActWarn are
ignored, no two-level-alarming is possible.
Fault and warning message as well as the output OutSig can be delayed via process
parameter settings.
Note
The CFC does not permit direct connection of Structure inputs to the binary process image,
because of different formats. You must either use block input InSigB instead or insert a PCS 7
driver block Pcs7DiIn or a converter (StruDiOu).
Structure variables:
InSig.Value Value Basic state 1-Signal
Format BOOL
InSigB
Note
Using binary input InSigB instead of structure input InSig, Text 0 and Text 1 must still be
configured at structure input InSig.Value.
ProcSig (MSIG)
ProcSig Process Signal to show the real status Basic state 0-Signal
Format BOOL
Interface ProcSig can be used in order to display the real status of the input value. Additionally
to fault and warning, the block icon shows if the input signal is present. 1-Signal at InSig (or
InSigB) is shown in green color.
Typical Application:
Pressure switches. Connecting the pressure signal to ProcSig changes the display to green
as soon as the oil pressure is available. Missing oil pressure is only evaluated if the supervision
is enabled (e. g. Motor must be running).
SupOn (RELS)
Note
Simulation has the highest priority. If the simulation is enabled for the annunciation block, the
supervision is automatically enabled.
Via feature bit setting, the supervision enable can be transmitted through the O_LINK interface.
With Feature.Bit18 = TRUE the running signal RunSig of the drive is automatically used
for supervision enable for the annunciation block. No connection to SupOn is needed.
AutModOn
OoSModOn
MsgTrigg (MAAT)
Note
In the AS wide acknowledgement, the faults are acknowledged automatically with the
acknowledgement of the alarm in the alarm line. If no alarm is present, fault acknowledgement
is not possible.
Via feature bit setting, the message trigger can be transmitted through the O_LINK interface.
With Feature.Bit16 = TRUE the dynamic fault signal DynFlt of the drive is automatically
used as message trigger for the allocated annunciation block. No connection to MsgTrigg is
needed.
Note
Message trigger does not work properly if the supervision is disabled (either through SupOn
= 0-Signal of through Feature.bit18).
MsgEn (MMFR)
Note
If MsgEn has 0-Signal the annunciation fault is not shown in the summarizing indication of
group and route and not listed in the status call.
DynFltEn (MAMV)
GrFltLck (MMZS)
GrStaLck (GFSO)
GrStaLck 1 = don't incl. in group sum. ind.+status call Basic state 0-Signal
Format BOOL
1-Signal at GrStaLck completely deselects the annunciation block for the Group Summarizing
fault and for the Group Status Call.
The function is similar to interface GrFltLck but the annunciation block is excluded from
status call as well.
LampTest (MLPZ)
Note
Using LampTest the lamp test interface at the C_PUSHBT module must not be connected.
ActWarn (AWAN)
With Feature.bit17 = TRUE the running signal RunSig of the drive is automatically used
to activate the warning (two-level-alarm) for the annunciation block. No connection to
ActWarn is needed.
Note
If the warn mode is active (Feature.bit29 = TRUE), Feature.bit17 and ActWarn are
ignored, no two-level-alarming is possible.
Ack (MQIT)
Note
Using Ack for individual acknowledgement, the acknowledgement interface at the C_PUSHBT
must not be connected.
For group-wise acknowledgement connect the output AckGr of the corresponding group to
interface Ack of the annunciation block. See Engineering Manual, chapter AS-Engineering.
Via Feature bit settings the internal acknowledge can be disabled, in order to allow exclusively
the acknowledgement via interface Ack:
With Feature.bit19 = TRUE only the interface Ack is active for acknowledgement.
Note
If additional Fault Reset is enabled the fault status bits are not automatically acknowledged
with Ack. After clearing the fault the Operator has to press “Fault reset” in the faceplate of the
annunciation block.
MemTrip (MTRIP)
Note
If the annunciation repetition time is set and the fault is not yet acknowledged, the repetition
of the alarm acknowledges the fault automatically.
TEST_OSS
SimuStatus
DisSeqTest
SimuSave
MSG8_EVID
COMMAND
2.1.3 Maintenance
MaiCntOn
Note
To permit the modification of the process values from the faceplates, they must not be
connected in the CFC.
SupOnTi
OutOnDTi
OutOfDTi
WaDelTi
Note
The time delay is only considered if input ActWarn has 1-Signal (corresponding drive is
running). In the start-up of a drive no warning is created and a fault leads immediately into a
fault message.
With OS_Perm.bit31 = TRUE the operator is permitted to change the delay time between
warning and fault message.
RepTi
Note
The annunciation repeat function is only effective if the alarm activation MsgTrigg has 1-
Signal. This means that a drive fault annunciation will only be repeated in case the fault has
not yet been acknowledged (DynFlt of the drive is still set).
If MemTrip = 1-Signal and the fault is not yet acknowledged, the annunciation repetition
acknowledges the fault automatically.
With OS_Perm.bit31 = TRUE the operator is permitted to change the alarm repeat time.
With OS_Perm.bit16 = TRUE the operator can start the maintenance interval.
MaiInt (MAI_INT)
MaiRL (MAI_REQL)
Note
If the block is in normal operation (none of the above mentioned situations) the inputs
Feature and OS_Perm are only read from the internal memory.
The HMI always shows the status of the internal memory.
Note
For a running plant this means that for any modification of Feature bits or OS Permissions the
module must be set to Out of Service mode.
Note
Both, the Feature bit settings of the Feature Master block and the Feature bit settings at the
block input Feature are only transferred to the internal memory if they are consistent
(ErrorNum = 0).
FeatMaster
FeatMaster Use OS permission and Feature bits from master Basic state 1-Signal
Format BOOL
Input FeatMaster is set to “S7-link = false” (cannot be connected).
With 1-Signal at input FeatMaster, the selected bits of the Feature Master block inputs
Feature and OS_Perm are transferred to the CEMAT block, when the module is in configu‐
ration state. These bits cannot be adjusted individually.
With 0-Signal at input FeatMaster the settings in the Feature Master block are not relevant
and all Feature bits and OS Permissions must be adjusted individually per instance.
Note
In this case, make sure that the settings which normally come from the Feature Master are
consistent and correct.
OS_Perm
Note
It is not allowed to connect any logic to OS_Perm input.
OpSt_In
Feature
Note
It is not allowed to connect any logic to Feature input.
EventTsIn
Note
Block EventTs must be installed in a Cyclic interrupt OB. The installation of block EventTs in
OB1 is not permitted and will not work!
Group/Route links
Each drive block, annunciation block or measurement block must be linked to a group or route
in order to collect the status of these objects for summarizing indications.
The group link is essential for control and diagnosis and comprises the following functions:
● All objects, linked to the group (or route) are listed in the group (or route) object list.
● All objects, linked to the group (or route) are highlighted in the process picture with button
"Show related objects".
● The faults of all objects, linked to the group (or route) are included in the summarizing fault
indication of the group (or route).
● The warnings of all objects, linked to the group (or route) are included in the summarizing
warning indication of the group (or route).
● In case of a dynamic fault during the startup of the group, the group start will be interrupted.
An annunciation block can be linked to two groups or routes via GR_LINK1 and GR_LINK2. If
an annunciation block belongs to more than two groups or routes the additional block C_MUX
must be inserted, which provides 5 additional link interfaces.
Note
The main group (or main route) should be connected to GR_LINK1! This is the one which is
opened with a click on button "Main group" in the faceplate of the annunciation block.
An Annunciation block which belongs to a drive can be connected to the drive via interface
O_LINK instead of the connection to the group or route vie GR_LINK1 and GR_LINK2 or via
C_MUX. The main group (or main route) information is not available in this case.
Note
It is not allowed to use the Object link and the Group/Route link at the same time: If O_LINK
is used, GR_LINK1 and GR_LINK2 or C_MUX must not be connected!
Via additional feature bit settings, control commands can also be transmitted through the group/
route link interface.
● With Feature.Bit16 = TRUE the dynamic fault signal DynFlt of the drive is
automatically used as message trigger for the allocated annunciation block. No connection
to MsgTrigg is needed.
Note
Feature.bit16 and Feature.bit18 must not be set at the same time!
● With Feature.bit17 = TRUE the running signal RunSig of the drive is automatically
used to activate the warning (two-level-alarm) for the annunciation block. No connection to
ActWarn is needed.
● With Feature.Bit18 = TRUE the running signal RunSig of the drive is automatically
used for supervision enable for the annunciation block. No connection to SupOn is needed.
Note
Feature.bit16 and Feature.bit18 must not be set at the same time!
Note
This is the only way of transmitting the mode feedback from the annunciation block to the
group. In difference to the drive blocks the C_ANNUNC block has no output OoSAct for
connection to FbObjOoS.
GR_LINK1
Note
GR_LINK1 must be used for the main group!
Structure variables:
GR_LINK1.Link Link Default: 0
Format INTEGER
GR_LINK1.Command Group / Route Command Default: 16#00
Format WORD
GR_LINK2
Structure variables:
GR_LINK2.Link Link Default: 0
Format INTEGER
GR_LINK2.Command Group / Route Command Default: 16#00
Format WORD
MUX_LINK
Note
If a C_MUX block is used, the programming order is very important. The C_MUX must be called
before the annunciation block!
If the same C_MUX block is connected to more than one object (e. g. the drive and
annunciations and measures of the same equipment), it is essential that no different group link
(or C_MUX) is programmed between those objects.
Structure variables:
MUX_LINK.Point_GRL Pointer Default: 0
Format INTEGER
MUX_LINK.Command Group / Route Command Default: 16#00
Format WORD
Note
Check the runtime sequence! The C_MUX module must be called before the annunciation
block. For the other modules the run sequence is as follows: first the annunciation blocks and
drives/devices, then the associated routes and finally the associated groups.
Note
Some people use one C_MUX block and connect its output to a number of drives/devices,
annunciations and measurements.
If you do so, make sure that the C_MUX is called before all the other objects and that no other
C_MUX call comes in between.
We don't recommend using the same C_MUX if the blocks are located in different runtime
groups.
The drive block collects the information and forwards it to the group (or route). The result is as
follows:
● All objects, linked to the drive are listed in the drive object list and in the group (or route)
object list (one level below the drive).
● All objects, linked to the drive are highlighted in the process picture with button "Show
related objects".
● The warnings of all objects, linked to the drive are included in the external warning indication
of the drive and in the summarizing warning indication of the group (or route).
● The faults of all objects, linked to the drive are included in the external fault indication of
the drive and in the summarizing fault indication of the group (or route).
● In case of a dynamic fault during the startup of the group, the group start will be interrupted.
Note
It is not allowed to use the Object link and the group/route link at the same time: If O_LINK is
used, GR_LINK1 and GR_LINK2 or C_MUX must not be connected!
Note
C_RECV_G can only be linked to a C_GROUP module. Linking to routes is not permitted and
will not work!
In the AS of the CEMAT Objects the output O_LINKQ of block C_SEND_G is connected to input
O_LINK of the drives/devices, annunciations, measurements and process feedback blocks.
O_LINK
Note
If annunciations, measurements or process feedback blocks belong to the drive, they don't
need to be connected to output O_LINKQ of the C_SEND_G block.
They can also be programmed as slave objects and connected to output O_LINKQ of the drive.
Structure variables:
O_LINK.iDB Instance DB master object Default: 0
Format INTEGER
O_LINK.iDW DW number NO_OF_FT in master object Default: 0
Format INTEGER
O_LINK.Command Group / Route Command Default: 16#00
Format BYTE
O_LINK.Status Status master object Default: 16#00
Format BYTE
ResTimOS
MaiRTm
MaiRTh
MaiCntSt
MAI_STA
MaiCorr
MaiCyc
STATUS
STATUS Interface to OS
Format DWORD
Interface to OS, For more information see Variable details.
STATUS2
STATUS2 Interface to OS
Format DWORD
Interface to OS, For more information see Variable details.
ALARM
FeatureOut
OS_PermOut
OS_PermLog
FWCopyMaster
OSCopyMaster
OpSt_Out
DelayCon
OutSig
Structure variables:
OutSig.Value Value
Format BOOL
OutSig.ST Signal status
Format BYTE
Structure variable OutSig.Value has a Property Text 1. Via this property, the sensor type
(max. 2 characters, e. g. "L+") can be added, for display in the block icon of the C_ANNUNC
block.
Text 1 is displayed in the block icon of C_ANNUNC.
DynFlt (MST)
Fault (MSO)
Lamp (MLA)
SimActQ
Warn
Structure variables:
Warn.Value Value
Format BOOL
Warn.ST Signal status
Format BYTE
MaintRQ
MaintAL
MaiRTm_Q
MaiRTh_Q
MaiCyc_Q
ST_Worst
Via feature bit setting it can be decided whether the Signal status is visible in the block outputs
as well:
If Feature.bit22 = TRUE, the worst status is additionally transmitted to the block outputs
(and via this to the next block).
The worst status of the binary signal InSig (or InSigB) and 'internal simulation' is transmitted
to outputs OutSig and Warn.
ErrorNum
Note
Only one error number can be indicated at a time!
The Event text (Message text in CFC) for SIG1 and SIG2 must be configured for each instance.
Each message is classified (Fault class).
This shows whether an electrical fault (E), a mechanical fault (M), a process fault (P) or a shut-
down with a local safety switch (S) applies.
By default all messages are of type (P) and can be adjusted during engineering.
● An electrician does not always need to be called first.
● The production operator can give specific instructions.
Still faulty message:
During start in automatic mode, any failure which inhibits the drive start leads to an interrupt
of the start procedure and must therefore be reported by an alarm message.
PCS7 can create the (incoming) alarm message only once and does not support the repetition
of incoming alarm messages without outgoing message. For this reason, CEMAT creates a
Message “Still faulty” for any alarm message which needs to be repeated.
The current operational state of the object is automatically taken into consideration during the
fault analysis. All fault annunciations are suppressed automatically if the alarm activation
MsgTrigg has 0-Signal.
● no superfluous fault annunciations are created
● the operator does not need to manually disable/suppress any annunciations.
Through connection of the control voltage signal to interface enable messages MsgEn, the
messages of the block are suppressed in case of a power failure (in order to avoid misleading
alarms and annunciation storm).
A detailed description of the individual Feature bits can be found in the chapters above.
Please consider that the Feature bit settings can only be changed in configuration state. For
a running plant this means that the block has to be in Out of Service mode.
If the block is in configuration state and the feature bit settings are consistent (ErrorNum =
0), the Feature Master block settings and the status of Feature are transferred into the internal
memory of the module.
Note
Do not connect any logic to input Feature
A detailed description of the individual OS Permission bits can be found in the chapters above.
Please consider that the OS Permission settings can only be changed in configuration state.
For a running plant this means that the block has to be in Out of Service mode.
If the block is in configuration state the Feature Master block settings and the status of
OS_Perm are transferred into the internal memory of the module.
Note
Do not connect any logic to input OS_Perm.