Professional Documents
Culture Documents
Operating principle 2
Time characteristics 3
PCS 7
Message characteristics 4
CEMAT
Valve C_VALVE 5
Module States
Operator Commands 6
Function Manual
Feature Bits 7
OS Permissions 8
I/O-bar of C_VALVE 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.....................................................................................................11
1.3 Configuration state.................................................................................................................14
1.4 Additional functions................................................................................................................15
1.5 Optional features....................................................................................................................16
1.6 Sequence Test.......................................................................................................................19
1.7 Visualization...........................................................................................................................20
2 Operating principle.....................................................................................................................................21
2.1 Hardware inputs.....................................................................................................................21
2.2 Input interfaces.......................................................................................................................29
2.2.1 Interfaces for operation mode change...................................................................................34
2.2.2 Limit position switches...........................................................................................................37
2.2.3 SIMOCODE drives.................................................................................................................43
2.2.4 User output function...............................................................................................................44
2.2.5 Inputs for testing and as Interface to the OS..........................................................................45
2.2.6 Process Parameters for starting and stopping.......................................................................47
2.2.7 User specific adaptations.......................................................................................................50
2.2.8 User Faceplate call................................................................................................................50
2.2.9 Process parameters for Maintenance function:......................................................................51
2.2.10 OS Permissions and Features:..............................................................................................52
2.2.11 Connection to EventTs...........................................................................................................56
2.3 Group and Object links...........................................................................................................57
2.3.1 Example of a circuit:...............................................................................................................60
2.3.2 Object links to slave objects...................................................................................................61
2.3.3 Object links to a group in a different AS.................................................................................63
2.4 Input/Output interfaces...........................................................................................................65
2.5 Output interfaces....................................................................................................................67
2.5.1 Outputs for testing and as Interface to the OS.......................................................................67
2.5.2 Output status for connection to other blocks..........................................................................71
2.6 Hardware outputs...................................................................................................................78
2.7 Engineering Errors.................................................................................................................80
Valve C_VALVE
Function Manual, 07/2016 3
Table of contents
3 Time characteristics....................................................................................................................................83
4 Message characteristics.............................................................................................................................85
5 Module States.............................................................................................................................................89
6 Operator Commands..................................................................................................................................91
7 Feature Bits................................................................................................................................................93
8 OS Permissions..........................................................................................................................................97
9 I/O-bar of C_VALVE...................................................................................................................................99
10 OS-Variable table.....................................................................................................................................109
11 Variable details.........................................................................................................................................111
11.1 Variable details COMMAND.................................................................................................111
11.2 Variable details ExtCmd.......................................................................................................112
11.3 Variable details MSG8_EVID...............................................................................................113
11.4 Variable details VISU_OS....................................................................................................114
11.5 Variable details INTFC_OS..................................................................................................115
11.6 Variable details STATUS.....................................................................................................116
11.7 Variable details STATUS2...................................................................................................117
11.8 Variable details STATUS3...................................................................................................118
11.9 Variable details MAI_STA....................................................................................................119
Valve C_VALVE
4 Function Manual, 07/2016
Function 1
Type/Number
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).
Valve C_VALVE
Function Manual, 07/2016 5
Function
1.1 General Function description
Operating modes
Module Type C_VALVE can be used to control all kind of Valves. Open/close commands can
be given in three different operating modes:
● In "automatic mode" the valve is opened/closed by a superordinated group module.
All process interlocks and protection interlocks are effective.
● The "manual mode" allows individual control via operator faceplate of the valve.
Different interlocking levels exist, which must be configured via Feature bits.
● In "local mode" the valve can be opened and closed by the locally installed switches or
pushbuttons.
Only the general protection interlock and the essential interlocks are effective.
The following table shows which mode change is permitted:
Valve C_VALVE
6 Function Manual, 07/2016
Function
1.1 General Function description
Standard Signals
The following standard signals are monitored by the Valve block:
● Contactor feedback FbkRun in conjunction with the contactor output ContOn
● Limit Position FbkPos1 (closed)
● Limit Position FbkPos2 (open)
● Electrical availability ElAvail
● Overload or Bimetal Overload
Note
Limit Positions:
Per definition the limit position FbkPos1 is "closed" and the limit position FbkPos2 is open,
but it can be configured, which is the active (energized) direction.
The valve block is able to handle valves with two limit positions, with a single limit position or
without limit positions. In case of a single limit position, the position switch for the active
(energized) position switch must exist.
Additional field switch signals allow local control via field switches or pushbuttons:
● Field switch ready signal AutModLo (Position switch or Repair switch)
● Field switch stop signal StopLoc (Stop local)
● Field switch start signal StartLoc (Start local)
The function of the field switch signals may differ from plant to plant. Therefore the function
must be configured via Feature bits. Refer to "Hardware Inputs", "Feature bit options for Field
switch (Local switch) signals"
If the valve is in automatic or in manual mode and the valve is energized, a wrong status at
any of the above mentioned signals leads to an alarm message.*)
*) The message can be of type "fault" (Alarm – high) or "warning" (Warning – high), depending
on the block settings.
Priorities for alarm messages:
*) The priority between ElAvail and Overload can be reversed via input MsgPrio.
Valve C_VALVE
Function Manual, 07/2016 7
Function
1.1 General Function description
Automatic start/stop
Please note that the push button for the non-active mode (StopLoc) must be a normal-close
contact.
Feature.bit29 = TRUE: direction 1 is active
Automatic start/stop
Valve C_VALVE
8 Function Manual, 07/2016
Function
1.1 General Function description
Please note that the push button for the non-active mode (StopLoc) must be a normal-close
contact.
Protection Signals
If additional protection interlocks exist for the valve, those signals have to be linked to an
Annunciation block C_ANNUNC or C_ANNUN8 in order to create an alarm. In order to stop
the valve in case of a fault an output of the annunciation block has to be connected to the
protection interlock of the valve.
Process interlocks
Process interlocks can be used in order to enable or disable the valve operation dependent
on a process condition, like "previous drive/device is running" or a process signal. If the process
interlocks are not fulfilled, no alarm is created. This implies that for diagnosis purpose the
interlock blocks must be used (if necessary also additional C_ANNUNC blocks).
The following process interlocks are available and can be used as per definition. Refer to
"Change of operation mode", "Feature bit options for mode change").
X = effective
*) the evaluation of the essential interlocks in local mode can be disabled via Feature bit
settings.
Valve C_VALVE
Function Manual, 07/2016 9
Function
1.1 General Function description
**) the evaluation of the stop interlock IntStop in manual mode can be enabled via feature
bit settings.
Sporadic mode
The sporadic mode allows opening and closing of the valve dependent on a process condition.
With the start command in automatic mode (group start command) the valve gets "activated"
and will then be ready for open/close via interface "Sporadic":
Process parameters
Through process parameters the following values can be configured online:
Valve C_VALVE
10 Function Manual, 07/2016
Function
1.2 Change of operation mode
Note
Via Feature bits the preferred interlocking level is defined (when switching the valve into
manual mode via interface ManModOn or via GR_LINK). Possible modes are enabled via OS
Permission.
Valve C_VALVE
Function Manual, 07/2016 11
Function
1.2 Change of operation mode
Valve C_VALVE
12 Function Manual, 07/2016
Function
1.2 Change of operation mode
A valve can be switched into Out of service mode via Operator faceplate or via program.
● Changing into Out of Service mode via Operator faceplate is only possible if the valve is
de-energized and in this case Switching back from Out of Service mode to Automatic,
Manual or Local mode needs to be done via Operator faceplate as well.
● 0-Signal at program interface OoSModOn forces the valve to Out of Service mode at any
time and the valve will then be de-energized.
In this case switching back from Out of Service mode to Automatic, Manual or Local mode
is possible via a rising edge at inputs AutModOn, ManModOn or LocModOn or via Operator
faceplate.
Valve C_VALVE
Function Manual, 07/2016 13
Function
1.3 Configuration state
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.
Valve C_VALVE
14 Function Manual, 07/2016
Function
1.4 Additional functions
SIMOCODE drives
If SIMOCODE is used, the communication between the valve block and the SIMOCODE can
be carried out via adapter block C_SIMOS or C_SIM_AD.
An additional button in the valve faceplate opens the faceplate of the adapter block in order to
display the SIMOCODE details.
Valve C_VALVE
Function Manual, 07/2016 15
Function
1.5 Optional features
Rapid stop
Option for Rapid stop via Operator Station exists. Via right mouse-click on the block icon the
Rapid stop push-button appears.
The Rapid stop function must be enabled via feature bit setting:
If Feature2.bit11 = TRUE the stop code and the time is written to the output LaStopRe.
Valve C_VALVE
16 Function Manual, 07/2016
Function
1.5 Optional features
Note
If Fault reset function is enabled at the C_DAMPER, the function must as well be enabled for
all linked C_ANNUNC, C_ANNUN8 and C_MEASUR blocks.
Note
Be aware that the simulation of limit positions may lead to uncertain plant operation, because
the real status of the valve is not secured any more.
Feature.bit31 = TRUE enables the simulation function. Two additional buttons are shown
in diagnosis window.
The enable buttons in the diagnosis window get active if the corresponding OS Permission is
given:
OS_Perm.bit27 = TRUE allows the operator to switch on the simulation of the active
position switch.
OS_Perm.bit28 = TRUE allows the operator to switch on the simulation of the idle position
switch.
If the simulation is enabled for any of the limit position switches, the block icon changes to
orange color (simulation).
Valve C_VALVE
Function Manual, 07/2016 17
Function
1.5 Optional features
Note
Be aware that the “Retain command” function may lead to uncertain plant operation, because
the real status of the valve is not secured any more.
Feature2.bit12 = TRUE enables the ‘retain last command if faulty’ function. An additional
button is shown in the diagnosis window.
The enable button in the diagnosis window gets active if the corresponding OS Permission is
given:
OS_Perm.bit26 = TRUE allows the operator to switch into ‘retain last command’ mode and
back.
Valve C_VALVE
18 Function Manual, 07/2016
Function
1.6 Sequence Test
Valve C_VALVE
Function Manual, 07/2016 19
Function
1.7 Visualization
1.7 Visualization
In the block icon of the valve the most important operation status are displayed (open, closed,
operating mode, fault). Refer to Variable Details. Control functions and detail information are
only available after opening the faceplate.
For status information the following variables exist:
Valve C_VALVE
20 Function Manual, 07/2016
Operating principle 2
2.1 Hardware inputs
FbkRun
FbkPos1 (VE1)
Valve C_VALVE
Function Manual, 07/2016 21
Operating principle
2.1 Hardware inputs
FbkPos2 (VE2)
ElAvail (VSB)
Overload
AutModLo (VVO)
Valve C_VALVE
22 Function Manual, 07/2016
Operating principle
2.1 Hardware inputs
Note
The behavior can be changed via feature bit options, , e.g. if a position switch (1-Signal =
Automatic; 0-Signal = Local) is used. In this case, 0-Signal at parameter AutModLo enables
starting and stopping via field switch signals StartLoc/StopLoc.
StopLoc (VSP)
StopLoc 0 = local stop: field switch stop signal Basic state 1-Signal
Format BOOL
The StopLoc parameter is used to stop the valve in local mode. This is a break contact, i.e.
the 0-signal de-energizes the valve.
By default, the local stop StopLoc is active in all operating modes.
Note
The behavior can be changed via feature bit options.
StartLoc (VSR)
StartLoc 1 = local start: field switch start signal Basic state 0-Signal
Format BOOL
The StartLoc parameter is used to start the valve in local mode. A rising edge at
StartLoc energizes the valve.
Note
The local start pushbutton must be pressed continuously until the FbkRun position feedback
arrives. For safety reasons, the signal is not memorized.
Local start is only possible if the valve is switched into local mode.
Note
The behavior can be changed via feature bit options.
Valve C_VALVE
Function Manual, 07/2016 23
Operating principle
2.1 Hardware inputs
Feature.bit3-12 can be used to adapt the Field switch signals to the requirement of the
plant.
Default settings
● In the default settings signal AutModLo is used as a repair switch (must have 1-Signal in
all operating modes) → Feature.bit8 = FALSE.
At the same time Feature.bit9 and Feature.bit10 must be FALSE and
Feature.bit12 is not relevant.
● A rising edge at StartLoc starts the valve in Local mode. The valve will be energized
continuously → Feature.bit5 = FALSE.
● Local start is only active if the Local mode is enabled → Feature.bit3 = FALSE.
● No start-up-warning is given in Local mode Feature.bit6 = FALSE.
● A falling edge at StopLoc stops the valve in Local mode. StopLoc is active in any mode
→ Feature.bit4 = TRUE.
If the valve is energized in Automatic mode or Manual mode, 0-Signal at parameter
StopLoc stops the valve together with the alarm message 'Local stop'.
● Switching an energized valve from Local mode to Automatic or Manual mode is possible
without interrupt → Feature.bit7 = TRUE.
● The Local mode needs to be enabled via operator station. The position switch does not
force the valve to Local mode → Feature.bit11 = FALSE.
Valve C_VALVE
24 Function Manual, 07/2016
Operating principle
2.1 Hardware inputs
● With Feature.bit5 = TRUE the local start is not memorized and the Local mode is an
inching mode. As long as signal StartLoc has 1-Signal the valve will be energized.
StartLoc = 0-Signal stops the valve.
● With Feature.bit6 = TRUE a start-up warning is created also in Local mode. Before
the start command is given to the valve, output WarnAct is set for time WarnTi. The start
command at StartLoc is not memorized, which means the start button must be pressed
continuously until the start-up warning is completed and the limit position is reached.
● With Feature.bit7 = TRUE switching an energized valve from Local mode to
Automatic/manual mode does not stop the valve, if the interlocking conditions are fulfilled.
This is only possible if Feature.bit8 = FALSE.
Note
Feature.bit7 is not evaluated if Feature.bit19 ("StartAut" switches drive to
Automatic mode) = TRUE. In this case Feature.bit7 is considered as TRUE.
Valve C_VALVE
Function Manual, 07/2016 25
Operating principle
2.1 Hardware inputs
Note
On order to have the same matrix chosen for the entire plant, Feature.bit9 and
Feature.bit12 should be set the same way for valves as for bi-directional drives and
dampers.
Valve C_VALVE
26 Function Manual, 07/2016
Operating principle
2.1 Hardware inputs
Valid combinations
Not all combinations are valid. Below you find possible feature settings
● AutModLo is used as position switch (1-Signal = Automatic; 0-Signal = Local)
● AutModLo is used as repair switch (local isolated) and must have 1-Signal in all operation
modes. 0-Signal at AutModLo will stop the valve.
Valve C_VALVE
Function Manual, 07/2016 27
Operating principle
2.1 Hardware inputs
If you have different requirements for your Field switch, please contact the competence center
for assistance.
Valve C_VALVE
28 Function Manual, 07/2016
Operating principle
2.2 Input interfaces
IntStaE
Structure variables:
IntStaE.Value Signal Basic state 1-Signal
Format BOOL
IntStaE.ST Signal status Default: 16#FF
Format BYTE
*) The evaluation of the essential start interlock in local mode can be suppressed via feature
bit setting:
If Feature2.bit1 = TRUE, the essential interlocks are not evaluated in local mode.
IntStart
Structure variables:
IntStart.Value Signal Basic state 1-Signal
Format BOOL
Valve C_VALVE
Function Manual, 07/2016 29
Operating principle
2.2 Input interfaces
IntOpE
Structure variables:
IntOpE.Value Signal Basic state 1-Signal
Format BOOL
IntOpE.ST Signal status Default: 16#FF
Format BYTE
*) The evaluation of the essential start interlock in local mode can be suppressed via feature
bit setting:
If Feature2.bit1 = TRUE, the essential interlocks are not evaluated in Local mode.
IntOper
Structure variables:
IntOper.Value Signal Basic state 1-Signal
Valve C_VALVE
30 Function Manual, 07/2016
Operating principle
2.2 Input interfaces
Format BOOL
IntOper.ST Signal status Default: 16#FF
Format BYTE
IntProtG
Note
Always connect output OutSig of the appropriate annunciation block to the protection interlock
of the valve, in order to consider possible time delays or simulations for both, message and
valve interlocking.
Structure variables:
IntProtG.Value Signal Basic state 1-Signal
Format BOOL
IntProtG.ST Signal status Default: 16#FF
Format BYTE
IntStop
Structure variables:
IntStop.Value Signal Basic state 1-Signal
Format BOOL
Valve C_VALVE
Function Manual, 07/2016 31
Operating principle
2.2 Input interfaces
IfFeature2.bit3 = TRUE, the stop interlock is also evaluated in Manual mode. This applies
to all manual modes, but stop delay StpDelTi is not considered in Manual mode..
Sporadic (VSPO)
Note
The valve status "OFF+activated" is indicated by a grey valve symbol plus additional indication
'SPO'.
The Sporadic ON/OFF function is made for operation in automatic mode, in order to switch
the valve on and off according to a process condition. If the valve is energized in manual or
local mode the status of interface Sporadic is ignored.
Valve C_VALVE
32 Function Manual, 07/2016
Operating principle
2.2 Input interfaces
MonOnly
Note
If the valve is in Out of Service mode it will not be forced to local mode but it will show “moving”
if the valve was started.
Valve C_VALVE
Function Manual, 07/2016 33
Operating principle
2.2 Input interfaces
For switching into manual mode via interface ManModOn or via GR_LINK, the interlocking level
is set according to the feature definition:
Note
Only one out of two feature bits 16 or 18 can be TRUE at the same time. If all Feature.bit16
and 18 are set to FALSE, the valve will be switched into Manual mode interlocked.
Mode change via program can be inhibited by setting the following Feature bits to FALSE:
Valve C_VALVE
34 Function Manual, 07/2016
Operating principle
2.2 Input interfaces
Note
Feature.bit25 of the corresponding group must be TRUE as well!
Using GR_LINK interface does not allow any individual or conditional connection. If this is
required, you have to use the interfaces AutModOn, ManModOn, LocModOn and
OoSModOn for the group-wise mode change.
Note
Out of service mode can not be selected via GR_LINK interface!
AutModOn
ManModOn
Valve C_VALVE
Function Manual, 07/2016 35
Operating principle
2.2 Input interfaces
Note
The button texts for the start and stop buttons in the faceplate of the valve can be configured
via Property Text 0 and Text 1. Default Texts: Text 0 = Off, Text 1 = On
LocModOn
Note
Switching into Local mode via LocModOn is not possible while the valve is energized.
OoSModOn
Note
Forcing to service mode has the highest priority and deenergizes the valve!
StaByEn (VSTB)
Valve C_VALVE
36 Function Manual, 07/2016
Operating principle
2.2 Input interfaces
NoFbk1 (VKR1)
NoFbk2 (VKR2)
Valve C_VALVE
Function Manual, 07/2016 37
Operating principle
2.2 Input interfaces
MsgEn (EMFR)
Note
If MsgEn has 0-Signal the valve fault is not shown in the summarizing indication of group and
route and not listed in the status call.
Exception: If StartAut has 1-Signal the valve fault is shown in the summarizing indication of
the group and route and it is listed in the status call.
MsgPrio
GrFltLck (EMZS)
GrStaLck (GFSO)
GrStaLck 1 = do not incl. in group sum. ind.+status call Basic state 0-Signal
Format BOOL
1-Signal at GrStaLck completely deselects the valve for the Group Summarizing fault and for
the Group Status Call.
The function is similar to interface GrFltLck but the valve is excluded from status call as well.
Valve C_VALVE
38 Function Manual, 07/2016
Operating principle
2.2 Input interfaces
LampTest (ELPZ)
Note
Using LampTest the lamp test interface at the C_PUSHBT module must not be connected.
Ack (VQIT)
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 valve. 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 Feature2.bit27 = 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 valve faceplate.
Valve C_VALVE
Function Manual, 07/2016 39
Operating principle
2.2 Input interfaces
StartAut (VBFE)
Note
Interface StartAut should not be connected with a continuous signal as a valve fault can
then not be acknowledged! If a continuous signal is required, one must take care that the
StartAut has signal zero when there is a fault.
Via feature bit setting the start command can be used to switch the valve to automatic mode:
Note
If Feature.bit19 = TRUE, the status of Feature.bit7 (No stop after switching from local
to auto/manual) is not evaluated. It is considered as TRUE.
Switching the valve from Local mode or Manual mode via to Automatic mode via StartAut
is only possible if the corresponding feature bits are enabled.
StopAut (VBFA)
Valve C_VALVE
40 Function Manual, 07/2016
Operating principle
2.2 Input interfaces
Note
If a valve belongs to more than one group or route, it may be necessary to use the inverted
permanent command on signal PeCmdOn of the associated groups or routes. But in this case
it has to be considered that in this case a shut down interrupt is not possible.
QuickStp (QSTP)
DSigBQ
Valve C_VALVE
Function Manual, 07/2016 41
Operating principle
2.2 Input interfaces
DSimAct
Netfault
Valve C_VALVE
42 Function Manual, 07/2016
Operating principle
2.2 Input interfaces
SimoStat
Structure variables:
SimoStat.Value Status Default: 16#00
Format BYTE
SimoStat.ST Signal Status Default: 16#FF
Format BYTE
Valve C_VALVE
Function Manual, 07/2016 43
Operating principle
2.2 Input interfaces
Feature2.bit29 = TRUE enables the user output function. The diagnosis view of the valve
faceplate shows the status indication and the button.
OS Permissions for User button:
UserFbk
UserPulse
Valve C_VALVE
44 Function Manual, 07/2016
Operating principle
2.2 Input interfaces
TEST_OSS
SimuStatus
SimuSave
MSG8_EVID
MSG8_EVID2
COMMAND
Valve C_VALVE
Function Manual, 07/2016 45
Operating principle
2.2 Input interfaces
ExtCmd
Valve C_VALVE
46 Function Manual, 07/2016
Operating principle
2.2 Input interfaces
Note
To permit the modification of the process values from the faceplates, they must not be
connected in the CFC.
FbkMonTi
The time for feedback monitoring FbkMonTi is used for the supervision of the contactor
feedback during the start-up of the valve. By default the value is preset to 2 seconds. The time
value can be increased if necessary.
With OS_Perm.bit31 = TRUE the operator is permitted to change the time for feedback
monitoring.
Note
The minimum feedback monitoring time is 2 seconds.
For switching off, the feedback monitoring time is always 2 seconds (adaptation not possible).
If an already energized valve loses the contactor feedback, FbkMonTi is not considered and
the valve will be stopped immediately.
MovMonTi
Valve C_VALVE
Function Manual, 07/2016 47
Operating principle
2.2 Input interfaces
Value in seconds
In normal control mode (automatic or manual mode), after giving contactor on command
ContOn te valve module checks whether the required limit position has been reached within
the time MovMonTi. In Local mode MovMonTi is not evaluated.
The parameter MovMonTi must be adjusted according to the valve run time. The set time
applies to both directions (open and close).
If the time value is exceeded the valve block creates the alarm message 'Move time'.
With OS_Perm.bit31 = TRUE the operator is permitted to change the Monitoring time from
pos1 to pos2.
LSDelTi
StaDelTi
StpDelTi
Valve C_VALVE
48 Function Manual, 07/2016
Operating principle
2.2 Input interfaces
WarnTi
Feature.bit6 = TRUE will trigger the start-up warning also in case of a local start command
StartLoc and the contactor ON command ContOn is delayed by this time.
Note
For security reasons the local start command is not memorized and the button must be pressed
continuously until the timer WarnTi has elapsed and the limit position has been reached.
Valve C_VALVE
Function Manual, 07/2016 49
Operating principle
2.2 Input interfaces
UserStatus
Note
Make sure that modifications in standard faceplates are documented and saved. CEMAT
updates will overwrite your modifications.
SelFp1 (UserFace)
Note
The button description for the User Function button in the standard faceplate is fixed, but the
tooltip text can be entered via Property 'OS additional text'. Default value can not be configured
as a property of the block input. Value can only be defined in the CFC.
Valve C_VALVE
50 Function Manual, 07/2016
Operating principle
2.2 Input interfaces
With OS_Perm.bit16 = TRUE the operator can start the maintenance interval.
MaiInt (MAI_INT)
MaiRL (MAI_REQL)
Valve C_VALVE
Function Manual, 07/2016 51
Operating principle
2.2 Input interfaces
Note
If the block is in normal operation (none of the above mentioned situations) the inputs
Feature, Feature2 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.
Valve C_VALVE
52 Function Manual, 07/2016
Operating principle
2.2 Input interfaces
Note
Both, the Feature bit settings of the Feature Master block and the Feature bit settings at the
block inputs Feature and Feature2 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, Feature2 and OS_Perm are transferred to the CEMAT block, when the module
is in configuration 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.
Valve C_VALVE
Function Manual, 07/2016 53
Operating principle
2.2 Input interfaces
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.
Valve C_VALVE
54 Function Manual, 07/2016
Operating principle
2.2 Input interfaces
Feature2
Note
It is not allowed to connect any logic to Feature2 input.
Valve C_VALVE
Function Manual, 07/2016 55
Operating principle
2.2 Input interfaces
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!
Valve C_VALVE
56 Function Manual, 07/2016
Operating principle
2.3 Group and Object links
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.
A valve can be linked to two groups or routes via GR_LINK1 and GR_LINK2. If a valve 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 valve faceplate.
Via additional feature bit settings, control commands can also be transmitted through the group/
route link interface.
● With Feature.bit25 = TRUE the mode change commands from the group or route are
automatically transmitted to the allocated drives/devices. No further connection to
AutModOn, ManModOn and LocModOn is needed. Of course, the permission for the
individual modes must be available and Feature.bit25 of the group or route must be
TRUE as well.
See also "Interfaces for mode change".
Note
Out of Service mode can not be selected via GR_LINK interface!
Valve C_VALVE
Function Manual, 07/2016 57
Operating principle
2.3 Group and Object links
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
Valve C_VALVE
58 Function Manual, 07/2016
Operating principle
2.3 Group and Object links
MUX_LINK
Note
If a C_MUX block is used, the programming order is very important. The C_MUX must be called
before the valve block!
If the same C_MUX block is connected to more than one object (e. g. the valve 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
Valve C_VALVE
Function Manual, 07/2016 59
Operating principle
2.3 Group and Object links
Note
Check the runtime sequence! The C_MUX module must be called before the valve. For the
other modules the run sequence is as follows: first the 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.
Valve C_VALVE
60 Function Manual, 07/2016
Operating principle
2.3 Group and Object links
The valve block collects the information and forwards it to the group (or route). The result is
as follows:
● All objects, linked to the valve are listed in the valve object list and in the group (or route)
object list (one level below the valve).
● All objects, linked to the valve are highlighted in the process picture with button "Show
related objects".
● The warnings of all objects, linked to the valve are included in the external warning indication
of the valve and in the summarizing warning indication of the group (or route).
● The faults of all objects, linked to the valve are included in the external fault indication of
the valve 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.
● Block icons for Option 4: The warnings of all objects, linked to the valve are indicated by
yellow color of the Block icon (HAC).
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!
Valve C_VALVE
Function Manual, 07/2016 61
Operating principle
2.3 Group and Object links
O_LINKQ
Structure variables:
O_LINKQ.iDB Instance DB master object
Format INTEGER
O_LINKQ.iDW DW number NO_OF_FT in master object
Format INTEGER
O_LINKQ.Command Group / Route Command
Format BYTE
O_LINKQ.Status Status master object
Format BYTE
Valve C_VALVE
62 Function Manual, 07/2016
Operating principle
2.3 Group and Object links
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.
Valve C_VALVE
Function Manual, 07/2016 63
Operating principle
2.3 Group and Object links
O_LINK
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
Note
If annunciations, measurements or process feedback blocks belong to the valve, 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 valve.
Valve C_VALVE
64 Function Manual, 07/2016
Operating principle
2.4 Input/Output interfaces
ResTimOS
MaiRTm
MaiRTh
MaiCo
MaiCoh
MaiCntSt
Valve C_VALVE
Function Manual, 07/2016 65
Operating principle
2.4 Input/Output interfaces
MaiCntTr
MaiFtDur
MAI_STA
MaiCorr
MaiCyc
Valve C_VALVE
66 Function Manual, 07/2016
Operating principle
2.5 Output interfaces
INTFC_OS
VISU_OS
VISU_OS Interface to OS
Format BYTE
Interface to OS
For more information see Variable details.
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.
STATUS3
STATUS3 Interface to OS
Format DWORD
Interface to OS
For more information see Variable details.
Valve C_VALVE
Function Manual, 07/2016 67
Operating principle
2.5 Output interfaces
ALARM
FeatureOut
FeatureOut2
OS_PermOut
OS_PermLog
FWCopyMaster
Valve C_VALVE
68 Function Manual, 07/2016
Operating principle
2.5 Output interfaces
FW2CopyMaster
OSCopyMaster
OpSt_Out
DelayCon
NO_OF_I
FT1
Valve C_VALVE
Function Manual, 07/2016 69
Operating principle
2.5 Output interfaces
Structure variables:
FT1.D1 Instance DB Object
Format INT
FT1.D2 Instance DB Master Object
Format INT
FT1.D3 Object Type
Format INT
FT1.D4 Status word object
Format WORD
Valve C_VALVE
70 Function Manual, 07/2016
Operating principle
2.5 Output interfaces
PosSig1 (VVS1)
Structure variables:
PosSig1.Value Signal
Format BOOL
PosSig1.ST Signal status
Format BYTE
PosSig2 (VVS2)
Valve C_VALVE
Function Manual, 07/2016 71
Operating principle
2.5 Output interfaces
Structure variables:
PosSig2.Value Signal
Format BOOL
PosSig2.ST Signal status
Format BYTE
DynFlt (VST)
Note
In the following cases the valve fault cannot be acknowledged:
● If the ON-command is permanently active;
● if the valve has not reached the de-energized limit position. (corresponds to welded
contactor in C_DRV_1D and C_DRV_2D)
Output DynFlt is used as message trigger of annunciation blocks (in case of drive fault
annunciations), see interface MsgTrigg of C_ANNUNC block or MsgTrig1 – MsgTrig7 of
C_ANNUN8 block.
Output DynFlt is also used transmit "not empty" information to the group in case of a trip of
a running equipment, see interface MatFlt of C_GROUP block. Only drives/devices which
are involved in the material transport are connected to interface MatFlt of the group.
The information can also be transmitted to the group via feature bit setting:
Valve C_VALVE
72 Function Manual, 07/2016
Operating principle
2.5 Output interfaces
Fault (SST)
Fault Fault
Format BOOL
A 1-Signal at output Fault means that at least one fault is present.
LaStopRe
If Feature2.bit11 = TRUE the stop code and the time is written to the output LaStopRe.
Structure variables:
LaStopRe.Value Reason
Format INT
LaStopRe.STime Stop time
Format STRING [22]
Structure variable LaStopRe.Value contains the code for the last stop reason. The texts are
defined in a dataset in @Overview1.pdl (Master_Stoptext_Dataset).
The following reasons may stop a valve.
Valve C_VALVE
Function Manual, 07/2016 73
Operating principle
2.5 Output interfaces
WarnAct (HORN)
With Feature.bit6 = TRUE the output WarnAct is also created with local start command
StartLoc.
Note
For security reasons the local start command StartLoc is not memorized and the button must
be pressed continuously until the timer WarnTi has elapsed and the limit position has been
reached.
RunSigSp
Valve C_VALVE
74 Function Manual, 07/2016
Operating principle
2.5 Output interfaces
SimActQ
AutoAct
ManuAct
Note
Connection is not needed if Feature.bit26 = TRUE
LocalAct
Note
Connection is not needed if Feature.bit26 = TRUE
Valve C_VALVE
Function Manual, 07/2016 75
Operating principle
2.5 Output interfaces
OoSAct
Note
Connection is not needed if Feature.bit26 = TRUE
MaintRQ
MaintAL
MaiRTm_Q
MaiRTh_Q
Valve C_VALVE
76 Function Manual, 07/2016
Operating principle
2.5 Output interfaces
MaiCo_Q
MaiTr_Q
MaiFt_Q
MaiCyc_Q
Valve C_VALVE
Function Manual, 07/2016 77
Operating principle
2.6 Hardware outputs
ContOn (VBE)
ContOn Contactor ON
Format BOOL
The output ContOn is used to trigger the main contactor.
Lamp1 (VL1)
Lamp2 (VL2)
UserOut
Valve C_VALVE
78 Function Manual, 07/2016
Operating principle
2.6 Hardware outputs
ST_Worst
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 signals DSigBQ, DSimAct, IntStaE, IntStart,
IntOpE, IntOper, IntProtG and SimoStat is transmitted to outputs PosSig1 and
PosSig2.
Valve C_VALVE
Function Manual, 07/2016 79
Operating principle
2.7 Engineering Errors
ErrorNum
Valve C_VALVE
80 Function Manual, 07/2016
Operating principle
2.7 Engineering Errors
Note
Only one error number can be indicated at a time!
Valve C_VALVE
Function Manual, 07/2016 81
Operating principle
2.7 Engineering Errors
Valve C_VALVE
82 Function Manual, 07/2016
Time characteristics 3
All CEMAT drive blocks must be called before the associated route or group.
If C_MUX blocks are used, the C_MUX blocks must be called before the drive block.
Valve C_VALVE
Function Manual, 07/2016 83
Time characteristics
Valve C_VALVE
84 Function Manual, 07/2016
Message characteristics 4
The module uses two ALARM_8 modules to generate annunciations.
*) The message class for MSG8_EVID SIG1 to SIG8 and MSG8_EVID2 SIG6 is by default
configured as “Alarm - high".
In case of a warning drive the message class for MSG8_EVID SIG1 to SIG8 and MSG8_EVID2
must be changed to “Warning - high" and the Feature2.bit2 must be configured.
Feature2.bit2 = TRUE changes the block to warning mode. This results in a yellow
indication for Group status call and block icon and the group start is not interrupted by a trip
of this valve.
Valve C_VALVE
Function Manual, 07/2016 85
Message characteristics
The operating messages for “Local start” and “Local stop” are only created if Feature2.bit0
= TRUE.
1*) Via Plausibility logic only one of three indications (Available, Overload or Local) is given.
All other indications are shown simultaneously.
Valve C_VALVE
86 Function Manual, 07/2016
Message characteristics
2*) The priority between Available and Overload can be reversed via 1-Signal at input
MsgPrio.
3*) If the motor is not running, contactor feedback fault results in a dynamic fault.
Acknowledgement is not possible as long as a contactor feedback is present.
4*) The messages for "Process Feedback fault", "Protection fault" and "Simocode fault"
are not created by the drive block itself, but by other CEMAT blocks (C_PROFB, C_ANNUNC
and C_SIMOS).
Valve C_VALVE
Function Manual, 07/2016 87
Message characteristics
Valve C_VALVE
88 Function Manual, 07/2016
Module States 5
Variable VISU_OS:
Valve C_VALVE
Function Manual, 07/2016 89
Module States
Valve C_VALVE
90 Function Manual, 07/2016
Operator Commands 6
Refer to the Variable details for the assignment of the command word COMMAND and external
command word ExtCmd (e. g. for Panel interface).
In case the block receives two commands in the same CPU cycle, the command from interface
COMMAND has higher priority.
Operator commands are restricted by the following criteria:
● Feature bit settings:
Via feature bits the complete function can be enabled or disabled.
● OS PermissionLog:
Via OS Permission it can be decided to allow or not to allow operator action.
The OS PermissionLog is build dependent on the OS Permissions and the actual status of
the object. (Example: Group start is enabled via OS Permission, but if the group is already
running completely the OS_PermLog = FALSE and the button “start” is disabled).
● Operation authorization levels
Via WinCC User Administration Operation authorization levels are defined. Each user gets
the permission to operate certain levels in certain areas.
The currently logged in user can carry out any operation belonging to this level.
● The Operation authorization level for each type of operation is defined at the block
parameters in the CFC and can be modified. This allows modular (instance specific)
adjustments for individual operator commands.
If additional authorization levels are defined in WinCC, operation can be permitted to
restricted personnel only.
The following table shows the Operator commands for C_VALVE and the required settings:
Valve C_VALVE
Function Manual, 07/2016 91
Operator Commands
Valve C_VALVE
92 Function Manual, 07/2016
Feature Bits 7
Via Feature bits certain functions of the CEMAT block can be enabled and disabled and the
behavior of the block can be configured.
The bits in structure Feature and FeatureOut are used as follows:
Valve C_VALVE
Function Manual, 07/2016 93
Feature Bits
Feature2
The bits in Structure Feature2 and FeatureOut2 are used as follows:
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.
Valve C_VALVE
94 Function Manual, 07/2016
Feature Bits
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 word Feature/Feature2
are transferred into the internal memory of the module.
Note
Do not connect any logic to input Feature and Feature2
Valve C_VALVE
Function Manual, 07/2016 95
Feature Bits
Valve C_VALVE
96 Function Manual, 07/2016
OS Permissions 8
Via OS Permissions operator actions can be enabled or disabled.
The bits in OS_Perm, OS_PermOut and OS_PermLog are used as follows:
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.
Valve C_VALVE
Function Manual, 07/2016 97
OS Permissions
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.
Valve C_VALVE
98 Function Manual, 07/2016
I/O-bar of C_VALVE 9
C_VALVE
Valve C_VALVE
Function Manual, 07/2016 99
I/O-bar of C_VALVE
Valve C_VALVE
100 Function Manual, 07/2016
I/O-bar of C_VALVE
Valve C_VALVE
Function Manual, 07/2016 101
I/O-bar of C_VALVE
Valve C_VALVE
102 Function Manual, 07/2016
I/O-bar of C_VALVE
Valve C_VALVE
Function Manual, 07/2016 103
I/O-bar of C_VALVE
Valve C_VALVE
104 Function Manual, 07/2016
I/O-bar of C_VALVE
Valve C_VALVE
Function Manual, 07/2016 105
I/O-bar of C_VALVE
Valve C_VALVE
106 Function Manual, 07/2016
I/O-bar of C_VALVE
Valve C_VALVE
Function Manual, 07/2016 107
I/O-bar of C_VALVE
Valve C_VALVE
108 Function Manual, 07/2016
OS-Variable table 10
C_VALVE
Valve C_VALVE
Function Manual, 07/2016 109
OS-Variable table
Valve C_VALVE
110 Function Manual, 07/2016
Variable details 11
11.1 Variable details COMMAND
Internal structure of the Commands, Alarms, Visualization status and Interface word:
Valve C_VALVE
Function Manual, 07/2016 111
Variable details
11.2 Variable details ExtCmd
Valve C_VALVE
112 Function Manual, 07/2016
Variable details
11.3 Variable details MSG8_EVID
Valve C_VALVE
Function Manual, 07/2016 113
Variable details
11.4 Variable details VISU_OS
Valve C_VALVE
114 Function Manual, 07/2016
Variable details
11.5 Variable details INTFC_OS
Valve C_VALVE
Function Manual, 07/2016 115
Variable details
11.6 Variable details STATUS
Valve C_VALVE
116 Function Manual, 07/2016
Variable details
11.7 Variable details STATUS2
Valve C_VALVE
Function Manual, 07/2016 117
Variable details
11.8 Variable details STATUS3
Valve C_VALVE
118 Function Manual, 07/2016
Variable details
11.9 Variable details MAI_STA
Valve C_VALVE
Function Manual, 07/2016 119
Variable details
11.9 Variable details MAI_STA
Valve C_VALVE
120 Function Manual, 07/2016