05 Engineering Examples 009
05 Engineering Examples 009
Engineering Examples
Content
Engineering Examples i
General .................................................................................................................... 3
Basic Rules ................................................................................................. 3
Connection rules and recommendations .................................................... 4
Annunciation Release ................................................................................. 4
Impulse Processing ..................................................................................... 5
Group functions ........................................................................................................ 6
Group start/stop .......................................................................................... 6
Start-up-warning ......................................................................................... 8
Group start interlock .................................................................................... 9
Group operation interlock .......................................................................... 10
Group switch-off interlock ......................................................................... 11
Start and Stop of the drives ...................................................................... 12
Feedback ON (all drives running) ............................................................. 14
Feedback OFF (all drives stopped) .......................................................... 15
Quick stop ................................................................................................. 16
Group Links ............................................................................................... 17
Object Links .............................................................................................. 19
Acknowledgement mode........................................................................... 21
Drive functions ....................................................................................................... 22
Change of operation mode ....................................................................... 22
Start and Stop in Automatic mode ............................................................ 25
Start and Stop in Single-start mode .......................................................... 28
Start and Stop in Local mode.................................................................... 29
Start-up warning in Single-start mode (and Local mode) ......................... 36
Sporadic mode .......................................................................................... 37
Drive in Standby (Alarm message also for non-running device) .............. 38
Protection interlocks .................................................................................. 39
Speed monitor supervision ....................................................................... 41
Set point input ........................................................................................... 44
Drive with SIMOCODE .............................................................................. 45
Drives with Subcontrol function................................................................. 46
Display of an analog value in % (e. g. Motor current) ............................... 47
Display analog value ................................................................................. 48
Star-Delta Starting; Slip ring Rotor with Starter Motor .............................. 49
Operation modes and control of the damper ............................................ 50
Analog actuators ....................................................................................... 52
Damper with middle position ..................................................................... 53
Damper with torque switch ........................................................................ 54
Wagging function ...................................................................................... 55
Fan and Damper ....................................................................................... 56
Annunciation blocks ............................................................................................... 58
Drive fault annunciations ........................................................................... 59
General
This description should provide support in the solution of control tasks using the CEMAT
software.
Please adhere to these recommendations that have proved themselves in practice.
Many block parameters start for historical reasons with a certain codification (name was never
changed because of Migration of existing plants). The codification is as follows:
Basic Rules
It is essential to conform to the following basic rules.
Limit Switches
The break contacts from these switches should be connected directly in the contactor control
circuit. Connect the make contact elements to the AS inputs.
Damper Directions
The following definition applies for the end position of the damper:
direction 1 = closed
direction 2 = open
The selection module is particularly suitable for smaller branches, standby circuits.
Advantage:
- reduced configuration effort
- reduced program run-time
The classical route module is particularly suitable for (long) transport routes that use different
drives.
Advantage:
- Through assignment of the objects to a route ‘partial groups’ are defined.
- Only the status of the objects belonging to a selected route will be forwarded to the group.
- Status call and object list call can be carried out for the individual route, which permits the
diagnostic function per destination
The question whether a selection module, a route module or various groups should be used
must be decided individually.
Annunciation Release
In all Cemat blocks through plausibility logic it is assured that in case of several simultaneous
faults only the "perpetrator" creates an alarm message.
For example, in case of a protection interlock of a motor, no alarm is created by the motor
block, it is created by the associated annunciation module.
In order not to create an alarm flush in case of loss of control power, each Cemat block has
an interface "Annunciation Release" xMFR, which has to be connected with the control power
signal.
In case of a periphery failure (such as bus failure, card failure, MCC failure) this signal must
get "0". At this moment the Cemat block does not create further messages (no incoming, no
outgoing messages).
For the annunciation of the control power failure itself an additional annunciation block has to
be programmed.
The annunciation release is one of the most important interfaces in order to achieve a smooth
! operation. The project engineer must assure that only the perpetrators of a fault create alarm
messages.
Impulse Processing
Both the pulse length and pause length must be longer than the OB1-cycle for signals that are
to be recorded from the cyclical program (OB1). As guidance value, it should be longer than
200ms.
OB1 Cycle
If the signals are recorded in the 100ms-OB cycle (time-controlled alarm processing), the
pulse times and the pause times of the signal must both be longer than 150 ms.
There are signals that are created with a flag attached to the drive shaft and a BERO switch.
Such signals, for example, have a short pulse and a long pause.
BERO-Signal
Group functions
Group start/stop
Starting and stopping of a group can be achieved via Operator Faceplate, through the
program or via a conventional Control desk (Push Buttons).
Group start via interface GEBG is only permitted if the start interlock and the operation
interlock have 1-Signal. A rising edge on GEBG is required.
For the group stop via interface GABG the switch-off-interlock is not considered!
!
In project standard 004 (Holcim), the group start via interface GEBG is only permitted if the
! group is switched into Standby mode. The Standby mode must be enabled by the operator.
The group stop via interface GABG is always permitted.
Group start and stop via conventional control desk (push buttons)
For the start and stop via conventional push-buttons the interface GTA must be connected
with the Stop button and interface GTE with the start button. GTA is normally closed, which
means it must be “1” if the button is not pressed. GTE is normally open.
In order to ensure a two-hand operation, the interface GFGS must additionally be connected
with a Release button. The Release button must be pressed together with the GTE or GTA
button.
The group start via GTE is only permitted if the start interlock and operation interlock have 1-
Signal. A rising edge on GTE is required.
Group Stop via GTA is only permitted if the switch-off interlock has 1-Signal.
In order to enable the interfaces GTA and GTA the pushbutton release GPTS must be
connected with a 1-Signal. (For the operation via operator faceplate GPTS must have 0-
Signal).
If you want to allow a parallel operation, via operator faceplate and via push buttons, this can
be achieved with the following logic.
Start-up-warning
Before the group start is transmitted to the drives, a start-up-warning must be given. The
group block has two outputs, one for a lamp and one for an acoustical signal (horn).
The lamp output GLA remains set during the complete start-up sequence and it will be
switched off when the group start is completed.
The horn output GHA will be set for the duration of parameter HORN_TIM. It can be used for
an acoustical alarm in the field.
The drives get started only after the waiting time WAIT_TIM has elapsed.
Horn time and Waiting time start simultaneously, which means that the waiting time should be
! a little bit bigger than the horn time. This insures that after the horn goes off the start is still
delayed for some seconds.
The start command is limited by the release time RELS_TIM. After the release time elapsed
no start command is given to the drives.
In case of a problem in any of the group objects during the start procedure, the dynamic fault
! of the object interrupts the group start command, but in this case the release time still
proceeds. If the problem can be solved within the release time the group start can be
triggered without creating a new start-up warning.
Time diagram:
Group start
ON Command GBE
Feedback ON GREZ
For the start-up-warning in single-start-mode the HORN outputs of the drives must
! additionally be considered.
In order to provide this information in the status call of the group, annunciation blocks must be
! programmed for the start interlocks. See “Annunciation bocks for status call function”.
In order to provide this information in the status call of the group, annunciation blocks must be
! programmed for the operation interlocks. See “Annunciation bocks for status call function”.
In order to provide this information in the status call of the group, annunciation blocks must be
! programmed for the switch-off interlocks. See “Annunciation bocks for status call function”.
Beside output GBE the group has an additional output GDE (continuous on command). Signal
! GDE is not suitable for starting the drives, because it is not reset in case of a fault. The drive
fault can not be acknowledged as long as there is a continuous 1-Signal on the motor
start command!
For the Stop of the drives, use output GDA of the group. The group output GDA is set with
the group stop and remains “1” until all drives of the group have been stopped.
There is no switch-off interlock available for the drives. For a sequential stop, the stop
condition (feeding drive has been stopped) must be connected together with the group output
GDA to the drive. The drive stop can additionally be delayed via parameter STOPDEL (see
drive blocks).
Beside output GDA the group has an additional output GBA (Off command). Output GBA is
! only a pulse, which means it is not suitable for stopping the drives (if a stop delay is
programmed, the output GBA doesn’t stay long enough).
In case of a group with routes, the route outputs WRE (Route Feedback ON) of the relevant
routes are connected to input GREZ of the group.
As long as GREZ has 1-Signal the start button of the group is disabled and restart is not
! possible. This especially has to be considered in case of an uninterrupted route change-over,
if one route is still running while a second route shall be started.
In case of a group with routes, the route outputs WRA (Route Feedback OFF) of the relevant
routes are connected to input GRAZ of the group.
Route Feedback OFF (Signal WRA) has 0-Signal if the route is not selected or if the route is
! completely stopped. For this reason, WRA must be inverted for the connection to the group
feedback OFF.
Quick stop
The group Quick Stop function is used for an immediate stop of the drives, which means the
stop delay STOPDEL is not considered.
The Quick Stop can either be carried out via the operator faceplate through the program via
interface GQSP.
In both cases the group sets an output GQS, which has to be connected to input QSTP of the
drives.
In order to display the Quick Stop Button in the operator faceplate, in the property „Styles“ of
! the block icon the attribute „StyleTag“ must be adapted accordingly.
With StyleTag 2, 6, 7 and 8 or. 102, 106, 107 and 108; the button “Quick Stop" in the group
faceplate will be visible. → See description 08_OS_Engineering_009.doc.
Group Links
All objects (Drives, Annunciation blocks, Measured values) belonging to a group must be
assigned to this group via group link. This connection is essential, in order to inform the group
about the status of the objects.
- Via the group link the group knows if one of the assigned objects has a problem. This is
important for the summarizing indication (summarizing fault and summarizing warning in
the block icon of the group) and for the status call.
- Dynamic faults interrupt the group start (GBE is reset).
- From Cemat V7.1 the group has a function to highlight all assigned objects in the process
picture.
Connect output G_LINK of the group to input GR_LINK1 (or GR_LINK2) off all related objects
(Drives, Annunciation blocks and Measured value blocks).
If the group has route modules, the output G_LINK of the group must be connected to input
! G_LINK of the route and output R_LINK of the route has to be connected to GR_LINK1/
GR_LINK2 of drives, annunciations and measured values.
As an object may belong to more than one group, each object has two link inputs GR_LINK1
and GR_LINK2 and an additional input MUX_LINK for the connection to a multiplex block
C_MUX. With this method the object can be assigned to an unlimited number of groups.
The main group should be connected to input GR_LINK1 of the object, because the button
“Related Objects“ opens the faceplate of this group.
Caution: If a C_MUX block is used, the runtime sequence is crucial. 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), the runtime sequence is even more important.
In case of annunciation blocks we must distinguish between annunciation blocks with direct
connection to the group/route or annunciation blocks which are linked via O_LINK to a drive
(child objects).
If the annunciation block is linked directly to the route/group the C_MUX block must be called
before the annunciation block. If the annunciation block is linked via O_LINK to a drive the
C_MUX block must be called after the annunciation block. Details see below.
Object Links
Since Cemat V8 SP1 it is possible to link annunciation blocks and measurements which
belong to a motor via interface O_LINK directly to the drive block. In this case the group links
GR_LINK1, GR_LINK2 and MUX_LINK must not be used!
- The drive block itself has an object browser function and is able to show a list of linked
objects.
- Additionally the drive block transmits all information from the linked annunciation blocks
and measured value blocks to the group, which interrupts the group start in case of a
dynamic fault (or warning) and which is used for summarizing indication (summarizing
fault and summarizing warning in the block icon of the group), object list and status call.
! Caution: 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!
Caution: Using C_MUX blocks the runtime sequence is crucial for the functionality of the
System, especially if you connect the same C_MUX block to more than one CEMAT Object.
! The only valid order is as follows:
1. Child Objects (all Annunciations, Process Feedback blocks, Measurements and Adapter
blocks which are linked via O_LINK to the drive)
2. C_MUX block (single C_MUX or cascaded C_MUX blocks)
3. Parent Objects (C_DRV_1D, C_DRV_2D, C_DAMPER and C_VALVE) and all
Annunciations
and Measurements with direct link to Groups or Routes
4. Corresponding Routes
5. Corresponding Group
Make sure that this sequence is strictly followed and that it is not “interrupted” by the
connection to a different C_MUX block or by any direct connection to a Group or Route!!!
Acknowledgement mode
All dynamic faults, warnings and interlocks must be acknowledged.
AS-wide Acknowledgement
Normally the fault acknowledgement goes together with the acknowledgement of the alarm
message in the alarm line and faults are acknowledged for the complete AS. In case of an
alarm message from AS1 in the alarm line, the acknowledgement will reset the faults of this
AS (only the dynamic fault of the blocks, the messages must be acknowledged individually.)
This is the default setting in the system chart SYSPLCxx at block C_FB_PLC, if parameter
ACK_GR and ACK_OB have value "0". In our opinion this is the most convenient method,
because beside the acknowledgement of the alarm message no further action is required.
Group-wise acknowledgement
Beside this there is a possibility of acknowledgement per group. In this case, in the system
chart SYSPLCxx at block C_FB_PLC the parameter ACK_GR must be changed to 1-Signal.
Additionally the output ACK of the group must be connected to the acknowledgement inputs
EQIT, KQT1, VQIT, MQIT and UQIT of all related objects.
Drive functions
Change of operation mode
Starting and stopping of drives can be carried out in three different operation modes. The
most important operation mode is the Automatic mode. In the Automatic mode the drives are
started and stopped via a group. All process interlocks are effective.
In Local mode the drives can be started and stopped via locally installed push-buttons. In this
operating mode the process interlocks are not effective.
In Single-start mode the drives can be started and stopped via operator faceplate from HMI.
Regarding process interlocks the behaviour is different in the individual project versions:
- In project version 004 the single-start mode is meant for maintenance only, and the
process interlocks are therefore not effective.
- Im Project veraions 006 and 007 there is a possiblility of a non-interlocked single-start
mode. But this mode must be explicitely released.
In some of the project versions (000, 007, 023, 024,025, 028) the operation mode is enabled
by the group block, the faceplate of the group has buttons for operation mode change and the
group block has outputs for enabling the corresponding operation mode of the drives.
Therefore the group output GES must be connected to drive input xEIZ and group output GLO
must be connected to drive input xLOC.
In all other project versions (004, 006, 026, 027) the operation mode can be changed
individually via the drive faceplate. Some project versions additionally allow group-wise mode
change from local to automatic (004, 002, 026) or from automatik to local (004, 026).
In Project version 004 group output ENLM switches the drives into local mode and output
DILM switches the drives back to automatic. Both outputs are only pulses and must be
connected to the input of the drives with the same name.
The feedback to the group (LOCAL to FB_L) is used for the indication in the block icon and
tells the operator that at least one drive is in local mode.
In Project version 026 group output GVE must be connected to drive input xVFE and group
output GVA must be connected to drive input xVFA. The outputs of the group are pulses and
only used for switching over.
The feedback to the group (EBV to GRVO) is used for the indication in the block icon and tells
the operator that at least one drive is in local mode.
In Project version 006 the group has an output GAU (Pulse) which must be connected to
input xAUT of the drives, in order to switch all drives of a group back into automatic mode. In
case of a group with routes, the switch-back can be carried out per route. In this case output
GAU of the group must be connected to input WAUT of the route and output WAU of the route
must be connected to input xAUT of the drives.
The feedback to the group (EHV to GZHV) is used for the indication in the block icon and tells
the operator that at least one drive is in ‘Manual interlocked’ mode.
The feedback to the group (EHE to GZHE) is used for the indication in the block icon and tells
the operator that at least one drive is in ‘Manual non-interlocked’ mode.
Output GDE of the group is not suitable as drive start command, because this signal is not
! reset in case of a fault. The drive fault cannot be acknowledged as long a there is a
continuous 1-Signal at the on command!!
For the Stop of the drives in automatic mode the output GDA of the group must be connected
to input EBFA or VBFA of the drives.
Output GDA is set with the group Stop and remains "1" until the group is completely stopped.
As the drives to not have a stop interlocking, for a sequential stop the stop condition (feeding
drive is stopped) must be connected together with the group output GDA to the drive. The
drive stop can additionally be delayed via parameter STOPDEL.
Group Output GBA (Command Off) is only a pulse and normally not suitable for stopping the
! drives (if a stop delay is used output GBA does not stay long enough).
For the Quick stop of the drives the group output GQS must be connected to input QSTP of
the drives. In case of a Quick Stop the drive is stopped immediately (without considering the
Stop delay).
Regarding local mode the project versions are different, which means depending on the local
switch which is used one project version is more or less suitable.
Probably other variants of local switches exist. In case you have any doubts and cannot
decide which project version fits best, please contact the Cemat Competence Center.
On the following pages you find examples for the different project versions:
The Project versions 000 and 028 can be used for variant 1, variant 3 and variant 4.
The Local mode is enabled per group. Additionally the switch EVO must be in position Local.
If no additional switch for the selection between Remote/Local is available, the input EVO
must be simulated using inverted group enable GLO.
If the enable via HMI shall not be used, the input ELOC must be simulated by using inverted
EVO signal.
The project version 024 is suitable for variant 1, but it requires a special matrix. In this matrix
4 different situations are simulated with only two signals.
Switch position K0 KX
Automatic 1 0
Local Stop 0 0
Local 0 1
Local Start 1 1
The project version 025 is suitable for variant 2, but it requires a special matrix. In this matrix
3 different situations are simulated with only two signals.
Caution: If DLOC is connected the mode change via drive faceplate is no longer possible!
!
If the start-up warning shall be given also in local mode, you have to change parameter
L_STA_WA of the drive to 1-Signal. See drive M3.
Caution: In local mode the start button must remain pressed until the start-up warning is
! completed.
Sporadic mode
Concerns Unidirectional drive, Bi-directional drive and Valve
Sometimes it is required to start and stop drives dependent on a process signal or time
controlled. This concerns devices for heating, cooling, lubrication or valves for silo aeration.
In this case the drives have to be activated via group start signal GBE or via route start signal
WBE and can then be switched on and off via the status at interface ESPO.
0-Signal at interface ESPO stops the motor without reset of the command memory EKS. The
motor remains activated and starts automatically with 1-Signal at this interface.
To switch off the drive completely it needs a 1-Signal at EBFA or 0-Signal at the operation
interlock (EBVG or IntOper). If the drive has been stopped by fault the group must be started
again.
For the feedback to the group signal EVSP must be used. EVSP has 1-Signal, as soon as the
drive is activated.
This interface is only effective in automatic mode. In Single-start mode or in Local mode
ESPO is not considered. In case of a mode change the behaviour is as follows:
- If a drive which is running in automatic mode is switched to single-start mode, it will then run
continuously.
- If a drive which is running in single-start mode is switched into automatic mode, the signal
status of ESPO is considered. If ESPO = 0-Signal the drive is stopped (EKS is reset). If
ESPO = 1-Signal the drive will proceed in sporadic mode.
Protection interlocks
Protection interlocks are interlocking conditions which must stop the drive in case of a fault, in
order to protect machines or persons.
In case of a missing protection interlock the drive indicates ‘faulty’ (red indication), similar to
normal drive faults (static fault if the drive was not running, dynamic fault if the drive was
stopped through protection interlock.)
Unlike for normal drive signals as e. g. electrical availability or overload, the drive block does
not create alarm messages for protection interlocks. An annunciation block has to be
programmed for this purpose. See chapter ’Drive fault annunciations’.
In Project version 004 the binary interfaces are called PINT1, PINT, PINTX and PINTY, the
structure interfaces are called IntProt1, IntProt, IntProtX and IntProtY. These interfaces are
effective in all operation modes.
The Unidirectional drive and the Bi-directional drive have an additional binary interface PINT2
and an additional structure interface IntProt2, which can be by-passed in local mode with the
local start button. In this case the motor will run only as long as the start button is pressed.
2. The process feedback signal is a pulse. The signal must be connected to interface
SW_SPEED and parameter REL_SSM must have 1-Signal. The feedback supervision
time SPEEDTIM is set to 10 seconds and parameter SM_EVS_I is configured in a way
that outputs EVS and RunSing are set after the feedback supervision time.
The tolerance value for the detection of pulses TOL_SSM is preset to 50 cycles, which
means if after 50 OB1 cycles no signal change at input SW_SPEED is detected, the
motor is switched off with ‘Speed monitor fault’.
In Project version 006 the drive block has an additional interface EVQD for the
acknowledgement of the speed monitor fault. The speed monitor must be acknowledged from
local. Via the normal fault acknowledgement the speed monitor fault cannot be reset.
In Project version 004, block C_PROFB is used for process feedback supervision and alarm
message. Also this block has two options, the supervision of a continuous signal or the
supervision of pulses
Via connection of drive output STAT_DRV to input STAT_DRV of block C_PROFB the
process feedback block receives the status of the drive.
The output ‘ProFb’ of block C_PROFB transmits the process feedback to the motor and
output ‘Fault’ of block C_PROFB must be used as protection interlock in order to switch off
the drive in case of a fault.
Dependent on the function, different options exist:
1. The process feedback is a continuous signal. The signal must be connected to interface
IN_SIG and parameter EN_SSM must have 0-Signal.
The feedback supervision time during start-up ON_DEL is set to 10 seconds and
parameter OUTIM is configured in a way that outputs EVS and RunSig are immediately
set when the process feedback is true.
Via parameter EN_OFFDM the supervision during switch-off is activated and parameter
OFF_DLY is set to 15 seconds.
2. The process feedback signal is a pulse. The signal must be connected to interface
PULS_SSM and parameter EN_SSM must have 1-Signal. The feedback supervision time
during start-up ON_DEL is set to 10 seconds and parameter OUTIM is configured in a
way that outputs EVS and RunSing are set after the feedback supervision time.
The tolerance value for the detection of pulses TOL_SSM is preset to 50 cycles, which
means if after 50 OB1 cycles no signal change at input PULS_SSM is detected, the motor
is switched off with ‘Process feedback fault’. The supervision during switch-off is
deactivated.
If the set point is given by a program, e. g. by a primary controller, this function must be
enabled via interface EN_SPEX and the external set point must be connected to input
SP_EX.
For set point tracking SP_TR must have 1-Signal.
The name of the SIMOCOE Adapter must be similar to the drive + ’_SC’. In the example
above the motor block is called ’M1’ and the Adapter block is called ’M1_SC’.
Parameter REL_SC must contain the block type for the SIMOCODE Adapter, in this case
C_SIMOS.
The drive gives the start command (output EBE) to the C_SIMOS (input START2).
The C_SIMOS gives the feedback (output FEED_ON2) to the drive (input ERM).
The C_SIMOS transmits the status (output STAT_SC) to the drive (STAT_SC). The status
contains the information ’General Fault’ and ’General Warning’, which is displayed in the
diagnostic window of the drive block.
If the motor current in % shall be displayed in the drive faceplate, the function must be
enabled via parameter REL_MVC and output I_PERC of C_SIMOS must be connected to
input MV_PERC of the drive.
At the SIMOCODE Adapter block you have to configure the Basic type and the start address
for inputs and outputs. Make sure that the inputs and outputs are in the process image!
Additional connections:
The 4 free configurable outputs INPUT1_O, INPUT2_O, INPUT3_O and INPUT4_O of the
C_SIMOS are not predefined and can be used in order to transmit additional information (e. g.
electrical availability or overload) from the SIMOCODE block to the drive.
Input RESET of C_SIMOS can be used in order to acknowledge the SIMOCODE fault via
program.
The Subcontrol does not have its own block icon. If required, the subcontrol faceplate can be
opened via the drive faceplate.
The block icon of the drive must have special attributes, containing the information about the
subcontrol name and type.
Additional Link Attributes for Subcontrol Functions (only for C_DRV_1D, Index 150):
SubText is the button Text, displayed in the motor faceplate
SubTag is the TAG (Tagname) of the Subcontrol
SubType is the S7 Structure name (Block type)
If you want to display a power instead value of a current value, you have to modify the
description at parameter CURR_OS:
If you want to link more than one measured values to the drive and select one of those for
display in the drive faceplate, you have to use the function C_ANASEL. This block is
described under additional blocks.
Note: In the local operation (local control using the AS), the Local-On push-button must
! remain depressed until the drive runs fully (ERM=1).
The ERM signal provides the criteria for maintaining the On command. If the On command
was stored immediately and the drive for some reason did not start, then dangerous
operational states could arise, because the motor could start subsequently without the push-
button being activated.
Caution: In all Operation modes (Automatic mode, Single-start mode, Local mode, Inching
! mode or Positioning mode) the damper is controlled via two binary outputs.
Inching mode is possible via conventional control desk buttons or via the operator faceplate.
In case of control desk buttons the damper is opened/ closed as long as there is a 1-Signal at
the corresponding input. In case of Inching mode via HMI the damper is opened and closed
step-wise via faceplate buttons.
For the inching mode a special release function is required (KTFG = 1) which disables the ON
commands for automatic mode.
The Positioning mode allows entering a set point (as external set point or via damper
faceplate) and the damper is opened or closed until the actual position matches with the set
point. In this case a position feedback is always required.
- The release of the positioning mode is achieved through a 1-Signal at interface KPOS and
KTFG
- Output ‘PV_Out‘ of the measured value for damper position must be connected to interface
POS_IN of the damper.
- Via parameter SCB, SCE and UNIT Scale beginning, Scale end and Dimension
for the Set point can be defined. The actual value (damper position) is always in %.
- Set point tracking can be enabled via parameter KSNF.
- Via parameter KWUG and KWOG the set point limits can be defined.
- You also have to parameterize the minimum pulse length TMIN, the damper runtime TM,
and
..for a Hysteresis function the response threshold AN and the dropout threshold AB.
Analog actuators
If the damper/actuator needs an analog signal for the control (like e. g. analog actuators from
AUMA), this can be achieved as follows:
Caution: These actuators can exclusively be controlled in positioning mode, because in all
! other operation modes the output W_ACT_O is not actualized.
In local mode the analog output must be controlled directly (not via PLC)!
Wagging function
If the wagging function is enabled (KWED = 1-Signal), in case of a torque switch trip the
damper will be controlled back to the old position. After this it will try again for the controlled
position. This behaviour is called ‘wagging’.
The number of trials (wagging number) can be configured at process parameter WAGG_NO.
If after the maximum number of trials the selected limit position is still not reached, an alarm
message is given for ’Mechanical fault’.
Example for a damper with torque switches, in case the wagging function is enabled:
a) Connections between fan and damper in case of positioning through control desk buttons:
Annunciation blocks
Annunciation blocks are used to for the supervision of binary process signals. The signal
status is displayed in the process picture (ok, fault or warning) and in the summarizing
indication of the group. In case of a fault a message (fault message or warning message) can
be created in the alarm line.
Depending on the format of the input to be evaluated, the annunciation block has different
interfaces.
MST0 for the evaluation of a Boolean signal
PV for the evaluation of a structure input (e. g. from APL channel driver Pcs7DiIn)
Parameter OKS decides how the signal is evaluated. The status of OKS corresponds to
status ’input signal ok’. As most of the process signals are fail-safe, which means in good
condition they are “1”, we recommend to set parameter OKS to 1-Signal in order to avoid the
negation of the input.
The simulation value M_SIM should be similar to the OK-Signal.
Via the process parameters IN_DEL and OUT_DEL incoming and outgoing faults can be
delayed.
Parameter WMOD decides if a fault or a warning is displayed. (WMOD = 1-Signal for
warnings).
- In the example above the binary signals are directly read from the process image. For this
purpose interface MST0 is used. Both signals are fail-safe (in good condition ’1’);
therefore OKS and M_SIM are set to 1-Signal.
- The message for the pull rope switch must be created without delay (process parameter
IN_DEL = 0). The message for the belt drift switch has to be delayed for 10 seconds
(Process parameter IN_DEL = 10).
- In order to create the message at the same time as the drive stop, the output of the
annunciation block (MAU or OutSig) bust be used for the connection to the protection
interlock. It must be distinguished between protection interlocks which are always
effective (ESVG or IntProtG) and protection interlocks which are effective only in
automatic or single-start mode. (ESVA or IntProtA).
- In order to trigger the alarm with each drive fault (even if the operator tries to start an
already faulty motor) the alarm activation MAAT of the annunciation block must be
connected with the output ‘dynamic fault’ (EST, VST, KST) of the drive block.
- The annunciation release of drive block and annunciation block must be connected with
the same signal for ‘control power ok’.
Warning messages
Via parameter WMOD is defined if in case of a bad input signal a fault or a warning is
indicated. (WMOD = 1-Signal for warning).
If the signal is used for interlocks with other blocks, block output ’Warn’ must be used,
because MAU and OutSig are always ‘good’.
Caution: Output ‘Warn’ does not depend on OKS. In case of a fault output ‘Warn’ has
! 1-Signal!
Example:
The alarm message must only be created if the group was started (and not stopped).
- Via connection of WMOD with 1-Signal, in case of level “High“ a warning message is
created instead of a fault message. Output “Warn“ is used as start interlocking of the
group.
Caution: Signal must be inverted (does not depend on OKS).
- The connection of MMZS with 1-Signal effects that the fault or warning is not included in
the summarizing indication of the group. After all, the silo levels are no faults or warnings,
they are only interlocking conditions.
- If GFSO is connected with 1-Signal the interlocking would be excluded form group status
call as well. However, this behaviour is not wanted, because the interlocking should
appear in the status call as well.
- Through connection of the alarm interlocking MAMV with signal GVG of the group, the
message is only created if the group was started. If the group is was not started only a
static indication is given (without message).
- The annunciation release must be connected with the signal for ‘control power ok’.
- As parameter IN_DEL has 0-signal, the warning message is created without delay.
However, a time delay for the warning is also possible.
- Via parameter WARN_DEL the time delay between warning message and fault message
is configured.
- Signal OutSig is not influenced by the warning and switches off the drive only in case of a
fault.
- Input AWAN activates the two-level alarm and must be connected with the running signal
of the motor.
Only for a running drive (EVS = 1-Signal) the belt drift fault leads to a two-level alarm.
In case of a present belt drift fault at the moment of a drive start, the fault message is
created immediately.
Caution: In project version 004 the running signal EVS cannot be used for AWAN because in
! single-start mode the running signal is not created. You must use a logic instead: Contactor
feedback ERM & not LOCAL.
- Interface MMZS is connected with 1-Signal in order to exclude the annunciation block in
the summarizing indication of the group.
- Interface MAMV is connected with 0-Signal, this kind of annunciation block must never
create an alarm.
- This annunciation block does not need a block icon. Deselect the option in the block
properties.
Release supervision
Certain process signals must only be evaluated if the associated device which creates or
influences this signal is running.
The following example shows a pressure supervision which should only be active if the
associated pump is in operation.
If 10 seconds after the pump start the pressure is not yet built or in case of pressure loss
during operation, the pump will be stopped immediately (via protection interlock).
- The supervision gets enabled through connection of interface RELS with the running
signal EVS of the drive. The time delay of 10 seconds for the supervision is configured at
parameter REL_DEL.
- If the input signal which is connected to MST0 is additionally connected to MSIG, the
block icon in the process picture shows green colour as soon as the pressure is built.
- With 1-Signal at interface MTRIP you achieve that after the stop the fault is memorized
until acknowledgement. If MTRIP has 0-Signal, immediately after the drive stop the status
of the annunciation block is ‘good’ again.
- Via connection of the protection interlocking IntProtG with the summarizing fault FX of the
annunciation block (negation required) the motor will be switched off if one of the ropes is
pulled.
- Through connection of the alarm activation FAT1 – FAT7 with the dynamic fault of the
drive, the fault message is only created if the motor is stopped by fault.
- Don’t forget to enter the individual fault texts via property ‘identifier’ at parameter FLS1 –
FLS7. The texts are used in the diagnostic window and in the status call function. The
maximum text length is 16 characters.
- The annunciation release SWK must be connected with the signal for ‘control power ok’.
Measured value
Read in a measured value
Measured value blocks are used for the supervision of analog process signals. The value and
the signal status are displayed in the process picture and in the summarizing indication of the
group. In case of a fault a message (fault message or warning message) will be created in the
alarm line.
Depending on the format of the input to be evaluated, the measured value block has different
interfaces. Parameter TYP defines which input is evaluated:
TYP = 77 Reading a card value from input MV_CARD
TYP = 10 Reading a REAL value form input MV_PHYS
TYP = 20 Reading a REAL structure from input PV
Reading a physical value in structure format (e. g. from APL driver block Pcs7AnIn)
If you want to inhibit the outputs HH, H, L and LL in the above mentioned situation as well,
you have to connect interface RA_OI with 0-Signal.
Example:
The message for the limit supervisions should only be created if the group is completely
started.
If the limit bits are used for start interlock or operation interlock of the group the following
aspects have to be considered:
- Upper limit 1 and upper limit 2 are interlocks and should not be included in the
summarizing indications of the group block icon. Therefore UMZS has to be connected
with the limit bits.
If UMZS is connected with a continuous 1-Signal (LOG1) also Life Zero fault (bad quality)
is excluded from the summarizing indication.
- By connecting the alarm interlocking UAMV with Signal GVG of the group, the measured
value block only creates alarm messages when the group is started.
- Via status call function the operator can check for existing interlocks at any time (also if
the group has not been started).
In this case the measured value is blocked with a 1-Signal at interface UGWA (for
example while the calibration is running).
If UGWA = 1-Signal the measured value is not read in anymore and the last value is
frozen. The limit bits are frozen as well.
In this case the bypass is carried out via HMI (Service mode).
In the Service mode the measured value is still read but all limit bits are forced to “0“.
- The limit supervision is enabled via connection of interface RELS with the running signal
EVS of the corresponding drive. The time delay of 10 seconds is configured at parameter
REL_DEL.
- With 1-Signal at interface MTRIP you achieve that after the drive stop the fault is
memorized until acknowledgement. If MTRIP has 0-Signal, immediately after the drive
stop the status of the measured value block is ‘good’ again.
Pressure control
A pump shall be switched on if the minimum pressure is reached and switched off with
maximum pressure.
- The switching limit ‘SL‘ is used for switching ON and the switching limit ‘SH‘ for switching
OFF.
- Start and stop of the pump is carried out via interface ESPO.
- For the feedback to the group EVSP is used instead of EVS.
Route functions
Feedback ON (all drives running)
Via the route feedback ON (interface WREZ) the route is informed that the start-up has been
completed and all drives are running.
Depending on the application this can be an AND-Function with the running signal of all
drives, or the last drive of a start sequence.
With 1-Signal at input WREZ, for a selected route the binary output WRE is set, which is used
as feedback to the group.
b) Feedback to the group if both routes may run at the same time:
If one route is already running and a second group shall be started additionally, you have
to take care that with the selection of the new route the group feedback gets “0“.
Otherwise restart of the group is not possible.
With 1-Signal at input WRAZ the binary output WRA which is used for the feedback to the
group is reset.
The route feedback OFF (Signal WRA) gets "0" if the route is not selected or completely
! stopped. For the connection of the group feedback OFF the output WRA must therefore be
inverted!
Task:
The change for charging into Silo1 or Silo 2 has to be without interrupt, i.e., the feeding drives
should not be stopped during the switching operation.
Both air slides E02 and E03 must run while the damper is being moved. The part of the old
transport direction that is no longer required is switched off only when the new direction has
been traversed completely.
The following connection example provides a solution for a transport group with two routes:
The air slides E02 and E03 and the damper position K1 (direction silo 1) belong to route 1.
The air slides E01 and E03 and the damper position K2 (direction silo 2) belong to route 2.
Operation:
During the switching, the new route must be selected first and then the group started.
Whether the route selection and the group start takes place manually or automatically is not
relevant.
The connection example becomes clearer by looking at the individual conditions that must be
fulfilled for a change of routes without interrupt.
- The route change can only take place when the group is stationary or runs completely
refer to WHVR
- If a route was pre-selected and the pre-selection of another route is added, then the own
pre-selection must be removed.
refer to WVWL and WUUS
- In case of a route change without interrupt the group has to be started while it is
completely running (because the drives of the “old” route are still running).
To permit the group to give the start command again, the “group feedback On / route
feedback On“ must be removed. This is done by linking the route pre-selection WVE with
the drive feedbacks.
refer to WREZ
- The old route is deselected automatically once the newly started route runs completely.
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 GDA
signal) or for a fault if the switching has not been performed within a specified time.
refer to EBFA from E01
Note: The automatic group-On command must be supplied only when the GREZ signal of the
! group becomes zero (otherwise no start is possible).
refer to GEBG.
In the faceplate of the interlock block at each input the name of the connected block is
displayed automatically, here e. g. 100_BC2/RS01. For additional information you can enter a
text at the corresponding input under Object properties → Text 0 and Text 1 (maximum 16
characters).
b) Binary interlock block C_INTER5 (can only be called from diagnostic window)
C_INTER5 is called via the variable name. The interlock block must therefore be named as
follows:
Name of the Cemat block + Underline + Name of the interface + Index (1/2/3).
You can connect 3 blocks of type C_INTER5 to each interface.
The text for the inputs is configured via parameter S_TEXT (5 texts a 16 characters,
separated by semicolon).
c) Binary interlock block C_INTERL (can only be called from diagnostic window)
C_INTER5 is called via the variable name. The interlock block must therefore be named as
follows:
Name of the Cemat block + Underline + Name of the interface + Index (1/2/3).
You can connect 3 blocks of type C_INTERL to each interface.
The text for the inputs is configured via parameter S_TEXT (5 texts a 16 characters,
separated by semicolon).
The texts for the inputs are defined via object properties of the corresponding input (I1_1 to
I1_5 and I2_1 to I2_5) under Text 1 (text length max. 16 characters).
Caution: A mix of C_INTER5 and C_INTERL at the same interface is not permitted.
!
The function for left mouse click must be adapted (enter number of the AS):
- You have to connect output PV_Out of the measured value to input Inxx of the
C_ANASEL and output PV_Stat of the measured value to input InxxStat of the
C_ANASEL.
- The output Out_Val of the C_ANASEL must be connected to input PV of the drive and the
output Out_Stat of the C_ANASEL to input PV_Stat of the drive.