The present disclosure relates to a robotic device capable of engaging with a cleaning environment (e.g., bathtub, shower, etc.) to allow for easier cleaning of the bottom surface and at least one sidewall.
Robotic device may be used to clean a surface in various situations. Exemplary known cleaning robotic systems may include a cleaning device configured to engage one or more surfaces. Generally, though, these known robotic devices focus one engaging the one or more surfaces via features located on only one surface (e.g., a bottom surface) thereof. Such conventional systems thus do not provide a manner for cleaning one or more differently oriented surfaces in a simultaneous manner, let alone doing so with feature positioned on a single surface. Thus, a need exists for improved robotic devices providing enhanced coverage and performance.
Various embodiments of the present disclosure describe and comprise robotic devices, cleaning apparatuses, mobile devices, and corresponding systems, devices, components, and methods related to robotic devices.
For example, in certain embodiments, a robotic device for cleaning a surrounding environment is provided. In these embodiments, the robotic device may include a body portion that may define at least a top surface, a bottom surface, and/or a continuous sidewall surface. In these and/or other embodiments, the sidewall surface may be defined by a perimeter of the body portion. In these and/or other embodiments, the robotic device may further comprise a drive system that includes at least two drive elements configured to propel the robotic device within the surrounding environment. In these and/or other embodiments, the at least two drive elements may extend a distance beneath the bottom surface. In these and/or other embodiments, the robotic device may further comprise two or more bottom brushes having a primary axis of each brush that extends below the bottom surface and extends at least partially beyond the at least two drive elements to engage the surrounding environment. In these and/or other embodiments, the robotic device may further comprise a continuous opening that extends around the sidewall surface. In these and/or other embodiments, the robotic device may further comprise a pair of sidewall brushes that extend from the robotic device. In these and/or other embodiments, the pair of sidewall brushes sidewall brushes may be configured to oscillate along the continuous opening until making contact with each other.
In various embodiments, the robotic device may further comprise a storage compartment. In certain embodiments, the storage compartment may store the pair of sidewall brushes and may be defined between the top surface and the bottom surface at an end of the robotic device. In some embodiments, the pair of sidewall brushes may move from a stored position to an active position, relative to the storage compartment, upon an activation of a cycle. In some embodiments, the pair of sidewall brushes may be positioned in a vertical manner relative to the storage compartment while in the active position.
In various embodiments, the pair of sidewall brushes may oscillate horizontally relative to the continuous opening of the robotic device. In some embodiments, the pair of sidewall brushes may oscillate individually from each other from a first linear position to a second linear position along the continuous opening. In some embodiments, a first sidewall brush may oscillate along a first side of the robotic device, and a second sidewall brush may oscillate along a second side of the robotic device, wherein the first side and the second side are relative to the sidewall surface. In some embodiments, the first linear position may be defined by the storage compartment at a first end of the robotic device. In some embodiments, the second linear position may be defined by the linearly opposite end of the robotic device relative to the storage compartment.
In various embodiments, the robotic device may further comprise a bumper. In certain embodiments, the bumper may extend around the body portion to protect a finish of the surrounding environment.
In various embodiments, the robotic device may further comprise a controller and at least one sensor. In certain embodiments, the controller and the at least one sensor may be configured to detect a location of the robotic device within the surrounding environment and communicate the location to guide the robotic device. In some embodiments, the controller may further comprise a processor. In at least one embodiments, the processor may be configured to communicate with the controller to direct the robotic device. In these and/or other embodiments, the controller, directed by the processor, may control at least one oscillating function of the pair of sidewall brushes. In some embodiments, the controller may further comprise a communication element that communicates with at least one electronic device.
In various embodiments, the robotic device may further comprise at least one power switch. In certain embodiments, the at least one power switch activates the robotic device and/or selects a cycle type.
For example, in certain embodiments, a robotic system for cleaning a surrounding environment is provided. In these embodiments, the robotic system may include a robotic device. In some embodiments, the robotic device may include a body portion that may define at least a top surface, a bottom surface, and/or a continuous sidewall surface. In these and/or other embodiments, the sidewall surface may be defined by a perimeter of the body portion. In these and/or other embodiments, the robotic device may further comprise a drive system that includes at least two drive elements configured to propel the robotic device within the surrounding environment. In these and/or other embodiments, the at least two drive elements may extend a distance beneath the bottom surface. In these and/or other embodiments, the robotic device may further comprise two or more bottom brushes having a primary axis of each brush that extends below the bottom surface and extends at least partially beyond the at least two drive elements to engage the surrounding environment. In these and/or other embodiments, the robotic device may further comprise a continuous opening that extends around the sidewall surface. In these and/or other embodiments, the robotic device may further comprise a pair of sidewall brushes that extend from the robotic device. In these and/or other embodiments, the pair of sidewall brushes sidewall brushes may be configured to oscillate along the continuous opening until making contact with each other. In these and/or other embodiments, the robotic system may further comprise a distributed network that may communicate with one or more electronic devices and with the robotic system.
For example, in certain embodiments, a method of operating a robotic device is provided. In these embodiments, the method may include selective, via a power switch, a power type and/or a cycle type. In these and/or other embodiments, the method may further comprise causing an activation of a cycle for the robotic device to begin cleaning a surrounding environment. In these and/or other embodiments, the robotic device may comprise a body portion that may define at least a top surface, a bottom surface, and/or a continuous sidewall surface. In these and/or other embodiments, the sidewall surface may be defined by a perimeter of the body portion. In these and/or other embodiments, the robotic device may further comprise a drive system that includes at least two drive elements configured to propel the robotic device within the surrounding environment. In these and/or other embodiments, the at least two drive elements may extend a distance beneath the bottom surface. In these and/or other embodiments, the robotic device may further comprise two or more bottom brushes having a primary axis of each brush that extends below the bottom surface and extends at least partially beyond the at least two drive elements to engage the surrounding environment. In these and/or other embodiments, the robotic device may further comprise a continuous opening that extends around the sidewall surface. In these and/or other embodiments, the robotic device may further comprise a pair of sidewall brushes that extend from the robotic device. In these and/or other embodiments, the pair of sidewall brushes sidewall brushes may be configured to oscillate along the continuous opening until making contact with each other. In these and/or other embodiments, the robotic device may further comprise at least one power switch that may activate the robotic device and/or select a cycle type.
In various embodiments, the cycle type may define the running time of the robotic device and the cleaning type. In some embodiments, the depressing of the at least one power switches a predetermined number of time selects at least one cycles. In some embodiments, the selecting of different cycles and/or run times may be based on the number of depressions of the power switch.
In various aspects, a robotic device for cleaning a surrounding environment comprises a body portion that defines at least a top surface, a bottom surface, and a continuous sidewall surface. The sidewall surface may be defined by a perimeter of the body portion. The robotic device may comprise a drive system that includes at least two drive elements configured to propel the robotic device within the surrounding environment. The at least two drive elements may extend a distance beneath the bottom surface. The robotic device may comprise two or more bottom brushes having a primary axis of each brush that extends below the bottom surface and extend at least partially beyond the at least two drive elements to engage the surrounding environment. The robotic device may comprise a continuous opening that extends around the sidewall surface, wherein the continuous opening is defined along the sidewall surface between the top surface and the bottom surface. The continuous opening may extend purely horizontally around an entirety of the perimeter of the body portion. The robotic device may comprise at least one sidewall brush that extends from the body portion and is configured to travel along the continuous opening and relative to the top surface and the bottom surface of the body portion. Each of the at least one sidewall brush may be configured to travel along the continuous opening with the assistance of a sidewall drive mechanism that comprises a connection rod.
In various examples, the at least one sidewall brush is positioned in a vertical manner.
In various examples, the at least one sidewall brush is configured to travel horizontally relative to the continuous opening of the robotic device.
In various examples, a first sidewall brush of the at least one sidewall brush is configured to travel along a first side of the robotic device, and a second sidewall brush of the at least one sidewall brush is configured to travel along a second side of the robotic device, wherein the first side and the second side are relative to the sidewall surface.
In various examples, the robotic device comprises a bumper that extends around the body portion, wherein the bumper protects a finish of the surrounding environment.
In various examples, the robotic device comprises a controller and at least one sensor to detect a location of the robotic device in the surrounding environment and communicate the location to guide the robotic device.
In various examples, the controller further comprises a processor configured to communicate with the controller of the robotic device.
In various examples, the controller, directed by the processor, controls at least one traveling function of the at least one sidewall brush.
In various examples, the continuous opening extends circumferentially around the sidewall surface and the at least one sidewall brush is configured to travel circumferentially along the continuous opening.
In various examples, the at least one sidewall brush is positioned in a vertical manner, and wherein the at least one sidewall brush is configured to remain in the vertical position as it travels along the continuous opening.
In various examples, the at least one sidewall brush extends vertically 18 inches tall.
In various examples, the at least one sidewall brush extends vertically at least 6 inches and up to 18 inches tall.
In various examples, each of the at least one sidewall brush comprises a plurality of bristles that are configured to contact a sidewall surface of a tub or shower when the robotic device is cleaning the surrounding environment.
In various examples, the plurality of bristles are configured to receive a cleaning solution from a reservoir to deliver the cleaning solution to the sidewall surface of the tub or shower.
In various examples, the robotic device is for cleaning a bottom surface and at least one sidewall of a bathtub or a shower.
In various examples, the at least one sidewall brush is configured to move from a first position to a second position, wherein the first position is at a back of the robotic device and the second position is at a front of the robotic device.
In various examples, the first position is at least ninety degrees from the second position relative to a center of the robotic device.
In various examples, the continuous opening extends circumferentially around the sidewall surface and the at least one sidewall brush is configured to travel circumferentially along the continuous opening.
In various examples, the at least one sidewall brush is configured to move from a first position to a second position, wherein the first position is at a back of the robotic device and the second position is at a front of the robotic device.
In various examples, each of the at least one sidewall brush is positioned in a vertical manner, and wherein each of the at least one sidewall brush is configured to remain in the vertical position as it travels along the continuous opening from the first position to the second position.
In various examples, each of the at least one sidewall brush extends vertically at least 6 inches and up to 18 inches tall.
In various examples, the robotic device comprises comprising a vertical center shaft and a large gear. Each of the at least one sidewall brush may be coupled to a respective connection rod of a respective sidewall drive mechanism. Each connection rod may be configured to pivot around the vertical center shaft. Each sidewall drive mechanism may further comprises a motor and a small gear that is coupled to the motor and is configured to be rotatable by the motor. The small gear may be positioned such that gear teeth of the small gear mesh with gear teeth of the large gear. Each sidewall drive mechanism may be configured to orbit a respective sidewall brush around the body portion of the robotic device when its small gear is rotated by its motor.
In various examples, each sidewall drive mechanism further comprises a second motor that is coupled to a distal end of the respective connection rod, wherein the second motor is configured to rotate the respective sidewall brush on an axis that extends through the sidewall brush.
The above summary is provided merely for purposes of summarizing some example embodiments to provide a basic understanding of some aspects of the present disclosure. Accordingly, it will be appreciated that the above-described embodiments are merely examples and should not be construed to narrow the scope or spirit of the present disclosure in any way. It will be appreciated that the scope of the present disclosure encompasses may potential embodiments in addition to those here summarized, some of which will be further described below. Other features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.
The following drawings are illustrations of a particular embodiment of the present disclosure and therefore do not limit the scope of the present disclosure. The drawings are not necessarily drawn to scale and are intended for use in conjunction with explanation in the following description.
Various embodiments of the present invention will be described in a more detailed manner hereinafter with reference to the accompanying drawings, in which some, embodiments of the invention are shown. Reference numbers refer to like elements throughout the drawings. Multiple embodiments of the current invention may be embodied in different forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements.
As used herein, terms such as “front,” “rear,” “top,” etc. are used for explanatory purposes in the examples provided below to describe the relative positions of certain components or portions of components. As used herein, the term “or” is used in both the alternative and conjunctive sense, unless otherwise indicated. The term “along,” and similarly utilized terms, means near or on, but not necessarily requiring directly on an edge or other referenced location. The terms “approximately,” “generally,” and “substantially” refer to within manufacturing and/or engineering design tolerances for the corresponding materials and/or elements unless otherwise indicated. The use of such terms is inclusive of and is intended to allow independent claiming of specific values listed. Thus, use of any such aforementioned terms, or similarly interchangeable terms, should not be taken to limit the spirit and scope of embodiments of the present invention. As used in the specification and the appended claims, the singular form of “a,” “an,” and “the” include plural references unless otherwise stated. The terms “includes” and/or “including,” when used in the specification, specify the presence of stated feature, elements, and/or components; it does not preclude the presence or addition of one or more other features, steps, operations, elements, components, and/or groups thereof.
As used herein, the phrases “in one embodiment,” “according to one embodiment,” “in some embodiments,” and the like generally refer to the fact that the particular feature, structure, or characteristic following the phrase may be included in at least one embodiment of the present disclosure. Thus, the particular feature, structure, or characteristic may be included in more than one embodiment of the present disclosure such that these phrases do not necessarily refer to the same embodiment. As used herein, the terms “example,” “exemplary,” and the like are used to “serving as an example, instance, or illustration.” Any implementation, aspect, or design described herein as “example” or “exemplary” is not necessarily to be construed as preferred or advantageous over other implementations, aspects, or designs. Rather, use of the terms “example,” “exemplary,” and the like are intended to present concepts in a concrete fashion.
As used herein, the term “battery-powered” is intended to refer to devices capable of engaging a battery to receive electrical power (e.g., wall outlet, or the like) in at least some circumstances. The term “battery-powered” is intended to be interpreted inclusively and includes devices capable of engaging a battery as well as devices capable of being plugged in to a non-battery power source in at least some circumstances.
Aspects of the present disclosure may be implemented as computer program products that comprises articles of manufacture. Such computer program products may include one or more software components including, for example, applications, software objects, methods, data structure, and/or the like. A software component may be coded in any of a variety of programming languages. An illustrative programming language may be a lower-level programming language such as an assembly language associated with a particular hardware architecture and/or operating system platform/system.
Other example of programming languages included, but are not limited to, a macro language, a shell or command language, a job control language, a script language, a database query, or search language, and/or report writing language. In one or more example embodiments, a software component comprising of instructions in one of the foregoing examples of programming languages may be executed directly by an operating system or other software component without having to be first transformed into another form. A software component may be stored as a file or other data storage methods. Software components of a similar type or functionally related may be stored together such as, for example, in a particular directory, folder, or library. Software components may be static (e.g., pre-established, or fixed) or dynamic (e.g., created or modified at the time of execution).
Additionally, or alternatively, aspects of the present disclosure may be implemented as a non-transitory computer-readable storage medium storing applications, programs, program modules, scripts, source code, program code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, and/or the like (also referred to herein as executable instructions, instructions for execution, computer program products, program code, and/or similar terms used herein interchangeably). Such non-transitory computer-readable storage media may include all computer-readable media (including volatile and non-volatile media).
In one aspect, a non-volatile readable storage may include a floppy disk, flexible disk, hard disk, solid-state storage (SSS) (e.g., a solid-state drive (SSD), solid state card (SSC), solid state module (SSM), enterprise flash drive, magnetic tape, and/or the like. A non-volatile computer-readable storage medium may also include compact disc read only memory (CD-ROM), compact disc-rewritable (CD-RW), digital versatile disc (DVD), Blu-ray disc (BD), any other non-transitory optical medium, and/or the like. Such a non-volatile computer-readable storage medium may also include read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory (e.g., Serial, NAND, NOR, and/or the like), multimedia memory cards (MMC), secure digital (SD) memory cards, SmartMedia cards, CompactFlash (CF) cards, Memory Sticks, and/or the like. Further, a non-volatile computer-readable storage medium may also include conductive-bridging random access memory (CBRAM), phase-change random access memory (PRAM), ferroelectric random-access memory (FeRAM), non-volatile random-access memory (NVRAM), magnetoresistive random-access memory (MRAM), resistive random-access memory (RRAM), Silicon-Oxide-Nitride-Oxide-Silicon memory (SONOS), floating junction gate random access memory (FJG RAM), Millipede memory, racetrack memory, and/or the like.
In one aspect, a volatile computer-readable storage medium may include random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), fast page mode dynamic random access memory (FPM DRAM), extended data-out dynamic random access memory (EDO DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), double data rate type two synchronous dynamic random access memory (DDR2 SDRAM), double data rate type three synchronous dynamic random access memory (DDR3 SDRAM), Rambus dynamic random access memory (RDRAM), Twin Transistor RAM (TTRAM), Thyristor RAM (T-RAM), Zero-capacitor (Z-RAM), Rambus in-line memory module (RIMM), dual in-line memory module (DIMM), single in-line memory module (SIMM), video random access memory (VRAM), cache memory (including various levels), flash memory, register memory, and/or the like. It will be appreciated that where aspects are described to use a computer-readable storage medium, other types of computer-readable storage media may be substituted for or used in addition to the computer-readable storage media described above.
Aspects of the present disclosure are described below with reference to block diagrams and flowchart illustrations. Thus, it should be understood that each block of the block diagrams and flowchart illustrations may be implemented in the form of a computer program product, a solely hardware aspect, a combination of hardware and computer program products, and/or apparatus, systems, computing devices, computing entities, and/or the like carrying out instructions, operations, steps, and similar words used interchangeably (e.g., the executable instructions, instructions for execution, program code, and/or the like) on a computer-readable storage medium for execution. For example, retrieval, loading, and execution of code may be performed sequentially such that one instruction is retrieved, loaded, and executed at a time. In some embodiments, retrieval, loading, and/or execution may be performed in parallel such that multiple instructions are retrieved, loaded, and/or executed together. Thus, such aspects can produce specifically configured machines performing the steps or operations specified in the block diagrams and flowchart illustrations. Accordingly, the block diagrams and flowchart illustrations support various combinations of aspects for performing the specified instructions, operations, or steps.
As should be appreciated, various aspects of the present disclosure may also be implemented as methods, apparatuses, systems, computing devices, computing entities, and/or the like. As such, aspects of the present disclosure may take the form of a data structure, apparatus, system, computing device, computing entity, and/or the like executing instructions stored on a computer-readable storage medium to perform certain steps or operations. Thus, aspects of the present disclosure may also take the form of an entirely hardware aspect, an entirely computer program product aspect, and/or an aspect that comprises combination of computer program products and hardware performing certain steps or operations.
The figures are provided to illustrate some examples of the invention described. The figures are not to limit the scope of the present embodiment of the invention or the appended claims. Aspects of the example embodiment are described below with reference to example applications for illustration. It should be understood that specific details, relationships, and methods are set forth to provide a full understanding of the example embodiment. One of ordinary skill in the art recognize the example embodiment can be practice without one or more specific details and/or with other methods.
The present disclosure relates to a robotic device capable of cleaning a bathtub and/or shower to allow for an ergonomic cleaning function for users who may be handicapped, lost use of upper body strength, elderly users, etc. Various devices and methods are also provided. In some example embodiments, the robotic device disclosed herein may be used to clean a plurality of surfaces of a bathtub and/or shower. In various embodiments, the robotic device may comprise a driving mechanism and a cleaning mechanism. The driving mechanism may be configured to move the robotic device throughout the cleaning environment (e.g., bathtub, shower, etc.). Typical robotic devices are configured to only clean a bottom surface within the cleaning environment. This requires users, in the case of the cleaning environment being a bathtub and/or shower, to still manually clean one or more additional surfaces manually. The present disclosure solves these problems and other via the robotic device disclosed herein.
In some instances, various robotic devices clean a plurality of surfaces simultaneously within a surrounding environment. The robotic device according to various embodiments of the present disclosure may be able to engage with and/or clean a plurality of cleaning surfaces simultaneously. For example, the robotic device may be configured to deploy one or more sidewall brushes upon the activation of a cleaning cycle. The one or more sidewall brushes may be configured to engage with at least one sidewall of the cleaning environment while one or more bottom brushes of the robotic device engages the bottom surface of the cleaning environment.
As described herein, the invention includes a robotic device that utilizes at least one sidewall brush and at least one bottom brush to allow for easy cleaning of a surrounding environment (e.g., bathtub, shower, bathroom, kitchen, etc.).
In various embodiments, the sidewall brushes 204 may comprise a plurality of bristles 205 (
In various embodiment, the sidewall brushes 204 oscillate horizontally along an opening, described in detail herein after, with the assistance of rotating and/or oscillating mechanism 330. The sidewall brushes 204 may oscillate horizontally relative to the sidewall surface 105 of the robotic device 10. In various embodiments, the sidewall brushes 204 may rotate simultaneously while oscillating along the opening. In other embodiments, the sidewall brushes 204 may rotate while at a first linear position and/or at a second linear position.
With further reference to
With further reference to
With further reference to
With still further reference to
With further reference to
With further reference to
With even further reference to
With reference to
With reference to
With reference to
Referring to
Each assembly 341 may include a connection rod 202. Each connection rod 202 may be pivotably coupled to a vertical center shaft 207 that may be positioned in a center of the robotic device 10. For example, each connection rod 202 may include at least one bearing 206a (
Each assembly 341 may include a vertical distal shaft 208, which may be pivotably connected to the respective connection rod 202. For example, each connection rod 202 may include at least one bearing 206b that allows the vertical distal shaft 208 to pivot relative to the connection rod 202. Each vertical distal shaft 208 may be coupled to a motor 209, which may be an electric motor. The motor 209 may be configured to rotate the distal shaft 208. Each distal shaft 208 may be rigidly coupled to a small gear 343. As such, rotation of the distal shaft 208 by the motor 209 may cause rotation of the small gear 343.
Rotation of the small gear 343 may cause the small gear 343 to orbit around the large gear 344 (e.g., rotate circumferentially around the large gear 344). The circumferential movement of the small gear 343 may cause the vertical distal shaft 208, the motor 209, the connection rod 202, and the sidewall brush 204 to pivot around an axis defined by the center shaft 207. Stated differently, rotation of the small gear 343 may cause the respective sidewall brush 204 to oscillate along the opening 203 of the robotic device 10. For example, rotation of the small gear 343 in a clockwise direction by the motor may cause the respective sidewall brush 204 to orbit around the body portion 102 of the robotic device 10 in a clockwise direction, as denoted by arrow C in
As will be appreciated, each sidewall brush 204 may be controlled independently. As such, a first sidewall brush 204a may move clockwise while a second sidewall brush 204b moves counterclockwise. In various examples, a first sidewall brush 204a may move clockwise while a second sidewall brush 204b also moves clockwise. Each sidewall brush 204 may completely orbit around the body portion, such that it rotates more than 360 degrees around the body portion 102 of the robotic device 10.
Referring to
In various examples, rotation of the motor at the distal end of the connection rod 202 may cause the respective sidewall brush 204 to rotate, as denoted by arrow R in
The term “circuitry” should also be understood, in some embodiments, to include software for configuring the hardware. For example, in some embodiments, “circuitry” may include processing circuitry, storage media, network interfaces, input/output devices, and the like. In some embodiments, such as in examples where circuitry is included with controller 400 may provide or supplement the functionality of particular circuitry. For example, the processor 410 may provide processing functionality, the memory 440 may provide storage functionality, the communications element 420 may provide network interface functionality, and the like.
In some embodiments, the controller component 400 can be or comprise a printed circuited board (PCB). In some examples, the controller component 400 (e.g., PCB) can further comprise one or more of a full bridge motor driver, a sensor, one or more thermal sensors, one or more user interfaces, one or more protection circuits, configuration management circuitry, a wireless interface, sensing element circuitry (e.g., image sensor circuitry), an interface connector, power control circuitry, gate driver circuitry and/or the like.
The processing circuitry 410 can be embodied as means including one or more microprocessors with accompanying digital signal processor(s), one or more processor(s) without an accompanying digital signal processor, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits such as, but not limited to, an application specific integrated circuit (ASIC) or field programmable gate array (FPGA), or some combination thereof. Accordingly, although illustrated in
In various embodiments, the controller 400 may be configured to communicate with a robotic system 402 via wireless external communication networks using any of a variety of protocols, such as embedded sim (eSIM), remote sim provisioning (RSP), general packet radio service (GPRS), Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 200 (CDMA200), CDMA200 1× (1×RTT), Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Evolution-Data Optimized (EVDO), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), IEEE 802.11 (Wi-Fi), Wi-Fi Direct, 802.16 (WiMAX), ultra-wideband (UWB), IR protocols, NFC protocols, RFID protocols, IR protocols, ZigBee protocols, Z-Wave protocols, 6LoWPAN protocols, Wibree, Bluetooth protocols, wireless universal serial bus (USB) protocols, and/or any other wireless protocol.
In one or more embodiments, the controller 400 may be configured to communicate via one or more communication elements 420, wherein the controller 400 may be configured to transmit operation instructions to one or more components of the robotic systems. In various embodiments, the controller 400 may be configured to communicate with the robotic system 402, wherein the controller may be configured to communicate with one or more sensors of the robotic system 402 configured to detect the location of the robotic system within the surrounding environment.
Whether configured by hardware, firmware/software methods, or by a combination thereof, the processing circuitry 410 can include an entity capable of performing operations according to embodiments of the present disclosure while configured accordingly. Thus, for example, when the processing circuitry 410 is embodied as an ASIC, FPGA or the like, the processing circuitry 410 can include specifically configured hardware for conducting one or more operations described herein. Additionally, or alternatively, when the processing circuitry 410 is embodied as an executor of instructions, such as can be stored in the memory 440, the instructions can specifically configure the processing circuitry 410 to perform one or more algorithms and operations described herein.
Thus, the processing circuitry 410 used herein can refer to a programmable microprocessor, microcomputer or multiple processor chip or chips that can be configured by software instructions (applications) to perform a variety of functions, including the functions of the various embodiments described above. In some devices, multiple processors can be provided dedicated to wireless communication functions and one processor dedicated to running other applications. Software applications can be stored in the internal memory before they are accessed and loaded into the processors. The processors can include internal memory sufficient to store the application software instructions. In many devices, the internal memory can be a volatile or nonvolatile memory, such as flash memory, or a combination thereof. The memory can also be located internal to another computing resource (e.g., enabling computer readable instructions to be downloaded over the Internet or another wired or wireless connection.
The memory 440 can include suitable logic, circuitry, and/or interfaces that are adapted to store a set of instructions that is executable by the processing circuitry 410 to perform predetermined operations. Additionally, or alternately, the memory 440 can be configured to store data/information, application programs, instructions, etc., so that the controller component 400 can execute various functions according to the embodiments of the present disclosure. For example, in at least some embodiments, the memory 440 is configured to cache input data for processing by the processing circuitry 410. Thus, in at least some embodiments, the memory 440 is configured to store program instructions for execution by the processing circuitry 410. The memory 440 can store information in the form of static and/or dynamic information. When the functions are executed, the stored information can be stored and/or used by the controller component 400. Example memory embodiments can include, but are not limited to, a hard disk, random access memory, cache memory, read only memory (ROM), erasable programmable read-only memory (EPROM) & electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, a compact disc read only memory (CD-ROM), digital versatile disc read only memory (DVD-ROM), an optical disc, circuitry configured to store information, or some combination thereof. In an example embodiment, the memory 440 can be integrated with the processing circuitry 410 on a single chip, without departing from the scope of the disclosure.
The communication element 420 can be implemented as any apparatus included in a circuit, hardware, a computer program product, or a combination thereof, which is configured to receive and/or transmit data from/to another component or apparatus. The computer program product comprises computer-readable program instructions stored on a computer-readable medium (for example, the memory 440) and executed by a processor 410 (for example, the processing circuitry 410). In some embodiments, the communication element 420 (as with other components discussed herein) can be at least partially implemented as the processing circuitry 410 or otherwise controlled by the processing circuitry 410. In this regard, the communication element 420 can communicate with the processing circuitry 410, for example, through a bus. The communication element 420 can comprise, for example, antennas, transmitters, receivers, transceivers, network interface cards and/or supporting hardware and/or firmware/software and is used for establishing communication with another apparatus. The communication element 420 can be configured to receive and/or transmit any data that can be stored by the memory 440 by using any protocol that can be used for communication between apparatuses. The communication element 420 can additionally or alternatively communicate with the memory 440, the input/output element 430 and/or any other component of the processor 410, for example, through a bus.
In some embodiments, the controller 400 can comprise an input/output element 430. The input/output element 430 can communicate with the processing circuitry 410 to receive instructions input by the user and/or to provide audible, visual, mechanical, or other outputs to the user. Therefore, the input/output element 430 can comprise supporting devices, such as a keyboard, a mouse, a display, a touch screen display, microphone, audio recorder, speaker, biometric scanner, and/or other input/output mechanisms. In various embodiments, the robotic system 402 may be activated by a voice command, wherein the input/output element 430 receives the instructions and communicates the instructions to the processing circuitry 410. Alternatively, at least some aspects of the input/output element 430 can be implemented on a device used by the user to communicate with the controller 400. The input/output element 430 can communicate with the memory 440, the communication element 420 and/or any other component, for example, through a bus. One or a plurality of input/output modules and/or other components can be included in the controller 400.
In various embodiments, the input/output element 430 may communicate with one or more electronic devices (e.g., user phone, tablet, computer, etc.) to receive one or more instructions and/or commands. The instructions and/or command may determine the cycle type and/or run time of the robotic system. The input/output element 430 may further relay messages (e.g., status updates, etc.) from the controller 400 to the electronic devices. In various embodiments, the controller may be executed the received instructions and/or commands via the processing circuitry 410 and/or memory 440. The processing circuitry 410 and/or memory 440 may cause the robotic device 10 to complete at least one cycle and/or operate for a predetermined amount of time.
As described above and as will be appreciated based on this disclosure, embodiments of the present disclosure may be configured as systems, methods, apparatuses, computing devices, personal computers, servers, mobile devices, backend network devices, and the like. Accordingly, embodiments may comprise various means including entirely of hardware or any combination of software and hardware. Furthermore, embodiments may take the form of a computer program product on at least one non-transitory computer-readable storage medium having computer-readable program instructions embodied in the computer-readable storage medium (e.g., computer software stored on a hardware device). Any suitable computer-readable storage medium may be utilized including non-transitory hard disks, CD-ROMs, flash memory, optical storage devices, or magnetic storage devices.
As will be appreciated, any such computer program instructions and/or other type of code may be loaded onto a computer, processor or other programmable apparatus's circuitry to produce a machine, such that the computer, processor, or other programmable circuitry that execute the code on the machine creates the means for implementing various functions, including those described herein in connection with the components of circuitry.
In various embodiments, the controller 400 may be configured to control the location of the robotic device 10, control the cycle type of the robotic device 10, control the cycle time of the robotic device 10, control the location of the robotic device 10, etc. In various embodiments, the controller 400 may be further configured to collect location data regarding the location of the robotic device 10, collect path data of the robotic device 10, cleaning data of the robotic device 10, and/or the like.
In some embodiments, the processor 501 (and/or coprocessor or any other processing circuitry assisting or otherwise associated with the processor) may be in communication with the memory 502 via a bus for passing information among components of, for example, a user device 500. The memory 502 is non transitory and may include, for example, one or more volatile and/or non-volatile memories or some combination thereof. In other words, for example, the memory 502, may be a storage device (e.g., a computer readable storage medium). The memory 502 may be configured to store information, data, content application instruction and/or the like for enabling an apparatus (e.g., user device 500) to carry out various functions in accordance with example embodiments of the present disclosure. Although illustrated in
Memory 502 may be configured to store information, data, application instructions and/or the like for enabling circuitry to carry out various function in accordance with example embodiments discussed herein. In an example embodiment, processor 501 is configured to execute instructions stored in the memory 502 or otherwise accessible to the processor 501. Alternatively or additionally, the processor 501 may be configured to execute hard coded functionalities. As such, whether configured by hardware or software methods or by a combination thereof, the processor 501, may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present disclosure. Alternatively, as in another example, when the processor 501 is embodied as an executor of software instructions, the instructions may specifically configure processor 501 to perform one or more algorithms and/or operations described herein when the instructions are executed. For example, these instructions when executed by processor 501 may cause user device 500 to perform one or more functionalities of a user device as described herein. In some embodiments, input/output circuitry 503 may in turn be in communication with processor 501 to provide an audible, visual, mechanical or other output and/or in some embodiments to receive an indication of input.
Input/output circuitry 503 may include means for performing analog to digital and/or digital to analog data conversion. Input/output circuitry 503 may include support, for example, for a display, touch screen, keyboard, button, click wheel, mouse, joystick, an image capturing device (e.g., a camera), motion sensor (e.g., accelerometer and/or gyroscope), microphone, audio recorder, speaker, biometric scanner and/or other input/output mechanisms. Input/output circuitry 503 may comprise a user interface (e.g., a teamwork user interface, an interactive team assessment interface, a team health metrics dashboard, etc.) and may comprise a web-user interface, a mobile application, a kiosk and/or the like. The processor 501 and/or other interface circuitry comprising the processor 501 may be configured to control one or more functions of a display or one or more user interface elements through computer program instruction (e.g., software and/or firmware) stored on a memory accessible to the processor 501 (e.g., memory 502, and/or the like).
In various embodiments, a user may use the input/output circuitry 503 to send one or more instructions and/or commands to the robotic system. The instructions and/or commands may comprise information regarding the selection of a cycle type and/or a run time for the robotic system. In various embodiments, the input/output circuitry 503 may be further configured to power on and/or off the robotic system.
Communications circuitry 504 may be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data from/to a network and/or any other device, circuitry or module in communication with circuitry (e.g., user device 500). In this regard, the communications circuitry 504 may include, for example, a network interface for enabling communication with a wired or wireless communication network. Communications circuitry 504 may be configured to receive and/or transmit any data that may be stored by memory 502 using protocols that may be used for communication between computing devices. For example, the communications circuitry 504 may include one or more network interface cards, antenna, transmitter, receiver, buses, switches, routers, modems and supporting hardware and/or software, and/or firmware/software, or any other device suitable for enabling communications via network. Additionally or alternatively, the communication interface may include the circuitry for interacting with the antenna to cause transmission of signal via the antenna or to handle receipt of signals received via the antenna. These signals may be transmitted by circuitry using any of a number of wireless, personal area networks (PAN) technology, such as Bluetooth V 1.0 though V 3.0, Bluetooth low energy (BLE), inferred wireless (e.g., IRDA), ultra-wide band (UWB), induction wireless transmission, and/or the like. In addition, it should be understood that these signals may be transmitted using Wi-Fi, Near Field communications (NFC), world-wide interoperability for microwave access (WiMAX), and/or other proximity-based communications protocols. Communications circuitry 504 may additionally or alternatively be in communication with the memory 502, input/output circuitry 503 and or any other component of the circuitry via a bus.
Robotic device 10 can communicate with one or more user devices 500 via a communication network 600. Communication network 600 may include any one or more wired and/or wireless communication networks including, for example, a wired or wireless local area network (LAN), personal area network (PAN), metropolitan area network (MAN), wide area network (WAN), or the like, as well as any hardware, software, and/or firmware requires for implementing the one or more networks (e.g., network routers, switches, hubs, etc.). For example, communications network 600 may include a cellular telephone, mobile broadband, long term evolution (LTE), GSM/EDGE, UMTS/HSPA, IEEE 802.11, IEEE 802.16, IEEE 802.20, Wi-Fi, dial-up, Bluetooth, and/or WiMAX network. Furthermore, the communications network 600 may include a public network, such as the Internet, a private network, such as an intranet, or combination thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to TCP/IP based networking protocols. For instance, the networking protocol may be customized to suit the needs of the robotic device 10.
With further reference to
With reference to
Many modifications and other embodiments of the present disclosure set forth herein will come to mind to one skilled in the art to which these embodiments pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Moreover, although the foregoing descriptions and the associated drawings describe example embodiments in the context of certain example combinations of elements and/or functions, it should be appreciated that different combinations of elements and/or functions can be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and/or functions than those explicitly described above are also contemplated as can be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
This application is a continuation-in-part of U.S. Nonprovisional application Ser. No. 18/183,586, filed on Mar. 14, 2023, which claims priority to U.S. Provisional Application No. 63/344,185 filed on May 20, 2022, the contents of each of which are hereby incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
20180199785 | Farmer | Jul 2018 | A1 |
20220066456 | Ebrahimi Afrouzi et al. | Mar 2022 | A1 |
Number | Date | Country |
---|---|---|
215738714 | Feb 2022 | CN |
0424229 | Apr 1991 | EP |
5787428 | Sep 2015 | JP |
2017-131355 | Aug 2017 | JP |
10-0596479 | Jul 2006 | KR |
10-2015-0042070 | Apr 2015 | KR |
Entry |
---|
International Search Report and Written Opinion for PCT/US2023/066439 (ISA/KR) mailed Aug. 22, 2023 (11 pages). |
Number | Date | Country | |
---|---|---|---|
20240366052 A1 | Nov 2024 | US |
Number | Date | Country | |
---|---|---|---|
63344185 | May 2022 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 18183586 | Mar 2023 | US |
Child | 18775283 | US |