CN112148257B - Flight control software reliability design method and device and computer storage medium - Google Patents

Flight control software reliability design method and device and computer storage medium Download PDF

Info

Publication number
CN112148257B
CN112148257B CN202010955404.1A CN202010955404A CN112148257B CN 112148257 B CN112148257 B CN 112148257B CN 202010955404 A CN202010955404 A CN 202010955404A CN 112148257 B CN112148257 B CN 112148257B
Authority
CN
China
Prior art keywords
ignition
takeoff
logic
time sequence
control software
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010955404.1A
Other languages
Chinese (zh)
Other versions
CN112148257A (en
Inventor
胡骁
李�浩
张亚琳
潘彦鹏
张雪婷
陈旭东
吕瑞
涂海峰
严大卫
陈喆
葛云鹏
梁卓
宋志国
张东
蔡亚楠
王凯旋
李迎博
薛晨琛
李烨
谭黎立
杨立杰
丁禹
赵楠
陈铁凝
郝仁杰
丘岳诗
孟文霞
姜春旺
杜肖
谭清科
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Academy of Launch Vehicle Technology CALT
Original Assignee
China Academy of Launch Vehicle Technology CALT
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Academy of Launch Vehicle Technology CALT filed Critical China Academy of Launch Vehicle Technology CALT
Priority to CN202010955404.1A priority Critical patent/CN112148257B/en
Publication of CN112148257A publication Critical patent/CN112148257A/en
Application granted granted Critical
Publication of CN112148257B publication Critical patent/CN112148257B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/20Software design
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B64AIRCRAFT; AVIATION; COSMONAUTICS
    • B64CAEROPLANES; HELICOPTERS
    • B64C13/00Control systems or transmitting systems for actuating flying-control surfaces, lift-increasing flaps, air brakes, or spoilers
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/31Programming languages or programming paradigms
    • G06F8/315Object-oriented languages

Abstract

The flight control software reliability design method, the flight control software reliability design device and the computer storage medium comprise the following steps: acquiring a flight profile; determining key time sequence actions and the dependency relationship thereof according to the flight profile; identifying a minimum preamble time sequence set of the action to be judged according to the key time sequence action and the dependency relationship thereof; and judging the minimum preamble time sequence set. According to the scheme, a minimized preorder logic guarantee mechanism is provided, on one hand, the sequence and conditions of logic conversion are restrained, on the other hand, the preposed guarantee requirement is minimized, the mark judgment error caused by the abnormity of 'irrelevant' information is prevented, and the reliability of flight control software is effectively improved.

Description

Flight control software reliability design method and device and computer storage medium
Technical Field
The present application relates to flight control technologies, and in particular, to a method and an apparatus for designing reliability of flight control software, a computer storage medium, and an electronic device.
Background
The flight control software is the most critical software of the rocket and plays a role in harmony of the success or failure of the flight test. The correctness of the flight control software determines the accuracy of the calculation result under the normal branch, and the reliability of the flight control software determines the robustness of the calculation result under the abnormal branch. In general, a flight control system semi-physical simulation test fully examines the correctness of flight control software, but the reliability examination of the flight control software is relatively weak due to the difference between the flight environment and the test environment, so that the reliability design of the flight control software needs to be focused.
The flight control software is used as arrow embedded software, the calculation time of the flight control software is constrained forcibly, and the reliability of the traditional flight control software is designed mainly from the software level and is not high.
Disclosure of Invention
The embodiment of the application provides a flight control software reliability design method and device, a computer storage medium and electronic equipment, so as to solve the technical problems.
According to a first aspect of the embodiments of the present application, there is provided a flight control software reliability design method, including the following steps:
acquiring a flight profile;
determining key time sequence actions and the dependency relationship thereof according to the flight profile;
identifying a minimum preamble time sequence set of the action to be judged according to the key time sequence action and the dependency relationship thereof;
and judging the minimum preamble time sequence set.
According to a second aspect of the embodiments of the present application, there is provided a flight control software reliability designing apparatus, including:
the acquisition module is used for acquiring a flight profile;
the determining module is used for determining key time sequence actions and the dependency relationship thereof according to the flight profile;
the identification module is used for identifying the minimum preamble time sequence set of the action to be judged according to the key time sequence action and the dependency relationship thereof;
and the judging module is used for judging the minimum preamble time sequence set.
According to a third aspect of embodiments herein, there is provided a computer storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the flight control software reliability design method as described above.
According to a fourth aspect of embodiments herein, there is provided an electronic device comprising one or more processors, and memory for storing one or more programs; the one or more programs, when executed by the one or more processors, implement a flight control software reliability design method as described above.
According to the flight control software reliability design method and device, the computer storage medium and the electronic device, a minimized preorder logic guarantee mechanism is provided, on one hand, the sequence and conditions of logic conversion are constrained, on the other hand, the preposed guarantee requirement is minimized, the mark judgment error caused by the abnormity of 'irrelevant' information is prevented, and the reliability of the flight control software is effectively improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a schematic flow chart diagram illustrating an implementation of a reliability design method for flight control software according to an embodiment of the present application;
FIG. 2 is a schematic structural diagram of a flight control software reliability design device in a second embodiment of the present application;
fig. 3 shows a schematic structural diagram of an electronic device in the fourth embodiment of the present application.
Detailed Description
In the process of implementing the present application, the inventors found that:
the flight control software is used as arrow embedded software, the calculation time of the flight control software is forcibly restricted, and according to statistics, the flight control software occupies a longer time and is used for calculating navigation, guidance and attitude control, so that the development of joint optimization design is urgently needed, and the equivalent calculation overhead is reduced on the premise of ensuring the accuracy of a calculation result.
The 'ignition takeoff' is used for space launching and plays a crucial role, once the 'ignition takeoff' fails, serious consequences such as spacecraft explosion and the like can be caused, and huge economic loss and casualties are caused. The 'calculation flow' plays a crucial role in flight control, and once the 'calculation flow' fails, the generated control command may be wrong, and in a serious case, the flight test is directly lost. The 'information acquisition' is performed in flight test, plays a crucial role, and once the 'information acquisition' fails, the 'information acquisition' may cause the timing action to be executed in advance, and in severe cases, the 'information acquisition' directly causes the flight test to be disqualified.
The traditional reliability design of the flight control software is mainly considered from a software level, and the degree of special combination with the flight control software is insufficient.
In order to solve the above problems, the embodiments of the present application provide a reliability design method that takes "joint optimization", "ignition takeoff", "calculation flow" and "information acquisition" as key points and fully considers the key timing sequence actions in the flight process, with respect to the key timing sequence actions in the flight process.
The scheme in the embodiment of the application can be implemented by adopting various computer languages, such as object-oriented programming language Java and transliterated scripting language JavaScript.
In order to make the technical solutions and advantages of the embodiments of the present application more apparent, the following further detailed description of the exemplary embodiments of the present application with reference to the accompanying drawings makes it clear that the described embodiments are only a part of the embodiments of the present application, and are not exhaustive of all embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
Example one
Fig. 1 shows a flow chart of an implementation of a flight control software reliability design method in an embodiment of the present application.
As shown in the figure, the flight control software reliability design method comprises the following steps:
step 101, acquiring a flight profile;
step 102, determining a key time sequence action and a dependency relationship thereof according to the flight profile;
step 103, identifying a minimum preamble time sequence set of the action to be judged according to the key time sequence action and the dependency relationship thereof;
and 104, judging the minimum preamble time sequence set.
In specific implementation, the critical timing action may be determined according to a flight profile and a preset rule. The dependency of the critical timing action may be determined from a flight control process, for example: the execution of a certain sequence of actions needs to be performed when a certain number of sequence of actions are completed or conditions are met.
According to the flight control software reliability design method provided by the embodiment of the application, a minimized preorder logic guarantee mechanism is provided, on one hand, the sequence and conditions of logic conversion are restrained, on the other hand, the preposed guarantee requirement is minimized, the mark judgment error caused by the abnormity of 'irrelevant' information is prevented, and the reliability of the flight control software is effectively improved.
In one embodiment, the method further comprises:
and the preorder actions of which the time sequence actions or the minimum preorder set do not occur are not examined.
In one embodiment, the method further comprises:
identifying data variables that are not immediately used and data variables that are state-ambiguous;
determining a derived flag variable according to a data variable which is not used immediately and a data variable with an undefined state; the derived flag variable is used for representing the acquisition condition of the data variable;
when a data variable which is not immediately used or a data variable whose state is unclear is used, a derived flag variable is first determined, and the data variable which is not immediately used or the data variable whose state is unclear is used according to the determination result of the derived flag variable.
In one embodiment, the method further comprises:
performing an ignition control operation according to a predetermined ignition logic; the ignition logic comprises normal ignition logic and reserve ignition logic; the ignition mark is supplemented when the backup ignition is carried out; interrupt enable is turned off when the ignition flag is set; the backup firing logic includes that a takeoff flag is set and a backup firing criterion is met;
the ignition zero point is recorded.
In one embodiment, the method further comprises:
executing takeoff control operation according to predetermined takeoff logic; the takeoff logic comprises normal takeoff logic and reserve takeoff logic; when the reserve takeoff is carried out, a takeoff mark is supplemented; interrupting enabling and closing when the takeoff flag is set; the reserve takeoff logic comprises that an ignition mark is set, the starting judgment time of reserve takeoff is reached, and reserve takeoff criterion is met;
the ignition zero point is updated.
In one embodiment, the ignition flag or takeoff flag setting timing is as follows:
setting the ignition flag bit when the normal ignition condition or the reserved ignition condition is met;
setting the reserve ignition flag bit when the reserve ignition condition is met;
setting the takeoff flag bit when the normal takeoff condition or the reserve takeoff condition is met;
and setting the standby takeoff flag bit when the standby takeoff condition is met.
In one embodiment, the method further comprises:
for the unit level, optimizing a function in the flight control software according to the calculation requirement of the predetermined flight control software so as to reduce the calculation overhead of the unit level or the loop body;
for the module level, identifying static data amount in the flight process, storing the static data amount by using a global variable, and transmitting dynamic data amount required by both a guidance module and an attitude control module to a navigation module for calculation;
for the logic level, the complexity of the Kalman algorithm is increased to increase the calculation period of the Kalman algorithm, or the complexity of the precondition preparation algorithm is increased when the pilot module calculates that the precondition needs to be prepared online and the calculation expense of the precondition is more than a preset threshold value.
In particular, the optimization of the function in the flight control software may include pre-storing the result of the preset function of the first variable as the second variable, or adding a precondition or condition for execution to the preset function.
Example two
Based on the same invention concept, the embodiment of the application provides a flight control software reliability design device, the principle of the device for solving the technical problem is similar to a flight control software reliability design method, and repeated parts are not repeated.
Fig. 2 shows a schematic structural diagram of a flight control software reliability design device in the second embodiment of the present application.
As shown in the figure, the flight control software reliability designing device includes:
an obtaining module 201, configured to obtain a flight profile;
a determining module 202, configured to determine a key timing action and a dependency relationship thereof according to the flight profile;
the identification module 203 is configured to identify a minimum preamble time sequence set of the action to be determined according to the key time sequence action and the dependency relationship thereof;
a judging module 204, configured to judge the minimum preamble timing set.
The flight control software reliability design device provided in the embodiment of the application provides a minimized preorder logic guarantee mechanism, on one hand, the order and conditions of logic conversion are constrained, on the other hand, the preposed guarantee requirement is minimized, the mark judgment error caused by the abnormity of 'irrelevant' information is prevented, and the reliability of the flight control software is effectively improved.
In one embodiment, the determining module is further configured to not qualify a preamble action that does not occur in a timing sequence or a minimum preamble set.
In one embodiment, the apparatus further comprises:
the variable identification module is used for identifying data variables which are not used immediately and data variables with ambiguous states;
the derivation determining module is used for determining a derivation flag variable according to the data variable which is not used immediately and the data variable with an undefined state; the derived flag variable is used for representing the acquisition condition of the data variable;
and the execution module is used for judging the derivative flag variable when the data variable which is not used immediately or the data variable with an undefined state is used, and using the data variable which is not used immediately or the data variable with an undefined state according to the judgment result of the derivative flag variable.
In one embodiment, the apparatus further comprises:
the ignition control module is used for executing ignition control operation according to predetermined ignition logic; the ignition logic comprises normal ignition logic and reserve ignition logic; the ignition mark is supplemented when the backup ignition is carried out; interrupt enable is turned off when the ignition flag is set; the backup firing logic includes a takeoff flag being set and backup firing criteria to be met; the ignition zero point is recorded.
In one embodiment, the apparatus further comprises:
the take-off control module is used for executing take-off control operation according to the predetermined take-off logic; the takeoff logic comprises normal takeoff logic and reserve takeoff logic; when the aircraft takes off in reserve, the takeoff mark is supplemented; interrupting enabling and closing when the takeoff flag is set; the reserve takeoff logic comprises that an ignition mark is set, the starting judgment time of reserve takeoff is reached, and reserve takeoff criterion is met; the ignition zero point is updated.
In one embodiment, the ignition flag or takeoff flag setting timing is as follows:
setting the ignition flag bit when the normal ignition condition or the reserved ignition condition is met;
setting the reserve ignition flag bit when the reserve ignition condition is met;
setting the takeoff flag bit when the normal takeoff condition or the reserve takeoff condition is met;
and setting the standby takeoff flag bit when the standby takeoff condition is met.
These conditions can be set according to actual needs in specific implementation, and are not described herein.
In one embodiment, the apparatus further comprises:
the unit-level processing module optimizes functions in the flight control software according to the predetermined calculation requirements of the flight control software so as to reduce the calculation overhead of a unit level or a cycle body;
the module-level processing module is used for identifying the static data volume in the flight process, storing the static data volume by using a global variable, and transmitting the dynamic data volume required by both the guidance module and the attitude control module to the navigation module for calculation;
and the logic level processing module increases the calculation period of the Kalman algorithm by increasing the complexity of the Kalman algorithm, or increases the complexity of the precondition preparation algorithm when the pilot module calculates that preconditions need to be prepared online and the calculation overhead of the preconditions is greater than a preset threshold.
EXAMPLE III
Based on the same inventive concept, embodiments of the present application further provide a computer storage medium, which is described below.
The computer storage medium has a computer program stored thereon, which when executed by a processor implements the steps of the flight control software reliability design method according to an embodiment.
The computer storage medium provided by the embodiment of the application provides a minimized preorder logic guarantee mechanism, on one hand, the order and the condition of logic conversion are restrained, on the other hand, the preposed guarantee requirement is minimized, the mark judgment error caused by the abnormity of 'irrelevant' information is prevented, and the reliability of flight control software is effectively improved.
Example four
Based on the same inventive concept, the embodiment of the present application further provides an electronic device, which is described below.
Fig. 3 shows a schematic structural diagram of an electronic device in the fourth embodiment of the present application.
As shown, the electronic device includes memory 301 for storing one or more programs, and one or more processors 302; the one or more programs, when executed by the one or more processors, implement a flight control software reliability design method as described in embodiment one.
The electronic equipment provided by the embodiment of the application provides a minimized preorder logic guarantee mechanism, on one hand, the order and the condition of logic conversion are restrained, on the other hand, the preposed guarantee requirement is minimized, the mark judgment error caused by the abnormity of 'irrelevant' information is prevented, and the reliability of flight control software is effectively improved.
EXAMPLE five
In order to facilitate the implementation of the present application, the embodiments of the present application are described with a specific example.
The embodiment of the application provides a reliability design, which specifically comprises:
1) the design method of reliable joint optimization is provided, the optimization design is developed from a unit level, a module level and a logic level, and the equivalent calculation overhead of flight control software is effectively reduced;
2) the design method for reliable ignition takeoff is provided, the mutual relation of an ignition mark, a reserve ignition mark, a takeoff mark and a reserve takeoff mark is set, a reserve processing mechanism of ignition logic and takeoff logic is provided, and the reliability of ignition takeoff is effectively improved;
3) the design method of the reliable calculation process is provided, common mathematical library functions are packaged, on the basis, a general design method of 'logic judgment + action execution + information arrangement' oriented to the complex calculation process is provided, and the reliability of the calculation process is effectively improved;
4) a design method for reliable information acquisition is provided, a minimized preorder logic guarantee mechanism is provided for mark variables, a derived mark protection mechanism is provided for data variables, and the reliability of information acquisition is effectively improved.
In particular, the method comprises the following steps of,
design method for reliable joint optimization
The optimization design is developed from the unit level, the module level and the logic level to reduce the computational overhead in the control cycle.
1) Unit level:
a) avoiding directly using sin, cos, pow and other functions repeatedly, replacing each basic function by a primary parameter quantity, replacing a function formed by the primary parameter quantities of more than two basic functions by a secondary parameter quantity, and so on, replacing a function formed by more than two ith-level parameter quantities by i + 1-level parameter quantities. In the embodiment of the application, the computer is considered to be fast to perform simple addition, subtraction, multiplication and division, but the functions are complex to calculate and low in speed, so that the embodiment of the application proposes that the function result of the variable X is taken as another variable Y to be stored in advance, and the variable Y is directly called when the function is called subsequently.
Specific examples are as follows:
Figure BDA0002678427050000091
b) the calculation overhead of the loop body is reduced, and specific examples are as follows:
Figure BDA0002678427050000101
c) and function functions and interfaces are optimized, and repeated execution of the same calculated amount among different functions is avoided.
2) Module level:
a) identifying static data amount in the flight process, storing data (preset according to actual requirements in specific implementation) with invariable ignition starting by using a global variable, and ensuring that the whole flight process is calculated only once, for example, a transformation matrix of an emission coordinate system and a geocentric coordinate system;
b) in the traditional method, a scheduling module needs to communicate with a navigation module to determine a target position, then the scheduling module communicates with a guidance module to calculate a path, and finally the scheduling module communicates with an attitude control module to calculate data such as an attitude angle.
3) And a logic stage: the flight control software pays attention to the calculation cost in a control period, so that the calculation process can be reasonably planned, the calculation cost in the control period is reduced by properly increasing the total calculation cost, and a typical application scenario is as follows:
a) assuming that the period of kalman filtering is T1 and the control period is T2, the computation overhead in a single control period can be effectively reduced by increasing the complexity of the kalman algorithm (i.e. increasing the total computation overhead), relaxing its computation period to N T2 (ensuring N < INT (T1/T2)), and placing the computation process in N T2 (the computation overhead in each T2 becomes smaller, and there is room for sending instructions);
b) assuming that the guidance module needs to prepare the preconditions online (calculating the interpolation table online according to the flight conditions), but the calculation cost of the preconditions is high, the calculation period can be widened to NxT 2 by increasing the complexity of the precondition preparation algorithm (i.e. increasing the total calculation cost), so that the calculation cost in a single control period is effectively reduced.
Design method for reliable ignition takeoff
The method comprises the steps of firstly defining the definition and setting time of a zone bit, then designing logic branches of reserve ignition and reserve takeoff, respectively embedding the logic branches into an ignition logic branch and a takeoff logic branch, and finally designing the compensation logic of the takeoff flag and the ignition zero in consideration of the extremely strict requirement of the flight process on the ignition zero, so that the reliability of the ignition takeoff logic is ensured under the condition of one-degree fault.
(1) Flag bit definition and setting time
The definition and the setting time of the ignition takeoff flag bit are shown in the following table:
Figure BDA0002678427050000111
(2) backup logic
The design logic for the reserve ignition is as follows:
1) the takeoff mark is set;
2) the backup firing criteria are met.
The design logic for reserve takeoff is as follows:
1) the ignition flag has been set;
2) the starting judgment time of the reserve takeoff is reached;
3) the reserve takeoff criterion is met.
(3) Firing logic
Considering normal ignition and reserve ignition, designing an ignition logic, which specifically comprises the following steps:
1) designing an initialization logic;
2) designing a normal ignition logic;
3) designing reserved ignition logic;
4) when the ignition is reserved, the additional design of an ignition mark is carried out;
5) when the ignition flag is set, the interrupt enable design is closed;
6) design of ignition zero point recording.
(4) Takeoff logic
Considering normal takeoff and reserve takeoff, designing takeoff logic, specifically comprising:
1) designing an initialization logic;
2) designing normal takeoff logic;
3) designing a reserve takeoff logic;
4) when the takeoff is reserved, the takeoff mark is designed in a complementary mode;
5) when the takeoff flag is set, the interrupt enabling design is closed;
6) and (4) designing ignition zero point updating.
(III) design method of reliable calculation flow
Common mathematical functions are packaged, a general design method of 'logic judgment + action execution + information arrangement' oriented to a complex calculation process is provided, and the reliability of the calculation process is effectively improved.
(1) Mathematical function encapsulation
General computational requirements of flight control software include:
1) inhibiting the zero-removing operation;
2) forbidding opening even square roots on the negative numbers;
3) the inverse trigonometric function requires range protection.
For the above requirements, the corresponding mathematical functions can be customized as shown in the following table:
Figure BDA0002678427050000121
Figure BDA0002678427050000131
using double SavedAsin (double t) as an example, encapsulation is described as follows:
Double SavedAsin(double t)
{
double dResult=0.0;
if(t>=1.0)
{
dResult=Pi/2.0;
}
else if(t<=-1.0)
{
dResult=-Pi/2.0;
}
else
{
dResult=asin(t);
}
return dResult;
}
in the above example, it can be seen that, in the embodiment of the present application, before a value is transmitted to an asin function, it is determined whether the value is between-1 and 1, and then the value is input to the asin function, otherwise, pi/2 or-pi/2 is directly returned, which is higher in reliability compared with the prior art (conventionally, no determination step is directly input to the function, and if the value exceeds 1, an error is reported).
By encapsulating the reliability calculation requirements into functions, not only can the overall code scale be reduced, but also the consistency and correctness of all relevant calculations are ensured.
(2) General design method
1) And (4) logical judgment: the part is directly related to instruction calculation, and has the main functions of accurately acquiring the current flight stage and completing the preparation of calculation conditions;
2) and (3) executing actions: the part is directly related to instruction calculation, and the main function is to complete the calculation of the instruction according to the flight stage;
3) information arrangement: this part is not directly related to the instruction calculation, the main function being to output telemetry.
The improved features of the present application with respect to the general design are:
1) according to the correlation calculated by the instruction, the correlation is divided into 'logic judgment + action execution' + 'information sorting', the central service and the auxiliary service are separated, the probability of artificial coding errors is reduced, and the reliability of flight control software is improved;
2) according to the thought of judging first and then executing, the logic judgment and the action execution are separated, the maintainability of codes is enhanced, the development situation of demand agile iteration is adapted, the probability of artificial coding errors is reduced, and the reliability of flight control software is further improved.
Design method for acquiring reliable information
The embodiment of the application provides a minimum preamble logic guarantee mechanism, on one hand, the order and the condition of logic conversion are restricted, on the other hand, the requirement of the pre-guarantee is minimized, and the error judgment of the mark caused by the abnormity of 'irrelevant' information is prevented. Meanwhile, the embodiment of the application provides a derived flag protection mechanism aiming at the data variable used in a cross-domain mode, so that data is prevented from being used wrongly under an abnormal condition, and the reliability of information acquisition is effectively improved.
(1) Minimum guarantee
The design principle of minimum guarantee includes:
1) identifying a minimum preamble time sequence set of the action to be judged according to the key time sequence action;
for example: taking 5 flight phases as an example, assuming that in the first flight phase, the second flight phase can be executed only when a judgment is satisfied conventionally, for example, when determining whether to start the engine No. 2, the embodiment of the present application only needs to identify whether the engine No. 1 is started, and does not need to identify the engine No. 3 (because it is definitely off theoretically); in determining whether to start the engine # 3, there is no need to pay attention to whether the engine # 1 is on or off (because the judgment to the engine # 3 has already been performed, the engine # 1 is theoretically certainly on).
2) Judging only aiming at the identified minimum forward sequence set, and not checking the forward sequence action of the minimum forward sequence set;
3) and no time sequence action is performed, and no examination is performed.
(2) Derived protection mechanisms
The design principle of the derived protection mechanism comprises:
1) defining a derived flag variable aiming at a data variable which is not used immediately, wherein the derived flag variable is used for representing the acquisition condition of the data variable;
2) aiming at data variables with undefined states, defining derived flag variables for representing the acquisition condition of the data variables;
3) when the two types of data variables are used, the derived flag variables are judged first, and the validity of data acquisition is ensured.
For example: acquiring ignition time in a fourth flight phase, wherein a time interval is formed between the ignition time and subsequent flight, and if certain information of the ignition time needs to be utilized in the subsequent flight process, judging whether a derived flag variable is true or not, and if so, indicating that a correct data variable is stored or acquired; if the data variable is false, the data variable is abnormal from the ignition moment to the acquisition moment, and the data variable is not used, so that abnormal shutdown and other phenomena are avoided.
In summary, the specific process of the reliability design in the embodiment of the present application may be as follows:
1) acquiring and analyzing a flight profile, knowing and mastering key time sequence actions and dependency relationship thereof, and designing a guarantee strategy for minimizing a preposed time sequence;
2) identifying data variables which are not used immediately and data variables with undefined states, and designing derivative flag variables;
3) from three levels of single machine level, module level and logic level, a general method for reducing the calculation overhead in the control period is considered;
4) packaging a common mathematical function;
5) carrying out ignition takeoff logic design according to the proposed ignition takeoff logic;
6) and developing module design according to a general design method of logic judgment, action execution and information arrangement.
The reliability design provided by the embodiment of the application has the following advantages:
the design of reliable joint optimization provides a general method for reducing the calculation overhead in a control period from three levels of a single machine level, a module level and a logic level, and effectively improves the reliability of flight control software;
the design of reliable ignition take-off defines the definition and the setting time of the flag bit, designs the complete ignition take-off logic and ensures the reliability of the ignition take-off logic under the condition of one-time fault;
the design of the reliable calculation flow encapsulates common mathematical functions, provides a general design method of 'logic judgment + action execution + information arrangement', and effectively improves the reliability of flight control software;
the design of reliable information acquisition designs a minimum preorder logic guarantee mechanism, provides a derived mark protection mechanism, and effectively improves the reliability of flight control software.
The reliability design method provided by the embodiment of the application can adapt to the reliability design of various flight control software, has the characteristic of universality, and can be popularized and used.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims (9)

