Method and system for testing a remote control device

Abstract

Testing the operating characteristics of a remote control device (32) associated with a materials handling vehicle can include waiting to receive a first input indicating that a first button of the remote control device (32) has been pressed, where the first button includes a travel button (197A) of the remote control device (32). The testing can also include, after receiving the first input, waiting to receive a second input indicating that at least a second button (197B-C) of the remote control device (32) has been pressed, where the second button (197B-C) is associated with a first auxiliary vehicle function. The testing further includes determining whether a predetermined button press sequence is successful based at least in part on receiving or not receiving the first input and the second input; and optionally driving a display on the vehicle to provide a visual indication based on the determination of whether the button press sequence was successful or unsuccessful.

Description

BACKGROUND OF THE INVENTION

[0001] Materials handling vehicles are commonly used for order picking in warehouses and distribution centers. Such vehicles typically include a power unit and a load handling assembly, which may include load-carrying forks. The vehicle also has a control structure for controlling the operation and movement of the vehicle.

[0002] In a typical order picking operation, an operator fills an order from available inventory items located in storage areas provided along one or more aisles of a warehouse or distribution center. The operator drives the vehicle between respective pick locations of the item(s) to be picked. The operator may drive the vehicle either by using the control structure on the vehicle or via a wireless remote control device associated with the vehicle, such as the remote control device disclosed in co-owned U.S. Patent No. 9,082,293, the entire disclosure of which is incorporated herein by reference. SUMMARY OF THE INVENTION

[0003] According to a first aspect, there is provided a method for testing operational characteristics of a remote control device associated with a materials handling vehicle, the method comprising: waiting, by a processor, for a first input indicating that a first button of the remote control device has been pressed, wherein the first button includes a travel button of the remote control device; waiting, by the processor, for a second input indicating that at least a second button of the remote control device has been pressed after receiving the first input, wherein the second button is associated with a first auxiliary vehicle function; determining, by the processor, at least in part based on receipt or non-receipt of the first input and the second input, whether a predetermined button press sequence is successful; and driving, by the processor, a display on the vehicle to provide a visual indication based on the determination of whether the button press sequence is successful or unsuccessful.

[0004] The determination may be at least in part based on the processor determining whether the second input is received within a predetermined time period after receiving the first input.

[0005] Before waiting for the first input or the second input, the processor may detect that the remote control device is connected to a vehicle charging station, and wherein the determination may be at least in part based on the processor determining whether the first input is received within a predetermined time period after detecting the remote control connection to the charging station.

[0006] The first auxiliary function is associated with one of operation of a vehicle horn, a vehicle brake, or vehicle forks.

[0007] The second input may indicate that at least a second button and a third button of the remote control device have been pressed simultaneously, where the third button is associated with a second auxiliary vehicle function and where the first auxiliary function may be associated with one of the operations of a vehicle horn, a vehicle brake, or vehicle forks, and the second auxiliary function may be associated with a different one of the operations of a vehicle horn, a vehicle brake, or vehicle forks.

[0008] After receiving the first input and the second input, the processor may wait to receive a third input indicating that at least a third button of the remote control device has been pressed, where the third button is associated with the second auxiliary vehicle function; and the processor may determine whether a predetermined button press sequence is successful based at least in part on whether the first input, the second input, and the third input have been received or not received.

[0009] This determination may be based at least in part on the processor determining whether the third input is received within a predetermined time period after receiving the second input.

[0010] The predetermined button press sequence may include that the drive button of the remote control device is the first button pressed.

[0011] According to a second aspect, there is provided a system for testing the operating characteristics of a remote control device associated with a material handling vehicle, the system may include a memory device storing executable instructions; and a processor communicating with the memory device. In particular, when the processor executes the executable instructions: it may wait to receive a first input indicating that a first button of the remote control device has been pressed, where the first button includes the drive button of the remote control device; after receiving the first input, it may wait to receive a second input indicating that at least a second button of the remote control device has been pressed, where the second button is associated with a first auxiliary vehicle function; it may determine whether a predetermined button press sequence is successful based at least in part on whether the first input and the second input have been received or not received; and it may drive a display on the vehicle to provide a visual indication of whether the button press sequence is successful or unsuccessful based on the determination.

[0012] This determination may be based at least in part on the processor determining whether the second input is received within a predetermined time period after receiving the first input.

[0013] Before waiting to receive the first input or the second input, the processor may detect that the remote control device is connected to a vehicle charging station, and where this determination may be based at least in part on the processor determining whether the first input is received within a predetermined time period after detecting that the remote control is connected to the charging station.

[0014] The first auxiliary function is associated with one of the operations of a vehicle horn, a vehicle brake, or vehicle forks.

[0015] The second input may indicate that at least a second button and a third button of the remote control device have been pressed simultaneously, where the third button is associated with a second auxiliary vehicle function, and where the first auxiliary function may be associated with one of the operations of a vehicle horn, a vehicle brake, or vehicle forks, and the second auxiliary function may be associated with a different one of the operations of a vehicle horn, a vehicle brake, or vehicle forks.

[0016] After receiving the first input and the second input, the processor may wait to receive a third input indicating that at least the third button of the remote control device has been pressed, where the third button is associated with the second auxiliary vehicle function; and the processor may determine whether a predetermined button press sequence has been successful based at least in part on the receipt or non-receipt of the first input, the second input, and the third input.

[0017] The determination may be based at least in part on the processor determining whether the third input is received within a predetermined time period after receiving the second input.

[0018] The predetermined button press sequence may include that the drive button of the remote control device is the first button pressed. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 and Figure 2 are a side view and a top view of a material handling vehicle capable of being remotely and wirelessly operated according to various aspects of the present invention;

[0020] Figure 2A is a side view of another material handling vehicle capable of being remotely and wirelessly operated according to various aspects of the present invention;

[0021] Figure 3 is a schematic diagram of several components of a material handling vehicle capable of being remotely and wirelessly operated according to various aspects of the present invention;

[0022] Figures 4 - 7 is a view of a remote control device according to various aspects of the present invention;

[0023] Figure 8A and Figure 8B are cross-sectional views showing a remote control device engaged with a charging station according to various aspects of the present invention;

[0024] Figure 9 and Figure 10 is a view of another remote control device according to various aspects of the present invention;

[0025] Figure 11 is a schematic diagram of several components of a charging station according to various aspects of the present invention;

[0026] Figures 12 - 14is a view showing a remote control device and a charging station according to various aspects of the present invention;

[0027] Figure 15 is a schematic diagram of several components of a remote control device according to various aspects of the present invention;

[0028] Figure 16 depicts a method according to various aspects of the present invention;

[0029] Figure 17 depicts a pairing method according to various aspects of the present invention;

[0030] Figure 18 depicts another pairing method according to various aspects of the present invention;

[0031] Figure 19 depicts a method for re - pairing a vehicle and a remote control device according to various aspects of the present invention;

[0032] Figure 20 depicts a method for re - establishing communication between a vehicle and a remote control device according to various aspects of the present invention;

[0033] Figure 21 depicts a method for charging a remote control device according to various aspects of the present invention;

[0034] Figure 22 depicts another method for charging a remote control device according to various aspects of the present invention;

[0035] Figure 23 is a schematic diagram of several components of a kit according to various aspects of the present invention;

[0036] Figure 24 is a view of another remote control device according to various aspects of the present invention;

[0037] Figure 25 is a schematic diagram illustrating various aspects of the present invention;

[0038] Figure 26 and Figure 27 illustrates a remote control device and a charging station constructed according to another embodiment;

[0039] Figures 28A - 28I illustrates Figure 26 and Figure 27 various states of first and second visual indicators of the charging station of Detailed Description

[0040] In the following detailed description of the illustrated embodiments, reference is made to the accompanying drawings, which show, by way of illustration and not limitation, specific embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and changes may be made without departing from the spirit and scope of the various embodiments of the invention.

[0041] Low-level order picking truck

[0042] Now referring to the drawings, and in particular Figure 1 and Figure 2 , the material handling vehicle 10, illustrated as a low level order picking truck, includes a load handling assembly 12 extending from a power unit 14. The vehicle 10 forms part of a system 8 according to aspects of the present invention, which will be described more fully below. The load handling assembly 12 includes a pair of forks 16, each fork 16 having a load support wheel assembly 18. In addition to or in lieu of the illustrated arrangement of the forks 16, the load handling assembly 12 may include other load handling features, such as a load backrest, scissor lift forks, outriggers, or individually height-adjustable forks, to name just a few examples. Further still, the load handling assembly 12 may include load handling features such as a mast, a load platform, a collection cage, or other support structures carried by or otherwise provided for handling the load supported and carried by the vehicle 10. Although the present disclosure is made with reference to the illustrated vehicle 10, it will be apparent to those skilled in the art that the vehicle 10 may include a variety of other industrial vehicles, such as forklifts, reach trucks, etc., and the following description of the invention with reference to the drawings should not be limited to order picking trucks unless otherwise specified. Additionally, the vehicle 10 may be implemented in other forms, styles, and features, including vehicles 10 that do not include a load handling assembly, such as trailers, etc.

[0043] The illustrated power unit 14 includes a step-through operator station 20 that separates a first end section (opposite the forks 16) of the power unit 14 from a second end section (near the forks 16). The operator station 20 includes a platform 21 on which an operator can stand to drive the vehicle 10 and / or provide a location from which the operator can operate the various included features of the vehicle 10.

[0044] A presence sensor 22 (see Figure 2 ) may be provided to detect the presence of an operator on the vehicle 10. For example, the presence sensor 22 may be located on, above, or below the platform 21, or otherwise provided around the operator station 20. In Figure 2In an exemplary vehicle 10, presence sensors 22 are shown in dashed lines, indicating that they are located below the platform 21. In such an arrangement, the presence sensors 22 can include load sensors, switches, etc. Alternatively, the presence sensors 22 can be implemented above the platform 21, such as by using ultrasonic, capacitive, or other suitable sensing techniques. The utilization of the presence sensors 22 will be described in more detail herein.

[0045] According to Figure 2 one embodiment shown in, the vehicle 10 can include a pole that extends vertically from the power unit 14 and includes an antenna 30 provided to receive control signals from a corresponding wireless remote control device 32. The pole can include a light 33 at the top, as Figure 1 and Figure 2 shown in. According to Figure 2A another embodiment shown in, the antenna can be located within other vehicle components such that control signals from the remote control device 32 are received elsewhere in the vehicle 10, as will be discussed below. The remote control device 32 includes additional components of the system 8 that will be described in more detail below.

[0046] The remote control device 32 can be manually operated by an operator, for example, by pressing a button or other controls, to cause the remote control device 32 to transmit at least a first type of signal specifying a driving request to the vehicle 10 paired with the remote control device 32. The driving request is a command to request the vehicle 10 to drive, as will be described in more detail herein. Although the remote control device 32 is in Figure 1 and Figure 2is shown as a finger-mounted structure, but various implementations of the remote control device 32 can be achieved, including, for example, a glove structure, a lanyard, or a belt-mounted structure, etc. Further, the vehicle 10 and the remote control device 32 can include any additional and / or alternative features or implementations, examples of which are disclosed in U.S. Provisional Patent Application Serial No. 60 / 825,688, filed on September 14, 2006, entitled "SYSTEMS AND METHODS OF REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE"; U.S. Patent Application Serial No. 11 / 855,310, filed on September 14, 2007, entitled "SYSTEMS AND METHODS OF REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE", now U.S. Patent No. 9,082,293; U.S. Patent Application Serial No. 11 / 855,324, filed on September 14, 2007, entitled "SYSTEMS AND METHODS OF REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE", now U.S. Patent No. 8,072,309; U.S. Provisional Patent Application Serial No. 61 / 222,632, filed on July 2, 2009, entitled "APPARATUS FOR REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE"; U.S. Patent Application Serial No. 12 / 631,007, filed on December 4, 2009, entitled "MULTIPLE ZONE SENSING FOR MATERIALS HANDLING VEHICLES", now U.S. Patent No. 9,645,968; U.S. Provisional Patent Application Serial No. 61 / 119,952, filed on December 4, 2008, entitled "MULTIPLE ZONE SENSING FOR REMOTELY CONTROLLED MATERIALS HANDLING VEHICLES"; and / or U.S. Patent No. 7,017,689, issued on March 28, 2006, entitled "ELECTRICAL STEERING ASSIST FOR MATERIAL HANDLING VEHICLE", the entire disclosure of each document is incorporated herein by reference. Additional details related to the remote control device 32 will be discussed in detail below.

[0047] Vehicle 10 further includes one or more non-contact obstacle sensors 40 provided around the vehicle 10, for example towards a first end section of the power unit 14, as Figure 1 and Figure 2 shown. The obstacle sensors 40 are operable to define at least one detection zone. For example, when the vehicle 10 travels in response to a wirelessly received driving request from the remote control device 32, the at least one detection zone may define an area at least partially in front of the forward driving direction of the vehicle 10, as also described in more detail herein.

[0048] The obstacle sensors 40 may include any suitable proximity detection technology, such as ultrasonic sensors, image capture devices, infrared sensors, laser scanner sensors, etc., which are capable of detecting the presence of an object / obstacle or generating signals that can be analyzed to detect the presence of an object / obstacle within a predefined detection zone(s). In the Figure 1 and Figure 2 exemplary embodiment shown, the vehicle 10 includes a first obstacle detector 42 mounted to the power unit 14 and a pair of second obstacle detectors 44A and 44B. The first obstacle detector 42 is spaced apart from the second obstacle detectors 44A and 44B along a vertical axis V of the vehicle 10 that defines a vertical direction, i.e., the second obstacle detectors 44A and 44B are located below the first obstacle detector 42 (closer to the ground than the first obstacle detector 42), see A . The second obstacle detectors 44A and 44B are spaced apart from each other along a horizontal axis H of the vehicle 10 that defines a horizontal direction, see Figure 1 . A Figure 2 .

[0049] The first obstacle detector 42 may include a scanning laser sensor capable of detecting objects, for example, in first, second, and third zones Z 1 , Z 2 , Z 3 (also referred to herein as the scanning zone or detection zone), the first, second, and third zones Z 1 , Z 2 , Z 3 may include planar zones, see Figure 1 and Figure 2 . The second zone Z 2 may include a "stop zone", and the first and third zones Z 1 and Z 3may include left and right “steering bumper zones,” such as the stop zone and left and right steering bumper zones described in U.S. Patent No. 8,452,464, titled “STEER CORRECTION FOR A REMOTELY OPERATED MATERIALS HANDLING VEHICLE,” issued on May 28, 2013, the entire disclosure of which is incorporated herein by reference. It should be noted that the first obstacle detector 42 may be capable of detecting objects in more or fewer zones than the three zones Z 1 、Z 2 、Z 3 . In an exemplary detection zone configuration, any or all of the detection zones may be used, as disclosed in U.S. Patent No. 9,002,581, titled “OBJECT TRACKING AND STEER MANEUVERS FOR MATERIALS HANDLING VEHICLES,” issued on April 7, 2015, the entire disclosure of which is incorporated herein by reference.

