Drones convertible into personal computers

Drones convertible into personal computers are disclosed, A disclosed unmanned aerial vehicle (UAV) includes a body and rotors carried by the body. The rotors move relative to the body from a first position when the UAV is in a drone mode to a second position when the UAV is in a computer mode.

FIELD OF THE DISCLOSURE

This disclosure relates generally to unmanned aircraft and, more particularly, to drones that are convertible into personal computers.

BACKGROUND

Unmanned aerial vehicles (UAVs), sometimes referred to as drones, are becoming more readily available. Indeed, the market for UAVs is rapidly growing. UAVs are now being used in a wide variety of industries, such as farming, shipping, forestry management, surveillance, disaster scenarios, gaming, photography, marketing, etc. As both navigational capabilities and power efficiency for UAVs have increased, some UAVs can travel very significant distances to perform tasks (e.g., take measurements, record photographs or video, etc.).

The figures are not to scale. Instead, the thickness of the layers or regions may be enlarged in the drawings. In general, the same reference numbers will be used throughout the drawing(s) and accompanying written description to refer to the same or like parts. As used in this patent, stating that any part is in any way on (e.g., positioned on, located on, disposed on, or formed on, etc.) another part, indicates that the referenced part is either in contact with the other part, or that the referenced part is above the other part with one or more intermediate part(s) located therebetween. Stating that any part is in contact with another part means that there is no intermediate part between the two parts.

DETAILED DESCRIPTION

Drones (e.g., UAVs) that are convertible into computers are disclosed. Unmanned aerial vehicles (UAVs), which are also referred to as drones have an increased variety of applications. As both navigational capabilities and power efficiency for UAVs have increased, some UAVs can travel very significant distances to perform tasks (e.g., take measurements, record photographs or video, etc.). Further, data taken or recorded by a UAV are typically offloaded from the UAV to an external computer for further analysis due to computational and/or battery limitations of the UAV.

Examples disclosed herein enable UAVs to be used as computers (e.g., personal computers, computer terminals, workstations, etc.). Examples disclosed herein enable a UAV to undergo a physical transformation from a drone mode to a computer mode. In the drone mode, the UAV is capable of moving itself from one geographic location go another (e.g., via rotors itself or the like). In the computer mode, the UAV does not move itself from one physical location to another. Instead, its means of locomotion (e.g., its rotors) may be disabled and/or repositioned for another use, such as cooling. For example, in the computer mode, the UAV can analyze data obtained by the UAV during flight. In some examples, the UAV can be deployed as a self-transporting computer (e.g., deployed via its own means for locomotion to a remotely located user and/or site to provide computing capabilities). Some examples disclosed herein implement movable (e.g., rotatable and/or translatable) arms or mounts having rotor blades coupled thereto. In some examples, the movable arms/mounts are disposed on opposite sides of the UAV and may be folded towards a body and/or a heatsink of the UAV when the UAV is converted from the drone mode to the computer mode. As a result, a processor disposed in the body is cooled by airflow generated by the rotor blades (e.g., by the blades blowing air towards the heatsink) when the UAV is operated in the computer mode. Some example UAVs disclosed herein are placed into a receiving dock in the computer mode of the UAV so that the UAV can be easily communicatively coupled to input/output (I/O) devices and/or an external network, and to prevent contact with and/or injury from the rotors while operating as cooling fans.

In some examples, the UAV includes a scalable processor that can operate at relatively lower clock speeds for flight navigation and/or camera control when in the drone mode, and can also operate at relatively higher clock speeds when in the computer mode. In some examples, the rotor blades are generally aligned at a same vertical height when the rotor blades are positioned for flight operation in the drone mode. In some examples, the UAV includes movable (e.g., rotatable) landing legs in addition to the rotatable arms/mounts. In some examples, the dock provides power (e.g., supplemental power, primary power, etc.) to the UAV when the UAV is docked thereto to provide additional power for running the processor at higher clock speeds in the computer mode. Operating at a lower clock speed in the drone mode reduces power usage and heat generation. In some examples, the UAV includes a camera mounted to the body of the UAV. In some examples, the camera is mounted via a gimbal.

FIG. 1illustrates an example unmanned aerial vehicle (UAV)100constructed in accordance with teachings of this disclosure and shown in a drone mode. The UAV100of the illustrated example includes a body (e.g., frame body, a body structure, etc.)102. Rotor assemblies104are coupled to opposite sides of the body102. In this example, both of the rotor assemblies104include a movable support (e.g., a mounting plate, a contoured mounting plate)106a,106b. The movable supports106a,106bhave arms/mounts107projecting therefrom. The arms/mounts107support rotors (e.g., rotor blades, etc.)110a,110bat their respective distal ends111. In the illustrated example, each rotor assembly104includes one arm support106a,106b, and each support106a,106bincludes two arms/mounts107. Therefore, each support106a,106bincludes two rotors110. Other numbers of these components may be provided in other examples.

