ROBOTIC STABILIZATION MECHANISMS AND RELATED METHODS

BRIEF DESCRIPTION OF DRAWINGS

The accompanying drawings illustrate a number of example embodiments and are a part of the specification. Together with the following description, these drawings demonstrate and explain various principles of the present disclosure.

FIG. 1 is a graphical representation of an example operating environment, including a powerline, in which various example embodiments may be employed, according to at least one embodiment of the present disclosure.

FIG. 2 is a block diagram of an example robotic system for installing cable along a powerline, according to at least one embodiment of the present disclosure.

FIG. 3 is a perspective view of an example robotic system for installing cable along a powerline, according to at least one embodiment of the present disclosure.

FIG. 4 is a side view of an example robotic system that may install a segment of cable about a powerline, where the robotic system is in a payload retracted configuration (e.g., a normal operating mode), according to at least one embodiment of the present disclosure.

FIG. 5 is a side view of the robotic system of FIG. 4 with the payload subsystem in a payload extended configuration (e.g., an obstacle avoidance mode), according to at least one embodiment of the present disclosure.

FIGS. 6A-6C are simplified end views of an example robotic system that uses lateral gripper movement for stabilization, according to at least one embodiment of the present disclosure.

FIG. 7 is a flow diagram of an example method of obstacle avoidance, according to at least one embodiment of the present disclosure.

FIG. 8 is a flow diagram of an example method of stabilizing a robot mounted to a powerline, according to at least one embodiment of the present disclosure.

FIG. 9 is a flow diagram of an example method of stabilizing a robot mounted to a powerline, according to at least one additional embodiment of the present disclosure.

FIG. 10 is a block diagram of an example robotic system for installing a cable on a powerline, according to at least one embodiment of the present disclosure.

FIG. 11 is a block diagram of an example stabilization system employable within the robotic system of FIG. 10 to balance the robotic system in an unstable equilibrium configuration (e.g., a payload extended configuration), according to at least one embodiment of the present disclosure.

Throughout the drawings, identical reference characters and descriptions indicate similar, but not necessarily identical, elements. While the example embodiments described herein are susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and will be described in detail herein. However, the example embodiments described herein are not intended to be limited to the particular forms disclosed. Rather, the present disclosure covers all modifications, equivalents, and alternatives falling within this disclosure.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Robotic devices may be employed to install a cable (e.g., fiber optic cable or another material) onto preexisting power infrastructure, such as overhead powerline conductors (also referred to herein as “powerlines”) for electrical power transmission and distribution lines, by way of helically wrapping the cable about the powerline. Such an installation may benefit from the use of the preexisting right-of-way and corresponding infrastructure (e.g., power conductors, electrical towers or poles, and so on) associated with the electrical power distribution system. Robotic devices traveling along powerline conductors may also be used for inspection of the powerline conductors. Such a robotic device may include, in some examples, a drive subsystem that causes the robotic device to travel along the powerline (e.g., between towers or poles) while a rotation subsystem of the device helically wraps the fiber optic cable or other materials about the powerline.

While translating along a powerline during cable installation or inspection of the powerline, robotic devices may encounter one or more obstacles (e.g., insulators, taps, and the like), especially along powerlines of electrical distribution systems. In such cases, human operators may intervene to temporarily remove and then reattach the robotic device to allow the robotic device to continue to install the cable on the powerline and/or inspect the powerline beyond the encountered obstacle.

The present disclosure is generally directed to robotic systems for travelling along powerlines and associated methods. As will be explained in greater detail below, embodiments of the present disclosure may stabilize the robotic system while the system is in an unstable equilibrium configuration to facilitate obstacle avoidance during a cable installation process and/or inspection procedure, thus potentially reducing the amount of human intervention required to allow the robotic device to proceed along the powerlines. Consequently, for this reason and others described below, fiber or other material “make ready” costs (e.g., costs incurred in preparing a utility powerline for installation of cable and subsequently installing the cable) may be significantly reduced.

Stabilization mechanisms of the present disclosure may include at least one gripper mounted to the robotic system. The gripper may be configured to grasp a powerline. A controller may be configured to control a lateral position of the gripper, and an inertial measurement unit (“IMU”) may be configured to sense lateral movement and/or axial rotation of the robotic system. The controller may control the lateral position of the gripper based on data from the IMU.

Features from any of the embodiments described herein may be used in combination with one another in accordance with the general principles described herein. These and other embodiments, features, and advantages will be more fully understood upon reading the following detailed description in conjunction with the accompanying drawings.

The following will provide, with reference to FIGS. 1-11, detailed descriptions of systems and methods for stabilizing a robotic system in an unstable equilibrium configuration to facilitate installation of cable on a powerline. A brief description of an example operating environment in which various embodiments of systems and methods for installing cable may operate is provided in connection with FIG. 1. Example robotic systems for installing cable on a powerline are discussed in conjunction with FIGS. 2-6. In association with FIG. 7, an example method of obstacle avoidance is described. Example methods of stabilization are described with reference to FIGS. 8 and 9. An example robotic system and an associated example stabilization system are discussed in connection with FIGS. 10 and 11, respectively.

FIG. 1 is a graphical representation of an example operating environment 100 in which various embodiments disclosed herein may be utilized. As depicted in the example of FIG. 1, the operating environment 100 may include an electrical power transmission or distribution system having a plurality of utility poles 102 carrying multiple powerlines 101. Examples of powerlines 101 may include stranded cables, but the powerlines 101 are not restricted to such embodiments. While any number of powerlines 101 may be carried via the utility poles 102, two powerlines 101 are illustrated in FIG. 1 for visual simplicity. In some examples, the powerlines 101 are mechanically coupled to the utility poles 102 via insulators 104, although other types of components (e.g., taps, standoffs, etc.) may be employed in various embodiments. While specific reference is made herein to the utility poles 102, any type of utility pole, H-frame, lattice tower, or other type of pole or tower that carries or supports one or more powerlines 101 may be included and covered in various embodiments of the operating environment 100 discussed herein. Additionally, the powerlines 101 may include one or more phase conductors, ground wires, static wires, or other conductors supported by the utility poles 102, towers, or the like.

Also shown in FIG. 1 is a cable 112 (e.g., a fiber optic cable or another material to be helically wrapped about the powerline 101) aligned with, and mechanically coupled to, the powerline 101. In some embodiments, the cable 112 may be helically wrapped about the powerline 101, such as by way of a human-powered or electrically powered robotic device. However, other physical relationships between the powerline 101 and the cable 112 are also possible. While only one cable 112 is depicted in FIG. 1, multiple powerlines 101 employing the same utility poles 102 may each have a corresponding cable 112 or multiple cables 112 attached or otherwise coupled thereto.

