An assembly type multi-source bus data efficient processing system

Abstract

This invention discloses an assemblable, multi-source bus data high-efficiency processing system, comprising: a bus data configuration module for configuring bus type, bus messages, bus parameters, and calculation formulas, and storing the configuration information in a database; a message parsing thread creation module for retrieving configuration information from the database, creating message parsing threads based on message IDs to form a parsing thread pool, and creating and maintaining a hash table between message IDs and message parsing threads; and a bus data parsing module for retrieving configuration information from the database, parsing external experimental data based on the configuration information, and outputting a text file. This invention achieves flexible configuration and rapid response in data processing.

Description

Technical Field

[0001] This invention relates to an assemblable, multi-source bus data high-efficiency processing system, belonging to the field of bus data processing technology in the aerospace industry. Background Technology

[0002] After each test of a spacecraft model, the data stored in the memory or received by the testing station needs to be analyzed so that personnel from various disciplines such as attitude control, guidance, propulsion, and structure can interpret it. The interpretation results are an important basis for analyzing and judging the success or failure of the test.

[0003] However, faced with increasingly complex aerospace system architectures and explosively growing data volumes, existing bus data processing technologies have gradually revealed the following significant shortcomings in engineering practice, making it difficult to meet current development needs for high efficiency, flexibility, and independent control: 1. Traditional parsing methods are inefficient and struggle to handle the challenges of massive amounts of data. Aerospace bus data is characterized by large data volume, high transmission rate, and long duration. Existing technologies mostly employ serial processing or simple single-threaded modes, lacking effective parallel computing mechanisms, resulting in excessively long data processing times and severely slowing down post-experiment analysis cycles. Furthermore, most existing software does not adopt a pipelined architecture; data filtering, delivery, and parsing are tightly coupled, making it impossible to achieve parallel operation of each stage, further limiting the overall throughput.

[0004] 2. The software has a high degree of coupling, making it difficult to adapt to complex and ever-changing business needs. Aerospace systems are vast, with significant differences in communication protocols between different units and subsystems. Furthermore, the bus frame format, parameter definitions, and calculation formulas frequently change across different launches of the same model. Existing processing software typically hard-codes frame formats, data types, and specific physical quantity conversion formulas within the program. This "siloed" development model results in extremely poor software flexibility: encountering a new bus protocol or modifying the calculation formula for a parameter necessitates rewriting the source code, compiling, or even completely refactoring the software. This not only leads to long development cycles and high maintenance costs but also easily introduces new errors, making it unsuitable for the "multi-variety, small-batch, rapid-iteration" characteristics of aerospace missions.

[0005] 3. Low functional module reuse rate and serious duplication of construction. Due to the lack of a unified data abstraction layer and modular design philosophy, existing data processing software is often "one-off" software tailored to specific models or missions. When new missions arrive, even if the core processing logic is similar, developers need to repeatedly write a large amount of code, making it impossible to effectively reuse existing mature functional modules. This low-level duplication of development not only wastes valuable human resources but also leads to inconsistent software quality, hindering the accumulation and inheritance of knowledge, and restricting the improvement of aerospace software engineering standards.

[0006] 4. Poor scalability, making it difficult to integrate new algorithms. With the advancement of aerospace technology, the mathematical models for parameter processing are becoming increasingly complex. Existing software architectures typically lack standardized plug-in interfaces, and adding a new type of processing formula often requires a deep understanding of the underlying code logic and intrusive modifications. This closed architecture makes the development of new features difficult and risky, and hinders the rapid response to researchers' needs for verifying new data processing algorithms.

[0007] 5. Weak cross-platform capabilities pose potential risks to independent controllability. Currently, some data processing tools rely on specific commercial operating systems or non-domestic development environments, which not only pose information security risks but also make it difficult to meet the strategic requirements of fully domestic software operating platforms in the future aerospace field. Existing technologies do not adequately consider cross-platform adaptability and lack the ability to "code once, run on multiple platforms," ​​resulting in high software migration costs and limiting their widespread application in different hardware environments.

