LAlarmHdl SIMATIC V1 1 en 02 2022

Alarm Handling for
SINAMICS drives in
S7-1500
Siemens
LAlarmHdl for SIMATIC Industry
Online
https://support.industry.siemens.com/cs/ww/en/view/109761931 Support
Legal information
Legal information
Use of application examples
Application examples illustrate the solution of automation tasks through an interaction of several
components in the form of text, graphics and/or software modules. The application examples are
a free service by Siemens AG and/or a subsidiary of Siemens AG (“Siemens”). They are non-
binding and make no claim to completeness or functionality regarding configuration and
equipment. The application examples merely offer help with typical tasks; they do not constitute
customer-specific solutions. You yourself are responsible for the proper and safe operation of the
products in accordance with applicable regulations and must also check the function of the
respective application example and customize it for your system.
Siemens grants you the non-exclusive, non-sublicensable and non-transferable right to have the
application examples used by technically trained personnel. Any change to the application
examples is your responsibility. Sharing the application examples with third parties or copying the
application examples or excerpts thereof is permitted only in combination with your own products.
The application examples are not required to undergo the customary tests and quality inspections
of a chargeable product; they may have functional and performance defects as well as errors. It is
your responsibility to use them in such a manner that any malfunctions that may occur do not
result in property damage or injury to persons.
Disclaimer of liability
Siemens shall not assume any liability, for any legal reason whatsoever, including, without
limitation, liability for the usability, availability, completeness and freedom from defects of the
application examples as well as for related information, configuration and performance data and
any damage caused thereby. This shall not apply in cases of mandatory liability, for example
under the German Product Liability Act, or in cases of intent, gross negligence, or culpable loss of
life, bodily injury or damage to health, non-compliance with a guarantee, fraudulent
non-disclosure of a defect, or culpable breach of material contractual obligations. Claims for
damages arising from a breach of material contractual obligations shall however be limited to the
© Siemens AG 2022 All rights reserved
foreseeable damage typical of the type of agreement, unless liability arises from intent or gross
negligence or is based on loss of life, bodily injury or damage to health. The foregoing provisions
do not imply any change in the burden of proof to your detriment. You shall indemnify Siemens
against existing or future claims of third parties in this connection except where Siemens is
mandatorily liable.
By using the application examples you acknowledge that Siemens cannot be held liable for any
damage beyond the liability provisions described.
Other information
Siemens reserves the right to make changes to the application examples at any time without
notice. In case of discrepancies between the suggestions in the application examples and other
Siemens publications such as catalogs, the content of the other documentation shall have
precedence.
The Siemens terms of use (https://support.industry.siemens.com) shall also apply.
Security information
Siemens provides products and solutions with industrial security functions that support the secure
operation of plants, systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is necessary
to implement – and continuously maintain – a holistic, state-of-the-art industrial security concept.
Siemens’ products and solutions constitute one element of such a concept.
Customers are responsible for preventing unauthorized access to their plants, systems, machines
and networks. Such systems, machines and components should only be connected to an
enterprise network or the internet if and to the extent such a connection is necessary and only
when appropriate security measures (e.g. firewalls and/or network segmentation) are in place.
For additional information on industrial security measures that may be implemented, please visit
https://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more secure.
Siemens strongly recommends that product updates are applied as soon as they are available
and that the latest product versions are used. Use of product versions that are no longer
supported, and failure to apply the latest updates may increase customer’s exposure to cyber
threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed
at: http://www.siemens.com/industrialsecurity.
LAlarmHdl for SIMATIC

Entry-ID: 109761931, V1.1, 02/2022 2
Table of contents
Table of contents
Legal information ..................................................................................................... 2
1 Introduction .................................................................................................... 4
1.1 Overview ........................................................................................... 4
1.2 Mode of operation.............................................................................. 6
1.3 Components used ............................................................................. 7
2 Engineering .................................................................................................... 8
2.1 Description of interface ...................................................................... 8
2.1.1 LAlarmHdl_DriveAlarmsIOSystem (FB 31900) ................................... 9
2.1.2 LAlarmHdl_AddSINADriveAlarms (FB 31901) .................................. 12
2.1.3 PLC data types ................................................................................ 15
2.1.4 PLC tags ......................................................................................... 17
2.2 Project integration............................................................................ 18
2.2.1 Set up project languages ................................................................. 18
2.2.2 Device configuration of the PLC ....................................................... 19
2.2.3 Device configuration of the SINAMICS drive systems....................... 20
2.2.4 Integrating the alarm classes and text lists for alarm view into
STEP 7............................................................................................ 21
2.2.5 Integrating the library blocks into STEP 7......................................... 22
2.2.6 Engineering of the fully autonomous alarm handling solution............ 23
2.2.7 Engineering of the modular alarm handling approach ....................... 25
2.2.8 WinCC “Alarm view” settings ........................................................... 29
2.2.9 Cycle time reduction and data storage adaption in fully

autonomous solution........................................................................ 30
2.3 Operation ........................................................................................ 31
2.3.1 Operation of the fully autonomous solution....................................... 31
2.3.2 Operation of the modular approach .................................................. 31
2.3.3 Operation of the WinCC Comfort Panel............................................ 33
2.3.4 Operation of the SIMATIC S7-1500 Webserver ................................ 33
2.4 Error handling .................................................................................. 34
2.4.1 Error handling of fully autonomous solution ...................................... 34
2.4.2 Error handling of modular approach ................................................. 35
2.5 Time synchronization of SINAMICS drive systems ........................... 36
3 Appendix....................................................................................................... 37
3.1 Service and support ......................................................................... 37
3.2 Application support .......................................................................... 38
3.3 Links and literature .......................................................................... 38
3.4 Change documentation .................................................................... 38

Entry-ID: 109761931, V1.1, 02/2022 3
1 Introduction
1 Introduction
1.1 Overview
The purpose of the LAlarmHdl library is to collect all messages from SINAMICS
drives. These messages can be displayed at Siemens HMIs via the standard
control “Alarm View”, the web server of the PLC as well as the TIA Portal
Engineering in the diagnostics alarm display. The messages are removed when the
problem in the drive is resolved.
In contrast to the system diagnostics, where only one error out of the 19
PROFIdrive error classes is sent, Alarm Handling integrates the detailed
SINAMICS message text.
The library contains two different software automation levels that meet the
requirements of the software structure:
- A fully autonomous solution that scans the configured IO system for SINAMICS
drives and adds automatically messages from the found drive objects to the
alarm display of the PLC. This is preferred for central alarm handling. This
should be selected if many drive objects are included in the project. This
functionality is provided by using the function block (FB)
LAlarmHdl_DriveAlarmsIOSystem.
Note: the functionality is not available for the PROFIdrive Integrated IO system
of the SIMATIC Drive Controller.
- A modular and efficient approach where a programmer can add the messages
of a single SINAMICS drive object to the alarm display of the PLC. This should
be chosen when only a few drives are present in the project. This functionality
is provided by the function block (FB) LAlarmHdl_AddSINADriveAlarms.

Entry-ID: 109761931, V1.1, 02/2022 4
1 Introduction
Table 1-1: Comparison about approaches and blocks

LAlarmHdl_DriveAlarmsIOSystem LAlarmHdl_AddSINADriveAlarms
User Fully autonomous approach without Modular approach with more
interaction many interactions from the user. interaction with the user (e.g. error
handling).
Call of An instance is needed to handle a An instance is needed for every drive
application complete IO system with all drive object. This allows to select the
objects. Centrally called once for an polled drives and message types.
IO system in the PLC.
Multi drive All drive objects of a multi drive Every drive object can be polled but
systems system (e.g. SINAMICS S120) are needs an own instance.
polled.
Polling of Different messages are polled Polling of messages can be done
messages according to demand (e.g. fault cyclically, or user must detect if an
occurred) automatically. error occurred.
Other IO All errors of other IO devices like No integration of devices apart from
devices ET 200SP, drives, etc. are stored in SINAMICS drives are possible.
the IOSystemData DB. Messages
are only send for SINAMICS
devices
Required A lot of data work-memory is Only as much data work-memory as
data work- needed for keeping data of all drive necessary for polled drive objects is
memory objects in an IO system. necessary.
Required PLC calculation performance in Only PLC calculation performance is
PLC background is needed to scan the needed to communicate to drives

calculation IO system for faults or alarms user sets the according inputs to poll
performance occurred in drive objects. the drive.
Additionally, PLC calculation
performance is needed to
communicate to drives after a
problem occurred.
Message Messages reported to the alarm Messages reported to the alarm view
reporting view system of the PLC. Messages system of the PLC. Messages can be
can be viewed in STEP 7 viewed in STEP 7 Professional Alarm
Professional Alarm View, PLC View, PLC Webserver, WinCC
Webserver, WinCC Comfort and RT Comfort and RT Panels.
Panels.

Entry-ID: 109761931, V1.1, 02/2022 5
1 Introduction
1.2 Mode of operation

Figure 1-1: Read out of drive messages and message generation
Panels
S7-1500 SIMATIC
Webserver
Scan of IO system
Collect messages
TIA Portal
Definition of
messages in
text list
LAlarmHdl_DriveAlarmsIOSystem is the FB for an autonomous application that

scans an IO system for connected SINAMICS drives and afterwards watches the
drives for appearing alarms or faults. If an alarm or fault is detected the FB
LAlarmHdl_AddSINADriveAlarms block is used to report the message to the
system diagnostics.
LAlarmHdl_AddSINADriveAlarms is the FB that collects messages of a SINAMICS

drive via acyclic data exchange and sends a program alarm with the text of the
SINAMICS message. This FB needs a signal from the user for reading the different
alarm types.
After the message is reported via a program alarm, the messages can be seen via
system mechanism “alarm view” in the panel, the SIMATIC webserver and the
TIA Portal Engineering.
The messages generated in the controller contain the following information:

• Message type (Alarm, Fault, Safety Message)
• Name of the drive object
• Message code and additional information (value)
• Message description
• Timestamp for message arrived of the drive object.
NOTE A cyclic time synchronization between the drive systems and the PLC is required
for this application.

Entry-ID: 109761931, V1.1, 02/2022 6
1 Introduction
After solving the problem in the SINAMICS (e.g. by resetting the technology object)
the message is automatically deleted from the alarm view.
1.3 Components used

This application example has been created with the following hardware and
software components:
Table 1-2
Component Number Article number Note
CPU 1513-1 PN 1. 6ES7 513-1AL02-0AB0 Or other S7-1500
CPU with FW V2.5
SINAMICS S210 2. 6SL3 210-5HB10-1UF0 Or any other
SINAMICS drive
STEP 7 Professional V15 3. 6ES7822-1..05-.. Or newer version
This application example consists of the following components:

Table 1-3
Component File name Note
LAlarmHdl library LAlarmHdl_V1_1_x.zip

LAlarmHdl example LAlarmHdl_Example_Autonomous_V1_1_x.zip
with drives detection
at IO system
LAlarmHdl example LAlarmHdl_Example_Modular_V1_1_x.zip
with FB instance per
drive object
LAlarmHdl manual LAlarmHdl_SIMATIC_V1_1_en.pdf

Entry-ID: 109761931, V1.1, 02/2022 7
2 Engineering
2 Engineering
2.1 Description of interface
The function blocks are implemented in Structured Control Language (SCL). They
are programmed for use in a cyclic task.
Additional required library:

Note
LAcycCom for acyclic data exchange:
https://support.industry.siemens.com/cs/ww/en/view/109479553
List of blocks
The following table lists all blocks of the LAlarmHdl library.
Table 2-1 List of blocks

Block Symbol Classification
FB 31900 LAlarmHdl_DriveAlarmsIOSystem In-house development
FB 31901 LAlarmHdl_AddSINADriveAlarms In-house development

DB 31900 LAlarmHdl_IOSystemData In-house development
Size of the individual block

Table 2-2 Size of the blocks1
Block Symbol Size in Size in Size in
code data work- load
work- memory memory
memory [Kbytes] [Kbytes]
[Kbytes]
FB 31900 LAlarmHdl_DriveAlarmsIOSystem 9 145
2
FB 31901 LAlarmHdl_AddSINADriveAlarms 5 92
DB 31900 LAlarmHdl_IOSystemData 63 65
Table 2-3 Size of block instances

Symbol Size in data Size in load Size in retain
work-memory memory memory
[Kbytes] [Kbytes] [Kbytes]
InstLAlarmHdl_DriveAlarmsIOSystem 348 366 6

InstLAlarmHdl_AddSINADriveAlarms 22 10 0.2
1
Instance data blocks (prefix InstLAlarmHdl_) are not delivered with the library. They will be
generated automatically with the call of a function block.
2
Additional memory for internally called LAcycCom FBs required.

Entry-ID: 109761931, V1.1, 02/2022 8
2 Engineering
2.1.1 LAlarmHdl_DriveAlarmsIOSystem (FB 31900)
Figure 2-1: Block diagram of FB LAlarmHdl_DriveAlarmsIOSystem
LAlarmHdl_DriveAlarmsIOSystem
HW_IOSYSTEM ioSystemHwId error Bool
status Word
diagnostics LAlarmHdl_typeDiagnostics
ioSystemData
LAlarmHdl_typeIOSystem LAlarmHdl_typeIOSystem
requestBuffer
LAcycCom_typeRequestBuffer LAcycCom_typeRequestBuffer
Principle of operation
The FB LAlarmHdl_DriveAlarmsIOSystem is a fully autonomous solution for alarm
and message handling for all SINAMICS drives in a PROFINET or PROFIBUS IO
system. All devices / slaves that are configured in the hardware configuration are
detected and stored in the ioSystemData data structure. Afterwards it is determined
if a module is a SINAMICS drive or another IO module.
All SINAMICS drives of an IO system are monitored for faults, alarms and safety
messages automatically. If a SINAMICS drive reports a problem the according
message is polled and added to the alarm view.
The messages can be seen in TIA Portal engineering in the diagnostics alarm view
section, in the SIMATIC webserver and in all SIMATIC Comfort panels in the alarm
view control.
NOTICE The PROFIdrive standard alarms must be activated in all drives in the
hardware configuration. Otherwise messages cannot be read.
For more information see chapter 2.2.3
NOTE By using this solution, the FB LAlarmHdl_AddSINADriveAlarms is not allowed to

be used additionally for polling drive alarms from a single drive object.
NOTE If Safety Integrated Extended/Advanced Functions in SINAMICS S120 are used,

set the Control Unit parameter p3117 = 1 to save both the Basic Functions
messages and the Extended/Advanced Functions messages in the standard
fault buffer. This optimizes the code and communication performance of this
solution because the separate safety message buffer does not need to be read.

Entry-ID: 109761931, V1.1, 02/2022 9
2 Engineering
Input parameters
Table 2-4: LAlarmHdl_DriveAlarmsIOSystem input parameters
Name Data type Comment
ioSystemHwId HW_IOSYSTEM This ID is representing the IO System (PN
or DP), find the ID in the system constants
(default value: 0)
Output parameters
Table 2-5: LAlarmHdl_DriveAlarmsIOSystem output parameters
error Bool Rising edge informs that an error occurred
during the execution of the FB
(default value: FALSE)
status Word 16#0000 - 16#7FFF: Status of the FB,
16#8000 - 16#FFFF: Error identification
(default value: 16#7000,
STATUS_NO_CALL)
diagnostics LAlarmHdl_typeDiagnostics Diagnostics information of FB
InOut parameters
Table 2-6: LAlarmHdl_DriveAlarmsIOSystem inOut parameters
ioSystemData LAlarmHdl_typeIOSystem IO-System diagnostics data
requestBuffer LAcycCom_typeRequestBuffer Connection to the request buffer of the
LAcycCom resource manager. All
LAcycCom blocks have to use the same
request buffer

Entry-ID: 109761931, V1.1, 02/2022 10
2 Engineering
Status and error displays

Table 2-7 LAlarmHdl_DriveAlarmsIOSystem status displays
Status Meaning Comment
16#7000 STATUS_NO_CALL No call of FB
16#7001 STATUS_FIRST_CALL First call after enabling
16#7002 STATUS_SUBSEQUENT_CALL Subsequent call of FB
16#7200 WARN_ADD_SINA_DRIVE_AL Error at subfunction LAlarmHdl_AddSINADriveAlarms
ARMS (see: diagnostics.subfunctionStatus)
16#8401 ERR_MAX_DEVICES_PER_IO There are more modules configured than defined with
SYSTEM the user constant:
LALARMHDL_MAX_DEVICES_PER_IO_SYSTEM
16#8402 ERR_NO_OF_DOS_PER_IO_S There are more DOs configured than defined with the
YSTEM user constant:
LALARMHDL_DOS_PER_IO_SYSTEM_UPPER_LIM
16#8403 ERR_NO_OF_DOS_PER_DEVI There are more DOs configured in a drive system than
CE defined with the user constant:
LALARMHDL_MAX_DOS_PER_DEVICE
16#8600 ERR_GET_DEVICE_STATES Error at system function DeviceStates
(see: diagnostics.subfunctionStatus)
16#8601 ERR_GET_NAME Error at system function Get_Name
NOTE More information about the error handling can be found in chapter 2.4.

Entry-ID: 109761931, V1.1, 02/2022 11
2 Engineering
2.1.2 LAlarmHdl_AddSINADriveAlarms (FB 31901)
Figure 2-2: Block diagram of FB LAlarmHdl_AddSINADriveAlarms
LAlarmHdl_AddSINADriveAlarms
Bool enable valid Bool

resetAlarm
Bool busy Bool
View
Bool readAlarms error Bool
Bool readFaults status Word

read
Bool alarmActive Bool
SIMessages
HW_IO hardwareId faultActive Bool
SIMessage
Int driveObjectId Bool
Active
WString[LALARMHDL_ driveObject resetAlarm
Bool
MAX_NAME_LEN] Name ViewActive
update
Time diagnostics LAcycCom_typeDriveDiagnostics
Interval
requestBuffer
LAcycCom_typeRequestBuffer LAcycCom_typeRequestBuffer
Principle of operation
The FB LAlarmHdl_AddSINADriveAlarms reads active messages from a

SINAMICS drive object. A SINAMICS drive object can be a control unit, a drive, an
external encoder, etc.
The messages can be seen in TIA Portal engineering in the diagnostics alarm view
section, in the SIMATIC webserver and in all SIEMENS panels in the alarm view
control.
NOTE If Safety Integrated Extended/Advanced Functions in SINAMICS S120 are used,

set the Control Unit parameter p3117 = 1 to save both the Basic Functions
messages and the Extended/Advanced Functions messages in the standard
fault buffer. This optimizes the code and communication performance of this
solution, because the separate safety message buffer does not need to be read
(set input readSIMessages := FALSE).
Input parameters
Table 2-8: LAlarmHdl_AddSINADriveAlarms input parameters
enable Bool TRUE: Enable functionality of FB
resetAlarmView Bool Rising edge: Delete messages in
alarm view
readAlarms Bool TRUE: Enable cyclic reading of
alarms

Entry-ID: 109761931, V1.1, 02/2022 12
2 Engineering

readFaults Bool TRUE: Enable cyclic reading of
faults
readSIMessages Bool TRUE: Enable cyclic reading of SI
Messages
hardwareId HW_IO Hardware identifier of the hardware
module
(default value: 0)
driveObjectId Int Optional: Identification number of the
drive object (value <0: driveObjectId
is not used, i.e. the corresponding
drive object is only addressed via the
hardwareId)
(default value: -1)
driveObjectName WString[LALARMHDL_MAX_NAME_LEN] User-defined name for the drive
object, which is displayed in the
corresponding message texts
(default value:
WSTRING#’SINAMICS_DO’)
updateInterval Time Update interval for cyclic reading
(default value: T#1s)
Output parameters
Table 2-9: LAlarmHdl_AddSINADriveAlarms output parameters
valid Bool TRUE: Valid set of output values
available at the FB
busy Bool TRUE: FB is not finished, and new
output values can be expected
error Bool TRUE: An error occurred during the
execution of the FB
status Word 16#0000 - 16#7FFF: Status of the
FB, 16#8000 - 16#FFFF: Error
identification
(default value: 16#7000,
STATUS_NO_CALL)
alarmActive Bool TRUE: An alarm is active
faultActive Bool TRUE: A fault is active
SIMessageActive Bool TRUE: A safety message is active
resetAlarmViewAc Bool TRUE: Reset of alarm view is active
tive (default value: FALSE)
diagnostics LAcycCom_typeDriveDiagnostics Diagnostics information of FB

Entry-ID: 109761931, V1.1, 02/2022 13
2 Engineering
InOut parameters
Table 2-10: LAlarmHdl_AddSINADriveAlarms inOut parameters
requestBuffer LAcycCom_typeRequestBuffer Connection to the request buffer of
the resource manager. All
LAcycCom blocks have to use the
same request buffer
Status and error displays

Table 2-11 LAlarmHdl_AddSINADriveAlarm status displays
Status Meaning Comment
16#7000 STATUS_NO_CALL No call of FB
16#7001 STATUS_FIRST_CALL First call after enabling
16#7002 STATUS_SUBSEQUENT_CALL Subsequent call of FB
16#8600 ERR_UNDEFINED_STATE Error due to an undefined state in state machine
16#8601 ERR_READ_DRIVE_MESSAGES Error while using
LAcycCom_ReadDriveMessagesDateTime block
16#8602 ERR_TRIGGERED_ALARMS_PE Too many alarms triggered in a cycle per DO;
R_CYCLE decrease constant
NO_OF_TRIGGERED_ALARMS_PER_CYCLE
NOTE More information about the error handling can be found in chapter 2.4.

Entry-ID: 109761931, V1.1, 02/2022 14
2 Engineering
2.1.3 PLC data types
LAlarmHdl_typeDriveInfo
Table 2-12: LAlarmHdl_typeDriveInfo
mapHwId UInt Mapped hardware id
(default value: 0)
noOfDOs USInt Number of drive objects at this
control unit
(default value: 0)
detectionState Int Actual detection state internal
case structure
(default value: 0)
driveAlarmInstOffset Int Internal offset for first instance of
LAlarmHdl_AddSINADriveAlarms
(default value: 0)
doIds Array[1..LALARMHDL_MAX_DOS_PER_ Drive object identifiers
DEVICE] of Int
doName Array[1..LALARMHDL_MAX_DOS_PER_ Name of drive object
DEVICE] of
WString[ALARMHDL_MAX_NAME_LEN]
checkSafetyExtended Array[1..LALARMHDL_MAX_DOS_PER_ TRUE: Integrated safety extended
DEVICE] of Bool functionalities activated at drive
object and safety messages are

stored in SI message buffer
LAlarmHdl_typeDevice
Table 2-13: LAlarmHdl_typeDevice
hardwareId HW_DEVICE Hardware identifier of the
device/slave
(default value: 0)
number UInt PROFINET device
number/PROFIBUS address of
the slave
(default value: 0)
name WString[LALARMHDL_MAX_NAME_LE Name of the device/slave
N] (default value: WString#’’)
type SInt Type of device
(default value: -2)
exists Bool TRUE: Device/slave is existing
configured Bool TRUE: Device/slave is configured
faulty Bool TRUE: Device/slave is faulty
problem Bool TRUE: Device/slave has a
problem
disabled Bool TRUE: Device/slave is disabled

Entry-ID: 109761931, V1.1, 02/2022 15
2 Engineering

error Bool TRUE: Error in device/slave
driveInfo LAlarmHdl_typeDriveInfo Array with drive information
LAlarmHdl_typeIOSystem
Table 2-14: LAlarmHdl_typeIOSystem
hardwareId HW_IOSYSTEM Hardware identifier of the IO-
System/DP-Mastersystem
(default value: 0)
number UInt IO-System/DP-Mastersystem
number
(default value: 0)
error Bool TRUE: Error in IO-System/DP-
Mastersystem
actualConfiguredDevic Int Number of configured
es devices/slaves in IO-System/DP-
Mastersystem
(default value: 0)
devices Array[1..LALARMHDL_MAX_DEVICES_ Device/Slave information

PER_IO_SYSTEM] of
LAlarmHdl_typeDevice
LAlarmHdl_typeDiagnostics
Table 2-15: LAlarmHdl_typeDiagnostics
status Word Status identifier when error
occurred
(default value: 16#0000)
subfunctionStatus Word Block status or error information
(default value: 16#0000)
deviceIndex Int Current device index where error
occurred
(default value: 0)
instanceIndex Int Current instance index where
error occurred
(default value: 0)

Entry-ID: 109761931, V1.1, 02/2022 16
2 Engineering
2.1.4 PLC tags
Table 2-16: Constants for device type in LAlarmHdl_Tags

Name Type Value Comment
LALARMHDL_DEVICE_TYPE_OTHER SInt -1 Device is configured in IO
system, but it is no
PROFIdrive device and no
SINAMICS
LALARMHDL_DEVICE_TYPE_SINAMICS SInt 1 Device is configured and a
SINAMICS drive system is
detected
LALARMHDL_DEVICE_TYPE_PROFIDRIVE SInt 2 Device type is PROFIdrive
LALARMHDL_DEVICE_TYPE_SINAMICS_SI SInt 3 Device is configured and a
SINAMICS drive system is
detected (extended safety is
active and safety messages
Cxxxxx are stored in separate
safety buffer)
Table 2-17: Miscellaneous constants in LAlarmHdl_Tags

Name Type Value Comment
LALARMHDL_MAX_DEVICES_PER_IO_SYSTEM Int 64 Max number of devices/slaves
per IO-System/DP-
Mastersystem
LALARMHDL_MAX_DOS_PER_DEVICE Int 10 Max number of DOs per
device
LALARMHDL_DOS_PER_IO_SYSTEM_UPPER_LIM Int 29 Upper limit of DOs per I/O-
system
LALARMHDL_MAX_NAME_LEN Int 40 Max length for name of DO

Entry-ID: 109761931, V1.1, 02/2022 17
2 Engineering
2.2 Project integration

2.2.1 Set up project languages
First of all, the correct project languages have to be chosen. The library includes
PLC alarm text lists for the SINAMICS drive systems in Chinese, English, French,
German, Italian and Spanish. The LAlarmHdl message texts are a combination of
the message texts of the following SINAMICS drive systems: S210, S120, G120
and V90 PN (descending order). That means, in case of equal error numbers but
different texts, e.g. at S120 and S210, the text of the S210 is used.
To have the messages available in the corresponding languages set up the project
languages in STEP 7 before integrating the LAlarmHdl PLC alarm text lists and the
LAlarmHdl blocks.
Figure 2-3: Set up project languages in TIA Portal


Entry-ID: 109761931, V1.1, 02/2022 18
2 Engineering
2.2.2 Device configuration of the PLC
To show the messages from the text lists correctly in your PLC, the languages
must be configured in the device configuration. The messages can only be
displayed if the language is configured and the according texts are available in this
language. In the following example, the project languages German and English are
selected to be loaded to the PLC.
Figure 2-4: Configuration of multilingual support in the PLC


Entry-ID: 109761931, V1.1, 02/2022 19
2 Engineering
2.2.3 Device configuration of the SINAMICS drive systems
To get the correct device state from the SINAMICS drive systems, the standard
alarms for PROFIdrive must be activated. This can be done in the device
configuration of the SINAMICS drive system (e.g. S120).
Figure 2-5: Configuration of standard alarms (PROFIdrive) in SINAMICS drive system


Entry-ID: 109761931, V1.1, 02/2022 20
2 Engineering
2.2.4 Integrating the alarm classes and text lists for alarm view into STEP 7
To display the messages in the alarm view of the PLC the text lists and alarm
classes must be integrated into the PLC from the LAlarmHdl library.
1. Integrate the alarm classes one by one from the library to the alarm classes in
the common data of the project
Figure 2-6: Integrating alarm classes in the common data of the project
2. Integrate the text lists one by one from the library to the PLC alarm text lists
Figure 2-7: Integrating text lists in the PLC alarm text lists

Entry-ID: 109761931, V1.1, 02/2022 21
2 Engineering
2.2.5 Integrating the library blocks into STEP 7
The table below lists the steps for integrating the blocks of the LAlarmHdl library
into your STEP 7 program.
Figure 2-8: Integrating the library blocks into STEP 7

NOTE Please follow the sequence of inserting the folders.
Table 2-18: Integrating the library blocks into STEP 7

No. Action
1. Integrate resource management and drive based functionalities of LAcycCom.
2. Copy the folder LAlarmHdl_Tags with Drag & Drop into the “PLC tags” in the PLC.
3. Copy the folder LAlarmHdl_Types with Drag & Drop into the “PLC data types” in the PLC.
4. Copy the folder LAlarmHdl_Blocks with Drag & Drop into the “Program blocks” in the PLC.
5. Now the blocks can be configured and called in the user program.
NOTE Additional required library is LAcycCom. The Resource management as well as

the Drive Based Functionalities are required.

Entry-ID: 109761931, V1.1, 02/2022 22
2 Engineering
2.2.6 Engineering of the fully autonomous alarm handling solution
To add the fully autonomous alarm handling solution for SINAMICS drive systems
the following steps must be done for every IO system.
Call in Startup OB
To have the best performance and prevent buffer overflow, the FB
LAlarmHdl_DriveAlarmsIOSystem must be called in the Startup OB. Then the
complete hardware configuration is scanned for IO devices at startup of the PLC.
For every IO system, one instance of the FB LAlarmHdl_DriveAlarmsIOSystem
block is required and one data block of type LAlarmHdl_typeIOSystem. In the
library a data block (DB) LAlarmHdl_IOSystemData of this type is already included.
If a second IO system includes also SINAMICS drive system, this block can be
copied and renamed.
Figure 2-9: Call of FB LAlarmHdl_DriveAlarmsIOSystem in Startup OB


Entry-ID: 109761931, V1.1, 02/2022 23
2 Engineering
Call in program cycle OB or cyclic interrupt OB

To scan the IO system cyclically for faults, alarms, … in the SINAMICS drive
systems, the FB LAlarmHdl_DriveAlarmsIOSystem must be called in a program
cycle OB (e.g. OB1) or a cyclic interrupt OB. Therefore, the same instances must
be used as in the Startup OB.
NOTE For operating the LAlarmHdl blocks the LAcycCom Resource Management and
Drive based functionalities are required in the PLC. More information can be
found in the LAcycCom manual.
Figure 2-10: Call of LAlarmHdl_DriveAlarmsIOSystem in program cycle OB


Entry-ID: 109761931, V1.1, 02/2022 24
2 Engineering
2.2.7 Engineering of the modular alarm handling approach
To add the modular approach for alarm handling an instance of the FB

LAlarmHdl_AddSINADriveAlarms function block must be added for every drive
object operated with alarm handling.
NOTE For operating the LAlarmHdl blocks the LAcycCom Resource Management and
Drive based functionalities are required in the PLC. More information can be
found in the LAcycCom manual.
NOTE To ensure most resources for other program parts the blocks should be operated
in a program cycle OB (e.g. OB1) or in a cyclic interrupt OB with low priority.
Use of status word to detect existing messages in the drive object

If the drive object has a cyclic communication and returns a status word with alarm,
fault and safety status this can be used to trigger the reading of the messages. This
solution guarantees the optimal calculation and communication performance.
In the following example the status word (ZSW1) is used to detect alarms and
faults. The readAlarms and readFaults inputs are triggered by means of this
information.
If the separate safety message buffer at SINAMICS S120 is used, the trigger
information for reading these messages (via input readSIMessages) can be taken
from the Safety Information Channel status word S_ZSW1B (not shown in the
following example).

Entry-ID: 109761931, V1.1, 02/2022 25
2 Engineering
Figure 2-11: Use of status word to detect existing messages

Cyclic reading of messages from a drive object

If no information of the status of the drive object is available, the messages can
also be read cyclically. The cycle is configured at the updateInterval input.
The cyclic reading of messages decreases the performance in comparison to use
the status of the drive object.
In the following figure the alarms and faults are read cyclically from a control unit.
The reading of safety integrated messages is disabled.

Entry-ID: 109761931, V1.1, 02/2022 26
2 Engineering
Figure 2-12: Cyclic reading of messages
Determining the hardware identification number

The hardware identifier of type “HW_IO” refers to an addressable component of the
IO device, e. g. the SINAMICS S120 CU. These hardware identifiers are created by
TIA Portal when a new SINAMICS drive is added to the project.
For acyclic data exchange the hardware identifier of the according module access
point or, if this is not available, the hardware identifier of the telegram can also be
used.
In the picture below, the relevant system constant has the value 266 and the
symbolic name
SINAMICS-S120-CU320-2PN~DO_Control_Unit_1~Module_Access_Point.
Figure 2-13: Determining the hardware identification number
When calling the FB LAlarmHdl_AddSINADriveAlarms the system constant has to

be interconnected via tag name or the decimal value to the hardwareId input. The
symbolic name of the system constant depends on the selected device name and
the project language. The value of the constant in the above picture may deviate to
the value in the user project.

Entry-ID: 109761931, V1.1, 02/2022 27
2 Engineering
Addressing of the drive object only by hardware identifier (for local parameter access)
By setting the driveObjectId input to -1 the FB LAlarmHdl_AddSINADriveAlarms
function block communicates with the module selected by the hardware identifier
set at the hardwareId input.
The correct hardware identifier is selected by using the module access point
hardware identifier or the hardware identifier of a telegram. Therefore, the drive
object identifier is not needed for accessing the module of the drive.
In the example below the module access point of the control unit is selected. This
leads to a communication with the drive object 1, the control unit itself. The drive
object identifier is selected by the hardware identifier.
Figure 2-14: Example block call without drive object identifier

When -1 is selected at the driveObjectId input, the FB

LAlarmHdl_AddSINADriveAlarms block sets the communication mechanism to
local parameter access via PROFIdrive (dataset 0xB02E). The local parameter
access is mandatory for every PROFIdrive compliant drive system.
Every value >= 0 is leading to an access to the drive object with global parameter
access (dataset 47). Then the hardware identifier is only specifying the drive
system and the drive object is addressed via the drive object identifier. This access
method is optional for PROFIdrive compliant drives but works with every
SINAMICS drive system.

Entry-ID: 109761931, V1.1, 02/2022 28
2 Engineering
2.2.8 WinCC “Alarm view” settings
To view the messages in the text lists included in LAlarmHdl, the following steps
have to be done in the engineering of the HMI in WinCC Comfort.
1. Choose background colors for the alarm classes in the HMI
Figure 2-15: Choose background colors for the alarm classes
2. Activate display of alarm class colors in the HMI
Figure 2-16: Activate display of alarm class colors

3. Add an alarm view to an HMI screen
Figure 2-17: Add alarm view

Entry-ID: 109761931, V1.1, 02/2022 29
2 Engineering
4. Enable display of LAlarmHdl alarm classes in the properties of the alarm view
Figure 2-18: Enable display of LAlarmHdl alarm classes in the alarm view
2.2.9 Cycle time reduction and data storage adaption in fully autonomous
solution
To guarantee the best performance in cycle time and to have the best use of data
storage in the PLC some constants should be adapted to the needs of the project.
LALARMHDL_DOS_PER_IO_SYSTEM_UPPER_LIM
The most import constant is LALARMHDL_DOS_PER_IO_SYSTEM_UPPER_LIM.
This constant defines the number of instances of instruction Program_Alarm that
are strictly limited depending on PLC type.
The drive objects are counted for each drive system in the instance data block at
tag statNextFreeAlarmIdx. Keep in mind that only connected and fully detected
drive systems are counted.
The constant should be set one less than the accumulated number of drive objects,
because the corresponding array starts with 0.
LALARMHDL_MAX_DOS_PER_DEVICE
The constant LALARMHDL_MAX_DOS_PER_DEVICE influences the memory
usage in the PLC but doesn’t have any influence on cycle time.
The constant should be set to the maximum number of drive objects existing at any
drive system at any IO system.
LALARMHDL_MAX_DEVICES_PER_IO_SYSTEM
The constant LALARMHDL_MAX_DEVICES_PER_IO_SYSTEM influences the
memory usage in the PLC but doesn’t have any influence on cycle time.
The constant should be set to the maximum number of devices available at any IO
system at the PLC where alarm handling should be integrated.

Entry-ID: 109761931, V1.1, 02/2022 30
2 Engineering
2.3 Operation
2.3.1 Operation of the fully autonomous solution
If the fully autonomous solution with the FB LAlarmHdl_DriveAlarmsIOSystem is

used, no further operation is necessary.
If a SINAMICS drive system, configured in the hardware configuration, is not
available at the IO system (e.g. device is disconnected), all messages for this
device are deleted. When the device returns, it is checked for pending messages
and reintegrated in the alarm handling.
2.3.2 Operation of the modular approach
Activation
The FB LAlarmHdl_AddSINADriveAlarms is activated via the enable input. After
enabling the block, the other inputs of the interface are used to read the messages
from a drive object. With a falling edge at enable input the FB is stopped and all
messages are deleted from the alarm view.
If an error occurs, the error can be acknowledged by restart of the FB with a new
rising edge at enable input.
Figure 2-19: Timing diagram of activation and deactivation
enable
valid
busy
error
ERR_TRIGGERED_ALARMS_
PER_CYCLE
status
STATUS_SUBSEQUENT_CALL
STATUS_FIRST_CALL
STATUS_NO_CALL
1) 2) 3) 4) 5)
1) The function block is activated by setting the enable input. After enabling
the FB, the output status is changing to STATUS_FIRST_CALL and
afterwards to STATUS_SUBSEQUENT_CALL. All configuration
parameters are stored internally at the rising edge of the enable input.
In case there is a configuration error, (e.g. the number of read messages
per cycle is too high) the error output is set and a respective status is
displayed.
2) With a falling edge of enable, the function block is reset.
3) The constant is corrected now, and the FB enable input is set again.
4) Enabling of function block is finished when valid output is signalizing
TRUE. The function block is ready for operation.
5) The FB is deactivated with reset of the enable input. The valid output is
reset immediately. When deactivating is finished the output busy is reset
and the output status changes to STATUS_NO_CALL.

