On-board charging station for a remote control device

BACKGROUND

Materials handling vehicles are commonly used for picking stock 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 control structures for controlling operation and movement of the vehicle.

In a typical stock picking operation, an operator fills orders from available stock items that are located in storage areas provided along one or more aisles of a warehouse or distribution center. The operator drives the vehicle between various pick locations where item(s) are to be picked. The operator may drive the vehicle either by using the control structures on the vehicle, or via a wireless remote control device that is associated with the vehicle, such as the remote control device disclosed in commonly owned U.S. Pat. No. 9,082,293, the entire disclosure of which is hereby incorporated by reference herein.

SUMMARY

In accordance with a first aspect, a system is provided comprising: a materials handling vehicle; a wearable remote control device comprising: a wireless communication system including a wireless transmitter; and a rechargeable power source; a receiver at the vehicle for receiving transmissions from the wireless transmitter; a controller at the vehicle that is communicably coupled to the receiver, the controller being responsive to receipt of the transmissions from the remote control device; and a charging station at the vehicle. The charging station may charge the rechargeable power source of the wearable remote control device. The charging station may comprise a visual indicator configured to indicate one or more of: a charging state of the rechargeable power source when coupled to the charging station, a charging state of the rechargeable power source when removed from the charging station, a pairing status between the wearable remote control device and the vehicle controller, or that the remote control device is physically connected to the charging station.

The visual indicator may display a first color when the remote control device is attached to the charging station. The visual indicator may display a second color when the remote control device has been paired to the vehicle controller.

The visual indicator may provide one of a flash display or a fully filled display.

The visual indicator may provide a visual indication as a cue for an operator to perform an action. The action may be a test to confirm that the remote control device is functional and can communicate with the vehicle.

The visual indicator may define a first visual indicator, and the charging station may further comprise a second visual indicator. The first visual indicator and the second visual indicator may be configured to be activated independently of each other such that either the first visual indicator is activated while the second visual indicator is not activated or the second visual indicator is activated while the first visual indicator is not.

The first visual indicator when activated may provide one of an intermittent display or a steady-state display.

The intermittent display may be operational at a first pulsing rate or a second pulsing rate, wherein the first and second rates vary in frequency.

The second visual indicator when activated may provide one of an intermittent display, a partially filled display or a steady-state display.

The first visual indicator and the second indicator may be configured to be concurrently activated.

The first visual indicator may be located proximate to a docking port of the charging station configured to receive the wearable remote control device and may be shaped to correspond to a graphic provided on the wearable remote control device to aid a user in positioning and connecting the wearable remote control device to the docking port of the charging station.

The first visual indicator may define a visual display related to inserting the wearable remote control device into the charging station.

The first or second visual indicators either individually or in combination with one another may provide a visual display related to the charging station being enabled or disabled.

The first or second visual indicators either individually or in combination with one another may provide a visual display related to a charging error occurring with the charging station or the rechargeable power source.

The first or second visual indicators either individually or in combination with one another may provide a visual display related to a pairing error occurring between the wearable remote control device and the vehicle.

The first or second visual indicators either individually or in combination with one another may provide a visual display related to a communication error occurring between the wearable remote control device and the controller.

When the vehicle is turned on, the first indicator may pulse until the remote control device is connected to a docking port of the charging station such that the first indicator is turned OFF when the remote control device is connected to the docking port.

When the vehicle is turned on, the first indicator pulses until the remote control device is connected to a docking port of the charging station, changes to a steady state ON display after the remote control device is connected to the docking port and remains ON providing the steady state ON display until the rechargeable power source is fully charged.

In accordance with a second aspect, a method is provided for coupling a wearable remote control device to a charging station, wherein the wearable remote control device may comprise a wireless transmitter, a rechargeable power source, and at least one control causing the wireless transmitter to wirelessly transmit a request to a controller of a materials handling vehicle; and wherein the materials handling vehicle may comprise a receiver for receiving transmissions from the wireless transmitter. The controller may be communicably coupled to the receiver and may be responsive to receipt of the transmissions from the remote control device. The charging station may be configured for charging the rechargeable power source of the wearable remote control device and may comprise a visual indicator. The method may comprise: displaying, by the visual indicator, an indication of one or more of: a charging state of the rechargeable power source when coupled to the charging station, a charging state of the rechargeable power source when removed from the charging station, a pairing status between the wearable remote control device and the vehicle controller, or that the remote control device is physically connected to the charging station.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIGS. 1 and 2 are side and top views of a materials handling vehicle capable of remote wireless operation according to various aspects of the present invention;

FIG. 2A is a side view of another materials handling vehicle capable of remote wireless operation according to various aspects of the present invention;

FIG. 3 is a schematic diagram of several components of a materials handling vehicle capable of remote wireless operation according to various aspects of the present invention;

FIGS. 4-7 are views of a remote control device according to various aspects of the present invention;

FIGS. 8A and 8B are cut away views showing a remote control device being engaged with a charging station according to various aspects of the present invention;

FIGS. 9 and 10 are views of another remote control device according to various aspects of the present invention;

FIG. 11 is a schematic diagram of several components of a charging station according to various aspects of the present invention;

FIGS. 12-14 are views showing a remote control device and a charging station according to various aspects of the present invention;

FIG. 15 is a schematic diagram of several components of a remote control device according to various aspects of the present invention;

FIG. 16 depicts a method according to various aspects of the present invention;

FIG. 17 depicts a pairing method according to various aspects of the present invention;

FIG. 18 depicts another pairing method according to various aspects of the present invention;

FIG. 19 depicts a method to re-pair a vehicle and a remote-control device according to various aspects of the present invention;

FIG. 20 depicts a method to reestablish communication between a vehicle and a remote-control device according to various aspects of the present invention;

FIG. 21 depicts a method to charge a remote control device according to various aspects of the present invention;

FIG. 22 depicts another method to charge a remote control device according to various aspects of the present invention;

FIG. 23 is a schematic diagram of several components of a kit according to various aspects of the present invention;

FIG. 24 is a view of another remote control device according to various aspects of the present invention;

FIG. 25 is a schematic diagram illustrating various aspects of the present invention;

FIGS. 26 and 27 illustrate a remote control device and a charging station constructed in accordance with a further embodiment;

FIGS. 28A-28I illustrate various states for first and second visual indicators of the charging station of FIGS. 26 and 27; and

FIGS. 29A-29C illustrate various states for first and second visual indicators of the charging station of FIGS. 26 and 27.

DETAILED DESCRIPTION

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

Low Level Order Picking Truck

Referring now to the drawings, and particularly to FIGS. 1 and 2, a materials handling vehicle 10, which is illustrated as a low level order picking truck, includes a load handling assembly 12 that extends from a power unit 14. The vehicle 10 forms part of a system 8 according to aspects of the invention, which system 8 will be more fully described below. The load handling assembly 12 includes a pair of forks 16, each fork 16 having a load supporting wheel assembly 18. The load handling assembly 12 may include other load handling features in addition to, or in lieu of the illustrated arrangement of the forks 16, such as a load backrest, scissors-type elevating forks, outriggers or separate height adjustable forks, as a few examples. Still further, the load handling assembly 12 may include load handling features such as a mast, a load platform, a collection cage or other support structure carried by the forks 16 or otherwise provided for handling a load supported and carried by the vehicle 10. While the present disclosure is made with reference to the illustrated vehicle 10, it will be apparent to those of skill in the art that the vehicle 10 may comprise a variety of other industrial vehicles, such as a forklift truck, a reach truck, etc., and that the following description of the invention with reference to the Figures should not be limited to an order picking truck unless otherwise specified. Additionally, the vehicle 10 may be implemented in other formats, styles and features, including a vehicle 10 that does not include a load handling assembly, such as a tugger vehicle, etc.

The illustrated power unit 14 comprises a step-through operator's station 20 dividing a first end section of the power unit 14 (opposite the forks 16) from a second end section (proximate the forks 16). The operator's station 20 includes a platform 21 upon which an operator may stand to drive the vehicle 10 and/or to provide a position from which the operator may operate various included features of the vehicle 10.

Presence sensors 22 (see FIG. 2) may be provided to detect the presence of an operator on the vehicle 10. For example, presence sensors 22 may be located on, above or under the platform 21, or otherwise provided about the operator's station 20. In the exemplary vehicle 10 of FIG. 2, the presence sensors 22 are shown in dashed lines indicating that they are positioned underneath the platform 21. Under this arrangement, the presence sensors 22 may comprise load sensors, switches, etc. As an alternative, the presence sensors 22 may be implemented above the platform 21, such as by using ultrasonic, capacitive or other suitable sensing technology. The utilization of presence sensors 22 will be described in greater detail herein.

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

The remote control device 32 is manually operable by an operator, e.g., by pressing a button or other control, to cause the remote control device 32 to wirelessly transmit at least a first type signal designating a travel request to a vehicle 10 that is paired to the remote control device 32. The travel request is a command that requests the vehicle 10 to travel, as will be described in greater detail herein. Although the remote control device 32 is illustrated in FIGS. 1 and 2 as a finger-mounted structure, numerous implementations of the remote control device 32 may be implemented, including for example, a glove structure, a lanyard or sash mounted structure, etc. Still further, the vehicle 10 and the remote control device 32 may comprise any additional and/or alternative features or implementations, examples of which are disclosed in U.S. Provisional Patent Application Ser. No. 60/825,688, filed Sep. 14, 2006, entitled “SYSTEMS AND METHODS OF REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE;” U.S. patent application Ser. No. 11/855,310, filed Sep. 14, 2007, entitled “SYSTEMS AND METHODS OF REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE” now U.S. Pat. No. 9,082,293; U.S. patent application Ser. No. 11/855,324, filed Sep. 14, 2007, entitled “SYSTEMS AND METHODS OF REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE” now U.S. Pat. No. 8,072,309; U.S. Provisional Patent Application Ser. No. 61/222,632, filed Jul. 2, 2009, entitled “APPARATUS FOR REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE;” U.S. patent application Ser. No. 12/631,007, filed Dec. 4, 2009, entitled “MULTIPLE ZONE SENSING FOR MATERIALS HANDLING VEHICLES” now U.S. Pat. No. 9,645,968; U.S. Provisional Patent Application Ser. No. 61/119,952, filed Dec. 4, 2008, entitled “MULTIPLE ZONE SENSING FOR REMOTELY CONTROLLED MATERIALS HANDLING VEHICLES;” and/or U.S. Pat. No. 7,017,689, issued Mar. 28, 2006, entitled “ELECTRICAL STEERING ASSIST FOR MATERIAL HANDLING VEHICLE”; the entire disclosures of which are each hereby incorporated by reference herein. Additional details in connection with the remote control device 32 will be discussed in detail below.

The vehicle 10 also comprises one or more contactless obstacle sensors 40, which are provided about the vehicle 10, e.g., towards the first end section of the power unit 14 as shown in FIGS. 1 and 2. The obstacle sensors 40 are operable to define at least one detection zone. For example, at least one detection zone may define an area at least partially in front of a forward traveling direction of the vehicle 10 when the vehicle 10 is traveling in response to a wirelessly received travel request from the remote control device 32, as will also be described in greater detail herein.

The obstacle sensors 40 may comprise 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 objects/obstacles or are capable of generating signals that can be analyzed to detect the presence of objects/obstacles within the predefined detection zone(s). In the exemplary embodiment illustrated in FIGS. 1 and 2, the vehicle 10 includes a first obstacle detector 42 and a pair of second obstacle detectors 44A and 44B mounted to the power unit 14. The first obstacle detector 42 is spaced apart from the second obstacle detectors 44A and 44B along a vertical axis VA of the vehicle 10 defining a vertical direction, i.e., the second obstacle detectors 44A and 44B are located below (closer to the ground than) the first obstacle detector 42, see FIG. 1. The second obstacle detectors 44A and 44B are spaced apart from each other along a horizontal axis HA of the vehicle 10 defining a horizontal direction, see FIG. 2.

The first obstacle detector 42 may comprise a sweeping laser sensor capable of detecting objects, for example, in first, second, and third zones Z₁, Z₂, Z₃(also referred to herein as scan zones or detection zones), which first, second, and third zones Z₁, Z₂, Z₃may comprise planar zones, see FIGS. 1 and 2. The second zone Z₂may comprise a “stop zone”, and the first and third zones Z₁and Z₃may comprise left and right “steer bumper zones”, such as the stop zone and the left and right steer bumper zones described in U.S. Pat. No. 8,452,464, issued May 28, 2013, entitled “STEER CORRECTION FOR A REMOTELY OPERATED MATERIALS HANDLING VEHICLE”, the entire disclosure of which is incorporated by reference herein. It is noted that the first obstacle detector 42 may be capable of detecting objects in additional or fewer zones than the three zones Z₁, Z₂, Z₃illustrated. In one exemplary detection zone configuration, any or all of the detection zones may be used as disclosed in U.S. Pat. No. 9,002,581 issued Apr. 7, 2015 and entitled “OBJECT TRACKING AND STEER MANEUVERS FOR MATERIALS HANDLING VEHICLES”, the entire disclosure of which is incorporated by reference herein.

The second obstacle detectors 44A and 44B may comprise point laser sensors that are capable of detecting objects between one or more of the zones Z₁, Z₂, Z₃of the first obstacle detector 42 and the vehicle 10, i.e., underneath one or more of the zones Z₁, Z₂, Z₃, as illustrated in FIG. 1, and/or past the zones Z₁, Z₂, Z₃, and are preferably capable of at least detecting objects underneath the second zone Z₂. The second obstacle detectors 44A and 44B are thus capable of detecting objects located in a non-detect zone DZ of the first obstacle detector 42, see FIG. 1, i.e., which non-detect zone DZ is defined as an area below the zones Z₁, Z₂, Z₃and thus not sensed by the first obstacle detector 42. Hence, the first obstacle detector 42 functions to detect objects located along a path of travel of the power unit 14 beyond the non-detect zone DZ, while the second obstacle detectors 44A and 44B function to sense objects along the path of travel of the power unit 14 in the non-detect zone DZ, which is located just in front of the vehicle 10, as shown in FIG. 1.

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

The vehicle 10 shown in FIGS. 1 and 2 further includes a charging station 50 that comprises an additional component of the system 8 and that is provided for charging a rechargeable power source of the remote control device 32. Additional details in connection with the charging station 50 will be described below.

Control System for Remote Operation of a Low Level Order Picking Truck

