BOT payload alignment and sensing

Information

  • Patent Grant
  • 9187244
  • Patent Number
    9,187,244
  • Date Filed
    Thursday, December 15, 2011
    13 years ago
  • Date Issued
    Tuesday, November 17, 2015
    9 years ago
Abstract
An autonomous transport robot for transporting a payload, the autonomous transport robot includes a payload bed having at least one reference datum surface and at least one payload justification device, the at least one payload justification device being configured to position a payload on the payload bed in substantial contact with the at least one reference datum surface to place the payload in a predetermined position on the payload bed.
Description
BACKGROUND

1. Field


The embodiments generally relate to storage and retrieval systems and, more particularly, to autonomous transports of the storage and retrieval systems.


2. Brief Description of Related Developments


Warehouses for storing case units may generally comprise a series of storage racks that are accessible by transport devices such as, for example, fork lifts, carts and elevators that are movable within aisles between or along the storage racks or by other lifting and transporting devices. These transport devices may be automated or manually driven. Generally the items transported to/from and stored on the storage racks are contained in carriers, for example storage containers such as trays, totes or shipping cases, or on pallets.


When transporting the cases to and from the storage racks with automated transports it would be advantageous to be able to locate the cases relative to the automated transport while holding the case securely during transport.





BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and other features of the disclosed embodiments are explained in the following description, taken in connection with the accompanying drawings, wherein:



FIG. 1 schematically illustrates an exemplary storage and retrieval system in accordance with the embodiments;



FIG. 2 illustrates a schematic plan view of an exemplary storage and retrieval system in accordance with the embodiments;



FIG. 3 illustrates a structural portion of a storage and retrieval system in accordance with the embodiments;



FIGS. 4A and 4B illustrate storage shelves in accordance with the embodiments;



FIG. 5 is an illustration of the exemplary autonomous transport vehicle in accordance with the embodiments;



FIG. 6 is a schematic illustration of a portion the exemplary autonomous transport vehicle of FIG. 5 in accordance with the embodiments;



FIG. 7A is a schematic illustration of a portion the exemplary autonomous transport vehicle of FIG. 5 in accordance with the embodiments;



FIG. 7B is another schematic illustration of a portion the exemplary autonomous transport vehicle of FIG. 5 in accordance with the embodiments;



FIG. 8 is a schematic illustration of a portion the exemplary autonomous transport vehicle of FIG. 5 in accordance with the embodiments;



FIG. 9 is a schematic illustration of a portion the exemplary autonomous transport vehicle of FIG. 5 in accordance with the embodiments;



FIG. 10 is an illustration of a portion of the exemplary autonomous transport vehicle of FIG. 5 in accordance with the embodiments; and



FIG. 11 is a flow diagram in accordance with the embodiments.





DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENT(s)


FIG. 1 schematically illustrates an exemplary storage and retrieval system in accordance with the embodiments. Although the disclosed embodiments will be described with reference to the embodiments shown in the drawings, it should be understood that the disclosed embodiments can be embodied in many alternate forms. In addition, any suitable size, shape or type of elements or materials could be used.


In accordance with the embodiments the storage and retrieval system 100 may be substantially similar to that described in, for example, U.S. patent application Ser. No. 12/757,381, entitled “STORAGE AND RETRIEVAL SYSTEM” and filed on Apr. 9, 2010, and U.S. Provisional Patent Application No. 61/423,340 entitled “Warehousing Scalable Storage Structure” filed on Dec. 15, 2010 (now U.S. patent application Ser. No. 13/326,674 filed on Dec. 15, 2011), the disclosures of which are incorporated by reference herein in their entireties and may operate in a retail distribution center or warehouse to, for example, fulfill orders received from retail stores for case units (where case units as used herein means items not stored in trays, on totes or on pallets, e.g. uncontained or items stored in trays, totes or on pallets). It is noted that the case units may include cases of items (e.g. case of soup cans, boxes of cereal, etc.) or individual items that are adapted to be taken off of or placed on a pallet. In accordance with the embodiments, shipping cases or case units (e.g. cartons, barrels, boxes, crates, jugs, totes, pallets or any other suitable device for holding case units) may have variable sizes and may be used to hold items in shipping and may be configured so they are capable of being palletized for shipping. It is noted that when, for example, bundles or pallets of case units arrive at the storage and retrieval system the content of each pallet may be uniform (e.g. each pallet holds a predetermined number of the same item—one pallet holds soup and another pallet holds cereal) and as pallets leave the storage and retrieval system the pallets may contain any suitable number and combination of different items (e.g. each pallet may hold different types of items—a pallet holds a combination of soup and cereal). In alternate embodiments the storage and retrieval system described herein may be applied to any environment in which case units are stored and retrieved.


The storage and retrieval system 100 may be configured for installation in, for example, existing warehouse structures or adapted to new warehouse structures. In the embodiments, the storage and retrieval system may include in-feed and out-feed transfer stations 170, 160, multilevel vertical conveyors 150A, 150B, a storage structure 130, and a number of autonomous transport vehicles or robots 110 (referred to herein as “bots”). The storage and retrieval system may also include robot or bot transfer stations (as described in, for example, U.S. patent application Ser. No. 12/757,220, entitled “STORAGE AND RETRIEVAL SYSTEM” and filed on Apr. 9, 2010, the disclosure of which is incorporated by reference herein in its entirety) that may provide an indirect interface between the bots 110 and the multilevel vertical conveyor 150A, 150B. The in-feed transfer stations 170 and out-feed transfer stations 160 may operate together with their respective multilevel vertical conveyors 150A, 150B for bi-directionally transferring case units to and from one or more levels of the storage structure 130. It is noted that while the multilevel vertical conveyors are described herein as being dedicated inbound or in-feed conveyors 150A and outbound or out-feed conveyors 150B, each of the conveyors 150A, 150B may be used for both inbound and outbound transfer of case units/items from the storage and retrieval system. The multilevel vertical conveyors may be any suitable lifting devices for transporting case units between levels of the storage and retrieval system. It is noted that while multilevel vertical conveyors are described herein in other aspects the conveyors may be any suitable conveyors or transfer/picking devices having any suitable transport path orientation. Some non-limiting suitable examples of multilevel vertical conveyors can be found in, for example, U.S. patent application Ser. No. 12/757,354, entitled “LIFT INTERFACE FOR STORAGE AND RETRIEVAL SYSTEMS” and filed on Apr. 9, 2010, and U.S. Provisional Patent Application No. 61/423,298 entitled “LIFT INTERFACE FOR STORAGE AND RETRIEVAL SYSTEMS” and filed on Dec. 15, 2010 (now U.S. patent application Ser. No. 13/327,088 with filed on Dec. 15, 2011), the disclosures of which are incorporated by reference herein in their entireties and U.S. patent application Ser. No. 12/757,220, entitled “STORAGE AND RETRIEVAL SYSTEM,” (previously incorporated by reference). For example, the multilevel vertical conveyors may have any suitable number of support shelves for transporting the case units to a predetermined level of the storage and retrieval system. The support shelves may have slatted supports configured to allow fingers of the bots 110 or in-feed/out-feed transfer stations 170, 160 to pass between the slats for transferring case units to and from the conveyor. It is noted that in the embodiments transfer of case units between the bots and the multilevel vertical conveyors may occur in any suitable manner.


As may be realized, the storage and retrieval system 100 may include multiple in-feed and out-feed multilevel vertical conveyors 150A, 150B that are accessible by, for example, bots 110 on each level of the storage and retrieval system 100 so that one or more case unit(s) can be transferred from a multilevel vertical conveyor 150A, 150B to each storage space on a respective level and from each storage space to any one of the multilevel vertical conveyors 150A, 150B on a respective level. The bots 110 may be configured to transfer the case units between the storage spaces and the multilevel vertical conveyors with one pick (e.g. substantially directly between the storage spaces and the multilevel vertical conveyors). By way of further example, the designated bot 110 picks the case unit(s) from a shelf of a multilevel vertical conveyor, transports the case unit(s) to a predetermined storage area of the storage structure 130 and places the case unit(s) in the predetermined storage area (and vice versa).