Entry-ID: 109761931, V1.1, 02/2022 31
2 Engineering
Reading of messages
Messages are read according to the input that is set.
Alarms are read as long as the readAlarms input is set or as long as the alarm is
pending on the drive object.
The same handling is used for faults with the readFaults input and safety integrated
messages with the readSIMessages input.
Figure 2-20: Timing diagram of operating mode handling

updateInterval
Inputs
readAlarm
resetAlarmView
Outputs
alarmActive
Conditions
alarm in drive active
Message in alarm
view displayed
1) 2) 3) 4) 5) 6) 7) 8)
1) The reading of alarms is started with a rising edge at readAlarms input.

The first scenario shows the connection of the input to the status word of
the drive object. So, at the same time the readAlarms input is set an alarm
is active in the drive.
2) After the reading has been finished and an alarm was detected, the
alarmActive output is set and the alarm is sent to the alarm view of the
PLC. The drive object is checked for alarms in the updateInterval.
3) The readAlarms input is reset, but the alarm was not cleared in the drive.
In this case the block keeps on reading the alarms in the updateInterval
until the alarm has been cleared in the drive object. After recognizing that
the alarm is cleared the alarm is deleted from the alarm view.
4) No alarm occurred in drive. The readAlarms input is set. In this case the
drive object is checked immediately and afterwards in the updateInterval
with acyclic data exchange.
5) An alarm in the drive object occurs. In the next updateInterval the alarm is
read from the drive object, the alarmActive output is set and the alarm is
sent to the alarm view of the PLC.
6) The alarm is cleared in the drive object. In the next updateInterval the reset
of the alarm is recognized by the block and the alarm is reset in the alarm
view of the PLC.
7) The readAlarms input is reset and the reading of the alarms is stopped. For
some reason an alarm is stuck in the alarm view and was not reset by the
PLC.
8) Stuck alarms set by this instance can be cleared by setting the
resetAlarmView input. If the error was not cleared in the drive object and
the resetAlarmView input is set, the message is also deleted. After
resetting the input, not acknowledged alarms are set again when the
readAlarms input is set.

