This application claims the benefit of the EP Application No. 18198698.5 filed Oct. 4, 2018, which is incorporated herein by reference in its entirety.
The embodiments herein relate to elevator systems, and more particularly to an elevator car position determination in a hoistway using sensor data.
Elevator monitoring systems may have limited information available to track the position of an elevator car in a hoistway. While tracking vertical movement of an elevator car from a ground floor reference point may assist in tracking elevator car position, it is possible for reference information to be lost during a power failure or a maintenance override action such that upon recovery, the position of the elevator car within the hoistway (e.g., a floor number) is not readily known. Inaccurate position tracking can hinder predictive maintenance, reduce functionality, and/or result in other effects.
According to an embodiment, a method includes collecting a calibration set of vibration data for an elevator car at a plurality of landings in a hoistway. One or more characteristic signatures are determined at each of the landings based on the calibration set of vibration data. An analysis set of vibration data is collected for the elevator car. A position of the elevator car is identified in the hoistway based on comparing one or more features of the analysis set of vibration data to the one or more characteristic signatures. An indicator of the position of the elevator car in the hoistway is output.
In addition to one or more of the features described herein, or as an alternative, further embodiments include where the calibration set of vibration data and the analysis set of vibration data are collected from one or more vibration sensors configured to detect vibration associated with movement of at least one elevator door.
In addition to one or more of the features described herein, or as an alternative, further embodiments include where the at least one elevator door includes a combination of at least one elevator car door and at least one elevator landing door.
In addition to one or more of the features described herein, or as an alternative, further embodiments include where the one or more characteristic signatures at each of the landings are determined based on one or more of: a time domain analysis, a frequency domain analysis, and a sequence analysis.
In addition to one or more of the features described herein, or as an alternative, further embodiments include where identifying the position of the elevator car includes performing a matching comparison of the one or more features of the analysis set of vibration data to the one or more characteristic signatures at each of the landings based on one or more of: the time domain analysis, the frequency domain analysis, and the sequence analysis.
In addition to one or more of the features described herein, or as an alternative, further embodiments include where the sequence analysis includes a combination of vibration data collected as the elevator car transitions between two of the landings and vibration data collected at one of the landings corresponding to an elevator door movement.
In addition to one or more of the features described herein, or as an alternative, further embodiments include periodically updating the calibration set of vibration data for the elevator car at the landings in the hoistway.
In addition to one or more of the features described herein, or as an alternative, further embodiments include where outputting the indicator of the position of the elevator car in the hoistway includes sending the indicator to one or more of: a service system and an analysis system.
According to an embodiment, a system includes one or more vibration sensors and an elevator car position monitor operably coupled to the one or more vibration sensors. The elevator car position monitor comprising a processing system configured to perform collecting a calibration set of vibration data from the one or more vibration sensors for an elevator car at a plurality of landings in a hoistway and determining one or more characteristic signatures at each of the landings based on the calibration set of vibration data. The processing system is further configured to perform collecting an analysis set of vibration data for the elevator car, identifying a position of the elevator car in the hoistway based on comparing one or more features of the analysis set of vibration data to the one or more characteristic signatures, and outputting an indicator of the position of the elevator car in the hoistway.
In addition to one or more of the features described herein, or as an alternative, further embodiments include where the one or more vibration sensors are configured to detect vibration associated with movement of at least one elevator door comprising a combination of at least one elevator car door and at least one elevator landing door.
Technical effects of embodiments of the present disclosure include determining an elevator car position in a hoistway using vibration data.
The foregoing features and elements may be combined in various combinations without exclusivity, unless expressly indicated otherwise. These features and elements as well as the operation thereof will become more apparent in light of the following description and the accompanying drawings. It should be understood, however, that the following description and drawings are intended to be illustrative and explanatory in nature and non-limiting.
The present disclosure is illustrated by way of example and not limited in the accompanying figures in which like reference numerals indicate similar elements.
The tension member 107 engages the machine 111, which is part of an overhead structure of the elevator system 101. The machine 111 is configured to control movement between the elevator car 103 and the counterweight 105. The position reference system 113 may be mounted on a fixed part at the top of the elevator shaft 117, such as on a support or guide rail, and may be configured to provide position signals related to a position of the elevator car 103 within the elevator shaft 117. In other embodiments, the position reference system 113 may be directly mounted to a moving component of the machine 111, or may be located in other positions and/or configurations as known in the art. The position reference system 113 can be any device or mechanism for monitoring a position of an elevator car and/or counter weight, as known in the art. For example, without limitation, the position reference system 113 can be an encoder, sensor, or other system and can include velocity sensing, absolute position sensing, etc., as will be appreciated by those of skill in the art.
The controller 115 is located, as shown, in a controller room 121 of the elevator shaft 117 and is configured to control the operation of the elevator system 101, and particularly the elevator car 103. For example, the controller 115 may provide drive signals to the machine 111 to control the acceleration, deceleration, leveling, stopping, etc. of the elevator car 103. The controller 115 may also be configured to receive position signals from the position reference system 113 or any other desired position reference device. When moving up or down within the elevator shaft 117 along guide rail 109, the elevator car 103 may stop at one or more landings 125 as controlled by the controller 115. Although shown in a controller room 121, those of skill in the art will appreciate that the controller 115 can be located and/or configured in other locations or positions within the elevator system 101. In one embodiment, the controller may be located remotely or in the cloud.
The machine 111 may include a motor or similar driving mechanism. In accordance with embodiments of the disclosure, the machine 111 is configured to include an electrically driven motor. The power supply for the motor may be any power source, including a power grid, which, in combination with other components, is supplied to the motor. The machine 111 may include a traction sheave that imparts force to tension member 107 to move the elevator car 103 within elevator shaft 117.
Although shown and described with a roping system including tension member 107, elevator systems that employ other methods and mechanisms of moving an elevator car within an elevator shaft may employ embodiments of the present disclosure. For example, embodiments may be employed in ropeless elevator systems using a linear motor to impart motion to an elevator car. Embodiments may also be employed in ropeless elevator systems using a hydraulic lift to impart motion to an elevator car.
As shown in
An elevator car position monitor 212 can be operably coupled to the elevator car 103 to determine a position of the elevator car 103 in the hoistway 202, such as determining whether the elevator car 103 is at one of the landings 204A-204D or positioned between two of the landings 204A-204D. The elevator car position monitor 212 is configured to gather vibration data that may be associated with movement of the elevator car 103 through the hoistway 202 and/or movement of a component of the elevator system 200, such as movement of one or more elevator doors 210 (e.g., opening/closing). The vibration data can be collected along one or more axis, for instance, to observe vibration along an axis of motion of the one or more elevator doors 210 and vibration during vertical travel of the elevator car 103 in the hoistway 202 (e.g., up/down vibrations 214, side-to-side vibration 216, front/back vibration 218). An example plot 300 of vibration data is depict in
The elevator car position monitor 212 can also include a processing system 406, a memory system 408, and a communication interface 410 among other interfaces (not depicted). The processing system 406 can include any number or type of processor(s) operable to execute instructions. For example, the processing system 406 may be, but is not limited to, a single-processor or multi-processor system of any of a wide array of possible architectures, including field programmable gate array (FPGA), central processing unit (CPU), application specific integrated circuits (ASIC), digital signal processor (DSP) or graphics processing unit (GPU) hardware arranged homogenously or heterogeneously. The memory system 408 may be a storage device such as, for example, a random access memory (RAM), read only memory (ROM), or other electronic, optical, magnetic or any other computer readable storage medium. The memory system 408 is an example of a tangible storage medium readable by the processing system 406, where software is stored as executable instructions for execution by the processing system 406 to cause the system 400 to operate as described herein. The memory system 408 can also store various types of data such as vibration data 420 acquired from the one or more vibration sensors 402 and characteristic signatures 422 to support classification of the vibration data 420 relative to positions within the hoistway 202 of
The communication interface 410 can establish and maintain connectivity over a network 412 using wired and/or wireless links (e.g., Internet, cellular, Wi-Fi, Bluetooth, Z-Wave, ZigBee, etc.) with one or more other systems, such as a service system 414, an analysis system 416, and/or to access various files and/or databases (e.g., software updates). The service system 414 can be a device used by a mechanic or technician to support servicing of the elevator system 200 of
Referring now to
At block 504, the elevator car position monitor 212 determines one or more characteristic signatures 422 at each of the landings 204A-204D based on the calibration set of vibration data 420. The characteristic signatures 422 may be defined and determined using one or more analysis techniques, such as one or more of a time domain analysis, a frequency domain analysis, and a sequence analysis. The time domain analysis can include monitoring for waveform shapes, peaks, phase relationships, slopes, and other such features. Time domain analysis may be performed based on data acquired from the one or more vibration sensors 402 and can include time-based correlations with other data sources, such as audio data, pressure data, and the like. Frequency domain analysis can include performing a domain transform, such as a Fast Fourier Transform, a Wavelet Transform, and other such known transforms, based on time domain data collected from the one or more vibration sensors 402. Frequency domain analysis can be used to examine frequency, magnitude, and phase relationships. Time domain analysis can be used to localize data sets in time, for instance, where a rise in root-mean-square (RMS) occurs during a segment of time, the corresponding segment can be provided for frequency domain analysis. Sequence analysis can include identifying a combination of events or signatures to create a more complex signature. For instance, sequence analysis may include identifying a combination of vibration data 420 collected as the elevator car 103 transitions between two of the landings 204A-204D and vibration data 420 collected at one of the landings 204A-204D corresponding to an elevator door 210 movement. Squeaks, rattles, bumps, imbalances, and other such variations may be localized and repeatable at various positions in the elevator system 200, which can be captured as the characteristic signatures 422.
At block 506, the elevator car position monitor 212 collects an analysis set of vibration data 420 for the elevator car 103. The analysis data set of vibration data 420 can be collected during operation of the elevator car 103. Similar analysis method can be applied to the analysis set of vibration data 420 as used to create the characteristic signatures 422 to perform a matching comparison of one or more features of the analysis set of vibration data 420 to the one or more characteristic signatures 422 at each of the landings 204A-204D based on one or more of: a time domain analysis, a frequency domain analysis, and a sequence analysis. For instance, while the elevator car 103 is halted in the hoistway 202, the elevator car position monitor 212 can collect vibration data 420 from the one or more vibration sensors 402 while the elevator doors 210 are cycled opened and shut as the analysis set of vibration data 420. The analysis set of vibration data 420 can also include data collection while the elevator car travels through the hoistway 202 between the landings 204A-204D.
At block 508, the elevator car position monitor 212 identifies a position of the elevator car 103 in the hoistway 202 based on comparing one or more features of the analysis set of vibration data 420 to the one or more characteristic signatures 422. Features extracted from the analysis set of vibration data 420 can be compared to the characteristic signatures 422 to determine whether the analysis set of vibration data 420 most closely matches vibration pattern 0, 1, 2, 3, or 4 associated with landings 204A-204D, for instance. Tracking of features between the landings 204A-204D, such as vibration signatures associated with a rail misalignment between two of the landings 204A-204D can further assist in identifying the position of the elevator car 103. Further, vertical motion of the elevator car 103 upward or downward may be detected using the one or more vibration sensors 402 to determine a direction of travel of the elevator car 103 and further assist in identifying the position of the elevator car 103.
At block 510, the elevator car position monitor 212 outputs an indicator of the position of the elevator car 103 in the hoistway 202. For example, the elevator car position monitor 212 may send the indicator to one or more of: a service system 414 and an analysis system 416 through network 412 or an alternate communication channel.
As described above, embodiments can be in the form of processor-implemented processes and devices for practicing those processes, such as a processor. Embodiments can also be in the form of computer program code containing instructions embodied in tangible media, such as network cloud storage, SD cards, flash drives, floppy diskettes, CD ROMs, hard drives, or any other computer-readable storage medium, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes a device for practicing the embodiments. Embodiments can also be in the form of computer program code, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into an executed by a computer, the computer becomes an device for practicing the embodiments. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.
The term “about” is intended to include the degree of error associated with measurement of the particular quantity and/or manufacturing tolerances based upon the equipment available at the time of filing the application.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, element components, and/or groups thereof.
Those of skill in the art will appreciate that various example embodiments are shown and described herein, each having certain features in the particular embodiments, but the present disclosure is not thus limited. Rather, the present disclosure can be modified to incorporate any number of variations, alterations, substitutions, combinations, sub-combinations, or equivalent arrangements not heretofore described, but which are commensurate with the scope of the present disclosure. Additionally, while various embodiments of the present disclosure have been described, it is to be understood that aspects of the present disclosure may include only some of the described embodiments. Accordingly, the present disclosure is not to be seen as limited by the foregoing description, but is only limited by the scope of the appended claims.
Number | Date | Country | Kind |
---|---|---|---|
18198698 | Oct 2018 | EP | regional |
Number | Name | Date | Kind |
---|---|---|---|
5306882 | Gerwing et al. | Apr 1994 | A |
5682024 | Koopman, Jr. et al. | Oct 1997 | A |
5736695 | Hoepken | Apr 1998 | A |
6311803 | Turk | Nov 2001 | B1 |
6366532 | Hoepken | Apr 2002 | B1 |
6570817 | Hoepken | May 2003 | B2 |
6659232 | Oelschlegel | Dec 2003 | B2 |
7077244 | Oh et al. | Jul 2006 | B2 |
7484598 | Tyni et al. | Feb 2009 | B2 |
8276716 | Meri et al. | Oct 2012 | B2 |
8307953 | Ferreira | Nov 2012 | B2 |
8540057 | Schuster et al. | Sep 2013 | B2 |
8678143 | Bunter | Mar 2014 | B2 |
9567188 | Huff et al. | Feb 2017 | B2 |
9676591 | Banno | Jun 2017 | B2 |
9809419 | Otsuka et al. | Nov 2017 | B2 |
9926170 | Michel et al. | Mar 2018 | B2 |
20170029244 | Madarasz et al. | Feb 2017 | A1 |
20190002238 | Bogli | Jan 2019 | A1 |
20190367325 | Pahlke | Dec 2019 | A1 |
20190382238 | Witczak | Dec 2019 | A1 |
20190382239 | Witczak | Dec 2019 | A1 |
20200062542 | Sudi | Feb 2020 | A1 |
20200109027 | Witczak | Apr 2020 | A1 |
20200122967 | Sarkar | Apr 2020 | A1 |
Number | Date | Country |
---|---|---|
102112384 | Jun 2011 | CN |
102239102 | Nov 2011 | CN |
105540369 | May 2016 | CN |
105704540 | Jun 2016 | CN |
107810157 | Mar 2018 | CN |
112013006754 | Apr 2019 | DE |
2489621 | Aug 2012 | EP |
3424862 | Jan 2019 | EP |
3632830 | Apr 2020 | EP |
3640188 | Apr 2020 | EP |
05330754 | Dec 1993 | JP |
H06263351 | Sep 1994 | JP |
09208149 | Aug 1997 | JP |
10226470 | Aug 1998 | JP |
2006242826 | Sep 2006 | JP |
2086496 | Aug 1997 | RU |
Entry |
---|
EP Application No. 18198698.5 Extended EP Search Report dated Sep. 19, 2019, 7 pages. |
Number | Date | Country | |
---|---|---|---|
20200109027 A1 | Apr 2020 | US |