AUTONOMOUS MOBILE ROBOT
20250346304 ยท 2025-11-13
Assignee
Inventors
- Devin Rosencrance (Oshkosh, WI, US)
- Taylor Adkins (Oshkosh, WI, US)
- Louis Bafile (Oshkosh, WI, US)
- Matt Becker (Oshkosh, WI, US)
- Patrick Dingman (Oshkosh, WI, US)
- Luke Dugan (Oshkosh, WI, US)
- Milan Klimes (Oshkosh, WI, US)
- Samuel Nessibu (Oshkosh, WI, US)
- Guido Ritelli (Oshkosh, WI, US)
- Kurtis Thrush (Oshkosh, WI, US)
- Tyler Walsh (Oshkosh, WI, US)
Cpc classification
B66F7/0666
PERFORMING OPERATIONS; TRANSPORTING
B62B2205/003
PERFORMING OPERATIONS; TRANSPORTING
B62B5/065
PERFORMING OPERATIONS; TRANSPORTING
B62B2203/13
PERFORMING OPERATIONS; TRANSPORTING
B62B2205/20
PERFORMING OPERATIONS; TRANSPORTING
B62B5/005
PERFORMING OPERATIONS; TRANSPORTING
B62B3/06
PERFORMING OPERATIONS; TRANSPORTING
B62B2205/30
PERFORMING OPERATIONS; TRANSPORTING
G05B19/41865
PHYSICS
B62B3/0618
PERFORMING OPERATIONS; TRANSPORTING
B62B2203/60
PERFORMING OPERATIONS; TRANSPORTING
B66F9/18
PERFORMING OPERATIONS; TRANSPORTING
B62B3/1476
PERFORMING OPERATIONS; TRANSPORTING
G05D1/644
PHYSICS
B66F9/0755
PERFORMING OPERATIONS; TRANSPORTING
B62B3/0625
PERFORMING OPERATIONS; TRANSPORTING
G05D1/246
PHYSICS
B62B2205/04
PERFORMING OPERATIONS; TRANSPORTING
B62B2203/07
PERFORMING OPERATIONS; TRANSPORTING
B60D2001/005
PERFORMING OPERATIONS; TRANSPORTING
B60K1/00
PERFORMING OPERATIONS; TRANSPORTING
B66F7/08
PERFORMING OPERATIONS; TRANSPORTING
B62B3/00
PERFORMING OPERATIONS; TRANSPORTING
B60L50/60
PERFORMING OPERATIONS; TRANSPORTING
B62D21/02
PERFORMING OPERATIONS; TRANSPORTING
B62B3/04
PERFORMING OPERATIONS; TRANSPORTING
B66F7/065
PERFORMING OPERATIONS; TRANSPORTING
B60L58/12
PERFORMING OPERATIONS; TRANSPORTING
B66F7/0658
PERFORMING OPERATIONS; TRANSPORTING
G05D1/69
PHYSICS
B66F9/205
PERFORMING OPERATIONS; TRANSPORTING
B62B3/0643
PERFORMING OPERATIONS; TRANSPORTING
B60P1/02
PERFORMING OPERATIONS; TRANSPORTING
B62D65/18
PERFORMING OPERATIONS; TRANSPORTING
B66F7/06
PERFORMING OPERATIONS; TRANSPORTING
B62B2205/06
PERFORMING OPERATIONS; TRANSPORTING
B60P7/13
PERFORMING OPERATIONS; TRANSPORTING
G05D2101/22
PHYSICS
B60D1/62
PERFORMING OPERATIONS; TRANSPORTING
B62B2205/26
PERFORMING OPERATIONS; TRANSPORTING
B62D51/02
PERFORMING OPERATIONS; TRANSPORTING
G07C5/02
PHYSICS
B62B5/064
PERFORMING OPERATIONS; TRANSPORTING
B60D1/155
PERFORMING OPERATIONS; TRANSPORTING
B62B3/022
PERFORMING OPERATIONS; TRANSPORTING
B66F7/00
PERFORMING OPERATIONS; TRANSPORTING
International classification
Abstract
A system for transporting products throughout a manufacturing environment, includes a mobile robot including a frame, a tractive element coupled to the frame, a motor coupled to the frame and configured to drive the tractive element to propel the vehicle, at least one sensor configured to collect sensor data regarding a surrounding environment of the vehicle, an interface configured to engage a product, a lift assembly coupling the interface to the frame and configured to raise the interface relative to the frame, and a controller operatively coupled to the motor, the at least one sensor, and the lift assembly. The controller is configured to control the motor and the lift assembly based on information from the at least one sensor to autonomously transport the product.
Claims
1. A system for transporting products throughout a manufacturing environment, comprising: a mobile robot comprising: a frame; a tractive element coupled to the frame; a motor coupled to the frame and configured to drive the tractive element to propel the mobile robot; at least one sensor configured to collect sensor data regarding a surrounding environment of the mobile robot; an interface configured to engage a product; a lift assembly coupling the interface to the frame and configured to raise the interface relative to the frame; and a controller operatively coupled to the motor, the at least one sensor, and the lift assembly and configured to control the motor and the lift assembly based on information from the at least one sensor to transport the product.
2. The system of claim 1, further comprising: a subframe pivotably coupled to the frame; a second tractive element coupled to the subframe, wherein the motor and the tractive element are coupled to the frame via the subframe, and wherein the subframe pivots relative to the frame to maintain contact of the tractive element and the second tractive element with a ground surface.
3. The system of claim 1, wherein the lift assembly is a scissor assembly and comprises a lift actuator coupled between the frame and the scissor assembly so that the lift actuator is configured to selectively raise the interface relative to the frame, wherein the lift actuator is a multi-stage telescoping actuator that includes a base stage, an intermediate stage, and an outer stage, and wherein the base stage is coupled to the frame, the outer stage is coupled to the scissor assembly, and the intermediate stage is arranged between the base stage and the outer stage.
4. The system of claim 1, wherein the lift assembly is a scissor assembly, and comprises: a platform; the scissor assembly coupled between the frame and the platform and including a prop pin; a lift actuator coupled between the frame and the scissor assembly, wherein the lift actuator is configured to selectively raise the platform relative to the frame; and a support prop including a plurality of notches, wherein the support prop is pivotably coupled to a side of the scissor assembly so that when the lift actuator raises the platform, the support prop is pivotably biased to bring one of the plurality of notches into engagement with the prop pin and prevent the platform from being lowered.
5. The system of claim 1, wherein the mobile robot further comprises: a first channel and a second channel coupled to the frame, the first channel extending along a longitudinal axis and the second channel extending along a lateral axis, the first channel and the second channel each including: a first guide and a second guide offset from one another and each including a first portion and a second portion, wherein the first portions extend substantially parallel to one another, and wherein the second portions extend away from one another as the second portions extend away from the first portions.
6. The system of claim 1, the mobile robot further comprising: a cart interface for coupling a cart to the mobile robot, the cart interface comprising: a mounting bracket configured to be coupled to the frame; a cam plate pivotably coupled to the mounting bracket; an actuator coupled to the mounting bracket and the cam plate and configured to rotate the cam plate relative to the mounting bracket; and a pin coupled to the cam plate; wherein rotation of the cam plate causes the pin to move upward to engage the cart.
7. The system of claim 1, further comprising: a cart including a plurality of tractive elements and a platform configured to support the product; the mobile robot further comprising: a pin movably coupled to the frame and configured to engage the cart to couple the cart to the frame; an actuator assembly including at least one actuator, wherein the actuator assembly is configured to raise the pin relative to the frame; and wherein the controller is further configured to: control the motor to propel the mobile robot to a position in which the pin is positioned beneath the cart; and control the actuator assembly to raise the pin until the pin engages the cart to couple the cart to the frame.
8. The system of claim 1, the mobile robot further comprising: a cart interface coupled to the frame and configured to couple the mobile robot to a cart extending above the cart interface, the cart interface including: a first pin repositionable relative to the frame from a first lowered position to a first raised position to engage the cart; a second pin repositionable from a second lowered position to a second raised position to engage the cart; and an actuator coupled to the first pin and configured to move the first pin from the first lowered position to the first raised position, wherein the first pin is repositionable without requiring movement of the second pin.
9. The system of claim 1, wherein the frame comprises a front surface, a rear surface opposite the front surface, and side surfaces extending between the front surface and the rear surface, and wherein the at least one sensor comprises a first sensor oriented parallel with at least one of the front surface, the rear surface, or the side surfaces and a second sensor oriented non-parallel with the front surface, the rear surface, and the side surfaces.
10. The system of claim 1, the mobile robot further comprising: a first implement including: a first implement interface configured to be coupled to a first type of product; and a first base frame configured to be removably coupled to a mounting interface of the frame; and a second implement including: a second implement interface configured to be coupled to a second type of product; and a second base frame configured to be removably coupled to the mounting interface of the frame.
11. The system of claim 1, further comprising a tow bar coupled to the mobile robot at a first end of the tow bar and coupled to a second mobile robot at a second end of the tow bar opposite the first end, wherein, responsive to the motor propelling the mobile robot, the tow bar exerts a force on the second mobile robot to maintain a space between the second mobile robot and the mobile robot.
12. The system of claim 1, further comprising: a second mobile robot; wherein the interface comprises a platform defining a platform aperture and a cradle configured to support an end of the product for movement, the cradle rotatably coupled to the frame, the mobile robot further comprising: a bracket coupled with the cradle and defining a bracket aperture; and a pin configured to be received in a platform aperture and the bracket aperture to inhibit rotation of the cradle relative to the platform, wherein the controller is further configured to: monitor a position of the pin; and control the motor of at least one of the mobile robot or the second mobile robot based on the position of the pin; wherein the mobile robot and the second mobile robot are configured to transition between a first configuration and a second configuration by moving the pin out of the platform aperture and the bracket aperture of one of the mobile robot and the second mobile robot and into the platform aperture and the bracket aperture of the other of the mobile robot and the second mobile robot.
13. The system of claim 1, wherein the at least one sensor is moveable coupled to the frame, the mobile robot further comprising: an actuator configured to move the at least one sensor to reposition the at least one sensor relative to the frame, wherein the controller is further configured to detect an obstruction of the at least one sensor and operate the actuator to reposition the at least one sensor.
14. The system of claim 1, wherein the controller is further configured to: obtain a floorplan of a production system and a current position of the mobile robot; receive one or more inputs comprising a plurality of locations and an order of the plurality of locations; generate, based on the floorplan of the production system and a footprint of the mobile robot, a route for the mobile robot from the current position of the mobile robot to the plurality of locations in the order.
15. The system of claim 1, further comprising: a second mobile robot coupled with the mobile robot, the mobile robot and the second mobile robot configured to support the product; wherein at least one of the controller is configured to, or one or more memory devices storing instructions thereon, that, when executed by one or more processors, cause the one or more processors to: obtain one or more locations in a floorplan of a production system; obtain a route for the mobile robot and the second mobile robot, from a first current position of the mobile robot and a second current position of the second mobile robot to the one or more locations; and generate a series of coordinated motions between the mobile robot and the second mobile robot based on the route.
16. The system of claim 1, the mobile robot further comprising: at least one of an audio output device or a visual output device, wherein the controller is further configured to: determine a condition of the mobile robot; and provide an alert, via the at least one audio output device or visual output device based on the determined condition, wherein the determined condition is at least one of a plurality of conditions, and wherein each condition of the plurality of conditions is associated with a unique alert, the unique alert comprising at least one unique aspect specific to the condition relative to the other conditions of the plurality of conditions.
17. The system of claim 1, the mobile robot further comprising: a sensor coupled to the interface and configured to provide sensor data indicating a measured force on the interface, wherein the controller is further configured to: receive an indication of a current stage of assembly of the product; determine an expected force on the interface based on the current stage of assembly of the product; compare the measured force with the expected force; and in response to a determination that the measured force differs from the expected force, provide a notification to a user.
18. The system of claim 1, wherein the controller is further configured to: operate the mobile robot in a first mode of a plurality of modes, wherein the plurality of modes comprises a manual mode, a guided mobile robot mode, and an autonomous mode; determine a match value between the sensor data and at least one operational criteria of a plurality of operational criteria; and operate the mobile robot in a second mode of the plurality of modes based on the match value, wherein the second mode is different than the first mode.
19. The system of claim 1, wherein the controller is further configured to: operate the mobile robot along a first path; sense, via the at least one sensor, at least one indicator in the environment; determine, based on the at least one indicator, a boundary of a first predefined zone; determine the first path extends into the first predefined zone in the environment surrounding the mobile robot; generate a second path based on the sensor data that avoids the first predefined zone; and operate the mobile robot along the second path.
20. A system for transporting products throughout a manufacturing environment, comprising: (1) a mobile robot comprising: a frame; a tractive element coupled to the frame; a motor coupled to the frame and configured to drive the tractive element to propel the mobile robot; at least one sensor configured to collect sensor data regarding a surrounding environment of the mobile robot; an interface configured to engage a product; a lift assembly coupling the interface to the frame and configured to raise the interface relative to the frame; and a controller operatively coupled to the motor, the at least one sensor, and the lift assembly and configured to control the motor and the lift assembly based on information from the at least one sensor to transport the product, (2) the mobile robot further comprising: a subframe pivotably coupled to the frame; a second tractive element coupled to the subframe, wherein the motor and the tractive element are coupled to the frame via the subframe, and wherein the subframe pivots relative to the frame to maintain contact of the tractive element and the second tractive element with a ground surface; and (3) wherein the lift assembly is a scissor assembly and comprises a lift actuator coupled between the frame and the scissor assembly so that the lift actuator is configured to selectively raise the interface relative to the frame, wherein the lift actuator is a multi-stage telescoping actuator that includes a base stage, an intermediate stage, and an outer stage, and wherein the base stage is coupled to the frame, the outer stage is coupled to the scissor assembly, and the intermediate stage is arranged between the base stage and the outer stage; and (4) wherein the lift assembly further comprises: a platform; the scissor assembly coupled between the frame and the platform and including a prop pin; the lift actuator coupled between the frame and the scissor assembly, wherein the lift actuator is configured to selectively raise the platform relative to the frame; and a support prop including a plurality of notches, wherein the support prop is pivotably coupled to a side of the scissor assembly so that when the lift actuator raises the platform, the support prop is pivotably biased to bring one of the plurality of notches into engagement with the prop pin and prevent the platform from being lowered; and (5) the mobile robot further comprising: a first channel and a second channel coupled to the frame, the first channel extending along a longitudinal axis and the second channel extending along a lateral axis, the first channel and the second channel each including: a first guide and a second guide offset from one another and each including a first portion and a second portion, wherein the first portions extend substantially parallel to one another, and wherein the second portions extend away from one another as the second portions extend away from the first portions; and (6) the mobile robot further comprising: a cart interface for coupling a cart to the mobile robot, the cart interface comprising: a mounting bracket configured to be coupled to the frame; a cam plate pivotably coupled to the mounting bracket; a cart interface actuator coupled to the mounting bracket and the cam plate and configured to rotate the cam plate relative to the mounting bracket; and a first pin coupled to the cam plate; wherein rotation of the cam plate causes the first pin to move upward to engage the cart; and (7) wherein the cart includes a plurality of tractive elements and a platform configured to support the product, and the mobile robot further comprises: the first pin movably coupled to the frame and configured to engage the cart to couple the cart to the frame; an actuator assembly including at least one actuator, wherein the actuator assembly is configured to raise the first pin relative to the frame; and wherein the controller is further configured to: control the motor to propel the mobile robot to a position in which the pin is positioned beneath the cart; and control the actuator assembly to raise the first pin until the first pin engages the cart to couple the cart to the frame; and (8) the mobile robot further comprising: a cart interface coupled to the frame and configured to couple the mobile robot to a cart extending above the cart interface, the cart interface including: a second pin repositionable relative to the frame from a first lowered position to a first raised position to engage the cart; a third pin repositionable from a second lowered position to a second raised position to engage the cart; and a second cart interface actuator coupled to the second pin and configured to move the second pin from the first lowered position to the first raised position, wherein the second pin is repositionable without requiring movement of the third pin; and (9) wherein the frame comprises a front surface, a rear surface opposite the front surface, and side surfaces extending between the front surface and the rear surface, and wherein the at least one sensor comprises a first sensor oriented parallel with at least one of the front surface, the rear surface, or the side surfaces and a second sensor oriented non-parallel with the front surface, the rear surface, and the side surfaces; and (10) the mobile robot further comprises: a first implement including: a first implement interface configured to be coupled to a first type of product; and a first base frame configured to be removably coupled to a mounting interface of the frame; and a second implement including: a second implement interface configured to be coupled to a second type of product; and a second base frame configured to be removably coupled to the mounting interface of the frame; and (11) a tow bar coupled to the mobile robot at a first end of the tow bar and coupled to a second mobile robot at a second end of the tow bar opposite the first end, wherein, responsive to the motor propelling the mobile robot, the tow bar exerts a force on the second mobile robot to maintain a space between the second mobile robot and the first mobile robot; and (12) wherein the interface comprises a platform defining a platform aperture and a cradle configured to support an end of the product for movement, the cradle rotatably coupled to the frame, the mobile robot further comprising: a bracket coupled with the cradle and defining a bracket aperture; and a pin configured to be received in a platform aperture and the bracket aperture to inhibit rotation of the cradle relative to the platform, wherein the controller is further configured to: monitor a position of the pin; and control the motor of at least one of the mobile robot or the second mobile robot based on the position of the pin; wherein the mobile robot and the second mobile robot are configured to transition between a first configuration and a second configuration by moving the pin out of the platform aperture and the bracket aperture of one of the mobile robot and the second mobile robot and into the platform aperture and the bracket aperture of the other of the mobile robot and the second mobile robot; and (13) wherein the at least one sensor is moveable coupled to the frame, the mobile robot further comprising: a sensor actuator configured to move the at least one sensor to reposition the at least one sensor relative to the frame, wherein the controller is further configured to detect an obstruction of the at least one sensor and operate the sensor actuator to reposition the at least one sensor; and (14) wherein the controller is further configured to: obtain a floorplan of a production system and a current position of the mobile robot; receive one or more inputs comprising a plurality of locations and an order of the plurality of locations; generate, based on the floorplan of the production system and a footprint of the mobile robot, a route for the vehicle from the current position of the vehicle to the plurality of locations in the order; and (15) the second mobile robot coupled with the mobile robot, the mobile robot and the second mobile robot configured to support the product; wherein at least one of the controller is configured to, or one or more memory devices storing instructions thereon, that, when executed by one or more processors, cause the one or more processors to: obtain one or more locations in a floorplan of a production system; obtain a route for the first vehicle and the second vehicle, from a first current position of the first vehicle and a second current position of the second vehicle to the one or more locations; and generate a series of coordinated motions between the first vehicle and the second vehicle based on the route; and (16) the mobile robot further comprising: at least one of an audio output device or a visual output device, wherein the controller is further configured to: determine a condition of the mobile robot; and provide an alert, via the at least one audio output device or visual output device based on the determined condition, wherein the determined condition is at least one of a plurality of conditions, and wherein each condition of the plurality of conditions is associated with a unique alert, the unique alert comprising at least one unique aspect specific to the condition relative to the other conditions of the plurality of conditions; and (17) the mobile robot further comprising: a sensor coupled to the interface and configured to provide sensor data indicating a measured force on the interface, wherein the controller is further configured to: receive an indication of a current stage of assembly of the product; determine an expected force on the interface based on the current stage of assembly of the product; compare the measured force with the expected force; and in response to a determination that the measured force differs from the expected force, provide a notification to a user; and (18) wherein the controller is further configured to: operate the mobile robot in a first mode of a plurality of modes, wherein the plurality of modes comprises a manual mode, a guided mobile robot mode, and an autonomous mode; determine a match value between the sensor data and at least one operational criteria of a plurality of operational criteria; and operate the mobile robot in a second mode of the plurality of modes based on the match value, wherein the second mode is different than the first mode; and (19) wherein the controller is further configured to: operate the mobile robot along a first path; sense, via the at least one sensor, at least one indicator in the environment; determine, based on the at least one indicator, a boundary of a first predefined zone; determine the first path extends into the first predefined zone in the environment surrounding the mobile robot; generate a second path based on the sensor data that avoids the first predefined zone; and operate the mobile robot along the second path.
21-380. (canceled)
Description
BRIEF DESCRIPTION OF THE FIGURES
[0006] The disclosure will become more fully understood from the following detailed description, taken in conjunction with the accompanying figures, wherein like reference numerals refer to like elements, in which:
[0007]
[0008]
[0009]
[0010]
[0011]
[0012]
[0013]
[0014]
[0015]
[0016]
[0017]
[0018]
[0019]
[0020]
[0021]
[0022]
[0023]
[0024]
[0025]
[0026]
[0027]
[0028]
[0029]
[0030]
[0031]
[0032]
[0033]
[0034]
[0035]
[0036]
[0037]
[0038]
[0039]
[0040]
[0041]
[0042]
[0043]
[0044]
[0045]
[0046]
[0047]
[0048]
[0049]
[0050]
[0051]
[0052]
[0053]
[0054]
[0055]
[0056]
[0057]
[0058]
[0059]
[0060]
[0061]
[0062]
[0063]
[0064]
[0065]
[0066]
[0067]
[0068]
[0069]
[0070]
[0071]
[0072]
[0073]
[0074]
[0075]
[0076]
[0077]
[0078]
[0079]
[0080]
[0081]
[0082]
[0083]
[0084]
[0085]
[0086]
[0087]
[0088]
[0089]
[0090]
[0091]
[0092]
[0093]
[0094]
[0095]
[0096]
[0097]
[0098]
[0099]
[0100]
[0101]
[0102]
[0103]
[0104]
[0105]
[0106]
[0107]
[0108]
[0109]
[0110]
[0111]
[0112]
[0113]
[0114]
[0115]
[0116]
[0117]
[0118]
[0119]
[0120]
[0121]
[0122]
[0123]
[0124]
[0125]
[0126]
[0127]
[0128]
[0129]
[0130]
[0131]
[0132]
[0133]
[0134]
[0135]
[0136]
[0137]
[0138]
[0139]
[0140]
[0141]
[0142]
[0143]
DETAILED DESCRIPTION
[0144] Before turning to the figures, which illustrate certain exemplary embodiments in detail, it should be understood that the present disclosure is not limited to the details or methodology set forth in the description or illustrated in the figures. It should also be understood that the terminology used herein is for the purpose of description only and should not be regarded as limiting.
Overall Vehicle
[0145] Referring to
[0146] The vehicle 10 may be manually controlled, partially autonomous, or fully autonomous. In some embodiments, the vehicle 10 is configured as a semi-automated guided vehicle (SGV). When configured as an SGV, the vehicle 10 may be manually operated by an operator (e.g., through a wireless or tethered user interface). By way of example, the operator may manually control the steering of the vehicle 10. In some embodiments, the vehicle 10 is configured as an automated guided vehicle (AGV). When configured as an AGV, the vehicle 10 may navigate along a predefined route (e.g., using a magnetic strip or other fixed navigation element). If the vehicle 10 configured as an AGV encounters an obstacle, the vehicle 10 may rely on manual intervention from an operator (e.g., through a user interface) to correct course and navigate around the obstacle. In some embodiments, the vehicle 10 is configured as an autonomous mobile robot (AMR). When configured as an AMR, the vehicle 10 may autonomously navigate through an area without requiring a predefined path. The vehicle 10 configured as an AMR may avoid obstacles without manual intervention by an operator.
[0147] The vehicle 10 includes a chassis, shown as frame 12, that supports the other components of the vehicle 10. In some embodiments, the frame 12 defines an enclosure that contains one or more components of the vehicle 10. The frame 12 includes a pair of side portions, shown as drive modules 14, a central portion, shown as controls enclosure 16, and a lateral member, shown as back plate 18. The drive modules 14 each extend longitudinally along the vehicle 10 and are laterally offset from one another. The controls enclosure 16 and the back plate 18 each extend laterally between the drive modules 14, fixedly coupling the drive modules 14 to one another. The controls enclosure 16 and the back plate 18 are longitudinally offset from one another, such that a recess or passage, shown as implement recess 20, is defined between the controls enclosure 16, the back plate 18, and the drive modules 14.
[0148] The drive modules 14 may contain components that facilitate propulsion of the vehicle (e.g., the drivetrain 40). The drive modules 14 may include one or more removable or repositionable panels, shown as drive module doors 24, that facilitate access to components within the drive modules 14 from outside of the vehicle 10. The controls enclosure 16 may contain components that facilitate powering or control over the vehicle (e.g., the controller 102, the batteries 110). The controls enclosure 16 includes a removable or repositionable panel, shown as controls enclosure door 22, that facilitates access to components within the controls enclosure 16 from outside of the vehicle 10. In other embodiments, the vehicle 10 includes a separate housing, body, or enclosure that is coupled to the frame 12 and contains one or more components of the vehicle.
[0149] The frame 12 defines a top surface 30, a front surface 32, a rear surface 34, and a pair of side surfaces 36 of the vehicle 10. The top surface 30 extends substantially horizontally across the drive modules 14 and the controls enclosure 16. A distance from the top surface 30 to the ground beneath the vehicle 10 may define a height of the vehicle 10. The front surface 32 is positioned at a front end portion of the frame 12 and extends substantially vertically and laterally across the drive modules 14 and the controls enclosure 16. The rear surface 34 is positioned at a rear end portion of the frame 12 and extends substantially vertically and laterally across the drive modules 14 and the back plate 18. The side surfaces 36 each extend longitudinally along one of the drive modules 14, between the front surface 32 and the rear surface 34.
[0150] The vehicle 10 includes a drive system or driveline, shown as drivetrain 40, that is configured to propel and steer the vehicle 10. The driveline includes a pair of actuators or motors (e.g., hydraulic motors, pneumatic motors, electric motors, etc.), shown as drive motors 42. In some embodiments, the drive motors 42 are electric motors powered by an electrical energy source (e.g., the batteries 110, energy from a power grid external to the vehicle 10, etc.). The drive motors 42 are each configured to provide rotational mechanical energy to drive rotation of one or more tractive elements 44 (e.g., wheel and tire assemblies as shown in
[0151] The frame 12, the drivetrain 40, and various other components coupled to the frame 12 form a base portion of the vehicle 10, shown as base assembly 48. To facilitate moving a product, the vehicle 10 may include an implement that that selectively couples the base assembly 48 to a product.
[0152] Referring to
[0153] Certain large products, such as the telehandler 56, may be difficult to support with only a single vehicle 10. To facilitate steering the product and spreading out the weight of the product, multiple vehicles 10 may be utilized. In the example shown in
[0154] Referring to
[0155] When extended, the driving pin 62 and the turning pin 64 each engage the cart 66 to limit movement of the cart 66 relative to the base assembly 48. When both the driving pin 62 and the turning pin 64 engage the cart 66, the cart 66 may be rotatably fixed to the base assembly 48. When only the driving pin 62 engages the cart 66, the base assembly 48 may rotate freely about the central axis 46 relative to the cart 66, but movement of the vehicle 10 in a particular direction may cause movement of the cart 66 in that same direction. When the driving pin 62 and the turning pin 64 are both retracted away from the cart 66, the vehicle 10 may move freely relative to the cart 66.
[0156] The cart 66 may be equipped with casters or slides to facilitate free movement of the cart 66 along the ground. In some embodiments, the cart 66 supports some or all of the weight of the boom assembly 68. The driving pin 62 and the turning pin 64 may generally push horizontally on the cart 66, such that there may be little or no transmission of vertical forces between the cart implement 60 and the cart 66. Accordingly, the vertical load on the vehicle 10 may be minimized while still permitting the vehicle 10 move the cart 66 and the boom assembly 68 throughout the environment as desired. This reduction in load may reduce the overall cost of the vehicle 10.
[0157] Referring to
[0158] The vehicle 10 includes a controller 102 that controls operation of the vehicle 10. The controller 102 includes a processing circuit, shown as processor 104, and a memory device, shown as memory 106. The memory 106 may contain one or more instruction that, when executed by the processor 104, cause the processor to perform the various functions described herein.
[0159] The controller 102 further includes a communication interface 108 (e.g., a communication circuit, a network interface, etc.) that facilitates communication with (e.g., to and from) other components of the vehicle 10 and/or the control system 100. The communication interface 108 may facilitate wired communication (e.g., through CAN, Ethernet, communication of power, etc.). Additionally or alternatively, the communication interface 108 may facilitate wireless communication (e.g., through Bluetooth, Wi-Fi, radio transmission, inductive transmission of energy, etc.).
[0160] The base assembly 48 includes one or more energy storage devices, shown as batteries 110. The batteries 110 store energy (e.g., as chemical energy). The batteries 110 may deliver electrical energy to other components of the vehicle 10 to power the vehicle 10. The batteries 110 may be charged by an outside source of energy (e.g., an electrical grid, a wireless charging interface, etc.). In other embodiments, the base assembly 48 includes a different type of energy storage device (e.g., a fuel tank for an internal combustion engine of a generator, a fuel cell, etc.).
[0161] The base assembly 48, the lifting implement 50, and the cart implement 60 may each include one or more sensors 112 operatively coupled to the controller 102. The sensors 112 may provide sensor data describing the current status of the vehicle 10 and/or the surrounding environment. By way of example, the sensors 112 may include mapping or imaging sensors (e.g., LIDAR sensors, light curtains, cameras, ultrasonic sensors, etc.). By way of example, the sensors 112 may include position sensors (e.g., GPS, potentiometers, encoders, etc.). By way of example, the sensors 112 may include orientation or acceleration sensors (e.g., accelerometers, gyroscopic sensors, inertial measurement units, compasses, etc.). By way of example, the sensors 112 may include pressure sensors, flowmeters, buttons, or other types of sensors.
[0162] The base assembly 48 may include one or more operator interface elements (e.g., input devices, output devices, etc.), shown as user interface 114. The user interface 114 may include output devices that provide information to one or more users. By way of example, the user interface 114 may include displays, speakers, lights, haptic feedback (e.g., vibrators, etc.), or other output devices. The user interface 114 may include input devices that receive information (e.g., commands) from one or more users. By way of example, the user interface 114 may include buttons, switches, knobs, touchscreens, microphones, or other input devices.
[0163] The lifting implement 50 and/or the cart implement 60 may include one or more actuators 116 that facilitate controlled movement (e.g., movement of the lifting implement 50 or the cart implement 60). The actuators 116 may include linear actuators (e.g., electric linear actuators, hydraulic cylinders, etc.), motors (e.g., electric motors, hydraulic motors, etc.), or other types of actuators. The actuators 116 may be electrically-powered, hydraulically-powered, or otherwise powered.
[0164] The lifting implement 50 and/or the cart implement 60 may include a hydraulic system 120. The hydraulic system 120 may supply pressurized hydraulic fluid (e.g., hydraulic oil) to facilitate operation of other components of the vehicle 10. By way of example, the hydraulic system 120 may supply pressurized hydraulic fluid to an actuator 116. In some embodiments, the hydraulic system 120 forms a self-contained hydraulic loop with one or more actuators 116.
[0165] The hydraulic system 120 includes a low-pressure reservoir, shown as tank 122, that stores a volume of hydraulic fluid at a low pressure. A pump 124 receives electrical energy from the batteries 110, draws hydraulic fluid from the tank 122, and supplies a flow of pressurized hydraulic fluid. One or more valves 126 (e.g., solenoid valves, directional control valves, etc.) control the flow of the hydraulic fluid from the pump 124. By way of example, the valves 126 may control the flow rate, direction, and destination of hydraulic fluid flowing throughout the hydraulic system 120. The controller 102 may control operation of the actuators 116 by controlling the valves 126.
[0166] The control system 100 further includes additional devices in communication with the vehicle 10. The devices may communicate with the vehicle 10 directly or through a network 130 (e.g., a local area network, a wide area network, the Internet, etc.). The network 130 may utilize wireless and/or wired communication. In some embodiments, the network 130 is a mesh network formed between multiple devices of the control system 100 (e.g., permitting indirect communication between two devices through a third device).
[0167] The control system 100 may include multiple vehicles 10. A vehicle 10 may communicate with other vehicles 10 to share information and facilitate operation. By way of example, a vehicle 10 may provide commands to another vehicle 10 to coordinate transportation of a large item that is carried by both of the vehicles 10. By way of another example, a vehicle 10 may provide its location to another vehicle 10 to facilitate path generation and avoid collisions.
[0168] The control system 100 may include one or more user devices 132 (e.g., smartphones, tablets, laptops, desktop computers, etc.). The user devices 132 may facilitate a user monitoring and/or controlling operation of the vehicles 10. By way of example, the user devices 132 may indicate statuses of the vehicles 10 (e.g., positions, whether maintenance is needed, if any errors are occurring, what task a vehicle 10 is assigned, etc.). By way of example, the user devices 132 may permit a user to command a vehicle 10 to travel to a different place or to assign a vehicle 10 to a particular production line.
[0169] The control system 100 may include one or more remote devices 134 (e.g., servers). In some embodiments, a remote device 134 functions as a production manager that controls various operations throughout a manufacturing environment. The production manager may receive requests for production of certain equipment (e.g., fifteen telehandlers are requested for production by Apr. 12, 2025, etc.). The production manager may monitor the statuses of vehicles 10, personnel, equipment, and raw materials. By way of example, the vehicles 10 may provide sensor data from the sensors 112 to a remote device 134 for storage and/or analysis. Based on the available data, the production manager may generate assignments for vehicles 10, personnel, equipment, and raw materials to meet the production requests. The production manager may adapt to changes in availability (e.g., by reassigning a vehicle 10 to a different task or area in response to a failure of one of the vehicles 10). The assignments for a vehicle 10 may include a path along which the vehicle 10 should travel, a desired configuration of the vehicle 10 (e.g., the type of implement available to the vehicle 10), an amount of time that the vehicle 10 should wait at a given station, etc.
[0170] Referring to
[0171] Initially the product 152 and the subassembly 154 move along separate manufacturing lines 156 and 158. After the last station 160 needed to prepare the subassembly 154, the manufacturing line 158 intersects the manufacturing line 156, and the subassembly 154 is attached to the product 152. The product 152 and the subassembly 154 then move together along the manufacturing line 156. This proceeds until the product 152 is fully assembled and removed from the vehicles 10. The vehicles 10 may then return to collect another product that requires assembly, and the manufacturing process is repeated.
[0172] In some embodiments, the product 152 assembled by the production system is a vehicle or work machine. By way of example, the product 152 may be a lift device, such as a telehandler, a scissor lift, a boom lift, a vertical lift, an aerial work platform, or another type of lift device. By way of another example, the product 152 may be a fire truck, an aircraft rescue and firefighting apparatus (ARFF) truck, a refuse vehicle, a concrete mixing truck, a tow truck, a broadcast van, a military vehicle, a robot, a truck, a van, a passenger vehicle, or another type of vehicle. In other embodiments, the product 152 is not a vehicle (e.g., is a stationary piece of equipment).
Drive Arrangement
[0173] Referring generally to the figures, a vehicle may include a drive arrangement to maneuver the vehicle about a ground surface and maintain engagement of the vehicle with the ground surface. More specifically, the drive arrangement may include one or more subframes coupled to a frame of the vehicle. The one or more subframes each include a drive wheel driven by a motor and a caster wheel. The one or more subframes may pivot to maintain engagement of the drive wheel and the caster wheel with the ground surface. The drive arrangement may include one or more caster wheels, which also maintain contact with the ground surface, to distribute the weight of the vehicle and facilitate steering of the vehicle as the vehicle maneuvers the ground surface.
[0174] Referring generally to the figures, a vehicle that is utilized in a manufacturing line or process is shown. The vehicle includes a frame and a base assembly coupled to the frame. The base assembly is configured to couple various implements to the frame, and the implements facilitate positioning, supporting, and/or lifting of a component of a product (e.g., a telehandler or an axle assembly of a telehandler). In some embodiments, the implement includes a lift implement with a cradle that receives and supports the component of the product and a lift assembly coupled between the cradle and the base assembly. The lift assembly includes a plurality of lift arms that are pivotably coupled to one another (e.g., a scissor stack or a scissor assembly). A lift actuator is coupled between the base assembly and the lift arms and is configured to selectively raise the cradle relative to the base assembly. In some embodiments, the lift actuator is in the form of a multi-stage telescoping actuator that includes a base stage, an Before turning to the figures, which illustrate certain exemplary embodiments in detail, it should be understood that the present disclosure is not limited to the details or methodology set forth in the description or illustrated in the figures. It should also be understood that the terminology used herein is for the purpose of description only and should not be regarded as limiting.
[0175] Referring generally to the figures, a vehicle may include a drive arrangement to maneuver the vehicle about a ground surface and maintain engagement of the vehicle with the ground surface. More specifically, the drive arrangement may include one or more subframes coupled to a frame of the vehicle. The one or more subframes each include a drive wheel driven by a motor and a caster wheel. The one or more subframes may pivot to maintain engagement of the drive wheel and the caster wheel with the ground surface. The drive arrangement may include one or more caster wheels, which also maintain contact with the ground surface, to distribute the weight of the vehicle and facilitate steering of the vehicle as the vehicle maneuvers the ground surface.
[0176] Referring to
[0177] The first drive module 210 and one of the wheels 290 (e.g., a third caster wheel 292) are positioned along a first lateral or left side 206 of the vehicle 10 and located within the drive module 14 on the left side 206 of the vehicle 10. The first drive module 210 is coupled to the side surface 36 (e.g., on the right side of the vehicle 10) and a first interior wall 211 of the frame 12 (e.g., see
[0178] Referring to
[0179] Referring to
[0180] The first subframe 218 further includes a pivot assembly or link, shown as pivot pin 232 that extends through the outer portion 224 and the inner portion 226 (e.g., through apertures defined by bushings of the outer portion 224 and the inner portion 226) and is positioned between the front portion 220 and the rear portion 222 of the first subframe 218. The pivot pin 232 pivotably couples the first subframe 218 to the side surface 36 and the inner wall 211 of the frame 12. In some embodiments, the pivot pin 232 extends below the central wall 221 of the front portion 220. The pivot pin 232 defines a first lateral axis 230 that extends through the center of the pivot pin 232. The pivot pin 232 is configured to allow the first subframe 218 to pivot relative to the frame 12 about the first lateral axis 230.
[0181] In some embodiments, the first subframe 218 further includes a biasing element (e.g., a coil spring, a gas spring, a hydraulic actuator, etc.), shown as a first biasing element 228. The first biasing element 228 is coupled to the rear portion 222 of the first subframe 218 (e.g., see
[0182] Referring to
[0183] Similar to the first subframe 218, the second subframe 258 includes a first or front portion disposed toward the front surface 32 of the frame 12, an opposing, second, or rear portion, an outer or first lateral portion disposed toward the side surface 36, and an opposing, inner, or second lateral portion from the front portion to the rear portion. The front portion includes a middle or extending portion, shown as central wall, extending between the outer portion and a portion of the inner portion. The second caster wheel 256 is coupled to the central wall of the front portion of the second subframe 258 by a bracket (e.g., caster wheel bracket or mount), and the second drive wheel 254 is coupled to the outer portion towards the rear portion of the second subframe 258.
[0184] The second subframe 258 further includes a pivot assembly or link, shown as pivot pin 272 that extends through the outer portion and the inner portion and is positioned between the front portion and the rear portion of the second subframe 258. The pivot pin 272 pivotably couples the second subframe 258 to the side surface 36 and the inner wall 251 of the frame 12. In some embodiments, the pivot pin 272 extends below the central wall of the front portion of the second subframe 258. The pivot pin 272 defines a second lateral axis 270 that extends through the center of the pivot pin 272. The pivot pin 272 is configured to allow the second subframe 258 to pivot relative to the frame 12 about the second lateral axis 270. In some embodiments, the second subframe 258 further includes a coil spring, a gas spring, a hydraulic actuator, or other biasing element substantially similar or identical to the first biasing element 228 of the first subframe 218. In some embodiments, the second subframe 258 will engage a bumper 274 coupled to the top surface 30 of the frame 12 that is substantially similar or identical to the bumper 234.
[0185] The first drive module 210 and the second drive module 250 are configured to operate or function independently from each other to maneuver and/or propel the vehicle 10 over a ground surface (e.g., the first subframe 218 and the second subframe 258 pivot different amounts or degrees, the first drive motor 212 and the second drive motor 252 operate at different speeds and/or directions, one or more of the first caster wheel 216, the second caster wheel 256, the third caster wheel 292, or the fourth caster wheel 294 move in different directions or speeds, etc.). Independent motion of the drive modules 210 and 250 may facilitate operation on inconsistent ground surfaces (e.g., ground surfaces that are not flat).
[0186] In some embodiments, the vehicle 10 may traverse the ground surface, which may be uneven, sloped, curved, or include thresholds, bumps, divots, cracks, etc. By way of example, the first drive motor 212 drives the first drive wheel 214, and the first subframe 218 pivots about the first lateral axis 230 to maintain engagement of the first drive wheel 214, the first caster wheel 216, and the third caster wheel 292 with the ground surface. Similarly, the second drive motor 252 drives the second drive wheel 254, and the second subframe 258 pivots the second lateral axis 270 to maintain engagement of the second drive wheel 254, the second caster wheel 256, and the fourth caster wheel 294 with the ground surface. In some embodiments, the first lateral axis 230 and the second lateral axis 270 align or coincide as the first subframe 218 and the second subframe 258 each independently pivot relative to the frame 12 to main engagement of the first drive wheel 214, the first caster wheel 216, the second caster wheel 256, the second drive wheel 254, the third caster wheel 292, or the fourth caster wheel 294 with the ground surface. In other embodiments, as on a sloped ground surface, the first lateral axis 230 and the second lateral axis 270 are unaligned as the first subframe 218 and the second subframe 258 each independently pivot relative to the frame 12 to main engagement of the first drive wheel 214, the first caster wheel 216, the second caster wheel 256, the second drive wheel 254, the third caster wheel 292, or the fourth caster wheel 294 with the ground surface.
[0187] In some embodiments, the first drive motor 212 and the second drive motor 252 operate independently from one another to facilitate skid steer operation of the vehicle 10. By way of example, the first drive motor 212 and the second drive motor 252 may drive the first drive wheel 214 and the second drive wheel 254, respectively, at the same speed to drive the vehicle 10 straight. By way of another example, the first drive motor 212 and the second drive motor 252 may drive the first drive wheel 214 and the second drive wheel 254, respectively, at different speeds and/or in different directions (e.g., one drive wheel rotates forward while the other drive rotates backwards) to turn the vehicle 10 about a central or substantially vertical axis 276. In some embodiments, the front surface 32, the rear surface 34, and the pair of side surfaces 36 of the frame 12 define an outer perimeter of the frame 12, within which the central vertical axis 276 extends. In such embodiments, the central vertical axis 276 may shift based on the relative speeds and directions of the first drive motor 212 and the second drive motor 252.
[0188] Referring to
[0189] Referring to
[0190] Referring to
[0191] Referring to
[0192] Referring to
[0193] The first drive module 210 includes a bracket 314. The bracket 314 includes a first portion 316 and a second portion 318. The first portion 316 extends substantially perpendicular to the second portion 318. The first portion 316 and the second portion 318 are each configured to couple to a mounting location 320 on the frame 12 (as shown in
Lifting Implement
[0194] Referring generally to the figures, a vehicle that is utilized in a manufacturing line or process is shown. The vehicle includes a frame and a base assembly coupled to the frame. The base assembly is configured to couple various implements to the frame, and the implements facilitate positioning, supporting, and/or lifting of a component of a product (e.g., a telehandler or an axle assembly of a telehandler). In some embodiments, the implement includes a lift implement with a cradle that receives and supports the component of the product and a lift assembly coupled between the cradle and the base assembly. The lift assembly includes a plurality of lift arms that are pivotably coupled to one another (e.g., a scissor stack or a scissor assembly). A lift actuator is coupled between the base assembly and the lift arms and is configured to selectively raise the cradle relative to the base assembly. In some embodiments, the lift actuator is in the form of a multi-stage telescoping actuator that includes a base stage, an intermediate or middle stage, and an end or distal stage. The inclusion of a multi-stage actuator facilitates a compact arrangement of the lift assembly, for example, when fully retracted (e.g., greater extension range or stroke but smaller size when fully retracted). In some embodiments, the lift actuator is hydraulically controlled and operated by a lift valve that selectively supplies hydraulic fluid (e.g., oil) to the lift actuator to extend one or more stages of the lift actuator. In some embodiments, the stages of the lift actuator are retracted by gravity and the weight acting on the cradle.
[0195] In some embodiments, the lift assembly includes a support prop or prop wing arranged to both lateral sides of the scissor assembly that is configured to permit extension of the lift actuator but that acts in compression to resist retraction of the scissor assembly. In general, the prop wings acts to hold the cradle in one of various raised positions, for example, in the event of a power or pressure failure, to prevent the cradle from involuntarily retracting toward the base assembly. In some embodiments, the prop wings are pivotably coupled to the scissor assembly and each include a plurality of recesses or notches that are configured to engage a pin of the scissor assembly. The prop wings are biased, for example via gravity and/or a gas spring, in a direction that urges one of the notches into engagement with the pin of the scissor assembly. When one of the notches engages and receives the pin, the scissor assembly is prevented from retracting and held in its raised position. With the prop wings each including a plurality of notches, the prop wings are configured to operate and hold the cradle in a plurality of raised positions. In some embodiments, the prop wings are each coupled to a prop actuator that are configured to selectively pivot the prop wings out of engagement with the pin to enable the cradle to be lowered.
[0196] In some embodiments, the cradle is supported on and rotatably coupled to a top platform. For example, the cradle is rotatable about a vertical axis, which allows the cradle to rotate relative to the frame/base assembly and enables steering operation of the vehicle, for example, when the product is supported by and spans between two of the vehicles. In some embodiments, the cradle includes an arcuate slot within which a pin (e.g., a shoulder bolt) is received, and the ends of the arcuate slot limit the rotational movement of the cradle relative to the top platform and the frame/base assembly.
[0197] In some embodiments, the cradle includes a pair of laterally separated bracket assemblies that define a channel or slot within which the component (e.g., an axle assembly of a telehandler is received). The bracket assemblies each include a fixed bracket and a movable bracket. The movable bracket is configured to be selective moved relative to the fixed bracket to adjust (e.g., increase or decrease) a distance between the movable bracket and the fixed bracket, which allows the cradle to receive different sized components (e.g., an axle of a telehandler).
[0198] As described herein, the base assembly 48 of the vehicle 10 may be selectively coupled to an implement that facilitates supporting and/or moving of the component or product. In some embodiments, the base assembly 48 is coupled to the lifting implement 50 that both supports the product and selectively raises and lowers the product relative to the base assembly 48.
[0199] In some embodiments, the lift assembly 54 includes a scissor assembly 404 formed by a plurality of lift arms 406 that are pivotably coupled to one another in a crisscross or X-shaped arrangement. The scissor assembly 404 is coupled between the bottom platform 400 (e.g., the base assembly 48) and the top platform 402. In some embodiments, each of the lift arms 406 is in the form of a lift plate. The lift arms 406 may include a lower section 408 and an upper section 410. The lower section 408 includes a plurality of the lift arms 406, with each of the lift arms 406 in the lower section 408 being pivotably coupled to the bottom platform 400 at one end and to a respective one of the lift arms 406 in the upper section 410 at an opposing end. The upper section 410 includes a plurality of the lift arm 406, with each of the lift arms 406 in the upper section 410 being pivotably coupled to a respective one of the lift arms 406 in the lower section 408 at one end and to the top platform 402 at an opposing end.
[0200] The ends of each of the lift arms 406 are pivotably coupled to the bottom platform 400, the top platform 402, or another end of one of the lift arms 406 by a pivot pin 412. For example, at least two of the lift arms 406 in the lower section 408 are pivotably coupled at one end to the bottom platform 400 by one of the pivot pins 412 that extends through a base bracket 414 (see, e.g.,
[0201] The ends of the lift arms 406 of the upper section 410 that are pivotably coupled to another end of one of the lift arms 406 in the lower section 408 (e.g., an end not coupled to the top platform 402) are rigidly coupled to a pair of intermediate brackets. For example, each lower end of the lift arms 406 in the upper section 410 is rigidly coupled to (e.g., welded) an inner intermediate bracket 418 and an outer intermediate bracket 419 (see, e.g.,
[0202] In some embodiments, each of the pivot pins 412 may be in a double shear arrangement (e.g., bracket-lift arm-bracket). For example, each of the base brackets 414 receives an end of a respective one of the lift arms 406 in the lower section 408, so that the end of the lift arm 406 is arranged between two bracket lobes of the base bracket 414 (e.g., a bracket lobe is arranged on both lateral sides of the lift arm 406). The pivot pin 412 extends through each bracket lobe of the base bracket 414 and the lift arm 406 to form a double shear arrangement (see, e.g.,
[0203] As described herein, the lifting implement 50 may includes one or more of the actuators 116 to facilitate controlled movement of various components of the lifting implement 50. In some embodiments, the lifting implement 50 includes a lift actuator 420 and one or more prop actuators 422. In general, the lift actuator 420 is configured to selectively raise the scissor assembly 404 and the top platform 402 (and the cradle 52 supported thereon). For example, the scissor assembly 404 (and the top platform 402 and the cradle 52) are movable between a raised position (see, e.g.,
[0204] The lift actuator 420 is coupled between the bottom platform 400 (and the base assembly 48 coupled thereto) and the scissor assembly 404. Specifically, one end (e.g., a base end) of the lift actuator 420 is rigidly coupled to the bottom platform 400 by an actuator bracket 424 so that the base end of the lift actuator 420 is fixed to the bottom platform 400, and an opposite end (e.g., outer or distal end) of the lift actuator 420 is coupled to a pair of the lift arms 406 in the upper section 410 (e.g., a pair of lift arms 406 that are also coupled to the top platform 402). In this way, for example, extension of the lift actuator 420 displaces the scissor assembly 404, and the top platform 402 and the cradle 52, toward the raised position where the top platform 402 and the cradle 52 move in a direction away from the bottom platform 400 and the base assembly 48. In some embodiments, the lift actuator 420 may be configured to extend toward an extended position, which corresponds with the raised position of the cradle 52, the top platform 402, and the scissor assembly 404, via one of the valves 126 selectively supplying hydraulic fluid from the pump 124 to the lift actuator 420. In some embodiments, the lift actuator 420 may be configured to retract, after being extended, toward a retracted position, which corresponds with the lowered position of the cradle 52, the top platform 402, and the scissor assembly 404, via gravity and/or a weight of the cradle 52 and the top platform 402. In some embodiments, the lift actuator 420 may be retracted via one of the valves 126 selectively removing hydraulic fluid from the lift actuator 420 and directing the hydraulic fluid to the tank 122.
[0205] In general, the selective extension/retraction of the lift actuator 420 and corresponding raising/lowering of the scissor assembly 404 results in the cradle 52 being selectively raised and lowered relative to the bottom platform 400, the base assembly 48, and the frame 12. It follows that the component (e.g., the axle of the telehandler 56), which is at least partially received within and supported by the cradle 52, may be selectively raised and lowered during the manufacturing line process by the lift assembly 54. In addition to the cradle 52 being selectively raised and lowered by the lift assembly 54, the cradle 52 is rotatably coupled to the top platform 402 to enable steering operation between two of the vehicles 10 during the manufacturing line process.
[0206] With specific reference to
[0207] In general, the cradle 52 includes a rotation slot or rotation limiting channel that defines a rotational range of the cradle 52 relative to the top platform 402 (and the base assembly 48 and the frame 12). In some embodiments, the cradle base 428 includes a rotation slot or arcuate slot 434 that extends through (e.g., vertically) the cradle base 428. The rotation slot 434 extends laterally across a front end of the cradle base 428. The rotation slot 434 extends past or away from both sides of a centerline 436 defined through cradle 52. In this way, for example, the cradle 52 is allowed to rotate in two directions relative to the top platform 402. Specifically, the cradle 52 is allowed to rotate in a first direction (e.g., clockwise) relative to the top platform 402, and in a second direction (e.g., counterclockwise) relative to the top platform 402. As such, the rotational coupling between the cradle 52 and the top platform 402 enables the vehicle 10 to steer in both directions (e.g., right and left).
[0208] A pin 438 is received within the rotation slot 434 and protrudes outwardly above the rotation slot 434 (e.g., above a top surface of the cradle base 428). In some embodiments, the pin 438 is in the form of a bolt, a shoulder bolt, or an equivalent structure that extends through the rotation slot 434. In general, the interface between the rotation slot 434 and the pin 438 defines a rotational range or rotational limit for the cradle 52 relative to the top platform 402. For example, the lateral ends of the rotation slot 434 act as end stops for the rotational range of the cradle 52, and as the cradle 52 rotates relative to the top platform 402, the rotation slot 434 moves relative to the pin 438 until the pin 438 engages one of the lateral ends of the rotation slot 434. Once the pin 438 engages one of the lateral ends of the rotation slot 434, the cradle 52 is prevented from rotating relative to the top platform 402 in one direction (e.g., clockwise or counterclockwise). By way of example, if the pin 438 engages a first end of the rotation slot 434 (e.g., a right end from the perspective of
[0209] In general, the rotational coupling between the cradle 52 and the top platform 402 enables steering operation for the vehicle 10. As described herein, two of the vehicles 10 may support the telehandler 56 during the manufacturing line process, and the front vehicle may turn relative to the rear vehicle via the drive motors 42 or a steering motor. As the front vehicle turns relative to the rear vehicle, the cradle 52, which supports the telehandler 56, of the front vehicle may rotate relative to the top platform 402 of the front vehicle and allow the two vehicles to turn (e.g., the two vehicles are not restricted to travel in a straight line).
[0210] With reference to
[0211] The first bracket assembly 442 includes a fixed bracket 446 and a movable bracket 448. In general, the fixed bracket 446 and the movable bracket 448 define a slot or channel 450 therebetween that is configured to at least partially receive the telehandler 56 (e.g., the axle of the telehandler 56), as shown in
[0212] The fixed bracket 446 is rigidly coupled to the bracket plate 430 so that the fixed bracket 446 does not move relative to the bracket plate 430. The movable bracket 448 may be selectively moved relative to the fixed bracket 446 (and the bracket plate 430) to adjust a size of the channel 450 defined between the fixed bracket 446 and the movable bracket 448. In some embodiments, the movable bracket 448 is selectively moved by lifting the movable bracket 448 relative to the bracket plate 430 and sliding the movable bracket 448 along an angled feature formed in the bracket plate 430. For example, the bracket plate 430 includes an angled slot 452 that extends through the bracket plate 430 and a plurality of locking slots 454, each of which extends through the bracket plate 430. The angled slot 452 is arranged at an acute angle relative to a first surface 456 of the bracket plate 430 (e.g., an angle greater than zero degrees and less than ninety degrees). In other words, a first end of the angled slot 452 is arranged closer to the first surface 456 than a second end of the angled slot 452, which defines a nonzero or acute angle between the angled slot 452 and the first surface 456. In some embodiments, an angle defined between a center line of the angled slot 452 and the first surface 456 may be between about fifteen degrees and about sixty degrees.
[0213] The plurality of locking slots 454 includes a first set of locking slots 458 and a second set of locking slots 460 that are laterally separated (e.g., separated in a direction generally perpendicular to the centerline 436) from the first set of locking slots 458. The first set of locking slots 458 are arranged and oriented in the same pattern as the second set of locking slots 460, except being laterally separated from the second set of locking slots 460. Each of the slots in the first set of locking slots 458 and the second set of locking slots 460 is laterally offset from an adjacent slot and arranged a different distance from the first surface 456 than an adjacent slot. For example, the locking slots on the left side (e.g., from the perspective of
[0214] The movable bracket 448 includes a clip 462, a pair of locking bars 464, and a pair of handles 466. The clip 462 extends through and is at least partially received within the angled slot 452, and the locking bars 464 are each received within a corresponding one of the locking slots in the first set of locking slots 458 and the second set of locking slots 460. To move the movable bracket 448 and adjust a size of the channel 450, a user may grasp the handles 466 of the movable bracket 448 and lift the movable bracket 448 relative to the bracket plate 430. As the handles 466 are lifted, the locking bars 464 are removed from the locking slots 458, which enables the movable bracket 448 to move relative to the fixed bracket 446. Once the locking bars 464 are removed from the locking slots 458, the movable bracket 448 is allowed to move laterally (e.g., left to right, or right to left from the perspective of
[0215] With reference to
[0216] The support props 470 are each pivotably coupled to a side of the scissor assembly 404 by a pivot pin 472. In some embodiments, a centerline or center axis defined through the pivot pin 472 defines a pivot axis for the support prop 470. In some embodiments, the pivot pin 472 may be coupled to the scissor assembly 404 at a junction between two of the lift arms 406 in the upper section 410 (e.g., a center of the x-shaped crisscross between the two lift arms 406). The support props 470 include a plurality of notches or recesses 474 that are sequentially arranged along an outer edge or side of the support prop 470. In some embodiments, the notches 474 each define a generally rounded indent that extends inwardly into the outer edge of the support prop 470. In some embodiments, the notches 474 may define a different shape, for example, rectangular, triangular, or another polygonal shape.
[0217] In general, at least one of the notches 474 on both of the support props 470 are configured to engage a prop pin 476 that extends outwardly from a side of the scissor assembly 404. For example, one of the prop pins 476 extends outwardly from each side of the scissor assembly 404. The prop pins 476 are arranged generally below the pivot pins 472. For example, the prop pins 476 may be coupled to the scissor assembly 404 at a junction between two of the lift arms 406 in the lower section 408 (e.g., a center of the x-shaped crisscross between the two lift arms 406).
[0218] The support props 470 are both pivotably biased by a spring 478 coupled between the respective support prop 470 and the scissor assembly 404. For example, each of the springs 478 is coupled between an outer side of the support prop 470 and an outer side of the scissor assembly 404. Specifically, the springs 478 are coupled to one of the outer intermediate brackets 419 and the support prop 470. In some embodiments, the springs 478 may be in the form of a gas spring. In some embodiments, the springs 478 may both act in compression so that the springs 478 pivotably bias the support props 470 in a first direction (e.g., so that the notches 474 are rotationally biased toward the prop pins 476).
[0219] The support props 470 are both pivotably coupled to a respective one of the prop actuators 422. The prop actuators 422 are configured to selectively pivot the support props 470 in a second direction opposite to bias of the spring 478. For example, each of the prop actuators 422 are coupled to the support props 470 by a linkage 479 so that extension of the prop actuators 422 results in the linkage 479 pivoting the support props 470 away from the prop pins 476. In some embodiments, the prop actuators 422 are hydraulically operated and are configured to extend via one or more of the valves 126 selectively supplying hydraulic fluid from the pump 124 to the prop actuators 422 (see, e.g.,
[0220] During operation, as the scissor assembly 404, the top platform 402, and the cradle 52 are raised by the lift actuator 420, the springs 478 pivotably bias the support props 470 in the first direction, which ensures that the notches 474 sequentially engage the prop pins 476 (e.g., like a rachet mechanism). In this way, for example, as the scissor assembly 404 is raised, the support props 470 always align and ensure engagement between at least one of the notches 474 with the prop pins 476 (e.g., at an intermediate position as shown in
[0221] To lower the scissor assembly 404, the top platform 402, and the cradle 52 from a position above the lowered position (e.g., any position between the lowered position and the raised position), the support props 470 are pivoted away from the prop pins 476 so that the scissor assembly 404 is allowed to freely retract toward the base assembly 48. For example, the prop actuators 422 are configured to selectively actuate or extend, which applies a pivotal force on the support props 470 via the linkages 479. The pivotal force applied by the prop actuators 422 counteracts (e.g., opposes) and overcomes the pivotal force of the springs 478, and the support props 470 pivot away from the prop pins 476 (e.g., in a direction toward the top platform 402 as shown in
[0222] With reference to
[0223] As described herein, the lift actuator 420 is configured to selectively raise the scissor assembly 404, the top platform 402, and the cradle 52. For example, one or more of the valves 126 may selectively supply pressurized hydraulic fluid from the pump 124 to a port 490 that extends through an outer wall of the base stage 480. The port 490 is in fluid communication with a base chamber 492 defined between the base stage 480 and the middle stage 482. As the pressurized hydraulic fluid enters the base chamber 492, the base chamber 492 expands and the middle stage 482 and the outer stage 484 (and the actuator rod 486) extend relative to the base stage 480.
[0224] A bottom wall 494 of the middle stage 482 includes one or more holes 496 (see, e.g.,
[0225] Once the middle stage 482 is no longer able to extend relative to the base stage 480, the holes 496 formed in the middle stage 482 provide the pressurized hydraulic fluid to the middle chamber 498, which then expands and extends the outer stage 484 and the actuator rod 486 relative to the middle stage 482 and the base stage 480. Similar to the middle stage 482, the actuator rod 486 is allowed to extend relative to the middle stage 482 until a stop flange 504, formed in a base of the actuator rod 486, engages a middle collar 506 coupled to a distal end of the middle stage 482 (e.g., an end furthest away from the base stage 480). The middle collar 506 is arranged radially between an inner wall of the middle stage 482 and an outer wall of the actuator rod 486 (see, e.g.,
[0226] In some embodiments, the one or more valves 126 are configured to connect the port 490 to the tank 122 and allow the actuator rod 486 to telescopically retract into the middle stage 482 and the base stage 480 via gravity and/or the weight of the top platform 402 acting on the actuator rod 486. The use of a multi-stage actuator as the lift actuator 420 facilitates a compact arrangement, for example, when the lift actuator 420 is retracted (see, e.g.,
[0227]
[0228] The cradle 52 includes an axle support bracket 513 coupled to an outer surface of one of the one or more cradle arms 432 (see, e.g.,
[0229] In the illustrated embodiment, the rotation slot 434 defines an arcuate shape, similar to
[0230] Turning to
[0231] To adjust a spacing or gap between the fixed bracket 446 and the movable bracket 448, the movable bracket 448 is moved toward the fixed bracket 446, which moves the L-shaped locking bars 464 into a position where they can be removed through the first set of locking slots 458 and the second set of locking slots 460. The movable bracket 448 is then pulled up to remove the locking bars 464 from the current pair of the first set of locking slots 458 and the second set of locking slots 460 and moved (e.g., diagonally and closer to or further away from the fixed bracket 446) to align the locking bars 464 with another pair of the first set of locking slots 458 and the second set of locking slots 460, which are at a different longitudinal location along the bracket plate 430. The movable bracket 448 is then moved downwardly toward the bracket plate 430 so that the locking bars 464 are inserted into the pair of the first set of locking slots 458 and the second set of locking slots 460. With the locking bars 464 within the pair of the first set of locking slots 458 and the second set of locking slots 460, the movable bracket 448 is then moved in a direction away from the fixed bracket 446, which hooks the locking bars 464 on an edge of the pair of first set of locking slots 458 and the second set of locking slots 460, which aids in preventing the movable bracket 448 from being removed from the first set of locking slots 458 and the second set of locking slots 460 (e.g., without moving it toward the fixed bracket 446). Accordingly, the movable bracket 448 is selectively movable to any corresponding pair of the first set of locking slots 458 and the second set of locking slots 460 to adjust the distance between the fixed bracket 446 and the movable bracket 448.
[0232] Turning to
[0233] Each of the support brackets 514 includes a support bar 520 extending outwardly (e.g., in a direction away from the pin 518) from an end of the slot 516. Each of the support bars 520 is received within a support channel 522 that is formed in a support block 524. The support blocks 524 are coupled to a respective one of the lift arms 406 (e.g., the same one of the lift arms 406 in the upper section 410 that the prop actuator 422 is coupled to), and the support channel 522 slidably receives at least a portion of the support bar 520 therein. During operation, as the prop actuators 422 extend and retract to selectively pivot the support props 470, the support bracket 514, which are coupled to the prop actuators 422 via the pins 518, also extend and retract, and the support bars 520 slide or move within a respective one of the support channels 522. At least a portion of the support bar 520 remains in engagement with the support channel 522 over the entire stroke of the prop actuator 422, and the engagement between the support bar 520 and the support channel 522 provides lateral stability to the prop actuators 422 and the scissor assembly 404 during operation. In other words, with the support channel 522 and the support block 524 being rigidly coupled to one of the lift arms 406, the coupling between the support bracket 514, the prop actuators 422, and the linkage 479 acts to laterally hold or constrain the prop actuators 422, the linkage 479, and the scissor assembly 404 (e.g., inhibits or constrains lateral movement) during operation.
[0234] With specific reference to
[0235] Turning to
[0236] In an exemplary embodiment, each of the prop position arms 528 is coupled to an encoder or a rotary position sensor 530 that measures a rotational position of the prop position arms 528. The rotary position sensor 530 is included in the sensors 112 and is in communication with the controller 102. The controller 102 is configured to determine a rotational position of the support props 470 based on the rotational position of the prop position arms 528 measured by the rotary position sensor 530. For example, actuation (e.g., extension) of the prop actuators 422 in a first translational direction moves the pins 518 in the along the first translation direction and pivots both the support props 470 and the prop position arms 528 to a particular rotational position (e.g., the support props 470 rotate in a first rotational direction). The distance that the pins 518 travel along the first translation direction is directly correlated to the rotational position of the prop position arms 528 and the support props 470. Similarly, actuation (e.g., retraction) of the prop actuators 422 in a second translational direction (e.g., opposite to the first translational direction) moves the pins 518 in the along the second translation direction and pivots both the support props 470 and the prop position arms 528 to a particular rotational position (e.g., the support props 470 rotate in a second rotational direction opposite to the first rotational direction). The distance that the pins 518 travel along the second translation direction is directly correlated to the rotational position of the prop position arms 528 and the support props 470. As such, the rotary position sensor 530 is configured to output a signal to the controller 102 that indicates a position of the support props 470 and provides an indication of whether the notches 474 are in engagement with the prop pins 476, or the notches 474 are pivoted away from the prop pins 476.
Cart
[0237] Referring generally to the figures, a cart interface or coupling assembly may be coupled to a frame of vehicle to detachably couple the vehicle to a cart. More specifically, the cart interface may be coupled to a top surface of the vehicle. The cart interface includes an actuator coupled to a mounting interface, which is configured to be mounted to the top surface of the vehicle. The actuator engages a cam plate coupled to one or more pin assemblies configured to engage a bottom portion of the cart. In some embodiments, the one or more pin assemblies engage the bottom portion of the cart to couple the vehicle to the cart. The pin assemblies may be overextended to lift up on the cart, increasing the weight supported by the vehicle and increasing the traction of a drivetrain of the vehicle.
[0238] Referring to
[0239] The bottom portion 614 of the cart 600 includes one or more channels or troughs (e.g., a first channel, a second channel, etc.), shown as channels 626, and one or more support or linking plates, shown as frame plates 627. The channels 626 are fixedly coupled to a bottom side or underside of the frame members 620. Each of the channels 626 includes a pair of channel walls, rails, or guards (e.g., cattle chutes), shown as guides 628, and a flat member, top member, or ceiling, shown as plate 630. A first pair of the channels 626 extend longitudinally across the cart 600 (e.g., from the front portion 616 to the rear portion 618), defining and centered about a longitudinal axis 632. A second pair of the channels 626 extend laterally across the cart 600 (e.g., between the pair of side portions 619), defining and centered about a lateral axis 634.
[0240] As shown in
[0241] In some embodiments, the first portion 633 and the second portion 635 of each channel 626 are fixedly coupled (e.g., welded, etc.) with one another and the plate 630. In some embodiments, the guides 628 and the plate 630 are assembled to the cart 600 using a series of fasteners. In some embodiments, there are more or fewer channels 626 than shown in the
[0242] The channels 626 along the longitudinal axis 632 and the channels 626 along the lateral axis 634 intersect once another at a substantially vertical axis 636. In some embodiments, the cart 600 is rotatable (e.g., relative to the vehicle 10) about the substantially vertical axis 636. In some embodiments, the frame members 620 arranged on the front portion 616, the rear portion 618, and the pair of side portions 619 define an outer or external perimeter of the cart 600. In such embodiments, the substantially vertical axis 636 may be positioned within and extending through the external perimeter (e.g., the substantially vertical axis 636 is laterally and/or longitudinally centered on the cart 600).
[0243] Referring to
[0244] Referring to
[0245]
[0246] Referring to
[0247] The actuator 640 and the cradle may facilitate adding multiple products onto the cart 600 simultaneously. This may be advantageous in a manufacturing environment that is only capable of placing products onto one side of the cart 600. By way of example, a first equipment 644 may be placed into the cradle 642 in the position shown in solid lines in
[0248] Referring generally to
[0249] Referring now to
[0250] The frame members 620 include a sixth frame member 656, a seventh frame member 658, and an eighth frame member 660. The sixth frame member 656 extends substantially parallel to and offset from the fourth frame member 652 in a fourth direction opposite the third direction. The fifth frame member 654 intersects at least a portion of the first frame member 646, second frame member 648, and the third frame member 650. The sixth frame member 656 is substantially the same length as the fifth frame member 654 and is longer than the fourth frame member 652. The sixth frame member 656 intersects at least a portion of the first frame member 646, the second frame member 648, and the third frame member 650. The seventh frame member 658 extends substantially parallel to the fifth frame member 654 and is offset from the fifth frame member 654 in the third direction. The eighth frame member 660 extends substantially parallel to the sixth frame member 656, and is offset from the sixth frame member 656 in the fourth direction.
[0251] The frame members 620 includes a ninth frame member 662, a tenth frame member 664, an eleventh frame member 666, and a twelfth frame member 668. The ninth frame member 662 extends between a first end of the fifth frame member 654 and a first end of the seventh frame member 658, and the tenth frame member 664 extends between a second end of the fifth frame member 654 and a second end of the fifth frame member 654, the first ends opposite the second ends. The eleventh frame member 666 extends between a first end of the sixth frame member 656 and a first end of the eighth frame member 660, and the twelfth frame member 668 extends between a second end of the sixth frame member 656 and a second end of the eight frame member 660, the second end opposite the first end.
[0252] The support members 622 include a series of first support members 670 and a series of second support members 672. The first support members 670 are each angled with respect to the corresponding frame members 620, and the second support members 672 are each perpendicular with respect to the corresponding frame members 620. Two of the first support members 670 extend between the first frame member 646 and the second frame member 648, and two of the first support members 670 extend between the first frame member 646 and the third frame member 650. Two of the second support members 672 extend between the fifth frame member 654 and the seventh frame member 658, and two of the second support members 672 extend between the sixth frame member 656 and the eighth frame member 660.
[0253] The shape, size, and arrangement of the frame members 620 and the support members 622 cause the frame 602 to form an I shape as viewed from above. Specifically, the lateral width of the frame 602 is greater at the front end and the rear end of the frame 602 than in the longitudinal center of the frame. This arrangement forms a first recess between the fifth frame member 654, the second frame member 648, and the sixth frame member 656, and a second recess between the fifth frame member 654, the third frame member 650 and the sixth frame member 656. These recesses extend laterally inward from the left and right sides of the frame 602. The recesses may provide clearance for lifting forks used to place the boom assemblies 68 or other equipment 644 onto the cart 600, while still ensuring that the front and rear ends of the boom assemblies 68 are supported by the cart 600.
[0254] The cart 600 includes a series of side panels 674, as shown in
[0255] The side panels 674 face outward from the frame 602. Each of the side panels 674 includes a visual indicator (e.g., QR code, etc.) that can be viewed by a vehicle 10 nearby the cart 600. The visual indicators each provide information visually. A sensor 112 of the vehicle 10, such as a camera, may detect and read the visual indicator to gather information about the cart 600. By way of example, the visual indicators may contain information used to identify the cart 600 or a component carried by the cart 600 (e.g., an identification number). By way of another example, the visual indicators may be placed at predetermined locations on the cart 600, such that by locating the visual indicators, the controller 102 may determine a position of the cart 600 relative to the vehicle 10.
[0256] Referring to
[0257] A of slots 680 are arranged along the seventh frame member 658 and the eighth frame member 660 of the cart 600, and are configured to receive the cradle 642. The slots 680 extend from locations vertically aligned with the ninth frame member 662 and the eleventh frame member 666 to locations closer to the tenth frame member 664 and the twelfth frame member 668 than the ninth frame member 662 and the eleventh frame member 666. The cradle 642 is configured to extend between and slide along the slots 680.
[0258] Referring now to
[0259] The cart 600 further includes a secondary cradle 692 fixedly coupled to the frame 602. The secondary cradle 692 includes a series of lateral members 693, a longitudinal member 694, and a series of vertical members 695. The longitudinal member 694 extends between the tenth frame member 664 and the twelfth frame member 668, and is substantially parallel and offset from the third frame member 650 along the second direction. The lateral members 693 each extend from the longitudinal member 694 towards the second frame member 648. The vertical members 695 each extend from the lateral members 693 and the longitudinal member 694. The actuator 640 extends from the longitudinal member 694 of the secondary cradle 692. The cradle 642 is vertically offset from the secondary cradle 692, facilitating movement of the cradle 642 relative to the secondary cradle 692.
[0260] As shown in
[0261] Referring now to
[0262] Referring now to
Cart Interface
[0263] Referring generally to
[0264]
[0265] The actuator 704 is coupled to the mounting interface 702 by a first mounting bracket 712. In some embodiments, the actuator 704 is rotatably or pivotably coupled to the first mounting bracket 712 to permit movement of the actuator 704 relative to the mounting interface 702 (e.g., as the cam plate 706 rotates). In some embodiments, the actuator 704 includes an electric motor, which may be configured to drive, power, or move the actuator 704 to actuate. In some embodiments, the actuator 704 is an electric linear actuator. A distal end portion of the actuator 704 is further coupled to the cam plate 706.
[0266] The cam plate 706 defines one or more apertures or aperture pairs, shown as a first aperture 714, a second aperture 716, a third aperture 718, and a fourth aperture 720. The first aperture 714 is positioned towards the bottom (e.g., in a direction towards the mounting interface 702) of the cam plate 706 and receives a fastener (e.g., bolt, rivet, screw, or other fastening device) to pivotally couple an end portion of the actuator 704 to the cam plate 706. The second aperture 716 is positioned towards the front (e.g., in a direction away from the actuator 704) of the cam plate 706 and receives a fastener to pivotally couple the cam plate 706 to the mounting interface 702 by a second mounting bracket 722. The third aperture 718 is positioned towards the top (e.g., in a direction away from the mounting interface 702) of the cam plate 706 and receives a fastener to pivotally couple the cam plate 706 to the first pin assembly 708 by or through a first linkage 724. The fourth aperture 720 is positioned towards the rear (e.g., in a direction towards the actuator 704) of the cam plate 706 and receives a fastener to pivotally couple the cam plate 706 to a second pin assembly 710 by or through a second linkage 726. In some embodiments, the position and/or quantity of the first aperture 714, the second aperture 716, the third aperture 718, or the fourth aperture 720 may vary based on one or more of a shape or size of the cam plate 706, the position or orientation of the actuator 704, the position or orientation of the first mounting bracket 712 or the second mounting bracket 722, or the position, orientation, or quantity of pin assemblies (e.g., the first pin assembly 708, the second pin assembly 710).
[0267]
[0268] The spring 730 has an uncompressed length. If the driving pin 62 is not in engagement with plate 630, the spring 730 is permitted to expand to the uncompressed length without resistance. Accordingly, in such a situation, the driving pin 62 has a predetermined vertical offset distance from the pin 728. Varying the vertical position of the pin 728 raises or lowers the driving pin 62. If the driving pin 62 engages the plate 630, the plate 630 limits upward movement of the driving pin 62 and begins to compress the spring 730. Varying the vertical position of the pin 728 increases or decreases the biasing force of the spring 730 and thus the biasing force applied to the plate 630 through the driving pin 62.
[0269] In some situations, such as when the vehicle 10 drives relative to the cart 600, the drive pin 62 moves along a channel 626 (e.g., along one of the longitudinal axis 632 or the lateral axis 634). As the drive pin 62 moves along the channel 626, the driving pin 62 may encounter one of the positioning members 638. The driving pin 62 may engage the positioning member 638, and the positioning member 638 may force the driving pin 62 downward and compress the spring 730. Once the driving pin 62 reaches the space between the positioning members 638, the spring 730 may force the driving pin 62 upward and into the space.
[0270] The second pin assembly 710 includes the second linkage 726, a turning pin 64, and a housing 736 that receives a portion of the turning pin 64. In some embodiments, the turning pin 64 is configured to move along a central axis defined by the housing 736 and engage the plate 630 of the channel 626. Because the second linkage 726 is directly coupled to the turning pin 64, the turning pin 64 does not have the freedom of movement relative to the second linkage 726 that the driving pin 62 is provided by the spring 730. Accordingly, each position of the second linkage 726 has a corresponding position of the turning pin 64.
[0271] The first pin assembly 708 and the second pin assembly 710 are coupled to one another by a plate 738. The plate 738 includes a first aperture 740 that receives the housing 732 of the first pin assembly 708 and a second aperture 742 that receives the housing 736 of the second pin assembly 710. The housing 732 and the housing 736 are both fixedly coupled to the plate 738. Accordingly, the plate 738 prevents movement of the housing 732 relative to the housing 736.
[0272] Referring to
[0273] In operation, the actuator 704 may be used to reposition the driving pin 62 and the turning pin 64 and control engagement between the vehicle 10 and the cart 600. Each position of the actuator 704 may have a corresponding position of the cam plate 706. Accordingly, by controlling the extension of the actuator 704, the positions of the driving pin 62 and the turning pin 64 may be controlled. In some embodiments, the actuator 704 includes a sensor 112 that provides feedback regarding the position or extended length of the actuator 704. The controller 102 may utilize this feedback to perform closed-loop control over the position of the cam plate 706.
[0274] In some embodiments, the actuator 704 extends fully, moving the cam plate 706 to an extreme clockwise position, referred to as a fully retracted position. In the fully retracted position, the driving pin 62 and the turning pin 64 are retracted low enough to where neither the driving pin 62 nor the turning pin 64 can enter into the channel 626. Accordingly, the cart interface 700 does not interface (e.g., is incapable of interfacing) with the cart 600. The fully retracted position may be useful when it is desirable for the vehicle 10 navigate beneath a cart 600 without engaging the cart 600. The actuator 704 may return the cam plate 706 to the fully retracted position at any time to release the vehicle 10 from engagement with a cart 600.
[0275] In some embodiments, the actuator 704 retracts or actuates the cam plate 706 to pivot counterclockwise about the second aperture 716 to an extended or single engagement position. In the single engagement position, the cam plate 706 is positioned such that the second driving pin 62 of the first pin assembly 708 extends high enough to enter into the channel 626, but the turning pin 64 of the second assembly 710 is low enough to prevent the turning pin 64 from engaging with the channel 626. The single engagement position may be used when initially coupling the vehicle 10 to a cart 600. By way of example, a vehicle 10 may begin by approaching the cart 600. The vehicle 10 may align the driving pin 62 with a channel 626 of the cart 600. The increased width of the second portion 635 may facilitate this alignment. As the vehicle 10 continues to move toward the cart 600, the tapered shape of the second portion 635 may automatically align the first portion 633 with the driving pin 62.
[0276] The vehicle 10 may continue to move along the length of the channel 626 until the driving pin 62 reaches a positioning member 638. The spring 730 may compress to permit the driving pin 62 to move along the positioning member 638 until the driving pin 62 reaches the space between the driving pints 62. The spring 730 may then force the driving pin 62 into the space between the positioning members 638. Engagement between the tall, flat walls of the positioning members 638 and the driving pin 62 prevents the driving pin 62 from leaving the space. Accordingly, the cart 600 is then positionally tied (i.e., forced to move along the same path) as the vehicle 10. In this configuration, the substantially vertical axis 636 and the central axis 46 of the vehicle 10 may be aligned. Accordingly, the vehicle 10 can freely rotate about its central axis 46 to adjust the orientation of the vehicle 10 relative to the cart 600. By way of example, the vehicle 10 may drive in a first direction (e.g., north), then turn and drive in a second direction (e.g., west) without varying an orientation of the cart 600.
[0277] In some embodiments, the actuator 704 extends to actuate the cam plate 706 to pivot about the second aperture 716 to a neutral or dual engagement position. In the dual engagement position, the cam plate 706 is positioned such that the driving pin 62 of the first pin assembly 708 and the turning pin 64 of the second assembly 710 are raised to a height where both the driving pin 62 and the turning pin 64 would extend into the channel 626. If the turning pin 64 is aligned with one of the channels 626, the turning pin 64 will enter into the channel 626 and prevent rotation of the cart 600 relative to the vehicle 10. Accordingly, the dual engagement position may be useful to adjust the orientation of the cart 600. Due to the arrangement of the channels 626, the vehicle 10 may have twice as many orientations where the turning pin 64 may enter a channel 626 as there are channels 626 (e.g., two for each channel 626).
[0278] If the actuator 704 attempts to bring the turning pin 64 to the dual engagement position without the turning pin 64 being aligned with one of the channels 626, the turning pin 64 may instead engage a guide 628 and/or a frame plate 627. Because the frame plates 627 are flush with the guides 628, the vehicle 10 may simply rotate to slide the turning pin 64 along the frame plates 627 and the guides 628 until alignment is reached. At that point, the actuator 704 may force the turning pin 64 into the channel 626.
[0279] In the single engagement position and the dual engagement position, the turning pin 64 may be separated from the plate 630 or may lightly touch the plate 630. Accordingly, minimal vertical force is transferred between the cart 600 and the vehicle 10. Because of this, the vehicle 10 generally supports only the weight of the vehicle 10. While the cart 600 and/or any products supported by the cart 600 may have a significant weight, the majority of that weight may be directed to the ground through the casters 610. Accordingly, the structure of the vehicle 10 can be made lighter and more cost effective, as the vehicle 10 does not have to support the additional weight of the cart load.
[0280] In some embodiments, the actuator 704 is configured to actuate the cam plate 706 so that the driving pin 62 and the turning pin 64 are in a traction configuration or traction position. By way of example, while the vehicle 10 is driving the cart 600 (e.g., the driving pin 62 is extended upward and arranged between the positioning members 638 and the turning pin 64 is extended upward and received within at least one of the channels 626 in the dual engagement position), the controller 102 may detect, via the sensors 112 (e.g., a wheel encoder, a speed sensor, etc.), that one or more of the tractive elements 44 have lost or reduced traction (e.g., detect wheel slip, or wheel traction below a predefined threshold). In response to detecting that one or more of the tractive elements have lost or reduced traction, the controller 102 may instruct the actuator 704 to rotate the cam plate 706 (e.g., counterclockwise from the perspective of
Alternative Cart Interface
[0281] Referring generally to
[0282] Referring to
[0283] The first cover 3022 and the second cover 3024 each define a hole, opening, or passage, shown as pin aperture 3130. The aperture 3130 of the second cover 3024 receives the driving pin 62. The aperture 3130 of the second cover 3024 receives the turning pin 64. The apertures 3130 facilitate extension of the driving pin 62 and the turning pin 64.
[0284] As shown in
[0285] Referring to
[0286] The frame assembly 3001 further includes a pair of receivers, receiving cups, annular members, or support arms, shown as guiding sleeves 3017. The guiding sleeves 3017 are each fixedly coupled to a top end portion of the base frame 3014. A first one of the guiding sleeves 3017 extends longitudinally forward from the base frame 3014 and receives and supports the pin 62. The other of the guiding sleeves 3017 extends longitudinally rearward from the base frame 3014 and receives and supports the turning pin 64.
[0287] The base frame 3014 includes a base plate or mounting plate, shown as mounting interface 3016, that is fixedly coupled to a lower end of the base frame 3014. The mounting interface 3016 is directly and fixedly coupled to the frame 12 to couple the cart interface 3000 to the vehicle 10. The mounting interface 3016 and the mounting interface 702 may have similar mounting features to make the cart interface 3000 interchangeable with the cart interface 700. The mounting interface 3016 generally extends horizontally (e.g., within a horizontal plane). The base frame 3014 is fixedly coupled to the mounting interface 3016 and extends upward from a top surface of the mounting interface 3016.
[0288] Referring to
[0289] Referring to
[0290] The first actuator assembly 3018 and the second actuator assembly 3019 each include a linear actuator (e.g., an electric linear actuator), shown as actuator 3030, and a protraction, pin, or sliding assembly, shown as pin assembly 3100. The actuator 3030 of the first actuator assembly 3018 may control raising and lowering of the pin assembly 3100 of the first actuator assembly 3018. Similarly, the actuator 3030 of the first actuator assembly 3018 may control raising and lowering of the pin assembly 3100 of the second actuator assembly 3019. The pin assembly 3100 of the first actuator assembly 3018 may serve as or include the driving pin 62. The pin assembly 3100 of the second actuator assembly 3019 may serve as or include the turning pin 64.
[0291] Referring to
[0292] In operation, the motor 3031 rotates to extend and retract the first actuator 3030 along an axis AX that is centered along the rod 3033 and the body 3034. Rotational mechanical energy from the motor 3031 may be transferred to the actuator rod 3009 by the transmission 3032. The motor 3031 my rotate in a first direction to extend the actuator 3030 outwards and raise the pin assembly 3100. The motor 3031 may rotate in an opposing second direction to retract the actuator 3030 inward and lower the pin assembly 3100. The actuator 3030 may be continuously repositionable throughout a range of motion between a fully retracted position and a fully extended position. In some embodiments (e.g., where the actuator rod 3009 includes a screw that is rotated to extend and retract the actuator rod 3009), the motor 3031 is capable of holding the actuator 3030 at any desired position within the range of motion.
[0293] Operation of the motor 3031 may be controlled by the controller 102. By way of example, the controller 102 may supply electrical energy from the batteries 110 to the motor 3031 to control operation of the motor 3031. The controller 102 may control the speed and direction of the actuator 3030 and whether the actuator 3030 is holding its current position. In some embodiments, a sensor 112 (e.g., an encoder, a linear potentiometer, etc.) provides sensor data indicating a current extended length of the actuator 3030. This sensor data may be used by the controller 102 to provide closed-loop control over the length of the actuator 3030.
[0294] Referring to
[0295] Referring to
[0296] Referring again to
[0297] The pin body 3040 receives a bushing member or friction-reducing member, shown as bearing 3042, fixedly coupled to the first pin body 3040. The bearing 3042 may be annular and may define a circumference of the internal volume 3102. The bearing 3042 may form the internal volume 3102 as a vertical passage or aperture that is centered within the pin passage 3004 and the pin body 3040.
[0298] An adapter, sliding member, sliding element, or cup, shown as spring cup 3043, is received within the internal volume 3102. Specifically, the spring cup 3043 is received within the bearing 3042. The bearing 3042 may facilitate relative vertical movement of the first pin body 3040 and the spring cup 3043. Accordingly, the spring cup 3043 may move along a length of the internal volume 3102.
[0299] The spring cup 3043 is coupled to the first actuator interface 3035 by a fastener, shown as shoulder bolt 3008. The shoulder bolt 3008 extends laterally through the spring cup 3043 and through an aperture defined by the first actuator interface 3035 of the actuator rod 3009. The shoulder bolt 3008 may be in threaded engagement with a portion of the spring cup 3043 to fixedly couple the shoulder bolt 3008 to the spring cup 3043. The shoulder bolt 3008 may pivotably couple the spring cup 3043 to the end of the actuator rod 3009, such that the spring cup 3043 moves with the actuator rod 3009 as the actuator 3030 extends and retracts.
[0300] A biasing element, shown as compression spring 3044, is received within the internal volume 3102 between the threaded pin cap 3012 and the spring cup 3043. The spring cup 3043 defines a first recess that receives a first, lower end of the compression spring 3044. The threaded pin cap 3012 defines a second recess that receives a second, upper end of the compression spring 3044. The compression spring 3044 couples the pin assembly 3100 to the spring cup 3043 and the actuator 3030 while permitting movement of the pin assembly 3100 relative to the first pin assembly 3002. The compression spring 3044 applies an upward biasing force onto the threaded pin cap 3012 that forces the threaded pin cap 3012 away from the spring cup 3043. Accordingly, the compression spring 3044 biases the first pin assembly 3002 upward.
[0301] The first pin assembly 3002 further includes a fastener or snap ring, shown as internal circlip 3046, that is received within an annular groove along an inner surface of the first pin body 3040. The annular groove limits vertical movement of the internal circlip 3046. A washer or spacer, shown as spacer 3047, is positioned within the internal volume 3102 between the internal circlip 3046 and the spring cup 3043. Accordingly, engagement between the bottom portion of the spring cup 3043 and the top portion of the spacer 3047 and engagement between and the top portion of the internal circlip 3046 and the bottom portion of the spacer 3047 limit downward movement of the spring cup 3043 relative to the first pin body 3040. Accordingly, the internal circlip 3046 and the spacer 3047 limit extension of the compression spring 3044.
[0302] Referring to
[0303] Throughout operation, a downward force may be applied to each pin assembly 3100 (e.g., on the top surface 3041) to cause compression of the compression spring 3044, permitting the first pin body 3040 to move downward relative to the spring cup 3043. The compression spring 3044 resists this movement so that when downward force is removed, the biasing force of the compression spring 3044 causes the pin assembly 3100 to return to its original position where the bottom portion of the spring cup 3043 is engaged with the internal circlip 3046 and the spacer 3047. Accordingly, the actuators 3030 may raise and lower the driving pin 62 and the turning pin 64, but the driving pin 62 and the turning pin 64 may be forced downward or biased upward without requiring movement of the actuator 3030.
[0304] Referring to
[0305] Throughout this process, the actuators 3030 move the pin assemblies 3100 to three different positions: a lowered position (e.g., shown in
[0306]
[0307]
[0308] In the configuration of
[0309] In the configuration of
[0310] In the configuration of
[0311] To disengage the cart interface 3000 from the cart 600, the actuators 3030 may return the driving pin 62 and the turning pin 64 to the lowered positions. Lowering the turning pin 64 without lowering the driving pin 62 may permit rotation of the vehicle 10 relative to the cart 600 about the substantially vertical axis 636 while still limiting translation of the cart 600 relative to the vehicle 10. Lowering both the driving pin 62 and the turning pin 64 may completely disengage the cart interface 3000 from the cart 600.
Sensing System and Sensor Configuration
[0312] Referring generally to the figures, an autonomous vehicle system includes a vehicle having a control system, a base assembly, and one or more tractive elements. A sensor system is coupled to the vehicle. The sensor system is configured to detect one or more objects located in an area near the vehicle and communicate the detection of the one or more objects to the control system. Based on receiving the communication regarding the detection of the one or more objects, the control system is configured to generate one or more controls for one or more of the base assembly or the one or more tractive elements. The control system is further configured to send the one or more controls to the one or more of the base assembly or the one or more tractive elements.
[0313] The sensors 112 of the vehicle 10 may facilitate autonomous navigation of the vehicle 10 throughout the manufacturing environment without the need for guide wires or other physical guiding devices, dedicated travel lanes, floor markings, etc. The sensors 112 may operate at a distance from any potentially sensed object, and no contact is required between the sensors 112 and an object to be sensed.
[0314] Turning now to
[0315] Data captured by or acquired using the short-range sensors 800 and the long-range sensors 802 may include, for example, data that may be used (e.g., by the controller 102) to determine a proximity of the vehicle 10 or any component of the vehicle 10 to an object (e.g., an obstacle, a wall, a person, etc.) while the vehicle 10 is stationary or in motion. By way of another example, data captured by the short-range sensors 800 and the long-range sensors 802 may include data that may be used to detect objects near or around the vehicle 10 or any component of the vehicle 10. In some embodiments, the data captured by the short-range sensors 800 and the long-range sensors 802 may be used to determine a state in which the vehicle 10 and/or any component of the vehicle 10 are operating. By way of example, the short-range sensors 800 and the long-range sensors 802 may be configured to acquire data to facilitate monitoring operation of the actuators 116, and such data may be used to determine whether the lift assembly 54 is in an extended position, a retracted position, any other position therebetween, and/or whether the lift assembly 54 is in the process of extending or retracting. By way of another example, the short-range sensors 800 and the long-range sensors 802 may be configured to acquire data to facilitate monitoring an orientation of the lift assembly 54 including a decline or depression angle, a rotation angle, and/or incline angle of the lift assembly 54.
[0316] In the embodiment of
[0317] The short-range sensors 800 may be considered secondary sensors to the long-range sensors 802, discussed further herein. The four short-range sensors 800 are each positioned on front, rear, left, and right sides of the vehicle 10. The short-range sensors 800 are oriented to perform sensing operations for areas in front of the vehicle 10, behind the vehicle 10, and/or to the sides of the vehicle 10. In other embodiments, fewer or more than four of the short-range sensors 800 may be included and/or the short-range sensors 800 may positioned or oriented differently. For example, the vehicle 10 may have eight of the short-range sensors 800, with two of the short-range sensors 800 positioned on each of the front, rear, left, and right sides of the vehicle.
[0318] In some embodiments, the short-range sensors 800 are light curtain sensors. The light curtain sensors may use an array of photoelectric beams to detect intrusion into a space (e.g., a sensing field, a plane, a curtain, etc.). An intrusion may be detected when an object interrupts one or more of the photoelectric beams within the sensing field. When an intrusion is detected, the light curtain sensors may send a signal (e.g., to the control system 100, etc.) to limit (e.g., cease) operations of the vehicle 10.
[0319] In some embodiments, the short-range sensors 800 are ultrasonic sensors. The ultrasonic sensors may use a transducer to send and receive ultrasonic pulses (e.g., sound waves, etc.) that relay information back to the ultrasonic sensor regarding the proximity of an object. The ultrasonic sensors may measure distances of objects sensed in various directions around the vehicle 10. In order to determine a direction (e.g., an angular position, etc.) in which the object was sensed at a distance away from the vehicle 10, multiple ultrasonic sensors may be used (e.g., overlapping, etc.). The multiple ultrasonic sensors may communicate to triangulate the location of the object and thereby determine the distance and position of the object relative to the vehicle 10. For example, the multiple ultrasonic sensors may each measure a distance of an object from the vehicle 10 and transmit the distance to the control system 100 or another computing device, which may mathematically calculate a location of the object, including a direction of the object.
[0320] The long-range sensors 802 may have a longer range or larger field of view than the short-range sensors 800 and may be able to detect objects at further distances from the vehicle 10 than the short-range sensors 800. As shown in
[0321] Each corner of the frame 12 defines an angled or chamfered surface 804 extending between (a) the front surface 32 or the rear surface 34 and (b) one of the side surfaces 36. The chamfered surfaces 804 extend at approximately a 45-degree angle relative to the adjacent surfaces. Each of the long-range sensors 802 is coupled to one of the chamfered surfaces 804 by a bracket 806, and the long-range sensor 802 extends below the corresponding bracket 806. By including the chamfered surfaces 804 that are angled relative to the front surface 32, the rear surface 34, and the side surfaces 36, the frame 12 is prevented from obstructing the fields of view of the long-range sensors 802. Accordingly, the chamfered surfaces 804 facilitate full sensor coverage around the vehicle 10 with only two long-range sensors 802.
[0322] In some embodiments, the long-range sensors 802 are LIDAR sensors. The LIDAR sensors may use light in the form of a rapidly firing laser (e.g., pulsed, strobed, etc.) to measure distances of objects from the vehicle 10. The light is sent from a source (e.g., a transmitter, etc.) and is reflected by objects. The reflected light is detected by a receiver, and the amount of time taken for the light to travel back to the receiver (e.g., time of flight (TOF), time delay, etc.) is recorded. The reflected light and the recorded amount of time are used to develop a three-dimensional (3D) map of the area surrounding the LIDAR sensor, including any objects present.
[0323] The long-range sensors 802 may generate a point map (e.g., a three-dimensional map of the surroundings) to facilitate navigation of the vehicle 10. In the sensor configuration of
[0324] The long-range sensors 802 may also facilitate locating a position of the vehicle 10 within an environment. For example, the point map generated by the long-range sensors 802 may map the environment surrounding the vehicle 10 and allow the long-range sensors to determine the position of the vehicle 10 within the environment. In another example, the control system 100 may receive a pre-generated map from a remote device 134, and may compare data from the pre-generated map to data gathered by the long-range sensors 802. The comparison of data between the pre-generated map and the long-range sensors may allow the control system 100 to determine the position of the vehicle 10 within the environment.
[0325] The sensors 112, including the short-range sensors 800 and the long-range sensors 802, may function to limit operations of the vehicle 10. For example, if the vehicle 10 is stationary and the short-range sensor 800 or the long-range sensor 802 positioned on the front of the vehicle 10 detects an object within the corresponding sensing field, the short-range sensor 800 or the long-range sensor 802 may send a signal to the control system 100 to prevent the vehicle 10 from moving in a forward direction. The vehicle 10 may remain stationary until the object is removed from the path of the vehicle 10. By way of another example, if the vehicle 10 is driving forward and the short-range sensor 800 or the long-range sensor 802 detects an object within the corresponding sensing field, the short-range sensor 800 or the long-range sensor 802 may send a signal to the control system 100 to cease driving operations of the vehicle 10 such that the vehicle 10 comes to a stop. The vehicle 10 may remain at a stop until the object is removed from the path of the vehicle 10, at which time the vehicle 10 may resume motion and proceed forward again.
[0326] In general, the short-range sensors 800 are responsible for controlling movement of the vehicle 10 in response to the detection of an object. The long-range sensors 802 are generally responsible for mapping an environment surrounding the vehicle 10 and determining a position of the vehicle 10 in the environment. When the short-range sensors 800 detect an object, the short-range sensors may function to limit operations of the vehicle 10 in various manners. For example, the short-range sensors 800 may stop all movement of the vehicle 10 when an object is detected, or may stop movement of the vehicle 10 only in the direction in which the short-range sensor 800 detected the object. By way of another example, the short-range sensors 800 may function to reduce the speed of the vehicle 10 in response to detecting an object. The short-range sensors 800 may also function to limit or control any other operation of the vehicle 10 such as steering, lifting, etc.
[0327] As shown in
[0328] The vehicle 10 may include a lighting system or other visual or auditory alert system, shown in
[0329] Turning now to
[0330] The skate 900 may be pulled or towed behind the vehicle 10. As such, the skate 900 may only move in a forward direction. In this respect, an object located behind or to the sides of the skate 900 may not trigger one or more of the sensors 112 to halt operation of the vehicle 10. If an object is present in a location between the vehicle 10 and the skate 900, the short-range sensors 800 and the long-range sensors 802 of the vehicle 10 may detect the object and may halt operation of the vehicle 10, thereby ceasing movement of the skate 900.
[0331] The vehicle 10 and the skate 900 may together support a load 810. The load 810 may be a component, a machine, an assembly, a product, a tool, etc. As shown in
[0332] Turning now to
[0333] Positioned on a front side of the vehicle 10 may be one or more headlights 856 configured to illuminate the area in front of the vehicle 10. The headlights 856 may also indicate the direction of travel for the vehicle 10. The vehicle 10 also includes a user interface 114 with screen (e.g., a touchscreen, etc.) which may provide information accessible by an operator and may receive input from the operator. Although the user interface 114 is shown on the front side of the vehicle 10, the user interface 114 may be positioned anywhere on the vehicle 10. Additionally, the vehicle 10 may include one or more batteries 110 which may be positioned on a side of the vehicle 10, or anywhere else on the vehicle 10. The batteries 110 may be rechargeable or replaceable.
[0334] As shown in
[0335]
[0336] A method of operating the vehicle 10 and the system described herein may include several processes. For example, the method may include coupling a sensor system to an autonomous vehicle comprising a base assembly and one or more tractive elements and positioning the autonomous vehicle in an environment. The method may also include driving the vehicle along a path. Additionally, the method may include detecting, by the sensor system, one or more objects located in an area near the autonomous vehicle, and communicating the detection of the one or more objects to a control system. The method may further include generating one or more controls for one or more of the base assembly or the one or more tractive elements and sending the one or more controls to the one or more of the base assembly or the one or more tractive elements. Generating the one or more controls may include generating a stop control. Detecting the one or more objects may include detecting an obstacle or a person.
[0337] The method may include additional processes such as coupling a lift assembly to the autonomous vehicle, generating one or more controls for the lift assembly, and sending the one or more controls to the lift assembly. Coupling the sensor system to the autonomous vehicle may include coupling short-range sensors and long-range sensors to the autonomous vehicle. The method may also include generating, by the long-range sensors, a point map mapping an environment surrounding the autonomous vehicle. The method may additionally include receiving, to the control system, a pre-generated map of the environment and comparing, by the control system the pre-generated map to the point map.
Adjustable Sensor System
[0338] Referring generally to the figures, an autonomous vehicle includes one or more sensors for sensing the environment around the vehicle. The vehicle may support a product through various stages of assembly along an assembly line. In some embodiments, the product may obscure one or more sensors of the vehicle. To compensate for the field of view of the one or more sensors, the vehicle may adjust a position of the one or more sensors on the vehicle. In some embodiments, the vehicle preemptively moves/repositions the one or more sensors prior to the obstruction. For example, the vehicle may track the current stage of assembly for the product and include predetermined information regarding the position of the product relative to the vehicle at each stage. Prior to the product being positioned to obscure a sensor, the vehicle can adjust the sensor position to ensure the sensor field of view is not compromised, or to at least reduce the obstruction caused by the product. The sensor may be moved automatically to a predetermined position or may be moved until the sensor determines that the obstruction is reduced. The position of the sensor may be monitored by a second sensor to confirm the first sensor position and relocation, if necessary. In some embodiments, the vehicle may additionally and/or alternatively adjust an output of the sensor to compensate for the obstruction or the stage of assembly. In some embodiments, the vehicle may simply disable or temporarily inactivate or otherwise ignore the signal from one or more sensors the vehicle determines are obstructed. In some embodiments, the vehicle may additionally activate a secondary sensor to replace the sensor which was deactivate. The secondary sensor may be positioned in a position which is less obstructed by the product than the first sensor. The vehicle is therefore configured to detect an obstruction of one or more of the one or more sensors coupled to the vehicle, determine a corrective action, and automatically perform the corrective action to compensate for the obstructed sensor.
[0339] As the vehicle 10 facilitates movement of a load (e.g., a product or components of a product, etc.) throughout a manufacturing environment, changes during the movement or changes in the state or configuration of the product may cause one or more of the sensors 112 (e.g., the short-range sensors 800, the long-range sensors 802, etc.) to become obstructed. For example, the vehicle 10 may be facilitating movement of a product during various stages of assembly. As such, the specifications of the product may change during the various stages of assembly. Certain components of the product may therefore be positioned differently on the vehicle 10 at different points in time and may cause an obstruction to the sensors 112. For example, a piece of machinery having a boom may be undergoing assembly. When the boom is added to the assembly during the production of the machinery, the boom may overhang the vehicle 10 or otherwise be positioned to cause an obstruction to a field of view or sensor range of one or more of the sensors 112 (e.g., the booms hangs in front of an ultrasonic sensor on the vehicle 10, etc.).
[0340] To account for obstruction of the sensors 112, the vehicle 10 may detect the obstruction and automatically perform a corrective action from a plurality of corrective actions to compensate for the obstruction. The corrective action may include repositioning the sensors 112, activating additional sensors 112, deactivating the obstructed sensors 112, ignoring the signals from the obstructed sensors 112, adjusting a parameter or output of the sensors 112, or other coupling a new sensor 112 to the vehicle 10 and/or the product. The corrective action (repositioning of the sensors 112 on the vehicle 10 or adding additional sensors 112 to the vehicle 10, etc.) may occur automatically in response to an obstruction of one or more of the sensors 112 or it may occur on a certain interval (e.g., when the vehicle 10 reaches a certain station or stage of assembly, etc.).
[0341] In some embodiments, the corrective action includes the one or more of the sensors 112 being repositioned or added to the vehicle 10 manually. In such embodiments, the corrective action may include providing a notification to a user indicating the obstruction and what sensors 112 should be moved or added to the vehicle 10. For example, one or more of the sensors 112 may detect an obstruction of one or more of the sensors 112. In response, the controller 102 may submit a request to an operator (e.g., a manager, a user, etc.) to manually reposition one or more of the sensors 112 or add an additional sensor 112 to the vehicle 10. In another example, an operator may detect an obstruction of one or more of the sensors 112. The operator may manually reposition one or more of the sensors 112 or add an additional sensor 112 to the vehicle 10. The operator may reposition or add one or more of the sensors 112 from an offline state on the vehicle 10. The operator may cause the offline sensor 112 to become online, thereby adding the newly online sensor 112 to the sensing system of the vehicle 10. The newly online sensor 112 may remain in place or the operator may reposition the newly online sensor 112 to a different position on the vehicle 10. In some embodiments, the operator may add an additional sensor 112 not already located on the vehicle 10. For example, the operator may have access to a stock of additional sensors 112 that can be added (e.g., coupled, etc.) to the vehicle 10.
[0342] In some embodiments, the sensors 112 may be repositioned or moved on the vehicle 10 automatically (e.g., via an actuator, etc.) as the corrective action. Referring back to
[0343] In operation, one or more of the sensors 112 may detect an obstruction of one or more of the sensors 112. In response, the controller 102 may automatically control the corresponding sensor actuator 1404 to move the obstructed sensor 112 to a different position (e.g., an unobstructed position on the vehicle 10, etc.). The control 102 may rely on the secondary sensors 812 to determine the position of the obstructed sensors 112 and to monitor the movement of the obstructed sensor 112 to its new position. In some embodiments, the controller 102 is configured to move the sensors 112 through a range of positions until a signal from the sensor 112 indicates the field of view of the sensor 112 is either not obstructed or is obstructed below a threshold amount such that the sensor 112 can operate accurately.
[0344] Referring specifically to
[0345] Referring again to
[0346] In some embodiments, an additional sensor 112 may be added to the vehicle 10 and/or the product. For example, at a stage of manufacturing where the product extends far longer than the vehicle 10, a sensor 112 can be coupled to a front or end of the product and wirelessly communicate with the controller 102 to provide the controller with accurate information regarding the environment around the vehicle. For example, referring now to
[0347] Any additional sensors 112 added to the vehicle 10 (e.g., added to the vehicle 10, added to a load via a fixture, etc.) may be temporary. For example, an additional sensor 112 may be added to the vehicle 10 or to the load in an advantageous position (e.g., a better position for sensing based on the location of the vehicle 10 or a current task of the vehicle 10, etc.). One or more of the sensors 112 on the vehicle 10 or on the load (e.g., an obstructed sensor, etc.) may be turned off temporarily.
[0348] In some embodiments, the controller 102 monitors a state or condition of the product (e.g., manufacturing station, assembly station, assembly state, etc.) and preemptively performs a corrective action to avoid or reduce a predetermined and/or predicted obstruction of a field of view of a sensor. For example, the controller may receive a signal indicating the vehicle 10, and the product it carries, such as boom assembly 68, are prior to a stage wherein the boom assembly 68 will be modified and thereafter obstruct the field of view of a sensor 112. To preemptively account for the upcoming obstruction, the controller 102 may control one or more sensor actuators 1404 to adjust a position of one or more sensors 112 to reduce or eliminate the upcoming obstruction. In some embodiments, the controller 102 includes a plurality of predetermined obstruction states. Each predetermined obstruction state may be associated with the one or more sensors 112 affected by the obstruction, and with positions for the one or more sensors 112 to be moved to accommodate the obstruction. The state or condition of the product can be provided to the vehicle 10 or monitored and/or determined directly via the vehicle 10 by the one or more sensors 112.
[0349] In some embodiments, the corrective action includes adjusting a sensor output, signal, or parameter of the sensor 112 based on an obstruction. The parameter or sensor output can be a threshold required to trigger an alert, a threshold require to detect an object, a minimum allowable distance between the vehicle 10 and a detected object, etc. This parameter can be adjusted to accommodate the obstruction. In some embodiments, the corrective action includes the controller 102 ignoring or muting the signal from the obstructed sensor 112. For example, if during normal operation (i.e., unobstructed) the sensor 112 may trigger an alert, but the controller 102 has determined the sensors 112 is obstructed (e.g., based on a signal from the sensors 112, a stage or condition of the product, a signal from secondary sensors 812, etc.) the controller 102 can ignore the signal from the obstructed sensor 802 and therefore mute the sensor 112.
[0350] In some embodiments, the vehicle 10 may have a plurality of operating modes, each corresponding to an arrangement of sensors 112. The plurality of operating modes includes an autonomous mode, a semi-autonomous mode, a manual mode, a slow mode, a fast mode, etc.). For example, if the sensors 112 are in a first position, the controller 102 may control the vehicle 10 in an autonomous mode. If one or more of the sensors 112 are obstructed, the controller 102 may determine the arrangement of the sensors 112 now meets the conditions for a second operation mode such as a semi-autonomous operating mode.
[0351] Based on the positioning of the sensors 112 onboard the vehicle 10, a status or confirmation of a status of the sensors 112, or the operating mode, the vehicle 10 may perform various functions. For example, when the sensors 112 are in a first configuration onboard the vehicle 10, the vehicle 10 may be configured to perform certain functions (e.g., only predetermined functions, a first set of steps, etc.). After repositioning of one or more of the sensors 112 or the addition of additional sensors 112, the sensors 112 may be in a second configuration onboard the vehicle 10. In the second configuration, the vehicle 10 may perform certain functions (e.g., only predetermined functions, a second set of steps, etc.) which are different from the functions performed by the vehicle 10 when the sensors 112 are in the first configuration. The vehicle 10 may perform any functions or combination of functions when the sensors 112 are in any configuration onboard the vehicle 10.
[0352] The vehicle 10 may also monitor and track the stages of assembly of a product by receiving various inputs (e.g., via the sensors 112, manually by an operator, with a camera, etc.) and processing the inputs. For example, the vehicle 10 may determine a current stage of assembly of the product. The vehicle 10 may then determine an effect on the sensors 112 onboard the vehicle 10 based on the current stage of assembly of the product. The vehicle 10 may determine how the sensors 112 will be affected by one or more stages of assembly of the product and may adjust the sensors 112 accordingly. For example, the vehicle 10 may change the threshold required to trigger a notification or an action. As another example, the vehicle 10 may mute a notification or prevent an action that would be generated by a sensor 112 known to be obstructed at the current stage of assembly of the product.
[0353] A method of manufacturing a vehicle according to the description provided herein may include several processes. The method may include providing a frame and coupling an interface assembly configured to support a product to the frame. The method may also include coupling one or more sensors to the frame, the sensors configured to sense an environment around the vehicle. The method may further include communicably coupling a controller to the one or more sensors, the controller configured to receive a signal from the one or more sensors, detect an obstruction in the field of view of the one or more sensors, determine a corrective action to compensate for the obstruction, and automatically perform the corrective action. The controller may be further configured to determine the corrective action by selecting a corrective action from a plurality of corrective actions.
[0354] The method may also include one or more additional processes. Configuring the controller to determine the corrective action to compensate for the obstruction may include configuring the controller to reposition one or more of the sensors on the vehicle. The method may include coupling a sensor actuator to one or more of the sensors, the sensor actuator configured to move the sensor between a plurality of positions. Configuring the controller to automatically perform the corrective action may also include moving one or more of the sensors from a first position in the plurality of positions to a second position in the plurality of positions based on the signal, wherein the second position is the position least obstructed according to the signal.
Modular Implements
[0355] Referring generally to the figures, a vehicle includes multiple interchangeable implements. The vehicle includes a frame defining a recess and a series of flanges extending along the recess. Each of the flanges defines a series of first apertures. Each implement includes a base frame defining a series of second apertures. The second apertures align with the first apertures, such that bolts can be inserted through both sets of apertures to fixedly and removably couple the base frame of the implement to the frame of the vehicle. By utilizing a common bolt pattern between the base frames of different implements, the implements may be quickly and easily removed and interchanged by removing the bolts.
[0356] Referring to
[0357] Referring to
[0358] The front flange 1000 and the side flanges 1002 each define a series of apertures or passages, shown as fastener apertures 1004. Specifically, the front flange 1000 defines three fastener apertures 1004 spaced laterally apart from one another. Each of the side flanges 1002 defines a pair of fastener apertures 1004 spaced longitudinally from one another. In other embodiments, the front flange 1000 and/or the side flanges 1002 define more or fewer fastener apertures 1004.
[0359] The fastener apertures 1004 extend vertically through the respective flanges. The fastener apertures 1004 may extend completely through the flanges (e.g., may be through holes) or extend partially through the flanges (e.g., may be blind holes). Each of the fastener apertures 1004 is configured (e.g., sized and shaped) to receive a corresponding fastener 1006 to secure an implement to the frame 12. In some embodiments, the fastener apertures 1004 are threaded to threadedly engage the fasteners 1006. In other embodiments, the fastener apertures 1004 are through holes, and the fasteners 1006 engage with a nut or other retainer on a bottom side of the corresponding flange.
[0360] The back plate 18 defines a series of apertures or passages, shown as fastener apertures 1010. Specifically, the back plate 18 defines four fastener apertures 1010 spaced laterally apart from one another. In other embodiments, the back plate 18 defines more or fewer fastener apertures 1004.
[0361] The fastener apertures 1010 extend longitudinally through the back plate 18. The fastener apertures 1010 may extend completely through the flanges (e.g., may be through holes). Each of the fastener apertures 1010 is configured (e.g., sized and shaped) to receive a corresponding fastener 1012 to secure an implement to the frame 12. In some embodiments, the fastener apertures 1010 are clearance holes permitting the fasteners 1012 to pass completely through the back plate 18.
[0362] Referring to
[0363] The base plate 1022 defines a series of passages or apertures, shown as slots 1030. The slots 1030 are similar in quantity and position to the fastener apertures 1004. The slots 1030 extend vertically through the base plate 1022 and are each sized to receive one of the fasteners 1006 therethrough. The slots 1030 each have a first lateral dimension and a second longitudinal dimension. The longitudinal dimension is larger than the lateral dimension, such that the slots 1030 are wider longitudinally than laterally. Accordingly, the slots 1030 permit adjustment of the longitudinal positions of the fasteners 1006 relative to the base frame 1020.
[0364] The back plate 1024 defines a series of apertures or passages, shown as fastener apertures 1032. The fastener apertures 1032 are similar in quantity and position to the fastener 1012. The fastener apertures 1032 extend longitudinally through the back plate 1024. Each of the fastener apertures 1032 is configured (e.g., sized and shaped) to receive a corresponding fastener 1012 to secure the lifting implement 50 to the frame 12. In some embodiments, the fastener apertures 1032 are threaded to threadedly engage the fasteners 1012.
[0365] To assemble the lifting implement 50 with the base assembly 48, the base frame 1020 is inserted into the implement recess 20. The base plate 1022 rests atop the front flange 1000 and the side flanges 1002. Accordingly, the engagement between the base plate 1022, the front flange 1000, and the side flanges 1002 limits downward movement of the base frame 1020 relative to the frame 12 (e.g., supports downward forces on the lifting implement 50).
[0366] The slots 1030 align with the fastener apertures 1004. Accordingly, the fasteners 1006 may be inserted through the slots 1030 and engage with the fastener apertures 1004. Engagement between the fasteners 1006 and the sides of the slots 1030 limits lateral movement of the base frame 1020 relative to the frame 12. While the fasteners 1006 are loose, the slots 1030 permit longitudinal adjustment of the base frame 1020 relative to the frame 12.
[0367] The base frame 1020 is adjusted rearward until the back plate 1024 engages the back plate 18. Engagement between the back plate 1024 and the back plate 18 limits rearward movement of the base frame 1020 relative to the frame 12. The fastener apertures 1010 align with the fastener apertures 1032. Accordingly, the fasteners 1012 may be inserted through the fastener apertures 1032 and engage with the fastener apertures 1010. Engagement between the fasteners 1012 and the back plate 18 limits forward movement of the base frame 1020 relative to the frame 12. The fasteners 1006 and the fasteners 1012 are tightened to fixedly couple the base frame 1020 to the frame 12. The actuators 116, sensors 112, and/or any other functional components of the lifting implement 50 may be operatively coupled (e.g., electrically and/or hydraulically coupled) to the base assembly 48 (e.g., by one or more electrical connectors and/or hydraulic connectors). At this point, the lifting implement 50 may be ready for use.
[0368] To remove the lifting implement 50 from the base assembly 48, the electrical and hydraulic connectors may be disconnected. The fasteners 1006 and 1012 may be removed. The lifting implement 50 may then be lifted out of the implement recess 20. After the lifting implement 50 is removed, it may be replaced with another implement (e.g., the cart implement 60).
[0369] Referring to
[0370] Referring to
[0371] Referring to
[0372] The cart implement 60 includes a substantially horizontal top plate 1050 that has a substantially horizontal top surface, shown as a top surface 1052. The top surface 1052 defines a pair of apertures, shown as pin apertures 1054, that each receive either the driving pin 62 or the turning pin 64. With the base frame 1020 fixedly coupled to the frame 12, the top surface 1052 is flush with the top surface 30 of the frame 12. Accordingly, every part of the cart implement 60 below the top surface 1052 may fit completely within the implement recess 20.
[0373] The cart implement 60 may represent the cart interface 700 and/or the cart interface 3000. Accordingly, the cart interface 700 and the cart interface 3000 may each be interchangeably coupled with the frame 12. The base frame 1020 may represent or include the mounting interface 702 and/or the mounting interface 3016.
[0374] Referring to
[0375] The turning implement 1060 includes a structure, shown as frame 1062. The frame 1062 is fixedly coupled to the base frame 1020 and extends upward from the base frame 1020. The turning implement 1060 includes a movable portion, shown as lift table 1064. The lift table 1064 is slidably coupled to the frame 1062 by a series of linear bearings or linear guides, shown as guides 1066. The guides 1066 permit the lift table 1064 to move vertically relative to the frame 1062, but prevents movement in other directions.
[0376] The turning implement 1060 includes a pair of actuators (e.g., actuators 116), shown as lift actuators 1068. By way of example, the lift actuators 1068 may be or include electric linear actuators. The lift actuators 1068 are each coupled to the frame 1062 and to the lift table 1064. The lift actuators 1068 are configured to raise and lower the lift table 1064 relative to the frame 1062.
[0377] The turning implement 1060 further includes a rotational member (e.g., a slewing bearing), shown as turntable 1070. The turntable 1070 includes a first portion, shown as base section 1072, and a second portion, shown as rotating section 1074. The base section 1072 is fixedly coupled to the lift table 1064, and the rotating section 1074 is rotatably coupled to the base section 1072. The rotating section 1074 is configured to rotate about a substantially vertical axis. The rotating section 1074 may be coupled to a product, such as the telehandler 56 or the boom assembly 68. By way of example, the rotating section 1074 may be coupled to a cradle 52 that supports a product.
[0378] The turning implement 1060 includes an actuator (e.g., an actuator 116), shown as turning actuator 1076. By way of example, the turning actuator 1076 may be or include an electric motor. The turning actuator 1076 is coupled to the frame 1062 and to the rotating section 1074. The turning actuator 1076 is configured to rotate the rotating section 1074 relative to the frame 1062.
Modular Frame
[0379] Referring to
[0380] As shown in
[0381] As shown in
Vehicle Coupling System
[0382] Referring generally to the figures, a first vehicle may be utilized with a second vehicle to cooperatively operate to support a product and facilitate moving the product (e.g., through various stages of assembly). The first vehicle may include a drive motor to propel the first vehicle along a ground surface with which the first vehicle is engaged. The first vehicle may be coupled with the second vehicle with a tow bar extending therebetween. The tow bar may be pivotally coupled with the first vehicle and fixedly coupled with the second vehicle. In response to the drive motor propelling the first vehicle, the tow bar exerts a force on the second vehicle to maintain a distance between the first vehicle and the second vehicle. In this manner, the second vehicle does not include a drive motor, and is instead driven by the coupling with the first vehicle via the tow bar.
[0383] The products carried by the first vehicle and the second vehicle may have varying lengths. A distance between the first vehicle and the second vehicle may change based on the length of the product to be carried thereby. To accommodate for the change in the distance between the first vehicle and the second vehicle (and the varying lengths of the products), the tow bar may include two or more members telescopically coupled to each other to enable varying a length of the tow bar.
[0384] The first vehicle and the second vehicle may be coupled together by a conduit configured to transfer at least one of (i) electrical energy, (ii) fluid power, or (iii) information between the first cart and the second cart. By way of example, the first vehicle may transfer, via the conduit, electrical energy from batteries of the first vehicle to power one or more components of the second vehicle. By way of another example, the first vehicle may transfer, via the conduit, fluid power from a hydraulic system to fluidly power one or more components of the second vehicle. By way of yet another example, the first vehicle may transfer, via the conduit, data associated with the operation of the first vehicle to the second vehicle (e.g., to control one or more components of the second vehicle). A conduit management system may be used to support a portion the conduit extending across a space defined by a distance between the first vehicle and the second vehicle. By way of example, the conduit may be routed through an interior cavity of the tow bar to couple (e.g., electrically couple, fluidly couple, and/or communicably couple) the first vehicle and the second vehicle to each other.
[0385] Referring to
[0386] According to an exemplary embodiment, the skate 1200 omits the drive motors 42 and is instead propelled and steered by the vehicle 10. The skate 1200 and the vehicle 10 may be mechanically coupled to each other by a mechanical linkage (e.g., tube, bar, coupler, etc.), shown as tow bar 1204, extending therebetween to maintain a distance between the skate 1200 and the vehicle 10 (e.g., as the vehicle 10 travels). The tow bar 1204 may be pivotably coupled to the vehicle 10 (e.g., by a pivot joint, by a pin about which the tow bar 1204 can pivot, etc.) and fixedly coupled to the skate 1200 such that when the drive motors 42 of the vehicle 10 provide rotational mechanical energy to drive the tractive elements 44 and propel the vehicle 10, the tow bar 1204 pulls the skate 1200 with the vehicle 10. In this manner, responsive to the vehicle 10 being driven, the tow bar 1204 exerts a force on the skate 1200 such that the skate 1200 is driven at the same speed, in the same direction, and is maintained at a fixed distance (e.g., the fixed distance being a length of the tow bar 1204) from the vehicle 10 (e.g., even if the vehicle 10 and the skate 1200 are not collectively supporting the product). By way of example, when the vehicle 10 turns, the tow bar 1204 pivots relative to the vehicle 10 and exerts a force on the skate 1200 to pull the skate 1200 such that the skate 1200 trails the vehicle 10.
[0387] Referring still to
[0388] Referring to
[0389] Referring to
[0390] Referring to
[0391] Referring still to
[0392] Referring to
[0393] The first telescoping section 1236 includes a flange 1250 configured to engage with a shoulder 1254 of the second telescoping section 1240 to prevent translation of the shoulder 1254 beyond the flange 1250, thereby maintaining the second telescoping section 1240 within the first telescoping section 1236. By way of example, when the tow bar 1204 is in the lengthened position 1244, the flange 1250 may engage with the shoulder 1254 to prevent translation of the shoulder 1254 past the flange 1250. Similarly, the first telescoping section 1236 includes a flange 1258 configured to engage with the shoulder 1254 of the second telescoping section 1240 to prevent translation of the shoulder 1254 past the flange 1258, thereby maintaining the second telescoping section 1240 within the first telescoping section 1236. By way of example, when the tow bar 1204 is in the shortened position 1246, the flange 1258 may engage with the shoulder 1254 to prevent translation of the shoulder 1254 past the flange 1258.
[0394] Referring still to
[0395] In some embodiments, the conduit 1266 is or includes an electrical energy transfer conduit (e.g., wire, cable, etc.) configured to transfer electrical energy between the vehicle 10 and the skate 1200. In such embodiments, the conduit 1266 electrically couples an electrical energy source of the vehicle 10 (e.g., the batteries 110) with the skate 1200 to facilitate delivering electrical energy to one or more components thereof and power the same. By way of example, the conduit 1266 may be configured to deliver electrical energy from the batteries 110 of the vehicle 10 to power a control system (e.g., control system 1300) of the skate 1200, the user interface 1232, the actuators 116 of the lifting implement 50 included in the skate 1200 (e.g., in an embodiment where the actuators 116 are electrically powered), or other components of the skate 1200.
[0396] In some embodiments, the conduit 1266 is or includes a fluid transfer conduit (e.g., hose, pipe, tube, hydraulic fluid line, pneumatic fluid line, etc.) configured to transfer fluid power between the vehicle 10 and the skate 1200. In such embodiments, the conduit 1266 fluidly couples a fluid supply source of the vehicle 10 (e.g., the hydraulic system 120, a pneumatic pump, etc.) with the skate 1200 to facilitate delivering fluid power to one or more components thereof. By way of example, the conduit 1266 may be configured to supply pressurized hydraulic fluid from the hydraulic system 120 of the vehicle 10 to the hydraulic system 120 of the skate 1200 to fluidly power the actuators 116 of the lifting implement 50 included in the skate 1200 (e.g., in an embodiment where the actuators 116 are hydraulically powered) or other components of the skate 1200.
[0397] In some embodiments, the conduit 1266 is or includes a data transfer conduit (e.g., wire, cables, CAN, Ethernet, etc.) configured to transfer data between the vehicle 10 and the skate 1200. In such embodiments, the conduit 1266 is a wired connection that communicably couples the control system 100 of the vehicle 10 with skate 1200 to facilitate transmitting information to the skate 1200 to control operation thereof. By way of example, the control system 100 of the vehicle 10 can transmit control signals to a control system (e.g., control system 1300) of the skate 1200 and/or directly to one or more components of the skate 1200 via the conduit 1266 to control operation thereof. Additionally or alternatively, the communication interface 108 may facilitate wireless communication (e.g., through Bluetooth, Wi-Fi, radio transmission, inductive transmission of energy, etc.) between the vehicle 10 and the skate 1200. By way of another example, the control system of the skate 1200 can transmit control signals and/or other information associated with the operation of thereof to the vehicle 10 via the conduit 1266 and/or wirelessly via communications established between a communication interface (e.g., communication interface 1308) of the skate 1200 and the communication interface 108 of the vehicle 10.
[0398] Referring to
[0399] Referring to
[0400] Referring to
[0401] Referring to
[0402] In some embodiments, the when the vehicle 10 and the skate 1200 are cooperatively operating to facilitate steering the product and distributing the weight of the product during transportation, the conduit 1266 may be routed between the vehicle 10 and the skate 1200 along the product. By way of example, at least a portion of the section of the conduit 1266 extending between the vehicle 10 and the skate 1200 may be coupled to the product (e.g., by one or more hooks, adhesives, fasteners, channels, tip-ties, etc.). By way of another example, the conduit 1266 may be supported by (e.g., rest on, couple with, etc.) one or more components of the product (e.g., a frame of the telehandler 56).
[0403] Referring to
[0404] The base assembly 1206 may include one or more user interfaces 1232. The user interface 1232 may be configured as an emergency stop button that can be engaged by a user to manually override one or more operations of the vehicle 10, the skate 1200, and/or any one or more components included therein. As described in greater detail above, the user interface 1232 may include one or more other operator interface elements (e.g., input devices, output devices, etc.).
[0405] The skate 1200 includes the implement 50 configured to receive and directly support a product and raise or lower the product. The controller 1302 may control operation of the implement 50 and the components thereof.
[0406] The control system 1300 may include the vehicle 10 and the skate 1200. The vehicle 10 and the skate 1200 may be coupled (e.g., electrically coupled, fluidly coupled, and/or communicably coupled) to each other via the conduit 1266. The controller 1302 of the skate 1200 may control the transfer of electrical energy, the transfer of fluid power, and/or the transfer of data between the vehicle 10 and the skate 1200. By way of example, responsive to a signal received from the controller 1302 of the skate 1200, the vehicle 10 may (i) transfer electrical energy from the batteries 110 of the vehicle 10 to power one or more components of the skate 1200, (ii) transfer fluid power from the hydraulic system 120 to fluidly power one or more components of the skate 1200, and/or (iii) transfer data associated with the operation of the vehicle 10 to the skate 1200 (e.g., to control one or more components of the skate 1200) via the conduit 1266. In some embodiments, the skate 1200 transmits data associated with the operation thereof to the vehicle 10 (e.g., wirelessly via the communication interface 1308 and/or via a wired connection). Responsive to the data, the controller 102 of the vehicle 10 may determine whether to transfer electrical energy, fluid power, and/or data to the skate 1200. In some embodiments, the controller 102 is communicably coupled with the skate 1200 to control operation of the components thereof. In such an embodiment, the skate 1200 does not include the controller 1302 and operational control and processing is performed remote from the skate 1200 (e.g., by the controller 102, by a remote server, etc.).
[0407] In some embodiments, the skate 1200 includes one or more sensors (e.g., sensors 112) operatively coupled to the controller 1302 and/or the controller 102. The sensors may provide sensor data indicative of the current status of the vehicle 10, the skate 1200, and/or the surrounding environment. In such embodiments, vehicle 10 may communicate with the skate 1200 to share information and facilitate operation. By way of example, the vehicle 10 may provide commands to the skate 1200 to coordinate transportation of a large item that is carried by both the vehicle 10 and the skate 1200. By way of another example, the vehicle 10 may provide its location to the skate 1200 to facilitate path generation and avoid collisions. In such embodiments, the skate 1200 may include one or more drive motors (e.g., drive motors 42) to provide rotational mechanical energy to drive rotation of one or more tractive elements and propel the skate 1200 to maintain a fixed distance from the vehicle 10 without the use of the tow bar 1204.
Vehicle Coupling
[0408] Referring generally to the figures, a vehicle that is utilized in a manufacturing line or process is shown. The vehicle includes a frame and a base assembly coupled to the frame. The base assembly is configured to couple various implements to the frame, and the implements facilitate positioning, supporting, and/or lifting of a component of a product (e.g., a telehandler or an axle assembly of a telehandler). In some embodiments, the implement includes a lift implement with a cradle that receives and supports the component of the product and a lift assembly coupled between the cradle and the base assembly. The lift assembly includes a platform to which the cradle is rotatably coupled to.
[0409] In some embodiments, a first vehicle and a second vehicle (that are substantially similar or identical to each other) cooperatively support the product for movement, and the front vehicle (e.g., the first vehicle or the second vehicle) may turn relative to the rear vehicle (e.g., the first vehicle or the second vehicle) via drive motors or a steering motor. As the front vehicle turns relative to the rear vehicle, the cradle of the front vehicle may rotate relative to the platform of the front vehicle and permit the two vehicles to turn. The first vehicle and the second vehicle each include a rotation locking assembly configured to selectively permit or inhibit rotation of the cradle relative to the platform based on which vehicle of the first vehicle or the second vehicle is the front vehicle. The rotation locking assembly includes a pin configured to extend within an aperture of a bracket coupled with the cradle and an aperture of the platform in a first position to inhibit rotation of the cradle relative to the platform. The pin is movable out of the first position (e.g., out of engagement with the cradle and the platform) to a second position to permit rotation of the cradle relative to the platform.
[0410] To transition from a first configuration in which the first vehicle is the front vehicle and the second vehicle is the rear vehicle to a second configuration in which the second vehicle is the front vehicle and the first vehicle is the rear vehicle, a pin of the first vehicle is transitioned from the second position to the first position and the pin of the second vehicle is transitioned from the first position to the second position. Similarly, to transition from the first configuration to the second configuration, the pin of the first vehicle is transitioned from the first position to the second position and the pin of the second vehicle is transitioned from the second position to the first position. Transitioning between the first configuration and the second configuration is advantageous in certain operational scenarios in which it is difficult or impossible (e.g., due to space constraints) to transition the front vehicle (e.g., turn the front vehicle and the rear vehicle supporting the product) from traveling in a first direction to traveling in a second direction opposite the first direction while remaining in one of the first configuration or the second configuration.
[0411] As shown in
[0412] According to an exemplary embodiment, any of the functions or processes described herein with respect to the first vehicle 10a may be performed by the second vehicle 10b. In such an embodiment, any of the functions or processes described herein with respect to the control system 100 of the first vehicle 10a may be performed by the control system 100 of the second vehicle 10b and/or one or more servers (e.g., remote devices 134). By way of example, data collection may be performed by the control system 100 of the first vehicle 10a and control over one or more components to move or steer the product may be performed by the control system 100 of the second vehicle 10b. By way of example, data collection may be performed by the control system 100 of the second vehicle 10b and control over one or more components to move or steer the product may be performed by the control system 100 of the first vehicle 10a. By way of still another example, a first portion of data collection may be performed by the control system 100 of the first vehicle 10a, a second portion of data collection may be performed by the control system 100 of the second vehicle 10b, and control over one or more components to move or steer the product may be performed by the control system 100 of the first vehicle 10a and/or the control system 100 of the second vehicle 10b.
[0413] As shown in
[0414] As shown in
[0415] With the first vehicle 10a and the second vehicle 10b oriented as shown and described, when the first vehicle 10a and/or the second vehicle 10b are steered to turn the product supported thereby, the first vehicle 10a does not contact the second vehicle 10b. By way of example, one or both of the first vehicle 10a or the second vehicle 10b were oriented with the first side 1310 positioned proximate the space 1318, when the first vehicle 10a and/or the second vehicle 10b are steered to turn the product, the first vehicle 10a and the second vehicle 10b may contact each other and potentially cause damage (e.g., scrapes, abrasions, dents, etc.) to each other. Further, with the first sides 1310 of the first vehicle 10a and the second vehicle 10b positioned away from the space 1318, the space 1318 is larger (e.g., compared to the space 1318 if one or both of the first vehicle 10a or the second vehicle 10b were oriented with the first side 1310 positioned proximate the space 1318) to provide access to a greater area of the bottom surface of the product.
[0416] As shown in
[0417] As shown in
[0418] As shown in
[0419] As shown in
[0420] In the second position 1328, the pin 1320 extends through a third opening, shown as second bracket opening 1356, defined by a second bracket 1352. As shown in
[0421] As shown in
[0422] When the cradle 52 is positioned (e.g., rotated) such that the first bracket aperture 1336 is aligned (e.g., vertically aligned, vertically coaxial, etc.) with the platform aperture 1340, the first bracket aperture 1336 and the platform aperture 1340 may cooperatively receive the pin 1320 (e.g., in the first position 1324) to inhibit rotation of the cradle 52. Similarly, in such a position, the pin 1320 may be removed from the first bracket aperture 1336 and the platform aperture 1340 out of engagement with the cradle 52 and the top platform 402 (e.g., by an operator) and placed in the second bracket opening 1356 to transition (e.g., move) the pin 1320 to the second position 1328. In some embodiments, the pin 1320 is otherwise moveable to transition between the first position 1324 and the second position 1328 (or another position that is not the first position 1324) to selectively permit rotation of the cradle 52 relative to the top platform 402. By way of example, the pin 1320 may be coupled with a solenoid configured to move the pin 1320 between the first position 1324 and the second position 1328 (or another position that is not the first position 1324). In some embodiments, the rotation locking assembly does not include the pin 1320 and uses another suitable mechanism to selectively permit rotation of the cradle 52 relative to the top platform 402. By way of example, the rotation locking assembly may include a lock (e.g., a pad lock) configured to lock in the first position 1324 or the second position 1328 (or another position that is not the first position 1324) such that an operator with access to the lock (e.g., an operator with a key to lock/unlock the lock, an operator with a password (e.g., pin, combination, etc.), etc.) can transition the lock between the first position 1324 and the second position 1328 (or another position that is not the first position 1324). By way of another example, the rotation locking assembly may include an electromagnetic lock configured to selectively magnetically couple the cradle 52 with the top platform 402. By way of another example, the rotation locking assembly may include a brake system configured to selectively induce a friction force between the cradle 52 and the top platform 402.
[0423] As shown in
[0424] According to an exemplary embodiment, the rotation locking assembly enables selectively permitting and inhibiting rotation of the cradle 52 relative to the top platform 402 for the first vehicle 10a and the second vehicle 10b to enable steering of the first vehicle 10a and the second vehicle 10b while supporting the telehandler 56. As described herein, the first vehicle 10a and the second vehicle 10b may support the telehandler 56 (e.g., during the manufacturing line process), and the front vehicle 10 of the first vehicle 10a or the second vehicle 10b may turn relative to the rear vehicle 10 of the other one of the first vehicle 10a or the second vehicle 10b via the drive motors 42 or a steering motor. The pin 1320 of the front vehicle 10 may be positioned in the second position 1328 (or another position not in the first position 1324) such that as the front vehicle 10 turns relative to the rear vehicle 10, the cradle 52, which supports the telehandler 56, of the front vehicle 10 may rotate relative to the top platform 402 of the front vehicle 10, and the pin 1320 of the rear vehicle 10 may be positioned in the first position 1324 such that as the front vehicle 10 turns relative to the rear vehicle 10, the cradle 52 is inhibited from rotating relative to the top platform 402 of the rear vehicle 10 and allow the two vehicles to turn (e.g., the two vehicles are not restricted to travel in a straight line). By way of example, when the first vehicle 10a is the front vehicle 10 and the second vehicle 10b is the rear vehicle 10, the pin 1320 of the first vehicle 10a may be in the second position 1328, and the pin 1320 of the second vehicle 10b may be in the first position 1324. By way of another example, when the second vehicle 10b is the front vehicle 10 and the first vehicle 10a is the rear vehicle 10, the pin 1320 of the second vehicle 10b may be in the second position 1328, and the pin 1320 of the first vehicle 10a may be in the first position 1324. In this manner, regardless of which vehicle 10 of the first vehicle 10a or the second vehicle 10b is the front vehicle 10 and which vehicle 10 of the first vehicle 10a or the second vehicle 10b is the rear vehicle 10, the pin 1320 is repositionable to selectively permit or inhibit rotation of the cradle 52 relative to the top platform 402 depending on the arrangement of the vehicles 10.
[0425] According to an exemplary embodiment, to transition from a first configuration in which the first vehicle 10a is the front vehicle 10 and the second vehicle 10b is the rear vehicle 10 to a second configuration in which the second vehicle 10b is the front vehicle 10 and the first vehicle 10a is the rear vehicle 10, the pin 1320 of the first vehicle 10a is transitioned (e.g., moved) from the second position 1328 to the first position 1324 (e.g., removed from the second bracket opening 1356 and received in the first bracket aperture 1336 and the platform aperture 1340) and the pin 1320 of the second vehicle 10b is transitioned from the first position 1324 to the second position 1328 (e.g., removed from the first bracket aperture 1336 and the platform aperture 1340 and received in the second bracket opening 1356). Similarly, to transition from the first configuration to the second configuration, the pin 1320 of the first vehicle 10a is transitioned from the first position 1324 to the second position 1328 and the pin 1320 of the second vehicle 10b is transitioned from the second position 1328 to the first position 1324. In some embodiments, transitioning between the first configuration and the second configuration is advantageous in certain operational scenarios in which it is difficult or impossible (e.g., due to space constraints) to transition the front vehicle 10 (e.g., turn the front vehicle 10 and the rear vehicle 10 supporting the telehandler 56) from traveling in a first direction to traveling in a second direction opposite the first direction while remaining in one of the first configuration or the second configuration. By way of example, if the first vehicle 10a is the front vehicle 10 traveling in a first direction along the manufacturing line 156 between the stations 160 and then needs to travel in a second direction along the manufacturing line 156 (e.g., to a previous stations 160 or another stations 160, after delivering a first telehandler 56 and receiving a second telehandler 56, etc.), instead of turning the first vehicle 10a and the second vehicle 10b supporting the telehandler 56 around such that the first vehicle 10a remains the front vehicle 10, the rotation lock assembly enables transitioning from the first configuration to the second configuration such that the second vehicle 10b becomes the front vehicle 10 and can travel in the second direction along the manufacturing line 156. In some embodiments, the vehicle system includes a single pin 1320 for the rotation locking assemblies of the first vehicle 10a and the second vehicle 10b. By way of example, in the first configuration, the single pin 1320 may be in the first position 1324 at the first vehicle 10a, and in the second configuration, the single pin 1320 may be in the first position 1324 at the second vehicle 10b.
[0426] According to an exemplary embodiment, based on the sensor data indicating that the pin 1320 is extending through the first bracket aperture 1336 and the platform aperture 1340, the controller 102 determines that the pin 1320 is in the first position 1324 and that rotation of the cradle 52 relative to the top platform 402 is inhibited. In some embodiments, when the sensor data indicates that the pin 1320 is extending through one of the first bracket aperture 1336 or the platform aperture 1340 and not the other (e.g., the pin 1320 is extending through the first bracket aperture 1336 and not through the platform aperture 1340) or is otherwise improperly received in the first bracket aperture 1336 or the platform aperture 1340, the controller 102 determines that the pin 1320 is not in the first position 1324 and that rotation of the cradle 52 relative to the top platform 402 may be unintentionally permitted. In some embodiments, when the sensor data indicates that the pin 1320 is extending through the second bracket opening 1356, the controller 102 determines that the pin 1320 is in the second position 1328 and that rotation of the cradle 52 relative to the top platform 402 is permitted.
[0427] According to an exemplary embodiment, in response to the determination that the pin 1320 of the front vehicle 10 is in the second position 1328 and that the pin 1320 of the rear vehicle 10 is in the first position 1324, the controller 102 facilitates normal, unrestricted operation of the front vehicle 10 and the rear vehicle 10 (e.g., permits operation of the front vehicle 10 and the rear vehicle 10 in a first mode of operation). By way of example, in the first mode of operation, the controller 102 may permit normal, unrestricted operation of the drivetrain 40, the base assembly 48, the lifting implement 50, and/or any other component of the first vehicle 10a and the second vehicle 10b (e.g., the front vehicle 10 and the rear vehicle 10). In some embodiments, in response to a determination that (i) the pin 1320 of the front vehicle 10 is not in the second position 1328 (e.g., in the first position 1324, hanging from the cradle arm 432 by the cord 1360, improperly received in the first bracket aperture 1336 or the platform aperture 1340, etc.) and/or (ii) the pin 1320 of the rear vehicle 10 is not in the first position 1324 (e.g., in the second position 1328, hanging from the cradle arm 432 by the cord 1360, improperly received in the first bracket aperture 1336 or the platform aperture 1340, etc.), the controller 102 (i) limits operation of the front vehicle 10 and/or the rear vehicle 10 (e.g., in a second mode of operation) and/or (ii) provides an alert (e.g., visually or audibly via the user interface 114) indicative of an improper position of the pin 1320 of the front vehicle 10 and/or the rear vehicle 10. By way of example, in the second mode of operation, the controller 102 may (i) limit operation of the drive motors 42 such that the first vehicle 10a and/or the second vehicle 10b cannot exceed a threshold speed (e.g., 5 miles per hour, 2 miles per hour, 0 miles per hour, etc.), (ii) limit operation of the lift assembly 54 such that the lifting implement 50 cannot be raised or lowered, and/or (iii) any other control to limit operation of the first vehicle 10a and/or the second vehicle 10b. The first vehicle 10a and/or the second vehicle 10b may be limited to the second mode of operation until the pin 1320 of the front vehicle 10 is in the second position 1328 and the pin 1320 of the rear vehicle 10 is in the first position 1324.
Pathing Generation System
[0428] Referring generally to the figures, a system includes a vehicle, one or more input devices, and one or more memory devices storing instructions thereon. When executed by one or more processors, the instructions cause the one or more processors to retrieve, from the one or more memory devices, a floorplan of a production system, receive a current position of the vehicle, and receive, from the one or more input devices, one or more inputs. The one or more inputs include one or more of one or more locations in the production system, a footprint of the vehicle, or one or more obstacles. The instructions also cause the one or more processors to generate a route for the vehicle from the current position of the vehicle to the one or more locations based on the one or more inputs.
[0429] Referring now to
[0430] The production system 1601 may include one or more obstacles (e.g., shown in
[0431] Once the operator has edited the floorplan 1602 to include the obstacle 1606a, if necessary, the pathing generation system 1600 may generate one or more routes, such as route 1608a and route 1608b, of possible paths from the current location 1603 of the vehicle 10 to the target location 1604. As shown in
[0432] As shown in
[0433] In the embodiment of
[0434] Turning now to
[0435] As described further herein, route 1704a, route 1708b, and route 1712a depict the most efficient path (e.g., the shortest or fastest path, etc.) between two points (e.g., the vehicle 10 and a location), without regard to any potential obstacles between the two points. The route 1704a, the route 1708b, and the route 1712a are depicted as dashed lines to indicate a reference path for greater understanding of the embodiments disclosed herein, although the route 1704a, the route 1708b, and the route 1712a may not appear as possible paths or generated routes on the user interface or to an operator of the pathing generation system 1600.
[0436] The pathing generation system 1600 may generate the routes 1704 based one or more characteristics of the vehicle 10 and/or the load being moved by the vehicle 10. The one or more characteristics can include a capacity of the vehicle 10, a weight of the vehicle 10 and/or the load, a size or envelope of the vehicle 10, a size of the load (e.g., telehandler 56), a desired distance between the vehicle 10 or the load and an obstacle, or other characteristics of the vehicle 10 and/or the load. The size or footprint of the vehicle 10 (e.g., a length, width, and height) which defines outer boundaries of the vehicle 10 may be predetermined or may be measured by one or more sensors. For example, the vehicle 10 may be a predetermined and is known to the pathing generation system 1600. In some embodiments, the footprint of the vehicle 10 may be monitored and/or measured by one or more cameras, sensors, etc., during various stages of operation of the vehicle 10 within the production system 1601. In some embodiments, the footprint of the vehicle 10 may be determined based on a current stage of assembly of the product being moved by the vehicle 10. The current stage can be determined by a weight of the product, tracking waypoints at each stage of manufacturing the product, a location of the vehicle 10 and/or the product in the production system 1601, by an input from an operator, or by one or more sensors monitoring the product and/or the production system 1601. As such, the footprint of the vehicle 10 may be automatically communicated to the pathing generation system 1600 at various stages of operation. The vehicle 10 may have a base footprint of the vehicle 10 alone, or the vehicle 10 may have a load footprint when the vehicle 10 is carrying one or more loads, such as a component of a product assembly, a part, a machine, a tool, etc. The footprint of the vehicle 10 may be taken into account by the pathing generation system 1600 when the pathing generation system 1600 is determining one or more possible paths the vehicle 10 could take. The vehicle 10 may not be able to travel in a substantially straight path from a current location of the vehicle 10 to the target location 1700a, for example along route 1704a, due to the footprint of the vehicle 10 and the obstacle 1702a. Instead, the pathing generation system 1600 may generate a route 1704b, which avoids the obstacle 1702a.
[0437] In some embodiments, the routes 1704 are generated incrementally, based on the floorplan 1602 and/or the signals from the sensors 112, such that a route to a second target location after a first target location is not determined until after the vehicle 10 is at or near the first target location. In some embodiments, based on signals from the sensors 112, the vehicle 10 may adjust a route 1704 or may switch from one route 1704 to another route 1704.
[0438] Referring still to
[0439] Near the exit of the target location 1700a, the production system 1601 may include an obstacle 1702b and an obstacle 1702c. In an embodiment where the vehicle 10 exits the target location 1700a without the first load 1706, the vehicle 10 alone may be able to travel along any number of paths around the obstacle 1702c, including by turning left and traveling between the target location 1700a and the obstacle 1702c, or turning right and passing along a right side portion of the obstacle 1702c. However, due to the change in footprint, when the vehicle 10 exits the target location 1700a with the first load 1706, the vehicle 10 may not be able to turn onto one or more of the possible paths. For example, the vehicle 10 carrying the first load 1706 may have a longer footprint (i.e., a length of the vehicle 10 is increased when the vehicle 10 is carrying the first load 1706). Due to the longer footprint, the vehicle 10 may not be able to make as sharply of a turn as when the vehicle 10 moves throughout the production system 1601 without any load. In some situations, the vehicle 10 could reverse one or more times to move into a position to maneuver a turn (e.g., a three-point turn, etc.). However, due to the longer footprint of the vehicle 10 carrying the first load 1706, the vehicle 10 may no longer be able to reverse to maneuver a turn. For example, as shown in
[0440] The vehicle 10 may drive along the route 1708b to arrive at the target location 1700b. At the target location 1700b, the vehicle 10 may receive a second load 1710. The second load 1710 may change the footprint of the vehicle 10. For example, the second load 1710 may change the length, width, and/or height of the outer boundaries of the vehicle 10. The target location 1700b may be the next stage in a manufacturing process after the stage at target location 1700a. In some embodiments, the second load 1710 is a modification or addition to the first load 1706 that is added or performed at the target location 1700b. When the vehicle 10 is carrying the first load 1706 and the second load 1710, the vehicle 10 may need to operate differently. For example, the vehicle 10 may not be able to travel as closely to obstacles, walls, stations, humans, features, etc. or turn as sharply as the vehicle 10 may be able to without the second load 1710. In the embodiment of
[0441] Near the exit of the target location 1700a, the production system 1601 may include an obstacle 1702d. In an embodiment where the vehicle 10 exits the location 170ba without the second load 1710, the vehicle 10 alone may be able to travel along any number of paths around the obstacle 1702d, including by turning right and passing around a left side portion of the obstacle 1702d, or by turning farther right and traveling between the target location 1700b and the obstacle 1702d. However, due to the change in footprint, when the vehicle 10 exits the target location 1700b with the second load 1710, the vehicle 10 may not be able to turn onto one or more of the possible paths. For example, the vehicle 10 carrying the second load 1710 may have a wider footprint (i.e., a width of the vehicle 10 is increased when the vehicle 10 is carrying the second load 1710). Due to the wider footprint, the vehicle 10 may or may not be able to make as sharply of a turn as when the vehicle 10 moves throughout the production system 1601 without any load. In the embodiment of
[0442] In contrast to the embodiment described with respect to the obstacle 1702b potentially preventing the vehicle 10 from reversing to execute the left turn when exiting the target location 1700a, at the exit of the target location 1700b, in the embodiment of
[0443] Turning now to
[0444] In some embodiments, the optimized floorplan 1720 may only be generated once or a small number of times in relation to the regular generation of floorplans by the pathing generation system 1600. In other words, the optimized floorplan 1720 may not be generated each and every time a floorplan is generated by the pathing generation system 1600. For example, the production system 1601 may already be operating under the most efficient possible configuration or arrangement.
[0445] As shown in
[0446] In the embodiment of
[0447] Additionally, the target location 1700c has been moved towards the obstacle 1702d and the obstacle 1702e. The pathing generation system 1600 may determine that, given the footprint of the vehicle 10 at the exit of the target location 1700b (e.g., the vehicle 10 is carrying the second load 1710), any route that passes between the target location 1700b and the obstacle 1702d will not be able to be traveled by the vehicle 10. As such, the pathing generation system 1600 may determine that it is acceptable to move the target location 1700c in a manner which blocks or further hinders a more efficient possible path (e.g., a route that passes between the target location 1700b and the obstacle 1702d) because the vehicle 10 will not take that possible path due to the footprint of the vehicle 10. By moving the target location 1700c towards the obstacle 1702d and the obstacle 1702e, a route 1724 may be able to be generated which shortens the distance and travel time between the target location 1700b and the target location 1700c. It should be understood that reference to any particular arrangement of locations or directional terms only serve to illustrate non-limiting examples of the operations of the vehicle 10 within the production system 1601.
[0448] In an embodiment in which the vehicle 10 exits the target location 1700b without the second load 1710 or without any load, it may still be preferable to move the target location 1700c towards the obstacle 1702d and the obstacle 1702e. Even though moving the target location 1700c towards the obstacle 1702d and the obstacle 1702e may block or further hinder a more efficient possible path (e.g., a route that passes between the target location 1700b and the obstacle 1702d) for the vehicle 10, because the vehicle 10 still has one or more possible paths to the target location 1700c (e.g., the route 1724), moving the target location 1700c towards the obstacle 1702d and the obstacle 1702e opens up a larger amount of space within the production system 1601 (e.g., in the lower right quadrant of the optimized floorplan 1720). An increase in space within the production system 1601 can be beneficial, allowing for better overall use of space within the production system 1601. As real estate generally holds great value, saving floor space and providing for a larger area for additional stations, machines, storage, personnel, etc. results in overall cost savings or greater profits.
[0449]
[0450] At step 1758, the pathing generation system 1600 may receive one or more inputs from the input device. For example, the operator of the pathing generation system 1600 input a series of target locations and/or an order of approaching the target locations for the vehicle 10 throughout the production system 1601. As another example, the operator of the pathing generation system 1600 may edit the floorplan to include one or more of obstacles, locations, or egress points if the obstacle, location, or egress point is not already accounted for in the floorplan.
[0451] At step 1760, the pathing generation system 1600 may determine a desired path for the vehicle 10. For example, the desired path may avoid one or more obstacles. As another example, the desired path may be a most efficient path (e.g., the shortest or fastest path, etc.) for the vehicle 10. In some embodiments, the desired path may be automatically generated by the pathing generation system 1600. In other embodiments, the operator of the pathing generation system 1600 may provide input, such as an input selecting or preferring the desired path over any other possible path.
[0452] At step 1762, a route may be generated for the vehicle 10. The route may be the same as the desired path or it may vary. For example, in some embodiments, the desired path may be generated in combination with the possible paths generated in the step 1756 (e.g., prior to any input from the input device). Subsequent to the one or more inputs from the input device, the route generated for the vehicle 10 at the step 1762 may differ from the desired path. The vehicle 10 may then travel along the route generated at the step 1762. In some embodiments, the route may be updated while the vehicle is traveling along the route based on data from one or more sensors coupled to the vehicle (e.g., the sensors 112).
[0453] At step 1764, an optimized floorplan may be generated. For example, the pathing generation system 1600 may be configured to analyze data gathered from various floorplans, possible paths, generated routes, and/or input from an operator or the input device to learn about and/or recognize inefficiencies within the production system 1601, including inefficiencies associated with the vehicle 10 traveling throughout the production system 1601. In some embodiments, the optimized floorplan may only be generated once or a small number of times in relation to the regular generation of floorplans by the pathing generation system 1600. In other words, the optimized floorplan may not be generated each and every time a floorplan is generated by the pathing generation system 1600. For example, the production system 1601 may already be operating under the most efficient possible configuration or arrangement. Step 1764 is an optional step and may or may not be performed. In some embodiments, step 1764 is performed on its own based on mapping data provided to or obtained by the vehicle 10.
6541 Coordinated Motion System
[0454] Referring generally to the figures, a system includes a first vehicle, a second vehicle coupled to the first vehicle, and a load supported by the first vehicle and the second vehicle. The system also includes one or more input devices and one or more memory devices storing instructions thereon. When executed by one or more processors, the instructions cause the one or more processors to retrieve, from the one or more memory devices, a floorplan of a production system and receive a first current position of the first vehicle and a second current position of the second vehicle, and receive, from the one or more input devices, one or more inputs. The one or more inputs include one or more of one or more locations in the production system, a footprint of the first vehicle, the second vehicle, and the load, or one or more obstacles. The instructions also cause the one or more processors to retrieve a route for the first vehicle and the second vehicle, from the first current position of the first vehicle and the second current position of the second vehicle to the one or more locations based on the one or more inputs and generate a series of coordinated motions between the first vehicle and the second vehicle based on the route and the one or more inputs.
[0455] As shown in
[0456] The load 1800 may be coupled to the vehicle 10a and/or the vehicle 10b at one or more coupling points (e.g., coupling point 1802a, coupling point 1802b, etc.). The coupling point 1802a and the coupling point 1802b may be a component on the vehicle 10a or the vehicle 10b which is configured to secure the load 1800 in a fixed or rotatable manner (e.g., a turntable), or the coupling point 1802a and the coupling point 1802b may be a mechanism external to the load 1800 and the vehicle 10a and the vehicle 10b (e.g., a strap, a bolt, etc.). In some embodiments, the coupling points 1802 may be implements such as lifting implement 50 or cart implement 60. In some embodiments, the load 1800 may be large, bulky, unwieldy, etc., and one vehicle 10 may not be sufficient to support the load 1800 alone. In some embodiments, it may be preferable to have two or more of the vehicles 10 supporting the load 1800 to increase the maneuverability of the load amongst other benefits.
[0457] The vehicle 10a and the vehicle 10b may need to move through the production system 1601 in various ways, such as by making a turn around a corner, an obstacle, a station, etc. With respect to the embodiments previously described herein relating to the operation of the vehicle 10 within the production system 1601, the operation of the vehicle 10a and the vehicle 10b may be substantially similar or may differ. For example, the use of two or more vehicles, such as the vehicle 10a and the vehicle 10b, may increase difficulty of movement within the production system 1601.
[0458] Referring now to
[0459] The coordinated motion system 1770 is configured to generate one or more paths or routes for one or more of the load 1800, the vehicle 10a, and the vehicle 10b. As shown in
[0460] In
[0461] Alternatively, in the embodiment of
[0462] As shown in
[0463] As shown in
[0464] In the embodiment of
[0465] As shown in
[0466] As shown in
[0467] Turning now to
[0468] At step 2108, the coordinated motion system 1770 may receive or retrieve, from the pathing generation system 1600, the one or more inputs from one or more of the input devices. For example, the operator may input a series of stops and/or an order of the series of stops for the vehicle 10a and the vehicle 10b at various locations throughout the production system 1601. As another example, the operator may edit the floorplan to include one or more of obstacles if the obstacle is not already accounted for in the floorplan. The one or more input devices also may communicate the footprint of the vehicle 10 to the pathing generation system 1600 at various stages of operation of the vehicle 10.
[0469] At step 2110, the pathing generation system 1600 may determine a desired path for the load 1800 and/or the vehicle 10a and the vehicle 10b, taking into account the footprint of the vehicle 10a, the vehicle 10b, and the load 1800. For example, the desired path may avoid one or more obstacles. As another example, the desired path may be a shortest path, a fastest path, or a most efficient path for the vehicle 10a and the vehicle 10b. In some embodiments, the desired path for the vehicles 10a, 10b is based on the desired path for the load 1800. The desired path may be communicated from the coordinated motion system 1770 to the pathing generation system 1600. In some embodiments, the desired path may be automatically generated by the coordinated motion system 1770 which may include the pathing generation system 1600. In other embodiments, the operator may provide input, such as an input selecting or preferring the desired path over any other possible path.
[0470] At step 2112, the coordinated motion system 1770 may receive or retrieve, from the pathing generation system 1600, a route for the vehicle 10a and the vehicle 10b. The route may be the same as the desired path or it may vary. For example, in some embodiments, the desired path may be generated in combination with the possible paths generated in the step 2106 (e.g., prior to any input from the input device). Subsequent to the one or more inputs from the input device, the route generated for the vehicle 10 at the step 2112 may differ from the desired path.
[0471] At step 2114, the coordinated motion system 1770 may generate a series of coordinated motions between the vehicle 10a and the vehicle 10b based on the route and the one or more inputs. In some embodiments, the series of coordinated motions in combination result in the load 1800 moving along the desired load path. For example, the coordinated motion system 1770 may instruct the vehicle 10a to drive in a specified manner, as previously described herein. The coordinated motion system 1770 may or may not instruct the vehicle 10b to drive in a specified manner based on the instructions provided to the vehicle 10a. Generating the series of coordinated motions between the vehicle 10a and the vehicle 10b may include changing a position of one or more of the vehicle 10a relative to the vehicle 10b or the vehicle 10b relative to the vehicle 10a along at least a portion of the route. Generating the series of coordinated motions between the vehicle 10a and the vehicle 10b may also include avoiding obstacles and maintaining a distance between the vehicle 10a and the vehicle 10b along at least a portion of the route.
Vehicle Data Sharing
[0472] Referring generally to the figures, a system includes a first vehicle, a second vehicle coupled to the first vehicle, and a load supported by the first vehicle and the second vehicle. The system also includes one or more input devices and one or more memory devices storing instructions thereon. When executed by one or more processors, the instructions cause the one or more processors to retrieve, from the one or more memory devices, a floorplan of a production system and receive a first current position of the first vehicle and a second current position of the second vehicle, and receive, from the one or more input devices, one or more inputs. The one or more inputs include one or more of one or more locations in the production system, a footprint of the first vehicle, the second vehicle, and the load, or one or more obstacles. The instructions also cause the one or more processors to retrieve a route for the first vehicle and the second vehicle, from the first current position of the first vehicle and the second current position of the second vehicle to the one or more locations based on the one or more inputs and generate a series of coordinated motions between the first vehicle and the second vehicle based on the route and the one or more inputs.
[0473] One of the first vehicle and the second vehicle also includes an audio output device and/or a visual output device to provide audible and/or visual alerts to operators within an area around the vehicles. The vehicles can provide a plurality of alerts based on a plurality of conditions. At least some of the plurality of conditions may be of the same condition type, and thereby one or more aspects of the alerts for each of the conditions of the same condition type may be the same. For example, the visual alert may be the same while audible alert may change. In this manner, the interaction between the audible alert and the visual alert may provide sufficient information even to an operator who may only be familiar with the condition type and not the condition itself.
[0474] The first vehicle and the second vehicle may also be connected by a local area network established by the first vehicle and the second vehicle. The local area network may facilitate mapping a worksite around the first vehicle and the second vehicle based on the sensors of both the first vehicle and the second vehicle.
[0475] Referring now to
[0476] One or both of the audible alerts or the visual alerts may be generated by a vehicle 10 in response to a plurality of conditions. In some embodiments, each condition of the plurality of conditions is associated with a unique combination of an audible alert and/or a visual alert. The plurality of conditions may include when a first vehicle 10 is pairing with a second vehicle 10, when a first vehicle 10 is paired with a second vehicle 10 such that movement of the first vehicle 10 and the second vehicle 10 is coordinated, a state of charge of a power source of the vehicle 10 (e.g., a battery level), a charging status of the vehicle 10 (e.g., charging, not charging, charged, etc.), if power is being provided from the vehicle to an accessory, an implement, and/or a load, a fault, the direction of travel of the vehicle 10, when carrying a load, when traversing a path, or when communicating with another vehicle 10, amongst other conditions.
[0477] In some embodiments, the plurality of conditions are each associated with one or more types of a plurality of types. The plurality of types may include pairing, communicating, vehicle status, or safety. Each type may include a subset of the plurality of conditions. For example, the condition of pairing and the condition of being paired each fall under the type of pairing. The conditions of communicating with a user controller (e.g., user device 132), communicating with a remote device (e.g., remote device 134) or communicating with another vehicle 10 each fall under the type of communicating. The conditions of being active, inactive, charged, discharged, etc. each fall under the type of status. The conditions of an error, fault, or other safety alert may fall under the type of safety. While only some conditions have times have been elaborated on herein, it should be understand that other conditions and types exist which may be included and/or determined by the vehicle 10.
[0478] In some embodiments, the subset of plurality of conditions of the same type share one or more common alert features. In some embodiments, for example, alerts for a first type of condition (e.g., pairing, communicating, status, etc.) may have the same audible alerts, but different visual alerts, or vice versa. In some embodiments, the alerts may share other common features such as, for audible alerts, a spoken word content, a loudness level, a key, a repetition rate, etc. and for visual alerts a color, an intensity, a brightness, a flashing rate, etc. For example, when pairing, a first vehicle 10 and a second vehicle 10 may each have flashing blue lights, and when paired, the first vehicle 10 and the second vehicle 10 may have solid blue lights. The common alert feature in this case is the color of the light, while the strobing frequency is varied from one condition to the other. For another example, when considering conditions of the type safety, the visual alert for each condition may be the same, such as a strobing red or yellow light, while the audible alert may vary based on the condition, such that each condition of the type safety has a different audible alert but the same visual alert. Additionally details regarding the structure of the user interface 114, the audio output device 115a, the visual output device 115b, and the operation of the same for various alerts may be found with reference to indicator 1204 in U.S. patent application Ser. No. 17/576,717, filed Jan. 14, 2022, and U.S. patent application Ser. No. 17/576,798, filed Jan. 14, 2022, the disclosures of which are incorporated herein by reference in their entirety.
[0479] Technically and beneficially, the interaction of audible and visual alerts according to known types with common alert features establishes a generic alert language to facilitate operator's understanding of a given alert even in circumstances where an operator may not understand or be able to sense the entire alert. For example, an operator may be aware that blue lights indicating a vehicle 10 is paired or pairing in some way with another vehicle, but may not know the difference between a solid blue light and a flashing blue light. However, because each alert shares a common alert feature (i.e., a blue color) the operator at least has a base line understanding of what a blue color alert may be referring to, even though the operator lacks complete knowledge.
[0480] Referring now to
[0481] In some embodiments, the vehicle 10 is connected to other vehicles 10 over a wireless connection that facilitates sharing information between the vehicles 10. This connection allows a plurality of vehicles 10 to combine the output of the respective sensors 112 when mapping a floorplan 1602. The combined output facilitates quicker and more efficient mapping but using multiple vehicles which can move and map different areas of a floorplan 1602 simultaneously. The vehicles 10 may be configured to wirelessly communicate with each other using a local area network established by the each of the vehicles 10 themselves. In some embodiments, the wireless network connecting vehicle 10 and vehicle 10 as shown in
[0482] As the vehicles 10 map a floorplan 1602, they may communicate data to each other across the local area network to establish the complete floorplan 1602 to be used by a pathing generation system 1600 as described herein.
[0483] In some embodiments, the sensors 112 are omitted, and the mapping is facilitated entirely by the external sensors 2205. In such cases, each of the vehicles 10 may be controlled by a remote device 134 (e.g., server) which is communicably coupled to the external sensors 2205 and the vehicles 10. The autonomous operation of the vehicles 10 thus relies on the mapping and sensing of the external sensors 2205. In such embodiments, the pathing generation system 1600 may be found in the remote devices 134 for controlling one or more of the vehicles 10.
Overall Manufacturing System
[0484] Referring generally to the figures, a manufacturing method includes a load-based verification of assembly of a product at each stage of production in a production system. The production system is configured to move a product through a manufacturing line to different stations using one or more vehicles. Each station may be associated with a different manufacturing or assembly process that is performed there. At each station, the build process may not be completed properly, which undesirably impacts the final product.
[0485] To counteract this a manufacturing system includes a parameter-based verification of assembly, such as load-based verification of assembly, at each stage of production to determine if assembly is completed properly. The manufacturing system includes one or more vehicles that move a product through the production line. Each vehicle includes a chassis. The chassis is coupled to one or more interfaces that support the product. The interface is coupled to a force sensor that detects the position and magnitude of mass of the product supported by that interface. The vehicle includes a controller, operatively coupled to the sensors, and trained to determine expected force sensor readings at each stage of assembly. At each station, the controller receives measured sensor readings of the current status of the product. The controller compares the measured sensor readings to the expected sensor readings. In response to the determination that measured sensor readings differ from expected sensor readings, the controller provides a notification to the user of potential reasons for the unacceptable load.
[0486] Referring to
[0487] In the example, shown in
[0488] The vehicle 2500 includes a chassis 2508. The chassis 2508 is configured to support other components of the vehicle 2500. In embodiments, which include a first vehicle 2504 and a second vehicle 2506, the first vehicle 2504 has a first chassis 2510 and the second vehicle has a second chassis 2512. By way of example, the chassis 2508, first chassis 2510, and second chassis 2512 may be the frame 12 shown in
[0489] The vehicle 2500 includes a first interface 2514 and a second interface 2516. The first interface 2514 is configured to support a first portion of the product 2502. The second interface 2516 is configured to support a second portion of the product 2502. In some embodiments, a single interface (e.g., first interface 2514, second interface 2516) can be configured to support the entire product 2502. The first interface 2514 and the second interface 2516 are coupled to the chassis 2508. The first interface 2514 is coupled to a first portion (e.g., front end, etc.) of the chassis 2508 and the second interface 2516 is coupled to a second portion (e.g., back end, etc.), laterally separated from the first portion, of the chassis 2508. In embodiments which include a first vehicle 2504 and a second vehicle 2506, the first interface 2514 is coupled to the first chassis 2510 and the second interface 2516 is coupled to the second chassis 2512. In some embodiments, the first interface 2514 and the second interface 2516 may be interchangeable (e.g., cradle 52, lifting device, lift assembly 54, driving pin 62, turning pin 64, etc.). For example, the first interface 2514 can be changed from the cradle 52 to the lift assembly 54.
[0490] The vehicle 2500 includes a first sensor 2518. The first sensor 2518 is coupled to the first interface 2514. The first sensor 2518 can be configured to provide first sensor data indicating a first measured force 2522 (e.g., normal force, weight) on the first interface 2514. In some embodiments, the first sensor 2518 can be configured to provide first sensor data indicating a force of gravity 2526 on the product 2502. In embodiments with more than one vehicle 2500, the first sensor 2518 is coupled to the first interface 2514 on the first vehicle 2504. In some embodiments, the first sensor 2518 is a force sensor (e.g., load cell, inertial measurement unit, etc.). In some embodiments, the first sensor 2518 is at least one of a current sensor, a voltage sensor, or a pressure sensor, which infer the force of the product 2502 based on a sensed value (e.g., a load on an electrical actuator, a load on a drive motor, a hydraulic pressure, etc.).
[0491] In some embodiments the first measured force 2522 can be the normal force on the first interface 2514. Additionally or alternatively, the first measured force 2522 can be the weight of the product 2502 on the first interface 2514. In such embodiments, the first sensor 2518 may communicate with other components of the manufacturing system (e.g., a controller 102, etc.) to calculate a center of gravity 2528 of the product 2502.
[0492] The vehicle 2500 includes a second sensor 2520. The second sensor 2520 is coupled to the second interface 2516. The second sensor 2520 can be configured to provide second sensor data indicating a second measured force 2524 (e.g., normal force, weight) on the second interface 2516. In some embodiments, the second sensor 2520 can be configured to provide second sensor data indicating the force of gravity 2526 on the product 2502. In embodiments with more than one vehicle 2500, the second sensor 2520 is coupled to the second interface 2516 on the second vehicle 2506. In some embodiments, the second sensor 2520 is a force sensor (e.g., load cell, inertial measurement unit, etc.). In some embodiments, the second sensor 2520 is at least one of a current sensor, a voltage sensor, or a pressure sensor, which infer the force of the product 2502 based on a sensed value (e.g., a load on an electrical actuator, a load on a drive motor, a hydraulic pressure, etc.).
[0493] In some embodiments the second measured force 2524 can be the normal force on the second interface 2516. Additionally or alternatively, the second measured force 2524 can be the weight of the product 2502 on the second interface 2516. In such embodiments, the second sensor 2520 may communicate with other components of the manufacturing system (e.g., a controller 102, etc.) to calculate the center of gravity 2528 of the product 2502.
[0494] The manufacturing system further includes a controller 102. The controller 102 is operatively coupled to the first sensor 2518 and the second sensor 2520. The controller 102 is configured to move the product 2502 from one stage of assembly to another stage of assembly (e.g., from one station 160 to another station 160). The controller 102 is configured to receive sensor data from the first sensor 2518 and the second sensor 2520 indicating a first measured force 2522 on the first interface 2514 and a second measured force 2524 on the second interface 2516. By way of example, the controller 102 may be part of the control system 100 and may include a processor 104, a memory 106, and a communication interface 108 as shown in
[0495] The controller 102 is configured to receive an indication of a current stage of assembly of the product 2502 (e.g., components that need to be added, etc.). The controller can be configured to determine an expected force (e.g., first expected force on the first interface 2514, second expected force on the second interface 2516) based on the current stage of assembly of the product 2502. In some embodiments, the indication includes the expected force for a stage of the manufacturing process. In some embodiments, the memory 106 may store first expected force data and second expected force data. In such embodiments, first expected force data is the expected force (e.g., expected normal force, expected force of gravity, etc.) of the product 2502 on the first interface 2514 and second expected force data is the expected force (e.g., expected normal force, expected force of gravity, etc.) of the product 2502 on the second interface 2516.
[0496] In some embodiments, the memory 106 may contain one or more instructions (e.g., comparative analysis, center of gravity calculations, etc.), that when executed by the processor 104, may cause the processor 104 to perform various functions (e.g., compare expected and measured values, calculate center of gravity 2528, etc.). After receiving the indication of the current stage of assembly of the product 2502, the controller 102 is configured to compare the measured force (e.g., first measured force 2522, second measured force 2524) with the expected force (first expected force, second expected force) using the instructions.
[0497] The controller 102 can be configured to perform one or more control actions in response to a difference between expected force data and measured force data (e.g., first measured force 2522 differs from first expected force, second measured force 2524 differs from second expected force, etc.). The control actions can be at least one of notifying a user, controlling an operating parameter (e.g., speed, direction of travel, acceleration of the vehicle 2500, etc.) of the vehicle 2500, the first vehicle 2504, and/or the second vehicle, controlling the operation of another vehicle 2500, controlling the operation of the production line 150, etc.,
[0498] The controller 102 can further be configured to determine if the station 160 is complete (e.g., all components are properly installed on the product 2502, etc.) or if an error has occurred (e.g., components are not properly installed, a tool is left on the product 2502, etc.). For example, the controller 102 can be configured to receive first sensor 2518 and second sensor 2520 data indicating a first measured force 2522 and a second measured force 2524, respectively. In such example, the controller 102 can compare the measured force data (e.g., first measured force 2522, second measured force 2524) to the expected force data (e.g., first expected force, second expected force, etc.) to determine if there is a difference between the expected force data and the measured force data. In response to a difference between expected force data and measured force data the controller 102 can be configured to determine that the station 160 is incomplete or an error has occurred.
[0499] The first expected force data and the second expected force data can be for a number of parameters (e.g., weight, center of gravity, time at station, etc.) and can be a range of acceptable values. Ranges of acceptable values can be provided for each station 160, and may vary from station 160 to station 160.
[0500] The controller 102 can be configured to calculate a center of gravity 2528 of the product 2502. For example, the controller 102 can be configured to perform center of gravity calculations using the first measured force 2522 (e.g., weight of the product 2502 on the first interface 2514) and the second measured force 2524 (e.g., weight of the product 2502 on the second interface 2516). The center of gravity 2528 can be configured to be a range of acceptable positions along the product 2502. If the measured center of gravity 2528 falls outside the range of acceptable center of gravity positions, the controller 102 can be configured to determine the station 160 is incomplete or an error has occurred. In response to the determination that the station 160 is incomplete, the controller 102 can perform a control action. The control action can include providing a notification to the user and/or adjusting an operating parameter of the vehicle 2500. The operating parameter is at least one of a speed, a direction of travel, or an acceleration of the vehicle 2500. In some embodiments, a station 160 is incomplete when a component is not installed on the product 2502. In some embodiments, an error has occurred when a component is installed incorrectly or in the wrong position on the product 2502, additional items (e.g., tools, other product components, etc.) are left on the product 2502, and/or a failed first sensor 2518 and/or second sensor 2520 reading.
[0501] In response to an error and/or an incomplete assembly the controller 102 can notify the user of the status of the product 2502. The notification can be visual or aural. For example, the notification may be a flashing light, or an alarm. In some embodiments, the notification includes a prediction of the cause of the error. For example, one or more parameters of the notification can be based on the outcome of the comparison between the measured value and the expected range of values for that specific parameter (e.g., weight, center of gravity 2528, etc.), and one or more other sensed values such as time at station 160. For example, in response to the comparison indicating the measured weight falls below an expected weight range and/or the time at station 160 being less than an expected time at station 160, the controller 102 can notify a user with an alarm that indicates, either through tone, color, spoken language, etc., that the product 2502 may not include the component as expected in that specific station 160. Similarly, if the measured weight falls above the expected weight, the notification may indicate that a tool was left on the vehicle 2500. In this way, the controller 102 can both detect the issue and attempt to predict the source of the issue based on the values of the measured weight and how it compares to the expected value range.
[0502] In some embodiments, the controller 102 may also control the vehicle 10, such as the controller 102 may prohibit further movement of the vehicle 10 from one station 160 to another until the measured value (e.g., weight, center of gravity) falls within the acceptable range. In some embodiments, the controller 102 may automatically control the vehicle 2500 to move out of the main product line 150, for example to a staging or waiting area, to allow the production line 150 to continue and to allow for a safe space for a user to troubleshoot the problem. Beneficially, this can allow the production line 150 to continue to run while a problem at a single station 160 is resolved. In some embodiments, in response to an input from a user, the vehicle 2500 can ignore a condition such as a measured value exceeding a range. For example, a user may input an override request and control the vehicle 2500 to the next station 160 despite, according to the vehicle sensors (e.g., the first sensor 2518, the second sensor 2520), the measured value is outside of the expected value.
[0503] Referring to
[0504] Referring to
[0505] In some embodiments, step 2532 is optional and the controller 102 is provided (e.g., by the user, etc.) the expected weight, first expected force, and/or second expected force for one or more stations 160 prior to the start of manufacturing. For example, the expected weight can be based on measured values from prior operation of the production line 150. In some embodiments, the station 160 specific data provided to the first vehicle 2504 and/or the second vehicle 2506 may include an acceptable weight or weight range and acceptable center of gravity position ranges for each station 160 of a production line 150. If a weight is outside of the acceptable weight range, then the station 160 is either incomplete or a mistake has occurred. If a weight is within the acceptable range, the first vehicle 2504 and/or the second vehicle 2506 can proceed to the next stage. Similarly, if a center of gravity 2528 is outside the acceptable range of center of gravity positions, the station 160 may be incomplete or a mistake may have occurred. If the center of gravity 2528 is within the acceptable range, then the first vehicle 2504 and/or the second vehicle 2506 can proceed to the next station 160.
[0506] The manufacturing method 2530 includes an input step 2534. The input step 2534 may include the user inputting the desired product configuration and desired current stage of assembly of the product 2502 into the controller 102. By way of example, the controller 102 may be the controller 102 shown in
[0507] In some embodiments, one or more stations 160 of the production line 150 may include an indicator (e.g., visual indicator, aural indication, transmitter, etc.) which provides an indication of the current product configuration and/or current stage of the first vehicle 2504 and/or the second vehicle 2506. For example, each station 160 can include a Bluetooth emitter configured to emit, within a predetermined area of the production line 150, a first signal indicating that the area is identified as one of the stations 160. At another different station 160, a different Bluetooth emitter may emit a second signal, different than the first signal, indicating the identity of the other station 160. This emitter can be Bluetooth, WiFi, NFC, etc.
[0508] In some embodiments, the indicator is a visual indicator that is recognized by one sensor 112 (e.g., cameras) of the first vehicle 2504 and the second vehicle 2506. In some embodiments, the indicator is a specific sound or tone which can be sensed by the sensors 112 of the first vehicle 2504 and the second vehicle 2506. In some embodiments, the indicator is a magnetic indicator that can be sensed by magnetic sensors 112 such as a Hall-effect sensors, wherein the magnetic field of each magnetic indicator is unique and identifiable, to be associated with a station 160. In some embodiments, the vehicle 10 can identify the current product configuration and/or station 160 entirely based on image processing techniques.
[0509] The manufacturing method 2530 includes a transfer step 2536. The transfer step 2536 includes transferring to the controller 102, the product configuration and desired current stage of assembly of the product 2502. In other embodiments, step 2536 includes the vehicle 2500 itself determining the product configuration and the desired current state of assembly of the product 2502 as discussed above. When the controller 102 receives and/or determines the product configuration and the desired current stage of assembly of the product 2502, the controller 102 may determine or retrieve from memory 106 the corresponding first expected force, second expected force, expected weight of each component, and the expected force of gravity 2526 at the desired station 160. Each of the first expected force, second expected force, expected weight of each component, and the expected force of gravity 2526 at the desired station 160 may be a range of acceptable values.
[0510] In some embodiments, the user device 132, user interface 114, or remote device 134 may facilitate wireless communication (e.g. through Bluetooth, Wi-Fi, radio transmission, inductive transmission of energy, etc.) to the controller 102 to transfer the product configuration and the desired current stage of assembly of the product 2502. Additionally or alternatively, the user device 132, user interface 114, or remote device 134 may facilitate wired communication (e.g. through CAN, Ethernet, communication of power, etc.) to the controller 102 to transfer the product configuration and the desired current stage of assembly of the product 2502.
[0511] The manufacturing method 2530 includes a receiving sensor data information step 2538. The receiving sensor data information step 2538 includes providing by the first sensor 2518, first sensor 2518 data indicating a first measured force 2522 on the first interface 2514 (i.e. normal force on the first interface 2514) to the controller 102 and providing by the second sensor 2520, second sensor 2520 data indicating a second measured force 2524 on the second interface 2516 (i.e. normal force on the second interface 2516) to the controller 102. In some embodiments, the receiving sensor data information step 2538 includes providing, by the first sensor 2518 and the second sensor 2520, measured force data indicating the measured force of gravity 2526 on the product 2502 and the position of the center of gravity of the product 2502.
[0512] The manufacturing method 2530 includes a comparative step 2540. The comparative step 2540 includes comparing measured force data to expected force data (e.g., first measured force data to first expected force data, second measured force data to second expected force data) and determining if the measured force data, found in the receiving sensor data information step 2538, is within the range of expected sensor data, found in the training step 2532. In some embodiments, the processor 104 compares first expected force data to first measured force 2522 data and compares second expected force data to second measured force 2524 data to determine if the measured force data differs from expected force data. Additionally, in some embodiments, the processor 104 performs a center of gravity calculation to determine the measured center of gravity 2528 of the product 2502 and compares the expected center of gravity 2528 to the measured center of gravity 2528 to determine if measured center of gravity 2528 differs from expected center of gravity 2528.
[0513] The manufacturing method 2530 includes a notify user step 2542. The notify user step 2542 includes notifying the user when the measured force data differs from the expected force data described in the comparative step 2540. If the measured force data does not differ from the expected force data a positive notification (i.e. check mark, green screen, etc.) will be used to notify the user. If the measured force data differs from the expected force data a negative notification (e.g., an X, a red screen, etc.) will be used to notify the user. In some embodiments, following the transfer of the status of the product from the controller 102 to the user device 132, the controller will provide a notification to the user describing the status of the product 2502 (e.g., the measured sensor data is outside the range of the expected sensor data). Additionally or alternatively, the controller 102 can transfer the status of the product to the user interface 114, providing a notification to the user about the status of the product 2502. Additionally or alternatively, the controller 102 can transfer the status of the product to the remote device 134, providing a notification to the user about the status of the product 2502.
[0514] In some embodiments, the notification will include predictive analysis (i.e. required components not installed, component installed in the wrong location, additional items accidentally left on vehicle 2500, etc.). In some embodiments, the notification will provide a check list of required components at each station 160. In some embodiments, the controller 102 may also perform one or more other control actions such as controlling a state or position of the vehicle (e.g., vehicle 10, first vehicle 2504, second vehicle 2506) such as inhibiting further movement or automatically moving the vehicle out of the production line, controlling the state or position of vehicles in adjacent stations 160 of the production line 150, controlling the production line 150 itself (e.g., slowing the line, speeding up the line, etc.) or other control actions to facilitate the efficient operation of the production line 150.
Reconfiguration of Vehicle Operation and Corresponding Autonomous Modes
[0515] Referring generally to the figures, one or more vehicles may be configured to operate in one of a plurality of different modes of operation, including different degrees of autonomous operation (e.g., manually controlled, partially autonomous, or fully autonomous). In some embodiments, a vehicle can be configured to switch between different modes of operation (e.g., between a mode of operation that is substantially user controlled to a mode of operation that is fully, or at least substantially, autonomous). Stated differently, in some embodiments, the vehicles may be configured to switch between different levels of autonomous operation (e.g., minimally autonomous to fully autonomous and vice versa) based a user input or information related to the operation of the one or more vehicles, including based on the feasibility of operating a vehicle autonomously in the presence of one or more different operational conditions (e.g., inclement weather, power outage, steep grades, spills, unexpected obstacles, etc.). For example, the vehicles may switch between a first mode of operation and a second mode of operation based on a match value determined from sensor data, which is indicative of one or more operational conditions and one or more operational criteria.
[0516] As described above, one or more of the vehicles 10 (e.g., one or more embodiments of the vehicle 10 shown in, and described with reference to,
[0517] The vehicles 10 switch between a first mode of operation and a second mode of operation based on sensor data indicative of one or more operational conditions and one or more operational criteria. More specifically, the vehicle may determine a mode of operation based on sensor data relevant to the operation of the vehicle 10 and/or the environment surrounding the vehicle 10, including, for example, data collected by one or more sensors (e.g., sensors 112), light sensors, traction data (e.g., sensor data indicating a quality of the terrain on which the vehicle operates), load data (sensor data indicative of a load position, load orientation, the distribution of a load including between two or more vehicles, etc.), location data, network data, energy supply and state data (e.g., of batteries 110, etc.) such as a state of charge, and the like. The sensor data may be provided by sensors 112 of the vehicle 10, or based on sensor data provided by one or more remote device 134 or other vehicles 10 communicably coupled to the vehicle 10.
[0518] For example, a vehicle 10 may initially operate in a first mode or as an autonomous mobile robot and receive sensor data from one or more sensors 112 (e.g., cameras, LIDAR, etc.) indicative of a large unexpected obstacle in the vehicle's path. The vehicle 10 may initially remain in the first mode, and continue to operate as an autonomous mobile robot and upon unsuccessfully attempting to navigate around the unexpected obstacle, or due to sensor data indicating one or more additional operational conditions (e.g., low light/visibility, unexpected location, and/or an unstable load carried by the vehicle), the vehicle 10 may change operation to operate in a second mode (e.g., as an autonomous guided vehicle or a semi-autonomous guided vehicle, as described above). In some embodiments, the vehicle 10 may operate in one of a plurality of modes such as an autonomous mode, a semi-autonomous mode, or a manual mode and transition to a different mode of the plurality of modes based a command from at least one of a user device (e.g., user device 132), user interface 114, or remote device 134.
[0519]
[0520] Although the steps are shown in
[0521] The method 2600 can, in some embodiments, include a method of operating a vehicle. In some embodiments, the method 2600 can include operating 2610 a vehicle in a first mode of operation. The vehicle 10 may include a plurality of modes of operation such as an autonomous mode, a semi-autonomous mode, and a user-guided or manual mode. In the autonomous mode, the vehicle 10 may be referred to as a self-guided vehicle or an autonomous mobile robot (AMR). In the semi-autonomous mode, the vehicle may be referred to as an automated guided vehicle (AGV). In the user-guided mode, the vehicle may be a remote-controlled vehicle. For example, in some embodiments, the method 2600 may include operating a vehicle in a first mode of operation that is fully autonomous or as an automated mobile robot, as described above, with reference to
[0522] Alternatively, or in addition, the vehicle 10 may operate in a first mode of operation that is substantially user controlled and/or that requires substantial input from a user to operate the vehicle 10, such as to steer the vehicle 10 while it is in a semi-automated guided vehicle configuration. For example, the vehicle 10 may operate in a semi-autonomous guided vehicle configuration based on the presence of one or more operating conditions.
[0523] The method 2600 can further include receiving 2620 sensor data indicative of one or more operational conditions. In some embodiments, operational conditions may include one or more conditions of the vehicles' environment that relate to the vehicle's operation. Operational conditions may include, for example, local weather, vehicle location, grade, traction, connectivity, proximity to one or more additional vehicles, tire pressure, battery levels, detected obstacles and/or obstructions, load data, light and/or visibility, sound, temperature, etc. The sensor data may be provided by the sensors 112 of the vehicle 10 or received from one or more other vehicles 10.
[0524] For example, in some embodiments, the method 2600 can receive sensor data indicative of an exceptionally steep grade based on or more orientation sensors of the vehicle 10 and may further receive sensor data indicative of a low traction environment (e.g., as traction data based on, or received from the operation of the vehicle's drivetrain).
[0525] The method 2600 can include accessing 2630 one or more operational criteria, wherein the one or more operational criteria correspond to one or more operational modes of the vehicle. The operational criteria may include one or more criteria specified for one or more different modes of operation of the vehicle, including, for example, one or more criteria that prohibit, or substantially conflict with, one or more modes of operation of the vehicle 10. For example, the operational criteria may include criteria that specify the vehicle 10 operate in a user controlled mode when a grade is above a given angle, when vehicle traction is inconsistent, or when the vehicle's load is precarious and/or difficult to maneuver safely.
[0526] Alternatively, or in addition, the one or more operational criteria may specify that a semi-autonomous and/or partially autonomous operation of the vehicle 10 may be used in the presence of certain operational conditions. For example, where the vehicle 10 has reliable connectivity to a vehicle network and/or guiding features, the vehicle may continue to operate autonomously even when a load is large, heavy, and/or costly, or the vehicle must maneuver between relatively small spaces and/or with little physical clearance.
[0527] In some embodiments, the method 2600 can include determining 2640 a match value between the sensor data (e.g., received at 2620) and the one or more operational criteria (e.g., accessed at 2630). For example, the method 2600 can include determining a match value via the controller 102 and/or the processor 104 of the vehicle. In some embodiments, determining the match value may include determining a degree of overlap and/or similarity between the operational conditions indicated by the sensor data and the one or more operational criteria accessed at 2630. For example, the method 2600 can include determining a match value for each operational condition for which sensor data has been received and for which an operational criteria may apply.
[0528] In some embodiments, the method 2600 can include determining if a user override is received at 2650. The user override can be a user input designating a mode of operation for the vehicle to operate in. For example, the user override can indicate the vehicle 10 should change from a manual mode to an autonomous mode.
[0529] In some embodiments, if a user override is not received, the method 2600 can include switching 2660 operation of the vehicle 10 from the first mode of operation to a second mode of operation based on the match value indicating a match between one or more operational criteria and the one or more operational conditions indicated by the sensor data. For example, the vehicle 10 controller 102 may change the operation of the vehicle from fully autonomous, or autonomous mobile robot operation, to a second mode of operation as a semi-autonomous guided vehicle for which steering must be controlled via user input. The vehicle may change to a SGV mode of operation based on the match value indicating the vehicle 10 lacks network connectivity and is located in an unexpected location (e.g., outside of an expected manufacturing environment and/or manufacturing station).
[0530] In some embodiments, if a user override is received at 2650, the method 2600 can include switching 2670 operation of the vehicle 10 from the first mode of operation to a second mode of operation based on the user override. For example, a user can override the vehicle and inhibit it from transitioning to an autonomous mode, and instead direct it to a manual mode. The user override otherwise direct the vehicle 10 to transition to any of the modes.
Selective Manual Operation
[0531] Referring generally to the figures, one or more vehicles may be configured to operate in one of a plurality of different modes of operation, including different degrees of autonomous operation (e.g., manually controlled, partially autonomous, or fully autonomous). In some embodiments, a vehicle can be configured to switch between different modes of operation (e.g., between a mode of operation that is substantially user controlled to a mode of operation that is fully, or at least substantially, autonomous). Stated differently, in some embodiments, the vehicles may be configured to switch between different levels of autonomous operation (e.g., minimally autonomous to fully autonomous and vice versa) based a user input or information related to the operation of the one or more vehicles, including based on the feasibility of operating a vehicle autonomously in the presence of one or more different operational conditions (e.g., inclement weather, power outage, steep grades, spills, unexpected obstacles, etc.). For example, the vehicles may switch between a first mode of operation and a second mode of operation based on a match value determined from sensor data, which is indicative of one or more operational conditions and one or more operational criteria.
[0532] The different modes of operation may work together. A manually controlled mode of operation may be used to guide a vehicle along a path. The manually-guided vehicle may leave virtual waypoints to mark the path for future semi-autonomous or autonomous navigation along the same path. While being guided, an operator may also manually identify one or more milestones along the path. The vehicle may mark the location of the milestones relative to the path for future semi-autonomous or autonomous navigation. In a semi-autonomous or autonomous mode, the vehicle may move along the path and to one or more milestones indicated on the path in response to a command or automatically. An operator may also manually identify one or more zones the vehicle is to avoid moving through. The operator may use a user device (e.g., mobile phone, camera, laser pointer, IR emitter, motion/motion-sensing controller, etc.) to indicate the outer boundaries of a zone for the vehicle through operation of the user device. An operator may also manually identify the one or more zones by placing a plurality of indicators around an outer perimeter of the zone. The indicators may include visual indicators (e.g., flags, cones, markers, QR codes, NFC tags, radio-signal emitters, etc.) which may be detected by the vehicle. A vehicle may sense the zone a single time and remember the position of the zone relative to the surrounding work environment even after the indicators are removed.
[0533] During operation in a semi-autonomous or autonomous mode, a manual override may also be provided to force the vehicle to switch to a manual operation mode. The manual override can be generated from a controller onboard on the vehicle or from an external device (e.g., remote controller, mobile phone, laptop). The device can be onsite or offsite at a remote location. When taking manual control, an operator can control of a plurality of a vehicles or a single vehicle depending on the override provided.
[0534] Referring now to
[0535] As shown in
[0536] Upon sensing the indicators 2720, the controller 102 of the vehicle 10 performs one or more actions to determine the outer perimeter of the zone 2710. The actions may depend on the type of indicators 2720 that are sensed. The controller 102 of the vehicle 10 may reference a lookup table to determine a corresponding action or sequence of actions to take for each type of indicator 2720. For example, a first type of indicators 2720 may represent a corner of a zone, as shown in the first zone 2710. The vehicle 10 may then determine that indicators 2720 of the corner type the vehicle 10 determines an outer perimeter line, shown as perimeter 2712 which is defined by the indicators 2720. The perimeter 2712 may be a continuous line formed by connecting adjacent indicators 2720 (i.e., the vertices or corners of the first zone 2710) to each other until each indicator 2720 is connected to the rest of the indicators 2720. The types of indicators 2720 may indicate the indicator 2720 is a corner, a center, a side, a height of the zone to be established, a duration of the zone to be established, etc. For the height of the zone, the indicator 2720 may indicate that the zone, such as zone 2710 should not be entered by vehicle 10 with a height greater than the height indicated by the type of indicator. For example, the type of indicator may represent a zone which begins 2 feet above the ground of the production system 150, such that vehicles 10 shorter than 2 feet may freely enter the zone, but vehicles 10 at or greater than 2 feet may not. The duration of a zone may indicate how long vehicles 10 are to avoid the zone. In some embodiments, once a zone defined by indicators 2720 is sensed by a vehicle 10, the indicators 2720 may be removed by the vehicle may maintain the zone (e.g., in its memory 106). The duration the zone may be maintained and/or avoided may be a predetermined amount of time, such as 1 hour, 1 day, or 1 week, or a predetermined number of passes by a vehicle 10, such as after passing and identify the zone once, twice, three times, etc. After the duration has elapsed, the vehicle 10 may freely enter the zone. In such a manner, the features of the zones may be customized and/or determined by the type of indicator 2720 used.
[0537] Upon determining the boundary of the first zone 2710, the vehicle 10 may automatically adjust its path, shown as path A, to avoid the first zone 2710. In some embodiments, the vehicle 10 selects a path from a plurality of possible paths. In some embodiments, the selected path may be the path with the highest average distance from the plurality of zones along the path. In some embodiments, the selected path may be the path with the lowest average distance from the plurality of zones along the path. In some embodiments, selected path may be the path that is extends adjacent or next to the least number of zones. In some embodiments, the selected path may be the path with the largest minimum distance between the vehicle 10 and one of the plurality of zones. In some embodiments, the selected path may be the shortest path that maintains a predetermined minimum distance from each of the plurality of zones. In such embodiments, the vehicle 10 may be in a semi-autonomous or autonomous mode and automatically determine the appropriate path taking into account the senses first zone 2710.
[0538] In some embodiments with only two indicators 2720, the controller 102 determines a line connecting the indicators 2720 together and the vehicle 10 will treat the line as a boundary not to be crossed. In some instances a single indicator 2720 is used, such as the third zone 2725. In such cases, the vehicle 10 establishes a zone shown as the third zone 2725 with the indicator 2720 at its center. The diameter of the third zone 2725 may be a predetermined distance from the indicator 2720. In such cases, the predetermined distance may be based on the type of indicator 2720 used to indicate the third zone 2725. In other embodiments, the predetermined distance is configured by an operator or owner of the vehicle 10. Still, in other embodiments, the vehicle 10 may be configured to determine a maximum possible distance from the indicator 2720 based on the position of the indicator 2720 relative to surrounding objects, walls, or hazards in the production system 150.
[0539] The production system 150 also includes the second zone 2715. The second zone 2715 is shown in a partially completed state as it is being defined by an operator 2705. The second zone 2715 may be defined or established by an operator, shown as operator 2705, operating the user device 132. The user device 132 may be a motion/motion-sensing controller, smartphone, tablet, laptop, camera, laser pointer, IR emitter, etc. The user device 132 may facilitate a user mapping out the zone 2715 in virtual space. By way of example, the user devices 132 may be a motion/motion-sensing controller with an accelerometer, gyroscope, and/or a magnetometer that is capable of determining its own orientation in 3D space. The user device 132 can then act as a digital marker or a wand that can be wielded by an operator such as operator 2705 to delineate the boundaries of the second zone 2715. The operator 2705 may point the user device 132 at a point of the production system 150. The path 2717 traced by the virtual end 133 of the user device 132, may represent the outer boundary of a zone. Using the user device 132, an operator such as operator 2705 may trace a line or a boundary of zone. The user device 132 is communicably coupled to the vehicle 10 and may provide the path 2717 traced by the user device 132 to the vehicle 10 as zone data for the vehicle 10 to process and place the zone in the production system 150.
[0540] By way of another example, the user device 132 may include a touch interface, a display, and a camera. The camera may image the production system 150 and the operator 2705 may provide one or more user inputs to identify the path on the image of the production system 150 displayed. The user inputs may include tracing the boundary of the second zone 2715, and/or selecting multiple points in the image of the production system 150 to be connected to form the boundary of the second zone 2715. The data from the user device (e.g., the image, the user inputs, and/or the second zone 2715) may be provided to the vehicle 10.
[0541] In some embodiments, the operator 2705 may place the vehicle 10 in a manual operating mode and control the vehicle 10 to drive around the zone to define the boundary of the zone. The path traversed by the vehicle 10 may then be stored in memory as a boundary not to be crossed.
[0542]
[0543] Although the steps are shown in
[0544] The method 2800, can, in some embodiments, include a method of operating a vehicle such as vehicle 10. The vehicle 10 may include a plurality of modes of operation such as an autonomous mode, a semi-autonomous mode, and a user-guided or manual mode. In the autonomous mode, the vehicle 10 may be referred to as a self-guided vehicle or an autonomous mobile robot (AMR). In the semi-autonomous mode, the vehicle may be referred to as an automated guided vehicle (AGV). In the user-guided mode, the vehicle may be a remote-controlled vehicle. For example, in some embodiments, the method 2800 may include at step 2810 operating a vehicle in a first mode of operation that is fully autonomous or as an automated mobile robot, as described above, with reference to
[0545] Alternatively, or in addition, at step 2810 the vehicle 10 may operate in a first mode of operation that is substantially user controlled and/or that requires substantial input from a user to operate the vehicle 10, such as to steer the vehicle 10 while it is in a semi-automated guided vehicle configuration. For example, the vehicle 10 may operate in a semi-autonomous guided vehicle configuration based on the presence of one or more operating conditions.
[0546] The method 2800 further includes at step 2820 establishing one or more zones in a workspace. The one or more zones (e.g., first zone 2710, second zone 2715, third zone 2725, etc.) may be established by an operator using a user device (e.g., user device 132) to virtually define the boundaries of the one or more zones in a workspace (e.g., production system 150) and/or by an operator placing one or more physical indicators in the zone (e.g., indicators 2720). The physical indicators may include visual markings and/or emit one or more sounds or signals to be sensed by the vehicle 10. In some embodiments, zones are established according to one or more rules based on the type of physical indicator used. There may be a plurality of types of indicators, with each type corresponding to a different function or feature of the zone. In some embodiments, rather than an operator placing the one or more physical indicators, a second vehicle 10 may place the one or more physical indicators in the workspace.
[0547] The method 2800 further includes at step 2830 receiving, at the vehicle the one or more zones. In some embodiments, where the zones are virtually defined by an operator using a user device, step 2830 includes receiving zone data from the user device 132. The zone data may include a position of the zone in the production system 150. In other embodiments, the zone data may include the user inputs, and the controller of the vehicle itself may determine the zone position in the production system 150 based on the user inputs. In some embodiments, where the zones are defined by physical indicators (e.g., indicators 2720) step 2830 includes using one or more sensors of the vehicle (e.g., sensors 112) to detect the physical indicators in the workspace. Upon detecting the physical indicators, the vehicle may then determine the boundary of the zone defined by the physical indicators, and thereby receive at the vehicle the one or more zones.
[0548] The method 2800 further includes at step 2840 operating the vehicle in the workspace to avoid the one or more zones. In step 2840 the vehicle may be operated in a manual mode, a semi-autonomous mode, or an autonomous mode. In a semi-autonomous or autonomous mode, the vehicle may determine a path to an endpoint that avoids each of the one or more zones in the work space. The path may be a selected path from a plurality of possible paths. The vehicle may determine the selected path based on one or more characteristics of the plurality of possible paths such as length, duration to traverse, minimum distance to a zone, maximum average distance to a zone, number of adjacent zones along the path, etc. The vehicle may then automatically traverse the production system 150 along a path that avoids the one or more zones. In some embodiments, in zones indicated by physical indicators (e.g., the indicators 2720) once the vehicle 10 has determined the zone defined by the physical indicators, even if the physical indicators are removed, the vehicle 10 can remember the zone and continue to avoid the zone. In some embodiments, any zones received or sensed by a first vehicle may be provided to a second vehicle, for the second vehicle to receive and avoid in a manner similar to the first vehicle. Thus, a zone sensed by a first vehicle may be provided to and avoided by a second vehicle. In some embodiments, each of a plurality of vehicles sense only a part of a zone, and in communicating each of the sensed parts to each other, the plurality of vehicles thereby sense the entire zone, and each vehicle can thereafter automatically avoid the sensed zone.
[0549]
[0550] Although the steps are shown in
[0551] The method 2900, can, in some embodiments, include at step 2910 a method of operating a vehicle such as vehicle 10 in a manual mode of operation. In the manual or user-guided mode, the vehicle may be a remote-controlled vehicle.
[0552] The method 2900 further includes at step 2920 receiving one or more waypoints. The vehicle 10 may receive a user input (e.g., via the user interface 114, the user device 132, the remote device 134, etc.) indicating the location of a waypoint. The location of the waypoint may be the location of the vehicle 10 at the time the user input is received. In some embodiments, the waypoint also includes a time series of the speed of the vehicle recorded since the last waypoint. In other embodiments, the vehicle 10 automatically determines waypoints based on a predetermined duration of time elapsing. For example, a vehicle may set waypoints of its current location every second, every 5 seconds, every minute, etc. In some embodiments, the vehicle determines a waypoint at each moment the vehicle changes its direction of travel. As the vehicle 10 is manually controlled in the workspace such as the production system 150, the vehicle may receive a plurality of waypoints.
[0553] The method 2900 further includes at step 2930 determining a path based on the plurality of waypoints. The plurality of waypoints may define a path of the vehicle 10 by connecting each adjacent (i.e., in time or in space) waypoint to the next consecutively. In some embodiments, the plurality of waypoints define only a portion of a path of the vehicle 10 as it has been under manual control. The portion of the total traversed path as indicated by the waypoints may be saved as a discrete path separate and apart from the total traversed path.
[0554] The method 2900 further includes at step 2940 operating the vehicle in a second mode of operation to follow the path. The vehicle 10 may be operable in plurality of modes of operation. While the vehicle 10 may learn the path and obtain the waypoints in a manual mode of operation (i.e., while controlled by an operator) when the vehicle 10 is in a semi-autonomous or autonomous mode, the vehicle 10 may traverse the path as indicated by the plurality of waypoints automatically. In some embodiments, the vehicle 10 may proceed along the path at the same speed as when in the manual mode. Still in other embodiments the vehicle 10 may follow the path at a predetermined speed which may be less than or greater than the speed the vehicle 10 traversed the path in the manual mode.
[0555] As utilized herein with respect to numerical ranges, the terms approximately. about. substantially. and similar terms generally mean+/10% of the disclosed values. When the terms approximately. about. substantially. and similar terms are applied to a structural feature (e.g., to describe its shape, size, orientation, direction, etc.), these terms are meant to cover minor variations in structure that may result from, for example, the manufacturing or assembly process and are intended to have a broad meaning in harmony with the common and accepted usage by those of ordinary skill in the art to which the subject matter of this disclosure pertains. Accordingly, these terms should be interpreted as indicating that insubstantial or inconsequential modifications or alterations of the subject matter described and claimed are considered to be within the scope of the disclosure as recited in the appended claims.
[0556] It should be noted that the term exemplary and variations thereof, as used herein to describe various embodiments, are intended to indicate that such embodiments are possible examples, representations, or illustrations of possible embodiments (and such terms are not intended to connote that such embodiments are necessarily extraordinary or superlative examples).
[0557] The term coupled and variations thereof, as used herein, means the joining of two members directly or indirectly to one another. Such joining may be stationary (e.g., permanent or fixed) or moveable (e.g., removable or releasable). Such joining may be achieved with the two members coupled directly to each other, with the two members coupled to each other using a separate intervening member and any additional intermediate members coupled with one another, or with the two members coupled to each other using an intervening member that is integrally formed as a single unitary body with one of the two members. If coupled or variations thereof are modified by an additional term (e.g., directly coupled), the generic definition of coupled provided above is modified by the plain language meaning of the additional term (e.g., directly coupled means the joining of two members without any separate intervening member), resulting in a narrower definition than the generic definition of coupled provided above. Such coupling may be mechanical, electrical, or fluidic.
[0558] References herein to the positions of elements (e.g., top. bottom. above. below) are merely used to describe the orientation of various elements in the FIGURES. It should be noted that the orientation of various elements may differ according to other exemplary embodiments, and that such variations are intended to be encompassed by the present disclosure.
[0559] The hardware and data processing components used to implement the various processes, operations, illustrative logics, logical blocks, modules and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or, any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some embodiments, particular processes and methods may be performed by circuitry that is specific to a given function. The memory (e.g., memory, memory unit, storage device) may include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage) for storing data and/or computer code for completing or facilitating the various processes, layers and modules described in the present disclosure. The memory may be or include volatile memory or non-volatile memory, and may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. According to an exemplary embodiment, the memory is communicably connected to the processor via a processing circuit and includes computer code for executing (e.g., by the processing circuit or the processor) the one or more processes described herein.
[0560] The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
[0561] Although the figures and description may illustrate a specific order of method steps, the order of such steps may differ from what is depicted and described, unless specified differently above. Also, two or more steps may be performed concurrently or with partial concurrence, unless specified differently above. Such variation may depend, for example, on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations of the described methods could be accomplished with standard programming techniques with rule-based logic and other logic to accomplish the various connection steps, processing steps, comparison steps, and decision steps.
[0562] It is important to note that the construction and arrangement of the vehicle 10 and the production system as shown in the various exemplary embodiments is illustrative only. Additionally, any element disclosed in one embodiment may be incorporated or utilized with any other embodiment disclosed herein. For example, the first drive module 210 of the exemplary embodiment shown in at least