Entry-ID: 109761931, V1.1, 02/2022 32
2 Engineering
2.3.3 Operation of the WinCC Comfort Panel
To show the messages in the WinCC Comfort Panel the configured alarm view has
to be opened. The messages are automatically shown in the alarm view at the time
they appear.
Figure 2-21: Appearance of the messages in the WinCC Comfort Panel
2.3.4 Operation of the SIMATIC S7-1500 Webserver

As well as in WinCC Comfort Panels, the messages can also be seen in the
SIMATIC S7-1500 webserver. To do this open the webserver and go to the alarms
page.
Figure 2-22: Appearance of the messages in the S7-1500 webserver

Entry-ID: 109761931, V1.1, 02/2022 33
2 Engineering
2.4 Error handling

2.4.1 Error handling of fully autonomous solution
The fully autonomous solution with the FB LAlarmHdl_DriveAlarmsIOSystem sets

only errors at the commissioning phase. That means if all drives are connected to
the PLC and no error is appearing, also no error is shown at the polling phase. The
errors can all be solved with configuring the according constants and restarting the
PLC.
WARN_ADD_SINA_DRIVE_ALARMS – 16#7200
Error at an instance of the subfunction LAlarmHdl_AddSINADriveAlarms occurred.
More information can be found in the diagnostics output of the function block.
The according instance can be found in the instance data block of the FB
LAlarmHdl_DriveAlarmsIOSystem. The according index of multi instance array
(instAlarmHdl) is diagnostics.instanceIndex.The device where the error occurred
can be found in ioSystemData.devices[diagnostics.deviceIndex].
NOTE Most likely the call of the LAcycCom_ResourceManager is missing if this error
occurs.
ERR_MAX_DEVICES_PER_IO_SYSTEM – 16#8401
More devices are configured in the IO system than could be stored in the
predefined storage.
To solve the problem, increase the constant LALARMHDL_MAX_DEVICES_
PER_IO_SYSTEM in tag table LAlarmHdl_Tags to the number of devices
configured in your hardware configuration for this IO system.
ERR_NO_OF_DOS_PER_IOSYSTEM – 16#8402
More drive objects were found in the IO system than could be polled with the
predefined storage.
To solve the problem, increase the constant LALARMHDL_DOS_PER_IO_
SYSTEM_UPPER_LIM in tag table LAlarmHdl_Tags to the number of DOs that are
configured in your IO system.
ERR_NO_OF_DOS_PER_DEVICE – 16#8403
More drive objects were found in a configured device than could be saved in the
predefined storage
To solve the problem, increase the constant LALARMHDL_MAX_DOS_PER_
DEVICE in tag table LAlarmHdl_Tags to the number of DOs existing in the device
with the most drive objects.
ERR_GET_DEVICE_STATE – 16#8600
Error at called system function DeviceStates. Have a look at the Online Help of
STEP 7 Professional with the error code displayed in the output
diagnostics.subfunctionStatus.
ERR_GET_NAME – 16#8601
Error at called system function Get_Name. Have a look at the Online Help of STEP
7 Professional with the error code displayed in the output
diagnostics.subfunctionStatus.

