WO2018080385A1

WO2018080385A1 - Robotic vehicle having power cord awareness

Info

Publication number: WO2018080385A1
Application number: PCT/SE2017/051049
Authority: WO
Inventors: Rajinder Mehra; Tommy Olsson
Original assignee: Husqvarna Ab
Priority date: 2016-10-28
Filing date: 2017-10-25
Publication date: 2018-05-03
Also published as: SE540069C2; SE1651427A1

Abstract

A robotic vehicle (20) including processing circuitry (110) configured to receive power cord-information indicative of position-data of at least a portion of a power cord (28) operably coupled to the robotic vehicle (20), tension-data of at least a portion of the power cord (28) operably coupled to the robotic vehicle (20), or both; receive operating parameters for a predetermined minimum operating dimension between the robotic vehicle (20) and the power cord (28), for a predetermined maximum tension of the power cord (28), or both; determine an actual operating dimension between the robotic vehicle (20) and the power cord (28), an actual tension of the power cord (28), or both; and prevent operation of the robotic vehicle (20) when the actual operating dimension between the robotic vehicle (20) and the power cord (28) meets or exceeds the predetermined minimum operation dimension, when the actual tension of the power cord (28) meets or exceeds the predetermined maximum tension of the power cord (28).

Description

ROBOTIC VEHICLE HAVING POWER CORD AWARENESS

TECHNICAL FIELD

[0001] Example embodiments generally relate to robotic devices and, more particularly, relate to a robotic device that is configured to have power cord awareness and mitigate or prevent operation of the robotic vehicle in a manner that damages or destroys the power cord attached to the robotic vehicle.

BACKGROUND

[0002] Construction equipment includes such devices as saws, drills, generators, nail guns, demolition robots, and the like. These devices are often used to perform tasks that inherently produce debris, and they are also inherently required to be mobile. Accordingly, these devices are typically made to be relatively robust and capable of handling difficult work in hostile environments, while balancing the requirement for mobility. However, these devices typically also include some form of working assembly that is capable of cutting work pieces, drilling holes, shoot nails or rivets, demolish structures, or the like. Thus, these devices have the capability to be sources of risk for damage to equipment or people.

[0003] The construction environment may include immense amounts of coordination for both safety and productivity purposes. In some examples, a manager, such as a foreman, may have to determine the deployment of personnel and equipment throughout a job site. The foreman may make deployment determinations based on safety concerns, preventing workers on opposing sides of a wall or floor from drilling or sawing through and injuring each other. The foreman may also make deployments based on the number or type of construction devices available at the job sight and or power supplies at the job sight. There may be a limited number of specific tools and the foreman may set priorities for the construction devices. There also may be limited battery packs and or wired power. The foreman may also maintain information for each construction device, such as location, repair status, maintenance status, or the like, this information may be used to schedule maintenance or find alternative resources when a construction tool breaks or becomes unusable for other reasons. [0004] In some construction sites, robotic devices may be particularly suited to use due to the harsh working conditions and location of strenuous tasks which may not be practical and/or safe for individuals. In such construction sites, robot vehicles, such as demolition robots, may be deployed. Demolition robots, however, may be capable causing great amounts of unintended damaged if the operator is distracted or inattentive. Demolition robots may also cause unintended damage to various structures if the demolition robot is not driven precisely in restrictive areas such as, hallways, stairwells, or the like. Moreover, it is also possible that the demolition robots could damage their own power cord.

BRIEF SUMMARY OF SOME EXAMPLES

[0005] Some example embodiments may, therefore, provide a robotic vehicle that employs a capability or capabilities for mitigating or preventing operation of the robotic vehicle in a manner that damages or destroys the power cord attached to the robotic vehicle. In this regard, the robotic vehicle may be considered to have awareness of a power cord attached thereto and via processing circuitry and/or certain power cord configurations prevent operation of the robotic vehicle in a manner that would damage or destroy the power cord. For example, the robotic vehicle may be configured to automatically detach the power cord from the robotic vehicle when the power cord experiences a predetermined tension and/or hover over or off the ground in an area proximate to the robotic vehicle so as to avoid damaging the power cord with outriggers that may be extended and retracted repeatedly during a period of operation. Such power cord awareness by the robotic vehicle, for example, may also be realized by employing a variety of sensors in the robotic vehicle and/or the power cord in conjunction with processing circuitry configured to mitigate or prevent operation of the robotic vehicle, for example based on data received from the sensors, in a manner damaging or destroying the power cord. For instance, the processing circuitry may be configured to turn off the power of the robotic vehicle when potentially unsafe and/or damaging operating conditions are realized.

[0006] In an example embodiment, a robotic vehicle (e.g., a demolition robot) is provided. The robotic vehicle may include processing circuitry configured to receive power cord- information indicative of position-data of at least a portion of a power cord operably coupled to the robotic vehicle, tension-data of at least a portion of a power cord operably coupled to the robotic vehicle, or both. The processing circuitry may also be configured to receive operating parameters for a predetermined minimum operating dimension between the robotic vehicle and the power cord, for a predetermined maximum tension of the power cord, or both, determining an actual operating dimension between the robotic vehicle and the power cord, an actual tension of the power cord, or both, and preventing operation of the robotic vehicle when the actual operating dimension between the robotic vehicle and the power cord meets or exceeds the predetermined minimum operation dimension, when the actual tension of the power cord meets or exceeds the predetermined maximum tension of the power cord.

[0007] In another example embodiment, a method of operating a robotic vehicle (e.g., a demolition robot) is provided. The method may include receiving power cord-information indicative of position-data of at least a portion of a power cord operably coupled to the robotic vehicle, tension-data of at least a portion of a power cord operably coupled to the robotic vehicle, or both; receiving operating parameters for a predetermined minimum operating dimension between the robotic vehicle and the power cord, for a predetermined maximum tension of the power cord, or both; determining, via processing circuitry, an actual operating dimension between the robotic vehicle and the power cord, an actual tension of the power cord, or both; and preventing operation of the robotic vehicle when the actual operating dimension between the robotic vehicle and the power cord meets or exceeds the predetermined minimum operation dimension, when the actual tension of the power cord meets or exceeds the predetermined maximum tension of the power cord.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