1. A flight control software reliability design method is characterized by comprising the following steps:
acquiring a flight profile;
determining key time sequence actions and the dependency relationship thereof according to the flight profile;
identifying a minimum preamble time sequence set of the action to be judged according to the key time sequence action and the dependency relationship thereof;
judging the minimum preamble time sequence set;
and the preorder actions of which the time sequence actions or the minimum preorder set do not occur are not examined.
2. The method of claim 1, further comprising:
identifying data variables that are not immediately used and data variables that are state-ambiguous;
determining a derived flag variable according to a data variable which is not used immediately and a data variable with an undefined state; the derived flag variable is used for representing the acquisition condition of the data variable;
when a data variable which is not immediately used or a data variable whose state is unclear is used, a derived flag variable is first determined, and the data variable which is not immediately used or the data variable whose state is unclear is used according to the determination result of the derived flag variable.
3. The method of claim 1, further comprising:
performing an ignition control operation according to a predetermined ignition logic; the ignition logic comprises normal ignition logic and reserve ignition logic; the ignition mark is supplemented when the backup ignition is carried out; interrupt enable is turned off when the ignition flag is set; the backup firing logic includes that a takeoff flag is set and a backup firing criterion is met;
the ignition zero point is recorded.
4. The method of claim 1, further comprising:
executing takeoff control operation according to predetermined takeoff logic; the takeoff logic comprises normal takeoff logic and reserve takeoff logic; when the aircraft takes off in reserve, the takeoff mark is supplemented; interrupting enabling and closing when the takeoff flag is set; the reserve takeoff logic comprises that an ignition mark is set, the starting judgment time of reserve takeoff is reached, and reserve takeoff criterion is met;
the ignition zero point is updated.
5. The method of claim 3 or 4, wherein the ignition or takeoff flag set timings are as follows:
setting the ignition flag bit when the normal ignition condition or the reserved ignition condition is met;
setting the reserve ignition flag bit when the reserve ignition condition is met;
setting the takeoff flag bit when the normal takeoff condition or the reserve takeoff condition is met;
and setting the standby takeoff flag bit when the standby takeoff condition is met.
6. The method of claim 1, further comprising:
for the unit level, optimizing a function in the flight control software according to the calculation requirement of the predetermined flight control software so as to reduce the calculation overhead of the unit level or the loop body;
for the module level, identifying static data amount in the flight process, storing the static data amount by using a global variable, and transmitting dynamic data amount required by both a guidance module and an attitude control module to a navigation module for calculation;
for the logic level, the complexity of the Kalman algorithm is increased to increase the calculation period of the Kalman algorithm, or the complexity of the precondition preparation algorithm is increased when the pilot module calculates that the precondition needs to be prepared online and the calculation expense of the precondition is more than a preset threshold value.
7. A flight control software reliability design device, comprising:
the acquisition module is used for acquiring a flight profile;
the determining module is used for determining key time sequence actions and the dependency relationship thereof according to the flight profile;
the identification module is used for identifying the minimum preamble time sequence set of the action to be judged according to the key time sequence action and the dependency relationship thereof;
and the judging module is used for judging the minimum preamble time sequence set and not checking the preamble actions which do not occur or the minimum preamble set.
8. A computer storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 6.
9. An electronic device comprising one or more processors, and memory for storing one or more programs; the one or more programs, when executed by the one or more processors, implement the method of any of claims 1 to 6.
CN202010955404.1A 2020-09-11 2020-09-11 Flight control software reliability design method and device and computer storage medium Active CN112148257B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010955404.1A CN112148257B (en) 2020-09-11 2020-09-11 Flight control software reliability design method and device and computer storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010955404.1A CN112148257B (en) 2020-09-11 2020-09-11 Flight control software reliability design method and device and computer storage medium