[0008] In summary, current bus data processing technologies in the aerospace field suffer from drawbacks such as low processing efficiency, poor configuration flexibility, low software reusability, difficulty in expansion and maintenance, and weak cross-platform capabilities. There is an urgent need to develop a high-efficiency multi-source bus data processing system that features assemblability, supports dynamic plug-in loading, and employs pipelined and multi-threaded parallel mechanisms to address these technical challenges and improve the timeliness and accuracy of aerospace model data interpretation. Summary of the Invention

[0009] The technical problem solved by this invention is to overcome the shortcomings of the prior art and provide an assemblable multi-source bus data high-efficiency processing system that realizes flexible configuration and fast response of data processing.

[0010] The technical solution of this invention is: This invention discloses an assemblable, multi-source bus data high-efficiency processing system, comprising: a bus data configuration module, a message parsing thread establishment module, and a bus data parsing module; wherein, The bus data configuration module is used to configure the bus type, bus messages, bus parameters and calculation formulas, and store the configuration information in the database; The message parsing thread creation module retrieves configuration information from the database; obtains message IDs based on the configuration information; creates message parsing threads based on the message IDs, forming a parsing thread pool; and creates and maintains a hash table between message IDs and message parsing threads. The bus data parsing module retrieves configuration information from the database, parses external experimental data based on the configuration information, and outputs a text file. The bus data parsing module includes a bus data filtering module, a bus data delivery module, and a bus parameter parsing module; among them, The bus data filtering module retrieves configuration information from the database, obtains the bus data frame format based on the configuration information, selects qualified bus data frames and message IDs from external test data based on the bus data frame format, obtains the valid data area, and transmits the valid data area to the bus data delivery module. The bus data delivery module uses a hash table between message ID and message parsing thread to find the message parsing thread corresponding to the message ID from the parsing thread pool, and sends the valid data area to the message parsing thread in the bus parameter parsing module corresponding to the message ID. The bus parameter parsing module retrieves the binary data corresponding to each bus parameter from the valid data area based on the configuration information, performs physical value calculations on the binary data, and outputs the results to a text file.

[0011] Furthermore, in the above system, the specific method for selecting qualified bus data frames and message IDs from external test data according to the bus data frame format is as follows: S11. Obtain bus data configuration from configuration information, including frame header, frame tail, data length position and message ID position; S12. Based on the frame header, traverse the input external test data byte by byte to find the frame header position of the bus data; S13. Read the data length value according to the data length position; S14. Based on the frame header position and data length value, find the frame tail position, read the value, and determine whether it is the correct frame tail value; if yes, proceed to step S15; otherwise, proceed to step S16. S15. Remove the frame header, frame tail, and data length from the current frame bus data, extract the bus data area and message ID, and transmit them to the bus data delivery module. Then, starting from the byte after the frame tail, repeat steps S12 to S14 until the input external test data has been traversed. S16. Repeat steps S12 to S14 starting from the last byte of the frame header until the input external test data has been traversed.

[0012] Furthermore, in the above system, the specific method for retrieving the message parsing thread corresponding to the message ID from the parsing thread pool based on the hash table between the message ID and the message parsing thread, and sending the valid data area to the parsing thread corresponding to the message ID, is as follows: Based on the hash table between the message ID and the message parsing thread, the corresponding message parsing thread is searched in the parsing thread pool. If the corresponding message parsing thread is found, the bus data area data is transmitted to the corresponding message parsing thread in the bus parameter parsing module. If the corresponding message parsing thread is not found, the received bus data area data is discarded, and the system continues to wait to receive a valid data area and message ID.

[0013] Furthermore, in the above system, the specific method for obtaining the binary data corresponding to each bus parameter from the valid data area according to the configuration information and performing physical value calculation on the binary data is as follows: The message parsing thread in the bus parameter parsing module receives the valid data area transmitted by the bus data delivery module. Obtain the mapping bus parameter configuration of the message corresponding to the valid data area from the configuration information, including the number of parameters bound to the valid data area, the starting position of each parameter in the data area, and the parameter length; The message parsing thread iterates through the bound parameters and extracts the binary data of each parameter from the valid data area according to the start bit configuration and parameter length configuration of each parameter. The physical value corresponding to the binary data is calculated based on the formula bound to each parameter, and the physical value is output to a text file.

