WYSIWYG user-defined test data monitoring software interface configuration system

Abstract

The invention relates to a WYSIWYG (what you see is what you get) user-defined test data monitoring software interface configuration system, which belongs to the field of monitoring software system design, and comprises a control operation interface used for a user to operate a user-defined monitoring software interface through a graphical interface in the whole test process; the display configuration module is used for analyzing graphical interface operation of a user and generating a monitoring software interface configuration file, the monitoring software interface configuration file is used for storing configuration information, and the configuration information comprises monitoring software interface content, layout and control attribute parameters; the content of the monitoring software interface comprises the types and the number of controls on the monitoring software interface; each control attribute parameter comprises a control shape, a size, position information and a binding parameter; the binding parameter is used for associating the control with the parameter data; the data display module dynamically loads the configuration information to form and display a monitoring software interface, and updates the monitoring software interface in real time according to the configuration information; and the data receiving module is used for receiving test data generated in the test process, storing the test data in a data pool, obtaining theme data subscribed by a user from the data pool, analyzing the theme data to obtain binding parameter data of each control, and transmitting the binding parameter data to a monitoring software interface for display.

Description

Technical Field

[0001] This invention relates to the field of data monitoring software system design in ground tests of aerospace systems, and particularly to a WYSIWYG user-defined test data monitoring software interface configuration system. Background Technology

[0002] In recent years, the number of aerospace system test missions has been increasing. These missions require monitoring the status parameters of various devices, and the accuracy and intuitiveness of the test data are directly related to the success or failure of the mission. Therefore, data monitoring software interfaces need to display a large amount of parameter information from different data sources in real time. Depending on the monitoring needs of different stages of the test, the interface content and layout often require extensive modifications. To address the issue of frequent iterations of data monitoring software interface requirements, the traditional approach is to extract the software monitoring interface into a configuration file to allow customization of the software interface without recompiling. However, during the test, it is difficult for different disciplines to fully communicate their specific requirements at once, leading to repeated modifications and iterations when editing the configuration file. This places high demands on the technical status control capabilities of the software development team and increases the workload of software configuration management. Summary of the Invention

[0003] The technical problem solved by this invention is to overcome the shortcomings of the prior art and provide a WYSIWYG user-defined test data monitoring software interface configuration system, which is suitable for the development of data monitoring software in ground tests of aerospace systems. It solves the technical risks brought to software development by the rapid update and iteration of the display requirements of data monitoring software interface, and reduces the workload of software configuration management.

[0004] The solution of the present invention is: a WYSIWYG user-defined experimental data monitoring software interface configuration system, which includes a control operation interface, a display configuration module, a data display module, and a data receiving module;

[0005] The control operation interface is used by users to operate the customized monitoring software interface through a graphical interface throughout the entire experiment.

[0006] The display configuration module parses the user's graphical interface operations and generates a monitoring software interface configuration file. The monitoring software interface configuration file is used to store configuration information, including the monitoring software interface content, layout, and attribute parameters of each control. The monitoring software interface content includes the types and quantities of controls on the monitoring software interface. The attribute parameters of each control include the control's shape, size, position information, and binding parameters. The binding parameters are parameter data identifiers associated with the control.

[0007] The data display module dynamically loads configuration information to form and display the monitoring software interface, and updates the monitoring software interface in real time based on the configuration information.

[0008] The data receiving module receives the experimental data generated during the experiment and stores it in the data pool. It retrieves the topic data subscribed to by the user from the data pool, parses the parameter data bound to each control, and transmits it to the monitoring software interface for display.

[0009] Preferably, the custom monitoring software interface includes adding controls to the monitoring software interface, batch generating controls, customizing control combinations, adjusting the layout of controls, and setting the attribute parameters of controls. Users can adjust the custom monitoring software interface and preview it in real time during the experiment through graphical operation, which is WYSIWYG.

[0010] Preferably, the monitoring software interface configuration file is a formal description language XML configuration file.

[0011] Preferably, the monitoring software interface configuration file describes the configuration items in the form of XML nodes, and the configuration items include version information, basic control information, control attributes, and layout;