Entry-ID: 109761931, V1.1, 02/2022 34
2 Engineering
2.4.2 Error handling of modular approach
The modular approach with FB LAlarmHdl_AddSINADriveAlarms can have errors

that must be solved after first start as well as errors which must be solved at
runtime.
ERR_READ_DRIVE_MESSAGES – 16#8601
An error in the subfunction LAcycCom_ReadDriveMessagesDateTime occurred.
For more detailed information the error code of the subfunction is displayed in the
output diagnostics.subfunctionStatus.
NOTE More information about the error code in diagnostics.subfunctionStatus can be

found in the LAcycCom manual:
The diagnostics of the LAcycCom_ReadDriveMessagesDateTime block can be
found in the instance data block of LAlarmHdl_AddSINADriveAlarms at the tag
instReadDriveMessages.diagnostics.
NOTE Most likely the call of the LAcycCom_ResourceManager is missing if this error
occurs.
ERR_TRIGGERED_ALARMS_PER_CYCLE – 16#8602
For a drive object more alarms are triggered in a cycle than possible. Please
decrease the internal constant NO_OF_TRIGGERED_ALARMS_PER_CYCLE in
the FB LAlarmHdl_AddSINADriveAlarms.

Entry-ID: 109761931, V1.1, 02/2022 35
2 Engineering
2.5 Time synchronization of SINAMICS drive systems

