C_PROFB_009
C_PROFB_009
Operating principle 2
Time characteristics 3
PCS 7
Message characteristics 4
CEMAT
Process Feedback C_PROFB (V9.1) 5
Module States
Operator Commands 6
Function Manual
Feature Bits 7
OS Permissions 8
I/O-bar of C_PROFB 9
OS-Variable table 10
Variable details 11
11/2020
A5E50300996-AA
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 Block name and installation position .................................................................................... 5
1.2 General Function description................................................................................................ 6
1.3 Change of operation mode .................................................................................................. 9
1.4 Configuration state ............................................................................................................ 10
1.5 Optional features ............................................................................................................... 11
1.6 Sequence Test.................................................................................................................... 12
1.7 Visualization ...................................................................................................................... 13
2 Operating principle.............................................................................................................................. 15
2.1 Input interfaces ................................................................................................................. 15
2.1.1 Inputs for testing and as Interface to the OS ....................................................................... 19
2.1.2 Maintenance...................................................................................................................... 20
2.1.3 Process Parameters ............................................................................................................ 21
2.1.4 Process parameters for Maintenance function:.................................................................... 25
2.1.5 OS Permissions and Features:............................................................................................. 26
2.1.6 Connection to EventTs ....................................................................................................... 30
2.2 Group and Object links....................................................................................................... 31
2.3 Input/Output interfaces...................................................................................................... 33
2.4 Output interfaces............................................................................................................... 35
2.4.1 Outputs for testing and as Interface to the OS .................................................................... 35
2.4.2 Output status for connection to other blocks ...................................................................... 37
2.5 Engineering Errors ............................................................................................................. 42
3 Time characteristics ............................................................................................................................. 45
4 Message characteristics....................................................................................................................... 47
5 Module States ...................................................................................................................................... 49
6 Operator Commands............................................................................................................................ 51
7 Feature Bits.......................................................................................................................................... 53
8 OS Permissions..................................................................................................................................... 55
9 I/O-bar of C_PROFB............................................................................................................................... 57
10 OS-Variable table ................................................................................................................................. 61
11 Variable details .................................................................................................................................... 63
11.1 Variable details COMMAND ................................................................................................ 63
11.2 Variable details MSG8_EVID................................................................................................ 64
11.3 Variable details STATUS ...................................................................................................... 65
Type/Number
Calling OBs
All CEMAT Functions must be installed in the same OB and between the Runtime
groups OB1_START and OB1_END.
By default, the Runtime groups OB1_START and OB1_END are installed in OB1 (which had
advantages related to comfort and cycle time).
As other PCS 7 functions, such as CMT require the installation of the blocks in a cyclic interrupt
OB, we recommend – especially for green field plants – the installation of the CEMAT functions
in a cyclic interrupt OB (e. g. OB34 or OB35).
In this case the functions from runtime groups OB1_START and OB1_END must be called in this
cyclic interrupt OB as well. Please follow the instruction of Engineering Manual
14_Tips_Tricks_009.doc.
Note
It is not permitted to install the CEMAT Application Program in different OBs. In case of an
installation in a cyclic interrupt OB, all CEMAT blocks must be called in the same OB cycle. PCS 7
APL blocks MUST be installed in a cyclic interrupt OB.
If Feature.bit31 = FALSE, the process feedback monitoring starts after the “Start-up
monitoring time” PFOnDTi has elapsed.
All further functions are optional and can be defined through corresponding parameterization
of the Feature bits and block parameters.
Signal evaluation:
The display and alarm behavior of the block can be configured through parameterization. Some
functions depend on Feature bit settings:
• After starting the drive in Automatic or in Manual mode, the process feedback must be
available within "Start-up monitoring time" PFOnDTi.
• If Feature.bit13 = TRUE the process feedback is monitored in all operation modes.
• While the drive is running, the process feedback must always be available, but fluttering is
tolerated if the flutter suppression time FlutTm > 0.
(only for binary, continuous input signals)
• The shutdown monitoring can be enabled via Feature bit setting. In this case, after the drive
has been stopped, the process feedback must be off within "shutdown monitoring
time" PFOfDTi.
• The enable messages interface MsgEn can be used in order to prevent an onrush of messages
in case of power failure. The message generation in the block is frozen and neither incoming
nor outgoing messages are created.
Via Feature bit setting the "message enable" can be carried out internally, via O_LINK
connection.
• The fault status can be memorized (kept up to the next successful startup of drive) or not,
depending on a Feature bit setting.
• Via Feature bit settings the process feedback block can be switched into warn mode. In this
case Output OutSig remains "1" in case of a process feedback fault.
If the block is switched to simulation, OutSig is set to 1-Signal and output ProFB corresponds
to the status of the drive (1-Signal if drive has been started, 0-Signal if drive has been stopped).
The change to simulation is carried out via diagnosis window or automatically if the AS is
switched to sequence test mode.
OS_Perm.bit15 must be TRUE to enable switching to simulation via OS.
Process parameters
Through process parameters the following values can be configured online:
If Feature.bit13 = TRUE the process feedback monitoring is enabled in all operating modes.
In case of a process feedback fault the motor will be stopped and the Process feedback block
creates an alarm message.
Note
Please keep in mind that if the Process Feedback monitoring is activated in all operating modes,
even in local mode the Process Feedback fault must be acknowledged before a restart of the
drive (either through Operator station or through input Ack).
This requires a phone-call to the Operator or an acknowledgement button in the field.
Note
For a running plant this means that for any modification of Feature bits or OS Permissions the
module must be set to Out of Service mode.
Note
As the process feedback block is always linked to a drive block, the Fault reset function must be
enabled for the drive and for the C_PROFB block.
1.7 Visualization
In the block icon of the process feedback block the most important operation status are
displayed (signal status, fault, warning). Refer to Variable Details. Control functions and detail
information are only available after opening the faceplate.
For status information the following variables exist:
InSig (IN_SIG)
Note
The CFC does not permit direct connection of Structure inputs to the binary process image,
because of different formats. You must either use block input InSigB instead or insert a PCS 7
driver block Pcs7DiIn or a converter (StruDiOu).
Structure variables:
InSig.Value Value Basic state 1-Signal
Format BOOL
InSigB
Note
Using binary input InSigB instead of Structure input InSig, Text 0 and Text 1 must still be
configured at structure input InSig.Value.
PV
PV Input Signal
Format STRUCT
Interface PV is used to monitor an analog input as process feedback signal. The signal is eval‐
uated together with the running signal RunSig of the motor.
Via feature bit settings the kind of evaluation is configured:
Note
The CFC does not permit direct connection of Structure inputs to the analog process image,
because of different formats. You must either insert a PCS 7 driver block Pcs7AnIn or a converter
(StruAnOu).
Structure variables:
PV.Value Value Default: 0.0
Format REAL
PV.ST Signal status Default: 16#FF
Format BYTE
MsgEn (ENAL)
Note
If MsgEn has 0-Signal the process feedback fault is not shown in the summarizing indication of
group and route and not listed in the status call.
Via feature bit setting, the message enable can be transmitted through the O_LINK interface.
With Feature.bit16 = TRUE the status of MsgEn from the drive block is transmitted to the
process feedback block. No further connection to MsgEn of the process feedback block is
required.
Ack (ACK)
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 process feedback block. See Engineering Manual, chapter AS-Engineering.
Via Feature bit settings the internal acknowledge can be disabled, in order to allow exclusively
the acknowledgement via interface Ack:
With Feature.bit19 = TRUE only the interface Ack is active for acknowledgement.
Note
If additional Fault Reset is enabled the fault status bits are not automatically acknowledged
with Ack. After clearing the fault the Operator has to press “Fault reset” in the faceplate of the
process feedback block.
SimuStatus
DisSeqTest
SimuSave
MSG8_EVID
COMMAND
2.1.2 Maintenance
MaiCntOn
Note
To permit the modification of the process values from the faceplates, they must not be
connected in the CFC.
PFOnDTi
PFOfDTi
ProFbTol
Flutter suppression
If the drive is running, a loss of the Process feedback may happen, e. g. due to an uncertain
signal. The flutter suppression function can be used in order not to stop the drive immediately
in this case.
For activating the flutter suppression, parameter FlutTm must be > 0
The following time diagram shows the function:
FlutTm
SigOkTm
StUpLim
ShDoLim
With OS_Perm.bit16 = TRUE the operator can start the maintenance interval.
MaiInt (MAI_INT)
MaiRL (MAI_REQL)
Note
If the block is in normal operation (none of the above mentioned situations) the inputs Feature
and OS_Perm are only read from the internal memory.
The HMI always shows the status of the internal memory.
Note
For a running plant this means that for any modification of Feature bits or OS Permissions the
module must be set to Out of Service mode.
Note
Both, the Feature bit settings of the Feature Master block and the Feature bit settings at the block
input Feature are only transferred to the internal memory if they are consistent (ErrorNum =
0).
FeatMaster
FeatMaster Use OS permission and Feature bits from master Basic state 1-Signal
Format BOOL
Input FeatMaster is set to “S7-link = false” (cannot be connected).
With 1-Signal at input FeatMaster, the selected bits of the Feature Master block
inputs Feature and OS_Perm are transferred to the CEMAT block, when the module is in
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.
AutoFeatMast
AutoFeatMast Auto take-over of feature and OS perm. bits Basic state 1-Signal
Format BOOL
1-Signal at input AutoFeatMast enables the automatic take-over of the Feature bit and OS
Permission settings from Feature Master (without being in configuration mode). This only
works if input FeatMaster has 1-Signal and if the drive is stopped.
If the connected drive is running and the Feature bits or OS Permissions in the Feature Master
block are changed, the Preset window of the process feedback block displays a value > 0 as
“Difference to feature master”. The take-over will be carried out with the next stop of the drive
and the counter will be reset.
OS_Perm
Note
It is not allowed to connect any logic to OS_Perm input.
OpSt_In
Feature
Note
It is not allowed to connect any logic to Feature input.
EventTsIn
Note
Block EventTs must be installed in a Cyclic interrupt OB. The installation of block EventTs in OB1
is not permitted and will not work!
Group/Route links
There is no direct link to the group or route.
The drive block collects the information and forwards it to the group (or route). The result is as
follows:
• All objects, linked to the drive are listed in the drive object list and in the group (or route)
object list (one level below the drive).
• All objects, linked to the drive are highlighted in the process picture with button "Show
related objects".
• The warnings of all objects, linked to the drive are included in the external warning indication
of the drive and in the summarizing warning indication of the group (or route).
• The faults of all objects, linked to the drive are included in the external fault indication of the
drive and in the summarizing fault indication of the group (or route).
• In case of a dynamic fault during the startup of the group, the group start will be interrupted.
Via additional feature bit settings, control commands can also be transmitted through the object
link interface.
With Feature.bit16 = TRUE the status of MsgEn from the drive block is transmitted to the
process feedback block. No further connection to MsgEn of the process feedback block is
required.
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.Com‐ Group / Route Command Default: 16#00
mand
Format BYTE
O_LINK.Status Status master object Default: 16#00
Format BYTE
Note
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!!!
ResTimOS
MaiRTm
MaiRTh
MaiCntSt
MAI_STA
MaiCorr
MaiCyc
MaiFlutCyc
MaiFlutCyc Number of times the flutter monitoring was star‐ Default: 16#00
ted
Format DWORD
Every time the Flutter suppression FlutTm is triggered, counter MaiFlutCyc is increased by
one. The value is displayed as “Fluttering cycles” in the Maintenance view of the block.
ProFbCV
STATUS
STATUS Interface to OS
Format DWORD
Interface to OS
For more information see Variable details.
ALARM
DelayCon
FeatureOut
OS_PermOut
OS_PermLog
FWCopyMaster
OSCopyMaster
OpSt_Out
ProFB
If Feature.bit31 = TRUE, the process feedback is monitored after the electrical feedback
arrived and output ProFB is set to 1-Signal as soon as the process feedback is available.
If Feature.bit31 = FALSE, the process feedback monitoring starts after the start-up of the
drive (after Start-up monitoring time PFOnDTi has elapsed) and output ProFB is delayed by this
time.
Structure variables:
ProFB.Value Signal Basic state 1-Signal
Format BOOL
ProFB.ST Signal status Default: 16#FF
Format BYTE
OutSig
Feature.bit14 = FALSE: In case of a process feedback fault while starting the drive, the
output signal OutSig will be "good" immediately after the trip, because after the drive has been
stopped, the situation is ok.
Feature.bit14 = TRUE: The fault status of OutSig is kept up to a successful startup of the
drive.
If Feature.bit29 = TRUE the process feedback block is configured for warning mode and
output OutSig is always "1" (and will not stop the drive).
Note
Special Logic for Warning devices! For warning devices the warning mode at C_PROFB must
activated as well. In order to stop the warning device by a fault (warning!) of the C_PROFB you
have to connect output Fault of the C_PROFB to the Protection interlock IntProtA of the
drive.
Note
If Fault reset is enabled at the C_PROFB block (Feature.bit12 = TRUE) or if Fault reset is
enabled at the C_DRV_1D/C_DRV_2D block, Feature.bit14 of C_PROFB must be FALSE!
Structure variables:
OutSig.Value Value
Format BOOL
OutSig.ST Signal status
Format BYTE
Structure variable OutSig.Value has a Property Text 1. Via this property, the sensor type (max.
2 characters, e. g. "S1") can be added, for display in the block icon of the C_PROFB block.
Text 1 is displayed in the block icon of C_PROFB.
Fault
FlutAct
AckQ
SimActQ
MaintRQ
MaintAL
MaiRTm_Q
MaiRTh_Q
MaiCyc_Q
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 InSig(or InSigB), the analog value PV and the internal
simulation is transmitted to outputs OutSig and ProFB.
MsgAckn1
TimeStamp
CountDiffer
ErrorNum
Note
Only one error number can be indicated at a time!
The Event text (Message text in CFC) for SIG1 to SIG6 must be configured for each instance.
Each message is classified as process fault (P) (Fault class).
Still faulty message:
During start in automatic mode, any failure which inhibits the drive start leads to an interrupt of
the start procedure and must therefore be reported by an alarm message.
PCS7 can create the (incoming) alarm message only once and does not support the repetition
of incoming alarm messages without outgoing message. For this reason, CEMAT creates a
Message “Still faulty” for any alarm message which needs to be repeated.
The current operational state of the drive is automatically taken into consideration during the
fault analysis.
• no superfluous fault annunciations are created
• the operator does not need to manually disable/suppress any annunciations.
Through connection of the control voltage signal to interface enable messages MsgEn, the
messages of the block are suppressed in case of a power failure (in order to avoid misleading
alarms and annunciation storm).
A detailed description of the individual Feature bits can be found in the chapters above.
Please consider that the Feature bit settings can only be changed in configuration state. For a
running plant this means that the drive block has to be in Out of Service mode.
If the block is in configuration state and the feature bit settings are consistent (ErrorNum = 0),
the Feature Master block settings and the status of Feature are transferred into the internal
memory of the module.
Note
Do not connect any logic to input Feature
A detailed description of the individual OS Permission bits can be found in the chapters above.
Please consider that the OS Permission settings can only be changed in configuration state. For
a running plant this means that the drive block has to be in Out of Service mode.
If the block is in configuration state the Feature Master block settings and the status of
OS_Perm are transferred into the internal memory of the module.
Note
Do not connect any logic to input OS_Perm.