[0050] The second obstacle detectors 44A and 44B may include point laser sensors that are capable of detecting objects between one or more of the zones Z 1 、Z 2 、Z 3 and the vehicle 10 (i.e., below one or more of the zones Z 1 、Z 2 、Z 3 , as shown in Figure 1 ) and / or passing through the zones Z 1 、Z 2 、Z 3 , and preferably is capable of detecting at least objects below the second zone Z2. Thus, the second obstacle detectors 44A and 44B are capable of detecting objects located in the non-detection zone DZ of the first obstacle detector 42, see Figure 1 , i.e., the non-detection zone DZ is defined as the area below the zones Z 1 、Z 2 、Z 3 and is thus not sensed by the first obstacle detector 42. Thus, the first obstacle detector 42 is used to detect objects along the travel path of the power unit 14 that are outside the non-detection zone DZ, while the second obstacle detectors 44A and 44B are used to sense objects along the travel path of the power unit 14 in the non-detection zone DZ that is directly in front of the vehicle 10, as shown in Figure 1 .

[0051] Additional sensor configurations and / or detection zones can be used, such as those discussed in the various patents and patent applications incorporated herein by reference.

[0052] Figure 1 and Figure 2 The vehicle 10 shown in also includes a charging station 50 that includes additional components of the system 8 and is provided for charging the rechargeable power supply of the remote control device 32. Additional details related to the charging station 50 will be described below.

[0053] Control System for Remote Operation of Low-Level Order Pickers

[0054] Reference Figure 3 , the block diagram illustrates a control arrangement for integrating remote control commands with the vehicle 10. A receiver 102, which can be, for example, a Bluetooth Low Energy (BLE) radio transceiver, is provided for receiving commands issued by the remote control device 32. The receiver 102 passes the received control signal to a controller 103, which implements an appropriate response to the received command and can thus also be referred to herein as the master controller. In this regard, the controller 103 is implemented in hardware and can also execute software (including firmware, resident software, microcode, etc.). Additionally, aspects of the present invention can take the form of a computer program product implemented in one or more computer-readable media having computer-readable program code embodied thereon. For example, the vehicle 10 can include a memory storing the computer program product, which when implemented by a processor of the controller 103, implements steering correction as more fully described herein.

[0055] Thus, the controller 103 can at least partially define a data processing system suitable for storing and / or executing program code and can include, for example, at least one processor directly or indirectly coupled to a memory element via a system bus or other suitable connection. The memory element can include local memory employed during actual execution of the program code, memory integrated into a microcontroller or application-specific integrated circuit (ASIC), programmable gate arrays, or other reconfigurable processing devices, etc.

[0056] The response implemented by controller 103 in response to a command received wirelessly (e.g., via wireless transmitter 178 of remote control device 32, to be discussed below) and sent to receiver 102 on vehicle 10 can include one or more actions or inactions, depending on the logic being implemented. Positive actions can include controlling, adjusting, or otherwise affecting one or more components of vehicle 10. Controller 103 can also receive information from other inputs 104 (e.g., from sources such as presence sensors 22, obstacle sensors 40, switches, load sensors, encoders, and other devices / features available to vehicle 10) to determine appropriate actions in response to commands received from remote control device 32. Sensors 22, 40, etc. can be connected to controller 103 via input 104 or via a suitable truck network such as controller area network (CAN) bus 110.

[0057] In an exemplary arrangement, remote control device 32 is operable to wirelessly transmit a control signal to receiver 102 on vehicle 10, the control signal representing a first type of signal such as a drive command. A drive command is also referred to herein as a "drive signal", "drive request", or "forward signal". A drive request is used to initiate a request to drive vehicle 10, e.g., as long as the drive signal is received by receiver 102 and / or transmitted by remote control device 32 for a predetermined amount, e.g., to move vehicle 10 forward in a first direction or jog for a limited driving distance or limited time. For example, the first direction can be defined by vehicle 10 first moving in power unit 14, i.e., the direction in which forks 16 move backward. However, other driving directions can alternatively be defined. Also, vehicle 10 can be controlled to drive in a generally straight direction or along a previously determined heading. Accordingly, the limited driving distance can be specified by an approximate driving distance, driving time, or other measurement.

[0058] Accordingly, the first type of signal received by receiver 102 is transmitted to controller 103. If controller 103 determines that the drive signal is a valid drive signal and the current vehicle conditions are appropriate (explained in more detail in U.S. Patent No. 9,082,293, which is hereby incorporated by reference), then controller 103 sends a signal to the appropriate control configuration of vehicle 10 to drive forward and then stop vehicle 10. Stopping vehicle 10 can be achieved, for example, by either allowing vehicle 10 to coast to a stop or by initiating a braking operation to brake vehicle 10 to a stop.

[0059] As an example, controller 103 may be communicatively coupled to a traction control system, shown as traction motor controller 106 of vehicle 10. Traction motor controller 106 is coupled to a traction motor 107 that drives at least one steerable wheel 108 of vehicle 10. Controller 103 may communicate with traction motor controller 106 in response to receiving a drive request from remote control device 32 to accelerate, decelerate, adjust, and / or otherwise limit the speed of vehicle 10. Controller 103 may also be communicatively coupled to a steering controller 112, which is coupled to a steering motor 114 that steers at least one steerable wheel 108 of vehicle 10. In this regard, in response to receiving a drive request from remote control device 32, vehicle 10 may be controlled by controller 103 to travel an expected path or maintain an expected heading.

[0060] As yet another illustrative example, controller 103 may be communicatively coupled to a brake controller 116, which controls vehicle brakes 117 to decelerate, stop, or otherwise control the speed of vehicle 10 in response to receiving a drive request from remote control device 32. Further still, where applicable, controller 103 may be communicatively coupled to other vehicle features (such as main contactor 118 and / or other outputs 119 associated with vehicle 10) to effectuate desired actions in response to implementing a remote driving function.

[0061] In accordance with various aspects of the present invention, controller 103 may communicate with receiver 102 and with traction motor controller 106 to operate vehicle 10 under remote control in response to receiving a drive command from an associated remote control device 32. Moreover, if vehicle 10 is traveling under remote control in response to a drive request and an obstacle is detected in one or more of detection zones Z 1 、Z 2 、Z 3 then controller 103 may be configured to perform various actions. In this regard, when a drive signal is received by controller 103 from remote control device 32, controller 103 may consider any number of factors to determine whether action should be taken on the received drive signal to initiate and / or maintain movement of vehicle 10.

[0062] Accordingly, if vehicle 10 moves in response to a command received from remote control device 32, then controller 103 may dynamically change, control, adjust, or otherwise affect the remote control operation, such as by stopping vehicle 10, changing the steering angle of vehicle 10, or taking other actions. Thus, particular vehicle features, the state / condition of one or more vehicle features, the vehicle environment, etc. may affect the manner in which controller 103 responds to a drive request from remote control device 32.

[0063] The controller 103 may reject confirmation of a received driving request based on, for example, one or more predetermined conditions related to the environment or one or more operating factors. For example, the controller 103 may ignore otherwise valid driving requests based on information obtained from one or more of the sensors 22, 40. By way of illustration, in accordance with various aspects of the present invention, when determining whether to respond to a driving command from the remote control device 32, the controller 103 may optionally consider factors such as whether the operator is on the vehicle 10. As described above, the vehicle 10 may include at least one presence sensor 22 for detecting whether the operator is located on the vehicle 10. In this regard, the controller 103 may also be configured to respond to a driving request to operate the vehicle 10 under remote control when the one or more presence sensors 22 specify that no operator is on the vehicle 10. Thus, in this embodiment, the vehicle 10 cannot be operated in response to a wireless command from the remote control device 32 unless the operator physically leaves the vehicle 10. Similarly, if the obstacle sensor 40 detects an object, including the operator, approaching and / or nearing the vehicle 10, then the controller 103 may reject confirmation of the driving request from the remote control device 32. Thus, in an exemplary embodiment, the operator must be located within a restricted range of the vehicle 10, e.g., close enough to the vehicle 10 to be within the wireless communication range (which may be limited by setting a maximum distance of the operator from the vehicle 10). Other arrangements may alternatively be implemented.

[0064] Any other reasonable condition, factor, parameter, or other consideration may alternatively be implemented by the controller 103 to interpret and take action in response to signals received from the transmitter 178. Other exemplary factors are set forth in greater detail in U.S. Provisional Patent Application Serial No. 60 / 825,688, entitled "SYSTEMS AND METHODS OF REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE"; U.S. Patent Application Serial No. 11 / 855,310, entitled "SYSTEMS AND METHODS OF REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE", now U.S. Patent No. 9,082,293; U.S. Patent Application Serial No. 11 / 855,324, entitled "SYSTEMS AND METHODS OF REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE", now U.S. Patent No. 8,072,309; U.S. Provisional Patent Application Serial No. 61 / 222,632, entitled "APPARATUS FOR REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE"; U.S. Patent Application Serial No. 12 / 631,007, entitled "MULTIPLE ZONE SENSING FOR MATERIALS HANDLING VEHICLES", now U.S. Patent No. 9,645,968; and U.S. Provisional Patent Application Serial No. 61 / 119,952, entitled "MULTIPLE ZONE SENSING FOR REMOTELY CONTROLLED MATERIALS HANDLING VEHICLES", the disclosures of which are hereby incorporated by reference in their entireties.

[0065] After confirming the driving request, the controller 103 interacts with the traction motor controller 106, for example, directly or indirectly (e.g., via a bus such as the CAN bus 110 if used), to propel the vehicle 10. Depending on the specific implementation, the controller 103 may interact with the traction motor controller 106 and an optional steering controller 112 to propel the vehicle 10 as long as a driving control signal is received. Alternatively, the controller 103 may interact with the traction motor controller 106 and optionally the steering controller 112 to cause the vehicle 10 to move forward for a period of time or a predetermined distance in response to the detection and sustained actuation of driving control on the remote control device 32. Further, the controller 103 may be configured to "time out" and stop the vehicle 10 based on a predetermined event (such as exceeding a predetermined time period or driving distance), regardless of the detection of the sustained actuation of the corresponding control on the remote control device 32.

[0066] The remote control device 32 may also be operable to transmit a second type of signal (such as a "stop signal" indicating that the vehicle 10 should brake and / or otherwise come to rest). The second type of signal may also be implicit, for example, after implementing a "drive" command, e.g., after the vehicle 10 has traveled a predetermined distance, for a predetermined time, etc., under remote control in response to the drive command. If the controller 103 determines that the wirelessly received signal is a stop signal, then the controller 103 sends a signal to the traction motor controller 106, the brake controller 116, and / or other truck components to cause the vehicle 10 to come to rest. As an alternative to the stop signal, the second type of signal may include a "coast signal" or a "controlled deceleration signal" specifying that the vehicle 10 should coast and ultimately decelerate to a stop.

[0067] The time required to bring the vehicle 10 to a complete stop may vary depending on, for example, the intended application, environmental conditions, the capabilities of the specific vehicle 10, the load on the vehicle 10, and other similar factors. For example, after completing an appropriate jogging movement, it may be desirable to allow the vehicle 10 to "coast" some distance before coming to rest, such that the vehicle 10 stops slowly. This can be achieved by using regenerative braking to decelerate the vehicle 10 to a stop. Alternatively, a braking operation may be applied after a predetermined delay time to allow the vehicle 10 to travel an additional predetermined range after the stop operation is initiated. For example, if an object is detected in the travel path of the vehicle 10 or if immediate stopping is desired after a successful jogging operation, it may also be desirable to cause the vehicle 10 to stop relatively more quickly. For example, the controller 103 may apply a predetermined torque to the braking operation. In this case, the controller 103 may instruct the brake controller 116 to apply the brakes 117 to stop the vehicle 10.

[0068] Figure 3Also shown therein is an in-vehicle charging station 50 that can communicate with the controller 103. As will be explained in more detail below, the charging station 50 can be used to charge the rechargeable power supply 180 of the wireless remote control device 32. The charging station 50 can be located on the side of the vehicle 10, such as near the operator station 20, near the manual driving control device of the vehicle 10 (such as Figure 1 and Figure 2 shown therein), or on the side panel of the power unit 14.

[0069] The pairing system 34 can wirelessly communicate with a compatible near-field system on the wireless remote control device 32 using a near-field system. Using the pairing system 34, the vehicle 10 and the wireless remote control device 32 can be "paired" such that the vehicle 10 will only transmit and receive messages from its paired wireless remote control device 32. In addition to or in place of near-field or other types of wireless communication (such as near-field communication (NFC)), the pairing system 34 can also use physical contact that allows electrical communication between the remote control device 32 and the vehicle 10, at least for the initial pairing procedure. For example, the electrical contacts of the charging station 50 used to charge the remote control device 32 can be used to pair the vehicle 10 with the remote control device 32, as will be described in more detail herein. The pairing system 34 includes components that physically implement communication methods for sending messages (e.g., Bluetooth, NFC, BLE, Wi-Fi, etc.), and includes components that programmatically exchange information in an agreed-upon protocol to establish and maintain the pairing. Thus, the pairing system 34 includes devices that can execute programmable instructions to implement a predetermined algorithm and protocol to complete the pairing operation.

[0070] In Figure 3 the charging station 50, the receiver 102, and the pairing system 34 are depicted as separate functional blocks. However, those of ordinary skill in the art will recognize that two or more of these components can be combined into a single element to provide a multi-functional device.

[0071] System

[0072] As described above, according to one aspect of the present invention, the vehicle 10 (including the charging station 50) and the remote control device 32 form a system 8. The remote control device 32 and the charging station 50 will now be described in turn.

[0073] Referring Figure 4 - Figure 8, the remote control device 32 according to this embodiment is a finger-mounted device, but the remote control device 32 can take other forms, such as a glove-mounted device, a wrist-mounted device, a lanyard-mounted device, etc. The remote control device 32 can be mountable on one finger, two fingers, or more than two fingers of the operator.

[0074] Figure 4- The remote control device 32 shown in FIG. 8 includes an integrated rigid base 172 (see Figure 6 ), and an integrated rigid upper housing 174. The base 172 and the upper housing 174 are coupled together in any suitable manner and define an internal area 176 for receiving the internal components of the remote control device 32, including a wireless communication system 456 that includes a wireless transmitter 178 (such as the wireless transmitter 178 described above with reference to Figure 3 ), and a rechargeable power source 180). In one exemplary embodiment, the wireless transmitter 178 includes model BGM121 manufactured by SiLabs. It should be noted that as used herein, the terms "transmitter" and "receiver" are intended to denote a device capable of unidirectional communication, i.e., a device that only transmits or receives signals, or a device capable of bidirectional communication, such as a transceiver that both transmits and receives signals.