The bots 110 may be configured to place case units, such as the above described retail merchandise, into picking stock in the one or more levels of the storage structure 130 and then selectively retrieve ordered items for shipping the ordered items to, for example, a store or other suitable location. In the embodiments, the bots 110 may interface in any suitable manner with the multilevel vertical conveyors 150A, 150B such as through, for example, extension of a transfer arm or effector of the bot (which may have fingers for interfacing with slatted support shelves of the multi-level vertical conveyors) relative to a frame of the bot. Suitable examples of bots are described in U.S. patent application Ser. No. 12/757,312, entitled “AUTONOMOUS TRANSPORTS FOR STORAGE AND RETRIEVAL SYSTEMS” and filed on Apr. 9, 2010, U.S. Provisional Patent Application No. 61/423,365 entitled “AUTOMATED BOT WITH TRANSFER ARM” and filed on Dec. 15, 2010 (now U.S. patent application Ser. No. 13/326,952 filed on Dec. 15, 2011), U.S. Provisional Patent Application No. 61/423,388 entitled “AUTOMATED BOT TRANSFER ARM DRIVE SYSTEM” and filed on Dec. 15, 2010 (now U.S. patent application Ser. No. 13/326,993 filed on Dec. 15, 2011), U.S. Provisional Patent Application No. 61/423,359 entitled “BOT HAVING HIGH SPEED STABILITY” and filed on Dec. 15, 2010 (now U.S. patent application Ser. No. 13/326,447 filed on Dec. 15, 2011), and U.S. Provisional Patent Application No. 61/423,206 entitled “BOT SENSING POSITION” and filed on Dec. 15, 2010 (now U.S. patent application Ser. No. 13/327,035 filed on Dec. 15, 2011), the disclosures of which are incorporated by reference herein in their entireties.


The storage structure 130 may include multiple levels of storage rack modules where each level includes an array of storage spaces (arrayed on the multiple levels and in multiple rows on each level), picking aisles 130A formed between the rows of storage spaces, and transfer decks 130B. It is noted that, each level may also include respective bot transfer stations for providing an indirect interface between the bots and the multilevel vertical conveyors. In the embodiments, the picking aisles 130A and transfer decks 130B may be arranged for allowing the bots 110 to traverse respective levels of the storage structure 130 for placing case units into picking stock and to retrieve the ordered case units. As may be realized, the storage and retrieval system may be configured to allow random accessibility to the storage spaces. For example, all storage spaces in the storage structure 130 may be treated substantially equally when determining which storage spaces are to be used when picking and placing case units from/to the storage structure 130 such that any storage space of sufficient size can be used to store items. The storage structure 130 of the embodiments may also be arranged such that there is no vertical or horizontal array partitioning of the storage structure. For example, each multilevel vertical conveyor 150A, 150B is common to all storage spaces (e.g. the array of storage spaces) in the storage structure 130 such that any bot 110 can access each storage space and any multilevel vertical conveyor 150A, 150B can receive case units from any storage space on any level so that the multiple levels in the array of storage spaces substantially act as a single level (e.g. no vertical partitioning). The multilevel vertical conveyors 150A, 150B can also receive case units from any storage space on any level of the storage structure 130 (e.g. no horizontal partitioning). It is also noted that the storage and retrieval system may be configured so that each multilevel vertical conveyor serves a predetermined area of the array of storage spaces.


The storage structure 130 may also include charging stations 130C for replenishing, for example, a battery pack of the bots 110. In the embodiments, the charging stations 130C may be located at, for example, transfer areas 295 (FIG. 2) of the transfer deck 130B so that the bots 110 can substantially simultaneously transfer items, for example, to and from a multilevel vertical conveyor 150A, 150B while being charged. The bots 110 and other suitable features of the storage and retrieval system 100 may be controlled by, for example, one or more central system control computers (e.g. control server) 120 through, for example, any suitable network 180. The network 180 may be a wired network, a wireless network or a combination of a wireless and wired network using any suitable type and/or number of communication protocols. It is noted that, in the embodiments, the system control server 120 may be configured to manage and coordinate the overall operation of the storage and retrieval system 100 and interface with, for example, a warehouse management system 125, which in turn manages the warehouse facility as a whole. The control server 120 may be substantially similar to that described in, for example, U.S. patent application Ser. No. 12/757,337, entitled “CONTROL SYSTEM FOR STORAGE AND RETRIEVAL SYSTEMS” and filed on Apr. 9, 2010 (the disclosure of which is incorporated by reference herein in its entirety).


Referring also to FIG. 2, an exemplary configuration of the storage and retrieval system 100 is shown. Other suitable exemplary configurations of storage and retrieval systems can be found in, for example, U.S. Provisional Patent Application No. 61/423,340 entitled “Warehousing Scalable Storage Structure” and filed on Dec. 15, 2010 (now U.S. patent application Ser. No. 13/326,674 filed on Dec. 15, 2011), and U.S. patent application Ser. No. 12/757,381, entitled “STORAGE AND RETRIEVAL SYSTEM” and filed on Apr. 9, 2010 (the disclosures of which are incorporated by reference herein in their entireties). It should be understood that the storage and retrieval system may have any suitable configuration. As can be seen in FIG. 2, the storage and retrieval system 200 is configured, for exemplary purposes only, as a single-ended picking structure in which only one side of the system 200 has a transfer section or deck 130B. The single-ended picking structure may be used in, for example, a building or other structure having loading docks disposed only on one side of the building. In the embodiments, the storage and retrieval system 200 includes transfer deck(s) 130B and picking aisles 130A that allow bots 110 to traverse an entirety of a level of the storage structure 130 on which that bot 110 is located for transporting items between any suitable storage locations/picking aisles 130A and any suitable multilevel vertical conveyors 150A, 150B. The multilevel vertical conveyors 150A, 150B provide transport of case units into the storage and retrieval system 200 through input workstations 210 and provide output of case units from the storage and retrieval system 200 through output workstations 220. In the embodiments, the storage and retrieval system 200 includes a first and second storage section 230A, 230B located side by side so that the picking aisles of each section are substantially parallel with each other and facing the same direction (e.g. towards transfer deck 130B). It is noted that the storage and retrieval system may have any suitable number of storage sections arranged relative to each other in any suitable configuration.


Referring to FIGS. 1, 3, 4A and 4B, each of the storage bays 510, 511 of the storage structure 130 may hold the picking stock on storage shelves 600 that are separated by aisle spaces 130A. In the embodiments the storage bays 510, 511 and storage shelves 600 may be substantially similar to those described in, for example, U.S. patent application Ser. No. 12/757,220, entitled “STORAGE AND RETRIEVAL SYSTEM,” and U.S. patent application Ser. No. 12/757,381, entitled “STORAGE AND RETRIEVAL SYSTEM” (both of which being previously incorporated by reference). For example, the storage shelves 600 may include one or more support legs 620L1, 620L2 extending from, for example, the horizontal supports 610, 611, 613 (which are supported by vertical supports 612). The support legs 620, 620L2 may have any suitable configuration and may be part of, for example, a substantially U-shaped channel 620 such that the legs are connected to each other through channel portion 620B. The channel portion 620B may provide an attachment point between the channel 620 and one or more horizontal supports 610, 611, 613. It is noted that, each support leg 620L1, 620L2 may also be configured to individually mount to the horizontal supports 610, 611, 613. In the embodiments, each support leg 620L1, 620L2 includes a bent portion 620H1, 620H2 having a suitable surface area configured to support case units stored on the shelves 600. The bent portions 620H1, 620H2 may be configured to substantially prevent deformation of the case units stored on the shelves. It is noted that the leg portions 620H1, 620H2 may have a suitable thickness or have any other suitable shape and/or configuration for supporting case units stored on the shelves. As can be seen in FIGS. 4A and 4B, the support legs 620L1, 620L2 or channels 620 may form a slatted or corrugated shelf structure where spaces 620S between, for example, the support legs 620L1, 620L2 allow for arms or fingers of the bots 110 to reach into the shelving for transferring case units to and from the shelves. It is also noted that transfer of items to and from the multilevel vertical conveyors 150A, 150B (whether the transfer is made directly or indirectly by the bot 110) may occur in a substantially similar manner to that described above with respect to the storage shelves 600. It is noted that the spacing between the case units on the shelves may be any suitable spacing. It is also noted that transfer of case units to and from the multilevel vertical conveyors 150A, 150B (whether the transfer is made directly or indirectly by the bot 110) may occur in a substantially similar manner to that described above with respect to storage shelves 600.