When using an alarm handling system which integrates the drive messages into
the alarm view, it is necessary to synchronize the time between the controller and
the drives. The advantage of synchronized times is that the messages from the
drives and the messages of the controller (e.g. technology object) are sorted by
timestamp in the alarm view. This allows a first fault analysis.
If the timestamp of a drive and the PLC differs too much, the alarm handling blocks
use automatically the timestamp of the PLC when transferring the alarm to the
alarm display in the PLC.
Table 2-19:Time synchronization methods according to drive system

Drive system Control unit Method for time Accuracy
synchronization
S210 - NTP server approx. 10ms
S120 CU320-2 a) Acyclic by parameter a) approx. 100ms
S150 CU310-2 b) Acyclic with ping/snap via RT b) approx. 10ms
c) Acyclic with ping/snap via IRT c) approx. 1ms
d) NTP server d) approx. 10ms
G120 CU230P-2 By user e.g. with TIA Portal
G120 others No time synchronization possible
V90 PN All Acyclic by parameter approx. 100ms
NOTE A detailed description about time synchronization methods can be found in

chapter “Time synchronization between the control and converter” in \3\
NOTE For the time synchronization method "Acyclic by parameter" the block
LAcycCom_RTCSinamicsAcyclic can be used (see \4\).
For the time synchronization method "Acyclic with ping/snap …" the block
LAcycCom_RTCSinamics can be used (see \4\).