As depicted in FIG. 1, the cable 112 may be secured to the powerline 101 via one or more cable clamps 106. In some examples where the cable 112 includes a fiber optic cable, the cable 112 may follow a powerline 101 associated with a particular phase of the power being transmitted, or the cable 112 may alternate between two or three different phases. Moreover, each cable 112 may carry one or more optical fibers for facilitating communication within and across the operating environment 100.

Additionally, FIG. 1 illustrates an optical fiber splice case 108 that, in some embodiments, splices together corresponding ends of optical fibers of the cable 112. For example, relatively long stretches (e.g., multiple-kilometer spans) of cable 112 that may be coupled to the powerline 101 may be mechanically coupled together, thermally fused together, or otherwise coupled in the optical fiber splice case 108, which may include optical couplers, amplifiers, and/or other components to facilitate transmission of optical data signals from one span of the cable 112 to the next.

Additionally, in some embodiments, the optical fiber splice case 108 may include wireless access points and other networking components (e.g., for communication with Internet of Things (IoT) devices, smart grid sensors (e.g., voltage sensors, current sensors, and the like), and user access networks). Moreover, the optical fiber splice case 108 may include optical, electromagnetic, and other types of sensors to measure powerline conditions; environmental sensors for measuring temperature, humidity, and so on; video cameras for surveillance; and the like. To power such components, the optical fiber splice case 108 may also include solar cells and/or batteries. In some examples, such as that shown in FIG. 1, the optical fiber splice case 108 may be attached to, or positioned on or near, the powerline 101, as opposed to being mounted on a lower portion of the utility pole 102, thus potentially eliminating the use of a phase-to-ground transition that otherwise may be coupled with each length of the cable 112 to provide electrical isolation from the powerline 101.

FIG. 2 is a block diagram of an example robotic system 200 for installing cable (e.g., the cable 112, such as a fiber optic cable or another material) along an overhead powerline (e.g., the powerline 101). As depicted in FIG. 2, the robotic system 200 may include a drive subsystem 202, a stabilization subsystem 204, an extension subsystem 206, a rotation subsystem 208, and/or a payload subsystem 210. In some embodiments, FIG. 2 provides a general representation of how the subsystems 202-210 are mechanically coupled to each other, although other examples may possess alternative connection arrangements.

In some embodiments, the drive subsystem 202 may translate the robotic system 200 along the powerline 101. Also, in some examples, the extension subsystem 206 may mechanically couple the rotation subsystem 208 to the drive subsystem 202 and selectively extend the rotation subsystem 208, along with the payload subsystem 210, away from the drive subsystem 202 and/or the powerline 101 to avoid obstacles (e.g., insulators 104) along the powerline 101. The rotation subsystem 208, in some examples, may rotate the payload subsystem 210, which may in turn carry a segment of the cable 112, about the powerline 101 while the drive subsystem 202 translates along the powerline 101 such that the segment of the cable 112 is helically wrapped about the powerline 101.

The stabilization subsystem 204 may include one or more stabilization components (e.g., one or more thrusters, gyroscopes, gripper movement mechanisms, inertial measurement units (IMUs), controllers, processors, or the like) that may help attain or maintain a desired position of the robotic system 200 relative to the powerline 101. As described in greater detail below, the desired position may be directly above the powerline 101 (e.g., with a center of gravity of the robotic system 200 directly above the powerline 101). Further, in some examples, the stabilization components may be employed at least during times when the extension subsystem 206 is extending the rotation subsystem 208 (and, consequently, the payload subsystem 210) away from (e.g., vertically above) the powerline 101, such as to avoid an obstacle.

FIG. 3 is a perspective view of an example robotic system 300 for installing cable (e.g., fiber optic cable or another material) along a powerline. The robotic system 300 may include a drive subsystem 302, a stabilization subsystem 304, an extension subsystem 306, a rotation subsystem 308, and a payload subsystem 310.

The drive subsystem 302 may be configured to drive the robotic system 300 along a powerline (e.g., the powerline 101) as the rotation subsystem 308 rotates the payload subsystem 310 to deploy a cable (e.g., fiber optic cable or another material) along and around the powerline. The drive subsystem 302 may be implemented in a variety of ways. For example, the drive subsystem 302 may include one or more rollers, grippers, actuators, conveyers, pulleys, etc., that may be arranged and operated to move the robotic system 300 along the powerline. In the example shown in FIG. 3, the drive subsystem 302 may include grippers 312 and rollers 314 that are configured to clamp onto the powerline and to drive the robotic system 300 along the powerline. The rollers 314 may be powered and/or unpowered. The grippers 312 may be mounted on a gripper frame element 316, and the rollers 314 may be mounted on a roller frame element 318.

The grippers 312 may be laterally (e.g., perpendicular to the powerline) movable along a gripper rail 320 affixed to the gripper frame element 316. The rollers 314 may be laterally movable along a roller rail 322 affixed to the roller frame element 318. The roller frame element 318, and consequently the roller rail 322 and the rollers 314, may be axially (e.g., parallel to the powerline) movable along a frame rail 324 relative to other portions of the robotic system 300. The drive subsystem 302 may include one or more grippers 312 and/or rollers 314 in a first end portion (e.g., to the left in the perspective of FIG. 3) of the robotic system 300 and one or more grippers 312 and/or rollers 314 in a second, opposite end portion (e.g., to the right in the perspective of FIG. 3) of the robotic system 300.

During operation, the grippers 312 may grip the powerline to stabilize the robotic system 300, such as during an obstacle avoidance maneuver. To engage with the powerline, the grippers 312 may be moved from a retracted (e.g., outward) position inward toward the powerline along the gripper rail 320. To drive the robotic system 300 along the powerline, at least one of the rollers 314 may be engaged with the powerline and may be caused to rotate. The rollers 314 may be translated axially along the frame rail 324 during an obstacle avoidance maneuver to keep the rollers 314 in contact with the powerline for stability. The rollers 314 may also be disengaged and moved laterally outward to avoid obstacles. After the obstacle is passed by the rollers 314, the rollers 314 may then be moved back into position to engage with the powerline for continued driving of the robotic system 300 along the powerline.

The stabilization subsystem 304 may be configured to stabilize the robotic system 300 along the powerline as the robotic system 300 is driven along the powerline and/or during an obstacle avoidance maneuver. The stabilization subsystem 304 may be implemented in a variety of ways. For example, the stabilization subsystem 304 may include upper actuators 326 (e.g., thrusters, fans, gyroscopes, etc.) that are positioned to be above the powerline, at least during certain obstacle avoidance maneuvers. As shown in FIG. 3, the stabilization subsystem 304 may include four upper actuators 326, although other embodiments may include a different number of upper actuators 326. The upper actuators 326 may be configured to force air laterally away from the robotic system 300, resulting in an opposing force against a frame of the robotic system 300. The upper actuators 326 may be configured to be selectively driven (e.g., activated, deactivated, driven at different speeds, driven at different rotational directions, etc.) to stabilize a rolling of the robotic system 300, such as about the powerline.