Referring to FIG. 3, a block diagram illustrates a control arrangement for integrating remote control commands with the vehicle 10. A receiver 102, which may be a Bluetooth Low Energy (BLE) radio, for example, is provided for receiving commands issued by the remote control device 32. The receiver 102 passes the received control signals to a controller 103, which implements the appropriate response to the received commands and may thus also be referred to herein as a master controller. In this regard, the controller 103 is implemented in hardware and may also execute software (including firmware, resident software, micro-code, etc.). Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon. For example, the vehicle 10 may include memory that stores the computer program product, which, when implemented by a processor of the controller 103, implements steer correction as described more fully herein.

Thus, the controller 103 may define, at least in part, a data processing system suitable for storing and/or executing program code and may include at least one processor coupled directly or indirectly to memory elements, e.g., through a system bus or other suitable connection. The memory elements can include local memory employed during actual execution of the program code, memory that is integrated into a microcontroller or application specific integrated circuit (ASIC), a programmable gate array or other reconfigurable processing device, etc.

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

In an exemplary arrangement, the remote control device 32 is operative to wirelessly transmit a control signal that represents a first type signal such as a travel command to the receiver 102 on the vehicle 10. The travel command is also referred to herein as a “travel signal”, “travel request” or “go signal”. The travel request is used to initiate a request to the vehicle 10 to travel, e.g., for as long as the travel signal is received by the receiver 102 and/or sent by the remote control device 32, by a predetermined amount, e.g., to cause the vehicle 10 to advance or jog in a first direction by a limited travel distance, or for a limited time. The first direction may be defined, for example, by movement of the vehicle 10 in a power unit 14 first, i.e., forks 16 to the back, direction. However, other directions of travel may alternatively be defined. Moreover, the vehicle 10 may be controlled to travel in a generally straight direction or along a previously determined heading. Correspondingly, the limited travel distance may be specified by an approximate travel distance, travel time or other measure.

Thus, a first type signal received by the receiver 102 is communicated to the controller 103. If the controller 103 determines that the travel signal is a valid travel signal and that the current vehicle conditions are appropriate (explained in greater detail in U.S. Pat. No. 9,082,293, which is already incorporated by reference herein), the controller 103 sends a signal to the appropriate control configuration of the vehicle 10 to advance and then stop the vehicle 10. Stopping the vehicle 10 may be implemented, for example, by either allowing the vehicle 10 to coast to a stop or by initiating a brake operation to cause the vehicle 10 to brake to a stop.

As an example, the controller 103 may be communicably coupled to a traction control system, illustrated as a traction motor controller 106 of the vehicle 10. The traction motor controller 106 is coupled to a traction motor 107 that drives at least one steered wheel 108 of the vehicle 10. The controller 103 may communicate with the traction motor controller 106 so as to accelerate, decelerate, adjust and/or otherwise limit the speed of the vehicle 10 in response to receiving a travel request from the remote control device 32. The controller 103 may also be communicably coupled to a steer controller 112, which is coupled to a steer motor 114 that steers at least one steered wheel 108 of the vehicle 10. In this regard, the vehicle 10 may be controlled by the controller 103 to travel an intended path or maintain an intended heading in response to receiving a travel request from the remote control device 32.

As yet another illustrative example, the controller 103 may be communicably coupled to a brake controller 116 that controls vehicle brakes 117 to decelerate, stop or otherwise control the speed of the vehicle 10 in response to receiving a travel request from the remote control device 32. Still further, the controller 103 may be communicably coupled to other vehicle features, such as main contactors 118, and/or other outputs 119 associated with the vehicle 10, where applicable, to implement desired actions in response to implementing remote travel functionality.

According to various aspects of the present invention, the controller 103 may communicate with the receiver 102 and with the traction motor controller 106 to operate the vehicle 10 under remote control in response to receiving travel commands from the associated remote control device 32. Moreover, the controller 103 may be configured to perform various actions if the vehicle 10 is traveling under remote control in response to a travel request and an obstacle is detected in one or more of the detection zone(s) Z₁, Z₂, Z₃. In this regard, when a travel signal is received by the controller 103 from the remote control device 32, any number of factors may be considered by the controller 103 to determine whether the received travel signal should be acted upon to initiate and/or sustain movement of the vehicle 10.

Correspondingly, if the vehicle 10 is moving in response to a command received by the remote control device 32, the controller 103 may dynamically alter, control, adjust or otherwise affect the remote control operation, e.g., by stopping the vehicle 10, changing the steer angle of the vehicle 10, or taking other actions. Thus, the particular vehicle features, the state/condition of one or more vehicle features, vehicle environment, etc., may influence the manner in which the controller 103 responds to travel requests from the remote control device 32.

The controller 103 may refuse to acknowledge a received travel request depending upon predetermined condition(s), e.g., that relate to environmental or operational factor(s). For example, the controller 103 may disregard an otherwise valid travel request based upon information obtained from one or more of the sensors 22, 40. As an illustration, according to various aspects of the present invention, the controller 103 may optionally consider factors such as whether an operator is on the vehicle 10 when determining whether to respond to a travel command from the remote control device 32. As noted above, the vehicle 10 may comprise at least one presence sensor 22 for detecting whether an operator is positioned on the vehicle 10. In this regard, the controller 103 may be further configured to respond to a travel request to operate the vehicle 10 under remote control when the presence sensor(s) 22 designate that no operator is on the vehicle 10. Thus, in this implementation, the vehicle 10 cannot be operated in response to wireless commands from the remote control device 32 unless the operator is physically off of the vehicle 10. Similarly, if the obstacle sensors 40 detect that an object, including the operator, is adjacent and/or proximate to the vehicle 10, the controller 103 may refuse to acknowledge a travel request from the remote control device 32. Thus, in an exemplary implementation, an operator must be located within a limited range of the vehicle 10, e.g., close enough to the vehicle 10 to be in wireless communication range (which may be limited to set a maximum distance of the operator from the vehicle 10). Other arrangements may alternatively be implemented.

Any other number of reasonable conditions, factors, parameters or other considerations may also/alternatively be implemented by the controller 103 to interpret and take action in response to received signals from the transmitter 178. Other exemplary factors are set out in greater detail in U.S. Provisional Patent Application Ser. No. 60/825,688, entitled “SYSTEMS AND METHODS OF REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE;” U.S. patent application Ser. No. 11/855,310, entitled “SYSTEMS AND METHODS OF REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE” now U.S. Pat. No. 9,082,293; U.S. patent application Ser. No. 11/855,324, entitled “SYSTEMS AND METHODS OF REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE” now U.S. Pat. No. 8,072,309; U.S. Provisional Patent Application Ser. No. 61/222,632, entitled “APPARATUS FOR REMOTELY CONTROLLING A MATERIALS HANDLING VEHICLE;” U.S. patent application Ser. No. 12/631,007, entitled “MULTIPLE ZONE SENSING FOR MATERIALS HANDLING VEHICLES” now U.S. Pat. No. 9,645,968; and U.S. Provisional Patent Application Ser. No. 61/119,952, entitled “MULTIPLE ZONE SENSING FOR REMOTELY CONTROLLED MATERIALS HANDLING VEHICLES;” the disclosures of which are each already incorporated by reference herein.

Upon acknowledgement of a travel request, the controller 103 interacts with the traction motor controller 106, e.g., directly or indirectly, e.g., via a bus such as the CAN bus 110 if utilized, to advance the vehicle 10. Depending upon the particular implementation, the controller 103 may interact with the traction motor controller 106 and optionally, the steer controller 112, to advance the vehicle 10 for as long as a travel control signal is received. Alternatively, the controller 103 may interact with the traction motor controller 106 and optionally, the steer controller 112, to advance the vehicle 10 for a period of time or for a predetermined distance in response to the detection and maintained actuation of a travel control on the remote control device 32. Still further, the controller 103 may be configured to “time out” and stop the travel of the vehicle 10 based upon a predetermined event, such as exceeding a predetermined time period or travel distance regardless of the detection of maintained actuation of a corresponding control on the remote control device 32.

The remote control device 32 may also be operative to transmit a second type signal, such as a “stop signal”, designating that the vehicle 10 should brake and/or otherwise come to rest. The second type signal may also be implied, e.g., after implementing a “travel” command, e.g., after the vehicle 10 has traveled a predetermined distance, traveled for a predetermined time, etc., under remote control in response to the travel command. If the controller 103 determines that a wirelessly received signal is a stop signal, the controller 103 sends a signal to the traction motor controller 106, the brake controller 116 and/or other truck component to bring the vehicle 10 to a rest. As an alternative to a stop signal, the second type signal may comprise a “coast signal” or a “controlled deceleration signal” designating that the vehicle 10 should coast, eventually slowing to rest.

The time that it takes to bring the vehicle 10 to a complete rest may vary, depending for example, upon the intended application, the environmental conditions, the capabilities of the particular vehicle 10, the load on the vehicle 10 and other similar factors. For example, after completing an appropriate jog movement, it may be desirable to allow the vehicle 10 to “coast” some distance before coming to rest so that the vehicle 10 stops slowly. This may be achieved by utilizing regenerative braking to slow the vehicle 10 to a stop. Alternatively, a braking operation may be applied after a predetermined delay time to allow a predetermined range of additional travel to the vehicle 10 after the initiation of the stop operation. It may also be desirable to bring the vehicle 10 to a relatively quicker stop, e.g., if an object is detected in the travel path of the vehicle 10 or if an immediate stop is desired after a successful jog operation. For example, the controller 103 may apply predetermined torque to the braking operation. Under such conditions, the controller 103 may instruct the brake controller 116 to apply the brakes 117 to stop the vehicle 10.

Also shown in FIG. 3 is the on-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 a rechargeable power source 180 of the wireless remote control device 32. The charging station 50 may be located on a side portion of the vehicle 10, for example, proximate to the operator's station 20 near manual driving controls of the vehicle 10 as shown in FIGS. 1 and 2, or on a side panel of the power unit 14.

A pairing system 34 can utilize a close range system to wirelessly communicate with a compatible close range system on the wireless remote control device 32. Using the pairing system 34, a vehicle 10 and wireless remote control device 32 can be “paired” such that a vehicle 10 will transmit and receive messages from only its paired wireless remote control device 32. In addition to, or as an alternative to close range or other types of wireless communications, such as near-field communication (NFC), the pairing system 34 can also use physical contacts that allow electrical communication between the remote control device 32 and the vehicle 10, at least for the initial pairing procedure. For example, electrical contacts of the charging station 50 used for charging the remote control device 32 could be used for pairing the vehicle 10 to the remote control device 32, as will be described in greater detail herein. The pairing system 34 includes components that physically implement the communication method (e.g., Bluetooth, NFC, BLE, Wi-Fi, etc.) used to send messages and includes components that programmatically exchange information in an agreed upon protocol to establish and maintain a pairing. Thus, the pairing system 34 includes a device that can execute programmable instructions to implement a predetermined algorithm and protocol to accomplish pairing operations.

In FIG. 3, the charging station 50, the receiver 102, and the pairing system 34 are depicted as distinct functional blocks. However, one of ordinary skill will recognize that two or more of these components can be combined in a single element to provide a multi-function device.

System

As noted above, the vehicle 10 (including the charging station 50) and the remote control device 32 form the system 8 in accordance with an aspect of the present invention. The remote control device 32 and the charging station 50 will now be described in turn.

With reference to FIGS. 4-8, the remote control device 32 according to this embodiment is a finger-mounted device, although the remote control device 32 could take other forms, such as a glove-mounted device, a wrist-mounted device, a lanyard-mounted device, etc. The remote control device 32 may be mountable over one finger, two fingers, or more than two fingers of the operator.

The remote control device 32 illustrated in FIGS. 4-8 comprises a polymeric rigid base 172 (see FIG. 6) and a polymeric rigid upper housing 174. The base 172 and upper housing 174 are coupled together via any suitable manner and define an internal area 176 for receiving internal components of the remote control device 32, including a wireless communication system 456 including a wireless transmitter 178, such as the wireless transmitter 178 described above with reference to FIG. 3, and a rechargeable power source 180. In one exemplary embodiment, the wireless transmitter 178 comprises a model BGM121 manufactured by SiLabs. It is noted that the terms “transmitter” and “receiver” as used herein are intended to mean a device capable of one-way communication, i.e., the device only transmits or receives signals, or a device capable of two-way communication, such as a transceiver, which both transmits and receives signals.

The rechargeable power source 180 may be a super capacitor, 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.3 F. The rechargeable power source 180 is small enough to fit within the internal area 176 while also having enough capacity on a substantially full charge to yield a use period of the remote control device 32 of at least two hours, at least four hours, at least eight hours, or more. A use period of up to eight hours may be preferable to correspond with an eight-hour working shift for an operator.

A supercapacitor (also called a supercap or ultracapacitor) is a high-capacity capacitor with capacitance values much higher than other capacitors but, typically with lower voltage limits that bridge the gap between electrolytic capacitors and rechargeable batteries. They typically store 10 to 100 times more energy per unit volume or mass than electrolytic capacitors, can accept and deliver charge much faster than batteries, and tolerate many more charge and discharge cycles than rechargeable batteries. Because supercapacitors can be used in applications requiring many rapid charge/discharge cycles, some embodiments of the remote control device 32 can include a supercapacitor as the rechargeable power source 180. In embodiments of the present invention, the current supplied to the supercapacitor can be limited to about 2 A and can accomplish charging to a full charge in about 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 to a full charge state, or to a charge state less than a substantially full charge state (as will be discussed in detail herein) via the charging station 50 within a desired charging period. The power supplied to the rechargeable power source 180 by the charging station 50 may be varied in accordance with the capacity of the rechargeable power source 180, the desired charge amount, and/or the desired charging period, as will be discussed in greater detail herein.

With reference to FIG. 6, the remote control device 32 further comprises securing structure 188 for securing the remote control device 32 to one or more fingers of the operator's hand. The securing structure 188 in the embodiment shown in FIG. 6 comprises a holding strap 190 that includes, for example, hook and loop tape fasteners 191 to secure the holding 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 located on opposed ends of the remote control device 32 for receiving the holding strap 190.

The holding strap 190 shown in FIG. 6 defines a first finger receiving area 194 for receiving the single finger OF (see FIGS. 1 and 2) of an operator using the remote control device 32. Both right and left hand versions of the remote control device 32 may be created. The remote control device 32 is releasably held on the operator's index finger via the holding strap 190. In one exemplary embodiment, a first end 190A of the holding strap 190 is threaded through the first slot 192A and a second end 190B of the holding strap 190 is threaded through the second slot 192B. The first end 190A of the holding strap 190 may be permanently fastened to the rigid base 172, e.g., via stitching or gluing, while the second end 190B of the holding strap 190 may be releasably inserted through the second slot 192B and doubled back such that the hook and loop tape fasteners 191 are engaged with one another to fasten the holding strap 190 to the operator's finger. The holding strap 190 can be adjusted to accommodate fingers of different sizes or such that the remote control device 32 could be worn over a glove (not shown). It is noted that other types of holding straps 190 may be used.