Entry-ID: 109761931, V1.1, 02/2022 36
3 Appendix
3 Appendix
3.1 Service and support
Industry Online Support
Do you have any questions or need assistance?
Siemens Industry Online Support offers round the clock access to our entire
service and support know-how and portfolio.
The Industry Online Support is the central address for information about our
products, solutions and services.
Product information, manuals, downloads, FAQs, application examples and videos
– all information is accessible with just a few mouse clicks:
support.industry.siemens.com
Technical Support
The Technical Support of Siemens Industry provides you fast and competent
support regarding all technical queries with numerous tailor-made offers
– ranging from basic support to individual support contracts. Please send queries
to Technical Support via Web form:
www.siemens.com/industry/supportrequest
SITRAIN – Training for Industry

We support you with our globally available training courses for industry with
practical experience, innovative learning methods and a concept that’s tailored to
the customer’s specific needs.
For more information on our offered trainings and courses, as well as their
locations and dates, refer to our web page:
www.siemens.com/sitrain
Service offer
Our range of services includes the following:
• Plant data services
• Spare parts services
• Repair services
• On-site and maintenance services
• Retrofitting and modernization services
• Service programs and contracts
You can find detailed information on our range of services in the service catalog
web page:
support.industry.siemens.com/cs/sc
Industry Online Support app

