Embodiments provided herein generally relate to vehicular control limits, and particularly to systems and methods for providing a vehicle control limits for a vehicle under automatic operation mode.
Many warehouse environments utilize one or more forklifts and/or other vehicles for moving products into, out of, and within the warehouse. Accordingly, many current solutions utilize a vehicle operator to determine which products need to be moved and to where those products will be moved. While the vehicle operators may be capable of sufficiently navigating the vehicle to perform the desired tasks, oftentimes, vehicle operators make mistakes, take inefficient routes, and/or otherwise slow the process. As such, many current solutions provide semi-automated and/or fully automated operation of the vehicle. While semi-automated and fully automated operation may provide additional options, oftentimes, system failures arise due to miscommunication between a navigation system and a vehicle control system.
Included are embodiments for providing vehicle control limits. One embodiment of a system includes a navigation system and a vehicle that includes a memory component that stores a program. Embodiments of the system are configured to receive an indication for automatic control of the vehicle, receive a route for the vehicle to reach a destination for completing a work order from the navigation system, and determine a vehicle limit, wherein the vehicle limit is based on a current state of the vehicle. Some embodiments are configured to communicate the vehicle limit from a vehicle control module (VCM) to a navigation control module (NCM), determine, via the NCM, an automatic command based on the destination and the vehicle limit and send the automatic command to a motor of the vehicle.
Also included are embodiments of a method. Some embodiments of the method include receiving a work order, the work order related to movement of load to a three-dimensional destination, determining a route for a vehicle to reach the three-dimensional destination for completing the work order, and determining a vehicle limit, wherein the vehicle limit is based on a current state of the vehicle. Some embodiments of the method include determining an automatic command based on the three-dimensional destination and the vehicle limit and sending the automatic command to the vehicle.
Also included are embodiments of a vehicle. Some embodiments of the vehicle include a memory component that stores a program that, when executed by a processor, causes the vehicle to receive an indication for automatic control of a vehicle, receive a route to reach a destination, and determine a vehicle limit of the vehicle, wherein the vehicle limit is based on a current state of the vehicle. In some embodiments, the program causes the vehicle to communicate the vehicle limit from a vehicle control module (VCM) to a navigation control module (NCM) and utilize the NCM to navigate the vehicle to the destination, while adhering to the vehicle limit.
The embodiments set forth in the drawings are illustrative and exemplary in nature and not intended to limit the subject matter defined by the claims. The following detailed description of the illustrative embodiments can be understood when read in conjunction with the following drawings, where like structure is indicated with like reference numerals and in which:
Also included is the remote computing device 104. The remote computing device 104 may also be configured as a server or other computing device and may be configured to provide the navigation system 102 with the work orders, and/or other information. In some embodiments, the remote computing device 104 may be located on the same premises as the navigation system 102, while in some embodiments the remote computing device 104 may be located remotely from the navigation system 102. Similarly, depending on the particular embodiment, the remote computing device 104 may be configured to service one or more different environments and communicate with one or more different navigation systems.
If an automatic command has been sent to the vehicle 106, the vehicle 106 may determine a vehicle condition and operate in automatic mode. Thus, the vehicle 106 may implement automatic control from the NCM 114, the navigation system 102, navigation system operator, vehicle operator, and/or other external source by determining an efficient operation of the vehicle 106 to perform the task and sending a control command based on the efficient operation, vehicle condition and desired task. With this information, the vehicle 106 may travel to a desired location, perform the desired task, and then proceed to the next location.
As an example, if the vehicle 106 is currently operating in automatic mode, the vehicle 106 may receive a task, a predetermined destination (address D212), and/or a route for reaching the predetermined destination. Depending on the information received, the vehicle 106 may calculate a route to the predetermined location at the address D212 and may then perform the task. In this particular example, the task requests the vehicle 106 to pick up the product located at the address D212. From the current location of the vehicle 106, the vehicle 106 may then use sensors and mapping data to navigate according to the determined path. In some embodiments, the vehicle 106 may include a light sensor. The light sensor may determine the relative position of the vehicle 106 with regard to the overhead lighting fixtures. Based on this information, and/or other information (such as laser sensor information, odometer readings, etc.), the vehicle 106 (and/or the navigation system 102) may ensure that the vehicle 106 is on the correct path.
As the vehicle 106 is operated in automatic mode, the vehicle may receive one or more control signals from the NCM 114 to the VCM 112. To prevent the NCM 114 from sending a command to the VCM 112 that violates a predetermined vehicle limit, the VCM 112 and the NCM 114 may communicate vehicle limit data. Specifically, based on a determined weight of a load, height of the fork, and/or other parameters, the vehicle 106 may have an acceleration limit, by which the vehicle 106 may not accelerate beyond a predetermined rate. Similarly, the vehicle 106 may have a fork height limit, a hoist acceleration limit, a hoist speed limit, etc. a steering limit may also be imposed on the vehicle. If the vehicle 106 includes one or more accessories, the vehicle may impose an accessory lower limit, an accessory speed limit, an accessory upper limit, and/or other limits.
While these limits may be easily implemented when the vehicle 106 operates in manual mode, oftentimes automatic mode may send a command for an action that is not permitted. Accordingly, the VCM 112 may communicate limit data with the NCM 114 to prevent confusion within the vehicle 106.
The mapping data 338b may include information for the layout of the environment, as illustrated in
Additionally, the memory component 140 may store operating logic 342, traction logic 344a, steering logic 344b, hoist logic 344c, and accessory logic 344d. The operating logic 342 may include an operating system and/or other software for managing components of the VCM 112. The traction logic 344a may be configured with one or more algorithms and parameters for facilitating optimal traction control for the vehicle 106. The steering logic 344b may be configured with one or more algorithms and parameters for facilitating optimal steering control of the vehicle 106. The hoist logic 344c may include one or more algorithms and parameters for facilitating optimal hoist control of the vehicle 106. The accessory logic 344d may include one or more algorithms and parameters for facilitating operation of accessories of the vehicle 106. A local communication interface 346 is also included in
The processor 330 may include any processing component operable to receive and execute instructions (such as from the data storage component 336 and/or the memory component 140). The input/output hardware 332 may include and/or be configured to interface with a monitor, positioning system, keyboard, touch screen, mouse, printer, image capture device, microphone, speaker, gyroscope, compass, and/or other device for receiving, sending, and/or presenting data. The network interface hardware 334 may include and/or be configured for communicating with any wired or wireless networking hardware, including an antenna, a modem, LAN port, wireless fidelity (Wi-Fi) card, WiMax card, mobile communications hardware, and/or other hardware for communicating with other networks and/or devices. From this connection, communication may be facilitated between the VCM 112 and other computing devices.
It should be understood that the components illustrated in
It should be understood that while the graphs 400, 500 of
As illustrated, Table 1 identifies traction data that may be sent from the VCM 112 to the NCM 114 via the navigation control interface. Specifically, the purpose of the message in Table 1 is traction feedback and vehicle traction limits. While Table 1 indicates that the data is sent as an 8 byte message, this is merely an example. Regardless, Table 1 illustrates that byte 0 and byte 1 are utilized for traction speed feedback. Bytes 2 and 3 may be utilized for identifying a traction speed limit. Bytes 4 and 5 may be utilized to identify a traction acceleration force limit. Bytes 6 and 7 may be utilized to identify a traction deceleration force limit.
Specifically, the traction speed feedback of bytes 0 and 1 may be communicated from the VCM 112 to the NCM 114 to identify a current speed and/or traction state that the vehicle 106 is experiencing. Additionally, the vehicle 106 may be subject to one or more vehicle limits that are imposed. The vehicle limits may include a speed limit, an acceleration limit, and/or a deceleration limit.
Table 2 includes steering data that is sent from the VCM 112 to the NCM 114 via the navigation control interface. Specifically, bytes 0 and 1 may be utilized to provide a wheel angle feedback (current wheel angle) of the vehicle. Bytes 2 and 3 may be utilized to identify a counterclockwise maximum wheel angle. Bytes 4 and 5 may be utilized to identify a clockwise maximum wheel angle. Bytes 6 and 7 may be utilized to identify a wheel angle rate limit of rotation.
Table 3 includes hoist data that may be communicated by the VCM 112 to the NCM 114 via the navigation control interface. Specifically, the data provided in this message reports information regarding the current state of the fork. Accordingly, bytes 0 and 1 may be utilized to identify the fork height feedback (current fork height) of the vehicle 106. Bytes 2 and 3 may be utilized to identify a fork hoist speed limit of the vehicle 106. Bytes 4 and 5 may be utilized to identify a hoist acceleration limit of the fork. Bytes 6 and 7 may be utilized to identify a hoist height limit of the fork. Additionally, other data may be provided to the NCM 114, such as current load weight, current vehicle speed, etc. This other data may be provided within one of the data communications depicted in Tables 1-4 and/or via other data messages.
Table 4 includes vehicle accessory data that may be communicated by the VCM 112 to the NCM 114 via the navigation control interface. Specifically, bytes 0 and 1 may be utilized to identify an accessory position of an accessory on the vehicle 106. Bytes 2 and 3 may be utilized to identify an accessory upper limit of the vehicle 106. Bytes 4 and 5 may be utilized to identify an accessory lower limit. Bytes 6 and 7 may be utilized to identify an accessory speed limit.
It should be understood that while only one accessory is depicted in Table 4, similar data may be provided for other accessories on the vehicle 106. Similarly, based on the functionality of the accessories, the data in Table 4 may change for each of accessory to which a limit applies.
In Tables 1-4 above, communication between the VCM 112 may indicate one or more limits that are placed on the vehicle 106. Specifically, when operating in manual mode, the vehicle 106 may be subject to the limits stored in the data storage component 336, discussed above. However, when the vehicle 106 is operating in automatic mode, the navigation system 102 and/or the NCM 114 may not be aware of the limits on the vehicle 106. Thus, when the navigation system 102 and/or the NCM 114 provide a speed (or other) command to the VCM 112, the vehicle 106 may not be able to provide the requested performance due to the limits. As such, the information in Tables 1-4 may include limit data on the vehicle 106. The limit data may include a plurality of limits, such as depicted in
While particular embodiments have been illustrated and described herein, it should be understood that various other changes and modifications may be made without departing from the spirit and scope of the claimed subject matter. Moreover, although various aspects of the claimed subject matter have been described herein, such aspects need not be utilized in combination. It is therefore intended that the appended claims cover all such changes and modifications that are within the scope of the claimed subject matter.
The present application is filed under 35 U.S.C. 111(a) as a continuation of International Patent Application No. PCT/US12/052,837, filed Aug. 29, 2012, which international application designates the United States and claims the benefit of U.S. Provisional Application Ser. No. 61/528,494 filed Aug. 29, 2011.
Number | Name | Date | Kind |
---|---|---|---|
3567048 | Whitham | Mar 1971 | A |
3942088 | Yosioka et al. | Mar 1976 | A |
4040500 | Blakeslee | Aug 1977 | A |
4077486 | Blakeslee et al. | Mar 1978 | A |
4083422 | Blakeslee et al. | Apr 1978 | A |
4279487 | Baker et al. | Jul 1981 | A |
4319820 | Ostrowski et al. | Mar 1982 | A |
4744408 | Pearson et al. | May 1988 | A |
5068790 | Wellman | Nov 1991 | A |
5184122 | Decious et al. | Feb 1993 | A |
5213548 | Colbert et al. | May 1993 | A |
5401223 | White et al. | Mar 1995 | A |
5557519 | Morita | Sep 1996 | A |
5625558 | Togai et al. | Apr 1997 | A |
5726890 | Takamoto et al. | Mar 1998 | A |
5778327 | Simmons et al. | Jul 1998 | A |
5778853 | Saito | Jul 1998 | A |
5795264 | Steeby et al. | Aug 1998 | A |
5938710 | Lanza et al. | Aug 1999 | A |
5938711 | Steeby et al. | Aug 1999 | A |
5995001 | Wellman et al. | Nov 1999 | A |
5995884 | Allen et al. | Nov 1999 | A |
6050359 | Mouri et al. | Apr 2000 | A |
6220219 | Wadas et al. | Apr 2001 | B1 |
6317637 | Limroth | Nov 2001 | B1 |
6414594 | Guerlain | Jul 2002 | B1 |
6445984 | Kellogg | Sep 2002 | B1 |
6553302 | Goodnight et al. | Apr 2003 | B2 |
6591172 | Oda et al. | Jul 2003 | B2 |
6643578 | Levine | Nov 2003 | B2 |
6781516 | Reynard et al. | Aug 2004 | B2 |
6789008 | Kato et al. | Sep 2004 | B2 |
6813557 | Schmidt et al. | Nov 2004 | B2 |
6853877 | Slater et al. | Feb 2005 | B1 |
6931958 | Takeda | Aug 2005 | B2 |
6995688 | Reynolds | Feb 2006 | B2 |
7099745 | Ebert | Aug 2006 | B2 |
7344037 | Zakula, Sr. et al. | Mar 2008 | B1 |
7366600 | Osaki et al. | Apr 2008 | B2 |
7444193 | Cutler | Oct 2008 | B2 |
7634332 | Williams et al. | Dec 2009 | B2 |
7739006 | Gillula | Jun 2010 | B2 |
7865277 | Larson et al. | Jan 2011 | B1 |
8249910 | Wellman et al. | Aug 2012 | B2 |
20030154319 | Araki et al. | Aug 2003 | A1 |
20040193363 | Schmidt et al. | Sep 2004 | A1 |
20050075784 | Gray et al. | Apr 2005 | A1 |
20050131645 | Panopoulos | Jun 2005 | A1 |
20050187752 | Colby et al. | Aug 2005 | A1 |
20050246078 | Vercammen | Nov 2005 | A1 |
20060064216 | Palmer | Mar 2006 | A1 |
20060089765 | Pack et al. | Apr 2006 | A1 |
20070158128 | Gratz et al. | Jul 2007 | A1 |
20070293989 | Norris | Dec 2007 | A1 |
20080114533 | Weiss et al. | May 2008 | A1 |
20080245598 | Gratz et al. | Oct 2008 | A1 |
20090222160 | Morselli et al. | Sep 2009 | A1 |
20090271058 | Chilson | Oct 2009 | A1 |
20090287406 | Ohi | Nov 2009 | A1 |
20090288893 | Wyall et al. | Nov 2009 | A1 |
20100084207 | Wyall | Apr 2010 | A1 |
20100161136 | Takeshita et al. | Jun 2010 | A1 |
20110071718 | Norris et al. | Mar 2011 | A1 |
20110098890 | Lee et al. | Apr 2011 | A1 |
20110251701 | Jung | Oct 2011 | A1 |
20120022761 | Matsuda | Jan 2012 | A1 |
20120065820 | Morris | Mar 2012 | A1 |
20120323432 | Wong et al. | Dec 2012 | A1 |
Entry |
---|
Search Report and Written Opinion as it relates to PCT/US2012/052809 mailed Dec. 19, 2012. |
Search Report and Written Opinion as it relates to PCT/US2012/052820 mailed Jan. 22, 2013. |
International Search Report and Written Opinion pertaining to PCTUS/2012/052837, dated Nov. 15, 2012. |
Office Action dated May 22, 2013 for U.S. Appl. No. 13/626,385, filed Sep. 25, 2012. |
Office Action dated Mar. 22, 2013 for U.S. Appl. No. 13/626,396 filed Sep. 25, 2012. |
Final Office Action dated Oct. 16, 2013 for U.S. Appl. No. 13/626,396, filed Sep. 25, 2012. |
Number | Date | Country | |
---|---|---|---|
20130054077 A1 | Feb 2013 | US |
Number | Date | Country | |
---|---|---|---|
61528494 | Aug 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | PCT/US2012/052837 | Aug 2012 | US |
Child | 13626400 | US |