0% found this document useful (0 votes)
30 views

C_PROFB_009

Uploaded by

Priyanka
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
30 views

C_PROFB_009

Uploaded by

Priyanka
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 66

Function 1

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.

Siemens AG A5E50300996-AA Copyright © Siemens AG 2020.


Digital Industries Ⓟ 03/2021 Subject to change All rights reserved
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents

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

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 3
Table of contents

11.4 Variable details MAI_STA .................................................................................................... 66

Process Feedback C_PROFB (V9.1)


4 Function Manual, 11/2020, A5E50300996-AA
Function 1
1.1 Block name and installation position

Type/Number

Module name: C_PROFB


Module no.: FB1008

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.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 5
Function
1.2 General Function description

1.2 General Function description


Block C_PROFB can monitor binary or analog process feedback signals of a drive, such as speed
monitor or pressure signals. C_PROFB must always be linked to a drive block C_DRV_1D or
C_DRV_2D, because it needs to exchange information with the drive block.
In case of a process feedback fault the drive will be stopped via protection interlock. The alarm
is created by the process feedback block.
Depending on three different phases, during startup of the drive, during shutdown of the drive
or while the drive is running, the process feedback is evaluated differently, and different
messages are created in case of a fault:
• The duration of the “startup phase” can be configured via the start-up monitoring
time PFOnDTi. After this time the process feedback must be available.
• In the “running phase” the process feedback must stay, otherwise it comes to a trip, except
the flutter suppression is enabled (flutter suppression time FlutTm > 0). In this case the
interruption of the process feedback is tolerated for a certain time.
Flutter suppression is only possible for continuous inputs (not for pulses or analog values)
• The duration of the “shutdown phase” can be configured via shutdown monitoring
time PFOfDTi. After this time the process signal must be 0.

Read Process feedback signal:


The process feedback block can either evaluate a digital input or an analog value. The digital
input may be a continuous signal or pulses. The configuration is done via Feature settings:

BitNr. Function/Features Default val‐


ue
15 Analog process value monitoring FALSE
27 Process Feedback pulse evaluation FALSE

If Feature.bit15 = FALSE the binary input InSig or InSigB is evaluated as process


feedback signal. The process feedback may be available as continuous signal (1-Signal after the
drive is running) or pulses, depending on Feature.bit27:
• If Feature.bit27 = FALSE, input InSig or InSigB must be a continuous signal. The
input must get "1" after the drive is running and it must get "0" after the drive has been
stopped (except "shutdown monitoring" is disabled).
• If Feature.bit27 = TRUE, input InSig or InSigB must be pulsing after the drive is
running and pulses must stop after the drive has been stopped (except "shutdown
monitoring" is disabled).
If Feature.bit15 = TRUE, the analog input signal PV is evaluated as process feedback
signal. The value must exceed the startup OK limit StUpLim after the drive is running and must
be below Shutdown OK limit ShDoLim after the drive has been stopped (except "shutdown
monitoring" is disabled).

Process Feedback C_PROFB (V9.1)


6 Function Manual, 11/2020, A5E50300996-AA
Function
1.2 General Function description

Output of the Process signal:


The status of the process feedback signal is transmitted to the drive via output ProFB. 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. After output ProFB is set the drive status
changes from "startup" to "running".
By default setting the process feedback must arrive and stay within the “Start-up monitoring
time” PFOnDTi. This behavior can be changed in order to monitor the process feedback after the
“Start-up monitoring time” PFOnDTi has elapsed.
Default Feature bit setting:

BitNr. Function/Features Default val‐


ue
31 Process feedback monitoring also during start-up (PFOnDTi) TRUE

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:

BitNr. Function/Features Default val‐


ue
13 Process feedback monitoring in all operating modes FALSE
14 Keep fault status up to new startup of drive FALSE
16 O_LINK used for message enable from drive (int. MsgEn) FALSE
29 Warning mode active FALSE
30 Shutdown monitoring TRUE

• 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.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 7
Function
1.2 General Function description

• 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.

Enable, block or simulation functions:


Under certain circumstances it can be necessary to switch the process feedback block to
simulation mode. Switching to simulation requires an OS Permission:

BitNr. Function/OS Permission Default val‐


ue
15 1 = Operator can change to simulation TRUE
18 1 = Enable Single step mode change TRUE

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:

• PFOnDTi (s) Start-up monitoring time for Process feedback supervision


• PFOfDTi (s) Shutdown monitoring time for Process feedback supervision
• ProFbTol (x 0.1s) Tolerance value in case of pulse evaluation
• FlutTm Flutter suppression time [s]
• SigOkTm Additional monitoring time [s] after fluttering suppression time
elapsed
• StUpLim Startup OK limit (PV must exceed this limit after Startup)
• ShDoLim Shutdown OK limit (PV must go below this limit after Shutdown)

Process Feedback C_PROFB (V9.1)


8 Function Manual, 11/2020, A5E50300996-AA
Function
1.3 Change of operation mode

1.3 Change of operation mode


The process feedback block always has the same mode as the drive block to which it is linked
via O_LINK. Mode change can not be carried out at the C_PROFB itself.
If the drive is in automatic mode or in an interlocked manual mode, a process feedback creates
a message and a dynamic fault for drive and process feedback block.
If the drive is in non-interlocked manual mode or in local mode, a process feedback fault does not
influence the drive start. The process feedback block just indicates the status of the input, but
it does not show “faulty” and does not create any message.
The behavior for non-interlocked manual mode and local mode can be changed via Feature bit
setting:

BitNr. Function/Features Default val‐


ue
13 Process feedback monitoring in all operating modes FALSE

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.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 9
Function
1.4 Configuration state

1.4 Configuration state


Due to safety reasons the status of the Feature bits and OS Permissions can only be modified if
the block is in configuration state. The block is in configuration state:
- if it is called for the first time in the program or
- during restart of the AS or
- if the block is in Out of Service mode or
- in sequence test mode (PIN protected)

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.

Feature Master block


Features and OS Permissions related to the operating or programming philosophy must be
consistent in all instances of the block. In order to ensure this, the relevant Feature bits and OS
Permission bits can be selected and defined once per block type via the Feature Master block
C_M_PROFB (located in the system chart). These settings can be applied to all instances of the
block type C_PROFB.
Modifications in the Feature Master settings are only applied by the instance if it is in
configuration mode OR if the automatic take-over of Feature Master settings is enabled. In any
case the instance will only accept the changes when the device is stopped.

Process Feedback C_PROFB (V9.1)


10 Function Manual, 11/2020, A5E50300996-AA
Function
1.5 Optional features

1.5 Optional features

Additional Fault Reset


For all Objects types for drives, annunciation blocks and measurements, there is an option to
memorize the trip until an additional “Fault Reset” button in the object faceplate is pressed.
Resetting the fault on object level forces the operator to look at the equipment to be reset.
Only dynamic faults are memorized, static faults don’t require additional Fault Reset.
The Fault Reset can only be carried out after the fault is cleared (after the fault is acknowledged
and gone).
The Fault Reset Function is enabled via the following Feature bit and OS Permission:

BitNr. Function/Features Default val‐


ue
12 Additional Fault reset function FALSE

Feature.bit12 = TRUE enables the function “Fault reset”

BitNr. Function/OS Permission Default val‐


ue
12 1 = Enable Fault reset FALSE

OS_Perm.bit12 = TRUE enables the “Fault reset” button.

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.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 11
Function
1.6 Sequence Test

1.6 Sequence Test


The sequence test mode can be used for program test without the periphery being available.
This is very useful for general function tests, for the Factory Acceptance Test or for Operator
Training.
The sequence test mode always applies to the complete PLC and must be enabled via System
chart SYSPLCxx, block C_FB_PLC at input SEQ_TEST. A PLC restart is necessary in order to switch
into Sequence test mode and back.
In the sequence test mode all block inputs related to physical I/Os are simulated internally and
the corresponding connections to the block inputs are not evaluated any more.
In the sequence test mode the signal status of the inputs can be simulated via diagnosis view of
the process feedback faceplate, where the status indications are converted into simulation
buttons which allow “switching” of the inputs:
• After the Sequence Test mode is enabled, by default all inputs are in healthy condition and
the simulation buttons appear.
• For Signals InSig and InSigB, a click on the button changes the signal status (toggle
function). The same applies to signal PV, where not the Process Value is simulated, but the
condition.
1-Signal = healthy; 0-Signal leads to a fault in case the drive was started.
The sequence test mode includes a function for saving, restoring or interrupting the simulation.
This can be carried out via block C_FB_PLC, inputs SimSave, SimLoad and SimPause in System
chart SYSPLCxx. See Engineering Manual 06_AS_Engineering_009.

Process Feedback C_PROFB (V9.1)


12 Function Manual, 11/2020, A5E50300996-AA
Function
1.7 Visualization

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:

STATUS General Running and Status Information


FeatureOut Status display for Feature Word
OS_PermOut Status display for OS_PermOut Word
OS_PermLog Status display for OS_PermLog Word (includes add. AS
connection code)

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 13
Function
1.7 Visualization

Process Feedback C_PROFB (V9.1)


14 Function Manual, 11/2020, A5E50300996-AA
Operating principle 2
2.1 Input interfaces

InSig (IN_SIG)

InSig (IN_SIG) Input Signal


Format STRUCT
Interface InSig is used to monitor a binary 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:

BitNr. Function/Features Default val‐


ue
15 Analog process value monitoring FALSE
27 Process feedback pulse evaluation FALSE

If Feature.bit15 = FALSE interface InSig (or InSigB) is evaluated.


If Feature.bit15 = TRUE interface PV is evaluated.
If Feature.bit27 = FALSE the input must be a continuous signal.
If Feature.bit27 = TRUE input InSig (or InSigB) must deliver pulses.
After starting the motor, input InSig (or InSigB) must be "1" (or continuously pulsing) within
Start-up monitoring time PFOnDTi.
After stopping the motor, input InSig (or InSigB) must be "0" within Shutdown monitoring
time PFOfDTi. Shutdown monitoring can be disabled via feature bit:

BitNr. Function/Features Default val‐


ue
30 Shutdown monitoring TRUE

If Feature.bit30 = TRUE the shutdown monitoring is enabled.

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

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 15
Operating principle
2.1 Input interfaces

InSig.ST Signal status Default: 16#FF


Format BYTE
Structure variable InSig.Value has Properties Text 0 and Text 1. Via these properties, texts
can be configured which are displayed in the in the status call function of the group/route.
Text 0 is used for the status call.
Text 1 is not used at the moment.

InSigB

InSigB Input Signal (Bool) Basic state 1-Signal


Format BOOL
Input InSigB has exactly the same function as Structure variable InSig.Value and can be
used for direct connection to a Hardware input from the Symbols file. (Because the connection
of Hardware input to Structure is not possible.)
Input InSigB is evaluated if InSig is not connected.With 0-signal at this interface the an‐
nunciation function is blocked.

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:

BitNr. Function/Features Default val‐


ue
15 Analog process value monitoring FALSE

If Feature.bit15 = FALSE interface InSig (or InSigB) is evaluated.


If Feature.bit15 = TRUE interface PV is evaluated.
After starting the motor, input PV must reach the startup ok limit StUpLim within Start-up
monitoring timePFOnDTi.
After stopping the motor, input PV must reach the shutdown ok limit ShDoLim within Shutdown
monitoring time PFOfDTi.

Process Feedback C_PROFB (V9.1)


16 Function Manual, 11/2020, A5E50300996-AA
Operating principle
2.1 Input interfaces

Shutdown monitoring can be disabled via feature bit:

BitNr. Function/Features Default val‐


ue
30 Shutdown monitoring TRUE

If Feature.bit30 = TRUE the shutdown monitoring is enabled.

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)

MsgEn 1 = Enable message Basic state 1-Signal


Format BOOL
With 0-signal at this interface the annunciation function is blocked.
Typical application:
In case of a control voltage failure for MCC or field signals, an alarm message would be triggered
for each sensor signal. To prevent this, you have to connect the control voltage signal to the
enable message interface MsgEn of the process feedback block.
If MsgEn has 0-Signal, the process feedback block does not create any incoming or outgoing
message. The fault message for "control voltage failure" must be generated by an annunciation
module, which has to be engineered for this purpose.

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.

BitNr. Function/Features Default val‐


ue
16 O_LINK used for message enable from drive (int. MsgEn) FALSE

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 17
Operating principle
2.1 Input interfaces

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)