[0012] Version information is used to configure version, author, and date;

[0013] Basic control information is used to configure the control name and type;

[0014] Control properties are used to configure the property values ​​of the control. Common properties include type, bound parameter information, duration, and refresh cycle. Bound parameter information includes parameter name, parameter code or parameter table number, encoding method, parameter type, parameter symbol, and system. Custom properties are defined according to the function of the control, such as the lighting condition property of an indicator light control.

[0015] Control layout is used to configure the layout of all controls on the monitoring software interface, including the layout method and the row number, column number, number of rows spanned, and number of columns spanned for each control.

[0016] Preferably, the control operation interface includes:

[0017] The main interface of the software is an editable area, which allows users to directly adjust the number and layout of controls by dragging and dropping within the editable area.

[0018] A dialog box for modifying the layout of a control within its parent control. This allows you to adjust the layout of child controls, including horizontal, vertical, or grid layouts.

[0019] A dialog box for modifying control properties, used to set properties for individual or batch controls;

[0020] The dialog box for batch control creation is used to add controls in batches to the monitoring software interface. It automatically generates multiple controls arranged in sequence according to the size of the monitoring software interface.

[0021] Preferably, the control operation interface further includes an XML editing dialog box, which allows users to directly edit the monitoring software interface configuration file.

[0022] Preferably, the control types include curves, group boxes, labels, LCDs, indicator lights, tables, tabs, blank containers, and open interfaces. Each control is equipped with a dynamic link library encapsulated into a unified interface. The display configuration module is based on the Qt signal and slot mechanism. The platform slot function responds in real time to the user's operation trigger signal to update the control properties on the monitoring software interface, calls the dynamic link library of the interface control, and realizes the configuration of the control.

[0023] Preferably, the data center includes a data distribution module SigMgr and a data parsing module.

[0024] ProcTopicWorker, parameter management module TableNoCodeMgr;

[0025] The data distribution module SigMgr establishes and maintains data configuration files, which include user-subscribed data topics, the IP address and port number of each data topic, to manage all data signals and subscription relationships. Based on the data configuration files, it retrieves the relevant topic data that the user has subscribed to from the bus data pool and publishes it to the corresponding data parsing module ProcTopicWorker.

[0026] The data parsing module ProcTopicWorker corresponds one-to-one with the data topic. According to the preset format of the data topic, it parses the heterogeneous data in the data topic and converts it into a recognizable parameter format. The parsed parameter information is stored in the cache area for the parameter management module TableNoCodeMgr to query and use.

[0027] The parameter management module TableNoCodeMgr is used to record the calling relationship between parameters and controls, check whether there is any parameter data update in the buffer, obtain the updated parameter data, notify the control that calls the parameter or have the control query and obtain the updated parameter data, and update the monitoring software interface.

[0028] Preferably, the parameter management module TableNoCodeMgr adopts a singleton pattern to manage parameter data, and multiple controls bound to the same parameter do not need to instantiate a new parameter object, thereby improving data distribution performance.

[0029] Preferably, the above-mentioned WYSIWYG user-defined experimental data monitoring software interface configuration system further includes a user management module. The user management module realizes the customized configuration of different users by assigning user roles. The user roles include administrator roles and terminal user roles. After logging in, all users can maintain the configuration of the monitoring interface under the corresponding user role permissions. Administrator users can set the subscription topic permissions and interface display style permissions for each user.

[0030] The advantages of this invention compared to the prior art are:

[0031] (1) This invention decouples interface design from software and configuration files, improving the software's versatility and simplifying the design and management process of the software interface. It can be applied to the interface design of data monitoring software. This method has been applied in actual aerospace system missions.

[0032] (2) This invention grants users access to interface configuration permissions. Users can customize the interface through a graphical interface and generate a configuration file from the user's configuration attributes. The interface can be dynamically loaded and updated in real time without restarting the software, and what you see is what you get during the process.

[0033] (3) The present invention defines the monitoring interface based on a formal description language XML configuration file. The configuration file can also be directly edited. The XML configuration file has a standardized format. The interface layout, pages, controls and other configuration items are described in the form of nodes. The functions of each configuration item are independently allocated and it has scalability.