[0075] The rechargeable power source 180 can be a supercapacitor, a high-capacity battery, etc. For example, an AVX supercapacitor, model SCCR20E335PRB, can be used, which has a rated voltage of 3V and a capacitance of 3.3F. The rechargeable power source 180 is small enough to fit within the internal area 176, while also having sufficient capacity when substantially fully charged to provide a usage period of at least two hours, at least four hours, at least eight hours, or more for the remote control device 32. A usage period of up to eight hours may be preferred to correspond to an eight-hour work shift of the operator.

[0076] A supercapacitor (also known as a supercap or ultracapacitor) is a high-capacity capacitor with a capacitance value much higher than that of other capacitors, but typically with a lower voltage limit, to bridge the gap between electrolytic capacitors and rechargeable batteries. They usually store 10 to 100 times more energy per unit volume or mass than electrolytic capacitors, can accept and deliver charge faster than batteries, and can withstand more charge and discharge cycles than rechargeable batteries. Since supercapacitors can be used in applications that require many rapid charge / discharge cycles, some embodiments of the remote control device 32 may include a supercapacitor as the rechargeable power source 180. In an embodiment of the present invention, the current supplied to the supercapacitor can be limited to approximately 2A and the charging to full charge can be completed in approximately 2 seconds or less. Regardless of the specific type of rechargeable power source 180 used, embodiments of the present invention contemplate recharging the rechargeable power source 180 to a desired amount (such as a full charge state, or a charge state below substantially full charge) via the charging station 50 within a desired charging period (as will be discussed in detail herein). The power supplied to the rechargeable power source 180 by the charging station 50 can vary according to the capacity of the rechargeable power source 180, the desired amount of charge, and / or the desired charging period, as will be discussed in more detail herein.

[0077] Reference Figure 6 , the remote control device 32 further includes a securing structure 188 for securing the remote control device 32 to one or more fingers of an operator's hand. Figure 6 The securing structure 188 in the embodiment shown includes a retaining strap 190 that includes, for example, a hook-and-loop fastener 191 to secure the retaining strap 190 to a single finger (e.g., the index finger) of the operator. The remote control device 32 is provided with first and second slots 192A and 192B at opposite ends of the remote control device 32 for receiving the retaining strap 190.

[0078] Figure 6 The retaining strap 190 shown defines a first finger receiving area 194 for receiving a single finger of an operator using the remote control device 32. F (See Figure 1 and Figure 2)。Right - hand and left - hand versions of the remote control device 32 can be created. The remote control device 32 is removably held on the operator's index finger via a retention strap 190. In one exemplary embodiment, the first end 190A of the retention strap 190 passes through the first slot 192A and the second end 190B of the retention strap 190 passes through the second slot 192B. The first end 190A of the retention strap 190 can be permanently fastened to the rigid base 172, for example, via stitching or gluing, while the second end 190B of the retention strap 190 can be releasably inserted through the second slot 192B and folded back such that the hook - and - loop fasteners 191 engage each other to fasten the retention strap 190 to the operator's finger. The retention strap 190 can be adjusted to accommodate different finger sizes or such that the remote control device 32 can be worn over a glove (not shown). Note that other types of retention straps 190 can be used.

[0079] The remote control device 32 also includes at least one control, depicted in Figure 4 - FIG. 8 as first, second, and third controls 196A - C. The controls 196A - C each include a button 197A - C and a two - state switch 198A - C located below the corresponding button 197A - C. The switches 198A - C are communicatively coupled to the wireless communication system 456 such that actuation of each of the controls 196A - C causes the wireless transmitter 178 to wirelessly transmit a corresponding request to the vehicle 10. In Figure 4 - the exemplary remote control device 32 depicted in FIG. 8: The first control 196A includes a drive button 197A which, when pressed, causes the wireless transmitter 178 to wirelessly transmit a request for the vehicle 10 to drive across the floor surface; the second control 196B includes a horn button 197B which, when pressed, causes the wireless transmitter 178 to wirelessly transmit a request for the vehicle 10 to sound a horn / sound alert; and the third control 196C includes a brake button 197C which, when pressed, causes the wireless transmitter 178 to wirelessly transmit a request for the vehicle to stop (if moving under wireless control) and optionally power down.

[0080] The remote control device 32 is compact, and substantially the entire remote control device 32 can be mounted and directly positioned above the operator's index finger. Thus, the interference caused by the operator wearing the remote control device 32 while performing work tasks is minimal or non - existent. Since the rigid base 172 and the upper housing 174 are preferably formed of a durable and rigid polymeric material such as acrylonitrile butadiene styrene (ABS), polycarbonate, or nylon, the remote control device 32 is durable and long - lasting. The rigid base 172 and the upper housing 174 define a durable, generally non - flexible and rigid structure.

[0081] The operator can easily manually actuate the drive button 197A with his / her thumb to cause the wireless transmitter 178 to wirelessly transmit at least a first type of signal specifying a drive request or command to the vehicle 10. It is contemplated that as long as the operator holds down the drive button 197A, the drive request can cause the vehicle 10 to move, either for a predetermined distance or for a predetermined amount of time. For example, the horn button 197B and the brake button 197C can be actuated by the operator's other hand.

[0082] As Figure 4 and Figure 5 shown, the remote control device 32 also includes one or more charging contacts 210. It should be noted that more or fewer than the four charging contacts 210 shown can be used. For example, one charging contact 210 or two or more charging contacts 210 can be used. In addition, the remote control device 32 also includes one or more sensors in the form of a first presence contact 212, which is illustrated in Figure 4 and Figure 5 as a single first presence contact 212 located in the middle of the four charging contacts 210. The charging contacts 210 and the first presence contact 212 can be arranged within an opening 214 formed in the outer surface of the upper housing 174 of the remote control device 32. The tops of the charging contacts 210 and the first presence contact 212 can be positioned below the outer surface of the upper housing, i.e., the charging contacts 210 and the first presence contact 212 can be recessed within the opening 214, which can prevent damage to the charging contacts 210 and the first presence contact 212 due to accidental contact. It should be noted that other configurations of the number, orientation, and placement of the charging contacts 210 and the (one or more) first presence contacts 212 can be used without departing from the scope and spirit of the present invention.

[0083] In an embodiment, the charging contacts 210 mate or engage with elements (e.g., the electrical contacts of the in-vehicle charging station 50 or the charging element 220 (to be discussed below)), and the first presence contact 212 mates or engages with a complementary second sensor in the form of a second presence contact 222, such as a switch, spring pin, or pressure pin of the in-vehicle charging station 50, as Figure 8A and Figure 8B shown and will be described in more detail herein. It should be noted that one or more of the charging contacts 210 and the corresponding charging elements 220 can be provided for redundancy. In one example, Figures 4 - 7 the four charging contacts 210 shown in Figures 12 - 14 and the four charging elements 220 shown in can be provided as two pairs of redundant contacts / elements 210 / 220, where as long as one charging contact 210 from each pair mates with its corresponding charging element 220 and is in electrical communication therewith, charging of the rechargeable power source 180 (as discussed below) is enabled.

[0084] Embodiments of the present invention also contemplate non-contact or inductive charging, where the rechargeable power supply 180 of the remote control device 32 can be charged by being in proximity to a compatible inductive charging station (not shown) or on the surface thereof. Such an inductive charging station can be located, for example, in the driving or steering controls of the vehicle 10 such that the rechargeable power supply 180 can be charged while the operator manually drives the vehicle 10 from the operator station 20.

[0085] Figure 9 and Figure 10 Another exemplary remote control device 32 is illustrated, where like reference numerals correspond to like components as listed above for Figure 4 -FIG. 8. The remote control device 32 according to this embodiment is intended to be a two-finger design, i.e., Figure 9 and Figure 10 the fixed structure 188 in the embodiment shown in Figure 9 and Figure 10 includes a retaining strap 190 that defines first and second finger receiving regions 194, 195 for receiving the index finger and middle finger of an operator using the remote control device 32. The remote control device 32 according to Figure 4 -FIG. 8 includes two charging contacts 210 instead of the four charging contacts 210 in the remote control device 32 of Figure 9 and Figure 10 The remaining components of the remote control device 32 of Figure 4 -FIG. 8 can generally be the same as those of the remote control device 32 of

[0086] Figure 11A functional block diagram of a vehicle charging station 50 in accordance with the principles of the present invention is provided, where a pairing system 34 is incorporated into the charging station 50. As explained in more detail below, the charging station 50 can include a receiver 102, for example, a Bluetooth Low Energy (BLE) radio transceiver 402 that can communicate with a vehicle's controller 103. Although not shown, the communication can be via the vehicle's CAN bus, so the charging station 50 can include a CAN bus interface. The charging station 50 can also include one or more light emitting diodes (LEDs) 404 or other visual indicators to assist in communicating information to an operator. For example, one LED can be used to indicate that the remote control device 32 is currently coupled to the charging station 50. Other LEDs can indicate the current charge state of the rechargeable power source 180 of the remote control device. A current limiter 406 or other protection circuitry can be provided to help ensure that the remote control device 32 is safely recharged, as the current limiter 406 allows voltage from the vehicle power source to be provided to the charging element 220 of the charging station 50 for charging the rechargeable power source 180 of the remote control device. These charging elements 220 interface with the charging contacts 210 of the remote control device 32 and provide an electrical connection between the vehicle's power source and the rechargeable power source 180 of the remote control device 32. A second presence contact 222 engages with a first presence contact 212 to detect when the remote control device 32 is physically connected to the charging station 50 such that the charging contacts 210 engage with the charging elements 220. According to an embodiment, after the second presence contact 222 is engaged by the first presence contact 212, a pairing process is initiated.

[0087] It should be noted that the first and second presence contacts 212, 222 can be provided on either the remote control device 32 or the charging station 50, respectively. That is, although the second presence contact 222 is illustrated on the charging station 50 and the first presence contact 212 is illustrated on the remote control device 32, the second presence contact 222 can be located on the remote control device 32 and the first presence contact 212 can be located on the charging station 50.

[0088] The relationship between the second presence contact 222 and the charging element 220 is such that when the charging process is initiated, the charging contacts 210 of the remote control device 32 and the charging elements 220 of the charging station 50 contact each other before the second presence contact 222 engages the first presence contact 212, see Figure 8A, which shows that the height of the second presence contact 222 is less than the height of the charging element 220, the height being measured relative to the top surfaces of the respective charging element 220 and the second presence contact housing 222A from which the second presence contact 222 extends. Power supply from the charging station 50 to the remote control device 32 via the charging element / charging contact 220 / 210 is initiated only after the second presence contact 222 engages the first presence contact 212. During the charging process, the charging contact 210 of the remote control device 32 engages the charging element 220 of the charging station 50, and the second presence contact 222 engages the first presence contact 212, enabling power supply from the charging station 50 to the remote control device 32 via the charging element / charging contact 220 / 210, see Figure 8B . After the rechargeable power supply 180 has been charged to a desired amount, such as fully charged or charged to a desired amount less than fully charged as described herein, power supply from the charging station 50 to the remote control device 32 via the charging element / charging contact 220 / 210 is cut off. In the case where the remote control device 32 is removed from the charging station 50 before the rechargeable power supply 180 has been charged to the desired amount, as the remote control device 32 is removed from the charging station 50, the second presence contact 222 disengages from the first presence contact 212 before the charging element 220 disengages from the charging contact 210. When the second presence contact 222 disengages from the first presence contact 212, the power supply from the charging station 50 to the rechargeable power supply 180 of the remote control device 32 via the charging element / charging contact 220 / 210 is cut off. This arrangement is intended to prevent arcing between the charging element 220 and the charging contact 210. The use of the first presence contact 212 and the second presence contact 222 in the form of spring pins provides the following advantages: precise control of the relative height of the second presence contact 222 with respect to the charging element 220; a small footprint, good sealing, e.g., to prevent moisture from entering the second presence contact housing 222A around the second presence contact 222; and it allows differentiation of the first presence contact 212 from foreign objects (such as a piece of metal), which prevents current from flowing into this foreign object if it is placed in contact with one or more of the second presence contact 222 and the charging element 220.

[0089] As an alternative to the presence contacts 212, 222 for initiating power supply from the charging station 50 to the remote control device 32, there may be a separate switch that the operator engages to start the charging operation. In a specific embodiment using inductive charging, such a switch may be incorporated into the steering control of the vehicle such that detection of the operator's grip on the steering control and subsequent enabling of charging occur.

[0090] The control 414 for providing a control signal to operate the LED 404 can come from various sources. For example, when the remote control device 32 is operating within the range of the charging station 50, the controller 103 can receive information about the charging status of the rechargeable power supply 180 and drive the display of the LED 404 to convey this information using the CAN bus interface. When the remote control device 32 is coupled to the charging station 50, the LED 404 can be used to convey a) the remote control device 32 is physically connected to the charging station 50, b) there is a remote control device 32 currently paired with the vehicle's controller 103, c) the progress / status of the current charging operation, and / or d) the charging status of the rechargeable power supply 180. The information for items c) and d) can be sent by the remote control device 32 to the charging station 50, for example, via a Bluetooth Low Energy (BLE) connection, which will be discussed in more detail below. According to one aspect, since the pairing and charging processes are carried out very quickly, the LED 404 may not display the progress / status of the current charging operation. After the remote control device 32 is removed from the charging station 50, the remote control device 32 can store its charging profile and then send the charging profile to the charging station 50, for example, via a BLE connection, where the charging profile can be evaluated, for example, by the controller 103 to determine whether proper charging of the rechargeable power supply 180 has occurred. The second presence contact 222 can also send a control signal to the control 414 indicating whether the charging contact 210 of the remote control device 32 is properly coupled to the corresponding charging element 220 of the charging station 50.

[0091] Figures 12 - 14 Other features of the charging station 50 located at the vehicle 10 are illustrated. The charging station 50 can include one or more physical protrusions or guiding structures 420 that help guide the remote control device 32 into proper alignment such that the charging element 220 of the station is aligned with the charging contact 210 of the remote control device 32, i.e., the (one or more) guiding structures 420 align the remote control device 32 in the correct orientation for charging the rechargeable power supply 180. In Figure 12 it, a single guiding structure 420 including multiple guiding surfaces is shown. The (one or more) guiding structures 420 can be placed around the location of the charging element 220 and can be shaped or angled such that when the operator places the remote control device 32 in the charging station 50, the remote control device 32 is physically guided into proper alignment.

[0092] In Figure 13Among them, the LED 404 includes a visual indicator 424, which indicates that the remote control device 32 is attached to the charging station 50. The visual indicator 424 can illuminate, flash, or gradually fill with a first color to indicate that the remote control device 32 is attached to the charging station 50, and fill with a second color or completely fill with the first color to indicate that the remote control device 32 has been paired with the vehicle controller 103. That is, the visual indicator 424 can use the second color or the completely filled first color as a pairing indicator to confirm the establishment of communication between the remote control device 32 and the vehicle 10. In addition, according to an optional aspect of the present invention, after the communication is established between the remote control device 32 and the vehicle 10, the LED 404 can flash, illuminate as a second color, or provide some other visual indication as a clue for the operator to perform an action, as a test to confirm that the remote control device 32 is functioning and can communicate with the vehicle 10, such as by concurrently pressing the horn button 197B and the brake button 197C. It should be understood that, contrary to a single indicator that can perform both functions, separate indicators can be used for the purpose of indicating that the remote control device 32 is attached to the charging station 50 and indicating that the remote control device 32 has been paired with the vehicle 10.