Ack 1 = acknowledge (additional) Basic state 0-Signal


Format BOOL
The acknowledgement of the process feedback block is normally carried out together with the
acknowledgement of any alarm within the same AS (default setting). Interface Ack is only
needed for individual acknowledgement (via push-button) or in case of group-wise acknowl‐
edgement.
A signal change from "0" to "1" at Ack acknowledges the process feedback block (resetting
flag DynFlt).
In case of a conventional control desk, a push-button can be connected to Ack (for individual
acknowledgement) or to the acknowledgement interface at block C_PUSHBT can be used (for
AS-wise acknowledgement).

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:

BitNr. Function/Features Default val‐


ue
19 Only Interface Ack for acknowledgement active FALSE

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.

Process Feedback C_PROFB (V9.1)


18 Function Manual, 11/2020, A5E50300996-AA
Operating principle
2.1 Input interfaces

2.1.1 Inputs for testing and as Interface to the OS

SimuStatus

SimuStatus Interface to set status for sequence test Default: 16#00


Format DWORD
SimuStatus contains the signal status in sequence test mode and must never be connected
or changed

DisSeqTest

DisSeqTest 1 = Disable sequence test for this object Default: 16#00


Format BOOL
If input DisSeqTest = ‘1’, the Simulation of the Process value in sequence test mode is disabled
(e. g. in order to use an internal simulation by program).

SimuSave

SimuSave Saved status interface for sequence test Default: 16#00


Format DWORD
After using the “save” function in sequence test mode, input SimuSave contains the memo‐
rized simulation status. This input must never be connected or changed.

MSG8_EVID

MSG8_EVID Message ID Default: 16#00


Format DWORD
Interface to OS

COMMAND

COMMAND Command word Default: 16#00


Format WORD
Interface to OS
For more information see Variable details.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 19
Operating principle
2.1 Input interfaces

2.1.2 Maintenance

MaiCntOn

MaiCntOn 1 = Maintenance counter active Basic state 1-Signal


Format BOOL
The operating hours for the Maintenance function are only counted if interface MaiCntOn has
1-Signal. This interface may be used e. g. if you want to count the operation hours for an
instrument only while the corresponding motor is running.
The function can also be enabled via Feature bit setting:

BitNr. Function/Features Default


value
20 O_LINK used for maintenance counter activation (int. MaiCntOn) FALSE