[0034] (4) The monitoring software interface control of the present invention is associated with the parameter data by setting binding parameters. After receiving the data, it is immediately transmitted to the interface display. The user does not need to pause or stop the experiment during the configuration process. The control status and data display are dynamically updated in real time during the interface configuration process, which is WYSIWYG.

[0035] (5) This invention provides a data communication based on the publish-subscribe model, which shields different hardware platforms, operating systems and communication protocols downwards, and provides a standardized unified publish-subscribe application development interface upwards.

[0036] (6) Use the singleton pattern to manage parameter information. The parameter table number or parameter code is a unique identifier to avoid repeatedly creating parameter objects and improve data distribution performance.

[0037] (7) This invention enables customized configurations for different users by assigning user roles. After logging in, ordinary users can maintain all monitoring pages under their account. An administrator mode is also provided to set subscription topic permissions and monitoring parameter permissions for each user, and to maintain the login status of each user on different terminals, enabling remote push and synchronous updates of configuration files. Attached Figure Description

[0038] Figure 1 This is a block diagram of the configuration system for the user-defined test data monitoring software interface, which is a WYSIWYG representation of an embodiment of the present invention.

[0039] Figure 2 This is a data communication model based on the publish-subscribe pattern in an embodiment of the present invention.

[0040] Figure 3 This describes the data transmission process in an embodiment of the present invention.

[0041] Figure 4 This is a schematic diagram of system-level user management in an embodiment of the present invention. Detailed Implementation

[0042] The present invention will be further described below with reference to the embodiments.

[0043] This invention addresses the characteristics of aerospace system data monitoring software, such as frequent interface iterations and high customization requirements. It proposes a WYSIWYG user-defined experimental data monitoring software interface configuration system, which can improve the reusability, universality, and rapid response capability of data monitoring software, reduce software development and configuration management costs, and has significant implications for applying this technology to practical engineering applications.

[0044] This invention provides a WYSIWYG user-defined experimental data monitoring software interface configuration system, which includes a control operation interface, a display configuration module, a data display module, a data receiving module, and a user management module.

[0045] The control operation interface is used by users to operate the customized monitoring software interface through a graphical interface throughout the entire experiment.

[0046] The display configuration module parses the user's graphical interface operations and generates a monitoring software interface configuration file. The monitoring software interface configuration file is used to store configuration information, including the monitoring software interface content, layout, and attribute parameters of each control. The monitoring software interface content includes the types and quantities of controls on the monitoring software interface. The attribute parameters of each control include the control's shape, size, position information, and binding parameters. The binding parameters are identifiers for the parameter data associated with the control.

[0047] The data display module dynamically loads configuration information to form and display the monitoring software interface, and updates the monitoring software interface in real time based on the configuration information.

[0048] The data receiving module receives the experimental data generated during the experiment and stores it in the data pool. It retrieves the topic data subscribed to by the user from the data pool, parses the parameter data bound to each control, and transmits it to the monitoring software interface for display.

[0049] The user management module enables customized configurations for different users by assigning user roles. These user roles include administrator roles and regular user roles. After logging in, all users can maintain all pages under their respective user role permissions. Administrator users can set monitoring parameter permissions for each user.

[0050] The custom monitoring software interface includes adding controls, batch generating controls, customizing control combinations, adjusting the layout of controls, and setting the attribute parameters of controls. Users can adjust the custom monitoring software interface and preview it in real time during the experiment through graphical operation, which is WYSIWYG.

[0051] The monitoring software interface configuration file is a formal description language XML configuration file.

[0052] The monitoring software interface configuration file describes the configuration items in the form of XML nodes. The configuration items include version information, basic control information, control attributes, and layout.

[0053] Version information is used to configure version, author, and date;

[0054] Basic control information is used to configure the control name and type;

[0055] Control properties are used to configure the property values ​​of the control. Property values ​​include general properties and custom properties. General properties include type, bound parameter information, duration, and refresh cycle. Bound parameter information includes parameter name, parameter code or parameter table number, encoding method, parameter type, parameter symbol, and system. Custom properties are defined according to the function of the control, such as the lighting condition property of an indicator light control.