The robotic system 300 may, at least during some operations (e.g., during an obstacle avoidance maneuver), have a center of gravity that is vertically above the powerline. This may cause the robotic system 300 to be unstable when the robotic system 300 is supported by the powerline. For example, if the center of gravity of the robotic system 300 deviates to a side (e.g., due to wind or operational movements) and the center of gravity is not directly above the powerline, the robotic system 300 may tend to roll about the powerline. The stabilization subsystem 304 may be configured to counteract such rolling instabilities.

The upper actuators 326 may be positioned away from the powerline to be able to apply a rotational force to the robotic system 300. For example, the upper actuators 326 may be above the center of gravity of the robotic system 300 during an obstacle avoidance maneuver. Thus, as the center of gravity moves out of alignment with the powerline and the robotic system 300 begins to roll, at least one the upper actuators 326 may be driven to force air in the direction of the rolling motion to force the robotic system back into a stable position with the center of gravity directly above the powerline.

In some examples, at least some of the upper actuators 326 may be mounted to a portion of the frame that may be extended (e.g., raised) by the extension subsystem 306. Thus, as the extension subsystem 306 is activated to raise a portion of the robotic system 300 (e.g., the payload subsystem 310), such as to avoid an obstacle, at least some of the upper actuators 326 may also be raised. This may enable the upper actuators 326 to apply a greater torque to the robotic system 300 corresponding to a greater instability that may occur when a center of gravity of the robotic system 300 is increasingly higher than the powerline. In additional examples, at least some of the upper actuators 326 may be positioned on the frame to be above the powerline, but may be mounted to a fixed section of the frame (e.g., a portion of the frame that is not raised by the extension subsystem 306).

The upper actuators 326 may also be configured to roll the robotic system 300 about the powerline to reposition the robotic system 300 relative to the powerline. For example, during normal operation in which a cable is deployed along the powerline, the robotic system 300 may be inverted compared to the orientation shown in FIG. 3 to translate along the powerline in a stable position (e.g., with a center of gravity below the powerline). When an obstacle to be avoided, such as an insulator supporting the powerline from below, is detected along a bottom of the powerline, the upper actuators 326 may be operated to rotate the robotic system 300 about the powerline to attain the orientation shown in FIG. 3. In this orientation, the center of gravity of the robotic system 300 may be above the powerline and may therefore be in an unstable position. The upper actuators 326 may be operated to maintain the robotic system 300 in this unstable position throughout an obstacle avoidance maneuver.

In some embodiments, the stabilization subsystem 304 may also include lower actuators 328 (e.g., thrusters, fans, gyroscopes, etc.). The lower actuators 328 may be positioned on the frame of the robotic system 300 to be closer to the powerline than the upper actuators 326 (e.g., at a same vertical level as the powerline). The lower actuators 328 may be positioned and configured to be selectively driven to stabilize a sway of the robotic system 300. For example, due to the flexibility of the powerline, the robotic system 300 and the powerline may tend to laterally sway, such as in response to wind or operational movements of the robotic system 300. The lower actuators 328 may be configured to counteract the swaying by forcing air in a direction of the sway, resulting in a force that pushes back against the swaying motion.

As noted above, the robotic system 300 may be normally operated in an inverted orientation compared to the orientation shown in FIG. 3. In some examples, the lower actuators 328 may also be actuated to assist in rotating the robotic system 300 about the powerline to position the robotic system 300 in the pose (e.g., orientation) shown in FIG. 3.

The extension subsystem 306 may be configured to move at least the payload subsystem 310 to avoid obstacles. The extension subsystem 306 may be implemented in a variety of ways. For example, the extension subsystem 306 may include extension rails 330 along which the payload subsystem 310 may be extended (e.g., raised or lowered, depending on the pose of the robotic system 300). An extension actuator 332 (e.g., a servo motor, a piston, etc.) may be used to extend the payload subsystem 310 along the extension rails 330.

The rotation subsystem 308 may be configured to rotate the payload subsystem 310 to enable the payload subsystem 310 to wrap cable around the powerline as the robotic system 300 progresses along the powerline. The rotation subsystem 308 may be implemented in a variety of ways. For example, the rotation subsystem 308 may include a rotation actuator (e.g., a motor, a gear, pulleys, belts, etc.) that is operatively coupled to the payload subsystem 310.

The payload subsystem 310 may be configured to house cable (e.g., fiber optic cable or another material) for deployment along the powerline. The payload subsystem 310 may be implemented in a variety of ways. For example, the payload subsystem 310 may include a spool of cable within a payload housing 340. In some embodiments, the payload housing 340 may generally have a U-shape, with an opening that can be positioned to extend around the powerline.

While operating in a cable deployment mode, the robotic system 300 may be moved along a powerline by the drive subsystem 302. Simultaneously, the rotation subsystem 308 may rotate the payload subsystem 310. The cable within the payload subsystem 310 may be deployed from the payload subsystem 310 and wrapped around the powerline. During operation in the cable deployment mode, the stabilization subsystem 304 may maintain the robotic system 300 in a desired (e.g., upright) orientation.

While operating in an obstacle avoidance mode, the rotation subsystem 308 may stop rotating the payload subsystem 310 and the extension subsystem 306 may extend (e.g., lift) the payload subsystem 310 enough to avoid contacting the obstacle. The stabilization subsystem 304 may be used to maintain the robotic system in a desired (e.g., upright) orientation. The drive subsystem 302 may be used to move the robotic system 300 past the obstacle, after which the extension subsystem 306 may retract (e.g., lower) the payload subsystem 310 back into its initial position to deploy cable along the powerline. The rotation subsystem 308 may resume rotating the payload subsystem 310 about the powerline and the drive subsystem 302 may continue to drive the robotic system along the powerline.

As noted above, during cable deployment, the robotic system 300 may be operated in an inverted orientation compared to the view of FIG. 3 to improve stability. During an obstacle avoidance maneuver, the robotic system 300 may be rotated about the powerline into the position shown in FIG. 3. In some examples, the position of the center of gravity of the robotic system 300 may be manipulated to facilitate rotation of the robotic system 300 from a normal operating (e.g., cable deployment) position to an inverted position for obstacle avoidance. For example, the payload housing 340 may be rotated about the powerline to move the center of gravity closer to the powerline to facilitate rotation of the robotic system 300 (e.g., by requiring less actuator power to induce the rotation compared to when the center of gravity is farther from the powerline, by inducing less sway in the powerline, etc.).

The robotic system 300 may also include additional features and elements. For example, a power source (e.g., one or more batteries 342) may be included to provide power to the other subsystems to enable the robotic system 300 to operate. In some examples, as illustrated in FIG. 3, the batteries 342 may be positioned on battery rails 343 that extend downward (in the orientation shown in FIG. 3), such that the batteries 342 are below the powerline during at least some operations (e.g., during an obstacle avoidance maneuver). This configuration may improve a stability of the robotic system by lowering a center of gravity of the robotic system 300. In addition, the robotic system 300 may include one or more control elements, such as processors, controllers, communication interfaces (e.g., for wireless or wired communication), memory, etc.