Publications (2)

Publication Number Publication Date
CN112148257A CN112148257A (en) 2020-12-29
CN112148257B true CN112148257B (en) 2022-08-09

Family

ID=73889513

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010955404.1A Active CN112148257B (en) 2020-09-11 2020-09-11 Flight control software reliability design method and device and computer storage medium

Country Status (1)

Country Link
CN (1) CN112148257B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101894068A (en) * 2010-05-31 2010-11-24 北京航空航天大学 Embedded software reliability accelerated test method
CN108897676A (en) * 2018-06-06 2018-11-27 中国人民解放军海军工程大学 Flight guidance control software reliability analysis System and method for based on formation rule
CN110941561A (en) * 2019-12-05 2020-03-31 北京星际荣耀空间科技有限公司 Flight control software evaluation method, device and system
CN111488276A (en) * 2020-04-07 2020-08-04 北京航空航天大学 Software reliability testing method and device based on code tracking

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101894068A (en) * 2010-05-31 2010-11-24 北京航空航天大学 Embedded software reliability accelerated test method
CN108897676A (en) * 2018-06-06 2018-11-27 中国人民解放军海军工程大学 Flight guidance control software reliability analysis System and method for based on formation rule
CN110941561A (en) * 2019-12-05 2020-03-31 北京星际荣耀空间科技有限公司 Flight control software evaluation method, device and system
CN111488276A (en) * 2020-04-07 2020-08-04 北京航空航天大学 Software reliability testing method and device based on code tracking

