Embodiments provided herein generally relate to multimode vehicular navigation control, and particularly to systems and methods for providing a plurality of functional modes and control modes to a vehicle to enhance vehicle performance.
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 the products should be moved. While the vehicle operators may be capable of sufficiently navigating the vehicle to perform the desired tasks, the vehicle operators represent a significant cost to moving goods through a warehouse. As such, many current solutions provide semi-automated and/or fully automated operation of the vehicle. While such operation changes can provide different controls for the vehicle, oftentimes, automatic operation of the vehicle may still be difficult.
Included are embodiments for multimode vehicular navigation control. Some embodiments include a vehicle that has a memory component and a vehicle control module (VCM), where the VCM includes a controller. Additionally, the memory component may store functional modes of operation and control modes of operation, each of the control modes of operation being associated with a mechanism for controlling the vehicle, and each of the functional modes of operation being associated with a desired function of the vehicle. In some embodiments the VCM receives control commands from a system operator and implements the control commands, utilizing the controller. In some embodiments, at least one of the control modes of operation is configured for automatic control of the vehicle and at least one of the control modes of operation is a torque control mode for providing a power signal directly to a vehicle motor, without utilization of the controller.
Also included are embodiments of a method for multimode vehicular navigation control. The method may include receiving an automatic command at a navigation control module (NCM), determining a functional mode command and a control mode command, and determining a type of functional mode associated with the functional mode command. Some embodiments include determining a type of control mode associated with the control mode command, sending a signal from the NCM to a vehicle control module (VCM) on the vehicle that identifies a control operation, and activating a motor of the vehicle, based on the type of functional mode and the type of control mode.
Also included are embodiments of a vehicle. In some embodiments, the vehicle includes a memory component and a vehicle control module (VCM), which includes a controller. In some embodiments, the memory component stores functional modes of operation and control modes of operation, where each of the control modes of operation is configured for controlling the vehicle, and each of the functional modes of operation defines a function of operation of the vehicle. In some embodiments, at least one of the control modes of operation is configured for automatic control of the vehicle and at least one of the control modes of operation is a torque control mode for providing a power signal directly to a vehicle motor, without utilization of the controller. In some embodiments, at least one of the control modes of operation utilizes the VCM and controller for controlling the vehicle.
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 operate in automatic mode and may receive automatic control commands to implement an automatic control function. Thus, the vehicle 106 may perform the desired tasks without the assistance of a human operator. As such, the vehicle 106 may receive one more locations (or a predetermined route) from the navigation system 102. 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 (such as address D212), and/or a route for reaching the address D212. Depending on the information received, the vehicle 106 may calculate a route to the predetermined destination 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 includes 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.
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 and optimal traction and maintaining traction via a traction control module (TCM) 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 via a steering control module (SCM). 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 the accessories of the vehicle 106, such as via a hydraulic module. 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 the VCM 112 may communicate with the NCM 114 to coordinate the various conditions of manual operation and automatic operation of the vehicle 106. As such, Table 1 below represents an example of data that may be sent from the VCM 112 to the NCM 114, depending on the type of VCM being utilized.
As illustrated in Table 1, the VCM 112 may communicate vehicle data directly with NCM 114 via the navigation control interface 116 (
Similarly, bytes 3 and 4 may be utilized for a vehicle status. As an example, bit 0 may be utilized for a state of the MSS 302 (manual/auto). Bit 1 may be utilized to identify a brake switch state of BRS1 (on/off). Bit 2 may be utilized to identify the ED1 contactor state (open/closed). Bit 3 may be utilized to identify a state of the manual contactor 305. Bits 4-7 may be utilized for up to 15 different error codes. Similarly, byte 4 is utilized for identifying a functional mode type, such as a traction mode, steering mode, hoist mode, and accessory mode. Byte 5 may be used as a freshness counter, while bytes 6 and 7 may be utilized to identify the load weight on the fork.
Similarly Table 2 represents data that may be sent from the NCM 114 to the VCM 112, depending on the particular type of NCM 114.
As illustrated in Tables 1 and 2, the VCM 112 may send the NCM 114 messages regarding the particular functional mode that may be used in Byte 4. Specifically, bits 8 and 9 are reserved for traction mode (using traction logic 344a); bits 10 and 11 are reserved for steer mode (using steering logic 344b); bits 12 and 13 are hoist mode (using hoist logic 344c), and bits 14 and 15 are reserved for accessory mode (using accessory logic 344d). As illustrated in Table 3, when the vehicle 106 is in traction mode, steer mode, hoist mode, or accessory mode, a selection may be made regarding the control mode to be utilized. As an example, speed control with default PI gains may be utilized when the vehicle 106 is being automatically controlled by the NCM 114. While the NCM 114 is controlling operation of the vehicle 106, the speed control with default PI gains may be utilized with a speed parameter to control the responsiveness of the vehicle 106. As such, a system administrator (or other third party) may choose to use the PI values which were used to tune the vehicle 106 for manual operation. The speed control with adjustable PI gains is similar, except that the PI gains are available to be dynamically adjusted by the system user or system administrator, depending on the particular action that the vehicle 106 is performing. As an example, the vehicle 106 may determine a weight of the current load on the vehicle 106. If the vehicle 106 is carrying a load that meets a predetermined weight threshold, the vehicle 106 may send a signal to the navigation system 102 (and/or NCM 114). The navigation system 102 (and/or NCM 114) may then alter the PI gains to provide a tighter response to commands.
Additionally included is the torque control mode. More specifically, while the other control modes are configured for sending a speed control to a controller, such as proportional-integral-derivative (PID) controller, a proportional-integral (PI) controller, a fuzzy controller, an H-infinity controller, and/or other similar controllers, which sends a control command and/or a power signal to a motor (as with the speed controls described above), the torque control mode utilizes the TCM, which may be configured as a power module to utilize a torque command and provide a power signal directly to the motor without utilization of the controller residing in the VCM 112. Thus, the torque control mode may provide the system user with more overall control of the vehicle 106 in automatic mode. However, this may require a greater level of competency on the part of the AGV system integrator to configure the vehicle 106. The position control mode may utilize a position parameter and provide position commands to the VCM 112, which shifts the burden from the NCM 114 to the VCM 112 to accurately control the position of the vehicle 106
As also illustrated in Table 3, each of the functional modes (traction, steering, hoist, and accessory) may be utilized for any of a plurality of different control modes (speed control with default PI values, speed control with adjustable PI values, torque control, and position control). Specifically, if the vehicle 106 is operating in traction mode, the traction logic 344a may be utilized for providing traction control of the vehicle 106. If the vehicle 106 is operating in steer mode, the steering logic 344b may be utilized for providing control parameters for steering of the vehicle 106. In hoist mode, the hoist logic 344c may be utilized to provide control parameters with regard to hoisting the fork of the vehicle 106. In accessory mode, the accessory logic 344d may be utilized for controlling one or more accessories of the vehicle 106. Each of these control modes may be used with any of the functional modes depicted in Table 3.
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/052809 (CRO 0490 WO), filed Aug. 29, 2012, which international application designates the United States and claims the benefit of U.S. Provisional Application Ser. No. 61/528,499 (CRO 0490 MA) 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 |
7932827 | Chand et al. | Apr 2011 | B2 |
8060400 | Wellman | Nov 2011 | B2 |
8179286 | Faus et al. | May 2012 | B2 |
8239251 | Wellman | Aug 2012 | B2 |
8239252 | Wellman | Aug 2012 | B2 |
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 |
20110281562 | Videtich | Nov 2011 | A1 |
20120022761 | Matsuda | Jan 2012 | A1 |
20120065820 | Morris | Mar 2012 | A1 |
20120323432 | Wong et al. | Dec 2012 | A1 |
20140209406 | Wetterer et al. | Jul 2014 | A1 |
Number | Date | Country |
---|---|---|
101939248 | Jan 2011 | CN |
Entry |
---|
Notice of Allowance for U.S. Appl. No. 13/626,400 dated Jan. 8, 2014. |
Search Report and Written Opinion as it relates to PCT/US2012/052820 mailed Jan. 22, 2013. |
Final Office Action dated Sep. 23, 2013 for U.S. Appl. No. 13/626,400, filed Sep. 25, 2012. |
Office Action dated May 22, 2013 for U.S. Appl. No. 13/626,385, filed Sep. 25, 2012. |
Office Action dated Mar. 27, 2013 for U.S. Appl. No. 13/626,400, filed Sep. 25, 2012. |
Patent Examination Report pertaining to Australian Patent Application No. 2012302054, dated Jun. 10, 2014. |
Communication pursuant to Rules 161(1) and 162 EPC pertaining to European Patent Application No. 12770315.5 dated May 2, 2014. |
Office Action dated Jul. 8, 2014 pertaining to U.S. Appl. No. 14/208,852. |
Patent Examination Report No. 1 dated Jun. 20, 2014 pertaining to Australian Patent Application No. 2012302046. |
International Search Report and Written Opinion pertaining to PCT/US2012/052837, dated Nov. 15, 2012. |
Search Report and Written Opinion as it relates to PCT/US2012/052809 mailed Dec. 19, 2012. |
Office Action dated Jun. 25, 2015 pertaining to Chinese Patent Application No. 201280042137.2. |
Office Action dated Sep. 1, 2015 pertaining to Chinese Patent Application No. 201280042687.4. |
Office Action dated Feb. 19, 2016 pertaining to Chinese Patent Application No. 201280042137.2. |
Number | Date | Country | |
---|---|---|---|
20130054052 A1 | Feb 2013 | US |
Number | Date | Country | |
---|---|---|---|
61528499 | Aug 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | PCT/US2012/052809 | Aug 2012 | US |
Child | 13626396 | US |