The supports106a,106bare rotatably mounted to the body102to rotate about respective axes108. Thus, the arms107and the rotors110pivot as their respective support106a,106bis rotated. In the illustrated example, the supports106a,106bpivot in opposite directions. The supports106a,106bmay be mounted to the body102using any described type of mechanical fastener such as hinges.

In the illustrated example, the body102includes two heatsink arrays112a,112b. One of the heatsink arrays112ais mounted to a top of the body102. The other of the heatsink arrays112bis mounted to the bottom of the body102(SeeFIGS. 2 and 3). The example body102also includes a camera assembly114. In this example, the camera assembly114includes a gimbal to stabilize images and/or video taken by the camera assembly114. A power switch or button116is carried by the body102for turning the UAV100on and off.

In the illustrated example, the UAV100includes landing legs120. In this example, the landing legs120are movably (e.g., pivotably) coupled to the body102and/or the supports106a,106bfor rotation in directions generally indicated by double arrows122. The legs120may be mounted to the body102and/or the mount for rotation using any type of mechanical fastener (e.g., a bushing and bolt). In other examples, the legs120are mounted to respective ones of the arms107. In such examples, the landing legs120rotate outward from the body102when the supports106are pivoted. In some examples, the legs120are integral with the corresponding rotatable supports106and do not pivot relative to the arms107.

In some examples, the UAV100includes one or more actuators130to move the supports106a,106b, the arms107and/or the landing legs120between various positions. The actuators130may be implemented as a motor(s), solenoid(s) and/or any other appropriate actuation device. The inclusion of the actuator(s)130enables automated and/or powered conversion between the drone and computer modes.

The UAV100of the illustrated example includes a self-guidance system. Additionally or alternatively, the UAV100can be manually guided or controlled via a wireless (e.g., RF) signal connection. In the illustrated example, the UAV100can maneuver based on controlled rotation of the rotors110. In particular, varying rotational speeds of the rotors110enables controlled movement (e.g., flight maneuvers, navigation, etc.) of the UAV100. In some examples, the camera assembly114is used to capture images or video while the UAV100is in flight. As will be discussed in greater detail below, the UAV100can be converted from the drone mode ofFIG. 1when the UAV100is capable of self-propelled flight into a computer mode where the UAV100does not move itself, but instead operates as a non-self-propelled computer (e.g., a personal computer, a workstation, a user terminal, a computational node, etc.). In the computer mode, the rotors110are not used for movement of the UAV100, but instead are used to cool a processor314(shown inFIG. 3) of the UAV100. The processor314may operate at a higher clock speed in the computer mode than in the drone mode.

FIG. 2is a front view of the example UAV100ofFIG. 1. In the illustrated view ofFIG. 2, a reference line202is shown to illustrate that the rotors110a,110bare generally aligned at a same height (along a horizontal plane in the view ofFIG. 2) when the UAV100is in a level position relative to a reference like Earth. The rotatable supports106a,106b(and/or the arms107of the supports106a,106b) rotate along opposite directions to deploy or un-deploy, as indicated by double arrows206. In other words, the supports106a,106bof the illustrated example rotate toward different sides of the body102(i.e., the support106ais rotated toward the upper side of the body102and the support106bis rotated toward the lower side of the body102in the view ofFIG. 2). The rotors110are generally aligned with the reference line202in the same horizontal plane when deployed in the drone mode. In some examples, a camera lens208of the camera assembly114is also generally aligned with the reference line202. Additionally or alternatively, the heatsink arrays112a,112bare positioned on opposite sides of the body102(e.g., on the upper and lower sides of the body102). at approximately equal vertical distances on opposite sides the reference line202.

FIG. 3is an exploded view of the example UAV100ofFIGS. 1 and 2. In particular, numerous components of the body102are shown separated from one another for clarity. According to the illustrated example ofFIG. 3, the body102includes a frame (e.g., an airframe structure, a chassis, etc.)304. The body102carries the upper heatsink array112a, a battery (e.g., a battery assembly, a battery module)306, a printed circuit board (PCB) (e.g., a motherboard, etc.)308with numerous electrical components and/or circuits such as those shown inFIG. 12, a thermal bracket310, a camera board312of the camera assembly114(shown inFIGS. 1 and 2) and the lower heatsink array112b. In some examples, the PCB308carries and/or implements a mode converter316.

