Flight control ICD protocol simulation verification system based on virtual modeling and flight control system

Abstract

The application provides a virtual modeling-based flight control ICD protocol simulation verification system and a flight control system, comprising a network topology modeling module, a virtual bus modeling service module, an ICD modeling service module, a processing algorithm modeling service module and an ICD simulation running monitoring module, and each module cooperatively realizes a full-process closed loop from ICD analysis to virtual bus simulation verification. The application completes network construction of the system by simulating the commonly used system network bus in the design stage, and in combination with the data processing algorithm, the business data interaction between the system nodes can be simulated in the system design front end, the ICD design problem is identified, the compatibility verification of the ICD and the hardware bus interface is completed in the design front end, the rework waste caused by the design mismatch problem is reduced, and the reliability and delivery efficiency of the system are improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of flight control systems, in particular to a flight control ICD protocol simulation verification system based on virtual modeling and a flight control system. BACKGROUND

[0002] As the core control unit of aviation equipment, the matching degree of the interface control document (ICD) and the hardware bus interface of the flight control system directly determines the reliability, real-time performance and compatibility of the system, and is a key link to ensure the integration efficiency of the system in the development of aviation equipment. At present, with the increasing complexity of aviation equipment functions, the types of communication buses involved in the flight control system are increasingly diverse, including TTP, 1553B, CAN, 1394B, TTE and other special buses. The communication mechanisms, interface parameters and data transmission protocols of different buses are significantly different, further increasing the difficulty of matching and verifying the ICD and the hardware bus interface.

[0003] The existing flight control ICD design and verification technology has obvious limitations, mainly in the following three aspects:

[0004] 1. Verification timing lag: Current ICD design work is mostly concentrated in the system design stage, which can only carry out simple interface sending and receiving logic verification without considering the characteristics of hardware networking. Complete ICD and hardware bus interface coupling integration verification must wait until the software coding is implemented and combined with actual hardware equipment, resulting in a serious lag in the verification link compared to the design link.

[0005] 2. High cost of problem modification: If the ICD design and hardware bus interface are found to be incompatible (such as bus rate incompatibility, data frame format error, node communication logic conflict, etc.) in the later integration verification stage, the ICD design scheme needs to be modified, the software needs to be re-coded and debugged, and the hardware integration test needs to be carried out again, which not only greatly prolongs the development cycle, but also causes a huge waste of manpower, material resources and time.

[0006] 3. Poor verification flexibility and reusability: The existing verification method highly depends on actual hardware resources. When complex scenarios involving multiple bus types and multiple node topologies need to be verified, corresponding physical hardware environments need to be built, which requires a large investment in hardware resources and has low scenario switching efficiency. At the same time, the test components formed in the verification process lack standardized design and cannot be reused in the ICD verification of different types of flight control systems, resulting in repeated environment building for similar verification work and low development efficiency.

[0007] In summary, the existing technology cannot meet the needs of efficient, low-cost and highly reusable verification of ICD and hardware bus interface in the early stage of flight control system design, and there is an urgent need for a flight control ICD protocol simulation verification scheme based on virtual modeling to fill the verification gap between the design stage and the hardware integration stage. SUMMARY

[0008] In view of the defects in the prior art, the present application aims to provide a flight control ICD protocol simulation verification system based on virtual modeling and a flight control system.

[0009] The flight control ICD protocol simulation verification system based on virtual modeling comprises a network topology modeling module, a virtual bus modeling service module, an ICD modeling service module, a processing algorithm modeling service module and an ICD simulation running monitoring module.

[0010] The network topology modeling module is used to construct a flight control system network framework to provide a basic carrier for simulation verification.

[0011] The virtual bus modeling service module is used to shield physical bus implementation details and reproduce real bus communication logic in a virtual environment.

[0012] The ICD modeling service module is used to design ICD formats and generate logic and define data transmission rules between nodes.

[0013] The processing algorithm modeling service module is used to define ICD data processing rules to realize data analysis and forwarding.

[0014] The network topology modeling module transmits topology configuration data to the virtual bus modeling service module and the ICD modeling service module; the ICD modeling service module transmits ICD configuration data and generated data to the processing algorithm modeling service module and a data layer; the processing algorithm modeling service module transmits algorithm configuration data and processed data to the ICD simulation running monitoring module and the data layer; and the ICD simulation running monitoring module transmits monitoring data and analysis results to the data layer for saving.