[0014] Furthermore, in the above system, the bus type is configured as follows: the bus type includes 1553B bus data, 422 bus data and platform high-string data, and different bus types have different frame header and frame tail information; during configuration, the bus message is bound to the corresponding bus type.

[0015] Furthermore, in the above system, the bus messages are configured, including: bus message attribute configuration and mapped bus parameter configuration; bus message attribute configuration includes setting the message name, message ID, instruction word length, data area length, and header length; mapped bus parameter configuration describes the message data area, specifying which parameters the message data area contains and the position of each parameter in the message; during configuration, bus parameters and bus messages are bound together, and the position of each bus parameter in the message data area is indicated by the start bit and parameter length.

[0016] Furthermore, in the above system, the bus parameters are configured to set the parameter name, parameter code, parameter length, byte order, value type, sensor type, sensor model, sensor and text output type.

[0017] Furthermore, in the above system, the calculation formula is configured, including sensor type configuration, sensor model configuration, and sensor configuration; sensor type configuration sets the type of calculation formula; sensor configuration configures the formula coefficients and segment coefficients for specific formulas.

[0018] Furthermore, in the above system, the calculation formulas are configured using a plug-in approach. Each type of sensor is an independent dynamic link library, and the sensor formula modules can be dynamically loaded and unloaded through database table configuration.

[0019] The advantages of this invention over the prior art are as follows: (1) This invention aims to solve the technical problems existing in the current aerospace bus data processing, such as low parsing efficiency, difficulty in adapting to complex and ever-changing frame formats and calculation formulas, high software coupling leading to low reuse rate, difficulty in expanding new functions, and weak cross-platform adaptability, so as to realize flexible configuration, rapid response and autonomous control of data processing.

[0020] (2) This invention uses a configurable approach to adapt to various parsing requirements of bus data. The processing formula is implemented in a plug-in manner, which can be dynamically loaded and unloaded and flexibly bound. The software platform has an interface to facilitate the rapid development of new types of processing formulas. The pipeline approach and multi-threaded design are used to achieve efficient processing of bus data.

[0021] (3) This invention proposes an efficient multi-source bus data processing technology that can be assembled by studying the requirements of data processing software for various models and multiple launches. Through data abstraction, variable items such as parameter data types, frame formats, and processing formulas are abstracted into configurable items, improving the black-box reusability of the software. By studying software modularization technology and module integration technology, the modularization of calculation formulas and rapid integration of functional modules are realized, shortening the software development cycle and continuously enhancing the new vitality of the software. This invention uses Qt as the development language to achieve one-time coding adaptation to multiple operating system platforms, meeting the requirements of the localization of software operation platforms for future aerospace models, and ensuring information security and independent controllability.

[0022] (4) The present invention adopts a configurable method to adapt to various bus parsing requirements. It can be flexibly configured according to the actual situation, and then the corresponding parsing is completed according to the specific configuration, thereby improving the software reuse rate. (5) The parameter calculation formula module of this invention is implemented in a plug-in manner. Each type of calculation formula is an independent dynamic link library, which can be dynamically loaded and unloaded. The software platform provides an abstract interface, which can quickly and reliably complete the development of new types of calculation formulas, solve the problem of complex and ever-changing bus parameter processing formulas, and can quickly complete the development of new types of sensors without modifying the software platform. (6) The present invention adopts a pipeline approach, which breaks down bus data parsing into three steps: bus data filtering, bus data delivery, and bus parameter parsing. Each step receives the data processed in the previous step, and each step completes its processing work independently after acquiring the data, thereby improving processing efficiency. (7) The present invention adopts a multi-threaded design, each thread runs independently, data is transferred between threads, and a mutex lock is used to protect the data buffer area. The multi-threaded design greatly improves the speed of bus data processing.