If Feature.bit20 = TRUE the running signal is evaluated automatically via O_LINK.

Process Feedback C_PROFB (V9.1)


20 Function Manual, 11/2020, A5E50300996-AA
Operating principle
2.1 Input interfaces

2.1.3 Process Parameters


The process parameters can either be set in the CFC during engineering and/or modified by the
operator, if the Operator has the corresponding OS Permission:

BitNr. Function/OS Permission Default val‐


ue
31 1 = Operator can modify process parameters TRUE

Note
To permit the modification of the process values from the faceplates, they must not be
connected in the CFC.

PFOnDTi

PFOnDTi Start-up monitoring time Default: 10


Format INTEGER (0 - 999)
Value in seconds
After the start of the drive, input InSig(or InSigB) must become 1-signal and input PV must
have reached the Startup OK limit StUpLim within Start-up monitoring time PFOnDTi, oth‐
erwise the output OutSig becomes 0-signal and the block generates and alarm.
With OS_Perm.bit31 = TRUE the operator is permitted to change of the time value for Start-
up monitoring.

PFOfDTi

PFOfDTi Shutdown monitoring time Default: 15


Format INTEGER (0 - 999)
Value in seconds
After the drive has been stopped, input InSig (or InSigB) must become 0-signal and
input PV must have reached the Shutdown OK limit ShDoLim within Shutdown monitoring
time PFOfDTi, otherwise the output OutSig becomes 0-signal and the block generates and
alarm.
PFOfDTi is only evaluated the function is enabled via feature bit:

BitNr. Function/Features Default val‐


ue
30 Shutdown monitoring TRUE

If Feature.bit30 = TRUE the shutdown monitoring is enabled.


With OS_Perm.bit31 = TRUE the operator is permitted to change of the time value for
shutdown monitoring.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 21
Operating principle
2.1 Input interfaces

ProFbTol

ProFbTol Tolerance value for process feedback Default: 50


Format INTEGER (1 - 9999)
Time value = ProFbTol * 0,1s. (Default setting accords approximately 5 seconds).
In case of pulse evaluation the process feedback block should sense an edge change at the pulse
input within this time. Only then the output ProFB becomes 1-signal.
With OS_Perm.bit 31 = TRUE the operator is permitted to change of the Tolerance value
for process feedback.

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:

Scenario 1: Fluttering only happens within Flutter suppression time FlutTm


The process signal gets unhealthy (once or a couple of times), but all failures happen within the
flutter suppression time FlutTm and will therefore be ignored. After this the signal stays healthy
within monitoring time SigOkTm.
Block output ProFB remains “1”
Number of fluttering cycles MaiFlutCyc increases by 1.
Scenario 2: Fluttering happens within the Monitoring time SigOkTm
The process signal gets unhealthy (once or a couple of times) within flutter suppression time
FlutTm (similar to scenario 1) and will therefore be ignored. But after this the signal does not
remain healthy for the duration of monitoring time SigOkTm.
Block output ProFB changes to “0” and stops the drive.
Number of fluttering cycles MaiFlutCyc increases by 1.
Scenario 3: Fluttering happens longer than Flutter suppression time FlutTm
The process signal gets unhealthy (once or a couple of times), and it is still unhealthy when the

Process Feedback C_PROFB (V9.1)


22 Function Manual, 11/2020, A5E50300996-AA
Operating principle
2.1 Input interfaces

flutter suppression time FlutTm elapsed.


Block output ProFB changes to “0” and stops the drive.
Number of fluttering cycles MaiFlutCyc increases by 1.

FlutTm

FlutTm Flutter suppression time [s] Default: 0


Format INT (0 - 999)
Value in seconds
Parameter FlutTm specifies the maximum permitted fluttering time.
Once the flutter-monitoring is activated this timer will start to count down as soon as InSig is
lost (falling edge of InSig is detected) during the monitored drive is running. The fluttering
timer will count down (beginning with FlutTm) until the parametrized time is elapsed. During
the count down, block output FlutAct ist set to “1”.
With the first loss of the process signal the fluttering counter MaiFlutCyc is increased by one.
With OS_Perm.bit31 = TRUE the operator is permitted to change of the Flutter suppression
time.

SigOkTm

SigOkTm Additional monitoring time [s] after fluttering Default: 0


suppression time elapsed
Format INT (0 - 999)
Value in seconds
Parameter SigOkTm specifies the timespan necessary to identify an input signal as "healthy"
after fluttering was detected (InSig must be healthy at least for this time in order to hold the
output of ProFB as "healthy").
The timer starts counting down as soon as the FlutTm has elapsed if InSig is "healthy".
If the InSig is "unhealthy" when the FlutTM has elapsed, the SigOkTm is not triggered, the
output of ProFB directly is set to "unhealthy".
With OS_Perm.bit31 = TRUE the operator is permitted to change of the Flutter suppression
time.

StUpLim

StUpLim Startup OK limit Default: 100.0


Format REAL
After starting the motor, input PV must reach the startup ok limit StUpLim within Start-up
monitoring time PFOnDTi.
With OS_Perm.bit31 = TRUE the operator is permitted to change of the Startup OK limit.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 23
Operating principle
2.1 Input interfaces

ShDoLim

ShDoLim Shutdown OK limit Default: 0.0


Format REAL
After stopping the motor, input PV must reach the shutdown ok limit ShDoLim within Shut‐
down monitoring time PFOfDTi.
The shutdown OK limit is only evaluated if Feature.bit30 = TRUE.
With OS_Perm.bit 31 = TRUE the operator is permitted to change of the Shutdown OK
limit.

Process Feedback C_PROFB (V9.1)


24 Function Manual, 11/2020, A5E50300996-AA
Operating principle
2.1 Input interfaces

2.1.4 Process parameters for Maintenance function:


The process parameters for Maintenance function are normally entered via Operator Faceplate.
In order to modify the maintenance parameters and in order to start the maintenance function
a special OS Permission is needed:

BitNr. Function/OS Permission Default val‐


ue
16 1 = Operator can start the Maintenance function TRUE

With OS_Perm.bit16 = TRUE the operator can start the maintenance interval.

MaiInt (MAI_INT)

MaiInt Maintenance Interval Default: 16#00


Format DWORD
Depending on the parameterization the Maintenance Interval relates to a fixed time value or to
operating hours (as long as MaiCntOn = 1). If the Maintenance Interval is exceeded the
output MaintAL will be set.
With OS_Perm.bit16 = TRUE the operator is permitted to the change of the Maintenance
Interval.

MaiRL (MAI_REQL)

MaiRL Maintenance Request Limit Default: 16#00


Format DWORD
The Maintenance Request Limit can be used in order to indicate to the operator that the Main‐
tenance Interval will be completed soon. If the Maintenance Request Limit is exceeded, the
output MaintRQ will be set.
With OS_Perm.bit16 = TRUE the operator is permitted to the change of the Maintenance
Request Limit.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 25
Operating principle
2.1 Input interfaces

2.1.5 OS Permissions and Features:

OS Permissions and Features:


Via Feature bits certain functions of the Cemat block can be enabled and disabled and the
behavior of the block can be configured.
Via OS Permissions operator actions can be enabled or disabled.
Due to safety reasons it is not possible to change the status of the Feature bits and OS
Permissions online. The Cemat block C_PROFB works with an internal memory which is only
refreshed in configuration state
• if it is called for the first time in the program or
• during restart of the AS or
• if the block is in Out of Service mode or
• in sequence test mode (PIN protected)

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.

