Differences

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

--- events [2020/12/01 16:13] – [Other event usage options] emozolyak
+++ events [2020/12/03 15:57] – [Notes on event usage] emozolyak
@@ Line 202: / Line 202: @@
 The Report constructor for events may not be convinient in some cases:
   *the processes last long time (days, weeks, monthes, years etc) and event logging may be interrupted by some maintenacne or other occastions which is not acceptable (this will split the event)
-  *you need to generate report which unites data from many different events, so you can not use report cunstructor which is bound by one event and its sub-events
+  *you need to generate report which unites data from many different events, so you can not use event's report constructor which is bound by one event and its sub-events
   *the system consist of many logical units which would require to make a lot of duplicating reports
 In this cases, still a desired report can be obtained from particular events, lua, api and screen/dashboard editor.
 You can use the following approach:
-  *use screen/dashboard for user control (picking dates, machines, dates etc.)
+  *use screen/dashboard for user report setup (picking dates, machines, shifts etc.)
   *use lua script which would make api call to webhmi's event log and fetch neccessary data
-  *use javascript to change widget properites - start / end time for graph, changing parameters etc.
+  *use javascript to change screen widget properites - start / end time for graph, changing parameters etc.
+<WRAP center round info 80%>
+Please refer to the following application [[events_in_machine_monitoring | note]].
+</WRAP>
 ===== Notes on event usage =====
@@ Line 216: / Line 219: @@
 === Editing events in the running project ===
-<WRAP center round important 60%>
+<WRAP center round important 80%>
 Due to 'on the fly' method of recordig events, WebHMI project restart will cause an event being recorded to
 "split". If you have some important report or critical data in your project and edit or comission the project remotely, apply changes when the event unlikely to happen or won't cause data distortion.
@@ Line 225: / Line 228: @@
 === One - time events ===
-<WRAP center round tip 60%>
+<WRAP center round tip 80%>
 With one-time event, i.e. those not having 'event has duration' checkbox set, remember that while the event condition is **true** WebHMI will generate excess records in the DB on every scan. Use lua script which provides one scan duration of the event enabling condition.
 </WRAP>