[0056] Control layout is used to configure the layout of all controls on the monitoring software interface, including the layout method and the row number, column number, number of rows spanned, and number of columns spanned for each control.

[0057] The control operation interface includes:

[0058] The main interface of the software is an editable area, which allows users to directly adjust the number and layout of controls by dragging and dropping within the editable area.

[0059] A dialog box for modifying the layout of a control within its parent control. This allows you to adjust the layout of child controls, including horizontal, vertical, or grid layouts.

[0060] A dialog box for modifying control properties, used to set properties for individual or batch controls;

[0061] The dialog box for batch control creation is used to add controls in batches to the monitoring software interface. It automatically generates multiple controls arranged in sequence according to the size of the monitoring software interface.

[0062] The control interface also includes an XML editing dialog box, which allows users to directly edit the monitoring software interface configuration file.

[0063] The controls include curves, group boxes, labels, LCDs, indicator lights, tables, tabs, blank containers, and open interfaces. Each control is equipped with a dynamic link library (DLL) encapsulated into a unified interface. The display configuration module is based on the Qt signal and slot mechanism. The platform slot functions respond in real-time to user actions that update control properties on the monitoring software interface, calling the DLL of the interface control to configure it. The open interfaces are used to interface with external public plugins, such as NTP time synchronization plugins and heartbeat receiving plugins.

[0064] The data center includes the data distribution module SigMgr, the data parsing module ProcTopicWorker, and the parameter management module TableNoCodeMgr;

[0065] The data distribution module SigMgr establishes and maintains data configuration files, which include user-subscribed data topics, the IP address and port number of each data topic, to manage all data signals and subscription relationships. Based on the data configuration files, it retrieves the relevant topic data that the user has subscribed to from the bus data pool and publishes it to the corresponding data parsing module ProcTopicWorker.

[0066] The data parsing module ProcTopicWorker corresponds one-to-one with the data topic. According to the preset format of the data topic, it parses the heterogeneous data in the data topic and converts it into a recognizable parameter format. The parsed parameter information is stored in the cache area for the parameter management module to query and use.

[0067] The parameter management module TableNoCodeMgr is used to record the calling relationship between parameters and controls, check whether there is any parameter data update in the buffer, obtain the updated parameter data, notify the control that calls the parameter or have the control query and obtain the updated parameter data, and update the monitoring software interface.

[0068] The parameter management module TableNoCodeMgr uses a singleton pattern to manage parameter data, and multiple controls bound to the same parameter do not need to instantiate a new parameter object, thereby improving data distribution performance.

[0069] Example:

[0070] like Figure 1As shown, the monitoring software interface configuration system provided by the present invention includes a communication layer, a system layer, and a user layer. The user layer includes administrator users and terminal users. The system layer includes a user management module, a system management module, a log recording module, a control operation interface, a display configuration module, a data display module, and a data receiving module. The data center includes a data distribution module SigMgr, a data parsing module ProcTopicWorker, and a parameter management module TableNoCodeMgr.

[0071] The system layer can also connect to external public plugins, including NTP time synchronization plugins and heartbeat receiving plugins.

[0072] like Figure 2 As shown, the communication layer of this invention adopts a publish-subscribe communication model for data transmission and reception. The publish-subscribe data distribution service is a data-centric communication approach, focusing on data distribution between applications. The data-centric system consists of data publishers and subscribers. Communication is based on named data streams, which transmit known types of data from publishers to subscribers. Status information from various external devices is published to the monitoring computer in the form of parameters through different topics. The data monitoring software can receive this information after subscribing to the topic.

[0073] The data center obtains raw message data from the data pool through a publish-subscribe data communication middleware. After subscribing to the topic corresponding to the parameter data associated with the control through the communication middleware, the data center can receive the corresponding parameter data. External devices categorize device status parameters and publish them to the monitoring computer through different topics. For example, online status is published through the HeartBeat topic, while device operating status, such as voltage and current, is published through the State topic.

