Configuration radar BITE interface module organization method

Abstract

The invention relates to the field of software radar man-machine interaction and the technical field of radar system monitoring and maintenance, in particular to a configuration module organization method for a radar BITE interface. A configuration file is input, configuration file information mainly comprises radar hardware information and hardware arrangement, such as the number of types of hardware, layout and BITE state monitoring points, and the configuration file information adopts a format defined by components and can be translated into layout, arrangement and nesting of an interface, components in the interface, message response of the components and the like by a software module. And after analysis of the interface translation module, the event binding module and the data processing and storage function module, a complete radar BITE state display and management interface is generated. According to the invention, the flexibility, configurability and maintenance efficiency of the radar monitoring interface are improved.

Description

Technical Field

[0001] The present invention relates to the field of software radar human-computer interaction and radar system BITE (Built-In Test Equipment) monitoring and maintenance technology, and in particular to a configurable module organization method for a radar BITE interface, aiming to improve the flexibility, configurability and maintenance efficiency of the radar monitoring interface. Background Art

[0002] With the continuous development of radar technology, the complexity and maintenance difficulty of radar systems are also increasing. Traditional radar BITE interfaces often adopt fixed designs, which are difficult to adapt to different test requirements and upgrades of radar systems. In addition, the configuration and adjustment of interface elements usually require the intervention of professional developers, which is costly and inefficient to maintain. Therefore, there is an urgent need for a more flexible and efficient design method for configurable radar BITE interface modules. Summary of the invention

[0003] In view of the shortcomings of the prior art, the purpose of the present invention is to provide a configurable radar BITE interface module organization method. The present invention realizes the rapid construction, flexible adjustment and efficient maintenance of the radar BITE interface through modular design, dynamic configuration, configurable interface translation, serialized event binding and data interaction and storage functions.

[0004] The technical solution of the present invention is: a configuration radar BITE interface module organization method, characterized in that: it includes the following modules:

[0005] 1. Configuration file organization

[0006] Determine the organization of configuration files, including main configuration files and sub-configuration files; the main configuration file has only one level, including the number of each radar subsystem and sub-configuration file path information; the sub-configuration file contains the number of the corresponding subsystem, title name, and various types of sub-interface information that can be nested;

[0007] 2. The radar BITE interface module includes three sub-modules: interface translation module, event binding module and data processing and storage function module, specifically:

[0008] 2.1. Interface translation module:

[0009] a) reading the main configuration file to generate a configuration data storage container with a tree structure;

[0010] b) Find the root node of the tree container and traverse the first-level child nodes to generate the tab navigation buttons of the BITE status interface of each subsystem of the radar, and then traverse the "file" field and "type" field contained in the child nodes; read the corresponding sub-configuration file according to the sub-configuration file path of the "file" field, and add it to the tree container as the second-level child node of the node;

[0011] c) Traverse the sub-nodes of the second-level sub-node, read the interface title information contained in the "title" field and set it as the title of the corresponding subsystem BITE status interface tab page, read the "sort" field as the sub-interface arrangement method in the tab page; read the "state", "value", "table" and other fields to generate the corresponding sub-interface and embed it in the tab page according to the arrangement method; count the node types and node numbers of the first-level and second-level sub-nodes;

[0012] d) Traverse the third-level child nodes, read the content of the "item" field, split it according to "," and create the split string into status lights, data or data tables according to the attributes of its parent node to arrange and layout in the interface; split the single item information containing the ":" symbol with the ":" symbol, read the field after the ":", and number the corresponding sub-interface of the item, which is used in the user event binding process of the event binding module; count the node type and number of the child nodes of the current level;

[0013] e) Iterate through the fourth-level, fifth-level, ... child nodes, and repeat step d) until all untraversed nodes are leaf nodes. This method can adapt to any number of BITE monitoring nodes at any multiple levels.

[0014] 2.2 The data processing and storage module includes three functions: network configuration function, data container generation function, and process data analysis and storage function:

[0015] a) Network configuration function: create network communication sockets and receive data that conforms to standardized protocols;