Referring to FIG. 5 an exemplary bot 110 is shown. In the embodiments the bot 110 includes a longitudinally extended frame 110F that has a first end 1500 and a second end 1501 where the longitudinal axis 6000 extends from the first end 1500 to the second end 1501. At least one drive section 110D may be coupled to one of the first and/or second ends 1500, 1501 in any suitable manner for driving the bot 110 along the transfer deck(s) 130B and picking aisles 130A (FIG. 1). The drive 110D may include drive wheels, tracks or any other suitable drive mechanism for effecting travel of the bot along the transfer deck(s) 130B and picking aisles 130A. The other end of the bot 110 may have any suitable supports, such as caster wheels, fixed wheels, steerable wheels, and similar mechanisms for movably supporting the bot 110 as it travels along the transfer deck(s) 130B and picking aisles 130A. The bot 110 may have any suitable controller 1220 (FIG. 1) for effecting operation of the bot 110 (as described herein) and/or communication between the bot 110 and the control server 120 (FIG. 1). As may be realized the configuration of the bot shown in the drawings is merely exemplary and it should be understood that the bot may have any suitable configuration for carrying out the detection and positioning of case units relative to the bot 110 as described herein.


Referring now to FIGS. 5, 6, 7A and 7B the frame 110F of the bot 110 forms a payload bed 1510 that is configured to hold case units or any other suitable payload. The payload bed 1510 may be suitably sized for accepting (e.g. holding) any case unit 1700 (or pickface 1700P where a pickface is one or more cases that is to be picked and carried by the bot 110) that may be transferred into or removed from the storage and retrieval system 100. For example, in the embodiments the payload bed 1510 may be larger than an expected pick size (i.e. larger than the pickface 1700P the bot is expected to pick from, for example, the storage shelf 600 or any other suitable component of the storage and retrieval system such as the multilevel vertical conveyors). In this example, the pickface 1700P is shown as including two case units 1700 arranged laterally with respect to longitudinal axis 6000 of the bot 110. However, the pickface may include any suitable number of case units arranged laterally, longitudinally or in a lateral/longitudinal grid pattern.


The payload bed 1510 may include any suitable guide surfaces for allowing the case units to be transferred into the payload bed 1510 without obstruction. For example, in the embodiments the frame 110F forming the payload bed 1510 may include one or more flanges 1510C1, 1510C2 on the sides 1510S1, 1510S2 of the payload bed 1510. In this example, the flanges 1510C1, 1510C2 may be chamfered or angled surfaces at a top opening 1510TP of the payload bed 1510. The angled surfaces substantially form a wedge shape so that on contact with an edge of the case unit during transfer of the pickface into the payload area (e.g. lowering of the case unit into the payload area in the direction of arrow 1673) the angled surfaces guide the case unit(s) 1700 of the pickface 1700P into the payload area without obstructions (e.g. the case unit(s) being snagged or otherwise caught on a portion of the bot 110). The unobstructed transfer of the case units to the bot payload area facilitates loading of the case unit in one pick (e.g. substantially without repositioning the pickface or retrying the loading of the pickface onto the bot 110). While in this example the flanges 1510C1, 1510C2 are shown as being substantially straight surfaces it should be understood that the flanges may have any suitable shape and/or configuration such as for exemplary purposes only, arcuate. Also in this example, the flanges 1510C1, 1510C2 are shown as terminating substantially at an edge 1510E of the payload area, but it should be understood that the flanges may extend past the edge 1510E. Still, the flanges may be moveable or retractable such that when case units are loaded into the payload bed 1510 the flanges are moved to extend past the edge 1510E to guide the case units into the payload area and once the case units are loaded, the flanges are retracted so they do not protrude past the edge 1510E. Also, the flanges may be pivotable between a vertically upright position and the angled position shown in, for example, FIG. 7B.


A fence 1510F may be located at a side opening 1510P of the payload bed 1510. In the embodiments the fence 1510F may be attached to the frame 110F in any suitable manner such as with fasteners or welding. It is noted that the fence 1510F may form part of the frame 110F or be of unitary construction with the frame 110F. In the embodiments the fence may include slots 1510FS disposed between stopping members 1510FM. The slots 1510FS may be configured to allow the fingers 1540 to extend through the fence 1510F between the stopping members 1510FM in a substantially lowered position so that the fingers 1540 can be, for example, extended into a storage shelf 600 below a case unit. The stopping members 1510FM may be configured to extend above the payload bed 1510 to form a barrier that substantially prevents case units from exiting the payload bed 1510 once the case units are positioned on the payload bed 1510. In this example, the number of slots 1510FS is equal to the number of fingers 1540 but in alternate embodiments, the fence 1510F may be configured such that more than one finger 1540 passes through a single slot (e.g. the number of slots is less than the number of fingers). It should be noted that the fence may also have any suitable configuration for preventing case units from exiting the payload area when the case units are carried by the bot 110. For example, the fence may be movable so that the stopping members are retractable such that when in an extended configuration the fence prevents the case units from exiting the payload area.


The payload bed 1510 may include any suitable payload supports for supporting the case units when the case units are carried by the bot 110. For exemplary purposes only, in the embodiments the payload supports may include a “fluid” (or otherwise movable) bed. In one example, the bed may include rollers 1510R, where a rotational axis of each roller 1510R is disposed substantially transversely (or laterally) to the longitudinal axis 6000 of the bot 110. The payload supports may also be belts, ball bearings or any other suitable “fluid” support that moves the case units on the payload bed for at least in part justifying a location of the case unit relative to the payload bed/bot as will be described in greater detail below. Each roller may be supported within the frame 110F in any suitable manner. In this example, the rollers may be rotatably supported on one end at least in part by the fence 1510F adjacent the side opening 1510P of the payload bed 1510 and rotatably supported on the other opposite end by any suitable frame member, such as frame member 110M (FIG. 9). In the embodiments the rollers 1510R (or other suitable payload supports) may be inter-disposed with fingers 1540 of the bot 110 in an alternating manner. It is noted that the rollers 1510R and the fingers 1540 may be arranged relative to each other in any suitable manner. The rollers may be connected to any suitable drive 1532 (FIG. 8) for rotating the rollers 1510R about their axes for moving case units on the payload bed 1510 as will be described in greater detail below. For exemplary purposes only, the drive 1532 may be a belt and pulley drive 1533 as shown in FIG. 8 but it should be understood that the drive 1532 may be any drive capable of causing rotation of the rollers 1510R.


The fingers 1540 of the bot 110 extend laterally relative to the longitudinal axis 6000 of the bot. The fingers 1540 are also capable of movement in the direction of arrow 1673 (e.g. in a direction substantially perpendicular to the direction 1550 of extension and retraction of the fingers). The fingers may be driven by any suitable drive for lifting the pickfaces 1700P over the fence 1510F and into/out of the payload bed 1510 of the bot 110. One example, of a drive unit that may drive the fingers 1540 can be found in U.S. Provisional Patent Application No. 61/423,388 entitled “AUTOMATED BOT TRANSFER ARM DRIVE SYSTEM,” and filed on Dec. 15, 2010 (now U.S. patent application Ser. No. 13/326,993 filed on Dec. 15, 2011), previously incorporated by reference.


A case unit contact member 1530 may be movably located at least partially within the payload area. The case unit contact member 1530 may be driven laterally in the direction of arrow 1550 by any suitable drive 1531. For exemplary purposes only, the drive 1531 may be a belt and pulley drive 1534 (FIG. 9) but it should be understood that the drive may be any suitable drive for causing movement of the case unit contact member in the direction of arrow 1550. In the embodiments both of the case unit contact member 1530 and the fingers 1540 are configured to move laterally in the direction of arrow 1550. The case unit contact member 1530 may be configured to move along rails 1530R1, 1530R2. The rails may be mounted to the frame 110F in any suitable manner for guiding the movement of at least the case unit contact member 1530. It should be understood that the movement of the case unit contact member 1530 may be guided in any suitable manner. For exemplary purposes only, referring to FIG. 9, the case unit contact member 1530 may have slide members 1530D1, 1530D2 for movably coupling the case unit contact member 1530 to the rails 1530R1, 1530R2. The case unit contact member 1530 may be independently movable in the direction of arrow 1550 for engaging case units disposed on the payload bed 1510 as will be described in greater detail below.


Referring to FIGS. 6 and 10 the case unit contact member 1530 may be configured to allow the fingers to move in the direction of arrow 1673 (e.g. perpendicular to the plane of extension and retraction of the case contact member 1530 and fingers 1540 in the direction of arrow 1550). For example, the case unit contact member 1530 may include any suitable slots 1680 that allow each finger to be lifted in the direction of arrow 1673 without substantially contacting the case unit contact member 1530. In this example, the case unit contact member has a slot 1680 for each finger 1540 but it should be understood that the slots 1680 may have any suitable configuration such as for example, a configuration that allocated one slot to more than one finger 1540. As described above, the fence 1510F includes slots 1510FS that allow the fingers 1540 to pass through the fence 1510 in a substantially lowered position as well as in a raised position when transferring case units to and from the payload bed 1510.


