This invention relates generally to the battery technology field, and more specifically to a new and useful battery thermal management system and method in the battery technology field.
Electric vehicles use battery power to enable vehicle functions, such as propulsion and support systems. Modern battery technology requires careful thermal management during discharge to prevent undesired thermal events from disrupting optimal power delivery and, in some cases, damaging the battery and/or the vehicle itself. Inadequate thermal management of the battery can endanger the vehicle, its occupants, bystanders, and/or the surrounding environment. In addition, it is often desirable to charge the battery in a fast and efficient manner, which must be balanced against the heat generated within the battery by such charging processes. These challenges are compounded in contexts where the electric vehicle system design is subject to stringent constraints on weight, complexity, and/or safety, such as aviation.
Thus, there is a need in the battery technology field to create a new and useful battery thermal management system and method. This invention provides such new and useful systems and methods.
The following description of preferred embodiments of the invention is not intended to limit the invention to these preferred embodiments, but rather to enable any person skilled in the art to make and use this invention.
1. Overview
The battery thermal management system 100 includes a battery pack 110, a circulation subsystem 120, and a heat exchange system 130. The circulation subsystem includes: a pump 122 and a fluid manifold 124, and can optionally include a hose coupling 126 and a lockout mechanism 128. The system 100 can optionally include a cooling system 190, a reservoir 150, a de-ionization filter 160, a battery charger 170, and a controller 180. The system 100 can additionally or alternatively include any other suitable components. An example of the system 100 is shown in
The system 100 functions to manage the thermal state of the battery pack. The thermal state can include the distribution of the temperature within the battery pack, the average temperature of the battery pack, the temperature rise or fall rate of the battery pack, and/or any other suitable metric quantifying the a temperature-related characteristic of all or part of the battery pack and/or thermally coupled elements.
The system 100 can also function to circulate a working fluid within the battery pack (e.g., to achieve temperature uniformity within the battery pack, to heat or cool the battery pack, etc.). The working fluid can be any suitable fluid that can be heated and/or cooled, and flowed through a closed or open circuit of the circulation subsystem to transfer heat among the various components (including, e.g., the external environment). The working fluid can additionally or alternatively be any suitable fluid medium for exchanging heat between portions of the battery pack and/or a heat exchanger of the system 100. For example, the working fluid can be water, a water/glycol mixture (e.g., 50/50, 70/30, 80/20, etc.), a refrigerant (e.g., R134a), an oil, air, fluid coolant, mineral oil, any other suitable gas or gas mixture, and/or any other suitable fluid. In variants, the working fluid can be a non-hazardous, natural, or bio-degradable fluid in order to minimize the environmental impact of leaks or spills. In variants, the working fluid can be non-conductive (e.g., mineral oil), which can eliminate the possibility of shorting electronics and/or enable flood cooling of the battery cells 114 (e.g., in a fully submersed configuration). In some examples, the system 100 can be configured to circulate multiple working fluids for various purposes (e.g., a first working fluid for cooling the battery pack circulated in parallel with a second working fluid for heating the battery pack, wherein the first and second working fluids can be circulated at differing times depending on the needs of the thermal management system, etc.).
The system 100 can also function to detect and manage a thermal event within the battery pack. A thermal event can include any off-nominal temperature reached by a portion of the battery pack. For example, a thermal event can include a thermal runaway in one or more cells 114 of a battery pack, wherein an uncontrolled, positive feedback exothermic reaction occurs within the cell or cells. A thermal event can also include thermal propagation, wherein an off-nominal (e.g., spiked, increasing, etc.) temperature spreads from one to multiple cells not initially affected. However, a thermal event can additionally or alternatively include any other temperature-related occurrence within the battery pack that requires mitigation to ensure proper battery pack operation (e.g., charging, discharging, storage, etc.).
The battery thermal management system can be used in conjunction with and/or include several related systems, in various embodiments. Such related systems can include an aircraft, aircraft subsystems (e.g., powertrain subsystems, propulsion subsystems, avionics subsystems, etc.), a ground-based vehicle (e.g., an automotive, a locomotive, etc.), land-based infrastructure (e.g., air traffic control systems, ground-based maintenance systems, etc.), and/or any other suitable systems.
In variations of the system 100, components of the battery thermal management system are distributed between a vehicle and an infrastructure installation (examples shown in
This distribution functions to enable thermal conditioning of the battery pack located on board the vehicle without requiring the vehicle to transport the components used for thermal conditioning during operation (e.g., flight, driving, traversing water, etc.). This allows the heat exchanger to be left behind during vehicle operation (e.g., enabling more efficient vehicle operation due to the reduced part count and weight). This distribution also enables a larger or more complex heat exchangers to be used to enable rapid charging of the battery pack on board the vehicle. The infrastructure installation can be static (e.g., fixed to the ground as part of substantially permanent infrastructure) or mobile (e.g., a movable/towable trailer that can be transported to a service area to be connected to the vehicle during charging or other thermal conditioning).
As shown in
The method 200 functions to manage the thermal state of the battery pack associated with the vehicle. The method 200 can also function to implement the functionality of any component or components of a system analogous to the system 100, as described herein or otherwise suitably defined.
The method 200 is preferably implemented and/or executed using a system substantially analogous to the system 100; however, the method 200 can be implemented and/or executed by any other suitable system with any other suitable components that can be used for battery pack thermal management.
The battery thermal management system 100 and/or method 200 is preferably implemented in conjunction with an aircraft (e.g., the system can include an aircraft); in variations wherein the battery thermal management system is distributed between a vehicle and an infrastructure installation, the vehicle is preferably an aircraft. In particular, the aircraft is preferably a rotorcraft, but can additionally or alternatively include any suitable aircraft. The rotorcraft is preferably a tiltrotor aircraft with a plurality of aircraft propulsion systems (e.g., rotor assemblies, rotor systems, etc.), operable between a forward arrangement 105 (an example is shown in
The aircraft can have any suitable mass (e.g., unloaded mass, loaded mass, maximum takeoff mass, etc.) with any appropriate mass distribution (or weight distribution). The aircraft mass can be: 1 kg, 5 kg, 10 kg, 50 kg, 100 kg, 500 kg, 1000 kg, 1250 kg, 1500 kg, 1750 kg, 2000 kg, 2250 kg, 2500 kg, 2750 kg, 3000 kg, 5000 kg, 1000 kg, 20000 kg, less than 1500 kg, 1500-2000 kg, 2000-3000 kg, 3000-5000 kg, 5000-10000 kg, greater than 10000 kg, any suitable range bounded by the aforementioned values, and/or any other appropriate mass. The aircraft is preferably a passenger carrier, configured to transport 1, 2, 3, 4, 5, 6, 7, 10, greater than 10, and/or any suitable number of passengers, however the aircraft can alternately be an unmanned aircraft, a teleoperated passenger aircraft, and/or any other suitable aircraft.
In a specific example, portions of the battery thermal management are integrated into the electric tiltrotor aircraft described in U.S. application Ser. No. 16/409,653, filed 10 May 2019, which is incorporated in its entirety by this reference. However, any other suitable aircraft can be used.
Onboard portions of the battery thermal management system are preferably located in, mounted on, and transported with a vehicle 101. Onboard portions of the battery thermal management system are preferably integrated into an aircraft (e.g., the system can include an aircraft), but can additionally or alternatively be used with any other suitable vehicle (e.g., scooter, automobile, etc.).
In a specific example of the battery thermal management system, portions of the system are integrated into an electric tiltrotor aircraft including a plurality of tiltable rotor assemblies (e.g., six tiltable rotor assemblies). The electric tiltrotor aircraft can operate as a fixed wing aircraft, a rotary-wing aircraft, and in any liminal configuration between a fixed and rotary wing state (e.g., wherein one or more of the plurality of tiltable rotor assemblies is oriented in a partially rotated state). The control system of the electric tiltrotor aircraft in this example can function to command and control the plurality of tiltable rotor assemblies within and/or between the fixed wing arrangement and the rotary-wing arrangement.
The term “compressor” as utilized herein in relation to refrigeration systems, refrigeration cycles, sub-ambient cooling, or otherwise, is a mechanical device that increases the pressure of a gas (e.g., gas, vapor, liquid-vapor mixture, etc.) by reducing its volume. Compressors can be: positive displacement compressors, rotary compressors (e.g., lobe, screw, liquid ring, scroll, vane, etc.), reciprocating compressors (e.g., diaphragm, double acting, single acting, etc.), dynamic compressors (e.g., centrifugal, axial, mixed-flow, diagonal, air bubble, etc.), and/or any other suitable type of compressor. In examples, compressors can pressurize, compress, and/or transport compressible fluids, while pumps can pressurize and/or transport compressible and/or incompressible fluids (e.g., water, water/glycol mixture, oil, etc.).
The term “active cooling” as utilized herein, in relation to portions of the system 100, method 200, or otherwise, can refer to the application of electrical or mechanical energy, supplied from a battery pack or other power source, to remove heat from a thermal endpoint (e.g., as opposed to passive cooling that uses little or no energy). In particular, active cooling can refer to the use of forced convection heat transfer (e.g., as opposed to natural/free convection and/or radiation) between a system and/or component and a working fluid. Active cooling can include forced air through a fan or blower, forced liquid, and thermoelectric coolers (TECs), and/or other active cooling mechanisms.
The term “rotor” as utilized herein, in relation to portions of the system 100, method 200, or otherwise, can refer to a rotor, a propeller, and/or any other suitable rotary aerodynamic actuator. While a rotor can refer to a rotary aerodynamic actuator that makes use of an articulated or semi-rigid hub (e.g., wherein the connection of the blades to the hub can be articulated, flexible, rigid, and/or otherwise connected), and a propeller can refer to a rotary aerodynamic actuator that makes use of a rigid hub (e.g., wherein the connection of the blades to the hub can be articulated, flexible, rigid, and/or otherwise connected), no such distinction is explicit or implied when used herein, and the usage of “rotor” can refer to either configuration, and any other suitable configuration of articulated or rigid blades, and/or any other suitable configuration of blade connections to a central member or hub. Likewise, the usage of “propeller” can refer to either configuration, and any other suitable configuration of articulated or rigid blades, and/or any other suitable configuration of blade connections to a central member or hub. Accordingly, the tiltrotor aircraft can be referred to as a tilt-propeller aircraft, a tilt-prop aircraft, and/or otherwise suitably referred to or described.
The term “substantially” as utilized herein can mean: exactly, approximately, within a predetermined threshold (e.g., within 1%, within 5%, within 10%, etc.), predetermined tolerance, and/or have any other suitable meaning.
2. Benefits
Variations of the technology can afford several benefits and/or advantages.
First, variations of the technology can reduce the vehicle mass by arranging substantial portions of the thermal conditioning system at an extra-vehicular infrastructure installation 102. For an equivalent vehicle mass, this can also enable a higher overall energy capacity, and therefore increased range and/or power output (e.g., by replacing the portions of the thermal conditioning system that would otherwise be carried with the vehicle with additional battery pack mass). This can also enable more powerful heat exchangers to be used, since the heat exchanger weight is no longer limited by the vehicle's transportation capabilities. For example, a heat exchanger that can exchange a correspondingly greater amount of heat with the external environment than a vehicle-borne heat exchanger can be used to enable rapid (e.g., higher heat-generating) charging, and then left behind by the vehicle during operation (e.g., at the infrastructure installation). Reducing the size of onboard refrigeration components and/or eliminating refrigeration components from the vehicle can enable tighter packaging and/or volumetric constraints of the battery thermal management system, which can avoid thermal management components from infringing on cabin space. Additionally, eliminating onboard fans and/or compressors eliminates the acoustic impact of such devices, thereby reducing cabin noise, the reducing the total (external) acoustic profile of the vehicle, and/or improving passenger comfort. In variants, onboard refrigeration component removal can be enabled by rejecting the excess heat, generated by the battery cells (of the battery pack) during flight, into the battery pack thermal mass (e.g., other battery cells, the pack housing, pack electronics, etc.) to maintain the battery cell temperatures below the cell separation and/or degradation temperature.
Second, variations of the technology can leverage the vehicle environment and operation characteristics to condition the battery pack during operation without the need for active heating or sub-ambient cooling. For example, heat generated as the battery pack discharges during vehicle operation can be distributed within the battery pack (e.g., via active circulation to equalize the temperature across the thermal mass of the battery pack, via passive conduction among cells in the battery pack, etc.) to raise the battery pack temperature to a desired temperature set point (e.g., operation set point; via waste heat utilization to achieve uniformity within the battery pack). In another example, airflow around the vehicle can be used to convect heat away from the battery pack (e.g., via direct airflow adjacent to the battery pack, via airflow through a radiative cooler coupled to the onboard portion of the circulation subsystem or the battery pack itself, etc.) to lower the battery pack temperature to a desired temperature set point.
Third, variations of the technology can intelligently manage the thermal state of the battery pack during vehicle operation in accordance with dynamic mission objectives. For example, the technology can automatically respond to a change in mission objective from “proceed to destination” (e.g., nominal operation) to “emergency landing” by ceasing active circulation of the working fluid through the circulation subsystem to reserve battery pack energy for propulsion and control operations. In another example, the technology can automatically respond to a change in the flight profile (e.g., distance remaining until destination, time remaining until destination, electrical discharge or power requirements of the remaining flight profile, etc.) by adjusting the flow rate of the circulating working fluid to redistribute the heat within the battery pack among the thermal mass of the pack in accordance with a new desired temperature distribution (e.g., determined dynamically based on the new flight profile).
Fourth, variations of the technology can enhance the safety characteristics of the vehicle by preventing, predicting, detecting, and/or mitigating thermal events in the battery pack of the vehicle. Active circulation of working fluid through can redistribute heat within the battery pack to minimize temperature variation among battery cells within the same or a different battery pack (an example is shown in
Fifth, variations of the technology can leverage the defined duration and other characteristics of trips in certain vehicle types (e.g., aircraft) to predict energy expenditures (e.g., and associated heat generation) with high accuracy, and correspondingly improve battery thermal management. For example, an aircraft with a defined and known onboard energy capacity (e.g., stored in one or more battery packs) has an operational envelope associated with its performance characteristics (e.g., aerodynamic behaviors, speed, propulsion power, drag, mass, etc.) that does not dynamically change for a given trip (e.g., flight), because the performance characteristics can be precisely known and the external factors are known to higher certainty than in other contexts (e.g., the weather parameters can be precisely measured, but the route and/or destination does not dynamically change such as in automobile contexts). Thus, such variations can factor in a correspondingly greater number of precisely known a priori data to the predicted temperature profile of the battery pack during the trip, and condition the battery pack accordingly before the trip commences (e.g., without needing to travel with a dynamic battery conditioning system in the event that the trip parameters change substantially). In a specific example, a battery takeoff temperature setpoint is determined based on an estimated battery pack heat generation during the trip (e.g., flight) and the thermal mass of the battery pack and/or circulation subsystem, thereby ensuring that the battery pack does not exceed thermal and/or performance limitations during the trip.
However, variations of the system can additionally or alternatively provide any other suitable benefits and/or advantages.
3. System
The battery thermal management system 100 includes a battery pack 110, a circulation subsystem 120, and a heat exchange system 130. The circulation subsystem includes: a pump 122 and a fluid manifold 124, and can optionally include a hose coupling 126 and a lockout mechanism 128. The system 100 can optionally include a cooling system 190, a reservoir 150, a de-ionization filter 160, a battery charger 170, and a controller 180. The system 100 can additionally or alternatively include any other suitable components. An example of the system 100 is shown in
The battery pack functions to store energy for powering vehicle operations during use. The battery pack can also function to release the stored energy (e.g., in the course of powering vehicle operations). The energy stored by the battery pack is preferably stored in the form of chemical potential energy and released in the form of electrical energy; however, the energy can additionally or alternatively be stored and/or released in any suitable form. Operation of the battery pack can include charging of the battery pack, discharging of the battery pack, and/or maintenance of the charge of the battery pack (e.g., storage of energy); however, operation of the battery pack can include any other suitable use of the battery pack.
The battery pack is integrated with the vehicle 101, and can be arranged within, upon, or otherwise suitably coupled to the vehicle. Thus, the battery pack moves (e.g., is transported) with the vehicle as the vehicle moves. The system can include any suitable number of battery packs. The system can include: one battery pack per propulsion system, one battery pack associated with a plurality of propulsion systems, one propulsion system associated with a plurality of battery packs, a plurality of battery packs onboard the vehicle (e.g., 2, 3, 4, more than 4, etc.), a single battery pack for the vehicle, and/or any other suitable number of battery packs associated with any number of aircraft components. The battery packs can have any suitable arrangement, and can be located in the fuselage, empennage, wing, cabin (e.g., below a passenger region), tail, a nacelle, and/or any other suitable region. Preferably, the batteries are symmetrically distributed about the center of the aircraft, but can additionally or alternately be offset by a predetermined distance from a passenger region, (e.g., by 1 meter, 2 meters, >2 meters, etc.), another battery, a rotor disk, a rotor disk plane, and/or any other suitable vehicle component, and/or otherwise distributed about the vehicle. For example, the system can include one battery pack for each propulsion unit (or other suitable load) that powers an associated electric motor. In another example, the system can include a single battery pack connected to each propulsion unit (e.g., an automotive vehicle with a single battery pack and a single integrated powertrain including multiple motors). In further examples, the system can include a number of battery packs greater than the number of propulsion units; a number of battery packs less than the number of propulsion units; and/or any suitable number of battery packs. The battery packs can be interconnected in any suitable manner with the powered components of the vehicle (e.g., wherein a plurality of battery packs is connected to each powered component for redundancy in a fault-tolerant power network).
The battery pack can include a plurality of cells in any suitable arrangement (e.g., parallel, serial, etc.) that cooperatively make up the battery pack.
The battery pack and the cells thereof can use various battery chemistries to store electrochemical energy in a rechargeable manner. For example, the battery pack be an aluminum ion battery, a carbon battery (e.g., a single carbon battery, a dual carbon battery, etc.), a flow battery (e.g., a vanadium redox battery, a zinc-bromine battery, a zinc-cerium battery, etc.), a lead-acid battery (e.g., a deep cycle battery, a VRLA battery, an AGM battery, a gel battery, etc.), a glass battery, a lithium-ion battery (e.g., a lithium ion lithium cobalt oxide battery, a lithium ion manganese oxide battery, a lithium ion polymer battery, a lithium iron phosphate battery, a lithium-sulfur battery, a lithium-titanate battery, a thin film lithium ion battery, a lithium ceramic battery, etc.), a magnesium ion battery, a metal-air electrochemical battery (e.g., a lithium-air battery, an aluminum-air battery, a germanium-air battery, a calcium-air battery, an iron-air battery, a potassium-ion battery, a silicon-air battery, a zinc-air battery, a tin-air battery, a sodium-air battery, a beryllium-air battery, etc.), a molten salt battery, a nickel-cadmium battery (e.g., a vented cell nickel-cadmium battery), a nickel hydrogen. battery, a nickel-iron battery, a nickel metal hydride (NiMH) battery, a nickel-zinc battery, an organic radical battery, a polymer-based battery, a polysulfide bromide battery, a potassium-ion battery, a rechargeable alkaline battery, a rechargeable fuel battery, a sand battery, a silicon air battery, a silver-zinc battery, a silver calcium battery, a sodium-ion battery, a sodium-sulfur battery, a solid-state battery, a ferrate salt cathode battery (e.g., a super-iron battery), a zinc-ion battery, and/or any other suitable battery utilizing any other suitable chemistry for the storage and release of electrical energy. Additionally or alternatively, the battery pack can include capacitive energy storage units such as capacitors, supercapacitors, and/or any other suitable means for storing electrical energy and releasing the electrical energy in a controllable manner.
The battery pack can include any suitable energy storage capacity which can be <10 kWh, 10 kWh, 25 kWh, 35 kWh, 50 kWh, 80 kWh, 100 kWh, 150 kWh, >150 kWh, any suitable range defined by the aforementioned values, and/or any other suitable storage capacity. Preferably, the charge rate of the battery pack (and/or individual cells within the battery pack) is limited to 2 C, but can alternately be <1 C, 1 C, 1.5 C, 2.5 C, 3 C, 5 C, >5 C, and/or any other suitable charge rate.
The battery cells can have any suitable electrical and/or power characteristics. The battery cells can operate at any suitable voltage (e.g., 2.4V, 4.2V, nominal, max, minimum, etc.), charge current, discharge current, C-rate, energy capacity, temperature range, and/or have any other suitable characteristics. In a specific example, each battery cell in the battery pack is arranged in series. In a second specific example, two sets of battery cells (in series) in a battery pack are arranged in parallel. The battery cells in a battery pack cooperatively generate a pack voltage, which can be: <100V, 240V, 350V, 400V, 450V, 600V, >600V, any range bounded by the aforementioned values, and/or any other suitable pack voltage.
The battery cells inside the battery pack can have any suitable geometry and/or arrangement. The battery cells can be cylindrical, button, prismatic, pouch, and/or any other suitable geometry. The battery cells are preferably arranged into multiple cell arrays, but can be arranged in a single array or otherwise arranged. The battery pack can include thermal insulation 116 between cells in the same array (e.g., interleaved between cells), adjacent cell arrays (e.g., interleaved between arrays), and/or any other suitable cell set. The thermal insulation 116 can be made of any suitable material, such as polyurethane, cellulose, fiberglass, carbon fiber, polystyrene, metal, plastic, and/or any other suitable insulation material. An example of a battery pack configuration including thermal insulation is illustrated in
The circulation subsystem preferably thermally interfaces with the top, bottom, and/or side (cylindrical, arcuate, broad, and/or narrow faces) of the battery cells. The circulation subsystem preferably thermally interfaces with the battery cells via the onboard heat exchanger, but can alternately interface with the battery cells through any other suitable component. The thermal interface can be arranged on the side of the cell array opposing the thermal insulation, adjacent the thermal insulation, on the bottom with thermal insulation on the side, on the side with thermal insulation on the bottom, interdigitated between cell arrays, interdigitated between cells, and/or otherwise arranged relative to the cell and/or thermal insulation.
The circulation subsystem of the battery thermal management system functions to increase temperature uniformity (e.g., among cells) within the battery pack. Increasing temperature uniformity can include reducing temperature disparity between disparate regions (e.g., cells) of the battery pack. In cases wherein the battery pack is at or near a uniform temperature, the circulation subsystem can also function to uniformly or nearly-uniformly adjust the temperature of the battery pack (e.g., to condition the battery pack temperature). The circulation subsystem can also function to circulate working fluid through and/or adjacent to the battery pack. The circulation subsystem can also function to store heat generated by the battery pack. The circulation subsystem can include the fluid envelope within which the working fluid is circulated, an onboard pump, a reservoir, a heat exchanger (e.g., onboard and/or offboard) and an offboard pump.
The fluid envelope functions to house the working fluid as it circulates among components of the battery thermal management system. The envelope can include piping, tanks, valves, regulators, and/or any other suitable fluid handling components. For example, the envelope can include the fluid manifolds (e.g., distribution manifolds) and the cold plate volumes. The envelope can be made of any suitable material that can transfer heat between the working fluid and other components of the system (e.g., the heat exchanger, the battery pack, etc.) and/or the external environment (e.g., the airflow proximal the battery pack). The envelope can be thermally uninsulated, partially insulated (e.g., along a portion of the periphery), or insulated from the environment/ambient conditions. The envelope can be constructed of any suitable materials such as: metals, plastics, polymers, rigid materials, non-rigid materials, or any suitable combination thereof. The material of the envelope is preferably selected to correspond to the properties/requirements of the working fluid (e.g., to avoid corrosion or other deleterious interactions, avoid degradation in high and/or low temperature conditions, meet pressure requirements of circulation subsystem, minimize head loss in circulation subsystem, etc.), but can additionally or alternatively be selected with any suitable basis.
The circulation subsystem preferably includes an onboard pump, which functions to circulate working fluid through the battery pack (e.g., via the onboard heat exchanger, via a cold plate). The system preferably includes at least one onboard pump for each battery pack; accordingly, a plurality of battery packs is preferably associated with a corresponding plurality of onboard pumps. However, the system can include one pump for each set of two battery packs, and/or any other suitable number of onboard pumps. The onboard pump is preferably arranged within the vehicle, and connected to the envelope in parallel to an interface connection between the vehicle and the infrastructure installation as shown in
The onboard pump can also function to circulate working fluid through the battery pack at a defined flow rate, wherein the defined flow rate is determined by an onboard pump controller. The onboard pump is preferably sized (e.g., physically sized, sized according to maximum pumping speed and power requirements, etc.) according to the volume of working fluid onboard the vehicle when the circulation subsystem is disconnected from the infrastructure installation (e.g., a smaller volume). For example, the onboard pump can be smaller, lighter, and/or less powerful than the offboard pump because the onboard pump is preferably not used to circulate the working fluid during conditioning (e.g., when the circulation subsystem is connected to the infrastructure installation and thus the heat exchanger). However, the onboard pump can additionally or alternatively be otherwise suitably sized.
The onboard pump is preferably connected to the envelope in parallel (examples are shown in
In alternative variations, the onboard pump can be a passive (e.g., unpowered) pump that is driven by temperature differentials originating from waste heat (e.g., generated by the battery pack during discharge, one or more electric motors during operation, etc.). The circulation subsystem can be arranged to create such temperature differentials in order to establish a convective loop of the working fluid through the envelope; for example, the envelope can be arranged within the vehicle to reject heat to the environment at a first position, and guide working fluid (e.g., gravitationally) around a closed, thermally driven cycle. However, the onboard pump can be otherwise suitably configured to passively circulate the working fluid in such variations.
The onboard pump can be any appropriate type of pump, such as: submerged pump, unsubmerged pump, positive displacement pump (e.g., rotary, reciprocating, linear), impulse pump, velocity pump, centrifugal pump, axial-flow pump, gear pump, screw pump, progressive cavity pump, roots pump, peristaltic pump, plunger pump, triplex-type plunger pump, radial-flow pump, valveless pump, helico-axial pump, and/or any other suitable type of pump. The onboard pump can have any suitable maximum flow rate, which can be limited based on the: supply power, physical limitations of the circulation subsystem, electronic control, and/or otherwise defined. The maximum flow rate of the onboard pump can be: <5 L/min, 5 L/min, 10 L/min, 20 L/min, 40 L/min, 60 L/min, 80 L/min, 100 L/min, >100 L/min, any range defined by the aforementioned values, and/or any other suitable flow rate. The onboard pump can accept any suitable supply power. The input supply can be AC or DC, with any suitable supply voltage such as: 12 VDC, 24 VDC, 48 VDC, 96 VDC, 120 VAC, 240 VAC, the same voltage as the battery pack, and/or any other suitable supply voltage. The onboard pump supply power can have any suitable maximum continuous or peak power, such as: <25 W, 25 W, 50 W, 100 W, 250 W, 350 W, 500 W, 1 kW, 2.5 kW, 5 kW, 10 kW, >10 kW, any suitable range defined by the aforementioned values, and/or any other suitable power.
The pump controller functions to operate the pump (e.g., onboard pump) between various modes, including a failsafe mode. In the failsafe mode, the pump can operate at a high flow rate in response to the detection of an off-nominal state (e.g., a thermal event) in order to circulate working fluid through the battery pack and thereby mitigate an existing thermal event and/or prevent propagation of a thermal event across multiple cells in the battery pack. Entering the failsafe mode can be triggered by detection of a thermal event in one or more cells of the battery pack, loss of power to a redundant portion of the onboard pump controller (e.g., one of two control modules), detection of a precursor condition to a thermal event, loss of communication, and/or any other suitable trigger event. The pump controller can regulate pump PRM, flow rate, pressure (e.g., pump head), power state (e.g., on/off) and/or any other suitable pump parameter.
The pump controller can be integrated into the battery electronics, integrated into the pump, or separate from the pump and battery electronics. The pump controller can be located proximal to the pump, proximal to the battery pack, proximal to a vehicle controller (e.g., flight computer), between battery pack and pump, between two battery packs, and/or otherwise arranged.
The pump controller is preferably fault tolerant, such that the onboard pump is able to operate effectively even in cases wherein all or part of the battery pack has failed (e.g., due to a thermal event, due to other trauma to the system, etc.) and ceased delivering electrical power. Fault tolerance can be achieved by powering the onboard pump controller and onboard pump using redundant connectivity between the onboard pump controller and onboard pump and a single battery pack; fault tolerance can additionally or alternatively be achieved using redundant connectivity to the onboard pump controller and onboard pump from multiple battery packs.
In a specific example of a fault tolerant configuration, the onboard pump is powered by two different halves of the battery pack via parallel sets of three phase windings, as shown in
In fault tolerant configurations, the failsafe mode of operation of the onboard pump can include operating the pump on one set of three phase windings if a thermal event occurs in one of the cells of the battery pack associated with the other of the two sets of three phase windings. The pump can enter the failsafe mode (e.g., high flow rate) in response to various trigger events as described above, including the loss of power to one of the parallel motor drive electronics subsystems (e.g., due to a thermal event disrupting power delivery to one of the parallel motor drive electronics subsystems), the receipt of a failure trigger from the battery electronics (e.g., generated in response to a detected power surge or droop associated with a possible thermal event), and/or any other suitable trigger event.
In a variant of a fault tolerant configuration, the pump controller is redundantly powered by the architecture described in U.S. application Ser. No. 16/573,837, filed 17 Sep. 2019, which is incorporated in its entirety by this reference. In a specific example of the variant, the pump controller is redundantly powered and/or communicatively connected to a first switch set and a second switch set. Each switch set 310 receives control data from a plurality of flight controllers. The first switch set is connected to a first battery pack and the second switch set is connected to a second battery pack. Examples are illustrated in
Fault tolerant configurations can include fault tolerant data and/or power connections to/from any suitable vehicle components. Vehicle components can include one or more: mission displays, radios, controllers, data loggers or acquisition devices, vehicle navigation systems (VNS), one or more cabin systems (e.g., powered devices within the cabin of the aircraft, powered devices that control environmental parameters of the cabin of the aircraft, etc.), avionics gateways, air data booms, battery management systems (BMS), heating, ventilation, and air-conditioning (HVAC) components, inceptors, inverters (e.g., a quad inverter, a standard inverter, etc.), flight devices (e.g., that control control surfaces, such as ailerons, flaps, rudder fins, landing gear, etc.), vehicle sensors (e.g., kinematics sensors, such as IMUs; optical sensors, such as cameras; acoustic sensors, such as microphones and radar; temperature sensors; smoke detectors; fire rope sensors; altimeters; pressure sensors; and/or any other suitable sensor), and any other suitable components onboard the vehicle. Vehicle components can additionally or alternately include: a sensor fusion module, a flight path vector module, data acquisition cards, a data acquisition logger, and an Ethernet radio module.
Redundant vehicle components can be distributed with any appropriate geometry or relationship. Redundant vehicle components can be distributed: linearly (e.g., parallel with or aligned along the pitch or roll axes as shown in
The circulation subsystem can include an offboard pump, which functions to circulate working fluid 152 through the heat exchanger and battery pack to condition the battery pack. The offboard pump can additionally or alternately function to circulate working fluid through the fluid manifold while fluidly connected to the circulation subsystem. The offboard pump can additionally or alternately function to circulate the working fluid through the offboard heat exchanger to condition the working fluid. The offboard pump is preferably a component of an infrastructure installation 102 that is offboard the vehicle and connected to by the vehicle during conditioning; however, the offboard pump can additionally or alternatively be a standalone component of the battery thermal management system. The offboard pump can operate independently of the onboard pump, in conjunction with the onboard pump (e.g., increasing the pressure and/or flow rate of working fluid), and/or otherwise operate. The offboard pump can be the same or different from the onboard pump—it can be the same/different type, same/different size, same/different power, and/or otherwise implemented. The offboard pump can be powered by a battery charger, external power source, battery packs, and/or be otherwise powered. The offboard pump can be arranged in series or parallel with the onboard pump(s), and/or there can be a plurality of offboard pumps arranged in series/parallel.
In some variations, the system can include both onboard and offboard pumps; in alternative variations, the system can include just an onboard pump (e.g., wherein the onboard pump can circulate working fluid through the battery pack in isolation as well as the battery pack and heat exchanger in combination when the vehicle is coupled to the infrastructure installation, and wherein the onboard pump is appropriately sized for circulating working fluid through both the isolated and combined circulation subsystem), or just an offboard pump (e.g., wherein the working fluid can passively circulate, such as via convection driven by waste heat from the battery pack, in situations wherein the vehicle is not coupled to the infrastructure installation).
In variants, the offboard pump can be the same size as the onboard pump and/or configured to circulate the working fluid at substantially the same flow rate as the onboard pump (e.g., circulating working fluid within: 50%, 25%, 15%, 10%, 5%, 2%, 1%, and/or exactly equivalent flow rate). Alternatively, the offboard pump can circulate working fluid at a greater flow rate than the onboard pump, can be larger than the onboard pump, can be smaller than the onboard pump, and/or can be otherwise configured.
In a first variant, the onboard and offboard pumps circulate the same working fluid. In a second variant, the onboard and offboard pump circulate different working fluids. In a first example of the second variant, the offboard pump injects the working fluid into the onboard system, wherein the onboard working fluid is drained before offboard cooling, then re-introduced before flight. In a second example of the second variant, the offboard pump circulates a second working fluid parallel to the onboard system (e.g., wherein the onboard working fluid is thermally connected but fluidly isolated from the offboard working fluid). In a third variant, there is no offboard pump.
The circulation subsystem can optionally include one or more fluid manifolds (or distribution manifolds) which functions to contain the working fluid and fluidly connect a remainder of components of the fluid envelope. The fluid manifold can fluidly connect and/or terminate at the onboard pump, onboard heat exchanger, fluid coupling, reservoir, and/or any other suitable components, connected in any combination of series and/or parallel. Preferably, the fluid manifold connects: an outlet of the onboard pump to an inlet of the onboard heat exchanger, an outlet of the onboard heat exchanger to an inlet of the pump, an inlet of the onboard heat exchanger to an outlet of the infrastructure installation (and/or an inlet of the fluid coupling), an outlet of the onboard heat exchanger to an inlet of the infrastructure installation (and/or an outlet of the fluid coupling), and/or connects any of the aforementioned connections to a reservoir. The fluid manifold can include piping, tanks, valves, regulators, and/or any other suitable fluid handling components. The fluid manifold can be thermally uninsulated, partially insulated (e.g., along a portion of the periphery), or insulated from the environment/ambient conditions. The fluid manifold can be constructed of any suitable materials such as: metals, plastics, polymers, rigid materials, non-rigid materials, or any suitable combination thereof. The material of the of the fluid manifold is preferably selected to correspond to the properties/requirements of the working fluid (e.g., to avoid corrosion or other deleterious interactions, avoid degradation in high and/or low temperature conditions, meet pressure requirements of circulation subsystem, minimize head loss in circulation subsystem, etc.), but can additionally or alternatively be selected with any suitable basis.
The circulation subsystem can optionally include a reservoir (examples are shown in
Additionally, the reservoir can function as a heat reservoir (adding thermal mass to the system). The volume (and/or associated mass of working fluid), for a thermal reservoir can be selected based on a range tradeoff between thermal capacity (e.g., for the specific heat of the working fluid contained within the reservoir) and the added mass of the fluid. In variants, the pump can selectively increase/decrease the mass of working fluid contained within the reservoir before beginning a trip based on the temperature setpoint and/or other trip parameters before takeoff, ensuring the optimal efficiency and/or range for different trips.
The circulation subsystem can optionally include a hose coupling, which functions to fluidly connect the working fluid onboard the vehicle to the extravehicular infrastructure (e.g., offboard cooling system). Preferably, the hose coupling establishes a dry connection (minimal leakage from connecting/disconnecting), but can alternately establish a wet connection and/or any other suitable fluid connection. The fluid coupling can be: threaded or unthreaded, gendered or ungendered, tapered or untapered, can optionally include a gasket, can optionally an include a spring-loaded valve (e.g., dry connection), and/or can have any other suitable features. The hose coupling can include a: camlock, quick-connect, quick disconnect, flanged coupling, hoselink, express coupling, storz, tri-clamp connection, leverlock, and/or any other suitable hose coupling type. The hose coupling can be any suitable material such as brass, stainless steel, aluminum, plastic, and/or any other material with any appropriate material finish (e.g., corrosion resistance, etc.). The hose coupling can include a vehicle side (integrated with the vehicle, connected to the circulation subsystem) and an extravehicular side (e.g., mechanically connected to the infrastructure installation 102). In a first variant, the extravehicular side of the hose coupling can be integrated with a charging connector 172 (e.g., part of a charging handle, as shown in the example in
The circulation subsystem can optionally include a lockout mechanism (e.g., interlock) which functions to fluidly disconnect the extravehicular infrastructure from the vehicle (e.g., onboard circulation subsystem). The lockout mechanism can be an electrical interlock, mechanical interlock, fluid interlock, shutoff valve, and/or any other suitable mechanism. The lockout mechanism can operate manually or automatically by any suitable actuation mechanism. The actuation can be electromechanical (e.g., solenoid valve, biased open, biased closed, etc.), manual (e.g., user operated), mechanical (e.g., spring loaded, relying on fluid pressure/flow to generate state change from open to closed, etc.), and/or otherwise operate. Preferably the lockout mechanism automatically decouples the fluid line if a decoupling condition is satisfied, such as if: the flow rate exceeds an absolute threshold, the flow rate differs from the flow rate commanded (e.g., by the BMS, pump controller, controller, etc.), the temperature of the incoming fluid exceeds an absolute threshold, the temperature of the incoming fluid differs from the expected temperature by a predetermined amt (e.g., >5 deg C.), composition of offboard working fluid does not match that of the working fluid onboard the vehicle (e.g., 50/50 water glycol onboard vs 80/20 offboard), the system receives a user input (e.g., hit a button, audio input, etc.) to activate the lockout mechanism, and/or any other suitable decoupling condition is satisfied. The lockout mechanism can be arranged at any suitable location relative to the aircraft and/or circulation subsystem. Preferably the lockout mechanism is arranged proximal to and/or integrated with the hose coupling, but can alternately be arrange at each onboard heat exchanger, proximal the onboard pump inlet, and/or have any other suitable arrangement. In a specific example, the lockout mechanism is a solenoid valve integrated with the hose coupling (an example is shown in
The circulation subsystem can optionally include a deionization filter, which functions to remove ions from the working fluid which can be introduced during battery cooling, conditioning, and/or otherwise introduced. The ion filter is preferably located offboard the vehicle (e.g., in the extravehicular infrastructure) to reduce vehicle mass/complexity, as continuous ion filtration is not required in some variants, however the deionization filter can alternately be located onboard the vehicle in any appropriate portion of the circulation subsystem. The working fluid can pass through the deionization filter: continuously, during battery charging, periodically, during battery conditioning (e.g., while fluidly connected to extravehicular infrastructure), and/or with any other suitable timing. In variants, the ion filter can reduce the conductivity of the coolant, which can reduce the likelihood of shorting in the event of a leak.
The heat exchange system 130 functions to distribute, transfer, remove (e.g., reject), and/or otherwise manage heat. The heat exchange system can exchange heat between a heat source and a heat sink. The heat source is preferably the heat generating components of the system (e.g., battery cells, battery pack, control electronics, etc.), but can be any other suitable heat source. The heat sink can be: the working fluid, another battery pack component (e.g., battery pack housing, battery cell, etc.), another battery pack, an aircraft component (e.g., support structure, etc.), the cabin (e.g., cabin environment, volume of air in the cabin), the ambient environment, and/or any other suitable heat sink.
The heat exchange system 130 is preferably thermally and fluidly connected to the circulation subsystem, but can be only thermally connected to the circulation subsystem, thermally or fluidly isolated from the circulation subsystem, or otherwise connected to the circulation subsystem. The heat exchange system 130 is preferably thermally connected to the battery pack (and/or cells therein), but can additionally or alternatively be fluidly connected to the battery pack or otherwise connected to the battery pack. The heat exchange system 130 can include one or more onboard heat exchangers for each cell, cell array, cell array pair, battery pack, or other cell subpopulation. The cells within a cell array can be thermally connected to a heat exchanger in series, in parallel, or a combination thereof. An onboard heat exchanger can be thermally connected to one or more cell arrays. The cell arrays within the battery pack can be thermally connected to a heat exchanger in series (e.g., by a single fluid path), in parallel, or any suitable combination thereof.
The heat exchange system can include one or more heat exchangers, manifolds, and/or other components. Examples of heat exchangers and/or heat exchange components can include: a condenser, an evaporators, a radiator, a cold plate (or cooling plate), hot plate (or heating plate), a double pipe heat exchanger, a shell and tube heat exchanger, a plate heat exchanger, a plate and shell heat exchanger, an adiabatic wheel heat exchanger, a plate fin heat exchanger, a pillow plate heat exchanger, a waste heat recovery unit, a phase-change heat exchanger, a direct contact heat exchanger (e.g., gas—liquid, immiscible liquid—liquid, solid-liquid or solid—gas, etc.), a microchannel heat exchanger, air coils, a helical-coil heat exchanger, a spiral heat exchanger, and/or any other suitable type or arrangement of heat exchanger. and/or any other suitable heat exchange component.
The heat exchange system 130 can include one or more: onboard heat exchangers arranged onboard the aircraft, offboard heat exchangers arranged offboard the aircraft, and/or other heat exchangers.
The onboard heat exchanger preferably functions to distribute heat across the battery packs and/or battery cells of the battery pack. The onboard heat exchanger can alternately function to: heat the battery cells, cool the battery cells, increase the thermal mass of the battery pack, remove heat from the battery cells for temporary thermal storage in the working fluid (e.g., during a trip, thereby increasing the thermal capacity of the system, etc.), function as a heat interface between the cells and the working fluid, increase the structural rigidity of the battery pack (e.g., function as a structural member or as part of the housing), and/or perform other functionalities. Alternately, the onboard heat exchanger can function to transfer thermal energy to an onboard cooling system (e.g., radiator, active cooling system, etc.). In one example, the onboard heat exchanger removes (e.g., rejects) less than a threshold amount or proportion of battery-generated heat from the aircraft during flight (e.g., removes less than 90%, 80%, 70%, 60%, 50%, 40%, 30%, 20%, 10%, 5%, etc. offboard the aircraft during flight). In a second example, the onboard heat exchanger passively removes battery-generated heat from the aircraft (e.g., using a radiator, using an aircraft component as a radiator, etc.). In a third example, the onboard heat exchanger actively removes battery-generated heat from the aircraft.
The heat exchange system 130 can include a single onboard heat exchanger per battery pack, multiple onboard heat exchangers per battery pack (e.g., one per cell array, one per cell), and/or any other suitable number of onboard heat exchangers per battery pack, cell array, or battery cell. Multiple onboard heat exchangers can be: stacked (e.g., with the cell, with the cell array), arranged adjacent each other (e.g., in-plane), interleaved, and/or otherwise arranged.
The onboard heat exchanger can interface the with the battery cells by side cooling, bottom cooling, and/or flood cooling (e.g., with a non-conductive working fluid, with mineral oil working fluid). The onboard heat exchanger preferably includes a plurality of cooling channels (e.g., in series and/or parallel), which can have any suitable thickness. Preferably, the heat exchanger channel thickness is minimized in order to improve packaging and/or thermal efficiency: the thickness can be: <0.5 mm, 0.5 mm, 1 mm, 1.5 mm, 2 mm, 3 mm, 4 mm, 5 mm, 7 mm, 10 mm, >10 mm, any range bounded by the aforementioned values, and/or any other suitable thickness. The onboard heat exchanger can be constructed of any suitable materials, which can be rigid, flexible, metal (e.g., copper, steel, aluminum, titanium, high temp plastics, etc.), thermal interface material (e.g., thermal paste), and/or any other suitable materials. The onboard heat exchanger can have any suitable construction.
Examples of the onboard heat exchanger include: a cold plate (e.g., cooling plate) type heat exchanger, which transfers heat from the battery cell to a working fluid within the cold plate's cavity; a solid thermally conductive plate; a flexible heat exchanger; heat pipes, heat spreaders, heat pipes, fins, extended surfaces, and/or another heat exchanger. In a first specific variant (an example of which is illustrated in
The onboard heat exchanger can have any suitable relationship or arrangement relative to: a cell, a cell array subset, an array of cells, a battery pack, and/or any other suitable component. For example, the onboard heat exchanger can thermally contact all or a portion of: a narrow face of the cell (e.g., cell side), broad face of the cell, edge of the cell, and/or any other suitable portion of the cell or cell array. Preferably, the onboard heat exchanger allows circulation of the working fluid therethrough, removing heat from the battery cell(s) by conduction. Alternately, the onboard heat exchanger can exchange (e.g., remove) heat with the battery by forced convection, free convection, or radiation as the primary mode of heat transfer. The onboard heat exchanger is preferably permanently integrated with the battery pack, but can alternatively be removably integrated with the battery pack (e.g., to increase or decrease the envelope and/or battery pack thermal mass).
The thermal interface between the battery pack (battery cells of the battery pack) and the onboard heat exchanger can be configured to redistribute thermal energy between battery cells, redistribute thermal energy between battery cells of the same array, redistribute thermal energy between arrays of battery cells within the same battery pack, redistribute thermal energy between battery packs, cool the battery pack (or battery cell), heat the battery pack (or battery cell), and/or transfer thermal energy from the battery pack (or battery cell) to the circulation subsystem, but can be otherwise configured. In a specific example, the circulation subsystem includes an onboard heat exchanger located inside the battery pack, thermally connecting the battery pack to the working fluid. In the first specific example, the onboard heat exchanger is a cold plate, which can function in multiple ways, such as: heating the battery cells, redistributing heat between the battery cells, cooling the battery cells, transferring heat from the battery cells for temporary thermal storage in the working fluid (e.g., during a trip, thereby increasing the thermal capacity of the system, etc.), and/or performing other functionalities. In a specific variant, the thermal interface between the battery pack and the onboard heat exchanger can be an adhesive, bonding agent, thermal interface material (TIM), and/or other component. In a specific example, the onboard heat exchanger is a cold plate glued to the bottom of the cells, ensuring thermal contact (e.g., with no or minimal air gap) and increasing the structural rigidity (i.e., cold plate can act as a structural element and/or transfer loads to the carbon structure/vehicle frame).
The offboard heat exchanger of the heat exchange system 130 preferably functions to exchange heat between the working fluid and the external environment, remove heat from the aircraft (e.g., offboard the aircraft), remove heat from the circulation system, and/or otherwise manage heat. In a first variant, the heat exchanger directly exchanges heat from the working fluid to the surrounding air (e.g., by forced convection). In a second variant, the offboard heat exchanger indirectly exchanges heat to the external environment by thermally connecting the working fluid to a sub-ambient cooling system (e.g., refrigeration cycle). The offboard heat exchanger can cool the working fluid and/or heat the working fluid, depending upon the desired temperature set point of the battery pack. Because the offboard heat exchanger is preferably a component of the infrastructure installation, the type and configuration of heat exchanger is preferably not constrained by the available space and/or mass budget associated with the vehicle.
The offboard heat exchanger is preferably part of the infrastructure installation, and is preferably not integrated with the vehicle. The offboard heat exchanger is preferably an active heat exchanger (e.g., wherein the working fluid is actively flowed through a structure to increase the heat transfer from the working fluid to the external environment such as air, wherein the external fluid such as air is actively flowed to increase heat transfer to or from the working fluid, etc.), but can additionally or alternatively be a passive heat exchanger (e.g., a heat sink) that transfers the heat to or from the working fluid to an external fluid medium (e.g., the air). The offboard heat exchanger can include: a condenser, an evaporator, a radiator, a refrigeration system, a cooling system, and/or any other suitable component.
In a first variant, a refrigeration system can be arranged in an extra-vehicular (off-board) infrastructure installation, allowing the vehicle to operate without the mass of one or more components of the refrigeration system. A refrigeration system can include one or more refrigeration components such as a: compressor, heat exchanger (intercooler, conditioner, evaporator, etc.), fan, air duct, thermal expansion valve (TXV), drier, refrigerant (e.g., a reservoir or volume of fluid), refrigerant manifold, and/or any other suitable elements. Including one or more refrigeration components in an extra-vehicular installation can reduce (e.g., the required power, size, volume, and/or cost of the component onboard the vehicle) and/or eliminating the need for such components to be included among the components on-board the aircraft. In a specific example of the first variant, the vehicle includes a small on-board compressor and a larger off-board compressor. In a second specific example of the first variant, the vehicle does not include an onboard compressor thermally connected to the circulation subsystem.
In a second variant, the heat exchange system 130 can include a cooling system 190, which functions to remove thermal energy from the working fluid thereby conditioning the battery. Preferably, the cooling system is located offboard the aircraft (e.g., separate and distinct from the aircraft; e.g., be the offboard heat exchanger or component thereof) as a part of the extravehicular infrastructure, however the cooling system can alternately be located onboard the aircraft (e.g., a small cooling system onboard the aircraft and a larger cooling system offboard the aircraft), and/or be otherwise located. The cooling system is preferably a sub-ambient cooling system which cools via the refrigeration cycle, and can include any suitable refrigeration components such as: compressor 192, offboard heat exchanger (intercooler, condenser, evaporator, etc.), fan, air duct, thermal expansion valve 194 (TXV), drier, refrigerant (e.g., a reservoir or volume of fluid), refrigerant manifold, and/or any other suitable elements. Including one or more cooling components in an extra-vehicular installation can reduce (e.g., the required power, size, volume, and/or cost of the component onboard the vehicle) and/or eliminating the need for such components to be included among the components on-board the aircraft. In a specific example, the system includes a small on-board compressor and a larger off-board compressor. In a second specific example of the first variant, the vehicle does not include an onboard compressor thermally connected to the circulation subsystem. In a third example, a large volume of working fluid is cooled in an offboard cooling system advance of the battery conditioning (e.g., before the aircraft lands). In the third example, the battery thermal management is not limited to the maximum cooling power or heat rejection, of the refrigeration cycle, but rather relies on the thermal capacity of the reservoir to condition the battery pack, which can enable more efficient cooling (e.g., via a larger temperature difference between the working fluid and the battery cells). In a fourth example, the working fluid on the vehicle is replaced with chilled working fluid from the offboard cooling system, thereby increasing the thermal capacity of the onboard reservoir. However, the offboard cooling system can alternately include a super-ambient cooling system and/or any other suitable cooling system with any other suitable cooling components.
The system can include battery electronics 112, such as a battery management system (BMS). The battery electronics can be coupled to one or more battery packs (e.g., with a 1:1, 1:N, or N:1 battery electronics to battery pack relationship). The battery electronics function to monitor the state of the battery pack. The state of the battery pack can include: state of charge (SoC), state of health (SoH), state of power (SoP), state of safety (SoS), temperature (e.g., of the pack, of a cell, of a cell array, of the working fluid, a temperature distribution of cells, etc.), and/or any other suitable characteristics. The battery electronics can also function to report the state of the battery pack to other components of the battery thermal management system. The battery electronics can also function to control the charge and/or discharge of the battery pack (e.g., based on commands from a vehicle operator or computerized vehicle operation system). The battery electronics can additionally function to control recirculation and/or cooling systems onboard or offboard the vehicle.
The battery electronics can include one or more sensors. The sensors of the battery electronics function to measure parameters of the battery pack during operation. The sensors can measure the electrically-related parameters of the battery pack (e.g., current flow through the battery pack, voltage of the battery pack, charge state of the battery pack, etc.), thermal parameters of the battery pack (e.g., temperature at any suitable point in the battery pack, temperature outside the battery pack, temperature change rate at any suitable point in or around the battery pack, etc.), flow rate of the working fluid through the battery pack (e.g., through the heat sink), and/or any other suitable parameters. Any suitable sensor type or modality can be utilized to measure the aforementioned parameters (e.g., a current probe, a shunt, a thermocouple, a thermistor, etc.). The battery electronics can include a communication module (wired or wireless) configured to communicatively connect to the on-board pump, vehicle controller, extravehicular infrastructure (e.g., off-board pump, battery charger, off-board cooling system, etc.), and/or any other suitable vehicle component/endpoint.
The battery electronics can be cooled by the same system(s) as the battery cells 114 and/or different cooling components. The battery electronics can be air cooled, connected to separate heat sink, thermally connected to airframe, and/or otherwise cooled separately from the battery cells—thereby reducing the thermal load on the battery thermal management system. The battery electronics can be powered by the battery packs that it controls, and/or be powered by a separate battery pack.
The battery thermal management system can optionally include a charging station, which functions to supply electrical energy to the battery packs. The charging station can be integrated with the offboard cooling system or can be separate. The electrical connector (a.k.a. charger) and hose coupling can be integrated into a single device (e.g., a charging handle) or can be separate devices. There can be any suitable number of charging stations such as one or more per: aircraft, battery pack, pump, hose coupling, or there can be multiple aircrafts, battery packs, pumps, and/or hose couplings associated with a single charging station. In a first variant, the system includes a single charger (e.g., with +/− sides) and a single (offboard side) hose coupling (e.g., with separate inlet and outlet tubes), which can connect to: the rear of the vehicle, front of the vehicle, side of the vehicle, wing of the vehicle, and/or other suitable endpoint. In a second variant, the system includes two (offboard side) hose couplings (e.g., with separate inlet and outlet tubes), which can connect to: the front/rear of the vehicle, left/right sides of the vehicle, left/right wings of the vehicle, and/or other suitable vehicle endpoints.
The battery thermal management system can optionally include an authorization mechanism which functions to ensure that authorized cooling and/or charging systems can charge/cool the vehicle. In a first variant, the authorization system is mechanical. In a first example of the first variant, a proprietary key unlocks the fluid coupling. In a second example of the first variant, the fluid coupling has a proprietary interface. In a second variant, the authorization system is digital. In a first example of the second variant, the offboard fluid coupling head or offboard charging and/or cooling installation sends its identifier to controller (e.g., onboard controller), the controller verifies the offboard charging/cooling system (e.g., with an onboard database, with a central management system, with a proprietary cloud system, etc.), and the controller initiates cooling/charging in response to verification (e.g., by starting the pump, unlocking the fluid coupling, etc.). In a second example, the offboard charging and/or cooling system verifies the aircraft in the same or similar manner to the first example.
In a specific example, the battery thermal management system includes a set of onboard and offboard components. The set of onboard components of this example includes one or more battery packs, a portion of the circulation subsystem, an onboard pump, and an onboard pump controller, and excludes a heat exchanger or reservoir. The set of onboard components are integrated with an eVTOL aircraft in this example. The set of offboard components of this example (e.g., the infrastructure installation) includes a heat exchanger, another portion of the circulation subsystem that can be connected to the onboard portion to enable conditioning of the one or more battery packs, an offboard pump, an offboard pump controller, and a reservoir. In a specific example, the vehicle excludes heavy components (e.g., components weighing more than 5%, 10%, 20%, etc. of the unloaded vehicle weight) of the circulation subsystem or thermal conditioning system, such as a compressor or refrigeration unit.
The system can include a controller. The controller can be distributed across multiple nodes (e.g., a computational node aboard the vehicle and a node coupled to the infrastructure installation) or centralized at a single point (e.g., a centralized controller that is communicatively coupled with controllable components of the system such as the onboard pump controller, the offboard pump controller, etc.). The controller functions to execute command instructions based on input data to control elements of the battery thermal management system. In examples, the controller can execute or implement the entirety or portions of the method 200; however, the controller can additionally or alternatively execute or implement any suitable functionality of the system components as described herein or otherwise suitably defined.
The system can optionally include gas relief (e.g., venting) to evacuate pressurized or unpressurized working fluid in a gaseous state (or other gasses) from any suitable portion of the fluid manifold and/or fluid envelope. Working fluid vaporization can, in variants, protect against propagation of thermal events and/or increase the thermal capacity of the system by taking advantage of the latent heat of vaporization of the working fluid. Gas relief mechanisms (vents, valves, burst membranes, etc.) can be included in: the battery pack (e.g., pack side, pack end), onboard heat sink, fluid manifold (e.g., adjacent to the pump), reservoir, the pump, and/or at any other suitable location in the fluid envelope. In variants, thermal events (e.g., thermal runaway) can be mitigated by making more working fluid (e.g., coolant) available to change phases (e.g., vaporize and capture latent heat of vaporization), which can allow greater heat absorption without requiring heat redistribution to other parts of the system (e.g., internal energy of gas rejected through gas relief mechanisms does not remain in system). In a first example, the flow rate can increase (e.g., pump RPM, redirect coolant toward one or more cells undergoing a thermal event, redirect coolant toward anticipated thermal event, pumping more coolant from the reservoir, etc.) to enable increased availability of fluid for phase change. In a second example, heat absorbed through phase change (e.g., vaporization) is removed/rejected from the system. In a third specific example, heat absorbed through phase change (e.g., vaporization) remains in the system, and can be redistributed to working fluid (e.g., in a reservoir, in a liquid phase), other battery cells, and/or other suitable endpoints. However, thermal events can be otherwise mitigated using the working fluid or other mechanism.
The system of the preferred embodiment and variations thereof can be embodied and/or implemented at least in part as a machine configured to receive a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated with and/or part of the system. The computer-readable medium can be stored on any suitable computer-readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a general or application specific processor, but any suitable dedicated hardware or hardware/firmware combination device can alternatively or additionally execute the instructions.
4. Method
As shown in
Block S100 includes determining the temperature setpoint of the battery pack. Block S100 functions to determine a target temperature to which the battery pack should be conditioned. Block S100 is preferably performed prior to vehicle departure from the infrastructure installation, such that the active conditioning components of the infrastructure installation can be used to condition the battery pack (e.g., in accordance with one or more variations of Block S150), but Block S100 can additionally or alternatively be performed at any other suitable time. Block S100 is preferably performed automatically by a controller substantially analogous to the controller of the system 100, but can be otherwise suitably performed by any suitable component of a suitable system and/or entity associated with such a system (e.g., a human operator).
The temperature setpoint is preferably the takeoff temperature setpoint, but can additionally or alternatively be the operational setpoint or any other suitable setpoint.
Block S100 is preferably performed based on the trip profile of the vehicle. The trip profile can include a duration, trip range, vehicle weight, time spent in various modes of operation (e.g., hover, forward/cruise, transition, takeoff, landing, etc.), ambient temperature (e.g., of locations along the trip), battery parameters (e.g., age, capacity, cell type/model, current temperature, current SoC, SoP, SoH, etc.), vehicle weight, cargo weight, weight distribution, and/or any other suitable parameters. Battery parameters can be determined for an individual cell, can be generic for cells with similar parameters, can be determined for a battery pack, can be generic for battery packs with similar parameters, or be otherwise determined. In examples wherein the vehicle is an aircraft, the trip profile can include a flight plan (e.g., for one or more flights or legs of a flight) and/or any other flight data (e.g., weather data, air traffic data, etc.). The trip profile can be received from a user, user device, onboard controller, a remote system and/or other suitable endpoint, and can include any other suitable set of parameters.
Block S100 can include determining an expected power consumption for the trip (e.g., flight). The expected power consumption can be determined based on the trip profile, a power consumption model, and/or other information. In a first variation, the expected power consumption can be determined based on a physical vehicle model, which can be theoretical or empirically determined based on testing data or historical trip data (e.g., for the vehicle, for a fleet of vehicles). In a second variation, the expected power consumption can be selected from a lookup table/chart for the trip profile and/or physical vehicle model. In a third variation, the expected power consumption can be determined based on a machine learning model trained to output expected power consumption. However, the expected power consumption for the trip can be otherwise determined.
Block S100 can include determining the expected heat generation during the trip (e.g., the flight) based on a battery model. The expected heat generation can be: the heat generation rate, heat generated between flight locations, rate of heat generation, and/or other heat generation parameter. The expected heat generation can be: selected (e.g., from a lookup table), calculated (e.g., from an equation, by a battery model, etc.), or otherwise determined. The battery model can be generated based on testing data (e.g., empirical testing for the battery cell, for the battery pack), historical flight data for a given battery pack, a predetermined model (e.g., received from the manufacturer or a battery characterization entity, etc.), or otherwise generated. The battery model can be predetermined, selected for use based on the battery cell type (e.g., class, manufacturer, model, etc.), or otherwise determined. The battery model can determine the expected heat generation based on the starting battery pack temperature (e.g., averaged across all cells, measured at a single temperature sensor for the pack, temperature of the working fluid, etc.), the estimated state of charge (e.g., at takeoff), the state of health (SoH) estimated for a battery pack or each battery cell, an expected power consumption (e.g., total power consumption, as a timeseries, power consumption rate, etc.) for the trip (e.g., determined from an aircraft model or simulation, a lookup table, etc.), battery specifications, and/or any other suitable parameters. In a first variant, the expected heat generation is selected from a lookup table/chart for the given input parameters. In a second variant, the expected heat generation is determined based on a machine learning model trained to output expected power consumption. However, the expected heat generation during the trip (e.g., flight) can be otherwise determined.
Block S100 can include, based on the expected heat generation, determining an expected temperature rise of the battery pack. The temperature rise can be the absolute temperature increase over an entirety of the trip (e.g., flight), a temperature increase for each segment of a mission (e.g., each leg of a flight), a rate of increase, or another parameter. The expected temperature rise can be determined based on: the thermal mass of the battery pack (e.g., specific heat), specific heat of the working fluid (e.g., for a known volume and/or temperature of working fluid), and/or expected heat loss during the trip (e.g., expected heat dissipation to the environment, to a remainder the vehicle, to the cabin, from heat sources/sinks, etc.). The thermal mass of the battery pack can be: empirically determined by testing, theoretically modeled (e.g., calculated), determined based on historical temperature changes during charging and/or discharging, retrieved from a database, and/or otherwise determined. The thermal mass of the battery pack can be: the absolute thermal mass of the battery pack, the available thermal mass of the battery pack (e.g., amount of heat the battery pack can absorb before reaching a maximum battery temperature, discussed below, given the current battery pack temperature and/or estimated battery pack temperature at takeoff), and/or other thermal parameter.
Based on the expected heat rise, Block S100 can optionally include determining an expected temperature difference between the battery cells and the working fluid, which can include: assuming a fixed offset (e.g., same temperature, 2 deg C. difference, etc.), dynamically modelling temperature transience based on material properties and flow rate, using historical/testing data, and/or otherwise determining the expected temperature difference. However, the expected temperature rise of the battery pack and/or cells can be otherwise determined.
Block S100 can include offsetting the expected temperature rise from battery temperature requirement to determine the temperature setpoint. The battery temperature requirement can be a maximum battery (pack or cell) temperature of: >65 deg C., 65 deg C., 60 deg C., 55 deg C., 50 deg C., 45 deg C., 40 deg C., <45 deg C., any range bounded by the aforementioned values, and/or any other suitable temperature. The battery temperature requirement can be determined based on testing data, battery specifications, battery efficiency ranges, battery lifetime (e.g., temperature at which battery starts to degrade), battery SoH, battery SoC, a likelihood of thermal runaway (e.g., at a given state of charge, absolute threshold for a given battery chemistry, battery manufacturer requirement, warranty requirement, etc.), a safety margin, the flight plan (e.g., wherein different battery temperature requirements are selected for each leg of a flight or each flight of a flight series), and/or otherwise determined. In a specific example, the expected temperature change during the flight can be subtracted from the battery temperature requirement to obtain the temperature setpoint.
Block S100 can include adjusting the temperature setpoint of the battery based on the battery SoC (e.g., current SoC, expected SoC at takeoff, expected SoC profile during flight), which functions to reduce or mitigate the risk of thermal runaway propagating at high battery SoC. Adjusting the temperature setpoint can include determining the likelihood of a thermal event at a given SoC and an expected power consumption, determined based on the current SoC, takeoff SoC, cooling rate, rate of thermal redistribution, estimated heat generated during charging, and/or any other suitable parameters. Determining the likelihood of a thermal event can be determined based on a probability of thermal propagation at a particular SoC, a lookup table, a machine learning model, and/or other suitable technique. The likelihood of a thermal event can be predicted once for a trip profile, over a timeseries model of an expected trip profile, periodically for an expected trip profile, for a continuous function approximation of a trip profile/SoC, and/or otherwise predicted. In a first example, the temperature set point for the battery, for a trip of 10 miles, is determined to be 40 deg C. The battery pack has a 95% SoC. Block S100 adjusts the temperature set point down to 30 deg C. to ensure that thermal events are unable to propagate given the high SoC.
Because the vehicle is preferably optimized for low mass and therefore preferably lacks active conditioning equipment, the temperature set point is preferably determined in accordance with calculated temperature change during the trip (e.g., calculated based on the trip profile). However, the temperature set point can be determined based on desired aircraft component temperatures (e.g., wing temperatures, nacelle temperatures, hub temperatures, cabin temperatures), wherein the battery pack(s) can function as heat sources, other component heat generation, and/or other parameters. For example, the trip profile can include the takeoff weight of the vehicle, the trip distance, and the estimated time in flight at each phase of the trip and associated expected power expenditures. In this example, Block S100 can include calculating the discharge characteristics of the battery pack during a flight based on the trip profile (e.g., including a flight plan), and calculating the expected temperature rise during flight and determining a pre-flight temperature set point such that the battery pack temperature remains within a predetermined range (e.g., determined to prevent the occurrence of a thermal event). In related examples, the basis for determining the temperature set point can additionally or alternatively include the vehicle mass (loaded or unloaded), the drag profile of the vehicle, the energy discharge profile, and/or any other suitable predetermined or dynamically determined time-series quantifying aspects of vehicle travel (e.g., a trip).
In a second variant, the temperature setpoint can be heuristically determined (e.g., based on a flight plan).
In a third variant, the temperature setpoint for the battery pack can be predetermined (e.g., absolute maximum, static setpoint, etc.).
In a fourth variant, the temperature setpoint can be determined based on a user input.
In a fifth variant, the temperature setpoint can be determined from a lookup table (e.g., relating flight parameters, such as flight length or aircraft weight, with the temperature setpoint or expected temperature rise).
In a sixth variant, the temperature setpoint can be determined by a trained neural network. However, the temperature setpoint can be otherwise determined.
In seventh variant, the temperature set point can be determined based on an optimal discharge temperature associated with the particular chemistry of the battery pack (e.g., a temperature or temperature range at which power delivery is maximally efficient. The temperature set point can be equal to the optimal discharge temperature, but can additionally or alternatively be less than the optimal discharge temperature such that the battery pack is at the optimal discharge temperature for a desired time period during the trip (e.g., for a maximized time period, for a time period associated with higher risk vehicle operations such as takeoff and/or landing, etc.) as a result of warming of the battery pack during discharge. However, the temperature set point can additionally or alternatively be otherwise suitably determined. An example of Block S100 is shown in
In an eighth variant the expected temperature rise can be negative (e.g., a temperature change, a temperature decrease, etc.).
Block S150 includes adjusting the battery pack temperature to the temperature set point. In variants, vehicle operation (e.g., takeoff or flight) can be conditioned on the battery pack temperature satisfying the temperature set point. Block S150 functions to condition the battery pack, which can include heating and/or cooling the battery pack, in order to avoid the need for active temperature control and maximize performance of the battery pack during vehicle operation. The temperature setpoint is preferably the takeoff temperature setpoint, but can additionally or alternatively be the operational setpoint or any other suitable setpoint. Block S150 is preferably performed while the vehicular components (e.g., the battery pack and onboard circulation subsystem) are coupled to the extra-vehicular components (e.g., the offboard circulation subsystem, heat exchanger, offboard pump, etc.), which is preferably prior to vehicle operation on a trip (e.g., flight); however, Block S150 can additionally or alternatively be performed at any other suitable time. S150 is preferably performed during battery pack charging (e.g., to a predetermined SOC), but can additionally or alternatively be performed independent from battery pack charging (e.g., only the battery packs are cooled while the aircraft is grounded; the aircraft takes off only after the takeoff temperature setpoint is reached; etc.).
In variations, Block S150 can include connecting the circulation subsystem to the offboard cooling system, which can be performed manually (e.g., by a user), automatically (e.g., robotic and/or electromechanical connection), and/or otherwise performed.
In variations, Block S150 can include actively circulating working fluid through the combined onboard and offboard circulation subsystem using the offboard pump, such that heat is exchanged between the heat exchanger and the environment (e.g., to accept or reject heat to the environment) and between the battery pack and the working fluid (e.g., to heat or cool the battery pack to the set point temperature). In alternative variations, Block S150 can include allowing the battery pack to passively cool to the temperature of the environment (e.g., wherein the temperature set point is substantially equal to the temperature of the environment and it is determined that the battery pack will passively reach thermal equilibrium with the environment prior to initiation of a trip and operation of the vehicle). In a third variation, S150 can include cooling or warming the battery pack to a charging temperature range, and/or maintaining the battery pack temperature within the charging temperature range, by circulating fluid through the circulation subsystem. In this variation, S150 can optionally include cooling or warming the battery pack to the takeoff temperature setpoint after charging completion.
Block S150 can include controlling the offboard cooling system operation, which may be controlled: at the BMS (e.g., onboard BMS), at the battery electronics, at a vehicle controller, at the charging station, offboard the vehicle, onboard the vehicle, and/or at any other suitable endpoint. Block S150 can include controlling the circulation subsystem (e.g., circulating the working fluid), which can optionally include adjusting a flow rate through the pump (e.g., onboard and/or offboard). Block S150 can include actively circulating the working fluid, and can optionally include (actively) circulating a second working fluid (e.g., refrigerant). Block S150 can include actively removing heat from the working fluid, such as with an offboard refrigeration system (e.g., including a compressor, TXV, evaporator, and condenser; an example is shown in
In a specific example, the battery pack temperature can be reduced during cargo (e.g., passenger) loading/unloading and/or battery charging. The turnover time for unloading, loading, battery charging and/or conditioning can be: less than 3 minutes, 5 minutes, 7 minutes, 10 minutes, 12 minutes, 15 minutes, 20 minutes, 35 minutes, 30 minutes, 45 minutes, 1 hour, greater than 1 hour, any range bounded by the aforementioned values, and/or any other suitable turnover time. The temperature decrease during the vehicle turnover time can be: <5 deg C., 5 deg C., 10 deg C., 15 deg C., 25 deg C., 30 deg C., 35 deg C., >35 deg C., any range bounded by the aforementioned values, and/or any other suitable temperature change. In a first example, the battery pack temperature decreases (e.g., continuously, monotonically, etc.) during concurrent charging and conditioning (as shown in the example in
In a first example, battery charging, concurrent with Block S150 or otherwise, can include: electrically connecting the battery pack to the charger (e.g., via electrical connector), determining a SoC threshold based on the expected power consumption for the trip profile and the battery power capacity, determining satisfaction of a charging condition (e.g., SoC equal to or greater than the SoC threshold), ceasing charging of the battery pack in response to satisfaction of the charging condition, and/or electrically disconnecting the battery pack from the charger.
Block S150 can optionally include disconnecting the circulation subsystem from the offboard cooling system, which can occur manually (e.g., by the user) and/or automatically via the lockout mechanism (an example is shown in
Block S200 includes determining the instantaneous temperature of the battery pack. Block S200 functions to determine the temperature of the battery pack for use in adjusting the temperature of the battery pack (e.g., towards a set point temperature as determined in accordance with one or more variations of Block S100, downward to avoid the risk or occurrence of a thermal event, etc.). Block S200 can include directly measuring the instantaneous temperature of the battery pack (e.g., with a temperature sensor), inferring or estimating the temperature of the battery pack (e.g., based on the output of another sensor that is not a temperature sensor, in accordance with a thermal model of the battery pack, etc.), calculating the temperature of the battery pack (e.g., based on the output power of the battery pack), and/or otherwise suitably determining the temperature. The temperature determined can be the temperature at a physical point within the battery pack (e.g., an arbitrary point, a point coupled to a sensor input, etc.), a temperature distribution (e.g., three dimensional distribution) within the battery pack (e.g., at a cell-by-cell resolution, at a finer or coarser resolution than cell-by-cell, etc.), the rate of temperature change of a point within the battery pack, the distribution of the rate of temperature change within the battery pack, and/or any other suitable quantification or derivative quantity of temperature.
Block S200 can be performed during battery conditioning (e.g., in accordance with one or more variations of Block S150); for example, the instantaneous temperature of the battery pack can be measured to determine whether the battery pack has reached the determined temperature set point. Block S200 can also be performed during vehicle operation (e.g., flight, driving, traversing water, etc.); for example, Block S200 can include monitoring the temperature and/or temperature-related data to determine the thermal state of the battery pack during use.
Block S200 can include detecting a thermal event. Detecting a thermal event can include determining that the temperature and/or temperature rise rate has exceeded a threshold value, based on a temperature or temperature change rate measurement. Block S200 can include inferring a thermal event, based on a signal that is indicative of a thermal event (e.g., a current spike or dropout, a power fluctuation, etc.) in addition to or alternatively to a direct measurement of the temperature or other fire detection measures (e.g., smoke detector, fire rope, etc.). For example, Block S200 can include detecting propagation of a thermal anomaly between multiple cells in the battery pack based on the measured temperature rise rate in a plurality of adjacent cells. In another example, Block S200 can include detecting a thermal event in a battery pack based on an output current dropout resulting from an internal short circuit. However, Block S200 can include otherwise suitably detecting a thermal event.
Block S200 can include predicting a thermal event. A thermal event can be predicted based on a thermal model of the battery pack, and Block S200 can include determining that a thermal event is likely to occur (e.g., associated with a quantifiable probability above a threshold value) based on vehicle operational data (e.g., flight data, trip data, etc.). For example, Block S200 can include predicting that a thermal runaway is likely based on flight data indicating an emergency landing has occurred (e.g., a shock sensor reading, a message from a flight computer, etc.).
Block S200 can optionally include notifying a user, pilot, remote server, third party of thermal event and/or a current temperature. Notification can occur: with any suitable timing, which can be before the trip, during conditioning, during battery charging, during the trip (e.g., periodically, continuously, etc.), in response to thermal event detection, and/or with any other suitable timing. An example is shown in
Block S200 can optionally include controlling the vehicle based on the temperature, which can include: continuing the trip plan execution if the temperature is within a predetermined temperature range (e.g., below absolute battery max, within threshold deviation from expected temperature profile, no current thermal event, etc.), in response to the temperature exceeding a threshold: reducing/cutting power draw from a battery pack, executing an emergency landing, dynamically adjusting the trip plan during the trip, and/or otherwise controlling the vehicle.
Block S200 can additionally or alternatively include determining a thermal event in any other suitable manner.
Block S250 includes redistributing heat within the battery pack based on the temperature of the battery pack. Block S250 functions to utilize the thermal mass of the battery pack as a whole to absorb excess heat resulting from a thermal event in a portion of the battery pack. Block S250 can also function to achieve temperature uniformity within the battery pack. Block S250 can also function to prevent the occurrence of a thermal event (e.g., transport heat away from a malfunctioning cell to prevent a thermal runaway) and/or the worsening of a thermal event (e.g., transport heat away from a cell experiencing thermal runaway to prevent propagation). S250 can be performed by the onboard pump, offboard pump, and/or any other suitable pump.
Block S250 can include controlling a flow rate of an onboard pump that is operable to circulate working fluid through a closed, onboard portion of the onboard circulation subsystem. Block S250 can include determining the flow rate based on received data (e.g., thermal event data, flight data, trip data, etc.) and controlling the onboard pump (e.g., by way of a pump controller) to implement the determined flow rate.
Block S250 is preferably performed during vehicle operation away (e.g., and decoupled) from the infrastructure installation, and thus preferably does not include active conditioning of the battery pack (e.g., to cool the battery pack as a whole, to warm the battery pack as a whole) but rather preferably includes redistributing the heat of the battery pack across the thermal mass of the battery pack (e.g., transporting excess heat from one cell to another cell or cells which are at or below a nominal temperature). However, Block S250 can additionally or alternatively include exchanging heat between the onboard system and the environment (e.g., through a radiator section of the onboard circulation subsystem) without the use of a dedicated, high-throughput heat exchanger such as that integrated with the infrastructure installation.
Block S250 can be performed in response to a detected thermal event or other system failure, as a mechanism for failsafe and/or failure-tolerant operation of the vehicle. For example, Block S250 can include operating the onboard pump at a maximum flow rate in response to a detected thermal event.
Block S250 can be performed based on contextual data. For example, the contextual data can include flight information such as altitude and an estimated time period and power profile required before executing an emergency landing, and Block S250 can include determining a maximum allowable flow rate based on the remaining energy in the battery pack (to power the onboard pump) and the contextual data, and operating the onboard pump at the determined maximum allowable flow rate. In a related example, Block S250 can include preventing activation of the onboard pump in spite of the occurrence of a thermal event in cases wherein onboard energy would be better utilized in powering propulsion systems (e.g., enabling an aircraft to land safely even while sustaining damage to the battery pack).
Block S250 can be performed based on a predicted thermal event. For example, Block S250 can include preemptively operating the onboard pump at a maximum flow rate in response to a prediction that a thermal runaway is probable (e.g., based on detection of a hard landing, the output of a shock sensor, an emergency switch being activated by a vehicle operator, etc.).
Block S250 can optionally include detecting a leak in the circulation subsystem. Block S250 can, in response to detecting a leak, automatically stop the pump to minimize the amount of fluid loss and/or likelihood of electrical shorting, sending a notification (e.g., to a user within the aircraft, a pilot, a central management system, etc.), or otherwise mitigate leak-caused failures. Leak detection can make use of resistive, capacitive, and/or optical sensors, and/or any other suitable set of sensors. Leaks can be detected as: loss of working fluid volume from the fluid envelope (e.g., based on a time series of sensor measurements) above a predetermined loss threshold (e.g., 0.5 L, 1 L, etc.), a change in the working fluid resistivity (e.g., increase, decrease), detecting an open circuit (e.g., by running current through the working fluid), and/or otherwise determined.
In a first variant, Block S250 does not remove substantial amounts of heat from the thermal system cooperatively defined by the battery pack and circulation subsystem during the trip. In a first example, less than 50%, 25%, 10%, 5%, 3%, 1%, of generated heat (or total heat) is rejected during the trip.
In a second variant, Block S250 does not remove substantial amounts of heat from the battery pack and/or vehicle system during the trip. In a first example, less than 10%, 5%, 1%, of generated heat, or total heat is removed during the trip. In a second example, the temperature of the battery pack (e.g., net temperature, highest individual cell temperature, etc.) increases monotonically (e.g., rate of temperature change can be uniform or non-uniform, but is strictly greater than zero; continuously; etc.) during the trip. In a third example, the thermal energy contained within the thermal system of the battery pack and working fluid increases continuously (e.g., rate of temperature change can be uniform or non-uniform, but is strictly greater than zero) during the trip.
In a third variant, Block S250 removes heat from the battery pack and/or vehicle system during the trip.
In a fourth variant, Block S250 redistributes heat continuously during a trip. In a specific example, the working fluid is circulated at a max flowrate (e.g., absolute maximum, maximum continuous flowrate) of the pump, onboard heat exchanger, and/or fluid manifold (or envelope). In a second specific example, the flow rate of circulation during the trip is substantially the same circulation during battery conditioning, such as within 50%, within 25%, within 10%, within 5%, within 3%, within 1%, exactly the same, and/or otherwise equivalent.
In a first specific example, active heating and/or cooling includes applying mechanical work to a working fluid in order to create a steady state temperature difference (e.g., of greater than: 5 deg C., 10 deg C., 15 deg C., 20 deg C., 25 deg C., 50 deg C., etc.) between the working fluid and the battery pack. In a second specific example, there is no active heat removal and/or active cooling of the battery pack during a trip, and there is active heat removal and/or active cooling of the battery after the trip. In a third specific example, there is no active cooling of the collective thermal system of the battery pack and the circulation subsystem (e.g., including the fluid manifold and the volume of working fluid onboard the aircraft). In the third specific example, there is no forced convection between the environment and the collective thermal system including the battery pack and the circulation subsystem (e.g., heat exchange limited to radiation, natural convection, and conduction).
Although omitted for conciseness, the preferred embodiments include every combination and permutation of the various system components and/or method Blocks, which can be combined in any suitable permutation or combination and/or omitted in whole or in part from variations of the preferred embodiments.
As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the preferred embodiments of the invention without departing from the scope of this invention defined in the following claims.
This application is a continuation of U.S. application Ser. No. 16/857,003, filed 23 Apr. 2020, which claims the benefit of U.S. Provisional Application No. 62/837,504, filed 23 Apr. 2019, each of which is incorporated in its entirety by this reference. This application is related to U.S. application Ser. No. 16/409,653, filed 10 May 2019, U.S. application Ser. No. 16/573,837, filed 17 Sep. 2019, each of which is incorporated in its entirety by this reference.
Number | Name | Date | Kind |
---|---|---|---|
1386713 | Leinweber et al. | Aug 1921 | A |
1496723 | Miller | Jun 1924 | A |
1794202 | Pickard | Feb 1931 | A |
D171509 | Lightbourn et al. | Feb 1954 | S |
2868476 | Schlieben | Jan 1959 | A |
2969935 | Price | Jan 1961 | A |
2981339 | Kaplan | Apr 1961 | A |
3002712 | Sterling | Oct 1961 | A |
3035789 | Young | May 1962 | A |
3059876 | Platt | Oct 1962 | A |
3081964 | Quenzler | Mar 1963 | A |
3082977 | Melvin | Mar 1963 | A |
3089666 | Quenzler | May 1963 | A |
3136499 | Kessler | Jun 1964 | A |
3141633 | Mackay | Jul 1964 | A |
3159361 | Weiland | Dec 1964 | A |
3181810 | Olson | May 1965 | A |
3231221 | Platt | Jan 1966 | A |
3259343 | Roppel | Jul 1966 | A |
3350035 | Schlieben | Oct 1967 | A |
3360217 | Trotter | Dec 1967 | A |
3404852 | Sambell et al. | Oct 1968 | A |
3592412 | Glatfelter | Jul 1971 | A |
3618875 | Kappus | Nov 1971 | A |
3693910 | Aldi | Sep 1972 | A |
3795372 | Feldman | Mar 1974 | A |
3834654 | Miranda | Sep 1974 | A |
3856238 | Malvestuto | Dec 1974 | A |
4022405 | Peterson | May 1977 | A |
4047840 | Ravenhall et al. | Sep 1977 | A |
4053125 | Ratony | Oct 1977 | A |
4146199 | Wenzel | Mar 1979 | A |
4263786 | Eng | Apr 1981 | A |
4356546 | Whiteside et al. | Oct 1982 | A |
4387866 | Eickmann | Jun 1983 | A |
4459083 | Bingham | Jul 1984 | A |
4519746 | Wainauski et al. | May 1985 | A |
4569633 | Flemming | Feb 1986 | A |
4667909 | Curci | May 1987 | A |
4742760 | Horstman et al. | May 1988 | A |
4784351 | Eickmann | Nov 1988 | A |
4799629 | Mori | Jan 1989 | A |
4914657 | Walter et al. | Apr 1990 | A |
4925131 | Eickmann | May 1990 | A |
4979698 | Lederman | Dec 1990 | A |
4982914 | Eickmann | Jan 1991 | A |
5001646 | Caldwell et al. | Mar 1991 | A |
5031858 | Schellhase et al. | Jul 1991 | A |
5082079 | Lissaman et al. | Jan 1992 | A |
5085315 | Sambell | Feb 1992 | A |
5141176 | Kress et al. | Aug 1992 | A |
5156363 | Cizewski et al. | Oct 1992 | A |
5174721 | Brocklehurst | Dec 1992 | A |
5184304 | Huddle | Feb 1993 | A |
5374010 | Stone et al. | Dec 1994 | A |
5381985 | Wechsler et al. | Jan 1995 | A |
5405105 | Kress | Apr 1995 | A |
5419514 | Duncan | May 1995 | A |
5472156 | Bivens et al. | Dec 1995 | A |
5515282 | Jackson | May 1996 | A |
5715162 | Daigle | Feb 1998 | A |
5806805 | Elbert et al. | Sep 1998 | A |
5823468 | Bothe | Oct 1998 | A |
5839691 | Lariviere | Nov 1998 | A |
5842667 | Jones | Dec 1998 | A |
5868351 | Stamps et al. | Feb 1999 | A |
5899085 | Williams | May 1999 | A |
6098923 | Peters | Aug 2000 | A |
6254032 | Bucher | Jul 2001 | B1 |
6260796 | Klingensmith | Jul 2001 | B1 |
6276633 | Balayn et al. | Aug 2001 | B1 |
6286783 | Kuenkler | Sep 2001 | B1 |
6293491 | Wobben | Sep 2001 | B1 |
6343127 | Billoud | Jan 2002 | B1 |
6402088 | Syrovy et al. | Jun 2002 | B1 |
6460810 | James | Oct 2002 | B2 |
6474604 | Carlow | Nov 2002 | B1 |
6561455 | Capanna | May 2003 | B2 |
6625033 | Steinman | Sep 2003 | B1 |
6655631 | Austen-Brown | Dec 2003 | B2 |
6719244 | Gress | Apr 2004 | B1 |
6745977 | Long et al. | Jun 2004 | B1 |
6883748 | Yoeli | Apr 2005 | B2 |
6892980 | Kawai | May 2005 | B2 |
7048505 | Segota et al. | May 2006 | B2 |
7118066 | Allen | Oct 2006 | B2 |
7147182 | Flanigan | Dec 2006 | B1 |
7159817 | Vandermey et al. | Jan 2007 | B2 |
7219013 | Young et al. | May 2007 | B1 |
7263630 | Sailer | Aug 2007 | B2 |
7310573 | Stickling | Dec 2007 | B2 |
7318565 | Page | Jan 2008 | B2 |
7364114 | Wobben | Apr 2008 | B2 |
7376088 | Gambardella et al. | May 2008 | B2 |
7802754 | Karem | Sep 2010 | B2 |
7822516 | Yanaka et al. | Oct 2010 | B2 |
7857253 | Yoeli | Dec 2010 | B2 |
7857254 | Parks | Dec 2010 | B2 |
7874513 | Smith | Jan 2011 | B1 |
7877627 | Freydel | Jan 2011 | B1 |
7950606 | Atkey et al. | May 2011 | B2 |
8016226 | Wood | Sep 2011 | B1 |
8016566 | Agnihotri et al. | Sep 2011 | B2 |
8056866 | De | Nov 2011 | B2 |
8152096 | Smith | Apr 2012 | B2 |
8275494 | Roth | Sep 2012 | B1 |
8376264 | Hong et al. | Feb 2013 | B1 |
8469306 | Kuhn | Jun 2013 | B2 |
8485464 | Kroo | Jul 2013 | B2 |
8527233 | Mcintyre | Sep 2013 | B2 |
8602347 | Isaac et al. | Dec 2013 | B2 |
8616492 | Oliver | Dec 2013 | B2 |
8708273 | Oliver | Apr 2014 | B2 |
8733690 | Bevirt et al. | May 2014 | B2 |
8800912 | Oliver | Aug 2014 | B2 |
8849479 | Walter | Sep 2014 | B2 |
8998125 | Hollimon et al. | Apr 2015 | B2 |
9046109 | Duke et al. | Jun 2015 | B2 |
9075144 | Straub et al. | Jul 2015 | B1 |
9102401 | Collins et al. | Aug 2015 | B2 |
9128109 | Oneill | Sep 2015 | B1 |
9316141 | Pilavdzic | Apr 2016 | B2 |
9415870 | Beckman et al. | Aug 2016 | B1 |
9422055 | Beckman et al. | Aug 2016 | B1 |
9435661 | Brenner et al. | Sep 2016 | B2 |
9527581 | Bevirt et al. | Dec 2016 | B2 |
9561857 | Weber | Feb 2017 | B2 |
9694699 | Kelty | Jul 2017 | B2 |
9694911 | Bevirt et al. | Jul 2017 | B2 |
9771157 | Gagne et al. | Sep 2017 | B2 |
9786961 | Dyer et al. | Oct 2017 | B2 |
9851723 | Builta | Dec 2017 | B2 |
9855819 | Ochocinski et al. | Jan 2018 | B2 |
9944386 | Reichert et al. | Apr 2018 | B1 |
9963228 | McCullough et al. | May 2018 | B2 |
10029808 | Blanding et al. | Jul 2018 | B2 |
10046855 | Bevirt et al. | Aug 2018 | B2 |
10144503 | Vander Lind et al. | Dec 2018 | B1 |
10144504 | Selwa et al. | Dec 2018 | B1 |
10177424 | Melack et al. | Jan 2019 | B1 |
10183746 | McCullough et al. | Jan 2019 | B2 |
10208676 | Johnson et al. | Feb 2019 | B2 |
10246184 | Ragland | Apr 2019 | B2 |
10247100 | Leamy et al. | Apr 2019 | B2 |
10287011 | Wolff et al. | May 2019 | B2 |
10364036 | Tighe et al. | Jul 2019 | B2 |
10392107 | Har et al. | Aug 2019 | B2 |
10407164 | Blumer | Sep 2019 | B2 |
10497996 | Muniz et al. | Dec 2019 | B1 |
10501194 | Knapp et al. | Dec 2019 | B2 |
10513334 | Groninga et al. | Dec 2019 | B2 |
10780786 | Del Core | Sep 2020 | B2 |
10960785 | Villanueva et al. | Mar 2021 | B2 |
20020153452 | King et al. | Oct 2002 | A1 |
20030038213 | Yoeli | Feb 2003 | A1 |
20030062443 | Wagner et al. | Apr 2003 | A1 |
20030080242 | Kawai | May 2003 | A1 |
20030085319 | Wagner et al. | May 2003 | A1 |
20030094537 | Austen-Brown | May 2003 | A1 |
20030106959 | Fukuyama | Jun 2003 | A1 |
20040093130 | Osder et al. | May 2004 | A1 |
20040126241 | Zha et al. | Jul 2004 | A1 |
20040141170 | Jamieson et al. | Jul 2004 | A1 |
20040195460 | Sailer | Oct 2004 | A1 |
20040245376 | Muren | Dec 2004 | A1 |
20040261428 | Murry et al. | Dec 2004 | A1 |
20050178879 | Mao | Aug 2005 | A1 |
20050230524 | Ishiba | Oct 2005 | A1 |
20050251328 | Merwe et al. | Nov 2005 | A1 |
20060016930 | Pak | Jan 2006 | A1 |
20060097103 | Atmur | May 2006 | A1 |
20060113426 | Yoeli | Jun 2006 | A1 |
20060226281 | Walton | Oct 2006 | A1 |
20070036657 | Wobben | Feb 2007 | A1 |
20070154314 | Jarrah et al. | Jul 2007 | A1 |
20070170307 | De | Jul 2007 | A1 |
20070221779 | Ikeda | Sep 2007 | A1 |
20080048065 | Kuntz | Feb 2008 | A1 |
20080205416 | Dechiara | Aug 2008 | A1 |
20080283673 | Yoeli | Nov 2008 | A1 |
20090008499 | Shaw | Jan 2009 | A1 |
20090084907 | Yoeli | Apr 2009 | A1 |
20090140102 | Yoeli | Jun 2009 | A1 |
20090159757 | Yoeli | Jun 2009 | A1 |
20090200431 | Konings et al. | Aug 2009 | A1 |
20090224095 | Cox et al. | Sep 2009 | A1 |
20090283629 | Kroetsch et al. | Nov 2009 | A1 |
20100025006 | Zhou | Feb 2010 | A1 |
20100052978 | Tillotson | Mar 2010 | A1 |
20100072325 | Sambell | Mar 2010 | A1 |
20100076625 | Yoeli | Mar 2010 | A1 |
20100100260 | Mcintyre et al. | Apr 2010 | A1 |
20100193644 | Karem | Aug 2010 | A1 |
20100264257 | Brunken | Oct 2010 | A1 |
20100270419 | Yoeli | Oct 2010 | A1 |
20100270435 | Karem | Oct 2010 | A1 |
20110001020 | Forgac | Jan 2011 | A1 |
20110024552 | Patt et al. | Feb 2011 | A1 |
20110042508 | Bevirt | Feb 2011 | A1 |
20110042509 | Bevirt et al. | Feb 2011 | A1 |
20110042510 | Bevirt et al. | Feb 2011 | A1 |
20110049306 | Yoeli | Mar 2011 | A1 |
20110049307 | Yoeli | Mar 2011 | A1 |
20110139923 | Papanikolopoulos et al. | Jun 2011 | A1 |
20110139939 | Martin et al. | Jun 2011 | A1 |
20110147533 | Goossen et al. | Jun 2011 | A1 |
20110180656 | Shue et al. | Jul 2011 | A1 |
20110284201 | Soenmez et al. | Nov 2011 | A1 |
20110303795 | Oliver | Dec 2011 | A1 |
20110315809 | Oliver | Dec 2011 | A1 |
20120025016 | Methven et al. | Feb 2012 | A1 |
20120061526 | Brunken | Mar 2012 | A1 |
20120091257 | Wolff et al. | Apr 2012 | A1 |
20120222441 | Sawada et al. | Sep 2012 | A1 |
20120234518 | Brodie et al. | Sep 2012 | A1 |
20120234968 | Smith | Sep 2012 | A1 |
20120251326 | Schimke et al. | Oct 2012 | A1 |
20130060406 | Christensen et al. | Mar 2013 | A1 |
20130132548 | Cabos | May 2013 | A1 |
20130138413 | Finch et al. | May 2013 | A1 |
20130164578 | Sweet et al. | Jun 2013 | A1 |
20130201316 | Binder et al. | Aug 2013 | A1 |
20130204544 | Thomas | Aug 2013 | A1 |
20140039735 | Major et al. | Feb 2014 | A1 |
20140046510 | Randolph et al. | Feb 2014 | A1 |
20140096501 | Pantalone et al. | Apr 2014 | A1 |
20140138492 | Van Staagen | May 2014 | A1 |
20140174707 | Lombardo et al. | Jun 2014 | A1 |
20140193683 | Mardall et al. | Jul 2014 | A1 |
20140230761 | Pilavdzic | Aug 2014 | A1 |
20140277869 | King et al. | Sep 2014 | A1 |
20140292260 | Dyer et al. | Oct 2014 | A1 |
20140299708 | Green et al. | Oct 2014 | A1 |
20140339372 | Dekel et al. | Nov 2014 | A1 |
20140358333 | White et al. | Dec 2014 | A1 |
20150012154 | Senkel et al. | Jan 2015 | A1 |
20150056058 | Grissom et al. | Feb 2015 | A1 |
20150102659 | Liffring et al. | Apr 2015 | A1 |
20150136897 | Seibel et al. | May 2015 | A1 |
20150147181 | Henze et al. | May 2015 | A1 |
20150232178 | Reiter | Aug 2015 | A1 |
20150266571 | Bevirt et al. | Sep 2015 | A1 |
20150274292 | Delorean | Oct 2015 | A1 |
20150360794 | Certain et al. | Dec 2015 | A1 |
20160026190 | Kowalski et al. | Jan 2016 | A1 |
20160031555 | Bevirt et al. | Feb 2016 | A1 |
20160031556 | Bevirt et al. | Feb 2016 | A1 |
20160059733 | Hettrich et al. | Mar 2016 | A1 |
20160083073 | Beckman | Mar 2016 | A1 |
20160107501 | Johnston | Apr 2016 | A1 |
20160109882 | Ouellette et al. | Apr 2016 | A1 |
20160112151 | Chedas et al. | Apr 2016 | A1 |
20160144957 | Claridge et al. | May 2016 | A1 |
20160167800 | Joubert et al. | Jun 2016 | A1 |
20160204483 | Schilder | Jul 2016 | A1 |
20160204488 | Arai et al. | Jul 2016 | A1 |
20160209290 | Shue | Jul 2016 | A1 |
20160214723 | Fox et al. | Jul 2016 | A1 |
20160236790 | Knapp et al. | Aug 2016 | A1 |
20160265556 | Stadler et al. | Sep 2016 | A1 |
20160272312 | Mallard | Sep 2016 | A1 |
20160294882 | Michaels | Oct 2016 | A1 |
20160304194 | Bevirt et al. | Oct 2016 | A1 |
20160304214 | Himmelmann et al. | Oct 2016 | A1 |
20160325841 | Beckman et al. | Nov 2016 | A1 |
20160342159 | Lanterna et al. | Nov 2016 | A1 |
20170036753 | Shue | Feb 2017 | A1 |
20170066531 | McAdoo | Mar 2017 | A1 |
20170101176 | Alber et al. | Apr 2017 | A1 |
20170104385 | Salamon et al. | Apr 2017 | A1 |
20170131716 | Brekke et al. | May 2017 | A1 |
20170137132 | Wiegers et al. | May 2017 | A1 |
20170217584 | Elfeky et al. | Aug 2017 | A1 |
20170247126 | Blanding et al. | Aug 2017 | A1 |
20170267371 | Frolov et al. | Sep 2017 | A1 |
20170274983 | Beckman et al. | Sep 2017 | A1 |
20170277152 | Liu et al. | Sep 2017 | A1 |
20170297431 | Epstein et al. | Oct 2017 | A1 |
20170331323 | Ehrmantraut | Nov 2017 | A1 |
20180001994 | Morrison | Jan 2018 | A1 |
20180002016 | McCullough et al. | Jan 2018 | A1 |
20180105279 | Tighe et al. | Apr 2018 | A1 |
20180115029 | Ren et al. | Apr 2018 | A1 |
20180134400 | Knapp et al. | May 2018 | A1 |
20180145381 | Dinh et al. | May 2018 | A1 |
20180148182 | Fagundes et al. | May 2018 | A1 |
20180183657 | Beilin et al. | Jun 2018 | A1 |
20180215475 | Hurt et al. | Aug 2018 | A1 |
20180237148 | Hehn et al. | Aug 2018 | A1 |
20180239366 | Cutler et al. | Aug 2018 | A1 |
20180244370 | Lombard | Aug 2018 | A1 |
20180251207 | Kim | Sep 2018 | A1 |
20180251226 | Fenny et al. | Sep 2018 | A1 |
20180287234 | Melack et al. | Oct 2018 | A1 |
20180290736 | Mikic et al. | Oct 2018 | A1 |
20180305030 | Galzin | Oct 2018 | A1 |
20180319491 | Kearney-Fischer | Nov 2018 | A1 |
20180354615 | Groninga et al. | Dec 2018 | A1 |
20180356439 | Luo et al. | Dec 2018 | A1 |
20180358664 | Zhang et al. | Dec 2018 | A1 |
20180362166 | Marr et al. | Dec 2018 | A1 |
20190004542 | Kim | Jan 2019 | A1 |
20190077219 | Frieling et al. | Mar 2019 | A1 |
20190097282 | Melack et al. | Mar 2019 | A1 |
20190144109 | Ewing et al. | May 2019 | A1 |
20190202310 | Gebhart | Jul 2019 | A1 |
20190210740 | Luo | Jul 2019 | A1 |
20190214161 | Chen et al. | Jul 2019 | A1 |
20190315471 | Moore et al. | Oct 2019 | A1 |
20190316849 | Mendez Abrego et al. | Oct 2019 | A1 |
20190341659 | Terwilliger | Nov 2019 | A1 |
20190351740 | Filipkowski et al. | Nov 2019 | A1 |
20200001995 | Yang et al. | Jan 2020 | A1 |
20200140094 | White | May 2020 | A1 |
20200142431 | Mehl et al. | May 2020 | A1 |
20200148347 | Bevirt et al. | May 2020 | A1 |
20200207477 | Ghesquiere et al. | Jul 2020 | A1 |
20200262313 | Muniz et al. | Aug 2020 | A1 |
20200303789 | Macdonald et al. | Sep 2020 | A1 |
20200339010 | Villanueva et al. | Oct 2020 | A1 |
20200350648 | Rheaume | Nov 2020 | A1 |
20200355121 | O'Meallie et al. | Nov 2020 | A1 |
20200376927 | Rajaie et al. | Dec 2020 | A1 |
20200385127 | Devault | Dec 2020 | A1 |
20200391876 | Morrison | Dec 2020 | A1 |
20210170908 | Villanueva et al. | Jun 2021 | A1 |
Number | Date | Country |
---|---|---|
102239321 | Nov 2011 | CN |
102245878 | Nov 2011 | CN |
102407944 | Apr 2012 | CN |
102245878 | Nov 2013 | CN |
102239321 | Jul 2014 | CN |
103363993 | Apr 2016 | CN |
105789729 | Jul 2016 | CN |
107042884 | Aug 2017 | CN |
107709161 | Feb 2018 | CN |
108349585 | Jul 2018 | CN |
102012104783 | Dec 2013 | DE |
0945841 | Sep 1999 | EP |
2423106 | Feb 2012 | EP |
3210885 | Aug 2017 | EP |
3315401 | May 2018 | EP |
3366583 | Aug 2018 | EP |
3401216 | Nov 2018 | EP |
3499634 | Jun 2019 | EP |
3565083 | Nov 2019 | EP |
1271102 | Apr 1972 | GB |
2017154728 | Sep 2017 | JP |
2022530619 | Jun 2022 | JP |
03074924 | Sep 2003 | WO |
03086857 | Oct 2003 | WO |
2016034830 | Mar 2016 | WO |
2016189421 | Dec 2016 | WO |
2017009037 | Jan 2017 | WO |
2017108634 | Jun 2017 | WO |
2019001203 | Jan 2019 | WO |
2019056053 | Mar 2019 | WO |
2020219747 | Oct 2020 | WO |
2020219747 | Feb 2021 | WO |
Entry |
---|
International Search Report and Written Opinion for application No. PCT/US20/29617 dated Jan. 12, 2021. |
European Search Report for Application No. 15765064.9 dated Oct. 16, 2017. |
International Search Report and Written Opinion for Application No. PCT/US10/46500 dated Apr. 13, 2011. |
International Search Report and Written Opinion for Application No. PCT/US15/21344 dated Sep. 11, 2015. |
International Search Report and Written Opinion for Application No. PCT/US15/21350 dated Sep. 15, 2015. |
International Search Report and Written Opinion for application No. PCT/US20/030143 dated Dec. 8, 2020. |
International Search Report and Written Opinion for application No. PCT/US20/052920 dated Dec. 9, 2020. |
International Search Report and Written Opinion for Application No. PCT/US2017/059809 dated Jul. 31, 2018. |
International Search Report and Written Opinion of the ISA for Application No. PCT/US2019/065293 dated Feb. 11, 2020. |
International Search Report for Application No. PCT/US2019/065301, dated Aug. 31, 2020. |
“Ailerons”, NASA student page, 3 pages, Nov. 1, 2018, downloaded from: https://www.grc.nasa.gov/ww/k-12/airplane/alr.hltm. |
“Airfolds Blade Profile”, Mecaflux Heliciel, Propeller & Wing, https://www.heliciel.com/en/aerodynamique-hydrodynamique/profils%20aile%20profil%20pale.htm, 2021. |
“Curtiss-Wright X-19”, Wikipedia, https://en.wikipedia.org/wiki/Curtiss-Wright_X-19, 1963. |
“Inclined Flat Plate”, Aerodynamics of the airplane, Feb. 13, 2016. |
“International Search Report and Written Opinion for PCT Application No. PCT/US2019/039247 dated Sep. 13, 2019”. |
“International Search Report and Written Opinion for PCT Application No. PCT/US2019035236 dated Aug. 20, 2019.” |
“International Search Report and Written Opinion of the ISA dated Dec. 4, 2019 for PCT/US19/51565.” |
“International Search Report and Written Opinion of the ISA dated Mar. 19, 2020 for PCT/US19/67618.” |
“International Search Report and Written Opinion of the ISA, dated Jul. 24, 2019, for application No. PCT/US19/31863.” |
Berger, Tom , “Handling Qualities Requirements and Control Design for High-Speed Rotorcraft”, Special Report FCDD-AMV-20-01, Feb. 2020, Combat Capabilities Devcom Aviation and Missile Center, U.S. Army, 360 pages. |
Bevacqua, Mia , “Studies Show How to Modify HVAC Systems for Improved EV Range”, https://m.futurecar.com/2301/Studies-Show-How-to-Modify-HVAC-Systems-for-Improved-EV-Range, May 27, 2018. |
Carson, Biz , “First Look: Uber Unveils New Design For Uber Eats Delivery Drone”, https:www.forbes.com/sites/bizcarson/2019/10/28/first-look-uber-unveils-new-design-for-uber-eats-delivery-drone/#1703f8d778f2. |
Denham, Jr., James W., et al., “Converging on a Precision Hover Control Strategy for the F35B Stovl Aircraft”, AIAA Guidance, Navigation and Control Conference and Exhibit Aug. 18-21, 2006, Honolulu, Hawaii, Abstract only. |
Dollinger, Daniel , et al., “Control Inceptor Design for Remote Control of a Transition UAV”, AIAA Aviation Forum 17-21 2019, Dallas, Texas, AIAA Aviation 2019 Forum, Paper 10.2514/6.2019-3268, 12 pages. |
Falco, Gianluca , et al., “Loose and Tight GNSS/INS Integrations: Comparison of Performance Assessed in Real Urban Scenarios”, Sensors (Basel) Feb. 2017; 17 (2): 225, https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5335985/. |
Gold, Phillip J., et al., “Design and Pilot Evaluation of the RAH-66 Comanche Selectable Control Modes”, https://ntrs.nasa.gov/search.jsp?, N94-13322, pp. 419-431, Jul. 1, 1993. |
Kang, Youngshin , et al., “Development of flight control system and troubleshooting on flight test of a tilt-rotor unmanned aerial vehicle”, International Journal of Aeronautical and Space Sciences (IJASS), vol. 17 No. 1, 2016, pp. 120-131. |
Kim, Tae , “Reduction of Tonal Propeller Noise by Means of Uneven Blade Spacing”, University of California, Irvine, Thesis, publication date 2016. |
Rabb, Stefan , et al., “Proposal of a Unified Control Strategy for Vertical Take-off and Landing Transition Aircraft Configurations”, AIAA Aviation Forum, Jun. 25-29, 2018, Atlanta, Georgia, 2018 Applied Aerodynamics Conference, 22 pages. |
Radhakrishnan, Anand , et al., “An Experimental Investigation of a Quad Tilt Rotor in Ground Effect”, 21st Applied Aerodynamics Conference, Jun. 23-26, 2003, Orlando, Florida, AIAA 2003-3517, 11 pages. |
Saraf, A. Amit Kumar , et al., “Study of Flow Separation on Airfoil with Bump”, International Journal of Applied Engineering Research ISSN 09773-4562, vol. 13, No. 16 (2018), pp. 128686-12872. |
Sullivan, Brenda M., et al., “A Subject Test of Modulated Blade Spacing for Helicopter Main Rotors”, Presented at the American Helicopter Society 58th Annual Forum, Montreal, Canada, Jun. 11-13, 2002, http://ntrs.nasa.gov/search.isp. |
Thorsen, Adam T., “Development of Evaluation of a Unified Control Architecture for a Compound Rotorcraft in Maneuvering Flight”, AIAA Aviation Forum, AIAA Atmospheric Flight Mechanics Conference, Jun. 13-17, 2016, Washington, D.C., AIAA Paper 10.2514/6.2016-3392, 19 pages. |
Vigano, Luca, et al., “Development of Augmented Control Laws for a Tiltrotor in Low and High Speed Flight Modes”, 43rd European Rotorcraft Forum Proceedings, Sep. 12-15, 2017, Milan, Italy, vol. 1, pp. 438 to 451. |
Walker, Gregory , et al., “F-35B integrated flight-propulsion control development”, AIAA Aviation Forum, 2013 International Powered Lift Conference, Aug. 12-14, 2013, Los Angeles, CA, AIA Paper 10.2514/6.2013-4243, 16 pages. |
Whittle, Richard , “Flying the Osprey is not dangerous, just different: Veteran pilots”, Breaking Defense, Sep. 5, 2012, 9 pages, downloaded from: https://breakingdefense.com/2012/09/flying-the-osprey-is-not-dangerous-just-different-veteran-pilo/. |
Yeh, Y.C. (Bob), “Triple-Triple Redundant 777 Primary Flight Computer”, 1996, IEEE, pp. 293-307 (Year: 1996). |
Young, Larry A., “Conceptual Design Aspects of Three General Sub-Classes of Multi-Rotor Configurations: Distributed, Modular, and Hetergenerous”, NASA Ames Research Center, Moffett Field, CA 94035, Published 2015, Computer Science. |
“U.S. Appl. No. 16/857,003, Non Final Office Action dated Jun. 26, 2020”, 12 pgs. |
“U.S. Appl. No. 16/857,003, Examiner Interview Summary dated Sep. 22, 2020”, 3 pgs. |
“U.S. Appl. No. 16/857,003, Response filed Nov. 3, 2020 to Non Final Office Action dated Jun. 26, 2020”, 12 pgs. |
“U.S. Appl. No. 16/857,003, Notice of Allowance dated Nov. 7, 2020”, 9 pgs. |
“U.S. Appl. No. 16/857,003, Notice of Allowance dated Jan. 26, 2021”, 2 pgs. |
“U.S. Appl. No. 16/857,003, Notice of Allowance dated Feb. 23, 2021”, 2 pgs. |
“International Application Serial No. PCT US2020 029617, Invitation to Pay Additional Fees dated Nov. 3, 2020”, 2 pgs. |
“International Application Serial No. PCT US2020 029617, International Preliminary Report on Patentability dated Nov. 4, 2021”, 9 pgs. |
“U.S. Appl. No. 17/174,596, Non Final Office Action dated May 18, 2022”, 10 pgs. |
“European Application Serial No. 20795592.3, Response filed Jun. 6, 2022 to Communication Pursuant to Rules 161 (2) and 162 EPC dated Dec. 8, 2021”, 10 pgs. |
“Chinese Application Serial No. 202080045865.3, Office Action dated Jul. 11, 2022”, w English Translation, 19 pgs. |
“U.S. Appl. No. 17/174,596, Response filed Aug. 18, 2022 to Non Final Office Action dated May 18, 2022”, 9 pgs. |
Number | Date | Country | |
---|---|---|---|
20210162884 A1 | Jun 2021 | US |
Number | Date | Country | |
---|---|---|---|
62837504 | Apr 2019 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16857003 | Apr 2020 | US |
Child | 17174633 | US |