You will receive optimum support wherever you are with the "Siemens Industry
Online Support" app. The app is available for Apple iOS, Android and Windows
Phone:
support.industry.siemens.com/cs/ww/en/sc/2067

Entry-ID: 109761931, V1.1, 02/2022 37
3 Appendix
3.2 Application support

Siemens AG
Digital Industries
Factory Automation
Production Machines
DI FA PMA APC
Frauenauracher Str. 80
91056 Erlangen, Germany
mailto: tech.team.motioncontrol@siemens.com
3.3 Links and literature

Table 3-1
No. Topic
\1\ Siemens Industry Online Support
https://support.industry.siemens.com
\2\ Link to this entry page of this application example
\3\ Link to the S120 Function Manual Drive Functions in STARTER
\4\ Link to LAcycCom library for acyclic data exchange
\5\ Link to LSNTP library for time synchronization
3.4 Change documentation

Table 3-2
Version Date Modifications
V1.0 03/2019 First version
V1.1 07/2021 The LAlarmHdl PLC alarm text lists now include further
languages (Chinese, French, Italian, Spanish) besides
German and English
V1.1 02/2022 The FB LAlarmHdl_DriveAlarmsIOSystem does not support
the PROFIdrive Integrated IO system of the SIMATIC Drive
Controller