[0074] In this embodiment, the monitoring software interface controls include: indicator lights, tables, curves, text, group boxes, tabs, etc., as shown in the table below. The controls are bound to parameters that need to display data, and users can configure information such as the control's name, duration, and refresh cycle.

[0075] Table 1 List of Control Types

[0076]

[0077]

[0078] In this embodiment, the formal description interface configuration file should generally contain 5 types of nodes, and the node definitions are shown in the table below.

[0079] Table 2 Formal Description of Interface Configuration File

[0080]

[0081]

[0082] In this embodiment, the main functional classes of the system layer software can be decomposed into a customized interface part and a data center part, as shown in Table 3 below:

[0083]

[0084]

[0085] like Figure 3 As shown, the system layer of this invention uses a data center to receive, parse, and transmit parameters within each topic message. The detailed data flow involves the data distribution module SigMgr, which creates and maintains data reception configuration files, extracts data from the bus data pool, and publishes it to the corresponding data parsing module ProcTopicWorker. ProcTopicWorker parses heterogeneous data according to the preset topic format, converts it into parameter format, and stores it in a cache. The parameter management module TableNoCodeMgr monitors data updates in the cache and updates the monitoring interface through proactive notifications or queries from controls, achieving a closed loop from data to the interface.

[0086] like Figure 4 As shown, the system-level user management function of this invention achieves differentiated user configuration permissions through user role allocation. Administrators can manage user roles and user subscription permissions, perform configuration synchronization and backup, and achieve cross-terminal login status synchronization and remote configuration file updates. After logging in, ordinary users can maintain the configuration and display of the monitoring page under their own account.

[0087] The data parsing module ProcTopicWorker is a platform-specific plugin that uses a unified interface to implement customized parameter parsing, such as ProcStateWorker and ProcDPWorker.

[0088] The parameter management module TableNoCodeMgr uses a singleton pattern to manage parameters. Each parameter's table number or parameter code serves as a unique identifier. The singleton stores detailed information such as the parameter's table number, parameter code, original code, physical quantity, processing formula, and unit. For example, a voltage parameter might be (10001, 1), V15_T, 0x3A98, 15, Y = 0.001X, V, etc. When a parameter value is updated, the control that calls that parameter is notified, or the control queries and retrieves the updated parameter data.

[0089] This invention provides a user-customizable interface configuration method. Throughout the experiment, users can add controls, generate controls in batches, and create custom control combinations through the interface, as well as set control properties and bind parameters. The interface configuration is generated by the display configuration module, or users can directly edit the configuration file. The configuration interface is convenient and user-friendly. The data display module dynamically loads configuration information to form a monitoring interface, quickly generating customized interfaces.

[0090] This invention allows modules to dynamically subscribe to various topic signals. After subscribing to a topic, the data management module is responsible for retrieving the data of that topic from the bus data pool, thereby implementing an optimized observer pattern to improve data distribution performance.

[0091] Although the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make possible changes and modifications to the technical solutions of the present invention by utilizing the methods and techniques disclosed above without departing from the spirit and scope of the present invention. Therefore, any simple modifications, equivalent changes and alterations made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solutions of the present invention shall fall within the protection scope of the technical solutions of the present invention.

Claims

1. A WYSIWYG user customized test data monitoring software interface configuration system characterized by The control operation interface, the display configuration module, the data display module, and the data receiving module are included. The control operation interface is used for the user to operate the self-defined monitoring software interface through the graphical interface during the whole test process. The display configuration module analyzes the graphical interface operation of the user, generates a monitoring software interface configuration file, and stores configuration information in the monitoring software interface configuration file. The data display module dynamically loads the configuration information to form and display the monitoring software interface, and updates the monitoring software interface in real time according to the configuration information. The data receiving module receives test data generated during the test process and stores the test data in a data pool, obtains theme data subscribed by the user from the data pool, analyzes the theme data to obtain binding parameter data of each control, and transmits the binding parameter data to the monitoring software interface for display.

2. The WYSIWYG user customized test data monitoring software interface configuration system of claim 1, wherein, The self-defined monitoring software interface includes adding controls, batch generating controls, customizing control combinations, adjusting the layout of controls, and setting the attribute parameters of controls.