Modification of Feature bits and OS Permissions:


The modification of Feature bits and OS Permissions is only possible in configuration state. Only
the Feature bit settings which are consistent (without error, ErrorNum = 0) are accepted.

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.

Process Feedback C_PROFB (V9.1)


26 Function Manual, 11/2020, A5E50300996-AA
Operating principle
2.1 Input interfaces

General settings at the Feature Master:


It must be distinguished between Features and OS Permissions which define the general
operation or programming philosophy of a plant and Features and OS Permissions which enable
instance specific functions.
• Features and OS Permissions which define the general plant philosophy should be identical
in all instances of the block.
The Feature Master block C_M_PROFB (installed in the System Chart) enables the selection
and configuration of the relevant Feature bits and OS Permission bits (once per block type).
In configuration state (or if AutoFeatMast = 1 and the device is stopped) these bits are
transferred to the internal memory of Feature and OS_Perm, and thus cannot be
configured individually per instance. (See Engineering Manual, chapter AS-Engineering)
• The Feature bits and OS Permission bits which are not selected at the Feature Master block
can be configured individually at each instance.

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).

Modification of the Feature Master settings:


In order to ensure that the Feature Master settings are always consistent, modifications of
Feature bits and OS Permissions are only accepted if the Feature Master block is “locked”. Change
input Lock at the Feature Master block to “1” and carry out the modifications. If the
modifications are completed, change input Lock back to “0”.
With the falling edge at input Lock the modifications are transferred to the output of the Feature
Master and available for the instances.
A counter value at the Feature Master will be increased by one. In addition to the counter, the
Feature Master block has two outputs locked and unlocked which can be connected to an
EventTs block in order to trigger a message.
For the automatic take-over of the new settings by the instance, input AutoFeatMast must
have 1-Signal and the drive must be stopped. If the connected drive is running, the process
feedback block will ignore the new settings. A counter in the Preset window of the process
feedback block shows if there is a difference to the Master settings.

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.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 27
Operating principle
2.1 Input interfaces

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

OS_Perm Operator Permissions


Format STRUCT
Via OS Permissions operator actions can be enabled or disabled.
Please consider that the Cemat block works with the internal Feature bit and OS Permission
memory, which is only refreshed in configuration state.
The faceplate of the block shows the status of the internal memory.
Chapter OS Permissions contains a list of all available Permission bits. The function of the
individual permission is described with the corresponding interfaces.

Note
It is not allowed to connect any logic to OS_Perm input.

OpSt_In

OpSt_In Enabled Operator Station Default: 16#00


Format DWORD
Input parameter for a local operator panel. This input must be connected with output Out of
block OStations. Via input OpSt_In the group block receives the information, which Operator
Stations are enabled for the operation of the group.

Process Feedback C_PROFB (V9.1)


28 Function Manual, 11/2020, A5E50300996-AA
Operating principle
2.1 Input interfaces

Feature

Feature Status of various features


Format STRUCT
Via Feature bits certain functions of the Cemat block can be enabled and disabled and the
behavior of the block can be configured.
Please consider that the Cemat block works with an internal Feature bit and OS Permission
memory which is only refreshed in configuration state and only if the feature bit settings are
consistent (ErrorNum = 0).
The faceplate of the block shows the status of the internal memory.
Chapter Feature bits contains a list of all available Features. The function of the individual
feature bits is described with the corresponding interfaces.

Note
It is not allowed to connect any logic to Feature input.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 29
Operating principle
2.1 Input interfaces

2.1.6 Connection to EventTs


Via the following interface the CEMAT block can be connected to the APL-Block EventTs:

EventTsIn

EventTsIn Timestamp parameters


Format ANY
Via APL block EventTs additional messages can be created. The message class can be of any
type.
Connect the Output EventTsOut of the EventTs block to input EventTsIn of the C_PROFB.
The messages of the block EventTs get the tagname of the process feedback block. If the
C_PROFB is in “Out of Service” or if messages are disabled with MsgEn = “0”, the messages from
the EventTs block are suppressed.
Event text and message class must be configured in the Message Configuration of the EventTs
block. Free Text 1 cannot be entered in the message configuration in the CFC (because for the
attribute S7_alarm_ui = 1), but in order to be consistent with the CEMAT blocks Free Text
1 can be modified in the process object view.

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!

Process Feedback C_PROFB (V9.1)


30 Function Manual, 11/2020, A5E50300996-AA
Operating principle
2.2 Group and Object links

2.2 Group and Object links

Group/Route links
There is no direct link to the group or route.

Object links to master objects


Process feedback blocks always belong to a drive and do not have a link interface to the group
(or route). The process feedback block must be linked to a drive block via O_LINK. The drive
forwards the status of the process feedback block to the group.

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.

BitNr. Function/Features Default val‐


ue
16 O_LINK used for message enable from drive (int. MsgEn) FALSE

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 31
Operating principle
2.2 Group and Object links

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

O_LINK Link to another object


Format STRUCT
Interface O_LINK of the process feedback block is used for the link to a master object (drive/
device).

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!!!

Process Feedback C_PROFB (V9.1)


32 Function Manual, 11/2020, A5E50300996-AA
Operating principle
2.3 Input/Output interfaces

2.3 Input/Output interfaces

ResTimOS

ResTimOS Reset time RT for OS Default: 16#00


Format DWORD
Interface to OS

MaiRTm

MaiRTm Runtime (s) updated every minute Default: 16#00


Format DWORD
Interface to OS

MaiRTh

MaiRTh Runtime (s) updated every hour Default: 16#00


Format DWORD
Interface to OS

MaiCntSt

MaiCntSt Maintenance act. counter in hours or starts Default: 16#00


Format DWORD
Interface to OS

MAI_STA

MAI_STA Maintenance Status Default: 16#80022


Format DWORD
Interface to OS
For more information see Variable details.

MaiCorr

MaiCorr Maintenance correction value Default: 16#00


Format DWORD
The maintenance correction value can be used in order to preset the value for MaiCntSt
(Maintenance act. counter in hours or starts) at the moment of starting the maintenance
interval.
With OS_Permission.bit16 = TRUE the operator is permitted to the change of the main‐
tenance correction value.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 33
Operating principle
2.3 Input/Output interfaces

MaiCyc

MaiCyc Number of completed maintenance cycles Default: 16#00


Format DWORD
This counter tells how often the maintenance cycle was completed (“completion” must be
confirmed by the operator).

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.

Process Feedback C_PROFB (V9.1)


34 Function Manual, 11/2020, A5E50300996-AA
Operating principle
2.4 Output interfaces

2.4 Output interfaces

2.4.1 Outputs for testing and as Interface to the OS

ProFbCV

ProFbCV Current value process feedback (OS)


Format BYTE
Interface to OS

STATUS

STATUS Interface to OS
Format DWORD
Interface to OS
For more information see Variable details.

ALARM

ALARM for Test


Format WORD
For more information see Variable details.

DelayCon

DelayCon Delay Counter


Format INTEGER
Interface to OS

FeatureOut

FeatureOut Feature word to OS


Format DWORD
For more information see Table Feature bits.

OS_PermOut

OS_PermOut Operator Permissions to OS


Format DWORD
For more information see Table OS Permissions.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 35
Operating principle
2.4 Output interfaces

OS_PermLog

OS_PermLog Operator Permissions: Output for OS