[0008] Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

[0009] FIG. 1 illustrates a robotic vehicle (i.e., a demolition robot) according to an example embodiment;

[0010] FIG. 2 illustrates a perspective view of a block diagram of a system according to an example embodiment;

[0011] FIG. 3 illustrates a block diagram of one example of onboard electronics or processing circuitry that may be used in connection with employment of an example

embodiment on robotic vehicles that may employ an example embodiment; and

[0012] FIG. 4 illustrates a block diagram of a method according to an example embodiment. DETAILED DESCRIPTION

[0013] Some example embodiments now will be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all example embodiments are shown. Indeed, the examples described and pictured herein should not be construed as being limiting as to the scope, applicability or configuration of the present disclosure. Rather, these example embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout. Furthermore, as used herein, the term "or" is to be interpreted as a logical operator that results in true whenever one or more of its operands are true. As used herein, operable coupling should be understood to relate to direct or indirect connection that, in either case, enables functional interconnection of components that are operably coupled to each other.

[0014] FIG. 1 illustrates a robotic vehicle (i.e., a demolition robot) according to an example embodiment of the present invention. As shown in FIG. 1, the robotic vehicle comprises a demolition robot 20 including a plurality of outriggers (e.g., support legs) 25 which may extend and retract to secure and/or stabilize the demolition robot prior to and/or during operation of the demolition robot 20. The outriggers 25 are illustrated as being in a fully retracted position in FIG. 1. The demolition robot 20 may further comprise caterpillar tracks 26 configured to move the robotic vehicle 20 across a variety of landscapes (e.g., debris, inclined surfaces, stairs, etc.) and a rotating tower 27. The demolition robot 20 may also include a control arm 21, which may be moved to engage a variety of working elements and/or perform a variety of work- tasks. Each of the foregoing features of the demolition robot 20 may be remotely controlled by an operator interfacing with a remote control device 19 including, for example, a first control stick 23 and a second control stick 24. The remote control device 19 may also include, although not shown, a variety of switches and/or buttons which may be used in conjunction with the control sticks 23,24 to control operation of each of the functionally operational features of the demolition robot 20. In the example embodiment illustrated in FIG. 1, the demolition robot 20 is electrically powered via an electrical power cord 28. In accordance with certain embodiments of the invention, the power cord 28 may comprise one or more position sensors and/or tension sensors 29 directly or indirectly attached onto or within the power cord 28. In accordance with certain example embodiments, the one or more position sensors and/or tension sensors may emit signal(s) (e.g., electrical signals) which may be directly or indirectly recognized by the demolition robot 20. For example, demolition robot 20 may include onboard circuitry (as illustrated in FIG. 2) including processing circuitry configured to perform a variety of tasks to provide awareness of the location of the power cord relative to the demolition robot 20, particularly relative to moving elements of the demolition robot 20 such as the outriggers 25 and the control arm 21, and/or the amount of tension placed on the power cord 28.

[0015] In this regard, FIG. 2 illustrates a generic example of a system in which one or more robotic vehicles (e.g., demolitions robots) may utilize a network for the performance of preventing operation of the demolition robots in a manner that would damage or destroy (e.g., by smashing, cutting, pulling, pinching, etc.) the power cord attached thereto or to another networked robotic vehicle according to an example embodiment. As shown in FIG. 2, a system 10 according to an example embodiment may include one or more robotic vehicles (e.g., demolitions robots 20). Notably, although FIG. 2 illustrates three (3) devices, it should be appreciated that less or many more robotic vehicles (e.g., demolitions robots 20) may be included in some embodiments and thus, the three (3) devices of FIG. 2 are simply used to illustrate a multiplicity of robotic vehicles (e.g., demolitions robots 20) and the number of robotic vehicles (e.g., demolitions robots 20) is in no way limiting to other example

embodiments. In this regard, example embodiments are scalable to inclusion of any number of robotic vehicles (e.g., demolitions robots 20) being tied into the system 10. Moreover, it should be appreciated that FIG. 2 illustrates one example embodiment in which multiple robotic vehicles (e.g., demolitions robots 20) may be operated within a community of networked robotic vehicles (e.g., demolitions robots 20) to mitigate and/or prevent operation of any of the robotic vehicles (e.g., demolitions robots 20) in a manner that would damage or destroy any of the power cords electrically connected to any of the networked robotic vehicles (e.g., demolitions robots 20). However, it should be appreciated that the architecture of various example embodiments may vary. Thus, the example of FIG. 2 is merely provided for ease of explanation of one example embodiment and should not be considered to be limiting with respect to the architecture of the system 10. Accordingly, for example, some embodiments may have specific sets or subsets of robotic vehicles (e.g., demolitions robots 20) that are associated with corresponding specific servers that belong to or are utilized by a particular organization, entity or group over a single network (e.g., network 30). However, in other embodiments, multiple different sets of robotic vehicles (e.g., demolitions robots 20) may be enabled to access other servers associated with different organizations, entities or groups via the same or a different network if so desired.

[0016] The robotic vehicles (e.g., demolitions robots 20) may, in some cases, each include sensory, computing and/or communication devices associated with the different robotic vehicles (e.g., demolitions robots 20) that belong to or are associated with an organization (e.g., a group of demolition robots equipped with a similar working element and performing the same or similar work in the same or proximate working area). For example, among the robotic vehicles (e.g., demolitions robots 20) one robotic vehicle may be associated with a first facility or location of a first organization. Meanwhile, a second robotic vehicle may be associated with a second facility or location of the first organization. As such, for example, some of the robotic vehicles (e.g., demolitions robots 20) may be associated with the first organization, while other ones of the robotic vehicles are associated with a second organization. Thus, for example, the robotic vehicles may be remotely located from each other, collocated, or combinations thereof.

However, in some embodiments, each of the robotic vehicles may be associated with individuals, locations or entities associated with different organizations or merely representing individual robotic vehicles. For example, robotic vehicles associated with a first organization may be located separately from robotic vehicles associated with a second organization and, therefore, the robotic vehicles associated with the first organization may not need to be directly networked with robotic vehicles associated with the second organization. In this regard, a single network (e.g., network 30) may, if so desired, segregate network connections between robotic vehicles of a first organization from network connections between robotic vehicles of a second organization.