Entry-ID: 109761931, V1.1, 02/2022 38

LAlarmHdl SIMATIC V1 1 en 02 2022

Uploaded by

Copyright:

Available Formats

LAlarmHdl SIMATIC V1 1 en 02 2022

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LAlarmHdl SIMATIC V1 1 en 02 2022

Uploaded by

Copyright:

Available Formats

Alarm Handling for

LAlarmHdl for SIMATIC

2.2.9 Cycle time reduction and data storage adaption in fully

LAlarmHdl for SIMATIC

LAlarmHdl for SIMATIC

Table 1-1: Comparison about approaches and blocks

PLC background is needed to scan the needed to communicate to drives

LAlarmHdl for SIMATIC

1.2 Mode of operation

LAlarmHdl_DriveAlarmsIOSystem is the FB for an autonomous application that

LAlarmHdl_AddSINADriveAlarms is the FB that collects messages of a SINAMICS

The messages generated in the controller contain the following information:

LAlarmHdl for SIMATIC

1.3 Components used

This application example consists of the following components:

LAlarmHdl library LAlarmHdl_V1_1_x.zip

LAlarmHdl for SIMATIC

Additional required library:

Table 2-1 List of blocks

FB 31901 LAlarmHdl_AddSINADriveAlarms In-house development

Size of the individual block

Table 2-3 Size of block instances

InstLAlarmHdl_DriveAlarmsIOSystem 348 366 6

LAlarmHdl for SIMATIC

2.1.1 LAlarmHdl_DriveAlarmsIOSystem (FB 31900)

Figure 2-1: Block diagram of FB LAlarmHdl_DriveAlarmsIOSystem

HW_IOSYSTEM ioSystemHwId error Bool

NOTE By using this solution, the FB LAlarmHdl_AddSINADriveAlarms is not allowed to

NOTE If Safety Integrated Extended/Advanced Functions in SINAMICS S120 are used,

LAlarmHdl for SIMATIC

LAlarmHdl for SIMATIC

Status and error displays

LAlarmHdl for SIMATIC

2.1.2 LAlarmHdl_AddSINADriveAlarms (FB 31901)

Figure 2-2: Block diagram of FB LAlarmHdl_AddSINADriveAlarms

Bool enable valid Bool

Bool readFaults status Word

The FB LAlarmHdl_AddSINADriveAlarms reads active messages from a

NOTE If Safety Integrated Extended/Advanced Functions in SINAMICS S120 are used,

LAlarmHdl for SIMATIC

Name Data type Comment

LAlarmHdl for SIMATIC

Status and error displays

LAlarmHdl for SIMATIC

2.1.3 PLC data types

object and safety messages are

LAlarmHdl for SIMATIC

Name Data type Comment

devices Array[1..LALARMHDL_MAX_DEVICES_ Device/Slave information

LAlarmHdl for SIMATIC

2.1.4 PLC tags

Table 2-16: Constants for device type in LAlarmHdl_Tags

Table 2-17: Miscellaneous constants in LAlarmHdl_Tags

LAlarmHdl for SIMATIC

2.2 Project integration

Figure 2-3: Set up project languages in TIA Portal

LAlarmHdl for SIMATIC

2.2.2 Device configuration of the PLC