Format DWORD
For more information see Table OS Permissions.

FWCopyMaster

FWCopyMaster Feature master copy bits to OS


Format DWORD
FWCopyMaster indicates the Feature bits which are overwritten by the settings from Feature
Master block. For more information see Table Feature bits.

OSCopyMaster

OSCopyMaster Feature master copy bits to OS


Format DWORD
OSCopyMaster indicates the OS Permission bits which are overwritten by the settings from
Feature Master block. For more information see Table OS Permissions.

OpSt_Out

OpSt_Out Enabled Operator Stations


Format DWORD
Output OpSt_Out provides the value of the input parameter OpSt_In and can be used for the
connection to other blocks.
Bit 31 contains the information of Feature.bit24 'Local authorization active (1=evaluate
permission from OPStation)'.

Process Feedback C_PROFB (V9.1)


36 Function Manual, 11/2020, A5E50300996-AA
Operating principle
2.4 Output interfaces

2.4.2 Output status for connection to other blocks

ProFB

ProFB Process feedback


Format STRUCT
1-Signal at output ProFB means that the process feedback is available. Output ProFB of the
C_PROFB must be connected to input ProFB of the motor.
Output ProFB is either set immediately after process feedback has arrived or after the Start-up
monitoring time PFOnDTi has elapsed. This can be configured via feature bit setting:

BitNr. Function/Features Default val‐


ue
31 Process feedback monitoring also during start-up (PFOnDTi) TRUE

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

OutSig 1 = Output Signal ok


Format STRUCT
In case of a process feedback fault parameter OutSig becomes 0-signal. This information is
transmitted to the drive via O_LINK connection. No further connection is needed.
Output OutSig is influenced by Feature bit settings and Simulation. In case of
Simulation OutSig is forced to 1-Signal.
Feature bit settings:

BitNr. Function/Features Default val‐


ue
14 Keep fault status up to new startup of drive FALSE
29 Warning mode active FALSE

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.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 37
Operating principle
2.4 Output interfaces

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

Fault Static Fault/Warning


Format BOOL
1-signal means that a fault or a warning is present.
If the block is configured for Warning mode (Feature.bit29 = TRUE), output Fault must
be connected to protection interlock IntProtA of the motor.

FlutAct

FlutAct 1 = Fluttering Active


Format BOOL
Output FlutAct has 1-Signal if the flutter suppression is activated.
The signal is set if the process signal is lost during the monitored drive is running. It will be reset
after flutter suppression time FlutTm) elapsed.

Process Feedback C_PROFB (V9.1)


38 Function Manual, 11/2020, A5E50300996-AA
Operating principle
2.4 Output interfaces

AckQ

AckQ 1 = Acknowledgement of fault and /or message


Format BOOL
Output AckQ contains the status of the internal acknowledgement bit of the block (according
to the acknowledgement settings in SYSPLCxx and in the block).
This output can be used in order to forward the acknowledgement command to a satellite block
or to an output (in order to forward the acknowledgement to an external device).

SimActQ

SimActQ 1 = Simulation activated


Format BOOL
In Simulation mode output SimActQ has 1-Signal and the process feedback is simulated in‐
ternally.

MaintRQ

MaintRQ Maintenance Request


Format BOOL
Output MaintRQ is set to 1-Signal if the auto request value has been exceeded, which means
the maintenance interval is nearly completed. This output can be connected to an annunciation
block in order to generate an alarm.

MaintAL

MaintAL Maintenance Alarm


Format BOOL
Output MaintAL is set to 1-Signal if the maintenance interval has been completed. This output
can be connected to an annunciation block in order to generate an alarm.

MaiRTm_Q

MaiRTm_Q Runtime (s) updated every minute


Format DWORD
Interface to OS

MaiRTh_Q

MaiRTh_Q Runtime (s) updated every hour


Format DWORD
Interface to OS

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 39
Operating principle
2.4 Output interfaces

MaiCyc_Q

MaiCyc_Q Number of Completed Maintenance Cycles


Format REAL
Output MaiCyc_Q contains the value from MaiCyc in REAL Format.

ST_Worst

ST_Worst Worst Signal Status


Format BYTE
For all structure interfaces the status information (Simulation, Bad quality etc.) is displayed in
the diagnostic window:
InSig (or InSigB), PV, internal simulation.
The worst status of these signals is transmitted to output ST_Worst and always displayed.
Via feature bit setting it can be decided whether the Signal status is visible in the block outputs
as well:

BitNr. Function/Features Default val‐


ue
22 Write quality code ST_Worst to module output FALSE

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

MsgAckn1 Message acknowledgement status


Format WORD
Output ACK_STATE of the first ALARM_8
For details of ACK_STATE see online help of SFB 34 ALARM_8

TimeStamp

TimeStamp Time-stamp (feature bit take-over)


Format STRING[22]
Date and time of the last Feature bit and OS Permission update from Feature Master (for the
display in the Preset Window).

Process Feedback C_PROFB (V9.1)


40 Function Manual, 11/2020, A5E50300996-AA
Operating principle
2.4 Output interfaces

CountDiffer

CountDiffer Counter difference


Format INT
A value > 0 shows that the Feature bit and OS Permission settings of the Feature Master are not
yet used by the instance, e. g. because the settings in the Feature Master block were changed
while the drive was running.
The next stop of the drive will reset the counter value and the Feature bit and OS Permission
settings of the Feature Master block are transmitted to the instance.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 41
Operating principle
2.5 Engineering Errors

2.5 Engineering Errors

ErrorNum

ErrorNum Error Number Default: -1


Format INTEGER
In case of an invalid connection or an invalid feature bit setting the functionality of the block can
not be guaranteed any more. If the error number is different than -1 you have to check the
application program or the feature bits and correct it:

Error number Fault description


1
2
3 The process feedback block is not linked (O_LINK)
→ Check O_LINK connections
4 Block (including Signal objects) cannot be added to O_LINK buffer.
→ The O_LINK buffer is limited to 20 objects!
5 The O_LINK of C_PROFB is connected to a C_SEND_G.
The O_LINK of C_PROFB must always be connected to a drive!
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26 If Fault reset is enabled (Feature.bit12 = TRUE) the fault status must not be kept until
new startup of drive. Feature.bit14 must be FALSE!

Process Feedback C_PROFB (V9.1)


42 Function Manual, 11/2020, A5E50300996-AA
Operating principle
2.5 Engineering Errors

Note
Only one error number can be indicated at a time!

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 43
Operating principle
2.5 Engineering Errors

Process Feedback C_PROFB (V9.1)


44 Function Manual, 11/2020, A5E50300996-AA
Time characteristics 3
All CEMAT process feedback blocks must be called before the associated route or group.
If C_MUX blocks are used, the C_MUX blocks must be called after the process feedback block and
before the drive block.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 45
Time characteristics

Process Feedback C_PROFB (V9.1)


46 Function Manual, 11/2020, A5E50300996-AA
Message characteristics 4
The module uses an ALARM_8 module to generate annunciations.

Variable details MSG8_EVID:

Message ID Event Message class Priority Fault class


SIG1 Process feedback Alarm - high 0 P
SIG2 Process feedback Warning - high 0 P
SIG3 Process feedback start‐ Alarm - high 0 P
up
SIG4 Process feedback start‐ Warning - high 0 P
up
SIG5 Process feedback shut‐ Alarm - high 0 P
down
SIG6 Process feedback shut‐ Warning - high 0 P
down
SIG7 0
SIG8 Still faulty Alarm - high 0 P

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).

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 47
Message characteristics