Referring again to FIGS. 1, 6, 7A and 7B the bot 110 may also include any suitable sensor(s) 1703 for detecting the pickface 1700P (and case units 1700 that make up the pickface) as they are transferred to and from the payload bed 1510. In the embodiments the sensor 1703 may be a through-beam sensor. The sensor 1703 may include a transmitter 1701 and receiver 1702 that are, for example, mounted to the frame (in any suitable manner) adjacent a side opening 1510P of the payload bed 1510. The sensor 1703 may be configured and positioned on the bot 110 to sense the edges of the pickface 1700P when the pickface 1700P is transferred between, for example, a storage shelf 600 or multilevel vertical conveyors 150A, 150B and the payload bed 1510. In the embodiments the sensor 1703 may be configured to sense the leading and trailing edges 1700A, 1700B of the pickface 1700P as the pickface 1700P passes by the sensor 1703 to determine, for example, the depth D of the pickface 1700P. It should be understood that the sensor may be configured to sense any suitable feature of the pickface 1700P (e.g. the pickface as a unit and/or each individual case unit of the pickface) for determining, for example, any suitable dimensions of the pickface 1700P. In the embodiments, the bot controller 1220 (or any other suitable controller such as for example the control server 120) may be configured to register a detection signal(s) from the sensor 1703 during transfer of the case unit(s) to and/or from the bot 110. The controller 1220 may be configured to respond to the detection of the leading edge 1700A and trailing edge 1700B of the pickface 1700P for determining the depth D of the pickface 1700P. As may be realized, which edge of the pickface is the leading edge depends on which direction the pickface 1700P is travelling. For example, as the pickface 1700P enters the payload area the edge closest to the case unit contact member 1530 is the leading edge and as the pickface 1700P leaves the payload area the edge closest to the case unit contact member 1530 is the trailing edge of the pickface 1700P. For exemplary purposes only, the controller 1220 may be configured to use the leading and trailing edge sensor signals along with any other suitable information/data (such as for example indexing of a drive that drives the movement of fingers 1540 as they are extended and retracted from/to the payload bed area) for determining the pickface depth D.


The sensor 1703 may also be configured to sense if the pickface 1700P extends beyond the opening 1510P of the payload bed 1510. If the pickface does extend beyond the opening of the payload bed 1510 the controller 1220 may be configured to cause the bot 110 to time out (e.g. halt operation) so that corrective action can be taken if such an “overhanging” of the payload is detected. Such corrective action may include but is not limited to returning the payload to the storage shelf 600 from which the case was picked or if the case was picked from a multilevel vertical conveyor to a storage shelf in a location where the case units/pickfaces can be inspected and redirected to an appropriate location within the storage and retrieval system. Such corrective action may also include the bot effecting the stopping of the multilevel vertical conveyor either through communication between the bot and the multilevel vertical conveyor or through communication with, for example, the control server 120 (or any other suitable controller that communicates with both the bots and the multilevel vertical conveyor). As may be realized, the bot may include other suitable sensors to determine what amount the pickface 1700P extends beyond the opening 1510P of the payload bed 1510 where the controller 1220 only allows the bot 110 to be redirected to, for example, an inspection area if the overhang of the pickface is less than a predetermined overhang amount. The predetermined overhang amount may be any suitable overhang distance such that the overhanging pickface will not contact the structure of the storage and retrieval system, other bots or other pickfaces during redirection to, for example, the inspection area. As may also be realized, the sensor 1703 can also be used to detect and measure any gaps between the cases of the pickface.


In the embodiments, the bot 110 may also have any suitable sensors for detecting the length L (FIG. 7) of the pickface 1700P. For example, the bot 110 may include sensors 1713A, 1713B each disposed at opposite longitudinal ends of the payload bed 1510. For exemplary purposes only, the sensors 1713 may be contact plates, through beam sensors, load cells or any other suitable sensors that detect, for example, substantial contact between the case unit and the side of the payload bed 1510. The bot controller 1220 may also be configured to monitor strain (e.g. an increase in current, etc.) on the drive 1532 for detecting substantial contact between the case unit 1700 and the side 151S1, 151S2. It should be understood that while the sensors 1713 are shown in the figures as being located adjacent the sides 1510S1, 1510S2, the sensors 1713 may be located in any suitable location of the bot 110 for sensing the substantial contact between the case unit and the sides 1510S1, 1510S2.


In the embodiments, when the pickface 1700P is disposed on, for example, the rollers 1510R of the payload bed 1510, the rollers may be driven in a first direction 1551 until the pickface 1700P is sensed by a first one of the sensors 1713A, 1713B (e.g. the pickface substantially contacts a side 1510S1, 1510S2 of the payload bed 1510). A first detection signal may be sent to, for example, the bot controller 1220 indicating the pickface is disposed at a first side of the payload bed 1510. Where the pickface includes more than one case unit the rollers may continue to be driven a predetermined amount of time after a first case unit of the pickface 1700P is sensed by the sensor 1713A, 1713B so that the remaining case units 1700 of the pickface 1700P also substantially contact the side 1510S1, 1510S2 of the payload bed 1510. The rollers may then be driven in the opposite direction 1551 so that the pickface is driven towards and is sensed by the other sensor 1713A, 1713B (e.g. substantially contacts the other side 1510S1, 1510S2) disposed on the opposite side of the payload bed 1510. A second detection signal may be sent to, for example, the bot controller 1220 indicating the pickface is disposed at a second side of the payload bed 1510. Again where the pickface 1700P includes more than one case unit the roller may continue to be driven a predetermined amount of time after a first one of the case units is sensed by the sensor 1713A, 1713B to allow the other case units of the pickface to substantially contact the side 1510Sa, 1510S2. The bot controller 1220 may be configured to determine the length L of the pickface using the first and second detection signals from the sensors 1713A, 1713B in combination with, for example, data regarding the operation of the bed drive or motor 1532. It should be understood that the length L of the pickface 1700P may be determined in any suitable manner using any suitable sensors by any suitable processor or controller. In one example, the bot 110 may be configured to send pickface measurement data to, for example, control server 120 for determining the measurements of the pickface.


Referring to FIGS. 1, 5, 6, 7A, 7B, 8, 10 and 11 an exemplary operation of the bot 110 will be described. The bot 110 may be instructed by, for example the control server 120 to pick a pickface 1700P from a multilevel vertical conveyor 150A or a storage shelf 600. The bot 110 extends the fingers 1540 through the slots 1510FS in the fence 1510F and underneath the case unit to be picked. The pickface is lifted by the fingers 1540 and carried into the payload bed area. As may be realized the fingers 1540 may be raised so that when the case unit(s) are transferred into and out of the payload area of the frame 110F, the case unit(s) are carried over the stopping members 1510FM of the fence substantially without contacting the stopping members 1510FM. As the fingers are retracted into the payload bed area the controller 1220 determines the depth D of the pickface 1700P as described above (FIG. 11, Block 1102). For example, as the pickface 1700P is carried into the payload area of the bot 110 the sensor 1703 senses a first or leading edge 1700A as well as the second or trailing edge 1700B of the pickface 1700P as well as any gaps between, for example, the cases that form the pickface where the pickface includes multiple cases. As described above, the controller 1220 detects the signals from the sensor 1703 corresponding to the sensing of the first and second edges 1700A, 1700B and along with other suitable information (such as for example, data regarding the operation of the finger extension/retraction drive motor) determines the depth D of the pickface 1700P being transferred into the payload area.


The bot controller 1220 and/or the control server 120 may be programmed with an expected depth of the pickface 1700P being picked by the bot. In the embodiments the bot controller 1220 may communicate with the control server 120 and inform the control server of the pickface depth D. If the determined pickface depth D matches the expected pickface depth then a confirmation may be sent by the control server 120 to the bot controller 1220 that the correct pickface 1700P has been picked and commands the bot 110 to proceed with transportation of the pickface 1700P. In the embodiments, if the determined pickface depth D does not match the expected pickface depth then the control server 120 commands the bot 110 to return the pickface 1700P to the storage shelf 600 from which the pickface 1700P was obtained or commands the bot 110 to redirect the pickface 1700P to an area of the storage and retrieval system where the pickface 1700P can be, for example, inspected. In the embodiments if the determined pickface depth D does not match the expected pickface depth the bot 110 may be configured to verify its location within the storage and retrieval system 100 and/or re-measure the depth D of the case unit. If the pickface depth D is determined to be incorrect after bot location verification and/or pickface depth re-measurement a fault signal may be sent to, for example, the control server 120 and the bot may return the pickface 1700P back to the storage shelf 600 from which the pickface 1700P was obtained or redirect the pickface 1700P to any other suitable location within the storage and retrieval system. The bot 110 may then proceed to, for example, another storage location, multilevel vertical conveyor, etc. for picking another case unit.