In the illustrated example, the PCB308carries the aforementioned processor314. The processor314may be implemented as a die, a system-on-chip (SOC), a multicore processor, etc. In the illustrated example, the processor314is a hardware (e.g., a semiconductor board) processor. The processor314can be run at a lower clock speed when the UAV100is in the drone mode. Conversely, the processor314can run at a relatively higher clock speed when the UAV100is operated in the computer mode (e.g., higher clock speeds will facilitate computational tasks such as running user applications, data processing, video and/or graphical processing, etc.).

While the example UAV100includes both upper and lower heatsink arrays112a,112b, a single heatsink array may be implemented in some examples. While the UAV100utilizes the same processor314for both flight and computer functionality, the UAV100may include two or more processors. For example, the UAV100may utilize a flight processor in the drone mode, and a different processor in the computer mode. These two different processors may operate at different clock speeds. In some examples, the thermal bracket310is at least partially composed of copper. However, any appropriate material may be used.

FIG. 4Ais a top view of the example UAV100ofFIGS. 1-3. In the example ofFIG. 4A, the UAV100is shown in the drone mode with the rotors110deployed outward from the body102for flight.

FIG. 4Bis a cross-sectional view taken along the line4B-4B ofFIG. 4A. In this example, the upper and lower heatsink arrays112a,112bare shown. The PCB308, the processor314and the thermal bracket310are shown disposed between the heatsink arrays112a,112b.

To facilitate heat conduction from the processor314and/or the PCB308to one or more of the heatsink arrays112a,112b, the processor314is thermally coupled to the thermal bracket310. The thermal bracket310is, in turn, coupled to the lower heatsink array112bin this example. Additionally or alternatively, an upper side (in the view ofFIG. 4B) of the PCB308may be thermally coupled to the upper heatsink array112a(e.g., via a second thermal bracket). In other examples, the processor314is directly thermally coupled to the lower heatsink array112b(e.g., the thermal bracket310is omitted). In this example, thermal gaskets and/or thermal paste402are used to facilitate contact between the PCB308, the heatsink arrays112a,112b, the processor314and the thermal bracket310, thereby enabling relatively high thermal conduction therebetween.

FIG. 5Adepicts the example UAV100ofFIGS. 1-4converting from the drone mode into the computer mode. In a first position502, the UAV100is in the drone mode. To begin the conversion, the landing legs120are folded upwards towards the body102, as generally indicated by arrows504. In the first position502, the supports106a,106bare in their respective vehicle operation positions (e.g., deployed flight positions), but ready to be rotated towards the body102, as generally indicated by arrows506. In this example, the rotatable supports106a,106bare rotated in opposite directions (e.g., the same rotational direction). Locks of any type may be used to hold the supports106a,106band/or the landing legs120in the deployed position and/or the stored position. In other examples, one or both of the supports106a,106bare rotated in the opposite direction from those shown inFIG. 5A. In some examples, at least one of the supports106a,106band/or the landing legs120are rotated by the actuators130. In such examples, the UAV100is at least partially self-folding.

FIG. 5Aalso depicts an intermediate position510in which the rotatable supports106a,106bare being folded towards the body102, as generally indicated by arrows512. A third example position516depicts the UAV100with the supports106a,106bfully folded towards the body102and, thus, the UAV100in the computer mode. Subsequently the fully folded UAV100is inserted into a dock520(e.g., a cavity of the dock520) to facilitate operation in the computer mode and protect against injury that can result from inadvertent contact with the rotors110. The UAV100in the dock520may be thought of as the final computing position518. In the example positions516and518, the supports106are rotated to respective computer operation positions so that the UAV100can be inserted into the dock520. In particular, the example supports106are rotated to position the rotors110in close proximity to (e.g., adjacent to) the respective heatsink arrays112a,112b.

FIG. 5Bdepicts the example UAV100in communication with an external monitor524and a mouse for operating as a personal computer. In some examples, the dock520may be in wired or wireless communication with the display or monitor524and/or in wired or wireless communication with one or more input devices526(e.g., a keyboard and/or mouse). The example dock520is also coupled to an external power supply/cable530.

In some examples, at least one of the input devices526and/or the display524are integral with the dock520. In some other examples, a battery532is used to power the dock520and/or supplement operation of the UAV100when operating in the computer mode. In other examples, the display524is integral with the UAV100.

In some examples, the UAV100forms part of a distributed computing system (e.g., a server, a distributed computation system, a network node or gateway, a calculation array, etc.) when in the computer mode. In some other examples, the UAV100is not inserted into a dock and is, instead, operated as a computer without the benefit of the dock520after the UAV100has landed at a destination.

The dock520is useful in some examples to facilitate connection to other devices. As such, the dock520includes a connector that communicates with an interface of the UAV100. In other examples, the dock520is omitted. In some such examples, I/O devices526may be directly coupled to the UAV100. In some examples, the UAV100includes a projector (e.g., a video projector)534so that the display524is not needed.