Process Feedback C_PROFB (V9.1)


48 Function Manual, 11/2020, A5E50300996-AA
Module States 5
Status indications:

Status / Text Display Text Presentation Icon Display


No fault Black on grey Grey
Fault not ackn. White on red Red blinking
Fault White on red Red
No warning *) Black on grey Grey
Warning not ackn. *) Black on yellow Yellow blinking
Warning *) Black on yellow Yellow

*) yellow when the process feedback is configured as "warning" (Feature.bit29 = TRUE)


Also refer to the Variable details.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 49
Module States

Process Feedback C_PROFB (V9.1)


50 Function Manual, 11/2020, A5E50300996-AA
Operator Commands 6
Refer to the Variable details for the assignment of the command word COMMAND.
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 built 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_PROFB and the required settings:

OS Commands Feature Bit


OS_PermissionLog
Op_Level
Block Param‐
eter
Simulation Simulation 15 24 InSig
Analog val‐ Startup OK limit 21 20 StUpLim
ues Shutdown OK limit 26 20 ShDoLim
Acknowl‐ Fault Reset 12 12 5 AutModOn
edge
Process Pa‐ Tolerance speed monitor 31 22 ProFbTol
rameter Start-up monitoring time [s] 31 22 PFOnDTi
Shutdown monitoring time [s] 31 22 PFOfDTi
Fluttering suppression time [s] 31 22 FlutTm
Additional monitoring time [s] after flut‐ 31 22 SigOkTm
tering suppression time elapsed
Mainte‐ Reset statistic values 23 RelTimOS
nance Start Maintenance 16 29 MaiInt

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 51
Operator Commands

Process Feedback C_PROFB (V9.1)


52 Function Manual, 11/2020, A5E50300996-AA
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:

BitNr. Function/Features Default val‐


ue
0 FALSE
1 FALSE
2 FALSE
3 FALSE
4 FALSE
5 FALSE
6 FALSE
7 FALSE
8 FALSE
9 FALSE
10 FALSE
11 FALSE
12 Additional Fault reset function FALSE
13 Process feedback monitoring in all operating modes FALSE
14 Keep fault status up to new startup of drive FALSE
15 Analog process value monitoring FALSE
16 O_LINK used for message enable from drive (int. MsgEn) FALSE
17 FALSE
18 FALSE
19 Only Interface Ack for acknowledgement active FALSE
20 O_LINK used for maintenance counter activation (internal MaiCntOn) FALSE
21 FALSE
22 Write quality code ST_Worst to module output FALSE
23 FALSE
24 Local authorization active (OP Station perm. needed) FALSE
25 FALSE
26 FALSE
27 Process feedback pulse evaluation FALSE
28 FALSE
29 Warning mode active FALSE
30 Shutdown monitoring TRUE
31 Process feedback monitoring also during start-up (PFOnDTi) TRUE

A detailed description of the individual Feature bits can be found in the chapters above.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 53
Feature Bits

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

Process Feedback C_PROFB (V9.1)


54 Function Manual, 11/2020, A5E50300996-AA
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:

BitNr. Function/OS Permission Default val‐


ue
0 FALSE
1 FALSE
2 FALSE
3 FALSE
4 FALSE
5 FALSE
6 FALSE
7 FALSE
8 FALSE
9 FALSE
10 FALSE
11 FALSE
12 1 = Enable Fault reset FALSE
13 FALSE
14 FALSE
15 1 = Operator can change to simulation TRUE
16 1 = Operator can start the maintenance function TRUE
17 FALSE
18 1 = Enable Single step mode change TRUE
19 FALSE
20 FALSE
21 FALSE
22 FALSE
23 FALSE
24 FALSE
25 FALSE
26 FALSE
27 FALSE
28 FALSE
29 FALSE
30 FALSE
31 1 = Operator can modify process parameters TRUE

A detailed description of the individual OS Permission bits can be found in the chapters above.

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 55
OS Permissions

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.

Process Feedback C_PROFB (V9.1)


56 Function Manual, 11/2020, A5E50300996-AA
I/O-bar of C_PROFB 9
C_PROFB

Name Description Format Default Type Attr. HMI


InSig Input Signal STRUCT I
InSig.Value Value BOOL 1 I U +
InSig.ST Signal Status BYTE 16#FF I U
InSigB Input Signal (Bool) BOOL 0 I U
PV Input Signal STRUCT I U
PV.Value Value REAL 0.0 I U
PV.ST Signal Status BYTE 16#FF I U
MsgEn 1 = enable messages BOOL 1 I
Ack 1 = Acknowledge (additional) BOOL 0 I U
SimuStatus Interface to set status for sequence test DWORD 16#0 I U +
DisSeqTest 1 = Disable sequence test for this object BOOL 0 I U
SimuSave Saved status interface for sequence test DWORD 16#0 I U +
MSG8_EVID Message ID DWORD 16#00 I U
COMMAND Command word WORD 16#00 I U +
MaiCntOn 1 = Maintenance counter active BOOL 1 I U
PFOnDTi Start-up monitoring time INT 10 I U +
PFOfDTi Shutdown monitoring time INT 15 I U +
ProFbTol Tolerance value for Process feedback (pulse eval‐ INT 50 I U +
uation)
FlutTm Flutter suppression time [s] INT 0 I U +
SigOkTm Additional monitoring time [s] after fluttering INT 0 I U +
suppression time elapsed
StUpLim Startup OK limit REAL 100.0 I U +
ShDoLim Shutdown OK limit REAL 0.0 I U +
MaiInt Maintenance Interval DWORD 16#00 I U +
MaiRL Maintenance Request Limit DWORD 16#00 I U +
FeatMaster Use OS permission and feature bits from master BOOL 1 I U
block
AutoFeatMast Automatic take-over of feature and OS permis‐ BOOL 1 I U
sion bits
OS_Perm Operator Permissions STRUCT I U
OS_Perm.Bit0 Spare BOOL 0 I U
OS_Perm.Bit1 Spare BOOL 0 I U
OS_Perm.Bit2 Spare BOOL 0 I U
OS_Perm.Bit3 Spare BOOL 0 I U
OS_Perm.Bit4 Spare BOOL 0 I U
OS_Perm.Bit5 Spare BOOL 0 I U

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 57
I/O-bar of C_PROFB

Name Description Format Default Type Attr. HMI