[0016] b) Data container generation function, based on C++ dynamic container; count the node types and node numbers of the first-level, second-level... nodes, form a tree-like radar BITE monitoring node data storage container, and complete the space allocation of the dynamic container; after completing the creation of the radar BITE monitoring node data storage container, serialize the data storage container; developers can complete the analysis of the radar BITE status and convert it into a standard standardized data protocol, and send the data protocol through the network socket to the process data analysis and storage function for analysis and storage;

[0017] c) Process data analysis and storage function, when the network communication socket receives data that conforms to the standardized data protocol generated in b), the data analysis process is performed.

[0018] 2.3 Event binding module:

[0019] There are two types of event binding:

[0020] 2.3.1、User operation event binding

[0021] a) Find the root node of the tree container and traverse its first-level child nodes to read the value of the "id" field; traverse the second-level child nodes, bind the tab page whose value of the "sysIndex" field is the same as the value of the "id" field to the tab page navigation button of the corresponding "id" through a button click event, and when the user clicks the button, the tab page stacking area will switch to the corresponding tab page;

[0022] b) Traverse all the sub-nodes of the "state", "value", and "table" sub-interfaces under the second-level sub-node, read the "subID" field value of the sub-interface where the "sub" field is true, and compare it with the "subID"

[0023] The "item" with the same field value is bound to the button click event. When the user clicks the "item"

[0024] , the data and status displayed in the sub-interface will switch to the sub-interface status corresponding to the "item" clicked by the user.

[0025] 2.3.2, Data input event binding:

[0026] a) Binding data input events with data processing and storage modules;

[0027] b) Bind the data update event with the interface refresh event. When data is updated in the radar BITE monitoring node data storage container, the interface of the node corresponding to the data update and all its child nodes is displayed.

[0028] According to the configurable radar BITE interface module organization method as described above, it is characterized in that the format of the configuration file is JSON or XML format.

[0029] According to the configurable radar BITE interface module organization method as described above, it is characterized in that: the main configuration file corresponds to the radar BITE subsystem tab navigation button, specifically "id": the sequential number of the BITE subsystem in the tab; "type": the translation logic of the subsystem interface; "file": the path and file name of the subsystem configuration file.

[0030] According to the configured radar BITE interface module organization method as described above, it is characterized in that: the sub-configuration file includes a radar BITE subsystem tab page module, specifically: "sysIndex": used to correspond to the response event of the navigation button, corresponding to the "id" of the navigation button; "state": defines the BITE sub-interface within the tab page, which only contains a certain number of BITE status lights or other BITE sub-interfaces; "value": defines the BITE sub-interface within the tab page, which only contains a certain number of BITE status texts or data or other BITE sub-interfaces; "table": defines the BITE sub-interface within the tab page.

[0031] According to the configurable radar BITE interface module organization method as described above, it is characterized in that: the sub-configuration file includes a "state" type sub-interface, specifically: "type": the style of the status light; "size": the size of the status light; "item": the name of the status light under the current sub-interface.

[0032] According to the configurable radar BITE interface module organization method as described above, it is characterized in that: the sub-configuration file includes a "value" type sub-interface: specifically: "item": the name of the BITE status data under the current sub-interface.

[0033] According to the configurable radar BITE interface module organization method as described above, it is characterized in that: the sub-configuration file includes general definitions, specifically: "title": the title name of the tab page or BITE sub-interface; "sub": whether it is a sub-interface of a certain "item"; "subID": the number of the sub-interface; "sort": the sorting method of controls in the tab page.

[0034] According to the configurable radar BITE interface module organization method as described above, it is characterized by: serializing to form a configuration file in XML or JSON format containing information such as radar multi-level BITE status monitoring node name, type and corresponding sub-node number.

[0035] According to the configured radar BITE interface module organization method as described above, it is characterized in that: the specific process of the data analysis flow is: according to the radar subsystem number and sub-interface number defined in the standard protocol, find the data location in the radar BITE monitoring node data storage container, put the data into the tree-shaped radar BITE monitoring node data storage container, and trigger the interface refresh event; after the interface refresh event is triggered, the interface translation module reads the updated sub-node data in the radar BITE monitoring node data storage container and refreshes the interface.