[0017] Each one of the robotic vehicles (e.g., a demolition robot 20 as illustrated in FIG. 1) may include a housing inside which a power unit or motor (not shown) is housed. In some embodiments, the power unit may be an electric motor an internal combustion engine, hydraulic system, pneumatic system, combustion chamber, or the like. The robotic vehicles 20 may each further include a work assembly (e.g., control arm 21 as illustrated in FIG. 1). The work assembly may be operated via the power unit to perform construction and /or demolition operations, such as drilling, cutting, hydraulic hammering, pulverizing, or the like. The robotic vehicles may include sensors for location, device operation, orientation, or the like, as discussed below in reference to FIG. 3. Additionally or alternatively, each of the robotic vehicles may include location sensors and/or a user interface, as discussed below in reference to FIG. 3. [0018] In an example embodiment, each of the robotic vehicles (e.g., demolitions robots 20) may include onboard circuitry 22 which may include or otherwise be embodied as a computing device (e.g., a computer, access terminal, processing circuitry, or the like) capable of

communication with the network 30. As such, for example, each one of the robotic vehicles may include (or otherwise have access to) memory for storing instructions or applications for the performance of various functions and a corresponding processor for executing stored instructions or applications and a corresponding processor or processing circuitry. Each one of the robotic vehicles may also include software and/or corresponding hardware (e.g., the onboard circuitry 22) for enabling the performance of the respective functions of the clients as described below. In an example embodiment, one or more of the robotic vehicles may be configured to execute applications or functions implemented via software for enabling a respective one of the robotic vehicles to communicate with the network 30 for requesting and/or receiving information and/or services via the network 30 and/or for providing data to other devices via the network 30. The information or services receivable at the robotic vehicles may include deliverable components (e.g., downloadable software to configure the onboard circuitry 22 of the demolition robots 20, or information for consumption or utilization at the onboard circuitry 22 of the demolition robots 20).

[0019] The network 30 may be a data network, such as a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN) (e.g., the Internet), and/or the like, which may couple the robotic vehicles to devices such as processing elements (e.g., personal computers, server computers or the like) and/or databases. Communication between the network 30, the robotic vehicles and the devices or databases (e.g., servers) to which the robotic vehicles are coupled may be accomplished by either wired or wireless communication mechanisms and corresponding communication protocols.

[0020] In an example embodiment, other devices to which the robotic vehicles (e.g., demolitions robots 20) may be coupled via the network 30 may include a server network 32 including one or more application servers (e.g., application server 40), and/or a database server 42, which together may form respective elements of the server network 32. Although the application server 40 and the database server 42 are each referred to as "servers," this does not necessarily imply that they are embodied on separate servers or devices. As such, for example, a single server or device may include both entities and the database server 42 could merely be represented by a database or group of databases physically located on the same server or device as the application server 40. The application server 40 may include monitoring circuitry 44 (which may be similar to or different from the onboard circuitry 22 of the robotic vehicles 20) that may include hardware and/or software for configuring the application server 40 to perform various functions. As such, for example, the application server 40 may include processing logic and memory enabling the application server 40 to access and/or execute stored computer readable instructions for performing various functions.

[0021] In an example embodiment, one function that may be provided by the application server 40 (e.g., via the monitoring circuitry 44) may be the provision of services relating to preventing operation of the robotic vehicles 20 in a manner that would damage or destroy a power cord associated with one of the robotic vehicles, as will be described in greater detail below. For example, the application server 40 may be configured to receive data from the robotic vehicles (e.g., demolitions robots 20) and process the data, for example in conjunction with data received from a power cord, to prevent movement of the robotic vehicles that may damage or destroy the power cord as described herein. Thus, for example, the onboard circuitry 22 may be configured to send the data (e.g., position data associated with location of the robotic vehicle and/or portions of the robotic vehicle) to the application server 40 for the application server 40 to prevent operation of the robotic vehicle in locations or circumstances that may damage or destroy the power cord. In some embodiments, for example, the application server 40 may be configured to provide robotic vehicles with instructions (e.g., for execution by the onboard circuitry 22) for taking prescribed actions (e.g., powering down, stopping movement in a particular direction, etc.) when the positioning and/or operation of the robotic vehicle encroaches upon predetermined levels associated with, for example, tension levels placed on the power cord and/or an actual minimum operating dimensions between the robotic vehicle and the power cord.

[0022] Accordingly, in some example embodiments, data from robotic vehicles (e.g., demolitions robots 20) may be provided to and analyzed at the application server 40 (e.g., via the monitoring circuitry 44) to identify or define an actual operating dimension between the robotic vehicle and the power cord 28 and/or the actual tension placed on the power cord 28 (e.g., in real time or at a later time). The actual operating dimension between the robotic vehicle and the power cord 28 and/or the actual tension placed on the power cord 28 may be associated with particular actions undertaking or currently in process by the robotic vehicle, and these particular actions (e.g., extending or retracting outriggers 25, transiting a work area in a particular direction, movement of the control arm, etc.) may be halted and/or reversed to prevent or mitigate destruction or damage to the power cord 28. For example, operations of extending or retracting the outriggers 25 may inadvertently snag or grab the power cord 28 and exert a damaging level of tension, weight or force on the power cord 28 due to the movement of the outriggers 25. The increased level of tension placed on the power cord 28 may be correlated with the movement of the outriggers 25, and the application server 40 may provide the robotic vehicle (e.g., demolition robot) 20 with instructions (e.g., for execution by the onboard circuitry 22) to stop movement of the outriggers 25 and/or move the outriggers 25, at least partially, in an opposite direction to prevent increased tension on the power cord 28 and/or reduce tension placed on the power cord 28. In a similar manner, movement of the robotic vehicle across a work area may inadvertently dangerously approach the power cord 28 and/or exert a damaging level of tension on the power cord 28. In this regard, the application server 40 may provide the robotic vehicle (e.g., demolition robot 20) with instructions (e.g., for execution by the onboard circuitry 22) to stop movement of the robotic vehicle or alternatively, at least partially (e.g., 1-4 inches), move the robotic vehicle in an opposite direction to prevent increased tension on the power cord and/or reduce tension placed on the power cord.