FIGS. 6A and 6Bare front, right side perspective and rear, left side, perspective views, respectively, of an example implementation of the dock520. Turning toFIG. 6A, the dock520of the illustrated example includes a housing602having an opening or slot (e.g., a top opening)604to receive the UAV100. Further, the dock520includes vents606, an opening608to access the power switch116and an opening610for the camera assembly114. In this example, the vents606are generally circular-shaped radial patterns having support webs611. In some examples, the dock520also includes an I/O port612, which may be implemented as a universal serial bus (USB) connector. In some examples, the camera assembly114is operated when the UAV100is docked in the dock520and also when the UAV100is operated in the drone mode.

Turning toFIG. 6B, the dock520is shown with stops (e.g., finger stops)620. The stops620may be rubber or plastic. In this example, the dock520also includes openings or vents622on an opposite side from the vents606described above in connection withFIG. 6A. In this example, the vents622are generally identical to the vents606in terms of overall structures and geometry. In the illustrated example, the dock520also includes outlet openings (e.g., exhaust openings)624. The dock520also includes I/O ports626(e.g., USB ports). While the I/O ports626of the illustrated example are universal serial bus connectors, any appropriate I/O ports and/or data protocol(s) may be used.

FIGS. 7A-7Cdepict example airflows that may be generated for cooling the UAV100and/or its electronics in examples disclosed herein. Turning toFIG. 7A, a cross-sectional view is shown depicting the UAV100disposed within the dock520. The rotatable support106a, the frame304and the stops620are shown inFIG. 7A. In this example, arrows702indicate inlet air drawn into the dock520by the rotors110into the openings606,622while arrows704indicate exhaust air exiting the dock520.

Turning toFIG. 7B, a cross-sectional view taken along line7B-7B ofFIG. 7Ais shown. In this example, arrows710generally indicate air drawn into the view ofFIG. 7Bby the rotors110. The air flows towards the heatsink array112a. Further, arrows712,713indicate heated air exiting away from the heatsink array112a. Fins714of the heatsink array112agenerally extend in the directions of the arrows712, thereby facilitating relatively efficient heat removal from the heatsink array112a. The orientation (e.g., generally horizontal) of the fins714facilitates outward movement of the air in the directions indicated by the arrows712. The fins714increase surface area for heat transfer associated with the heatsink array112a.

FIG. 7Cis a cross-sectional view taken along line7C-7C ofFIG. 7A. Similar toFIG. 7B,FIG. 7Cdepicts arrows720indicating air drawn toward the heatsink array112bby the rotors110(into the view ofFIG. 7C) while arrows722depict heated air being exhausted from the dock520and the heatsink array112b.

FIGS. 8A-8Ddepict an example interface that may be implemented in examples disclosed herein to couple the UAV100to the dock520.FIG. 8Ais a perspective view of the folded UAV100in the computer mode. In the illustrated example, the UAV100includes an interface802proximate the rotatable support106a. The interface802of this example includes multiple electrical pins and may be implemented as a pogo pin pad connector, for example.

FIG. 8Bis a cross-sectional view of the dock520with the UAV100disposed within.FIG. 8Bis shown from above (e.g., along a direction of insertion of the UAV100into the dock520).

FIG. 8Cis a cross-sectional view taken along line8C-8C ofFIG. 8B. As can be seen in the illustrated view ofFIG. 8C, a lower wall (e.g., an alignment wall)804of the dock520and a bottom edge806of the UAV100are in contact. In this example, the dock520includes a connector810structured to mate with the interface802of the UAV100shown in connection withFIG. 8A.

To facilitate engagement of the connector810to the interface802to thereby secure the UAV100in position relative to the dock520, the UAV100is inserted into the dock520until the bottom edge806contacts the lower wall804. In particular, as the folded UAV100is inserted into the dock520, the inner walls812and/or structural guides of the dock520guide the movement of the UAV100so that the connector810is aligned to the interface802during insertion of the UAV100. In this example, the connector810is implemented as a pogo pin connector. Accordingly, the interface802and the connector810define a pogo pin interface (e.g., a pogo pin pad array). However, any other appropriate connection or insertion scheme may additionally or alternatively be implemented.

In some examples, the dock520includes supports822a,822bto determine a presence of the UAV100within the dock520. The supports822a,822bmay be implemented as sensors (e.g., magnetic sensors, optic sensors, proximity sensors, actuated switches, etc.).

FIG. 8Dis a detailed view of the connector810in engagement with the interface802when the folded UAV100is placed into the dock520. In this example, the orientation of the dock520relative to a support surface820(shown inFIG. 8C) facilitates compression of the pogo pins of the connector810against the interface802based on gravity. In particular, the weight of the UAV100compresses the pogo pins against the interface802.