The remote control device 32 further comprises at least one control, depicted in FIGS. 4-8 as first, second, and third controls 196A-C. The controls 196A-C each comprise a button 197A-C and a two-state switch 198A-C located underneath the corresponding button 197A-C. The switches 198A-C are communicably coupled to the wireless communication system 456, such that actuation of each one of the controls 196A-C causes the wireless transmitter 178 to wirelessly transmit a respective request to the vehicle 10. In the exemplary remote control device 32 depicted in FIGS. 4-8: the first control 196A comprises a travel button 197A that, when pressed, causes the wireless transmitter 178 to wirelessly transmit a request for the vehicle 10 to travel across a floor surface; the second control 196B comprises a horn button 197B that, when pressed, causes the wireless transmitter 178 to wirelessly transmit a request for the vehicle 10 to sound a horn/audible alarm; and the third control 196C comprises a brake button 197C that, 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.

The remote control device 32 is compact, and substantially the entirety of the remote control device 32 is mountable and positioned directly over the index finger of the operator. Hence, interference of the operator performing working tasks caused by wearing the remote control device 32 is minimal or non-existent. The remote control device 32 is durable and long lasting since the rigid base 172 and the upper housing 174 are preferably formed from a durable and rigid polymeric material, such as acrylonitrile butadiene styrene (ABS), polycarbonate or nylon. The rigid base 172 and the upper housing 174 define a durable, generally non-flexible and rigid structure.

An operator can easily actuate the travel button 197A manually via his/her thumb to cause the wireless transmitter 178 to wirelessly transmit at least a first type signal designating a travel request or command to the vehicle 10. It is contemplated that the travel request may result in the vehicle 10 traveling for as long as the operator holds down the travel button 197A, or by a predetermined distance or for a predetermined amount of time. The horn button 197B and the brake button 197C can be actuated by the operator's opposite hand, for example.

As shown in FIGS. 4 and 5, the remote control device 32 further comprises one or more charging contacts 210, it being noted that additional or fewer charging contacts 210 than the four shown may be used, e.g., one charging contact 210 or two or more charging contacts 210 may be used. Additionally, the remote control device 32 further includes one or more sensors in the form of first presence contacts 212, illustrated in FIGS. 4 and 5 as a single first presence contact 212 located intermediate the four charging contacts 210. The charging and first presence contacts 210, 212 may be arranged within openings 214 formed in an outer surface of the upper housing 174 of the remote control device 32. The tops of the charging and first presence contacts 210, 212 may be positioned below the outer surface of the upper housing, i.e., the charging and first presence contacts 210, 212 may be recessed within the openings 214, which may prevent damage to the charging and first presence contacts 210, 212 due to accidental contact. It is noted that other configurations for the number, orientation, and placement of the charging contacts 210 and the first presence contact(s) 212 could be used without departing from the scope and spirit of the invention.

In embodiments, the charging contacts 210 mate or engage with elements, e.g., electrical contacts or charging elements 220 of the on-vehicle charging station 50 (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, pogo pin or pressure pin, for example, of the on-vehicle charging station 50, as shown in FIGS. 8A and 8B and will be described in more detail herein. It is noted that one or more of the charging contacts 210 and corresponding charging elements 220 may be provided for redundancy. In one example, the four charging contacts 210 illustrated in FIGS. 4-7 and four charging elements 220 illustrated in FIGS. 12-14 could be set up as two pairs of redundant contacts/elements 210/220, where charging of the rechargeable power source 180 (as discussed below) is enabled as long as one charging contact 210 from each pair is engaged with and in electrical communication with its corresponding charging element 220.

Embodiments of the present invention also contemplate contactless, or induction, charging in which the rechargeable power source 180 of the remote control device 32 can be charged by the remote control device 32 being in close proximity to, or on the surface of, a compatible induction charging station (not shown). Such an induction charging station may be located, for example, in a driving or steering control of the vehicle 10 such that the rechargeable power source 180 may be charged while the operator is manually driving the vehicle 10 from the operator's station 20.

FIGS. 9 and 10 illustrate another exemplary remote control device 32, where like reference numbers correspond to similar components to those listed above for FIGS. 4-8. The remote control device 32 according to this embodiment is intended as a two-finger design, i.e., the securing structure 188 in the embodiment shown in FIGS. 9 and 10 comprises a holding strap 190 that defines first and second finger receiving areas 194, 195 for receiving the index and middle fingers of an operator using the remote control device 32. The remote control device 32 according to FIGS. 9 and 10 includes two charging contacts 210 instead of four charging contacts 210 in the remote control device 32 of FIGS. 4-8. The remaining components of the remote control device 32 of FIGS. 9 and 10 may be generally the same as the remote control device 32 of FIGS. 4-8 and thus will not be described in detail herein.

FIG. 11 provides a functional block-level diagram of a vehicle charging station 50 in accordance with the principles of the present invention in which the pairing system 34 is incorporated into the charging station 50. As explained in more detail below, the charging station 50 can include the receiver 102, e.g., a Bluetooth Low Energy (BLE) radio 402 that can communicate with the vehicle's controller 103. Although not shown, the communication can be through the vehicle's CAN bus and, thus, 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 that help convey information to an operator. For example, one LED may be used to indicate that a remote control device 32 is presently coupled with the charging station 50. Other LEDs may indicate a current state of charge of the remote control device's rechargeable power source 180. A current limiter 406 or other protection circuitry can be provided that helps ensure a remote control device 32 is safely re-charged as the current limiter 406 allows the voltage from the vehicle's power source to be provided to the charging elements 220 of the charging station 50 for charging the remote control device's rechargeable power source 180. These charging elements 220 interface with the charging contacts 210 of the remote control device 32 and provide the electrical connection between the vehicle's power source and the rechargeable power source 180 of the remote control device 32. The second presence contact 222 engages with the first presence contact 212 to detect when a remote control device 32 is physically connected to the charging station 50 such that the charging contacts 210 are engaged with the charging elements 220. According to embodiments, upon the second presence contact 222 being engaged by the first presence contact 212, the pairing process is initiated.

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

The relationship between the second presence contact 222 and the charging elements 220 is such that the charging contacts 210 of the remote control device 32 and the charging elements 220 of the charging station 50 are in contact with one another before the second presence contact 222 engages the first presence contact 212 when a charging procedure is being initiated, see FIG. 8A, which shows that the height of the second presence contact 222 is less than the height of the charging elements 220, the heights measured with respect to top surfaces of element housings 220A and a second presence contact housing 222A from which the respective charging elements 220 and second presence contact 222 extend. The supply of power from the charging station 50 to the remote control device 32 via the charging elements/charging contacts 220/210 is only initiated after the second presence contact 222 engages the first presence contact 212. During a charging procedure, the charging contacts 210 of the remote control device 32 are engaged with the charging elements 220 of the charging station 50, and the second presence contact 222 is engaged with the first presence contact 212, thus enabling the supply of power from the charging station 50 to the remote control device 32 via the charging elements/charging contacts 220/210, see FIG. 8B. After the rechargeable power source 180 is charged to the desired amount, e.g., fully charged or charged to a desired amount less than fully charged as described herein, the supply of power from the charging station 50 to the remote control device 32 via the charging elements/charging contacts 220/210 is cut off. In the case that the remote control device 32 is removed from the charging station 50 before the rechargeable power source 180 is 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 prior to the charging elements 220 disengaging from the charging contacts 210. The supply of power from the charging station 50 to the rechargeable power source 180 of the remote control device 32 via the charging elements/charging contacts 220/210 is cut off when the second presence contact 222 disengages from the first presence contact 212. This arrangement is intended to prevent arcing between the charging elements 220 and the charging contacts 210. Using the first presence contact 212 and second presence contact 222 in the form of a pogo pin provides the following advantages: a precise control of the relative heights of the second presence contact 222 and the charging elements 220; a small footprint, a good seal, e.g., to prevent moisture from entering the second presence contact housing 222A from around the second presence contact 222; and it allows for the differentiation between the first presence contact 212 and a foreign object, such as a piece of metal, which prevents electrical current from flowing into such a foreign object if it were to be placed in contact with the second presence contact 222 and one or more of the charging elements 220.

As an alternative to the presence contacts 212, 222 being used to initiate the supply of power from the charging station 50 to the remote control device 32, a separate switch may be present that the operator engages to begin a charging operation. In one specific embodiment using induction charging, such a switch can be incorporated into the vehicle's steering control, such that the operator's gripping of the steering control is detected and charging is subsequently enabled.

Controls 414 for providing controlling signals to operate the LEDs 404 can be from various sources. While the remote control device 32 is operated within range of the charging station 50, the controller 103 can receive information about the state of charge of the rechargeable power source 180 and drive the display of the LEDs 404 to convey this information utilizing a CAN bus interface, for example. When the remote control device 32 is coupled with the charging station 50 the LEDs 404 can be used to convey a) that a remote control device 32 is physically connected to charging station 50, b) that there is a remote control device 32 presently paired with the controller 103 of the vehicle, c) the progress/charging state of a current charging operation, and/or d) the charging state of the rechargeable power source 180. The information for items c) and d) may be sent to the charging station 50 by the remote control device 32, for example, over a Bluetooth Low Energy (BLE) connection, which BLE connection will be discussed in greater detail below. According to one aspect, since the pairing and charging processes are performed very quickly, the progress/charging state of a current charging operation may not be displayed by the LEDs 404. The remote control device 32 may store its charging profile and then send the charging profile to the charging station 50, e.g., over the BLE connection, after the remote control device 32 is removed from the charging station 50, wherein the charging profile may be evaluated, for example, by the controller 103, to determine if a proper charge of the rechargeable power source 180 occurred. The second presence contact 222 can also send control signals to controls 414 that indicate whether charging contacts 210 of the remote control device 32 are properly coupled with corresponding charging elements 220 of the charging station 50.

FIGS. 12-14 illustrate other features of the charging station 50 located at the vehicle 10. The charging station 50 can include one or more physical protrusions or guide structures 420 that help guide the remote control device 32 into correct alignment so that the station's charging elements 220 are aligned with the charging contacts 210 of the remote control device 32, i.e., the guide structure(s) 420 align the remote control device 32 in the proper orientation for charging the rechargeable power source 180. In FIG. 12, a single guide structure 420 including a plurality of guide surfaces is shown. The guide structure(s) 420 can be placed around the location of the charging elements 220 and can be shaped or slanted so that the remote control device 32 is physically guided to correct alignment as the operator places the remote control device 32 in the charging station 50.

In FIG. 13, the LEDs 404 include a visual indicator 424 that indicates a remote control device 32 is attached to the charging station 50. The visual indicator 424 may illuminate, flash, or progressively fill as a first color to indicate that the remote control device 32 is attached to the charging station 50, and as a second color or fully filled first color to indicate that the remote control device 32 has been paired to the vehicle controller 103, i.e., the visual indicator 424 may use the second color or fully filled first color to serve as a pairing indicator that confirms the establishment of communication between the remote control device 32 and the vehicle 10. Additionally, according to one optional aspect of the invention, the LEDs 404 may flash, illuminate as a second color, or provide some other visual indication after establishment of communication between the remote control device 32 and the vehicle 10 as a cue for the operator to perform an action as a test to confirm that the remote control device 32 is functional and can communicate to the vehicle 10, such as by pressing the horn button 197B and brake button 197C concurrently. It is understood that separate indicators may be used for the purposes of indicating that a remote control device 32 is attached to the charging station 50 and to indicate that the remote control device 32 has been paired to the vehicle 10, as opposed to a single indicator that can serve both functions.

The LEDs 404 can further serve as an indicator to identify the progress of a 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 LEDs 404 may serve as an indicator to indicate the present state of charge of the rechargeable power source 180 of the remote control device 32. Thus, the LEDs 404 can indicate the state of charge of the rechargeable power source 180 both when charging the rechargeable power source 180 at the charging station 50 and during use of the remote control device 32, i.e., while the operator is using the remote control device 32 to assist in performing work operations. In one exemplary embodiment, the LEDs 404 can comprise a series of lights, each light representing a level of the state of charge of the rechargeable power source 180.

In FIGS. 12 and 14, an exemplary location of the second presence contact 222 is shown within the charging station 50. It is noted that the remote control device 32 illustrated in FIGS. 12-14 is the single-finger embodiment of FIGS. 4-7. It is also noted that the charging contacts 210 and first presence contact 212 of the single-finger and the two-finger embodiments could be arranged to mirror one another. Thus, the same charging station 50 could be used for instances of the single-finger or two-finger remote control devices 32.

The charging station 50 may be located at various locations on the vehicle 10. Its location should be such that it does not interfere with normal operation of the vehicle 10, but where it is accessible and convenient for the operator. In embodiments the charging station 50 is located in the operator's station 20 (see FIGS. 1 and 2, where the charging station 50 is located in the operator's station 20 but is also accessible from outside of the vehicle 10), on a surface of one of the sides of the vehicle 10, or, for the induction charging embodiment, within the steering control of the vehicle 10.

The charging station 50 may include a voltage regulator (not shown) that transforms the power from the vehicle 10 received by the charging station 50 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 in which the rechargeable power source 180 is an AVX supercapacitor described above or equivalent device, a 3V DC (1%) supply voltage could be provided to the current limiter 406.

It is 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 invention. For example, one or more components of the remote control device 32 may be combined in an integral component, or components may be substituted for alternate components that effect a similar/identical purpose.

In one embodiment, charging of the rechargeable power source 180 via the charging station 50 occurs when one or more charging contacts 210 engage a corresponding charging element 220 of the charging station 50. In some embodiments, at least two charging contacts 210 or at least four charging contacts 210 and corresponding charging elements 220 are present. In some embodiments, one or more pairs of charging contacts 210 are provided, wherein at least one charging contact 210 from each pair must engage a corresponding charging element 220 for charging to occur. As described above, at least one of the remote control device 32 and the charging station 50 can include a second presence contact 222, such as a switch, for example. The second presence contact 222 detects whether or not the at least one charging contact 210 is correctly engaged with the at least one corresponding charging element 220 for charging the rechargeable power source 180, wherein if a correct engagement is detected, the transfer of power to the rechargeable power source 180 is enabled by the charging station 50, and if a correct engagement is not detected, the transfer of power to the rechargeable power source 180 is not enabled by the charging station 50.