[0023] In some example embodiments, data from robotic vehicles (e.g., demolition robots 20) may be provided to and analyzed at the application server 40 (e.g., in real time) to identify or define operating conditions related to, for example, actual operating dimensions between the robotic vehicle and power cord 28 and/or an actual tension placed on the power cord 28. Based at least on part on such data, for example, operating conditions may be associated or correlated to actions to be taken by the application server 40 in response to a future detection of such operating conditions. The application server 40 (e.g., via the monitoring circuitry 44) may then provide a report or warning or may direct action to be taken at one or more robotic vehicles when an occurrence of the particular operating conditions is detected in the future. For example, recognition of the simultaneous retracting and/or extending of the outriggers 25 and increasing tension placed on the power cord 28 may be quickly recognized and in response to these recognized operating conditions, the operation of the outriggers 25 may be halted as discussed above. [0024] In still other embodiments, the robotic vehicles themselves may analyze data for detection operating conditions (e.g., actual tension placed on the power cord 28 and actual operating dimension between the robotic vehicle and the power cord 28 using the onboard circuitry 22) and define and/or take action responsive to detecting the operating conditions. Thus, the robotic vehicles may operate in some cases independently of the network 30 and the application server 40. However, in some cases, the application server 40 may be used to provide defined operating conditions and/or predetermined operating parameters to the robotic vehicles and the robotic vehicles may be configured thereafter to operate to detect operating conditions relative to predetermined operating parameters, and take actions correspondingly.

[0025] In some embodiments, for example, the onboard circuitry 22 and/or the monitoring circuitry 44 (e.g., positioning circuitry) may include or have access to stored instructions for handling activities associated with practicing example embodiments as described herein. As such, in some embodiments, the onboard circuitry 22 and/or the monitoring circuitry 44 (e.g., positioning circuitry) may include software and/or hardware for enabling the onboard circuitry 22 and/or the monitoring circuitry 44 to communicate via the network 30 for the provision and/or receipt of information associated with performing activities as described herein.

[0026] FIG. 3 illustrates a block diagram showing components that may be associated with embodiment of the onboard circuitry 22 and/or the monitoring circuitry 44 according to an example embodiment. As shown in FIG. 3, the onboard circuitry 22 and/or the monitoring circuitry 44 (e.g., positioning circuitry) may include or otherwise be embodied as a power-cord- awareness device 100. The power-cord-awareness device 100 may include processing circuitry 110 of an example embodiment as described herein. In this regard, for example, the power-cord- awareness device 100 may utilize the processing circuitry 110 to provide electronic control inputs to one or more functional units of the onboard circuitry 22 and/or the monitoring circuitry 44 and to process data generated by the one or more functional units regarding various indications of device activity (e.g., operational parameters and/or location information) relating to a corresponding one of the demolition robots 20. In some cases, the processing circuitry 110 may be configured to perform data processing, control function execution and/or other processing and management services according to an example embodiment of the present invention. In some embodiments, the processing circuitry 110 may be embodied as a chip or chip set. In other words, the processing circuitry 110 may comprise one or more physical packages (e.g., chips) including materials, components and/or wires on a structural assembly (e.g., a baseboard). The structural assembly may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon. The processing circuitry 110 may therefore, in some cases, be configured to implement an

embodiment of the present invention on a single chip or as a single "system on a chip." As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.

[0027] In an example embodiment, the processing circuitry 110 may include one or more instances of a processor 112 and memory 114 that may be in communication with or otherwise control a device interface 120 and, in some cases, a user interface 130. As such, the processing circuitry 110 may be embodied as a circuit chip (e.g., an integrated circuit chip) configured (e.g., with hardware, software or a combination of hardware and software) to perform operations described herein. However, in some embodiments, the processing circuitry 110 may be embodied as a portion of an on-board computer on a device being monitored (e.g., one of the robotic vehicles 20), while in other embodiments, the processing circuitry 110 may be embodied as a remote computer that monitors device activity for one or more devices.

[0028] The user interface 130 may be in communication with the processing circuitry 110 to receive an indication of a user input at the user interface 130 and/or to provide an audible, visual, tactile or other output to the user. As such, the user interface 130 may include, for example, a display, one or more levers, switches, buttons or keys (e.g., function buttons), and/or other input/output mechanisms. In an example embodiment, the user interface 130 may include one or a plurality of lights, a display, a speaker, a tone generator, a vibration unit and/or the like.

[0029] The device interface 120 may include one or more interface mechanisms for enabling communication with other devices (e.g., sensors of the sensor network 140, or functional units of the power-cord-awareness device 100). In some cases, the device interface 120 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 sensors in communication with the processing circuitry 110 via internal communication systems of the power-cord- awareness device 100. In some cases, the device interface 120 may further include wireless communication equipment (e.g., a one way or two way radio) for at least communicating information from the power-cord-awareness device 100 to a network and, in the case of a two way radio, in some cases receiving information from a network.

[0030] The processor 112 may be embodied in a number of different ways. For example, the processor 112 may be embodied as various processing means such as one or more of a microprocessor or other processing element, a coprocessor, a controller or various other computing or processing devices including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), or the like. In an example embodiment, the processor 112 may be configured to execute instructions stored in the memory 114 or otherwise accessible to the processor 112. As such, whether configured by hardware or by a combination of hardware and software, the processor 112 may represent an entity (e.g., physically embodied in circuitry - in the form of processing circuitry 110) capable of performing operations according to embodiments of the present invention while configured accordingly. Thus, for example, when the processor 112 is embodied as an ASIC, FPGA or the like, the processor 112 may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor 112 is embodied as an executor of software instructions, the instructions may specifically configure the processor 112 to perform the operations described herein.

[0031] In an example embodiment, the processor 112 (or the processing circuitry 110) may be embodied as, include or otherwise control the operation of the power-cord-awareness device 100 based on inputs received by the processing circuitry 110. As such, in some embodiments, the processor 112 (or the processing circuitry 110) may be said to cause each of the operations described in connection with the power-cord-awareness device 100 in relation to operation the power-cord-awareness device 100 relative to undertaking the corresponding functionalities associated therewith responsive to execution of instructions or algorithms configuring the processor 112 (or processing circuitry 110) accordingly.