[0023] (8) This invention can significantly improve the reusability and development efficiency of data processing software in the aerospace field, and reduce the repetitive workload caused by changes in requirements and complex requirements in software development. Therefore, applying this technology to engineering practice is of great significance. Attached Figure Description

[0024] Figure 1 This is a system architecture diagram of the present invention; Figure 2 This is a diagram of the bus message configuration interface of the present invention; Figure 3 This is a diagram showing the sensor formula configuration of the present invention; Figure 4 This is a diagram showing the database configuration for the calculation formula module of this invention. Figure 5 This is a flowchart of the bus screening module of the present invention; Figure 6 This is a flowchart of the bus parameter parsing process of the present invention; Figure 7 This is a schematic diagram of the bus data parsing thread design of the present invention; Figure 8 This is a schematic diagram of the interaction between the bus data parsing threads of the present invention. Detailed Implementation

[0025] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0026] This invention adopts a comprehensive technical approach of "data abstraction + plug-in architecture + pipelined parallelism". First, through data abstraction technology, volatile parameter data types, frame format definitions, and processing formulas are extracted from the core code and transformed into dynamically modifiable and loadable configuration information. Second, a plug-in calculation formula module based on dynamic link libraries is constructed, providing standardized abstract interfaces to support the independent development of new formula types. Finally, a pipelined processing engine based on multi-threaded protection is designed, decoupling the entire data processing flow into three independent stages: data filtering, data delivery, and parameter parsing. A mutex lock mechanism ensures the synchronization and safety of data buffers between threads, achieving high-concurrency, low-latency parallel processing of multi-source bus data, and seamless cross-operating system platform adaptation based on the Qt framework.

[0027] This invention discloses an assemblable, multi-source bus data high-efficiency processing system, comprising: a bus data configuration module, a message parsing thread establishment module, and a bus data parsing module; wherein, The bus data configuration module is used to configure the bus type, bus messages, bus parameters and calculation formulas, and store the configuration information in the database; The message parsing thread creation module retrieves configuration information from the database; obtains message IDs based on the configuration information; creates message parsing threads based on the message IDs, forming a parsing thread pool; and creates and maintains a hash table between message IDs and message parsing threads. The bus data parsing module retrieves configuration information from the database, parses external experimental data based on the configuration information, and outputs a text file. The bus data parsing module includes a bus data filtering module, a bus data delivery module, and a bus parameter parsing module; among them, The bus data filtering module retrieves configuration information from the database, obtains the bus data frame format based on the configuration information, selects qualified bus data frames and message IDs from external test data based on the bus data frame format, obtains the valid data area, and transmits the valid data area to the bus data delivery module. The bus data delivery module uses a hash table between message ID and message parsing thread to find the message parsing thread corresponding to the message ID from the parsing thread pool, and sends the valid data area to the message parsing thread in the bus parameter parsing module corresponding to the message ID. The bus parameter parsing module retrieves the binary data corresponding to each bus parameter from the valid data area based on the configuration information, performs physical value calculations on the binary data, and outputs the results to a text file.

[0028] Preferably, qualified bus data frames and message IDs are selected from external test data according to the bus data frame format. The specific method is as follows: S11. Obtain bus data configuration from configuration information, including frame header, frame tail, data length position and message ID position; S12. Based on the frame header, traverse the input external test data byte by byte to find the frame header position of the bus data; S13. Read the data length value according to the data length position; S14. Based on the frame header position and data length value, find the frame tail position, read the value, and determine whether it is the correct frame tail value; if yes, proceed to step S15; otherwise, proceed to step S16. S15. Remove the frame header, frame tail, and data length from the current frame bus data, extract the bus data area and message ID, and transmit them to the bus data delivery module. Then, starting from the byte after the frame tail, repeat steps S12 to S14 until the input external test data has been traversed. S16. Repeat steps S12 to S14 starting from the last byte of the frame header until the input external test data has been traversed.