[0093] The LED 404 can also be used as an indicator to identify the progress of the recharging operation when the remote control device 32 is attached. When the remote control device 32 is not attached to the charging station 50, the LED 404 can be used as an indicator to indicate the current charging state of the rechargeable power supply 180 of the remote control device 32. Therefore, the LED 404 can indicate the charging state of the rechargeable power supply 180 when the charging station 50 is charging the rechargeable power supply 180 and during the use of the remote control device 32 (i.e., when the operator is using the remote control device 32 to assist in performing work operations). In an exemplary embodiment, the LED 404 can include a series of lights, each light representing a charging state level of the rechargeable power supply 180.

[0094] In Figure 12 and Figure 14 an exemplary position of the second presence contact 222 within the charging station 50 is shown. It should be noted that Figures 12 - 14 the remote control device 32 shown in Figures 4 - 7 is a single-finger embodiment of

[0095] . It should also be noted that the charging contacts 210 and the first presence contact 212 of the single-finger and double-finger embodiments can be arranged to be mirror images of each other. Therefore, the same charging station 50 can be used for instances of single-finger or double-finger remote control devices 32.

[0095] The charging station 50 can be located at various positions on the vehicle 10. Its position should be such that it does not interfere with the normal operation of the vehicle 10, but is an accessible and convenient position for the operator. In an embodiment, the charging station 50 is located in the operator station 20 (seeFigure 1 and Figure 2 , where the charging station 50 is located within the operator station 20 but is also accessible from outside the vehicle 10), on a surface on one side of the vehicle 10, or, for inductive charging embodiments, within the steering control of the vehicle 10.

[0096] The charging station 50 may include a voltage regulator (not shown) that converts the power received by the charging station 50 from the vehicle 10 into a regulated direct current (DC) voltage signal selected based on the charging characteristics of the rechargeable power source 180. For example, in an embodiment where the rechargeable power source 180 is the above-described AVX supercapacitor or equivalent device, a 3V DC (1%) power supply voltage may be provided to the current limiter 406.

[0097] It should be noted that the remote control device 32 is described herein as having an exemplary configuration and may be structurally modified without departing from the spirit and scope of the present invention. For example, one or more components of the remote control device 32 may be combined into an integral component, or components may be replaced with alternative components that achieve similar / identical purposes.

[0098] In one embodiment, when one or more charging contacts 210 engage corresponding charging elements 220 of the charging station 50, the rechargeable power source 180 is charged via the charging station 50. In some embodiments, there are at least two charging contacts 210 or at least four charging contacts 210 and corresponding charging elements 220. In some embodiments, one or more pairs of charging contacts 210 are provided, where at least one charging contact 210 in each pair must engage the corresponding charging element 220 for charging. As described above, at least one of the remote control device 32 and the charging station 50 may include, for example, a second presence contact 222 (such as a switch). The second presence contact 222 detects whether at least one charging contact 210 is correctly engaged with at least one corresponding charging element 220 to charge the rechargeable power source 180, where if correct engagement is detected, then the charging station 50 enables the transfer of power to the rechargeable power source 180, and if correct engagement is not detected, then the charging station 50 does not enable the transfer of power to the rechargeable power source 180.

[0099] In addition, the arrangement of the remote control device 32 and the charging station 50 is configured such that the second presence contact 222 indicates removal of the remote control device 32 from the charging station 50, which stops the transfer of power from the charging station 50 to the rechargeable power source 180 before at least one charging contact 210 disengages from at least one corresponding charging element 220. Thus, the transfer of power from the charging station 50 to the rechargeable power source 180 is stopped before at least one charging contact 210 disengages from at least one corresponding charging element 220. For example, this can be achieved by setting the heights of the charging element 220 and the second presence contact 222, as Figure 8A shown, where when the remote control device 32 is inserted into the charging station 50, the charging element 220 is pushed downward into the corresponding element housing 220A before the second presence contact 222 engages the first presence contact 212.

[0100] Figure 15 is a block-level functional diagram of a portion 450 of the remote control device 32 that is related to recharging the rechargeable power source 180. Other portions of the remote control device 32 (such as, for example, those related to mechanical actuators) are not depicted in Figure 15 As described above, the remote control device 32 may include one or more charging contacts 210 configured to engage corresponding charging elements. In some embodiments, the charging element may be the charging element 220 of the charging station 50. In other embodiments, the charging element may be the charging element of an adapter connected to a power source to recharge the rechargeable power source 180.

[0101] The remote control device 32 may include a protection circuitry 452 that limits electrical parameters such as voltage and / or current within an expected operating range. The charging controller and disconnect circuitry 454 may monitor the voltage received from the protection circuitry 452 and monitor the current charge state of the rechargeable power source 180 to determine when to stop charging the rechargeable power source 180. For example, according to one exemplary embodiment, when the charge on the rechargeable power source 180 reaches 3V, the charging controller and disconnect circuitry 454 may operate to stop further charging. The charging controller and disconnect circuitry 454 may include temperature sensing capabilities or be connected to a temperature sensor such that the rechargeable power source 180 may be charged (or discharged) to different charge levels. In some embodiments, if the sensed temperature is determined to be higher than a predetermined set point temperature, then the rechargeable power source 180 is discharged to a high temperature charge state, e.g., below a fully charged state. In an exemplary aspect of the present invention, the sensed temperature is the ambient temperature. In an alternative aspect, the sensed temperature is the battery temperature. In some embodiments, if the sensed temperature is determined to be higher than a predetermined threshold temperature, then the rechargeable power source 180 is charged at the charging station 50 to a predetermined charge level below the 100% charge level. This may help prevent damage or degradation of the rechargeable power source 180.

[0102] As Figure 15 shown, the remote control device 32 may include a wireless communication system 456, such as, for example, a BLE radio transceiver that may communicate via a BLE connection with the BLE radio transceiver 402 of the charging station 50. The wireless communication system 456 and / or the BLE radio transceiver 402 of the charging station 50 may be configured to enter a low power mode, for example, when the remote control device 32 is paired with the vehicle 10 and / or when the rechargeable power source 180 of the remote control device 32 is being charged at the charging station 50, to ensure that only remote control devices 32 within a minimum distance from the charging station 50 (e.g., less than five inches or less than three inches corresponding to the signal strength of the communication received from the remote control device 32) are recognized as remote control devices 32 to be paired. Additionally, if the BLE radio transceiver 402 of the charging station 50 is to identify two or more remote control devices 32 that may be used for pairing and cannot determine the correct remote control device for pairing, then the charging station 50 cannot be paired with any available remote control device 32 and may require the operator to repeat the pairing process.

[0103] Associating / Pairing the Remote Control Device with the Vehicle

[0104] Figures 16 - 18 illustrates details of an exemplary pairing process in accordance with aspects of the present invention. The remote control device 32 and the vehicle 10 described above will be used to describe Figures 16 - 18The pairing process, but it should be understood that according to the present invention, other configurations / styles of the remote control device and the vehicle can also be paired together.

[0105] Reference Figure 16 , when at 502 the vehicle operator retrieves the remote control device 32, method 500 begins. If the remote control device 32 is a wearable device as in the Figure 4 -FIG. 8 and Figures 9 - 10 embodiment, then the remote control device 32 is also worn by the operator, for example, by securing the retention strap 190 to the operator's finger(s).

[0106] Then, the vehicle operator initiates a power-on sequence to enable the vehicle 10 to operate, i.e., at 504 the operator starts the vehicle 10. When starting the vehicle 10, the operator may be required to provide login information to the vehicle 10. This information can be provided, for example, by entering a personal identification number (PIN) into the vehicle 10's control panel, by providing a login ID to the vehicle 10 using a key card, or the operator's PIN can be encoded into a memory device (such as a radio frequency identification (RFID) chip integrated into the remote control device 32).

[0107] Then, at 506 the operator begins the pairing operation with the vehicle 10, and then at 508 the pairing system 34 pairs the remote control device 32 used by the operator with the vehicle 10. Details of two exemplary pairing operations will be described below with reference to Figure 17 and Figure 18 The details of two exemplary pairing operations are described in detail.

[0108] Once paired, the system 8 can provide a visual indication, for example, by displaying a message on the vehicle 10, illuminating the LED 424 in a predetermined color, creating an audible or visual cue indicating that the pairing is complete, etc.

[0109] According to one aspect of the present invention, the remote control device 32 can be unpair ed from the vehicle 10 by turning off the power of the vehicle 10. Other exemplary methods for unpairing the remote control device 32 from the vehicle 10 are described below in exemplary use cases.

[0110] Respectively with reference to Figure 17 and Figure 18 The operations of two example pairing systems 34 are described, Figure 17 and Figure 18 are flowcharts of example methods 550 and 600 for using the pairing system 34 to pair the vehicle 10 and the remote control device 32, where the pairing system 34 is part of the charging station 50 on the vehicle 10 board. Figure 17 and Figure 18 The descriptions of methods 550 and 600 in Figure 16corresponds to step 506.

[0111] Reference Figure 17 and method 550, at 552, when the second presence contact 222 is engaged by the first presence contact 212 when the remote control device 32 is inserted into the charging station 50, the BLE radio transceiver 402 of the charging station 50 is enabled to start scanning or listening for nearby BLE transmissions. As discussed above, the engagement of the first presence contact 212 with the second presence contact 222 can also enable the current limiter 406 such that power from the vehicle 10 can be provided from the charging element 220 to the charging contact 210, which will recharge the rechargeable power source 180 of the remote control device 32. Thus, the pairing and charging operations are initiated by a single action of coupling the remote control device 32 to the charging station 50. Instead of using BLE transmissions to pair the remote control device 32 with the vehicle controller 103, the remote control device 32 can be paired with the vehicle controller 103 through direct physical contact, for example, between the charging contact 210 and the charging element 220. Alternatively, dedicated pairing contacts (not shown) can be provided on the remote control device 32 and the vehicle 10 (e.g., at the charging station 50) to pair the remote control device 32 with the vehicle controller 103 via direct physical contact. Such pairing contacts on the remote control device 32 and the vehicle 10 can be engaged with each other while the charging contact 210 is engaged with the charging element 220, such that the pairing process can occur simultaneously with the charging process. These pairing contacts can be used solely to perform the message exchange for the pairing operation.

[0112] According to one aspect of the present invention, in the case where the pairing process is completed wirelessly, at 554, the remote control device 32 detects the presence of a voltage at its charging contact 210 and starts transmitting a BLE advertisement indicating that the remote control device 32 is available for communication with nearby devices via the wireless transmitter 178.

[0113] In response, the BLE radio transceiver 402 of the charging station 50 can receive one of the transmitted advertisements, and at 556, issue a BLE scan request directed to the specific remote control device 32 associated with the received advertisement. If the BLE radio transceiver 402 of the charging station 50 is to identify two or more remote control devices 32 available for pairing, i.e., by receiving BLE advertisements from two or more remote control devices 32 while scanning or listening for nearby BLE transmissions, the vehicle 10 cannot be paired with any of the available remote control devices 32 and the operator may be required to repeat the pairing process by removing the remote control device 32 from the charging station 50 and then reinserting the remote control device 32 into the charging station 50.

[0114] At 558, the remote control device 32 responds to the scan request with the unique identification code received by the BLE radio transceiver 402.

[0115] At 560, the vehicle 10 verifies the code and instructs the BLE radio transceiver 402 to open a BLE connection and start communicating with the remote control device 32.

[0116] At 562, once a communication session is established between the remote control device 32 and the charging station 50, a predetermined pairing algorithm can be implemented between the remote control device 32 and the charging station 50 to complete the pairing operation at 564. Once paired, the vehicle 10 communicates wirelessly with the remote control device 32, and the controller 103 of the vehicle 10 is capable of implementing wireless requests received from the remote control device 32.

[0117] In the example flowchart described above Figure 17 a similar method can be performed to pair the remote control device 32 with the vehicle 10 using, for example, one or more of the charging elements 220 of the charging station 50 and the charging contacts 210 of the remote control device 32 or the aforementioned dedicated pairing contacts. Instead of transmitting and receiving messages via the wireless / BLE radio transceiver, messages of the same or equivalent type can be communicated via various protocols through the elements / contacts 220 / 210. The message can be modulated and transmitted on one of the elements / contacts 220 / 210 that provides voltage. In either case, the pairing of the vehicle 10 and the remote control device 32 can occur simultaneously with the charging of the rechargeable power source 180 of the remote control device 32.

[0118] Referring to Figure 18And method 600, at 602, when the second presence contact 222 is engaged by the first presence contact 212 when the remote control device 32 is inserted into the charging station 50, the BLE radio transceiver 402 of the charging station 50 is enabled with a predetermined (e.g., 1500 ms) timeout to start scanning or listening for nearby BLE transmissions from the remote control device 32. As discussed above, the engagement of the first presence contact 212 with the second presence contact 222 can also enable the current limiter 406 such that power from the vehicle 10 can be provided from the charging element 220 to the charging contact 210, which will charge the rechargeable power source 180 of the remote control device 32. Thus, the pairing and charging operations are initiated by a single action of coupling the remote control device 32 to the charging station 50 such that the components of the remote control device 32 physically contact the elements of the charging station 50. Instead of using BLE transmissions to pair the remote control device 32 with the vehicle controller 103, the remote control device 32 can be paired with the vehicle controller 103 through direct physical contact, e.g., between the charging contact 210 and the charging element 220. Alternatively, dedicated pairing contacts (not shown) can be provided on the remote control device 32 and the vehicle 10 (e.g., at the charging station 50) to pair the remote control device 32 with the vehicle controller 103 via direct physical contact. Such pairing contacts on the remote control device 32 and the vehicle 10 can engage each other concurrently with the engagement of the charging contact 210 to the charging element 220 such that the pairing process can occur simultaneously with the charging process. These pairing contacts can be used alone to perform message exchanges for the pairing operation.

[0119] At 604, during the pairing process, the signal strength of the BLE transmission between the wireless transmitter 178 and the BLE radio transceiver 402 can be reduced to help prevent any other nearby vehicle 10 from receiving the BLE transmission from the remote control device 32.

[0120] According to one aspect of the present invention, in the case where the pairing process is completed wirelessly, at 606, the remote control device 32 detects that voltage is present at its charging contact 210 and starts transmitting BLE advertisements at a predetermined rate (e.g., 20 ms rate) with a preset timeout (e.g., 2000 ms timeout) via the wireless transmitter 178, indicating that the remote control device 32 is available for communication with nearby vehicles 10. If the BLE radio transceiver 402 of the charging station 50 is to identify two or more remote control devices 32 available for pairing, i.e., by receiving BLE advertisements from two or more remote control devices 32 while scanning or listening for nearby BLE transmissions, the vehicle 10 cannot pair with any of the available remote control devices 32 and the operator may be required to repeat the pairing process by removing the remote control device 32 from the charging station 50 and then reinserting the remote control device 32 into the charging station 50.