FIGS. 9A and 9Bdepict example stops620that may be implemented in examples disclosed herein.FIG. 9Ais a cross-sectional view of the UAV100inserted in the dock520. The illustrated view ofFIG. 9Adepicts an example placement of the stops620relative to the UAV100and the rotors110.

FIG. 9Bis a detailed view of a portion ofFIG. 9Aillustrating how the stops620may prevent access (e.g., human access) to the rotor blades110by a hand902and/or fingers904when the UAV is operating in the computer mode while positioned in the dock520. In some examples, the stops620are additionally or alternatively used to contact and/or retain the UAV100from being unintentionally removed from the dock520. In such examples, the stops620may be implemented as retention or snap tabs.

The stops620have a generally hollow triangular profile in the view ofFIG. 9B. However, any other appropriate geometry may be used.

FIG. 10is a schematic overview of an example mode converter316of the UAV100. The example mode converter316includes a mode detector1002, a rotor controller1004, and a clock controller1006. The example mode detector1002is communicatively coupled to a sensor1010.

In the illustrated example, the mode detector1002determines whether the UAV100is in the computer mode or the drone mode. In some examples, the mode detector1002utilizes measurements from the sensor1010to make the mode determination. For example, the sensor1010may be a temperature sensor, a switch, a magnet detector, a rotor position sensor, etc. to detect a presence of the UAV100in the dock520. In some examples, the mode is determined by a position (e.g., angular position) of the supports106a,106band/or the rotors110relative to the body102. In other examples, the mode detector1002may detect current from the dock520and/or the portion(s) of one or more of the supports822a,822bto make the mode determination.

To control a speed and/or an on/off state of the rotors110, the rotor controller1004is communicatively coupled to one or more motors that drive the rotors110. In this example, the mode detector1002directs the rotor controller1004to spin (e.g., to turn on for either for propulsion or to cool the processor314) based on the mode (e.g., drone mode or computer mode) of the UAV100identified by the mode detector1002.

The clock controller1006of the illustrated example controls a clock speed of the processor314. In particular, the example clock controller1006directs the processor314to operate at a higher clock speed when the UAV100is operated in the computer mode. Conversely, the clock controller1006directs the processor314to operate at a lower clock speed when the UAV100is operated in the drone mode (e.g., to conserve power). The processor314includes an onboard clock1008, but the processor314is able to operate at a fraction of the clock speed as needed.

In some examples, the rotor controller1004is directed by the mode detector1002to control rotational speeds of the rotors110. Additionally or alternatively, the rotor controller1004may utilize a temperature measured by the sensor1010(e.g., by the temperature of the processor314) to control the on/off state and/or the rotational speeds of the rotors110when in the computer mode.

While an example manner of implementing the mode converter316ofFIG. 3is illustrated inFIG. 10, one or more of the elements, processes and/or devices illustrated inFIG. 10may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example mode detector1002, the example rotor controller1004, the example clock controller1006and/or, more generally, the example mode converter316ofFIG. 3may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, any of the example mode detector1002, the example rotor controller1004, the example clock controller1006and/or, more generally, the example mode converter316could be implemented by one or more analog or digital circuit(s), logic circuits, programmable processor(s), programmable controller(s), graphics processing unit(s) (GPU(s)), digital signal processor(s) (DSP(s)), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)). When reading any of the apparatus or system claims of this patent to cover a purely software and/or firmware implementation, at least one of the example, mode detector1002, the example rotor controller1004, and/or the example clock controller1006is/are hereby expressly defined to include a non-transitory computer readable storage device or storage disk such as a memory, a digital versatile disk (DVD), a compact disk (CD), a Blu-ray disk, etc. including the software and/or firmware. Further still, the example mode converter316ofFIG. 3may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated inFIG. 10, and/or may include more than one of any or all of the illustrated elements, processes and devices. As used herein, the phrase “in communication,” including variations thereof, encompasses direct communication and/or indirect communication through one or more intermediary components, and does not require direct physical (e.g., wired) communication and/or constant communication, but rather additionally includes selective communication at periodic intervals, scheduled intervals, aperiodic intervals, and/or one-time events.

A flowchart representative of example hardware logic or machine readable instructions for implementing the mode converter316ofFIG. 3is shown inFIG. 11. The machine readable instructions may be a program or portion of a program for execution by a processor such as the processor1212shown in the example processor platform1200discussed below in connection withFIG. 12. The program may be embodied in software stored on a non-transitory computer readable storage medium such as a CD-ROM, a floppy disk, a hard drive, a DVD, a Blu-ray disk, or a memory associated with the processor1212, but the entire program and/or parts thereof could alternatively be executed by a device other than the processor1212and/or embodied in firmware or dedicated hardware. Further, although the example program is described with reference to the flowchart illustrated inFIG. 11, many other methods of implementing the example mode converter316may alternatively be used. For example, the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, or combined. Additionally or alternatively, any or all of the blocks may be implemented by one or more hardware circuits (e.g., discrete and/or integrated analog and/or digital circuitry, an FPGA, an ASIC, a comparator, an operational-amplifier (op-amp), a logic circuit, etc.) structured to perform the corresponding operation without executing software or firmware.