[0015] Preferably, the network topology modeling module comprises:

[0016] A graphical modeling interface is provided to support automatic generation of an initialization topology graph by setting the number of simulation nodes and the type of communication bus.

[0017] The graphical modeling interface supports dynamic editing of communication connection relationships and communication interface types for each simulation node and has a self-checking function to check the consistency of bus interface interaction types and parameter configurations between nodes and trigger an error prompt when the bus parameters between nodes do not match.

[0018] The network topology modeling result is saved in an XML format, and the XML format supports cross-platform editing and can be modified offline or imported into other simulation systems of the same type.

[0019] Preferably, the toolbar of the graphical modeling interface is pre-provisioned with typical business network topology graphs to support direct reuse.

[0020] Preferably, the virtual bus modeling service module comprises:

[0021] The underlying layer adopts DDS distributed bus, shields the internal implementation logic of the commonly used communication bus of the flight control, and completes bus communication transceiver mechanism simulation through configuration of external parameters, and the communication configuration is consistent with the physical bus;

[0022] Supports configuration of port rate, working mode, node ID, and node IP interface parameters of the selected bus, and the graphical editing components provided by the encapsulation library are integrated in the bus type menu bar of the network topology modeling interface as modeling interface type options;

[0023] Adopts a description mode combining XML configuration and dynamic library, and when a new bus type is added, the new bus type implementation file encapsulated according to the specified interface is placed in a fixed directory, so that dynamic upgrading of the bus type can be completed without modification of the system core code.

[0024] Preferably, the ICD modeling service module comprises:

[0025] Provides a graphical ICD modeling interface, supports dynamic creation of ICD types and formats, and can import and export ICD files in XML, TXT, CSV, and Excel formats;

[0026] Supports addition of frame protocols, and provides three ICD data field filling modes, namely fixed filling, file filling, and algorithm filling.

[0027] Preferably, the ICD field generation field triggering mechanism comprises event triggering and timing triggering, the ICD field can be configured with a frame header, a frame tail, and a frame identifier, supports dynamic configuration of integer and floating point data types and endianness, and the number of protocol parameters, the field length, and the byte order can be flexibly adjusted;

[0028] Provides an ICD field automatic generation function based on standard algorithms, random algorithms, or user-defined algorithms, supports dynamic business binding of interface models and protocol models, and bus interaction data stream configuration.

[0029] Preferably, the processing algorithm modeling service module comprises:

[0030] Built-in typical business data processing algorithm library, including data filtering algorithms and checksum calculation algorithms, and users can select ICD data processing algorithms corresponding to bus interfaces according to business processing unit names;

[0031] Supports binding of dynamic data processing algorithms and Simulink model processing to complete bus transceiver ICD data processing;

[0032] The processing algorithm running service is provided, and the selected processing algorithm can be bound with the configured bus interface, and the processing and forwarding of ICD data are completed according to the sending and receiving settings of the bus interface.

[0033] Preferably, the ICD simulation running monitoring module comprises:

[0034] The network topology structure, node communication interface, interface ICD format and interface data processing algorithm based on configuration are supported, the processing algorithm is loaded, the virtual bus data sending and receiving are activated, and the service scene data interaction verification is started according to the set ICD data or ICD data trigger generation mechanism;

[0035] The data communication monitoring function and configuration display interface are provided, the data can be viewed according to the 'node-interface-ICD' tree structure, and the data can be parsed according to the service format to locate the problem.

[0036] The simulation data is locally saved and played back according to the time dimension, the data interaction process can be traced back without re-running the simulation, and the problem cause analysis is used.

[0037] According to the flight control system provided by the application, the flight control ICD protocol simulation verification system based on virtual modeling is adopted.

[0038] Compared with the prior art, the application has the following beneficial effects:

[0039] 1、The application completes the network construction of the system by virtually simulating the commonly used system network bus in the design stage, and the data processing algorithm is combined, so that the business data interaction between the system nodes can be simulated in the front end of the system design, the ICD design problem is identified, the compatibility verification of the ICD and the hardware bus interface is completed in the front end of the design, the waste caused by the rework due to the design mismatch problem is reduced, and the reliability and delivery efficiency of the system are improved.