[0036] According to the configurable radar BITE interface module organization method as described above, it is characterized in that: during the system startup process, the module organization method reads the configuration file, the interface translation module completes the generation of the radar BITE interface according to the method described in 2.1, the data processing and storage module completes the construction of the data processing flow according to the method described in 2.2, and the event binding module completes the binding of user operation events and data input events according to the method described in 2.3.

[0037] According to the configurable radar BITE interface module organization method as described above, it is characterized in that: the module organization method workflow is: the developer views the data storage container serialization configuration file generated in 0b), writes the radar BITE data parsing and transcoding program according to the standardized data protocol shown in the configuration file, parses the radar BITE data into a standardized data protocol, sends it to this software module, and generates a data input event.

[0038] The beneficial effects of the present invention are: providing a flexible and efficient radar BITE interface module organization method, through modular design, dynamic configuration, configurable interface translation, serialized event binding and data interaction and storage functions, to achieve rapid construction, flexible adjustment and efficient maintenance of the radar BITE interface. Developers can directly define interface elements and corresponding behaviors in the configuration file without recompiling or generating executable files. This not only significantly improves the flexibility and rapidity of interface adjustment, but also simplifies the process of interface update and maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 Radar BITE interface module block diagram

[0040] Figure 2 Radar BITE interface module workflow diagram

[0041] Figure 3 Configuration file organization diagram

[0042] Figure 4 Schematic diagram of the first-level BITE interface configuration file (main configuration file)

[0043] Figure 5 Schematic diagram of the secondary BITE interface configuration file (sub-configuration file)

[0044] Figure 6 Radar BITE interface reference diagram

[0045] Glossary:

[0046] Radar terminal: As a key component in the radar system, the terminal undertakes the important function of human-computer interaction. The radar terminal display and control system processes the received radar video information through target detection and target tracking, and then feeds back important information such as the target's position and distance to the user through visualization; at the same time, the user can also make specific settings for the radar system through the terminal so that the radar can adapt to the current environment.

[0047] Radar BITE: In radar systems, BITE (Built-In Test Equipment) refers to equipment used to test the components and functions of each subsystem within the radar system to ensure the normal operation and troubleshooting of the system. BITE is widely used in radar systems. It not only includes the testing of each component within the radar system, but also includes the performance testing of the entire system. Through BITE, fault detection and performance testing of the radar system can be achieved to ensure the stable operation and high reliability of the radar system.

[0048] Serialization and deserialization: Serialization is a process of describing an object as a series of bytes. Putting an object in a program into a hard disk (file) is serialization. If it is not stored on the disk but stored in the memory, it will increase memory consumption; serialization is the process of converting the state information of an object into a form that can be stored or transmitted; deserialization is the process of rebuilding these bytes into an object. Converting the bytecode in the hard disk (file) back into an object is deserialization. During serialization, the object writes its current state to a temporary or persistent storage area. Later, the object can be recreated by reading or deserializing the state of the object from the storage area.

[0049] XML: Extensible Markup Language (XML) is a markup language similar to HTML, but its main purpose is to describe data rather than display data. It uses custom tags to structure data and has strong extensibility and self-description. Many software and applications use XML files to store configurations, which is the current mainstream configuration file storage format.

[0050] JSON: JSON (JavaScript Object Notation) is designed based on a subset of ECMAScript. It is an open standard file format and data exchange format that is easy for people to read and write, and easy for machines to parse and generate. JSON is independent of language design, and many programming languages ​​support data exchange in JSON format.

[0051] Qt: Qt is a cross-platform C++ graphical user interface application development framework that can build high-performance desktop applications. Qt is an object-oriented framework that uses special code generation extensions (called MetaObject Compiler (moc)) and some macros. Qt is easy to extend and allows true component programming. DETAILED DESCRIPTION

[0052] The technical solution of the present invention is further described below in conjunction with the accompanying drawings.

[0053] The present invention includes a configuration radar BITE interface module organization method, whose input is a configuration file, and the configuration file information mainly includes radar hardware information and hardware arrangement, such as hardware type quantity, layout, BITE status monitoring points, which adopts the format of component definition and can be translated by the software module of the present invention into the layout, arrangement, nesting of the interface and the components in the interface, the message response of the components, etc. After being parsed by the interface translation module, the event binding module and the data processing and storage function module, a complete radar BITE status display and management interface is generated.

[0054] The input of the radar BITE status display and management interface is: the user's keyboard and mouse interface operation events and the BITE data of each radar subsystem (need to be converted into a standard format consistent with the configuration file); its output is a graphical user interface that refreshes the data and status of each BITE monitoring point of each radar subsystem according to events such as data and user operations, as well as a database file containing BITE information records.

[0055] 1. Configuration file organization

[0056] Determine how the configuration files are organized. The configuration files must be in a user-readable, unrestricted, and highly extensible language format such as JSON or XML. The benefits of using such configuration files are:

[0057] a) Due to its human-readable nature, users or developers can manually edit the configuration file at any time according to their needs;

[0058] b) Due to the characteristics of no hierarchy restriction and strong scalability, BITE monitoring nodes of any complexity and any number of hierarchies can be represented through configuration files, and the generated interface can be fully displayed on the terminal device interface equipped with the device.

[0059] The following lists the file structure of a JSON-based configuration file and the definitions of various components and their properties in the JSON file. The main configuration file has only one level, which contains information such as the number of each radar subsystem, the path of the sub-configuration file, etc. The sub-configuration file contains information such as the number of the corresponding subsystem, the title name, and various types of sub-interfaces that can be nested.

[0060] 1.1 Radar BITE subsystem tab navigation buttons (main configuration file):

[0061] "id": the sequential number of the BITE subsystem in the tab page;

[0062] "type": translation logic of the subsystem interface;

[0063] "file": The path and file name of the subsystem configuration file.

[0064] 1.2 Radar BITE subsystem tab (sub-configuration file):

[0065] "sysIndex": used to respond to the navigation button's response event, corresponding to the "id" of the navigation button;

[0066] "state": defines the BITE sub-interface in the tab page, which only contains a certain number of BITE status lights or other BITE sub-interfaces;

[0067] "value": defines the BITE sub-interface in the tab page, which only contains a certain number of BITE status texts or data or other BITE sub-interfaces;

[0068] "table": defines the BITE sub-interface within the tab page, which contains one or more data tables.

[0069] 1.3 "state" type sub-interface (sub-configuration file):

[0070] "type": the style of the status light, which can include ball, button, etc.;

[0071] "size": the size of the status light;

[0072] "item": the name of the status light in the current sub-interface (multiple items can be defined, separated by ","). If the "\n" character is included, the layout will wrap.

[0073] 1.4 "value" type sub-interface (sub-configuration file):

[0074] "item": the name of the BITE status data in the current sub-interface (multiple items can be defined, separated by ","). The data type can be defined. If the "\n" character is included, the layout will be wrapped.

[0075] 1.5 General Definitions (Sub-profiles)

[0076] "title": the title of the tab or BITE sub-interface;

[0077] "sub": whether it is a sub-interface of a certain "item";

[0078] "subID": the ID of the sub-interface;

[0079] "sort": The sorting method of controls in the tab page (true means horizontal layout, false means vertical layout).

[0080] 2. Radar BITE interface module includes three sub-modules: interface translation module, event binding module and data processing and storage function module. The specific module organization includes the following:

[0081] 2.1. Interface translation module:

[0082] The core principle of the interface translation module is based on Qt's dynamic interface creation function, which can dynamically create interfaces and components based on the configuration files read after the program starts. All user interface (UI) components and trigger functions are defined and constructed through configuration files, and the interface translation module only needs necessary constructors. The flexibility of this method allows only the basic framework for parsing and implementing these configurations to be retained in the code, while the specific UI layout and functions are completely determined by external JSON configuration files.

[0083] According to the above configuration file organization method, users or developers can generate a tree-like configuration file structure with no hierarchy limit. The interface translation module reads the configuration file with a tree structure according to the above principle to generate a multi-level BITE status interface. The specific method is as follows:

[0084] a) Read the main configuration file to generate a tree-structured configuration data storage container. The structure of the container is as follows: Figure 3 As shown;

[0085] b) Find the root node of the tree container and traverse its child nodes (first-level child nodes), generate the tab navigation buttons of the BITE status interface of each subsystem of the radar, and then traverse the "file" field and "type" field contained in the child nodes. Read the corresponding sub-configuration file according to the sub-configuration file path of the "file" field, and add it to the tree container as the second-level child node of the node;

