Thrust allocation using optimization in distributed flight control system
A distributed flight control system with an optimization-based thrust allocation ensures safe emergency landings for eVTOL multicopters by independently controlling rotor blades, addressing the safety concerns of motor failures.
Patent Information
- Application Number
- JP2024140555
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2020-02-19
- Filing Date
- 2024-08-22
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2041-02-01
AI Technical Summary
eVTOL multicopters lack wings for gliding in case of motor failure or emergency situations, posing safety concerns due to potential crashes.
A distributed flight control system using an optimization problem with a single solution to generate thrust values for each motor, ensuring safe and controlled emergency landings by independently controlling rotor blades even in the event of motor failures.
The system allows eVTOL multicopters to remain airborne and land safely with minimal shocks, avoiding crashes and enhancing passenger safety by optimizing thrust allocation during motor failures.
Smart Images

Figure 2024164134000001_ABST
Abstract
Description
[Technical field]
[0001] Personal air vehicles, such as electric vertical take-off and landing (eVTOL) multicopters, offer a way to get around congested highways and city streets. However, safety is an important consideration for such vehicles. In particular, such eVTOL multicopters do not have wings and therefore cannot glide in the event of a motor failure or other emergency. New techniques and / or systems that make air vehicles, such as eVTOL multicopters, safer are desired. [Background technology]
[0002] Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings. [Brief description of the drawings]
[0003] [Figure 1] 4 is a flow diagram illustrating an embodiment of a process for generating thrust values using an optimization problem having a single solution and achieving those thrust values on a motor.
[0004] [Diagram 2] 1 is a diagram illustrating an embodiment of an electric vertical take-off and landing (eVTOL) multicopter.
[0005] [Figure 3A] FIG. 1 is a schematic diagram of a top view illustrating an embodiment of an eVTOL multicopter hovering with the associated rotor rotation directions and rotation rates shown.
[0006] [Figure 3B] FIG. 1 is a schematic diagram of a top view illustrating an embodiment of an eVTOL multicopter making a right turn with the associated rotor rotational direction and speed shown.
[0007] [Figure 3C]FIG. 1 is a schematic diagram of a top view illustrating an embodiment of a forward pitching eVTOL multicopter with associated rotor rotation directions and speeds shown.
[0008] [Figure 4] 1 is a diagram illustrating an example of a flight control system with redundant flight control devices and decision blocks.
[0009] [Diagram 5] 1 is a diagram illustrating an embodiment of a distributed flight control system, in this example, the number of flight controllers is equal to the number of motors.
[0010] [Figure 6] 1 is a schematic diagram of a top view illustrating an embodiment of an eVTOL multicopter with a motor failure.
[0011] [Figure 7] 1 is a diagram illustrating an example of a stepwise thrust allocation process. In this example of thrust allocation, thrust is allocated in steps.
[0012] [Figure 8] 11 is a flow diagram illustrating an embodiment of a process for generating thrust values, including by using a maximum thrust vector.
[0013] [Figure 9] 11 is a flow diagram illustrating an embodiment of a process for generating thrust values, including by tracking whether any of the thrust values are actively constrained.
[0014] [Figure 10] 11 is a flow diagram illustrating an embodiment of a process for generating thrust values, including by using axial weighting parameters.
[0015] [Figure 11] 1 is a flow diagram illustrating an embodiment of a process for generating thrust values where the optimization problem has multiple parts or terms associated with different objectives. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0016] The present invention can be implemented in a variety of ways, including as a process, an apparatus, a system, a composition of matter, a computer program product embodied on a computer-readable storage medium, and / or a processor, such as a processor configured to execute instructions stored and / or provided by a memory coupled to the processor. These implementations, or any other form the present invention may take, may be referred to herein as techniques. In general, the order of steps of the disclosed processes may be varied within the scope of the present invention. Unless otherwise specified, components such as a processor or memory described as being configured to perform a task may be implemented as general components temporarily configured to perform the task at a given time, or as specific components manufactured to perform the task. As used herein, the term "processor" refers to one or more devices, circuits, and / or processing cores configured to process data, such as computer program instructions.
[0017] A detailed description of one or more embodiments of the present invention is provided below along with the accompanying figures illustrating the principles of the present invention. Although the present invention will be described in connection with such embodiments, the present invention is not limited to any embodiment. The scope of the present invention is limited only by the claims, and the present invention encompasses numerous alternatives, modifications, and equivalents. In order to provide a thorough understanding of the present invention, numerous specific details are set forth in the following description. These details are provided for illustrative purposes, and the present invention may be practiced according to the claims without some or all of these specific details. For the sake of clarity, technical subjects that are well known in the art related to the present invention have not been described in detail so as not to unnecessarily obscure the present invention.
[0018] Various embodiments of a distributed flight control system are described herein that perform thrust allocation (i.e., generate thrust values for the motors in the vehicle) using an optimization problem that has a single solution. In some examples described herein, the vehicle is an electric vertical take-off and landing (eVTOL) multicopter in which each of the rotors (motors) is independently controllable and thrust values are generated using the techniques described herein. As described in more detail below, the benefits of the systems and / or techniques described herein are particularly evident and / or useful in the presence of motor failure. For example, the systems and / or techniques described herein may allocate thrust in a manner that allows for a safer and / or more controlled emergency landing in the event of one or more motor failures. The following figure describes one such embodiment of a distributed flight control system that performs thrust allocation using convex optimization.
[0019] 1 is a flow diagram illustrating an embodiment of a process for generating thrust values using an optimization problem having a single solution and for causing motors to achieve those thrust values. As described above, in some embodiments, the process is performed by and / or within the eVTOL aircraft.
[0020] In 100, thrust values for multiple motors in an aircraft are generated using multiple flight control devices, with each flight control device in the multiple flight control devices generating thrust values for each motor in the multiple motors using an optimization problem that has a single solution. For example, assume there are N motors and N flight control devices in an aircraft. Each of the flight control devices generates thrust values using a strictly convex or strictly concave optimization problem (e.g., finding the minimum of a strictly convex optimization function, described in more detail below). Because the optimization problem (e.g., performed by the flight control devices) is strictly convex or strictly concave, there is a single unique solution. This allows all flight computers to perform thrust allocation in parallel, but still arrive at the same solution, thereby enabling a distributed flight control system architecture. In various embodiments, the flight control devices may be implemented in hardware (e.g., application-specific integrated circuit (ASIC), field-programmable gate array (FPGA)), or software (e.g., firmware running on an embedded microprocessor).
[0021] At 102, for each flight controller among the plurality of flight controllers, one of the generated thrust values is passed to a corresponding motor among the plurality of motors, and other thrust values generated for that flight controller terminate at that flight controller. For example, assume a first flight controller generates ten thrust values for motors indexed or numbered 1 through 10, respectively. The first generated thrust value (associated with and / or indexed with the first motor) is passed to that first motor. Other generated thrust values obtained from the first flight controller are not connected to any motors and terminate at the first flight controller. For a second flight controller, the second generated thrust value is passed to a second motor, but other generated thrust values are not connected to any motors, etc.
[0022] At 104, the passed thrust values are realized using multiple motors. In other words, the motors achieve the thrust values they receive (e.g., a first motor realizes a first thrust value obtained from a first flight controller, a second motor realizes a second thrust value obtained from a second flight controller, etc.). As described in more detail below, in the event of a motor failure, this process may result in a better emergency landing (e.g., a safer and / or more controlled descent).
[0023] To better understand the process of Figure 1, it may be helpful to describe an exemplary vehicle that performs the process described above. The following diagram describes an exemplary eVTOL aircraft that controls its motors using the process of Figure 1.
[0024] FIG. 2 is a diagram illustrating an embodiment of an electric vertical take-off and landing (eVTOL) multicopter. In this example, the eVTOL aircraft (200) is a multicopter with ten rotors (e.g., rotor 202). Each of the ten rotors is independently powered and / or controlled by its own motor and its own battery, not shown in FIG. 2. This independent controllability allows the eVTOL aircraft to perform a variety of maneuvers. The rotors are at fixed positions and angles. Thus, the motors are independently controlled to create desired forces and moments to maneuver or otherwise fly the aircraft. Some examples of maneuvers are described below.
[0025] FIG. 3A is a schematic diagram of a top view illustrating an embodiment of an eVTOL multicopter hovering with the associated rotor rotation directions and speeds shown. In this example of a vehicle hovering (shown in FIG. 2), the outer eight rotors (300a-307a) are rotating approximately equally so as to provide no overall momentum. Note, for example, that the magnitude of the curved arrows associated with rotors 300a-307a are approximately the same length. The direction of the arrow indicates the direction of rotation for a given rotor. The rotation speed (e.g., represented by the length of the curved arrow) of a given motor (rotor) is controlled by the thrust value generated for that motor (e.g., generated in step 100 of FIG. 1).
[0026] 3B is a schematic top view illustrating an embodiment of an eVTOL multicopter turning right with associated rotor rotation directions and speeds shown. In this example, the vehicle is pointing to the right, and therefore the clockwise rotating rotors (e.g., rotors 302b, 304b, 306b, and 307b) are rotated faster than the counterclockwise rotors (e.g., rotors 300b, 301b, 303b, and 305b). This maintains an overall normal force (e.g., thereby maintaining a stable height) while increasing the overall yaw moment (e.g., resulting in the vehicle turning).
[0027] 3C is a schematic top view illustrating an embodiment of an eVTOL multicopter that is pitched forward (downward) with the associated rotor rotation direction and speed shown. To provide the required pitching moment, the rear rotors (e.g., rotors 302c-305c) behind the center of mass rotate faster than the front rotors (e.g., rotors 300c, 301c, 306c, and 307c).
[0028] The control thrust values used to control the motors may be generated by various (control) systems. The following diagram describes an example of an older system with redundant flight control and decision blocks.
[0029] FIG. 4 is a schematic diagram showing an example of a flight control system with redundant flight controllers and decision blocks. In this example, which illustrates how other systems accomplish thrust allocation, three flight computers (400a-400c) are used to provide redundancy. The flight computers calculate the (desired) forces and moments (e.g., F z , M x , M y , and M. z ) for each flight computer. Each flight computer performs thrust allocation (e.g., generates thrust values) to produce the input and / or desired forces and moments. For example, flight controller A (400a) generates thrust values 1A-10A for motors 1-10, respectively. Similarly, flight controller B (400b) generates thrust values 1B-10B for motors 1-10, respectively, etc.
[0030] All of the generated thrust values are passed from the flight computers (400a-400c) to a decision block (402). The decision block uses all of the generated thrust values to reach a conclusion as to which thrust value to pass to the motors. For example, a voting scheme may be used where the decision block may compare the thrust values for a given motor from each of the flight computers (e.g., for motor 1, compare thrust values 1A-1C). If two or more of the thrust values for a given motor are the same, then that thrust value is output as a first consensus thrust value (e.g., consensus thrust 1) and passed to that motor (e.g., motor 1 (404a)). For example, if the thrust 1A obtained from flight control device A (400a) and the thrust 1B obtained from flight control device B (400b) for a first motor (404a) are the same, but the thrust 1C obtained from flight control device C (400c) is different, then decision block 402 will communicate (at least in this example voting scheme) a majority thrust value of thrusts 1A / 1B.
[0031] Similarly, a second coincident thrust value (e.g., coincident thrust 2) is generated by decision block (402) for a second motor (404b) based on the input thrust values for that motor (e.g., thrusts 2A, 2B, and 2C obtained from flight control device A (400a), flight control device B (400b), and flight control device C (400c), respectively). This is done for each motor in the system.
[0032] One drawback associated with the control system shown here is that the decision blocks (402) can become complicated. For example, to obtain redundancy, the decision blocks may have to be duplicated again, thereby requiring more communication channels and / or another layer of voting on the decision. More generally, decision blocks tend to become complicated. The following diagram shows an improved and / or simpler (control) system that is later found to be faster and / or better at achieving the desired forces and moments.
[0033] FIG. 5 is a diagram illustrating an embodiment of a distributed flight control system. In this example, the number of flight controllers is equal to the number of motors. Thus, in this example, there are 10 flight controllers (500a-500d) since there are 10 motors. In contrast, the number of flight controllers in the example of FIG. 4 is selected according to other design goals, and uses an odd number greater than or equal to two (e.g., for redundancy) and thus three flight controllers (e.g., because the example uses a voting system).
[0034] Each of the ten flight controllers in this example inputs the same desired thrust and moment and generates thrust values for each motor. Instead of using decision blocks, only the selected generated thrust values are connected and / or used to control the motors. For example, a first thrust value (associated with and / or for the first motor (502a)) obtained from the first flight controller (500a) is passed to the first motor (502a). Other generated thrust values obtained from the first flight controller (500a) are not connected and / or used. Other generated thrust values for the first motor (502a) generated by the second flight controller (500b) through the tenth controller (500d) are not connected and / or used to control the first motor (502a). Returning for a moment to FIG. 1, this is an example of how some of the generated thrust values end up at the flight control (e.g., thrust values 2 through 10 originating from flight control device 1 (500a) are not connected to any motors). In other words, each flight computer thinks it is flying the entire vehicle and therefore solving the complete thrust allocation problem (i.e., generating thrust values for all motors in the vehicle, 10 in this example). However, it actually sends the thrust value for only a single motor (e.g., the motor corresponding to that flight control device) to the motor.
[0035] Similarly, the second thrust value obtained from the second flight controller (500b) (associated with and / or for the second motor (502b)) is passed to and / or connected to the second motor (502b). The other nine generated thrust values obtained from the second flight controller (500b) are not connected (e.g., the first thrust value and the third thrust value through the tenth thrust value). This pattern repeats for the remaining flight controllers and the remaining motors.
[0036] A requirement or constraint for the system presented here is that the system is contingent on all of the flight control devices arriving at the same solution and / or thrust values. In fact, the thrust values do not need to be exact. The system will function as long as the thrust values generated are all within a small tolerance of each other's thrust values (e.g., motor thrust resolution, within 1N of force, etc.) (e.g., due to slightly differing estimates due to sensor and / or processing noise). In other words, the flight computers perform the same thrust allocation process so that they can produce (nearly) identical thrust values. This property allows the flight computers to operate independently.
[0037] Generally speaking, it has been found that the thrust allocation (i.e., generation of thrust values given input and / or desired forces and moments) performed by the distributed control system shown herein produces better results compared to the control system shown in Figure 4. For example, the distributed control system uses fewer and / or simpler (electronic) components (e.g., there are no decision blocks at all, which tend to be complex).
[0038] It is noted that the techniques and / or systems described herein are applicable to manned flight as well as autonomous flight. In other words, the input forces and moments may be obtained from the pilot via manual or from the autonomous flight controller. As has been described herein, the benefits of this system are particularly evident during motor failure conditions. In some manned applications, the vehicle switches from a manned flight mode (e.g., where the pilot controls the aircraft) to an autonomous flight mode when a motor failure is detected. The autonomous flight manager may then pass the input forces and moments associated with an emergency flight plan to the flight controller to land the vehicle safely as soon as possible.
[0039] As noted above, the techniques and / or systems described herein are particularly beneficial and / or useful in the event of one or more motor failures. The following diagram illustrates an example of a motor failure condition so that some benefits and / or improvements associated with the techniques and / or systems described herein can be described.
[0040] FIG. 6 is a schematic diagram of a top view illustrating an embodiment of an eVTOL multicopter with motor failure. In this example, the representative eVTOL multicopter does not have wings to perform fixed-wing flight (see, e.g., the perspective view shown in FIG. 2) and therefore must rely solely on rotors to stay airborne. The eVTOL multicopter shown herein is also an ultra-lightweight vehicle with strict weight restrictions that may preclude the addition of such wings. For this reason, an improved (control) system that can better land the eVTOL aircraft (e.g., in a more controlled manner, with less impact, etc.) in the event of a motor failure condition without requiring additional and / or heavier parts is more desirable for this ultra-lightweight application and / or for the illustrated vehicle. Of course, the techniques described herein may apply to and be implemented in other vehicles.
[0041] In this example, the vehicle pitches forward when one of the motors (600) fails. For example, the system transitions from the state shown in FIG. 3C to the state shown in FIG. 6. Even with the distributed control system shown in FIG. 5, thrust allocation may be less than optimal with some thrust allocation techniques. The following figure shows an example of how thrust allocation has been performed in the past when the multicopter may crash if some motors fail.
[0042] FIG. 7 is a diagram illustrating an example of a stepwise thrust allocation process. In this example of thrust allocation, thrusts are allocated in steps. Inputs for the process include input and / or desired forces and moments (F z , M x , M y , and M.z For example, in FIG. 6, the forces and moments associated with pitching forward are input into the thrust allocation process.
[0043] At 700, the normal force (F z ), roll moment (M x ), and pitch moment (M y For example, in FIG. 6, there are 10 motors and thrust values are generated for those motors, and the thrust value of 10 is calculated based on the input normal force (F zdes ), roll moment (M xdes ), and pitch moment (M ydes ) is an assigned value greater than or equal to zero to achieve the desired yaw moment (M zdes It is noted that the ) represented by
[0044] At 702, if necessary, the thrust values are uniformly reduced based on the maximum achievable thrust. Another factor not considered during the (initial) thrust allocation at step 700 is the maximum thrust achievable by the motors. Saturation occurs when one or more of the motors are at their maximum achievable thrust. When this occurs, in this example, the thrust values generated at step 700 are uniformly reduced so as not to exceed the maximum achievable thrust. This is sometimes referred to as clipping.
[0045] In the 704, the yaw moment (M z ), any remaining thrust is allocated to achieve the input and / or desired yaw moment (M zdes ), and if there is any remaining thrust (e.g., within the maximum thrust achievable limit), it may be allocated to one or more of the motors to produce the input and / or desired yaw moment (M zdes ) (or at least come close to it).
[0046] While the step-by-step process of FIG. 7 is fast and efficient, it does have some drawbacks. The most serious problem is that losing any (e.g., even one) motor can cause a typical eVTOL multicopter to crash. In the event of a motor failure (see, e.g., FIG. 6), the thrust allocation process described in FIG. 7 relies on the input and / or requested normal force (F zdes In the example in Figure 6, there are a total of 10 motors, 9 of which are operational, so the (original) requested F zdes is scaled up by a factor of 10 / 9. The new desired normal force input to the process of FIG. zdes This approach is suboptimal because the solver continues to allocate thrust as if all 10 motors were available (e.g., at step 700). z ), roll moment (M x ), and pitch moment (M y ) is missing or absent due to the allocation of thrust using the non-functioning motor, the resulting thrust values may not achieve the desired control. In some cases (e.g., if a motor fails), the eVTOL crashes.
[0047] Even if the vehicle does not crash, the flight experience may be uncomfortable and / or suboptimal, especially if saturation occurs. Compensating for saturation in this example (e.g., in step 702 of FIG. 7 ) requires clipping, a crude compensation technique. As a result of clipping, the altitude may be improperly combined (i.e., the clipped thrust values may create vertical forces that are not in line with the desired vertical forces, so the vehicle may undesirably climb or fall). Furthermore, due to clipping in step 702, the roll and / or pitch moments may be improperly combined as well. The clipped thrust values may create roll and / or pitch moments that are not in line with the desired roll and / or pitch moments, so the vehicle may undesirably roll and / or pitch. This often leads to vibrations that increase the danger to passengers and increase the difficulty of maneuvering. In other words, the thrust values generated may not create the desired forces and moments, and / or the flight experience may be uncomfortable and / or dangerous for the occupants.
[0048] In contrast, allocating thrust (e.g., in step 100 of FIG. 1) using an optimization problem that has a single solution (e.g., a strictly convex optimization problem) provides a safer flight experience even if one or more of the motors fail. The following is an example of a convex optimization problem used to allocate thrust (e.g., in step 100 of FIG. 1):
number
[0049] In this example, Equation 1 is a convex optimization problem (in this case, a strictly convex quadratic function), where T is the vector of motor thrusts, F zdesis a vector of desired forces and moments, A is a load cosine matrix that maps motor thrusts to achieved forces and moments, W is a diagonal weighting matrix, and V n is a submatrix of the unitary matrix obtained from the singular value decomposition of A that projects T into the null space of forces and moments, and ε is a small positive number (e.g., to reduce the magnitude of the second term (i.e., ensuring that the function is strictly convex) relative to the first term (i.e., achieving the desired forces and moments). It is noted that while this example optimization problem finds the minimum of a (strictly) convex function, in some embodiments the optimization problem finds the maximum of a (strictly) concave function.
[0050] In terms of inputs and outputs, T (the vector of motor thrusts) is the output that the convex optimization problem is solved to produce, and F zdes The desired force and moment vectors and the motor faults (if any) are the inputs. Any motor fault is resolved by the maximum thrust vector, the array T max For example, if the i-th motor fails, T max The i-th component in becomes zero, which in turn forces the i-th component in T to be zero as well, which does not correspond to any thrust from the i-th motor.
[0051] One of the most important properties of the example convex optimization problem shown in Equation 1 is that the example eVTOL multicopter is no longer vulnerable to certain motor failures. With the example convex optimization problem running on a distributed flight control system (e.g., see FIG. 5), the eVTOL multicopter can stay airborne if one of the motors fails. In some cases, depending on a pair of motors, the eVTOL multicopter can stay airborne even if two motors fail. It is noted that other optimization problems similarly improve the airworthiness of the vehicle in the event of one or more motor failures.
[0052] It is noted that all of the example optimization problems described herein (e.g., Equation 1, Equation 2, etc.) are independent with respect to the number of motors and / or motor placement or configuration of the aircraft. For example, if during development of a next-generation eVTOL multicopter it is decided to change the number, size, and / or placement or arrangement of motors from the current configuration, the same optimization problem and / or thrust allocation process can be reused. This is useful because the flight control system is known, predictable, and thoroughly tested, as opposed to a new system that would have to be developed if the flight control system was not scalable and / or applicable.
[0053] For convenience and ease of explanation, Equation 1 has some relevant properties and / or characteristics (e.g., strictly convex, quadratic, etc.). This convex optimization problem is merely representative, and other convex optimization problems may have other combinations or properties and / or characteristics (e.g., strictly convex but not quadratic). It may be useful to review a brief derivation illustrating the benefits associated with various inputs, parameters, and the like contained in Equation 1. The following shows an example of a simpler convex optimization problem:
number
[0054] In the example of Equation 2, the motor thrust is non-negative (i.e., subject to the constraint 0≦T) and at most T max (i.e., the constraint T ≤ T max ) using a least-squares objective to find the desired forces and moments (i.e., F zdes ) and the realized forces and moments (i.e., AT).
[0055] 0≦T≦T max The constraints, and the limit of T maxSetting the corresponding elements in T to zero means that the thrust values generated using the representative convex optimization problems described herein (e.g., Eq. 1, Eq. 2, etc.) are always feasible. That is, the flight controller can provide a feasible (e.g., non-negative, T max 6 always produces a set of motor thrusts that never exceed . Moreover, the example optimization problem described herein is always feasible no matter what, so there are no very rare tricky cases to deal with separately (described in more detail below). Conceptually, this avoids the saturation problem in the first place, whereas the step-by-step process of FIG. 6 allows for a set of motor thrust values to be generated that is not feasible (i.e., saturation) and then has to solve the problem after the fact (e.g., by clipping, which is a crude and / or immature solution).
[0056] Any (all) motor failure will result in the maximum thrust vector (T max Another benefit of incorporating motor failure information into the design is that it allows for better and / or more explicit ways of incorporating motor failure information. For example, some other techniques may attempt to incorporate motor failure information into the design variables or may reformulate the problem in other ways (e.g., switching to a different optimization problem in the case of a motor failure), both of which may make thrust allocation more complicated and / or slower to produce an acceptable set of thrust values. max Since the vector needs to be there to reflect the thrust limits of the motor, the existing elements in the optimization function serve multiple purposes.
[0057] The following diagram describes this example more formally.
[0058] 8 is a flow diagram illustrating an embodiment of a process for generating thrust values, including by using a maximum thrust vector. FIG 8 is related to FIG 1, and for convenience, the same or similar reference numbers are used to indicate the same or related steps.
[0059] In 800, thrust values for a plurality of motors in an aircraft are generated using a plurality of flight control devices, and each flight control device in the plurality of flight control devices generates a thrust value for each motor in the plurality of motors using an optimization problem having a single solution, and generating the thrust values includes: max ) so that any motor failure is reflected in the maximum thrust vector. In some embodiments of step 800, constraining the achievable thrust values constrains the thrust values to be greater than or equal to zero (e.g., T≦T max In addition, the method further includes the step of 0≦T.
[0060] As described above, constraining the thrust values to be feasible forces the optimizer to reason directly about saturation conditions, producing better and faster results. Also, using the maximum thrust vector to account for motor failures allows for simpler designs (e.g., not requiring any additional parameters, inputs, etc.). In some embodiments, when a motor failure is detected or otherwise flagged, T max Corresponding values in (e.g., values corresponding to a detected motor failure) are immediately set to zero. For example, there may be a number of reasons for a motor failure. In some cases, there is a loss of communication with the motor, meaning that it is not known how long ago the motor stopped functioning. Also, even if a non-zero value (e.g., corresponding to a detected motor failure) is gradually decreased or otherwise set to zero, because the rotational frequency of the motor is relatively fast, deceleration will occur relatively quickly as well, resulting in little benefit.
[0061] At 102, for each flight control device in the plurality of flight control devices, one of the generated thrust values is passed to a corresponding motor in the plurality of motors, and the other thrust value generated for that flight control device is terminated at that flight control device.
[0062] At 104, the delivered thrust values are implemented using a number of motors.
[0063] Returning briefly to Equation 2, in some embodiments, an active setting technique, method, or process is used to solve a convex optimization problem (e.g., Equation 1, Equation 2, etc.). Active setting techniques are used to set feasible time points (e.g., 0≦T≦T max , which must be true and therefore feasible) and a set of constraints (e.g., a given thrust value must be true when a given motor is in motion, i.e., T max When a given motor fails or the thrust value is zero and T max T when the corresponding element in max If any of the thrust values are at the zero-set saturation value in T max In other words, whether the thrust values are constrained by an upper or lower bound. The thrust values are iteratively updated in a finite number of steps to obtain the optimal solution by tracking which constraints are active (i.e., actively constraining a given thrust value) in order to solve the problem more efficiently. For example, if motor 3 was saturated in the previous step (e.g., the motor thrust values for motor 3 are in the vector T max If it is known that motor 3 is saturated at the representative third value in the previous iteration (i.e., the thrust was maxed out at the third value in the previous iteration), then motor 3 will likely be saturated at the next iteration as well. The next iteration solves the problem without changing its thrust (e.g., the constrained thrust), but then verifies that the resulting solution is indeed still optimal for the representative saturated third motor. This reduces the number of thrust values that need to be considered, evaluated, and / or adjusted at the next iteration, reducing the number of things the process has to consider, leading to a much faster average time to find a solution.
[0064] The following diagram describes this example more formally.
[0065] 9 is a flow diagram illustrating an embodiment of a process for generating thrust values, including by tracking whether any of the thrust values are actively constrained. FIG 9 is related to FIG 1, and for convenience, the same or similar reference numbers are used to indicate the same or related steps.
[0066] At 900, thrust values are generated for a plurality of motors in an aircraft using a plurality of flight control devices, each flight control device in the plurality of flight control devices generating a thrust value for each motor in the plurality of motors using an optimization problem having a single solution, generating the thrust values includes by tracking whether any of the thrust values are actively constrained using an active set of constraints, and any motor failures are reflected in a maximum thrust vector.
[0067] As described above, this means that (e.g., T max The actively constrained thrust value (of the corresponding maximum element of the internal thrust value, or zero) is initially assumed to be actively constrained in the next iteration, thus simplifying the thrust allocation process since the thrust value will (again) be the maximum value, simplifying the process.
[0068] In some embodiments, a warm start is used in combination with the active set constraint technique (not shown in FIG. 9). For example, assume that a first set of thrust values is generated or otherwise passed to the motors to obtain the i-th set of desired forces and moments at a first time t (alternatively, index i in discrete time applications). In the case of a warm start, the first set of desired forces and moments is used as an initial variable set of thrust values from which the active set processing begins when generating a second set of thrust values to obtain a second set of desired forces and moments associated with the corresponding thrusts at a second (next) time or index. This may help the active set processing to more quickly find a set of thrust values to output, reducing processing time.
[0069] As described above, in some embodiments, step 900 further includes the constraint that the first set of thrust values generated to obtain a first set of desired forces and moments are used as an initial set of thrust values when generating thrust values for a subsequent second set of desired forces and moments (not shown in FIG. 9 ).
[0070] At 102, for each flight control device in the plurality of flight control devices, one of the generated thrust values is passed to a corresponding motor in the plurality of motors, and the other thrust values generated for that flight control device are terminated at that flight control device.
[0071] At 104, the delivered thrust values are executed using a number of motors.
[0072] Returning to Equation 2 for a moment, a drawback of Equation 2 is that it does not allow for prioritizing and / or weighting control along various axes. For example, in the case of the open cockpit of an eVTOL multicopter shown in Figure 2, it is critical that the vehicle does not flip upside down, as any occupants would be severely injured or killed. Thus, the desired roll moment M xdes ) and roll control (e.g., associated with the desired pitch moment M ydes ) is controlled by the pitch control (e.g., the yaw moment M zdes ) and yaw control (e.g., associated with normal force F zdes (associated with altitude control). In other words, to prevent the vehicle from flipping over, it may be more important not to flip over even if the vehicle descends (e.g., slowly) and rolls like in a spiral landing. Equation 2 does not allow for this, nor does it have this capability. The following example equation introduces such weighting and / or prioritization into the optimization function of Equation 2:
number
[0073] In Equation 3, W is a diagonal weighting matrix (more commonly referred to as axis weighting parameters). With such axis weighting parameters, control over one or more of the more important axes (e.g., roll and pitch in the above example) can be prioritized over one or more of the less important axes (e.g., yaw). As described above, control over the roll and pitch axes is important to prevent a typical open-cockpit eVTOL multicopter from flipping over, even at the expense of some yaw control. In other words, it may be acceptable for the vehicle to rotate (e.g., slowly) about the yaw (vertical) axis while performing an emergency landing to prevent the eVTOL multicopter from flipping over. Moreover, the axis weighting parameters (e.g., W) are parameterizable (e.g., W is adjustable as opposed to being strictly binary on / off) and continuous (e.g., this is beneficial since there is no risk of W being discontinuous, which would prevent the system from finding a solution for the thrust values and / or would delay the search for a solution due to discontinuities). In one example,
number
[0074] The following diagram describes this example more formally.
[0075] Figure 10 is a flow diagram illustrating an embodiment of a process for generating thrust values, including by using axis weighting parameters. Figure 10 is related to Figure 1, and for convenience, the same or similar reference numbers are used to indicate the same or related steps.
[0076] At 1000, thrust values are generated for multiple motors in an aircraft using multiple flight control devices, and each flight control device in the multiple flight control devices generates thrust values for each motor in the multiple motors using an optimization problem having a single solution, the optimization problem including axis weighting parameters set to values associated with prioritizing roll and pitch control over yaw control (and in some embodiments altitude control as well).
[0077] At 102, for each flight control device in the plurality of flight control devices, one of the generated thrust values is passed to a corresponding motor in the plurality of motors, and the other thrust value generated for that flight control device is terminated at that flight control device.
[0078] At 104, the delivered thrust values are executed using a number of motors.
[0079] Returning for a moment to Equation 3, it leaves open the possibility of multiple solutions. This is undesirable when used in the distributed control system described herein, since all of the flight controllers (see, e.g., FIG. 5) need to generate the same set of thrust values for the motors. The following shows an example optimization function with a regularization term to ensure that only one solution exists (in other words, the function is strictly convex):
number
[0080] Section 2
number
number
[0081] Returning for a moment to Equation 1, the second term
number
number
[0082] The following diagram describes this example more formally.
[0083] 11 is a flow diagram illustrating an embodiment of a process for generating thrust values where the optimization problem has multiple parts or terms associated with different objectives. FIG 11 is related to FIG 1, and for convenience, the same or similar reference numbers are used to indicate the same or related steps.
[0084] In 1100, thrust values are generated for a plurality of motors in an aircraft using a plurality of flight control devices, each flight control device in the plurality of flight control devices generates thrust values for each motor in the plurality of motors using an optimization problem having a single solution, a portion of the optimization problem is associated with ensuring that a single solution to the optimization problem exists, the portion of the convex optimization problem associated with ensuring that a single solution exists includes a matrix associated with projecting the thrust values onto a null space associated with one or more desired forces and / or moments, such that generating the thrust values is independent of the portion of the convex optimization problem associated with ensuring that a single solution exists. See, e.g., the second term in Equation 1.
[0085] For example, in Equation 1,
number
number
number
[0086] At 102, for each flight control device in the plurality of flight control devices, one of the generated thrust values is passed to a corresponding motor in the plurality of motors, and the other thrust value generated for that flight control device is terminated at that flight control device.
[0087] At 104, the passed thrust values are implemented using multiple motors.
[0088] Although the above embodiments have been described in some detail for clarity of understanding, the present invention is not limited to the details provided. There are many alternative ways to implement the present invention. The disclosed embodiments are illustrative and not restrictive.
Claims
1. 1. An aircraft, A plurality of flight control devices, generating thrust values for a plurality of motors in the aircraft, each of the flight control devices in the plurality of flight control devices generating the thrust values for each of the motors in the plurality of motors using an optimization problem having a single solution; a plurality of flight control devices configured to pass, for each flight control device among the plurality of flight control devices, one of the generated thrust values to a corresponding motor among the plurality of motors, the other thrust values generated for that flight control device being terminated at that flight control device; The plurality of motors are configured to achieve the delivered thrust value.
2. 2. The aircraft of claim 1, wherein generating the thrust values includes constraining the thrust values to be achievable using a maximum thrust vector, wherein any motor failure is reflected in the maximum thrust vector.
3. 2. An aircraft as claimed in claim 1, generating the thrust values includes constraining the thrust values to be achievable using a maximum thrust vector, such that any motor failure is reflected in the maximum thrust vector; The aircraft, wherein constraining the thrust value to be feasible further comprises constraining the thrust value to be greater than or equal to zero.
4. 2. The aircraft of claim 1, wherein generating the thrust values includes using an active set technique including by tracking whether any of the thrust values are actively constrained by a corresponding maximum thrust value in the maximum thrust vector, wherein any of the motor failures are reflected in the maximum thrust vector.
5. 2. The aircraft of claim 1, including using an active set technique, wherein generating the thrust values includes by tracking whether any of the thrust values are actively constrained by a corresponding maximum thrust value in the maximum thrust vector; Any said motor failure is reflected in said maximum thrust vector; The first set of thrust values generated to obtain a first set of desired forces and moments is used as an initial set of thrust values when generating thrust values to obtain a second set of desired forces and moments in the aircraft.
6. 2. An aircraft as claimed in claim 1, a portion of the optimization problem is associated with ensuring that a single solution to the optimization problem exists; the portion of the optimization problem associated with ensuring that a single solution exists includes a matrix associated with projecting the thrust values onto a null space associated with one or more desired forces and / or moments, such that generating the thrust values is independent of the portion of the optimization problem associated with ensuring that a single solution exists for the aircraft.
7. 1. A method comprising: generating thrust values for a plurality of motors in the aircraft, each of the flight control devices among the plurality of flight control devices generating the thrust values for each of the motors among the plurality of motors using an optimization problem having a single solution; for each of the flight control units in the plurality of flight control units, passing one of the generated thrust values to a corresponding motor in the plurality of motors, and other of the thrust values generated for that flight control unit being terminated at that flight control unit; Achieving the transmitted thrust value using the plurality of motors. A method for providing the above.
8. 8. The method of claim 7, wherein generating the thrust values includes constraining the thrust values to be achievable using a maximum thrust vector, and all motor failures are reflected in the maximum thrust vector.
9. 8. The method of claim 7, generating the thrust values includes constraining the thrust values to be achievable using the maximum thrust vector, such that all motor faults are reflected in the maximum thrust vector; The method, wherein constraining the thrust value to be feasible includes constraining the thrust value to be greater than or equal to zero.
10. 8. The method of claim 7, wherein generating the thrust values includes using an active set technique that includes tracking whether any of the thrust values are actively constrained by a corresponding maximum thrust value in the maximum thrust vector, and wherein any of the motor faults are reflected in the maximum thrust vector.
11. 8. The method of claim 7, wherein generating the thrust values includes using an active set technique that includes tracking whether any of the thrust values are actively constrained by a corresponding maximum thrust value in the maximum thrust vector; Any said motor failure is reflected in said maximum thrust vector; A method in which a first set of thrust values generated to obtain a first set of desired forces and moments is used as an initial set of thrust values when generating thrust values to obtain a subsequent second set of desired forces and moments.
12. 8. The method of claim 7, a portion of the optimization problem is associated with ensuring that a single solution to the optimization problem exists; The method wherein the portion of the optimization problem associated with ensuring that the single solution exists includes a matrix associated with projecting the thrust values onto a null space associated with one or more desired forces and / or moments, such that generating the thrust values is independent of the portion of the optimization problem associated with ensuring that the single solution exists.
13. A computer program product embodied in a non-transitory computer-readable storage medium, comprising: computer instructions for generating thrust values for a plurality of motors in an aircraft, each of the plurality of flight control devices generating the thrust values for each of the motors of the plurality of motors using an optimization problem having a single solution; computer instructions for passing, for each flight control device in the plurality of flight control devices, one of the generated thrust values to a corresponding motor in the plurality of motors, and another of the generated thrust values for that flight control device terminates in that flight control device; A computer instruction for implementing the thrust value using the plurality of motors.
1. A computer program product comprising:
14. 14. The computer program product of claim 13, wherein the computer instructions for generating the thrust values include computer instructions for constraining the thrust values to be achievable using a maximum thrust vector, and wherein any motor failure is reflected in the maximum thrust vector.
15. 14. A computer program product according to claim 13, comprising: the computer instructions for generating the thrust values include computer instructions for constraining the thrust values to be achievable using a maximum thrust vector, any motor failure being reflected in the maximum thrust vector; The computer program product, wherein the computer instructions for constraining the thrust value to be feasible further comprise computer instructions for constraining the thrust value to be greater than or equal to zero.
16. 14. The computer program product of claim 13, wherein the computer instructions for generating the thrust values include by tracking whether any of the thrust values are actively constrained by a corresponding maximum thrust value in the maximum thrust vector, and wherein any of the motor faults are reflected in the maximum thrust vector.
17. 14. The computer program product of claim 13, wherein the computer instructions for generating the thrust values include by tracking whether any of the thrust values are actively constrained by a corresponding maximum thrust value in the maximum thrust vector; Any said motor failure is reflected in said maximum thrust vector; A computer program product in which a first set of thrust values generated to obtain a first set of desired forces and moments is used as an initial set of thrust values when generating thrust values for a subsequent second set of desired forces and moments.
18. 14. A computer program product according to claim 13, comprising: a portion of the optimization problem is associated with ensuring that a single solution to the optimization problem exists; The computer program product, wherein the portion of the optimization problem associated with ensuring that the single solution exists includes a matrix associated with projecting the thrust values onto a null space associated with one or more desired forces and / or moments, such that generating the thrust values is independent of the portion of the optimization problem associated with ensuring that the single solution exists.
Citation Information
Patent Citations
Control rule deciding method for automatic controller
JP2002258905A
Control method for vertical takeoff and landing air vehicle
JP2014227155A
Distributed Flight Control System
JP2020503209A
Online optimization-based flight control system
US20190202546A1
Linear programming problem solving system, solution candidate calculation device, optimal solution calculation device, thruster control device for spacecraft, flying object control device, and linear programming problem solving method
WO2019224954A1