[0040] 2、The application can complete the data interaction design verification of a large complex system in a single machine or a distributed network by the plug-and-play simulation characteristics of the distributed simulation bus, reduces the configuration management cost of complex networking, and saves the manpower and time cost.

[0041] 3、The application can quickly complete the matching degree verification of the ICD and the physical bus in the early design stage by shielding the bus implementation details and simulating the bus data transmission function, identifies the problem as early as possible, and reduces the time cost waste caused by the modification design in the later stage.

[0042] 4、The application completes the design and verification process of the entire ICD by the graphical modeling method, can form a standardized consumable virtual bus verification component, and is convenient for subsequent regression and same model design verification consumption. DETAILED DESCRIPTION

[0043] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0044] Fig. 1 This is a diagram illustrating the implementation architecture of the simulation verification system in this invention.

[0045] Fig. 2 This is a functional block diagram of the simulation verification system in this invention;

[0046] Fig. 3 This is a flowchart illustrating the usage of the simulation verification system in this invention. Detailed Implementation

[0047] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the protection scope of the present invention.

[0048] This invention proposes a flight control ICD protocol simulation and verification system based on virtual modeling. By constructing a fully virtual bus environment and a standardized verification process, it achieves efficient verification during the design phase. The following details the specific technical aspects:

[0049] Reference Figs. 1-3 The core architecture of this invention comprises five functional modules, which work together to achieve a closed-loop process from ICD analysis to virtual bus simulation verification, specifically including:

[0050] 1. Network Topology Modeling Module; This module is the foundation of the entire simulation verification, responsible for building the network framework of the flight control system and providing a "carrier" for subsequent bus simulation and ICD verification. Specifically, it includes:

[0051] Graphical modeling interface design: Provides a graphical modeling interface that can automatically generate an initial topology diagram by setting the number of simulation nodes and the type of communication bus (such as TTP, 1553B, etc.). It also supports the quick reuse of typical business network topology diagrams (such as dual-redundant bus topology) in the modeling menu toolbar, eliminating the need for repeated drawing and improving modeling efficiency through direct reuse.

[0052] Dynamic configuration and self-verification: Supports dynamic editing of communication connection relationships (such as whether node A and node B are directly connected) and communication interface types (such as CAN interface or 1394B interface) for each node. It also features a self-verification function to check the correctness of bus interface interaction types and parameter configurations between nodes. For example, if node A's bus rate is 1Mbps, node B must match the same rate; otherwise, an error message will be displayed.

[0053] Data format and compatibility: The network topology modeling results are saved in XML format, which is cross-platform and easy to edit. Engineers can modify the XML file offline using Notepad or professional tools, or directly import it into other simulation systems of the same type to improve data reusability.

[0054] 2. Virtual bus modeling service module: This module takes the framework of the network topology module and reproduces the communication logic of the real bus in a virtual environment by shielding the implementation details of the physical bus, solving the problem of "relying on hardware for verification".

[0055] Underlying bus selection and logic shielding: The underlying DDS distributed bus is used to shield the internal implementation logic of common flight control communication buses such as TTP, 1553B, and CAN. Engineers do not need to understand the internal principles of the bus, but only need to configure external parameters. The bus configuration parsing simulation, routing exchange forwarding, and other communication mechanisms are consistent with the physical bus communication configuration.

[0056] Parameter configuration consistency guarantee: Supports configuring interface parameters such as port rate, working mode, node ID, and node IP of the selected bus to ensure consistency with the real physical configuration. The graphical editing components provided by the encapsulation library are displayed in the bus type menu bar of the network topology modeling interface and used as modeling interface types.

[0057] Dynamic expansion capability: The virtual bus encapsulation library uses a combination of XML configuration and dynamic library description. If a new bus type needs to be added, the completed new bus type encapsulation implementation in the specified directory can be used to dynamically upgrade and expand the bus type without modifying the core code, reducing the upgrade cost.

[0058] 3. ICD modeling service module: This module is responsible for designing the format and generation logic of ICD (Interface Control Document), clearly defining "what data is transmitted between nodes and in what format", and is the key to connecting virtual buses and business data.