[0029] Preferably, based on the hash table between the message ID and the message parsing thread, the message parsing thread corresponding to the message ID is found from the parsing thread pool, and the valid data area is sent to the parsing thread corresponding to the message ID. The specific method is as follows: Based on the hash table between the message ID and the message parsing thread, the corresponding message parsing thread is searched in the parsing thread pool. If the corresponding message parsing thread is found, the bus data area data is transmitted to the corresponding message parsing thread in the bus parameter parsing module. If the corresponding message parsing thread is not found, the received bus data area data is discarded, and the system continues to wait to receive a valid data area and message ID.

[0030] Preferably, based on the configuration information, binary data corresponding to each bus parameter is obtained from the valid data area, and physical value calculation is performed on the binary data. The specific method is as follows: The message parsing thread in the bus parameter parsing module receives the valid data area transmitted by the bus data delivery module. Obtain the mapping bus parameter configuration of the message corresponding to the valid data area from the configuration information, including the number of parameters bound to the valid data area, the starting position of each parameter in the data area, and the parameter length; The message parsing thread iterates through the bound parameters and extracts the binary data of each parameter from the valid data area according to the start bit configuration and parameter length configuration of each parameter. The physical value corresponding to the binary data is calculated based on the formula bound to each parameter, and the physical value is output to a text file.

[0031] Preferably, the bus type is configured as follows: the bus type includes 1553B bus data, 422 bus data and platform high-string data, and different bus types have different frame header and frame tail information; during configuration, the bus message is bound to the corresponding bus type.

[0032] Preferably, the bus message is configured, including: bus message attribute configuration and mapped bus parameter configuration; bus message attribute configuration includes setting the message name, message ID, instruction word length, data area length, and header length; mapped bus parameter configuration describes the message data area, specifies which parameters the message data area contains and the position of each parameter in the message; during configuration, the bus parameters and bus messages are bound, and the position of each bus parameter in the message data area is indicated by the start bit and parameter length.

[0033] Preferably, the bus parameters are configured to set the parameter name, parameter code, parameter length, byte order, value type, sensor type, sensor model, sensor and text output type.

[0034] Preferably, the calculation formula is configured, including sensor type configuration, sensor model configuration, and sensor configuration; sensor type configuration is to set the type of calculation formula; sensor configuration is to configure the formula coefficients and segment coefficients of the specific formula.

[0035] Preferably, the calculation formula is configured using a plug-in approach, with each type of sensor being an independent dynamic link library. The sensor formula module can be dynamically loaded and unloaded through database table configuration.

[0036] Example This invention addresses the general functional requirements of data processing software in the aerospace field, outlining its basic functions and general needs, and dividing the software into three parts: bus data configuration, message parsing thread establishment, and bus data parsing.

[0037] like Figure 1 As shown, this embodiment provides an assemblable multi-source bus data high-efficiency processing system, including: The bus data configuration module configures the bus type, bus messages, bus parameters, and calculation formulas, storing the configuration information in a database. Data processing personnel configure various information before testing, supporting multi-person collaborative configuration to improve speed. The message parsing thread creation module retrieves configuration information from the database; based on the configuration information, it obtains the message ID; and based on the message ID, it creates a message parsing thread pool, creating and maintaining a hash table between message IDs and message parsing threads. Bus data parsing includes three modules: bus data filtering, bus data delivery, and bus parameter parsing. These three modules work in a pipeline manner, processing data step-by-step as a product. The bus data filtering module operates in an independent thread, with a cooperating bus data delivery module, also operating in an independent thread. Each message has its own independent thread, and these threads constitute the parsing thread pool. The bus data filtering thread, bus data delivery thread, and parsing thread pool work in coordination. The main function of the bus data filtering module is to select qualified bus data frames and message IDs from the test data based on the bus data frame format, remove frame structure information, and retain only the valid data area before transmitting it to the bus data delivery module. The bus data delivery module uses a hash table between the message ID and the message parsing thread to find the corresponding message parsing thread from the parsing thread pool and delivers the valid bus data area to that thread for parsing. After receiving the valid bus data area, the bus parameter parsing module extracts the binary data of each bus parameter according to the configuration information, calculates the physical value based on the bound sensor formula, and finally outputs the calculated physical value to a text file.