[0086] c) Traverse the subnodes of the second-level subnode (third-level subnode), read the interface title information contained in the "title" field and set it as the title of the corresponding subsystem BITE status interface tab (referred to as the tab), and read the "sort" field as the sub-interface arrangement method in the tab. Read "state", "value",

[0087] The corresponding sub-interfaces generated by fields such as "table" are embedded in the tab page according to the layout method. Count the node types (status or data) and number of nodes of the first-level and second-level child nodes;

[0088] d) Traverse the third-level child nodes, read the content of the "item" field, split it according to "," and divide the split string (single item information) according to the attributes of its parent node ("state", "value",

[0089] "table") is created as status lights, data or data tables to arrange the layout in the interface.

[0090] Use the ":" symbol to split the single item information containing the ":" symbol, read the field after the ":", and number the sub-interface corresponding to the item (corresponding to the value of the "subID" field), which is used in the user event binding process of the event binding module. Count the node type (state or data) and number of sub-nodes at the current level;

[0091] e) Iterate through the fourth-level, fifth-level, ... child nodes, and repeat step d) until all untraversed nodes are leaf nodes. This method can adapt to any number of BITE monitoring nodes at any multiple levels.

[0092] In conventional radar BITE interfaces, the creation and layout of the interface are edited in the development environment using code or interface editors, and the interface cannot be changed after compilation. By using this interface translation module to generate the interface, the interface can be dynamically modified without running the development environment or compiling the program. This greatly improves the efficiency of software development and maintenance.

[0093] 2.2 The data processing and storage module includes three functions: network configuration function, data container generation function, and process data analysis and storage function:

[0094] a) Network configuration function: create a network communication socket to receive data that complies with standardized protocols;

[0095] b) Data container generation function, based on C++ dynamic container. In the process of creating sub-interfaces and components in steps 0c) d), the node types (status or data) and the number of nodes of the first-level, second-level... nodes are counted to form a tree-like radar BITE monitoring node data storage container, and the space allocation of the dynamic container is completed. After the creation of the radar BITE monitoring node data storage container is completed, the data storage container is serialized. Serialization forms an XML or JSON format configuration file containing information such as the radar multi-level BITE status monitoring node name, type, and corresponding number of child nodes. The developer can complete the analysis of the radar BITE status and convert it into a standard standardized data protocol, and send the data protocol through the network socket to the process data parsing and storage function for parsing and storage;

[0096] c) Process data analysis and storage function. When the network communication socket receives data that conforms to the standardized data protocol generated in b), the data analysis process is performed. According to the radar subsystem number and sub-interface number defined in the standard protocol (corresponding to the "subID" field value), the data location in the radar BITE monitoring node data storage container is found, the data is placed in the tree-like radar BITE monitoring node data storage container, and the interface refresh event is triggered. After the interface refresh event is triggered, the interface translation module reads the updated sub-node data in the radar BITE monitoring node data storage container and refreshes the interface.

[0097] 2.3 Event binding module:

[0098] The event binding module is the basis of the multi-level BITE interface. This module can realize various responses of all translated interface controls, among which the most important is the interface switching event. According to the configuration file definition in step 1, the event binding class is implemented based on the Qt meta-object system. For example, the click event response of the tab (first-level BITE interface) button is bound to the page switching function of the radar BITE subsystem status interface (second-level BITE interface) of the corresponding ID, and the click event of the status light of the second-level BITE interface is bound to the page switching of the third-level BITE interface. There are two main types of event binding:

[0099] 2.3.1、User operation event binding

[0100] a) Find the root node of the tree container and traverse its child nodes (first-level child nodes) to read the value of the "id" field. Traverse the second-level child nodes and bind the tab page with the same value of the "sysIndex" field as the "id" field to the tab page navigation button of the corresponding "id" for a button click event. When the user clicks the button, the tab page stacking area of ​​the software will switch to the corresponding tab page;

[0101] b) Traverse all the sub-nodes of the "state", "value", and "table" sub-interfaces under the second-level sub-node, read the "subID" field value of the sub-interface where the "sub" field is true, and compare it with the "subID"

