How to differentiate signal Identification / description from Smart Objects in AML / CEL table

How to differentiate signal Identification / description from Smart Objects in AML / CEL table

Hi all,

I have 1 Smart Object Template (Circuit Breaker) with Variable "ST" - Identification = Description "Status"
with event (Reaction Matrix) "Close, Open" , and about other 40 variables with event like that

Then I have 2 Smart Object from that: CB1 and CB2. (CB1, CB2 is name in the design drawing)
The full name (called be operator) of CB1 is "INCOMMING H01 CB471" and CB2 is "OUTGOING H02 CB471". I want to include these object full name in Signal Identification/description like below:
for CB1_ST: INCOMMING H01 CB471 Status
for CB2_ST: OUTGOING H02 CB471 Status

However, when 2 variable (CB1_ST, CB2_ST) open, In AML/CEL table, I get 2 rows (messages) with same signal Identification: "Status", no idea what message belong to what device. 

Can not create Alarm Area or Equipment Model then set related properties of Smart Object 's variable

Solution 1: In AML/CEL I can add column "Signal Name", but I think it is not friendly to remember CB1 = INCOMMING H01 CB471.

Solution 2: in theory, in Smart Object Template, can use signal identification as Released Properties, however It is not practical because of having 40 variables. Setting 40 released properties / SO , 300 SO in total is huge work.

So my question is any solution to differentiate signal Identification / description from Smart Objects in AML / CEL table,  or can use formula in Signal Identification / Description 


    Disclaimer

    This document governs the use of our Community Forum. By registering and using the platform, you accept these conditions.

    The COPA-DATA Community Forum serves to encourage the exchange of information and experience about the zenon software between forum users respectively zenon users.

    Please mind that any published information on the Community Forum is the subjective opinion and view based on the experience and the level of knowledge of the author. COPA-DATA does not overtake any responsibility for the content and the accuracy of the shared information.

    Users of the Community Forum are encouraged to share only well-founded experiences and to point out any risks associated with the implementation of proposed solutions to problems. COPA-DATA at its absolute discretion, reserves the right to moderate the forum. In this connection COPA-DATA may remove any information containing false facts, potentially dangerous solutions, bad language or content that may insult, degrade or discriminate others. COPA-DATA may block a non-complying user from forum access if the user violated this provision.

    COPA-DATA reserves the right to change this document from time to time at own discretion.


    Ing. Punzenberger COPA-DATA GmbH
    Karolingerstraße 7b · 5020 Salzburg · Austria
    www.copadata.com