[0121] Before transmitting a BLE advertisement from the wireless transmitter 178, the charging station 50 may provide power to recharge the rechargeable power source 180 for up to approximately, for example, 1000 ms. The charging of the rechargeable power source 180 by the charging station 50 will be discussed in detail below.

[0122] In response to receiving a BLE advertisement from the wireless transmitter 178, at 608, the BLE radio transceiver 402 of the charging station 50 may issue a BLE scan request.

[0123] At 610, the remote control device 32 receives the scan request from the BLE radio transceiver 402 and uses the address of the BLE radio transceiver 402 to create a unique identification code, which at 612 the remote control device 32 sends back to the BLE radio transceiver 402.

[0124] At 614, the vehicle 10 verifies the code and instructs the BLE radio transceiver 402 to open a BLE connection and start communicating with the remote control device 32. It should be noted that if during step 614 the vehicle 10 receives more than one valid identification code, for example, if the vehicle 10 receives identification codes from two different remote control devices 32, then the pairing will fail, the vehicle 10 will issue an error message or other warning, and the operator will be required to repeat the pairing process by removing the remote control device 32 from the charging station 50 and then reinserting the remote control device 32 into the charging station 50.

[0125] At 616, once a communication session is established between the remote control device 32 and the charging station 50, the pairing operation can be completed, and at 618 the signal strength of the BLE transmission between the wireless transmitter 178 and the BLE radio transceiver 402 can increase and resume to its normal level.

[0126] At 620, the operator may be required to perform an action as a test to confirm that the remote control device 32 is functioning and can communicate with the charging station 50, such as by pressing a sequence of buttons on the remote control device 32, for example, by concurrently pressing the horn button 197B and the brake button 197C.

[0127] Once paired, the vehicle 10 communicates wirelessly with the remote control device 32, and the controller 103 of the vehicle 10 is capable of implementing wireless requests received from the remote control device 32.

[0128] According to aspects of the present invention, the pairing period (which is the time period taken to establish communication between the remote control device 32 and the vehicle 10, starting at step 552 / 602 and ending at step 564 / 616) may be less than the charging period (which is the time taken to charge the rechargeable power source 180 to a desired charge state at the charging station 50), where this will be described below in connection withFigure 21 and 22 discusses charging of the rechargeable power supply 180.

[0129] Referring Figure 19 , in accordance with another aspect of the present invention, after performing a work operation, the vehicle operator may need to temporarily leave the vehicle 10, e.g., to take a break. Exemplary method 700 is shown for turning off, restarting the vehicle 10, and re-pairing the vehicle 10 with the remote control device 32 used by the operator. At 702 the operator turns off the power of the vehicle 10 to take a break or the like. After a period of time, the vehicle operator turns on the power of the vehicle 10 again. During this break period, the remote control device 32 may continue to be paired with the vehicle 10 for a predefined period of time. This state of maintaining the pairing between the vehicle 10 and the remote control device 32 can be indicated, for example, on a touch screen (not shown) provided on the vehicle 10 by illuminating the LED 424 with a predefined color, pattern, etc. Thus, if at 704 the operator powers on the vehicle 10 before the expiration of the predefined period, then at 706 the vehicle 10 can detect the remote control device 32, where the remote control device 32 remains paired with the vehicle 10. At this point, the operator may or may not have to take some type of action at 708, such as by pressing a button on the vehicle 10 (e.g., on the charging station 50, on the touch screen, etc.), or by pressing a sequence of buttons on the remote control device 32.

[0130] A successful operator action at 708 results in confirmation of the pairing between the remote control device 32 and the vehicle 10 at 710. A visual queue may be displayed on the indicator (LED 424) to indicate the pairing, e.g., by illuminating the LED 424 with the second color as described above.

[0131] Alternatively, in accordance with this aspect of the present invention, if the operator powers on the vehicle 10 after the expiration of the predefined period at 712, then the operator may be required to re-pair the remote control device 32 to the vehicle 10, as in the initial pairing, e.g., by inserting the remote control device 32 into the charging station 50 at 714.

[0132] Referring Figure 20, the exemplary method 800 is shown for re - establishing communication between the remote control device 32 and the vehicle 10 after a period of time during which no vehicle - related activity has been performed. At 802, the controller 103 on the vehicle 10 detects that no vehicle - related activity has been performed within a given period of time after communication between the remote control device 32 and the vehicle 10 has been established. Exemplary vehicle - related activities include driving the vehicle 10 (either using the manual controls in the operator station 20, other manual controls (e.g., on the side of the vehicle 10) for manual driving, or via the remote control device 32), standing on the platform 21, moving or placing items on the load handling assembly 12, etc. At 804, if no vehicle - related activity has occurred within a time greater than a first predetermined amount of time after communication between the remote control device 32 and the vehicle 10 has been established, then at 806 the communication between the remote control device 32 and the vehicle 10 is terminated and must be re - established using the pairing system 34, i.e., by inserting the remote control device 32 into the charging station 50 at the vehicle 10. This terminated pairing state between the vehicle 10 and the remote control device 32 can be indicated on the touch screen, for example, by illuminating the LED 424 in a predetermined color, pattern, etc.

[0133] At 808, if no vehicle - related activity has occurred within a time less than a second predetermined amount of time after communication between the remote control device 32 and the vehicle 10 has been established, the second predetermined amount of time being equal to or less than the first predetermined amount of time, then at 810 the communication between the remote control device 32 and the vehicle 10 is terminated, but can be re - established without the pairing system 34, for example, by performing a confirmation method using the remote control device 32. The confirmation method can include, for example, the operator performing a sequence of buttons on the remote control device 32, such as by long - pressing one or more of the buttons 197A - C. This pairing state between the vehicle 10 and the remote control device 32 can be indicated on the touch screen, for example, by illuminating the LED 424 in a predetermined color, pattern, etc.

[0134] Figure 21 is a flowchart of an exemplary method 900 for charging a remote control device in accordance with the principles of the present invention. In particular, the remote control device can be the same as or similar to the remote control device 32 discussed herein and can include a wireless communication system 456 that includes a wireless transmitter 178 (e.g., capable of one - way or two - way communication), a rechargeable power source 180, and at least one control (e.g., controls 196A - C) that causes the wireless transmitter 178 to wirelessly transmit a request to the controller of the material handling vehicle 10.

[0135] Method 900 for charging remote control device 32 begins at 902 by initiating contact between a component of remote control device 32 and an element of charging station 50, which is located at vehicle 10, and then sensing the contact between the remote control device component and the charging station element. As described above, remote control device 32 may include one or more charging contacts 210, each charging contact 210 being arranged to engage a corresponding charging element 220 of charging station 50 such that when they are engaged, a second presence contact 222 or similar device engages a corresponding first presence contact 212 to detect or sense that the (one or more) charging contacts 210 and the (one or more) charging elements 220 are in contact with each other. However, other components of remote control device 32 and other elements of charging station 50 may be used to detect / sense the initiation of contact.

[0136] Next, at 904, a charging period is started, during which power is supplied from charging station 50 to rechargeable power source 180. As described above, by way of example, the circuitry of charging station 50 is configured such that after sensing contact between the (one or more) charging contacts 210 and the (one or more) charging elements 220, power is supplied from charging station 50 to charging contacts 210 of remote control device 32 to charge rechargeable power source 180. Once rechargeable power source 180 is substantially fully charged (or charged to a desired amount less than the substantially fully charged state), remote control device 32 may be removed from charging station 50.

[0137] Accordingly, Figure 21 the method continues at 906 by interrupting the contact between the remote control device component and the charging station element and sensing the interruption of the contact between the remote control device component and the charging station element. As described above, the (one or more) charging contacts 210 of remote control device 32 and the (one or more) charging elements 220 of charging station 50 are arranged such that when the two systems are disengaged, this state can be detected or sensed. An example is second presence contact 222 that can detect when remote control device 32 is removed from charging station 50.

[0138] Finally, after sensing this interruption at 906, at 908 charging station 50 may stop supplying power from charging station 50 to rechargeable power source 180, thereby ending the charging period. It should be noted that second presence contact 222 may be located on remote control device 32 and its disengagement may cause the power supply from charging station 50 to rechargeable power source 180 to stop. The power supply from charging station 50 to rechargeable power source 180 may also be stopped when rechargeable power source 180 is charged to a desired amount (either fully charged or charged to a desired amount less than fully charged), as described herein.

[0139] Method 900 may include Figure 21Other optional steps as shown. For example, method 900 may further include confirming the establishment of communication between the remote control device 32 and the vehicle 10 at 910, for example, using at least one of an auditory or visual cue. Method 900 may further include establishing communication (e.g., pairing) between the remote control device 32 and the vehicle 10 during a pairing period at 912 when a remote control device component contacts a charging station element, such that the controller 103 receives a transmission from the remote control device 32 and is able to implement a wireless request from the remote control device 32. Such communication between the remote control device 32 and the vehicle 10 may be established concurrently during charging of the rechargeable power source 180 at the charging station 50, such that the pairing period overlaps with the charging period. In at least some embodiments, the pairing period is less than or equal to the charging period.

[0140] In addition, method 900 may include, at 914, displaying the charging status of the rechargeable power source 180 at the vehicle 10 (e.g., at the charging station 50), where the charging status of the rechargeable power source 180 may be displayed at the vehicle 10 while charging the rechargeable power source 180 and during use of the remote control device 32. The charging status of the rechargeable power source 180 may be displayed, for example, via a series of lights, each light representing a level of the charging status of the rechargeable power source 180.

[0141] Figure 22 is a flowchart of another example method 950 for charging a remote control device (such as the remote control device 32 discussed herein), the remote control device including a wireless communication system 456 that includes a wireless transmitter 178 (e.g., capable of one-way or two-way communication), a rechargeable power source 180, and at least one control (e.g., controls 196A-C) that causes the wireless transmitter 178 to wirelessly transmit a request to a controller of the material handling vehicle 10. As used herein, the term "control" when used to describe a control of the remote control device 32 means including any structure capable of providing a desired function, including but not limited to buttons, switches, dials, etc.

[0142] A method 950 for charging a remote control device 32 starts at 952 by initiating contact between components of the remote control device 32 and elements of a charging station 50, which is located at a vehicle 10, and then senses the contact between the remote control device components and the charging station elements. As described above, the remote control device 32 can include one or more charging contacts 210, each charging contact 210 being arranged to engage a corresponding charging element 220 of the charging station 50 such that when they engage, a second presence contact 222 or similar device engages a corresponding presence contact 212 to detect or sense that the (one or more) charging contacts 210 and the (one or more) charging elements 220 are in contact with each other. However, other components of the remote control device 32 and other elements of the charging station 50 can be used to detect / sense the initiation of contact.

[0143] At 954, a current charging state of a rechargeable power source 180 is determined. Step 954 can be performed before or after step 952, i.e., the charging state of the rechargeable power source 180 can be communicated to the charging station 50 when the remote control device 32 is coupled to the charging station 50 and during use of the remote control device 32 by an operator, as discussed herein.

[0144] Based on the current charging state of the rechargeable power source 180 and after performing step 952, at 956, a charging period is started, during which power is supplied from the charging station 50 to the rechargeable power source 180. In one exemplary embodiment, at step 958A, if the voltage of the rechargeable power source 180 is below a voltage threshold VT, then the charging station 50 charges the rechargeable power source 180 at a higher first power level PL1. According to this embodiment, at step 958B, if the voltage of the rechargeable power source 180 is above the voltage threshold VT, then the charging station 50 charges the rechargeable power source 180 at a lower second power level PL2. In either case (i.e., at step 958A or step 958B), the resulting charging period can be approximately the same, i.e., it can take approximately the same amount of time to charge the rechargeable power source 180 from above or below the voltage threshold VT to a desired amount. Although only two power levels PL1, PL2 associated with a single voltage threshold VT are discussed herein, additional voltage thresholds and power levels can be used, where the charging period can always be approximately the same amount of time regardless of the charging level of the rechargeable power source 180 when it is inserted into the charging station 50. Additionally, an equation can be used to dynamically set the power level based on the current charging state of the rechargeable power source 180.

[0145] Once the charging period is complete (i.e., once the rechargeable power source 180 is charged to a desired amount, i.e., substantially fully charged or charged to an amount less than substantially fully charged, e.g., given the sensed temperature, if such technology exists in system 8, or if less than full charge is desired), the remote control device 32 can be removed from the charging station 50.

[0146] Accordingly, Figure 22 the method at 960 continues, interrupts the contact between the remote control device components and the charging station elements, and senses the interruption of the contact between the remote control device components and the charging station elements. As described above, the (one or more) charging contacts 210 of the remote control device 32 and the (one or more) charging elements 220 of the charging station 50 are arranged such that when the two systems are disengaged, this state can be detected or sensed. An example is the second presence contact 222 that can detect when the remote control device 32 is removed from the charging station 50.

[0147] Finally, after sensing this interruption at 960, or after the rechargeable power source 180 is charged to the desired amount, at 962 the charging station 50 can stop supplying power from the charging station 50 to the rechargeable power source 180, thus ending the charging period.

[0148] Method 950 can include Figure 22 the other optional steps shown in. For example, method 950 can further include confirming the establishment of communication between the remote control device 32 and the vehicle 10 at 964, e.g., using at least one of an auditory or visual cue. Method 950 can further include establishing communication (e.g., pairing) between the remote control device 32 and the vehicle 10 during a pairing period at 966 while the remote control device components are in contact with the charging station elements, such that the controller 103 receives transmissions from the remote control device 32 and can implement wireless requests from the remote control device 32. Such communication between the remote control device 32 and the vehicle 10 can be established concurrently during the charging of the rechargeable power source 180 at the charging station 50, such that the pairing period overlaps with the charging period. In at least some embodiments, the pairing period is less than or equal to the charging period, but the pairing period can be greater than the charging period, as will be discussed in more detail below.

[0149] In addition, method 950 can include, at 968, displaying the charging status of the rechargeable power source 180 at the vehicle 10 (e.g., at the charging station 50), where the charging status of the rechargeable power source 180 can be displayed at the vehicle 10 when charging the rechargeable power source 180 and during use of the remote control device 32. The charging status of the rechargeable power source 180 can be displayed, for example, via a series of lights, each representing a level of the charging status of the rechargeable power source 180.

