Apparatus, systems, and methods for operating robots in an assisted drive mode
The integration of strain sensors in a robot's handle allows for assisted drive mode, enabling intuitive force-based control and safer manual movement by detecting user input and adjusting motor output for direction and acceleration, addressing ergonomic and usability issues in robot handling.
Patent Information
- Application Number
- PCT/EP2024/062877
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-10
- Filing Date
- 2024-05-09
- Publication Date
- 2024-11-14
AI Technical Summary
Robots are not ergonomically designed for manual movement, making it difficult and potentially hazardous for users to maneuver them, especially when they are large or heavy, as existing systems require specialized training for direction and acceleration inputs.
A robot with a handle equipped with strain sensors that detect force applied by the user, allowing the robot to switch from autonomous to assisted drive mode, enabling motor-assisted movement based on user input, and adjusting acceleration and direction accordingly.
Facilitates easier and safer manual movement of robots by reducing user exertion and integrating intuitive force-based control for direction and acceleration, improving ergonomics and usability.
Smart Images

Figure EP2024062877_14112024_PF_FP_ABST
Abstract
Description
[0001] APPARATUS, SYSTEMS, AND METHODS FOR OPERATING ROBOTS IN AN ASSISTED DRIVE MODE
[0002] FIELD OF THE DISCLOSURE
[0003] This disclosure relates generally to robots and, more particularly, to apparatus, systems, and methods for operating robots in an assisted drive mode.
[0004] BACKGROUND
[0005] During operation, a robot may move autonomously in an environment in response to, for instance, instructions generated based on user inputs. In some instances, such as for maintenance purposes, a user may manually move the robot by exerting force on the robot.
[0006] SUMMARY
[0007] According to a first aspect of the present disclosure, there is provided a robot comprising: a body; at least one motor; a handle; at least one strain sensor coupled to the handle; the robot being configured, in use, to: determine a measure of force applied to the handle based on one or more outputs of the at least one strain sensor; and cause the at least one motor to generate an output during the application of force to the handle to cause the robot to move responsive to the force applied to the handle based on the measure.
[0008] The at least one sensor comprises a first strain sensor and a second strain sensor, the first strain sensor being coupled to a first end of the handle and the second strain sensor being coupled to a second end of the handle, the second end opposite the first end. The first strain sensor may be associated with a sensor array comprising the first strain sensor and a plurality of other strain sensors, the first strain sensor and the plurality of other strain sensors being arranged in a symmetrical pattern. The first strain sensor and the second strain sensor may be disposed in the body.
[0009] The circuitry may be configured to: determine whether the force is applied on the handle by (a) a first hand and a second hand of a user or (b) the first hand and not the second hand of the user; and when the force is applied by the first hand and not the second hand, cause the at least one motor to move the robot in a first direction but not a second direction. When force is applied on the handle at a first time the circuitry may be configured to: detect a change in the force at a second time relative to a first of the handle; and generate an instruction to cause the robot to turn based on the detected change in force relative to the first end of the handle.
[0010] When force is applied on the handle at a first time the circuitry may be configured to detect an absence of force applied to the handle at a second time; and generate an instruction to cause the at least one motor to refrain from generating the output responsive to the detected absence of force.
[0011] The handle may be moveable between a stowed position and a deployed position relative to the body. The circuitry may be configured to cause the robot to switch from an autonomous drive mode to an assisted drive mode responsive to movement of the handle from the stowed position to the deployed position.
[0012] According to a second aspect of the present disclosure, there is provided a robot comprising: a body; means for driving movement of the body; a handle coupled to the body and having a length extending relative to a width of at least a portion of the body; means for registering force to generate outputs indicative of force applied to the handle; and means for controlling movement to cause the means for driving to generate an output to cause the robot to move while the means for registering force generates the outputs indicative of the force applied to the handle.
[0013] The handle may be moveably coupled to the body and further comprising means for controlling a drive mode of the robot, the means for controlling the drive mode to cause the robot to switch from an autonomous drive mode to an assisted drive mode responsive to movement of the handle. The means for registering force may be disposed at an end of the handle. The means for controlling movement may adjust the output of the means for driving based on a user drive profile. The means for controlling may be configured to cause the means for driving to refrain from generating the output responsive to an indication of an absence of force detected by the means for registering force. The means for controlling may be configured to instruct the means for driving to cause the robot to turn in a first direction based on a differential force measurement, the differential force measurement based on the outputs of the means for registering force.
[0014] According to a third aspect of the present disclosure, there is provided a method comprising: determining a measure of force applied to a handle of a robot based on one or more outputs of at least one strain sensor associated with the handle; and causing a motor of the robot to generate an output during the application of force to the handle to cause the robot to move responsive to the force applied to the handle based on the measure. The robot may switch from an autonomous drive mode to an assisted drive mode responsive to movement of the handle from a first position to a second position. The output of the motor may be determined based on a user drive profile associated with a user applying the force to the handle.
[0015] In one example, if force is applied on the handle at a first time the method may further comprise detecting a change in the force at a second time relative to a first end of the handle; and causing the robot to turn based on the detected change in force relative to the first end of the handle. In a further example, if the force is applied on the handle at a first time the method may further comprise detecting an absence of force applied to the handle at a second time; and generating an instruction to cause the motor to refrain from generating the output responsive to the detected absence of force.
[0016] BRIEF DESCRIPTION OF THE DRAWINGS
[0017] FIG. 1 illustrates an example system comprising a robot and assisted drive mode control circuitry for controlling movement of the robot in accordance with teachings of this disclosure;
[0018] FIG. 2 is a block diagram of an example implementation of the assisted drive mode control circuitry of FIG. 1 ;
[0019] FIGS. 3 and 4 illustrate an example robot comprising a handle in accordance with teachings of this disclosure;
[0020] FIGS. 5 and 6 illustrate another example robot comprising a handle in accordance with teachings of this disclosure;
[0021] FIG. 7 is a flowchart representative of example machine readable instructions and / or example operations that may be executed, instantiated, and / or performed by example programmable circuitry to implement the assisted drive mode control circuitry of FIG. 2; and
[0022] FIG. 8 is a block diagram of an example processing platform comprising programmable circuitry structured to execute, instantiate, and / or perform the example machine readable instructions and / or perform the example operations of FIG. 7 to implement the assisted drive mode control circuitry 138 of FIG. 2. In general, the same reference numbers will be used throughout the drawing(s) and accompanying written description to refer to the same or like parts. The figures are not necessarily to scale.
[0023] DETAILED DESCRIPTION
[0024] As mentioned above, during operation, a robot may move autonomously in an environment in response to, for instance, instructions generated based on user inputs. In some instances, the robot may be moved manually by a user for reasons such as maintenance purposes, to direct the robot to a fiducial to enable the robot to update position data relative to the environment, etc. Manual movement of the robot involves the user exerting force on (e.g., pushing) the robot to cause the robot to move. However, some robots are not ergonomically designed for manual movement based on their size, shape, and / or weight. Also, some robots may be carrying a heavy load. As a result, the user may have difficulty moving the robot manually, may risk injury when moving the robot manually, etc.
[0025] Disclosed herein are example robots (e.g., autonomous robots) comprising a handle control system to enable a user to maneuver the robot by applying force to a handle of the robot. In some examples disclosed herein, the robot switches from an autonomous drive mode to an assisted drive mode in response to force applied at the handle. In the assisted drive mode, motor(s) of the robot facilitate movement of the robot while the user exerts force on the handle. In some examples, the handle can be moved between a stowed position and a deployed position relative to a body of the robot. In some examples, the robot switches to the assisted drive mode when the handle is in the deployed position.
[0026] Example handle control systems disclosed herein include sensors to generate outputs indicative of force applied on the handle by the user. Examples disclosed herein include circuitry to cause the robot to move in response to the force applied at the handle. For example, the circuitry can determine acceleration of the robot based on outputs of the sensors indicating force applied at the handle. The circuitry communicates with motor(s) of the robot to facilitate movement of the robot while the user is exerting force on the handle. Thus, examples disclosed herein provide for assisted manual movement of the robot. In some examples, the circuitry adjusts acceleration of the robot based on the force applied at the handle and the weight of the robot (e.g., where mass can be derived from outputs of weight sensors at the robot). Example handle control systems disclosed herein determine (e.g., predict) an intent of the user with respect to movement of the robot. For example, the circuitry can analyze measurements output by sensors located at, for instance, opposing ends of the handle to determine a direction in which the robot should turn. Based on analysis of the differential sensor measurements, examples disclosed herein can infer a user intent to turn the robot to the right or left (e.g., where greater force may be applied by the hand associated with the direction in which the user wishes to turn the robot and reflected in the output(s) of the sensor(s) proximate to the relevant hand). In some examples, a drive profile for a user can be generated and saved. The user drive profile can define characteristics for the assisted drive mode for a particular user, such as preferred acceleration, minimum force thresholds for causing the robot to move, etc.
[0027] Some examples of robots disclosed herein have a form factor designed for facilitating carrying of inventory. For instance, the robot may have a form factor that substantially resembles a shopping cart or a push cart in which a handle extends along a portion of a body of the robot to enable a user to push or pull the robot. The body defines a storage area to receive and support goods placed therein during transport of the robot. Some example robots disclosed herein include forks defining a platform to support a load (e.g., a form factor resembling a pallet jack truck). Examples disclosed herein enable acceleration and direction of the robot to be controlled via the same input mechanism (i.e., force applied on the handle of the robot). Thus, examples disclosed herein can be distinguished from vehicles in which direction and acceleration inputs are decoupled and require two separate inputs (e.g., a steering wheel and accelerator pedal, or joysticks). Separate direction and acceleration inputs may involve specialized training and inputs that are not intuitive to an operator. Thus, examples disclosed here are advantageous with respect to robots having, for instance, a shopping cart form factor.
[0028] In examples disclosed herein, the sensor(s) of the handle can include strain sensors (e.g., strain gauges). Strain sensors such as strain gauges can be used instead of, for instance, capacitive touch sensors, because strain gauges can detect small changes in force, which can be used to recognize variations (e.g., slight variations) in force applied by the user’s hands. Further, strain gauges can measure both tension and compression, while capacitive touch sensors measure changes in capacitance, which is an indirect measure of force. Also, as compared to capacitive touch sensors, strain gauges can detect force applied when the user is wearing gloves (e.g., safety gloves) and are more durable when exposed to impact or vibration, thereby providing for robust measurements of amplitude of force on the handle in an environment such as a warehouse.
[0029] FIG. 1 illustrates an example system 100 for controlling movement of an autonomous robot 102 in an assisted drive mode in accordance with teachings of this disclosure. The autonomous robot 102 of FIG. 1 can include, for example, a cart comprising a storage area (e.g., bin(s), shelve(s), fork(s)) for carrying inventory (e.g., one or more objects) retrieved from a storage location in a warehouse or other environment. Although examples disclosed herein discussed in connection with autonomous robots, examples disclosed herein could be used with other types of robots.
[0030] The example autonomous robot 102 of FIG. 1 includes one or more motors 104 (e.g., electric motor(s) and / or other means for driving movement of the robot 102 via wheel(s) 106 of the robot 102). The example robot 102 includes motor control circuitry 108 and one or more motor switches 110 to control operation of the motor(s) 104. The motor control circuitry 108 includes electronics (e.g., hardware and software component(s)) to control, for example, a speed of the robot 102. The motor switches 110 can control a flow of current to the motor(s) 104 based on, for example, instructions generated by the motor control circuitry 108. The example robot 102 includes brake(s) 112, or more generally, braking mechanism(s) that serve as means for slowing or stopping movement of the robot 102.
[0031] In some examples, the robot 102 of FIG. 1 includes a display screen 120 to present content to a user of the robot 102. In some examples, the display screen 120 is a touch screen to enable the user to interact with data presented on the display screen 120 by touching the screen 120. A display control circuitry 122 (e.g., a graphics processing unit (GPU)) of the example robot 102 of FIG. 1 controls operation of the display screen 120 and facilitates rending of content (e.g., display frame(s) associated with graphical user interface(s)) via the display screen 120. In some examples, the robot 102 includes speaker(s) 123 to provide audio outputs. The robot 102 of FIG. 1 includes a power source 114 such as a battery to provide power to the motor(s) 104 and other components of the robot 102 communicatively coupled via a bus 116. A body, housing, or frame 118 of the robot 102 carries, contains, encloses, and / or otherwise supports electrical component(s) of the robot 102 that enable operation of the robot 102.
[0032] The example robot 102 of FIG. 1 includes one or more handle(s) 126, or means for guiding the robot 102. As disclosed herein, in some examples, the handle(s) 126 are separately coupled to the body 118 of the robot 102 and / or separately movable relative to the body 118. For instance, the handle(s) 126 can move between a stowed (e.g., folded, retracted) state and a deployed (e.g., unfolded, extended) state relative to the robot body 118. In some examples, the handle(s) 126 include lock(s), latch(es), and / or switch(es) 128 to secure or otherwise maintain the handle(s) 126 in the stowed position. In some examples, the handle(s) 126 include handle position sensor(s) 130 to output signal(s) indicative of movement of portion(s) of the handle(s) 126 (e.g., to indicate a change in position of the handle(s) from the stowed position to the deployed position). In some examples, the handle position sensor(s) 130 output signal(s) indicating a change of state of the lock(s), latch(es), or switch(es) 128 (e.g., to indicate that handle(s) 126 have been released from the lock(s) 128, a state of the switch 128 has been changed to release the handle 126, etc.). Additionally or alternatively, a user can press a button or an input at the display screen 120 to release the handle(s) 126. In some examples, the handle position sensor(s) 130 are additionally or alternatively carried by (e.g., coupled to) the body 118 of the robot 102. For instance, the handle position sensor(s) 130 carried by the robot body 118 can include proximity sensor(s) to output signal(s) indicative of a proximity of one or more portions of the handle(s) 126 to the body of the robot 102, thereby indicating that the handle(s) 126 are in the stowed position.
[0033] The example robot 102 includes a robot control circuitry 132 to control movement of the autonomous robot 102. In the example of FIG. 1, the robot control circuitry 132 is implemented by programmable circuitry 134 of the robot 102. The example robot control circuitry 132 of FIG. 1 controls autonomous movement or locomotion of the robot 102 in a first drive mode, or an autonomous drive mode. In the autonomous drive mode, the robot 102 moves to a location in an environment without or with limited user input control at the robot 102 during movement of the robot 102.
[0034] When the robot 102 is in the autonomous drive mode, the robot control circuitry 132 generates instructions to, for example, control travel of the robot 102 along a travel path to a location in an environment including the robot 102. For example, the robot control circuitry 132 generates instructions to cause the robot 102 to turn, travel forward, adjust speed, etc. The robot control circuitry 132 defines a travel trajectory for the robot 102 when the robot 102 is operating in the autonomous drive mode. The instructions generated by the robot control circuitry 132 can be transmitted to, for instance, the motor control circuitry 108. The robot control circuitry 132 includes drive safety control circuitry 136 that performs obstacle detection during travel of the robot 102, causes the robot 102 to perform maneuvers for collision avoidance, etc. The robot control circuitry 132 transmits the instructions with respect to autonomous movement (e.g., locomotion) of the robot 102 to the motor control circuitry 108 to cause the motor(s) 104 to move the robot 102.
[0035] The example autonomous robot 102 of FIG. 1 includes sensor(s) to provide information to the robot control circuitry 132 with respect to, for example, a location of the robot 102 in the environment (e.g., the warehouse), an orientation of the robot 102 in the environment, a proximity of the robot 102 (e.g., the body 118 of the robot 102) relative to external object(s) in the environment (e.g., to detect a potential collision), and / or other properties of the robot 102 (e.g., whether the robot 102 is carrying a load). For example, the robot 102 can include navigation sensor(s) 124 such as a satellite-based geographical positioning system (e.g., a global position system (GPS)), optical sensor(s), and / or other types of sensors. The robot control circuitry 132 analyzes data from the navigation sensor(s) 124 to, for example, adjust a trajectory of the robot 102 and generate corresponding instructions based on the outputs of the sensor(s) 124. In some examples, the robot 102 includes image sensor(s) 131 to generate image(s) of the surrounding environment during operation of the robot 102. The robot control circuitry 132 can analyze image data (e.g., using computer vision) output by the image sensor(s) 131 to, for instance, recognize object(s) in the environment, determine a location of the robot 102, etc. In some examples, the robot 102 includes weight sensor(s) 135 to measure, for example, a weight of a load carried by the robot 102 at a given time. In some examples, the robot control circuitry 132 determines a speed of the robot 102 based on the weight of the load carried by the robot 102.
[0036] The robot control circuitry 132 can generate the instructions to cause the robot 102 to move based on, for example, instructions received from a task orchestrator system 137 in communication with the robot control circuitry 132. The task orchestrator system 137 can manage workflows for the robot 102 and / or other robots in the environment, can assign user(s) (e.g., operator(s)) to perform task(s) in connection with the robot(s) 102, etc. As illustrated in FIG. 1, the robot control circuitry 132 can wirelessly communicate with the task orchestrator system 137 (e.g., via cloud-based device(s) 146). In some examples, the robot control circuitry 132 additionally or alternatively generates the instructions to cause the robot 102 to move based on inputs received at the robot 102 (e.g., via the display screen 120). For example, an instruction from the task orchestrator system 137 and / or a user input at the robot 102 can indicate an object to be retrieved from a warehouse in which the robot 102 disposed. The example robot control circuitry 132 of FIG. 1 can determine a trajectory of the robot 102 to the location of the object in the warehouse based on, for instance, previously defined rule(s) indicating a location of the object in the warehouse.
[0037] The autonomous robot 102 can also operate in a second drive mode, or a manual drive mode. In the manual drive mode, the motor switch(es) 110 disable operation of the motor(s) 104. The user causes the robot 102 to move by exerting force (e.g., muscle power) on the body 118 and / or on the handle(s) 126 to push or pull the robot 102, thereby causing the robot 102 to move. For instance, in the manual drive mode, the wheel(s) 106 rotate about their respective axes to enable the user to move (e.g., push) the robot 102.
[0038] The example robot 102 can operate in a third drive mode, or an assisted drive mode. In the assisted drive mode, the motor control circuitry 108 causes the motor(s) 104 to generate power in response to detection of force applied by the user at the robot 102 to assist the user in moving (e.g., pushing) the robot 102. In particular, in the example of FIG. 1, the motor control circuitry 108 causes the motor(s) 104 to generate power in response to detection of force applied by the user on the handle(s) 126 of the robot 102. The example robot 102 includes assisted drive mode control circuitry 138 to cause the motor(s) 104 of the robot 102 to move the robot 102 while force applied by the user at the handle(s) 126.
[0039] The example handle(s) 126 of FIG. 1 include a malleable material such as an elastomer, a soft metal, etc. The handle(s) 126 include means for registering force applied at the handle. For example, the handle(s) 126 include strain sensors 140 that detect tension or compression at the malleable portion(s) of the handle(s) 126 in response to engagement of the user’s hands with the handle(s) 126. The strain sensor(s) 140 can include, for example, strain gauges, fiber optic strain sensor(s), and / or other types of sensors that measure strain mechanically, electrically, or optically. As disclosed herein (FIG. 3), the strain sensor(s) 140 can define sensor arrays of the handle(s) 126. In some examples, the sensor(s) 140 are disposed along at least a portion of a handle 126 (e.g., along a portion of a length of the handle 126). Additionally or alternatively, the sensor arrays defined by the sensor(s) 140 can be located at, for instance, opposing ends of the handle 126. Although examples disclosed herein are discussed in connection with strain sensors, other types of sensors for measuring force could additionally or alternatively be used. The example assisted drive mode control circuitry 138 analyzes the outputs of the strain sensor(s) 140 to detect force applied at the handle(s) 126 and to facilitate movement (e.g., acceleration, turning) of the robot 102 in response to the applied force. In some examples, the assisted drive mode control circuitry 138 performs a comparative analysis of outputs of sensors located at, for example, opposing ends of the handle 126 to detect differences in force applied at different portions of the handle (e.g., which can indicate that the user wishes to turn the robot 102 in a particular direction), to detect that force is applied on one region of the handle 126 but not elsewhere relative to the handle 126 (e.g., which can indicated that the user is applying one hand to the handle 126), etc. Based on the detected properties of the force applied at the handle(s) 126, the assisted drive mode control circuitry 138 generates instructions to cause the motor(s) 104 to facilitate movement of the robot 102 during the application of user force.
[0040] For example, the assisted drive mode control circuitry 138 determines an acceleration of the robot 102 based on the force applied at the handle(s) and a mass of the robot (or a mass of the robot and a load carried by the robot 102 as determined based on outputs of the weight sensor(s) 135). In some examples, the assisted drive mode control circuitry 138 implements rule(s) that indicate that the robot 102 should travel with constant acceleration. In some examples, the rule(s) define, for example, acceleration limits, velocity thresholds, etc. The assisted drive mode control circuitry 138 generates instructions that are transmitted to the motor control circuitry 108 to cause the motor(s) 104 to rotate the wheel(s) 106 of the robot 102.
[0041] The assisted drive mode control circuitry 138 can determine (e.g., predict, infer) an intent of the user with respect to turning the robot 102 based on differential measurements output by the sensor(s) 140 at different locations relative to the handle 126. For example, if the assisted drive mode control circuitry 138 determines that an amplitude of force applied at a right side of the handle 126 is greater than the force applied at a left side of the handle 126, the assisted drive mode control circuitry 138 can determine that the user wishes to turn the robot 102 to the right. The assisted drive mode control circuitry 138 generates instructions to cause, for instance, the motor(s) 104 to generate torque to assist with causing the wheel(s) 106 to turn right or left in accordance with the measurements output by the sensors.
[0042] In some examples, the assisted drive mode control circuitry 138 accesses a driver profile associated with a user or operator of the robot 102. The driver profile can define user preferences such as a sensitivity of the strain sensor(s) in detecting user input(s) at the handle(s) 126, minimum force detected for causing the robot 102 to move, maximum speeds or acceleration of the robot 102, etc. The driver profile information can be entered via, for instance, a user application executed by the user device 144 and accessed via a display screen of the user device 144 and / or a user application executed by the robot 102 and accessed via the display screen 120 of the robot. In some examples, the driver profile for a user may be provided by the task orchestrator system 137 when a user is assigned to the robot 102. The user can make changes to the driver profile (e.g., adjust sensitivity of the sensors) over time.
[0043] As a result of the operation of the motor(s) 104 in connection with manipulation (e.g., pushing, turning) of the robot 102 by the user via the handle(s) 126, an exertion level by the user to move the robot 102 can be reduced. In some examples, the assisted drive mode control circuitry 138 causes the robot 102 to switch from operating in the autonomous drive mode to the assisted drive mode in response to, for instance, outputs of the handle position sensor(s) 130 indicating that the handle(s) 126 have moved from the stowed position to the deployed position. In some examples, the assisted drive mode control circuitry 138 causes the robot to switch from operating in the assisted drive mode to the autonomous in response to, for instance, outputs of the handle position sensor(s) 130 indicating that the handle(s) 126 have moved from the deployed position to the stowed position. In some examples, the user can additionally or alternatively provide inputs via, for instance, the display screen 120 to cause the robot 102 to switch between the autonomous drive mode, the assisted drive mode, and / or the manual drive mode.
[0044] In the example of FIG. 1 , the assisted drive mode control circuitry 138 is implemented by instructions executed on the programmable circuitry 134 of the robot 102. However, in other examples, the assisted drive mode control circuitry 138 is implemented by instructions on programmable circuitry 142 of a user device 144 and / or on the cloudbased device(s) 146. In other examples, the assisted drive mode control circuitry 138 is implemented by dedicated circuitry located on one or more of the robot 102 and / or the user device 144. In some examples, one or more components of the example assisted drive mode control circuitry 138 are implemented by the on-board programmable circuitry 134 of the robot 102 and one or more other components are implemented by the programmable circuitry 142 of the user device 144 and / or the cloud-based device(s) 146. These components may be implemented in software, firmware, hardware, or in combination of two or more of software, firmware, and hardware. Although in examples disclosed herein the assisted drive mode control circuitry 138 is discussed as implemented by programmable circuitry (e.g., machine-readable instructions executed by the programmable circuitry 134), the assisted drive mode circuitry 138 can additionally or alternatively be implemented as hardware for detecting force at the handle(s) 126 and cause the motor(s) 104 to provide outputs. Thus, examples disclosed herein may be implemented in hardware, software, or combinations thereof. In one example, the assisted drive mode control circuitry 138 of FIG. 2 may be instantiated by programmable circuitry such as the example programmable circuitry 812 of FIG. 8.
[0045] FIG. 2 is a block diagram of an example implementation of the assisted drive mode control circuitry 138 of FIG. 1 to facilitate movement of the example robot 102 of FIG. 1 responsive to force applied by a user at the handle(s) 126 of the robot 102. The assisted drive mode control circuitry 138 of FIG. 2 may be instantiated (e.g., creating an instance of, bring into being for any length of time, materialize, implement, etc.) by programmable circuitry such as a Central Processor Unit (CPU) executing first instructions.
[0046] The example assisted drive mode control circuitry 138 of FIG. 2 includes drive mode selector circuitry 200, force detection circuitry 202, and movement control circuitry 204. In some examples, the drive mode selector circuitry 200 is instantiated by programmable circuitry executing drive mode control instructions and / or configured to perform operations such as those represented by the flowchart of FIG. 7. In some examples, the force detection circuitry 202 is instantiated by programmable circuitry executing drive mode control instructions and / or configured to perform operations such as those represented by the flowchart of FIG. 7. In some examples, the movement control circuitry 204 is instantiated by programmable circuitry executing drive mode control instructions and / or configured to perform operations such as those represented by the flowchart of FIG. 7.
[0047] In some examples, the apparatus includes means for controlling a drive mode of a robot. For example, the means for determining may be implemented by the drive mode selector circuitry 200.
[0048] In some examples, the apparatus includes means for detecting force. For example, the means for detecting may be implemented by the force detection circuitry 202. In some examples, the force detection circuitry 202 may be instantiated by programmable circuitry such as the example programmable circuitry 812 of FIG. 8.
[0049] In some examples, the apparatus includes means for controlling movement of a robot. For example, the means for controlling may be implemented by the movement control circuitry 204. In some examples, the movement control circuitry 204 may be instantiated by programmable circuitry such as the example programmable circuitry 812 of FIG. 8.
[0050] The drive mode selector circuitry 200 of FIG. 2 detects when the handle(s) 126 have moved from the stowed position to the deployed position based on, for instance, outputs of the handle position sensor(s) 130 associated with the handle(s) 126 (e.g., indicating that the lock(s), latch(es), switch(es) 128 for the handle(s) 126 have been released). In some examples, the drive mode selector circuitry 200 detects that user input(s) have been received at the robot 102 instructing the robot 102 to switch to the assisted drive mode (selection of a button, an input provided via the display screen 120). In some examples, the drive mode selector circuitry 200 responds to a user- activated switch that is separate from the handle(s) 126, wherein the state of the switch informs the drive mode selector circuitry 200 that the user wishes to operate the robot 102 in the assisted drive mode. In response to determining that the handle(s) 126 are in the deployed position, the drive mode selector circuitry 200 communicates with the robot control circuitry 132 and / or the motor control circuitry 108 to cause the robot 102 to switch from the autonomous drive mode to the assistive drive mode. In some examples, the drive mode selector circuitry 200 determines that the robot 102 should operate in the assisted drive mode based on handle position rule(s) 206. For example, the handle position rule(s) 206 can set forth that if output(s) of the handle position sensor(s) 130 indicate that the handle(s) 126 have been in the deployed position for a threshold period of time, the drive mode selector circuitry 200 should cause the robot 102 to operate in the assisted drive mode.
[0051] The handle position rule(s) 206 can be defined by user input(s) and stored in a database 208. In some examples, the assisted drive mode control circuitry 138 includes the database 208. In some examples, the database 208 is located external to the assisted drive mode control circuitry 138 in a location accessible to the assisted drive mode control circuitry 138 as shown in FIG. 2.
[0052] The force detection circuitry 202 of FIG. 2 analyzes the outputs of the strain sensor(s) 140 to detect force applied by the user on the handle(s) 126. In some examples, the force detection circuitry 202 compares the outputs of the sensor(s) 140 to a minimum threshold force for causing the robot 102 to move in response to force applied at the handle(s). The minimum threshold force can be defined by force measurement rule(s) 210 stored in the database 208. The minimum threshold force can be defined to avoid unintentional touches on the handle(s) 126 (e.g., light touches, brushes of the user against the handle(s) 126) from causing movement of the robot 102.
[0053] Based on the analysis of the strain sensor output(s), the force detection circuitry 202 detects whether the user is using one hand or two hands to apply force to the handle(s) 126. For example, the force detection circuitry 202 can analyze differential measurements from the sensor(s) 140 at the respective ends of the handle 126 to detect whether one hand or two hands are on the handle 126 at a given time. For example, the force detection circuitry 202 can detect that (a) force applied to the handle 126 has been measured by a first sensor 140 and a second sensor 140, where the first and second sensors 140 are located within a threshold distance of each other and (b) no other sensor(s) 140 associated with the handle 126 are registering force. Based on this analysis and the force measurement rule(s) 210, the force detection circuitry 202 determines that the user intends to move (e.g., push) the robot 102 using one hand (e.g., a one-handed drive mode).
[0054] When the force detection circuitry 202 determines that the user is moving the robot 102 with one hand on the handle 126, the force detection circuitry 202 may analyze differences in outputs of the strain sensors 140 spaced closer together relative to the handle 126 to detect the torque produced at different portions (e.g., opposing edges) of the user’s hand that is engaged with the handle. As disclosed herein, the movement control circuitry 204 can determine (e.g., predict) the user’s intent to turn the robot 102 based on the differences in torque applied using different portions of the user’s hand (e.g., pressing a side of the user’s hand against the handle with greater force than an opposing side of the hand). As also disclosed herein, in response to the detection of the one-handed operation of the robot 102, the movement control circuitry 204 can adjust the output(s) of the motor(s) 104 to reduce the amount of force required by the user to move the robot 102.
[0055] In other examples, the force detection circuitry 202 determines that the user has both hands on the handle(s) 126 based on the outputs of the strain sensors 140 and the force measurement rule(s) 210. For example, the force detection circuitry 202 can determine that the user has both hands on the handle(s) 126 based on outputs of sensor arrays at opposing ends of the handle each detecting tension or compression of the handle 126 within a threshold range. When the force detection circuitry 202 determines that both hands are on the handle 126, the force detection circuitry 202 analyzes differential measurements between the strain sensors 140 at, for instance, the respective ends of the handle 126. The force detection circuitry 202 can use the differential measurements from sensors at, for instance, opposing ends of the handle 126 to detect whether the user is exerting more force using one of his or her hands on the handle 126 rather than the other (e.g., changes in torque applied by the user at the handle 126, which could indicate that the robot 102 should turn).
[0056] The force detection circuitry 202 can detect changes in the application of force by the user at the handle(s) 126 based on the output(s) of the sensor(s) 140 over time. For example, the force detection circuitry 202 can identify when the user has removed a hand from the handle 126 based on the changes in the differential sensor measurements and the force measurement rule(s) 210. The force detection circuitry 202 can detect when the user is no longer engaged with the handle(s) 126 based on changes in the outputs of the sensors 140 indicating that the force applied by the user has fallen below a threshold or that the sensors 140 are not registering applied forces at the handle(s) 126. The force detection circuitry 202 communicates with the movement control circuitry 204 to cause the robot 102 to move in response to the analysis of the outputs of the sensors 140.
[0057] The movement control circuitry 204 of FIG. 2 generates instructions to cause the robot 102 to move in response to force applied by the user at the handle(s) 126, registered by the strain sensor(s) 140, and determined by the force detection circuitry 202. For example, the movement control circuitry 204 determines acceleration of the robot 102 based on the force applied at the handle(s) 126 and a mass of robot 102 (or a mass of the robot 102 including a load carried by the robot 102, where the mass can be determined based on outputs of the weight sensor(s) 135). The movement control circuitry 204 generates instructions to cause the motor(s) 104 to assist with movement of the robot 102 in response to the force applied. The movement control circuitry 204 transmits the instructions to the motor control circuitry 108, which causes the motor(s) 104 generate outputs to propel the robot 102 while the user is exerting force on the handle(s) 126.
[0058] The movement control circuitry 204 analyzes force measurement data generated by the force detection circuitry 202 to determine (e.g., predict) an intent of the user when interacting with the robot 102 via the handle(s) 126. For example, the movement control circuitry 204 may consider a center of mass of the robot 102 to be at the center point of the robot 102.
[0059] Based on the differential sensor measurements determined by the force detection circuitry 202, the movement control circuitry 204 identifies that the user is exerting more force on the handle 126 using, for instance, his or her right hand. As a result, the movement control circuitry 204 determines that the user wishes to turn the robot 102 to the right. The movement control circuitry 204 generates instructions to facilitate turning of the robot 102 to the right. For instance, the movement control circuitry 204 instructs the motor(s) 104 to output torque to move a wheel axle of the robot 102 to change the direction of the wheel(s) 106.
[0060] The movement control circuitry 204 determines (e.g., predicts) the intent of the user based on movement intent rule(s) 212 stored in the database 208. The movement intent rule(s) 212 can define, for instance, expected movements to be performed by the user with respect to using the handle(s) 126 to move the robot 102 and associated characteristics of applied force. For instance, the movement intent rule(s) 212 can indicate differential force thresholds for determining that a user wishes to turn the robot 102 when two hands are engaged with the handle 126. The movement intent rule(s) 212 can indicate differential force thresholds for determining that a user wishes to turn the robot 102 when one hand is engaged with the handle 126. The movement intent rule(s) can indicate force thresholds for determining that the user wishes to reduce a speed of or stop movement the robot 102 (e.g., pulling on the handle(s) 126) and / or force thresholds for determining that the user wishes to increase a speed of the robot 102 (e.g., increased pushing on the handle(s) 126). In some examples, the movement control circuitry 204 can be trained using machine learning to determine user intent in moving the robot 102 based on interactions with the handle(s) 126.
[0061] The movement control circuitry 204 executes movement control rule(s) 214 to direct movement of the robot 102 based on (e.g., user- defined) thresholds, limits, ranges, etc. For instance, the movement control rule(s) 214 can define maximum acceleration and / or velocity values for the robot 102 (e.g., maximum acceleration regardless of the force input). The movement control rule(s) 214 can indicate that when the force detection circuitry 202 detects, based on the sensor outputs, that neither of the hands of the user are engaged with the handle(s) 126, then the movement control circuitry 204 should generate instructions to cause movement of the robot 102 to stop. For instance, the movement control circuitry 204 can generate instructions to cause the brake(s) 112 (FIG. 1) to activate, the motor(s) 104 to stop generating power outputs, etc. The movement control rule(s) 214 are stored in the database 208.
[0062] As another example, if the force detection circuitry 202 determines that only one hand of the user is on the handle 126, the movement control circuitry 204 can determine, based on the movement control rule(s) 214, that the user can pull the robot 102 while the robot 102 is in the assisted drive mode. However, for safety reasons, the movement control rule(s) 214 can indicate that one-handed pushing of the robot 102 is not permitted in the assisted drive mode. In such examples, the movement control circuitry 204 can generate instructions to cause the motor(s) 104 to assist with movement in one direction (i.e., the direction corresponding to pulling the robot 102) but not the other direction (i.e., the direction corresponding to pushing the robot 102). In response to the detection of the one-handed operation of the robot 102, the movement control circuitry 204 can cause the motor(s) 104 to adjust (e.g., increase) the power output(s) to reduce the amount of force required by the user to move the robot 102 in the one-handed mode as compared to when two hands are used to manipulate the robot 102.
[0063] In some examples, the movement control circuitry 204 use outputs of other sensors of the robot 102 (e.g., the navigation sensor(s) 124, the image sensor(s) 131) and / or information from the drive safety control circuitry 136 to, for instance, adjust assisted movement of the robot 102 in the environment. For instance, the drive safety control circuitry 136 and / or image data output by the image sensor(s) 131 and analyzed by the movement control circuitry 204 can indicate that there are obstacle(s) in a travel path of the robot 102 while the robot 102 is operating in the assisted drive mode. In response and based on the movement control rule(s) 214, the movement control circuitry 204 can, for instance, instruct the motor(s) 104 and / or the brake(s) 112 to stop movement of the robot 102, cause alert(s) to be output via the display screen 120 and / or the speaker(s) 124, etc.
[0064] In some examples, the movement control circuitry 204 adjusts the movement control rule(s) 214 for a particular user based on a user drive profile 216 for the user. The movement control circuitry 204 can access the user drive profile(s) 216 from, for example, the task orchestrator system 137 (FIG. 1) and / or a user application (e.g., a user authentication application). The user drive profile(s) 216 can define user preferences with respect to operation of the robot 102 in the assisted drive mode. For example, the user drive profile(s) 216 can indicate preferred sensitivity level(s) of the strain sensor(s) 140 for detecting intent to move the robot 102, preferred velocity of the robot 102, etc. The movement control circuitry 204 adjusts the instruction(s) provided to the motor control circuitry 108 with respect to assisted movement of the robot 102 to adhere to or effect a driving profile associated with the user operating the robot 102 at a particular time. The user may make changes to the driving profile 216 (e.g., increase / reduce the sensitivity of the strain sensors 140). The user driving profile(s) can be stored in the database 208 (e.g., local storage associated with the robot 102) or stored elsewhere (e.g., on a server and then retrieved responsive to receiving information of the user from the task orchestrator system 137 and / or a user authentication application; at a database associated with the task orchestrator system 137, etc.).
[0065] While an example manner of implementing the assisted drive mode control circuitry 138 of FIG. 1 is illustrated in FIG. 2, one or more of the elements, processes, and / or devices illustrated in FIG. 2 may be combined, divided, re-arranged, omitted, eliminated, and / or implemented in any other way. Further, the example drive mode selector circuitry 200, the example force detection circuitry 202, the example movement control circuitry 204, and / or, more generally, the example assisted drive mode control circuitry 138 of FIG. 2, may be implemented by hardware alone or by hardware in combination with software and / or firmware. Thus, for example, any of the example drive mode selector circuitry 200, the example force detection circuitry 202, the example movement control circuitry 204, and / or, more generally, the example assisted drive mode control circuitry 138, could be implemented by programmable circuitry in combination with machine readable instructions (e.g., firmware or software), processor circuitry, FPGAs or other known alternatives. Further still, the example assisted drive mode control circuitry 138 of FIG. 2 may include one or more elements, processes, and / or devices in addition to, or instead of, those illustrated in FIG. 2, and / or may include more than one of any or all of the illustrated elements, processes and devices.
[0066] FIG. 3 illustrates an example robot 300 in accordance with teachings of this disclosure. The example robot 300 of FIG. 3 has a form factor resembling a pallet jack truck. However, the example robot 300 can have other form factors, such as a shopping cart design with one or more storage bins.
[0067] The example robot 300 of FIG. 3 includes a body 302 and a handle 304 coupled to the body 302. As shown in FIG. 3, the handle 304 resembles the handle of, for example, a shopping cart, in that the handle 304 has a length extending relative to a width of at least a portion of the body 302. The handle 304 includes a malleable material such as an elastomer, a soft metal, etc. In the example of FIG. 3, the handle 304 is shown in a deployed position. In the deployed position, the handle 304 is extended relative to the body 302 such that a user can grasp the handle 304 (e.g., the user can wrap his or her hand and fingers around the handle 304 to push or pull the robot body 302).
[0068] The example handle 304 includes two sensor arrays 306 comprising strain sensors 308 (e.g., the strain sensors 140 of FIG. 1). In the example of FIG. 3, the sensor arrays 306 are located at opposing ends 310 of the handle. One of the sensor arrays 306 is shown in an expanded view in FIG. 3. As shown in FIG. 3, the sensor array 306 is defined by a plurality of strain sensors 308. The strain sensors 308 can be arranged in a symmetrical pattern, such as rows or a rosette pattern, or in a non-symmetrical pattern (e.g., random placement of the sensors 308). The strain sensors 308 detect tension or compression resulting from force applied by the user on the malleable portion(s) of the handle 304. In some examples, the handle 304 may be rigid, but an interface between the handle 304 and the body 302 of the robot 300 may include a malleable material to accommodate the sensors 308 to detect force on the handle 304.
[0069] In the example of FIG. 3, the location of the sensors 308 at the ends of the handle 304 rather than, for instance, along portion(s) of a length of the handle 304 can protect the sensors 308 from damage and facilitate ease of coupling the sensors 308 to, for example, cables or other electronic components within the body 302 of the robot 300. For instance, a portion of the respective ends of the handle 304 may extend into the robot body 302. In some examples, the sensor array(s) 306 are disposed internal to the body 302 of the robot 300 rather than external to the body 302 to further protect the sensors 308. Also, positioning the sensor array(s) 306 at the ends of the handle 304 can facilitate ease of replacement of the material of the handle 304 and / or the handle 304 itself (e.g., as compared to if the sensors 308 were located on the handle 304). However, one or more of the sensors 308 may additionally or alternatively be disposed along the length of the handle 304.
[0070] FIG. 4 illustrates the example robot 300 of FIG. 3 with the handle 304 in a stowed position relative to the deployed position shown in FIG. 3. As disclosed herein, in some examples, the handle 304 is moveable relative to the body 302 of the robot 300. In the stowed position of FIG. 4, the handle 304 is retracted relative to the robot body 302 as compared to the deployed position of FIG. 3. For example, in the stowed position, the handle 304 can be proximate to or at least partially resting against the body 302 of the robot 300. In some examples, the handle 304 is maintained in the stowed position via locks or latches (e.g., the lock(s), latch(es) 128 of FIG. 1). To move the handle 304 to the deployed position, the user can release any lock(s) or latch(es) and / or select any buttons or switches and move (e.g., pivot, lift) the handle 304.
[0071] FIG. 5 illustrates another example robot 500 comprising a body 502 and a handle 504 supported by the body 502. In the example of FIG. 5, the handle 504 is in a stowed position. FIG. 6 illustrates the robot 500 of FIG. 5 with the handle 504 in a deployed position. To move the handle 504 to the deployed position, a user may release any locks, latches, or switches that maintain the handle 504 in the stowed position and pull the handle 504 away from the robot body 502. As disclosed herein, in some examples, the drive mode selector circuitry 200 of the example assisted drive mode control circuitry 138 of FIG. 2 causes the robot 500 to switch from the autonomous drive mode to the assisted drive mode responsive to the handle 504 moving from the stowed position to the deployed position.
[0072] At least a portion of the handle 504 of FIGS. 5 and 6 includes a malleable material. The handle 504 includes strain sensors (e.g., the sensors 140, 308) to generate outputs indicative of force applied at the handle 504. The sensors can be disposed along at least a length of the handle, at interface(s) coupling the handle 504 to the robot body 502, or located elsewhere such that the sensors can register forces applied to the handle 504 (e.g., the malleable portion(s) of the handle 504).
[0073] A flowchart representative of example machine readable instructions, which may be executed by programmable circuitry to implement and / or instantiate the assisted drive mode control 138 of FIG. 2 and / or representative of example operations which may be performed by programmable circuitry to implement and / or instantiate the assisted drive mode control circuitry 138 of FIG. 2, are shown in FIG. 7. The machine readable instructions may be one or more executable programs or portion(s) of one or more executable programs for execution by programmable circuitry such as the processor circuitry 812 shown in the example processor platform 800 discussed below in connection with FIG. 8. In some examples, the machine readable instructions cause an operation, a task, etc., to be carried out and / or performed in an automated manner in the real world. As used herein, “automated” means without human involvement.
[0074] The program may be embodied in instructions (e.g., software and / or firmware) stored on one or more non-transitory computer readable and / or machine readable storage medium such as cache memory, Hard Disk Drive, CD, DVD, etc., volatile memory (e.g., Random Access Memory (RAM) of any type, etc.), and / or any other storage device or storage disk. The instructions of the non-transitory computer readable and / or machine readable medium may program and / or be executed by programmable circuitry located in one or more hardware devices, but the entire program and / or parts thereof could alternatively be executed and / or instantiated by one or more hardware devices other than the programmable circuitry and / or embodied in dedicated hardware. The machine readable instructions may be distributed across multiple hardware devices and / or executed by two or more hardware devices (e.g., a server and a client hardware device).
[0075] Further, although the example program is described with reference to the flowchart illustrated in FIG. 7, many other methods of implementing the example assisted drive mode control circuitry 138 may alternatively be used. For example, the order of execution of the blocks of the flowchart may be changed, and / or some of the blocks described may be changed, eliminated, or combined. As mentioned above, the example operations of FIG. 7 may be implemented using executable instructions (e.g., computer readable and / or machine readable instructions) stored on one or more non- transitory computer readable and / or machine readable media.
[0076] FIG. 7 is a flowchart representative of example machine readable instructions and / or example operations 700 that may be executed, instantiated, and / or performed by programmable circuitry to control movement of the example robot 102, 300, 500 of FIGS. 1-6 in response to force applied by a user to the robot 102, 300, 500 (e.g., via the handle(s) 126, 304, 504). The example machine-readable instructions and / or the example operations 700 of FIG. 7 begin at block 702, in which the robot 102, 300, 500 is in an autonomous drive mode.
[0077] At block 704, the drive mode selector circuitry 200 of the example assisted drive mode control circuitry 138 of FIG. 2 determines if an indication has been received that the robot 102, 300, 500 should switch from the autonomous drive mode to the assisted drive mode. For example, the drive mode selector circuitry 200 can determine that the robot 102, 300, 500 should switch to the assisted drive mode based on the handle position rule(s) 206 and output(s) of the handle position sensor(s) 130 indicating that the handle(s) 126, 304, 504 have moved from the stowed position to the deployed position and / or based on input(s) received at the robot 102, 300, 500 (e.g., via the display screen 120, via button(s)). At block 706, the drive mode selector circuitry 200 causes the robot 102, 300, 500 to switch from the autonomous drive mode to the assisted drive mode by, for instance, communicating with the robot control circuitry 132 and / or the motor control circuitry 108 of the robot 102, 300, 500.
[0078] At block 708, the force detection circuitry 202 of the example assisted drive mode control circuitry 138 of FIG. 2 determines a force applied to the handle(s) 126, 304, 504 by a user based on output(s) of sensor(s) 140, 308 associated with the handle(s) 126, 304, 504. For example, the force detection circuitry 202 correlates output(s) of the strain sensor(s) 140, 308 with force applied at the handle(s) 126, 304, 504. Based on the force measurement rule(s) 210, the force detection circuitry 202 can determine if the force satisfies a minimum force threshold for movement of the robot 102, 300, 500; if the force indicates that the user is applying force with one or both hands at the handle(s) 126, 304, 504; if the user is exerting more force with one hand than the other hand or with one portion of a hand than other portions of the same hand; etc.
[0079] At block 710, the movement control circuitry 204 of the example assisted drive mode control circuitry 138 of FIG. 2 analyzes the force detected by the force detection circuitry 202 to determine (e.g., predict) user intent with respect to movement of the robot 102, 300, 500. For example, based on the movement intent rule(s) 212 and differential force measurements with respect to outputs of the sensors 140, 308 analyzed by the force detection circuitry 202, the movement control circuitry 204 can determine that the user intends to turn the robot 102, 300, 500 to the left or to the right. In other examples the movement control circuitry 204 can determine that the user intends for the robot 102, 300, 500 to move in a substantially straight direction based on force data from the force detection circuitry 202. At block 712, the movement control circuitry 204 generates instructions to cause the motor(s) 104 of the robot 102, 300, 500 to assist with movement of the robot 102, 300, 500 while the force is applied at the handle(s) 126, 304, 504. The instructions can define, for instance, acceleration of the robot 102, 300, 500, motor torque outputs, turning direction, etc.
[0080] In some examples, at block 714, the movement control circuitry 204 determines that the instructions for directing movement of the robot 102, 300, 500 in the assisted drive mode should be adjusted based on the movement control rule(s) 214 and / or user drive profile(s) 216. For example, the movement control circuitry 204 can determine that the user intends to push the robot 102, 300, 500 with one hand on the handle 126, 304, 504 (as detected based on the sensor outputs). However, the movement control rule(s) 214 can indicate that pushing the robot 102, 300, 500 with one hand is not permitted. In such instances, the movement control circuitry 204 refrains from instructing the motor(s) 104 to generate power outputs to move the robot 102.
[0081] In some examples, the user drive profile(s) 216 can define, for instance, preferred speeds, force thresholds, etc. for a user of the robot 102, 300, 500 when the robot 102, 300, 500 is operating in the assisted drive mode. The movement control circuitry 204 can adjust the instruction(s) to the motor(s) 104 based on the user drive profile(s) 216 based on the user preferences.
[0082] At block 716, the movement control circuitry 204 adjusts the instruction(s) for the motor(s) 104 based on any movement control rule(s) 214 and / or user drive profile(s) 216. At block 718, the movement control circuitry 204 outputs instruction(s) for the motor(s) 104 to cause the motor(s) 104 to operate to assist with movement of the robot 102, 300, 500. For example, the movement control circuitry 204 transmits the instruction(s) to the motor control circuitry 108.
[0083] At block 720, the force detection circuitry 202 determines if any changes in the force applied to the handle(s) 126, 304, 504 has been detected. For example, the force detection circuitry 202 monitors the outputs of the sensors 140, 308 over time to detect changes in force applied to the handle(s) 126, 304, 504, such as changes in force measurements registered at different locations of the handle(s) 126, 304, 504; changes in sensor outputs indicating that the user has removed a hand from the handle 126, 304, 504, etc. If no changes in the user-applied force are detected, then the movement control circuitry 204 continues to output instructions for the motor(s) 104 to assist with movement of the robot 102, 300, 500 (block 718).
[0084] In some examples, at block 722, the change detected by the force detection circuitry 202 indicates that no force is being applied to the handle(s) 126, 304, 504 while the robot 102, 300, 500 is in the assisted drive mode (i.e., the user has removed both hands from the handle(s) 126, 304, 504). In such examples, at block 724, the movement control circuitry 204 generates instructions for the motor(s) 104 to stop movement of the robot 102, 300, 500 and / or refrain from generating outputs to cause further movement of the robot 102, 300, 500 until the force detection circuitry 202 determines that a user has again applied force to the handle(s) 126. If the force detection circuitry 202 detects changes in the force applied to the handle(s) 126, 304 other than an absence of applied force, then control returns to block 710, where the movement control circuitry 204 determines the user intent for movement of the robot 102, 300, 500 in view of the detected changes (e.g., changes in force (torque) applied by one hand to indicate that the robot 102, 300, 500 should turn).
[0085] At block 726, the drive mode selector circuitry 200 determines if an indication that the robot 102, 300, 500 should exit the assisted drive mode has been received. For example, the drive mode selector circuitry 200 can determine that the handle(s) 126, 304, 504 have been returned to the stowed position and / or a user input has been provided indicating that the robot 102, 300, 500 should exit the assisted drive mode. If an indication that the robot 102, 300, 500 should exit the assisted drive mode has not been received, then control returns to block 720, where the force detection circuitry 202 monitors for changes in force applied to the handle(s) 126, 304, 504 (e.g., to detect reengagement of the hand(s) of the user with the handle(s) 126, 304, 504).
[0086] At block 728, the drive mode selector circuitry 200 communicates with the robot control circuitry 132 and / or the motor control circuitry 108 to cause the robot 102, 300, 500 to exit the assisted drive mode and switch to, for instance, the autonomous drive mode. The instructions 700 end at block 730.
[0087] FIG. 8 is a block diagram of an example programmable circuitry platform 800 structured to execute and / or instantiate the example machine-readable instructions and / or the example operations of FIG. 7 to implement the assisted drive mode control circuitry 138 of FIG. 2. The programmable circuitry platform 800 can be, for example, a server, a personal computer, a workstation, a self-learning machine (e.g., a neural network), a mobile device (e.g., a cell phone, a smart phone, a tablet such as an iPad™), a personal digital assistant (PDA), an Internet appliance, or any other type of computing and / or electronic device.
[0088] The programmable circuitry platform 800 of the illustrated example includes programmable circuitry 812. The programmable circuitry 812 of the illustrated example is hardware. For example, the programmable circuitry 812 can be implemented by one or more integrated circuits, logic circuits, FPGAs, microprocessors, CPUs, GPUs, DSPs, and / or microcontrollers from any desired family or manufacturer. The programmable circuitry 812 may be implemented by one or more semiconductor based (e.g., silicon based) devices. In this example, the programmable circuitry 812 implements the example drive mode selector circuitry 200, the example force detection circuitry 202, and the example movement control circuitry 204.
[0089] The programmable circuitry 812 of the illustrated example includes a local memory 813 (e.g., a cache, registers, etc.). The programmable circuitry 812 of the illustrated example is in communication with main memory 814, 816, which includes a volatile memory 814 and a non-volatile memory 816, by a bus 818. The volatile memory 814 may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS® Dynamic Random Access Memory (RDRAM®), and / or any other type of RAM device. The non- volatile memory 816 may be implemented by flash memory and / or any other desired type of memory device. Access to the main memory 814, 816 of the illustrated example is controlled by a memory controller 817. In some examples, the memory controller 817 may be implemented by one or more integrated circuits, logic circuits, microcontrollers from any desired family or manufacturer, or any other type of circuitry to manage the flow of data going to and from the main memory 814, 816.
[0090] The programmable circuitry platform 800 of the illustrated example also includes interface circuitry 820. The interface circuitry 820 may be implemented by hardware in accordance with any type of interface standard, such as an Ethernet interface, a universal serial bus (USB) interface, a Bluetooth® interface, a near field communication (NFC) interface, a Peripheral Component Interconnect (PCI) interface, and / or a Peripheral Component Interconnect Express (PCIe) interface.
[0091] In the illustrated example, one or more input devices 822 are connected to the interface circuitry 820. The input device(s) 822 permit(s) a user (e.g., a human user, a machine user, etc.) to enter data and / or commands into the programmable circuitry 812. The input device(s) 822 can be implemented by, for example, an audio sensor, a microphone, a camera (still or video), a keyboard, a button, a mouse, a touchscreen, a trackpad, a trackball, an isopoint device, and / or a voice recognition system.
[0092] One or more output devices 824 are also connected to the interface circuitry 820 of the illustrated example. The output device(s) 824 can be implemented, for example, by display devices (e.g., a light emitting diode (LED), an organic light emitting diode (OLED), a liquid crystal display (LCD), a cathode ray tube (CRT) display, an in-place switching (IPS) display, a touchscreen, etc.), a tactile output device, a printer, and / or speaker. The interface circuitry 820 of the illustrated example, thus, typically includes a graphics driver card, a graphics driver chip, and / or graphics processor circuitry such as a GPU.
[0093] The interface circuitry 820 of the illustrated example also includes a communication device such as a transmitter, a receiver, a transceiver, a modem, a residential gateway, a wireless access point, and / or a network interface to facilitate exchange of data with external machines (e.g., computing devices of any kind) by a network 826. The communication can be by, for example, an Ethernet connection, a digital subscriber line (DSL) connection, a telephone line connection, a coaxial cable system, a satellite system, a beyond-line-of-site wireless system, a line-of-site wireless system, a cellular telephone system, an optical connection, etc.
[0094] The programmable circuitry platform 800 of the illustrated example also includes one or more mass storage discs or devices 828 to store firmware, software, and / or data. Examples of such mass storage discs or devices 828 include magnetic storage devices (e.g., floppy disk, drives, HDDs, etc.), optical storage devices (e.g., Blu-ray disks, CDs, DVDs, etc.), RAID systems, and / or solid-state storage discs or devices such as flash memory devices and / or SSDs.
[0095] The machine readable instructions 832, which may be implemented by the machine readable instructions of FIG. 7, may be stored in the mass storage device 828, in the volatile memory 814, in the non-volatile memory 816, and / or on at least one non- transitory computer readable storage medium such as a CD or DVD which may be removable.
[0096] It should be understood that the different elements discussed above as being instantiated by programmable circuitry such as the example programmable circuitry 812 of FIG. 8 may be instantiated by known equivalents, including hardware elements, software and / or a combination of the hardware and software.
[0097] From the foregoing, it will be appreciated that example systems, apparatus, articles of manufacture, and methods have been disclosed that provide for assisted movement of a robot in response force applied by a user at the robot. Examples robots disclosed herein include handle(s) having strain sensors to outputs indicators of force applied at the handle(s). Based on the detected force, examples disclosed herein instruct motor(s) of the robot to generate output(s) to assist with movement of the robot while the force is applied at the handle. Examples disclosed herein respond to changes in user- applied force to detect, for instance, that the user wishes to turn the robot, and generate corresponding instructions for the motor(s) to assist with the movement. Thus, examples disclosed herein translate force applied at the robot handle to assisted movement of the robot to facilitate ease of operation of the robot while the user is exerting force on the robot.
Claims
CLAIMS1. A robot comprising: a body; at least one motor; a handle; at least one strain sensor coupled to the handle; the robot being configured, in use, to: determine a measure of force applied to the handle based on one or more outputs of the at least one strain sensor; and cause the at least one motor to generate an output during the application of force to the handle to cause the robot to move responsive to the force applied to the handle based on the measure.
2. The robot of claim 1 , wherein the at least one sensor comprises a first strain sensor and a second strain sensor, the first strain sensor coupled to a first end of the handle and the second strain sensor coupled to a second end of the handle, the second end opposite the first end.
3. The robot of claim 2, wherein the first strain sensor is associated with a sensor array comprising the first strain sensor and a plurality of other strain sensors, the first strain sensor and the plurality of other strain sensors arranged in a symmetrical pattern.
4. The robot of claim 2, wherein the first strain sensor and the second strain sensor are disposed in the body.
5. The robot of any of claim 1 to claim 4, wherein the circuitry is configured, in use, to: determine whether the force is applied on the handle by (a) a first hand and a second hand of a user or (b) the first hand and not the second hand of the user; and when the force is applied by the first hand and not the second hand, cause the at least one motor to move the robot in a first direction but not a second direction.
6. The robot of any of claim 1 to claim 5, wherein the force is applied on the handle at a first time and the circuitry is configured, in use, to: detect a change in the force at a second time relative to a first end of the handle; and generate an instruction to cause the robot to turn based on the detected change in force relative to the first end of the handle.
7. The robot of any of claim 1 to claim 6, wherein the force is applied on the handle at a first time and the circuitry is configured, in use, to: detect an absence of force applied to the handle at a second time; and generate an instruction to cause the at least one motor to refrain from generating the output responsive to the detected absence of force.
8. The robot of any of claim 1 to claim 7, wherein the handle is moveable between a stowed position and a deployed position relative to the body.
9. The robot of claim 8, wherein the circuitry is configured, in use, to cause the robot to switch from an autonomous drive mode to an assisted drive mode responsive to movement of the handle from the stowed position to the deployed position.
10. A robot comprising: a body; means for driving movement of the body; a handle coupled to the body and having a length extending relative to a width of at least a portion of the body; means for registering force to generate outputs indicative of force applied to the handle; and means for controlling movement to cause the means for driving to generate an output to cause the robot to move while the means for registering force generates the outputs indicative of the force applied to the handle.
11. The robot of claim 10, wherein the handle is moveably coupled to the body and further comprising means for controlling a drive mode of the robot, the means for controlling the drive mode to cause the robot to switch from an autonomous drive mode to an assisted drive mode responsive to movement of the handle.
12. The robot of claim 10 or claim 11, wherein the means for registering force is disposed at an end of the handle.
13. The robot of any of claim 10 to claim 12, wherein the means for controlling movement is configured to adjust the output of the means for driving based on a user drive profile.
14. The robot of any of claim 10 to claim 13, wherein the means for controlling is configured to cause the means for driving to refrain from generating the output responsive to an indication of an absence of force detected by the means for registering force.
15. The robot of any of claim 10 to claim 14, wherein the means for controlling is configured to instruct the means for driving to cause the robot to turn in a first direction based on a differential force measurement, the differential force measurement based on the outputs of the means for registering force.
16. A method comprising: determining a measure of force applied to a handle of a robot based on one or more outputs of at least one strain sensor associated with the handle; and causing a motor of the robot to generate an output during the application of force to the handle to cause the robot to move responsive to the force applied to the handle based on the measure.
17. The method of claim 16, further comprising causing the robot to switch from an autonomous drive mode to an assisted drive mode responsive to movement of the handle from a first position to a second position.
18. The method of claim 16 or of claim 17, further comprising determining the output of the motor based on a user drive profile associated with a user applying the force to the handle.
19. The method of any of claim 16 to claim 18, wherein the force is applied on the handle at a first time and further comprising: detecting a change in the force at a second time relative to a first end of the handle; and causing the robot to turn based on the detected change in force relative to the first end of the handle.
20. The method of any of claim 16 to claim 19, wherein the force is applied on the handle at a first time and further comprising: detecting an absence of force applied to the handle at a second time; and generating an instruction to cause the motor to refrain from generating the output responsive to the detected absence of force.
Citation Information
Patent Citations
Mobile robot
US10493624B1
Robot operating in power-assist mode and method for moving the same
US20200262460A1
Robot system including robot having handle and method of controlling robot
US20210101291A1
Cart handle assembly with power assist function and cart having the same
US20210229723A1
Systems and methods for engaging brakes on a robotic device
WO2022015764A1
Cited By
Robotic vehicle
EP4760435A1
Robotic vehicle
WO2026190020A1