[0032] In an exemplary embodiment, the memory 114 may include one or more non- transitory memory devices such as, for example, volatile and/or non-volatile memory that may be either fixed or removable. The memory 114 may be configured to store information, data, applications, instructions or the like for enabling the processing circuitry 110 to carry out various functions in accordance with exemplary embodiments of the present invention. For example, the memory 114 could be configured to buffer input data for processing by the processor 112. Additionally or alternatively, the memory 114 could be configured to store instructions for execution by the processor 112. As yet another alternative or additional capability, the memory 114 may include one or more databases that may store a variety of data sets responsive to input from the sensor network 140 (e.g., position sensors from a power cord, tension sensors from a power cord, etc.), the power-cord-awareness device 100, or any other functional units that may be associated with the power-cord-awareness device 100. Among the contents of the memory 114, applications may be stored for execution by the processor 112 in order to carry out the functionality associated with each respective application. In some cases, the applications may include instructions for recognition of an actual operating dimension between the robotic vehicle and the power cord 28, an actual tension of the power cord 28, or both relative to operating parameters related to a predetermined minimum operating dimension between the robotic vehicle and the power cord 28, a predetermined maximum tension of the power cord 28, or both. The applications may also include instruction for initiation of one or more responses (e.g., powering down the robotic vehicle, halting movement of the robotic vehicle, etc.) to the recognition of the actual operation conditions relative to the operating parameters.

[0033] In some embodiments, the processing circuitry 110 may communicate with electronic components and/or sensors of a sensor network 140 (e.g., sensors that indicate positioning of the power cord 28, sensors that indicate the tension placed on the power cord 28, sensors that measure variable values related to device operational parameters like RPM, temperature, oil pressure, seat presence, and/or the like, and/or sensors that measure device movement employing movement sensor circuitry) of the demolition robot 20 via the device interface 120. In one embodiment, sensors of the sensor network 140 of one or more ones of the demolition robots 20 may communicate with the processing circuitry 110 of a remote monitoring computer via the network 30 and the device interface 120 using wireless communication or by downloading data that is transferred using a removable memory device that is first in communication with the robotic vehicle 20 to load data indicative of device activity, and is then (e.g., via the device interface 120) in communication with the remote monitoring computer (e.g., associated with the monitoring circuitry 44).

[0034] In some embodiments, the processing circuitry 110 may communicate with movement sensor circuitry of the demolition robot 20 (e.g., when the processing circuitry 110 is implemented as the onboard circuitry 22), or may receive information indicative of device location from movement sensor circuitry of one or more devices being monitored (e.g., when the processing circuitry is implemented as monitoring/positioning circuitry 44). The movement sensor circuitry may include movement sensors (e.g., portions of the sensor network 140) such as one or more accelerometers and/or gyroscopes, or may include global positioning system (GPS) or other location determining equipment.

[0035] The movement sensor circuitry (if employed) may be configured to provide indications of movement of the demolition robot 20 based on data provided by the one or more accelerometers and/or gyroscopes, and/or based on GPS or local position determining

capabilities. In other words, the movement sensor circuitry may be configured to detect movement of the demolition robot 20 based on inertia-related measurements or other location determining information. The indications may be provided to the power-cord-awareness device 100 along with or instead of operation parameter data to enable the power-cord-awareness device 100 to select and/or define instruction sets for initiation in response to a determination that a predefined operating condition is detected (e.g., the tension of the power cord 28 has met or exceeded a predetermined maximum tension level). In some embodiments, the movement sensor circuitry may utilize a carrier wave signal (e.g., the carrier associated with GPS satellite transmissions) in order to employ real time kinematic (RTK) satellite navigation techniques. RTK-GPS may employ phase measurements of the carrier wave (without regard for the content of such signals) in order to improve the accuracy of GPS positioning by employing carrier-phase enhancement. In some example embodiments, the movement sensor circuitry may include orientation sensors, configured to detect the orientation of a demolition robot, particularly the control arm 21 or outriggers 25 of the demolition robot relative the determined location of the power cord 28.

[0036] In one example embodiment, a robotic vehicle comprises processing circuitry (e.g., onboard circuitry 22 as shown in FIG. 2), as discussed herein, configured to receive power cord- information indicative of position-data of at least a portion of a power cord operably coupled to the robotic vehicle (e.g., demolition robot 20). Additionally or alternatively, the processing circuitry may be configure to receive power cord-information indicative of tension-data of at least a portion of a power cord 28 operably coupled to the robotic vehicle. In this regard, the processing circuitry may be configured to receive power cord-information indicative of position- data and tension data. In one example embodiment, the processing circuitry may be configured to also receive operating parameters for a predetermined minimum operating dimension between the robotic vehicle and the power cord 28, for a predetermined maximum tension of the power cord 28, or both. In this regard, the predetermined minimum operating dimension between the robotic vehicle and the power cord and/or the predetermined maximum tension of the power cord 28 can be input by an operator either remotely or locally at the robotic vehicle. The

predetermined minimum operating dimension, for example, may comprise a minimum distance between the robotic vehicle (or portion thereof) and the power cord 28 that should be maintained to facilitate operation of the robotic vehicle without a risk of damaging or destroying the power cord. Upon recognition of the actual operating dimension being the same or smaller (e.g., 1 foot) than the predetermined minimum operating dimension (e.g., 3 feet) may indicate an unsafe operating conditions. For example, the predetermined minimum operating dimension may be input or defined as being from 1 to 6 feet or from 6 inches to 3 feet. The processing circuitry may also be configured to determine an actual operating dimension between the robotic vehicle and the power cord 28, an actual tension of the power cord 28, or both. The robotic vehicle, according to such an example embodiment, may be further configured to prevent operation of the robotic vehicle when the actual operating dimension between the robotic vehicle and the power cord meets or exceeds the predetermined minimum operation dimension, when the actual tension of the power cord meets or exceeds the predetermined maximum tension of the power cord, or both. Accordingly, the processing circuitry may be further configured to compare the predetermined minimum operating dimension with the actual operating dimension, the predetermined maximum tension with the actual tension, or both. In this regard, the step or preventing operation of the robotic vehicle may be in response to recognition of unsafe operation conditions based, for example, on a comparison of the predetermined operating parameters to the actual operating dimension and actual tension placed on the power cord. Such a step, for example, may include detaching the power cord, halting movement of the robotic vehicle or portion thereof (e.g., outriggers, control arm, etc.), and turning the power off to the robotic vehicle.