“Including” and “comprising” (and all forms and tenses thereof) are used herein to be open ended terms. Thus, whenever a claim employs any form of “include” or “comprise” (e.g., comprises, includes, comprising, including, having, etc.) as a preamble or within a claim recitation of any kind, it is to be understood that additional elements, terms, etc. may be present without falling outside the scope of the corresponding claim or recitation. As used herein, when the phrase “at least” is used as the transition term in, for example, a preamble of a claim, it is open-ended in the same manner as the term “comprising” and “including” are open ended. The term “and/or” when used, for example, in a form such as A, B, and/or C refers to any combination or subset of A, B, C such as (1) A alone, (2) B alone, (3) C alone, (4) A with B, (5) A with C, and (6) B with C.

The example instructions1100ofFIG. 11begin at block1102as the example mode detector1002determines whether the UAV100is in the dock520(block1102). If the UAV100is inserted/coupled to the dock520(block1102), control of the process proceeds to block1120. Otherwise, the process proceeds to block1104.

When the mode detector1002determines that the UAV100is in the dock520, the example mode detector1002determines whether the supports106a,106bare in a drone position (e.g., instead of a computer position corresponding the computer mode) based on measurements/data from the sensor1010(block1104). If the supports106a,106bare determined to be in the drone position (block1104), control of the process proceeds to block1106. Otherwise, control of the process proceeds to block1110.

When the supports106a,106bare in the drone position, the clock controller1006sets the clock1008of the processor314to a reduced/lowered clock speed (e.g., from a first clock speed to a second clock speed lower than the first clock speed) (block1106). In some examples, the clock speed is predefined. In some examples, the clock speed is not varied by the clock controller1006if the clock speed is already set to the predefined clock speed.

After reducing the clock speed of the clock1008, the UAV100operates as a drone, for example (block1108). The UAV100may be manually controlled or self-navigating (e.g., based on a guidance system of the UAV100and/or external guidance systems).

The example mode detector1002then determines whether the UAV100is in a power off condition (block1110). If the UAV100is in not in a power off condition (block1110), control of the process returns to block1102to again check the state of the UAV100. Otherwise, the process ends.

Returning to block1102when the UAV100is in the dock520, the clock controller1006increases the clock speed of the clock1008to a predetermined speed (e.g., from a first clock speed to a second clock speed greater than the first clock speed) (block1120). In this example, the mode detector1002directs the clock controller1006to increase the clock speed and/or directs a degree to which the clock speed is to be increased. In other examples, the increased clock speed is not predetermined and is instead adjusted based on conditions measured by the sensor1010.

When the UAV100is operated in the computer mode (block1122). The UAV100may be operated as personal computer or as a node in a distributed computational system, for example. In some examples, a user can edit, process and/or modify data captured (e.g., photographs, video, audio, etc.) by the UAV100during flight.

According to the illustrated example, the mode detector1002determines whether a temperature threshold has been met and whether the UAV100is in the computer mode (block1124). If the temperature threshold has been met (e.g., a measured temperature is equal to the temperature threshold, the measured temperature exceeds the temperature threshold, etc.) in the computer mode (block1124), control proceeds to block1126. Otherwise, control proceeds to block1128.

If the temperature threshold has been met in the computer mode (block1124), the example rotor controller1004directs the rotors110to spin, thereby cooling the processor314, components of the PCB308, etc. (block1126) and the process proceeds to block1110.

When the temperature threshold has been not exceeded and/or the UAV100is not in the computer mode (block1124), the example rotor controller1004directs the rotors110to turn off (e.g., stop) (block1128) and the process proceeds to block1110. In other examples, the rotors110are operated while in the computer mode without regard to the temperature. In such examples, a degree to which the rotors110are spun may vary based on temperatures (e.g., temperatures of the processor314and/or the heatsink arrays112a,112b) measured by the sensor1010.

FIG. 12is a block diagram of an example processor platform1200structured to execute the instructions ofFIG. 11to implement the example mode converter316ofFIG. 3. The processor platform1200can be, for example, a server, a personal computer, a workstation, a self-learning machine (e.g., a neural network), a mobile device (e.g., a cell phone, a smart phone, a tablet such as an iPad™), a personal digital assistant (PDA), an Internet appliance, a DVD player, a CD player, a digital video recorder, a Blu-ray player, a gaming console, a personal video recorder, a set top box, a headset or other wearable device, or any other type of computing device.

