Changes for page 1. User Manual

Last modified by Iaroslav Platonov on 2026/06/08 09:26

From version 140.3
edited by Lana
on 2025/11/12 23:36
Change comment: There is no comment for this version
To version 168.1
edited by Lana
on 2025/11/13 00:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,10 +2,64 @@
2 2  
3 3  ~1. System login
4 4  
5 -2.
5 +2. Main menu
6 6  
7 -2.1.
7 +2.1. Diagrams
8 8  
9 +2.2.1. Control
10 +
11 +2.3. Analysis
12 +
13 +2.3.1. Real-time data analysis
14 +
15 +2.3.1.1. Devices, objects
16 +
17 +2.3.1.2. Statuses
18 +
19 +2.3.1.3. Time
20 +
21 +2.3.2. Metering data analysis
22 +
23 +2.3.3. Receipt of metering data form
24 +
25 +2.3.4. Device diagnostic
26 +
27 +2.4. Logs
28 +
29 +2.4.1. Technology events
30 +
31 +2.4.2. Camcoders
32 +
33 +2.4.3. Power quality
34 +
35 +2.4.4. Waveforms
36 +
37 +2.4.5. Device events
38 +
39 +2.4.6. System events
40 +
41 +2.4.7. User comments log
42 +
43 +2.4.8. All events log
44 +
45 +2.4.9. Custom logs
46 +
47 +2.5. Reports
48 +
49 +2.5.1. Flexible reports
50 +
51 +2.5.2. Power quality reports
52 +
53 +2.5.3. Short circuit currents
54 +
55 +2.6. Operative journal
56 +
57 +2.7. Widgets
58 +
59 +2.8. Sound alerts
60 +
61 +2.9. Pop-up messages
62 +
9 9  ----
10 10  
11 11  == 1. SYSTEM LOGIN ==
... ... @@ -557,5 +557,129 @@
557 557  
558 558  ==== 2.3.3. Receipt of metering data form ====
559 559  
614 +When selecting the **Receipt of metering data **item from the **Analysis** menu, the **Analysis of the receipt of data **page opens (see Fig. 2.46).
560 560  
616 +[[image:Screenshot 2025-11-12 at 20.37.28.png]]
617 +
618 +Figure 2.46. Analysis of the receipt of data
619 +
620 +Analysis of the receipt of data is a table containing a list of available devices with their ID numbers and codes, as well as the number of time intervals for which the server has received data from the metering devices relative to the total number of intervals (see Fig. 2.47).
621 +
622 +The left panel displays a device tree like the one in the **Analysis of data metering** interface. Each object shows the number of received and expected intervals. If the numbers match, both are displayed in the same color. If any intervals are missing, the first number is highlighted in red. Devices or objects can be located either through the tree or by using the search bar.
623 +
624 +To the right of the search bar, there are two icons. The **Reset **icon [[image:Screenshot 2025-11-12 at 20.38.26.png||height="29" width="26"]] clears the previous search results and collapses the tree. The **Filter** icon [[image:Screenshot 2025-11-12 at 20.38.55.png||height="28" width="25"]] enables filtering by collected channels. When the **Data gaps** checkbox is selected, only those devices with missing data will remain visible in the tree. This functionality simplifies the process of identifying devices with missing data for subsequent re-polling.
625 +
626 +In the right section of the interface, data receipt profiles for each device are generated based on the received intervals.
627 +
628 +[[image:Screenshot 2025-11-12 at 20.39.44.png]]
629 +
630 +Figure 2.47. Pop-up tooltips on the data receipt chart
631 +
632 +The first column of the table contains either the device ID or code, which can be toggled between. Next, the device name (channels) is displayed.
633 +
634 +The third column shows the data availability profile. When hovering the mouse pointer over the upper breakpoints of the chart (see Fig. 2.44), a tooltip displays the time when the last interval before the gap was received (the first interval after the gap). The tooltip at the lower breakpoints shows the time of the first (or last) interval within the data receipt gap.
635 +
636 +The fourth column shows the ratio of received intervals to the number of expected intervals.
637 +
638 +Above the table, there are two buttons:** Interrogate** and **Refresh.**
639 +
640 +The **Interrogate **button sends a request to the polling service to retrieve the archive from the selected device for the specified interval. After pressing the button, a message appears on the screen indicating the number of devices being polled and the time interval. If a warning appears stating that the operation may take a long time (see Fig. 2.48), reduce the number of devices or shorten the polling depth.
641 +
642 +[[image:Screenshot 2025-11-12 at 20.40.26.png]]
643 +
644 +Figure 2.48. Message displayed when the number of devices or polling depth exceeds the limit
645 +
646 +The **Refresh** button [[image:Screenshot 2025-11-12 at 20.40.59.png||height="28" width="84"]] re-polls data from the database for the status.
647 +
648 +In addition to the **Refresh** and **Interrogate** buttons, a **Calculate** button may appear on the gray interface panel. This button appears when devices bound to calculated channels are selected in the tree. These calculated channels display similarly to regular ones, but their data is derived from other channels or tags. If a calculated channel is based on data from other channels, it can be recalculated using the **Calculate **button. This functionality is necessary when the source data or formula of such a channel has changed.
649 +
650 +At the very top of the interface on the gray panel, there is a calendar like the one in the **Analysis of data metering** section.
651 +
652 +The **Receipt of metering data** interface depends on the user’s configured access rights.
653 +
654 +==== 2.3.4. **Device diagnostic** ====
655 +
656 +If the user has the appropriate rights, device diagnostics is available in the **Analysis** menu by selecting the **Device diagnostic** from the drop-down list (see Fig. 2.49).
657 +
658 +[[image:Screenshot 2025-11-12 at 20.42.50.png]]
659 +
660 +Figure 2.49. Device diagnostics interface
661 +
662 +This interface is used to control the polling status of the devices on the object. The left part of the screen displays the device tree. Selecting the required object will display all its devices in the right field. Each object has a numerical description of the device status: Enabled devices (in green) / Disabled, with bad status (in red) / Disconnected devices (in gray).
663 +
664 +The user can use the button [[image:Screenshot 2025-11-12 at 20.44.09.png||height="32" width="30"]] to reset the selection and to minimize the tree.
665 +
666 +The diagnostic field displays devices highlighted in three colors: red if the device does not respond or responds with errors (bad status), green if the status is good, and gray if the device is disconnected in the CENTO software.
667 +
668 +When hovering the mouse pointer over a device, a pop-up window appears with all the device protocols and their statuses (see Fig. 2.50)
669 +
670 +[[image:Screenshot 2025-11-12 at 20.45.11.png]]
671 +
672 +Figure 2.50. Hovering the mouse pointer over a device
673 +
674 +Three control buttons are displayed in the top right corner of the screen.
675 +
676 +The **Settings** button [[image:Screenshot 2025-11-12 at 20.45.44.png||height="30" width="31"]] opens the window for customizing the diagnostics display (see Fig. 2.51). Here the user can change the width of the screen and the number of columns in which the device bars are placed.
677 +
678 +[[image:Screenshot 2025-11-12 at 20.46.14.png||height="183" width="278"]]
679 +
680 +Figure 2.51. Settings menu
681 +
682 +The **Filter** button [[image:Screenshot 2025-11-12 at 20.46.51.png||height="29" width="28"]] allows filtering the devices displayed in the scheme by status and type (Fig. 2.52).
683 +
684 +[[image:Screenshot 2025-11-12 at 20.47.19.png||height="203" width="280"]]
685 +
686 +Figure 2.52. Filters menu
687 +
688 +The **Scale** button [[image:Screenshot 2025-11-12 at 20.47.58.png||height="27" width="28"]] adjusts the scheme to the window size.
689 +
690 +2.4. Logs.
691 +
692 +This menu item contains a set of logs available depending on the license and access rights. The full list of standard logs includes Technology events, Camcoders, Waveforms, Power quality, Device events, System events, and All Events. Additionally, the user can add custom logs.
693 +
694 +Each log displays a list of events in a table indicating the date and time of each event, event description, associated object and device, as well as the event type and severity level (see Fig. 2.53)
695 +
696 +[[image:Screenshot 2025-11-12 at 20.59.56.png]]
697 +
698 +Figure 2.53. Logs
699 +
700 +Each event also receives a color code based on its importance level. The colors are configured by users with administrator rights through the event settings interface.
701 +
702 +The user can change the number of records displayed per page and filter data using the filters located in each column to the right of the header.
703 +
704 +Table columns marked with the icon [[image:Screenshot 2025-11-12 at 21.00.49.png||height="34" width="28"]] are sortable. Columns marked with the icon [[image:1763010073904-370.png]] support searching. Columns **Object** and** Device** include built-in configuration trees, the IM tree and the device tree, respectively.
705 +
706 +Switching between logs is performed using the buttons located to the left of the logs table.
707 +The log offers several settings:
708 +
709 +The **Calendar **[[image:Screenshot 2025-11-12 at 21.01.54.png||height="31" width="259"]] opens a menu to set the period for which data is requested.
710 +
711 +[[image:Screenshot 2025-11-12 at 21.02.39.png||height="47" width="174"]]
712 +
713 +- Exporting selected data to MS Excel.
714 +
715 +[[image:Screenshot 2025-11-12 at 21.03.15.png||height="46" width="125"]]
716 +
717 +- Button to add a custom log.
718 +
719 +[[image:Screenshot 2025-11-12 at 21.03.49.png]]
720 +
721 +- Buttons to edit and delete custom logs.
722 +
723 +[[image:Screenshot 2025-11-12 at 21.04.26.png||height="37" width="187"]]
724 +
725 +- Buttons to control data refresh on the browser page. By default, all logs are static (unlike the Operative events journal described later), loading only the information available at page opening. The drop-down list in the auto-refresh field allows receiving new events at a selected interval.
726 +
727 +[[image:Screenshot 2025-11-12 at 21.05.12.png||height="55" width="47"]]
728 +
729 +- Button to collapse the list of logs.
730 +
731 +[[image:Screenshot 2025-11-12 at 21.05.47.png||height="49" width="49"]]
732 +
733 +- Button to configure log display, available only to users with Administrator rights by default. This opens the settings window (see Fig. 2.54) to set the row height and the method of displaying device paths. The user can choose how many tree levels to show, starting from the device, or hide starting from the tree root.
734 +
735 +[[image:Screenshot 2025-11-12 at 21.06.42.png]]
736 +
737 +Figure 2.54. Log display settings
738 +
561 561  
1763008721439-679.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +918 bytes
Content
1763010073904-370.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +902 bytes
Content
Screenshot 2025-11-12 at 20.37.28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +105.7 KB
Content
Screenshot 2025-11-12 at 20.38.26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +2.0 KB
Content
Screenshot 2025-11-12 at 20.38.55.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +1.5 KB
Content
Screenshot 2025-11-12 at 20.39.44.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +80.9 KB
Content
Screenshot 2025-11-12 at 20.40.26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +61.9 KB
Content
Screenshot 2025-11-12 at 20.40.59.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +4.8 KB
Content
Screenshot 2025-11-12 at 20.42.50.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +360.2 KB
Content
Screenshot 2025-11-12 at 20.44.09.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +2.8 KB
Content
Screenshot 2025-11-12 at 20.45.11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +142.5 KB
Content
Screenshot 2025-11-12 at 20.45.44.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +3.2 KB
Content
Screenshot 2025-11-12 at 20.46.14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +29.7 KB
Content
Screenshot 2025-11-12 at 20.46.51.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +2.0 KB
Content
Screenshot 2025-11-12 at 20.47.19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +18.7 KB
Content
Screenshot 2025-11-12 at 20.47.58.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +2.0 KB
Content
Screenshot 2025-11-12 at 20.59.56.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +362.9 KB
Content
Screenshot 2025-11-12 at 21.00.49.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +1.9 KB
Content
Screenshot 2025-11-12 at 21.01.54.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +21.0 KB
Content
Screenshot 2025-11-12 at 21.02.39.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +7.1 KB
Content
Screenshot 2025-11-12 at 21.03.15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +5.7 KB
Content
Screenshot 2025-11-12 at 21.03.49.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +4.1 KB
Content
Screenshot 2025-11-12 at 21.04.26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +5.7 KB
Content
Screenshot 2025-11-12 at 21.05.12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +3.3 KB
Content
Screenshot 2025-11-12 at 21.05.47.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +3.1 KB
Content
Screenshot 2025-11-12 at 21.06.42.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +65.1 KB
Content