[0102] The "item" with the same field value is bound to the button click event. When the user clicks the "item"

[0103] , the data and status displayed in the sub-interface will switch to the sub-interface status corresponding to the "item" clicked by the user.

[0104] 2.3.2, Data input event binding:

[0105] a) Bind the data input event to the data processing and storage module. When a data input event occurs, the data is input into the process data parsing and storage function of the data processing and storage module for processing, and the radar BITE monitoring node data storage container is updated to generate a data update event;

[0106] b) Bind the data update event with the interface refresh event. When data is updated in the radar BITE monitoring node data storage container, the interface of the node corresponding to the data update and all its child nodes is displayed.

[0107] 3. Software module workflow

[0108] 3.1. Startup and initialization

[0109] During the system startup process, the configuration file is read, the interface translation module completes the generation of the radar BITE interface according to the method described in 2.1, the data processing and storage module completes the construction of the data processing flow according to the method described in 2.2, and the event binding module completes the binding of user operation events and data input events according to the method described in 2.3.

[0110] 3.2 Workflow

[0111] The developer views the data storage container serialization configuration file generated in 0b), writes the radar BITE data parsing and transcoding program according to the standardized data protocol shown in the configuration file, parses the radar BITE data into a standardized data protocol, sends it to this software module, and generates a data input event.

[0112] When a BITE status data input event occurs, the data processing and storage module receives and processes the data and updates the data to the corresponding node. Then the interface refresh event is triggered to complete the status refresh of the corresponding monitoring node and its sub-interface.

[0113] When a user operation event occurs, the interface switches the tabs of each subsystem according to the navigation button clicked by the user, or switches the display of the monitoring node sub-interface according to the monitoring node clicked by the user.

Claims

1. A method for organizing a configured radar BITE interface module, characterized in that: The following modules are organized:

1. Configuration file organization Determine how the configuration files are organized, including the main configuration file and the sub-configuration file. The main configuration file has only one level, which contains the numbers of each radar subsystem and the path information of the sub-configuration file. The sub-configuration file contains the number of the corresponding subsystem, the title name, and various types of sub-interface information that can be nested.

2. The radar BITE interface module includes three sub-modules: interface translation module, event binding module and data processing and storage function module, specifically: 2.

1. Interface translation module: a) reading the main configuration file to generate a configuration data storage container in a tree structure; b) Find the root node of the tree container and traverse the first-level child nodes to generate the tab navigation buttons of the BITE status interface of each subsystem of the radar, and then traverse the "file" field and "type" field contained in the child nodes; read the corresponding sub-configuration file according to the sub-configuration file path of the "file" field, and add it to the tree container as the second-level child node of the node; c) Traverse the sub-nodes of the secondary sub-node, read the interface title information contained in the "title" field and set it as the title of the corresponding subsystem BITE status interface tab page, read the "sort" field as the sub-interface arrangement method in the tab page; read the "state", "value", "table" and other fields to generate the corresponding sub-interface and embed it in the tab page according to the arrangement method; Count the node types and numbers of first-level and second-level child nodes; d) Traverse the third-level child nodes, read the content of the "item" field, split it according to "," and create the split string into status lights, data or data tables according to the attributes of its parent node to arrange and layout in the interface; split the single item information containing the ":" symbol with the ":" symbol, read the field after the ":", and number the corresponding sub-interface of the item, which is used in the user event binding process of the event binding module; count the node type and number of the child nodes of the current level; e) Iterate through the fourth-level, fifth-level, and ... child nodes, and repeat step d) until all untraversed nodes are leaf nodes. This can adapt to any number of BITE monitoring nodes at any multiple levels; 2.2 The data processing and storage module includes three functions: network configuration function, data container generation function, and process data analysis and storage function: a) Network configuration function: create network communication sockets and receive data that conforms to standardized protocols; b) Data container generation function, based on C++ dynamic container; count the node types and node numbers of the first-level, second-level... nodes, form a tree-like radar BITE monitoring node data storage container, and complete the space allocation of the dynamic container; after completing the creation of the radar BITE monitoring node data storage container, serialize the data storage container; developers can complete the analysis of the radar BITE status and convert it into a standard standardized data protocol, and send the data protocol through the network socket to the process data analysis and storage function for analysis and storage; c) Process data analysis and storage function, when the network communication socket receives data that conforms to the standardized data protocol generated in b), the data analysis process is carried out; 2.3 Event binding module: There are two types of event binding: 2.3.1、User operation event binding a) Find the root node of the tree container and traverse its first-level child nodes to read the value of the "id" field; traverse the second-level child nodes, bind the tab page whose value of the "sysIndex" field is the same as the value of the "id" field to the tab page navigation button of the corresponding "id" through a button click event, and when the user clicks the button, the tab page stacking area will switch to the corresponding tab page; b) Traverse all the sub-nodes of the "state", "value", and "table" sub-interfaces under the second-level sub-node, read the value of the "subID" field of the sub-interface with the "sub" field being true, and bind it to the "item" with the same value of the "subID" field as the button click event. When the user clicks the "item", the data and status displayed on the sub-interface will switch to the sub-interface status corresponding to the "item" clicked by the user; 2.3.2, Data input event binding: a) Binding data input events with data processing and storage modules; b) Bind the data update event with the interface refresh event. When data is updated in the radar BITE monitoring node data storage container, the interface of the node corresponding to the data update and all its child nodes is displayed.