[0037] In accordance with some example embodiments, the processing circuitry of the robotic vehicle may be configure to receive robotic vehicle positioning-information indicative of robotic vehicle position-data of the robotic vehicle transiting a work area at one or more locations on the work area. In this regard, the determination of the actual operating dimension between the robotic vehicle and the power cord, via the processing circuitry, may be based at least in part on the position-data of the power cord operably coupled to the robotic vehicle and the robotic vehicle position-data of the robotic vehicle. As discussed previously, the processing circuitry may be configured to continuously (e.g., in real-time) determine the actual operating dimension between the robotic vehicle and the power cord, for example, based at least in part on the position-data of the power cord operably coupled to the robotic vehicle and the robotic vehicle position-data of the robotic vehicle. In this regard, the processing circuitry may also be configured to continuously (e.g., in real-time) compare the operating conditions to the predetermined operation parameters to provide real-time prevention of operation of the robotic vehicle in a manner that may damage or destroy the power cord. The robotic vehicle, as discussed previously, may receive information and/or data either locally at the robotic vehicle or remotely. For instance, the predetermined operation parameters may be received either locally at the robotic vehicle or remotely, such as wirelessly.

[0038] In accordance with certain example embodiments, the robotic vehicle may include and/or be operably coupled to a power cord comprising one or more position sensors detectable by the robotic vehicle. In one example embodiment, for instance, the one or more position sensors located on or about the power cord may comprise a boundary wire (e.g., a single position sensor of notable length) directly or indirectly attached along a length of the power cord. In this regard, the boundary wire may emit electrical signals detectable by the robotic vehicle and define a virtual boundary for operation of the robotic vehicle, in which the robotic vehicle should not reach or cross over. In some example embodiments, the boundary wire may be attached directly or indirectly along the entire length of the power cord for from about 1% to 99% of the length of the power cord. The boundary wire may, in some example embodiments, be powered or engaged whenever the power cord is plugged into an external power source (e.g., a electrical wall outlet). Additionally or alternatively, the boundary wire may be operably coupled to an separate and independent boundary wire power source (e.g. a small battery pack separate from an electrical wall outlet).

[0039] The robotic vehicle, according to some example embodiments, may include and/or be operably coupled to a power cord comprising a plurality of local position sensors directly or indirectly attached to or within the power cord. In some example embodiments, for instance, the plurality of position sensors may comprise a plurality of discrete and independent position sensors located spaced apart from each other along a length of the power cord. Such embodiments, for example, may be desirable as damage or malfunction of a single position sensor will not place the entire power cord in increased risk of inadvertent damage due to operation of the robotic vehicle. As shown in FIG. 1, for instance, the position sensors 29 may be spaced apart from one another such that damage or malfunction to one of the position sensors does not negate the operation or functioning of the power-cord-awareness device 100 discussed above. In this regard, a plurality of discrete and spaced apart position sensors may be located from every 1 foot to every 20 feet along the length of the power cord (e.g., every 6 feet).

[0040] Additionally or alternatively to the one or more position sensors, the power cord, according to some example embodiments, may comprise one or more tension sensors (e.g., strain gauges) detectable by the robotic vehicle, for example, in a similar manner as the robotic vehicle detects the position sensors of a power cord discussed above. The one or more tension sensors may provide actual tension placed on the power cord in separate and discrete areas along the length of the power cord. In this regard, the power cord may comprise a tension sensor located from every 3 feet to every 20 feet along a length of the power cord. In some example embodiments, the power cord may include a plurality of discrete position sensors and a plurality of tension sensors located along the length of the power cord to provide a relatively detailed physical profile of the power cord in relation to both position and tension.

[0041] In one example embodiment, the processing circuitry of the robotic vehicle may be further configured to receive dimensional warning parameters for a predetermined warning dimension between the robotic vehicle and the power cord. In this regard, the processing circuitry may also be configured to trigger a warning if the actual operating dimension between the robotic vehicle and the power cord exceeds the predetermined warning dimension. For example only, the predetermined warning dimension between the robotic vehicle and the power cord may be set by a user (e.g., remotely or locally) to be 6 feet. When the robotic vehicle or a portion thereof reaches or moves closer than 6 feet to the power cord, the processing circuitry may initiate a warning in response to recognition that the robotic vehicle or portion thereof has reached, exceeded, or passed the predetermined warning dimension between the robotic vehicle and the power cord. Such example embodiments may provide the operator of the robotic vehicle a warning (e.g., visual, audio, vibration, or any combination thereof) in sufficient time to take a corrective action to prevent the robotic vehicle from moving closer to the power cord and automatically taking action, such as powering off. In some example embodiments, the warning may comprise a vibrating the operators control device alone or in combination with visual and/or audio alarms.

[0042] Additionally or alternatively, the processing circuitry of the robotic vehicle may be further configured to receive tension warning parameters for a predetermined warning tension of the power cord. In this regard, the processing circuitry may also be configured to trigger a warning if the actual tension of the power cord meets, exceeds, or passes the predetermined warning tension.

[0043] For example only, the predetermined warning tension of the power cord may be set by a user (e.g., remotely or locally) to be 50 Newtons. When the actual tension on the power cord or a portion of the power cord reaches or exceeds 50 Newtons, the processing circuitry may initiate a warning in response to recognition that the tension placed on the power cord or portion thereof has reached, exceeded, or passed the predetermined warning tension of the power cord. Such example embodiments may provide the operator of the robotic vehicle a warning (e.g., visual, audio, vibration, or any combination thereof) in sufficient time to take a corrective action to prevent the additional tension being placed onto the power cord or a portion thereof and automatically taking action, such as powering off. In some example embodiments, the warning may comprise a vibrating the operators control device alone or in combination with visual and/or audio alarms.

