Application program interface for weight and balance metrics
First Claim
1. One or more non-transitory computer-readable media storing computer-executable instructions that, when executed on one or more processors, performs acts as an application program interface (API) to facilitate communications between a plurality of systems associated with an unmanned aerial vehicle (UAV) and a physical metrics acquisition (PMA) device, the API comprising:
- an initial routine configured to receive an optical signal, from the PMA device, based at least in part on a determination that that the UAV is in contact with the PMA device;
an identification routine configured to perform image analysis on the optical signal to identify the UAV, determine a type of the UAV, and receive a unique identifier of the UAV;
a data routine to receive flight task data for the UAV based on the unique identifier, the flight task data indicating at least a flight path;
a weight routine configured to;
receive, from the PMA device, signals that are each associated with a weight measured at one or more locations on the UAV;
calculate a total weight of the UAV and a center of mass of the UAV based on the signals; and
determine power consumption estimation based at least in part on the total weight of the UAV and the flight task data;
a data structure configured to store the total weight, the power consumption estimation, the type of the UAV, and the center of mass associated with the UAV; and
a transmit routine configured to transmit the data structure to at least a control system of the UAV, wherein the data structure is utilized by at least the control system of the UAV to control flight or operation of the UAV.
1 Assignment
0 Petitions
Accused Products
Abstract
An application program interface may be used to collect and disseminate physical metrics of an unmanned aerial vehicle (UAV). A weight distribution associated with a UAV may be determined prior to dispatch of the UAV and/or after the UAV returns from operation (e.g., a flight). In some embodiments, one or more UAVs may be placed on or proximate to a physical metrics acquisition (PMA) device to determine a distribution of weight of the UAV at three or more points associated with the UAV. The distribution of weight may be used generate analytics, which may include a total weight of a vehicle, a center of mass of the vehicle (in two or more dimensions), power requirements of the UAV for a given flight task (e.g., how much battery power the UAV requires, etc.), and/or other analytics. In various embodiments, the PMA device may perform moment of inertia tests for the UAV.
-
Citations
20 Claims
-
1. One or more non-transitory computer-readable media storing computer-executable instructions that, when executed on one or more processors, performs acts as an application program interface (API) to facilitate communications between a plurality of systems associated with an unmanned aerial vehicle (UAV) and a physical metrics acquisition (PMA) device, the API comprising:
-
an initial routine configured to receive an optical signal, from the PMA device, based at least in part on a determination that that the UAV is in contact with the PMA device; an identification routine configured to perform image analysis on the optical signal to identify the UAV, determine a type of the UAV, and receive a unique identifier of the UAV; a data routine to receive flight task data for the UAV based on the unique identifier, the flight task data indicating at least a flight path; a weight routine configured to; receive, from the PMA device, signals that are each associated with a weight measured at one or more locations on the UAV; calculate a total weight of the UAV and a center of mass of the UAV based on the signals; and determine power consumption estimation based at least in part on the total weight of the UAV and the flight task data; a data structure configured to store the total weight, the power consumption estimation, the type of the UAV, and the center of mass associated with the UAV; and a transmit routine configured to transmit the data structure to at least a control system of the UAV, wherein the data structure is utilized by at least the control system of the UAV to control flight or operation of the UAV. - View Dependent Claims (2, 3, 4)
-
-
5. One or more non-transitory computer-readable media storing computer-executable instructions of an application program interface (API), comprising:
-
an initial routine configured to receive an optical signal, from a physical metrics acquisition (PMA) device, based on a determination by the PMA device that an unmanned aerial vehicle (UAV) is in contact with the PMA device; an identification routine configured to perform image analysis on the optical signal to identify the UAV and receive a unique identifier of the UAV; a task routine to receive flight data for the UAV based on the unique identifier, the flight data including at least a travel distance; a data routine configured to receive signals each associated with a weight measured at a location on the UAV; a weight routine configured to calculate a total weight of the UAV and a center of mass of the UAV based at least partially on the signals, and determine power requirements for the UAV based at least partially on the total weight and the flight data; and a first data structure configured to store the total weight, the power requirements, and the center of mass associated with the UAV, the total weight and center of mass being accessible via the first data structure by at least one other system associated with the UAV, wherein the first data structure is utilized by the at least one other system associated with the UAV to control flight or operation of the UAV. - View Dependent Claims (6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16)
-
-
17. One or more non-transitory computer-readable media storing computer-executable instructions of an application program interface (API), comprising:
-
an initial routine configured to receive signals from a load cell grid based on a determination that an unmanned aerial vehicle (UAV) is in contact with the load cell grid, the load cell grid comprising a plurality of load cells, each load cell of the plurality of load cells having known coordinates within the load cell grid; a data routine configured to calculate a total weight of an unmanned aerial vehicle (UAV) and a center of mass of the UAV based on the signals from the load cell grid, each signal associated with a weight measured at a location on the UAV, and to determine power requirements for the UAV based at least partially on an assigned flight task; an identification routine configured to determine a type of the UAV based at least in part on known footprints associated with the UAV, the signals from the load cell grid, and the known coordinates; a data structure configured to store the type of the UAV, the total weight, the power requirements, and the center of mass associated with the UAV, the data structure being accessible by at least one other system associated with the UAV and is utilized by the at least one other system associated with the UAV to control flight or operation of the UAV; and a transmit routine configured to transmit the power requirements to a power manager. - View Dependent Claims (18, 19, 20)
-
Specification