[0059] Multi-format compatibility and flexible modeling: Provides a graphical ICD modeling interface that supports dynamic creation of ICD types and formats, can import and export ICD files in XML, TXT, CSV, excel formats, supports adding frame protocols (using templates or customizing), and provides three data filling field methods: fixed filling, file filling, and algorithm filling.

[0060] ICD generation field triggering mechanism includes event triggering and timing triggering. ICD fields can be configured with frame header, frame tail, frame identifier, support multiple data types such as integer and floating point, and size-end dynamic configuration, and the number of protocol parameters, field length, byte order, etc. can be flexibly configured.

[0061] ICD field automatic generation algorithm based on standard algorithm, random algorithm or user-defined algorithm is provided; dynamic service binding of interface model and protocol model (for performing protocol data generation and analysis under the interface) and bus interaction data stream configuration (defining the frame protocol data of each interface transceiving) are supported.

[0062] 4. Processing algorithm modeling service module; the module is responsible for defining the processing rules of ICD data, solving the problem of "how data is parsed and forwarded in the virtual bus", and ensuring that the simulation data meets the actual business requirements.

[0063] Algorithm library and flexible selection: a typical business data processing algorithm library (such as data filtering algorithm, checksum calculation algorithm) is provided, and users can select the ICD data processing algorithm of the bus interface according to the business processing unit name.

[0064] Algorithm and interface binding: dynamic data processing algorithm and Simulink model processing are supported to complete the bus transceiving ICD data processing; at the same time, running services are provided to bind the processing algorithm and the set bus interface (such as binding "attitude data filtering algorithm" with node 1 CAN interface), and complete ICD data processing and forwarding according to the configured transceiving settings.

[0065] 5. ICD simulation running monitoring module; the module is the final link of simulation verification, responsible for starting the simulation process, monitoring data interaction, analyzing verification results, and providing "problem positioning" and "after-the-fact review" basis for engineers.

[0066] Simulation process start: based on the configured network topology structure, node communication interface, interface ICD format, and interface data processing algorithm, the data interaction verification of the business scenario is completed. According to the configured data flow forwarding mode, the virtual bus data transceiving is activated by loading the processing algorithm, and the ICD data is generated according to the set ICD data or ICD data trigger generation mechanism, and the simulation process is started.

[0067] Data monitoring and analysis: data communication monitoring function and configuration display interface are provided, data can be viewed according to "node-interface-ICD" tree structure, and data analysis (displayed according to business format to facilitate problem positioning) is supported.

[0068] Data saving and playback: local data saving and time simulation playback are supported at the same time, which is convenient for simulation post-analysis. Engineers do not need to run the simulation again to trace back the entire process and analyze the problem cause (such as positioning the specific time point of "data packet loss" occurrence), saving the review time.

[0069] The entire process does not need to rely on actual hardware, and the compatibility verification of ICD and bus interface can be completed in the design stage, greatly reducing the later rework cost.

[0070] Those skilled in the art understand that, in addition to implementing the system provided by the present application and each device, module and unit thereof in the form of pure computer readable program code, the system provided by the present application and each device, module and unit thereof can also be implemented in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers and embedded microcontrollers, etc. by logically programming the method steps to achieve the same functions. Therefore, the system provided by the present application and each device, module and unit thereof can be considered as a hardware component, and the devices, modules and units included therein for implementing various functions can also be considered as structures within the hardware component; the devices, modules and units for implementing various functions can also be considered as both software modules implementing methods and structures within hardware components.

[0071] The specific embodiments of the present application are described above. It needs to be understood that the present application is not limited to the specific embodiments described above, and various changes or modifications can be made by those skilled in the art within the scope of the claims, which does not affect the essential content of the present application. The embodiments of the present application and the features in the embodiments can be combined with each other in any manner without conflict.

Claims