In some examples, the robotic system 300 may include at least one controller 344 configured to control the actuators 326, 328 of the stabilization subsystem 304. For example, the controller(s) 344 may include at least one proportional-integral-derivative (PID) controller 344 operatively coupled to the actuators 326, 328 to operate the actuators 326, 328 at appropriate actuator speeds to maintain the robotic system 300 in a desired pose (e.g., with a center of gravity laterally aligned with the powerline). The controllers 344 may receive feedback from one or more sensors, such as an inertial measurement unit (IMU) 346. The IMU 346 may include one or more accelerometers, gyroscopes, etc., configured to sense a pose (e.g., rotational orientation, translational position, etc.) of the robotic system 300. As the IMU 346 senses that the robotic system 300 rolls or sways, the controllers 344 may operate the actuators 326 and/or 328 to apply a force against a frame of the robotic system 300 to re-orient the robotic system 300 to a desired (e.g., upright) pose.

FIGS. 4 and 5 are side views of associated configurations of an example robotic system 400, which may serve as an embodiment of the robotic system 200 of FIG. 2, as described above. As illustrated in FIGS. 4 and 5, a drive subsystem may include separate drive subsystem end portions 402, and an extension subsystem may include separate extension subsystem end portions 404 mechanically coupled to the corresponding drive subsystem end portions 402. In some embodiments, the robotic system 400 may include a first (e.g., leading or fore) end and a second (e.g., trailing or aft) end that may be determined by a direction in which the robotic system 400 translates along the powerline 101, with each end corresponding to a drive subsystem end portion 402 and an extension subsystem end portion 404. Additionally, a rotation subsystem 406 (e.g., serving as rotation subsystem 208 of FIG. 2), or some portion thereof, may be coupled at opposing ends to the extension subsystem end portions 404. Further, a payload subsystem 410 (e.g., serving as payload subsystem 210 of FIG. 2) carrying a segment of cable 112 may be connected to, and held within, the rotation subsystem 308.

During a cable deployment operation (e.g., while not in an obstacle-avoidance scenario), the robotic system 400 may be in a payload retracted configuration 421, as depicted in FIG. 4, in which both of the drive subsystem end portions 402 are in a retracted (non-extended) position. In this state, at least one drive subsystem end portion 402 may propel the robotic system 400 along the powerline 101 while the rotation subsystem 406 may rotate the payload subsystem 410 about its longitudinal axis that substantially aligns with the powerline 101 and while the payload subsystem 410 pays out a segment of cable 112. These actions may result in the segment of the cable 112 being helically wrapped about the powerline 101. In addition, in some examples, the extension subsystem end portions 404 may retain the rotation subsystem 406 in a retracted state so that the rotation subsystem 406 and the payload subsystem 410 remain close to the powerline 101, thus increasing the physical stability of the system while installing the cable 112. As noted above, in some examples the robotic system 400 may be inverted from the orientation illustrated in FIG. 4 during cable deployment.

In some examples, the term “substantially” in reference to a given parameter, property, or condition, may refer to a degree that one skilled in the art would understand that the given parameter, property, or condition is met with a small degree of variance, such as within acceptable manufacturing tolerances. For example, a parameter that is substantially met may be at least about 90% met, at least about 95% met, at least about 99% met, or fully met.

In some embodiments, each of the drive subsystem end portions 402 may be independently operated in a retracted state (e.g., as illustrated in FIG. 4) or an extended state (e.g., longitudinally along powerline 101 to facilitate obstacle avoidance by extending beyond an obstacle) and to selectively engage or release the powerline 101 while bypassing an obstacle. Other examples may not include extendable or retractable versions of the drive subsystem end portions 402.

FIG. 5 is a side view of the robotic system 400 in a payload extended configuration 422 (e.g., an obstacle avoidance mode), in which the extension subsystem end portions 404 extend the payload subsystem 410 away (e.g., upward) from the drive subsystem end portions 402 and the powerline 101 as the drive subsystem end portions 402 translate the robotic system 400 along the powerline 101. These actions may allow the rotation subsystem 406 (and, consequently, the payload subsystem 410) to pass over the obstacle. In addition, in some examples, the rotation subsystem 406 may include one or more stabilizing components (e.g., upper actuators 430) to stabilize the orientation of the rotation subsystem 406, and thus the robotic system 400, such as by maintaining the current rotational position of the robotic system 400 relative to the powerline 101 (e.g., in the orientation illustrated in FIGS. 4 and 5). In some embodiments, the rotation subsystem 406 may provide stabilization only while the extension subsystem end portions 404 extend the rotation subsystem 406 upward or may provide such stabilization at other times as well.

In some embodiments, one or more components of the robotic system 400 that are primarily employed by the robotic system 400 for functions not directly associated with stabilization may be utilized to provide such stabilization. For example, components used for translation of the robotic system 400 along the powerline 101 (e.g., drive wheels and corresponding motors that clamp or otherwise engage the powerline 101 as part of the drive subsystem end portions 402) may be also configured to translate in a direction parallel to the ground and orthogonal to the powerline 101 relative to other portions of the robotic system 400, such as the extension subsystem end portions 404 and the rotation subsystem 406. In the payload extended configuration 422 and during an obstacle avoidance maneuver, the drive wheels may thus be located significantly below a center of gravity of the robotic system 400. Consequently, shifting the drive wheels horizontally in a direction toward which the payload subsystem 410 begins to tilt may counteract the tilt, resulting in a stabilization force being applied to the robotic system 400 to maintain the robotic system 400 in an upright pose.

To successfully balance the robotic system 400 at least while in the payload extended configuration 422, a control method may be employed that utilizes one or more mathematical models representing the robotic system 400 and powerline 101. For example, the robotic system 400 may be modeled as an inverted pendulum balancing on a vibrating string (e.g., representing the powerline 101), thus obeying the wave equation. In some embodiments, the mathematical model may be created by joining a finite element method (FEM) model of a vibrating string with a rigid-object model of an inverted pendulum on a cart on the string. In some examples, these models may be joined to form a unified model by algebraically eliminating a shared constraint force from separate equations of motion (EOM). Further, in some embodiments, the rigid-object model for the robotic system 400 may include a model for one or more actuators (e.g., the actuators 430, gyroscopes, or the like) that may impose force on the robotic system 400 to stabilize robotic system (e.g., in an upright position over the powerline 101).

In some embodiments, the unified model may then be used to create a balance controller (e.g., using an “H-infinity” (H_∞) control method and/or a PID control method) that may be parameterized or adjusted for the circumstances in which the robotic system 400 is currently employed. To that end, in some examples, for each obstacle crossing requiring extension of the payload subsystem 410 upward, the robotic system 400 may determine a vibration frequency induced by the robotic system 400 by intentionally causing the powerline 101 to vibrate (e.g., at a fundamental frequency). The robotic system 400 may then utilize the determined frequency to estimate a tension of the powerline 101.

In turn, in some examples, this estimated tension may be used with other parameters including the span length of the powerline 101 (e.g., between utility poles 102), the amount of cable 112 remaining in the payload subsystem 410, the position of the robotic system 400 along powerline 101, and/or other parameters associated with the robotic system 400 to calculate a mathematical model specifically for the current obstacle crossing. Based on that model, an H-infinity controller and/or PID controller may be created for each crossing to stabilize the robotic system 300 in the upright extended configuration. In some examples, the mathematical model may specifically take into account obstacle avoidance situations in which the robotic system 400 makes simultaneous contact with two adjacent spans of the powerline 101 on either side of a utility pole 102 (e.g., at an insulator 104 mounted thereto).

In some examples, the balancing of the robotic system 400 in an unstable equilibrium configuration (e.g., in the payload extended configuration 422) may employ several mathematical functions. For example, a three-dimensional (3D) model of a span of the powerline 101 (e.g., between two utility poles 102) may estimate the powerline 101 as a discrete string that includes a plurality of masses interconnected using stiff massless springs of equal length (e.g., resulting in the powerline 101 being difficult to stretch, but easy to bend). Using several known parameters for the powerline 101 (e.g., the length, nominal strain, linear mass, and stiffness of the unstretched powerline 101), an expression for the tension in the “stretched” powerline 101 when hanging from utility poles 102 may be generated in terms of the stiffness of each massless spring and the change in length of each spring.

Generally, including when the robotic system 400 is located at or adjacent to a utility pole 102, displacement of the powerline 101 in an upward and downward direction may be considered as minimal, and thus can generally be ignored to simplify the model. Further, displacement of the powerline 101 (e.g., in a side-to-side direction) may be represented as two smooth sections of powerline 101, one on each side of robotic system 400.

A model for the robotic system 400 may include an inverted pendulum on a cart, where motion in an up-and-down direction is ignored, and where acceleration in a side-to-side direction for the cart is coupled to acceleration of the powerline 101 at the location of the cart along the powerline 101. Further, the powerline 101 may be modeled as a vibrating string in horizontal plane since vibration in the up-and-down direction is ignored, as indicated above, resulting in a partial differential equation (PDE) describing the motion of the powerline 101. A discrete approximation for the PDE may be generated using a finite element method (FEM) to yield a finite element solution in matrix form.

Equations of motion relating to the robotic system 400, which may be modeled as a pendulum traveling on a massless cart in a side-to-side direction (e.g., transverse to the direction of the powerline 101), may be defined. While the dynamics for the powerline 101 and the pendulum portion of the model for the robotic system 400 may not be coupled, the cart portion of the model for the robotic system 400 and the powerline 101 may be coupled at the point at which the cart is attached to the powerline 101. Consequently, the powerline 101 and robotic system 400 may be considered as applying equal and opposite forces, and may exhibit the same acceleration, at that location. Based on these constraints, an equation of motion (EOM), in matrix form, that incorporates the dynamics for the powerline 101 and the pendulum portion of the model for the robotic system 300, as well as the constraints due to the coupling of the cart to the powerline 101, may be generated. Simplification of the EOM may be performed in part by eliminating values that are dependent on other values in the EOM, resulting in an equation of first-order state-space representation (e.g., in which a current state of a system may be represented by a number of state variables), which may be a convenient form for implementation in a control system.

Possible estimators may derive particular internal states of the robotic system 400 from physical quantities (e.g., acceleration) measured by one or more sensors (e.g., motor position sensors, inertial measurement units (IMUs), and the like) located on the robotic system 400. In some embodiments, an extended Kalman filter (EKF) may be used with the estimators to more accurately estimate the internal states employed in the controller based on a series of measurements of the physical quantities that likely include inaccuracies (e.g., noise).

A dynamics model for the one or more actuators employed to maintain stability of the robotic system 400 in an unstable equilibrium configuration may also be employed. In the examples described and shown herein, thrusters (e.g., fans) are employed as actuators. However, gyroscopes or other devices may be employed as the one or more actuators in other examples.

In deriving the model for the actuator(s), a one-to-one relationship may be presumed to exist between an electronic speed control (ESC) signal driving the actuator and a steady state thrust provided by the actuator. As used herein, the ESC signal may regulate the speed of an electric motor that operates the actuator by way of frequency and/or duty cycle of the ESC signal. There may be a time delay between the initiation of an ESC command and a change in thrust, which may be taken into account. In addition, battery voltage effects on actuator speed may also be considered. A dynamics model of the actuator that represents a first order behavior of the actuators, as well as continuous and discrete time delays exhibited by the actuators, may be derived. The output of the actuator model may then be mathematically coupled to the input of the combined cable/pendulum model described above to create a model for the overall stabilization system.

A potential form of feedback control and associated closed-loop dynamics for a controller for stabilizing the robotic system 400 may be based on the models described above. Various potential code modules and scripts may embody the controller, the models upon which the controller is based, and the like.

FIGS. 6A-6C are simplified end views of an example robotic system 600 that uses lateral gripper movement for stabilization, according to at least one embodiment of the present disclosure. The robotic system 600 is illustrated in an unstable equilibrium state, with a center of gravity CG that is above a powerline 602 supporting the robotic system 600. One or more grippers 604 may grasp the powerline 602 for physical support and for stabilization of the robotic system 600. For example, the grippers 604 may be configured as any of the grippers 312 and/or rollers 314 described above and shown in FIG. 3. The grippers 604 may be mounted to and laterally (e.g., transverse to an axis of the powerline 602) movable along one or more gripper rails 606. The robotic system 600 may include an IMU 608 configured to sense a pose (e.g., orientation, rotation, position, etc.) of the robotic system 600.

FIG. 6A shows the robotic system 600 in a relatively stable state, with the center of gravity CG positioned substantially directly above the powerline 602.

FIG. 6B shows the robotic system 600 in a first unstable state, with the center of gravity CG positioned above and to a first lateral side of the powerline 602. By way of example, wind, swaying of the powerline 602, and/or operational movements may have forced the robotic system 600 into this first unstable state. In this state, the IMU 608 may sense the instability of the robotic system 600 (e.g., rotation and/or sway of the robotic system 600). In response, the robotic system 600 (e.g., a controller 610 of the robotic system 600) may move the grippers 604 along the gripper rails 606 in a lateral direction (e.g., to the left as shown in FIG. 6B) toward a vertical plane including the center of gravity CG to restabilize the robotic system 600.

FIG. 6C shows the robotic system 600 in a second unstable state, with the center of gravity CG positioned above and to a second, opposite lateral side of the powerline 602. By way of example, wind, swaying of the powerline 602, and/or operational movements may have forced the robotic system 600 into this second unstable state. In this state, the IMU 608 may sense the instability of the robotic system 600 (e.g., rotation and/or sway of the robotic system 600). In response, the robotic system 600 (e.g., the controller 610) may move the grippers 604 along the gripper rails 606 in a lateral direction (e.g., to the right as shown in FIG. 6C) toward a vertical plane including the center of gravity CG to restabilize the robotic system 600.

In some embodiments, stabilization of the robotic system 600 may be accomplished by lateral movement of the grippers 604 without the use of any upper actuators 326 (e.g., thrusters) or lower actuators 328 (e.g., thrusters) as described above with reference to FIG. 3. In additional embodiments, the lateral movement of the grippers 604 may be used in conjunction with actuation of the upper actuators 326 and/or lower actuators 328 to stabilize the robotic system 600.

As the robotic system 600 crosses (e.g., avoids) obstacles, such as insulators 104, cable clamps 106, etc., the grippers 604 may release the powerline 602 and may be translated laterally away from and back toward the powerline 602 to avoid contacting the obstacles with the grippers 604. In some examples, the robotic system 600 may include four grippers 604, with two being stowable to a right side and two being stowable to a left side relative to the powerline 602. The lateral translation of the grippers 604 may influence a position of the center of gravity CG. Other subsystems of the robotic system 600 may be adjusted to adjust the center of gravity CG, counteracting the movement of the grippers 604, to maintain the center of gravity CG in a neutral position (e.g., above the powerline 602). In some embodiments, joint positions of the robotic system 600 may be determined based on, for example, encoder values, and the location of the center of gravity CG may be estimated. One or more of the joints may be articulated to move the center of gravity CG back into a neutral position. In another example, a payload assembly of the robotic system 600 (e.g., a cable spool) may be rotated to shift the center of gravity CG back into a neutral position to counteract an imbalance that may be caused by movement of the grippers 604.

FIG. 7 is a flow diagram of an example method 700 for obstacle avoidance that may be performed by the robotic system employing a balance controller that is based on the example modeling concepts discussed above. In the method 700, at step 702, span length data regarding one or more spans of the powerline over which the robotic system is to travel may be loaded onto the robotic system prior to normal operation (e.g., helical wrapping of the cable onto the powerline). Moreover, at step 704, during normal operation, the robotic system may log position information (e.g., GPS information, displacement information based on rotation of motors that cause the robotic system to travel along the powerline, and the like).

At step 706, the robotic system may stop translating along the powerline when an obstacle along the powerline (e.g., an insulator, a tap, a change in direction at the utility pole, and so on) is detected. Further, at step 708, one or more actuators (e.g., thrusters, gyroscopes, or the like) may be actuated to intentionally induce a swing of the powerline (e.g., at the fundamental frequency of the span). At step 710, a tension of the powerline may be identified or calculated based on an oscillation period of the powerline of the swing induced by the one or more actuators, as well as the length of the span and the diameter of the powerline, possibly in addition to other parameters describing the powerline. In addition, at step 712, the current weight, center of mass, and moment of inertia of the robotic system may be calculated based on an amount of the cable remaining in the payload subsystem, which in turn may be based on the amount of the cable that has been paid out (e.g., wrapped) onto the powerline from the current segment of the cable carried in the payload subsystem.

At step 714, a balance controller may be activated and the payload subsystem may be extended (e.g., raised upward) into the payload extended configuration in anticipation of crossing the detected obstacle. Further, the operation of the balance controller may be based on a dynamic model that may be updated based on at least one of the various measured or calculated parameters, as described above. At step 716, the obstacle may be crossed while the robotic system remains in the payload extended configuration. After the obstacle has been passed, at step 718, the robotic system may lower the payload subsystem back to the payload retracted configuration and may deactivate the balance controller.

FIG. 8 is a flow diagram of an example method 800 for stabilization of a powerline-crawling robot. At step 810, an axial rotation (e.g., roll) of a robot mounted to a powerline relative to a desired (e.g., upright) stable rotational state may be sensed. For example, the axial rotation may be sensed by an IMU, which may include an accelerometer, gyroscope, or the like.

At step 810, at least one upper thruster, which may be positioned over the powerline supporting the robot, may be activated to substantially laterally align a center of gravity of the robot with the powerline. In some embodiments, multiple upper thrusters may be selectively activated at variable speeds, working together to substantially laterally correct any axial rotation of the robot. Feedback, such as from the IMU, may be provided to one or more thruster controllers to enable the thruster controllers to provide appropriate activation signals to the upper thrusters, as discussed above.

At step 830, a lateral sway of the robot may be sensed, such as by the IMU. The lateral sway may be a lateral motion caused by the flexibility of the powerline supporting the robot. The lateral sway may result from wind, operation of the robot, or the like.

At step 840, at least one lower thruster, which may be positioned closer to the powerline supporting the robot than the upper thrusters, may be activated to inhibit (e.g., reduce or eliminate) the lateral sway of the robot and/or the powerline. In some embodiments, multiple lower thrusters may be selectively activated at variable speeds, working together to substantially laterally correct any sway of the robot. Feedback, such as from the IMU, may be provided to one or more thruster controllers to enable the thruster controllers to provide appropriate activation signals to the lower thrusters, as discussed above.

FIG. 9 is a flow diagram of an example method 900 of stabilizing a robot mounted to a powerline, according to at least one additional embodiment of the present disclosure. At operation 910, an axial rotation (e.g., roll) of a robotic system mounted to a powerline relative to a desired (e.g., upright) stable rotational state may be sensed. For example, the axial rotation may be sensed by an IMU, which may include an accelerometer, gyroscope, or the like.

At operation 920, a gripper that is grasping the powerline may be laterally moved in a direction toward a vertical plane including a center of gravity of the robotic system. Operation 910 may be performed in a variety of ways. For example, the gripper may be laterally moved along a gripper rail responsive to instructions from a controller, as described above with reference to FIGS. 3 and 6A-6C.

FIG. 10 is a block diagram of an example system 1000 (e.g., serving as the robotic system 200, 300, 400, and/or 600) for installing cable 112 onto the powerline 101. As depicted in FIG. 10, the system 1000 may include a memory 1040 storing various modules 1002 executable by one or more physical processors 1030 for causing or controlling various operations of the system 1000. In some embodiments, the modules 1002 may include high-level application code modules 1004 that perform high-level tasks that may include, but are not limited to, initialization and/or calibration of various portions of the system 1000; motion management for various subsystems (e.g., the drive subsystem end portions 402, the extension subsystem end portions 404, the rotation subsystem 406, and/or the payload subsystem 410) to initiate and monitor various operations (e.g., translation along the powerline 101, rotation of the payload subsystem 410 by the rotation subsystem 406 for installing the cable 112, obstacle avoidance (including balancing of the system 1000), the system 1000 loading and unloading, and so on; command and message logging; reception and interpretation of sensor signals (e.g., from sensors 1020); communication with an operator or an external control system (e.g., by way of a wired/wireless remote interface 1050); and the like.

Further, in some examples, motion management and related motion functions may be performed by way of a motor control stack 1006 that communicates with various motors 1014 of the system 1000 to perform the various motion operations noted above. In some embodiments, the modules 1002 may be received (e.g., via the wired/wireless remote interface 1050) and installed by way of software container technology. Also, in some examples, the modules 1002 may employ a software framework and related messaging scheme tailored for robotic applications (e.g., the Robot Operating System (ROS) framework).

In some embodiments, the wired/wireless remote interface 1050 may include communication circuitry (e.g., a wired or wireless transceiver) to facilitate reception of commands (e.g., from a human operator, etc.) to control various portions of the system 1000, as mentioned above, as well as to enable the return of status or logging information.

The sensors 1020 may include one or more sensors (e.g., proximity sensors, IMU sensors, limit switches, optical encoders, cameras, etc.) for detecting obstacles; for detecting a current pose, position, orientation, or motion of the system 1000 or its various components; and so on. The information provided by the sensors 1020 may be employed by the modules 1002 or firmware executed by microcontrollers on the system 1000 (discussed below) to perform their corresponding tasks.

In some embodiments, each motor 1014 of the system 1000 may have a corresponding microcontroller 1012 and associated (e.g., integrated) memory containing firmware that, when executed by the microcontroller 1012, controls the operation of that motor 1014. Further, in some examples, the motor control stack 1006 may issue commands and receive status information from the microcontrollers 1012 by way of a microcontroller interface 1010 coupled to a microcontroller network bus 1011 to which the microcontrollers 1012 are communicatively coupled. In some embodiments, the microcontroller network bus 1011 may be a Controller Area Network (CAN) bus, although other types of buses or interfaces may be employed in other examples.

FIG. 11 is a block diagram of an example stabilization system 1100 for the system 1000 (e.g., the robotic system 200, 300, 400, and/or 600) while the system 1000 is in an unstable equilibrium configuration (e.g., the payload extended configuration 422, such as for avoiding an obstacle). In at least some examples, the stabilization system 1100 may be implemented within the structure of the system 1000 as depicted in FIG. 10. For example, a GPS Unit 1102 and an IMU 1104 of the stabilization system 1100 may serve as some of the sensors 1020 of FIG. 10. Also, in some embodiments, a thrust control board 1110 may serve as a microcontroller 1012, while electronic speed control (ESC) circuits 1112 and associated actuators 1114 (e.g., motors to laterally move grippers along a gripper rail) may serve as constituent parts of one or more of the motors 1014.

In some embodiments, the physical processor 1030 may receive several inputs to implement a balance controller (e.g., a controller using an H-infinity control method and/or a PID method). More specifically, the physical processor 1030 may retrieve information (e.g., span length) for one or more pole spans 1120 of the powerline 101 from a cable path planning database 1108, which may store information for multiple such spans along which the robotic system 300, 400, and/or 600 is to travel to install the cable 112. The physical processor 1030 may also receive current positioning information for the system 1000, such as position data 1124 from the GPS Unit 1102 and/or motor displacement information from one or more drive motor control boards 1106 (e.g., by way of optical encoders or other devices that may track the number of rotations made by drive wheel motors of the drive subsystem end portions 402 that cause the system 1000 to travel along the powerline 101).

In addition, the physical processor 1030 may receive state-space input data 1130 from a thrust control board 1110 so that the balance controller provided by the physical processor 1030 may maintain current state-space information for the balance controller, as described above. In some examples, state-space input 1130 may include information that indicates or incorporates, for example, a current tilt rate 1128 and/or acceleration 1126 of the system from one or more IMUs 1104, as received by the thrust control board 1110. In some embodiments, the thrust control board 1110 may generate the state-space input 1130, such as a current tilt angle of the system 1000 relative to a vertical pose. Further, in some embodiments, the thrust control board 1110 may receive state-space output data 1132 from the physical processor 1030 based on the operation of the balance controller. For example, the state-space output 1032 may indicate a force to applied by one or more of the actuators 1114 (e.g., the actuators 430 of the robotic system 400, motors to control a lateral position of the grippers 604, etc.) to maintain the system 1000 at or near an upright position to retain rotational stability about the powerline 101.

In some embodiments, based on the state-space output 1132, the thrust control board 1110 may produce one or more pulse-width-modulation (PWM) commands to the ESC circuits 1112 so that the ESC circuits 1112 generate motor phase power signals 1136 for the actuators 1114 that possess a corresponding frequency and/or duty cycle associated with the intended force to be generated to maintain the system 1000 stability atop the powerline 101.

As discussed above in conjunction with FIGS. 1-11, robotic systems and methods described herein may facilitate automatic or semiautomatic installation of significant lengths of cable onto a powerline (e.g., by helical wrapping) while avoiding one or more obstacles (e.g., insulators, taps, and/or the like) along the powerline. As described earlier, the avoidance of such obstacles may entail maintaining stability of the robotic system during cable deployment and/or during an avoidance maneuver, such as by way of a balance controller, so that normal installation operation of the system may continue after the maneuver without significant human intervention. Such capabilities may result in accelerated and reliable installation of cable in underserved geographical areas by way of preexisting power transmission and/or distribution infrastructure. Consequently, such systems and methods may facilitate a substantial reduction in make-ready costs for providing cable in such a manner over conventional installation systems.

The following example embodiments are also included in the present disclosure.

Example 1: A stabilization mechanism, which may include: at least one gripper mounted to a powerline-crawling robot, the at least one gripper configured to grasp a powerline supporting the powerline-crawling robot; at least one controller configured to control a lateral position of the at least one gripper; and at least one inertial measurement unit configured to sense at least one of lateral movement and axial rotation of the powerline-crawling robot, wherein the at least one controller controls the lateral position of the at least one gripper based on data from the at least one inertial measurement unit.

Example 2: The stabilization mechanism of Example 1, wherein the at least one gripper includes at least two grippers.

Example 3: The stabilization mechanism of Example 1 or Example 2, further including at least one thruster positioned on a frame of the powerline-crawling robot, the at least one thruster positioned and configured to apply a further stabilizing force to the frame when activated.

Example 4: The stabilization mechanism of Example 3, wherein the at least one thruster includes: at least one upper thruster positioned above the powerline during an obstacle avoidance maneuver; and at least one lower thruster positioned at a same vertical level as the powerline during the obstacle avoidance maneuver.

Example 5: The stabilization mechanism of Example 4, wherein the at least one upper thruster is positioned and operable to counteract a rolling motion of the powerline-crawling robot and the at least one lower thruster is positioned and operable to counteract a swaying motion of the powerline-crawling robot.

Example 6: The stabilization mechanism of Example 4 or Example 5, wherein the at least one upper thruster includes four upper thrusters and the at least one lower thruster includes four lower thrusters.

Example 7: The stabilization mechanism of any of Examples 3 through 6, wherein the at least one thruster includes at least one fan.

Example 8: The stabilization mechanism of any of Examples 1 through 7, wherein the powerline-crawling robot has, at least during an obstacle avoidance maneuver, a center of gravity above the powerline to which the powerline-crawling robot is mounted.

Example 9: The stabilization mechanism of any of Examples 1 through 8, wherein the at least one gripper is mounted to at least one gripper rail along which the at least one gripper is laterally movable.

Example 10: A powerline-crawling robotic system, which may include: a drive subsystem configured to drive the powerline-crawling robotic system along a powerline; and a stabilization subsystem configured to stabilize the robotic system on the powerline, the stabilization subsystem including: an inertial measurement unit configured to sense a lateral movement and rotation of the powerline-crawling robot; and at least one gripper mounted to a frame of the powerline-crawling robotic system, the at least one gripper configured to grip the powerline and to move laterally to counteract the lateral movement and rotation of the powerline-crawling robot sensed by the inertial measurement unit.

Example 11: The powerline-crawling robotic system of Example 10, further including an extension sub system configured to extend a portion of the powerline-crawling robotic system away from the powerline.

Example 12: The powerline-crawling robotic system of Example 10 or Example 11, further including a payload subsystem configured to house a cable for deploying along the powerline.

Example 13: The powerline-crawling robotic system of Example 12, further including a rotation subsystem configured to rotate at least a portion of the payload subsystem about the powerline to helically deploy the cable about the powerline.

Example 14: The powerline-crawling robotic system of Example 12 or Example 13, wherein the payload subsystem houses a fiber optic cable.

Example 15: The powerline-crawling robotic system of any of Examples 10 through 14, wherein the stabilization subsystem further includes at least one thruster positioned on the powerline-crawling robotic system, the at least one thruster positioned and configured to apply a further stabilizing force to the powerline-crawling robotic system when activated.

Example 16: The powerline-crawling robotic system of Example 15, wherein the at least one thruster includes: at least one upper thruster positioned and configured to counteract a rotation of the powerline-crawling robotic system; and at least one lower thruster positioned and configured to counteract a sway of the powerline-crawling robotic system.

Example 17: The powerline-crawling robotic system of any of Examples 10 through 16, wherein the stabilization subsystem further includes a controller configured to control a lateral position of the at least one gripper based on data from the inertial measurement unit.

Example 18: A method of stabilizing a robot mounted to a powerline, which method may include: sensing, with an inertial measurement unit, an axial rotation of a robotic system mounted to a powerline relative to a desired stable rotational state; and laterally moving at least one gripper positioned on the robotic system to substantially laterally align a center of gravity of the robot with the powerline.

Example 19: The method of Example 18, wherein laterally moving the at least one gripper includes moving the at least one gripper along at least one gripper rail to which the at least one gripper is movably mounted.

Example 20: The method of Example 18 or Example 19, further including deploying a cable along the powerline while laterally moving the at least one gripper.

In additional embodiments, the present disclosure is also generally directed to systems and methods for optical detection of objects. To achieve autonomy in robotic systems, having an accurate perception of the environment, including obstacles near the robotic systems, may be important for navigation. Most machine vision sensors rely on reflected light to perceive the environment either through cameras, radar, or lidar. While these systems have proven to be effective for some applications, there are numerous scenarios that can trick these sensors, such as certain combinations of reflectivity, geometry, etc., causing the sensor to not see an obstacle.

Optical micrometers may use spinning mirrors to step a beam across a line to detect the shadow of an obstacle in the beam path. These spinning mirror devices are large, expensive, and heavy, making them less than ideal for applications that are sensitive to size, cost, and weight.

In some embodiments, systems and methods of the present disclosure may be used in conjunction with a powerline-crawling robot used to install cables (e.g., fiber optic cables or another material) along existing powerline infrastructure. The powerline-crawling robot may be configured to autonomously (e.g., semi- or fully autonomously) proceed along a powerline and past obstacles while deploying a cable.

To navigate complex obstacle geometries, the robot may be configured to sense, with high certainty and precision, the boundary of each obstacle that may be encountered along the powerline. In some examples, the robot may be about 6 feet in length, and the powerline may bend and flex under the weight of the robot. This may change the position of obstacles that are encountered relative to grippers that the robot uses to grasp the powerline. The relative position of the obstacles and/or grippers may be independent from the movement of other portions of the robot. The obstacles along the powerline may have varying reflectivity and small geometries, and the robot may include a variety of different components in the vicinity of the gripper. Therefore, attempts to use camera-based, radar-based, and/or lidar-based optical tracking of obstacles near the gripper may be difficult or ineffective in some scenarios.

Sensor systems of the present disclosure may include a small form factor collimated linear beam and a linear CMOS sensor array that are used with a signal-processing algorithm. Combining these components may improve accuracy and certainty of object detection for objects passing through the sensor system. The sensor systems of the present disclosure may be smaller and lighter weight than traditional optical micrometers, while also being capable of measuring and detecting objects across a large enough area for applications involving powerline-crawling robots. The sensor systems may also be configured to avoid conventional challenges of making measurements in sunlight by employing wavelengths in the near infrared band with bandpass filtering. The resulting sensor systems may be capable of detecting objects with high (e.g., up to 100%) certainty and within a small margin of error.

The process parameters and sequence of the steps described and/or illustrated herein are given by way of example only and can be varied as desired. For example, while the steps illustrated and/or described herein may be shown or discussed in a particular order, these steps do not necessarily need to be performed in the order illustrated or discussed. The various example methods described and/or illustrated herein may also omit one or more of the steps described or illustrated herein or include additional steps in addition to those disclosed.

The preceding description has been provided to enable others skilled in the art to best utilize various aspects of the example embodiments disclosed herein. This example description is not intended to be exhaustive or to be limited to any precise form disclosed. Many modifications and variations are possible without departing from the spirit and scope of the present disclosure. The embodiments disclosed herein should be considered in all respects illustrative and not restrictive. Reference should be made to any claims appended hereto and their equivalents in determining the scope of the present disclosure.

Unless otherwise noted, the terms “connected to” and “coupled to” (and their derivatives), as used in the specification and/or claims, are to be construed as permitting both direct and indirect (i.e., via other elements or components) connection. In addition, the terms “a” or “an,” as used in the specification and/or claims, are to be construed as meaning “at least one of.” Finally, for ease of use, the terms “including” and “having” (and their derivatives), as used in the specification and/or claims, are interchangeable with and have the same meaning as the word “comprising.”

ROBOTIC STABILIZATION MECHANISMS AND RELATED METHODS

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED APPLICATION

Provisional Applications (1)