The present application relates generally to transportation of items and, more particularly, to automated methods and systems for transporting items between variable endpoints.
An automated system for transporting items between variable endpoints in accordance with one or more embodiments includes a guidance system for identifying the endpoints and at least one autonomous mobile robot interacting with the guidance system for automatically moving items between the endpoints. The at least one robot is configured to (a) collect an item to be transported at a source endpoint, (b) travel to a destination endpoint utilizing the guidance system to locate the destination endpoint, (c) deliver the item to the destination endpoint, and (d) repeat (a) through (c) for a given set of items. The guidance system is dynamically reconfigurable to identify new endpoints.
A method of transporting items between endpoints in accordance with one or more embodiments includes the steps of: establishing a source endpoint and a destination endpoint; activating at least one autonomous mobile robot to automatically (a) travel to a source endpoint, (b) collect an item to be transported, (c) travel to the destination endpoint with the item, (d) deliver the item to the destination endpoint, and (e) repeat (a) through (d) for a given set of items; and changing the location of one or both of the source and destination endpoints, wherein the at least one robot dynamically adapts to changed endpoints to repeat steps (a)-(e).
Like or identical reference numbers are used to identify common or similar elements.
Various embodiments disclosed herein are generally directed to material handling methods and systems. In particular, automated methods and systems are provided for transporting items between variable endpoints. An automated system in accordance with one or more embodiments includes a guidance system for identifying the endpoints and one or more autonomous mobile robots or platforms interacting with the guidance system for automatically moving items between the endpoints. Each robot is configured to (a) collect an item to be transported at a source end point, (b) travel to a destination endpoint utilizing the guidance system to locate the destination endpoint, (c) deliver the item to the destination endpoint, and (d) repeat (a) through (c) for a given set of items. The guidance system is dynamically reconfigurable to identify new endpoints. The guidance system can mark a complete route or just the end points of a route for the robot.
Advantages of automated systems in accordance with various embodiments can include flexibility, minimal infrastructure, no programming needed, and adaptability to unstructured environments.
The automated system can be used across broad market segments. Automated systems in accordance with various embodiments can also be operated under a variety of conditions including the following. (1) The terrain is rough, e.g., outdoor environments where conventional material handling systems are difficult to use. (2) The surface over which material must travel cannot support heavy weight, e.g., the weight of trucks, forklifts or other mechanized solutions. (3) The workspace is unstructured and dynamic. In addition to most outdoor spaces, this description includes indoor spaces, where the workflow changes frequently or large objects (e.g., pallets) are often repositioned. (4) The pickup point or the drop off point or both, change during operations. (5) Obstruction of the workspace created by a fixed conveyor system is unacceptable. (6) Material must be moved long distances and system utilization is low to moderate. (7) The initial cost of the material-handling system is required to be low.
Platform
The form of an autonomous robot in a particular implementation can vary depending on payload and environmental factors. By way of example, if the robot operates on a flat surface inside a building, it can use a two-wheeled, differential drive mobility system. If it operates on a rough terrain, e.g., a construction site, it may use a tracked platform able to traverse inclines and loose soil.
Behaviors
The autonomous robots move items from a source or load point to a sink or unload point. The robot's basic behaviors depend on its relationship to the source and sink points and whether it is carrying a load. The following table describes some exemplary behaviors triggered by position and load status:
Beyond the basic behaviors outlined in the table, autonomous robots in accordance with various embodiments may have additional behaviors that are activated at intermediate positions along the route. These behaviors deal with obstacles (including other robots) discovered along the way.
Queuing
In accordance with one or more embodiments, each autonomous robot includes a sensor or other mechanism for detecting the presence of other nearby robots. If a robot encounters an obstacle along its route, it either stops or attempts to go around the obstacle. However, if the obstacle is another robot then the robot stops, thus forming a queue. Queues develop near endpoints of the route when robots wait to be loaded or unloaded.
Avoidance
If a robot encounters an obstacle along a route that is not another robot, the robot may attempt to continue toward its destination by skirting the object. The robot can include a wide-angle range sensor (see below) to provide it knowledge of obstructions on and near its route. This may make it possible for the robot to depart from a direct route and then return once the obstacle has been passed. However, whether the robot attempts to go around an obstacle or wait for the obstacle to move is a user choice. In generally uncluttered environments, it will be safe for a robot to search for an alternate route by itself. In more complex environments—especially those with non-geometric hazards—finding a safe alternative to the marked route may not be safe. Thus the user can instruct the robot whether to wait when the route is blocked.
Sensing
Route: In accordance with one or more embodiments, robots can navigate between source and sink using a guidance system such as a beacon marking the route's endpoints or a continuous route marker.
The beacon can be active (e.g., an IR emitter) or passive (e.g., a pattern recognized by an onboard camera). If a beacon is used, each robot should maintain a line of sight between the beacons, i.e., both beacons should be visible to the robot at nearly all times. The robot moves directly from one beacon toward the other unless an obstacle intervenes as described above.
The beacons can establish a coordinate system, where the beacon is the origin of the system. Angular encoding can be used to specify the axes of the coordinate system. The coordinate system enables robots to queue along a particular ray whose origin is the beacon. Angle encoding can also enable other useful properties.
A route marker indicating a robot's path may be used in situations where either a line of sight between beacons does not exist or traveling in a straight path between beacons is not desired. For example, a route marker might enable a robot to avoid a ditch at a construction site.
The route marker can be a worker-positioned tape or line, e.g., comprising a retro-reflective material that enables the robot to acquire it at a distance. The tape or line need not be permanently installed on the floor.
The robot can illuminate the tape or line using, e.g., conventional IR LEDs. In one or more embodiments, the robot detects the tape or line using a position-sensitive detector composed of discrete components (i.e., not a camera) to servo on the tape or line. The detector measures the degree of retro-reflectivity in view to eliminate false positives.
In some embodiments, the robots servo on the line directly. In other embodiments, the robots can servo at any selected offset with respect to the line. Offset servoing enables two important properties. When placing the line to mark the robot's path, workers need not allow space between line and objects. Any time the robot finds its path partially blocked by an object, it will increase its offset from the line so that it can follow the line without colliding with the object. A second feature enabled by offset following allows two robots that meet while traveling along the line in opposite directions to avoid collision. When the robots determine that a collision is imminent, each can offset its position relative to the line. They can thus pass without obstructing each other.
Obstacles: In order to move safely along its route, each robot is equipped with a sensor such as a wide-angle range sensor.
Robot: Each robot can be equipped with a sensor able to distinguish between obstacles and other robots at relatively short range. By way of example, this sensor can be an active IR emitter on one robot that is detected by a receiver on the other robot. The components of this system on the two robots can be arranged such that the following robot detects the robot in front only when the two are physically close.
Load: To allow autonomous operation, each robot can further include a sensor capable of detecting when the robot carries a load. The robot uses the output from this sensor to decide whether to wait at an end point or traverse to the opposite endpoint (see table above).
Manipulation: Robots may optionally include a mechanism enabling a robot to load and unload itself.
User interface: The interface for each robot is preferably simple and intuitive such that the workers themselves are able to setup material handling system wherever necessary. In one or more embodiments, no programming is required.
Implementation Examples:
Automated material handling systems can have a wide range of applications, including, by way of example, the following:
As shown in
In
In some embodiments, the guidance subsystem 54 comprises a plurality of beacons, each having a radio frequency or other (e.g., infrared) beacon transmitter. In this case, the guidance subsystem 54 includes one or more sensors for detecting signals from beacons.
The robot includes an obstacle detection subsystem 56 for detecting other robots and obstacles.
The robot includes a microprocessor-based controller subsystem 58 for controlling operation of the robot in performing programmed behaviors. A power supply 50 for all the subsystems can include one or more rechargeable batteries.
In some embodiments, the drive subsystem 52 takes the form of a differential drive comprising two coaxial wheels and a roller for balance. The wheels are driven together or independently by one or more motors and a drive train controlled by the controller subsystem 58.
The obstacle detection subsystem 56 can include one or more range sensors to detect other robots and obstacles. In some embodiments, the range sensor is a wide-angle (120 degree) range sensor. Raw range sensor data (in the form of a list of angle and range readings) supplied by the sensor is processed by a computer processor (e.g., a processor in the controller subsystem 58) to return the position of other robots and obstacles.
The controller subsystem 58 is configured (e.g., programmed) to perform various functions, including transporting items between endpoints. The controller subsystem 58 is responsive to the output of guidance subsystem 54 and the output of obstacle detection subsystem 56. The controller subsystem 58 controls the drive subsystem 52 to maneuver the robot to prescribed endpoint locations.
Having thus described several illustrative embodiments, it is to be appreciated that various alterations, modifications, and improvements will readily occur to those skilled in the art. Such alterations, modifications, and improvements are intended to form a part of this disclosure, and are intended to be within the spirit and scope of this disclosure. While some examples presented herein involve specific combinations of functions or structural elements, it should be understood that those functions and elements may be combined in other ways according to the present disclosure to accomplish the same or different objectives. In particular, acts, elements, and features discussed in connection with one embodiment are not intended to be excluded from similar or other roles in other embodiments. Additionally, elements and components described herein may be further divided into additional components or joined together to form fewer components for performing the same functions.
The processes the robots are programmed to perform as described above may be implemented in software, hardware, firmware, or any combination thereof. The processes are preferably implemented in one or more computer programs executing on the programmable controller subsystem, which includes a processor, a storage medium readable by the processor (including, e.g., volatile and non-volatile memory and/or storage elements), and input and output devices. Each computer program can be a set of instructions (program code) in a code module resident in a random access memory. Until required, the set of instructions may be stored in another computer memory (e.g., in a hard disk drive, or in a removable memory such as an optical disk, external hard drive, memory card, or flash drive) or stored on another computer system and downloaded via the Internet or other network.
Accordingly, the foregoing description and attached drawings are by way of example only, and are not intended to be limiting.
This application is a continuation of U.S. patent application Ser. No. 13/285,511 filed Oct. 31, 2011 entitled METHODS AND SYSTEMS FOR AUTOMATED TRANSPORTATION OF ITEMS BETWEEN VARIABLE ENDPOINTS, which is hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
3821504 | Shomaker et al. | Jun 1974 | A |
3913758 | Faircloth et al. | Oct 1975 | A |
4155198 | Kelley | May 1979 | A |
4217073 | Propst | Aug 1980 | A |
4401236 | Germaine | Aug 1983 | A |
4476651 | Drury | Oct 1984 | A |
4522546 | Ringer | Jun 1985 | A |
4700301 | Dyke | Oct 1987 | A |
4749327 | Roda | Jun 1988 | A |
4793096 | Todd, Sr. | Dec 1988 | A |
4854802 | deGroot | Aug 1989 | A |
4869637 | deGroot | Sep 1989 | A |
4994970 | Noji et al. | Feb 1991 | A |
5016541 | Feaster, Jr. | May 1991 | A |
5020964 | Hyatt et al. | Jun 1991 | A |
5020965 | Tanaka et al. | Jun 1991 | A |
5046914 | Holland et al. | Sep 1991 | A |
5051906 | Evans, Jr. et al. | Sep 1991 | A |
5081941 | Weeks | Jan 1992 | A |
5085553 | Bouwens et al. | Feb 1992 | A |
5160235 | Bikow | Nov 1992 | A |
5181818 | Tanaka et al. | Jan 1993 | A |
5211523 | Andrada Galan et al. | May 1993 | A |
5315517 | Kawase et al. | May 1994 | A |
5332363 | Tanaka et al. | Jul 1994 | A |
5348063 | Handleman | Sep 1994 | A |
5348361 | Ilchuk | Sep 1994 | A |
5403142 | Stewart | Apr 1995 | A |
5427492 | Tanaka et al. | Jun 1995 | A |
5496143 | Breyer | Mar 1996 | A |
5688102 | Vieselmeyer | Nov 1997 | A |
5769589 | Lubbers | Jun 1998 | A |
5819863 | Zollinger et al. | Oct 1998 | A |
5842306 | Onosaka et al. | Dec 1998 | A |
5959423 | Nakanishi et al. | Sep 1999 | A |
5974348 | Rocks | Oct 1999 | A |
5988971 | Fossey et al. | Nov 1999 | A |
6164537 | Mariani et al. | Dec 2000 | A |
6186730 | Place | Feb 2001 | B1 |
6212821 | Adam et al. | Apr 2001 | B1 |
6216631 | Wissner-Gross | Apr 2001 | B1 |
6243987 | Hessel | Jun 2001 | B1 |
6255793 | Peless et al. | Jul 2001 | B1 |
6336051 | Pangels et al. | Jan 2002 | B1 |
6347920 | Place | Feb 2002 | B1 |
6389329 | Colens | May 2002 | B1 |
6417641 | Peless et al. | Jul 2002 | B2 |
6431818 | Place | Aug 2002 | B1 |
6481948 | Spears | Nov 2002 | B2 |
6496755 | Wallach et al. | Dec 2002 | B2 |
6508033 | Hessel et al. | Jan 2003 | B2 |
6532404 | Colens | Mar 2003 | B2 |
6543983 | Felder et al. | Apr 2003 | B1 |
6611738 | Ruffner | Aug 2003 | B2 |
6638004 | Berger et al. | Oct 2003 | B2 |
6658324 | Bancroft et al. | Dec 2003 | B2 |
6667592 | Jacobs et al. | Dec 2003 | B2 |
6729836 | Stingel, III et al. | May 2004 | B2 |
6850024 | Peless et al. | Feb 2005 | B2 |
6854209 | Van Horssen et al. | Feb 2005 | B2 |
6857493 | Shupp et al. | Feb 2005 | B2 |
6915607 | Tagawa et al. | Jul 2005 | B2 |
6950722 | Mountz | Sep 2005 | B2 |
6984952 | Peless et al. | Jan 2006 | B2 |
6988518 | Rackers | Jan 2006 | B2 |
6997663 | Siebenga | Feb 2006 | B2 |
7054716 | McKee et al. | May 2006 | B2 |
7069111 | Glenn et al. | Jun 2006 | B2 |
7086820 | Blake | Aug 2006 | B1 |
7137770 | Ueda | Nov 2006 | B2 |
7184855 | Stingel, III et al. | Feb 2007 | B2 |
7198312 | Blaho | Apr 2007 | B2 |
7200465 | Stingel, III et al. | Apr 2007 | B2 |
7261511 | Felder et al. | Aug 2007 | B2 |
7274167 | Kim | Sep 2007 | B2 |
7343222 | Solomon | Mar 2008 | B2 |
7400108 | Minor et al. | Jul 2008 | B2 |
7506472 | Leyns et al. | Mar 2009 | B2 |
7559736 | Mohan | Jul 2009 | B1 |
7579803 | Jones et al. | Aug 2009 | B2 |
7610122 | Anderson | Oct 2009 | B2 |
7613544 | Park et al. | Nov 2009 | B2 |
9147173 | Jones | Sep 2015 | B2 |
20010008112 | Opitz | Jul 2001 | A1 |
20020120364 | Colens | Aug 2002 | A1 |
20020146306 | Morrell | Oct 2002 | A1 |
20020182046 | Schempf et al. | Dec 2002 | A1 |
20030030398 | Jacobs et al. | Feb 2003 | A1 |
20030118487 | Pressman et al. | Jun 2003 | A1 |
20030165373 | Felder et al. | Sep 2003 | A1 |
20030199944 | Chapin et al. | Oct 2003 | A1 |
20040139692 | Jacobsen et al. | Jul 2004 | A1 |
20050090961 | Bonk et al. | Apr 2005 | A1 |
20050091953 | Turner et al. | May 2005 | A1 |
20050126144 | Koselka et al. | Jun 2005 | A1 |
20050135912 | Schempf et al. | Jun 2005 | A1 |
20050135913 | Visser | Jun 2005 | A1 |
20050238465 | Razumov | Oct 2005 | A1 |
20050246056 | Marks et al. | Nov 2005 | A1 |
20050254924 | Swetman et al. | Nov 2005 | A1 |
20050254927 | Swetman et al. | Nov 2005 | A1 |
20050268987 | Rackers | Dec 2005 | A1 |
20060045679 | Ostendorff | Mar 2006 | A1 |
20060072988 | Hariki et al. | Apr 2006 | A1 |
20060095169 | Minor et al. | May 2006 | A1 |
20060120834 | Pressman et al. | Jun 2006 | A1 |
20060213167 | Koselka et al. | Sep 2006 | A1 |
20060221769 | Van Loenen et al. | Oct 2006 | A1 |
20060257236 | Stingel et al. | Nov 2006 | A1 |
20060293810 | Nakamoto | Dec 2006 | A1 |
20070017181 | Jacobsen et al. | Jan 2007 | A1 |
20070042803 | Anderson | Feb 2007 | A1 |
20070129849 | Zini | Jun 2007 | A1 |
20070140821 | Garon et al. | Jun 2007 | A1 |
20070152619 | Sugiyama et al. | Jul 2007 | A1 |
20070219720 | Trepagnier et al. | Sep 2007 | A1 |
20080046130 | Faivre et al. | Feb 2008 | A1 |
20080131254 | Cope et al. | Jun 2008 | A1 |
20080279663 | Alexander | Nov 2008 | A1 |
20090012667 | Matsumoto et al. | Jan 2009 | A1 |
20090021351 | Beniyama et al. | Jan 2009 | A1 |
20090054222 | Zhang et al. | Feb 2009 | A1 |
20090148034 | Higaki et al. | Jun 2009 | A1 |
20090175709 | Okabe et al. | Jul 2009 | A1 |
20090214324 | Grinnell et al. | Aug 2009 | A1 |
20090254217 | Pack et al. | Oct 2009 | A1 |
20110025454 | Pomerantz et al. | Feb 2011 | A1 |
20110301757 | Jones et al. | Dec 2011 | A1 |
20120114187 | Duarte | May 2012 | A1 |
20130110281 | Jones et al. | May 2013 | A1 |
20130110341 | Jones et al. | May 2013 | A1 |
20130325159 | Kilibarda et al. | Dec 2013 | A1 |
Number | Date | Country |
---|---|---|
3828447 | Mar 1990 | DE |
202006004871 | Jun 2006 | DE |
0195191 | Sep 1986 | EP |
0774702 | May 1997 | EP |
S61204714 | Sep 1986 | JP |
03-285602 | Dec 1991 | JP |
07-065908 | Mar 1995 | JP |
11-077579 | Mar 1999 | JP |
2002-321179 | Nov 2002 | JP |
2006-346767 | Dec 2006 | JP |
2007-508667 | Apr 2007 | JP |
2009-511288 | Mar 2009 | JP |
9422094 | Sep 1994 | WO |
99059042 | Nov 1999 | WO |
2007004551 | Jan 2007 | WO |
2009024246 | Feb 2009 | WO |
Entry |
---|
International Search Report and Written Opinon for PCT/US2012/057513, dated Mar. 4, 2013. |
SICK LMS 200 Technical Description, Jun. 2003 [online] [retrieved Sep. 11, 2014]. Retrieved from: http://www.sick-automation.ru/images/File/pdf/LMS%20Technicai%20Description.pdf. |
Number | Date | Country | |
---|---|---|---|
20160187886 A1 | Jun 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13285511 | Oct 2011 | US |
Child | 14836548 | US |