1. A virtual modeling based flight control ICD protocol simulation verification system, characterized in that, The application relates to a network topology modeling module, a virtual bus modeling service module, an ICD modeling service module, a processing algorithm modeling service module and an ICD simulation running monitoring module. The network topology modeling module is used for constructing a flight control system network framework to provide a basic carrier for simulation verification. The virtual bus modeling service module is used for shielding physical bus implementation details and reproducing real bus communication logic in a virtual environment. The ICD modeling service module is used for designing ICD formats and generating logic and defining data transmission rules between nodes. The processing algorithm modeling service module is used for defining ICD data processing rules, realizing data analysis and forwarding. The network topology modeling module transmits topology configuration data to the virtual bus modeling service module and the ICD modeling service module; the ICD modeling service module transmits ICD configuration data and generated data to the processing algorithm modeling service module and a data layer; the processing algorithm modeling service module transmits algorithm configuration data and processed data to the ICD simulation running monitoring module and the data layer; and the ICD simulation running monitoring module transmits monitoring data and analysis results to the data layer for storage. The ICD simulation running monitoring module comprises: Supporting a network topology structure based on completed configuration, node communication interfaces, interface ICD formats and interface data processing algorithms, loading processing algorithms and activating virtual bus data transmission, starting business scene data interaction verification according to a set ICD data or ICD data trigger generation mechanism; Providing data communication monitoring functions and configuration display interfaces, supporting data viewing according to a "node-interface-ICD" tree structure and data analysis according to a business format to locate problems; Supporting simulation data local storage and simulation playback according to a time dimension, without re-running simulation to trace data interaction processes for problem cause analysis. The network topology modeling module comprises: Providing a graphical modeling interface, supporting automatic generation of an initialization topology graph by setting simulation node numbers and communication bus types; 2. The virtual modeling based fly control ICD protocol simulation verification system according to claim 1, wherein, Supporting dynamic editing of communication connection relationships and communication interface types for each simulation node and having a self-checking function to check the consistency of bus interface interaction types and parameter configurations between nodes and triggering an error prompt when bus parameters between nodes do not match; Saving network topology modeling results in an XML format, wherein the XML format supports cross-platform editing and can be modified offline or imported into other simulation systems of the same type. A toolbar of the graphical modeling interface is preset with typical business network topology graphs, and direct reuse is supported. The virtual bus modeling service module comprises:

3. The virtual modeling based fly control ICD protocol simulation verification system according to claim 2, wherein, An underlying DDS distributed bus is adopted to shield internal implementation logic of a flight control physical bus, bus communication transceiver mechanism simulation is completed by configuring external parameters, and communication configuration is consistent with the physical bus; 4. The virtual modeling based fly control ICD protocol simulation verification system according to claim 1, wherein, Port rates, working modes, node IDs and node IP interface parameters of selected buses are supported to be configured, graphical editing components provided by an encapsulation library are integrated in a bus type menu bar of the network topology modeling interface as modeling interface type options; and ​ ​ The XML configuration is combined with the dynamic library to describe the mode, the new bus type implementation file is put into a fixed directory according to the prescribed interface encapsulation when a bus type is added, and thus the bus type dynamic upgrade can be completed without modifying the system core code.

5. The virtual modeling based fly control ICD protocol simulation verification system according to claim 1, wherein, The ICD modeling service module comprises: A graphical ICD modeling interface is provided, dynamic creation of ICD types and formats is supported, and ICD files in XML, TXT, CSV and Excel formats can be imported and exported; Frame protocol adding is supported, and three ICD data field filling modes, i.e., fixed filling, file filling and algorithm filling, are provided.

6. The virtual modeling based fly control ICD protocol simulation verification system according to claim 5, wherein, Further comprising: An ICD generation field triggering mechanism comprises event triggering and timing triggering, ICD fields can be configured with frame headers, frame tails and frame identifiers, support integer and floating point data types and dynamic configuration of big and little ends, and protocol parameter quantity, field length and byte sequence can be flexibly adjusted; An ICD field automatic generation function based on standard algorithms, random algorithms or user-defined algorithms is provided, dynamic business binding of interface models and protocol models is supported, and bus interaction data stream configuration is provided.

7. The virtual modeling based fly control ICD protocol simulation verification system according to claim 1, wherein, The processing algorithm modeling service module comprises: A typical business data processing algorithm library is built-in, including data filtering algorithms and checksum calculation algorithms, and users can select ICD data processing algorithms corresponding to bus interfaces according to business processing unit names; Dynamic data processing algorithms are bound to Simulink model processing to complete bus transceiving ICD data processing; A processing algorithm running service is provided, selected processing algorithms can be bound to configured bus interfaces, and ICD data processing and forwarding can be completed according to bus interface transceiving settings.

8. A flight control system, characterized by The flight control ICD protocol simulation verification system based on virtual modeling.

Images