Pcs 7 Cemat Unidirectional Drive C - DRV - 1D
Pcs 7 Cemat Unidirectional Drive C - DRV - 1D
Operating principle 2
Time characteristics 3
PCS 7
Message characteristics 4
CEMAT
Unidirectional Drive C_DRV_1D 5
Module States
Operator Commands 6
Function Manual
Feature Bits 7
OS Permissions 8
I/O-bar of C_DRV_1D 9
OS-Variable table 10
Variable details 11
07/2016
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
1 Function........................................................................................................................................................5
1.1 General Function description...................................................................................................6
1.2 Change of operation mode.....................................................................................................10
1.3 Configuration state.................................................................................................................13
1.4 Additional functions................................................................................................................14
1.5 Optional features....................................................................................................................16
1.6 Sequence Test.......................................................................................................................18
1.7 Power Management...............................................................................................................19
1.8 Visualization...........................................................................................................................20
2 Operating principle.....................................................................................................................................21
2.1 Hardware inputs.....................................................................................................................21
2.2 Input interfaces.......................................................................................................................28
2.2.1 Interfaces for operation mode change...................................................................................35
2.2.2 SIMOCODE drives.................................................................................................................43
2.2.3 Subcontrol function................................................................................................................44
2.2.4 Link to a measured value.......................................................................................................45
2.2.5 Display of the percentage value of measurement..................................................................46
2.2.6 Setpoint function....................................................................................................................46
2.2.7 User output function...............................................................................................................49
2.2.8 Inputs for testing and as Interface to the OS..........................................................................50
2.2.9 Process Parameters for starting and stopping.......................................................................52
2.2.10 User specific adaptations.......................................................................................................55
2.2.11 User Faceplate call................................................................................................................55
2.2.12 Process parameters for Maintenance function:......................................................................56
2.2.13 OS Permissions and Features:..............................................................................................57
2.2.14 Connection to EventTs...........................................................................................................61
2.3 Group and Object links...........................................................................................................62
2.3.1 Example of a circuit................................................................................................................65
2.3.2 Object links to slave objects...................................................................................................66
2.3.3 Object links to a group in a different AS.................................................................................68
2.4 Input/Output interfaces...........................................................................................................70
2.5 Output interfaces....................................................................................................................72
2.5.1 Outputs for Setpoint function..................................................................................................72
2.5.2 Outputs for testing and as Interface to the OS.......................................................................72
2.5.3 Output status for connection to other blocks..........................................................................76
2.6 Hardware outputs...................................................................................................................82
2.7 Engineering Errors.................................................................................................................84
3 Time characteristics....................................................................................................................................87
4 Message characteristics.............................................................................................................................89
5 Module States.............................................................................................................................................93
6 Operator Commands..................................................................................................................................95
7 Feature Bits................................................................................................................................................97
8 OS Permissions........................................................................................................................................101
9 I/O-bar of C_DRV_1D...............................................................................................................................103
10 OS-Variable table.....................................................................................................................................113
11 Variable details.........................................................................................................................................117
11.1 Variable details COMMAND.................................................................................................117
11.2 Variable details ExtCmd.......................................................................................................118
11.3 Variable details MSG8_EVID...............................................................................................119
11.4 Variable details VISU_OS....................................................................................................120
11.5 Variable details INTFC_OS..................................................................................................121
11.6 Variable details STATUS.....................................................................................................122
11.7 Variable details STATUS2...................................................................................................123
11.8 Variable details STATUS3...................................................................................................124
11.9 Variable details MAI_STA....................................................................................................125
Calling OBs
All CEMAT Functions must be installed in the same OB, which is preferable OB1. The System
Chart SYSPLCxx contains infrastructure blocks which must be called at the beginning (Runtime
group OB1_START) and at the end (Runtime group OB1_END) of this OB.
The application program must be called between OB1_START and OB1_END.
Calling of the CEMAT blocks in a cyclic interrupt OB (OB34 or OB35) is possible, but only if the
complete program is called in the same cyclic interrupt OB. In this case the infrastructure blocks
must as well be moved to the cyclic interrupt OB (see Engineering Manual chapter Tips &
Tricks).
Operating modes
Module Type C_DRV_1D can be used to control all kind of unidirectional drives. Start/stop can
be carried out in three different operating modes:
● In "automatic mode" the drive is started/stopped by a superordinated group module.
All process interlocks and protection interlocks are effective.
● The "manual mode" allows individual start/stop via operator faceplate of the drive.
Different interlocking levels exist, which must be configured via Feature bits.
● In "local mode" the drive can be started and stopped by the locally installed switches or
pushbuttons.
Only the general protection interlock and the essential interlocks are effective.
The following table shows which mode change is permitted:
Standard Signals
The following standard signals are monitored by the unidirectional drive block:
● Contactor feedback FbkRun in conjunction with the contactor output ContOn
● Electrical availability ElAvail
● Overload or Bimetal Overload
Additional field switch signals allow local control via field switches or pushbuttons:
● Field switch ready signal AutModLo (Position switch or Repair switch)
● Field switch stop signal StopLoc (Stop local)
● Field switch start signal StartLoc (Start local)
The function of the field switch signals may differ from plant to plant. Therefore the function
must be configured via Feature bits. Refer to "Hardware Inputs", "Feature bit options for
Field switch (Local switch) signals"
If the drive is in automatic or in manual mode and the drive is in operation, a wrong status at
any of the above mentioned signals leads to an alarm message.*)
*) The message can be of type "fault" (Alarm – high) or "warning" (Warning – high), depending
on the block settings.
Priorities for alarm messages:
*) The priority between ElAvail and Overload can be reversed via input MsgPrio.
● Process feedback ProFB not effective in local mode and in manual mode
non-interlocked
Protection Signals
If additional protection interlocks exist for the drive or for the equipment, those signals have to
be linked to an Annunciation block C_ANNUNC or C_ANNUN8 in order to create an alarm. In
order to stop the drive in case of a fault an output of the annunciation block has to be connected
to the protection interlock of the drive. We distinguish between:
The following table gives an overview which protection interlock is effective in which mode.
This must be considered also in case of an operation mode change.
X = effective
*) With a special feature bit setting interface IntProtA will be effective in local mode as well
and can be bypassed with Local start command StartLoc.
Process interlocks
Process interlocks can be used in order to enable or disable the drive operation dependent on
a process condition, like "previous drive/device is running" or a process signal. If the process
interlocks are not fulfilled, no alarm is created. This implies that for diagnosis purpose the
interlock blocks must be used (if necessary also additional C_ANNUNC blocks).
The following process interlocks are available and can be used as per definition. Refer to
"Change of operation mode", "Feature bit options for mode change").
X = effective
*) the evaluation of the essential interlocks in local mode can be disabled via Feature bit
settings.
**) the evaluation of the stop interlock IntStop in manual mode can be enabled via feature bit
settings.
Sporadic mode
The sporadic mode allows start and stop of a device dependent on a process condition. With
the start command in automatic mode (group start command) the device gets "activated" and
will then be ready for start/stop via interface Sporadic:
Process parameters
Through process parameters the following values can be configured online:
Note
Via Feature bits the preferred interlocking level is defined (when switching the drive into manual
mode via interface ManModOn or via GR_LINK). Possible modes are enabled via OS
Permission.
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.
SIMOCODE drives
If SIMOCODE is used in CEMAT, the communication between the drive block and the
SIMOCODE can be carried out via adapter block C_SIMOS or C_SIM_AD.
An additional button in the drive faceplate opens the faceplate of the adapter block in order to
display the SIMOCODE details.
The percentage value of current and power are directly displayed in the faceplate of the motor.
Subcontrol Function
If SINAMICS or ROBICON is used with CEMAT, the communication between the drive block
and the Frequency Converter is carried out via adapter block C_SINA or C_ROBI.
The C_DRV_1D block gives the start/stop command to the C_SINA or C_ROBI and receives
the feedback and a summarizing fault.
The faceplate of the adapter blocks can be opened via button ‘SU’ in the C_DRV_1D faceplate.
The same method can be used for any kind of Subcontrol function from a sub supplier (weigh
feeders, filter, grate cooler, etc.).
Setpoint Function
This function can be used to enter a setpoint (e. g. the Speed of a Variable Speed Drive). If
the function is enabled, the drive faceplate shows the setpoint and the Actual Value.
The setpoint can either be entered via drive the faceplate (via direct entry or 3-step operation),
or transmitted by the program, via external setpoint SP_Ex (e. g. from a PID Controller).
The setpoint is validated for Low and High Limits and written to the output SP_Out (which can
be used for the connection to a VSD block).
Application examples:
● An acknowledge command (pulse) is needed for the acknowledgement of an external
device. Customer wants the acknowledgement through the drive faceplate.
● The drive needs to be switched from slow to fast mode. Speed change is possible via
faceplate button or via input UserPulse and output UserOut can be used to toggle the
speed. The drive faceplate shows the actual mode.
Rapid stop
Option for Rapid stop via Operator Station exists. Via right mouse-click on the block icon the
Rapid stop push-button appears.
The Rapid stop function must be enabled via feature bit setting:
If Feature2.bit11 = TRUE the stop code and the time is written to the output LaStopRe.
Note
If Fault reset function is enabled at the C_DRV_1D, the function must as well be enabled for
all linked C_ANNUNC, C_ANNUN8, C_PROFB, C_PROFBx and C_MEASUR blocks.
In this case make sure that for the connected Process feedback blocks (C_PROFB or
C_PROFBx) Feature.bit14 = FALSE!
With OS_Perm.bit4 = TRUE the Operator can enable the Power Management.
After the Power Management is enabled the drive can be blocked via input PMblock.
1.8 Visualization
In the block icon of the unidirectional drive the most important operation status are displayed
(stopped, running, operating mode, fault). Refer to Variable Details. Control functions and
detail information are only available after opening the faceplate.
For status information the following variables exist:
FbkRun (ERM)
ElAvail (ESB)
Overload (EBM)
AutModLo (EVO)
Note
The behavior can be changed via feature bit options, e.g. if a position switch (1-Signal =
Automatic; 0-Signal = Local) is used. In this case, 0-Signal at parameter AutModLo enables
starting and stopping via field switch signals StartLoc/StopLoc.
If the drive is running in automatic mode or manual mode, 0-Signal at parameter AutModLo
stops the drive together with the alarm message 'Local'.
StopLoc (ESP)
StopLoc 0 = local stop: field switch stop signal Basic state 1-Signal
Format BOOL
The StopLoc parameter is used to stop the motor in local mode. This is a break contact, i.e.
the 0-signal stops the motor.
By default, the local stop StopLoc is active in all operating modes.
Note
The behavior can be changed via feature bit options.
StartLoc (ESR)
StartLoc 1 = local start: field switch start signal Basic state 0-Signal
Format BOOL
The StartLoc parameter is used to start the motor in local mode. A rising edge at
StartLoc starts the motor.
Note
The local start pushbutton must be pressed continuously until the FbkRun contactor feedback
message arrives. For safety reasons, the signal is not memorized.
Local start is only possible if the motor is switched into local mode.
Note
The behavior can be changed via feature bit options.
Feature.bit3-12 can be used to adapt the Field switch signals to the requirement of the
plant.
Default settings
● In the default settings signal AutModLo is used as a repair switch (must have 1-Signal in
all operating modes) → Feature.bit8 = FALSE.
At the same time Feature.bit9 and Feature.bit10 must be FALSE and
Feature.bit12 is not relevant.
● A rising edge at StartLoc starts the drive in local mode. The drive will be running
continuously → Feature.bit5 = FALSE.
● Local start is only active if the local mode is enabled → Feature.bit3 = FALSE.
● No start-up-warning is given in local mode Feature.bit6 = FALSE.
● A falling edge at StopLoc stops the drive in Local mode. StopLoc is active in any mode
→ Feature.bit4 = TRUE.
If the drive is running in Automatic mode or Manual mode, 0-Signal at parameter StopLoc
stops the drive together with the alarm message 'Local stop'.
● Switching a running drive from Local mode to Automatic or Manual mode is possible without
interrupt → Feature.bit7 = TRUE.
● The Local mode needs to be enabled via operator station. The position switch does not
force the drive to local mode Feature.bit11 = FALSE.
● With Feature.bit5 = TRUE the local start is not memorized and the local mode is an
inching mode. As long as signal StartLoc has 1-Signal the drive will be started.
StartLoc = 0-Signal stops the drive.
● With Feature.bit6 = TRUE a start-up warning is created also in Local mode. Before
the start command is given to the contactor, output WarnAct is set for time WarnTi. The
start command at StartLoc is not memorized, which means the start button must be
pressed continuously until the start-up warning is completed and the drive is running.
● With Feature.bit7 = TRUE switching a running drive from Local mode to Automatic/
manual mode does not stop the drive, if the interlocking conditions are fulfilled. This is only
possible if Feature.bit8 = FALSE.
Note
Feature.bit7 is not evaluated if Feature.bit19 (StartAut switches drive to
Automatic mode) = TRUE. In this case Feature.bit7 is considered as TRUE.
● With Feature.bit10 = TRUE, the matrix corresponds to former CEMAT Standard 025
(Caima). The evaluation of the signals AutModLo and StartLoc is as follows:
Note
On order to have the same matrix chosen for the entire plant, Feature.bit9 and
Feature.bit12 should be set the same way for unidirectional drives as for bi-directional
drives and dampers.
If you have different requirements for your Field switch, please contact the competence center
for assistance.
Valid combinations
Not all combinations are valid. Below you find possible feature settings
● AutModLo is used as position switch (1-Signal = Automatic; 0-Signal = Local)
● AutModLo is used as repair switch (local isolated) and must have 1-Signal in all operation
modes. 0-Signal at AutModLo will stop the drive.
If you have different requirements for your Field switch, please contact the competence center
for assistance.
IntStaE
Typical application:
Lubrication system must be running before start of the mill.
Structure variables:
IntStaE.Value Signal Basic state 1-Signal
Format BOOL
IntStaE.ST Signal status Default: 16#FF
Format BYTE
*) The evaluation of the essential start interlock in Local mode can be suppressed via feature
bit setting:
If Feature2.Bit1 = TRUE, the essential interlocks are not evaluated in Local mode.
IntStart
The fan can be started only with closed fan damper. For this, the interface IntStart must
be connected with the signal PosSig1 of the damper. The run signal of the fan must be
connected to the inching enable of the damper, i.e. as soon as the fan is operating, the damper
can be opened or positioned.
The start command of group CmdOn goes simultaneously to damper direction 1 and to the fan.
As soon as the damper has reached limit position 1, the start interlock of the fan has 1-signal
and the fan is switched on. See Engineering Manual, chapter Engineering examples.
Structure variables:
IntStart.Value Signal Basic state 1-Signal
Format BOOL
IntStart.ST Signal status Default: 16#FF
Format BYTE
IntOpE
Note
Make sure that you don't allow the Manual mode only protections and the Manual mode non-
interlocked for these drives.
Structure variables:
IntOpE.Value Signal Basic state 1-Signal
Format BOOL
IntOpE.ST Signal status Default: 16#FF
Format BYTE
*) The evaluation of the essential start interlock in Local mode can be suppressed via feature
bit setting:
If Feature2.Bit1 = TRUE, the essential interlocks are not evaluated in Local mode.
IntOper
Structure variables:
IntOper.Value Signal Basic state 1-Signal
Format BOOL
IntOper.ST Signal status Default: 16#FF
Format BYTE
IntProtG
Note
Always connect output OutSig of the appropriate annunciation block to the protection
interlock of the drive, in order to consider possible time delays or simulations for both, message
and drive interlocking.
Typical application:
All signals concerning operator and machine safety must be effective at any time (e.g. pull-
rope switch).
Structure variables:
IntProtG.Value Signal Basic state 1-Signal
Format BOOL
IntProtG.ST Signal status Default: 16#FF
Format BYTE
IntProtA
Note
Always connect output OutSig of the appropriate annunciation block to the protection
interlock of the drive, in order to consider possible time delays or simulations for both, message
and drive interlocking.
Typical application:
A belt drift switch stops the drive in Automatic mode. However, it must be possible to start the
drive in Local mode to align the belt.
Structure variables:
IntProtA.Value Signal Basic state 1-Signal
Format BOOL
IntProtA.ST Signal status Default: 16#FF
Format BYTE
Enable IntProtA in Local mode with “override” via local start button StartLoc:
The evaluation of interface IntProtA can be adapted in order to be effective in Local mode
as well, but a 1-Signal at StartLoc input bypasses the Interlocking condition.
For the alignment of the belt, the supervision of the belt drift switch is bypassed as long as the
local start button StartLoc is pressed.
The evaluation of interface IntProtA in Local mode us defined via feature bit setting:
IntStop
Structure variables:
IntStop.Value Signal Basic state 1-Signal
Format BOOL
IntStop.ST Signal status Default: 16#FF
Forma tBYTE
By default the stop interlock IntStop is effective only in Automatic mode. If the stop interlock
shall be effective in Manual mode as well, this can be achieved via feature bit setting:
If Feature2.bit3 = TRUE, the stop interlock is also evaluated in Manual mode. This applies
to all manual modes, but stop delay StpDelTi is not considered in Manual mode..
Sporadic (ESPO)
Typical application:
A pump may be started and stopped depending on a pressure signal.
Note
The drive status "OFF+activated" is indicated by a grey drive symbol plus additional indication
'SPO'.
The Sporadic ON/OFF function is made for operation in automatic mode, in order to start and
stop a device according to a process condition. If the drive is started in manual or local mode
the status of interface Sporadic is ignored.
Change from Manual mode, Local mode or Out of Service mode → Automatic mode:
→ Once in Automatic mode the drive will follow interface Sporadic
ProFb
Structure variables:
ProFb.Value Value Basic state 1-Signal
Format BOOL
ProFb.ST Signal status Default: 16#FF
Format BYTE
MonOnly
Note
If the motor is in Out of Service mode it will not be forced to local mode but it will show “running”
if the motor was started.
For switching into Manual mode via interface ManModOn or via GR_LINK, the interlocking level
is set according to the feature definition:
Note
Only one out of three Feature.bit16-18 can be TRUE at the same time. If all
Feature.bit16-18 are set to FALSE, the drive will be switched into Manual mode
interlocked.
Mode change via program can be inhibited by setting the following feature bits to FALSE:
Note
Feature.bit25 of the corresponding group must be TRUE as well!
Using GR_LINK interface does not allow any individual or conditional connection. If this is
required, you have to use the interfaces AutModOn, ManModOn, LocModOn and
OoSModOn for the group-wise mode change.
Note
Out of service mode can not be selected via GR_LINK interface!
AutModOn
ManModOn
Note
The button texts for the start and stop buttons in the faceplate of the drive can be configured
via Property Text 0 and Text 1. Default Texts: Text 0 = "Off", Text 1 = "On"
LocModOn
Note
Switching into local mode via LocModOn is not possible while the drive is running.
OoSModOn
Note
Forcing to service mode has the highest priority and stops the drive!
StaByEn (ESTB)
MsgEn (EMFR)
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 messages interface MsgEn of the drive block.
If MsgEn has 0-Signal, the drive 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 drive fault is not shown in the summarizing indication of group and
route and not listed in the status call.
Exception: If StartAut has 1-Signal the drive fault is shown in the summarizing indication of
the group and route and it is listed in the status call.
MsgPrio
GrFltLck (EMZS)
GrStaLck (GFSO)
GrStaLck 1 = don't incl. in group sum. ind.+status call Basic state 0-Signal
Format BOOL
1-Signal at input GrStaLck completely deselects the drive for the Group Summarizing fault
and for the Group Status Call.
The function is similar to interface GrFltLck but the drive is excluded from status call as well.
LampTest (ELPZ)
Note
Using LampTest the lamp test interface at the C_PUSHBT module must not be connected.
Ack (EQIT)
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 drives. See Engineering Manual, chapter AS-Engineering.
Via Feature bit settings the internal acknowledge can be disabled, in order to allow exclusively
the acknowledgement via interface Ack:
With Feature2.bit27 = TRUE only the interface Ack is active for acknowledgement.
Note
If additional Fault Reset is enabled the fault status bits are not automatically acknowledged
with Ack. After clearing the fault the Operator has to press “Fault reset” in the drive faceplate.
StartAut (EBFE)
Note
Interface StartAut should not be connected with a continuous signal as a drive fault can then
not be acknowledged! If a continuous signal is required, one must take care that the StartAut
has signal zero when there is a fault.
Via feature bit setting the start command can be used to switch the drive to Automatic mode:
If Feature.bit19 = TRUE, a rising edge at StartAut switches the drive to Automatic mode.
Note
If Feature.bit19 = TRUE, the status of Feature.bit7 (No stop after switching from local
to auto/manual) is not evaluated. It is considered as TRUE.
Switching the drive from Local mode or Manual mode via to Automatic mode via StartAut
is only possible if the corresponding feature bits are enabled.
StopAut (EBFA)
Note
If a drive belongs to more than one group or route, it may be necessary to use the inverted
permanent command on signal PeCmdOn of the associated groups or routes. But in this case
it has to be considered that in this case a shut down interrupt is not possible.
QuickStp (QSTP)
DSigBQ
DSimAct
PMinvol
Structure variables:
PMinvol.Value Signal Basic state 0-Signal
Format BOOL
PMinvol.ST Signal status Default: 16#FF
Format BYTE
PMblock
Netfault
SimoStat
Structure variables:
SimoStat.Value Status Default: 16#00
Format BYTE
SimoStat.ST Signal Status Default: 16#FF
Format BYTE
SubCFp
Note
The connection from the Subcontrol block to structure input SubCFp is essential; otherwise
the faceplate of the Subcontrol function can not be opened via the drive faceplate.
SubCFlt
Structure variables:
SubCFlt.Value Value Basic state 0-Signal
Format BOOL
SubCFlt.ST Signal Status Default: 16#FF
Format BYTE
AV (PV)
Structure variables:
AV.Value Value Default: 0.0
Format REAL
AV.ST Signal status Default: 16#FF
Format BYTE
Note
Only the selected measure is displayed in the drive faceplate.
AV_Stat (PV_Stat)
Structure variables:
AV_Stat.UNIT Unit Default: %
Format STRING[8]
AV_Stat.STATUS Status Default: 16#00
Format DWORD
Note
Only the status and the unit of the selected measure are displayed in the drive faceplate.
AV_Perc
The percentage value of an Analog Process Value such as motor current can be linked to the
drive via input AV_Perc.
Structure variables:
AV_Perc.Value Value Default: 0.0
Format REAL
AV_Perc.ST Signal status Default: 16#FF
Format BYTE
Note
In case of a measuring value the upper limit 1 of the measure corresponds to 100% value of
motor current. In the bar of the drive faceplate 0-130% are displayed.
The text for the Faceplate description is defined in the object properties of parameter
AV_Perc.Value under "Identifier". The default value is "I =".
As the measuring value does not necessarily need to be a current value (often the power is
used instead). In this case it is required to modify the text under "Identifier".
Note
The texts under "Identifier" are internal variables and for that reason a modification of the text
requires a new OS Compile.
Feature.bit29 = TRUE enables the setpoint function. In the drive faceplate the input field
and the display of the actual Setpoint and the Process value is activated (visible).
OS Permissions for Setpoint function:
SP_ExEn
SP_TrkPV
SP_Os
SP_Ex
Structure variables:
SP_Ex.Value Value Default: 0.0
Format REAL
The Unit is transmitted via Property "Unit" and the default setting is 'rpm'.
SP_Ex.ST Signal status Default: 16#FF
Format BYTE
SP_HiLim
SP_LoLim
PV (PV_IN)
Structure variables:
PV.Value Value Default: 0.0
Format REAL
The Unit is transmitted via Property "Shortcut" and the default setting is 'rpm'.
PV.ST Signal status Default: 16#FF
Format BYTE
Feature2.bit29 = TRUE enables the user output function. The diagnosis view of the drive
faceplate shows the status indication and the button.
OS Permissions for User button:
UserFbk
UserPulse
TEST_OSS
SimuStatus
SimuSave
SimuSPSave
MSG8_EVID
MSG8_EVID2
COMMAND
ExtCmd
Note
To permit the modification of the process values from the faceplates, they must not be
connected in the CFC.
FbkMonTi
Note
The minimum feedback monitoring time is 2 seconds.
If an already running drive loses the contactor feedback, FbkMonTi is not considered and the
drive will be stopped immediately.
FbkOffTi
Note
The minimum feedback off monitoring time is 2 seconds.
If an already running drive looses the contactor feedback, FbkOffTi is not considered.
StaDelTi
StpDelTi
WarnTi
There is an option to trigger the start-up warning in local mode as well, using the same timer.
This function must be enabled by a feature bit:
Feature.bit6 = TRUE will trigger the start-up warning also in case of a local start command
StartLoc and the contactor ON command ContOn is delayed by this time.
Note
For security reasons the local start command is not memorized and the button must be pressed
continuously until the timer WarnTi has elapsed and the drive is running.
If in Automatic mode a start-up-warning is required for the individual device (in addition to the
start-up warning of the group) this can be achieved via the following feature bit setting:
With Feature2.bit6 = TRUE the start-up warning is triggered also in case of an automatic
start via StartAut and the contactor ON command ContOn is delayed by this time.
Note
In Automatic mode, in addition to the start-up warning time WarnTi the contactor ON command
is delayed by the start delay time StaDelTi, which is triggered after the start-up warning time
WarnTi has elapsed.
This function may be useful for long belt conveyors where a separate start-up warning is
required.
UserStatus
Note
Make sure that modifications in standard faceplates are documented and saved. CEMAT
updates will overwrite your modifications.
SelFp1 (UserFace)
Note
The button description for the User Function button in the standard faceplate is fixed, but the
tooltip text can be entered via Property 'OS additional text'. Default value can not be configured
as a property of the block input. Value can only be defined in the CFC.
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, Feature2 and OS_Perm are only read from the internal memory.
The HMI always shows the status of the internal memory.
Note
For a running plant this means that for any modification of Feature bits or OS Permissions the
module must be set to Out of Service mode.
Note
Both, the Feature bit settings of the Feature Master block and the Feature bit settings at the
block input Feature and Feature2 are only transferred to the internal memory if they are
consistent (ErrorNum = 0).
FeatMaster
FeatMaster Use OS permission and Feature bits from master Basic state 1-Signal
Format BOOL
Input FeatMaster is set to “S7-link = false” (cannot be connected).
With 1-Signal at input FeatMaster, the selected bits of the Feature Master block inputs
Feature, Feature2 and OS_Perm are transferred to the CEMAT block, when the module
is in configuration state. These bits cannot be adjusted individually.
With 0-Signal at input FeatMaster the settings at the Feature Master block are not relevant
and all Feature bits and OS Permissions must be adjusted individually per instance.
Note
In this case, make sure that the settings which normally come from the Feature Master are
consistent and correct.
OS_Perm
Note
It is not allowed to connect any logic to OS_Perm input.
OpSt_In
Feature
Note
It is not allowed to connect any logic to Feature input.
Feature2
Note
It is not allowed to connect any logic to Feature2 input.
EventTsIn
Note
Block EventTs must be installed in a Cyclic interrupt OB. The installation of block EventTs in
OB1 is not permitted and will not work!
Group/Route links
Each drive block, annunciation block or measurement block must be linked to a group or route
in order to collect the status of these objects for summarizing indications.
The group link is essential for control and diagnosis and comprises the following functions:
● All objects, linked to the group (or route) are listed in the group (or route) object list.
● All objects, linked to the group (or route) are highlighted in the process picture with button
"Show related objects".
● The faults of all objects, linked to the group (or route) are included in the summarizing fault
indication of the group (or route).
● The warnings of all objects, linked to the group (or route) are included in the summarizing
warning indication of the group (or route).
● In case of a dynamic fault during the startup of the group, the group start will be interrupted.
A drive can be linked to two groups or routes via GR_LINK1 and GR_LINK2. If a drive belongs
to more than two groups or routes the additional block C_MUX must be inserted, which provides
5 additional link interfaces.
Note
The main group (or main route) should be connected to GR_LINK1! This is the one which is
opened with a click on button "Main group" in the drive faceplate.
Via additional feature bit settings, control commands can also be transmitted through the group/
route link interface.
● With Feature.Bit25 = TRUE the mode change commands from the group or route are
automatically transmitted to the allocated drives/devices. No further connection to
AutModOn, ManModOn and LocModOn is needed. Of course, the permission for the
individual modes must be available and Feature.bit25 of the group or route must be
TRUE as well.
See also "Interfaces for mode change".
Note
Out of Service mode can not be selected via GR_LINK interface!
GR_LINK1
Note
GR_LINK1 must be used for the main group!
Structure variables:
GR_LINK1.Link Link Default: 0
Format INTEGER
GR_LINK1.Command Group / Route Command Default: 16#00
Format WORD
GR_LINK2
Structure variables:
GR_LINK2.Link Link Default: 0
Format INTEGER
GR_LINK2.Command Group / Route Command Default: 16#00
Format WORD
MUX_LINK
Note
If a C_MUX block is used, the programming order is very important. The C_MUX must be called
before the drive block!
If the same C_MUX block is connected to more than one object (e. g. the drive and
annunciations and measures of the same equipment), it is essential that no different group link
(or C_MUX) is programmed between those objects.
Structure variables:
MUX_LINK.Point_GRL Pointer Default: 0
Format INTEGER
MUX_LINK.Command Group / Route Command Default: 16#00
Format WORD
Note
Check the runtime sequence! The C_MUX module must be called before the drive. For the
other modules the run sequence is as follows: first the drives/devices, then the associated
routes and finally the associated groups.
Note
Some people use one C_MUX block and connect its output to a number of drives/devices,
annunciations and measurements.
If you do so, make sure that the C_MUX is called before all the other objects and that no other
C_MUX call comes in between.
We don't recommend using the same C_MUX if the blocks are located in different runtime
groups.
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.
● Block icons for Option 4: The warnings of all objects, linked to the drive are indicated by
yellow color of the Block icon (HAC).
Note
It is not allowed to use the Object link and the group/route link at the same time: If O_LINK is
used, GR_LINK1 and GR_LINK2 or C_MUX must not be connected!
O_LINKQ
Structure variables:
O_LINKQ.iDB Instance DB master object
Format INTEGER
O_LINKQ.iDW DW number NO_OF_FT in master object
Format INTEGER
O_LINKQ.Command Group / Route Command
Format BYTE
O_LINKQ.Status Status master object
Format BYTE
Note
C_RECV_G can only be linked to a C_GROUP module. Linking to routes is not permitted and
will not work!
In the AS of the Cemat Objects the output O_LINKQ of block C_SEND_G is connected to input
O_LINK of the drives/devices, annunciations, measurements and process feedback blocks.
O_LINK
Structure variables:
O_LINK.iDB Instance DB master object Default: 0
Format INTEGER
O_LINK.iDW DW number NO_OF_FT in master object Default: 0
Format INTEGER
O_LINK.Command Group / Route Command Default: 16#00
Format BYTE
O_LINK.Status Status master object Default: 16#00
Format BYTE
Note
If annunciations, measurements or process feedback blocks belong to the drive, they don't
need to be connected to output O_LINKQ of the C_SEND_G block.
They can also be programmed as slave objects and connected to output O_LINKQ of the drive.
ResTimOS
MaiRTm
MaiRTh
MaiCo
MaiCoh
MaiCntSt
MaiCntTr
MaiFtDur
MAI_STA
MaiCorr
MaiCyc
Setpoint function
Using the Setpoint function, a Setpoint (e. g. the Speed of a Variable Speed drive) can directly
be entered via the drive faceplate. The setpoint is checked for Low limit SP_LoLim and High
limit SP_HiLim and directly transmitted to the output SP_Out.
The Setpoint function must be enabled via feature bit:
Feature.bit29 = TRUE enables the Setpoint function. In the drive faceplate the input field
and the display of the actual setpoint and the process value is activated (visible).
SP_Out
Structure variables:
SP_Out.Value Value
Format REAL
The unit is transmitted via property "Unit" and the default setting is 'rpm'.
SP_Out.ST Signal status
Format BYTE
INTFC_OS
VISU_OS
VISU_OS Interface to OS
Format BYTE
Interface to OS
For more information see Variable details.
STATUS
STATUS Interface to OS
Format DWORD
Interface to OS
For more information see Variable details.
STATUS2
STATUS2 Interface to OS
Format DWORD
Interface to OS
For more information see Variable details.
STATUS3
STATUS3 Interface to OS
Format DWORD
Interface to OS
For more information see Variable details.
ALARM
FeatureOut
FeatureOut2
OS_PermOut
OS_PermLog
FWCopyMaster
FW2CopyMaster
OSCopyMaster
OpSt_Out
DelayCon
NO_OF_I
FT1
Structure variables:
FT1.D1 Instance DB Object
Format INT
FT1.D2 Instance DB Master Object
Format INT
FT1.D3 Object Type
Format INT
FT1.D4 Status word object
Format WORD
RunSig
If Feature.bit27 = TRUE the output RunSig is also created in manual mode with reduced
interlocks.
Structure variables:
RunSig.Value Signal
Format BOOL
RunSig.ST Signal status
Format BYTE
DynFlt (EST)
Note
In the following cases the drive fault cannot be acknowledged:
● If the ON-command is permanently active;
● With a welded contactor (FbkRun = 1-Signal).
Output DynFlt is used as message trigger of annunciation blocks (in case of drive fault
annunciations), see interface MsgTrigg of C_ANNUNC block or MsgTrig1 – MsgTrig7 of
C_ANNUN8 block.
Output DynFlt is also used transmit "not empty" information to the group in case of a trip of
a running equipment, see interface MatFlt of C_GROUP block. Only drives which are
involved in the material transport are connected to interface MatFlt of the group.
The information can also be transmitted to the group via feature bit setting:
Fault (SST)
Fault Fault
Format BOOL
A 1-Signal at output Fault means that at least one fault is present.
LaStopRe
If Feature2.bit11= TRUE the stop code and the time is written to the output LaStopRe.
Structure variables:
LaStopRe.Value Reason
Format INT
LaStopRe.STime Stop time
Format STRING [22]
Structure variable LaStopRe.Value contains the code for the last stop reason. The texts are
defined in a dataset in @Overview1.pdl (Master_Stoptext_Dataset).
5 Rapid Stop
6 Stop by Mode Change
7 Stop by MonOnly
10 Available fault
11 Overload fault
12 Local switch fault
13 Contactor feedback fault
16 Process feedback trip
17 Local stop fault
18 Simocode fault
19 Subcontrol fault
20 Operation Interlock
21 Operation Interlock essential
26 Sporadic interface
27 Protection Interlock general
28 Protection Interlock auto/manual
29 Stop by Powermanagement
38 Process feedback start-up fault
WarnAct (HORN)
With Feature.bit6 = TRUE the output WarnAct is also created with local start command
StartLoc.
Note
For security reasons the local start command StartLoc is not memorized and the button must
be pressed continuously until the timer WarnTi has elapsed and the drive is running.
With Feature2.bit6 = TRUE the output WarnAct is created with automatic start command
StartAut.
Note
In Automatic mode, in addition to the start-up warning time WarnTi the contactor ON command
is delayed by the start delay time StaDelTi, which is triggered after the start-up warning time
WarnTi has elapsed.
RunSigSp
SimActQ
AutoAct
ManuAct
Note
Connection is not needed if Feature.bit26 = TRUE.
LocalAct
Note
Connection is not needed if Feature.bit26 = TRUE.
OoSAct
Note
Connection is not needed if Feature.bit26 = TRUE.
PMrel
MaintRQ
MaintAL
MaiRTm_Q
MaiRTh_Q
MaiCo_Q
MaiTr_Q
MaiFt_Q
MaiCyc_Q
ContOn (EBE)
ContOn Contactor ON
Format BOOL
The output ContOn is used to trigger the main contactor.
Lamp (ELS)
UserOut
ST_Worst
If Feature.bit22 = TRUE, the worst status is additionally transmitted to the block outputs
(and via this to the next block).
The worst status of the binary signals DSigBQ, DSimAct, IntStaE, IntStart,
IntOpE, IntOper, IntProtG, IntProtA, ProFB, PMinvol, SimoStat and
SubCFlt is transmitted to output RunSig.
The signal status of signal SP_Ex is transmitted to output SP_Out.
ErrorNum
Note
Only one error number can be indicated at a time!
*) The message class for MSG8_EVID SIG1 to SIG8 is by default configured as “Alarm - high".
In case of a warning drive the message class for MSG8_EVID SIG1 to SIG8 must be changed
to “Warning - high" and the Feature2.bit2 must be configured.
Feature2.bit2 = TRUE changes the block to warning mode. This results in a yellow
indication for Group status call and block icon and the group start is not interrupted by a trip
of this drive.
The operating messages for “Local start” and “Local stop” are only created if Feature2.bit0
= TRUE.
1*) Via Plausibility logic only one of three indications (Available, Overload or Local) is given.
All other indications are shown simultaneously.
2*) The priority between Available and Overload can be reversed via 1-Signal at input
MsgPrio.
3*) If the motor is not running, contactor feedback fault results in a dynamic fault.
Acknowledgement is not possible as long as contactor feedback is present.
4*) The messages for "Process Feedback fault", "Protection fault" and "Simocode fault"
are not
created by the drive block itself, but by other CEMAT blocks (C_PROFB, C_ANNUNC and
C_SIMOS).
Feature2
The bits in Structure Feature2 and FeatureOut2 are used as follows:
A detailed description of the individual Feature bits can be found in the chapters above.
Please consider that the Feature bit settings can only be changed in configuration state. For
a running plant this means that the block has to be in Out of Service mode.
If the block is in configuration state and the feature bit settings are consistent (ErrorNum =
0), the Feature Master block settings and the status of Feature word Feature/Feature2
are transferred into the internal memory of the module.
Note
Do not connect any logic to input Feature and Feature2
A detailed description of the individual OS Permission bits can be found in the chapters above.
Please consider that the OS Permission settings can only be changed in configuration state.
For a running plant this means that the block has to be in Out of Service mode.
If the block is in configuration state the Feature Master block settings and the status of
OS_Perm are transferred into the internal memory of the module.
Note
Do not connect any logic to input OS_Perm.