OS_Perm.Bit6 Spare BOOL 0 I U
OS_Perm.Bit7 Spare BOOL 0 I U
OS_Perm.Bit8 Spare BOOL 0 I U
OS_Perm.Bit9 Spare BOOL 0 I U
OS_Perm.Bit10 Spare BOOL 0 I U
OS_Perm.Bit11 Spare BOOL 0 I U
OS_Perm.Bit12 1 = Enable Fault reset BOOL 0 I U
OS_Perm.Bit13 Spare BOOL 0 I U
OS_Perm.Bit14 Spare BOOL 0 I U
OS_Perm.Bit15 1 = Operator can change to simulation BOOL 1 I U
OS_Perm.Bit16 1 = Operator can start the maintenance function BOOL 1 I U
OS_Perm.Bit17 Spare BOOL 0 I U
OS_Perm.Bit18 1 = Enable Single step mode change BOOL 1 I U
OS_Perm.Bit19 Spare BOOL 0 I U
OS_Perm.Bit20 Spare BOOL 0 I U
OS_Perm.Bit21 Spare BOOL 0 I U
OS_Perm.Bit22 Spare BOOL 0 I U
OS_Perm.Bit23 Spare BOOL 0 I U
OS_Perm.Bit24 Spare BOOL 0 I U
OS_Perm.Bit25 Spare BOOL 0 I U
OS_Perm.Bit26 Spare BOOL 0 I U
OS_Perm.Bit27 Spare BOOL 0 I U
OS_Perm.Bit28 Spare BOOL 0 I U
OS_Perm.Bit29 Spare BOOL 0 I U
OS_Perm.Bit30 Spare BOOL 0 I U
OS_Perm.Bit31 1 = Operator can modify process parameters BOOL 1 I U
OpSt_In Enabled operator station DWORD 16#00 I U
Feature Status of various features STRUCT I U
Feature.Bit0 Spare BOOL 0 I U
Feature.Bit1 Spare BOOL 0 I U
Feature.Bit2 Spare BOOL 0 I U
Feature.Bit3 Spare BOOL 0 I U
Feature.Bit4 Spare BOOL 0 I U
Feature.Bit5 Spare BOOL 0 I U
Feature.Bit6 Spare BOOL 0 I U
Feature.Bit7 Spare BOOL 0 I U
Feature.Bit8 Spare BOOL 0 I U
Feature.Bit9 Spare BOOL 0 I U
Feature.Bit10 Spare BOOL 0 I U
Feature.Bit11 Spare BOOL 0 I U
Feature.Bit12 Additional Fault reset function BOOL 0 I U
Feature.Bit13 Process feedback monitoring in all operating BOOL 0 I U
modes

Process Feedback C_PROFB (V9.1)


58 Function Manual, 11/2020, A5E50300996-AA
I/O-bar of C_PROFB

Name Description Format Default Type Attr. HMI


Feature.Bit14 Keep fault status up to new startup of drive BOOL 0 I U
Feature.Bit15 Analog process value monitoring BOOL 0 I U
Feature.Bit16 O_LINK used for message enable from drive (int. BOOL 0 I U
MsgEn)
Feature.Bit17 Spare BOOL 0 I U
Feature.Bit18 Spare BOOL 0 I U
Feature.Bit19 Only Interface Ack for acknowledgement active BOOL 0 I U
Feature.Bit20 O_LINK used for maintenance counter activation BOOL 0 I U
(int. MaiCnOn)
Feature.Bit21 Spare BOOL 0 I U
Feature.Bit22 Write quality code ST_Worst to module output BOOL 0 I U
Feature.Bit23 Spare BOOL 1 I U
Feature.Bit24 Local authorization active (OP Station perm. nee‐ BOOL 0 I U
ded)
Feature.Bit25 Spare BOOL 0 I U
Feature.Bit26 Spare BOOL 0 I U
Feature.Bit27 Process feedback pulse evaluation BOOL 0 I U
Feature.Bit28 Spare BOOL 0 I U
Feature.Bit29 Warning mode active BOOL 0 I U
Feature.Bit30 Shutdown monitoring BOOL 1 I U
Feature.Bit31 Process feedback monitoring also during start-up BOOL 1 I U
(PFOnDTi)
O_LINK Link to another object STRUCT I
O_LINK.iDB Instance DB master object INT 0 I U
O_LINK.iDW DW number NO_OF_FT in master object INT 0 I U
O_LINK.Com‐ Group/ route command BYTE 16#00 I U
mand
O_LINK.Status Status master object BYTE 16#00 I U
EventTsIn Timestamp parameters ANY I U

ResTimOS Reset time RT for OS DWORD 16#00 IO U +


MaiRTm Runtime (s) DWORD 16#00 IO U +
updated every minute
MaiRTh Runtime (s) DWORD 16#00 IO U +
updated every hour
MaiCntSt Maintenance Actual Counter in hours DWORD 16#00 IO U +
MAI_STA Maintenance Status DWORD 16# IO U +
0080022
MaiCorr Maintenance correction value DWORD 16#00 IO U +
MaiCyc Number of completed maintenance cycles DWORD 16#00 IO U +
MaiFlutCyc Number of times the flutter monitoring was star‐ INT 0 IO U +
ted

ProFbCV Current value process feedback (OS) BYTE 16#00 O U +


STATUS Interface to OS DWORD 16#00 O U +

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 59
I/O-bar of C_PROFB

Name Description Format Default Type Attr. HMI


ALARM For test WORD 16#00 O U
DelayCon Delay Counter INT 0 O U +
FeatureOut Feature word to OS DWORD 16#00 O U +
OS_PermOut Operator Permissions to OS DWORD 16#00 O U +
OS_PermLog Operator Permissions: Output for OS DWORD 16#FFFFFFFF O U +
FWCopyMaster Feature master copy bits to OS DWORD 16#00 O U +
OSCopyMaster Feature master copy bits to OS DWORD 16#00 O U +
OpSt_Out Enabled Operator Stations DWORD 16#00 O U +
ProFB Process feedback to the drive STRUCT O
ProFB.Value Value BOOL 0 O U +
ProFB.ST Signal Status BYTE 16#80 O U +
OutSig 1 = Output signal ok STRUCT O
OutSig.Value Value BOOL 0 O U +
OutSig.ST Signal Status BYTE 16#80 O U +
Fault Fault BOOL 0 O
FlutAct 1 = Fluttering active BOOL 0 O U
AckQ 1 = Acknowledge of fault and/or message BOOL 0 O
SimActQ 1 = Simulation activated BOOL 0 O U
MaintRQ Maintenance Request BOOL 0 O U
MaintAL Maintenance Alarm BOOL 0 O U
MaiRTm_Q Running time (s) DWORD 16#00 O U
updated every minute
MaiRTh_Q Running time (s) DWORD 16#00 O U
updated every hour
MaiCyc_Q Number of Completed Maintenance Cycles REAL 0.0 O U
ST_Worst Worst Signal Status BYTE 16#80 O U +
ErrorNum Error Number INT -1 O +
MsgAckn1 Message acknowledgement status WORD 16#00 O U
TimeStamp Time-stamp (feature bit take-over) STRING ‘’ O U +
[22]
CountDiffer Counter difference INT 0 O U +

Process Feedback C_PROFB (V9.1)


60 Function Manual, 11/2020, A5E50300996-AA
OS-Variable table 10
C_PROFB

OS Variable Description PLC Data Type OS Data Type