If the pickface 1700P is verified as being the correct case unit, the bot 110 may be configured to justify the pickface 1700P to a predetermined position on the payload bed 1510 when the case unit is transferred into the payload area of the frame 110F (FIG. 11, Block 1103). For example, after the fingers are retracted and the case unit is positioned over the payload bed 1510 the fingers 1540 may be lowered so that the pickface 1700P is supported by, for example, the rollers 1510R (or any other suitable supports) of the payload bed 1510. The bot 110 may drive the rollers 1510R, as described above for determining the length L of the pickface, such that the pickface 1700P is located in substantial contact with a side 1510S1, 1510S2 of the payload bed 1510. When the pickface 1700P is in substantial contact with a side 1510S1, 1510S2, the bot controller 1220 may detect a signal from one of the sensors 1713A, 1713B and instruct the drive 1532 to stop driving the rollers 1510R after a predetermined time period as described above so that all case units 1700 of the pickface are in substantial contact with the side 1510S1, 1510S2. As may be realized movement of the pickface in the direction of arrow 1551 (e.g. in the direction of the longitudinal axis 6000 of the bot 110) registers a position of or locates pickface 1700P relative to the bot 110 along one axis (e.g. the longitudinal axis of the bot).


The bot 110 may also be configured to register the pickface 1700P along a second axis (e.g. the lateral axis of the bot) so that the lateral and longitudinal position of the pickface 1700P relative to the bot 110 is known. For example, a second datum reference may be formed by, for example, the fence 1510F. It is noted that the second reference datum, as well as the first reference datum, may be formed by any suitable features of the payload bed 1510. In the embodiments, the case unit contact member 1530 may be operated through any suitable drive, such as drive 1531, to move the case unit contact member 1530 towards the side opening 1510P of the payload bed 1510 for contacting and pushing the pickface 1700P substantially against the fence 1510F for locating the pickface 1700P laterally relative to the bot 110. The bot may have any suitable sensors 1714, which may be substantially similar to sensors 1713, for detecting the substantial contact between the pickface and the fence 1510F. It is noted that the bot controller 1220 may be configured to monitor strain (e.g. an increase in current, etc.) on the drive 1531 for detecting substantial contact between the pickface 1700P and the fence 1510F. As may be realized the sensors 1714 may be positioned at any suitable location relative to the payload bed 1510 for detecting the substantial contact between the pickface 1700P and the fence 1510F. As may also be realized, both drives 1531, 1532 may operate substantially simultaneously or independently of each other for moving the pickface in the directions of arrows 1550, 1551 for substantially contacting the first and second references datums (e.g. one of the sides 1510S1, 1510S2 and the fence 1510F). In this manner, as the pickface is in substantial contact with first and second reference datums (which may be substantially perpendicular to each other) the pickface 1700P is repeatably positioned at a predetermined location on the payload bed 1510.


The case unit contact member 1530 may remain in substantial contact with the pickface 1700P and work in conjunction with the fence 1510F (as shown in e.g. FIG. 10) for actively gripping the pickface 1700P between the case unit contact member 1530 and fence 1510F during transport of the pickface on the bot 110 (FIG. 11, Block 1104). To grip the pickface 1700P the bot 110 may move the case unit contact member a distance dependent on the depth D of the pickface 1700P so that the case unit contact member effects gripping of the pickface between the case unit contact member and the fence. In this manner gripping the pickface 1700P allows the position of the pickface 1700P relative to the bot 110 to be substantially maintained during transport of the pickface 1700P as well as prevent the pickface from escaping or falling off of the payload bed 1510 during transport. It is noted that the pickface may be actively gripped by the bot 110 during transport of the pickface in any suitable manner.


The bot 110 may be instructed by the control server 120 to transport the pickface 1700P located on the payload bed 1510 to a predetermined location (e.g. destination) within the storage and retrieval system 100. At the predetermined destination the case unit contact member 1530 may be moved to release the grip on the pickface 1700P. In the embodiments the bot controller 1220 may cause the drive 1532 to move the rollers 1510R so that the pickface 1700P is moved in the direction of arrow 1551 a predetermined distance away from the first reference datum (e.g. one of sides 1510S1, 1510S2) so the pickface 1700P can be lifted off of the payload bed 1510 and transferred off of the bot without substantial contact with the sides of the payload bed 1510 (e.g. unimpaired travel of the pickface 1700P from the payload bed). The bot controller 1220 may be configured to receive signals from, for example, sensors 1713 or obtain any other suitable information (such as from encoders on the drive 1532) for determining a distance between the pickface 1700P and the side 1510S1, 1510S2. When the determined distance is substantially equal to, for example, a predetermined distance (e.g. stored in a memory of the bot or control server 120) the bot controller 1220 may cause the drive 1532 to stop movement of the pickface 1700P. The bot 110 may also cause the case unit contact member to push the pickface 1700P against the fence 1510F after the pickface 1700P is moved away from the side 1510S1, 1510S2 so that the pickface 1700P is re-justified against the fence and all case units in the pickface are in substantial contact with one another. The re-justification and compacting (e.g. moving the case units together) of the pickface may be monitored in any suitable manner such as with any suitable sensors (such as those described above) and/or monitoring a condition of one or more of the bot drive motors such as the motors 1531, 1532. As the distance between the pickface 1700P and side 1510S1, 1510S2 is tracked by the controller 1220 and the pickface 1700P is re-justified against the fence 1510F the relative position between the pickface 1700P and the bot may be maintained as having a known relationship allowing the bot to place the pickface 1700P on, for example, a storage shelf 600 in a predetermined location. The predetermined location of the pickface and each of the case units therein may be stored in any suitable location such as, for example, in a memory of control server 120 for use when picking pickfaces from their respective locations on the storage shelves.


The bot controller 1220 causes the fingers 1540 to lift the pickface 1700P off of the rollers 1510R and above the stopping members 1510FM of the fence 1510F and extend laterally away from the bot 110 for placing the pickface 1700P at a desired location. When the pickface 1700P is located above its destination location, on for example, the storage shelf 600, the fingers 1540 are lowered between the stopping members 1510FM of the fence (e.g. into the slots 1510FS) and the pickface 1700P is transferred onto, for example, the support surface 620H1, 620H2 of the slatted storage shelf 600 for placing the pickface 1700P on the shelf 600 (FIG. 11, Block 1105).


In a first aspect of the disclosed embodiments, an autonomous transport robot for transporting a payload is provided. The autonomous transport robot includes a payload bed having at least one reference datum surface and at least one payload justification device, the at least one payload justification device being configured to position a payload on the payload bed in substantial contact with the at least one reference datum surface to place the payload in a predetermined position on the payload bed.


In accordance with the first aspect of the disclosed embodiments, the at least one reference datum surface includes a first and second reference datum surfaces disposed substantially perpendicular to one another and one of the first and second reference datum surfaces is substantially parallel with a longitudinal axis of the autonomous transport robot.


In accordance with the first aspect of the disclosed embodiments, the at least one justification device includes a first justification device configured to move the payload in a first direction to substantially contact the first reference datum surface and a second justification device configured to move the payload in a second direction, substantially perpendicular to the first direction, to contact the second reference datum surface.


In accordance with the first aspect of the disclosed embodiments, the first justification device includes driven rollers that form a payload support surface of the payload bed.


In accordance with the first aspect of the disclosed embodiments, the second justification device includes a driven pusher bar.


In accordance with the first aspect of the disclosed embodiments, the autonomous transport robot includes at least one sensor for detecting the substantial contact between the payload and at least one of the first and second reference datum surfaces.


In accordance with the first aspect of the disclosed embodiments, the first justification device is configured to move the payload a predetermined distance away from a respective one of the reference datum surfaces when the payload is transferred off of the payload bed and the second justification device is configured to re-justify the payload against the second reference datum surface.


In accordance with the first aspect of the disclosed embodiments, the autonomous transport robot includes a retaining fence disposed at an opening of the payload bed, the autonomous transport robot further including a driven pusher bar movably disposed at least party above the payload bed, the retaining fence and the driven pusher bar being configured to actively grip the payload during transport of the payload on the autonomous transport robot.


