U.S. patent application number 16/378250 was filed with the patent office on 2019-08-01 for systems and methods for configurable user interfaces.
This patent application is currently assigned to Insitu, Inc.. The applicant listed for this patent is Insitu, Inc.. Invention is credited to Darcy Lynn Davidson, JR., Andrew Royds Hayes.
Application Number | 20190233088 16/378250 |
Document ID | / |
Family ID | 56093595 |
Filed Date | 2019-08-01 |
![](/patent/app/20190233088/US20190233088A1-20190801-D00000.png)
![](/patent/app/20190233088/US20190233088A1-20190801-D00001.png)
![](/patent/app/20190233088/US20190233088A1-20190801-D00002.png)
![](/patent/app/20190233088/US20190233088A1-20190801-D00003.png)
![](/patent/app/20190233088/US20190233088A1-20190801-D00004.png)
![](/patent/app/20190233088/US20190233088A1-20190801-D00005.png)
![](/patent/app/20190233088/US20190233088A1-20190801-D00006.png)
![](/patent/app/20190233088/US20190233088A1-20190801-D00007.png)
![](/patent/app/20190233088/US20190233088A1-20190801-D00008.png)
![](/patent/app/20190233088/US20190233088A1-20190801-D00009.png)
![](/patent/app/20190233088/US20190233088A1-20190801-D00010.png)
United States Patent
Application |
20190233088 |
Kind Code |
A1 |
Hayes; Andrew Royds ; et
al. |
August 1, 2019 |
SYSTEMS AND METHODS FOR CONFIGURABLE USER INTERFACES
Abstract
A user interface presented to an operator of an unmanned aerial
vehicle (UAV) may be presented to facilitate the ease of operation
of the UAV. The information displayed in the user interface may be
customized by the operator to display selected data. The display
configuration data may be saved and imported into other systems for
future use. Various entities related to one or more UAVs may be
presented in a hierarchical tree structure illustrating the
relationship between the entities. Electronic checklists may be
presented to a user to facilitate addressing common and emergency
situations.
Inventors: |
Hayes; Andrew Royds; (White
Salmon, WA) ; Davidson, JR.; Darcy Lynn; (Dallesport,
WA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Insitu, Inc. |
Bingen |
WA |
US |
|
|
Assignee: |
Insitu, Inc.
Bingen
WA
|
Family ID: |
56093595 |
Appl. No.: |
16/378250 |
Filed: |
April 8, 2019 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
15620646 |
Jun 12, 2017 |
10252788 |
|
|
16378250 |
|
|
|
|
14453364 |
Aug 6, 2014 |
9676472 |
|
|
15620646 |
|
|
|
|
61872448 |
Aug 30, 2013 |
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
B64C 19/00 20130101;
G05D 1/0016 20130101; B64C 39/00 20130101 |
International
Class: |
B64C 19/00 20060101
B64C019/00; B64C 39/00 20060101 B64C039/00; G05D 1/00 20060101
G05D001/00 |
Claims
1. A method of controlling an unmanned aerial vehicle (UAV),
comprising: presenting a first user interface to a user, the first
user interface comprising: a first section having a first plurality
of selectable fields associated with UAV flight data, the first
plurality of selectable fields related in a first manner; a second
section having a second plurality of selectable fields associated
with the UAV flight data, the second plurality of selectable fields
related in a second manner; accepting first user selected fields of
the first plurality of selectable fields, and second user selected
fields of the second plurality of selectable fields; accepting a
user command to move at least one of the first section and the
second section within the user interface to a user determined
location; accepting a user command in the user interface to save
the first user selected fields of the first plurality of selectable
fields, the second user selected fields, and the user determined
location; in response to the accepted user command, accepting a
name for the user interface in a text box presented in the first
user interface and saving user interface attributes including the
first user selected fields of the first plurality of selectable
fields, the second user selected fields, and the user determined
location in association with the name for the user interface;
presenting a second user interface to the user, the second user
interface comprising: the first section having the user selected
first plurality of selectable fields associated with UAV flight
data replaced with UAV flight data associated with each user
selected field; the second section having the user selected second
plurality of selectable fields associated with UAV flight data
replaced with UAV flight data associated with each user selected
field; wherein the at least one of the first section and the second
section is disposed at the user determined location; controlling
the UAV at least in part using the second user interface.
2. The method of claim 1, wherein the user interface attributes
further comprise display color and text characteristics.
3. The method of claim 2, wherein the user interface attributes are
saved in a configuration data file.
4. The method of claim 3, wherein: the first user interface
comprises an export control; and the method further comprises:
accepting a user selection of the export control; and in response
to the user selection of the export control, exporting the user
interface attributes to for use by another user interface.
5. The method of claim 3, wherein: the first user interface
comprises an import control; and the method further comprises:
accepting a user selection of the import control; and in response
to the user selection of the import control, importing other user
interface attributes from another user interface.
6. The method of claim 3, wherein the first plurality of selectable
fields are related to UAV autopilot set points.
7. The method of claim 3, wherein the second plurality of
selectable fields are related an approach of an autopilot of the
UAV.
8. An apparatus for controlling an unmanned aerial vehicle (UAV),
comprising: means for presenting a first user interface to a user,
the first user interface comprising: a first section having a first
plurality of selectable fields associated with UAV flight data, the
first plurality of selectable fields related in a first manner; a
second section having a second plurality of selectable fields
associated with the UAV flight data, the second plurality of
selectable fields related in a second manner; means for accepting
first user selected fields of the first plurality of selectable
fields, and second user selected fields of the second plurality of
selectable fields; means for accepting a user command to move at
least one of the first section and the second section within the
user interface to a user determined location; means for accepting a
user command in the user interface to save the first user selected
fields of the first plurality of selectable fields, the second user
selected fields, and the user determined location; means for, in
response to the accepted user command, accepting a name for the
user interface in a text box presented in the first user interface
and saving user interface attributes including the first user
selected fields of the first plurality of selectable fields, the
second user selected fields, and the user determined location in
association with the name for the user interface; means for
presenting a second user interface to the user, the second user
interface comprising: the first section having the user selected
first plurality of selectable fields associated with UAV flight
data replaced with UAV flight data associated with each user
selected field; the second section having the user selected second
plurality of selectable fields associated with UAV flight data
replaced with UAV flight data associated with each user selected
field; wherein the at least one of the first section and the second
section is disposed at the user determined location; means for
controlling the UAV at least in part using the second user
interface.
9. The apparatus of claim 8, wherein the user interface attributes
further comprise display color and text characteristics.
10. The apparatus of claim 9, wherein the user interface attributes
are saved in a configuration data file.
11. The apparatus of claim 10, wherein: the first user interface
comprises an export control; and the apparatus further comprises:
means for accepting a user selection of the export control; and
means for, in response to the user selection of the export control,
exporting the user interface attributes to for use by another user
interface.
12. The apparatus of claim 10, wherein: the first user interface
comprises an import control; and the apparatus further comprises:
means for accepting a user selection of the import control; and
means for in response to the user selection of the import control,
importing other user interface attributes from another user
interface.
13. The apparatus of claim 10, wherein the first plurality of
selectable fields are related to UAV autopilot set points.
14. The apparatus of claim 10, wherein the second plurality of
selectable fields are related an approach of an autopilot of the
UAV.
15. An apparatus for controlling an unmanned aerial vehicle (UAV),
comprising: a processor; a memory, communicatively coupled to the
processor, the memory comprising instructions comprising
instructions for: presenting a first user interface to a user, the
first user interface comprising: a first section having a first
plurality of selectable fields associated with UAV flight data, the
first plurality of selectable fields related in a first manner; a
second section having a second plurality of selectable fields
associated with the UAV flight data, the second plurality of
selectable fields related in a second manner; accepting first user
selected fields of the first plurality of selectable fields, and
second user selected fields of the second plurality of selectable
fields; accepting a user command to move at least one of the first
section and the second section within the user interface to a user
determined location; accepting a user command in the user interface
to save the first user selected fields of the first plurality of
selectable fields, the second user selected fields, and the user
determined location; in response to the accepted user command,
accepting a name for the user interface in a text box presented in
the first user interface and saving user interface attributes
including the first user selected fields of the first plurality of
selectable fields, the second user selected fields, and the user
determined location in association with the name for the user
interface; presenting a second user interface to the user, the
second user interface comprising: the first section having the user
selected first plurality of selectable fields associated with UAV
flight data replaced with UAV flight data associated with each user
selected field; the second section having the user selected second
plurality of selectable fields associated with UAV flight data
replaced with UAV flight data associated with each user selected
field; wherein the at least one of the first section and the second
section is disposed at the user determined location; controlling
the UAV at least in part using the second user interface.
16. The apparatus of claim 16, wherein the user interface
attributes further comprise display color and text
characteristics.
17. The apparatus of claim 16, wherein the user interface
attributes are saved in a configuration data file.
18. The apparatus of claim 17, wherein: the first user interface
comprises an export control; and the instructions further comprise
instructions for: accepting a user selection of the export control;
and in response to the user selection of the export control,
exporting the user interface attributes to for use by another user
interface.
19. The apparatus of claim 17, wherein: the first user interface
comprises an import control; and the instructions further comprise
instructions for: accepting a user selection of the import control;
and in response to the user selection of the import control,
importing other user interface attributes from another user
interface.
20. The apparatus of claim 17, wherein the first plurality of
selectable fields are related to UAV autopilot set points, and the
second plurality of selectable fields are related an approach of an
autopilot of the UAV.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. patent
application Ser. No. 15/620,646, entitled "SYSTEMS AND METHODS FOR
CONFIGURABLE USER INTERFACES," by Royds Hayes, et al, filed Jun.
12, 2017, which application is a continuation of U.S. patent
application Ser. No. 14/453,364, entitled "SYSTEMS AND METHODS FOR
CONFIGURABLE USER INTERFACES," by Royds Hayes, et al, filed Aug. 6,
2014, now issued as U.S. Pat. No. 9,676,472, which application
claims priority to U.S. Provisional Patent Application No.
61/872,448, entitled "SYSTEMS AND METHODS FOR CONFIGURABLE USER
INTERFACES," by Royds Hayes, et al, filed Aug. 30, 2013, both of
which applications are hereby incorporated by reference.
BACKGROUND
[0002] Unmanned aerial vehicles (UAVs) are aircraft with no human
pilot onboard that are often operated with assistance from
ground-based personnel and/or systems. The use of UAVs has been
increasing as the need for such aircraft grows and advances in UAV
technology make UAVs more capable and less expensive. Applications
of UAVs include use both military applications and civilian
applications such as policing, firefighting, and surveillance. UAVs
are typically operated by ground-based personnel using systems that
include a software interface allowing operators to control and
monitor one or more UAVs. Operating a UAV may require an operator
to consider many factors that may change at any time, including
constantly changing environmental and operational conditions.
Therefore, it is essential that the user interface to a system for
control and monitoring of a UAV be as user-friendly and accessible
as possible.
SUMMARY
[0003] Illustrative examples of the subject matter set forth herein
include, without limitation, a method, device, and
computer-readable storage medium. In one aspect, user interfaces
presented to an operator of a UAV may be presented to facilitate
the ease of operation of the UAV by using window and panel
attributes that increase ease of use, including window docking,
tabbing, and customized user interface display configurations.
Display configuration data may be saved for future use. Such
display configuration data may also be imported into other systems
or exported for use elsewhere. A hierarchical tree structure may be
presented to an operator clearly showing the various entities
related to one or more UAVs and illustrating the relationship
between the entities. Electronic checklists may be presented to a
user to facilitate addressing common and emergency situations. Upon
selection of elements within a checklist, more detailed information
may be presented to an operator. Controls and data inputs may also
be presented to an operator so that the operator can obtain refined
instructions based on input data and perform functions specific to
the selected step.
[0004] The features, functions, and advantages that have been
discussed can be achieved independently in various implementations
or may be combined in yet other implementations further details of
which can be seen with reference to the following description and
drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
[0005] Examples of techniques in accordance with the present
disclosure are described in detail below with reference to the
following illustrations:
[0006] FIG. 1 depicts a flow diagram of an aircraft production and
service methodology.
[0007] FIG. 2 depicts a block diagram of an aircraft.
[0008] FIG. 3 depicts a block diagram illustrating systems or
operating environments for controlling unmanned aerial vehicles
(UAVs).
[0009] FIG. 4 depicts an illustration of an example user interface
according to one example of the disclosed subject matter.
[0010] FIG. 5 depicts an illustration of another example user
interface according to one example of the disclosed subject
matter.
[0011] FIG. 6 depicts an illustration of an example tree structure
according to one example of the disclosed subject matter.
[0012] FIG. 7 depicts an illustration of another example user
interface according to one example of the disclosed subject
matter.
[0013] FIG. 8 depicts an illustration of another example user
interface according to one example of the disclosed subject
matter.
[0014] FIG. 9 depicts an illustration of another example user
interface according to one example of the disclosed subject
matter.
[0015] FIG. 10 depicts an illustration of another example user
interface according to one example of the disclosed subject
matter.
[0016] FIG. 11 depicts an illustration of an example computing
environment in which operations according to the disclosed subject
matter may be performed.
DETAILED DESCRIPTION
[0017] Examples in this disclosure may be described in the context
of aircraft manufacturing and service method 100 as shown in FIG. 1
and an aircraft 200 as shown in FIG. 2. During pre-production,
aircraft manufacturing and service method 100 may include
specification and design 102 of aircraft 200 and material
procurement 104.
[0018] During production, component and subassembly manufacturing
106 and system integration 108 of aircraft 200 may take place.
Thereafter, aircraft 200 may go through certification and delivery
110 in order to be placed in service 112. While in service by a
customer, aircraft 200 may be scheduled for routine maintenance and
service 114, which may also include modification, reconfiguration,
refurbishment, and so on.
[0019] Each of the processes of aircraft manufacturing and service
method 100 may be performed or carried out by a system integrator,
a third party, and/or an operator (e.g., a customer). For the
purposes of this description, a system integrator may include,
without limitation, any number of aircraft manufacturers and
major-system subcontractors. A third party may include, for example
and without limitation, any number of venders, subcontractors, and
suppliers. An operator may be an airline, leasing company, military
entity, service organization, and so on.
[0020] As shown in FIG. 2, aircraft 200 produced by aircraft
manufacturing and service method 100 may include airframe 202 with
a plurality of systems 204 and interior 206. Examples of systems
204 include one or more of propulsion system 208, electrical system
210, hydraulic system 212, and environmental system 214. Any number
of other systems may be included in this example. Although an
aerospace example is shown, the principles of the disclosure may be
applied to other industries, such as the automotive industry.
[0021] Apparatus, systems, and methods disclosed herein may be
employed during any one or more of the stages of aircraft
manufacturing and service method 100. For example, without
limitation, components or subassemblies corresponding to component
and subassembly manufacturing 106 may be fabricated or manufactured
in a manner similar to components or subassemblies produced while
aircraft 200 is in service.
[0022] FIG. 3 illustrates systems or operating environments,
denoted generally at 300, that provide flight plans for UAVs while
routing around obstacles having spatial and temporal dimensions.
These systems 300 may include one or more flight planning and
control systems 302. FIG. 3 illustrates several examples of
platforms that may host flight planning and control system 302.
These examples may include one or more server-based systems 304,
one or more portable computing systems 306 (whether characterized
as a laptop, notebook, tablet, or other type of mobile computing
system), and/or one or more desktop computing systems 308. Flight
planning and control system 302 may be a ground-based system that
performs pre-flight planning and route analysis for a UAV or a
vehicle-based system that is housed within a UAV.
[0023] Implementations of this description may include other types
of platforms as well, with FIG. 3 providing some non-limiting
examples. For example, the description herein contemplates other
platforms for implementing the flight planning systems, including,
but not limited to, wireless personal digital assistants,
smartphones, or the like. The graphical elements used in FIG. 3 to
depict various components are chosen only to facilitate
illustration and not to limit possible implementations of the
description herein.
[0024] Turning to flight planning and control system 302 in more
detail, it may include one or more processors 310 that each may
have a particular type or architecture that may be chosen based on
an intended implementation. Processors 310 may couple to one or
more bus systems 312 that are chosen for compatibility with
processors 310.
[0025] The flight planning and control systems 302 may include one
or more instances of computer-readable storage media 314 that
couple to the bus systems 312. Bus systems 312 may enable
processors 310 to read code and/or data to/from the
computer-readable storage media 314. Storage media 314 may
represent storage elements implemented using any suitable
technology, including, but not limited to, semiconductors, magnetic
materials, optics, or the like. Storage media 314 may include
memory components, whether classified as RAM, ROM, flash, or other
types, and may also represent hard disk drives.
[0026] Storage media 314 may include one or more modules 316 of
instructions that, when loaded into one or more of processors 310
and executed, cause flight planning and control system 302 to
provide flight plan computation services for one or more UAVs 318.
These modules may implement the various algorithms and models
described and illustrated herein.
[0027] UAVs 318 may be of any size and/or type and may be designed
for different applications. In different scenarios, the UAVs may
range from relatively small drones to relatively large transport
aircraft. Accordingly, the graphical illustration of UAV 318 as
shown in FIG. 3 is representative only, and is not drawn to
scale.
[0028] Flight plan computation services provided by one or more of
modules 316 may generate respective flight plan solutions 320 for
UAV 318 based on inputs 322, with operator 324 and/or one or more
databases 326 providing inputs 322. In this disclosure, flight
planning computation services include flight control and monitoring
and any other services that may be provided to allow operator 324
to control, monitor, and otherwise operate a UAV such as UAV
318.
[0029] Assuming that the flight plan services 316 define one or
more solutions 320, flight planning and control system 302 may load
the solutions into UAV 318, as represented by the arrow connecting
block 320 and UAV 318 in FIG. 3. In addition, flight planning and
control system 302 may also provide solutions 320 to operator 324
and/or databases 326, as denoted by the arrow 320A. Flight plan
solutions 320 may include any control commands, requests for data,
instructions, and any other data or commands that operator 324 may
convey or otherwise transmit to UAV 318 via flight planning and
control system 302.
[0030] Flight planning and control system 302 may provide a user
interface for operator 324 to use in control and monitoring of UAV
318. In an example, such a user interface may be customizable by
individual users so that each user may develop an interface that
works best for that respective user. FIG. 4 illustrates user
interface 400 that may allow a UAV operator to select fields and
other data to be presented in a user interface that the operator
may use to control and monitor a UAV. User interface 400 may
include one or more sections that each list display elements that
are related in some manner. For example, section 410 of user
interface 400 lists display elements related to autopilot set
points, while section 420 of user interface 400 lists display
elements related to autopilot approach. Any number and type of
sections related to any attributes, characteristics, or operational
areas may be displayed on user interface 400, and each such
sections may present any number and type of display elements. All
such examples are contemplated as within the scope of the present
disclosure.
[0031] Each of sections 410 and 420 may allow a user to select
particular elements to be displayed in a user interface used to
control and monitor a UAV. In one example, all possible display
elements may be listed for a particular section, and check boxes or
other user-selectable controls may be presented allowing the
operator to select those display elements that the user would like
to have presented when operating a UAV.
[0032] Once a selection of display elements is made, an operator
may save the display configuration data for future use. Name text
box 430 may provide the operator with an interface in which a name
for a particular display configuration may be entered. By allowing
the naming and saving of multiple display configurations, an
operator may use the display configuration that is most suitable
for the UAV tasks at hand. Upon completing a selection of display
elements and entering a name for the display configuration, an
operator may save the display configuration data by selecting save
button 440. Note that an operator may also select or otherwise
indicate other types of display preferences. For example, a user
may move sections 410 and 420 about within user interface 400, and
the position and/or location of sections 410 and 420 may be saved
as display configuration data. Any other attributes may be selected
or configured by an operator and saved in a display configuration
data file, including color, text characteristics (e.g., color,
font, size, etc.), background, etc. All such configurations are
contemplated as within the scope of the present disclosure.
[0033] An operator may also import settings from another display
configuration by selecting import button 450, which may allow the
operator to select and load a display configuration data file which
will populate the display element selections in each of sections
410 and 420, and any other sections that may be in use. After the
operator has made any changes, if desired, the modified display
configuration may be saved as well. The operator may also generate
a display configuration data file including the currently selected
display elements by selecting export button 460. Such a file may be
used with another flight planning and control system or other user
interface.
[0034] FIG. 5 illustrates example user interface 500 that may be
used in controlling, monitoring, and otherwise operating a UAV.
User interface 500 displayed according to a display configuration
having the name indicated in name text box 530 and that may have
been created as described above in regard to FIG. 4. User interface
500 shows section 510 displaying elements related to autopilot set
points and section 520 displaying elements related to autopilot
approach. Any number and type of sections related to any
attributes, characteristics, or operational areas may be displayed
on user interface 500, and each such sections may present any
number and type of display elements. All such examples are
contemplated as within the scope of the present disclosure.
[0035] User interface 500 may allow an operator to import settings
from another display configuration by selecting import button 550,
which may allow the operator to select and load a display
configuration data file which will populate sections 510 and 520,
and any other sections that may be in use, with display elements
according to the selected display configuration data file. The
operator may also export the current display configuration being
used by generating a display configuration data file including
indicators of the currently displayed elements by selecting export
button 560. Such a file may be used with another flight planning
and control system or other user interface.
[0036] To further facilitate ease of operation of a UAV, in an
example the relationships between various components of a UAV and
the systems and devices with which it interacts may be presented as
a hierarchical tree structure. UAV operation involves many
different entities, which may include one or more UAVs, each
component onboard each UAV, ground-based systems that interact,
directly or indirectly, in some manner with one or more UAVs, and
user operated systems that allow operators to interact with a UAV.
FIG. 6 illustrates structure 600 that shows the relationship of the
various entities involved in UAV operation in a manner that is easy
to quickly comprehend. Each entity may be represented by a unique
identifier. Icons and other non-text visual representations of each
entity may also accompany the entity descriptions in structure 600
to further aid in the ease of identification of such entities. For
example, a particular icon may be presented that represents a type
of entity (e.g., an icon for a workstation, a UAV, a ground data
terminal, a ground antenna, a recovery system, a payload interface
module, etc.) may be presented proximate to the unique identifier
for that entity. Each of the elements shown in structure 600 may
also be user selectable. Upon selection of an element, a window or
other interface may be generated showing detailed information about
the selected element and in some examples providing one or more
controls that may allow an operator to control or otherwise affect
the selected element.
[0037] The tree structure allows an operator to easily view the
relationship of each entity. For example, due to the visual
representation of the relationship in structure 600, an operator
can readily understand that camera entity 611 is a camera on or
under the control of vehicle 610. Similarly, an operator will be
able to easily determine from structure 500 that antenna 621 is
controlled or operated by terminal 620. In one example, the
hierarchy displayed in structure 600 may conform to the NATO
Standardization Agreement 4586 (STANAG 4586) hierarchy
[0038] In some examples of the present disclosure, the user
interface presented to an operator may be further enhanced to
facilitate the operation of a UAV. In one example, the user
interface presented to an operator may integrate drag and drop
functionality, window and panel movement and resizing, etc.
Portions of user interfaces, such as windows or panels, may be
dockable (e.g., will "stick" to one or more sides of a displayed
interface). Windows or panels of a user interface may also be
organized as tabs, where the user may select a tab to present the
selected window or panel while still having access to other tabs
associated with other, possibly currently hidden, windows or
panels. This will allow several user interface portions to be
easily accessible within a single interface. For example, operators
may typically work with mapping interfaces but may need to operate
multiple UAVs at once, and therefore may be able to more easily
operate such interfaces by selecting tabs, panels, or windows
representing controls of a particular UAV. Other personnel, such as
commanders and field operators may have more interest in tracker
functionality (e.g., UAV camera control) or video functionality
(e.g., UAV camera control), and therefore may be able to more
easily obtain and use such functionality by selecting tabs, panels,
or windows representing that particular functionality. The instant
subject matter allows such users can more quickly focus on a
particular aircraft or function.
[0039] As will be appreciated, the options available and/or desired
for each function of UAV operation may vary. Therefore, in another
example, menu options presented to an operator may be changed based
on the function selected by the operator. For example, FIG. 7 shows
section of user interface 700 that includes function selection
section 710 and options section 720. Upon an operator selecting a
particular function from function selection section 710, such as
"Training", the options presented in options section 720 may be
automatically changed options that are relevant to the selected
function. Any type and number of options may be used for each of
any type any number of functions and all such implementations are
contemplated as within the scope of the present disclosure.
[0040] In an example, an operator may be presented in a user
interface with checklists that provide a simplified way of stepping
through procedures that are typically performed in a similar
manner. For example, a method of controlling a UAV may include
generating an electronic checklist comprising a plurality of steps,
detecting a user selection of a step from among the plurality of
steps, and presenting information associated with the step. Such
checklists may be generated and provided by a flight planning and
control system. Such checklists may be initiated or selected using
any means, including selection from options presented with a
function selection as described above, selection from a menu,
automatically presented based on a trigger, etc. For example, user
interface 800 of FIG. 8 illustrates an example of an electronic
checklist integrated into a user interface. Checklist 810 may list
steps that are to be performed for a particular activity. Each step
may be checked off by an operator as performed, or may be
automatically updated based on data received by the flight planning
and control system as functions are performed.
[0041] Further detailed information about each step in checklist
810 may be provided when an operator selects a particular step. For
example, in user interface 800, the "CONTROL SURFACE POSITIONS"
step is selected from checklist 810, and in response, detailed
information and controls regarding this step are presented in
section 820 of user interface 800. Section 820 may include any
additional details about a selected step, controls that may affect
one or more devices or components of a UAV or other equipment,
controls that activate a macro that will perform one or more tasks,
and controls for obtaining additional information about any part of
the step. The data associated with a checklist step may be
customized and altered as needed. Such data may include
instructions to an operator about particular conditions and
situations to be aware of, steps to be taken manually, etc.
[0042] In another example, an operator may be presented in a user
interface with emergency checklists that provide a simplified way
of addressing emergencies by presenting the operator with a
checklist that steps the operator through procedures that may be
performed in particular emergencies. Such checklists may be
initiated or selected using any means, including selection from
options presented with a function selection as described above,
selection from a menu, automatically presented based on a trigger,
etc. For example, user interface 900 of FIG. 9 illustrates an
example of a selection of a particular emergency checklist. An
operator may request a listing of emergency check lists from menu
910, resulting in the presentation of listing of emergency
checklists 920. Listing of checklists 920 may include checklists
associated with particular types of emergencies and may also
include suggested checklists that may be determined by a system
based on data received regarding a UAV.
[0043] Upon selection of an emergency checklist, as shown in FIG.
10 illustrating user interface 1000, emergency procedures 1010 may
be presented to an operator. Emergency procedures 1010 may include
steps that an operator may take to address the emergency associated
with the selected checklist. Emergency procedures 1010 may include
additional details about a selected step, controls that may affect
one or more devices or components of a UAV or other equipment,
controls that activate a macro that will perform one or more tasks,
and controls for obtaining additional information about any part of
the step. Emergency procedures 1010 may also include user input box
1011 that allows the operator to provide data about the emergency
or devices and UAVs involved in the emergency to a flight planning
and control system to allow the system to update the presented
steps based on the supplied data so that the steps can be made more
specific to the ongoing emergency. As will be appreciated this may
allow an operator to more efficiently and effectively address the
emergency. Emergency procedures 1010 may include a control allowing
an operator to indicate that a step is complete. In response, a
flight planning and control system may then automatically present
the next step to the operator.
[0044] FIG. 11 and the following discussion are intended to provide
a brief general description of a suitable computing environment in
which the methods and systems disclosed herein and/or portions
thereof may be implemented. For example, the functions of server
304, laptop 306, desktop 308, flight planning and control system
302, and database 326 may be performed by one or more devices that
include some or all of the aspects described in regard to FIG. 11.
Some or all of the devices described in FIG. 11 that may be used to
perform functions of the claimed examples may be configured in
other devices and systems such as those described herein.
Alternatively, some or all of the devices described in FIG. 11 may
be included in any device, combination of devices, or any system
that performs any aspect of a disclosed example.
[0045] Although not required, the methods and systems disclosed
herein may be described in the general context of
computer-executable instructions, such as program modules, being
executed by a computer, such as a client workstation, server or
personal computer. Such computer-executable instructions may be
stored on any type of computer-readable storage device that is not
a transient signal per se. Generally, program modules include
routines, programs, objects, components, data structures and the
like that perform particular tasks or implement particular abstract
data types. Moreover, it should be appreciated that the methods and
systems disclosed herein and/or portions thereof may be practiced
with other computer system configurations, including hand-held
devices, multi-processor systems, microprocessor-based or
programmable consumer electronics, network PCs, minicomputers,
mainframe computers and the like. The methods and systems disclosed
herein may also be practiced in distributed computing environments
where tasks are performed by remote processing devices that are
linked through a communications network. In a distributed computing
environment, program modules may be located in both local and
remote memory storage devices.
[0046] FIG. 11 is a block diagram representing a general purpose
computer system in which aspects of the methods and systems
disclosed herein and/or portions thereof may be incorporated. As
shown, the exemplary general purpose computing system includes
computer 1120 or the like, including processing unit 1121, system
memory 1122, and system bus 1123 that couples various system
components including the system memory to processing unit 1121.
System bus 1123 may be any of several types of bus structures
including a memory bus or memory controller, a peripheral bus, and
a local bus using any of a variety of bus architectures. The system
memory may include read-only memory (ROM) 1124 and random access
memory (RAM) 1125. Basic input/output system 1126 (BIOS), which may
contain the basic routines that help to transfer information
between elements within computer 1120, such as during start-up, may
be stored in ROM 1124.
[0047] Computer 1120 may further include hard disk drive 1127 for
reading from and writing to a hard disk (not shown), magnetic disk
drive 1128 for reading from or writing to removable magnetic disk
1129, and/or optical disk drive 1130 for reading from or writing to
removable optical disk 1131 such as a CD-ROM or other optical
media. Hard disk drive 1127, magnetic disk drive 1128, and optical
disk drive 1130 may be connected to system bus 1123 by hard disk
drive interface 1132, magnetic disk drive interface 1133, and
optical drive interface 1134, respectively. The drives and their
associated computer-readable media provide nonvolatile storage of
computer-readable instructions, data structures, program modules
and other data for computer 1120.
[0048] Although the example environment described herein employs a
hard disk, removable magnetic disk 1129, and removable optical disk
1131, it should be appreciated that other types of
computer-readable media that can store data that is accessible by a
computer may also be used in the exemplary operating environment.
Such other types of media include, but are not limited to, a
magnetic cassette, a flash memory card, a digital video or
versatile disk, a Bernoulli cartridge, a random access memory
(RAM), a read-only memory (ROM), and the like.
[0049] A number of program modules may be stored on hard disk drive
1127, magnetic disk 1129, optical disk 1131, ROM 1124, and/or RAM
1125, including an operating system 1135, one or more application
programs 1136, other program modules 1137 and program data 1138. A
user may enter commands and information into the computer 1120
through input devices such as a keyboard 1140 and pointing device
1142. Other input devices (not shown) may include a microphone,
joystick, game pad, satellite disk, scanner, or the like. These and
other input devices are often connected to the processing unit 1121
through a serial port interface 1146 that is coupled to the system
bus, but may be connected by other interfaces, such as a parallel
port, game port, or universal serial bus (USB). A monitor 1147 or
other type of display device may also be connected to the system
bus 1123 via an interface, such as a video adapter 448. In addition
to the monitor 1147, a computer may include other peripheral output
devices (not shown), such as speakers and printers. The exemplary
system of FIG. 11 may also include host adapter 1155, Small
Computer System Interface (SCSI) bus 1156, and external storage
device 1162 that may be connected to the SCSI bus 1156.
[0050] The computer 1120 may operate in a networked environment
using logical and/or physical connections to one or more remote
computers or devices, such as remote computer 1149, that may
represent any of server 304, laptop 306, desktop 308, flight
planning and control system 302, and database 326. Each of server
304, laptop 306, desktop 308, flight planning and control system
302, and database 326 may be any device as described herein capable
of generating or otherwise interacting with user interfaces used to
control, monitor, or otherwise operate a UAV. Remote computer 1149
may be a personal computer, a server, a router, a network PC, a
peer device or other common network node, and may include many or
all of the elements described above relative to the computer 1120,
although only a memory storage device 1150 has been illustrated in
FIG. 11. The logical connections depicted in FIG. 11 may include
local area network (LAN) 1151 and wide area network (WAN) 1152.
Such networking environments are commonplace in police and military
facilities, offices, enterprise-wide computer networks, intranets,
and the Internet.
[0051] When used in a LAN networking environment, computer 1120 may
be connected to LAN 1151 through network interface or adapter 1153.
When used in a WAN networking environment, computer 1120 may
include modem 1154 or other means for establishing communications
over wide area network 1152, such as the Internet. Modem 1154,
which may be internal or external, may be connected to system bus
1123 via serial port interface 1146. In a networked environment,
program modules depicted relative to computer 1120, or portions
thereof, may be stored in a remote memory storage device. It will
be appreciated that the network connections shown are exemplary and
other means of establishing a communications link between computers
may be used.
[0052] Computer 1120 may include a variety of computer-readable
storage media. Computer-readable storage media can be any available
tangible, non-transitory, or non-propagating media that can be
accessed by computer 1120 and includes both volatile and
nonvolatile media, removable and non-removable media. By way of
example, and not limitation, computer-readable media may comprise
computer storage media and communication media. Computer storage
media include volatile and nonvolatile, removable and non-removable
media implemented in any method or technology for storage of
information such as computer-readable instructions, data
structures, program modules or other data. Computer storage media
include, but are not limited to, RAM, ROM, EEPROM, flash memory or
other memory technology, CD-ROM, digital versatile disks (DVD) or
other optical disk storage, magnetic cassettes, magnetic tape,
magnetic disk storage or other magnetic storage devices, or any
other tangible medium that can be used to store the desired
information and that can be accessed by computer 1120. Combinations
of any of the above should also be included within the scope of
computer-readable media that may be used to store source code for
implementing the methods and systems described herein. Any
combination of the features or elements disclosed herein may be
used in one or more examples.
[0053] This written description uses examples to disclose the
subject matter contained herein, including the best mode, and also
to enable any person skilled in the art to practice the invention,
including making and using any devices or systems and performing
any incorporated methods. The patentable scope of this disclosure
is defined by the claims, and may include other examples that occur
to those skilled in the art. Such other examples are intended to be
within the scope of the claims if they have structural elements
that do not differ from the literal language of the claims, or if
they include equivalent structural elements with insubstantial
differences from the literal languages of the claims.
* * * * *