[0150] According to one aspect of the present invention, the charging period can depend on the capacity of the rechargeable power source 180, the charging rate / power level supplied by the charging station 50, and / or the charging state of the rechargeable power source 180 when it is plugged into the charging station 50. Thus, when the remote control device 32 is placed in the charging station 50, a desired charging period can be achieved regardless of the current charging state of the rechargeable power source 180. For example, the current charging state of the rechargeable power source 180 can be known to the vehicle 10. For example, the charging state of the rechargeable power source 180 can be transmitted to the charging station 50 as discussed herein. The charging station 50 can be instructed, for example, by the controller 103 to supply power to the rechargeable power source 180 at different rates or levels based on the charging state of the rechargeable power source 180 when the remote control device 32 is placed in the charging station 50, such that when the remote control device 32 is placed in the charging station 50, the charging period is generally about the same regardless of the charging state of the rechargeable power source 180. For example, as discussed in step 958A / B of reference Figure 22 If the charging state of the rechargeable power source 180 is a lower first charging state, then a higher first rate / power level can be provided to the rechargeable power source 180 from the charging station 50. If the charging state of the rechargeable power source 180 is a higher second charging state, then a lower second rate / power level can be provided to the rechargeable power source 180 from the charging station 50. The resulting charging periods in both cases can be about the same time, for example within about 0.5 seconds of the desired charging period. Any number of rechargeable power source charging states and corresponding rates / power levels can be implemented such that the time required to charge the rechargeable power source 180 is within the desired charging period. Additionally, the rechargeable power source 180 can increase its service life when charging at a lower power level. Thus, an additional advantage of a consistent charging period as in the present invention is that the rechargeable power source 180 sometimes charges at a lower power level, for example when the charging state of the rechargeable power source 180 when plugged into the charging station 50 is the higher second charging state discussed above. Thus, as opposed to the case where the rechargeable power source 180 charges at a consistent, higher power level each time, charging the rechargeable power source 180 at different power levels as discussed herein can increase the service life of the rechargeable power source 180.

[0151] In addition, although the pairing period, described herein as the time period spent establishing communication between the remote control device 32 and the vehicle 10, can be less than or equal to the charging period, the charging period can also be less than the pairing period. As an example, it can be determined that the rechargeable power source 180 need not be fully charged to operate during a desired usage period. For example, a fully charged rechargeable power source 180 can provide more operating time than a desired usage period (e.g., an operator's shift), such that the rechargeable power source 180 can operate during the desired usage period without being fully charged. In such a case, the charging station 50 can be programmed to charge the rechargeable power source 180 to a state below full charge, which is sufficient for the remote control device to remain operable throughout the desired usage period. The time taken to charge the rechargeable power source 180 to this below-full charge state can be less than the pairing period. Other situations where the charging period can be less than the pairing period can also occur.

[0152] Reference Figure 23 , the principles of the present invention can also be implemented as a kit 1000 for retrofitting a material handling vehicle 10'. In Figure 23 , elements that are similar or identical to those described above with reference to Figures 1 - 22 include the same reference numerals followed by a prime ('). With respect to Figure 23 described but not specifically shown in Figure 23 , elements are equivalent to those having the same reference numerals as above but without the prime.

[0153] The vehicle 10' can include a vehicle controller 103', which responds to wireless requests from an associated remote control device 32' used by an operator interacting with the vehicle 10', similar to those types of vehicles 10 and remote control devices 32 described above. An example kit 1000 will include a charging station 50' located at the vehicle 10', a charging station 50' for charging a rechargeable power source 180' of the remote control device 32', where the charging station 50' is electrically coupled to the vehicle power source, and a receiver 102' (such as a BLE radio transceiver) communicatively coupled to the controller 103' of the vehicle 10'. In particular, the charging station 50' is configured such that the rechargeable power source 180' is charged to a desired amount (fully charged or less than fully charged as discussed herein) at the charging station 50' during a desired charging period.

