Configure global alarms

1. Open the global alarm area

Select Globale Alarme in the page list. Open the large alarm display’s properties by double-click or right-click and choose Configure alarms (Alarme einstellen). The global alarm page and its display are protected: they cannot be deleted, copied or duplicated.

2. Load the simulation example

Click Load simulation example (Simulationsbeispiel laden). It configures device Simulation, start address 40001, two words and three messages: 40001 bit 0 = fault, Anlage Störung; 40001 bit 1 = warning, Temperatur Warnung; 40002 bit 0 = information, Wartung erforderlich. These local test addresses do not select a future driver. Replacing existing alarm definitions requires confirmation.

3. Understand the alarm range

PLC/device identifies the source; its driver assignment determines communication. Start address is the first monitored address, e.g. 40020, DB10.DBW20 or a NodeId. Word count is 1–64. Symbol selects the start variable from the PLC table. Highlight unacknowledged messages emphasizes open messages. Alarm displays monitor their range independently: every message need not have a separate visible object or symbol. Reserve a dedicated alarm range in real projects to avoid accidental alarms from ordinary values or controls.

The shared address of the test button below is deliberate.

4. Import real-project definitions

The PLC table holds devices, symbols, addresses, data types and connection settings; import its CSV/XML from the main toolbar. The separate alarm-text CSV holds address, bit, message and class and is imported inside alarm settings. Prepare the PLC table, enable the intended driver, select the alarm start symbol and import alarm texts. Supported paths include simulation, full Modbus addresses, Connect device addresses, complete S7 addresses such as DB10.DBW20, and OPC UA NodeIds such as ns=2;s=Alarms.Active.

Individual BOOL nodes use bit 0. New projects include separate Modbus, S7 and OPC UA examples. The alarm CSV uses Adresse;Bit;Meldung;Klasse. Adresse/Register mean full addresses; only fields explicitly named Offset or RegisterOffset are added to the start address. Save CSV template creates an editable sample.

5. Edit individual messages

Select a list entry, change address, bit, text or class on the right, then Save changes to entry. Without selection that button is disabled. Entries are sorted by address and bit, including after editing/import; the edited entry stays selected. Add as new entry creates another message; Delete entry removes the selection; Delete all clears the list after confirmation.

6. Apply and save

Apply the alarm dialog and object properties. Check the colored preview on Globale Alarme, then save with Ctrl+S. Design-mode rows are a preview; actual timestamps and state changes come from runtime values.

7. Add a local test button

On Anlagenübersicht insert Basic objects → Button. Set its visible label to Alarm simulieren, PLC/device to Simulation and physical address to 40001; retain BOOL and leave IP and symbol empty. This intentionally targets bit 0 of the first alarm. In Button function choose Toggle on/off (Ein / Aus umschalten), on text Alarm EIN and off text Alarm AUS. Apply both dialogs and save.

8. Test the alarm lifecycle

Use no external driver and start F5. Click Alarm AUS to turn it on: the global strip becomes red with GLOBAL 1 · 1 offen. Open the alarm page, select KOMMT – Anlage Störung and acknowledge the selected message. Return to the overview, switch Alarm AUS, then reopen the alarm page. History records KOMMT (became active), QUITT. (acknowledged by an authorized operator) and GEHT (condition cleared). The global strip remains visible on process pages; Open alarm page opens history and Back returns.

Runtime history can be exported to CSV. Acknowledgement does not remove the cause: an active PLC bit keeps the fault active.

9. Common questions

Use the local Simulation example without driver configuration. For unexpected alarms, check overlapping addresses. For a disabled edit button, select an entry first. If CSV import yields no messages, check headers: address, bit and message are required, class is optional; bits outside 0–31 are ignored.

Messages in multiple languages

Custom alarm messages are not translated automatically. Enter the required translations for each German base message.

1. Open the alarm area and select a definition.
2. Click Translations next to the alarm text. English, French, Italian, Spanish, Dutch, Polish and Portuguese can be entered separately.
3. Apply the translations, choose Save entry changes, then apply the alarm dialog and save the project.

Active messages, the global alarm bar and displayed history use the selected interface language. Missing or blank translations fall back to the German base text. New history entries retain the message text and translations valid at the time of the event; older entries without translations retain their stored text. Dynamic text received from a PLC is displayed unchanged.

Standard labels also follow the interface language: ACTIVE, CLEARED, ACK., “No active global alarms”, “Acknowledge selected alarm” and “Export history as CSV”. Internal event codes remain stable; CSV exports may therefore still contain German event codes.

The tank demo has separate pump messages for manual mode (bit 1), fault (bit 2) and maintenance (bit 3).