Also Published As

Publication number Publication date
CN112148257A (en) 2020-12-29

Similar Documents

Publication Publication Date Title
US10867028B2 (en) Program-instruction-controlled instruction flow supervision
Laprie Dependability evaluation of software systems in operation
Korel et al. Automated regression test generation
US20150150024A1 (en) Method of detecting stack overflows and processor for implementing such a method
US20110314264A1 (en) Key allocation when tracing data processing systems
US20210365555A1 (en) A method and system for detecting and preventing issues in smart contracts based on historical behavior analysis
Garrett et al. Context in the risk assessment of digital systems
CN112148257B (en) Flight control software reliability design method and device and computer storage medium
US9582299B2 (en) Electronic system, onboard modular execution platform and method ensuring partitioning of configurable decision-making rules
CN112463133B (en) Coq-based verification method for time sequence safety of robot control system
CN111752732A (en) Enhanced anomaly prediction and management in real-time security critical embedded applications
US20050066311A1 (en) Autonomic execution tracking and correction of functions
CN113886119B (en) Fault repairing method and device
US10108530B2 (en) Method and tool for generating a program code configured to perform control flow checking on another program code containing instructions for indirect branching
Riefert et al. Identification of critical variables using an FPGA-based fault injection framework
Czerny et al. Effective application of software safety techniques for automotive embedded control systems
US8458790B2 (en) Defending smart cards against attacks by redundant processing
US11477030B2 (en) Method for improving safety of a component or system running a firmware or a finite state machine
CN109032932B (en) Constraint-supported combined test fault positioning method
CN112278328B (en) Satellite attitude control software protection method, device, equipment and storage medium
CN109947476A (en) A kind of statistical method and system in run time stack space
Velev et al. Automatic formal verification of reconfigurable dsps
Kovalev et al. Implementation of multiversion software based on an object-oriented approach
CN112181842B (en) Flight control software agility test method and system, terminal and storage medium
CN116467131B (en) ECC function verification method, device, medium and equipment of processor

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant