Patent Grant
11247344
This disclosure relates to mobile robots and mitigating slip of a robot appendage.
A legged robot is a robot that can walk and/or balance on one or more legs. Each leg may include one or more physical members connected by one or more joints, and one or more actuators that apply a force or torque to the physical member(s) and/or joint(s) to move and position the robot. Each leg may further include a foot that contacts the ground as the robot walks and/or balances in a given environment.
Legged robots may be utilized in a wide variety of environments. Some environments may be difficult for a legged robot to traverse due to, for example, a slippery surface, loose particles, slopes, and/or other surface conditions, which might cause one or more of the robot's feet to slip. When a robot's foot slips, the kinematic and energetic performance of the robot may be degraded. Other appendages of a robot (e.g., an end effector) may also slip with respect to an object or surface in the environment, degrading robot performance in a similar manner.
This disclosure provides for systems and methods that can mitigate slip of a robot appendage (e.g., a foot, an end effector, etc.). In particular, the disclosure provides for systems and methods that apply forces to the appendage based, at least in part, on an appendage position and a filter position determined for the appendage. The disclosure further provides for dynamically adjusting the filter position based on one or more conditions to thereby dynamically adjust the applied force in a manner that efficiently and effectively arrests appendage movement during a slip event.
The appendage position can be a recently measured (e.g., most recently measured) position of the appendage (e.g., an instantaneous position). The filter position can be a virtual position that tracks and/or follows the movement of the appendage. In some embodiments, the filter position initially represents the initial touchdown position of the appendage so that any difference between the filter position and further measurements of the appendage position before liftoff (which may imply that the appendage is slipping) can be used as input for force adjustment. The filter position may also be updated to be no more than a threshold distance from the most recently measured appendage position. This allows the robot to mitigate potential slippage without over-correcting. Other embodiments and uses of the filter position may be possible as described below.
In one aspect, a method for mitigating slip of a robot appendage includes (i) receiving an input from one or more sensors, (ii) determining, based on the received input, an appendage position of the robot appendage, (iii) determining a filter position for the robot appendage, (iv) determining a distance between the appendage position and the filter position, (v) determining, based on the distance, a force to apply to the robot appendage, (vi) causing one or more actuators to apply the force to the robot appendage, (vii) determining whether the distance is greater than a threshold distance, (viii) responsive to determining that the distance is greater than the threshold distance, the control system adjusting the filter position to a position, which is the threshold distance from the appendage position, for use in a next iteration, and (ix) responsive to determining that the distance is not greater than the threshold distance, maintaining the determined filter position for use in the next iteration of the method.
In another aspect, a robotic system includes a body, an appendage coupled to the body, one or more actuators coupled to the appendage, one or more sensors, and a control system communicatively coupled to the one or more sensors and the one or more actuators. The control system is configured to iteratively carry out a plurality of operations to mitigate slip of the appendage. For each iteration, the control system is configured to (i) receive an input from the one or more sensors, (ii) determine, based on the input, an appendage position of the appendage, (iii) determine a filter position for the appendage, (iv) determine a distance between the appendage position and the filter position, (v) determine, based on the distance, a force to apply to the appendage, (vi) cause the one or more actuators to apply the determined force to the appendage, (vii) determine whether the distance is greater than a threshold distance, (viii) responsive to a determination that the distance is greater than the threshold distance, adjust the filter position to a position, which is the threshold distance from the appendage position, for use in a next iteration, and (ix) responsive to a determination that the distance is not greater than the threshold distance, maintain the determined filter position for use in the next iteration.
In yet another aspect, a method for mitigating slip of a robot foot includes (i) determining a first appendage position of a robot appendage, (ii) determining a first filter position for the robot appendage, (iii) determining a first distance between the first appendage position and the first filter position, (iv) determining, based on the first distance, a first force to apply to the robot appendage, (v) causing one or more actuators to apply the first force to the robot appendage, (vi) determining that the first distance is greater than a threshold distance, and (vii) responsive to determining that the first distance is greater than the threshold distance, adjusting the first filter position to a second filter position spaced from the first appendage position by the threshold distance, (viii) after determining the first appendage position, determining a second appendage position of the robot appendage, (ix) determining a second distance between the second appendage position and the second filter position, (x) determining, based on the second distance, a second force to apply to the robot appendage, and (xi) causing the one or more actuators to apply the second force to the robot appendage. The second force is different than the first force.
These as well as other aspects, advantages, and alternatives will become apparent to those of ordinary skill in the art by reading the following detailed description with reference where appropriate to the accompanying drawings. Further, it should be understood that the description provided in this summary section and elsewhere in this document is intended to illustrate the claimed subject matter by way of example and not by way of limitation.
The following detailed description describes various features and functions of the disclosed systems and methods with reference to the accompanying figures. The illustrative system and method embodiments described herein are not meant to be limiting. It may be readily understood that certain aspects of the disclosed systems and methods can be arranged and combined in a wide variety of different configurations, all of which are contemplated herein.
When a robot operates in some environments, one or more the robot's appendages may slip. In general, a robot's appendage may slip when a friction force between the appendage and a surface (e.g., a ground surface) is insufficient to maintain the appendage's position on the surface. For instance, a robot's foot or end effector may slip on a wet surface, a muddy surface, a greasy surface, an oily surface, a surface having loose particles (e.g., gravel), a sloped surface (e.g., a grassy hill), a loose, unanchored surface (e.g., a loose, unanchored rug or mat), and/or other surfaces having a low coefficient of friction.
A slipping appendage can cause a number of problems for a robot. For example, in a severe slip scenario, the robot may lose its balance and fall to the ground. However, even in less severe slip scenarios, a slipping appendage may degrade performance of the robot. For instance, a slipping foot may provide less forward thrust and/or vertical lift to the robot when attempting to move in some slip scenarios. Thus, in such scenarios, it may take more time and the robot may need to expend more energy to achieve a desired movement or positioning. Additionally, for instance, a slipping foot may place the robot in an unintended or undesirable position within the environment in which it is operating.
Example embodiments provide systems and methods for mitigating slip of a robot appendage. Within some examples, a robotic system includes a body having one or more appendages such as, for instance, feet and/or end effectors. In some implementations, the robotic system includes two or more legs that extend downwardly from the body to a ground surface. Each leg may include one or more members connected by joints and configured to operate with various degrees of freedom with respect to one another. Each leg may also include a foot, which may contact the ground surface. The legs and feet can balance the robotic system on the ground surface. Additionally, the legs and feet enable the robotic system to move at various speeds according to mechanics for one or more different gaits.
In additional or alternative implementations, the robotic system includes one or more movable arms on which an end effector is attached. The end effector may take a number of different forms depending on the type of task that is to be performed by the robot. For example, a robot designed to pick up, move, and set down objects may include a gripper having a plurality of gripper fingers that controllably open and close. Other examples are also possible.
The robotic system may further include a control system that performs operations to cause the robotic system to interact with or move within an environment. In practice, each appendage may be in a swing state or a stance state. In the swing state, the appendage moves through or is positioned in free space and, in the stance state, the appendage contacts a surface (e.g., a ground surface) to support the body. To operate the robotic system in a given environment, each appendage may transition between the swing state and the stance state one or more times. A slip may occur, for example, when the appendage transitions into the stance state at an initial touchdown position on a surface and then, while still in the stance state, the appendage experiences unintended movement from the initial touchdown position.
In one aspect, the control system performs an iterative process that can help to mitigate slip of a robot appendage. In each iteration of the process, the control system can (i) receive one or more inputs from the one or more sensors, (ii) determine an appendage position of the appendage based on the input(s), (iii) determine a filter position of the appendage, (iv) determine a distance between the appendage position and the filter position, (v) determine a force based on the determined distance, and then (vi) cause the force to be applied to the robot foot.
In each iteration of the process, the control system can also decide whether to adjust the filter position for use in a next iteration of the process. If the decision is to do so, the control system can adjust the filter position to an adjusted filter position, which then may be used in a next iteration of the process. Whereas, if the decision is to not adjust the filter position, then the control system can maintain the filter position so that it may be used again in the next iteration of the process. The control system may thus use the outcome of one iteration to determine the filter position for a next iteration. Stated differently, the control system may determine the filter position during a given iteration based on an outcome of the immediately preceding iteration.
In some aspects, to determine whether to adjust the filter position, the control system determines whether the distance between the appendage position and the filter position is greater than a threshold distance. If the control system determines that the distance is not greater than the threshold distance, the control system maintains the filter position for use in the next iteration. Whereas, if the control system determines that the distance is greater than the threshold distance, the control system adjusts the filter position for use in the next iteration.
In some examples, the control system can adjust the filter position based on the appendage position, the filter position, and/or the threshold distance. For instance, in one implementation, the control system can adjust the filter position by determining an adjusted position that is (i) collinear with the appendage position and the filter position, (ii) between the appendage position and the filter position, and (iii) spaced from the appendage position by the threshold distance. In another implementation, the control system can determine an adjusted filter position that is spaced from the appendage position by the threshold distance. Other examples may also be possible.
In some examples, the control system determines the force to apply to the appendage based on a virtual spring having a spring constant, K. The virtual spring can be considered to be anchored to the filter position and extend to the appendage position for a given iteration. In this way, the virtual spring applies a force to the appendage that generally urges the appendage from the appendage position toward the filter position. By dynamically adjusting the filter position over multiple iterations of the process, the control system dynamically adjusts the applied force in a manner that efficiently and effectively arrests appendage movement during a slip event.
As shown in
Processor(s) 102 may operate as one or more general-purpose hardware processors or special purpose hardware processors (e.g., digital signal processors, application specific integrated circuits, etc.). The processor(s) 102 may be configured to execute computer-readable program instructions 106, and manipulate data 107, both of which are stored in the data storage 104. The processor(s) 102 may also directly or indirectly interact with other components of the robotic system 100, such as sensor(s) 112, power source(s) 114, mechanical components 110, and/or electrical components 116.
The data storage 104 may be one or more types of hardware memory. For example, the data storage 104 may include or take the form of one or more computer-readable storage media that can be read or accessed by processor(s) 102. The one or more computer-readable storage media can include volatile and/or non-volatile storage components, such as optical, magnetic, organic, or another type of memory or storage, which can be integrated in whole or in part with processor(s) 102. In some implementations, the data storage 104 can be a single physical device. In other implementations, the data storage 104 can be implemented using two or more physical devices, which may communicate with one another via wired or wireless communication. As noted previously, the data storage 104 may include the computer-readable program instructions 106 and the data 107. The data 107 may be any type of data, such as configuration data, sensor data, and/or diagnostic data, among other possibilities.
The controller 108 may include one or more electrical circuits, units of digital logic, computer chips, and/or microprocessors that are configured to (perhaps among other tasks), interface between any combination of the mechanical components 110, the sensor(s) 112, the power source(s) 114, the electrical components 116, the control system 118, and/or a user of the robotic system 100. In some implementations, the controller 108 may be a purpose-built embedded device for performing specific operations with one or more subsystems of the robotic device 100.
The control system 118 may monitor and physically change the operating conditions of the robotic system 100. In doing so, the control system 118 may serve as a link between portions of the robotic system 100, such as between mechanical components 110 and/or electrical components 116. In some instances, the control system 118 may serve as an interface between the robotic system 100 and another computing device. Further, the control system 118 may serve as an interface between the robotic system 100 and a user. The instance, the control system 118 may include various components for communicating with the robotic system 100, including a joystick, buttons, and/or ports, etc. The example interfaces and communications noted above may be implemented via a wired or wireless connection, or both. The control system 118 may perform other operations for the robotic system 100 as well.
During operation, the control system 118 may communicate with other systems of the robotic system 100 via wired or wireless connections, and may further be configured to communicate with one or more users of the robot. As one possible illustration, the control system 118 may receive an input (e.g., from a user or from another robot) indicating an instruction to perform a particular gait in a particular direction, and at a particular speed. A gait is a pattern of movement of the limbs of an animal, robot, or other mechanical structure.
Based on this input, the control system 118 may perform operations to cause the robotic device 100 to move according to the requested gait. As another illustration, a control system may receive an input indicating an instruction to move to a particular geographical location. In response, the control system 118 (perhaps with the assistance of other components or systems) may determine a direction, speed, and/or gait based on the environment through which the robotic system 100 is moving en route to the geographical location.
Operations of the control system 118 may be carried out by the processor(s) 102. Alternatively, these operations may be carried out by the controller 108, or a combination of the processor(s) 102 and the controller 108. In some implementations, the control system 118 may partially or wholly reside on a device other than the robotic system 100, and therefore may at least in part control the robotic system 100 remotely.
Mechanical components 110 represent hardware of the robotic system 100 that may enable the robotic system 100 to perform physical operations. As a few examples, the robotic system 100 may include physical members such as appendage(s) 120 (e.g., leg(s), feet, arm(s), end effector(s), etc.) and/or wheel(s). The physical members or other parts of robotic system 100 may further include actuators arranged to move the physical members in relation to one another. The robotic system 100 may also include one or more structured bodies for housing the control system 118 and/or other components, and may further include other types of mechanical components. The particular mechanical components 110 used in a given robot may vary based on the design of the robot, and may also be based on the operations and/or tasks the robot may be configured to perform.
In some examples, the mechanical components 110 may include one or more removable components. The robotic system 100 may be configured to add and/or remove such removable components, which may involve assistance from a user and/or another robot. For example, the robotic system 100 may be configured with removable arms, hands, feet, and/or legs, so that these appendages can be replaced or changed as needed or desired. In some implementations, the robotic system 100 may include one or more removable and/or replaceable battery units or sensors. Other types of removable components may be included within some implementations.
The robotic system 100 may include sensor(s) 112 arranged to sense aspects of the robotic system 100. The sensor(s) 112 may include one or more force sensors, torque sensors, velocity sensors, acceleration sensors, position sensors, proximity sensors, motion sensors, location sensors, load sensors, temperature sensors, touch sensors, depth sensors, ultrasonic range sensors, infrared sensors, object sensors, and/or cameras, among other possibilities. Within some examples, the robotic system 100 may be configured to receive sensor data from sensors that are physically separated from the robot (e.g., sensors that are positioned on other robots or located within the environment in which the robot is operating).
The sensor(s) 112 may provide sensor data to the processor(s) 102 (perhaps by way of data 107) to allow for interaction of the robotic system 100 with its environment, as well as monitoring of the operation of the robotic system 100. The sensor data may be used in evaluation of various factors for activation, movement, and deactivation of mechanical components 110 and electrical components 116 by control system 118. For example, the sensor(s) 112 may capture data corresponding to the terrain of the environment or location of nearby objects, which may assist with environment recognition and navigation. In an example configuration, sensor(s) 112 may include RADAR (e.g., for long-range object detection, distance determination, and/or speed determination), LIDAR (e.g., for short-range object detection, distance determination, and/or speed determination), SONAR (e.g., for underwater object detection, distance determination, and/or speed determination), VICON® (e.g., for motion capture), one or more cameras (e.g., stereoscopic cameras for 3D vision), a global positioning system (GPS) transceiver, and/or other sensors for capturing information of the environment in which the robotic system 100 is operating. The sensor(s) 112 may monitor the environment in real time, and detect obstacles, elements of the terrain, weather conditions, temperature, and/or other aspects of the environment.
Further, the robotic system 100 may include sensor(s) 112 configured to receive information indicative of the state of the robotic system 100, including sensor(s) 112 that may monitor the state of the various components of the robotic system 100. The sensor(s) 112 may measure activity of systems of the robotic system 100 and receive information based on the operation of the various features of the robotic system 100, such the operation of extendable legs, arms, or other mechanical and/or electrical features of the robotic system 100. The data provided by the sensor(s) 112 may enable the control system 118 to determine errors in operation as well as monitor overall operation of components of the robotic system 100.
As an example, the robotic system 100 may use force sensors to measure load on various components of the robotic system 100. In some implementations, the robotic system 100 may include one or more force sensors on an arm or a leg to measure the load on the actuators that move one or more members of the arm or leg. As another example, the robotic system 100 may use one or more position sensors to sense the position of the actuators of the robotic system. For instance, such position sensors may sense states of extension, retraction, or rotation of the actuators on arms or legs.
As another example, the sensor(s) 112 may include one or more velocity and/or acceleration sensors. For instance, the sensor(s) 112 may include an inertial measurement unit (IMU). The IMU may sense velocity and acceleration in the world frame, with respect to the gravity vector. The velocity and acceleration sensed by the IMU may then be translated to that of the robotic system 100 based on the location of the IMU in the robotic system 100 and the kinematics of the robotic system 100.
The robotic system 100 may include other types of sensors not explicated discussed herein. Additionally or alternatively, the robotic system may use particular sensors for purposes not enumerated herein.
The robotic system 100 may also include one or more power source(s) 114 configured to supply power to various components of the robotic system 100. Among other possible power systems, the robotic system 100 may include a hydraulic system, electrical system, batteries, and/or other types of power systems. As an example illustration, the robotic system 100 may include one or more batteries configured to provide charge to components of the robotic system 100. Some of the mechanical components 110 and/or electrical components 116 may each connect to a different power source, may be powered by the same power source, or be powered by multiple power sources.
Any type of power source may be used to power the robotic system 100, such as electrical power or a gasoline engine. Additionally or alternatively, the robotic system 100 may include a hydraulic system configured to provide power to the mechanical components 110 using fluid power. Components of the robotic system 100 may operate based on hydraulic fluid being transmitted throughout the hydraulic system to various hydraulic motors and hydraulic cylinders, for example. The hydraulic system may transfer hydraulic power by way of pressurized hydraulic fluid through tubes, flexible hoses, or other links between components of the robotic system 100. The power source(s) 114 may charge using various types of charging, such as wired connections to an outside power source, wireless charging, combustion, or other examples.
The electrical components 116 may include various mechanisms capable of processing, transferring, and/or providing electrical charge or electric signals. Among possible examples, the electrical components 116 may include electrical wires, circuitry, and/or wireless communication transmitters and receivers to enable operations of the robotic system 100. The electrical components 116 may interwork with the mechanical components 110 to enable the robotic system 100 to perform various operations. The electrical components 116 may be configured to provide power from the power source(s) 114 to the various mechanical components 110, for example. Further, the robotic system 100 may include electric motors. Other examples of electrical components 116 may exist as well.
Although not shown in
The body and/or the other components may include or carry the sensor(s) 112. These sensors may be positioned in various locations on the robotic device 100, such as on the body and/or on one or more of the appendages, among other examples.
On its body, the robotic device 100 may carry a load, such as a type of cargo that is to be transported. The load may also represent external batteries or other types of power sources (e.g., solar panels) that the robotic device 100 may utilize. Carrying the load represents one example use for which the robotic device 100 may be configured, but the robotic device 100 may be configured to perform other operations as well.
As noted above, the robotic system 100 may include various types of legs, arms, wheels, and so on. In general, the robotic system 100 may be configured with zero or more legs. An implementation of the robotic system with zero legs may include wheels, treads, or some other form of locomotion. An implementation of the robotic system with two legs may be referred to as a biped, and an implementation with four legs may be referred as a quadruped. Implementations with six or eight legs are also possible. For purposes of illustration, biped and quadruped implementations of the robotic system 100 are described below.
The robot 200 may be a physical representation of the robotic system 100 shown in
The configuration, position, and/or structure of the legs 204A-204D may vary in example implementations. The legs 204A-204D enable the robot 200 to move relative to its environment, and may be configured to operate in multiple degrees of freedom to enable different techniques of travel. In particular, the legs 204A-204D may enable the robot 200 to travel at various speeds according to the mechanics set forth within different gaits. The robot 200 may use one or more gaits to travel within an environment, which may involve selecting a gait based on speed, terrain, the need to maneuver, and/or energy efficiency.
Further, different types of robots may use different gaits due to variations in design. Although some gaits may have specific names (e.g., walk, trot, run, bound, gallop, etc.), the distinctions between gaits may overlap. The gaits may be classified based on footfall patterns—the locations on a surface for the placement the feet 206A-206D. Similarly, gaits may also be classified based on ambulatory mechanics.
The body 208 of the robot 200 connects to the legs 204A-204D and may house various components of the robot 200. For example, the body 208 may include or carry sensor(s) 210. These sensors may be any of the sensors discussed in the context of sensor(s) 112, such as a camera, LIDAR, or an infrared sensor. Further, the locations of sensor(s) 210 are not limited to those illustrated in
For example, the robot 300 may include legs 304 and 306 connected to a body 308. Each leg may consist of one or more members connected by joints and configured to operate with various degrees of freedom with respect to one another. Each leg may also include a respective foot 310 and 312, which may contact a surface (e.g., the ground surface). Like the robot 200, the legs 304 and 306 may enable the robot 300 to travel at various speeds according to the mechanics set forth within gaits. The robot 300, however, may utilize different gaits from that of the robot 200, due at least in part to the differences between biped and quadruped capabilities.
The robot 300 may also include arms 318 and 320. These arms may facilitate object manipulation, load carrying, and/or balancing for the robot 300. Like legs 304 and 306, each arm may consist of one or more members connected by joints and configured to operate with various degrees of freedom with respect to one another. Each arm may also include a respective hand 322 and 324. The robot 300 may use hands 322 and 324 for gripping, turning, pulling, and/or pushing objects. The hands 322 and 324 may include various types of appendages or attachments, such as fingers, grippers, welding tools, cutting tools, and so on.
The robot 300 may also include sensor(s) 314, corresponding to sensor(s) 112, and configured to provide sensor data to its control system. In some cases, the locations of these sensors may be chosen in order to suggest an anthropomorphic structure of the robot 300. Thus, as illustrated in
Example operations and processes for mitigating slip of a robot appendage will now be described. These operations and processes can be carried out by any of the robotic systems described above (including, e.g., the robotic systems 100, 200, and 300). For simplicity, however, the operations and processes will be described here with reference to the robotic system 100 of
According to the disclosure, the control system 118 of the robotic system 100 carries out an iterative process to determine forces that can be applied to a robot appendage 120 to mitigate slip of the robot appendage 120. For each iteration of the process, the control system 118 determines the force to apply to the appendage 120 based, at least in part, on a filter position determined by the control system for the appendage. The control system 118 can determine and dynamically adjust the filter position based on one or more conditions that may be indicative of whether and/or to what extent the robot appendage 120 may be slipping. This allows the control system 118 to dynamically determine, for each iteration of the process, a force that is appropriately tuned to the robot appendage's specific slip mitigation needs at that particular time.
In one aspect, for each iteration of the process, the control system 118 (i) receives one or more inputs from the one or more sensors 112, (ii) determines an appendage position of the appendage 120 based on the input(s), (iii) determines a filter position for the appendage 120, (iv) determines a distance between the appendage position and the filter position, (v) determines a force based on the determined distance, and then (vi) causes one or more actuators to apply the force to the robot appendage 120.
In some aspects, for each iteration, the control system 118 further determines whether to adjust the filter position of the appendage 120 for the next iteration or maintain the filter position of the appendage 120 for the next iteration without adjustment. To do so, the control system 118 determines whether the distance between the appendage position and the filter position is greater than a threshold distance. If the control system 118 determines that the distance is not greater than the threshold distance, the control system 118 maintains the filter position for the next iteration. Whereas, if the control system 118 determines that the distance is greater than the threshold distance, the control system 118 adjusts the filter position for the next iteration.
In some examples, the control system 118 can adjust the filter position based on the appendage position, the filter position, and/or the threshold distance. In one implementation, the control system 118 can adjust the filter position by determining an adjusted position that is (i) collinear with the appendage position and the filter position, (ii) between the appendage position and the filter position, and (iii) spaced from the appendage position by the threshold distance.
In such an implementation, the control system 118 can be conceptually considered to utilize a virtual string to determine the filter position. For instance, the virtual string can have a length equal to the threshold distance, and the virtual string can be attached at opposing ends to the appendage position and the filter position. In this arrangement, when the distance between the appendage position and the filter position exceeds the threshold distance, the virtual string drags the filter position in the direction of the appendage position. Dragging the filter position using the virtual string causes the filter position to move to an adjusted position that is (i) collinear with the appendage position and the filter position, (ii) between the appendage position and the filter position, and (iii) spaced from the appendage position by the threshold distance.
On the other hand, if the distance is not greater than the threshold distance, the virtual string will not drag the filter position due to slack in the virtual string between the appendage position and the filter position. As such, the control system 118 maintains the filter position in its position when the distance is not greater than the threshold distance.
To further illustrate,
At time t3, while still in the stance state, the robot appendage 120 moved further (possibly due to appendage 120 further slipping along the surface) such that the distance d between the filter position and the appendage position is now greater than the threshold distance TD. Accordingly, the filter position is adjusted to an adjusted position, which is the threshold distance TD from the appendage position at time t3. This adjusted position of the filter position is shown for time t4. In
As noted above, for each iteration i of the process, the control system 118 can determine a force Fi to apply to the robot appendage 120 based on the distance Di between the appendage position IPi and the filter position FPi determined for that iteration i. In some examples, the control system 118 further determines the force Fi based on a virtual spring having a spring constant, K. The virtual spring can be anchored to the filter position FPi and extend to the appendage position IPi for a given iteration i. In this way, the virtual spring applies the force Fi to the robot appendage 120 in a manner that generally urges the robot appendage 120 toward the filter position FPi.
In some additional examples, the control system 118 can further determine the force Fi based on a virtual damper and a velocity of the robot appendage 120 (e.g., an instantaneous velocity). In one example implementation, the control system 118 can use the following equation to determine the force Fi to be applied to the robot appendage 120:
Fi=−K*(IPi−FPi)−C(vi) (Equation 1)
where K is a spring constant, IPi is the appendage position, FPi is the filter position, C is a viscous damping gain constant, and vi is an velocity of the robot appendage 120 determined by the control system 118 for iteration i.
If the robot appendage 120 is not slipping, then the distance Di (i.e., IPi−FPi) and the velocity vi will be relatively small (or possibly zero). As a result, using Equation 1, the control system 118 will determine a relatively small (or zero) force Fi to apply to the robot appendage 120 when the appendage 120 is not slipping. Whereas, if the robot appendage 120 is slipping, the distance Di between the appendage position IPi and the velocity vi will be relatively greater. As a result, using Equation 1, the control system 118 will determine a relatively greater force Fi to apply to the robot appendage 120 when the appendage 120 is slipping.
As noted above, the control system 118 can determine the appendage position IP, and the filter position FP, as one-dimensional, two-dimensional, or three-dimensional coordinates. The control system 118 can utilize Equation 1 in two-dimensional coordinate and/or three-dimensional coordinate implementations as well. For instance, in a two-dimensional coordinate implementation, the control system 118 can employ Equation 1 in the following form:
where Fi,x is the force in the x-dimension, Fi,y is the force in the y-dimension, the appendage position is at coordinate (IPi,x, IPi,y), the filter position is at coordinate (FPi,x, FPi,y), vi,x is the velocity in the x-dimension, vi,y is the velocity in the y-dimension, (Kxx, Kxy, Kyx, Kyy) are the spring constants, and (Cxx, Cxy, Cyx, Cyy) are viscous damping gain constants.
In some aspects, the control system 118 can carry out the process in real-time to mitigate slip of the robot appendage 120. In one example, the control system 118 can perform approximately 50 iterations to approximately 1500 iterations per second. In another example, the control system 118 can perform approximately 200 iterations to approximately 600 iterations per second.
In some aspects, the control system 118 can continuously carry out the process while the robotic system 100 is operated. As noted above, during operation of the robotic system 100, a robot appendage 120 may be in a swing state or a stance state at a given time. In the swing state, the robot appendage 120 moves through or is positioned in free space. In the stance state, the robot appendage 120 contacts a surface of the environment (e.g., the ground surface) to provide support to the robotic system 100. Thus, in some aspects, the control system 118 can continuously carry out the iterative process for a robot appendage 120 in both the swing and stance states.
At block 510, the control system 118 receives one or more inputs from the one or more sensors 112 including sensor data as described above. At block 512, the control system 118 determines, based on the input(s) received from the sensor(s) 112, an appendage position IPi of the robot appendage 120 for the current iteration i of the process. In some examples, the input(s) may explicitly indicate the appendage position IPi of the appendage 120 to the control system 118 (e.g., in examples in which the sensor(s) 112 include a GPS sensor, etc.). In additional or alternative examples, the control system 118 can determine the appendage position IPi from the input(s) based on a forward kinematics analysis and/or other processing (e.g., based, in part, on prior position information for the robot appendage 120 and/or a priori knowledge of the environment in which the robotic system 100 is operating). More generally, the appendage position IPi can be determined based, at least in part, on input(s) indicating sensor data provided by any of the types of sensors 112 described above with respect to
In some aspects, the control system 118 can employ a coordinate system (e.g., a Cartesian coordinate system, a GPS coordinate system, etc.) to provide a frame of reference for determining the appendage position IPi of the appendage 120. The control system 118 can determine the appendage position IPi as a one-dimensional coordinate, a two-dimensional coordinate, or a three-dimensional coordinate with respect to the coordinate system. The number of dimensions determined by the control system 118 for the appendage position IPi may depend on, for example, the number of degrees of freedom for appendage movement, the type of terrain in the operational environment of the robotic system 100, and/or other robot design criteria.
In some implementations, the appendage position IPi can be at point on a surface of the appendage 120 (e.g., a bottom surface of the appendage 120) that is configured to be in contact with a surface of the environment when the appendage 120 is in the stance state (e.g., a ground surface). In one example, the appendage position IPi may be at the geometric center of that surface of the appendage 120. In other examples, the appendage position IPi can be in a different location on the appendage 120.
At block 514, the control system 118 determines whether the current iteration i is the first iteration of the process (e.g., whether i=1). If the control system 118 determines that the current iteration i is the first iteration at block 514, then at block 516 the control system 118 determines a filter position FPi by setting the appendage position IPi determined for the current iteration i (at block 512) as the filter position FPi. Thus, the control system 118 uses the initial appendage position IPi−1 as an initial filter position FPj=1 in this example.
Then, at block 518, the control system 118 determines a distance Di between the appendage position IPi and the filter position FPi determined for the current iteration i. For the first iteration of the process, the distance Di is zero because the appendage position IPi and the filter position IPi are the same. The distance Di may be a non-zero value for at least some subsequent iterations of the process.
At block 520, the control system 118 determines, based on the input(s) received from the sensor(s) 112 at block 510, a velocity vi of the robot appendage 120. At block 522, the control system 118 determines a force Fi to apply to the robot appendage 120 for the current iteration i based on the distance Di determined at block 518 and the velocity Vi determined at block 520. In general, the force Fi determined by the control system 118 can be configured to pull the robot appendage 120 back toward the filter position FPi. For example, the control system 118 can utilize Equation 1 or Equation 2 described above to determine the force Fi.
At block 524, the control system 118 causes the force Fi determined at block 522 for the current iteration i to be applied to the robot appendage 120. For example, the control system 118 can provide one or more control signals to one or more of the actuators (described above with respect to the mechanical components 110) to cause the actuator(s) to apply the force Fi to the appendage 120. As described above, the force Fi applied to the robot appendage 120 may urge the appendage 120 in a direction from the appendage position IPi towards the filter position FPi.
At block 526, the control system 118 determines whether the distance Di determined at block 518 is greater than a threshold distance. If the control system 118 determines that the distance Di is not greater than the threshold distance at block 526, then at block 528 the control system 118 sets the filter position FPi determined for the current iteration i as the filter position FPi+1 for the next iteration i+1. In other words, the control system 118 maintains the filter position FPi for the next iteration i+1. Whereas, if the control system 118 determines that the distance Di is greater than the threshold distance at block 526, then at block 530 the control system 118 determines an adjusted filter position and, at block 532, the control system 118 sets the adjusted filter position as the filter position FPi+1 for the next iteration i+1.
In some aspects, the control system 118 can determine the adjusted filter position based on the appendage position IPi for the current iteration and the threshold distance. For example, the control system 118 can determine the adjusted position by determining a position that is spaced from the appendage position by the threshold distance. Additionally or alternatively, for example, the control system 118 can determine the adjusted position by determining a position that is (i) collinear with the appendage position and the filter position, (ii) between the appendage position and the filter position, and (iii) spaced from the appendage position by the threshold distance. Other examples may also be possible.
After the control system 118 determines the filter position Fi+1 for the next iteration at block 528 or block 530, the control system 118 increments the iteration number i at block 534 and returns to block 510 to begin the next iteration of the process. At block 510, the control system 118 receives input(s) from the sensor(s) 112 and, at block 512, the control system 118 determines the appendage position IPi based on input(s) received from the sensor(s) 112.
At block 514, the control system 118 determines that the current iteration i is not the first iteration and, thus, the process progresses to block 536. Note that the control system 118 progresses from block 512 to block 536 for each iteration after the first iteration.
At block 536, the control system 118 determines whether the robot appendage 120 is in the swing state or the stance state for the current iteration i. The control system 118 can determine whether the robotic system 100 is in the swing state or the stance state based on the input(s) received from the sensor(s) 112 at block 510.
As one example, the robot appendage 120 may include one or more pressure sensors 112 that can measure a pressure (if any) between the robot appendage 120 and a surface and provide sensor data indicative of the measured pressure to the control system 118. The control system 118 can receive input(s) indicating the measured pressure, compare the measured pressure to a pressure threshold, and determine the state of the appendage 120 based on the comparison. For instance, if the control system 118 determines that the measured pressure is greater than the pressure threshold, the control system 118 can determine that the appendage 120 is in the stance state. Whereas, if the control system 118 determines that the measured pressure is not greater than the pressure threshold, the control system 118 can determine that the appendage 120 is in the swing state. Other examples for are also possible.
If, at block 536, the control system 118 determines that the robot appendage 120 is in the swing state, then at block 538 the control system 118 determines the filter position FPi by setting the appendage position IPi determined for the current iteration i (at block 512) as the filter position FPi for the current iteration i. If, however, the control system 118 determines that the robot appendage 120 is in the stance state at block 536, then the control system 118 progresses to block 518 without making any changes to the filter position determined at either block 528 or block 532 during the immediately preceding iteration i−1. That is, if the appendage 120 is in the stance state, the control system 118 effectively determines the filter position FPi to be the outcome of the control system 118 adjusting or maintaining a prior filter position in the immediately preceding iteration i−1.
The control system 118 then determines the distance Di for the current iteration i at block 518, determines the velocity vi at block 520, determines the force Fi at block 522, causes the actuator(s) to apply the determined force Fi to the appendage 120 at block 524, determines whether the distance Di is greater than the threshold distance at block 526, and determines the filter position FPi+1 for the next iteration i+1 at either block 528 or blocks 530, 532 (depending on the determination at block 526). The control system 118 then increments the iteration number i and returns to block 510 to repeat the process.
Depending on conditions experienced by the robot appendage 120 during operation of the robotic system 100, the control system 118 may dynamically adjust the filter position FPi for one or more iterations of the process. This can beneficial in a number of ways. For example, by dynamically adjusting the filter position FPi based on a threshold analysis, the control system 118 can filter out some noisy information that may be received from the sensor(s) 112 during operation. For instance, depending on the accuracy of the sensor(s) 112, the inputs may indicate small variations in the appendage position IPi even though the robot appendage 120 is not moving. Additionally, for instance, small variations in the appendage position IPi may be detected due to compliance between the robot appendage 120 and the ground in some non-slip event scenarios. When such variations are within the threshold distance, the control system 118 does not adjust the filter position FPi. Among other things, this can help to ensure that noisy information from the sensor(s) 112 does not compromise slip mitigation force Fi determinations based on the filter position FPi.
Additionally, for example, because the filter position FPi is dynamically adjusted in a manner that tracks changes to the appendage position IPi, the control system 118 can dynamically determine forces Fi that can efficiently and effectively arrest appendage 120 movement with a reduced risk that such forces Fi will cause further slip of the appendage 120. In other words, the dynamic adjustment of the filter position FPi can help to mitigate over-corrections, which may cause further slips.
In general, the filter position FPi is a virtual position utilized by the control system 118 to determine a force that, when applied to the robot appendage 120, can mitigate slip of the robot appendage 120. As described above, this virtual position can be based on one or more conditions that may be indicative of whether and/or to what extent the robot appendage 120 may be slipping. For instance, when the algorithm initializes at block 516 and/or when the robot appendage 120 is in the swing state at block 538, the robot appendage 120 is unlikely to (or cannot) slip. Accordingly, in those instances, the control system 118 can set the filter position FPi as the appendage position IP, such that a negligible force (or no force) is applied to the robot appendage 120 for that iteration of the algorithm. On the other hand, when the robot appendage 120 is in the stance state, the robot appendage 120 contacts a surface and, thus, it is possible that the robot appendage 120 may experience a slip. In such instances, the control system 118 can utilize the above-described threshold analysis (at blocks 526, 528, 530, 532, 534) to dynamically determine and adjust the filter position FPi in a manner that tracks relative changes to the appendage position IPi so as to efficiently and effectively mitigate slip with reduced risk of an over-correction.
In the example shown in
As shown in
At block 614, the control system 118 determines whether the iteration number i equals the initial value set at block 608. If the control system 118 determines that the iteration number i equals the initial value (i.e., if the current iteration i is the first iteration), then the control system 118 sets the appendage position IPi as the initial filter position FPi at block 616. Whereas, if the control system 118 determines that the iteration number i does not equal the initial value (i.e., if the current iteration i is not the first iteration), then the process proceeds to block 618 without modifying the filter position FPi determined during an immediately preceding iteration i−1.
At block 618, the control system 118 determines the distance Di between the appendage position IPi and the filter position FPi. At block 620, the control system determines the velocity vi based on the input(s) received at block 610. At block 622, the control system determines the force Fi based on the distance Di and the velocity vi as described above. At block 624, the control system 118 causes the determined force Fi to be applied to the appendage 120.
At block 626, the control system 118 determines whether the distance Di is greater than the threshold distance. If the control system 118 determines that the distance Di is not greater than the threshold distance, then the control system 118 maintains the filter position FPi+1 for the next iteration i+1 at block 628. Whereas, if the control system 118 determines that the distance Di is greater than the threshold distance, then the control system 118 determines an adjusted filter position at block 630 and sets the adjusted filter position as the filter position FPi+1 for the next iteration i+1 at block 632.
After determining the filter position FPi+1 for the next iteration i+1, the control system 118 increments the iteration number i at block 634. At block 636, the control system 118 determines whether the appendage 120 is in the swing state or the stance state. If the control system 118 determines that the appendage 120 is in the stance state at block 636, then the process returns to block 610 and repeats. Whereas, if the control system 118 determines that the appendage 120 is in the swing state at block 636, then the process returns to block 606 until the control system 118 next determines that the appendage 120 transitions to the stance state again.
At block 716, the control system 118 determines a distance between the appendage position determined at block 712 and the filter position determined at block 714. At block 718, the control system 118 determines, based on the distance determined at block 716, a force to apply to the robot appendage 120 as described above. At block 720, the control system 118 causes one or more actuators to apply the force determined at block 718 to the appendage 120.
At block 722, the control system 118 determines whether the distance determined at block 716 is greater than a threshold distance. If the control system 118 determines that the distance is not greater than the threshold distance, then at block 724 the control system 118 maintains the filter position for use in a next iteration of the process. If the control system 118 determines that the distance is greater than the threshold distance, then at block 726 the control system 118 adjusts the filter position as described above. After block 724 or block 726, the process returns to block 710 so that the control system 118 can carry out the next iteration.
At block 814, the control system 118 determines a first distance between the first appendage position determined at block 810 and the first filter position determined at block 812. At block 816, the control system 118 determines, based on the first distance, a force to apply to the robot appendage 120. At block 818, the control system 118 causes one or more actuators to apply the first force to the robot appendage 120.
At block 820, the control system 118 determines that the first distance is greater than the threshold distance. At block 822, responsive to the control system 118 determining that the first distance is greater than the threshold distance, the control system 118 adjusts the first filter position to a second filter position spaced from the first appendage position by the threshold distance. In some examples, the second filter position is (i) collinear with the first appendage position and the first filter position, (ii) between the first appendage position and the first filter position, and (iii) spaced from the first appendage position by the threshold distance.
At block 824, the control system 118 determines a second appendage position (e.g., a second instantaneous position) of the robot appendage 120 (e.g., based on additional input(s) received from the sensor(s) 112). At block 826, the control system 118 determines a second distance between the second appendage position and the second filter position. At block 828, the control system 118 determines, based on the second distance, a second force to apply to the robot appendage 120. The second force can be different than the first force. At block 830, the control system 118 causes the actuator(s) to apply the second force to the robot appendage 120.
The above detailed description describes various features and functions of the disclosed systems, devices, and methods with reference to the accompanying figures. In the figures, similar symbols typically identify similar components, unless context indicates otherwise. The illustrative implementations described in the detailed description, figures, and claims are not meant to be limiting. Other implementations can be utilized, and other changes can be made, without departing from the scope of the subject matter presented herein. It will be readily understood that the aspects of the present disclosure, as generally described herein, and illustrated in the figures, can be arranged, substituted, combined, separated, and designed in a wide variety of different configurations, all of which are explicitly contemplated herein.
With respect to any or all of the message flow diagrams, scenarios, and flow charts in the figures and as discussed herein, each step, block and/or communication may represent a processing of information and/or a transmission of information in accordance with example implementations. Alternative implementations are included within the scope of these example implementations. In these alternative implementations, for example, functions described as steps, blocks, transmissions, communications, requests, responses, and/or messages may be executed out of order from that shown or discussed, including in substantially concurrent or in reverse order, depending on the functionality involved. Further, more or fewer steps, blocks and/or functions may be used with any of the message flow diagrams, scenarios, and flow charts discussed herein, and these message flow diagrams, scenarios, and flow charts may be combined with one another, in part or in whole.
For example, in one alternative implementation of the processes shown in
A step or block that represents a processing of information may correspond to circuitry that can be configured to perform the specific logical functions of a herein-described method or technique. Alternatively or additionally, a step or block that represents a processing of information may correspond to a module, a segment, or a portion of program code (including related data). The program code may include one or more instructions executable by a processor for implementing specific logical functions or actions in the method or technique. The program code and/or related data may be stored on any type of computer-readable medium, such as a storage device, including a disk drive, a hard drive, or other storage media.
A computer-readable medium may include non-transitory computer-readable media such as computer-readable media that stores data for short periods of time like register memory, processor cache, and/or random access memory (RAM). The computer-readable media may also include non-transitory computer-readable media that stores program code and/or data for longer periods of time, such as secondary or persistent long term storage, like read only memory (ROM), optical or magnetic disks, and/or compact-disc read only memory (CD-ROM), for example. The computer-readable media may also be any other volatile or non-volatile storage systems. A computer-readable medium may be considered a computer-readable storage medium, for example, or a tangible storage device.
Moreover, a step or block that represents one or more information transmissions may correspond to information transmissions between software and/or hardware modules in the same physical device. However, other information transmissions may be between software modules and/or hardware modules in different physical devices.
While various aspects and implementations have been disclosed herein, other aspects and implementations will be apparent to those skilled in the art. The various aspects and implementations disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope being indicated by the following claims.
This U.S. patent application is a continuation of, and claims priority under 35 U.S.C. § 120 from, U.S. patent application Ser. No. 15/901,419, filed on Feb. 21, 2018, which is a divisional of, and claims priority under 35 U.S.C. § 121 from, U.S. patent application Ser. No. 15/005,687, filed on Jan. 25, 2016. The disclosures of these prior applications are considered part of the disclosure of this application and are hereby incorporated by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5644204 | Nagle | Jul 1997 | A |
| 7603234 | Takenaka et al. | Oct 2009 | B2 |
| 8938319 | Park et al. | Jan 2015 | B2 |
| 9352470 | da Silva et al. | May 2016 | B1 |
| 9387588 | Blankespoor et al. | Jul 2016 | B1 |
| 9387896 | Blankespoor et al. | Jul 2016 | B1 |
| 9618937 | Blankespoor et al. | Apr 2017 | B1 |
| 20030009259 | Hattori et al. | Jan 2003 | A1 |
| 20050126833 | Takenaka et al. | Jun 2005 | A1 |
| 20100114329 | Casler et al. | May 2010 | A1 |
| 20100243344 | Wyrobek et al. | Sep 2010 | A1 |
| 20120143376 | Seo | Jun 2012 | A1 |
| 20130238183 | Goulding | Sep 2013 | A1 |
| 20140081424 | Herr et al. | Mar 2014 | A1 |
| 20140081461 | Williamson et al. | Mar 2014 | A1 |
| 20140320489 | Chizeck et al. | Oct 2014 | A1 |
| 20150202775 | Inazumi | Jul 2015 | A1 |
| 20150286221 | Goulding | Oct 2015 | A1 |
| 20150297934 | Agrawal et al. | Oct 2015 | A1 |
| 20150302777 | Campolo et al. | Oct 2015 | A1 |
| Entry |
|---|
| Focchi et al., Instituto Italiano d: Technologies “Slip Recovery for Quadruped Robots” 3 pages (2015). |
| Boone et al., Autonomous Robots 4(3), “Slepping and Tripping Reflexes for Bipedal Robots,” College of Computing, Georgia Institute of Technology, 11 pages (Dec. 1996). |
| Number | Date | Country | |
|---|---|---|---|
| 20200290213 A1 | Sep 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15005687 | Jan 2016 | US |
| Child | 15901419 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15901419 | Feb 2018 | US |
| Child | 16889035 | US |