[0038] Bus information configuration Bus information configuration includes bus type configuration, bus message configuration, bus parameter configuration, and calculation formula configuration (sensor configuration). The bus type determines the frame format of the bus data; during parsing, messages are filtered and valid data is obtained based on the bus data frame format.

[0039] Bus types include 1553B bus data, 422 bus data, and platform high-string data. During configuration, simply bind the message to the corresponding bus type; parsing will then follow the bound bus type. If new bus data (with a different data format) needs to be parsed, the new bus format can be added.

[0040] Bus message configuration includes bus message attribute configuration and mapped bus parameter configuration. Message attribute configuration provides a comprehensive description of the message, including message name, message ID, instruction word length, DLC (Data Area Length), header length, etc. The message ID is a unique identifier for the bus message and is configured in hexadecimal, such as... Figure 2The mapped bus parameter configuration describes the message data area, specifying which parameters are included and the position of each parameter within the message. During configuration, bus parameters are bound to bus messages, with the start bit and parameter length indicating the position of each bus parameter within the message data area.

[0041] Bus parameter configuration is the basis for obtaining the binary data of each parameter and calculating its physical value. Bus parameter configuration includes parameter name, parameter code, parameter length, byte order, value type, sensor type, sensor model, sensor information, and text output type. The sensor configuration determines the parameter calculation formula.

[0042] Calculation formula configuration and plug-in The calculation formula is determined by the sensor selected based on the parameter configuration; the sensor determines how the binary data of the parameters is converted into physical quantities. For example... Figure 3 Sensor formula configuration includes sensor type configuration, sensor model configuration, and sensor configuration. Sensor type configuration refers to the type of calculation formula, such as linear formula, quadratic formula, etc.; sensor type is a summary of calculation formulas of the same type; sensor configuration configures the formula coefficients and piecewise coefficients of specific formulas.

[0043] To accommodate the complex and ever-changing parameter calculation formulas, the sensor formulas are implemented using a plug-in approach. Each type of sensor is an independent dynamic link library, and the loading and unloading of sensor formula modules can be flexibly achieved through database table configuration (e.g., ...). Figure 4 (As shown). The software platform provides an abstract interface for the sensor module. By implementing the interface, new types of sensors can be developed quickly without modifying the software platform.

[0044] Message parsing thread established The message parsing thread creation module retrieves configuration information from the database; obtains message IDs based on the configuration information; and creates message parsing threads to form a parsing thread pool based on the message IDs, and creates and maintains a hash table between message IDs and message parsing threads.

[0045] Bus data parsing Bus data parsing comprises three modules: bus data filtering, bus data delivery, and bus parameter parsing. The bus data filtering module selects data frames from the experimental data that conform to the bus message format based on the bus data format. For example... Figure 5As shown, taking 1553B as an example, the bus data filtering module traverses the data byte by byte. When it finds the 1553B message frame header (0x50FC), it obtains the next byte, calculates the message length M, and then queries bytes M+1 and M+2. If it is the 1553B message frame tail (0xAF03), then the portion from position 0x50FC to position 0xAF03 is a qualified frame. After obtaining a qualified frame, the message instruction word is obtained according to the message format. The status word and block status word are removed according to the transmit / receive flags to obtain the message data area, which is then delivered to the bus data delivery module. Generally, the instruction word can serve as the unique identifier of a 1553B message. In practical applications, there may be messages with the same instruction word, and a message flag word is set in the message data area. In this case, the instruction word and the message flag can be used together as the message ID. This paper demonstrates how to parse such bus messages.

[0046] The bus data filtering module, after acquiring the bus data frame data area, delivers the message ID and data area to the bus data delivery module. In this invention, the parsing process for each message is completed in a separate thread, and all message parsing threads form a message parsing thread pool. By querying the hash table between the message ID and the message parsing thread, the bus data delivery module selects the corresponding message parsing thread from the thread pool and delivers the bus message data area to that thread.

[0047] The bus data delivery module acts as a "courier" during the bus parsing process, responsible for delivering the "data package" to the correct parsing thread based on the "package address".

