William_B

The before mentioned method (Jens_app and Sarfraz Bhatti)
is by far the best option.

I know it is purely academical now.. but the AT declaration is still a possibility.
Included is an abstract from the TIA V11 manual describing the AT declaration.

The downfall for this method is that it needs to be created within an FB;
it can not be created within a stand-alone DB.

The good thing about the method is that the access is symbolic
and thus more adaptable to changes within the DB structure.

w

Thank you all for sharing tactics. But I would like to enclose my following points:

1. As said by Sarfraz Bhatti and Jens_app HMI discrete alarms can be configured through absolute addressing of data block for which the data block must loose optimization attributes. But this way may lead to engineering reworks if unintentionally new row or rows are added above the subject tag in the data block because doing so will change address of the tag in data block and HMI tag will not update its address thus leading to change in HMI tag mapping with target tag in DB. For large number of tags, this will required extra engineering time to re-map those tags.
2. As  William_B said AT declaration can help out to trigger bits in DB while keeping HMI tag as Int type which fundamental requirement of Alarm tag.

Dear William_B the guide provided by you for AT declaration is insufficient to me. I am curious to implement this handy procedure. Although I understand its working philosophy and tried it at my own end but I still get syntax error when I use AT declaration. I tried it for both cases when DB is optimized and DB is non-optimized

1. Can you please, share more stuff with step by step guide? I tried other threads but I couldn't implement it. Perhaps I am missing something or there is problem with compatibility? I am using TIA Portal V13 Update1 and the controller used is 1215C.
2. Should DB be optimized or non-optimized. In your attached picture it is non-optimized.

you can do the following
1. in your data block (NOT optimized) define alarms in packs of 16 or 32 BOOLs (one struct for each part of machine)
    GENERAL : STRUCT
     HA_ESTOP : Bool; // ESTOP
      ……
     HA_SPARE_3_7 : Bool; // GENERAL - alarm 32
2. in HMI define HA_DBW0 for word 0 of your DB (covers alarms 0..15)
3. in HMI define HA_DBW2 for word 2 of your DB (covers alarms 16..31)
and so on

then create alarm list - just fill in 1st alarm with bit 0 and then expand list until it uses all 16 bits.
Create next alarm - it will show invalid. change alarm tag to HA_DBW2 and bit to 0. Repeate expand 

when you do 1,2,3 for length of your DB (for example 100 words for 200 bytes of alarms) sort list by trigger address
(you may need right click table header and enable address column) then copy alarm texts from DB comments to the list
(assume alarm texts are in full written to DB tag comments)