C DRV 1D 009
C DRV 1D 009
C DRV 1D 009
0
Function Block Library ILS_CEM
Function Description
Edition 09/13
Safety Guidelines
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 to property damage only have no safety alert symbol. The 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
with a safety alert symbol indicates that minor personal injury can result if proper precautions are not
taken.
Caution
without a safety alert symbol indicates that property damage can result if proper precautions are not
taken.
Attention
indicates that an unintended result or situation can occur if the corresponding notice is not taken into
account.
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 device/system may only be set up and used in conjunction with this documentation. Commissioning and operation
of a device/system may only be performed by qualified personnel. Within the context of the safety notices in this
documentation qualified persons are defined as persons who are authorized to commission, ground and label devices,
systems and circuits in accordance with established safety practices and standards.
Prescribed Usage
Note the following:
Warning
This device and its components may only be used for the applications described in the catalog or the
technical description, and only in connection with devices or components from other manufacturers
which have been approved or recommended by Siemens.
Correct, reliable operation of the product requires proper transport, storage, positioning and assembly
as well as careful operation and maintenance.
Trademarks
All names identified by are registered trademarks of the 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
Siemens AG
Automation and Drives
Postfach 4848, 90327 Nuremberg, Germany
Siemens AG 2005
Technical data subject to change.
Siemens Aktiengesellschaft
Description of C_DRV_1D
Type/Number
Calling OBs
Function
General Function description
Visualization
Additional functions
Sequence Test
Operating principle
Hardware inputs
Input interfaces
Group and Object links
Process values
Input/Output interfaces
Output interfaces
Hardware outputs
Time characteristics
Message characteristics
Module States
Commands
4
4
5
5
6
6
6
7
7
9
21
27
29
30
34
35
35
36
36
I/O-bar of C_DRV_1D
37
OS-Variable table
43
Variable details
45
Description of C_DRV_1D
Type/Number
Module name:
Module no.:
C_DRV_1D
FB1001
Calling OBs
C_DRV_1D must be called in OB1 (MAIN_TASK).
Function
General Function description
Module Type C_DRV_1D can be used to control all kind of unidirectional drives in a cement
plant. Start/stop can be carried out in three different operating modes:
- In the automatic mode the drive is started/stopped by a superordinated group module.
- The single-start mode allows individual start/stop via operator faceplate of the drive.
- In the local mode the drive can be started and stopped by the locally installed pushbuttons
ESR (start button) and ESP (stop button).
The following standard signals are monitored by the unidirectional drive block:
- Contactor feedback ERM in conjunction with the contactor output EBE
- Electrical availability ESB
- Overload or Bimetal EBM
- Local Switch EVO (1-Signal = Remote; 0-Signal = Local)
- Local stop button ESP
- Local start button ESR
Additionally there is an option of a supervision of a speed monitor fault. A continuous signal
can or pulses can be evaluated (Software Speed monitor).
If the drive is in automatic or in single-start mode and the drive is in operation, a wrong status at
any of the above mentioned signals leads to an alarm message.
If additional protections are available 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:
- Protection interlock ESVG or IntProtG
- Protection interlock ESVA or IntProtA
Interlocks can be used in order to enable or disable the drive operation dependent on a
process condition, like "previous drive is running" or a process signal:
- Start interlock EEVG or IntStart
- Operating interlock EBVG or IntOper
- Sporadic ON/OFF ESPO
Visualization
In the block icon of the unidirectional drive the most important operation status are displayed
(stopped, running, operating mode, fault). Operation functions and detail information are only
available after opening the faceplate.
Additional functions
Link to a measured value
- By connecting the percentage value of a measure to the drive block, the power or current of
the drive in % can be displayed in the faceplate of the motor.
- An additional measure can be displayed in the drive faceplate, either through connection of the
physical output of measured value block or through connection of the output of an analog
value selection block to the drive.
SIMOCODE drives
If SIMOCODE is used, 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 C_SIMOS 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
Sometimes function blocks and faceplates from sub suppliers are used, as e. g. for weigh
feeders, filter, grate cooler etc. In order to have the same philosophy for all kind of equipment
(block interfaces, summarizing indication in the group) a normal Cemat drive block can be used
in order to give a start command to the subcontrol function. The general fault of the Subcontrol
will be indicated in the diagnosis picture of the drive.
An additional button in the operator faceplate of the drive can be used to open another faceplate
for the display of the detail information for the Subcontrol.
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 theSetpoint and the Actual Value.
The Setpoint can directly be entered via drive faceplate 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_O (which can be
used for the connection to a VSD block).
Sequence Test
In Sequence Test mode the motor can be started without hardware signals. The feedback of the
contactor and eventually a speed monitor are simulated. The hardware inputs (ESB; EBM;
EVO...) are still active and have to be simulated by a test program at the beginning of OB1
Cycle.
If driver blocks are used, the Output SIM_ON of the drive can be connected to input SIM_ON of
the Driver blocks to enable the simulation.
Operating principle
Hardware inputs
ERM
Feedback ON
Format BOOL
The ERM parameter must be connected. It is appropriate to use the feedback contact of the
main contactor for this purpose. The feedback is monitored in automatic mode and in the singlestart mode. The monitoring time for switching on the motor can be set with the parameter
FEEDBTIM. The monitoring time for switching off is 2s. An alarm is issued if no feedback occurs
and/or the monitoring time expires.
ESB
Electrical availability
Format BOOL
The ESB parameter is used to monitor the electrical availability of the motor. The electrical
availability is monitored in automatic mode and in single-start mode, and results in a shutdown
with an alarm.
EBM
Overload
Format BOOL
The EBM parameter is used to monitor the overload of the motor (bimetal). The overload is
monitored in automatic mode and in single-start mode, and results in a shutdown with an alarm.
EVO
Local switch
Format BOOL
The EVO parameter is used for the connection with the local switch of the motor. EVO = 1signal means automatic position and EVO = 0-signal means local position. No alarm signal
occurs in the control room in local mode.
In position Local (EVO = 0-signal) the motor can be started and stopped via ESR and ESP.
ESP
Local stop
Format BOOL
The ESP parameter is used to stop the motor in local mode. This is a break contact, i.e. the 0signal stops the motor.
By default the local stop ESP is only active if the drive is in local mode. Connecting a 1-signal to
LST_ACT, the local stop is always effective.
ESR
Local start
Format BOOL
The ESR parameter is used to start the motor in local mode. A 1-signal to ESR starts the motor.
Prerequisite for the local start of the motor is the local release (interface ELOC interface = 1signal) and the EVO switch positioned to Local (EVO = 0-signal).
Caution:
The local start pushbutton must remain pressed until the ERM contactor feedback
message arrives. For safety reasons, the signal is not stored.
Input interfaces
EEVG
Start interlock
Format BOOL
The drive can be started in automatic mode or single-start mode only if the start interlock has 1signal. 0-signal at interface EEVG prevents the start. In local mode the starting interlock is not
effective.
Typical application:
The fan can be started only with closed fan damper. For this, the interface EEVG must be
connected with the signal KVS1 of the damper. The run signal of the fan must be connected to
the inching release of the damper, i.e. as soon as the fan is operating, the damper can be
opened or positioned.
The start command of group GBE goes simultaneously to damper direction 1 and to the fan
drive. As soon as the damper has reached limit position 1 the start interlock of the fan drive has
1-signal and the fan drive is also switched on.
IntStart
Start Interlock
Format STRUCT
For function description, see EEVG. This interface can be connected with a structure output as
e. g. signal PosSig1 of a damper or output Out of an interlock bock, e. g. Intlk02.
Structure variables:
IntStart.Value
Signal
Signal status
Default: 16#FF
Format BOOL
IntStart.ST
Format BYTE
EBVG
Operating interlock
Format BOOL
The drive can run in automatic mode or single-start mode only if the operating interlock has 1signal. 0-signal at interface EBVG prevents the start or switches off the running drive. In local
mode the operating interlock is not effective.
Typical application:
Material transport: Only if the downstream drive is running may the following drive be started. As
soon as the downstream drive fails the following drive must stop as well.
For this, interface EBVG must be connected with run-signal EVS of the downstream drive. The
start command of group GBE goes simultaneously to both drives. As soon as the downstream
drive is running the operating interlock of the following drive has 1-signal and this drive is also
started.
IntOper
Operation Interlock
Format STRUCT
For function description, see EBVG. This interface can be connected with a structure output as
e. g. signal RunSig of the previous drive or output Out of an interlock bock, e. g. Intlk02.
Structure variables:
IntOper.Value
Signal
Signal status
Default: 16#FF
Format BOOL
IntOper.ST
Format BYTE
ESVG
Format BOOL
All signals which indicate a drive fault and which are not monitored by the drive module as per
standard must be connected to the protection interlock of the drive. A 1-signal means status
healthy, 0-signal means faulty.
Interface ESVG is effective for all operating modes of the drive.
Caution:
When the drive is switched off via ESVG the drive module does not generate an
alarm message. There is no summarizing fault indication at the group and the
protection interlock is not shown in the status call.
For the fault message one must program an annunciation module. To connect the
protective interlock one must use the output MAU of the appropriate annunciation
module and not the input signal of the fault so that a possible time delay is taken
into consideration.
Typical application:
All suppressor circuits concerning operator and machine safety and so which must be effective
all the time (e.g. pull-rope).
IntProtG
Format STRUCT
For function description, see ESVG. This interface can be connected with a structure output as
e. g. output OutSig of the annunciation block or output Out of an interlock bock, e. g. Intlk02.
Structure variables:
IntProtG.Value
Signal
Signal status
Default: 16#FF
Format BOOL
IntProtG.ST
Format BYTE
10
ESVA
Format BOOL
All signals which indicate a drive fault and which are not monitored by the drive module as per
standard must be connected to the protection interlock of the drive. A 1-signal means status OK,
0-signal means faulty.
Interface ESVA is effective only in automatic mode and single-start mode, i.e. in the case of a
fault the drive can still be operated in local mode.
Caution:
When the drive is switched off via ESVA the drive module does not generate an
alarm message. There is no summarizing fault indication at the group and the
protection interlock is not shown in the status call.
For the alarm message one must program an annunciation module. To connect the
protective interlock one must use the output MAU of the appropriate annunciation
module and not the input signal of the fault so that a possible time delay is taken
into consideration.
Typical application:
Belt drift switch: If the belt drift switch responds this means in automatic mode a drive fault.
However, it must be possible to start the drive in local mode to align the belt.
IntProtA
Format STRUCT
For function description, see ESVA. This interface can be connected with a structure output as
e. g. output OutSig of the annunciation block or output Out of an interlock bock, e. g. Intlk02.
Structure variables:
IntProtA.Value
Signal
Signal status
Default: 16#FF
Format BOOL
IntProtA.ST
Format BYTE
ESPO
Sporadic ON/OFF
Format BOOL
0-Signal at interface ESPO stops the motor without resetting of the command memory EKS.
The motor is still activated and restarts automatically with 1-Signal at this interface.
To stop the motor completely 1-Signal at EBFA or 0-Signal at EBVG is required. If the motor is
stopped by a fault, it must be restarted through the associated group.
Typical application:
A pump which is started and stopped depending on a pressure signal.
This interface is effective in automatic mode only. In Single start mode or local mode ESPO is
not evaluated. For the change of operations mode the following has to be considered:
- If the drive is running in Automatic mode and switched to Single start mode, it keeps running
continuously (without considering ESPO).
- If the drive is running in Single start mode and switched to Automatic mode, with the change
of the operation mode ESPO is evaluated:
If ESPO has 0-Signal the drive will be stopped completely (reset of EKS).
If ESPO has 1-Signal the drive will to run in sporadic mode.
11
EDRW
Format BOOL
If a continuous 1-signal is available for speed monitor supervision the speed monitor signal must
be connected to interface EDRW. At the same time the software speed monitor must be
disabled (REL_SSM = 0-signal)
A 1-signal at interface EDRW means that the motor is running and the Speed monitor has
responded. The Speed monitoring time can be set (process value SPEEDTIM). If the Speed
monitor does not provide a continuous 1-signal within the default time, the drive module
generates an alarm message.
The speed monitor supervision is only effective in automatic mode and in single-start mode.
REL_SSM
Format BOOL
REL_SSM must be connected with a 1-signal if you wish to use the function of the software
speed monitor. The EDRW interface is then no longer evaluated.
The 0-signal causes monitoring of the EDRW interface.
This interface is not operable through OS.
SW_SPEED
Format BOOL
If you get pulses from the speed monitor, the pulse input must be connected to interface
SW_SPEED. The software speed monitor function must be enabled via REL_SSM = 1-Signal.
The Speed monitoring time can be set (process value SPEEDTIM). If the Speed monitor does
not provide pulses within the default time (considering the tolerance value TOL_SSM), the drive
module generates an alarm message. Input-signal for software speed monitor.
The speed monitor supervision is only effective in automatic mode and in single-start mode.
Make sure that the duration of the pulses is long enough. If the OB1 cycle time is 100ms, pulses
and pause should be at least 200ms.
SM_EVS_I
Format BOOL
With 0-Signal at SM_EVS_I, EVS gets 1-Signal after speed monitor has 1-Signal and the speed
monitor supervision time has elapsed.
With 1-Signal at SM_EVS_I, EVS gets 1-Signal immediately with the 1-Signal of the speed
monitor.
REL_EBD
Format BOOL
Speed Monitor Bypass can only be enabled/disabled from the Diagnostic Picture. If the Bypass
is switched on the speed monitor supervision is not active.
12
Caution:
L_STA_WA
Format BOOL
With 0-signal at this parameter, no start-up warning is given in local mode.
With 1-signal at this parameter, by pressing the Local start button a start-up warning is given
and the contactor output EBE is delayed by the start-up warning time HORN_TIM.
Caution: For security reasons the local start button must remain pressed until the drive is
running!
NSTP_L_A
Format BOOL
This parameter is foreseen for specific project-standards. 1-signal at this parameter causes no
stop for running drives after switchover from local mode into automatic mode, if the interlocking
conditions are fulfilled.
Caution: Parameter NSTP_L_A has to be modified only after an explicit instruction from the
Cemat Development.
LST_ACT
Format BOOL
With 0-signal at this parameter the local-stop is not effective in automatic mode.
1-signal at this parameter enables the local stop in automatic mode too and an alarm will be
created.
ELOC
Format BOOL
A 1-Signal at this interface releases the drive for the local mode through the PLC, i.e. the drive
can be started/stopped via inputs ESR and ESP. The operating mode is changed by the
appropriate group. The group module sets in local mode signal GLO. This information is passed
on to the drive module by connecting interface ELOC with signal GLO of the appropriate group.
In local mode operation via the PLC only the protective interlock ESVG is effective. The
connection of interfaces EEVG, EBVG and ESVA is not analyzed in local mode. In local mode
no logic signal EVS is generated!
EEIZ
Format BOOL
A 1-Signal at this interface releases the single-start mode for the drive, i.e. the drive can be
started and stopped separately from the central control room. The operating modes are
changed by the appropriate group. The group module sets the single-start mode signal GES.
This information is passed on to the drive module by connecting the interface EEIZ with signal
GES of the appropriate group.
In single-start mode all interlocks of the drive are effective! Start is carried out after the set horn
time (process value HORN_TIM) has expired.
13
ESTB
Stand-by mode
Format BOOL
In the philosophy of CEMAT-Standards only the active plant sections can generate alarm
messages. This means, if a drive at stop is faulty this is indicated in the symbol at the flow
mimic but there will be no alarm message.
A 1-Signal at interface ESTB means that the drive is in stand-by mode. In this mode the drive is
monitored for availability even under stand still conditions. If a fault occurs when the drive is in
stand-by mode, an alarm message is generated.
ETFG
Inching release
Format BOOL
Interface ETFG must be connected with LOG1 if the drive is to be operated as a positioning
drive, i.e. it is to be switched ON and OFF in short intervals (<= 2s).
EMFR
Annunciation release
Format BOOL
With 0-signal at this interface the annunciation function is blocked.
Typical application:
In the case of a control supply voltage failure for MCC or field signals, one alarm message
would be triggered for each sensor signal. To prevent this one should connect the control
voltage signal to the annunciation release interface at the appropriate modules. This causes no
alarms to be generated. The cause of control voltage failure is generated by an annunciation
module which has to be engineered for this purpose.
Caution: If EMFR has 0-Signal the drive fault is not shown in the summarizing indication of
group and route and not listed in the status call.
EMZS
Format BOOL
A 1-signal on EMZS prevents that the dynamic and static fault is passed to the group. In the
status call the drive fault can still be seen.
Typical application:
To interlock a main drive together with the affiliated auxiliary drive one must connect the
feedback contact ERM and the ON command EBE of the auxiliary drive to the protective
interlock of the main drive and vice versa. In this case, the group would indicate a fault as soon
as one of the two drives is running. To prevent this one must connect ERM and EBE of the
auxiliary drive together with OR to interface EMZS of the main drive.
GFSO
Format BOOL
1-Signal at GFSO completely deselects the drive for the Group Summarizing fault and for the
Group Status Call.
14
ELPZ
Format BOOL
If one has several control desks with lamps and wants to test the lamps for each control desk
separately, one can connect the corresponding lamp test signal to this interface.
Caution: Using ELPZ the lamp test interface at the C_PUSHBT module must not be
connected.
EQIT
Acknowledge (additional)
Format BOOL
The acknowledgement of the drive fault is normally carried out together with the
acknowledgement of any alarm within the same AS (default setting). Interface EQIT is only
needed for individual acknowledgement (via push-button) or in case of group-wise
acknowledgement.
A signal change from "0" to "1" at EQIT acknowledges the drive fault (resetting flag EST).
In case of a conventional control desk, a push-button can be connected to EQIT (for individual
acknowledgement) or to the acknowledgement interface at block C_PUSHBT can be used (for
AS-wise acknowledgement).
Caution: Using EQIT for individual acknowledgement, the acknowledgement interface at the
C_PUSHBT must not be connected.
For group-wise acknowledgement connect the output ACK of the corresponding group to
interface EQIT of the drives. See Engineering Manual, chapter AS-Engineering.
EBFE
Command ON
Format BOOL
Interface to start the drive in automatic mode. With 1-signal the drive is started. The interface is
normally connected through the GBE signal of the associated group(s) or the WBE signal of the
associated route(s).
The drive is started either immediately or delayed according to the set start delay time (process
value STARTDEL).
Caution:
Interface EBFE 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 EBFE has signal zero when there is a fault.
EBFA
Command OFF
Format BOOL
Interface to switch off the drive in automatic mode. With 1-signal the drive is switched off. The
interface is normally connected through the negated GDE signal of the associated group(s) or
through the negated WDE signal of the associated route(s).
The drive is switched off either immediately or delayed according to the set stop delay time
(process value STOPDEL).
15
QSTP
Quick stop
Format BOOL
In some situations it may be necessary to stop the drives of a group instantaneously (without
stop delay). The connection of interface QSTP with 1-signal results in the immediate stopping of
the drive in automatic mode (interface EBFA may have a delaying effect).
The group module sets during quick stop the signal GQS. Interface QSTP of the drives must be
connected with this signal.
Typical application:
During ship loading, when a chamber of the ship is fully loaded, the ship moves slightly and
loading continues immediately. For this, one stops the group with this function immediately (no
stop delay), and restarts immediately and the already loaded belts continue to convey.
DSIG_BQ
Format BOOL
If driver blocks are used, the information "one ore more driver blocks have bad quality" can be
displayed in the drive faceplate and in the block icon of the drive.
In order to achieve this, the outputs QBAD of the driver blocks must be connected with an OR
function to Interface DSIG_BQ.
DSIG_SIM
Format BOOL
If driver blocks are used, the information "one or more driver blocks are switched to simulation"
can be displayed in the drive faceplate and in the block icon of the drive.
In order to achieve this, the outputs QSIM of the driver blocks must be connected with an OR
function to Interface DSIG_SIM.
Enable SIMOCODE
Format BOOL
For drives with SIMOCODE you have to enable this function with 1-signal at this parameter. In
the faceplate of the drive an additional button appears which allows opening the SIMOCODE
faceplate. In the TEXT1 Variable (preset with C_SIMOS) the respective Adapter Module can
be set per instance.
STAT_SC
Status SIMOCODE
Default: 16#00
Format BYTE
For drives with SIMOCODE you have to connect this parameter with out-parameter STAT_SC
of the Adapter block "C_SIMOS". Additional you have to enable this function with 1-signal at
parameter "REL_SC".
16
Format BOOL
A running drive will be stopped with 1-signal at this parameter. The drive becomes the status
faulty and the symbol turns to red color. The alarm message has to be generated by the
subcontrol block.
Format BOOL
With 1-signal at this parameter the motor faceplate shows a bar for the motor current (or power)
in percent. Look also to parameter "MV_PERC".
MV_PERC
Format POINTER
If a measure block for the motor current exists or a SIMOCODE is used, the percentage value of
the motor current (or power) can be displayed as bar in the faceplate of the motor. Therefore the
output MV_PERC of the C_MEASUR or the output I_PERC of C_SIMOS has to be connected
to this interface.
For the display of the percentage value in the drive faceplate, interface REL_MVC must be set.
Caution: 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.
17
PV
Format STRUCT
In order to display the process value in the drive faceplate, input PV must be connected with
output PV_Out of C_MEASUR (for one value) or with output Out_Val of C_ANA_SEL (for up to
16 values).
Structure variables:
PV.Value
Value
Default: 0.0
Signal status
Default: 16#FF
Format REAL
PV.ST
Format BYTE
PV_Stat
Format STRUCT
In order to transmit the status and the unit of the process value to the drive, the input PV_Stat
must be connected with output PV_Stat of C_MEASUR or with output Out_Stat of C_ANA_SEL
(for up to 16 values).
Structure variables:
PV_Stat.UNIT
Unit
Default: %
Status
Default: 16#00
Format STRING[8]
PV_Stat.STATUS
Format DWORD
18
Caution: Only the status and the unit of the selected measure are displayed in the drive
faceplate.
Enable setpoint
Format BOOL
With 1-Signal at input EN_SP the Setpoint input function is enabled. In the drive faceplate the
input field and the display of the actual Setpoint and the Process value is activated (visible).
The Setpoint can either be entered via Drive Faceplate ore as an external Setpoint. The
Setpoint is checked for Low limit SP_LLM and High limit SP_HLM. If the value exceeds the
limits it is aborted. There is no further evaluation in the drive block, the Setpoint is directly
written to the output SP_O.
SP_TR
Setpoint tracking
Format BOOL
1-Signal at input SP_TR enables the Setpoint tracking. The external Setpoint SP_EX is tracked
to the internal Setpoint SP_IN.
EN_SPEX
Format BOOL
With 1-Signal at the input EN_SPEX the drive block reads the Setpoint from Input SP_EX.
SP_IN
Setpoint from OS
Default: 0
Format REAL
Setpoint input from OS Standard Faceplate (must not be connected in the CFC).
The Unit is transmitted via Property "Unit" and the default setting is 'rpm'.
SP_EX
Setpoint extern
Format STRUCT
Setpoint input from another AS module (e. g. from a PID controller).
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
19
PV_IN
Format STRUCT
Input PV_IN has to be connected to the Process value. The value will be displayed in the
faceplate of the drive.
PV_IN.Value
Value
Default: 0.0
Format REAL
The Unit is transmitted via Property "Shortcut" and the default setting is 'rpm'.
PV_IN.ST
Signal status
Default: 16#FF
Format BYTE
UserFace
Select Faceplate
Format ANY
Input UserFace can be connected to any block with an OS Interface (Faceplate). If a block is
connected, an additional button "U" (User) appears in the faceplate of the drive block. With this
button the Faceplate of the connected block can be opened.
Example:
In order to show the related Signals for the drive, input UserFace can be connected to block
C_REL_MOD (for a list of up to 16 objects) or, if fewer signals are used, in can be directly
connected to a C_INTERL, C_INTER5 or Intlk02.
Test interface
Default: 0
Format INTEGER
The test interfaces are only used during module development and must not be changed!
MSG8_EVID
Message ID
Default: 16#00
Command word
Default: 16#00
Format DWORD
Interface to OS
COMMAND
Format WORD
Interface to OS
20
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.
Caution: 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.
21
GR_LINK1
Format STRUCT
The GR_LINK1 interface of the drive must be connected with the R_LINK interface of the route
or with the G_LINK interface of the group.
Structure variables:
GR_LINK1.Link
Link
Default: 0
Default: 16#00
Format INTEGER
GR_LINK1.Command
Format WORD
GR_LINK2
Format STRUCT
If the drive belongs to two different routes or groups, the GR_LINK2 interface must be
connected with the second route/group.
Structure variables:
GR_LINK2.Link
Link
Default: 0
Default: 16#00
Format INTEGER
GR_LINK2.Command
Format WORD
MUX_LINK
Link to C_MUX
Format STRUCT
If the drive belongs to more than two different routes or groups, the C_MUX module must be
series-connected. C_MUX has 5 inputs (GR_LINK1 to GR_LINK5) for connection with the
groups/routes and one output (MUX_OUT) for connection with the MUX_LINK interface of the
drive.
Caution:
If a C_MUX block is used, the programming order is very important. The C_MUX
must be called before the drive block!
The MUX_IN interface can under no circumstances be used for connection with a
group or route. It is used exclusively for connection with another MUX module.
Structure variables:
MUX_LINK.Point_GRL
Pointer
Default: 0
Default: 16#00
Format INTEGER
MUX_LINK.Command
Format WORD
22
Example of a circuit:
Route1
Group1
C_Group
MAIN_TASK
C_Route
1/5
G_LINK
Motor1
C_DRV_1D
MAIN_TASK
1/3
ST
R_LINK
ST
MAIN_TASK
1/2
ST
G_LINK
Route2
C_Route
MAIN_TASK
1/4
Group2
C_Group
R_LINK
MAIN_TASK
ST
ST
G_LINK
1/6
G_LINK
ST
ST
GR_LINK1
ST
GR_LINK2
ST
MUX_LINK
Group3
C_Group
MAIN_TASK
1/7
MUX1
C_MUX
G_LINK
ST
Group4
C_Group
MAIN_TASK
1/8
G_LINK
1/1
BO
EN
ST
MUX_IN
ST
GR_LINK1
ST
GR_LINK2
ST
GR_LINK3
ST
GR_LINK4
ST
GR_LINK5
ENO
BO
MUX_OUT
ST
Caution:
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, then the
associated routes and finally the associated groups.
Caution:
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.
ST
MAIN_TASK
23
MAINTASK
1/5
O_LINK
O_LINKQ
R01
C_ANNUNC
MAINTASK
1/2
O_LINK
NO_OF_I
FT1
R02
C_ANNUNC
FT2
MAINTASK
1/3
FT3
....
O_LINK
FT20
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 summarizing warning
indication of the group (or route).
The faults of all objects, linked to the drive are included 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.
O_LINKQ
Format STRUCT
Drive output O_LINKQ must be connected to interface O_LINK of all allocated annunciations
and measurements, while the drive itself is connected via GR_LINK to the group (or route).
Structure variables:
O_LINKQ.iDB
Format INTEGER
O_LINKQ.iDW
Format INTEGER
O_LINKQ.Command
Format BYTE
O_LINKQ.Status
Format BYTE
24
Caution:
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 and measurements.
G01
C_GROUP
MAINTASK
2/5
LRECV04
C_RECV_G
LINK
MAINTASK
2/4
NO_OF_FT
FT1
FT2
NO_OF_I
FT3
FT1
....
FT2
FT30
FT3
....
G_LINK
G_LINK
AS01
FT50
bertragung im z. B. 2 Sekundentakt
AS02
LSEND04
C_SEND_G
LINK
MAINTASK
1/5
R01
C_ANNUNC
MAINTASK
1/2
O_LINK
O_LINKQ
NO_OF_I
FT1
M01
C_DRV_1D
MAINTASK
1/3
O_LINK
O_LINKQ
FT2
FT3
....
FT50
M02
C_DAMPER
O_LINK
MAINTASK
1/4
O_LINKQ
Caution: It is not allowed to use the Object link and the Group/Route link at the same time:
If O_LINK is used, GR_LINK1 and GR_LINK2 or C_MUX must not be connected!
25
O_LINK
Format STRUCT
Input interface O_LINK of the drive must be connected to output O_LINKQ of the C_SEND_G
block.
Structure variables:
O_LINK.iDB
Default: 0
Default: 0
Default: 16#00
Default: 16#00
Format INTEGER
O_LINK.iDW
Format INTEGER
O_LINK.Command
Format BYTE
O_LINK.Status
Format BYTE
26
Caution:
Process values
The process values can be set during engineering and they can be changed online from the
OS. To permit the modification of the process values from the faceplates, they must not be
connected in the CFC.
FEEDBTIM
Feedback time
Default: 2
!
STARTDEL
The minimum feedback monitoring time is 2 seconds. For switching off, the
feedback monitoring time is always 2 seconds (adaptation not possible).
Start delay
Default: 0
STOPDEL
Stop delay
Default: 0
SPEEDTIM
Default: 0
HORN_TIM
In the default setting (SM_EVS_I = 0) the EVS signal becomes 1 only after this
time has elapsed. In this case this value must be made 0 when no speed monitor
is required. Otherwise there will be an unnecessary delay in the starting of the
subsequent drives.
With SM_EVS_I = 1 the EVS-Signal becomes 1 immediately with the speed
monitor signal.
Default: 10
27
TOL_SSM
Default: 50
Additional process parameters for the Setpoint function (e. g. for variable speed drives):
SP_HLM
Default: 0
Format REAL
The Setpoint values SP_IN and SP_EX are limited by SP_HLM and SP_LLM.
SP_HLM is the maximum value for Setpoint SP_IN and SP_EX
SP_LLM
Default: 0
Format REAL
The Setpoints valus SP_IN and SP_EX are limited by SP_HLM and SP_LLM.
SP_LLM is the minimum value for Setpoint SP_IN and SP_EX.
Maintenance Interval
Default: 16#00
Format DWORD
The Maintenance Interval relates, depending on the parameterization, to a fixed time value, to
the operating hours or to the number of starts. If the Maintenance Interval is exceeded the
output MAI_AL will be set.
MAI_REQL
Default: 16#00
Format DWORD
The Die Maintenance Request Limit can be used in order to indicate to the operator that the
Maintenance interval will be completed soon. If the Maintenance Request Limit is exceeded, the
output MAI_REQ will be set.
28
Input/Output interfaces
RES_RTOS
Default: 16#00
Run-time for OS
Default: 16#00
Default: 16#00
Default: 16#00
Format DWORD
Interface to OS
RT_OS
Format DWORD
Interface to OS
RT_H
Format DWORD
Interface to OS
CNT_OS
Format DWORD
Interface to OS
CNT_H
Default: 16#00
Default: 16#00
Format DWORD
Internal
MAI_CNT
Format DWORD
Interface to OS
CNT_TRIP
Default: 16#00
Default: 16#00
Maintenance Status
Default: 16#80022
Format DWORD
Interface to OS
FT_DUR
Format DWORD
Interface to OS
MAI_STA
Format DWORD
Interface to OS
MAI_X
Maintenance Spare
Default: 16#00
Format DWORD
Interface to OS
Copyright Siemens AG. All Rights Reserved.
N:\Cemat\DOKU\V80_SP1\English\Reference\Objekte\000_Normal\C_DRV_1D_009.doc
29
Output interfaces
EVS
Running signal
Format BOOL
A 1-signal means drive running in automatic mode or in single-start mode. It is mainly used for
the interlocking with other drives and as a feedback to the route or the group. This signal is not
generated in local mode!
RunSig
Running signal
Format STRUCT
For function description, see EVS. This interface can be connected to a structure input as e. g.
signal IntOper of the next drive.
Remark: For the feedback to the group or route you still have to use signal EVS because the
group/route interfaces have no structure format.
Structure variables:
RunSig.Value
Signal
Format BOOL
RunSig.ST
Signal status
Format BYTE
EST
Dynamic fault
Format BOOL
When a fault occurs in a running drive, during drive start up or during stand-by mode, the
dynamic fault bit is set. It remains set until the fault is acknowledged.
Caution:
SST
Fault
Format BOOL
A 1-signal means that at least one fault is present.
HORN
Start-up horn
Format BOOL
This signal is set during the starting of the drive in single-start mode for a given time period and
can be logically connected to trigger a start-up warning.
If L_STA_WA has 1-Signal the start-up warning is also given in local mode.
EVSP
Format BOOL
A 1-signal means drive has received a start command in automatic mode or in single start
mode (Command Memory is ON). The drive starts when the interface ESPO has 1-Signal.
The EVSP-signal can be used as feedback to the route or the group.
30
SIM_ON
Simulation ON
Format BOOL
In the Sequence Test mode SIM_ON has 1-Signal. If module drivers are used the output
SIM_ON of the motor can be connected to SIM_ON of the driver blocks in order to switch all
driver blocks to simulation mode.
Additional output for setpoint input function (e. g. for variable speed drives):
SP_O
Setpoint Output
Format STRUCT
In case of a variable speed drive (if EN_SP has 1-Signal) the Setpoint can be entered via drive
Faceplate of given via external Setpoint interface SP_EX. The Setpoint it then transferred to the
Output SP_O.
Output SP_O can be connected to driver block or to a SUBCONTORL (VSD) block.
Structure variables:
SP_O.Value
Value
Format REAL
The Unit is transmitted via Property "Unit" and the default setting is 'rpm'.
SP_O.ST
Signal status
Format BYTE
Maintenance Request
Format BOOL
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.
MAI_AL
Maintenance Alarm
Format BOOL
The Maintenance interval has been completed. This output can be connected to an
annunciation block in order to generate an alarm.
31
Format BYTE
Interface to OS
INTFC_OS
Format DWORD
Interface to OS
For more information see Variable details.
VISU_OS
Format BYTE
Interface to OS
For more information see Variable details.
STATUS
Format DWORD
Interface to OS
For more information see Variable details.
STATUS2
Format DWORD
Interface to OS
For more information see Variable details.
STATUS3
Format DWORD
Interface to OS
For more information see Variable details.
ALARM
for Test
Format WORD
For more information see Variable details.
32
CURR_OS
Format INTEGER
Interface to OS
If a measuring value is assigned to the motor the parameter CURR_OS contains the measuring
value in percentage. The text for the Faceplate description is defined in the object properties of
parameter CURR_OS under "Identifier". The default value is "I =".
As the measuring value must not necessarily 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.
DLY_CNT
Delay Counter
Format INTEGER
Interface to OS
33
Hardware outputs
EBE
Command ON
Format BOOL
The EBE signal is used to trigger the main contactor.
ELS
Running/fault lamp
Format BOOL
The ELS running/fault lamp signals the status of the drive and can be used for the connection of
an annunciation lamp (when no visualization system is present).
A continuous 1-signal indicates that the drive is running. Rapid flashing indicates a dynamic
fault (non-acknowledged) and slow flashing indicates a static fault (already acknowledged). A 0signal indicates that the drive has stopped.
34
Time characteristics
The module must be called before the associated route or group.
Any called C_MUX modules must run before this module.
Message characteristics
The module uses the ALARM_8 module to generate annunciations.
A plausibility and priority logic at the process level analyses all object faults
only one fault annunciation is issued for each fault
secondary annunciations are suppressed automatically
the fault source is recorded in detail and uniquely.
The current operational state of the plant objects is automatically taken into consideration during
the fault analysis, e.g. all fault annunciations are suppressed automatically for a stationary
group
no superfluous fault annunciations are created
the operator does not need to manually disable/suppress any annunciations.
Each fault annunciation is also classified.
This shows whether an electrical or a mechanical fault, a process fault or a shut-down with a
local safety switch applies.
An electrician does not always need to be called first
The production operator can give specific instructions.
35
Module States
Variable VISU_OS:
No.
Display Symbol
Text Presentation
off
White
Black, white
Blinking red
White, red
fault
Red
White, red
running
Green
Black, green
local mode
Yellow
Black, yellow
Blinking yellow
Black, yellow
single mode
Blue
Black, blue
Blinking blue
Black, blue
Commands
Refer to the Variable details for the assignment of the command word.
36
I/O-bar of C_DRV_1D
C_DRV_1D
Name
Description
Format
Default
Type
ERM
Attr.
HMI
Feedback ON
BOOL
ESB
Electrical availability
BOOL
EBM
Overload
BOOL
EVO
Local switch
BOOL
ESP
Local stop
BOOL
ESR
Local start
BOOL
EEVG
Start interlock
BOOL
IntStart
Start interlock
STRUCT
IntStart.Value
Signal
BOOL
IntStart.ST
Signal Status
BYTE
16#FF
EBVG
Operating interlock
BOOL
IntOper
Operating interlock
STRUCT
IntOper.Value
Signal
BOOL
IntOper.ST
Signal Status
BYTE
16#FF
ESVG
BOOL
IntProtG
STRUCT
IntProtG.Value
Signal
BOOL
IntProtG.ST
Signal Status
BYTE
16#FF
ESVA
Protection interlock
(only remote)
BOOL
IntProtA
Protection interlock
(only remote)
STRUCT
IntProtA.Value
Signal
BOOL
IntProtA.ST
Signal Status
BYTE
16#FF
ESPO
Sporadic on/off
BOOL
EDRW
BOOL
ELOC
BOOL
Permitted
Values
I
+
I
+
37
38
Name
Description
Format
Default
Type
EEIZ
Attr.
BOOL
ESTB
Stand-by mode
BOOL
ETFG
Inching release
BOOL
EMFR
Annunciation release
BOOL
EMZS
BOOL
GFSO
BOOL
ELPZ
BOOL
EQIT
Acknowledge (additional)
BOOL
EBFE
Command ON
BOOL
EBFA
Command OFF
BOOL
QSTP
Quick stop
BOOL
DSIG_BQ
BOOL
DSIG_SIM
BOOL
STA2_B10
BOOL
STA2_B11
BOOL
STA2_B12
BOOL
STA2_B13
BOOL
STA2_B14
BOOL
STA2_B15
BOOL
STA2_B16
BOOL
STA2_B17
BOOL
L_STA_WA
1 = startup-warning in local
mode
BOOL
REL_SSM
BOOL
SW_SPEED
BOOL
TOL_SSM
INT
50
SM_EVS_I
EVS=1 when
speed monitor 1-signal
BOOL
NSTP_L_A
BOOL
HMI
Permitted
Values
Description
LST_ACT
Format
Default
Type
Attr.
BOOL
REL_SC
Enable SIMOCODE
BOOL
STAT_SC
Status SIMOCODE
BYTE
16#00
SUBC_FT
BOOL
REL_MVC
BOOL
MV_PERC
POINTER
EN_SP
BOOL
EN_SPEX
BOOL
SP_TR
Setpoint tracking
BOOL
SP_IN
Setpoint from OS
REAL
0.0
SP_EX
External Setpoint
STRUCT
SP_EX.Value
Value
REAL
0.0
SP_EX.ST
Signal Status
BYTE
16#FF
SP_HLM
REAL
0.0
SP_LLM
REAL
0.0
PV_IN
PV_IN.Value
Value
REAL
0.0
PV_IN.ST
Signal Status
BYTE
16#FF
PV
PV.Value
Value
REAL
0.0
PV.ST
Signal Status
BYTE
16#FF
PV_Stat
STRUCT
PV_Stat.UNIT
Unit
STRING
[8]
DWORD
16#00
INT
DWORD
16#00
WORD
16#00
PV_Stat.STATU
Status
S
TEST_OSS
MSG8_EVID
Message ID
COMMAND
Command word
STRUCT
STRUCT
HMI
Permitted
Values
39
40
Name
Description
Format
Default
Type
FEEDBTIM
Attr.
HMI
Feedback time
INT
STARTDEL
Start delay
INT
STOPDEL
Stop delay
INT
SPEEDTIM
INT
HORN_TIM
INT
10
GR_LINK1
STRUCT
GR_LINK1.
Link
Link
GR_LINK1.
Command
GR_LINK2
GR_LINK2.
Link
Link
GR_LINK2.
Command
MUX_LINK
Link to C_MUX
MUX_LINK.
Point_GRL
Pointer
MUX_LINK.
Command
O_LINK
O_LINK.
iDB
INT
O_LINK
iDW
DW number NO_OF_FT in
master object
INT
O_LINK.
Command
BYTE
16#00
O_LINK.
Status
BYTE
16#00
UserFace
Select Faceplate
ANY
MAI_INT
Maintenance Interval
DWORD
16#00
MAI_REQL
DWORD
16#00
RES_RTOS
DWORD
16#00
IO
RT_OS
Runtime (s)
refreshed every minute
DWORD
16#00
IO
RT_H
Runtime (s)
refreshed every hour
DWORD
16#00
IO
CNT_OS
Counter contactor
DWORD
16#00
IO
Permitted
Values
INT
WORD
16#00
STRUCT
INT
WORD
16#00
STRUCT
INT
WORD
16#00
STRUCT
Name
Description
Format
Default
Type
Attr.
HMI
CNT_H
Counter contactor
refreshed every hour
DWORD
16#00
IO
MAI_CNT
Maintenance Actual
Counter in hours or starts
DWORD
16#00
IO
CNT_TRIP
Maintenance
Counter for Trips
DWORD
16#00
IO
FT_DUR
Maintenance
Fault time duration in sec
DWORD
16#00
IO
MAI_STA
Maintenance Status
DWORD
16#
0080022
IO
MAI_X
Maintenance Spare
DWORD
16#00
IO
RT_OS_O
Run-time for OS
refreshed every minute
DWORD
16#00
RT_H_O
Run-time for OS
refreshed every hour
DWORD
16#00
SP_O
Setpoint Output
STRUCT
SP_O.Value
Value
REAL
0.0
SP_O.ST
Signal Status
BYTE
16#80
SSM_CVOS
BYTE
16#00
INTFC_OS
DWORD
16#00
VISU_OS
BYTE
16#00
STATUS
Status word 1
DWORD
16#00
STATUS2
Status word 2
DWORD
16#00
STATUS3
Status word 3
Structure input available
DWORD
16#00
ALARM
WORD
16#00
CURR_OS
INT
EVS
Running signal
BOOL
RunSig
Running signal
STRUCT
RunSig.Value
Signal
BOOL
RunSig.ST
Signal status
BYTE
16#80
EST
Dynamic fault
(not acknowledged)
BOOL
SST
Fault
BOOL
HORN
Start-up horn
BOOL
Permitted
Values
41
42
Name
Description
Format
Default
Type
EVSP
BOOL
SIM_ON
BOOL
EBE
Contactor ON Command
BOOL
ELS
Lamp
BOOL
O_LINKQ
O_LINKQ.
iDB
INT
O_LINKQ
iDW
DW number NO_OF_FT in
master object
INT
O_LINKQ.
Command
BYTE
16#00
O_LINKQ.
Status
BYTE
16#00
MAI_REQ
Maintenance Request
BOOL
MAI_AL
Maintenance Alarm
BOOL
DLY_CNT
Delay Counter
INT
STRUCT
Attr.
HMI
Permitted
Values
OS-Variable table
C_DRV_1D
PLC Data
OS Data Type
Type
OS Variable
Description
IntStart#Value
Signal
BOOL
Binary variable
IntOper#Value
Signal
BOOL
Binary variable
IntProtG#Value
Signal
BOOL
Binary variable
IntProtA#Value
Signal
BOOL
Binary variable
TOL_SSM
REL_SC
Enable SIMOCODE
BOOL
Binary variable
SP_IN
Setpoint from OS
REAL
SP_EX#Value
Value
REAL
SP_HLM
REAL
SP_LLM
REAL
PV_IN#Value
Value
REAL
PV#Value
Value
REAL
PV_Stat#UNIT
Unit
PV_Stat#STATUS Status
INT
STRING
[8]
DWORD
COMMAND
Command word
WORD
FEEDBTIM
Feedback time
INT
STARTDEL
Start delay
INT
STOPDEL
Stop delay
INT
SPEEDTIM
INT
HORN_TIM
INT
MAI_INT
Maintenance Interval
DWORD
MAI_REQL
DWORD
RES_RTOS
DWORD
RT_OS
Runtime (s)
refreshed every minute
DWORD
RT_H
Runtime (s)
refreshed every hour
DWORD
43
44
OS Variable
Description
PLC Data
OS Data Type
Type
CNT_OS
Counter contactor
DWORD
MAI_CNT
DWORD
CNT_TRIP
Maintenance
Counter for Trips
DWORD
FT_DUR
Maintenance
Fault time duration in sec
DWORD
MAI_STA
Maintenance Status
DWORD
MAI_X
Maintenance Spare
DWORD
SP_O.#Value
Value
REAL
SSM_CVOS
BYTE
INTFC_OS
DWORD
VISU_OS
BYTE
STATUS
Status word 1
DWORD
STATUS2
Status word 2
DWORD
STATUS3
Status word 3
Structure input available
DWORD
CURR_OS
INT
RunSig#Value
Signal
BOOL
Binary variable
RunSig#ST
Signal status
BYTE
DLY_CNT
Delay counter
INT
Variable details
Internal structure of the Commands, Alarms, Visualization status and Interface word:
Parameter
Function
OSAddr.
COMMAND
Designation German
Designation English
Msg
Class
Kommandowort
Commandword
COM_B20
OFF
AUS
OFF
COM_B21
ON
EIN
ON
COM_B22
R_RTOS
Laufzeit lschen
Op. Inp.
Op. Inp.
Op. Inp.
Op. Inp.
Einzel quittieren
Single acknowledge
COM_B23
COM_B24
3
BDW_on/off
COM_B25
COM_B26
COM_B27
COM_B10
COM_B11
Fault
Class
8
SACK
COM_B12
10
COM_B13
11
COM_B14
12
COM_B15
13
COM_B16
14
COM_B17
15
ALARM
Alarm
Alarm
SIG1
Schtz
Feedback
ALA_ESB
SIG2
El. Schaltbereit
Available
AL_H
ALA_EVO
SIG3
Vorort
Local
AL_H
ALA_EBM
SIG4
Bimetall
Overload
AL_H
ALA_ESD
SIG5
Drehwchter
Speed monitor
AL_H
ALA_LST
SIG6
Vorort Stop
Local stop
AL_H
ALA_SUB
SIG7
Subc. Sammelstrung
AL_H
ALA_REP
SIG8
Noch gestrt
Still faulty
AL_H
VISU_OS
dezimal
schw, wei
Steht
off
Wei ,rot
Wei ,rot
Strung quittiert
Fault acknowledged
schw, grn
Luft
running
schw, gelb
Vorortbetrieb steht
local mode
schw, gelb
Luft in Vorortbetrieb
schw, trkis
Einzelbetrieb steht
single mode
schw, trkis
Luft in Einzelbetrieb
ALA_ESS
hex
AL_H
45
Parameter
Function
INTFC_OS
Designation German
Designation English
Nahtstellenwort
Interface word
OS_IF_B40
EEVG
Einschaltverriegelung
Start interlock
OS_IF_B41
EBVG
Betriebsverriegelung
OS_IF_B42
ESVG
Schutzverriegelung
OS_IF_B43
ESVA
OS_IF_B44
ESPO
Schutzverriegelung
(nur Automatik und Einzel)
Sporadisch Ein/Aus
Operating interlock
Protection interlock (always
active)
Protection interlock (only
automatic and single)
Sporadic ON/OFF
OS_IF_B45
EDRW
Drehwchter
Speed monitor
OS_IF_B46
OS_IF_B47
OS_IF_B30
ELOC
Vorortbetrieb Freigabe
OS_IF_B31
EEIZ
Einzelbetrieb Freigabe
OS_IF_B32
ESTB
10
Betriebsart Stand-by
Stand-by mode
OS_IF_B33
ETFG
11
Tipp-Freigabe
Inching release
OS_IF_B34
12
OS_IF_B35
13
OS_IF_B36
REL_SSM
14
OS_IF_B37
REL_EVS_I
15
OS_IF_B20
GFSO
16
OS_IF_B21
EMFR
17
Meldefreigabe
Annunciation release
OS_IF_B22
EMZS
18
OS_IF_B23
19
OS_IF_B24
20
OS_IF_B25
21
OS_IF_B26
22
OS_IF_B27
ELPZ
23
OS_IF_B10
EQIT
24
Quittieren (Zusatz)
Acknowledge (additional)
OS_IF_B11
26
OS_IF_B13
EBFE
27
Befehl Ein
Command ON
OS_IF_B14
EBFA
28
Befehl Aus
Command OFF
Schnellstopp
Quick stop
OS_IF_B15
OS_IF_B17
46
Fault
Class
25
OS_IF_B12
OS_IF_B16
Msg
Class
29
QSTP
30
31
Parameter
Function
OSAddr.
STATUS
Designation German
Designation English
Status
Status
Betriebsart Vorort
Local mode
Freigabe Einzelbetrieb
Brcke Drehwchter
SSM
Softwaredrehwchter
STA_B44
HORN
Anfahrwarnung
Start up warning
STA_B45
EST
STA_B46
ERM
Rckmeldung EIN
Feedback ON
STA_B47
SC_FT
Strung SIMOCODE
STA_B30
ESS
STA_B31
ESB
STA_B32
EVO
10
Strung Schtz
Strung elektrische
Schaltbereitschaft
Strung Vorort
Contactor fault
Electrical availability
fault
Local switch fault
STA_B33
EBM
11
Strung Bimetall
Overload fault
STA_B34
ESD
12
Strung Drehwchter
STA_B35
ESV
13
Strung Schutzverriegelung
STA_B36
LST
14
Sequence test/Simulation
STA_B40
LOCAL
STA_B41
EIZ
STA_B42
BDW
STA_B43
STA_B37
Fault
Class
15
STA_B20
SIM_ON
16
Sequenz Test/Simulation
STA_B21
SST
17
Sammelstrung
general fault
STA_B22
BQU
18
Signal Strung
STA_B23
EVS
19
Laufsignal
Running Signal
STA_B24
EVS_SP
20
Laufsignal sporadisch
STA_B25
EKS
21
Kommando Speicher
Command memory
STA_B26
ON_DLY
22
Einschaltverzgerung
ON delay
STA_B27
OFF_DLY
23
Ausschaltverzgerung
OFF delay
STA_B10
MOV_T
24
Rckmeldeberwachung luft
STA_B11
SUW_T
25
Hupzeit luft
STA_B12
EN_SP
26
Freigabe Sollwerteingabe
STA_B13
EN_SPEX
27
STA_B14
SP_TR
28
Sammelfehler Subcontrol
STA_B15
29
STA_B16
STA_B17
Msg
Class
30
SUBC_FT
31
47
Parameter
Function
STATUS2
Designation German
Designation English
Status
Status
STA2_B40
ERM
Rckmeldung EIN
Feedback ON
STA2_B41
ESB
Schaltbereitschaft
El. Availability
STA2_B42
EBM
Bimetall
Overload
STA2_B43
EVO
Vorortschalter
Local Switch
STA2_B44
ESP
Vorort Stop
Local Stop
STA2_B45
ESR
Vorort Start
Local Start
STA2_B46
EBE
Befehl Ein
Command ON / OFF
STA2_B47
STA2_B30
STA2_B31
STA2_B32
10
STA2_B33
11
STA2_B34
12
STA2_B35
13
STA2_B36
14
STA2_B37
15
STA2_B20
REL_SC
16
Freigabe SIMOCODE
Enable SIMOCODE
STA2_B21
WA_SC
17
Warnung SIMOCODE
STA2_B22
REL_MVC
18
STA2_B23
LST_ACT
19
STA2_B24
20
STA2_B25
21
STA2_B26
L_STA_WA
STA2_B27
22
Fault
Class
23
STA2_B10
STA2_B10
24
Reserve fr Anwender
STA2_B11
STA2_B11
25
Reserve fr Anwender
STA2_B12
STA2_B12
26
Reserve fr Anwender
STA2_B13
STA2_B13
27
Reserve fr Anwender
STA2_B14
STA2_B14
28
Reserve fr Anwender
STA2_B15
STA2_B15
29
Reserve fr Anwender
STA2_B16
STA2_B16
30
Reserve fr Anwender
STA2_B17
STA2_B17
31
Reserve fr Anwender
48
Msg
Class
Parameter
Function
OSAddr.
STATUS3
Designation German
Designation English
Status
Status
STA3_B40
IntStart angeschlossen
IntStart connected
STA3_B41
IntOper angeschlossen
IntOper connected
STA3_B42
IntProtG angeschlossen
IntProtG connected
STA3_B43
IntProtA angeschlossen
IntProtA connected
STA3_B44
SP_EX angeschlossen
SP_EX connected
STA3_B45
5
6
PV_IN angeschossen
GR_LINK1 angeschlossen
PV_IN connected
GR_LINK1 connected
Analogwert angeschlossen
Objekt markieren
(Gruppenkommando)
STA3_B46
LINK
STA3_B47
STA3_B30
MARK
STA3_B31
STA3_B32
10
STA3_B33
11
STA3_B34
12
STA3_B35
13
STA3_B36
14
STA3_B37
15
STA3_B20
16
STA3_B21
17
STA3_B22
18
STA3_B23
19
STA3_B24
20
STA3_B25
21
STA3_B26
22
STA3_B27
23
STA3_B10
24
STA3_B11
25
STA3_B12
26
STA3_B13
27
STA3_B14
28
STA3_B15
29
STA3_B16
30
STA3_B17
31
Msg
Class
Fault
Class
49
Parameter
Function
MAI_STA
Designation German
Designation English
Maintenance Status
Maintenance Status
Maintenance Intervall:fest
Maintenance Intervall:
Betriebsstunden
Maintenance Intervall: Starts
16
Bedienanforderng
Operation Request
17
Bedienung
Operation In Progress
MAI_STA_B22
18
MAI_STA_B23
19
Bedineung ausgefhrt
Bedienung Temp
(keine Bedienaktion)
Operation Completed
Opartation Temp
(No Operator Action)
MAI_STA_B24
20
MAI_STA_B25
21
MAI_STA_B26
22
MAI_STA_B27
23
MAI_STA_B40
MAI_STA_B41
MAI_STA_B42
MAI_STA_B43
MAI_STA_B44
MAI_STA_B45
MAI_STA_B46
MAI_STA_B47
MAI_STA_B30
MAI_STA_B31
MAI_STA_B32
10
MAI_STA_B33
11
MAI_STA_B34
12
MAI_STA_B35
13
MAI_STA_B36
14
MAI_STA_B37
15
MAI_STA_B20
MAI_STA_B21
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
50
Msg
Class
Fault
Class