InSig#Value Value BOOL Binary variable
PV#Value Value REAL 32-bit floating-point number IEEE 754
SimuStatus Interface to set status for sequence DWORD Unsigned 32-bit value
test
SimuSave Saved status interface for sequence DWORD Unsigned 32-bit value
test
COMMAND Command word WORD Unsigned 16-bit value
PFOnDTi Start-up monitoring time INT Signed 16-bit value
PFOfDTi Shutdown monitoring time INT Signed 16-bit value
ProFbTol Tolerance value for Process feed‐ INT Signed 16-bit value
back (pulse evalutation)
FlutTm Flutter suppression time [s] INT Signed 16-bit value
SigOkTm Additional monitoring time [s] after INT Signed 16-bit value
fluttering suppression time elapsed
StUpLim Startup OK limit REAL 32-bit floating-point number IEEE 754
ShDoLim Shutdown OK limit REAL 32-bit floating-point number IEEE 754
MaiInt Maintenance Interval DWORD Unsigned 32-bit value
MaiRL Maintenance Request Limit DWORD Unsigned 32-bit value
ResTimOS Reset time RT for OS DWORD Unsigned 32-bit value
MaiRTm Runtime (s) DWORD Unsigned 32-bit value
updated every minute
MaiRTh Runtime (s) DWORD Unsigned 32-bit value
updated every hour
MaiCntSt Maintenance Actual Counter in DWORD Unsigned 32-bit value
hours
MAI_STA Maintenance Status DWORD Unsigned 32-bit value
MaiCorr Maintenance correction value DWORD Unsigned 32-bit value
MaiCyc Number of completed maintenance DWORD Unsigned 32-bit value
cycles
MaiFlutCyc Number of times the flutter moni‐ INT Signed 16-bit value
toring was started
ProFbCV Current value process feedback (OS) BYTE Unsigned 8-bit value
STATUS Interface to OS DWORD Unsigned 32-bit value
DelayCon Delay counter INT Signed 16-bit value
FeatureOut Status of various features DWORD Unsigned 32-bit value
OS_PermOut Operator Permissions DWORD Unsigned 32-bit value
OS_PermLog Operator Permissions: DWORD Unsigned 32-bit value
Output for OS
FWCopyMaster Feature master copy bits to OS DWORD Unsigned 32-bit value

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 61
OS-Variable table

OS Variable Description PLC Data Type OS Data Type


OSCopyMaster Feature master copy bits to OS DWORD Unsigned 32-bit value
OpSt_Out Enabled operator stations DWORD Unsigned 32-bit value
ProFB#Value Value BOOL Binary variable
ProFB#ST Signal Status BYTE Unsigned 8-bit value
OutSig#Value Value BOOL Binary variable
OutSig#ST Signal Status BYTE Unsigned 8-bit value
ST_Worst Worst Signal Status BYTE Unsigned 8-bit value
ErrorNum Error Number INT Signed 16-bit value
TimeStamp Time-stamp (feature bit take-over) STRING[22] Text variable 8-bit character set
CountDiffer Counter difference INT Signed 16-bit value

Process Feedback C_PROFB (V9.1)


62 Function Manual, 11/2020, A5E50300996-AA
Variable details 11
11.1 Variable details COMMAND
Internal structure of the Commands, Alarms, Visualization status and Interface word:

Parameter Function OS-Addr. Designation Msg Class Fault Class


COMMAND Commandword
COM_B20 BYPASS 0 Simulation On/OFF Op. Inp.
COM_B21 1
COM_B22 2
COM_B23 3
COM_B24 Reset 4 Fault Reset Op. Inp.
COM_B25 5
COM_B26 6
COM_B27 7
COM_B10 8
COM_B11 SACK 9 single acknowledge
COM_B12 10 Reset Running Time OS Op. Inp.
COM_B13 11
COM_B14 12
COM_B15 13
COM_B16 14
COM_B17 15

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 63
Variable details
11.2 Variable details MSG8_EVID

11.2 Variable details MSG8_EVID


Internal structure of the Commands, Alarms, Visualization status and Interface word:

Parameter Function OS- Designation Msg Class Fault


Addr. Class
MSG8_EVID Alarm
ALA_SIG1 SIG1 0 Process feedback AL_H P
ALA_SIG2 SIG2 1 Process feedback WA_H P
ALA_SIG3 SIG3 2
ALA_SIG4 SIG4 3
ALA_SIG5 SIG5 4
ALA_SIG6 SIG6 5
ALA_SIG7 SIG7 6
ALA_SIG8 SIG8 7 Still faulty AL_H P

Process Feedback C_PROFB (V9.1)


64 Function Manual, 11/2020, A5E50300996-AA
Variable details
11.3 Variable details STATUS

11.3 Variable details STATUS


Internal structure of the Commands, Alarms, Visualization status and Interface word:

Parameter Function OS-Addr. Designation Msg Class Fault Class


STATUS Status
STA_B40 0
STA_B41 DRV_FEEDB 1 Drive feedback ON
STA_B42 FT_SIG 2 fault signal
STA_B43 WMOD 3 1= Mode warning, 0 = Alarm
STA_B44 Not Ready 4 PROFB is not ready
STA_B45 BQU 5 Bad Quality of signals
STA_B46 PST 6 dyn. fault or warning
STA_B47 InSigCon 7 InSig connected
STA_B30 OUT_SIG 8 Interlock Output Signal
STA_B31 FroFB 9 ProFB signal to Drive
STA_B32 10 Flutter suppression active
STA_B33 SeqTestAct 11 Sequence test active
STA_B34 MARK 12 Highlight object (group command)
STA_B35 PV 13 PV connected
STA_B36 SIM_ON 14 Sequence test/Simulation
STA_B37 EN_OFFDM 15 enable shutdown monitoring
STA_B20 on_dly_run 16 On delay is running
STA_B21 off_dly_run 17 Off delay is running
STA_B22 18 ErrorNum > 0
STA_B23 MaNonInt 19 Manual: non interlocked
STA_B24 Auto 20 Automatic mode
STA_B25 Manual 21 Manual mode
STA_B26 Local 22 Local mode
STA_B27 OoS 23 Out of Service mode
STA_B10 InSig 24 Input signal hardware
STA_B11 SST 25 general fault
STA_B12 DST 26 dyn. fault or warning
STA_B13 MsgEn 27 enable annunciations
STA_B14 Ackn 28 aknowledge (external)
STA_B15 GR_STP 29 Bad Quality or group stopped and
fault (Holcim)
STA_B16 FeatMaster 30 Feature master bits active
STA_B17 Features differ 31 Counters between feature master
and instance differ

Process Feedback C_PROFB (V9.1)


Function Manual, 11/2020, A5E50300996-AA 65
Variable details
11.4 Variable details MAI_STA

11.4 Variable details MAI_STA


Internal structure of the Commands, Alarms, Visualization status and Interface word:

Parameter Function OS-Addr. Designation Msg Class Fault Class


MAI_STA Maintenance Status
MAI_STA_B40 0 Maintenance interval: fixed
MAI_STA_B41 1 Maintenance interval: Operating
hour
MAI_STA_B42 2
MAI_STA_B43 3
MAI_STA_B44 4 Maintenance Command: start
MAI_STA_B45 5 Maintenance Command: stop/reset
MAI_STA_B46 6
MAI_STA_B47 7
MAI_STA_B30 8 Status Alarm (Interval exceeded))
MAI_STA_B31 9 Status Request (Req. Val. Exceeded))
MAI_STA_B32 10 Status Run (Maintenance on)
MAI_STA_B33 11
MAI_STA_B34 12
MAI_STA_B35 13
MAI_STA_B36 14
MAI_STA_B37 15
MAI_STA_B20 16 Operation Request
MAI_STA_B21 17 Operation In Progress
MAI_STA_B22 18 Operation Completed
MAI_STA_B23 19 Operation Temp
MAI_STA_B24 20 (No Operator Action)
MAI_STA_B25 21
MAI_STA_B26 22
MAI_STA_B27 23
MAI_STA_B10 24
MAI_STA_B11 25
MAI_STA_B12 26
MAI_STA_B13 27
MAI_STA_B14 28
MAI_STA_B15 29
MAI_STA_B16 30
MAI_STA_B17 31

Process Feedback C_PROFB (V9.1)


66 Function Manual, 11/2020, A5E50300996-AA

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy