Spaceflight equipment test system based on scripts and plug-ins

Abstract

The application discloses a spaceflight equipment test system based on scripts and plug-ins and belongs to the technical field of LVC test verification. The system comprises a main control module, a plurality of slave control modules and a running support library. The slave control modules are plug-in submodules designed according to a unified coding format, the plug-in submodules define the implementation logic of an object model, and after being loaded, the plug-in submodules execute internal functions by calling the object model in the running support library. The main control module reads external configuration parameters, assigns values to internal variables of the plug-in submodules, loads all the plug-in submodules, and controls the plug-in submodules to be executed in sequence according to a set execution sequence. The running support library provides an object model library for the plug-in submodules, and objects defined in the object model include messages, state distribution objects and remote methods. Through the application of the application, communication between subsystem models is realized, subsystems of spaceflight equipment are associated with each other, and a digital equipment overall model is formed.

Description

Technical Field

[0001] This invention relates to a space equipment testing system based on scripts and plugins, belonging to the field of LVC testing and verification technology. Background Technology

[0002] LVC simulation refers to simulation that combines live, virtual, and construct elements. It can adapt to future joint operations, support complex test formats for combat-oriented aerospace equipment, and facilitate the transition to comprehensive combat effectiveness testing. It can also achieve test conditions that are impossible to achieve in reality, effectively solving the problem of real equipment participation in equipment testing. Implementing LVC simulation requires underlying communication based on a distributed simulation support architecture. Current technologies achieve communication between models by writing corresponding communication code on-the-fly, with each model having its own set of communication code. Adjusting the communication logic requires modifying the code, which is tedious and time-consuming. Summary of the Invention

[0003] The technical problem solved by this invention is to overcome the shortcomings of the prior art and propose a space equipment test system based on scripts and plug-ins. By combining LUA scripts and a plug-in architecture, a bridge is established between the system and the model, and between the system and the communication middleware. This enables communication between the subsystem models of space equipment and integrates the subsystems into a whole to form a digital equipment overall model.

[0004] The technical solution of this invention is:

[0005] A script- and plugin-based aerospace equipment testing system includes a main control module, multiple slave control modules, and a runtime support library.

[0006] Each control module is a pluggable submodule designed according to a unified coding format. The pluggable submodule defines the implementation logic of the object model. After being loaded, it executes its internal functions by calling the object model in the runtime support library.

[0007] The main control module reads external configuration parameters and assigns values ​​to the internal variables of each plug-in submodule, loads all plug-in submodules, and controls the corresponding plug-in submodules to be executed in sequence according to the set execution order.

[0008] The runtime support library provides an object model library for each plug-in submodule. The objects defined in the object model include messages, state distribution objects, and remote methods.

[0009] Furthermore, the main control module includes a configuration management submodule, a program initialization submodule, a plug-in management submodule, and an execution order control submodule;

[0010] The configuration management submodule reads external configuration files and saves the configuration parameters from those files.

[0011] The program initialization submodule initializes internal variables, requests and creates computer resources, and loads all plug-in submodules;

[0012] The plugin management submodule performs initialization, scheduling, and release operations on its included pluggable submodules;

[0013] The execution order control submodule sets the execution order of each pluggable submodule and sends signals to the corresponding pluggable submodule through the pluggable management submodule to execute the corresponding methods in the pluggable submodule.

[0014] Furthermore, the execution order control submodule sets the execution order of each pluggable submodule through an external LUA script, reads and parses the external script, obtains the method names in the pluggable submodules that need to be executed, and transmits signals to the corresponding pluggable submodules through the pluggable management submodule.

[0015] Furthermore, the method for initializing the program initialization submodule is as follows:

[0016] First, define entity variables for the publish / subscribe class of the model application in the LUA script and perform entity initialization. If physical hardware or semi-physical hardware is added to the experimental system, perform hardware initialization operations in the hardware initialization configuration.

