alerts
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
alerts [2018/08/06 08:26] – emozolyak | alerts [2020/04/08 15:24] – [New alerts configuration] emozolyak | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Alerts ====== | ====== Alerts ====== | ||
- | ---- | + | ===== New alerts configuration ===== |
+ | In WebHMI there is the concept of an alert. An alert is a state of the system that requires human attention. WebHMI signals on all alerts visually (red status bar on the dashboards) and an audible signal about unqualified accidents. The alerts are kept in a special alerts log. | ||
- | In WebHMI there is the concept of an alarm. An alarm is a state of the system that requires human attention. WebHMI signals all alarms visually (red status bar on the dashboards) and an audible signal about unqualified accidents. Emergencies are logged for later analysis. | + | Starting from 3.6 fw version, __a new alert setup__ has beed implemented. For versions below 3.6 please refer to the next section. |
- | Usually alarms in the PLC are organized as a set of bits in any of the registers. Each bit is the flag of a single alarm. In WebHMI alarms are configured in the register editor, i.e. a register or group of registers can be allocated for handling accidents. This makes it convenient to transfer them from the project to the project and from the connection to the connection when they are cloned. If any of the devices has a different format for representing the alarms, for example, for each type of alarm a separate register, or an alarm code with a combination of a bit flag, etc. - such alarms can be brought to the standard way by using the capabilities of scripts on Lua, having generated the alarm bits in the internal register. | + | When some alert triggers there will be pop-up window, like this - |
- | Any of alarms | + | {{ :: |
+ | |||
+ | There will be the alert title, group (if it belongs to a group), start time, duration, acknowledge status and the link to details. | ||
+ | In the new alerts there is a number of improvements: | ||
+ | *more complex conditions for each alert. | ||
+ | *richer alert description with insructions | ||
+ | *operator can add comments after alert has been triggered | ||
+ | *templates - for identical devices with the same alerts conditions, you can setup only one template | ||
+ | |||
+ | The alert setup link is here: | ||
+ | |||
+ | {{ :: | ||
+ | |||
+ | The example of an alert list: | ||
+ | |||
+ | {{ :: | ||
+ | |||
+ | Here: | ||
+ | -is the button to create an **alert object** | ||
+ | -is the button to create an **alert group** | ||
+ | -is the list of non-grouped alerts | ||
+ | -is the **category** name for organizing the list. There are 2 groups in the example provided. | ||
+ | -it is a list of **grouped alerts**. The titles in bold text indicate group title. Only a group can be a template for another group of alerts. The template column tells if the group is a template or templates' | ||
+ | -is a list of **templates' | ||
+ | |||
+ | In the __Basic__ edit alert tab you set title, template, category and level (Info, Warning, Alert), wether to allow acknoledge and sound signal. | ||
+ | |||
+ | {{ :: | ||
+ | |||
+ | In the __Condition__ tab, you define the condition which will trigger the alert. It can be specific bit of a register or its value (=, ≠, <, >, [a, b]((in range from a to b))). The multiple conditions are combined only with AND operator. So for OR operation or more complex conditions you can use Lua scripts. | ||
+ | |||
+ | {{ :: | ||
+ | |||
+ | In the __Information__ tab, there is a text editor with formatting options to create messages including one optional picture. This message will be shown if an operator press Details... link in the alert pop-up dialog. | ||
+ | |||
+ | {{ :: | ||
+ | |||
+ | Information page in this case could be like this: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== Alerts configuration before 3.6 fw version ===== | ||
+ | |||
+ | In WebHMI there is the concept of an alert. An alert is a state of the system that requires human attention. WebHMI signals all alert visually (red status bar on the dashboards) and an audible signal about unqualified accidents. Emergencies are logged for later analysis. | ||
+ | |||
+ | Usually alerts in the PLC are organized as a set of bits in any of the registers. Each bit is the flag of a single alert. In WebHMI alerts are configured in the register editor, i.e. a register or group of registers can be allocated for handling accidents. This makes it convenient to transfer them from the project to the project and from the connection to the connection when they are cloned. If any of the devices has a different format for representing the alert, for example, for each type of alert a separate register, or an alert code with a combination of a bit flag, etc. - such alerts can be brought to the standard way by using the capabilities of scripts on Lua, having generated the alert bits in the internal register. | ||
+ | |||
+ | Any of alerts | ||
{{:: | {{:: | ||
- | When an alarm occurs, the system will turn the status bar to red. The line will blink periodically to attract attention. Also, if there are unqualified | + | When an alert occurs, the system will turn the status bar to red. The line will blink periodically to attract attention. Also, if there are unqualified |
{{:: | {{:: | ||
- | To view the current | + | To view the current |
{{:: | {{:: | ||
+ | |||
+ | Also, using Lua programs, you can perform certain actions depending on the current alerts. For example, you can send SMS messages if there are alerts that have not been acknowledged for more than 10 minutes. Or any other action. An example of handling an alert list is [[http:// | ||
+ | |||
+ | Past alerts can be viewed in the alert log. | ||
+ | |||
+ | {{:: | ||
alerts.txt · Last modified: 2022/10/10 08:46 by emozolyak