Furthermore, the arrangement of the remote control device 32 and the charging station 50 is configured such that the second presence contact 222 indicates the removal of the remote control device 32 from the charging station 50, which ceases the transfer of power to the rechargeable power source 180 from the charging station 50, before the at least one charging contact 210 is disengaged from the at least one corresponding charging element 220. Hence, the transfer of power from the charging station 50 to the rechargeable power source 180 is ceased before the at least one charging contact 210 is disengaged from the at least one corresponding charging element 220. This may be effected, for example, by setting the heights of the charging elements 220 and the second presence contact 222 as shown in FIG. 8A, wherein the charging elements 220 are pushed down into respective element housings 220A before the second presence contact 222 engages the first presence contact 212, as the remote control device 32 is inserted into the charging station 50.

FIG. 15 is a block-level functional diagram of the portions 450 of the remote control device 32 that relate to recharging the rechargeable power source 180. The other portions of the remote control device 32 such as, for example, those that relate to the mechanical actuators are not depicted in FIG. 15. As noted above, the remote control device 32 can include one or more charging contacts 210 that are configured to engage a corresponding charging element. In some embodiments, the charging elements may be the charging elements 220 of the charging station 50. In other embodiments, the charging elements may be those of an adapter that connects to a source of power to recharge the rechargeable power source 180.

The remote control device 32 can include protection circuitry 452 that limits electrical parameters such as voltage and/or current to be within expected operating ranges. Charge controller and disconnect circuitry 454 can monitor the voltage being received from the protection circuitry 452 as well as monitor the present state of charge of the rechargeable power source 180 in order 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 charge controller and disconnect circuitry 454 can operate to stop further charging. The charge controller and disconnect circuitry 454 can include temperature sensing capabilities or be connected to a temperature sensor so that the rechargeable power source 180 can be charged (or discharged) to different charging levels. In some embodiments, the rechargeable power source 180 is discharged to a high temperature state of charge, e.g., a less than fully charged state, if a sensed temperature is determined to be above a predetermined setpoint temperature. In one exemplary aspect of the invention, the sensed temperature is an ambient temperature. In an alternative aspect, the sensed temperature is a battery temperature. In some embodiments, the rechargeable power source 180 is charged at the charging station 50 to a predetermined charge level less than a 100% charge level if a sensed temperature is determined to be above a predetermined threshold temperature. This may help prevent damage to or degradation of the rechargeable power source 180.

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

Associating/Pairing a Remote Control Device with a Vehicle

FIGS. 16-18 illustrate details of exemplary pairing processes in accordance with aspects of the invention. The remote control device 32 and vehicle 10 described above will be used in describing the pairing processes of FIGS. 16-18, but it is understood that other configurations/styles of the remote control device and vehicle could be paired together in accordance with the invention.

With reference to FIG. 16, the method 500 begins when the vehicle operator retrieves a remote control device 32 at 502. If the remote control device 32 is a wearable device as in the embodiments of FIGS. 4-8 and 9-10, the remote control device 32 is also donned by the operator, e.g., by securing the holding strap 190 to the operator's finger(s).

The vehicle operator then initiates a power on sequence to enable the vehicle 10 for operation, i.e., the operator starts the vehicle 10 at 504. In starting the vehicle 10, the operator may be required to provide login information to the vehicle 10. This information may be provided for, by example, entering a personal identification number (PIN) into a control panel of the vehicle 10, by utilizing a key fob to provide the logon ID to the vehicle 10, or the operator's PIN may be encoded into a memory device, such as a radio-frequency identification (RFID) chip that is integrated into the remote control device 32.

The operator then starts a pairing operation with the vehicle 10 at 506, and the pairing system 34 then pairs the remote control device 32 used by the operator to the vehicle 10 at 508. Details of two exemplary pairing operations will be described in detail below with reference to FIGS. 17 and 18.

Once paired, the system 8 may provide a visual indication as such, e.g., by displaying a message on the vehicle 10, illuminating the LED 424 in a predetermined color, making an audible or visual queue, etc., that indicates that the pairing is complete.

In accordance with an aspect of the invention, the remote control device 32 may be unpaired from the vehicle 10 by powering down the vehicle 10. Other exemplary methods for unpairing the remote control device 32 from the vehicle 10 are described below in exemplary use cases.

The operation of two example pairing systems 34 are described in relation to FIGS. 17 and 18, respectively, which are flowcharts of example methods 550 and 600 for pairing a vehicle 10 and a remote control device 32 using a pairing system 34 that is part of the charging station 50 on board the vehicle 10. The descriptions of the methods 550 and 600 of FIGS. 17 and 18 begin as the remote control device 32 is inserted into the charging station 50, corresponding to step 506 of FIG. 16.

With reference to FIG. 17 and the method 550, at 552, when the second presence contact 222 is engaged by the first presence contact 212 as the remote control device 32 is inserted into the charging station 50, the BLE radio 402 of the charging station 50 is enabled so as to start scanning or listening for nearby BLE transmissions. As discussed above, the engagement of the second presence contact 222 by the first presence contact 212 can also cause the current limiter 406 to be enabled so that power from the vehicle 10 can be provided to the charging contacts 210 from the charging elements 220, which will cause the rechargeable power source 180 of the remote control device 32 to be recharged. Accordingly, pairing and charging operations are initiated by the single action of coupling the remote control device 32 with the charging station 50. In lieu of using BLE transmissions to pair the remote control device 32 to the vehicle controller 103, the remote control device 32 can be paired to the vehicle controller 103 by direct physical contact between, for example, the charging contacts 210 and the charging elements 220. Alternatively, dedicated pairing contacts (not shown) may 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 to the vehicle controller 103 via direct physical contact. Such pairing contacts on the remote control device 32 and the vehicle 10 could be engaged with each other concurrently with the engagement of the charging contacts 210 to the charging elements 220, such that the pairing process could occur at the same time as the charging process. These pairing contacts could be used solely for performing message exchanges for pairing operations.

According to one aspect of the invention, where the pairing process is accomplished wirelessly, at 554, the remote control device 32 detects that a voltage is present at its charging contacts 210 and begins transmitting BLE advertisements via the wireless transmitter 178 indicating that the remote control device 32 is available for communicating with nearby devices.

In response, the BLE radio 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 402 of the charging station 50 were 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 may not pair with any of the available remote control devices 32 and may require the operator 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.

At 558, the remote control device 32 responds to the scan request with a unique identification code, which the BLE radio 402 receives.

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

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 wirelessly communicates 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.

In the example flowchart described above with respect to FIG. 17, a similar method can be performed to pair the remote control device 32 to 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 dedicated pairing contacts noted above. Instead of the messages being transmitted and received via wireless/BLE radios, the same or equivalent types of messages can be communicated through the elements/contacts 220/210 via various protocols. The messages can be modulated and transmitted over one of the elements/contacts 220/210 providing the voltage. In either case, pairing of the vehicle 10 and the remote control device 32 can occur concurrently with the charging of the rechargeable power source 180 of the remote control device 32.

With reference to FIG. 18 and the method 600, at 602, when the second presence contact 222 is engaged by the first presence contact 212 as the remote control device 32 is inserted into the charging station 50, the BLE radio 402 of the charging station 50 is enabled with a predetermined, e.g., 1500 ms, timeout so as to start scanning or listening for nearby BLE transmissions from remote control devices 32. As discussed above, the engagement of the second presence contact 222 by the first presence contact 212 can also cause the current limiter 406 to be enabled so that power from the vehicle 10 can be provided to the charging contacts 210 from the charging elements 220, which will cause the rechargeable power source 180 of the remote control device 32 to be recharged. Accordingly, pairing and charging operations are initiated by the single action of coupling the remote control device 32 with the charging station 50 such that a component of the remote control device 32 physically contacts an element of the charging station 50. In lieu of using BLE transmissions to pair the remote control device 32 to the vehicle controller 103, the remote control device 32 can be paired to the vehicle controller 103 by direct physical contact between, for example, the charging contacts 210 and the charging elements 220. Alternatively, dedicated pairing contacts (not shown) may 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 to the vehicle controller 103 via direct physical contact. Such pairing contacts on the remote control device 32 and the vehicle 10 could be engaged with each other concurrently with the engagement of the charging contacts 210 to the charging elements 220, such that the pairing process could occur at the same time as the charging process. These pairing contacts could be used solely for performing message exchanges for pairing operations.

At 604, the signal strength of the BLE transmissions between the wireless transmitter 178 and the BLE radio 402 may be decreased during the pairing process to help prevent any other nearby vehicles 10 from receiving the BLE transmissions from the remote control device 32.

According to one aspect of the invention, where the pairing process is accomplished wirelessly, at 606, the remote control device 32 detects that a voltage is present at its charging contacts 210 and begins transmitting BLE advertisements via the wireless transmitter 178 at a predetermined rate, e.g., a 20 ms rate with a predetermined timeout, e.g., 2000 ms timeout, indicating that the remote control device 32 is available for communicating with nearby vehicles 10. If the BLE radio 402 of the charging station 50 were 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 may not pair with any of the available remote control devices 32 and may require the operator 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.

The charging station 50 may provide power to charge the rechargeable power source 180 for up to about, e.g., 1000 ms before the BLE advertisements are sent from the wireless transmitter 178. Charging of the rechargeable power source 180 by the charging station 50 will be discussed in detail below.

In response to receiving the BLE advertisements from the wireless transmitter 178, the BLE radio 402 of the charging station 50 can, at 608, issue a BLE scan request.

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

At 614, the vehicle 10 verifies the code and instructs the BLE radio 402 to open a BLE connection and begin communicating with the remote control device 32. It is noted that if the vehicle 10 receives more than one valid identification code during step 614, for example, if the vehicle 10 receives identification codes from two different remote control devices 32, pairing will fail, the vehicle 10 may 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.

At 616, once a communication session is established between the remote control device 32 and the charging station 50, the pairing operation may be completed, and the signal strength of the BLE transmissions between the wireless transmitter 178 and the BLE radio 402 may be increased back to their normal levels at 618.

The operator may be required to perform an action at 620 as a test to confirm that the remote control device 32 is functional and can communicate to the charging station 50, such as by pressing a button sequence on the remote control device 32, for example, by pressing the horn button 197B and brake button 197C concurrently.

Once paired, the vehicle 10 wirelessly communicates 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.

In accordance with aspects of the invention, a pairing period (which is a time period that it takes to establish communication between the remote control device 32 and the vehicle 10 and commences with steps 552/602 and ends with steps 564/616) may be less than the charging period (which is the time it takes to charge the rechargeable power source 180 to a desired charge state at the charging station 50), wherein charging of the rechargeable power source 180 will be discussed below in connection with FIGS. 21 and 22.

Referring to FIG. 19, in accordance with an additional aspect of the invention, after performing work operations, the vehicle operator may need to temporarily leave the vehicle 10, e.g., to take a break. An exemplary method 700 is illustrated for shutting down, restarting and re-pairing the vehicle 10 to the remote control device 32 used by the operator. The operator powers down the vehicle 10 at 702, so as to take a break, etc. After a time, the vehicle operator powers the vehicle 10 back up. During this time of the break, the remote control device 32 may continue to be paired with the vehicle 10 for up to a predefined time period. This state of maintained pairing between the vehicle 10 and the remote control device 32 may be indicated, for example, on a touchscreen (not shown) provided on the vehicle 10, by illuminating the LED 424 in a predetermined color, pattern, etc. Thus, if the operator powers the vehicle 10 back up before the predefined time period expires at 704, the vehicle 10 may detect the remote control device 32 at 706, wherein the remote control device 32 remains paired with the vehicle 10. In this regard, 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 touchscreen, etc., or by pressing a button sequence on the remote control device 32.

A successful operator action at 708 results in a 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 (the LED 424) to signify the pairing, e.g., by illuminating the LED 424 in the second color noted above.

Alternatively, according to this aspect of the invention, if the operator powers the vehicle 10 back up after the predefined time period expires at 712, the operator may be required to re-pair the remote control device 32 to the vehicle 10 as with the initial pairing, e.g., by inserting the remote control device 32 into the charging station 50 at 714.

With reference to FIG. 20, an example method 800 is illustrated for reestablishing communication between the remote control device 32 and the vehicle 10 after a period of 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 for 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 manually using the manual controls in the operator's station 20, other manual controls, e.g., on the side of the vehicle 10, or via the remote control device 32), standing on the platform 21, moving or placing an item on the load handling assembly 12, etc. At 804, if no vehicle-related activity takes place for greater than a first predetermined amount of time after communication between the remote control device 32 and the vehicle 10 is established, the communication between the remote control device 32 and the vehicle 10 is terminated and must be re-established using the pairing system 34 at 806, i.e., by inserting the remote control device 32 into the charging station 50 at the vehicle 10. This state of terminated pairing between the vehicle 10 and the remote control device 32 may be indicated, for example, on the touchscreen, by illuminating the LED 424 in a predetermined color, pattern, etc.

At 808, if no vehicle-related activity takes place for less than a second predetermined amount of time after communication between the remote control device 32 and the vehicle 10 is established, the second predetermined amount of time equal to or less than the first predetermined amount of time, the communication between the remote control device 32 and the vehicle 10 is terminated but can be re-established without the pairing system 34, e.g., by performing a confirmation method utilizing the remote control device 32 at 810. The confirmation method may comprise, for example, the operator carrying out a button sequence on the remote control device 32, such as by long-pressing one or more of the buttons 197A-C. This state of pairing between the vehicle 10 and the remote control device 32 may be indicated, for example, on the touchscreen, by illuminating the LED 424 in a predetermined color, pattern, etc.

