User Tools

Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
alerts [2018/08/06 08:34]
emozolyak
alerts [2018/08/06 08:37] (current)
emozolyak
Line 4: Line 4:
  
  
-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.+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 ​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.+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 alarms ​can be allowed to be acknowledged. This allows you to tell the system that the operator is aware of its occurrence. Also for the alarm you can set its level - Information,​ Warning, Accident. In the initial state, the "Alarms" side menu item is empty, crashes there will only appear after creating at least one register with alarm bits in the project.+Any of alerts ​can be allowed to be acknowledged. This allows you to tell the system that the operator is aware of its occurrence. Also for the alerts ​you can set its level - Information,​ Warning, Accident. In the initial state, the "Alerts" side menu item is empty, crashes there will only appear after creating at least one register with alert bits in the project.
  
 {{::​setup_alerts2.png?​direct&​800|}} {{::​setup_alerts2.png?​direct&​800|}}
  
-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 ​alarms, an audible ​alarm will be issued every 15 seconds. ​+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 ​alerts, an audible ​alert will be issued every 15 seconds. ​
  
 {{::​alerts_in_status_bar.png?​direct&​800|}} {{::​alerts_in_status_bar.png?​direct&​800|}}
  
-To view the current ​alarms, you can click on the text with the alarms ​in the status line. This will open a pop-up window with a list of current crashes. In this window you can see their list, the time of the occurrence of the alarm, acknowledge the alarm, see the login of the user who acknowledged the alarm.+To view the current ​alerts, you can click on the text with the alerts ​in the status line. This will open a pop-up window with a list of current crashes. In this window you can see their list, the time of the occurrence of the alert, acknowledge the alert, see the login of the user who acknowledged the alert.
  
 {{::​alerts_list.png?​direct&​800|}} {{::​alerts_list.png?​direct&​800|}}
  
-Also, using Lua programs, you can perform certain actions depending on the current ​alarms. For example, you can send SMS messages if there are alarms ​that have not been acknowledged for more than 10 minutes. Or any other action. An example of handling an alarm list is [[http://​docs.webhmi.com.ua/​scripts#​getcurrentalerts | here]]+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://​docs.webhmi.com.ua/​scripts#​getcurrentalerts | here]]
  
-Past alarms ​can be viewed in the alarm log.+Past alerts ​can be viewed in the alert log.
  
 {{::​alert_log.png?​direct&​800|}} {{::​alert_log.png?​direct&​800|}}

Page Tools