2. A method for organizing configured radar BITE interface modules according to claim 1, characterized in that: The configuration file is in JSON or XML format.

3. The method for organizing a configured radar BITE interface module according to claim 1, characterized in that: The main configuration file is the radar BITE subsystem tab navigation button, specifically "id": the sequential number of the BITE subsystem in the tab; "type": the translation logic of the subsystem interface; "file": the path and file name of the subsystem configuration file.

4. The method for organizing a configured radar BITE interface module according to claim 1, characterized in that: The sub-configuration file includes the radar BITE subsystem tab module, specifically: "sysIndex": used to respond to the navigation button's response event, corresponding to the "id" of the navigation button; "state": defines the BITE sub-interface within the tab, which only contains a certain number of BITE status lights or other BITE sub-interfaces; "value": defines the BITE sub-interface within the tab, which only contains a certain number of BITE status texts or data or other BITE sub-interfaces; "table": defines the BITE sub-interface within the tab.

5. The method for organizing a configured radar BITE interface module according to claim 1, characterized in that: The sub-configuration file includes "state" type sub-interfaces, specifically: "type": the style of the status light; "size": the size of the status light; "item": the name of the status light in the current sub-interface.

6. A method for organizing configured radar BITE interface modules according to claim 1, characterized in that: The sub-configuration file includes "value" type sub-interfaces: specifically: "item": the name of the BITE status data under the current sub-interface.

7. The method for organizing a configured radar BITE interface module according to claim 1, characterized in that: The sub-configuration file includes common definitions, specifically: "title": the title name of the tab page or BITE sub-interface; "sub": whether it is a sub-interface of a certain "item"; "subID": the ID of the sub-interface; "sort": the sorting method of controls in the tab page.

8. A method for organizing configured radar BITE interface modules according to any one of claims 1 to 7, characterized in that: The specific process of the data analysis flow is as follows: according to the radar subsystem number and sub-interface number defined in the standard protocol, find the data location in the radar BITE monitoring node data storage container, put the data into the tree-like radar BITE monitoring node data storage container, and trigger the interface refresh event; After the interface refresh event is triggered, the interface translation module reads the updated sub-node data in the radar BITE monitoring node data storage container and refreshes the interface.

9. A method for organizing configured radar BITE interface modules according to any one of claims 1 to 7, characterized in that: Module organization method During system startup, the configuration file is read, the interface translation module completes the generation of the radar BITE interface according to the method described in 2.1, the data processing and storage module completes the construction of the data processing flow according to the method described in 2.2, and the event binding module completes the binding of user operation events and data input events according to the method described in 2.

3.

10. A method for organizing configured radar BITE interface modules according to any one of claims 1 to 7, characterized in that: The workflow of the module organization method is as follows: the developer checks the data storage container serialization configuration file generated in 0b), writes the radar BITE data parsing and transcoding program according to the standardized data protocol shown in the configuration file, parses the radar BITE data into a standardized data protocol, and sends it to this software module to generate a data input event.

Images