events
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
events [2020/12/01 12:00] – [Other event usage options] emozolyak | events [2021/08/05 13:36] – [Events] emozolyak | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | {{ : | ||
====== Events ====== | ====== Events ====== | ||
Line 76: | Line 77: | ||
***Save data** There are 2 options: | ***Save data** There are 2 options: | ||
*__Once per Event__ | *__Once per Event__ | ||
- | *__Every X seconds__ . All data will be saved at regular interval, i.e. there will be multiple records with their respective timestamps. This option is used when you want to build a graph based on the event data in [[creating_advanced_reports_in_level2? | + | *__Every X seconds__ . All data will be saved at regular interval, i.e. there will be multiple records with their respective timestamps. This option is used when you want to build a graph based on the event data in [[level2:creating_advanced_reports_in_level2? |
=== Selecting registers for the event === | === Selecting registers for the event === | ||
Line 191: | Line 192: | ||
=== Send event data to Level2 === | === Send event data to Level2 === | ||
- | There is a report builder in the Level2 system as well which uses data taken from WebHMI as a source. More on this [[creating_advanced_reports_in_level2? | + | There is a report builder in the Level2 system as well which uses data taken from WebHMI as a source. More on this [[level2:creating_advanced_reports_in_level2? |
=== Creating a timeline based on time from the event === | === Creating a timeline based on time from the event === | ||
Line 200: | Line 201: | ||
=== Advanced customized reports based on events, screens, lua and api === | === Advanced customized reports based on events, screens, lua and api === | ||
- | getting historical | + | 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 | ||
+ | *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/ | ||
+ | *use lua script which would make api call to webhmi' | ||
+ | *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]]. | ||
+ | </ | ||
===== Notes on event usage ===== | ===== Notes on event usage ===== | ||
Line 206: | Line 220: | ||
=== Editing events in the running project === | === Editing events in the running project === | ||
- | <WRAP center round important | + | <WRAP center round important |
Due to 'on the fly' method of recordig events, WebHMI project restart will cause an event being recorded to | Due to 'on the fly' method of recordig events, WebHMI project restart will cause an event being recorded to | ||
" | " | ||
Line 215: | Line 229: | ||
=== One - time events === | === 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' | With one-time event, i.e. those not having 'event has duration' | ||
</ | </ |
events.txt · Last modified: 2022/01/26 14:15 by emozolyak