[0044] In some example embodiments, the robotic vehicle may include and/or be operably coupled to a power cord, in which the power cord comprises a proximate end configured to releasably attach to a socket of the robotic vehicle and a distal end configured to releasably attach to a power supply (e.g., an electrical wall socket). In some example

embodiments that the proximate end and/or the distal end may comprise a magnetic connection configured to detach when the predetermined maximum tension is placed on the power cord. For example, the proximate end may comprise the magnetic connection configured to detach from the socket of the robotic vehicle when the predetermined maximum tension is placed on the power cord. In some example embodiments, the magnetic strength may be less than the predetermined maximum tension to ensure timely detachment of the power cord in the event that an undesirable force (e.g., tension) is placed on the power cord. Additionally or alternatively, the proximate end of the power cord may comprises a proximate end construction that is stronger (e.g., ability to withstand more weight, tension, etc.) than a distal end construction of the distal end of the power cord. In one example embodiment, for instance, the proximate end

construction may comprise a larger diameter than the distal end construction. For instance, the proximate end construction may comprise a protective sheath overlying (e.g., encircling) the proximate end of the power cord. In this regard, the protective sheath may comprise a rigid or flexible protective sheath. Rigid sheaths, for example, may be configured to withstand an external pressure of force applied to the outside of the power cord, while sparing the electrical connection within the power cord from being subjected to the external pressure or force.

Flexible sheaths, for example, may comprise an isolative material such as a rubber or elastomeric material configured to absorb most (or all) of an external pressure or force applied to the outside of the power cord. For example, the flexible sheath may compress to absorb pressure or force in an manner similar to a spring. In some example embodiments, for instance, the proximate end construction (e.g., increased thickness, different material of construction, protective sheath, or combinations thereof) may comprise the 1 to 12 feet of the proximate end of the power cord adjacent the robotic vehicle. Additionally or alternatively, the proximate end of the power cord may comprise a proximate end construction that is configured to hover off the ground (e.g., 1, 2, 3, or 4 feet off the ground). In one example embodiment, the proximate end construction being configured to hover off the ground may comprise a length from 1 to 6 feet and be located adjacent the robotic vehicle.

[0045] In some cases, a method of operating a robotic vehicle (e.g., a demolition robot) utilizing power-cord-awareness device 100 in relation to operation of the robotic vehicle in a manner to prevent or mitigate operation of the robotic vehicle in a manner that may damage or destroy a power cord operably coupled to the robotic vehicle or a second robotic vehicle networked with each other via a network (e.g., network 30) according to an example

embodiment may be provided. FIG. 4 illustrates a block diagram of some activities that may be associated with one example of such a method. In some embodiments, the processing circuitry 110 (which may include a processor capable of executing instructions stored in a non-transitory computer readable medium/memory) may be configured to implement a control algorithm for the robotic vehicle(s) according to the method.

[0046] In an example embodiment, the method may include receiving power cord- information indicative of position-data of at least a portion of a power cord operably coupled to the robotic vehicle, tension-data of at least a portion of a power cord operably coupled to the robotic vehicle, or both at operation 402; receiving operating parameters for a predetermined minimum operating dimension between the robotic vehicle and the power cord, for a

predetermined maximum tension of the power cord, or both at operation 404; determining, via processing circuitry, an actual operating dimension between the robotic vehicle and the power cord, an actual tension of the power cord, or both at operation 406; and preventing operation of the robotic vehicle when the actual operating dimension between the robotic vehicle and the power cord meets or exceeds the predetermined minimum operation dimension, when the actual tension of the power cord meets or exceeds the predetermined maximum tension of the power cord at operation 408. As illustrated in FIG. 4, one example embodiment the method may optionally include comparing, via processing circuitry, the predetermined minimum operating dimension with the actual operating dimension, the predetermined maximum tension with the actual tension, or both at operation 410. Operation 410 is shown in dashed lines in FIG. 4 to highlight the fact that it may be optional.

[0047] In some embodiments, the method may include additional, optional operations, and/or the operations described above may be modified or augmented. Some examples of

modifications, optional operations and augmentations are described below. In this regard, for example, in some cases, (1) receiving robotic vehicle positioning-information indicative of robotic vehicle position-data of the robotic vehicle transiting a work area at one or more locations on the work area; (2) determining the actual operating dimension between the robotic vehicle and the power cord is based at least in part on the position-data of the power cord operably coupled to the robotic vehicle and the robotic vehicle position-data of the robotic vehicle; (3) receiving the operating parameters comprises receiving the operating parameters locally at the robotic vehicle or remotely (e.g., wirelessly); (4) receiving dimensional warning parameters for a predetermined warning dimension between the robotic vehicle and the power cord and to trigger, via processing circuitry, a warning if the actual operating dimension between the robotic vehicle and the power cord exceeds the predetermined warning dimension; and (5) receiving tension warning parameters for a predetermined warning tension of the power cord and to trigger, via processing circuitry, a warning if the actual tension of the power cord exceeds the predetermined warning tension. In some method embodiments, any or all of (1) to (5) may be employed to provide power cord awareness to a robotic vehicle or robotic vehicles, which may be networked together. In an example embodiment, a robotic vehicle (e.g., a demolition robot) may be provided with processing circuitry configuring the robotic vehicle (e.g., a demolition robot) to perform any of the example embodiments as described herein.

[0048] Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are 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 exemplary embodiments in the context of certain exemplary combinations of elements and/or functions, it should be appreciated that different combinations of elements and/or functions may 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 may be set forth in some of the appended claims. In cases where advantages, benefits or solutions to problems are described herein, it should be appreciated that such advantages, benefits and/or solutions may be applicable to some example embodiments, but not necessarily all example embodiments. Thus, any advantages, benefits or solutions described herein should not be thought of as being critical, required or essential to all embodiments or to that which is claimed herein. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

THAT WHICH IS CLAIMED:

1. A robotic vehicle (20) comprising processing circuitry (110) configured to:

receive power cord-information indicative of position-data of at least a portion of a power cord (28) operably coupled to the robotic vehicle (20), tension-data of at least a portion of the power cord (28) operably coupled to the robotic vehicle (20), or both;

receive operating parameters for a predetermined minimum operating dimension between the robotic vehicle (20) and the power cord (28), for a predetermined maximum tension of the power cord (28), or both;