[0154] The kit 1000 can also include a pairing system 34' for establishing communication between the remote control device 32' and the vehicle 10' such that the controller 103' can implement wireless requests from the remote control device 32'. The pairing system 34' can, for example, be similar to the pairing system 34 and can implement Figure 17 and / or Figure 18The (one or more) pairing algorithms detailed in. Thus, the kit 1000 may also include a pairing indicator, e.g., a visual indicator 424', which confirms the establishment of communication between the remote control device 32' and the vehicle 10'. In addition, the pairing system 34' may be configured such that the pairing period (the time period taken to establish communication between the remote control device 32' and the vehicle 10') may be less than or equal to the charging period (the time period taken to charge the rechargeable power source 180' to the required amount). The pairing period may also be greater than the charging period. The pairing system 34' may be incorporated into the charging station 50' or may be a separate component.

[0155] It is contemplated that communication between the remote control device 32' and the vehicle 10' is established concurrently during charging of the rechargeable power source 180' at the charging station 50', i.e., the pairing period and the charging period may overlap. In addition, in some embodiments, the communication between the remote control device 32' and the vehicle 10' and the charging of the rechargeable power source 180' at the charging station 50' are initiated with a single action. For example, the single action may include physically contacting a component of the remote control device (e.g., one or more charging contacts 210 as described above) with an element of the charging station (e.g., one or more corresponding charging elements 220), as described above.

[0156] The remote control device 32' used in conjunction with the kit 1000 may be the same as the remote control device 32 disclosed herein. Thus, a remote control device manufactured for use with a vehicle 10 including an integrated charging station 50 and associated components may also be used with the kit 1000 for an existing vehicle 10'.

[0157] As described above with respect to the charging station 50, the charging station 50' of the kit 1000 may also include a guiding structure 420' to align the remote control device 32' in a proper orientation for charging the rechargeable power source 180'.

[0158] The kit 1000 may also include an indicator (e.g., an LED 404', a light, or a similar structure), which may be configured to be attachable to the vehicle 10' for indicating the charging status of the rechargeable power source 180'. The indicator may indicate the charging status of the rechargeable power source 180' both when the charging station 50' is charging the rechargeable power source 180' and during use of the remote control device 32'. In some embodiments, the indicator includes a series of lights, each light representing a level of the charging status of the rechargeable power source 180'.

[0159] Kit 1000 includes at least one charging element 220' on charging station 50', which engages at least one corresponding charging contact 210' of remote control device 32'. Further, at least one of remote control device 32' or charging station 50' includes a presence contact 212' or 222', which detects whether at least one corresponding charging contact 210' and at least one charging element 220' are properly engaged with each other. If proper engagement is detected, then charging station 50' initiates transmission of power to rechargeable power source 180' of remote control device 32', and if proper engagement is not detected, then charging station 50' does not enable transmission of power to rechargeable power source 180'. In at least some embodiments, remote control device 32' includes at least two charging contacts 210' or at least four charging contacts 210', which are positioned to engage corresponding charging elements 220' on charging station 50'.

[0160] The arrangement of remote control device 32' and charging station 50' of kit 1000 is configured such that presence contact 212' or 222' indicates removal of remote control device 32' from charging station 50', which stops transmission of power from charging station 50' to rechargeable power source 180' before at least one charging contact 210' is disengaged from at least one corresponding charging element 220'. Accordingly, transmission of power from charging station 50' to rechargeable power source 180' is stopped before at least one charging contact 210' is disengaged from at least one corresponding charging element 220'.

[0161] Kit 1000 may also utilize non - contact or inductive charging, wherein rechargeable power source 180' of remote control device 32' may be charged by being in proximity to or on the surface of a compatible inductive charging station (not shown). For example, such an inductive charging station may be located in the driving or steering controls of vehicle 10' such that rechargeable power source 180' may be charged while the operator manually drives vehicle 10' from operating station 20'. Kit 1000 according to this aspect of the invention may be at least partially located in vehicle steering controls or other vehicle components that facilitate non - contact / inductive charging of rechargeable power source 180'. For example, rechargeable power source 180' may be charged by the operator gripping the driving / steering control.

[0162] Kit 1000 may utilize as described above for Figures 1 - 22Any other features and / or functions of the described remote control device 32' and charging station 50'. Note that if the vehicle 10' used with the kit 1000 was previously set up to interact with a wireless remote control device, then the controller logic in the vehicle controller 103' may need to be updated for use with the kit 1000, and a receiver already provided on the vehicle 10' (i.e., for receiving wireless requests from a remote control device used with the vehicle 10' before the kit 1000 was installed on the vehicle 10') can be turned off to be replaced with the receiver 102' of the kit 1000 (i.e., for use with the remote control device 32' associated with the kit 1000).

[0163] Now refer to Figure 24 , a remote control device 32 according to an embodiment of the present invention can be incorporated into a glove garment 1100. The use of the glove garment 1100 eliminates the need for the retention strap 190, and the first control 196A can be provided on a finger of the glove garment 1100 rather than as part of the upper housing 174, but Figure 24 the remaining components of the remote control device 32 as shown in Figures 4 - 7 can be the same or similar to the components of the remote control device 32 of Figures 4 - 7 , including the shape of the portion of the upper housing 174 that engages the charging station 50 at the vehicle 10. Thus, the charging station 50 at the vehicle 10 can be the same as the charging station 50 described above, i.e., since the charging station engaging portion of the upper housing 174 of the remote control device 32 incorporated into the glove garment 1100 can have the same dimensions as the charging station engaging portion of the upper housing 174 of the remote control device 32 in the embodiment of Figures 4 - 7 the finger-mounted remote control device 32 or the remote control device 32 incorporated into the glove garment 1100 of Figure 24 , the same charging station 50 can be used with either

[0164] If the remote control device 32 incorporated into the glove garment 1100 is used in combination with the inductive charging technology disclosed herein, then an inductive charging structure can be incorporated, for example, into the palm of the glove garment 1100. Such a charging structure in the glove garment 1100 can be used with a charging element, for example, incorporated into the steering control of a vehicle paired with the remote control device 32, in which case the rechargeable power source of the remote control device 32 can be charged while the operator is holding the steering control.

[0165] According to additional aspects of the present invention, there can be conditions and / or events that cause the vehicle 10 to become unpaired from the remote control device 32, where, as described herein, a full pairing process using the pairing system 34 can be required to re-pair the vehicle 10 with the remote control device 32. There can be other conditions or events that cause the vehicle 10 to become unpaired from the remote control device 32, where something other than a full pairing process using the pairing system 34 can be required, as described herein, to re-pair the vehicle 10 with the remote control device 32. Several exemplary use cases regarding un-pairing and re-pairing will now be described.

[0166] A first exemplary use case can occur by turning off the power of the vehicle 10. According to this first use case, the remote control device 32 is unpaired from the controller 103 and a full pairing process using the pairing system 34, as described herein, is required to re-pair the vehicle 10 with the remote control device 32. According to this exemplary first use case, whenever the vehicle 10 is powered off, a full pairing process using the pairing system 34 can be required to re-pair the remote control device 32 to the vehicle 10.

[0167] A second exemplary use case can be substantially as described above regarding Figure 19 where the vehicle operator temporarily leaves the vehicle 10, e.g., to take a break. The details of this second exemplary use case were discussed above with reference to Figure 17 and will not be repeated.

[0168] Third and fourth exemplary use cases can occur if no vehicle-related activity occurs within a first predetermined amount of time after communication is established between the remote control device 32 and the vehicle 10 (third use case), or if no vehicle-related activity occurs within a second predetermined amount of time after communication is established between the remote control device 32 and the vehicle 10 (fourth use case). The details of these third and fourth exemplary use cases were discussed above with reference to Figure 20 and will not be repeated.

[0169] In cases involving multiple remote control devices 32 and / or multiple vehicles 10, multiple exemplary use cases can occur. In a fifth exemplary use case, it is assumed that a first remote control device 32 is currently paired with a first vehicle 10, and a second remote control device 32 is currently paired with a second vehicle 10. In this fifth use case, the first remote control device 32 is inserted into the charging station 50 of the second vehicle 10. In this case, the charging station 50 of the second vehicle 10 can charge the rechargeable power supply 180 of the first remote control device 32, the first remote control device 32 can become unpaired with the first vehicle 10, and the second remote control device 32 can become unpaired with the second vehicle 10. In the fifth use case, the first remote control device 32 will not be paired with the second vehicle 10.

[0170] In a sixth exemplary use case and with reference to Figure 24 , it is assumed that the remote control device 32 is currently paired with a first vehicle 10A such that the remote control device 32 wirelessly communicates with the first vehicle 10A, and a second vehicle 10B is currently not paired with the remote control device. In this sixth use case, the remote control device 32 uses a pairing process to pair with the second vehicle 10B, for example, by inserting the remote control device 32 into the charging station 50 of the second vehicle 10B. Using this pairing process, the charging station 50 of the second vehicle 10B can charge the rechargeable power supply 180 of the remote control device 32, and the remote control device 32 can become paired with the second vehicle 10B such that the remote control device wirelessly communicates with the second vehicle 10B. This pairing process also causes the remote control device to become unpaired with the first vehicle 10A such that the remote control device no longer wirelessly communicates with the first vehicle 10A. Once the remote control device 32 is paired with the second vehicle 10B and unpaired with the first vehicle 10A, the second vehicle 10B can respond to remote requests from the remote control device 32, while the first vehicle 10A can no longer respond to remote requests from the remote control device 32.

[0171] As described above, the wireless communication system 456 of the remote control device 32 and / or the BLE radio transceiver 402 of the charging station 50 can be configured to enter a low power mode, for example, when the remote control device 32 is paired with the second vehicle 10B and / or the rechargeable power supply 180 of the remote control device 32 is being charged at the charging station 50, for example, to ensure that only remote control devices 32 within a minimum distance from the charging station 50 (corresponding to the signal strength of the communication received from the remote control device 32) are recognized as remote control devices 32 available for pairing with the second vehicle 10B.

[0172] According to the sixth exemplary use case, before the pairing process, the second vehicle 10B can be sent to a designated location (such as, for example, the operator's location, the location of the first vehicle 10A, the end of the aisle where the operator and / or the first vehicle 10A are located, a designated waiting area, etc.) by a warehouse management system WMS that communicates with the second vehicle 10B. The second vehicle 10B can be an unloaded vehicle (i.e., without a load) and is thus ready to carry the items to be picked by the operator. For example, when the first vehicle 10A is loaded with the desired amount of picked items and is ready to be sent to a different location (i.e., a location different from the current location of the vehicle 10, such as a loading dock LD or other location to which the picked items on the first vehicle 10A will be sent), the second vehicle 10B can be instructed by the warehouse management system WMS to move to the designated location. The operator can also request that the second vehicle 10B be sent to the designated location, for example, using controls on the first vehicle 10A, via headphones, etc. Once the second vehicle 10B is paired with the remote control device 32, the second vehicle 10B can no longer execute commands from the warehouse management system WMS, such that the second vehicle 10B will only implement wireless commands from the remote control device 32 paired with it.

[0173] Once the remote control device 32 is unpair ed from the first vehicle 10A, the warehouse management system WMS can send an instruction to the first vehicle 10A to move to the loading dock LD and / or another location (such as a vehicle charging station (not shown)). Using this sixth exemplary use case, the operator can quickly switch between the vehicles 10A, 10B, thus increasing work productivity and efficiency.

[0174] In the seventh exemplary use case, it is assumed that the first remote control device 32 is currently paired with the vehicle 10, while the second remote control device 32 is not paired with the vehicle. In this seventh use case, the second remote control device 32 is inserted into the charging station 50 of the vehicle 10. In this case, the charging station 50 of the vehicle 10 can charge the rechargeable power supply 180 of the second remote control device 32, the first remote control device 32 can become unpair ed from the vehicle 10, and the second remote control device 32 will not be paired with the vehicle 10.

[0175] In an eighth exemplary use case, the remote control device 32 is moved out of the range of the vehicle 10, i.e., such that the wireless transmitter 178 is no longer able to communicate with the receiver 102 for a predetermined period of time. According to the eighth use case, the remote control device 32 may become unpair ed from the vehicle 10. According to the eighth use case, if the remote control device 32 is moved back into the range of the vehicle 10 after the predetermined period of time, then the vehicle 10 may need to be turned off and restarted to pair with the remote control device 32 using the pairing system 34, including pairing with the previously paired remote control device 32 or a different remote control device 32. If the remote control device 32 is moved back into the range of the vehicle 10 within the predetermined period of time, then the vehicle 10 may not need to be turned off and restarted to pair with the previously paired remote control device 32. For example, the previously paired remote control device 32 may be re-paired with the vehicle 10 by inserting the remote control device 32 into the vehicle's charging station 50. Pairing the vehicle 10 with a different remote control device 32 may require the vehicle to be turned off and restarted, regardless of how long the previously paired remote control device 32 was outside the range of the vehicle 10.

[0176] Additional exemplary use cases regarding pairing and / or charging durations will now be described.

[0177] In a ninth exemplary use case, a desired charge state of the rechargeable power source 180 (e.g., a substantially fully charged state) may be achieved by charging the rechargeable power source 180 at the charging station 50 for five seconds or less. According to this use case, the substantially fully charged state of the rechargeable power source 180 may result in a usage period of at least eight hours for the remote control device 32.

[0178] In a tenth exemplary use case, the charging station 50 changes the power level supplied to the rechargeable power source 180 based on the charge state of the rechargeable power source 180 when the remote control device 32 is inserted into the charging station 50, as described herein with respect to Figure 22 Regardless of the charge state of the rechargeable power source 180 when the remote control device 32 is inserted into the charging station 50, the charging duration according to the tenth use case will always be approximately four seconds. Thus, a predictable charging duration is achieved.

[0179] It should be noted that the type of transmission sent by the remote control device 32 to the vehicle 10 (e.g., a request, such as a drive request) may be other types of transmissions. As an example, the transmission may include a location-based transmission that notifies the vehicle 10's controller 103 where the remote control device 32 is located relative to the vehicle 10. These types of location transmissions may be used by the controller 103, for example, to follow the remote control device 32. Thus, the vehicle 10 may follow an operator wearing, holding, or carrying the remote control device 32. As described herein, such a remote control device 32 may be charged by the charging station 50 and paired with the vehicle 10.

[0180] According to another aspect of the present invention, when the vehicle 10 is in motion, charging of the rechargeable power source 180 by the charging station 50 may be disabled. This aspect of the present invention may not apply to inductive charging of the rechargeable power source 180.

[0181] In addition, when an operator attempts to pair the remote control device 32 with the vehicle 10 that communicates with the warehouse management system WMS, the warehouse management system WMS may determine whether one or more remote control device operation checks have been performed within a predetermined time period (e.g., within the most recent 12 hours). Such operation checks may include, for example, checking to ensure the operability of the controls of the remote control device 32 (such as the horn and / or brake buttons 197B, 197C). If such operation check(s) have not been performed within the predetermined time period, then the vehicle 10 may communicate to the operator that the operation check must be performed before the remote control device 32 can be paired with the vehicle 10, i.e., the remote control device 32 is only allowed to be paired with the vehicle 10 if one or more remote control device operation checks have been performed within the predetermined time period. The operation check may be performed by the operator who implements the controls, for example, by holding down the horn and / or brake buttons 197B, 197C.

[0182] In addition, when an operator attempts to pair the remote control device 32 with the vehicle 10 that communicates with the warehouse management system WMS, the warehouse management system WMS may determine whether the operator is authorized to operate the vehicle 10 with which the operator is attempting to pair the remote control device 32. For example, a vehicle that is only used in a specific location (such as in a cold storage facility) can only be paired with a remote control device 32 that the operator will use with the vehicle at that location. As another example, an operator may be limited to operating certain vehicles. In these cases, the remote control device 32 may only be authorized to be paired with such a vehicle if these condition(s) are met.

[0183] According to one aspect of the present invention, when it is determined that the operator is standing on the platform 21 of the vehicle 10, as detected by the presence sensor 22 for example, the charging life of the rechargeable power source 180 within a given operation cycle can be increased by turning off or reducing the power consumption of one or more components of the remote control device 32 (such as components of the wireless communication system 456, including the wireless transmitter 178).

[0184] The terms "pair" and "synchronize" (as used herein and in various patents and published patent applications incorporated herein by reference) are used interchangeably herein to describe a security process whereby a wireless remote control device and a vehicle controller identify each other as valid command and response devices.

[0185] Figure 26 andFigure 27 Shown in the figure is a charging station 1050 and a remote control device 1032 constructed in accordance with yet another aspect of the present disclosure. Elements on the charging station 1050 that are substantially the same as the elements on the charging station 50 above are denoted by the same reference numerals as those used for the elements on the charging station 50. Similarly, elements on the remote control device 1032 that are substantially the same as the elements on the remote control device 1032 above are denoted by the same reference numerals as those used for the elements on the remote control device 32.

[0186] The charging station 1050 includes a docking port 1052, which may include a pocket or recess shaped to receive the remote control device 1032 such that the charging contacts 210 on the remote control device 1032 are aligned or engaged with the charging elements 220 at the charging station 1050 to effect charging of a rechargeable power source 180 that forms part of the remote control device 1032. It is also contemplated that the remote control device 1032 may also interact with the docking port 1052 to allow charging of the rechargeable power source 180 via a non-contact charging operation, such as inductive charging.

[0187] The charging station 1050 may include one or more visual indicators that convey information to an operator, which may include one or more of the following: the charging status of the rechargeable power source 180 when the remote control device 1032 is coupled to the charging station 1050, the charging status of the rechargeable power source 180 when the remote control device 1032 is removed from the charging station 1050, the pairing status between the wearable remote control device 1032 and the vehicle controller 103, and / or the physical connection of the remote control device 1032 to the charging station 1050.

[0188] In Figure 26 and Figure 27 In the embodiment shown, a first visual indicator 1060 and a second visual indicator 1070 are provided on the charging station 1050. The first visual indicator 1060 may include one or more lights, such as LEDs. As Figure 26 and Figure 27 shown, the first visual indicator 1060 may be provided near the docking port 1052 defined within the charging station 1050, which, as described above, includes a pocket or recess shaped to receive the remote control device 1032. A graphic 1034 may be provided on the remote control device 1032, adjacent to the drive button 197A also provided on the remote control device 1032, see Figure 26, the travel button 197A can cause a wireless transmitter 178 forming part of the remote control device 1032 to wirelessly transmit a request for the vehicle 10 to travel across the floor surface. The first visual indicator 1060 can be shaped to correspond to a graphic 1034 provided on the remote control device 1032 to assist a user in positioning and connecting the remote control device 1032 to the docking port 1052 of the charging station 1050. In the illustrated embodiment, when the remote control device 1032 is coupled to the charging station 1050, the graphic 1034 provided on the remote control device 1032 is shaped as an isosceles triangle facing upward, but can include any other geometric shape, image, icon, etc. Also in the illustrated embodiment, the first visual indicator 1060 is generally shaped as an isosceles triangle pointing downward, but can include any other geometric shape, image, icon, etc. The first visual indicator 1060 shaped as a downward-facing triangle provides an indication to the user of how the remote control device 1032 should be positioned relative to the docking port 1052 such that the upward-facing triangle 1034 on the remote control device 1032 is positioned adjacent to and mates with or mirrors the first visual indicator 1060.

[0189] The second visual indicator 1070 can be positioned near the first visual indicator 1070, such as Figure 26 and Figure 27 shown directly above the first visual indicator 1060. The second visual indicator 1070 can be defined by a plurality of linearly arranged lights (such as LEDs) that can be individually and continuously activated. The lights of the second visual indicator 1070 can have a different color from one or more of the lights of the first visual indicator 1060.

[0190] When the vehicle 10 including the charging station 1050 is powered on, i.e., transitions from an OFF state to an ON state, the first visual indicator 1060 can be activated and preferably pulsates ON and OFF to provide a visual display associated with inserting the wearable remote control device 1032 into the docking port 1052, while the second visual indicator 1070 remains OFF, see Figure 28A . In the case where the first visual indicator 1060 is activated, i.e., pulsates ON and OFF, and the second visual indicator 1070 is OFF, this indicates to the operator that the charging station 1050 is enabled and operational and that she / he needs to couple the remote control device 1032 to the docking port 1052 of the charging station 1050 for pairing and charging. If the first visual indicator 1060 is not activated, then this can indicate that the charging station 1050 is not enabled. Thus, the first visual indicator 1060 and the second visual indicator 1070 can be configured to be activated independently of each other such that the first visual indicator 1060 can be activated while the second visual indicator 1070 is not activated.

[0191] Once the remote control device 1032 has been physically connected to the docking port 1052 of the charging station 1050, the first visual indicator 1060 can be deactivated, i.e., turned OFF, and at least one of the lights defining the second visual indicator 1070 can be activated to communicate to the operator that the remote control device 1032 has been physically connected to the docking port 1052, see Figure 28B . Once docking of the remote control device 1032 occurs, the remote control device 1032 will attempt to pair with the vehicle controller 103 and the rechargeable power source 180 of the remote control device 1032 will begin to be charged by the charging station 1050. The lights defining the second visual indicator 1070 can be continuously activated, such as being activated from left to right as shown in Figure 26 , Figure 27 and Figure 28B to indicate the status of the charging operation of the power source 180 or the charging status when the rechargeable power source 180 is coupled to the charging station 1050. Once the rechargeable power source 180 is fully charged, all of the lights defining the second indicator 1070 can be activated, i.e., turned ON, see Figure 28C . If the rechargeable power source 180 cannot be charged, then the first visual display 1060 can flash or pulsate ON and OFF to provide a visual display indicating an error, while the second visual display 1070 is turned OFF, see Figure 28I . This error may be related to a defect in the rechargeable power source 180, the charging station 1050, or both. The rate at which the first visual indicator 1060 flashes ON and OFF to indicate an error can be different in frequency compared to the rate at which the first visual indicator 1060 pulsates ON and OFF when the vehicle 10 is powered on.

[0192] As described above, once the rechargeable power source 180 is fully charged, all of the lights of the second visual indicator 1070 can be activated. All of the lights of the second visual indicator 1070 can also pulsate to provide an intermittent display to the operator as a cue for performing an action, the action being a test such as confirming that the remote control device 1032 is operational and can communicate with the vehicle 10, i.e., that the pairing has been successful. The remote control device 1032 can also include a horn button 197B and a brake button 197C, similar to the horn and brake buttons 197B, 197C provided on the remote control device 32, see Figure 4Actions such as tests to confirm that the control device 32 is working and can communicate with the vehicle can include pressing the horn button 197B to determine whether the horn on the vehicle 10 is activated and / or pressing the brake button 197C to determine whether the brakes on the vehicle are actuated. Once the test is successfully completed, all the lights of the second visual indicator 1070 can be continuously activated to define a steady-state display. Thus, based on the information to be conveyed to the operator / user, the second visual indicator 1070 can define an intermittent display, a steady-state display, or a display that activates fewer than all the lights, i.e., a partially filled display. If the test is not successfully completed, then the first visual indicator 1060 can flash or pulsate ON and OFF to indicate an error while the second visual indicator 1070 is turned off, see Figure 28I The error may occur due to a failure to successfully pair the remote control device 1032 with the vehicle controller 103. The rate at which the first visual indicator 1060 flashes or pulsates ON and OFF to indicate that the test was not successfully completed can be different from the frequency at which the first visual indicator 1060 is pulsated ON and OFF when the vehicle 10 is powered on.

[0193] As described above, after the vehicle has been turned off and on, the rechargeable power source 180 is successfully fully charged and the test is successfully completed, all the lights of the second visual indicator 1070 can be continuously activated to define a steady-state display. If, after the rechargeable power source 180 has been successfully fully charged and the test has been successfully completed, the operation of the vehicle 10 and the remote control device 1032 causes the rechargeable power source 180 to consume some of its charge, such that the operator reconnects the remote control device 1032 to the docking port 1052 for charging before turning off the vehicle. After charging, the second visual indicator 1070 may not pulsate to prompt the operator to perform the test, even though the rechargeable power source 180 may again reach a fully charged state. Since the vehicle 10 has not been turned off and restarted since the last successful test, the second visual indicator 1070 may not pulsate to prompt the operator to perform the test again, but instead remain in its steady-state display, indicating that the rechargeable power source 180 is fully charged.

[0194] Once the rechargeable power source 180 has been fully charged and the test has been successfully completed, which indicates that the pairing has been successfully completed, the first visual indicator 1060 can remain OFF and all the lights of the second visual indicator 1070 can remain ON to define a steady-state display. When the first and second visual indicators 1060 and 1070 are in these states, see Figure 28E, this can indicate to the operator that the pairing status between the remote control device 1032 and the vehicle controller 103 is affirmative and active and that the vehicle 10 can be operated via the remote control device 1032. During operation of the vehicle 10 using the remote control device 1032, the rechargeable power source 180 will lose power over time, which will be indicated by the second visual indicator 1070, i.e., as Figure 26 , Figure 27 and Figure 28F the lights extending from right to left as shown in will be deactivated or turned off to indicate a decrease in the power level of the power source 180 when the remote control device 1032 is not coupled to the charging station 1050. When the power is low, only a single light of the second visual indicator 1070 can be activated and the first visual indicator 1060 can be turned on to provide a steady-state display, signaling to the operator that she / he needs to charge the power source 180, see Figure 28G . Thus, the first visual indicator 1060 can define an intermittent display, see Figure 28A and Figure 28I , or a steady-state display, see Figure 28G . It should also be noted that both the first and second visual indicators 1060 and 1070 provide a steady-state display when activated as shown in Figure 28G . When the power on the rechargeable power source 180 has been depleted, the second visual indicator 1070 can be turned off and the first visual indicator 1060 can pulsate to indicate to the operator that the power source 180 needs to be charged, see Figure 28H .

[0195] As described above, the rate at which the first visual indicator 1060 flashes ON and OFF to indicate an error can be a different frequency compared to the rate at which the first visual indicator 1060 pulsates ON and OFF when the vehicle 10 is powered on. For example, the error may be related to an error in the charging station 1050, causing it to be unable to charge the remote control device 1032. For example, the error may also be related to an error in the remote control device 1032 or its power source 180, causing it to be unable to receive charging from the charging station 1050. Additionally, the error may, for example, involve both the charging station 1050 and the remote control device 1032, resulting in a communication message between the two devices that is not received by the intended recipient of the communication message.

[0196] As described above, when activated, the second visual indicator 1070 can provide an intermittent display as shown in the example of Figure 28D that can indicate to the operator to perform an action, or a steady-state display as shown in the example of Figure 28E that can indicate to the operator that the remote control device 1032 is fully ready for use.

[0197] In addition, when the first visual indicator 1060 and the second visual indicator 1070 are both activated, each of the first visual indicator 1060 and the second visual indicator 1070 can provide a corresponding steady-state display as shown in the example of Figure 28G indicating that the rechargeable power source 180 has a low charge.

[0198] In the example of Figure 28A the first visual indicator 1060 can pulsate as a way of defining a visual display associated with inserting the wearable remote control device 1032 into the charging station 1050.

[0199] As described above, Figure 28I the example of

[0200] includes a flashing first visual indicator to provide a display indicating that some error has occurred. This is merely an example, and more generally, at least one embodiment of the present disclosure anticipates that the first visual indicator 1060 or the second visual indicator 1070 can provide, either alone or in combination with each other, a visual display related to a charging error that occurs at the charging station 1050 or the rechargeable power source 108. Figure 28I As described above,

[0201] the example of Figure 28I includes a flashing first visual indicator 1060 to provide a display indicating that some error has occurred. This is merely an example, and more generally, at least one embodiment of the present disclosure anticipates that the first visual indicator 1060 or the second visual indicator 1070 can provide, either alone or in combination with each other, a visual display related to a pairing error that occurs between the wearable remote control device 1032 and the vehicle 10. As previously mentioned, the term "pairing" (as used herein) describes the secure process by which the wireless remote control device 1032 and the vehicle controller 10 recognize each other as valid command and response devices. A pairing error can occur when the two devices initially attempt to pair with each other but fail, or a pairing error can occur after successful pairing, resulting in the pairing being interrupted or lost in some way.

[0202] As described above, in at least one embodiment according to the present disclosure, with reference toFigure 17 and method 550, at 552, when a second presence contact 222 is engaged by a first presence contact 212 when the remote control device 32 is inserted into the charging station 50, the BLE radio transceiver 402 of the charging station 50 is enabled to start scanning or listening for nearby BLE transmissions. As described above, the engagement of the first presence contact 212 with the second presence contact 222 can also enable the current limiter 406 such that power from the vehicle 10 can be provided from the charging element 220 to the charging contact 210, which will charge the rechargeable power source 180 of the remote control device 32. Thus, the pairing and charging operations can be initiated by a single action of coupling the remote control device 32 to the charging station 50. Instead of using BLE transmissions to pair the remote control device 32 with the vehicle controller 103, the remote control device 32 can be paired with the vehicle controller 103 through direct physical contact, for example, between the charging contact 210 and the charging element 220. Alternatively, dedicated pairing contacts (not shown) can be provided on the remote control device 32 and the vehicle 10, for example, at the charging station 50, to pair the remote control device 32 with the vehicle controller 103 via direct physical contact. Such pairing contacts on the remote control device 32 and the vehicle 10 can engage with each other while the charging contact 210 is engaged with the charging element 220, such that the pairing process can occur simultaneously with the charging process. These pairing contacts can be used alone for message exchange for performing the pairing operation.

[0203] As described above in at least one other embodiment according to the present disclosure, refer to Figure 26 , once the remote control device 1032 has been physically connected to the docking port 1052 of the charging station 1050, the first visual indicator 1060 can be deactivated, i.e., turned off, and at least one of the lights defining the second visual indicator 1070 can be activated to convey to the operator that the remote control device 1032 has been physically connected to the docking port 1052, see Figure 28B . Once the docking of the remote control device 1032 occurs, the remote control device 1032 will attempt to pair with the vehicle controller 103 and the rechargeable power source 180 of the remote control device 1032 will start to be charged by the charging station 1050. Once the rechargeable power source 180 is fully charged, all of the lights defining the second indicator 1070 can be activated, i.e., turned on, see Figure 28C .

[0204] The remote control device 1032 can also include a drive button 197A that, when pressed, causes the wireless transmitter 178 to wirelessly transmit a request for the vehicle 10 to travel across the floor surface, and is similar to the drive button 197A provided on the remote control device 32, see Figure 4。The remote control device 1032 may also include a horn button 197B and a brake button 197C, similar to the horn and brake buttons 197B, 197C provided on the remote control device 32, see Figure 4 。After the rechargeable power supply 180 is fully charged, all the lights of the second visual indicator 1070 can be activated by pulsation to provide an intermittent display to the operator as a hint for performing an action, as a test to confirm that the remote control device 1032 is functioning and can communicate with the vehicle 10, i.e., the pairing has been successful. The actions for testing that the remote control device 32 is functioning and can communicate with the vehicle may include pressing the drive button 197A to see if the vehicle 10 moves, pressing the horn button 197B to determine if the horn on the vehicle 10 is activated, and / or pressing the brake button 197C to determine if the brakes on the vehicle are actuated. Once the test is successfully completed, all the lights of the second visual indicator 1070 can be continuously activated to define a steady-state display.

[0205] The buttons 197A - 197C may sometimes wear and / or fail. Therefore, the above button test can also be performed to test these buttons 197A - 197C to verify if they are working correctly, i.e., without defects.

[0206] According to an embodiment of the present disclosure, the buttons 197A - 197C can be tested by the operator pressing the following button sequence: the drive button 197A, then one of the horn button 197B or the brake button 197C, and then the other of the horn button 197B or the brake button 197C. The example sequence just described has three different steps; however, the sequence can be shortened to two steps by the operator pressing the horn button 197B and the brake button 197C simultaneously after first pressing the drive button 197A. The buttons 197A - 197C generate signals or inputs received by the vehicle controller 103 when pressed or actuated, and the vehicle controller 103 may include a processor as described above.

[0207] According to an embodiment of the present disclosure, there may be a timeout limit applied to the button press sequence such that for a test to be considered successful, the operator has a limited time to press the next button in the sequence (including the first button). If the test is considered unsuccessful, then the sequence may need to be restarted from the beginning.

[0208] One advantage of the example button press sequence described above is the operator's flexibility and the reduced likelihood of erroneously failing the button test due to time constraints caused by the inability to simultaneously press buttons 197B and 197C in situations such as when the operator is wearing thick gloves and in cold storage areas with poor dexterity. Additionally, once it is detected that the remote control device 32 or 1032 is connected to the charging station 50 or 1050, the drive button 197A is purposefully selected as the first button to be tested. Since the drive button 197A is the main button used during the operation of the vehicle 10, the example sequence can help the operator build muscle memory regarding the drive button 197A. Moreover, another beneficial aspect of making the drive button 197A the first button to be pressed is that it helps eliminate the possibility of accidental vehicle movement. For example, if pressing the drive button 197A is the last step in the sequence and the operator continues to press the drive button 197A after the button test is successfully completed, the vehicle 10 may accidentally move as a result.

[0209] Thus, as just described, the example button test or button press sequence during vehicle 10 startup can be flexible and include first pressing the drive button 197A and then either a) simultaneously, or b) sequentially in any order, pressing the other two buttons 197B and 197C. In the example above, the horn button 197B is provided only as an example of a button for operating a functional element or auxiliary function of the vehicle 10. For example, button 197B may not operate the horn, but may instead operate an auxiliary function related to the forks of the vehicle 10 in order to lower or raise them, tilt them, or perform another operation involving the forks. Additionally, according to embodiments of the present disclosure, the remote control device 32 or 1032 is not limited to just two buttons in addition to the drive button 197A. For example, in addition to the drive button 197A, there may be three additional buttons on the remote control device 32 or 1032, each corresponding to an operating element or auxiliary function of the vehicle 10, such as a brake, horn, forks, etc. In such an example embodiment, the button test or button press sequence during vehicle 10 startup can be flexible and include first pressing the drive button 197A and then sequentially pressing the other buttons in any order, or possibly, simultaneously pressing at least two or all of the buttons.

[0210] As described above, there may be time limits applied to button press sequences to determine whether a button test procedure has been successful. Once the remote control device 32 or 1032 is first inserted into the charging station 50 or 1050, the operator may be required to press the drive button 197A within a first predetermined time period, such as, for example, 1 to 5 seconds. Thus, the vehicle controller 103 may wait to receive an input from the drive button 197A until after the remote control device 32 or 1032 is coupled to the charging station 50 or 1050. Then, it may be required to press the next or second button in the sequence (i.e., any one of the auxiliary function buttons, sequentially or simultaneously) within a second predetermined time period, such as, for example, 1 to 5 seconds. It may be required to press the third or fourth button in the sequence within a third or fourth predetermined time period (each predetermined time period including, for example, 1 to 5 seconds). Although not required, there may be a further predetermined time period that defines a threshold for the time limit within which the entire sequence must be completed, such as, for example, 10 to 20 seconds. For example, if the operator is pressing one of the buttons but the button is inoperable, or if the operator is unable to press the button due to other environmental factors, then these time limits may be exceeded. In either case, the display 1080 on the vehicle 10 (see Figure 26 ) may be controlled by the vehicle controller 103 to indicate to the operator that the button press test was not successful, such that the operator should restart the sequence from the beginning. For example, the display 1080 may indicate or display "Button test failed" to let the operator know that the test was not successful. The vehicle may not be operable via the remote control device 32 or 1032 until the button press sequence, i.e., the button test, has been successfully completed. However, if the button press sequence is successfully completed, then the vehicle display 1080 may be controlled by the controller 103 to notify the operator with an appropriate message or other visual display, such as, for example, "Button test successful". The successful completion of the button press sequence confirms that the remote control device 1032 is functional and can communicate with the vehicle 10, i.e., the pairing has been successful. The successful completion of the button press sequence also indicates that all of the buttons 197A - 197C are operable.

[0211] The above-described button test or button press sequence may be monitored or controlled by the vehicle controller 103.

[0212] Thus, generally speaking, an embodiment according to the present disclosure relates to a method for testing the operating characteristics of a remote control device associated with a material handling vehicle. The method includes a processor (such as vehicle controller 103) waiting to receive a first input indicating that a first button of the remote control device has been pressed, where the first button includes a travel button of the remote control device; and the processor waiting to receive a second input indicating that at least a second button of the remote control device has been pressed after receiving the first input, where the second button is related to a first auxiliary vehicle function of the remote control device. The method further includes the processor determining whether a predetermined button press sequence is successful based at least in part on the receipt or non-receipt of the first input and the second input; and then the processor driving a display on the vehicle to provide a visual indication of whether the button press sequence is successful or unsuccessful based on the determination.

[0213] The invention of the present application has been described in such detail and with reference to the embodiments of the present application that it is obvious that modifications and variations are possible without departing from the scope of the invention defined in the appended claims.

Claims

1. A method for testing the operating characteristics of a remote control device associated with a material handling vehicle, comprising: waiting, by a processor, to receive a first input indicating that a first button of the remote control device has been pressed, wherein the first button includes a travel button of the remote control device; waiting, by the processor, to receive a second input indicating that at least a second button of the remote control device has been pressed after receiving the first input, wherein the second button is associated with a first auxiliary vehicle function; determining, by the processor, whether a predetermined button press sequence is successful based at least in part on receiving or not receiving the first input and the second input; and driving, by the processor, a display on the vehicle to provide a visual indication of whether the button press sequence is successful or unsuccessful based on the determination.

2. The method according to claim 1, wherein the determination is based at least in part on the processor determining whether the second input is received within a predetermined time period after receiving the first input.

3. The method according to any one of claims 1 or 2, further comprising: detecting, by the processor, that the remote control device is connected to a vehicle charging station before waiting to receive the first input or the second input.

4. The method according to claim 3, wherein the determination is based at least in part on the processor determining whether the first input is received within a predetermined time period after detecting that the remote control is connected to the charging station.

5. The method according to any one of claims 1-4, wherein the first auxiliary function is associated with one of the operation of a vehicle horn, a vehicle brake, or vehicle forks.

6. The method according to any one of claims 1-5, wherein the second input indicates that at least a second button and a third button of the remote control device have been pressed simultaneously, wherein the third button is associated with a second auxiliary vehicle function.

7. The method according to claim 6, wherein the first auxiliary function is associated with one of the operation of a vehicle horn, a vehicle brake, or vehicle forks, and the second auxiliary function is associated with a different one of the operation of a vehicle horn, a vehicle brake, or vehicle forks.

8. The method according to any one of claims 1-7, further comprising: waiting, by the processor, to receive a third input indicating that at least a third button of the remote control device has been pressed after receiving the first input and the second input, wherein the third button is associated with a second auxiliary vehicle function; and determining, by the processor, whether a predetermined button press sequence is successful based at least in part on receiving or not receiving the first input, the second input, and the third input.

9. The method according to claim 8, wherein the determination is based at least in part on the processor determining whether the third input is received within a predetermined time period after receiving the second input.

10. The method according to any one of claims 1-9, wherein the predetermined button press sequence includes that the travel button of the remote control device is the first button pressed.

11. A system for testing the operating characteristics of a remote control device associated with a material handling vehicle, comprising: a memory device storing executable instructions; and a processor communicatively coupled to the memory device, wherein the processor, when executing the executable instructions: waits to receive a first input indicating that a first button of a remote control device has been pressed, wherein the first button includes a drive button of the remote control device; after receiving the first input, waits to receive a second input indicating that at least a second button of the remote control device has been pressed, wherein the second button is associated with a first auxiliary vehicle function; determines whether a predetermined button press sequence is successful based at least in part on whether the first input and the second input are received or not received; and drives a display on the vehicle to provide a visual indication of whether the button press sequence is successful or unsuccessful based on the determination.

12. The system of claim 11, wherein the determination is based at least in part on determining whether the second input is received within a predetermined time period after receiving the first input.

13. The system of any one of claims 11 or 12, wherein the processor, when executing the executable code: before waiting to receive the first input or the second input, detects that the remote control device is connected to a vehicle charging station.

14. The system of claim 13, wherein the determination is based at least in part on determining whether the first input is received within a predetermined time period after detecting that the remote control is connected to the charging station.

15. The system of any one of claims 11-14, wherein the first auxiliary function is associated with one of a vehicle horn, a vehicle brake, or a lift of a vehicle fork.

16. The system of any one of claims 11-15, wherein the second input indicates that at least a second button and a third button of the remote control device have been pressed simultaneously, wherein the third button is associated with a second auxiliary vehicle function.

17. The system of claim 16, wherein the first auxiliary function is associated with one of a vehicle horn, a vehicle brake, or a lift of a vehicle fork, and the second auxiliary function is associated with a different one of a vehicle horn, a vehicle brake, or a lift of a vehicle fork.

18. The system of any one of claims 11-17, wherein the processor, when executing the executable code: after receiving the first input and the second input, waits to receive a third input indicating that at least a third button of the remote control device has been pressed, wherein the third button is associated with a second auxiliary vehicle function; and determines whether a predetermined button press sequence is successful based at least in part on whether the first input, the second input, and the third input are received or not received.

19. The system of claim 18, wherein the determination is based at least in part on determining whether the third input is received within a predetermined time period after receiving the second input.

20. The system of any one of claims 11-19, wherein the predetermined button press sequence includes that the drive button of the remote control device is the first button pressed.

Images