Placeholder when browsing alarms

[yogiTheBear7000]

Hello,
Today I played a little with the alarms.
I called the BrowseAlarm class in the test program. Here I was sent 52 alarms directly. As I had no active alarms at the time, I assume that this is the diagnostic buffer.
The alarm texts themselves were not visible, instead I found characters there that strongly resembled placeholders. Is there already a known way to get the correct texts?

I have now also compared the process with subscribing to alarms, but found no practicable approach here to get to the texts with an ExploreRequest. There is probably not a missing connection between the text placeholders and the texts.

Greetings....

[thomas-v2]

Hi,
did you use the example methin AlarmSubscriptionCreate() from AlarmsHandler.cs?
This method requests to get the full text on alarm events and not only the Id. With programalarms, then the string formatting with inserting the additional values is already done in the plc. I haven't checked if this is also done on system messages.

[thomas-v2]

If you want to browse the alarmids with the texts in advance, you have to insert the additional values which come with the alarm event later into the alarmtext with the specified format. And also strings from textlists wich are also possible. I don't have this string formatting in the library yet.
If you do the alarm subscriptions from the example method, the plc does this all for you. In my opinion this is the easier variant, at least from the library perspective. But there may be use cases where someone needs to know the possible alarms in advance.

[yogiTheBear7000]

Thank you Thomas for your answers.
No, did´nt use the Alarmsubscription. I have dealt with the browsing of alarms and once tried to fill the missing data such as the replace the placeholders.
I have now taken a closer look at the Alarm Subscription, where the texts are already largely filled. Just as you had written. Many thanks for that.
Perhaps you also have an idea of how to differentiate between the alarm classes, e.g. whether it is an acknowledgement or no acknowledgement or a user-defined alarm.