determine an actual operating dimension between the robotic vehicle (20) and the power cord (28), an actual tension of the power cord (28), or both; and

prevent operation of the robotic vehicle (20) when the actual operating dimension between the robotic vehicle (20) and the power cord (28) meets or exceeds the predetermined minimum operation dimension, when the actual tension of the power cord (28) meets or exceeds the predetermined maximum tension of the power cord (28), or both.

2. The robotic vehicle (20) of claim 1, wherein the processing circuitry (110) is further configured to compare the predetermined minimum operating dimension with the actual operating dimension, the predetermined maximum tension with the actual tension, or both.

3. The robotic vehicle (20) of claims 1-2, wherein the processing circuitry (110) is further configured to receive robotic vehicle positioning-information indicative of robotic vehicle position-data of the robotic vehicle (20) transiting a work area at one or more locations on the work area.

4. The robotic vehicle (20) of claim 3, wherein the actual operating dimension between the robotic vehicle (20) and the power cord (28) is based at least in part on the position- data of the power cord (28) operably coupled to the robotic vehicle (20) and the robotic vehicle position-data of the robotic vehicle (20).

5. The robotic vehicle (20) of claims 1-4, wherein receiving the operating parameters comprises receiving the operating parameters locally at the robotic vehicle (20).

6. The robotic vehicle (20) of claims 1-4, wherein receiving the operating parameters comprises receiving the operating parameters remotely.

7. The robotic vehicle (20) of claim 6, wherein receiving the operating parameters remotely comprises receiving the operating parameters wirelessly.

8. The robotic vehicle (20) of any of the preceding claims, wherein the

predetermined minimum operating dimension between the robotic vehicle (20) and the power cord (28) comprises from 6 inches to 3 feet.

9. The robotic vehicle (20) of any of the preceding claims, wherein the power cord (28) comprises one or more position sensors (29) detectable by the robotic vehicle (20).

10. The robotic vehicle (20) of claim 9, wherein the one or more position sensors (29) comprises a boundary wire directly or indirectly attached along a length of the power cord (28); wherein the boundary wire emits electrical signals detectable by the robotic vehicle (20).

11. The robotic vehicle (20) of claim 10, wherein the boundary wire is directly or indirectly attached along 1% to 99% of the length of the power cord (28).

12. The robotic vehicle (20) of claims 10-11, wherein the boundary wire is operably coupled to a boundary wire power source.

13. The robotic vehicle (20) of claim 9, wherein the one or more position sensors (29) comprise a plurality of discrete and independent position sensors located spaced apart from each other along a length of the power cord (28).

14. The robotic vehicle (20) of any of the preceding claims, wherein the power cord (28) comprises one or more tension sensors detectable by the robotic vehicle (20).

15. The robotic vehicle (20) of claim 14, wherein the power cord (28) comprises a tension sensor located from every 3 feet to 20 feet along a length of the power cord (28).

16. The robotic vehicle (20) of claims 14-15, wherein the one or more tension sensors comprise strain gauges.

17. The robotic vehicle (20) of any of the preceding claims, wherein the processing circuitry is further configured to receive dimensional warning parameters for a predetermined warning dimension between the robotic vehicle (20) and the power cord (28) and to trigger a warning if the actual operating dimension between the robotic vehicle (20) and the power cord (28) exceeds the predetermined warning dimension.

18. The robotic vehicle (20) of any of the preceding claims, wherein the processing circuitry (110) is further configured to receive tension warning parameters for a predetermined warning tension of the power cord (28) and to trigger a warning if the actual tension of the power cord (28) exceeds the predetermined warning tension.

19. The robotic vehicle (20) of claims 17-18, wherein the warning comprises a visual warning, an audio warning, a vibrating warning, or any combination thereof.

20. The robotic vehicle (20) of claim 19, wherein the vibrating warning comprises vibrating a control device (19) operated by a user.

21. The robotic vehicle (20) of claim 20, wherein the control device (19) comprises a remote control.

22. The robotic vehicle (20) of any of the preceding claims, wherein the power cord (28) comprises a proximate end configured to releasably attach to a socket of the robotic vehicle (20) and a distal end configured to releasably attach to a power supply.

23. The robotic vehicle (20) of claim 22, wherein the proximate end configured to releasably attach to a socket of the robotic vehicle (20) comprises a magnetic connection configured to detach from the socket of the robotic vehicle (20) when the predetermined maximum tension is placed on the power cord (28).

24. The robotic vehicle (20) of claim 23, wherein the magnetic connection comprises a magnetic strength being less than the predetermined maximum tension.

25. The robotic vehicle (20) of any of the preceding claims, wherein the power cord (28) comprises a proximate end configured to releasably attach to a socket of the robotic vehicle (20) and a distal end configured to releasably attach to a power supply; wherein the proximate end comprises a proximate end construction that is stronger than a distal end construction of the distal end.

26. The robotic vehicle (20) of claim 25, wherein the proximate end construction comprises a larger diameter than the distal end construction.

27. The robotic vehicle (20) of claims 25-26, wherein the proximate end construction comprises a protective sheath overlying the proximate end of the power cord (28).

28. The robotic vehicle (20) of claim 27, wherein the protective sheath comprise a rigid protective sheath.

29. The robotic vehicle (20) of claims 25-28, wherein the proximate end construction comprises from 1 to 6 feet of the proximate end of the power cord (20).

30. The robotic vehicle (20) of any of the preceding claims, wherein the power cord (28) comprises a proximate end configured to releasably attach to a socket of the robotic vehicle (20) and a distal end configured to releasably attach to a power supply; wherein the proximate end comprises a proximate end construction that is configured to hover off the ground.

31. The robotic vehicle (20) of claim 30, wherein the proximate end construction being configured to hover off the ground comprises enabling from 1 to 6 feet of the proximate end of the power cord (28) adjacent the robotic vehicle (20) to hover off the ground.

32. The robotic vehicle (20) of any of the preceding claims, wherein the robotic vehicle (20) comprises a demolition robot.

33. The robotic vehicle (20) of claim 32, wherein the demolition robot comprises a plurality of outriggers (25) and a control arm (21).