The subject matter disclosed herein relates generally to controlling travel of a vehicle, and in particular to controlling travel of a vehicle using a trajectory.
Vehicles, such as aircraft, are traditionally controlled by a pilot controlling the basic vehicle state. For example, in existing aircraft the pilot may control flight surfaces of the aircraft along with power output(s). This type of aircraft control may be used with manned aircraft, or autonomous aircraft, such as optionally-piloted vehicles (OPVs) and unmanned aerial vehicles (UAVs). As aircraft become more sophisticated, it is desirable to reduce pilot workload in controlling the aircraft states, and provide a system that allows the pilot to focus on the current mission rather than the basic states of the aircraft.
According to an aspect of the invention, a method of trajectory control for a vehicle includes obtaining an initial trajectory; presenting the initial trajectory as a current trajectory on an I/O device, the current trajectory presented overlaying terrain; initiating travel of the vehicle along the current trajectory; updating the current trajectory and the terrain in real time as the vehicle travels along the current trajectory; determining if change in the current trajectory is required; changing the current trajectory to an altered trajectory in response to determining change in the current trajectory is required; and presenting the altered trajectory on the I/O device, the altered trajectory presented overlaying the terrain.
In addition to one or more of the features described above or below, or as an alternative, further embodiments could include wherein the terrain is presented on the I/O device in a three dimensional representation.
In addition to one or more of the features described above or below, or as an alternative, further embodiments could include wherein determining if change in the current trajectory is required is in response to a sensor sensing an obstacle along the current trajectory.
In addition to one or more of the features described above or below, or as an alternative, further embodiments could include wherein determining if change in the current trajectory is required is in response to the I/O device initiating change in the current trajectory.
In addition to one or more of the features described above or below, or as an alternative, further embodiments could include wherein the terrain is derived from at least one of a stored terrain map and an image from a sensor.
In addition to one or more of the features described above or below, or as an alternative, further embodiments could include wherein obtaining the initial trajectory includes determining the initial trajectory in response to a destination, at least one travel parameter and vehicle constraints.
In addition to one or more of the features described above or below, or as an alternative, further embodiments could include wherein the travel parameter includes an operational mode for the vehicle.
In addition to one or more of the features described above or below, or as an alternative, further embodiments could include wherein the vehicle is an aircraft.
According to an aspect of the invention, a system for trajectory control for a vehicle includes a processing subsystem; and memory having instructions stored thereon that, when executed by the processing subsystem, cause the system to execute operations including: obtaining an initial trajectory; presenting the initial trajectory as a current trajectory on an I/O device, the current trajectory presented overlaying terrain; initiating travel of the vehicle along the current trajectory; updating the current trajectory and the terrain in real time as the vehicle travels along the current trajectory; determining if change in the current trajectory is required; changing the current trajectory to an altered trajectory in response to determining change in the current trajectory is required; and presenting the altered trajectory on the I/O device, the altered trajectory presented overlaying the terrain.
In addition to one or more of the features described above or below, or as an alternative, further embodiments could include wherein determining if change in the current trajectory is required is in response to a sensor sensing an obstacle along the current trajectory.
In addition to one or more of the features described above or below, or as an alternative, further embodiments could include wherein determining if change in the current trajectory is required is in response to the I/O device initiating change in the current trajectory.
In addition to one or more of the features described above or below, or as an alternative, further embodiments could include wherein the terrain is derived from at least one of a stored terrain map and an image from a sensor.
In addition to one or more of the features described above or below, or as an alternative, further embodiments could include wherein obtaining the initial trajectory includes determining the initial trajectory in response to a destination, at least one travel parameter and vehicle constraints.
In addition to one or more of the features described above or below, or as an alternative, further embodiments could include wherein the travel parameter includes an operational mode for the vehicle.
In addition to one or more of the features described above or below, or as an alternative, further embodiments could include wherein the vehicle is an aircraft.
Embodiments provide the technical effect of providing vehicle control using trajectory, and modifying the trajectory in response to user input and/or sensed conditions.
The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
In exemplary embodiments, trajectory control of a vehicle is used to establish and edit a flight path of an aircraft. Trajectory control may be implemented within autonomous aircraft, such as optionally-piloted vehicles (OPVs) and unmanned aerial vehicles (UAVs), and/or may be provided to assist a human-piloted aircraft. Furthermore, trajectory control can be implemented to control a travel path in any type of vehicle, including an aircraft, watercraft, spacecraft, or land vehicle.
Referring now to the drawings,
As illustrated, the autonomous UAV 100 is an aircraft that includes a main rotor system 102, an anti-torque system, for example, a tail rotor system 104, and a control system 106. The main rotor system 102 is attached to an airframe 108 and includes a rotor hub 110 having a plurality of blades 112 that rotate about axis A. Also, the tail rotor system 104 is attached aft of the main rotor system 102 and includes a plurality of blades 114 that rotate about axis B (which is orthogonal to axis A). The main rotor system 102 and the tail rotor system 104 are driven to rotate about their respective axes A, B by one or more turbine engines 116 through gearboxes (not shown). Although a particular configuration of an autonomous UAV 100 is illustrated as a rotary wing UAV and described in the disclosed embodiments, it will be appreciated that other configurations and/or machines including autonomous, semi-autonomous, and human-controlled vehicles that may operate in land or water including fixed-wing aircraft, rotary-wing aircraft, marine vessels (e.g., submarines, ships, etc.), and land vehicles (e.g., trucks, cars, etc.) for docking, parking, or autonomous positioning may also benefit from embodiments disclosed herein.
The control system 106 includes a vehicle computer system 118 (
In an embodiment, the sensor 124 may be one or more of: a LIDAR scanner, a video camera, a multi-spectral camera, a stereo camera system, a structure light-based 3D/depth sensor, a time-of-flight camera, a LADAR scanner, a RADAR scanner, a phased array sensor, or the like in order to capture sensor data within a field of view to assist in vehicle navigation. Additionally, the autonomous UAV 100 may include a navigation system 134, such as, for example, an inertial measurement unit (IMU) that may be used to acquire positional data related to a current rotation and acceleration of the autonomous UAV 100 in order to determine a geographic location of autonomous UAV 100, including a change in position of the autonomous UAV 100. The navigation system 134 can also or alternatively include a global positioning system (GPS) or the like to enhance positional awareness of the autonomous UAV 100. The navigation system 134 in combination with the sensor data may be used to alter a trajectory of the autonomous UAV 100. Sensor data from the sensing system 120 may also be relayed to other vehicles or control stations (not depicted) via a communication interface 150.
A trajectory controller 220 manages the aircraft trajectory, as described herein. Trajectory controller 220 may be implemented by processing subsystem 204, or by a separate, processor-based controller executing computer code stored in memory 206. The current trajectory 230 is generated by trajectory controller 220 and stored in the memory 206.
The processing subsystem 204 may include any number and type of processors, including a general purpose processor, a digital signal processor, a microcontroller, an application specific integrated circuit, a field programmable gate array, or the like. In an exemplary embodiment, the processing subsystem 204 includes a plurality of processing resources 205, which may be separate cores, processing circuits, and/or processors supporting parallel computing. Although depicted as singular blocks, the processing subsystem 204 and memory 206 can be distributed between multiple processing circuits and memory subsystems. In an embodiment, the processing subsystem 204 performs additional processing tasks for the system 200.
The system 200 may include a database 212 to store a variety of data, such as the vehicle constraints 214 and terrain maps 216, and the like. The vehicle constraints 214 may define a variety of limits associated with flight dynamics and limits of maneuverability of the autonomous UAV 100 of
The system 200 may provide one or more controls, such as vehicle controls 208. Trajectory controller 220 can interface with the navigation system 134 and the I/O devices 210 to provide higher-level commands to the vehicle controls 208 to adjust engine controls, rotor controls, and the like. The trajectory controller 220 provides commands to the vehicle controls 208 to maintain the aircraft on the current trajectory. Vehicle controls 208 control flight surfaces and power of the aircraft 100 to stay on the current trajectory.
One or more input/output (I/O) devices 210 may be used in forming an initial trajectory and altering the trajectory during flight. The I/O devices 210 may include a display device or screen, audio speakers, a graphical user interface (GUI), pointing devices, control stick(s), etc. Creation of an initial trajectory and altering the current trajectory are described in further detail herein with reference to
It is to be appreciated that the system 200 is illustrative. In some embodiments, additional components or entities not shown in
At block 312, the initial trajectory is presented on I/O device 210.
At block 314, travel of the vehicle commences. It is understood that the vehicle may initiate travel prior to presenting the trajectory at 312. As noted above, the trajectory controller 220 interfaces with the vehicle controls 208 and navigation system 134 to maintain the aircraft on the current trajectory. The trajectory is used as the travel path for the vehicle. The vehicle computer system 200 maintains the vehicle on the trajectory automatically, without the need for the operator to control status of the vehicle. Prior to any alterations in the trajectory, the initial trajectory is used as the current trajectory.
At block 316, the presentation of the trajectory is updated in real time as the vehicle travels. This entails changing the terrain 412 as the vehicle moves. The operator may also zoom in and out, to see the terrain and current trajectory at different scales.
As the vehicle is traveling, the system periodically determines if the trajectory needs to be changed. At block 318, it is determined if the sensors 124 have initiated a trajectory change. As noted above, the current trajectory may be derived based on terrain maps 216. The terrain maps 216 may not be 100% accurate (e.g., a cell tower has been erected since the terrain map was updated). Sensor(s) 124 are used to detect obstacles along the current trajectory and initiate a trajectory change if needed. At block 318, if a trajectory change is needed due to a sensed obstacle, the flow proceeds to block 322. At block 322, trajectory controller 220 alters the current trajectory to an altered trajectory based on the information from sensor(s) 124. The altered trajectory will meet the original destination, travel parameters, and any vehicle constraints 214.
If sensor(s) 124 do not initiate a change in the current trajectory at 318, flow proceeds to 320 where the system determines if the I/O devices 210 have initiated a change in the trajectory. An operator may use I/O devices 210 to manually alter the current trajectory. The operator may wish to alter the current trajectory, the destination, or some other travel parameter (e.g., altitude). In one embodiment, an operator may use a pointing device to drag a section of the current trajectory to a new location. Other operator actions may be used to alter the current trajectory. If an I/O device 210 has initiated a trajectory change, flow proceeds to block 322 where the trajectory is altered by trajectory controller 220. At block 322, trajectory controller 220 alters the current trajectory to an altered trajectory based on the input from the I/O device 210. The altered trajectory will meet the destination, travel parameters, and any vehicle constraints 214. Flow proceeds to block 316, where the altered trajectory is now used as the current trajectory in presentation in real time. The altered trajectory is now used as the flight path for the aircraft 100.
While the invention has been described in detail in connection with only a limited number of embodiments, it should be readily understood that the invention is not limited to such disclosed embodiments. Rather, the invention can be modified to incorporate any number of variations, alterations, substitutions or equivalent arrangements not heretofore described, but which are commensurate with the spirit and scope of the invention. Additionally, while various embodiments of the invention have been described, it is to be understood that aspects of the invention may include only some of the described embodiments. Accordingly, the invention is not to be seen as limited by the foregoing description, but is only limited by the scope of the appended claims.
This application is a National Stage application of PCT/US2016/021808, filed Mar. 10, 2016, which claims the benefit of U.S. Provisional Patent Application No. 62/134,322, filed Mar. 17, 2015, both of which are incorporated by reference in their entirety herein.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2016/021808 | 3/10/2016 | WO | 00 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2016/149039 | 9/22/2016 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
5706011 | Huss et al. | Jan 1998 | A |
6334344 | Bonhoure et al. | Jan 2002 | B1 |
6643580 | Naimer | Nov 2003 | B1 |
6985091 | Price | Jan 2006 | B2 |
7209070 | Gilliland | Apr 2007 | B2 |
7375678 | Feyereisen | May 2008 | B2 |
7483790 | Brent | Jan 2009 | B2 |
7487039 | Rumbo | Feb 2009 | B2 |
7609200 | Woodell | Oct 2009 | B1 |
7737878 | Van Tooren et al. | Jun 2010 | B2 |
7852236 | Feyereisen | Dec 2010 | B2 |
7917289 | Feyereisen | Mar 2011 | B2 |
7965202 | Chiew | Jun 2011 | B1 |
8027783 | Closse | Sep 2011 | B2 |
8049644 | Oehlert | Nov 2011 | B1 |
8095249 | Little | Jan 2012 | B2 |
8200433 | Siniff | Jun 2012 | B1 |
8229662 | Subelet | Jul 2012 | B2 |
8232910 | Burton | Jul 2012 | B1 |
8279108 | Nouvel | Oct 2012 | B2 |
8285427 | Rogers | Oct 2012 | B2 |
8339284 | He | Dec 2012 | B2 |
8457889 | Feyereisen | Jun 2013 | B2 |
8576094 | Suddreth | Nov 2013 | B2 |
8654149 | He | Feb 2014 | B2 |
9340282 | Case | May 2016 | B2 |
9390559 | Feyereisen | Jul 2016 | B2 |
9489758 | Ott | Nov 2016 | B2 |
9495878 | Kozlow | Nov 2016 | B2 |
9733103 | He | Aug 2017 | B2 |
9762895 | Henry | Sep 2017 | B1 |
9824598 | Onomura | Nov 2017 | B2 |
9892489 | Roggendorf | Feb 2018 | B1 |
9898933 | Pire | Feb 2018 | B2 |
10228691 | Pounds | Mar 2019 | B1 |
20010023390 | Gia | Sep 2001 | A1 |
20020143439 | Morizet | Oct 2002 | A1 |
20030107499 | Lepere | Jun 2003 | A1 |
20030122701 | Tran | Jul 2003 | A1 |
20030156046 | Dwyer | Aug 2003 | A1 |
20030195672 | He | Oct 2003 | A1 |
20030222887 | Wilkins, Jr. | Dec 2003 | A1 |
20040160341 | Feyereisen | Aug 2004 | A1 |
20040178943 | Niv | Sep 2004 | A1 |
20040217883 | Judge | Nov 2004 | A1 |
20040239529 | Tran | Dec 2004 | A1 |
20050049763 | Walsdorf | Mar 2005 | A1 |
20050099433 | Berson | May 2005 | A1 |
20050182528 | Dwyer | Aug 2005 | A1 |
20050261808 | Artini | Nov 2005 | A1 |
20050273248 | Artini | Dec 2005 | A1 |
20050273249 | Artini | Dec 2005 | A1 |
20060158350 | Glover | Jul 2006 | A1 |
20060227012 | He | Oct 2006 | A1 |
20060235581 | Petillon | Oct 2006 | A1 |
20070005199 | He | Jan 2007 | A1 |
20070055418 | Pire | Mar 2007 | A1 |
20070067093 | Pepitone | Mar 2007 | A1 |
20070085705 | He | Apr 2007 | A1 |
20070171094 | Alter | Jul 2007 | A1 |
20070265776 | Meunier | Nov 2007 | A1 |
20080051947 | Kemp | Feb 2008 | A1 |
20080208400 | Bouchet | Aug 2008 | A1 |
20080243383 | Lin | Oct 2008 | A1 |
20090177400 | Silly | Jul 2009 | A1 |
20100017113 | Artini | Jan 2010 | A1 |
20100026525 | Feyereisen | Feb 2010 | A1 |
20100030405 | He | Feb 2010 | A1 |
20100042273 | Meunier | Feb 2010 | A1 |
20100052949 | Suddreth | Mar 2010 | A1 |
20100060511 | Nouvel | Mar 2010 | A1 |
20100066566 | Reusser et al. | Mar 2010 | A1 |
20100240988 | Varga | Sep 2010 | A1 |
20100250022 | Hines et al. | Sep 2010 | A1 |
20110022291 | He | Jan 2011 | A1 |
20110210871 | Flotte | Sep 2011 | A1 |
20110227944 | Feyereisen | Sep 2011 | A1 |
20110288695 | Gariepy et al. | Nov 2011 | A1 |
20120026190 | He | Feb 2012 | A1 |
20120075168 | Osterhout | Mar 2012 | A1 |
20130002454 | Burns | Jan 2013 | A1 |
20130162632 | Varga | Jun 2013 | A1 |
20130270394 | Downs et al. | Oct 2013 | A1 |
20130338858 | Cherepinsky | Dec 2013 | A1 |
20140331161 | Venkataswamy | Nov 2014 | A1 |
20150310746 | Albert | Oct 2015 | A1 |
20150323932 | Paduano | Nov 2015 | A1 |
20160078769 | Coulmeau | Mar 2016 | A1 |
20160140850 | Feyereisen | May 2016 | A1 |
20160232793 | Morishita | Aug 2016 | A1 |
20180099748 | Lesperance | Apr 2018 | A1 |
20180350258 | He | Dec 2018 | A1 |
20190002122 | Ding | Jan 2019 | A1 |
20190079509 | Bosworth | Mar 2019 | A1 |
Number | Date | Country |
---|---|---|
2595136 | May 2013 | EP |
2015031358 | Mar 2015 | WO |
Entry |
---|
International Search Report and Written Opinion; International Application No. PCT/US2016/021808; International Filing Date: Mar. 10, 2016; dated Jun. 9, 2016; 14 Pages. |
European Search Report for Application No. 16765465.6; dated Oct. 26, 2018; 8 pages. |
Number | Date | Country | |
---|---|---|---|
20180052472 A1 | Feb 2018 | US |
Number | Date | Country | |
---|---|---|---|
62134322 | Mar 2015 | US |