In accordance with the first aspect of the disclosed embodiments, the autonomous transport robot further comprises at least one sensor for detecting at least one dimension of the payload.


In accordance with a first sub-aspect of the first aspect of the disclosed embodiments, the autonomous transport robot further includes a retractable effector for transferring the payload between a payload holding area and the payload bed, the payload bed including guide surfaces configured to guide the payload into an area of the payload bed during transfer of the payload onto the autonomous transport robot.


In accordance with the first sub-aspect of the first aspect of the disclosed embodiments, the effector is configured to be raised from below the payload bed to a position at least partially above a retaining fence disposed at an opening of the payload bed, the retaining fence extending above the payload bed and being configured to at least in part retain the payload on the payload bed.


In accordance with a second aspect of the disclosed embodiments, an autonomous transport robot for transporting a payload within a storage and retrieval system is provided. The autonomous transport robot includes a payload bed having an opening, an effector for transferring the payload to and from the payload bed at least party through the opening, at least one sensor disposed adjacent the opening for sensing a first and second edge of the payload and a controller configured to determine a dimension of the payload based at least in part on the sensing of the first and second edge of the payload and to compare the determined dimension of the payload with a predetermined dimension of the payload.


In accordance with a first sub-aspect of the second aspect of the disclosed embodiments, the controller is configured generate a fault signal if the detected dimension and the predetermined dimension do not substantially match.


In accordance with the first sub-aspect of the second aspect of the disclosed embodiments, the controller is further configured to cause the effector to return the payload to a payload holding area from which it came if the detected dimension and the predetermined dimension do not substantially match.


In accordance with the first sub-aspect of the second aspect of the disclosed embodiments, the controller is further configured to verify a position of the autonomous transport robot within the storage and retrieval system if the detected dimension and the predetermined dimension do not substantially match.


In accordance with a second sub-aspect of the second aspect of the disclosed embodiments, the at least one sensor comprises at least one sensor for detecting other edges of the payload substantially transverse to the first and second edges and the controller is configured to determine another dimension of the payload that is substantially transverse to the dimension based at least in part on the detection of the other edges.


In accordance with the second sub-aspect of the second aspect of the disclosed embodiments, the autonomous transport robot further comprises a payload justification device for moving the payload in a direction on the payload bed substantially transverse to a direction of loading of the payload onto the payload bed, the payload justification device being configured to at least in part facilitate the detection of the another dimension.


It should be understood that the exemplary embodiments disclosed herein can be used individually or in any suitable combination thereof. It should also be understood that the foregoing description is only illustrative of the embodiments. Various alternatives and modifications can be devised by those skilled in the art without departing from the embodiments. Accordingly, the present embodiments are intended to embrace all such alternatives, modifications and variances that fall within the scope of the appended claims.

Claims
  • 1. An autonomous transport robot for transporting a payload comprising: a payload bed having a payload port surface and at least one movable pose defining reference datum surface; andat least one payload justification device;wherein the at least one payload justification device being configured to position a payload on the payload bed in substantial contact with the at least one pose defining reference datum surface that is arranged relative to the payload support surface to place each payload so that a payload side is at a repeatable predetermined longitudinal position, independent of a payload size, on the payload bed relative to at least a longitudinal axis of the autonomous transport robot.
  • 2. The autonomous transport robot of claim 1, wherein the at least one pose defining reference datum surface includes a first and second reference datum surfaces disposed substantially perpendicular to one another and one of the first and second reference datum surfaces is substantially parallel with the longitudinal axis of the autonomous transport robot.
  • 3. The autonomous transport robot of claim 1, wherein the autonomous transport robot includes a retaining fence disposed at an opening of the payload bed, the autonomous transport robot further including a driven pusher bar movably disposed at least partly above the payload bed, the retaining fence and the driven pusher bar being configured to actively grip the payload during transport of the payload on the autonomous transport robot.
  • 4. The autonomous transport robot of claim 1, wherein the autonomous transport robot further comprises at least one sensor for detecting at least one dimension of the payload.
  • 5. The autonomous transport robot of claim 1, wherein the autonomous transport robot further includes a retractable effector for transferring the payload between a payload holding area and the payload bed, the payload bed including guide surfaces configured to guide the payload into an area of the payload bed during transfer of the payload onto the autonomous transport robot.
  • 6. The autonomous transport robot of claim 5, wherein the effector is configured to be raised from below the payload bed to a position at least partially above a retaining fence disposed at an opening of the payload bed, the retaining fence extending above the payload bed and being configured to at least in part retain the payload on the payload bed.
  • 7. The autonomous transport robot of claim 1, wherein the at least one justification device includes a first justification device configured to move the payload in a first direction to substantially contact the first reference datum surface and a second justification device configured to move the payload in a second direction, substantially perpendicular to the first direction, to contact a second reference datum surface.
  • 8. The autonomous transport robot of claim 1, wherein the first justification device includes driven rollers that form a payload support surface of the payload bed.
  • 9. The autonomous transport robot of claim 1, wherein the second justification device includes a driven pusher bar.
  • 10. The autonomous transport robot of claim 1, wherein the autonomous transport robot includes at least one sensor for detecting the substantial contact between the payload and at least one of the first and second reference datum surfaces.
  • 11. The autonomous transport robot of claim 1, wherein the first justification device is configured to move the payload a predetermined distance away from a respective one of the pose defining reference datum surfaces when the payload is transferred off of the payload bed and the second justification device is configured to re-justify the payload against the second reference datum surface.
CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a non-provisional of and claims the benefit of U.S. Provisional Patent Application No. 61/423,220, filed on Dec. 15, 2010, the disclosure of which are incorporated by reference herein in their entirety.

