Skip to Content
Last modified by Iaroslav Platonov on 2026/06/08 10:32
From version 205.1
edited by Lana
on 2025/12/04 17:57
Change comment: There is no comment for this version
To version 161.1
edited by Lana
on 2025/12/04 17:21
Change comment: Uploaded new attachment "Screenshot 2025-12-04 at 14.21.36.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,5 @@
1 1  = CONTENT =
2 2  
3 -{{toc /}}
4 -
5 5  = 1. INTRODUCTION =
6 6  
7 7  CENTO is a multifunctional software platform for data collection, processing, and display.
... ... @@ -370,7 +370,7 @@
370 370  
371 371  Figure 4.15. Color replacement modal window
372 372  
373 -Fig. 4.15 shows the** Color replacement** modal window, which allows the diagram developer to change the current color of not only the rendered elements (In the diagram) but also the color set in active object rules (In the rules) and text color (In the text). Clicking** Replace** applies the changes to the entire diagram. To change the color of individual objects, use standard style editing, as shown in Fig. 4.3.
371 +Fig. 4.15 shows the** Color replacement** modal window, which allows the diagram developer to change the current color of not only the rendered elements (In the diagram) but also the color set in active object rules (In the rules) and text color (In the text). Clicking** Replace** applies the changes to the entire diagram. To change the color of individual objects, use standard style editing, as shown in Fig. 4.3.
374 374  
375 375  == 4.7. Setting up an animation frame for technological events associated with a diagram object ==
376 376  
... ... @@ -378,7 +378,7 @@
378 378  
379 379  Figure 4.16. Scheme settings modal window
380 380  
381 -For each created diagram, the flashing frame around the active object in diagram view mode can be customized depending on the incoming technological event. In the** Settings **window, under the **Animation frames,** the fields include:
379 +For each created diagram, the flashing frame around the active object in diagram view mode can be customized depending on the incoming technological event. In the** Settings **window, under the **Animation frames,** the fields include:
382 382  
383 383  * **The frame **is the color of the frame
384 384  * **Border, px** is the thickness of the frame
... ... @@ -409,7 +409,7 @@
409 409  
410 410  Figure 4.18. Edit data of chart modal window
411 411  
412 -The** Edit data of chart** modal window includes the following settings:
410 +The** Edit data of chart** modal window includes the following settings:
413 413  
414 414  * **Chart depth**
415 415  * **Round** is rounding up values with the number of decimal places.
... ... @@ -428,7 +428,7 @@
428 428  
429 429  Figure 4.19. Chart in the diagram viewer
430 430  
431 -Fig. 4.19 shows an example of a customized chart. This chart updates in real time and displays data from the last 5 minutes. Right-clicking on the chart opens the** Measurements** window, which provides information about the linked tag, its value, and more. Hovering the left mouse button over the chart calls the pop-up with the date, time, and value.
429 +Fig. 4.19 shows an example of a customized chart. This chart updates in real time and displays data from the last 5 minutes. Right-clicking on the chart opens the** Measurements** window, which provides information about the linked tag, its value, and more. Hovering the left mouse button over the chart calls the pop-up with the date, time, and value.
432 432  
433 433  === 4.8.2. Charts of tag values selected on the diagram ===
434 434  
... ... @@ -485,7 +485,7 @@
485 485  
486 486  * Draw a suitable object, a rectangle, for example
487 487  * Click on the **Setting up rules** icon [[image:Screenshot 2025-12-04 at 13.24.08.png||height="20" width="24"]]
488 -* In the window that opens (see Fig. 4.25), the** Condition** and **Action** fields need to be filled in for the rule. If highlighting areas based on specific conditions is not required, the **Condition **field can be left empty – in this case, the rendered object is to be displayed using the color specified in the **Action** field.
486 +* In the window that opens (see Fig. 4.25), the** Condition** and **Action** fields need to be filled in for the rule. If highlighting areas based on specific conditions is not required, the **Condition **field can be left empty – in this case, the rendered object is to be displayed using the color specified in the **Action** field.
489 489  
490 490  [[image:Screenshot 2025-12-04 at 13.24.38.png||height="202" width="691"]]
491 491  
... ... @@ -493,7 +493,7 @@
493 493  
494 494  Fig. 4.25 shows the setting of the fill depending on the values without conditions. The action to change the fill consists of the fill areas:
495 495  
496 -1. In step #1, select the** Style** tab.
494 +1. In step #1, select the** Style** tab.
497 497  1. In the suggested menu, select the option **Fill depending on the values.**
498 498  1. Select the tag/attribute name from the drop-down list.
499 499  1. If a tag is selected, its ID should be entered or selected from the drop-down list. If an IM attribute is selected, it also needs to be specified from the drop-down list of the class tree.
... ... @@ -521,8 +521,8 @@
521 521  * **Disable context menus, posters, and animations** disables the following:
522 522  
523 523  1. Disables the installation of posters for elements that are object attributes in the IM but have the same element ID bindings on the diagram. In Fig. 4.27, the dedicated switch is linked to ID 13939, the element TO is linked to the same ID, it is located in the measurements of the object (Activation of the TO). For posters to be exposed only to the switch, it is necessary for an IM element to enable **Disabling context menus, posters, and animations.**
524 -1. The// Disable context menus, posters, animations// attribute disables animation for such an element if the event is triggered not by changing it, but by changing another attribute included in this object, but if the triggered event relates to this attribute, then animation will work for it. In Fig. 4.27, the dedicated switch is linked to ID 13939, the element TO is linked to the same ID, it is located in the measurements of the object (Activation of the TO). If the **Disable context menus, posters, animations** field is disabled, the TO element will flash at any event related to the object with ID 13939. For the "TO" to flash only at an event that relates to this parameter, the TO element should turn it on.
525 -1. The //Disable context menus, posters, animations// attribute also disables all context menus that are available to the object, but only measurements remain. In Fig. 3.27, the dedicated switch is linked to ID 13939, the element TO is bound to the same ID, it is located in the measurements of the object (Activation of the TO). If an IM element does not include the// Disable context menus, posters, animations //attribute, then all context menus from the switch are to be available to it.
522 +1. The// Disable context menus, posters, animations// attribute disables animation for such an element if the event is triggered not by changing it, but by changing another attribute included in this object, but if the triggered event relates to this attribute, then animation will work for it. In Fig. 4.27, the dedicated switch is linked to ID 13939, the element TO is linked to the same ID, it is located in the measurements of the object (Activation of the TO). If the **Disable context menus, posters, animations** field is disabled, the TO element will flash at any event related to the object with ID 13939. For the "TO" to flash only at an event that relates to this parameter, the TO element should turn it on.
523 +1. The //Disable context menus, posters, animations// attribute also disables all context menus that are available to the object, but only measurements remain. In Fig. 3.27, the dedicated switch is linked to ID 13939, the element TO is bound to the same ID, it is located in the measurements of the object (Activation of the TO). If an IM element does not include the// Disable context menus, posters, animations //attribute, then all context menus from the switch are to be available to it.
526 526  
527 527  [[image:Screenshot 2025-12-04 at 13.27.06.png]]
528 528  
... ... @@ -590,7 +590,7 @@
590 590  
591 591  Figure 4.35. Viewing a diagram with manual input objects
592 592  
593 -Fig. 4.35 shows two examples with the manual input objects. To manage the values of the real-time parameters, right-click or left-click in the rendered areas. After clicking, an icon [[image:Screenshot 2025-12-04 at 13.34.21.png||height="27" width="26"]]appears on the right. When clicked, the value is entered manually, as well as an icon [[image:Screenshot 2025-12-04 at 13.34.45.png||height="30" width="33"]] for manual input before data is received. This manual input value is to be reset automatically after data is received. To reset the values entered manually, click on [[image:Screenshot 2025-12-04 at 13.35.12.png||height="28" width="27"]].
591 +Fig. 4.35 shows two examples with the manual input objects. To manage the values of the real-time parameters, right-click or left-click in the rendered areas. After clicking, an icon [[image:Screenshot 2025-12-04 at 13.34.21.png||height="27" width="26"]]appears on the right. When clicked, the value is entered manually, as well as an icon [[image:Screenshot 2025-12-04 at 13.34.45.png||height="30" width="33"]] for manual input before data is received. This manual input value is to be reset automatically after data is received. To reset the values entered manually, click on [[image:Screenshot 2025-12-04 at 13.35.12.png||height="28" width="27"]].​​​​​​​
594 594  
595 595  == 4.12. Input of fixed manual entry values ==
596 596  
... ... @@ -606,7 +606,7 @@
606 606  
607 607  Fig. 4.36 shows an example of manual input configuration for a tag with ID 9001, where:
608 608  
609 -* **Tag ID** specifies the identification number of the tag selected from a drop-down list [[image:Screenshot 2025-12-04 at 13.36.43.png||height="22" width="24"]] or entered manually.
607 +* **Tag ID** specifies the identification number of the tag selected from a drop-down list [[image:Screenshot 2025-12-04 at 13.36.43.png||height="22" width="24"]] or entered manually.​​​​​​​
610 610  * **Action** selects from a drop-down list: either manual input or cancellation of manual input.
611 611  * **Value** specifies the value to be assigned to the tag when the diagram button is pressed.
612 612  * **Before cancel** – if the state switch is enabled [[image:Screenshot 2025-12-04 at 13.37.25.png||height="25" width="40"]], the value persists until it is manually reset by the user. If the state switch is disabled [[image:Screenshot 2025-12-04 at 13.37.59.png||height="23" width="38"]], the manual input is automatically to be cleared after the next tag value change during the device polling.
... ... @@ -648,7 +648,7 @@
648 648  
649 649  **3) Links for navigation to Real-Time Data Analysis**
650 650  
651 -To navigate to **Metering data** or **Real-time dat**a open the object properties as described above. In the** Link or mnemonic scheme ID** field, click the button [[image:Screenshot 2025-12-04 at 13.41.24.png||height="21" width="33"]] and select **Real-time data** or **Analysis of data metering** from the drop-down list.
649 +To navigate to **Metering data** or **Real-time dat**a open the object properties as described above. In the** Link or mnemonic scheme ID** field, click the button [[image:Screenshot 2025-12-04 at 13.41.24.png||height="21" width="33"]] and select **Real-time data** or **Analysis of data metering** from the drop-down list.
652 652  
653 653  Fig. 4.40 shows an example of selecting tags from the real-time data section. The opened modal window displays the interface of this page with trees of devices, objects, statuses, and time on the left side. To create a link from the diagram, the appropriate tree and relevant tags should be selected, then the desired tab – **Real-time data, Chart**, or **Table** – should be specified on the right side, followed by clicking the button [[image:Screenshot 2025-12-04 at 13.41.45.png||height="19" width="30"]].
654 654  
... ... @@ -678,7 +678,7 @@
678 678  
679 679  Figure 4.43. Enabling portable grounding
680 680  
681 -If this option is enabled, then the grounding [[image:Screenshot 2025-12-04 at 13.45.01.png||height="24" width="24"]] button appears on the right side of the screen in the diagram viewing mode. Right-clicking on it opens a menu for setting the size and color of the portable grounding icon (see Fig. 4.44) to be applied to portable groundings on all diagrams including those previously installed.
679 +If this option is enabled, then the grounding [[image:Screenshot 2025-12-04 at 13.45.01.png||height="24" width="24"]] button appears on the right side of the screen in the diagram viewing mode. Right-clicking on it opens a menu for setting the size and color of the portable grounding icon (see Fig. 4.44) to be applied to portable groundings on all diagrams including those previously installed. ​​​​​​​
682 682  
683 683  [[image:Screenshot 2025-12-04 at 13.45.24.png]]
684 684  
... ... @@ -716,7 +716,7 @@
716 716  
717 717  Figure 4.49. Displaying a number in exponential form
718 718  
719 -== 4.17. Displaying delimited values ==
717 +== 4.17. Dis​​​​​​​​​​​​​​playing delimited values ==
720 720  
721 721  In the settings [[image:Screenshot 2025-12-04 at 13.50.03.png]] , in diagram view mode, instant tag values can be displayed as delimited values. This setting is enabled by default (see Fig. 4.50).
722 722  
... ... @@ -760,461 +760,8 @@
760 760  * **Polling frequency (s)** is the time interval for updating data in the table, in seconds.
761 761  * **Interval **is for selection of the data interval (applies to the entire table).
762 762  * **Function** is data aggregation applied to the entire table.
763 -* **ID** specifies the metering channel, which can be entered manually or selected from a drop-down list [[image:Screenshot 2025-12-04 at 14.07.38.png||height="26" width="27"]]
764 -* **Name **is the column name corresponding to the metering channel.
765 -* **Width **is the column width.
766 -* **Change time **is a system field used to display the time of the metering channel's value change.
761 +* **ID** specifies the metering channel, which can be entered manually or selected from a drop-down list [[image:Screenshot 2025-12-04 at 14.07.38.png]]
767 767  
768 -Rows in this table can be moved [[image:Screenshot 2025-12-04 at 14.08.30.png]], deleted [[image:Screenshot 2025-12-04 at 14.09.56.png||height="32" width="33"]], and added [[image:Screenshot 2025-12-04 at 14.10.25.png||height="31" width="89"]].
769 -
770 -[[image:Screenshot 2025-12-04 at 14.10.47.png]]
771 -
772 -Figure 4.55. Display of metering channel data
773 -
774 -Fig. 4.55 shows the table in the diagram viewer using the settings from Fig. 4.54. Line formatting for the data is applied according to the table header.
775 -
776 -== 4.19. Heatmaps ==
777 -
778 -Heatmap functionality is accessible only with an active license for the corresponding module.
779 -
780 -The graphic element templates contain the **Sensor** element (see Fig. 4.56), which is responsible for filling areas of the diagram depending on any tag values.
781 -
782 -[[image:Screenshot 2025-12-04 at 14.11.51.png||height="72" width="83"]]
783 -
784 -Figure 4.56. Sensor graphic element
785 -
786 -On the objects of the diagram, place such images and, in the window with the bindings of the rules [[image:Screenshot 2025-12-04 at 14.12.20.png||height="22" width="26"]]in the actions, specify the ID of the tag, which changes the color (for example, see Fig. 4.57).
787 -
788 -Images need to be placed on the diagram objects, and in the **Component visual settings** window [[image:Screenshot 2025-12-04 at 14.12.20.png||height="22" width="26"]], the tag ID should be specified in the actions, which triggers the color change upon tag value modification (see example in Fig. 4.57).
789 -
790 -[[image:Screenshot 2025-12-04 at 14.13.22.png]]
791 -
792 -Figure 4.57. Binding to the tag ID
793 -
794 -After arranging and binding such sensors, select those elements (might be selected together with other graphic objects), the area inside which changes colors according to changes in the linked tags in the rules. Then click **Create heatmap** (see Fig. 4.58).
795 -
796 -[[image:Screenshot 2025-12-04 at 14.13.52.png]]
797 -
798 -Figure 4.58. Create heatmap
799 -
800 -The created heatmap can be edited by right-clicking on the **Heatmap properties** (see Fig. 4.56). The modal window specifies the high and low limits, the normal value, the gamma (the range of colors for building a heatmap), the power parameter (the temperature for building transitions between temperatures), and the ability to display only those points that exceed the temperature in normal mode, see Fig. 4.60.
801 -
802 -[[image:Screenshot 2025-12-04 at 14.14.27.png]]
803 -
804 -Figure 4.59. Editing heatmap properties
805 -
806 -[[image:Screenshot 2025-12-04 at 14.14.52.png]]
807 -
808 -Figure 4.60. Heatmap
809 -
810 -== 4.20. Layers ==
811 -
812 -In editing mode, to optimize work with large diagrams, individual sections of the diagram can be placed in layers that do not affect operation in viewing mode.
813 -
814 -To switch to the layer mode, go to the View > Layers in the upper horizontal menu (Ctrl+Shift+L).
815 -
816 -[[image:Screenshot 2025-12-04 at 14.15.37.png]]
817 -
818 -Figure 4.61. Layers menu
819 -
820 -Fig. 4.61 shows an example of a list of layers where:
821 -
822 -1. Add layer is used to add a part of the diagram to the layer with the name.
823 -1. Duplicating the selected layer in the list.
824 -1. It is used to move diagram elements from one layer to another.
825 -1. The layer removal button.
826 -1. To disable or enable the parts of the diagram included in a specific layer. Moreover, disabling the layer does not affect the display in viewing mode, but only speeds up editing.
827 -1. Blocking changes to a layer from the list.
828 -1. Foreground/background of the layer.
829 -
830 -== 4.21. Active ​​​​​​​SVG elements ==
831 -
832 -The diagram editor allows importing graphic element templates in SVG format from various sources. Developed animated images from external sources help optimize work in both view and edit modes of the diagram (see Section 4.22.1). They also enable monitoring technological processes with the ability to view moving and rotating objects on the diagram (see Section 4.22.2).
833 -
834 -=== 4.21.1. Active SVG elements to speed up the opening and editing of the diagram ===
835 -
836 -In editing mode, to optimize work with large diagrams, active elements in SVG format can be loaded. Such elements are created by software developers. The approach is in using a ready-made template for the active element specifying in the rules only the tag/attribute that is responsible for a particular action. Any graphic elements can be modified using a program that supports the SVG format, or directly by editing the file’s code.
837 -
838 -The loading of items is in the **Extras** menu item (see Fig. 4.62).
839 -
840 -[[image:Screenshot 2025-12-04 at 14.17.19.png]]
841 -
842 -Figure 4.62. Import animated SVGs
843 -
844 -Ready-made templates should be uploaded to the **Import animated SVG**s menu (see Fig. 4.63).
845 -
846 -[[image:Screenshot 2025-12-04 at 14.17.47.png]]
847 -
848 -Figure 4.63. Import animated SVGs
849 -
850 -The template uploaded in Fig. 4.64 replaces drawing of many graphic elements created in the diagram editor.
851 -
852 -[[image:Screenshot 2025-12-04 at 14.18.12.png]]
853 -
854 -Figure 4.64. Animated SVG
855 -
856 -For example, it is necessary to display the status of a discrete signal (switch position), as shown in Fig. 4.65. In case of developing diagrams in the editor, it is necessary to draw all the sticks and text forms separately (see Fig. 4.66) and describe each state in the rules.
857 -
858 -[[image:Screenshot 2025-12-04 at 14.18.44.png]]
859 -
860 -Figure 4.65. Legend for the position of the switch
861 -
862 -[[image:Screenshot 2025-12-04 at 14.19.10.png]]
863 -
864 -Figure 4.66. Graphic elements
865 -
866 -In case of using an .svg file, these states are written inside the code and after importing them into the editor, the user cannot visually track them in any way. After importing the file, configure the rules in the actions of which the **Status** field appears (see Fig. 4.67) with the selection of a specific state, depending on the conditions described in the rule.
867 -
868 -[[image:Screenshot 2025-12-04 at 14.19.47.png]]
869 -
870 -Figure 4.67. Rules for animated SVG
871 -
872 -The code of the animated element is shown below:
873 -
874 874  ----
875 875  
876 -<svg xmlns="http:~/~/www.w3.org/2000/svg" viewBox="0 0 80 80" width="80" height="80"
877 -
878 -data-states='{"On":{"~-~-background":"#d50404","~-~-border":"var(~-~-main)"},
879 -
880 -"Off":{"~-~-background":"#0f0","~-~-border":"var(~-~-main)"},
881 -
882 -"Error/Intermediate":{"~-~-background":"#fff","~-~-border":"var(~-~-main)"},
883 -
884 -"WE are exhausted":{"~-~-background":"#00f","~-~-border":"var(~-~-main)"},
885 -
886 -"n/a":{"~-~-background":"transparent","~-~-border":"#000"}}'>
887 -
888 -<rect style="fill:var(~-~-background,transparent);stroke:var(~-~-border,var(~-~-main,#000));stroke-width:6;" height="80" width="80" />
889 -
890 -</svg>
891 -
892 -----
893 -
894 -=== 4.21.2. Animated SVG ===
895 -
896 -If proficiency in CSS or SVG code is available, an animated SVG template can be independently developed based on the example provided in Section 4.21.1, along with the application of various animations for technological processes.
897 -
898 -Fig. 4.68 shows an example of graphic elements with various animated styles configured through an SVG file. This animation is imported into the menu, as shown in Fig. 4.62, and in the mnemonic diagram editor, it appears as an image where only the size can be adjusted; all other edits are made within the template from the external source (such as Inkscape, Figma, etc.).
899 -
900 -[[image:Screenshot 2025-12-04 at 14.21.36.png]]
901 -
902 -Figure 4.68. Animated Image
903 -
904 -Each element created, for example, Inkscape has a group, and each group has its own animation settings.
905 -
906 -For example, in Fig. 4.68, a grouped element is rendered, which needs to be moved up or down. The animation code for it would look as follows:
907 -
908 -----
909 -
910 -<animateTransform
911 -
912 - attributeName="transform"
913 -
914 - attributeType="XML"        
915 -
916 - type="rotate"
917 -
918 - values="360 85 83; 310 85 83; 360 85 83"
919 -
920 -keySplines="1 .9 .1 0 ; 0 .1 .9 1"
921 -
922 - dur="4s"
923 -
924 - repeatCount="indefinite" />
925 -
926 -----
927 -
928 -If the object needs to rotate around an axis (see Fig. 4.68), the example code for rotating counterclockwise would look like this:
929 -
930 -----
931 -
932 -<animateTransform
933 -
934 - attributeName="transform"
935 -
936 - attributeType="XML"
937 -
938 - type="rotate"
939 -
940 -values="0 117.36 311.98; 360 117.36 311.98"
941 -
942 -begin = "-3.1s"
943 -
944 - dur="4s"
945 -
946 - repeatCount="indefinite" />
947 -
948 -----
949 -
950 -For clockwise rotation, the example code would look like this:
951 -
952 -----
953 -
954 -<animateTransform
955 -
956 - attributeName="transform"
957 -
958 - attributeType="XML"
959 -
960 -
961 - type="rotate"
962 -
963 - from="0 112.36 251.98"
964 -
965 - to="360 112.36 251.98"
966 -
967 - dur="3s"
968 -
969 - repeatCount="indefinite" />
970 -
971 -----
972 -
973 -The coordinates values/from/to depend on the initial position of the graphic element. The smaller the time value (dur), the more frequently the graphic element moves.
974 -
975 -Thus, by knowing the SVG and CSS code, any animations can be imported into the diagram editor.
976 -
977 -== 4.22. Conversion of diagrams from version 2 of the editor to version ​​​​​​​3 ==
978 -
979 -For compatibility of the version 3 of the editor with the version 2, diagrams should be converted. To do this, type Alt+Shift+D on the keyboard. A version selection appears in the horizontal menu to the right of the **Open in viewer** button [[image:Screenshot 2025-12-04 at 14.24.51.png||height="24" width="29"]]. From the drop-down list, click version 3. After clicking, a message pops up in the upper-right corner, which warns about switching to the editor version 3 after clicking **Unsaved changes. Click here to save** see Fig. 4.69.
980 -
981 -[[image:Screenshot 2025-12-04 at 14.25.20.png]]
982 -
983 -Figure 4.69. Warning about switching to the editor version 3
984 -
985 -After saving, the system switches to the version 3 editor, and the page URL changes to /CENTO/web/ui/diagram_editor/. Next, press the Alt+Shift+D keyboard combination to hide the version selection menu. After converting, select the entire diagram and click on any of the selected objects. In the context menu, click on** Convert styles** and on one of the items **Convert active elements with stroke** or **Convert active elements without stroke,** depending on the features of the rendered objects. The selection of the item can be verified using the diagram viewer. Without closing a converted diagram, click **Unsaved change. Click here to save,** and then open the same diagram on another page in the viewer, all elements should look the same as on the original diagram in the editor version 2, if this is not the case, then on the page with the diagram where the conversion was performed, undo the last actions and select another item and check again in the viewer.
986 -
987 -If the diagram is closed with the wrong conversion option, it cannot be reverted. Restoring requires a copy of the diagram from the editor version 2.
988 -
989 -== 4.23. Display of the IM object name and the tag measurement units ==
990 -
991 -[[image:Screenshot 2025-12-04 at 14.26.29.png]]
992 -
993 -Figure 4.70. Options for displaying tag data
994 -
995 -Diagrams allow displaying not only the tag value but also its value along with the units of measurement, the units of measurement without the tag value, the name of the IM object, and the IM object code.
996 -
997 -To configure this, in the **Component visual settings** window, by clicking on the upper horizontal menu [[image:Screenshot 2025-12-04 at 14.26.56.png||height="26" width="27"]], actions are selected on the** Text** tab, specifically **IM measurement** (see Fig. 4.71) or **IM object** (see Fig. 4.72).
998 -
999 -[[image:Screenshot 2025-12-04 at 14.27.28.png]]
1000 -
1001 -Figure 4.71. IM measurement
1002 -
1003 -[[image:Screenshot 2025-12-04 at 14.27.52.png]]
1004 -
1005 -Figure 4.72. IM object
1006 -
1007 -To display tag values, tag values with units of measurement, or units of measurement only, select **IM Measurement** in **Actions** and choose the IM class attribute from the drop-down list [[image:Screenshot 2025-12-04 at 14.28.24.png||height="25" width="26"]].
1008 -
1009 -Examples of such value displays are shown in Fig. 4.70, numbers 1, 2, and 3.
1010 -
1011 -To display the name of the IM object and its code, select **IM Object** in **Actions** and choose the appropriate menu from the drop-down list. Examples of such value displays are shown in Fig. 4.70 under numbers 4, 5, and 6.
1012 -
1013 -To display the name of the object trimmings unnecessary characters, use the formula in **Actions:**
1014 -
1015 -[[image:Screenshot 2025-12-04 at 14.30.16.png]]
1016 -
1017 -Figure 4.73. IM object name with split characters
1018 -
1019 -Fig. 4.73 shows an example of configuring the display of the IM object name with split characters using the formula split(val, " ", 1), where the value is split by the delimiter space, thus removing the first word from the phrase. An example of this display is shown in Fig. 4.70 under number 5. This formula can also be used to display part of the IM object code.
1020 -
1021 -Since the rules reference the attributes of the IM (industrial object), in all the examples above, create an active object by right-clicking (1) and bind it in the IM tree [[image:Screenshot 2025-12-04 at 14.31.14.png||height="29" width="30"]] (2) to an object (3), as shown in Fig. 4.74. The data for the bound object is to be displayed in view mode as shown in Fig. 4.70.​​​​​​​
1022 -
1023 -[[image:Screenshot 2025-12-04 at 14.31.50.png]]
1024 -
1025 -Figure 4.74. Creating and binding to an IM object
1026 -
1027 -== 4.24. Uploading/downloading diagrams ==
1028 -
1029 -Uploading and downloading diagrams are available on the **Mnemonic diagrams** page, in the Actions column.
1030 -
1031 -[[image:Screenshot 2025-12-04 at 14.32.48.png]]
1032 -
1033 -Figure 4.75. Mnemonic diagrams page
1034 -
1035 -The button [[image:Screenshot 2025-12-04 at 14.33.20.png||height="25" width="26"]] uploads the diagram in an archive depending on the diagram version. If the diagram was in the version 2 of the editor, it is to be uploaded in the same version.
1036 -
1037 -The button [[image:Screenshot 2025-12-04 at 14.33.51.png||height="27" width="28"]] downloads the diagram in an archive depending on the diagram version. If the diagram was in version 3 of the editor, it is to be uploaded in the same version.
1038 -
1039 -The **Download** button allows downloading all the diagrams to one archive.
1040 -
1041 -The **Upload** button allows uploading all the diagrams from one previously downloaded archive. This allows diagrams to migrate from one server to another.
1042 -
1043 -= 5. Binding tags to the diagram using ID or code =
1044 -
1045 -**Example No. 1**
1046 -
1047 -An example of binding a real parameter taken from a database that outputs information as a numeric value on a diagram.
1048 -
1049 -Select the text on the diagram, which is to be a dynamic parameter, and open the window [[image:Screenshot 2025-12-04 at 14.39.54.png||height="28" width="29"]]. 
1050 -
1051 -In the rule, check the box next to the words** Without conditions** (1) (optional) and describe the first action. Mark the** Text** field, select the **Tag** parameter type (2) and write, for example, the ID=502001 (3) number from the database (or select it from the drop-down list (4) see Fig. 5.2), if it is necessary to round the values, enable rounding (5) and specify how many decimal places should be displayed. It is possible to format the text in the actions of the rules (6) (see Fig. 5.3), as well as output the value of the number in exponential form (7). Click **Save,** switch to the diagram [[image:Screenshot 2025-12-04 at 14.40.43.png||height="24" width="31"]]viewing mode and see the result (see Fig. 5.4).
1052 -
1053 -[[image:Screenshot 2025-12-04 at 14.41.18.png]]
1054 -
1055 -Figure 5.1. Binding to the text
1056 -
1057 -To quickly bind to a tag, the **Component visual settings** window can be skipped by using the **Bind an element to a tag or channel** tree [[image:Screenshot 2025-12-04 at 14.41.48.png||height="25" width="25"]]. This automatically fills the tag, see Fig. 5.1.
1058 -
1059 -[[image:Screenshot 2025-12-04 at 14.42.21.png]]
1060 -
1061 -Figure 5.2. Choose the parameter drop-down list
1062 -
1063 -[[image:Screenshot 2025-12-04 at 14.42.51.png]]
1064 -
1065 -Figure 5.3. Formatting the text in the rules
1066 -
1067 -[[image:Screenshot 2025-12-04 at 14.43.17.png]]
1068 -
1069 -Figure 5.4. Tag value in the view mode
1070 -
1071 -The tag settings include a field not only for the ID number but also for specifying a code that can be used when binding to the diagram. To do this, in Fig. 5.1, field No. 3, enter the tag code instead of its ID.
1072 -
1073 -In the viewing mode in Fig. 5.4 there is no difference in the display in this case.
1074 -
1075 -**Example No. 2**
1076 -
1077 -An example of binding a real parameter taken from a database, which outputs information on a diagram in the form of a dynamic element that changes color depending on the incoming value and the status of the parameter.
1078 -
1079 -CENTO receives various tag statuses:
1080 -
1081 -[[image:Screenshot 2025-12-04 at 14.44.04.png||height="421" width="343"]]
1082 -
1083 -Figure 5.5. Tag statuses
1084 -
1085 -For example, two statuses can be used: when the telemeasurment TI value is received in real time (i.e., 1 – Normal), and when the telemeasurment TI value is entered manually by the user (i.e., 4 – Manual input).
1086 -
1087 -Real parameter data for binding:
1088 -
1089 -|**ID number**|**Parameter name**|**Values**|**Decryption**
1090 -|10154|Emergency alarm (EA)|0/1|(((
1091 -normal/
1092 -
1093 -trigerring
1094 -)))
1095 -
1096 -Create a rectangle (with or without fill) and write the text //AC// inside the stroke.
1097 -
1098 -This element changes the background color depending on the incoming value and the status of the parameter, if the condition TI=0 is met, then the color is green, if the condition TI=1 is met, then the color is red, if there is no data, then the color is white (see Fig. 5.6).
1099 -
1100 -[[image:Screenshot 2025-12-04 at 14.45.25.png]]
1101 -
1102 -Figure 5.6. Color changing in a dynamic element
1103 -
1104 -To do this, select the created rectangle with left-clicking and open the bindings window [[image:Screenshot 2025-12-04 at 14.45.55.png||height="25" width="28"]]
1105 -
1106 -Create the following rules:
1107 -
1108 -Rule No. 1 (fill in green with the value of TI = 0):
1109 -
1110 -If the TI value is 0 (normal), then the background is green (see Fig. 5.7).
1111 -
1112 -Rule No. 2 (fill in red with the value of TI = 1):
1113 -
1114 -If the TI value is 1 (signal available, then the background is red (see Fig. 5.8).
1115 -
1116 -Rule No. 3 (fill in white when the T is not equal to 0 and not equal to 1):
1117 -
1118 -If the TI value is not equal to 0 and at the same time the TI value is not equal to 1, then the background is white (see Fig. 5.9).
1119 -
1120 -Rule No. 4 (fill in white if the status is not normal and not with manual input):
1121 -
1122 -If the TI status is not equal to 1 (normal) and at the same time the TI status is not equal to 4 (not manual input), then the background is white (see Fig. 5.10).
1123 -
1124 -[[image:Screenshot 2025-12-04 at 14.46.37.png]]
1125 -
1126 -Figure 5.7. Rule No. 1
1127 -
1128 -[[image:Screenshot 2025-12-04 at 14.46.57.png]]
1129 -
1130 -Figure 5.8. Rule No. 2
1131 -
1132 -[[image:Screenshot 2025-12-04 at 14.47.27.png]]
1133 -
1134 -Figure 5.9. Rule No. 3
1135 -
1136 -[[image:Screenshot 2025-12-04 at 14.47.57.png]]
1137 -
1138 -Figure 5.10. Rule No. 4
1139 -
1140 -== 5.2. Binding devices to the diagram ==
1141 -
1142 -There are several device status values:
1143 -
1144 -0 – Disabled,
1145 -
1146 -1 – Normal,
1147 -
1148 -2 – Device has data errors,
1149 -
1150 -3 – Device is unavailable,
1151 -
1152 -4 – Data with manual input available,
1153 -
1154 -7 – Waiting for data,
1155 -
1156 -9 – Status is missing.
1157 -
1158 - The device is bound to the diagram by selecting **Device status** from the menu item. The content of the rules is similar to the example described above with changing the color of an object (in the** Condition** field, select the desired type of parameter, specify the device address, specify the operator and enter a numeric value equal to one or another status, and then specify the **Action **to be applied to the condition being fulfilled, for example, see Fig. 5.11).
1159 -
1160 -[[image:Screenshot 2025-12-04 at 14.49.03.png]]
1161 -
1162 -Figure 5.11. Binding to the device status
1163 -
1164 -Additionally, when using a template with a set of rules, device binding can be performed through the device tree by clicking on [[image:Screenshot 2025-12-04 at 14.49.33.png||height="24" width="25"]]. This automatically fills in the device ID fields shown in Fig. 5.11 streamlining the debugging process without opening the rules window.
1165 -
1166 -== 5.3. Binding parameters to information model objects ==
1167 -
1168 -To create an information model, see the "Information model setup manual".
1169 -
1170 -For example, create a square element (to serve as a switch) and describe the rules for it. In this example, the square changes the background color depending on the incoming parameter of the information model object, which refers to the value from the CENTO database.
1171 -
1172 -The sequence of bindings to the parameters of an information model object is like the actions for binding to tags: instead of **Tag value** and **Tag status,** select the** IM attribute** and **IM parameter status**, see Fig. 5.12.
1173 -
1174 -[[image:Screenshot 2025-12-04 at 14.50.40.png]]
1175 -
1176 -Figure 5.12. Binding to the parameter of the information model object
1177 -
1178 -In this example, the address of the parameter is the information model class, and its attribute is selected when opening the drop-down list [[image:Screenshot 2025-12-04 at 14.51.19.png||height="35" width="28"]], see Fig. 5.13.
1179 -
1180 -[[image:Screenshot 2025-12-04 at 14.51.50.png]]
1181 -
1182 -Figure 5.13. Window with IM classes and their attributes
1183 -
1184 -After assembling the shape with the necessary rules for dynamic display, select the entire group and click the left mouse button. In the drop-down window, select **Create active element**, see Fig. 5.14. This function also applies to individual graphic drawings. To bind to the information model, open the appropriate bindings menu [[image:Screenshot 2025-12-04 at 14.52.28.png||height="31" width="31"]].
1185 -
1186 -[[image:Screenshot 2025-12-04 at 14.52.56.png]]
1187 -
1188 -Figure 5.14. Creating an active element
1189 -
1190 -After creating the active element, the settings shown in Fig. 5.15 become the default. To set properties, right-click on the active element and select **Edit data of element** from the menu.
1191 -
1192 -[[image:Screenshot 2025-12-04 at 14.53.33.png]]
1193 -
1194 -Figure 5.15. Edit the data of elements
1195 -
1196 -After setting up the properties, select the shape and click the button [[image:Screenshot 2025-12-04 at 14.54.04.png||height="27" width="26"]]. Find the necessary element in the tree and select it (see Fig. 5.16).
1197 -
1198 -[[image:Screenshot 2025-12-04 at 14.54.49.png]]
1199 -
1200 -Figure 5.16. Information model element binding
1201 -
1202 -In this way, it is bound to the elements of the information model. When switching from the editor to the diagram viewing mode and right-clicking on the created shape, the **Measurements** context menu appears, showing the complete set of parameters described in the information model, as shown in Fig. 3.3.
1203 -
1204 -Right-clicking displays a table of parameters, which includes all the parameters from measurements, with the option to configure short tag names and decode values, as shown in Fig. 5.17.
1205 -
1206 -[[image:Screenshot 2025-12-04 at 14.55.22.png]]
1207 -
1208 -Figure 5.17. Table of the IM element parameters
1209 -
1210 -This object also has the option to display posters, with their arrangement appearing as shown in Fig. 5.18.
1211 -
1212 -[[image:Screenshot 2025-12-04 at 14.55.48.png]]
1213 -
1214 -Figure 5.18. Installation of customized posters
1215 -
1216 -= ABBREVIATIONS =
1217 -
1218 -DB – the database
1219 -
1220 -IM – information model.
765 +
Screenshot 2025-12-04 at 14.24.51.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -2.7 KB
Content
Screenshot 2025-12-04 at 14.25.20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -26.2 KB
Content
Screenshot 2025-12-04 at 14.26.29.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -92.8 KB
Content
Screenshot 2025-12-04 at 14.26.56.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -2.4 KB
Content
Screenshot 2025-12-04 at 14.27.28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -92.5 KB
Content
Screenshot 2025-12-04 at 14.27.52.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -86.8 KB
Content
Screenshot 2025-12-04 at 14.28.24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -1.9 KB
Content
Screenshot 2025-12-04 at 14.30.16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -68.5 KB
Content
Screenshot 2025-12-04 at 14.30.57.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -2.1 KB
Content
Screenshot 2025-12-04 at 14.31.14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -2.1 KB
Content
Screenshot 2025-12-04 at 14.31.50.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -267.4 KB
Content
Screenshot 2025-12-04 at 14.32.48.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -85.2 KB
Content
Screenshot 2025-12-04 at 14.33.20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -1.8 KB
Content
Screenshot 2025-12-04 at 14.33.51.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -1.8 KB
Content
Screenshot 2025-12-04 at 14.39.54.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -3.1 KB
Content
Screenshot 2025-12-04 at 14.40.43.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -2.6 KB
Content
Screenshot 2025-12-04 at 14.41.18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -146.5 KB
Content
Screenshot 2025-12-04 at 14.41.48.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
Screenshot 2025-12-04 at 14.42.21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -108.6 KB
Content
Screenshot 2025-12-04 at 14.42.51.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -37.3 KB
Content
Screenshot 2025-12-04 at 14.43.17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -47.7 KB
Content
Screenshot 2025-12-04 at 14.44.04.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -86.7 KB
Content
Screenshot 2025-12-04 at 14.45.25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -171.4 KB
Content
Screenshot 2025-12-04 at 14.45.55.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
Screenshot 2025-12-04 at 14.46.37.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -44.3 KB
Content
Screenshot 2025-12-04 at 14.46.57.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -45.3 KB
Content
Screenshot 2025-12-04 at 14.47.27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -58.1 KB
Content
Screenshot 2025-12-04 at 14.47.57.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
Screenshot 2025-12-04 at 14.49.03.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -45.0 KB
Content
Screenshot 2025-12-04 at 14.49.33.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -2.3 KB
Content
Screenshot 2025-12-04 at 14.50.40.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -174.1 KB
Content
Screenshot 2025-12-04 at 14.51.19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -1.8 KB
Content
Screenshot 2025-12-04 at 14.51.50.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -60.5 KB
Content
Screenshot 2025-12-04 at 14.52.28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -2.9 KB
Content
Screenshot 2025-12-04 at 14.52.56.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -180.8 KB
Content
Screenshot 2025-12-04 at 14.53.33.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -68.6 KB
Content
Screenshot 2025-12-04 at 14.54.04.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -1.8 KB
Content
Screenshot 2025-12-04 at 14.54.49.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -330.4 KB
Content
Screenshot 2025-12-04 at 14.55.22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -83.5 KB
Content
Screenshot 2025-12-04 at 14.55.48.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -69.7 KB
Content