Skip to Content

Changes for page 7. Events Setup

Last modified by Iaroslav Platonov on 2026/06/09 11:03
From version 13.2
edited by Lana
on 2025/12/11 00:37
Change comment: There is no comment for this version
To version 16.2
edited by Lana
on 2025/12/11 00:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -43,11 +43,35 @@
43 43  Search for events of interest by filtering [[image:Screenshot 2025-12-10 at 21.36.03.png||height="32" width="33"]] (the filter is located to the right of the table headings)
44 44  )))
45 45  1. (((
46 -Edit event configuration [[image:Screenshot 2025-12-10 at 21.36.56.png||height="25" width="98"]]
46 +Edit event configuration [[image:Screenshot 2025-12-10 at 21.36.56.png||height="22" width="86"]]
47 47  )))
48 +1. (((
49 +Adjust the setpoint text [[image:Screenshot 2025-12-10 at 21.37.32.png||height="23" width="122"]]
50 +)))
48 48  
49 -​​​​​​​
52 +== 2.2. Creating and editing an event in web-interface ==
50 50  
54 +
55 +An event can be created manually and automatically. Events are automatically created when the setpoint parameter is enabled. For a detailed description, refer to the "Setup Manual".
56 +
57 +The text of setpoints can be edited in the **Event editor** interface.
58 +
59 +To do this, click on the button [[image:Screenshot 2025-12-10 at 21.38.47.png||height="22" width="119"]]. After that, the **Setpoint editing** window opens (see Fig. 2.3), where the wording of the setpoints for Triggering and/or Return can be modified, such as Upper/Lower warning limit, Upper/Lower alarm limit, and Upper/Lower physical limit.
60 +
61 +One or more variables can be specified in the setpoint triggering message:
62 +
63 +* ~{~{.tag_name}} - tag name;
64 +* ~{~{.tag_code}} - tag code;
65 +* ~{~{.tag_id}} - tag ID;
66 +* ~{~{.tag_code_or_id}} - tag code, if the code is empty, then its ID;
67 +* ~{~{.tag_limit}} - setpoint value;
68 +* ~{~{.tag_unit}} - tag units;
69 +* ~{~{.device_name}} - name of the device to which the tag is linked.
70 +
71 +IMPORTANT: if {figure brackets} or dots are missing when writing these parameters, a validation error will occur.
72 +
73 +If a parameter with an error (non-existent parameter) is entered, for example: ~{~{.tag_name_2}}, the Operating journal will receive an event of the following type: [[image:1765431562370-764.png]]**< no value> > 10**.
74 +
51 51  
52 52  
53 53  
1765431562370-764.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +937 bytes
Content
Screenshot 2025-12-10 at 21.37.32.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +14.4 KB
Content
Screenshot 2025-12-10 at 21.38.47.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +14.3 KB
Content