3. The WYSIWYG user customized test data monitoring software interface configuration system of claim 1, wherein, The monitoring software interface configuration file is an XML configuration file in a formal description language.

4. The WYSIWYG user customized test data monitoring software interface configuration system of claim 1, wherein, The monitoring software interface configuration file describes configuration items in the form of XML nodes, and the configuration items include version information, control basic information, control attributes, and layout. The version information is used for configuring the version, author, and date. The control basic information is used for configuring the control name and type. The control attributes are used for configuring the attribute values of the controls, and the general attributes include the type, binding parameter information, retention time, and refresh cycle. The binding parameter information includes the parameter name, parameter code or parameter table number, encoding method, parameter type, parameter symbol, and system to which the parameter belongs.

5. The WYSIWYG user customized test data monitoring software interface configuration system of claim 1, wherein, The custom attributes are defined according to the functions of the controls, such as the light-on condition attribute of the indicator light control. The control layout is used for configuring the layout of all controls on the monitoring software interface, including the layout method and the row number, column number, number of rows to span, and number of columns to span of each control. The control operation interface includes: The software main interface is an editable area, which is used for the user to directly adjust the number and layout of controls in the editable area through the drag-and-drop method. The dialog box for modifying the layout of controls in the parent control is used for adjusting the layout method of the child control, and the layout method includes horizontal layout, vertical layout, or grid layout.

6. The WYSIWYG user customized test data monitoring software interface configuration system of claim 5, wherein, The dialog box for modifying the attribute of the control is used for setting the attribute of the control or batch setting the attribute of the control. The dialog box for batch creating controls is used for adding controls in batches on the monitoring software interface, and automatically generates multiple controls arranged in sequence according to the size of the monitoring software interface. The control operation interface further includes an XML editing dialog box, which is used for the user to directly edit the monitoring software interface configuration file.

7. The WYSIWYG user customized test data monitoring software interface configuration system of claim 1, wherein, The control types include curve, group box, label, LCD, indicator light, table, tab, blank container and open interface, each of which is equipped with a dynamic link library encapsulated into a unified interface, and the display configuration module is based on the Qt signal-slot mechanism, a platform slot function responds to a user's operation of updating a control attribute on a monitoring software interface in real time, triggers a signal, calls a dynamic link library of an interface control, and realizes configuration of the control.

8. The WYSIWYG user custom test data monitoring software interface configuration system of claim 1, wherein, The data center comprises a data distribution module SigMgr, a data analysis module ProcTopicWorker and a parameter management module TableNoCodeMgr. The data distribution module SigMgr establishes and maintains a data configuration file, the data configuration file comprises data topics subscribed by users, IP addresses and port numbers of each data topic, and is used for managing all data signals and subscription relationships; according to the data configuration file, relevant topic data subscribed by users is taken out from a bus data pool and published to a corresponding data analysis module ProcTopicWorker; The data analysis module ProcTopicWorker corresponds to a data topic one by one, analyzes heterogeneous data in the data topic according to a preset format of the data topic, converts the heterogeneous data into identifiable parameter format, and stores the analyzed parameter information in a buffer area for query and use by the parameter management module TableNoCodeMgr; The parameter management module TableNoCodeMgr is used for recording a calling relationship between parameters and controls, checking whether parameter data in a buffer area is updated, obtaining updated parameter data, notifying a control calling the parameter or querying and obtaining the updated parameter data by the control, and updating a monitoring software interface.

9. The WYSIWYG user custom test data monitoring software interface configuration system of claim 1, wherein, The parameter management module TableNoCodeMgr adopts a singleton mode to manage parameter data, and a plurality of controls bound to the same parameter do not need to instantiate a new parameter object, so that data distribution performance is improved.

10. The WYSIWYG user customized test data monitoring software interface configuration system of claim 1, wherein, The user management module is further provided, the user management module realizes custom configuration of different users by assigning user roles, the user roles comprise an administrator role and a terminal user role, all users can maintain configuration of a monitoring interface under a corresponding user role permission after logging in, and the administrator role user can set subscription topic permission and interface display style permission of each user.

Images