US Referenced Citations (384)
Number Name Date Kind
1845962 Dorr Feb 1932 A
1887667 Wheeler Nov 1932 A
2606508 van Nes Aug 1952 A
2656995 Wolf Oct 1953 A
2673689 Bonanno Mar 1954 A
2792234 Page May 1957 A
2840248 Grove et al. Jun 1958 A
2877575 Stedt Mar 1959 A
2923421 de Senigon de Roumefort Feb 1960 A
2945604 Kroll et al. Jul 1960 A
2996621 Barrett, Jr. Aug 1961 A
3161303 Burrows Dec 1964 A
3162459 Marmorine et al. Dec 1964 A
3269744 Dobson Aug 1966 A
3369648 Weintz Feb 1968 A
3370492 Treff Feb 1968 A
3519149 Saul Jul 1970 A
3554390 Saul Jan 1971 A
3636586 Bollinger et al. Jan 1972 A
3677421 Kintner Jul 1972 A
3737056 Hathcock, Jr. Jun 1973 A
3738506 Cornford et al. Jun 1973 A
3744945 Metrailer Jul 1973 A
3746189 Burch et al. Jul 1973 A
3751758 Higbee et al. Aug 1973 A
3782565 Doran et al. Jan 1974 A
3802580 Castaldi Apr 1974 A
3850111 Hansen Nov 1974 A
3876087 Osta Apr 1975 A
3876095 Stedt Apr 1975 A
3896955 Collins et al. Jul 1975 A
3904216 Metrailer Sep 1975 A
3940105 Metrailer Feb 1976 A
3970840 De Bruine Jul 1976 A
3976302 Hammarstrand Aug 1976 A
3984012 Ennis et al. Oct 1976 A
4007843 Lubbers et al. Feb 1977 A
4026365 Andersson et al. May 1977 A
4037291 Huempfner et al. Jul 1977 A
4057019 Shaffer Nov 1977 A
4064986 Bertovich Dec 1977 A
4072203 Pierson Feb 1978 A
4079955 Thorpe et al. Mar 1978 A
4087116 Morimoto May 1978 A
4174854 Spicka et al. Nov 1979 A
4183304 Forster Jan 1980 A
4213396 Mehren et al. Jul 1980 A
4219296 Fujii et al. Aug 1980 A
4223611 Dawson et al. Sep 1980 A
4265582 Theobald May 1981 A
4271764 Braun et al. Jun 1981 A
4273234 Bourgeois Jun 1981 A
4307988 Page et al. Dec 1981 A
4346659 Binder Aug 1982 A
4349937 Fontana Sep 1982 A
4349938 Fontana Sep 1982 A
4353572 McCain Oct 1982 A
4372219 Gibbs Feb 1983 A
4372724 Stolzer Feb 1983 A
4394104 Camerini et al. Jul 1983 A
4395181 Loomer Jul 1983 A
4406570 Duncan et al. Sep 1983 A
4428708 Burt Jan 1984 A
4445440 Geiss May 1984 A
4459078 Chiantella et al. Jul 1984 A
4470742 Schindler Sep 1984 A
4492504 Hainsworth Jan 1985 A
4505630 Kaschner et al. Mar 1985 A
4527486 Baird et al. Jul 1985 A
4538950 Shiomi et al. Sep 1985 A
4678390 Bonneton et al. Jul 1987 A
4679149 Merz Jul 1987 A
4715662 van Zanten et al. Dec 1987 A
4716530 Ogawa et al. Dec 1987 A
4726725 Baker et al. Feb 1988 A
4733740 Bigowsky et al. Mar 1988 A
4750429 Mordaunt et al. Jun 1988 A
4773807 Kroll et al. Sep 1988 A
4786229 Henderson Nov 1988 A
4811229 Wilson Mar 1989 A
4812985 Hambrick et al. Mar 1989 A
4856956 Zur Aug 1989 A
4878876 Ishimoto Nov 1989 A
4883401 Kavieff Nov 1989 A
4887016 Malick Dec 1989 A
4905783 Bober Mar 1990 A
4909697 Bernard, II et al. Mar 1990 A
4936738 Brennan et al. Jun 1990 A
4966242 Baillargeon Oct 1990 A
4966513 Motoda Oct 1990 A
4993905 Potocnjak Feb 1991 A
5002449 Kita et al. Mar 1991 A
5004399 Sullivan et al. Apr 1991 A
5015145 Angell et al. May 1991 A
5069592 Galperin Dec 1991 A
5096355 Schroder Mar 1992 A
5134353 Kita et al. Jul 1992 A
5134940 Fujita et al. Aug 1992 A
5135344 Kita et al. Aug 1992 A
5140787 Corcoran Aug 1992 A
5149654 Gross et al. Sep 1992 A
5156639 Bostrom Oct 1992 A
5168815 Comer et al. Dec 1992 A
5179329 Nishikawa et al. Jan 1993 A
5187664 Yardley et al. Feb 1993 A
5199840 Castaldi et al. Apr 1993 A
5213463 Rothlisberger May 1993 A
5218909 Ng Jun 1993 A
5219264 McClure et al. Jun 1993 A
5226782 Rigling Jul 1993 A
5238100 Rose, Jr. et al. Aug 1993 A
5265944 Gloceri Nov 1993 A
5271703 Lindqvist et al. Dec 1993 A
5273392 Bernard, II et al. Dec 1993 A
5281901 Yardley et al. Jan 1994 A
5286157 Vainio et al. Feb 1994 A
5307888 Urvoy May 1994 A
5327354 Tsujimoto Jul 1994 A
5328316 Hoffmann Jul 1994 A
5333982 Tanizawa Aug 1994 A
5333983 Hatouchi et al. Aug 1994 A
5337880 Claycomb et al. Aug 1994 A
5362197 Rigling Nov 1994 A
5370492 Gleyze et al. Dec 1994 A
5377851 Asano et al. Jan 1995 A
5379229 Parsons et al. Jan 1995 A
5380139 Pohjonen et al. Jan 1995 A
5388955 Schroder Feb 1995 A
5397212 Watanabe et al. Mar 1995 A
5403147 Tanaka Apr 1995 A
5405232 Lloyd et al. Apr 1995 A
5418732 McFadin May 1995 A
5421685 Elmer et al. Jun 1995 A
5421697 Ostwald Jun 1995 A
5425612 Ebstein Jun 1995 A
5434490 Ishida et al. Jul 1995 A
5445485 Poutet Aug 1995 A
5450797 Becker et al. Sep 1995 A
5460476 Gazza Oct 1995 A
5472309 Bernard, II et al. Dec 1995 A
5501295 Muller et al. Mar 1996 A
5525884 Sugiura et al. Jun 1996 A
5529165 Shupert Jun 1996 A
5564880 Lederer Oct 1996 A
5588796 Ricco et al. Dec 1996 A
5601395 Lichti, Sr. et al. Feb 1997 A
5611422 Harkonen Mar 1997 A
5615992 Proske et al. Apr 1997 A
5626362 Mottola May 1997 A
5632350 Gauvin May 1997 A
5650703 Yardley et al. Jul 1997 A
5664688 Kitanaka et al. Sep 1997 A
5667230 Riley et al. Sep 1997 A
5668724 Ehret et al. Sep 1997 A
5707199 Faller Jan 1998 A
5718322 Mulhern Feb 1998 A
5718551 Ebstein Feb 1998 A
5725063 Ceragioli et al. Mar 1998 A
5743562 Mottola Apr 1998 A
5764014 Jakeway et al. Jun 1998 A
5801506 Netzler Sep 1998 A
5806870 Hull et al. Sep 1998 A
5810540 Castaldi Sep 1998 A
5829096 Perry Nov 1998 A
5833431 Rosse, III et al. Nov 1998 A
5839872 Goto et al. Nov 1998 A
5847537 Parmley Dec 1998 A
5857413 Ward Jan 1999 A
5866469 Hays Feb 1999 A
5918951 Rudd, III Jul 1999 A
5927926 Yagi et al. Jul 1999 A
5928058 Francis et al. Jul 1999 A
5988306 Ooishi Nov 1999 A
6000502 Leasor et al. Dec 1999 A
6021367 Pilutti et al. Feb 2000 A
6024381 Mottola Feb 2000 A
6036427 Kita et al. Mar 2000 A
6038501 Kawakami Mar 2000 A
6061607 Bradley et al. May 2000 A
6062942 Ogihara May 2000 A
6116842 Harris et al. Sep 2000 A
6149366 Deandrea Nov 2000 A
6158566 Pollock Dec 2000 A
6220676 Rudd, III Apr 2001 B1
6272406 Alofs et al. Aug 2001 B2
6324994 Glenn Dec 2001 B1
6325586 Loy Dec 2001 B1
6341269 Dulaney et al. Jan 2002 B1
6345217 Zeitler et al. Feb 2002 B1
6352035 Kashiwase et al. Mar 2002 B1
6354430 Oe Mar 2002 B1
6360673 Herrin et al. Mar 2002 B1
6389981 Strothmann et al. May 2002 B1
6390756 Isaacs et al. May 2002 B1
6391226 Chauvette et al. May 2002 B1
6425723 Okada et al. Jul 2002 B1
6439131 Higgins Aug 2002 B1
6439955 Feketo Aug 2002 B1
6503043 Smith et al. Jan 2003 B1
6508102 Margolis et al. Jan 2003 B1
6563128 Lublin May 2003 B2
6600418 Francis et al. Jul 2003 B2
6601435 Hong Aug 2003 B2
6629502 Matsukawa Oct 2003 B2
6631321 Ciprian Oct 2003 B1
6645355 Hanson et al. Nov 2003 B2
6652213 Mitchell et al. Nov 2003 B1
6655297 Kawato et al. Dec 2003 B2
6692211 Yuyama et al. Feb 2004 B2
6695328 Cope Feb 2004 B2
6721638 Zeitler Apr 2004 B2
6748292 Mountz Jun 2004 B2
6763767 Jackson et al. Jul 2004 B2
6808058 Shiohara Oct 2004 B2
6851921 Haag Feb 2005 B2
6861154 Olson et al. Mar 2005 B2
6864489 Chen et al. Mar 2005 B2
6880202 Thompson et al. Apr 2005 B2
6928336 Peshkin et al. Aug 2005 B2
6929440 Grond Aug 2005 B1
6948899 Lee Sep 2005 B2
6950722 Mountz Sep 2005 B2
6988451 Marcotte et al. Jan 2006 B2
6997665 Bouche et al. Feb 2006 B2
7002698 Hanson et al. Feb 2006 B2
7002772 Yardy Feb 2006 B2
7003375 Inui Feb 2006 B2
7008164 Rokkaku Mar 2006 B2
7011487 Kafka et al. Mar 2006 B2
7017228 Silverstein et al. Mar 2006 B2
7025191 Lichti et al. Apr 2006 B2
7058866 Flanagan et al. Jun 2006 B2
7074151 Thompson Jul 2006 B2
7085097 Starr et al. Aug 2006 B2
7100294 Goldsobel et al. Sep 2006 B1
7101139 Benedict Sep 2006 B1
7102848 Kumpon et al. Sep 2006 B2
7110855 Leishman Sep 2006 B2
7119982 Starr et al. Oct 2006 B2
7128196 Oldford et al. Oct 2006 B2
7128521 Hansl Oct 2006 B2
7135992 Karlsson et al. Nov 2006 B2
7137593 Baatz Nov 2006 B2
7145478 Goncalves et al. Dec 2006 B2
7145747 Brace et al. Dec 2006 B2
7155308 Jones Dec 2006 B2
7184855 Stingel, III et al. Feb 2007 B2
7192034 Radke et al. Mar 2007 B2
7221998 Brust et al. May 2007 B2
7266422 DeMotte et al. Sep 2007 B1
7319320 Kawashima et al. Jan 2008 B2
7329081 Baker et al. Feb 2008 B2
7381022 King Jun 2008 B1
7386379 Naik et al. Jun 2008 B2
7402018 Mountz et al. Jul 2008 B2
7426970 Olsen Sep 2008 B2
7433759 Nangoy Oct 2008 B2
7495561 Bodin et al. Feb 2009 B2
7506404 Block et al. Mar 2009 B2
7520376 Bar Apr 2009 B2
7536283 Potter et al. May 2009 B2
7539557 Yamauchi May 2009 B2
7584812 Radke et al. Sep 2009 B2
7587260 Bruemmer et al. Sep 2009 B2
7591630 Lert, Jr. Sep 2009 B2
7620477 Bruemmer Nov 2009 B2
7636982 Jones et al. Dec 2009 B2
7641014 Hu Jan 2010 B2
7648002 Easton et al. Jan 2010 B2
7661920 Kantola et al. Feb 2010 B2
7668621 Bruemmer Feb 2010 B2
7671293 Fry et al. Mar 2010 B2
7682122 Maynard et al. Mar 2010 B2
7686560 Laurin et al. Mar 2010 B2
7689318 Draper Mar 2010 B2
7695235 Rallis Apr 2010 B1
7730781 Zhang et al. Jun 2010 B2
7751928 Antony et al. Jul 2010 B1
7769513 Breed et al. Aug 2010 B2
7771152 Waltersbacher Aug 2010 B2
7792350 Kiley et al. Sep 2010 B2
7793742 Donaldson et al. Sep 2010 B2
7801644 Bruemmer et al. Sep 2010 B2
7826919 D'Andrea et al. Nov 2010 B2
7826926 Myeong et al. Nov 2010 B2
7861844 Hayduchok et al. Jan 2011 B2
7866671 Madler Jan 2011 B2
7885750 Lu Feb 2011 B2
7909562 Mead Mar 2011 B2
7926145 Liao Apr 2011 B2
7931431 Benedict et al. Apr 2011 B2
7960973 Zeller et al. Jun 2011 B2
7965871 Ihara et al. Jun 2011 B2
7967354 Faulkner et al. Jun 2011 B2
7974738 Bruemmer et al. Jul 2011 B2
7991505 Lert, Jr. et al. Aug 2011 B2
8000835 Eriz et al. Aug 2011 B2
8001837 Larson et al. Aug 2011 B2
8006824 Wada et al. Aug 2011 B2
8007221 More et al. Aug 2011 B1
8024066 Reverte et al. Sep 2011 B2
8031086 Thacher et al. Oct 2011 B2
8041456 Blackwell et al. Oct 2011 B1
8042627 Yang et al. Oct 2011 B2
8060257 Close et al. Nov 2011 B2
8136650 Frich et al. Mar 2012 B2
8280548 Zuber Oct 2012 B2
8364309 Bailey Jan 2013 B1
8378825 Dahms et al. Feb 2013 B2
8425173 Lert et al. Apr 2013 B2
8480347 Schafer Jul 2013 B2
8515575 Pfeiffer Aug 2013 B2
8594835 Lert et al. Nov 2013 B2
20020029719 Matsukawa Mar 2002 A1
20020037208 Patrito Mar 2002 A1
20020076307 Fallin et al. Jun 2002 A1
20030033217 Cutlip Feb 2003 A1
20030051544 Hong Mar 2003 A1
20030074125 Walenty et al. Apr 2003 A1
20030200129 Klaubauf et al. Oct 2003 A1
20040093116 Mountz May 2004 A1
20040167667 Goncalves et al. Aug 2004 A1
20040238326 Lichti Dec 2004 A1
20050029029 Thorne Feb 2005 A1
20050047895 Lert Mar 2005 A1
20050166787 Astrom Aug 2005 A1
20050212478 Takenaka Sep 2005 A1
20050217532 Conneally Oct 2005 A1
20060018996 Pollock et al. Jan 2006 A1
20060058921 Okamoto Mar 2006 A1
20060104712 Bufano et al. May 2006 A1
20060210382 Mountz et al. Sep 2006 A1
20060216137 Sakata et al. Sep 2006 A1
20060245862 Hansl et al. Nov 2006 A1
20060257236 Stingel et al. Nov 2006 A1
20070021864 Mountz et al. Jan 2007 A1
20070059132 Akamatsu et al. Mar 2007 A1
20070065258 Benedict et al. Mar 2007 A1
20070071585 Henkel Mar 2007 A1
20070177011 Lewin et al. Aug 2007 A1
20070276535 Haag Nov 2007 A1
20070288123 D'Andrea et al. Dec 2007 A1
20070290040 Wurman et al. Dec 2007 A1
20070293978 Wurman et al. Dec 2007 A1
20080001372 Hoffman et al. Jan 2008 A1
20080065265 Ozick et al. Mar 2008 A1
20080154429 Lee et al. Jun 2008 A1
20080161987 Breed Jul 2008 A1
20080166217 Fontana Jul 2008 A1
20080215180 Kota Sep 2008 A1
20080275609 Boydell Nov 2008 A1
20080281717 Kortelainen Nov 2008 A1
20090074545 Lert, Jr. et al. Mar 2009 A1
20090099879 Ouimet Apr 2009 A1
20090114115 Minges May 2009 A1
20090185884 Wurman et al. Jul 2009 A1
20090188774 Tsujimoto Jul 2009 A1
20090216366 Zuber et al. Aug 2009 A1
20090265031 Tachibana et al. Oct 2009 A1
20100044124 Radke et al. Feb 2010 A1
20100044977 Hughes et al. Feb 2010 A1
20100076591 Lert, Jr. Mar 2010 A1
20100086385 Shani Apr 2010 A1
20100102532 Timoney et al. Apr 2010 A1
20100131182 Deegan et al. May 2010 A1
20100135759 Dillon Jun 2010 A1
20100141483 Thacher et al. Jun 2010 A1
20100234995 Zini et al. Sep 2010 A1
20100286905 Goncalves et al. Nov 2010 A1
20100316469 Lert et al. Dec 2010 A1
20100324815 Hiruta et al. Dec 2010 A1
20110008138 Yamashita Jan 2011 A1
20110068943 Lane, Jr. Mar 2011 A1
20110090064 Dahms et al. Apr 2011 A1
20110106339 Phillips et al. May 2011 A1
20110130974 Yngve et al. Jun 2011 A1
20110176895 Kortelainen Jul 2011 A1
20110185975 van den Berg et al. Aug 2011 A1
20110202175 Romanov et al. Aug 2011 A1
20110231016 Goulding Sep 2011 A1
20110271469 Ziegler et al. Nov 2011 A1
20120189409 Toebes et al. Jul 2012 A1
20120277940 Kumar et al. Nov 2012 A1
20120299260 Goertzen et al. Nov 2012 A1
Foreign Referenced Citations (26)
Number Date Country
4104527 Aug 1992 DE
10142395 Nov 2002 DE
2011012950 Sep 2012 DE
466004 Jul 1991 EP
0466004 Jul 1991 EP
0737630 Oct 1996 EP
737630 Oct 1996 EP
1193195 Apr 2002 EP
1775240 Apr 2007 EP
2039580 Jan 2008 EP
2730715 Aug 1996 FR
4735387 Sep 1972 JP
08113321 May 1996 JP
20011344020 Dec 2001 JP
2002356207 Dec 2002 JP
2008510673 Apr 2008 JP
8501493 Apr 1985 WO
8501493 Apr 1985 WO
9534491 Dec 1995 WO
0187648 Nov 2001 WO
2005009324 Feb 2005 WO
2008152245 Dec 2008 WO
2008152245 Dec 2008 WO
2009106988 Sep 2009 WO
2010080539 Jul 2010 WO
2010118412 Oct 2010 WO
Related Publications (1)
Number Date Country
20120197431 A1 Aug 2012 US
Provisional Applications (1)
Number Date Country
61423220 Dec 2010 US