Differences

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

--- events [2019/01/15 09:59] – [Creating Event] emozolyak
+++ events [2019/01/15 10:34] – [Creating Event] emozolyak
@@ Line 36: / Line 36: @@
 In the Basic tab, there are 3 items:
-^Title| This title is for the list in the Setup menu |
+  ***Title** This title is for the list in the Setup menu
-^Description| To give any comments for the events |
+  ***Description** To give any comments for the events
-^Parent event| This event recorded only if a high-level, or parent event is running now. I.e. this event nests in a parent event with all its data. |
+  ***Parent event** This event recorded only if a high-level, or parent event is running now. I.e. this event nests in a parent event with all its data.
 {{ ::new_events_basic_tab.png?direct&800 |}}
@@ Line 48: / Line 48: @@
 {{ ::new_events_condition_tab.png?direct&800 |}}
-Of course, the event conditions sometimes  may be very complex, but with Lua scripts you can describe any imaginable
+Of course, the event conditions sometimes  may be very complex, but with Lua scripts you can describe any imaginable condition:
-condition:
 {{ ::new_events_lua_example.png?direct&800 |}}
@@ Line 68: / Line 67: @@
   ***Title** - The title field for the Setup menu. Possible to re-type here
-  ***Save to report checkbox** - If selected, it will be possible to set the E-registers in the form of **Ey.x**. See explanatoin below
+  ***Save to report checkbox** - If selected, it will be possible to set the E-registers in the form of **Ey.x**. See explanation below
   ***Report title** - It is the Report title when it's viewed or accessed from API, etc.
   ***Menu item name** It is how the 'Report' menu entry will look in the side bar menu
-  ***Save data** The registers values can be written __Once per Event__ or __Every X seconds__
+  ***Save data** The registers values (except for Event Start/End/Last update time selection) can be written __Once per Event__ or __Every X seconds__ . If you don't want to log some register's value for graphs all the time, but only inside a specific event, you may choose option of 'Every X seconds' and then a series of values will be recorded just in the event log data. Then an external application (or Level2 report builder) can use this data to biuld its own graph.
-  ***Register E1.0, 1.1, ... ** (see also [[webhmi_internal_registers | link]]). The E-registers are indexed from 0 and further in ascending order (x is an index), y is the event identifier that is assigned to it when it is created and is displayed in the event list. As a parameter of the E-register one of the 4 options are possible:
+== Selecting data to record in event log ==
+{{ ::e_register_selection_options.png?direct&600 |}}
+It is possible to pick up 4 options:
+    *//Start time// - event start time
+    *//End time// - event end time
+    *//Last update time// - the time of last record write time in the event ( this is a speical option for testing purposes)
+    *//Any register from Registers list// - and the third column of the report setting allows to select processing for the register - take minimal (Min), maximal value(Max), first value at the moment of event start (First Value) or the last upon the event end(Last Value), average value during the event time (Average Value).
+  ***Register E1.0, 1.1, ... ** (see also [[webhmi_internal_registers | link]]). The E-registers are indexed from 0 and further in ascending order (x is an index), y is the event identifier that is assigned to it when it is created and is displayed in the event list. Ey.x - it is address in the WebHMI internal register protocol, and also
+  *As a parameter of the E-register one of the 4 options are possible:
     *//Start time// - event start time
     *//End time// - event end time