The processor platform1200of the illustrated example includes a processor1212. The processor1212of the illustrated example is hardware. For example, the processor1212can be implemented by one or more integrated circuits, logic circuits, microprocessors, GPUs, DSPs, or controllers from any desired family or manufacturer. The hardware processor may be a semiconductor based (e.g., silicon based) device. In this example, the processor implements the example mode detector1002, the example rotor controller1004, and the example clock controller1006.

The processor1212of the illustrated example includes a local memory1213(e.g., a cache). The processor1212of the illustrated example is in communication with a main memory including a volatile memory1214and a non-volatile memory1216via a bus1218. The volatile memory1214may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS® Dynamic Random Access Memory (RDRAM®) and/or any other type of random access memory device. The non-volatile memory1216may be implemented by flash memory and/or any other desired type of memory device. Access to the main memory1214,1216is controlled by a memory controller.

The processor platform1200of the illustrated example also includes an interface circuit1220. The interface circuit1220may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), a Bluetooth® interface, a near field communication (NFC) interface, and/or a PCI express interface.

In the illustrated example, one or more input devices1222are connected to the interface circuit1220. The input device(s)1222permit(s) a user to enter data and/or commands into the processor1212. The input device(s) can be implemented by, for example, an audio sensor, a microphone, a camera (still or video), a keyboard, a button, a mouse, a touchscreen, a track-pad, a trackball, isopoint and/or a voice recognition system.

The processor platform1200of the illustrated example also includes one or more mass storage devices1228for storing software and/or data. Examples of such mass storage devices1228include floppy disk drives, hard drive disks, compact disk drives, Blu-ray disk drives, redundant array of independent disks (RAID) systems, and digital versatile disk (DVD) drives.

The machine executable instructions1232ofFIG. 11may be stored in the mass storage device1228, in the volatile memory1214, in the non-volatile memory1216, and/or on a removable non-transitory computer readable storage medium such as a CD or DVD.

FIG. 13is a flowchart representative of an example method1300to implement examples disclosed herein.

In this example, a determination (e.g., a user determination) is made regarding whether the UAV100is to be operated in a computer mode (block1301). If the UAV100is to be operated in the computer mode, control of the example method1300proceeds to block1304. Otherwise, the method1300proceeds to block1302.

In the illustrated example, a determination is made regarding whether to operate the UAV100in the drone mode (block1302). This determination may be user made. If the UAV100is to be operated in the drone mode (block1302), the method1300proceeds to block1312. Otherwise, the method1300proceeds to block1304.

When the UAV100is to be operated in the computer mode, the example rotatable arms107are folded or rotated toward the corresponding heatsink array112(block1304). In particular, the rotatable arms107are rotated with the respective rotatable supports106to place the rotors110proximate and/or facing the corresponding heatsink array112so that the heatsink array112can be cooled when the UAV100is operated in the computer mode. In some examples, the UAV100is able to at least partially self-fold at least one the arms107(e.g., via the actuator or motor130, etc.).

The UAV100is coupled to the dock520(block1305). In particular, the example UAV100is inserted into the dock520to communicatively couple the interface802of the UAV100with the connector810of the dock520. As a result, data communications between the UAV100and one or more of the I/O devices526is established in this example.

The UAV100is operated in the computer mode (block1306). In this example, a user operates the UAV100at a remote location.

In the illustrated example, a request to remove the UAV100from the dock520is received (e.g., from a user) (block1307). In particular, the UAV100may be physically removed from the dock520and/or a button on the dock520may be operated to cause the UAV100to be released from the dock520.

The rotors110are shut off once the UAV100is finished being operated in the computer mode (block1309). In this example, the rotor controller1004prevents voltage from being provided to motors of the rotors110when the request to remove the UAV100is received (e.g., from a user).

The UAV100is removed from the dock520(block1310). In this example, a user removes the UAV100from the dock520.

After the UAV100is removed from the dock520, the rotors110of the illustrated example are deployed (block1312). According to the illustrated example, the supports106a,106bare rotated away from the body102so that the rotors110can be deployed for locomotion of the UAV100.

It is then determined whether a power down condition has been reached (block1314). If the power down condition has not been reached (block1314), the example method1300returns to block1301. Otherwise, the example method1300ends.

Example 1 includes an unmanned aerial vehicle (UAV) including a body, and rotors carried by the body, where the rotors are to move relative to the body from a first position when the UAV is in a drone mode to a second position when the UAV is in a computer mode.

