Certain aerial work platforms, known as scissor lifts, incorporate a frame assembly that supports a platform. The platform is coupled to the frame assembly using a system of linked supports arranged in a crossed pattern, forming a scissor assembly. As the supports rotate relative to one another, the scissor assembly extends or retracts, raising or lowering the platform relative to the frame. Accordingly, the platform moves primarily or entirely vertically relative to the frame assembly. Scissor lifts are commonly used where scaffolding or a ladder might be used, as they provide a relatively large platform from which to work that can be quickly and easily adjusted to a broad range of heights. Scissor lifts are commonly used for painting, construction projects, accessing high shelves, changing lights, and maintaining equipment located above the ground.
One implementation of the present disclosure is a lift device, according to an exemplary embodiment. The lift device includes a chassis, tractive elements, a platform, a lift assembly, a first set of proximity sensors, and a controller. The tractive elements are rotatably coupled to the chassis and are configured to support the chassis. The platform is disposed above the chassis and includes a deck that extends in a substantially horizontal plane and defines a top surface configured to support an operator. The lift assembly couples the platform to the chassis and is configured to selectably move the platform between a lowered position and a raised position above the lowered position. The first set of proximity sensors are coupled to the platform and are configured to detect a distance of an obstacle relative to a portion of the platform and provide obstacle detection data. The controller is operably coupled with an alert system and configured to receive the obstacle detection data from the first set of proximity sensors. The controller is configured to provide an alert indication to the alert system in response to determining that the obstacle is within a minimum allowable distance from the lift device. The controller is configured to (a) select a subset of the first set of proximity sensors to analyze based on an active function of the lift device and (b) determine whether the obstacle is within the minimum allowable distance from the lift device based on the obstacle detection data from the subset of the first set of proximity sensors.
Another implementation of the present disclosure is a method for providing an alert for a lift device and restricting operation of the lift device, according to an exemplary embodiment. The method includes receiving object detection data from one or more proximity sensors. The method includes determining multiple sensor limit values based on machine function information of the lift device. The method includes determining if an obstacle is present in a stop zone or a warning zone using the received object detection data. The method includes restricting one or more operations of a lift assembly of the lift device and the lift device in response to determining that the obstacle is present in the stop zone. The method includes operating an alert system to provide at least one of a visual and an aural alert in response to determining that the obstacle is present in the warning zone.
Another implementation of the present disclosure is an obstacle detection system for a lift device, according to an exemplary embodiment. The obstacle detection system includes a first set of proximity sensors coupled to a platform of the lift device and oriented at least partially in a downwards direction. The obstacle detection system includes a second set of proximity sensors coupled to the platform. One or more of the second set of proximity sensors are oriented along a longitudinal axis of the platform or in a direction at least partially upwards. The obstacle detection system includes a controller operably coupled with an alert system. The controller is configured to receive obstacle detection data from the first set of proximity sensors and the second set of proximity sensors. The controller is also configured to determine a position of an obstacle relative to the lift device. The controller is also configured to determine if the obstacle is within a warning zone or a stop zone. The controller is also configured to operate the alert system to provide at least one of a visual alert and an aural alert in response to determining that the obstacle is within the warning zone. The controller is configured to restrict one or more operations of the lift device in response to determining that the obstacle is within the stop zone.
The invention is capable of other embodiments and of being carried out in various ways. Alternative exemplary embodiments relate to other features and combinations of features as may be recited herein.
The disclosure will become more fully understood from the following detailed description, taken in conjunction with the accompanying figures, wherein like reference numerals refer to like elements, in which:
Before turning to the FIGURES, which illustrate the exemplary embodiments in detail, it should be understood that the present application is not limited to the details or methodology set forth in the description or illustrated in the FIGURES. It should also be understood that the terminology is for the purpose of description only and should not be regarded as limiting.
Overview
Referring generally to the FIGURES, a lift device is shown, according to various exemplary embodiment. The lift device includes a frame assembly, a lifting assembly, and a platform. The platform includes various proximity sensors disposed about the platform and configured to detect obstacles, objects, obstructions, etc., in areas around the platform (e.g., above the platform, to the sides of the platform, in front of the platform, behind the platform, below the platform, etc.). The proximity sensors may be any sensors configured to measure a relative distance to an object or a proximity sensor configured to determine a relative location of the object. The proximity sensors provide object detection data to a controller. The controller uses the object detection data to determine if an alarm/alert should be provided to the operator of the lift device. The alert may be any of a visual alert and an aural alert. The controller can be configured to differentiate between objects in a warning zone and a stop zone. If objects are detected in the stop zone, or near the stop zone, the controller can restrict one or more operations of the lift device (e.g., extension of the platform). The controller can adjust the areas of the warning zones and/or the stop zones based on a distance between the platform and a ground surface. Advantageously, the controller prevents objects or obstacles from coming too close to the lift device, the platform, and the lift assembly.
Lift Device
According to the exemplary embodiment shown in
Referring again to
Referring to
In some embodiments, the frame assembly 12 is coupled to one or more actuators, shown in
Referring to
One or more actuators (e.g., hydraulic cylinders, pneumatic cylinders, motor-driven leadscrews, etc.), shown as lift actuators 66, are configured to extend and retract the lift assembly 14. As shown in
Referring again to
Referring again to
Referring again to the embodiments of
Referring to
Object/Obstacle Detection System
Referring now to
The lidar sensors 114 may be any proximity sensor configured to emit light (e.g., a laser) and determine proximity as well as relative location of an object (e.g., object 106) within a scan area 84 (see
where c is the speed of light. The angle θ of the object and the lidar sensor 114 may be the angle at which the laser is emitted. From the relative distance d and the angle θ at which the laser/light is emitted, the relative location of the object can be determined. If the lidar sensor 114 does not measure a return of light, this indicates that there is no object present at the current angular position of the lidar sensor 114. The lidar sensors 114 may emit lasers having a wavelength between 600 and 1000 nanometers. In other embodiments, the lidar sensors 114 emit lasers having a wavelength greater than 1000 nanometers (e.g., 1550 nanometers) or shorter than 600 nanometers (e.g., 532 nanometers). The scan area 84 of each of the lidar sensors 114 may be a two dimensional plane such that each of the lidar sensors 114 determines one or more relative locations (e.g., polar coordinates, Cartesian coordinates, etc.) of various points on the object relative to the respective lidar sensor 114.
The ultrasonic sensors 104 are generally oriented outwards and/or upwards, while the lidar sensors 114 are generally oriented downwards. Orienting the lidar sensors 114 downwards facilitates an object detection system 100 that is less prone to obstructions and direct sunlight which could potentially cause inaccurate measurements from the lidar sensors 114. Additionally, the lidar sensors 114 are positioned (and the ultrasonic sensors 104 are oriented) such that the lidar sensors 114 do not interfere with the ultrasonic sensors 104. While the present disclosure refers to lidar sensors and ultrasonic sensors, it is contemplated that other types of sensors could be used. For example, in some embodiments, all of the sensors 104 and 114 are lidar sensors. Any proximity sensor configured to measure the relative location of an object may be used in place of the lidar sensors 114. Likewise, any proximity sensor configured to measure relative distance of an object may be used in place of the ultrasonic sensors 104.
Referring still to
In an exemplary embodiment, lidar sensor 114b is positioned and/or oriented symmetrically/similarly to lidar sensor 114a. Likewise, lidar sensor 114d may be positioned and/or oriented symmetrically/similarly to lidar sensor 114c.
Each of lidar sensors 114 include a central axis 130, according to an exemplary embodiment. Central axis 130 extends radially outwards from a corresponding lidar sensor 114. Central axis 130 may define the orientation of the corresponding lidar sensor 114. For example, as shown in
Referring now to
where r is the distance 82 and θ is the angle 134. The scan area 84 defines a total planar area throughout which objects can be detected by the corresponding lidar sensor 114.
Scan Area and Sensor Orientation
Referring now to
The warning zone 92a and the warning zone 93a may be defined as portions of the scan area 84a directly adjacent the stop zone 90a, according to an exemplary embodiment. The warning zone 92a may have a maximum longitudinal width 146a. Likewise, the warning zone 93a may have a maximum longitudinal width 144a. The warning zone 92a may be defined as any portion of the scan area 84a that lies within the maximum longitudinal width 146a from a first end of the stop zone 90a. Likewise, the warning zone 93a may be defined as any portion of the scan area 84a that lies within the maximum longitudinal width 144a from a second opposite end of the stop zone 90a. In some embodiments, the maximum longitudinal width 144a is substantially equal to the maximum longitudinal width 146a. In other embodiments, the maximum longitudinal width 144a is less than or greater than the maximum longitudinal width 146a. The warning zone 93a of lidar sensor 114a may define an area adjacent the stop zone 90a at the first lateral end 124 of the platform 16. The warning zone 92a may define an area adjacent the stop zone 90a at the second lateral end 126 of the platform 16. The lidar sensor 114a is configured to monitor/detect the presence and relative location of any objects within the scan area 84a. The lidar sensor 114a also detects whether objects within the scan area 84a are within the warning zone 92a, the stop zone 90a, and the warning zone 93a.
As shown in
The lidar sensor 114a is angled about the lateral axis 31 (i.e., the x-direction) such that an angle 132a is defined between the central axis 130a and the longitudinal axis 33. In some embodiments, the angle 132a is substantially equal to 0 degrees such that the lidar sensor 114a points in the y-direction (e.g., points along the longitudinal axis 33). In an exemplary embodiment, the angle 132a is 60 degrees. The angular scan range (e.g., angle 134a) and the orientation of the lidar sensor 114a (e.g., angle 132a) may be adjusted to achieve a desired scan area 84a in some embodiments. The centerline 86a and the longitudinal axis 33 define an angle 150a. Likewise, the centerline 87a and the longitudinal axis 33 define an angle 152a. The angular orientation of the centerline 86a (e.g., angle 150a, the angular position of the first outermost laser or the initial angular position of the lidar sensor 114a) and the angular orientation of the centerline 87a (e.g., angle 152a, the angular position of the other outermost laser or the final angular position of the lidar sensor 114a) can be adjusted to achieve a desired scan area 84a. For example, the angle 150a may be substantially equal to 90 degrees such that the lidar sensor 114a initially (or the first outermost laser of the lidar sensor 114a) points substantially in the negative z-direction (i.e., along the vertical axis 35). Likewise, the angle 152a may be a value (e.g., 0 degrees) such that a portion (e.g., protrusion 160 as shown in
Lidar sensor 114b may be positioned and oriented similarly/symmetrically to lidar sensor 114a. In other embodiments, lidar sensor 114b is positioned similarly/symmetrically to lidar sensor 114a and is mirrored about the x-z plane. Lidar sensor 114b is similarly configured to monitor/detect objects within a scan area 84b. Lidar sensor 114b can be similarly configured to monitor/detect objects within a stop zone 90b, a warning zone 92b, and a warning area 93b. The stop zone 90b of the lidar sensor 114b may be defined similarly to the stop zone 90a of the lidar sensor 114a (e.g., a portion of the scan area 84 below the platform 16 or a portion of the scan area 84 that covers the lift assembly 14). Likewise, the warning area 92b and the warning area 93b of the lidar sensor 114b may be defined similarly to the warning area 92a and the warning zone 93a of the lidar sensor 114a, respectively. However, the lidar sensor 114b is positioned on a longitudinal side (i.e., longitudinal end 122) of the platform 16 opposite the longitudinal side (i.e., longitudinal end 120) of the lidar sensor 114a.
Referring now to
As shown in
The lidar sensor 114d can be configured and oriented similarly to the lidar sensor 114c. For example, the lidar sensor 114d may be configured to monitor/detect objects within a scan area 84d that is similar to the scan area 84c. The lidar sensor 114d may be configured and oriented similar to the lidar sensor 114c, but is positioned at an opposite lateral end (i.e., second lateral end 126 as opposed to first lateral end 124). In other embodiments, one of the lidar sensor 114c and the lidar sensor 114d is oriented such that it points directly downwards (i.e., in the negative z-direction, downwards along the vertical axis 35), while the other one of the lidar sensor 114c and the lidar sensor 114d is oriented at an angle (i.e., angle 132c is greater than or less than 90 degrees). For example, the lidar sensor 114c may be positioned at the first lateral end 124 and oriented as shown in
Referring again to
In some embodiments, if the platform 16 includes extendable decks 78, the upper most guard rail 73 is a telescoping rail. The upper most guard rail 73 includes an outer member 174 and an inner member 172. The outer member 174 is configured to receive the inner member 172 therewithin. When the extendable deck 78 is extended, the outer member 174 moves relative to the inner member 172. If the platform 16 includes the extendable deck 78, the lidar sensor 114a is coupled to a portion that remains stationary relative to the outer member 174 (e.g., to the inner member 172).
The guard rails 72 may include a protrusion 160. The protrusion 160 may be coupled (e.g., coupled directly or coupled indirectly) to outer member 174 such that the protrusion 160 moves relative to the inner member 172 as the extendable deck 78 is extended. The lidar sensor 114a is configured to track a position (e.g., a relative distance) of the protrusion 160 to determine a degree of extension of the extendable deck 78. The lidar sensor 114a may be coupled to a component of the platform 16 that remains stationary relative to the extendable deck 78. In this way, the lidar sensor 114a can monitor a degree of extension of the extendable deck 78.
The lidar sensor 114b that is positioned on the side of the platform 16 opposite the lidar sensor 114a (e.g., on the second longitudinal end 122) may be configured and/or oriented similarly to the lidar sensor 114a. For example, the lidar sensor 114b may be coupled (e.g., mounted) to the platform 16 on the second longitudinal end 122) at any of the positions as described hereinabove with reference to the lidar sensor 114a.
Referring now to
The lidar sensor 114d may be positioned and/or oriented on the opposite end of the platform 16 according to any of the positions and/or orientations of the lidar sensor 114c as described in greater detail hereinabove. For example, the lidar sensor 114d may be coupled to the deck 70 at a lateral midpoint of the deck 70, at a corner of the deck 70, etc., and may be oriented pointing directly downwards, partially downwards, at an angle, etc.
Referring again to
The platform 16 also includes ultrasonic sensor 104a and ultrasonic sensor 104b at the first lateral end 124 of the platform 16. The ultrasonic sensor 104a and the ultrasonic sensor 104b are coupled to a support member 180. The support member 180 may be coupled to the upper most guard rail 73 at the first lateral end 124 of the platform 16. In other embodiments, the ultrasonic sensor 104a and the ultrasonic sensor 104b are coupled directly to the upper most guard rail 73 (e.g., to the outer member 174). The support member 180 may have an overall length substantially equal to or less than an overall lateral length of the platform 16. The ultrasonic sensor 104a and the ultrasonic sensor 104b are positioned a distance apart along the length of the support member 180. The ultrasonic sensor 104a and the ultrasonic sensor 104b may be positioned at opposite ends of the support member 180.
The ultrasonic sensor 104a and the ultrasonic sensor 104b point in a direction at least partially upwards. The ultrasonic sensor 104a and the ultrasonic sensor 104b are configured to detect objects above the platform 16 at the first lateral end 124 of the platform 16 (e.g., beyond the first lateral end 124 of the platform 16 in the positive y direction and above the platform 16 in the positive z direction). In some embodiments, the ultrasonic sensor 104a and the ultrasonic sensor 104b are coupled (either directly, or indirectly by being coupled to the support member 180) to outer member 174 and move relative to inner member 172 as the extendable deck 78 is extended.
The platform 16 also includes ultrasonic sensor 104e and ultrasonic sensor 104d at the second lateral end 126 of the platform 16. The ultrasonic sensor 104e and the ultrasonic sensor 104d may be coupled to a support member 180 at the second lateral end 126 of the platform 16 similar to the support member 180 at the first lateral end 124 of the platform 16. The support member 180 at the second lateral end 126 of the platform 16 may be similar to the support member 180 at the first lateral end 124 of the platform 16 (e.g., coupled to the upper most guard rail 73). The ultrasonic sensor 104e and the ultrasonic sensor 104d may be coupled to the platform 16 and oriented similar to the ultrasonic sensor 104a and the ultrasonic sensor 104b, respectively. For example, the ultrasonic sensor 104e and the ultrasonic sensor 104d may be configured to detect/monitor the presence of objects/obstacles above the platform 16 at the second lateral end 126 of the platform 16 (e.g., to detect/monitor the presence of objects beyond the second lateral end 126 in the negative y direction and above the platform 16 in the positive z direction).
Referring still to
Referring still to
Ultrasonic Sensors
Referring now to
Referring still to
Referring now to
Platform
Referring now to
The platform 16 includes twelve ultrasonic sensors positioned about various members of the platform 16. The platform 16 includes a rail, tubular member, pipe, handle, etc., shown as guard rail 902. The guard rail 902 extends along a portion of a perimeter of a human machine interface (HMI) (e.g., a user interface, a control panel, an operator station, etc.), shown as HMI 1520. The guard rail 902 is extends above the HMI 1520 and can be grasped by a user when the lift assembly 14 is extending or retracting. The guard rail 902 includes an ultrasonic sensor 104a mounted to an upper portion of the guard rail 902 and directed inwards towards an area where a user stands to operate the HMI 1520. The ultrasonic sensor 104a can be configured to detect if a user is leaning over the guard rail 902. Advantageously, the object detection system 100 can use the detection of the user to restrict operation of the lift device 10. For example, if the ultrasonic sensor 104a detects that the user (e.g., the operator) is leaning over the guard rail 902, the object detection system 100 can prevent operation of the lift device 10.
Referring still to
The vertical rail 170a is positioned on the second longitudinal end 122 at the second lateral end 126. Likewise, the vertical rail 170c is positioned on the second longitudinal end 122 at the first lateral end 124. The vertical rail 170 includes ultrasonic sensor 104b, ultrasonic sensor 104c, ultrasonic sensor 104d, and ultrasonic sensor 104e. The ultrasonic sensor 105b and the ultrasonic sensor 104e are positioned at opposite ends of the vertical rail 170a. The ultrasonic sensor 104e points outwards from the platform 16 and at least partially upwards. The ultrasonic sensor 104e points in a direction at least partially along the lateral axis 31 (e.g., the negative x direction) and at least partially along the vertical axis 35. Specifically, the ultrasonic sensor 104e points in a direction parallel with a plane defined by the vertical axis 35 and the lateral axis 31 (e.g., the x-z plane).
The ultrasonic sensor 104b may be oriented similarly to the ultrasonic sensor 104e, but rather than pointing upwards from the platform 16, the ultrasonic sensor 104b points downwards (e.g., at least partially in the negative z-direction). The ultrasonic sensor 104b points in a direction that is co-planar with the direction that the ultrasonic sensor 104e points. An angle defined between the lateral axis 31 and a centerline extending outwards from the ultrasonic sensor 104b may be substantially equal to (although having an opposite sign) an angle defined between the lateral axis 31 and a centerline extending outwards from the ultrasonic sensor 104e.
The vertical rail 170a includes ultrasonic sensor 104c and ultrasonic sensor 104d, according to an exemplary embodiment. The ultrasonic sensor 104c is positioned substantially at a midpoint along the length of the vertical rail 170a. The ultrasonic sensor 104c points in a direction outwards from the platform 16 and substantially along the lateral axis 31. The ultrasonic sensor 104c is configured to monitor/detect the presence of objects to the right of the platform (e.g., to monitor/detect the presence and relative distance of objects beyond the second longitudinal end 122 of the platform 16 along the lateral axis 31 or in the negative x-direction).
The ultrasonic sensor 104d is positioned along the vertical rail 170a substantially at a midpoint between the ultrasonic sensor 104e and the ultrasonic sensor 104c. The ultrasonic sensor 104d points outwards from the platform 16 along the longitudinal axis 33 (e.g., the ultrasonic sensor points in the positive y-direction). The ultrasonic sensor 104d is configured to monitor/detect the presence and relative distance of objects behind the platform 16 (e.g., to monitor/detect the presence and relative distance of objects beyond the second lateral end 126 of the platform 16 along the longitudinal axis 33 or in the positive y-direction).
Referring still to
The vertical rail 170b includes ultrasonic sensor 104h, ultrasonic sensor 104g, and ultrasonic sensor 104f, according to an exemplary embodiment. The ultrasonic sensor 104h may be oriented similarly to the ultrasonic sensor 104e. The ultrasonic sensor 104g is oriented similarly to the ultrasonic sensor 104c. The ultrasonic sensor 104f is oriented similarly to the ultrasonic sensor 104b.
Referring still to
Referring still to
Referring now to
The ultrasonic sensor 104a and the ultrasonic sensor 104b are mounted (e.g., coupled) to the support member 180 at the first lateral end 124. The support member 180 at the first lateral end 124 is coupled (e.g., connected, coupled, fastened, etc.) to the upper most guard rail 73 of the platform 16. The ultrasonic sensor 104a and the ultrasonic sensor 104b are positioned at opposite ends of the support member 180. The ultrasonic sensor 104a points outwards from the platform 16 in a direction at least partially upwards (e.g., at least partially along the vertical axis 35 or at least partially along the positive z direction) and at least partially along the longitudinal axis 33 (e.g., at least partially in the negative y direction). The ultrasonic sensor 104a points in a direction that is substantially parallel to a plane defined by the vertical axis 35 and the longitudinal axis 33 (e.g., the z-y plane). The ultrasonic sensor 104b is oriented similarly to the ultrasonic sensor 104a but is positioned at the opposite end of the support member 180. The ultrasonic sensor 104a and the ultrasonic sensor 104b are configured to monitor/detect the presence and relative distance of objects in front of and above the platform 16 (e.g., to monitor/detect the presence and relative distance of objects beyond the first lateral end 124 of the platform along the longitudinal axis 33 and at least partially above the platform 16 along the vertical axis 35).
The platform 16 includes ultrasonic sensor 104d and ultrasonic sensor 104e coupled to support member 180 at the opposite end of the platform 16 (e.g., at the second lateral end 126 of the platform). The ultrasonic sensor 104d and the ultrasonic sensor 104e are coupled at opposite ends of the support member 180. The ultrasonic sensor 104d and the ultrasonic sensor 104e may be symmetric to the ultrasonic sensor 104b and the ultrasonic sensor 104a about a plane defined by the lateral axis 31 and the vertical axis 35 (e.g., symmetric about the x-y plane). The ultrasonic sensor 104d and the ultrasonic sensor 104e are configured to monitor/detect the presence and relative distance of objects behind and at least partially above the platform 16 (e.g., to monitor/detect the presence and relative distance of objects beyond the second lateral end 126 along the longitudinal axis 33 and at least partially above the platform 16 along the vertical axis 35).
The platform 16 includes ultrasonic sensor 104k and ultrasonic sensor 104j coupled to support member 180 at the first longitudinal end 120 of the platform 16. The ultrasonic sensor 104k and the ultrasonic sensor 104j point in a direction outwards from the platform 16, at least partially along the lateral axis 31 (e.g., at least partially in the positive x direction), and at least partially along the vertical axis 35 (e.g., at least partially in the positive z direction). The ultrasonic sensor 104k and the ultrasonic sensor 104j may both point in directions that are substantially parallel to a plane defined by the vertical axis 35 and the lateral axis 31 (e.g., the x-z plane). The ultrasonic sensor 104k and the ultrasonic sensor 104j are positioned at opposite ends of the support member 180. The ultrasonic sensor 104k and the ultrasonic sensor 104j are configured to monitor/detect the presence and relative distance of objects to the right of and at least partially above the platform 16 (e.g., to monitor/detect the presence and relative distance of objects beyond the first longitudinal end 120 of the platform 16 in a direction at least partially along the lateral axis 31 (e.g., the positive x-direction) and at least partially above the platform 16 along the vertical axis 35 (e.g., the positive z-direction)).
The platform 16 includes ultrasonic sensor 104i and ultrasonic sensor 104h coupled to support member 180 at the second longitudinal end 122 of the platform 16. The ultrasonic sensor 104i and the ultrasonic sensor 104h may be symmetric and similar to the ultrasonic sensor 104k and the ultrasonic sensor 104j about a plane defined by the vertical axis 35 and the longitudinal axis 33 (e.g., symmetric about the z-y plane). The ultrasonic sensor 104i and the ultrasonic sensor 104h are configured to monitor/detect the presence and relative distance of objects beyond the second longitudinal end 122 along the lateral axis 31 (e.g., objects beyond the platform 16 in the negative x direction) and at least partially above the platform 16 along the vertical axis 35 (e.g., objects above the platform 16 in the positive z direction).
Referring still to
Extendable Deck
Referring to
The controller 1500 can determine a current value of Δl based on a current y coordinate of the protrusion 160 relative to the lidar sensor 114a and a known longitudinal distance 812 between the lidar sensor 114a and the protrusion 160 when the extendable deck 78 is in the fully retracted position. The controller 1500 can determine the displacement Δl of the extendable deck 78 using the equation Δl=y−ydistance where Δl is the distance 802, y is a current longitudinal distance between the lidar sensor 114a and the protrusion 160, and ydistance is the known longitudinal distance 812 of the protrusion 160 from the lidar sensor 114a when the extendable deck 78 is fully retracted, and 0≤Δl≤lmax. The controller 1500 can also determine the value of Δl periodically over a time interval Δt to determine a rate of change of extension or retraction of the extendable deck 78. The protrusion 160 may be an additional component (e.g., a bar, a beam, a pipe, an extension, etc.) coupled to any of the extendable deck 78, a vertical rail 170 that moves with the extendable deck 78, the outer member 174 of the upper most guard rail 73, etc., or any other component of the platform 16 that moves with the extendable deck relative to the lidar sensor 114a. In other embodiments, the protrusion 160 is a component of the extendable deck 78 such as one of the vertical rails 170, a portion of one of the vertical rails 170, a portion of the extendable deck 78, a portion of the outer member 174 of the upper most guard rail 73, etc. In some embodiments, the “top beam” of the lidar sensor 114a monitors the extension of the extendable deck 78.
Advantageously, using the lidar sensor 114a to monitor the extension of the extendable deck 78 removes the need to use an extension sensor. The lidar sensor 114a can be used for object detection around the platform 16 (e.g., below the platform 16) and also to determine if the extendable deck 78 is fully extended, fully retracted, or at some position between fully extended and fully retracted (e.g., 50% extended, 75% extended, etc.).
Referring again to
In some embodiments, the controller 1500 uses the measured values of the longitudinal width 140 of the lift assembly 14 and/or the angle 306 (or angle 308) to adjust the stop zone 90 and/or the warning zones 93 and 92. For example, the controller 1500 may use the measured value of the longitudinal width 140 to adjust the longitudinal width 142a of the stop zone 90a or to adjust the longitudinal width 142b of the stop zone 90b. For example, as the platform 16 is raised due to the extension of the lift assembly 14 and the longitudinal width 140 of the lift assembly 14 decreases, the longitudinal width 142a of the stop zone 90a may also decrease. Likewise, the longitudinal width 144a of the warning zone 93a and the longitudinal width 146a of the warning zone 92a may decrease as the platform 16 is raised and the longitudinal width 140 of the lift assembly 14 decreases. In other embodiments, as the platform 16 is raised and the longitudinal width 140 of the lift assembly 14 decreases, the longitudinal width 142a of the stop zone 90a decreases but the longitudinal width 144a of the warning zone 93a and the longitudinal width 146a of the warning zone 92a increase or remain constant.
Controller
Referring now to
The controller 1500 includes a processing circuit 1502, a processor 1504, and memory 1506. The processor 1504 can be a general purpose or specific purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable processing components. The processor 1504 is configured to execute computer code or instructions stored in the memory 1506 or received from other computer readable media (e.g., CDROM, network storage, a remote server, etc.), according to some embodiments.
The memory 1506 can include one or more devices (e.g., memory units, memory devices, storage devices, etc.) for storing data and/or computer code for completing and/or facilitating the various processes described in the present disclosure. The memory 1506 can include random access memory (RAM), read-only memory (ROM), hard drive storage, temporary storage, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and/or computer instructions. The memory 1506 can include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. The memory 1506 can be communicably connected to the processor 1504 via the processing circuit 1502 and can include computer code for executing (e.g., by the processor 1504) one or more processes described herein.
The controller 1500 may a communications interface (not shown), according to some embodiments. The communications interface can include any number of jacks, wire terminals, wire ports, wireless antennas, or other communications interfaces for communicating information (e.g., sensory information) and/or control signals (e.g., control signals for controllable elements 1518, alert signals for alert system 1516, etc.). The communications interface facilitates a communicable connection between the controller 1500 and any of the lidar sensors 114, the ultrasonic sensors 104, the lift assembly sensor 115, the HMI 1520, the alert system 1516, the controllable elements 1518, etc., or any other sensors, systems, controllers and/or controllable elements of the lift device 10). For example, the communications interface can be configured to receive an analog or a digital signal of the sensory information from the lift assembly sensor 115, the lidar sensors 114, the ultrasonic sensors 104, etc. In some embodiments, the communications interface is configured to receive a user input from the HMI 1520. The communications interface can be a digital output (e.g., an optical digital interface) configured to provide a digital control signal to the controllable elements 1518 and/or the alert system 1516. In other embodiments, the communications interface is configured to provide an analog output signal to the alert system 1516 and/or the controllable elements 1518. In some embodiments, the communications interface is configured to provide display signals to HMI 1520 to display an indication of a detected object in any of the warning zones 92, the warning zones 93, and the stop zones 90.
Referring still to
The sensor limit manager 1508 can also provide the object detection manager 1510 with sensor limits for the ultrasonic sensors 104. For example, the sensor limit manager 1508 may provide the object detection manager 1510 with various sensor limits of each of the one or more ultrasonic sensors 104 indicating a warning zone and a stop zone. The sensor limits of the ultrasonic sensors 104 provided to the object detection manager 1510 by the sensor limit manager 1508 can define a minimum allowable distance between an object and any of the ultrasonic sensors 104. The minimum allowable distance may be a closest allowable distance between the platform 16 and the obstacle before the platform 16 is restricted from operating in a direction (e.g., extending) that would cause a collision. For example, the sensor limit manager 1508 may provide the object detection manager 1510 with a minimum allowable distance of 6 feet for one or more of the ultrasonic sensors 104, indicating that if any of the one or more ultrasonic sensors 104 detect that an object is 6 feet (or less) away from the platform 16, the platform 16 should not be allowed to be extended. In other embodiments, the sensor limit manager 1508 provides the object detection manager 1510 with a warning range, and the minimum allowable distance for any of the ultrasonic sensors 104. The warning range can indicate that if an object is detected by any of the ultrasonic sensors 104 within the warning range (e.g., between 6 and 10 feet away from the platform 16), an alert/alarm should be provided to the user. It should be understood that the warning range and the minimum allowable distance for the ultrasonic sensors 104 may be the same for each, or may vary based on the orientation and placement of the ultrasonic sensor 104. For example, one or more of the ultrasonic sensors 104 may have a first warning range and a first minimum allowable distance, while another one or more of the ultrasonic sensors may have a second warning range and a second minimum allowable distance. The sensor limit manager 1508 can determine any of the sensor limits based on known orientations and positions of each of the ultrasonic sensors 104 and/or the lidar sensors 114.
The controller 1500 can also be configured to receive machine function information from the HMI 1520. In other embodiments, the controller 1500 is configured to receive sensory information (e.g., from a GPS, a speed sensor, extension sensors, various feedback sensors, etc.) that indicate the machine function information. The machine function information can indicate any currently performed operations of the lift device 10. For example, the machine function information may indicate a direction of travel of the lift device 10, whether the lift assembly 14 is being raised or lowered, a direction of travel of the platform 16, etc. The sensor limit manager 1508 and/or the object detection manager 1510 can use the machine function information to perform their respective functions. For example, the sensor limit manager 1508 may adjust or define the sensor limits based on the machine function information. According to one example, the sensor limit manager 1508 may adjust the warning zone and/or the stop zone based on the machine function information. For example, the sensor limit manager 1508 may increase a size of the warning zone and/or the stop zone that is in front of the lift device 10 if the machine function information indicates that the lift device 10 is driving forwards.
The object detection manager 1510 can be similarly configured to receive and use the machine function information. In some embodiments, the object detection manager 1510 uses the machine function information to determine which of the ultrasonic sensors 104 and the lidar sensors 114 should be monitored/evaluated. For example, if the machine function information indicates that the lift device 10 is travelling forwards, the object detection manager 1510 may monitor and/or evaluate the object detection data received form the ultrasonic sensors 104 and the lidar sensors 114 that are oriented forwards. In this way, the object detection manager 1510 may use the machine function information to identify which of the ultrasonic sensors 104 and/or the lidar sensors 114 are relevant to object detection given the operation of the lift device 10.
In other embodiments, one of the lidar sensors 114 points downwards and is configured to measure a distance between the bottom of the platform 16 and the ground surface or the top of the frame assembly 12. In this case, the sensor limit manager 1508 can use the distance measured by the lidar sensor 114 to determine adjustments to the stop zones 90, the warning zones 92, and/or the warning zones 93.
The object detection manager 1510 is configured to receive the sensor limits from the sensor limit manager 1508 and the object detection data from the lidar sensors 114 and the ultrasonic sensors 104. The object detection manager 1510 uses the sensor limits and the object detection data to determine if any objects are within any of the stop zones 90, the warning zones 92, and/or the warning zones 93. The object detection manager 1510 is configured to output detected object data. The object detection data indicates whether or not an object is present in any of the stop zones 90, the warning zones 93, the warning zones 92, as well as a position, shape, size, etc., of the detected objects. The object detection manager 1510 can also determine if an object is within the warning range of the ultrasonic sensors 104 or if an object is at the minimum allowable distance relative to any of the ultrasonic sensors 104.
The memory 1506 also includes an alert system manager 1512. The alert system manager 1512 is configured to receive the detected object data from the object detection manager 1510 and provide alert signals to alert system 1516. The alert system manager 1512 receives the detected object data, and depending on whether or not the detected object data indicates the presence of an object within the stop zones 90, the warning zones 92, and the warning zones 93, outputs alert signals to the alert system 1516. For example, the alert system manager 1512 may receive the detected object data from the object detection manager 1510 indicating that an object is present within one of the warning zones 92. In response to receiving an indication that an object is within one of the warning zones 92, the alert system manager 1512 outputs alert signals to the alert system 1516 to cause the alert system 1516 to provide an appropriate alert to the operator. For example, in the case when an object is detected within one of the stop zones 90, the alert system manager 1512 may output alert signals to the alert system 1516 to cause the visual alert devices 1522 to provide a visual alert to the operator (e.g., a flashing light, a steady red light, etc.) and to cause the aural alert device(s) 1524 to provide an aural alert to the operator (e.g., a siren, intermittent beeping, a warning voice, etc.).
The alert system manager 1512 can cause the alert system 1516 to provide different alerts based on if an object is detected within one of the warning zones 92 or one of the warning zones 93, or if the object is detected within one of the stop zones 90. For example, if an object is detected within one of the warning zones 93 or one of the warning zones 92 (or a certain warning zone 93 or a certain warning zone 92), the alert system manager 1512 may cause the alert system 1516 to provide only a visual alert to the user via the visual alert devices 1522. However, if an object is detected at one of the stop zones 90, the alert system manager 1512 may cause the alert system 1516 to provide both a visual alert and an aural alert to the user via the visual alert device(s) 1522 and the aural alert device(s) 1524. In other embodiments, the alert system manager 1512 causes the alert system 1516 to provide different alerts based on a proximity between the detected object and any of the stop zones 90 (or between the detected object and the lift device 10). For example, the alert system manager 1512 may cause the alert system 1516 to provide only a visual alert via the visual alert device(s) 1522 is the detected object is at an outer bounds of the warning zones 93 or the warning zones 92, and both a visual and an aural alert if the detected object is near one of the stop zones 90 but within one of the warning zones 93 and/or one of the warning zones 92.
The alert system manager 1512 can also be configured to cause the alert system 1516 to display an approximate location of the detected object. For example, if an object is detected below the platform 16, the alert system manager 1512 may cause the alert system 1516 to display a visual alert (e.g., a message, a notification, a particular pattern of lights, etc.) indicating the that an object is below the platform. The alert system manager 1512 can also be configured to cause the alert system 1516 to display (via the visual alert device(s) and/or the aural alert device(s) 1524) an approximate distance between the detected object and the lift device 10 (e.g., a notification such as “WARNING: OBJECT WITHIN 20 FEET”).
In some embodiments, the alert system 1516 is integrated with the HMI 1520. For example, the HMI 1520 may include any or all of the visual alert device(s) 1522 (e.g., a screen, a display device, a user interface, etc.) or any or all of the aural alert device(s) 1518 (e.g., speakers, alarms, buzzers, etc.).
The alert system 1516 can also operate the visual alert device(s) 1522 and/or the aural alert device(s) 1524 to provide a directional alert. For example, some of the visual alert device(s) 1522 and/or the aural alert device(s) 1524 may be positioned at a front end of the lift device 10 (e.g., at a front end of the platform 16, first lateral end 124, etc.) while others of the visual alert device(s) 1522 and/or the aural alert device(s) 1524 are positioned at a rear end (e.g., second lateral end 126) of the lift device 10 (e.g., at the rear end of the platform 16). The controller 1500 can operate the visual alert device(s) 1522 and/or the aural alert device(s) 1524 to provide the directional alert. For example, if an object or obstacle is detected in a warning zone in front of the lift device 10, the controller 1500 (e.g., the alert system manager 1512) may operate the visual alert device(s) 1522 and/or the aural alert device(s) 1524 that are at the front end of the lift device 10 to provide a visual alert and/or an aural alert. Likewise, if the controller 1500 detects that an obstacle is rearwards of the lift device 10, the alert system manager 1512 may operate the visual alert device(s) 1522 and/or the aural alert device(s) 1524 at the rear end of the lift device 10 to provide their respective visual and/or aural alerts. The alert system manager 1512 may also use the machine function information to determine which of the visual alert device(s) 1522 and/or the aural alert device(s) 1524 should be operated. For example, if the machine function information indicates that the lift device 10 is travelling forwards and the controller 1500 determines that an object is present in the warning zone and/or the stop zone in front of the lift device 10, the alert system manager 1512 may operate the visual alert device(s) 1522 and/or the aural alert device(s) 1524 that are at the front end of the lift device 10 to provide their respective visual and/or aural alerts.
The memory 1506 includes a control signal generator 1514. The control signal generator 1514 is configured to receive the detected object data from the object detection manager 1510 as well as a user input from the HMI 1520. The control signal generator 1514 can also receive user inputs or information from a sensor or the primary driver 44 indicating a direction and speed of travel of the lift device 10 (e.g., 5 mph in the forward/positive y direction). The user input received from the HMI 1520 may be any of a command from the operator to extend the lift assembly 14 (e.g., raise the platform 16), retract the lift assembly 14 (e.g., lower the platform 16), drive the lift device 10 (e.g., along the longitudinal axis 33 in either direction), steer the lift device 10 (e.g., rotate the tractive assemblies 40), etc. The control signal generator 1514 is configured to receive the user inputs from the HMI 1520 and generate control signals for controllable elements 1518 of the lift device 10. The controllable elements 1518 may be any components of the lift device 10 that cause the lift device 10 to operate (e.g., that cause the lift assembly 14 to extend, retract, etc.). For example, the controllable elements 1518 may include any of the lift actuators 66, the primary driver 44, the pump 46, motors, engines, hydraulic valves, etc., of the lift device 10.
The control signal generator 1514 can restrict the operation of one or more of the controllable elements 1518 based on the detected object data received from the object detection manager 1510. For example, if the detected object data indicates that an object is detected within one of the stop zones 90, the control signal generator 1514 may restrict the lift device 10 from driving in the direction of the object. In another example, if an object is detected below the platform 16, the control signal generator 1514 may restrict the lift assembly 14 from being retracted (e.g., restrict the platform 16 from being lowered). In yet another example, if an object is detected above the platform 16 and is substantially at the minimum allowable distance relative to one of the ultrasonic sensors 104, the control signal generator 1514 may restrict extension of the lift assembly 14 (e.g., restrict the platform 16 from being raised/elevated).
The control signal generator 1514 can also be configured to restrict additional user inputs from being provided to the controllable elements 1518 if the user input would cause the lift device 10 to move or extend in a direction towards a detected obstacle. In some embodiments, the control signal generator 1514 only restricts additional user inputs if the detected object is at the minimum allowable distance relative to one of the ultrasonic sensors 104 or the detected object is at the transition between one of the stop zones 90 and one of the warning zones 92/93 and the user input would cause the detected object to be within one of the stop zones 90 or within the minimum allowable distance relative to one of the ultrasonic sensors 104. However, the control signal generator 1514 may still generate and send control signals to the controllable elements 1518 if the user input would cause the platform 16 and/or the lift device 10 to move away from the detected object.
The control signal generator 1514 can also use the direction of travel of the lift device 10 to determine if an alert should be provided to the user. For example, if an object is detected by ultrasonic sensor 104a in front of the lift device 10 (e.g., in front of the platform 16), but the direction of travel of the lift device 10 is in an opposite direction (e.g., away from the object such that the distance between the object and the lift device 10 is increasing), the control signal generator 1514 may determine that an alert should not be provided to the user. In another example, if the lift device 10 is travelling towards an obstacle (e.g., an obstacle is detected by ultrasonic sensor 104a in front of the lift device 10 and the lift device 10 is travelling in the forwards/positive y direction), the control signal generator 1514 may provide alert system manager 1512 with an indication that an alert should be provided to the user via the alert system 1516.
In some embodiments, the control signal generator 1514 ceases restricting certain user inputs (as described in greater detail above) in response to receiving an override command from the HMI 1520.
The object detection manager 1510 can be configured to monitor the extension of the extendable deck 78 using any of the techniques, methods, and functionality as described in greater detail above with reference to
The control signal generator 1514 receives the value of Δl and determines if the extendable deck 78 is extended (i.e., if Δl=0). If the extendable deck 78 is extended, the control signal generator 1514 may restrict one or more operations of the lift device 10. For example, if Δl>0, the control signal generator 1514 may restrict any of the extension of the lift assembly 14 (e.g., restrict the platform 16 from being elevated), the retraction of the lift assembly 14 (e.g., restrict the platform 16 from moving towards the ground), driving/steering of the lift device 10 (e.g., restrict the primary driver from causing the tractive assemblies 40 to rotate), until the extendable deck 78 is not extended (i.e., Δl is substantially equal to zero).
Alert Process
Referring now to
Process 1600 includes receiving object detection information from one or more proximity sensors (step 1602). The one or more proximity sensors may be any of lidar sensors (e.g., lidar sensors 114), ultrasonic sensors (e.g., ultrasonic sensors 104), radar detection devices, laser rangefinders, sonar detection devices, etc., or any other proximity sensors positioned about the lift device 10. Step 1602 can be performed by the controller 1500 or any other computing device of the lift device 10.
Process 1600 includes receiving lift assembly extension information (step 1604). The lift assembly extension information may be received from one of the lidar sensors 114 (e.g., the lidar sensor 114a) and can indicate a distance between the lidar sensor 114 and a portion of the extendable deck 78 (e.g., protrusion 160) that moves relative to the lidar sensor 114 with extension of the extendable deck 78. Step 1604 may be performed by controller 1500. Specifically, step 1604 may be performed by the object detection manager 1510 of the controller 1500.
Process 1600 includes determining whether or not the extendable deck 78 is extended (steps 1606 and 1608). Determining whether or not the extendable deck 78 is extended can include determining whether or not the extendable deck 78 is fully retracted (i.e., Δl=0), if the extendable deck 78 is fully extended (i.e., Δl=lmax) or if the extendable deck 78 is at a position between fully retracted and fully retracted (i.e., 0<Δl<lmax). If the extendable deck 78 is fully retracted (i.e., Δl is substantially equal to 0, step 1608 “NO”), process 1600 proceeds to step 1612. If the extendable deck 78 is at least partially extended (i.e., Δl>0, step 1608 “YES”), process 1600 proceeds to step 1610. Steps 1606 and 1608 may be performed by the controller 1500. Specifically, steps 1606 and 1608 may be performed by the object detection manager 1510 and/or the control signal generator 1514 of the controller 1500.
If the extendable deck 78 is at least partially extended (or fully extended), one or more operations of the lift assembly 14 and/or one or more operations of the lift device 10 are restricted (step 1610). Step 1610 can include restricting the extension and the retraction of the lift assembly 14 (such that the platform 16 does not move upwards or downwards while the extendable deck 78 is extended), and/or restricting the lift device 10 from being driven. Step 1610 may be performed by controller 1500. Specifically, step 1610 can be performed by the control signal generator 1514. Step 1610 can include restricting all operations of the lift assembly 14 and/or all operation of the lift device 10 until the extendable deck 78 is fully retracted. Process 1600 returns to step 1602 in response to performing step 1610. Steps 1604-1610 may be optional steps.
If the extendable deck 78 is not extended (step 1608, “NO”), process 1600 proceeds to determining sensor limits (step 1612). Determining the sensor limits (step 1612) may include determining an area of the stop zones 90 for each of the lidar sensors 114, an area of the warning zones 92 for each of the lidar sensors 114, and an area of the warning zones 93 for each of the lidar sensors 114. The sensor limits may be determined based on information received from the lift assembly sensor 115 that indicates a degree of extension of the lift assembly 14. For example, the longitudinal width 142a can be determined based on the distance 304 between the ground and the bottom of the platform 16. Step 1612 can be performed by the controller 1500. Specifically, step 1612 can be performed by the sensor limit manager 1508 of the controller 1500. Step 1612 may include determining (or retrieving) minimum allowable distances for each of the ultrasonic sensors 104 and/or warning ranges for each of the ultrasonic sensors 104.
Process 1600 includes receiving machine function information (step 1613), according to some embodiments. The machine function information can be a currently performed operation (e.g., a current driving operation such as forwards or rearwards motion, a current steering operation indicating a direction of travel of the lift device 10, a current operation of the lift assembly 14 such a raising or lowering the lift assembly 14, etc.). The machine function information can be used to determine which of the object detection information should be evaluated to detect the presence of obstacles surrounding the lift device 10. For example, if the machine function information indicates that the lift device 10 is driving forwards, the controller 1500 can evaluate the object detection information received from proximity sensors that face forwards (e.g., in a direction of travel of the lift device 10).
Process 1600 includes determining if an object is in any of the stop zones 90 or in any of the warning zones 92, or in any of the warning zones 93 (step 1614). Step 1616 can be performed based on the object detection information from any of the proximity sensors (e.g., the lidar sensors 114, the ultrasonic sensors 104) received in step 1602 and the sensor limits determined in step 1612 (e.g., the defined area of each of the stop zones 90, each of the warning zones 92, and each of the warning zones 93). Step 1614 can be performed by controller 1500. Specifically, step 1614 can be performed by object detection manager 1510. In some embodiments, step 1614 includes determining if an object is present in a stop zone or a warning zone based on the received object detection information and/or based on the machine function information. For example, if the lift assembly 14 is being raised, the controller 1500 may evaluate the object detection information received from proximity sensors that are above the lift device 10. Likewise, if the lift assembly 14 is being lowered, the controller 1500 may evaluate the object detection information received from proximity sensors that detect objects/obstacles below the lift device 10 (e.g., below the platform 16).
Process 1600 includes determining if an object is in any of the stop zones 90 (step 1616) or if an object is in any of the warning zones 92/93 (step 1618). Step 1616 can include determining if an object is at a transition between a stop zone 90 and an adjacent warning zone 92 or an adjacent warning zone 93. If an object is within one of the stop zones 90 or is at the transition between one of the stop zones 90 and the adjacent warning zones 93 or is at the transition between one of the stop zones and the adjacent warning zone 92 (step 1616 “YES”), process 1600 proceeds to step 1620. If an object is within one of the warning zones 92 or within one of the warning zones 93 (step 1618 “YES”), process 1600 proceeds to step 1622. Steps 1616 and 1618 may be performed concurrently. Steps 1616 and 1618 may be performed by the object detection manager 1510. Process 1600 proceeds to step 1626 in response to performing step 1618 (i.e., in response to “NO” for step 1618).
Process 1600 includes restricting one or more operations of the lift assembly 14 and/or one or more operations of the lift device 10 (step 1620) in response to determining that an object is in one of the stop zones 90 or at a transition between one of the stop zones 90 and an adjacent warning zone 92/93 (step 1616 “YES”). Step 1620 can include restricting the lift assembly 14 and/or the lift device 10 from moving in the direction of the detected object. However, the lift assembly 14 and/or the lift device 10 can still operate to move away from the detected object, according to some embodiments. Step 1620 can be performed by the control signal generator 1514 and the controllable elements 1518. Process 1600 proceeds to step 1622 in response to performing step 1620. Step 1622 and step 1620 may be performed concurrently with each other.
Process 1600 includes providing an alert to a user (step 1622) in response to determining that an object is present in one of the stop zones 90 (step 1616, “YES”) or in response to determining that an object is present in any of the warning zones 92/93 (step 1618, “YES”). The alert provided to the user may be any of a visual alert, an aural alert, or a combination of both. The alert may be provided to the user via the alert system 1516. More specifically, the visual alert may be provided to the user via visual alert device(s) 1522, and the aural alert can be provided to the user via aural alert device(s) 1524. The type of visual and/or the type of aural alert can be provided based on a distance between the detected object and any of the lift assembly 14, the platform 16, and the frame assembly 12. For example, if an object is detected at the transition between one of the stop zones 90 and an adjacent one of the warning zones 92/93, the alert provided to the user may be both a visual and an aural alert. In another example, if an object is detected within one of the warning zones 92/93 but is not at the transition between the stop zone 90 and the adjacent warning zones 92/93, the alert provided to the user may be only a visual alert or only an aural alert. Process 1600 proceeds to step 1626 in response to performing step 1622.
Process 1600 can be repeated (step 1626) over an entire duration of the operation of the lift device 10. Any of steps 1602-1626 may be performed concurrently with each other. Process 1600 can be performed in real-time to provide real time alerts to the user during operation of the lift device 10.
Configuration of Exemplary Embodiments
The present disclosure contemplates methods, systems, and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a machine, the machine properly views the connection as a machine-readable medium. Thus, any such connection is properly termed a machine-readable medium. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
As utilized herein, the terms “approximately”, “about”, “substantially”, and similar terms are intended to have a broad meaning in harmony with the common and accepted usage by those of ordinary skill in the art to which the subject matter of this disclosure pertains. It should be understood by those of skill in the art who review this disclosure that these terms are intended to allow a description of certain features described and claimed without restricting the scope of these features to the precise numerical ranges provided. Accordingly, these terms should be interpreted as indicating that insubstantial or inconsequential modifications or alterations of the subject matter described and claimed are considered to be within the scope of the invention as recited in the appended claims.
It should be noted that the terms “exemplary” and “example” as used herein to describe various embodiments is intended to indicate that such embodiments are possible examples, representations, and/or illustrations of possible embodiments (and such term is not intended to connote that such embodiments are necessarily extraordinary or superlative examples).
The terms “coupled,” “connected,” and the like, as used herein, mean the joining of two members directly or indirectly to one another. Such joining may be stationary (e.g., permanent, etc.) or moveable (e.g., removable, releasable, etc.). Such joining may be achieved with the two members or the two members and any additional intermediate members being integrally formed as a single unitary body with one another or with the two members or the two members and any additional intermediate members being attached to one another.
References herein to the positions of elements (e.g., “top,” “bottom,” “above,” “below,” “between,” etc.) are merely used to describe the orientation of various elements in the figures. It should be noted that the orientation of various elements may differ according to other exemplary embodiments, and that such variations are intended to be encompassed by the present disclosure.
Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Conjunctive language such as the phrase “at least one of X, Y, and Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to convey that an item, term, etc. may be either X, Y, Z, X and Y, X and Z, Y and Z, or X, Y, and Z (i.e., any combination of X, Y, and Z). Thus, such conjunctive language is not generally intended to imply that certain embodiments require at least one of X, at least one of Y, and at least one of Z to each be present, unless otherwise indicated.
It is important to note that the construction and arrangement of the systems as shown in the exemplary embodiments is illustrative only. Although only a few embodiments of the present disclosure have been described in detail, those skilled in the art who review this disclosure will readily appreciate that many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.) without materially departing from the novel teachings and advantages of the subject matter recited. For example, elements shown as integrally formed may be constructed of multiple parts or elements. It should be noted that the elements and/or assemblies of the components described herein may be constructed from any of a wide variety of materials that provide sufficient strength or durability, in any of a wide variety of colors, textures, and combinations. Accordingly, all such modifications are intended to be included within the scope of the present inventions. Other substitutions, modifications, changes, and omissions may be made in the design, operating conditions, and arrangement of the preferred and other exemplary embodiments without departing from scope of the present disclosure or from the spirit of the appended claim.
The present application claims the benefit of U.S. Provisional Patent Application No. 62/819,226, filed on Mar. 15, 2019, and U.S. Provisional Patent Application No. 62/734,192, filed on Sep. 20, 2018, both of which are incorporated herein by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
6578694 | Harris et al. | Jun 2003 | B2 |
6609603 | Cole | Aug 2003 | B2 |
6799934 | Bartlett | Oct 2004 | B1 |
7108473 | Bartlett | Sep 2006 | B2 |
7578379 | Gillmore et al. | Aug 2009 | B2 |
7648015 | Gillmore et al. | Jan 2010 | B2 |
8051970 | Shaber et al. | Nov 2011 | B2 |
20050187712 | Callaghan | Aug 2005 | A1 |
20170131716 | Brekke et al. | May 2017 | A1 |
20180057333 | Gale et al. | Mar 2018 | A1 |
Number | Date | Country |
---|---|---|
3 173 369 | May 2017 | EP |
3173369 | May 2017 | EP |
3 339 240 | Jun 2018 | EP |
Entry |
---|
International Search Report and Written Opinion regarding Application No. PCT/US2019/051947, dated Jan. 10, 2020, 15 pps. |
Number | Date | Country | |
---|---|---|---|
20200095105 A1 | Mar 2020 | US |
Number | Date | Country | |
---|---|---|---|
62819226 | Mar 2019 | US | |
62734192 | Sep 2018 | US |