FIG. 21 is a flowchart of an example method 900 for charging a remote control device in accordance with the principles of the present invention. In particular, the remote control device may be the same as or similar to the remote control device 32 discussed herein, and can include a wireless communication system 456 including a wireless transmitter 178 (e.g., capable of one 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 a materials handling vehicle 10.

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

Next, at 904, a charging period is started, wherein power is supplied from the charging station 50 to the rechargeable power source 180. As described above, as an example, circuitry of the charging station 50 is configured such that upon the sensing of contact between the charging contact(s) 210 and charging element(s) 220, power is supplied from the charging station 50 to the charging contacts 210 of the remote control device 32 to charge the rechargeable power source 180. Once the rechargeable power source 180 is substantially fully charged (or charged to the desired amount less than a substantially full state of charge), the remote control device 32 can be removed from the charging station 50.

Thus, the method of FIG. 21 continues, at 906, with interrupting 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 charging contact(s) 210 of the remote control device 32 and the charging element(s) 220 of the charging station 50 are arranged such that as the two systems are disengaged, that state can be detected or sensed. One example is the second presence contact 222 that can detect when the remote control device 32 is being removed from the charging station 50.

Finally, upon the sensing of this interruption at 906, the charging station 50 can cease the supply of power from the charging station 50 to the rechargeable power source 180 at 908, thus ending the charging period. It is noted that the second presence contact 222 can be located on the remote control device 32 and its disengagement can result in ceasing the supply of power from the charging station 50 to the rechargeable power source 180. The supply of power from the charging station 50 to the rechargeable power source 180 may also be ceased when the rechargeable power source 180 is charged up to the desired amount (either fully charged or charged up to a desired amount less than fully charged), as described herein.

The method 900 can include other optional steps shown in FIG. 21. For example, the method 900 can also include confirming the establishment of communication between the remote control device 32 and the vehicle 10 at 910, e.g., with at least one of an audible or visual queue. The method 900 can further include, while the remote control device component is in contact with the charging station element, establishing communication between the remote control device 32 and the vehicle 10 (e.g., pairing) during a pairing period at 912, such that the controller 103 receives transmissions from the remote control device 32 and is capable of implementing wireless requests from the remote control device 32. This communication between the remote control device 32 and the vehicle 10 can be established concurrently during charging of the rechargeable power source 180 at the charging station 50, such that the pairing period and the charging period overlap. In at least some embodiments the pairing period is less than or equal to the charging period.

Additionally, the method 900 may include, at 914, displaying a state of charge of the rechargeable power source 180 at the vehicle 10, e.g., at the charging station 50, wherein the state of charge of the rechargeable power source 180 may be displayed at the vehicle 10 both when charging the rechargeable power source 180 and during use of the remote control device 32. The state of charge of the rechargeable power source 180 may be displayed, for example, via a series of lights, each light representing a level of a state of charge of the rechargeable power source 180.

FIG. 22 is a flowchart of another example method 950 for charging a remote control device in accordance with the principles of the present invention, such as the remote control device 32 discussed herein, which comprises a wireless communication system 456 including a wireless transmitter 178 (e.g., capable of one 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 a materials handling vehicle 10. As used herein, the term “control”, when used to describe a control of the remote control device 32, is meant to include any structure capable of providing the desired function, including but not limited to buttons, switches, dials, etc.

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

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

Based on the current state of charge of the rechargeable power source 180 and after step 952 is performed, at 956, a charging period is started, wherein 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, the charging station 50 charges the rechargeable power source 180 at a first, higher 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, the charging station 50 charges the rechargeable power source 180 at a second, lower power level PL2. The resulting charging period in either case, i.e., at step 958A or step 958B, may be about the same, i.e., charging the rechargeable power source 180 up to the desired amount from above or below the voltage threshold VT may take about the same time. While only two power levels PL1, PL2 associated with a single voltage threshold VT are discussed herein, additional voltage thresholds and power levels could be used, wherein the charging period can always be about the same time, regardless of the charge level of the rechargeable power source 180 when it is inserted into the charging station 50. Additionally, an equation could be used to dynamically set the power level according to the current state of charge of the rechargeable power source 180.

Once the charging period is complete, that is, once the rechargeable power source 180 is charged to the desired amount, i.e., substantially fully charged or charged to an amount less than a substantially full state of charge, e.g., in view of the sensed temperature if that technology is present in the system 8, or if less than a full charge is desired, the remote control device 32 can be removed from the charging station 50.

Thus, the method of FIG. 22 continues, at 960, with interrupting 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 charging contact(s) 210 of the remote control device 32 and the charging element(s) 220 of the charging station 50 are arranged such that as the two systems are disengaged, that state can be detected or sensed. One example is the second presence contact 222 that can detect when the remote control device 32 is being removed from the charging station 50.

Finally, upon the sensing of this interruption at 960, or upon the rechargeable power source 180 being charged to the desired amount, the charging station 50 can cease the supply of power from the charging station 50 to the rechargeable power source 180 at 962, thus ending the charging period.

The method 950 can include other optional steps shown in FIG. 22. For example, the method 950 can also include confirming the establishment of communication between the remote control device 32 and vehicle 10 at 964, e.g., with at least one of an audible or visual queue. The method 950 can further include, while the remote control device component is in contact with the charging station element, establishing communication between the remote control device 32 and the vehicle 10 (e.g., pairing) during a pairing period at 966, such that the controller 103 receives transmissions from the remote control device 32 and is capable of implementing wireless requests from the remote control device 32. This communication between the remote control device 32 and the vehicle 10 can be established concurrently during charging of the rechargeable power source 180 at the charging station 50, such that the pairing period and the charging period overlap. In at least some embodiments, the pairing period is less than or equal to the charging period, although the pairing period may be greater than the charging period, as will be discussed in more detail below.

Additionally, the method 950 may include, at 968, displaying a state of charge of the rechargeable power source 180 at the vehicle 10, e.g., at the charging station 50, wherein the state of charge of the rechargeable power source 180 may be displayed at the vehicle 10 both when charging the rechargeable power source 180 and during use of the remote control device 32. The state of charge of the rechargeable power source 180 may be displayed, for example, via a series of lights, each light representing a level of a state of charge of the rechargeable power source 180.

In accordance with an aspect of the invention, the charging period may depend on the capacity of the rechargeable power source 180, the charge rate/power level supplied by the charging station 50, and/or the charge state of the rechargeable power source 180 when it is inserted into the charging station 50. Thus, a desired charging period could be achieved regardless of the current state of charge of the rechargeable power source 180 when the remote control device 32 is placed in the charging station 50. For example, the current state of charge of the rechargeable power source 180 may be known to the vehicle 10, e.g., the state of charge of the rechargeable power source 180 may be communicated to the charging station 50, as discussed herein. The charging station 50 may be instructed, e.g., by the controller 103, to supply power to the rechargeable power source 180 at different rates or levels based on the state of charge of the rechargeable power source 180 when the remote control device 32 is placed in the charging station 50, so that the charging period is generally about the same time regardless of the state of charge of the rechargeable power source 180 when the remote control device 32 is placed in the charging station 50. For example, as discussed above with reference to steps 958A/B of FIG. 22, if the state of charge of the rechargeable power source 180 is a first, lower state of charge, then a first, greater rate/level of power may be supplied from the charging station 50 to the rechargeable power source 180. If the state of charge of the rechargeable power source 180 is a second, higher state of charge, then a second, lesser rate/level of power may be supplied from the charging station 50 to the rechargeable power source 180. The resulting charging period in both cases could be about the same time, e.g., within about 0.5 seconds of the desired charging period. Any number of rechargeable power source states of charge and corresponding rates/levels of power could be implemented such that the time required to charge the rechargeable power source 180 is within the desired charging period. Additionally, the usage life of the rechargeable power source 180 may be increased when it is charged at a lower power level. Hence, an additional advantage of a consistent charging period as with the present invention is that the rechargeable power source 180 is sometimes charged at a lower power level, e.g., when the charge state of the rechargeable power source 180, when it is inserted into the charging station 50 is the second, higher state of charge discussed above. Hence, charging the rechargeable power source 180 at different power levels as discussed herein may increase the usage life of the rechargeable power source 180, as opposed to if the rechargeable power source 180 was charged at a consistent, higher power level with each charge.

Additionally, while the pairing period, which is described herein as the time period it takes to establish communication between the remote control device 32 and the vehicle 10, may be less than or equal to the charging period, the charging period may also be less than the pairing period. As one example, it may be determined that the rechargeable power source 180 does not need to be fully charged in order to operate for a desired use period. For example, a full charge of the rechargeable power source 180 may provide an operation time that is greater than a desired use period (e.g., an operator's shift), such that the rechargeable power source 180 does not need to be fully charged in order to be operable for the desired use period. In this case, the charging station 50 may be programmed to charge the rechargeable power source 180 up to a less than full state of charge, which would still be sufficient for the remote control device to be operable for the entire desired use period. The time it takes to charge rechargeable power source 180 up to this less than full state of charge may be less than the pairing period. Other situations may also occur where the charging period may be less than the pairing period.

With reference to FIG. 23, the principles of the present invention can also be implemented as a kit 1000 for retrofitting to a materials handling vehicle 10′. In FIG. 23, elements similar to or identical to those described above with reference to FIGS. 1-22 include the same reference number followed by a prime symbol (′). An element described with respect to FIG. 23 but not specifically shown in FIG. 23 is equivalent to the element having the same reference symbol as described above, but without the prime symbol.

The vehicle 10′ can include a vehicle controller 103′ that is responsive to wireless requests from an associated remote control device 32′ that is 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 would include a charging station 50′ at the vehicle 10′, the charging station 50′ for charging a rechargeable power source 180′ of the remote control device 32′, wherein the charging station 50′ is electrically coupled to a vehicle power source, and a receiver 102′ such as a BLE radio communicably 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 up to a desired amount (a full charge or less than full charge as discussed herein) at the charging station 50′ within a desired charging period.

The kit 1000 may further include a pairing system 34′ for establishing communication between the remote control device 32′ and the vehicle 10′, such that the controller 103′ is capable of implementing wireless requests from the remote control device 32′. The pairing system 34′ may, for example, be similar to pairing system 34 and can implement the pairing algorithm(s) detailed in FIG. 17 and/or FIG. 18. Thus, the kit 1000 can also include a pairing indicator, e.g., visual indicator 424′, that confirms the establishment of communication between the remote control device 32′ and the vehicle 10′. Furthermore, the pairing system 34′ can be configured such that the pairing period (a time period that it takes to establish communication between the remote control device 32′ and the vehicle 10′) may be less than or equal to the charging period (a time period it takes to charge the rechargeable power source 180′ to the desired 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 element.

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. Furthermore, in some embodiments, communication between the remote control device 32′ and the vehicle 10′, and charging of the rechargeable power source 180′ at the charging station 50′ are initiated with a single action. For example, the single action can comprise physically contacting a component of the remote control device, for example, one or more charging contacts 210 as described above, with an element of the charging station, for example, one or more corresponding charging elements 220 as described above.

The remote control device 32′ used in combination with the kit 1000 may be the same as the remote control devices 32 disclosed herein. Hence, a remote control device manufactured for use with a vehicle 10 including an integrated charging station 50 and related components could also be used with a kit 1000 for use with an existing vehicle 10′.

As described above with respect to the charging station 50, the charging station 50′ of the kit 1000 can also include guide structure 420′ to align the remote control device 32′ in the proper orientation for charging the rechargeable power source 180′.

The kit 1000 can also include an indicator (e.g., LEDs 404′, light, or similar structure) configurable to be attachable at the vehicle 10′ for indicating a state of charge of the rechargeable power source 180′. The indicator can indicate the state of charge of the rechargeable power source 180′ both when charging the rechargeable power source 180′ at the charging station 50′ and during use of the remote control device 32′. In some embodiments, the indicator comprises a series of lights, each light representing a level of the state of charge of the rechargeable power source 180′.

The kit 1000 includes at least one charging element 220′ on the charging station 50′ that engages at least one corresponding charging contact 210′ of the remote control device 32′. Furthermore, at least one of the remote control device 32′ or the charging station 50′ includes a presence contact 212′ or 222′ that detects whether or not at least one corresponding charging contact 210′ and at least one charging element 220′ are correctly engaged with one another. If a correct engagement is detected, the transfer of power to the rechargeable power source 180′ of the remote control device 32′ is enabled by the charging station 50′, and if a correct engagement is not detected, the transfer of power to the rechargeable power source 180′ is not enabled by the charging station 50′. In at least some embodiments, the remote control device 32′ comprises at least two charging contacts 210′ or at least four charging contacts 210′ that are positioned to engage corresponding charging elements 220′ on the charging station 50′.

The arrangement of the remote control device 32′ and the charging station 50′ of the kit 1000 is configured such that the presence contact 212′ or 222′ indicates the removal of the remote control device 32′ from the charging station 50′, which ceases the transfer of power to the rechargeable power source 180′ from the charging station 50′, before the at least one charging contact 210′ is disengaged from the at least one corresponding charging element 220′. Hence, the transfer of power from the charging station 50′ to the rechargeable power source 180′ is ceased before the at least one charging contact 210′ is disengaged from the at least one corresponding charging element 220′.

The kit 1000 may also utilize contactless, or induction, charging in which the rechargeable power source 180′ of the remote control device 32′ can be charged by being in close proximity to, or on the surface of, a compatible induction charging station (not shown). Such an induction charging station may be located, for example, in a driving or steering control of the vehicle 10′ such that the rechargeable power source 180′ may be charged while the operator is manually driving the vehicle 10′ from the operator's station 20′. The kit 1000 according to this aspect of the invention may be at least partially located in the vehicle steering control or other vehicle component that facilitates the contactless/induction charging of rechargeable power source 180′, e.g., the rechargeable power source 180′ may be charged by the operator grasping the driving/steering control.

The kit 1000 may utilize any of the other features and/or functions of the remote control device 32′ and the charging station 50′ described above for FIGS. 1-22. It is noted that if the vehicle 10′ to be used with the kit 1000 was previously set up for interacting with a wireless remote control device, the controller logic in the vehicle controller 103′ may need to be updated to be used with the kit 1000, and a receiver that was already provided at the vehicle 10′, i.e., for receiving wireless requests from a remote control device that was used with the vehicle 10′ before the kit 1000 was installed on the vehicle 10′, may be turned off in lieu of the receiver 102′ of the kit 1000, i.e., for use with the remote control device 32′ associated with the kit 1000.

With reference now to FIG. 24, a remote control device 32 in accordance with an embodiment of the invention may be incorporated into a glove garment 1100. The use of the glove garment 1100 eliminates the need for the holding strap 190, and the first control 196A may be provided on a finger of the glove garment 1100 as opposed to being a part of the upper housing 174, but the remaining components of the remote control device 32 illustrated in FIG. 24 may be the same or similar to those of the remote control device 32 of FIGS. 4-7, including a shape of the portion of the upper housing 174 that engages with the charging station 50 at the vehicle 10. Hence, the charging station 50 at the vehicle 10 may 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 FIGS. 4-7, the same charging station 50 could be used with either the finger-mounted remote control device 32 of FIGS. 4-7, or the remote control device 32 incorporated into the glove garment 1100 of FIG. 24.

If the remote control device 32 incorporated into the glove garment 1100 were used in combination with the inductive charging technology disclosed herein, inductive charging structures may be incorporated, for example, into the palm of the glove garment 1100. Such charging structures in the glove garment 1100 could be used with charging elements incorporated, for example, into a steering control of a vehicle paired to the remote control device 32, in which case a rechargeable power source of the remote control device 32 could be charged while the operator is grasping the steering control.

According to additional aspects of the present invention, there may be conditions and/or events that cause the vehicle 10 to become unpaired from the remote control device 32, wherein a complete pairing process utilizing the pairing system 34, as described herein, may be required to re-pair the vehicle 10 with the remote control device 32. There may be other conditions or events that cause the vehicle 10 to become unpaired from the remote control device 32, wherein something other than a complete pairing process utilizing the pairing system 34, as described herein, may be required to re-pair the vehicle 10 with the remote control device 32. Several exemplary use cases with regard to unpairing and re-pairing will now be described.

A first exemplary use case may occur by powering down the vehicle 10. According to this first use case, the remote control device 32 is unpaired from the controller 103 and requires a complete pairing process utilizing the pairing system 34, as described herein, to re-pair the vehicle 10 with the remote control device 32. In accordance with this exemplary first use case, a complete pairing process utilizing the pairing system 34 may be required to re-pair the remote control device 32 to the vehicle 10 whenever the vehicle 10 is powered down.

A second exemplary use case may be substantially as described above with respect to FIG. 19, wherein the vehicle operator temporarily leaves the vehicle 10, e.g., to take a break. The details of this second exemplary use case are discussed above with reference to FIG. 17 and will not be repeated again.

Third and fourth exemplary use cases may occur if no vehicle-related activity takes place for greater than a first predetermined amount of time after communication between the remote control device 32 and the vehicle 10 is established (third use case) or if no vehicle-related activity takes place for less than a second predetermined amount of time after communication between the remote control device 32 and the vehicle 10 is established (fourth use case). The details of these third and fourth exemplary use cases are discussed above with reference to FIG. 20 and will not be repeated again.

A number of exemplary use cases may arise where multiple remote control devices 32 and/or multiple vehicles 10 are concerned. In a fifth exemplary use case, assume 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. Under this circumstance, the charging station 50 of the second vehicle 10 may charge the rechargeable power source 180 of the first remote control device 32, the first remote control device 32 may become unpaired from the first vehicle 10, and the second remote control device 32 may become unpaired from the second vehicle 10. The first remote control device 32 will not be paired to the second vehicle 10 in the fifth use case.

In a sixth exemplary use case and with reference to FIG. 24, assume a 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 not currently paired with a remote control device. In this sixth use case, the remote control device 32 is paired with the second vehicle 10B using a pairing process, 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 may charge the rechargeable power source 180 of the remote control device 32, and the remote control device 32 may become paired with the second vehicle 10B such that the remote control device wirelessly communicates with the second vehicle 10B. This pairing process may also cause the remote control device to become unpaired from 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 from the first vehicle 10A, the second vehicle 10B may respond to remote requests from the remote control device 32, while the first vehicle 10A may no longer respond to remote requests from the remote control device 32.

As described above, the wireless communication system 456 of the remote control device 32 and/or the BLE radio 402 of the charging station 50 can be configured, for example, to enter a low power mode when the remote control device 32 is being paired to the second vehicle 10B and/or the rechargeable power source 180 of the remote control device 32 is being charged at the charging station 50, e.g., to ensure that only a remote control device 32 that is within a minimum distance, corresponding to the signal strength of the communications received from the remote control device 32, from the charging station 50, is recognized as the remote control device 32 for the second vehicle 10B to pair with.

According to the sixth exemplary use case, prior to the pairing process, the second vehicle 10B may be sent, e.g., by a Warehouse Management System WMS in communication with the second vehicle 10B, to a designated location, such as, for example, the location of the operator, the location of the first vehicle 10A, the end of an aisle in which the operator and/or first vehicle 10A are located, a designated waiting area, etc. The second vehicle 10B may be an unloaded vehicle, i.e., free from a load and thus ready to carry items to be picked by the operator. The second vehicle 10B may be instructed to move to the designated location by the Warehouse Management System WMS, for example, when the first vehicle 10A is loaded with a desired amount of pick items and is ready to be sent to a different location, i.e., a location that is different than the current location of the vehicle 10, such as a loading dock LD or other location where the pick items on the first vehicle 10A are to be sent. The operator may also request that the second vehicle 10B be sent to the designated location, for example, using a control on the first vehicle 10A, over a headset, etc. Once the second vehicle 10B is paired to the remote control device 32, the second vehicle 10B may no longer implement commands from the Warehouse Management System WMS, such that the second vehicle 10B will only implement wireless commands from the remote control device 32 with which it is paired.

Once the remote control device 32 is unpaired from the first vehicle 10A, the Warehouse Management System WMS may send instructions to the first vehicle 10A to move to the loading dock LD and/or to another location, such as a vehicle charging station (not shown). Using this sixth exemplary use case, an operator may quickly switch between vehicles 10A, 10B, resulting in an increase in work productivity and efficiency.

In a seventh exemplary use case, assume a first remote control device 32 is currently paired with a vehicle 10, and a second remote control device 32 is not paired with a vehicle. In this seventh use case, the second remote control device 32 is inserted into the charging station 50 of the vehicle 10. Under this circumstance, the charging station 50 of the vehicle 10 may charge the rechargeable power source 180 of the second remote control device 32, the first remote control device 32 may become unpaired from the vehicle 10, and the second remote control device 32 will not be paired to the vehicle 10.

In an eighth exemplary use case, the remote control device 32 is moved out of 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 time period. According to the eighth use case, the remote control device 32 may become unpaired from the vehicle 10. According to the eighth use case, if the remote control device 32 moves back into range of the vehicle 10 after a predetermined time period, the vehicle 10 may need to be shut down and restarted to pair with a remote control device 32 utilizing 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 moves back into range of the vehicle 10 within the predetermined time period, the vehicle 10 may not need to be shut down and restarted to pair with the previously paired remote control device 32, e.g., the previously paired remote control device 32 may be re-paired with the vehicle 10 by inserting the remote control device 32 into the charging station 50 of the vehicle. Pairing the vehicle 10 to a different remote control device 32 may require a vehicle shut down and restart, regardless of how long the previously paired remote control device 32 was out of range of the vehicle 10.

Additional exemplary use cases concerning pairing and/or charging periods will now be described.

In a ninth exemplary use case, a desired charge state, e.g., a substantially full charge state, of the rechargeable power source 180 can be achieved by charging the rechargeable power source 180 at the charging station 50 in five seconds or less. According to this use case, the substantially full charge state of the rechargeable power source 180 may yield a use period of the remote control device 32 of at least eight hours.

In a tenth exemplary use case, the charging station 50 varies the power level supplied to the rechargeable power source 180 depending on the state of charge 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 FIG. 22. A charging period according to the tenth use case will always be about four seconds, regardless of the state of charge of the rechargeable power source 180 when the remote control device 32 is inserted into the charging station 50. Hence, a predictable charging period is achieved.

It is noted that the type of transmissions sent by the remote control device 32 to the vehicle 10, e.g., requests, such as travel requests, may be other types of transmissions. As one example, the transmissions may comprise location-based transmissions that inform the controller 103 of the vehicle 10 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, e.g., to follow the remote control device 32. Hence, the vehicle 10 may follow an operator wearing, holding, or carrying the remote control device 32. Such a remote control device 32 could be charged by the charging station 50 and paired to the vehicle 10 as described herein.

In accordance with another aspect of the present invention, charging of the rechargeable power source 180 by the charging station 50 may be disabled while the vehicle 10 is in motion. This aspect of the invention may not apply to inductive charging of the rechargeable power source 180.

Furthermore, when an operator is attempting to pair a remote control device 32 to a vehicle 10 that is in communication with the Warehouse Management System WMS, the Warehouse Management System WMS can determine if one or more remote control device operational checks have been performed within a predetermined time period, for example, within the last 12 hours. Such operational checks may include, for example, checks to ensure the operability of controls of the remote control device 32, such as the horn and/or brake buttons 197B, 197C. If such operational check(s) have not been performed within the predetermined time period, the vehicle 10 may communicate to the operator that operational check(s) must be performed prior to the remote control device 32 being pairable with the vehicle 10, i.e., the remote control device 32 is only allowed to pair with the vehicle 10 if the one or more remote control device operational checks have been performed within the predetermined time period. The operational checks may be performed by the operator implementing the controls, e.g., by holding down the horn and/or brake buttons 197B, 197C.

Additionally, when an operator is attempting to pair a remote control device 32 to a vehicle 10 that is in communication with the Warehouse Management System WMS, the Warehouse Management System WMS can determine if the operator is authorized to operate the vehicle 10 that the operator is attempting to pair to the remote control device 32. For example, vehicles that are to be used only in a certain location, such as in a freezer, may only be pairable with remote control devices 32 where the operator will use the vehicle in that location. As another example, operators may be limited to operating certain vehicles. Remote control devices 32 in these situations may only be authorized to pair with such vehicles when these condition(s) are met.

In accordance with an aspect of the invention, the charge life of the rechargeable power source 180 over a given operating cycle may be increased by turning off or reducing the power consumption of one or more components of the remote control device 32, e.g., the components of the wireless communication system 456 including the wireless transmitter 178, when an operator is determined to be standing on the platform 21 of the vehicle 10, e.g., as detected by the presence sensors 22.

The terms “pairing” and “synchronizing” (as used herein and in the various patents and published patent applications incorporated by reference herein) are used interchangeably herein to describe a secure process whereby a wireless remote control device and vehicle controller identify each other as valid command and response devices.

A charging station 1050 and a remote control device 1032 constructed in accordance with a still further aspect of the present disclosure are illustrated in FIGS. 26 and 27. Elements on the charging station 1050 which are generally the same as elements on the charging station 50 described above are referenced with the same reference numerals used for those elements on the charging station 50. Similarly, elements on the remote control device 1032 which are generally the same as elements on the remote control device 32 described above are referenced with the same reference numerals used for those elements on the remote control device 32.

The charging station 1050 comprises a docking port 1052, which may comprise a pocket or recess shaped to receive the remote control device 1032 such that charging contacts 210 on the remote control device 1032 are aligned with and engage with charging elements 220 at the charging station 1050 to effect charging of a rechargeable power source 180 forming 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, e.g., inductive charging.

The charging station 1050 can comprise one or more visual indicators that convey information to an operator, which information may comprise one or more of: a charging state of the rechargeable power source 180 when the remote control device 1032 is coupled to the charging station 1050, a charging state of the rechargeable power source 180 when the remote control device 1032 is removed from the charging station 1050, a pairing status between the wearable remote control device 1032 and the vehicle controller 103, and/or that the remote control device 1032 is physically connected to the charging station 1050.

In the embodiment illustrated in FIGS. 26 and 27, a first visual indicator 1060 and a second visual indicator 1070 are provided on the charging station 1050. The first visual indicator 1060 may comprise one or more lights, such as LEDs. The first visual indicator 1060 may be provided proximate to the docking port 1052 defined within the charging station 1050, as viewed in FIGS. 26 and 27, which docking port 1052, as noted above, comprises 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 a travel button 197A also provided on the remote control device 1032, see FIG. 26, which travel button 197A may cause a wireless transmitter 178 forming part of the remote control device 1032 to wirelessly transmit a request for a vehicle 10 to travel across a floor surface. The first visual indicator 1060 may be shaped to correspond to the graphic 1034 provided on the remote control device 1032 to aid 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, the graphic 1034 provided on the remote control device 1032 is shaped as an isosceles triangle facing upward when the remote control device 1032 is coupled to the charging station 1050, but could comprise 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 could comprise any other geometric shape, image, icon, etc. The first visual indicator 1060 shaped as a downward facing triangle provides an indication to a user that 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 the first visual indicator 1060 so as to mate with or mirror the first visual indicator 1060.

The second visual indicator 1070 may be positioned proximate to the first visual indicator 1060, such as just above the first visual indicator 1060 as viewed in FIGS. 26 and 27. The second visual indicator 1070 may be defined by a plurality of linearly arranged lights, such as LEDs, which may be activated individually and serially. The lights of the second visual indicator 1070 may have a different color than the one or more lights of the first visual indicator 1060.

When a vehicle 10 comprising the charging station 1050 is powered up, i.e., turned from an OFF state to an ON state, the first visual indicator 1060 may be activated and, preferably, is pulsed ON and OFF to provide a visual display related to inserting the wearable remote control device 1032 into the docking port 1052, while the second visual indicator 1070 remains OFF, see FIG. 28A. With the first visual indicator 1060 activated, i.e., pulsed ON and OFF, and the second visual indicator 1070 OFF, this indicates to an operator that the charging station 1050 is enabled and functional and she/he needs to couple the remote control device 1032 to the docking port 1052 of the charging station 1050 to effect pairing and charging. If the first visual indicator 1060 is not activated, this may indicate that the charging station 1050 is not enabled. Hence, the first visual indicator 1060 and the second visual indicator 1070 may be configured to be activated independently of each other such that the first visual indicator 1060 may be activated while the second visual indicator 1070 is not activated.

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 may be deactivated, i.e., turned OFF, and at least one of the lights defining the second visual indicator 1070 may be activated to convey to the operator that the remote control device 1032 has been physically connected to the docking port 1052, see FIG. 28B. Once docking of the remote control device 1032 has occurred, 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. Lights defining the second visual indicator 1070 may be activated serially, such as from left to right as viewed in FIGS. 26, 27 and 28B, to indicate the status of the charging operation of the power source 180 or the charging state of the rechargeable power source 180 when coupled to the charging station 1050. Once the rechargeable power source 180 is fully charged, all lights defining the second indicator 1070 may be activated, i.e., turned ON, see FIG. 28C.

FIGS. 29A-29C provide an alternative embodiment, as compared to that of FIGS. 28A-28C, for the activating and deactivating of the first visual indicator 1060 and the second visual indicator 1070 during physical connection and pairing of the remote control device 1032 with the docking port 1052 of the charging station 1050. The embodiment of FIG. 29A-29C can be utilized for all charge/pair cycles such as an initial cycle after vehicle 10 is powered ON from an OFF state as well as subsequent charge cycles occurring before vehicle 10 is powered OFF. As described above, when a vehicle 10 comprising the charging station 1050 is powered up, i.e., turned from an OFF state to an ON state, the first visual indicator 1060 may be activated and, preferably, is pulsed ON and OFF to provide a visual display related to inserting the wearable remote control device 1032 into the docking port 1052, while the second visual indicator 1070 remains OFF, see FIG. 28A and FIG. 29A. With the first visual indicator 1060 activated, i.e., pulsed ON and OFF, and the second visual indicator 1070 OFF, this indicates to an operator that the charging station 1050 is enabled and functional and she/he needs to couple the remote control device 1032 to the docking port 1052 of the charging station 1050 to effect pairing and charging. 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 may remain activated so as to provide a steady-state ON display, and at least one of the lights defining the second visual indicator 1070 may be activated to convey to the operator that the remote control device 1032 has been physically connected to the docket port 1052, see FIG. 29B. Once docking of the remote control device 1032 has occurred, 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. Lights defining the second visual indicator 1070 may be activated serially, such as from left to right as viewed in FIGS. 26, 27, 29B and 29C, to indicate the status of the charging operation of the power source 180 or the charging state of the rechargeable power source 180 when coupled to the charging station 1050. Once the rechargeable power source 180 is fully charged, all lights defining the second indicator 1070 may be activated, i.e., turned ON, and the first visual indicator 1060 may be deactivated, i.e., turned OFF, see FIG. 29C.

Because the first visual indicator 1060 remains activated, as shown in FIG. 29B, while the rechargeable power source 180 is charging, the first visual indicator 1060 and the second visual indicator 1070 both provide cues to the operator that the remote control device 1032 should remain connected with the charging station 1050 and that charging of the rechargeable power source 180 is not complete until the first visual indicator 1060 is deactivated and all the lights of the second visual indicator 1070 are activated, i.e., see FIG. 29C.

In FIG. 28B, FIG. 28C, FIG. 29B and FIG. 29C, the individual lights of the second visual indicator 1070 can become activated, or turned on, one after the other which can be described as making the second visual indicator 1070 “grow.” As noted above, a desired charge state, e.g., a substantially full charge state, of the rechargeable power source 180 can be achieved by charging the rechargeable power source 180 at the charging station in five seconds or less. If, for example, the second visual indicator 1070 has five discrete segments, or lights, a timing of the “growing” of the second visual display 1070 can be configured such that the time period between activating each of the five lights is about one second (+/−5%), such that activation of all of the lights, including the fifth light, indicates that the rechargeable power source is fully charged. Alternatively, embodiments in accordance with the present disclosure contemplate the timing between activating each of the first four segments, LEDs, or lights of the second visual indicator 1070 can be about 1.2 seconds (+/−5%) and activating the fifth and final segment occurs about 200 ms (+/−5%) after activation of the previous, or fourth, light. One benefit of having a non-uniform timing delay between activating the light segments of the second visual indicator 1070 is to reduce the chance of an operator misunderstanding the lighting cues, removing the remote control device 1032 too early, and thereby preventing a full charge of the rechargeable power source 180.

In either embodiment involving the activation of the first visual indicator 1060 (i.e., FIGS. 28A-28C or FIGS. 29A-29C), if the rechargeable power source 180 can not be charged, then the first visual display 1060 may flash or pulse ON and OFF to provide a visual display indicating an error, while the second visual display 1070 is turned OFF, see FIG. 28I. The error may be related to the rechargeable power source 180, the charging station 1050 or both being defective. The rate at which the first visual indicator 1060 is flashed ON and OFF to indicate an error may vary in frequency as compared to the rate at which the first visual indicator 1060 is pulsed ON and OFF when the vehicle 10 is powered up.

As noted above, once the rechargeable power source 180 has been fully charged, all lights of the second visual indicator 1070 may be activated. All lights of the second visual indicator 1070 may also be pulsed to provide the operator with an intermittent display as a cue to perform an action as a test to confirm that the remote control device 1032 is functional and can communicate to the vehicle 10, i.e., that pairing has been successful. The remote control device 1032 may further comprise 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 FIG. 4. The action as a test to confirm that the remote control device 32 is functional and can communicate with the vehicle may comprise pressing the horn button 197B to determine if a horn on the vehicle 10 is activated and/or pressing the brake button 197C to determine if brakes on the vehicle are actuated. Once the test has been successfully completed, all lights of the second visual indicator 1070 may be activated continuously to define a steady-state display. Hence, the second visual indicator 1070 may define an intermittent display, a steady-state display, or a display where less than all of the lights are activated, i.e., a partially filled display, based on the information to be conveyed to the operator/user. If the test is not completed successfully, the first visual indicator 1060 may flash or pulse ON and OFF to indicate an error, while the second visual indicator 1070 is turned OFF, see FIG. 28I. The error may occur due to pairing between the remote control device 1032 and the vehicle controller 103 not occurring successfully. The rate at which the first visual indicator 1060 is flashed or pulsed ON and OFF to indicate that the test was not completed successfully may vary in frequency from when the first visual indicator 1060 is pulsed ON and OFF when the vehicle 10 is powered up.

As noted 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 lights of the second visual indicator 1070 may be activated continuously 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, operation of the vehicle 10 and the remote control device 1032 cause the rechargeable power source 180 to consume some of its charge such that the operator, before the vehicle is turned OFF, again connects the remote control device 1032 to the docket port 1052 for charging. After charging, the second visual indicator 1070 may not pulse to cue the operator to perform the test even though the rechargeable power source 180 may again reach full charge. Because the vehicle 10 has not been turned OFF and back ON since the last successful test, the second visual indicator 1070 may not be pulsed to cue the operator to perform the test again but instead, remain in its steady state display indicating the rechargeable power source 180 is fully charged.

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

As noted above, the rate at which the first visual indicator 1060 is flashed ON and OFF to indicate an error may be at a different frequency as compared to the rate at which the first visual indicator 1060 is pulsed ON and OFF when the vehicle 10 is powered up. The error may, for example, relate to an error with the charging station 1050 such that it is unable to charge the remote control device 1032. The error may also, for example, relate to an error with the remote control device 1032 or its power source 180 such that it is unable to receive a charge from the charging station 1050. Furthermore, the error may, for example, involve both the charging station 1050 and the remote control device 1032 such that there are communication messages between the two devices that are not being received by the intended recipient of the communication message.

As noted, the second visual indicator 1070 when activated can provide one of an intermittent display, as shown in the example of FIG. 28D, which may indicate to an operator to perform an action, or a steady-state display as shown in the example of FIG. 28E, which may indicate to an operator that the remote control device 1032 is fully ready to use.

Also, when the first visual indicator 1060 and the second indicator 1070 are concurrently activated, the first visual indicator 1060 and the second visual indicator 1070 can each provide respective steady-state displays as shown in the example of FIG. 28G, which can indicate that the rechargeable power source 180 has a low charge.

In the example of FIG. 28A, the first visual indicator 1060 may pulse as a way to define a visual display related to inserting the wearable remote control device 1032 into the charging station 1050.

As noted above, the example of FIG. 28I includes the first visual indicator flashing so as to provide a display indicative of the occurrence of some error. This is only an example and, more generally, at least one embodiment of the present disclosure contemplates that the first visual indicator 1060 or the second visual indicator 1070 can, either individually or in combination with one another, provide a visual display related to a charging error occurring with the charging station 1050 or the rechargeable power source 108.

As noted above, the example of FIG. 28I includes the first visual indicator 1060 flashing so as to provide a display indicative of the occurrence of some error. This is only an example and, more generally, at least one embodiment of the present disclosure contemplates that the first visual indicator 1060 or the second visual indicator 1070 can, either individually or in combination with one another, provide a visual display related to a pairing error occurring between the wearable remote control device 1032 and the vehicle 10. As explained earlier, the term “pairing” (as used herein) describes a secure process whereby the wireless remote control device 1032 and vehicle controller 103 identify each other as valid command and response devices. A pairing error can occur as the two devices try to initially pair with one another and fail or a pairing error can occur after a successful pairing such that the pairing is somehow interrupted or lost.

As noted above, the example of FIG. 28I includes the first visual indicator 1060 flashing so as to provide a display indicative of the occurrence of some error. This is only an example and, more generally, at least one embodiment of the present disclosure contemplates that the first visual indicator 1060 or second visual indicator 1070 can, either individually or in combination with one another, provide a visual display related to a communication error occurring between the wearable remote control device 1032 and the controller 103. Once paired, the remote control device 1032 and the controller 103 both act as senders and receivers of messages passed between the two according to a predetermined communications protocol. Communication errors can include, for example, when one of the devices does not receive an expected message.

Having thus described the invention of the present application in detail and by reference to embodiments thereof, it will be apparent that modifications and variations are possible without departing from the scope of the invention defined in the appended claims.

Number	Date	Country
1460082	Dec 2003	CN
1864199	Nov 2006	CN
101005981	Jul 2007	CN
101162395	Apr 2008	CN
101267958	Sep 2008	CN
101999102	Mar 2011	CN
108599283	Sep 2018	CN
10033857	Jan 2002	DE
202005003366	Jul 2005	DE
102005059226	Jul 2006	DE
60210360	Mar 2007	DE
102007027494	Jan 2009	DE
406070	Jan 1991	EP
556031	Aug 1993	EP
0732641	Sep 1996	EP
1237062	Sep 2002	EP
1288882	Mar 2003	EP
1462880	Sep 2004	EP
1475297	Nov 2004	EP
1653251	May 2006	EP
1813569	Aug 2007	EP
2036763	Mar 2009	EP
2482265	Aug 2012	EP
3173371	Jan 2019	EP
2764091	Dec 1998	FR
2819596	Jul 2002	FR
2849160	Jun 2004	FR
2867593	Sep 2005	FR
1002825	Sep 1965	GB
2197799	Jun 1988	GB
2360500	Oct 2003	GB
2398394	May 2006	GB
02152898	Jun 1990	JP
07138000	May 1995	JP
2002104800	Apr 2002	JP
2002179196	Jun 2002	JP
2005094425	Apr 2005	JP
2005241651	Sep 2005	JP
2006259877	Sep 2006	JP
2006293975	Oct 2006	JP
60486	Jan 2007	RU
8702483	Apr 1987	WO
9215977	Sep 1992	WO
9639679	Dec 1996	WO
02088918	Nov 2002	WO
2004057553	Jul 2004	WO
2006078604	Jul 2006	WO
2008039649	Apr 2008	WO
2010065864	Jun 2010	WO
2010095128	Aug 2010	WO
2011002478	Jan 2011	WO
2011022026	Feb 2011	WO
2012054443	Apr 2012	WO

Number	Date	Country
63105479	Oct 2020	US
63059567	Jul 2020	US
62800032	Feb 2019	US

	Number	Date	Country
Parent	16718473	Dec 2019	US
Child	17305463		US
Parent	16718411	Dec 2019	US
Child	16718473		US

On-board charging station for a remote control device

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer

Abstract

Description

Claims

CROSS REFERENCE TO RELATED APPLICATIONS

US Referenced Citations (238)

Foreign Referenced Citations (53)

Non-Patent Literature Citations (41)

Related Publications (1)

Provisional Applications (3)

Continuation in Parts (2)

Number	Name	Date	Kind
1835808	Pitts	Dec 1931	A
2959260	Johnson et al.	Nov 1960	A
3016973	Williamson	Jan 1962	A
3047783	Van Oort et al.	Jul 1962	A
3587784	Carl	Jun 1971	A
3825130	Lapham	Jul 1974	A
3831963	Placko et al.	Aug 1974	A
3946882	Koch	Mar 1976	A
3968893	Lapham	Jul 1976	A
4074120	Allred et al.	Feb 1978	A
4077486	Blakeslee et al.	Mar 1978	A
4106584	Matsubara	Aug 1978	A
4252495	Cook	Feb 1981	A
4258825	Collins	Mar 1981	A
4287966	Frees	Sep 1981	A
4362458	Jantzi	Dec 1982	A
4384695	Nohmi et al.	May 1983	A
4476954	Johnson et al.	Oct 1984	A
4518043	Anderson et al.	May 1985	A
4527651	Thiermann, Sr.	Jul 1985	A
4546840	Yukishige et al.	Oct 1985	A
4551059	Petoia	Nov 1985	A
4623032	Kemmer	Nov 1986	A
4644237	Frushour et al.	Feb 1987	A
4665487	Ogawa et al.	May 1987	A
4714140	Hatton et al.	Dec 1987	A
4716980	Butler	Jan 1988	A
4727492	Reeve et al.	Feb 1988	A
4785664	Reebs	Nov 1988	A
4849735	Kirtley et al.	Jul 1989	A
4878003	Knepper	Oct 1989	A
4893689	Laurich-Trost	Jan 1990	A
4954817	Levine	Sep 1990	A
4967362	Schutten et al.	Oct 1990	A
5023790	Luke, Jr.	Jun 1991	A
5036935	Kohara	Aug 1991	A
5044472	Dammeyer et al.	Sep 1991	A
5107946	Kamimura et al.	Apr 1992	A
5117935	Hall	Jun 1992	A
5141381	Kato et al.	Aug 1992	A
5151696	Kasahara et al.	Sep 1992	A
5170351	Nemoto et al.	Dec 1992	A
5220319	Kendel	Jun 1993	A
5245144	Stammen	Sep 1993	A
5307271	Everett et al.	Apr 1994	A
5357560	Nykerk	Oct 1994	A
5361861	Miller	Nov 1994	A
5402257	Hasselmann et al.	Mar 1995	A
5502638	Takenaka	Mar 1996	A
5652486	Mueller et al.	Jul 1997	A
5682313	Edlund et al.	Oct 1997	A
5709523	Ware	Jan 1998	A
5778327	Simmons et al.	Jul 1998	A
5816741	Troppman	Oct 1998	A
5892855	Kakinami et al.	Apr 1999	A
5913919	Bauer et al.	Jun 1999	A
5928292	Miller et al.	Jul 1999	A
5938710	Lanza et al.	Aug 1999	A
5939986	Schiffbauer et al.	Aug 1999	A
5964313	Guy	Oct 1999	A
6030169	Rossow et al.	Feb 2000	A
6112839	Ostler et al.	Sep 2000	A
6137404	O'Connor	Oct 2000	A
6148255	van der Lely	Nov 2000	A
6157892	Hada et al.	Dec 2000	A
6173215	Sarangapani	Jan 2001	B1
6179390	Guzorek et al.	Jan 2001	B1
6226902	Heyne	May 2001	B1
6276485	Eriksson et al.	Aug 2001	B1
6285925	Steffen	Sep 2001	B1
6364328	Stabler	Apr 2002	B1
6382359	Lohmann	May 2002	B1
6390496	Eicher	May 2002	B1
6459955	Bartsch et al.	Oct 2002	B1
6464025	Koeper et al.	Oct 2002	B1
6481525	Bloch et al.	Nov 2002	B1
6507366	Lee	Jan 2003	B1
6548982	Papanikolopoulos et al.	Apr 2003	B1
6552661	Lastinger et al.	Apr 2003	B1
6571176	Shinmura et al.	May 2003	B1
6587787	Yokota	Jul 2003	B1
6595306	Trego et al.	Jul 2003	B2
6686951	Dickson et al.	Feb 2004	B1
6688836	Gourand	Feb 2004	B2
6691015	Levine	Feb 2004	B1
6748292	Mountz	Jun 2004	B2
6750780	Bitelli	Jun 2004	B1
6764012	Connolly et al.	Jul 2004	B2
6784800	Orzechowski	Aug 2004	B2
6801125	McGregor et al.	Oct 2004	B1
6809680	Tojima	Oct 2004	B2
6810319	Manaka	Oct 2004	B2
6961561	Himmel et al.	Nov 2005	B2
7017689	Gilliland et al.	Mar 2006	B2
7025727	Brockway et al.	Apr 2006	B2
7027920	Madau	Apr 2006	B2
7047132	Jacobs	May 2006	B2
7076366	Simon et al.	Jul 2006	B2
7099764	Seto et al.	Aug 2006	B2
7133537	Reid	Nov 2006	B1
7266477	Foessel	Sep 2007	B2
7610121	Nishira et al.	Oct 2009	B2
7711464	Kaufmann	May 2010	B2
7734419	Kondoh	Jun 2010	B2
7765066	Braeuchle et al.	Jul 2010	B2
7775317	Goodwin et al.	Aug 2010	B1
7860653	Joe et al.	Dec 2010	B2
7937219	Ichinose et al.	May 2011	B2
8010261	Brubaker	Aug 2011	B2
8027029	Lu et al.	Sep 2011	B2
8060400	Wellman	Nov 2011	B2
8088262	Choi et al.	Jan 2012	B2
8099214	Moshchuk et al.	Jan 2012	B2
8170787	Coats et al.	May 2012	B2
8175772	Onuma	May 2012	B2
8180561	Osanai	May 2012	B2
3209091	Morichika et al.	Jun 2012	A1
8193903	Kraimer et al.	Jun 2012	B2
8195344	Song et al.	Jun 2012	B2
8280560	Huang et al.	Oct 2012	B2
8308174	Muth et al.	Nov 2012	B2
8386146	Shirai	Feb 2013	B2
8494718	Muth et al.	Jul 2013	B2
8577551	Siefring et al.	Nov 2013	B2
8705792	James et al.	Apr 2014	B2
8725317	Elston et al.	May 2014	B2
8725362	Elston et al.	May 2014	B2
8725363	Elston et al.	May 2014	B2
8731777	Castaneda et al.	May 2014	B2
8970363	Kraimer et al.	Mar 2015	B2
9002581	Castaneda et al.	Apr 2015	B2
9082293	Wellman et al.	Jul 2015	B2
9122276	Kraimer et al.	Sep 2015	B2
9493184	Castaneda et al.	Nov 2016	B2
9522817	Castaneda et al.	Dec 2016	B2
9643638	Wittliff, III	May 2017	B1
9908527	Elston et al.	Mar 2018	B2
10163334	Capps et al.	Dec 2018	B1
10179723	Kraimer et al.	Jan 2019	B2
10301155	Dues et al.	May 2019	B2
10404801	Martch	Sep 2019	B2
20010035729	Graiger et al.	Nov 2001	A1
20020035331	Brockway et al.	Mar 2002	A1
20020049539	Russell et al.	Apr 2002	A1
20020163495	Doynov	Nov 2002	A1
20020172017	Tarnowski et al.	Nov 2002	A1
20020178830	Kazerooni et al.	Dec 2002	A1
20030014162	Sadano	Jan 2003	A1
20030020808	Luke et al.	Jan 2003	A1
20030029647	Trego et al.	Feb 2003	A1
20030029648	Trego et al.	Feb 2003	A1
20030150663	Farbotnik et al.	Aug 2003	A1
20030205433	Hagman	Nov 2003	A1
20030209604	Harrison, Jr.	Nov 2003	A1
20030216854	Katakura et al.	Nov 2003	A1
20030235489	Hoff	Dec 2003	A1
20040099453	Guy	May 2004	A1
20040193349	Flann et al.	Sep 2004	A1
20040193363	Schmidt et al.	Sep 2004	A1
20040193374	Hac et al.	Sep 2004	A1
20050017858	Gross	Jan 2005	A1
20050052412	McRae et al.	Mar 2005	A1
20050073433	Gunderson et al.	Apr 2005	A1
20050075785	Gray et al.	Apr 2005	A1
20050216124	Suzuki	Sep 2005	A1
20050243058	Morris et al.	Nov 2005	A1
20050244259	Chilson et al.	Nov 2005	A1
20050246073	Needelman et al.	Nov 2005	A1
20050247508	Gilliland et al.	Nov 2005	A1
20050269145	Schmidt	Dec 2005	A1
20060025893	Fischer et al.	Feb 2006	A1
20060041271	Bosma et al.	Feb 2006	A1
20060058645	Komistek et al.	Mar 2006	A1
20060084422	Huang et al.	Apr 2006	A1
20060125806	Voyles et al.	Jun 2006	A1
20060229744	Patzwald et al.	Oct 2006	A1
20060231302	Rose	Oct 2006	A1
20060238156	Kim	Oct 2006	A1
20060250255	Flanagan	Nov 2006	A1
20060255961	Hofer et al.	Nov 2006	A1
20060265166	Makela	Nov 2006	A1
20070002808	Twitchell	Jan 2007	A1
20070016341	Nagasawa	Jan 2007	A1
20070056157	Hirata et al.	Mar 2007	A1
20070078455	Rashidi	Apr 2007	A1
20070088477	Brewer et al.	Apr 2007	A1
20070109110	Ohmura et al.	May 2007	A1
20070112461	Zini et al.	May 2007	A1
20070116548	Cooper	May 2007	A1
20070129870	Lange et al.	Jun 2007	A1
20070137904	Rose et al.	Jun 2007	A1
20070171090	Newman et al.	Jul 2007	A1
20070194882	Yokota et al.	Aug 2007	A1
20070219720	Trepagnier et al.	Sep 2007	A1
20070255451	Lewis et al.	Nov 2007	A1
20080011554	Broesel et al.	Jan 2008	A1
20080071429	Kraimer et al.	Mar 2008	A1
20080129445	Kraimer et al.	Jun 2008	A1
20080187175	Kim et al.	Aug 2008	A1
20080188900	Levin et al.	Aug 2008	A1
20080189005	Chilson et al.	Aug 2008	A1
20080201044	Yamada et al.	Aug 2008	A1
20080202243	Gross	Aug 2008	A1
20080225271	Ohmura	Sep 2008	A1
20080253834	Colvard	Oct 2008	A1
20090032560	Strandberg et al.	Feb 2009	A1
20090069967	Reed et al.	Mar 2009	A1
20090076664	McCabe et al.	Mar 2009	A1
20090192710	Eidehall et al.	Jul 2009	A1
20090306835	Ellermann et al.	Dec 2009	A1
20090326763	Rekow	Dec 2009	A1
20100021006	Kim et al.	Jan 2010	A1
20100063663	Tolstedt et al.	Mar 2010	A1
20100063680	Tolstedt et al.	Mar 2010	A1
20100114405	Elston et al.	May 2010	A1
20100145551	Pulskamp et al.	Jun 2010	A1
20100204866	Moshchuk et al.	Aug 2010	A1
20100209888	Huang et al.	Aug 2010	A1
20110018699	Chen et al.	Jan 2011	A1
20110035086	Kim et al.	Feb 2011	A1
20110046813	Castaneda et al.	Feb 2011	A1
20120242455	Hale et al.	Sep 2012	A1
20130197720	Kraimer et al.	Aug 2013	A1
20130294306	Borges et al.	Nov 2013	A1
20140074341	Weiss	Mar 2014	A1
20140266024	Chinnadura et al.	Sep 2014	A1
20150057843	Kraimer et al.	Feb 2015	A1
20150310722	Sousa	Oct 2015	A1
20150315001	Choi	Nov 2015	A1
20160349795	Rosenberg et al.	Dec 2016	A1
20160358389	Menard et al.	Dec 2016	A1
20170010619	Foster et al.	Jan 2017	A1
20170023945	Cavalcanti et al.	Jan 2017	A1
20180182236	Hor-Lao et al.	Jun 2018	A1
20190172340	Goepner	Jun 2019	A1
20200247264	Duckworth et al.	Aug 2020	A1
20200249668	Duckworth et al.	Aug 2020	A1
20220127079	Hagiwara et al.	Apr 2022	A1

Entry
International Search Report and Written Opinion of the International Searching Authority dated Oct. 28, 2021 International Application No. PCT/US2021/040796; European Patent Office; Rijswijk, Netherlands.
Notice of Allowance dated May 4, 2022; U.S. Appl. No. 16/718,473; United States Patent and Trademark Office; Alexandria, Virginia.
Notice of Allowance dated Mar. 28, 2022; U.S. Appl. No. 16/718,411; United States Patent and Trademark Office; Alexandria, Virginia.
Examination Report No. 1 dated May 31, 2022; Australian Application No. 2021209146; IP Australia.
Weber et al.; “Ein tragbares Funk-Fernsteuergerat fur Gewinnungsmaschinen”, Gluckauf, Minova Carbo Tech GmbH; Jul. 13, 1967; pp. 375-378; XP002093388; ISSN; 0340-7896; Essen DE.
Weber, Karl-Heinz et al.; “A Portable Wireless Remote Control Device for Mining Equipment”; Apr. 13, 1967; XP002093388; pp. 375-378, Essen, Germany.
Bourdon, G. et al.; Instantaneous Fuzzy Modelling for Obstacle Avoidance; Systems, Man and Cybernetics Intelligent Systems for the 21st Century; IEEE International Conference; vol. 3; Oct. 22, 1995; pp. 2546-2551; New York, NY; USA.
Durrant-Whyte, Hugh F., “An Autonomous Guided Vehicle for Cargo-Handling Applications;” The International Journal of Robotics Research, vol. 15, Oct. 1996, pp. 407-440.
BT Products AB; “Swedish Industry Standard”; Swedish Industry Standard; 1998.
Urban Challenge; http://www.darpa.mil/grandchallenge/index.asp; Nov. 3, 2007.
Urban Challenge; http://www.darpa.mil/grandchallenge/resources.asp; Nov. 2007.
Congmin, Zhu et al.; AGV Navigation System With Multiple Sensors; Chinese Journal of Scientific Instrument; Nov. 2008; China.
Photograph 3; RS409 Wearable RIng Scanner; http://www.motorola.com/business/v/index.jsp?vgnextoid=5dbee90e3ae95110VgnVCM10; First publication date unknown, and first discovered by the inventors on Oct. 30, 2008.
Yong, Zhou et al.; “Obstacle Detection for AGVS Based on Computer Vision”; Machine Design and Research; May 2008; China.
Photograph 2; TINYOM Hand Free Scanning; http://txcom.com/public/?page=tinyom; First publication date unknown, and first discovered by the inventors on Aug. 10, 2009.
Photograph 4; Peregrine; http://www.theperegrine.com/; First publication date unknown, and first discovered by the inventors on Nov. 23, 2009.
Photograph 1; AirMouse; http://theairmouse.com/; Deanmark Ltd; Ontario, Canada; First publication date unknown, and first discovered by the inventors on Jan. 28, 2010.
Wayback Machine, “Getting Started: a Wall following Robot”; Feb. 2, 2011; <www.mobotsoft.com>.
http://www.cajunbot.com/technology; 2011; Cajun Bot Labs.
http://www.cajunbot.com; 2011; Cajun Bot Labs.
International Search Report & Written Opinion; International Application No. PCT/US2019/067075; dated Mar. 6, 2020; European Patent Office; Rijswijk, Netherlands.
Dungaie, D. et al.; “Higher-order Kalman filter to support fast target tracking in a multi-function radar system;” Publication Year: 1999; pp. 14/1-14/3.
Bhatt, R. et al.; “A real-time guidance system for an autonomous vehicle,” vol. 4; Publication Year: 1987; pp. 1785-1791.
CajunBot Wiki; http:cajunbot.com/wiki/Main_Page; Apr. 18, 2010.
Garcia, Gregory; B.O.S.S. A Battery Operated Smart Servant; EEL 5666c; Intelligent Machines Design Lab Sensor Presentation; Center for Intelligent Machines and Robotics; University of Florida; Aug. 17, 2006.
Kovacs, S. et al.; Interpolation-based Fuzzy Logic Controller, as a Simplified Way for Constructing the Fuzzy Rulebase of the Path Tracking and Collision Avoidance Strategy of an AGV; Systems, Man and Cybernetics; IEEE International Conference; vol. 2; Oct. 11, 1998; pp. 1317-1322; New York, NY; USA.
International Search Report and Written Opinion of the International Searching Authority dated Apr. 14, 2020 International Application No. PCT/US2019/067068; European Patent Office; Rijswijk, Netherlands.
International Preliminary Report on Patentability dated Aug. 12, 2021; International Application No. PCT/US2019/067068; The International Bureau of WIPO; Geneva, Switzerland.
International Preliminary Report on Patentability dated Aug. 12, 2021; International Application No. PCT/US2019/067075; The International Bureau of WIPO; Geneva, Switzerland.
Youtube video dated Mar. 8, 2016 entitled “STILL iGo neo CX 20—oder picking the intelligent way”; https://www.youtube.com/watch?v=pRjn9s9VBho.
Youtube video dated Nov. 29, 2017 entitled “Toyota t-mote: remote drive solution”; https://www.youtube.com/watch?v=HBxFqCBp8r0.
Office Action dated Dec. 7, 2021; U.S. Appl. No. 16/718,411; United States Patent and Trademark Office; Alexandria, Virginia.
Office Action dated Feb. 1, 2022; U.S. Appl. No. 16/718,473; United States Patent and Trademark Office; Alexandria, Virginia.
Extended European Search Report dated Feb. 7, 2022; European Application No. 21204537.1; European Patent Office; Munich, Germany.
Examination Report No. 2 dated Aug. 29, 2022; Australian Application No. 2021209146; IP Australia.
Patent Application entitled “On-Board Charging Station for a Remote Control Device”; filed Jul. 26, 2022; U.S. Appl. No. 17/873,602; United States Patent and Trademark Office; Alexandria, Virginia.
Examination Report No. 1 dated Jun. 24, 2022; Australian Application No. 2019426894; IP Australia.
Trisha M. Luthman et al.; “On-Board Charging Station for a Remote Control Device”; U.S. Appl. No. 18/061,097, filed Dec. 2, 2022.
Sun Hwa Lee; International Preliminary Report on Patentability; International Application No. PCT/US2021/040796; dated Jan. 31, 2023; Geneva, Switzerland.
Khalid Ahmad; Examination Report; Australian Application No. 2021209146; dated Jan. 19, 2023; IP Australia.