Example 2 includes the subject matter of Example 1, and further includes arms having a first end carried by the body and a second end carrying the rotors, where the arms are to move from a first position to a second position, where the rotors are positioned to levitate the body when the arms are in the first position, and where the rotors are positioned to move air toward the body when the arms are in the second position.

Example 3 includes the subject matter of Example 2, and further includes at least one processor carried by the body and a heatsink carried by the body, the heatsink positioned to cool the processor, the rotors to move the air toward the heatsink when the UAV is in the computer mode.

Example 4 includes the subject matter of any one of Examples 2 or 3, where the arms are pivotally coupled to the body.

Example 5 includes the subject matter of Example 4, and further includes a support, the arms carried by the support, the support pivotally coupled to the body to pivotally couple the arms to the body.

Example 6 includes the subject matter of any one of Examples 1 to 5, and further includes an interface carried by the body, the interface to engage a connector of a dock when the UAV is positioned in the dock.

Example 7 includes the subject matter of any one of Examples 1 to 6, and further includes landing legs.

Example 8 includes the subject matter of Example 7, where the landing legs are mounted to move from a deployed position to a stored position.

Example 9 includes the subject matter of any one of Examples 1 to 8, and further includes a camera.

Example 10 includes the subject matter of any one of Examples 2 to 9, where the rotors include first, second, third and fourth rotors.

Example 11 includes the subject matter of Example 10, where the first and second rotors are located to a first side of the body when the UAV is in the drone mode, and where the third and fourth rotors are located to a second side of the body when the UAV is in the drone mode.

Example 12 includes the subject matter of Example 11, where the first and second rotors are located adjacent a top side of the body when the UAV is in the computer mode, and the third and fourth rotors are located adjacent a bottom side of the body when the UAV is in the computer mode.

Example 13 includes the subject matter of any one of Examples 1 to 12, and further includes an actuator to move the first and second rotors between the first and second positions.

Example 14 includes a dock including a housing, the housing defining a cavity to receive an unmanned aerial vehicle (UAV), the housing including air inlet openings positioned adjacent rotors of the UAV to enable the rotors to draw air toward the UAV through the housing, and a connector for mechanical and electrical engagement with an interface of the UAV when the UAV is in the cavity.

Example 15 includes the subject matter of Example 14, where the connector includes a pogo pin interface.

Example 16 includes the subject matter of any one of Examples 14 or 15, and further includes stops disposed to reduce human access to the rotors when the UAV is in the cavity.

Example 17 includes a system including an unmanned aerial vehicle (UAV) including an unmanned aerial vehicle (UAV) including a body, rotors carried by the body, the rotors to move relative to the body from a first position when the UAV is in a drone mode to a second position when the UAV is in a computer mode, and a dock to receive the UAV when the UAV is in the computer mode.

Example 18 includes the subject matter of Example 17, and further includes a sensor to detect a presence of the UAV in the dock.

Example 19 includes the subject matter of any one of Examples 17 or 18, and further includes a connector operatively coupled to the UAV or the dock, and an interface operatively coupled to the other of the UAV or the dock, where placement of the dock on a support surface facilitates engagement of the interface to the connector via gravity.

Example 20 includes the subject matter of any one of Examples 17 to 19, and further includes a connector operatively coupled to the UAV or the dock, and an interface operatively coupled to the other of the UAV or the dock, where placement of the dock on a support surface facilitates engagement of the interface to the connector via gravity.

Example 21 includes a method including determining whether rotors of an unmanned aerial vehicle (UAV) are moved into a rotor position or a computer position, where the rotor position corresponds to a drone mode of the UAV and the computer position corresponds to a computer mode of the UAV, and upon determining that the rotors are in the computer position, spinning the rotors to cool a body of the UAV.

Example 22 includes the subject matter of Example 21, and further includes increasing a clock speed of a processor of the UAV based on determining that rotors are in the computer position.

Example 23 includes the subject matter of any one of Examples 21 or 22, and further includes decreasing a clock speed of a processor of the UAV based on determining that rotors are in the drone position.

Example 24 includes the subject matter of any one of Examples 21 to 23, and further includes determining whether the UAV is placed in a dock.

Example 25 includes the subject matter of any one of Examples 21 to 24, and further includes detecting a temperature of a component of the UAV, and varying a rotational speed of at least one of the rotors based on the detected temperature.

From the foregoing, it will be appreciated that example methods, apparatus and articles of manufacture have been disclosed that enable a UAV or drone to be used as a personal computer. For example, examples disclosed herein enable deployment of personal computer functionality to remote areas. Examples disclosed herein also enable rotors that are used in flight of the UAV to cool electronics (e.g., computing processors or heatsinks attached thereto) when the UAV is converted to personal computer use. Examples disclosed herein also enable onboard analysis and/or processing of data captured by a UAV without necessitating a need to offload the data to another personal computer.