[0017] Secondly, the framework creates business threads to run the test system. It allows the creation of multiple business threads and scans and stores all dynamic library files under the pluggable submodule directory folder in memory. The files are stored in memory using the map function and exist as the main business thread is created and released.

[0018] Finally, determine whether the pluggable submodule is a valid plugin. If it is not a valid plugin, release the dynamic execution library file. If it is a valid plugin, perform the initialization within the plugin, including loading the configuration file, reading the log file, and performing the plugin's state initialization, including the initialization of the defined structure and state variables.

[0019] Furthermore, a pluggable submodule is an application composed of multiple dynamic link libraries, designed according to a unified encoding format, and can be loaded and executed by the main control module; the pluggable program includes a pluggable interaction management unit, a pluggable initialization unit, an interaction service unit, a state initialization unit, a state time evolution unit, and a state update unit;

[0020] The plug-in interaction management unit is used for communication and mutual calling between plug-in sub-modules and the main control module. It receives signals from the plug-in management sub-module in the main control module, sends signals to the plug-in initialization unit, state time evolution unit, and state update unit, and returns the execution results to the main control module.

[0021] The plugin initialization unit is automatically triggered after the plugin submodule is successfully loaded. It initializes and assigns values ​​to memory structure variables and initializes published state variables, subscribed state variables, published remote methods, and subscribed remote methods.

[0022] The interactive service unit uses a proxy-based service to complete remote method publication and remote method subscription; remote method publication is used to register remote method publishers in the middleware network, which receive requests from other remote method subscribers and return the results; remote method subscription is used to actively send requests to remote method publishers and obtain their computation results.

[0023] The state initialization unit is the starting point of the space-time evolution process of the experimental system. It checks the state data frame of the experimental system, assigns the values ​​in the state data frame of the experimental system to the state variables of the object model, and then saves the state variables of the object model as a complete simulation data frame and publishes it.

[0024] After the plugin initialization and state initialization are completed, the state time evolution unit performs internal logic calculations based on the initialized values ​​and sends the calculation results to the state update unit.

[0025] After a state-time evolution is completed, the state update unit saves the variable values ​​as a complete simulation data frame, publishes it to the model subscribers, and uses it as input for the next state-time evolution calculation.

[0026] Furthermore, when the plug-in interaction management unit receives the initialization signal, it sends an enable signal to the plug-in initialization unit and the state initialization unit; when it receives the time evolution signal, it sends an enable signal to the state time evolution unit; and when it receives the state update signal, it sends an enable signal to the state update unit.

[0027] Furthermore, the state initialization unit checks the virtual space state data frame, and the checking methods include integrity check, time deviation calculation, and time evolution confidence threshold check.

[0028] The integrity check ensures that all simulation variables that need to be assigned values ​​can find meaningful data value mappings in the data frame;

[0029] The time deviation calculation check statistically analyzes the deviation between the timestamps of all status values ​​and the latest logical time.

[0030] The time evolution confidence threshold check calculates whether the deviation of the state value exceeds the extrapolation threshold.

[0031] Furthermore, the interactive service unit uses a proxy-based service to publish remote methods. On the remote method publishing end, a thread pool mechanism is used to optimize the efficiency of remote method implementation. The thread pool includes a thread scheduling module and a thread pool module with multiple system threads. When a remote method request arrives at the publishing end, the thread scheduling management module will intelligently distribute the request to an available thread in the thread pool to achieve high-concurrency processing of remote methods.

[0032] Furthermore, the runtime support library also includes third-party runtime libraries.

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

[0034] (1) The present invention provides an aerospace equipment test system based on scripts and plug-ins. It adopts a master-slave framework structure. The master control module realizes the definition and maintenance of basic states such as initialization and time management. The slave control module is a plug-in sub-module. The program defines the implementation logic of the object model. The master and slave control modules are assigned values ​​through LUA scripts to realize the information flow and data interaction coupling relationship between the models.

[0035] (2) The present invention provides an aerospace equipment test system based on scripts and plug-ins. It adopts a combination of LUA scripts and plug-in architecture, and extracts all communication service information between models into LUA scripts. By defining the interaction of models in LUA scripts, different test systems can be constructed.

[0036] (3) The present invention provides an aerospace equipment test system based on scripts and plug-ins, which realizes the assignment and acquisition of attribute values ​​of three types of objects defined in the object model by calling the library file of the object model in the plug-in sub-module. Attached Figure Description

[0037] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0038] Figure 1 This is a schematic diagram of the experimental system composition according to an embodiment of the present invention;

[0039] Figure 2 This is an example diagram of the main control module configuration file in an embodiment of the present invention;

[0040] Figure 3 This is a flowchart of the program initialization process in an embodiment of the present invention;

[0041] Figure 4 This is a schematic diagram illustrating the working principle of the execution sequence control module in an embodiment of the present invention.

[0042] Figure 5 This is a schematic diagram of the working mechanism of the thread pool on the remote method publishing end in an embodiment of the present invention. Detailed Implementation

[0043] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0044] This invention proposes a script- and plugin-based aerospace equipment testing system that integrates model prototypes into a computer application program for the testing system. This program can assemble prototype object models into digital threads that can evolve with logical time in the data space of a virtual test field, solving the problem of aerospace equipment model integration at the application layer, defining the interaction logic of the aerospace equipment model itself, and forming a digital aerospace equipment testing overall model composed of a large number of cross-domain, heterogeneous prototypes and test equipment.

[0045] The aerospace equipment testing system includes a main control module, slave control modules, and an operation support library. The system model framework is as follows: Figure 1 As shown, the main control module is the master program, the slave control modules are slave programs, and the pluggable submodules are pluggable programs. A complete experiment consists of multiple experimental applications, each of which consists of a main control module, multiple slave control modules, and a runtime support library.

[0046] (1) Main control module

[0047] The main control module is the entry point of the experimental system model framework and the core of the entire framework; it can be run directly. In experimental applications, only one main control module is allowed, and this main control module must exist within the experimental model framework. The main control module consists of four sub-functional modules: configuration management, program initialization, plugin management, and execution order control.

[0048] The configuration management submodule reads external configuration files and saves the relevant parameter configurations to memory for use by other modules within the application. Considering application scenarios and scalability requirements, XML format is used as the encoding format for the configuration files. Figure 2 The image shown is a specific example of a configuration file.

[0049] The program initialization submodule executes LUA scripts to initialize the internal variables of the main control module; request and create computer resources; initialize the included plug-in submodules; and coordinate the normal startup of each plug-in function. Figure 3 The program initialization flowchart first defines entity variables for the publish / subscribe class of the model application in the LUA script, performing entity initialization. If physical or semi-physical hardware is added to the experimental system, hardware initialization is performed in the hardware initialization configuration. Second, business threads that execute the experimental system are created. The framework allows the creation of multiple business threads and scans and stores all dynamic library files under the pluggable submodule directory folder in memory using the map function, existing with the creation and release of the main business thread. Finally, it determines whether the pluggable submodule is a valid pluggable. If not, the dynamic execution library files are released; if valid, the pluggable initialization is performed, including loading configuration files, reading log files, and performing state initialization, including defining structure initialization and state variable initialization. These tasks are fundamental to the normal operation of the application. During program initialization, developers need to carefully consider the collaboration and dependencies between various functional modules to ensure the application can run stably under different environments and conditions. For example, in the process of requesting and creating computer resources, the differences between different operating systems and hardware platforms, as well as the actual needs and performance requirements of the application, need to be considered. During the loading and startup of plug-in submodules, it is necessary to consider issues such as the dependencies between plug-ins, the startup order, and error handling mechanisms.

[0050] The plug-in management submodule is used to process all external plug-in submodules corresponding to the main control module, including initialization, scheduling and release of the included plug-in submodules.

[0051] The execution order control submodule manages the execution order of business functions. This submodule supports parsing external scripting languages ​​and executing them sequentially according to the functions described in the scripting languages, strictly following the order. It uses Lua as the syntax for the external scripting language, which has rich function definition capabilities, allowing the definition of various methods within the execution plug-in submodules, such as... Figure 4 The diagram illustrates the working principle of the execution order control module. First, it reads the external scripting language and parses its content to obtain the method names from the pluggable submodules to be executed. Next, the execution order control module transmits signals to the corresponding pluggable interaction management module through the pluggable management module, ultimately executing the corresponding method in the pluggable submodule. Furthermore, the execution order control module possesses many advanced features, such as execution priority control and exception handling, to ensure the stability and efficiency of the program.

[0052] (2) Plug-in submodules

[0053] A pluggable submodule is an application composed of multiple dynamic link libraries. Designed according to a unified coding format, it can be loaded by the main control module and execute its internal functions. A complete experimental application can contain multiple pluggable submodules. The functions of these pluggable submodules are independent of each other and do not interfere with each other, working together to complete the experimental process.

[0054] The plug-in submodule includes multiple units such as plug-in interaction management, plug-in initialization, interaction service, state initialization, state time evolution, and state update.

[0055] The plug-in interaction management unit is used for communication and mutual calls between pluggable submodules and the main control module. It is responsible for receiving signals from the plug-in management in the main control module. Upon receiving an initialization signal, the plug-in interaction management unit will execute the plug-in initialization and state initialization functions within the pluggable submodule; upon receiving a time evolution signal, the plug-in interaction management unit will execute the state time evolution function within the pluggable submodule; upon receiving a state update signal, the plug-in interaction management unit will execute the state update function within the pluggable submodule.

[0056] The plugin initialization unit is automatically triggered after the plugin is successfully loaded, and performs the following key functions: 1) Executes the initialization and assignment of memory variables to ensure that all variables in the plugin are correctly initialized and assigned values; 2) Publishes the initialization of VIO state variables to ensure that they can be accessed and used by other plugins; 3) Subscribes to the initialization of VIO state variables to ensure that it can receive variable values ​​published by other plugins; 4) Publishes the initialization of remote methods to ensure that the method can be accessed and called by other plugins; 5) Subscribes to the initialization of remote methods to ensure that it can receive method call requests published by other plugins.

[0057] The interactive service unit employs proxy-based service technology to implement and optimize the scheduling of remote method functionalities. The implementations of these remote methods are distributed across other applications and returned to remote method subscribers via network transmission. Interactive service architecture takes two forms: remote method publication and remote method subscription. Remote method publication involves registering a remote method publisher in the middleware network. This publisher can receive requests from other remote method subscribers and return the results. Remote method subscription is used to actively request from the remote method publisher and obtain its computation results. To optimize the efficiency of remote method implementation, a thread pool mechanism is used on the remote method publisher, such as... Figure 5The diagram shows the working block of the thread pool on the remote method publishing end. This mechanism includes a thread scheduling module and a thread pool module with multiple system threads. When a remote method request arrives at the publishing end, the thread scheduling module intelligently distributes the request to an available thread in the thread pool, thereby achieving high-concurrency processing of remote methods. This design not only improves the system's parallel computing capabilities but also effectively avoids resource contention and thread blocking, thus optimizing overall performance and response speed.

[0058] The state initialization unit is the starting point for the spatial-temporal evolution of the experimental system, comprising two parts: checking the experimental system state data frame and assigning state values ​​to the object model. Checking the experimental system state data frame involves performing integrity checks, time deviation calculations, and time evolution confidence threshold checks on the latest state frame in the experimental system space to ensure that the logical time evolution has correct premises. The integrity check ensures that all simulation variables requiring assignment can find meaningful data value mappings in the data frame; the time deviation calculation statistically analyzes the deviation between all state value timestamps and the latest logical time; the time evolution confidence threshold check checks whether the calculated state value deviation exceeds an extrapolation threshold. The object model state assignment process assigns the values ​​from the experimental system's state data frame to the object model's state variables.

[0059] After the plugin initialization and state initialization are completed, the state time evolution unit performs internal logic calculations based on the initialized values, and then gives the results to the state update unit.

[0060] After a state-time evolution is completed, the state update unit saves the variable values ​​as a complete simulation data frame, publishes it to the model subscribers, and uses it as input for the next state-time evolution calculation.

[0061] Publishing simulation data frames is a crucial step in ensuring the continuity and integrity of the simulation process, and also an important guarantee for the reliability of simulation results. When saving simulation data frames, attention must be paid to their structure and content to ensure their integrity and readability. Furthermore, before publishing the data frames, necessary checks and verifications must be performed to ensure their correctness and consistency. These measures ensure the accuracy and reliability of the simulation results, providing strong support for subsequent simulation analysis and decision-making.

[0062] (3) Run support library

[0063] The runtime support library provides business support for pluggable submodules, including an object model (VOM) library, remote method implementations, and third-party runtime library components. The definition of the object model is found in the patent "A Method for Automatic Code Generation of a Virtual Experiment Distributed Object Model Framework" (201210429079.0). The implementations of remote methods are defined in the object model, and their implementation logic needs to be added to the object model. The framework supports referencing third-party runtime libraries based on C / C++ to achieve richer functionality.

[0064] This invention is the foundational framework of a distributed simulation support architecture, an application program running on an integrated support platform, used to integrate various component modules of aerospace equipment in digital space. This experimental system establishes bridges between the framework and the model, and between the framework and the communication middleware, enabling communication between subsystem models. Simultaneously, users can add specific application logic to the model framework to achieve interaction between models. Through the basic model framework, the various subsystems are integrated into a whole, interconnecting the subsystems of the aerospace equipment to form a complete digital equipment model.

[0065] The embodiments described above are merely preferred embodiments of the present invention. Ordinary variations and substitutions made by those skilled in the art within the scope of the technical solution of the present invention should be included within the protection scope of the present invention.

Claims

1. A script- and plugin-based aerospace equipment testing system, characterized in that, It includes a main control module, multiple slave control modules, and a runtime support library; Each control module is a pluggable submodule designed according to a unified coding format. The pluggable submodule defines the implementation logic of the object model. After being loaded, it executes its internal functions by calling the object model in the runtime support library. A pluggable submodule is an application composed of multiple dynamic link libraries, designed according to a unified encoding format, and can be loaded and executed by the main control module based on external LUA scripts. A pluggable submodule includes a pluggable interaction management unit, a pluggable initialization unit, an interaction service unit, a state initialization unit, a state time evolution unit, and a state update unit. The plug-in interaction management unit is used for communication and mutual calling between plug-in sub-modules and the main control module. It receives signals from the plug-in management sub-module in the main control module, sends signals to the plug-in initialization unit, state time evolution unit, and state update unit, and returns the execution results to the main control module. The plugin initialization unit is automatically triggered after the plugin submodule is successfully loaded. It initializes and assigns values ​​to memory structure variables and initializes published state variables, subscribed state variables, published remote methods, and subscribed remote methods. The interactive service unit uses a proxy-based service to complete remote method publication and remote method subscription; Remote method publication is used to register remote method publishers in the middleware network. The publisher receives requests from other remote method subscribers and returns the results. Remote method subscription is used to actively send requests to remote method publishers and obtain their computation results. The state initialization unit is the starting point of the space-time evolution process of the experimental system. It checks the state data frame of the experimental system, assigns the values ​​in the state data frame of the experimental system to the state variables of the object model, and then saves the state variables of the object model as a complete simulation data frame and publishes it. After the plugin initialization and state initialization are completed, the state time evolution unit performs internal logic calculations based on the initialized values ​​and sends the calculation results to the state update unit. After a state-time evolution is completed, the state update unit saves the variable values ​​as a complete simulation data frame, publishes it to the model subscribers, and uses it as input for the next state-time evolution calculation. The main control module reads external configuration parameters and assigns values ​​to the internal variables of each plug-in submodule, loads all plug-in submodules, and controls the corresponding plug-in submodules to be executed in sequence according to the set execution order. The runtime support library provides an object model library for each plug-in submodule. The objects defined in the object model include messages, state distribution objects, and remote methods.

2. The aerospace equipment testing system based on scripts and plugins according to claim 1, characterized in that, The main control module includes a configuration management submodule, a program initialization submodule, a plug-in management submodule, and an execution order control submodule; The configuration management submodule reads external configuration files and saves the configuration parameters from those files. The program initialization submodule initializes internal variables, requests and creates computer resources, and loads all plug-in submodules; The plug-in management submodule performs initialization, scheduling, and release operations on the plug-in submodules it manages; The execution order control submodule sets the execution order of each pluggable submodule and sends signals to the corresponding pluggable submodule through the pluggable management submodule to execute the corresponding methods in the pluggable submodule.

3. The aerospace equipment testing system based on scripts and plugins according to claim 2, characterized in that, The execution order control submodule sets the execution order of each pluggable submodule through an external LUA script, reads and parses the external script, obtains the method names in the pluggable submodules that need to be executed, and passes signals to the corresponding pluggable submodules through the pluggable management submodule.

4. The aerospace equipment testing system based on scripts and plugins according to claim 2, characterized in that, The method for initializing the program initialization submodule is as follows: First, define entity variables for the publish / subscribe class of the model application in the LUA script and perform entity initialization. If physical hardware or semi-physical hardware is added to the experimental system, perform hardware initialization operations in the hardware initialization configuration. Secondly, create business threads to run the test system, allowing the creation of multiple business threads, and scan and store all dynamic library files under the pluggable submodule directory folder in memory. The files are stored in memory using the map function and exist as the main business thread is created and released. Finally, determine whether the pluggable submodule is a valid plugin. If it is not a valid plugin, release the dynamic execution library file. If it is a valid plugin, perform the initialization within the plugin, including loading the configuration file, reading the log file, and performing the plugin's state initialization, including the initialization of the defined structure and state variables.

5. The aerospace equipment testing system based on scripts and plugins according to claim 1, characterized in that, When the plug-in interaction management unit receives the initialization signal, it sends an enable signal to the plug-in initialization unit and the state initialization unit; when it receives the time evolution signal, it sends an enable signal to the state time evolution unit; when it receives the state update signal, it sends an enable signal to the state update unit.

6. The aerospace equipment testing system based on scripts and plugins according to claim 1, characterized in that, The state initialization unit checks the virtual space state data frame, and the checking methods include integrity check, time deviation calculation, and time evolution confidence threshold check. The integrity check ensures that all simulation variables that need to be assigned values ​​can find meaningful data value mappings in the data frame; The time deviation calculation check statistically analyzes the deviation between the timestamps of all status values ​​and the latest logical time. The time evolution confidence threshold check calculates whether the deviation of the state value exceeds the extrapolation threshold.

7. The aerospace equipment testing system based on scripts and plugins according to claim 1, characterized in that, The interactive service unit uses a proxy-based service to publish remote methods. On the remote method publishing end, a thread pool mechanism is used to optimize the efficiency of remote method implementation. The thread pool includes a thread scheduling module and a thread pool module with multiple system threads. When a remote method request arrives at the publishing end, the thread scheduling management module will intelligently distribute the request to an available thread in the thread pool to achieve high-concurrency processing of remote methods.

8. The aerospace equipment testing system based on scripts and plugins according to claim 1, characterized in that, The runtime support library also includes third-party runtime libraries.

Images