[0048] The bus parameter parsing module parses each bus parameter based on the parameter configuration and the mapped bus parameter configuration. The bus parameter parsing process is as follows: Figure 6 As shown, the bus parameter parsing module extracts the binary data of each parameter from the bus data area according to the start bit configuration and parameter length configuration, adjusts the byte order according to the byte order configuration, calculates the physical value according to the bound formula, and outputs the result to a text file.

[0049] The bus filtering module reads bus data from the I / O buffer and then performs filtering to obtain the data area. Each time a data frame is obtained, it is transmitted to the delivery module, followed immediately by the filtering of subsequent data. Upon receiving data, the bus delivery module retrieves data from the buffer and delivers it to the correct message parsing thread. Once the delivery module's buffer is empty, it can receive data again and perform delivery. The message parsing thread receives the delivered data, retrieves it from the buffer, and parses it. Throughout this process, each thread's buffer is protected by a mutex lock to prevent conflicts caused by frequent read / write operations and ensure the safety of each thread. The bus data parsing thread is designed as follows: Figure 7 As shown, the interactions between the threads are as follows:Figure 8 As shown.

[0050] This embodiment provides an assemblable, multi-source bus data high-efficiency processing system, comprising the following steps: Step 1: Bus data configuration, used to configure the bus type, bus messages, bus parameters and calculation formulas, and store the configuration information in the database; Step 2: Establish message parsing threads, retrieve configuration information from the database, create message parsing threads to form a parsing thread pool based on message IDs, and create and maintain a hash table between message IDs and message parsing threads; Step 3: Bus data parsing. Load configuration information from the database, correctly parse the input external test data, and output the parsing results to a text file in the form of physical values. Sub-step 1: Bus data filtering. Obtain configuration information from the database. Based on the configuration information, obtain the bus data frame format. Based on the bus data frame format, select qualified bus data frames and message IDs from external test data, remove frame structure information and keep only the valid data area, and transmit the valid data area to the bus data delivery module. Sub-step 2: Bus data delivery. Based on the hash table between the message ID and the message parsing thread, the corresponding message parsing thread is found from the parsing thread pool, and the valid bus data area is delivered to the parsing thread corresponding to the message ID. Sub-step 3: Bus parameter parsing. Based on the configuration information, obtain the binary data corresponding to each bus parameter from the bus valid data area, perform physical value calculation on the binary data, and output it to a text file.

[0051] Although the present invention has been described in detail through the preferred embodiments above, it should be understood that the above description should not be considered as a limitation of the present invention. Various modifications and substitutions to the present invention will be apparent to those skilled in the art after reading the above description. Therefore, the scope of protection of the present invention should be defined by the appended claims.

[0052] The contents not described in detail in this specification are common knowledge to those skilled in the art.

Claims

1. An assemblable multi-source bus high-efficiency data processing system, characterized in that, include: The module consists of a bus data configuration module, a message parsing thread establishment module, and a bus data parsing module; among them, The bus data configuration module is used to configure the bus type, bus messages, bus parameters and calculation formulas, and store the configuration information in the database; The message parsing thread creation module retrieves configuration information from the database; obtains message IDs based on the configuration information; creates message parsing threads based on the message IDs, forming a parsing thread pool; and creates and maintains a hash table between message IDs and message parsing threads. The bus data parsing module retrieves configuration information from the database, parses external experimental data based on the configuration information, and outputs a text file. The bus data parsing module includes a bus data filtering module, a bus data delivery module, and a bus parameter parsing module; among them, The bus data filtering module retrieves configuration information from the database, obtains the bus data frame format based on the configuration information, selects qualified bus data frames and message IDs from external test data based on the bus data frame format, obtains the valid data area, and transmits the valid data area to the bus data delivery module. The bus data delivery module uses a hash table between message ID and message parsing thread to find the message parsing thread corresponding to the message ID from the parsing thread pool, and sends the valid data area to the message parsing thread in the bus parameter parsing module corresponding to the message ID. The bus parameter parsing module retrieves the binary data corresponding to each bus parameter from the valid data area based on the configuration information, performs physical value calculations on the binary data, and outputs the results to a text file.

