Carrier rocket flight verification test method and system
Through automated testing methods and systems, using configuration files to parse and interpret flight parameters and telemetry data, the problems of low efficiency and rely on manual processing in the existing technology are solved, and efficient and accurate launch vehicle flight verification tests are achieved.
Patent Information
- Application Number
- CN202310758600.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-06-26
- Publication Date
- 2025-02-28
AI Technical Summary
The prior art cannot meet the increasing demand for testing launch vehicles' missions, is inefficient and relies on manual processing of flight parameters and telemetry data.
An automated testing method and system is used to analyze and interpret flight parameters and telemetry data through configuration files, generate test data and automatically interpret it to determine whether the physical quantity exceeds the difference.
It realizes automation of flight parameter generation and telemetry data judgment, improves testing efficiency, reduces manpower investment, and ensures the accuracy and leak-free judgment of the test.
Smart Images
Figure CN119538393A_ABST
Abstract
Description
Technical Field
[0001] The invention belongs to the field of simulation testing, and in particular relates to a launch vehicle flight verification test method and system. Background Art
[0002] Rocket-borne flight testing involves the design of flight parameters and the interpretation of telemetry parameters. With the increasing integration of modern single-machine flight parameters and telemetry parameters, more and more parameters need to be processed. Therefore, it is important to quickly and accurately determine the test content, generate the corresponding flight parameters, and interpret the telemetry data generated by the test to ensure the success of the rocket flight.
[0003] The current flight parameter design and processing adopts the manual method of processing parameters using the existing processing guidelines. The telemetry data processing and judgment process is a combination of data processing and manual judgment. The existing technology cannot meet the increasing demand for flight mission testing. Summary of the invention
[0004] The technical purpose of the present invention is to provide a launch vehicle flight verification test method and system to solve the problem of low efficiency in the prior art.
[0005] To solve the above problems, the technical solution of the present invention is:
[0006] A launch vehicle flight verification test method comprises the following steps:
[0007] S1: Input flight parameters and parse them, filter the parsed flight parameters according to the configuration file, and generate corresponding test data;
[0008] S2: Call the corresponding test environment and load the test data into it to generate telemetry data;
[0009] S3: Convert telemetry data into physical quantity according to the configuration file, and automatically read it to determine whether the current physical quantity is out of tolerance, and display whether the reading result is passed.
[0010] Specifically, in step S1, the flight parameters include normal flight test data, shutdown-allowed test data, scheduled shutdown test data, small overload flight test data, triangle wave test data, and square wave test data.
[0011] Wherein, in step S1, the test data includes the test data type, the test environment type and the test data generation algorithm;
[0012] The algorithm classification of the configuration file is as follows: critical time category: Tout=Tin+t; threshold decision physical quantity category: Vout=k*Vin+b; telemetry window judgment category: Tstartout=Tstartin+1, Tendout=Tendin+t1+t2; telemetry physical quantity judgment category: Vout=k*Vin+b; telemetry time judgment category: Tout=Tin.
[0013] Wherein, in step S2, the test environment includes different types of launch vehicles.
[0014] Specifically, in step S3, the configuration file describes the channel information and telemetry parameter attributes in the telemetry data;
[0015] Before converting the telemetry data into physical quantities, all telemetry data need to be analyzed using sliding shift matching. The specific steps are as follows:
[0016] The telemetry data is formed into a data queue {D1, D2, D3..Dn} according to the specified length. When the data synthesized by Di, Di+1, Di+2, and Di+3 matches the data frame header specified in the configuration file, the data Dk, Dk+1, Dk+2, and Dk+3 at the corresponding position of the telemetry data are taken out according to the frame length L of the configuration file parameters to determine whether the synthesized data matches the data frame tail specified in the configuration file.
[0017] If the frame tail matches, take out the data queue from Di to Dk+3 and assign the telemetry frame parameter Fnm;
[0018] If the frame header or frame tail does not match, the matching continues from Di+1;
[0019] Among them, n in the telemetry frame parameter Fnm represents the nth data frame in the configuration file, and m represents the nth data frame of the corresponding data frame.
[0020] Among them, the specific steps of converting telemetry data into physical quantities according to the configuration file are:
[0021] Read the identifier of each telemetry data from the configuration file. The identifier is composed of the table number N of the telemetry data frame, the sequence number M of the telemetry data frame, and the sequence number K of the telemetry data, and the identifier is NKM;
[0022] Based on the identification of the telemetry data, the physical quantity conversion algorithm of each telemetry data is traversed in the configuration file, the physical quantity conversion algorithm corresponding to each telemetry data is found and the telemetry data is converted into a physical quantity.
[0023] Among them, the specific steps of determining the corresponding quantity conversion algorithm according to the identification of the telemetry data are:
[0024] When NK in the telemetry data identifier NKM is 100, 101, 102, 103, ..., 120, the physical quantity algorithm corresponding to the telemetry data is a linear algorithm, and the linear algorithm of the telemetry data is Vout=k*Vin+b;
[0025] When NK in the telemetry data identifier NKM is 121, 101, 102, 103, ..., 199, the physical quantity algorithm corresponding to the telemetry data is a nonlinear algorithm, and the nonlinear algorithm of the telemetry data is: DG = R2 / T-(Vin-Ve)*T / (V*R), where R is the temperature sensor resistance, T is the temperature sensor sensitivity coefficient, and Ve is the 5V voltage;
[0026] When NK in the telemetry data identifier NKM is 200, 201, 202, 203, .., 299, the physical quantity algorithm corresponding to the telemetry data is to calculate the fitting slope by linear difference according to the order of the data frames and the data in the single machine and product performance requirements;
[0027] When NK=300, 301, 302, 303, ..., 399 in the telemetry data identifier NKM, the physical quantities corresponding to the telemetry data are all switch quantities, and the judgment is made according to the physical quantity conversion algorithm and analog quantity threshold and judgment relationship set in the configuration file: SW=(Vin*k+b>ST?1:0).
[0028] Specifically, telemetry data is judged based on the following model:
[0029] Time data: Automatic interpretation using a single-point basic interpretation model;
[0030] Angle data: automatic interpretation using the basic interpretation model;
[0031] Speed data: automatic interpretation using a trajectory-based interpretation model;
[0032] Switching data: automatic interpretation using an operational interpretation model based on key time points.
[0033] A launch vehicle flight verification test system, configured with any one of the launch vehicle flight verification test methods described above, comprising:
[0034] Flight parameter analysis module, test data generation module, test execution module, telemetry data judgment module and test result display module;
[0035] The flight parameter parsing module is used to receive the flight parameters, parse the flight parameters and transmit them to the test data generating module;
[0036] The test data generation module is used to filter the parsed flight parameters according to the configuration file, generate corresponding test data, and send the test data to the test execution module and the telemetry data judgment module;
[0037] The test execution module is used to call the corresponding test environment, load the test data into it, generate telemetry data, and send the generated telemetry data to the telemetry data interpretation module;
[0038] The telemetry data interpretation module is used to convert the telemetry data into physical quantities according to the configuration file, and automatically interpret the data to determine whether the current physical quantity is out of tolerance, and transmit the automatic interpretation result to the test result display module;
[0039] The test result display module is used to display whether the test is passed according to the judgment result.
[0040] Due to the adoption of the above technical solution, the present invention has the following advantages and positive effects compared with the prior art:
[0041] For the launch vehicle flight software testing process with a large amount of data, the present invention proposes to use the method of binding configuration files to set the flight parameter design method, and to set the telemetry data analysis and judgment method, which solves the drawbacks of only manually generating flight parameters and manually interpreting them in the past, saving a lot of manpower for the testing process, and also automating and eliminating missed judgments in the flight parameter generation and telemetry data judgment process, providing a basis for flight software testing and ensuring smooth testing. BRIEF DESCRIPTION OF THE DRAWINGS
[0042] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the following detailed description of the preferred embodiment.The drawings are only for the purpose of illustrating the preferred embodiments and are not to be construed as limiting the invention.
[0043] Figure 1 It is a structural block diagram of the launch vehicle flight verification test system of the present invention;
[0044] Figure 2 The present invention is a flowchart of the launch vehicle flight verification test method. DETAILED DESCRIPTION
[0045] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the specific implementation methods of the present invention will be described below with reference to the accompanying drawings. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings and other implementation methods can be obtained based on these drawings without creative work.
[0046] In order to simplify the drawings, only the parts related to the present invention are schematically shown in each figure, and they do not represent the actual structure of the product. In addition, in order to simplify the drawings and facilitate understanding, in some figures, only one of the parts with the same structure or function is schematically drawn or marked. In this article, "one" not only means "only one", but also means "more than one".
[0047] The following is a further detailed description of a launch vehicle flight verification test method and system proposed by the present invention in conjunction with the accompanying drawings and specific embodiments. The advantages and features of the present invention will become more apparent from the following description and claims.
[0048] Example
[0049] See also Figure 1 and Figure 2 This embodiment provides a launch vehicle flight verification test method, comprising the following steps:
[0050] First, in step S1, the flight parameters are input and parsed, and the parsed flight parameters are screened according to the configuration file to generate corresponding test data. The input flight parameters include normal flight test data, allowed shutdown test data, timed shutdown test data, small overload flight test data, triangle wave test data, square wave test data, etc. The test data generation file includes test data type, test environment type and test data generation algorithm.
[0051] Test data generation includes generating test data according to the flight parameter type and the corresponding algorithm of the configuration file, which can be divided into key time category: Tout = Tin + t; threshold decision physical quantity category: Vout = k*Vin + b; telemetry window judgment category: Tstartout = Tstartin + 1, Tendout = Tendin + t1 + t2; telemetry physical quantity judgment category: Vout = k*Vin + b; telemetry time judgment category: Tout = Tin. The above formula is used for subsequent analysis, and the values of k and so on can be configured.
[0052] Next, in step S2, the corresponding test environment is called and the test data is loaded into it to generate telemetry data. The test environment includes different types of launch vehicles, such as Long March 2, Long March 4, Long March 6, etc.
[0053] Next, enter step S3, convert the telemetry data into physical quantities according to the configuration file, and automatically judge whether the current physical quantity is out of tolerance, and display whether the judgment result is passed. Among them, the configuration file describes the channel information and telemetry parameter attributes in the telemetry data.
[0054] Before converting the telemetry data into physical quantities, all telemetry data need to be analyzed using sliding shift matching. The specific steps are as follows:
[0055] The telemetry data is formed into a data queue {D1, D2, D3..Dn} according to the specified length. When the data synthesized by Di, Di+1, Di+2, and Di+3 matches the data frame header specified in the configuration file, the data Dk, Dk+1, Dk+2, and Dk+3 at the corresponding position of the telemetry data are taken out according to the frame length L of the configuration file parameters to determine whether the synthesized data matches the data frame tail specified in the configuration file. If the frame tail matches, the data queue from Di to Dk+3 is taken out and assigned the telemetry frame parameter Fnm. If the frame header or frame tail does not match, the matching continues from Di+1. Among them, n in the telemetry frame parameter Fnm represents the nth data frame in the configuration file, and m represents the nth data frame of the corresponding data frame.
[0056] For the retrieved data frame, the corresponding data is retrieved from the data queue according to the data start position Ps and end position Pe specified in the configuration file, and the data parameter Dn is assigned, where n represents the nth type of data of the data frame in the configuration file.
[0057] Next, the specific steps to convert telemetry data into physical quantities according to the configuration file are:
[0058] Read the identifier of each telemetry data from the configuration file. The identifier consists of the table number N of the telemetry data frame, the sequence number M of the telemetry data frame, and the sequence number K of the telemetry data, and is identified as NKM. Based on the identifier of the telemetry data, traverse the physical quantity conversion algorithm of each telemetry data in the configuration file, find the physical quantity conversion algorithm corresponding to each telemetry data, and convert the telemetry data into physical quantity. Specifically,
[0059] When NK in the telemetry data identifier NKM is 100, 101, 102, 103, ..., 120, the physical quantity algorithm corresponding to the telemetry data is a linear algorithm, and the linear algorithm of the telemetry data is Vout = k*Vin+b. k and b correspond to the slope coefficient and intercept coefficient of the analog quantity conversion respectively, and Vout is the physical quantity corresponding to the telemetry data NKM.
[0060] When NK in the telemetry data identifier NKM is 121, 101, 102, 103, ..., 199, the physical quantity algorithm corresponding to the telemetry data is a nonlinear algorithm, and the nonlinear algorithm of the telemetry data is: DG = R2 / T-(Vin-Ve)*T / (V*R), where R is the temperature sensor resistance, T is the temperature sensor sensitivity coefficient, and Ve is the 5V voltage;
[0061] When NK in the telemetry data identifier NKM is 200, 201, 202, 203, .., 299, the physical quantity algorithm corresponding to the telemetry data is to perform linear difference fitting slope calculation based on the order of the data frames and the data in the single machine and product performance requirements. The linear difference fitting slope calculation is used for 100 groups of data to obtain the fitting slope with the least error points.
[0062] When NK=300, 301, 302, 303, ..., 399 in the telemetry data identifier NKM, the physical quantities corresponding to the telemetry data are all switch quantities, and the judgment is made according to the physical quantity conversion algorithm and analog quantity threshold and judgment relationship set in the configuration file: SW=(Vin*k+b>ST?1:0).
[0063] Specifically, telemetry data is judged based on the following model:
[0064] Time data: Use the single-point basic interpretation model for automatic interpretation to determine whether the time data is within the standard value error range.
[0065] Angle data: The basic interpretation model is used for automatic interpretation. The physical quantity of the preset standard value in the configuration file is read based on the telemetry data frame based on the time t of the first frame to determine whether the difference between the two is within the tolerance range.
[0066] Speed data: Automatic interpretation is performed using a trajectory-based interpretation model. Specifically, the speed data that changes with time and the speed data preset in the configuration file are interpreted point by point to determine whether the difference between the two is within the tolerance range. The speed data in each direction is paired according to the time t according to the calculation formula preset in the configuration file, and the vector speed value is calculated. The calculated vector speed value is then interpreted point by point with the vector speed standard value in the configuration file to determine whether the difference between the two is within the tolerance range.
[0067] Switch quantity data: Automatically interpret the data using an operational interpretation model based on key time points. Obtain the transition moment based on the recorded switch quantity, and interpret it against the standard transition moment of the switch quantity in the configuration file to determine whether the difference between the two is within the tolerance range.
[0068] Finally, the telemetry data is displayed frame by frame based on the relationship between time, telemetry frame, and telemetry data. If the telemetry data is out of tolerance, the telemetry frame to which it belongs is highlighted and the telemetry data is marked in red. The telemetry data can also be displayed based on the time curve. If the telemetry data is out of tolerance, the point corresponding to the telemetry data is marked in red.
[0069] Preferably, the present embodiment also relates to a launch vehicle flight verification test system, which is configured with the above-mentioned launch vehicle flight verification test method, including: a flight parameter analysis module, a test data generation module, a test execution module, a telemetry data judgment module and a test result display module.
[0070] The flight parameter parsing module is used to receive flight parameters, parse the flight parameters and transmit them to the test data generation module. The test data generation module is used to filter the parsed flight parameters according to the configuration file, generate corresponding test data, and send the test data to the test execution module and the telemetry data judgment module. The test execution module is used to call the corresponding test environment, load the test data into it, generate telemetry data, and send the generated telemetry data to the telemetry data judgment module. The telemetry data judgment module is used to convert the telemetry data into physical quantities according to the configuration file, and automatically judge whether the current physical quantity is out of tolerance, and transmit the automatic judgment result to the test result display module. The test result display module is used to display whether the test is passed according to the judgment result.
[0071] The embodiments of the present invention are described in detail above in conjunction with the accompanying drawings, but the present invention is not limited to the above embodiments. Even if various changes are made to the present invention, if these changes fall within the scope of the claims of the present invention and their equivalents, they still fall within the protection scope of the present invention.
Claims
1. A launch vehicle flight verification test method, characterized in that: The steps include: S1: Input flight parameters and parse them, filter the parsed flight parameters according to the configuration file, and generate corresponding test data; S2: Call the corresponding test environment and load the test data into it to generate telemetry data; S3: Convert telemetry data into physical quantity according to the configuration file, and automatically read it to determine whether the current physical quantity is out of tolerance, and display whether the reading result is passed.
2. The launch vehicle flight verification test method according to claim 1, characterized in that: In step S1, the flight parameters include normal flight test data, shutdown-allowed test data, timed shutdown test data, small overload flight test data, triangle wave test data, and square wave test data.
3. The launch vehicle flight verification test method according to claim 1, characterized in that: In the step S1, the test data includes a test data type, a test environment type and a test data generation algorithm; The algorithm classification of the profile is as follows: Tout = Tin + t; Threshold decision physical quantity category: Vout = k*Vin+b; telemetry window judgment category: Tstartout = Tstartin+1, Tendout = Tendin+t1+t2; telemetry physical quantity judgment category: Vout = k*Vin+b; telemetry time judgment category: Tout = Tin.
4. The launch vehicle flight verification test method according to claim 1, characterized in that: In step S2, the test environment includes different types of launch vehicles.
5. The launch vehicle flight verification test method according to claim 1, characterized in that: In step S3, the configuration file describes the channel information and telemetry parameter attributes in the telemetry data; Before converting the telemetry data into physical quantities, all telemetry data need to be analyzed using sliding shift matching. The specific steps are as follows: The telemetry data is formed into a data queue {D1, D2, D3..Dn} according to the specified length. When the data synthesized by Di, Di+1, Di+2, and Di+3 matches the data frame header specified in the configuration file, the data Dk, Dk+1, Dk+2, and Dk+3 at the corresponding position of the telemetry data are taken out according to the frame length L of the configuration file parameters to determine whether the synthesized data matches the data frame tail specified in the configuration file. If the frame tail matches, take out the data queue from Di to Dk+3 and assign the telemetry frame parameter Fnm; If the frame header or frame tail does not match, the matching continues from Di+1; Among them, n in the telemetry frame parameter Fnm represents the nth data frame in the configuration file, and m represents the nth data frame of the corresponding data frame.
6. The launch vehicle flight verification test method according to claim 5, characterized in that: The specific steps to convert telemetry data into physical quantities according to the configuration file are: Read the identifier of each telemetry data from the configuration file. The identifier is composed of the table number N of the telemetry data frame, the sequence number M of the telemetry data frame, and the sequence number K of the telemetry data, and the identifier is NKM; Based on the identification of the telemetry data, the physical quantity conversion algorithm of each telemetry data is traversed in the configuration file, the physical quantity conversion algorithm corresponding to each telemetry data is found and the telemetry data is converted into a physical quantity.
7. The launch vehicle flight verification test method according to claim 6, characterized in that: The specific steps of determining the corresponding quantity conversion algorithm according to the identification of telemetry data are as follows: When NK in the telemetry data identifier NKM is 100, 101, 102, 103, ..., 120, the physical quantity algorithm corresponding to the telemetry data is a linear algorithm, and the linear algorithm of the telemetry data is Vout=k*Vin+b; When NK in the telemetry data identifier NKM is 121, 101, 102, 103, ..., 199, the physical quantity algorithm corresponding to the telemetry data is a nonlinear algorithm, and the nonlinear algorithm of the telemetry data is: DG = R2 / T-(Vin-Ve)*T / (V*R), where R is the temperature sensor resistance, T is the temperature sensor sensitivity coefficient, and Ve is the 5V voltage; When NK in the telemetry data identifier NKM is 200, 201, 202, 203, .., 299, the physical quantity algorithm corresponding to the telemetry data is to calculate the fitting slope by linear difference according to the order of the data frames and the data in the single machine and product performance requirements; When NK=300, 301, 302, 303, ..., 399 in the telemetry data identifier NKM, the physical quantities corresponding to the telemetry data are all switch quantities, and the judgment is made according to the physical quantity conversion algorithm and analog quantity threshold and judgment relationship set in the configuration file: SW=(Vin*k+b>ST?1:0).
8. The launch vehicle flight verification test method according to claim 7, characterized in that: Telemetry data is judged according to the following model: Time data: Automatic interpretation using a single-point basic interpretation model; Angle data: automatic interpretation using the basic interpretation model; Speed data: automatic interpretation using a trajectory-based interpretation model; Switching data: automatic interpretation using an operational interpretation model based on key time points.
9. A launch vehicle flight verification test system, equipped with a launch vehicle flight verification test method according to any one of claims 1 to 8, characterized in that: include: Flight parameter analysis module, test data generation module, test execution module, telemetry data judgment module and test result display module; The flight parameter analysis module is used to receive flight parameters, analyze the flight parameters and transmit them to the test data generation module; The test data generation module is used to filter the parsed flight parameters according to the configuration file, generate corresponding test data, and send the test data to the test execution module and the telemetry data judgment module; The test execution module is used to call the corresponding test environment, load the test data into it, generate telemetry data, and send the generated telemetry data to the telemetry data interpretation module; The telemetry data interpretation module is used to convert the telemetry data into physical quantities according to the configuration file, and automatically interpret the data to determine whether the current physical quantity is out of tolerance, and transmit the automatic interpretation result to the test result display module; The test result display module is used to display whether the test is passed according to the judgment result.