2. The assemblable multi-source bus data high-efficiency processing system according to claim 1, characterized in that, The method for selecting qualified bus data frames and message IDs from external test data according to the bus data frame format is as follows: S11. Obtain bus data configuration from configuration information, including frame header, frame tail, data length position and message ID position; S12. Based on the frame header, traverse the input external test data byte by byte to find the frame header position of the bus data; S13. Read the data length value according to the data length position; S14. Based on the frame header position and data length value, find the frame tail position, read the value, and determine whether it is the correct frame tail value; if so, proceed to step S15. Otherwise, proceed to step S16; S15. Remove the frame header, frame tail, and data length from the current frame bus data, extract the bus data area and message ID, and transmit them to the bus data delivery module. Then, starting from the byte after the frame tail, repeat steps S12 to S14 until the input external test data has been traversed. S16. Repeat steps S12 to S14 starting from the last byte of the frame header until the input external test data has been traversed.

3. The assemblable multi-source bus data high-efficiency processing system according to claim 1, characterized in that, The method for retrieving the message parsing thread corresponding to the message ID from the parsing thread pool based on the hash table between the message ID and the message parsing thread, and then sending the valid data area to the parsing thread corresponding to the message ID, is as follows: Based on the hash table between the message ID and the message parsing thread, the corresponding message parsing thread is searched in the parsing thread pool; if the corresponding message parsing thread is found, the bus data area data is transmitted to the corresponding message parsing thread in the bus parameter parsing module. If no corresponding message parsing thread is found, discard the received bus data area data and continue waiting to receive a valid data area and message ID.

4. The assemblable multi-source bus data high-efficiency processing system according to claim 1, characterized in that, The step involves obtaining binary data corresponding to each bus parameter from the valid data area based on the configuration information, and then performing physical value calculations on the binary data. The specific method is as follows: The message parsing thread in the bus parameter parsing module receives the valid data area transmitted by the bus data delivery module. Obtain the mapping bus parameter configuration of the message corresponding to the valid data area from the configuration information, including the number of parameters bound to the valid data area, the starting position of each parameter in the data area, and the parameter length; The message parsing thread iterates through the bound parameters and extracts the binary data of each parameter from the valid data area according to the start bit configuration and parameter length configuration of each parameter. The physical value corresponding to the binary data is calculated based on the formula bound to each parameter, and the physical value is output to a text file.

5. The assemblable multi-source bus data high-efficiency processing system according to claim 1, characterized in that, Configure the bus type as follows: The bus type includes 1553B bus data, 422 bus data and platform high-string data. Different bus types have different frame header and frame tail information. During configuration, the bus message is bound to the corresponding bus type.

6. The assemblable multi-source bus data high-efficiency processing system according to claim 1, characterized in that: Configuring bus messages includes: bus message attribute configuration and mapped bus parameter configuration; bus message attribute configuration includes setting the message name, message ID, instruction word length, data area length, and header length; mapped bus parameter configuration describes the message data area, specifying which parameters are included in the message data area and the position of each parameter in the message; during configuration, bus parameters are bound to bus messages, and the position of each bus parameter in the message data area is indicated by the start bit and parameter length.

7. The assemblable multi-source bus data high-efficiency processing system according to claim 1, characterized in that: The bus parameters are configured by setting the parameter name, parameter code, parameter length, byte order, value type, sensor type, sensor model, sensor and text output type. According to claim 1, the assembleable multi-source bus data high-efficiency processing system is characterized in that: the calculation formula is configured, including sensor type configuration, sensor model configuration and sensor configuration; the sensor type configuration is to set the type of calculation formula; the sensor configuration is to configure the formula coefficients and segment coefficients of the specific formula.

8. The assemblable multi-source bus data high-efficiency processing system according to claim 7, characterized in that: The calculation formulas are configured using a plug-in approach. Each type of sensor is an independent dynamic link library, and the sensor formula modules can be dynamically loaded and unloaded through database table configuration.

Images