Elevator system floor height mapping

Abstract

A method for generating a floor height map for an elevator system having an elevator car traveling in a hoistway includes: accessing operation group data, the operation group data including information corresponding to multiple operations of the elevator car in multiple floor travels by the elevator car; evaluating potential floor heights and potential floor travel sequences for at least one floor of the hoistway in response to the operation group data; determining the likelihood of each combination of potential floor heights and potential floor travel sequences in the multiple floor travels; selecting the potential floor height and the potential floor travel sequence as a selected floor height and a selected floor travel sequence in response to the likelihood; and generating a floor height map in response to the selected floor height and the selected floor travel sequence.

Description

Technical Field

[0001] Embodiments herein relate to the field of conveying systems, and in particular to methods and apparatus for mapping floor heights in an elevator system. Background Art

[0002] Elevator systems typically employ a condition-based maintenance (CBM) process in order to detect existing or potential maintenance items. Existing CBM processes can detect noise or vibration as the elevator car moves along the hoistway. The noise or vibration can also be measured when doors (e.g., landing doors and / or elevator car doors) are opened and closed. It would be beneficial to determine where the noise or vibration occurs in the elevator system so that maintenance personnel can more easily diagnose and resolve maintenance items. Summary of the invention

[0003] According to an embodiment, a method for generating a floor height map for an elevator system having an elevator car traveling in a shaft includes: accessing operation group data, the operation group data including information corresponding to multiple operations of the elevator car in multiple floor traversals by the elevator car; evaluating potential floor heights and potential floor travel sequences for at least one floor of the shaft in response to the operation group data; determining the likelihood of each combination of potential floor heights and potential floor travel sequences in the multiple floor traversals; in response to the likelihood, selecting the potential floor height and the potential floor travel sequence as a selected floor height and a selected floor travel sequence; and generating a floor height map in response to the selected floor height and the selected floor travel sequence.

[0004]

[0013] In addition to or as an alternative to one or more of the features described herein, further embodiments may include wherein the run group data includes a number of downward runs by the elevator car and a number of upward runs by the elevator car.

[0005] In addition or alternatively to one or more of the features described herein, further embodiments may include wherein the run group data includes the position of the elevator car at the end of each run group.

[0006] In addition or alternatively to one or more of the features described herein, further embodiments may include wherein the position of the elevator car at the end of each run group includes an absolute position.

[0007] In addition or alternatively to one or more of the features described herein, further embodiments may include wherein the position of the elevator cars at the end of each run group includes a relative position.

[0008] In addition or alternatively to one or more of the features described herein, further embodiments may include wherein the position of the elevator car at the end of each run group includes an absolute position and a relative position.

[0009] In addition to, or as an alternative to, one or more of the features described herein, further embodiments may include providing a floor height map to a maintenance system.

[0010] According to another embodiment, an elevator system includes: an elevator car that travels in a hoistway; a sensing device that is fixed to the elevator car, the sensor device generating operation data corresponding to the travel of the elevator car from one floor to another floor; a remote system that communicates with the sensing device, the remote system configured to execute a process, the process including: accessing operation group data, the operation group data including information corresponding to multiple operations of the elevator car in multiple floor traversals by the elevator car; evaluating potential floor heights and potential floor travel sequences for at least one floor of the hoistway in response to the operation group data; determining the likelihood of each combination of potential floor heights and potential floor travel sequences in multiple floor traversals; in response to the likelihood, selecting the potential floor height and the potential floor travel sequence as a selected floor height and a selected floor travel sequence; generating a floor height map in response to the selected floor height and the selected floor travel sequence.

[0011] In addition to, or as an alternative to, one or more of the features described herein, further system embodiments may include where the operational set data is generated by a remote system.

[0012] In addition to or as an alternative to one or more of the features described herein, further system embodiments may include wherein the run group data includes a number of downward runs by the elevator car and a number of upward runs by the elevator car.

[0013] In addition or alternatively to one or more of the features described herein, further system embodiments may include wherein the run group data includes the position of the elevator car at the end of each run group.

[0014] In addition to or in the alternative to one or more of the features described herein, further system embodiments may include wherein the position of the elevator car at the end of each run group includes an absolute position.

[0015] In addition or alternatively to one or more of the features described herein, further system embodiments may include wherein the position of the elevator cars at the end of each run group includes a relative position.

[0016] In addition to or in the alternative to one or more of the features described herein, further system embodiments may include wherein the position of the elevator car at the end of each run group includes an absolute position and a relative position.

[0017] In addition to or as an alternative to one or more of the features described herein, further system embodiments may include where the remote system is further configured to provide a floor height map to the maintenance system.

[0018] According to another embodiment, a computer program product embodied on a non-transitory computer-readable medium includes instructions that, when executed by a processor, cause the processor to perform operations including: accessing operation group data, the operation group data including information corresponding to multiple operations of an elevator car in multiple floor traversals by the elevator car; evaluating potential floor heights and potential floor travel sequences for at least one floor of a shaft in response to the operation group data; determining the likelihood of each combination of potential floor heights and potential floor travel sequences in the multiple floor traversals; selecting a potential floor height and a potential floor travel sequence as a selected floor height and a selected floor travel sequence in response to the likelihood; and generating a floor height map in response to the selected floor height and the selected floor travel sequence.

[0019] Technical effects of embodiments of the present disclosure include the ability to map landing heights in an elevator system.

[0020] Unless otherwise expressly indicated, the aforementioned features and elements may be combined in various combinations without exclusivity. These features and elements and their operation will become more apparent from the following description and accompanying drawings. However, it should be understood that the following description and drawings are intended to be illustrative and explanatory and non-restrictive in nature. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The present disclosure is illustrated by way of example and not limitation in the accompanying figures, in which like references indicate similar elements.

[0022] Figure 1 is a schematic illustration of an elevator system in which various embodiments of the present disclosure may be employed;

[0023] FIG. 2 is a diagram for use in an embodiment according to the present disclosure Figure 1 A schematic diagram of a sensor system for an elevator system;

[0024] Figure 3 is a schematic illustration of locations of sensing devices of the sensor system of FIG. 2 according to an embodiment of the present disclosure;

[0025] Figure 4is a schematic illustration of a sensing device of the sensor system of FIG. 2 according to an embodiment of the present disclosure; and

[0026] Figure 5 is a schematic illustration of a remote system according to an embodiment of the present disclosure;

[0027] Figure 6 Depicting examples of elevator car operations; and

[0028] Figure 7 is a flowchart of a method of mapping floor heights according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0029] Figure 1 1 is a perspective view of an elevator system 101 including an elevator car 103, a counterweight 105, a tension member 107, a guide rail 109, a machine 111, a position reference system 113, and a controller 115. The elevator car 103 and the counterweight 105 are connected to each other by the tension member 107. The tension member 107 may include or be configured as, for example, a rope, a steel cable, and / or a coated steel belt. The counterweight 105 is configured to balance the load of the elevator car 103 and to facilitate movement of the elevator car 103 in the elevator hoistway 117 and along the guide rail 109 relative to the counterweight 105 simultaneously and in opposite directions.

[0030] Tension member 107 engages machine 111, which is part of the overhead structure of elevator system 101. Machine 111 is configured to control movement between elevator car 103 and counterweight 105. Position reference system 113 may be mounted on a fixed portion at the top of elevator shaft 117, such as on a support or guide rail, and may be configured to provide a position signal related to the position of elevator car 103 within elevator shaft 117. In other embodiments, position reference system 113 may be mounted directly to the moving member of machine 111, or may be located in other locations and / or configurations as known in the art. As known in the art, position reference system 113 may be any device or mechanism for monitoring the position of an elevator car and / or counterweight. As will be appreciated by those skilled in the art, for example and without limitation, position reference system 113 may be an encoder, sensor, or other system, and may include speed sensing, absolute position sensing, etc.

[0031] As shown, the controller 115 is located in a controller room 121 of the elevator shaft 117 and is configured to control the operation of the elevator system 101 (and in particular the elevator car 103). For example, the controller 115 may provide a drive signal to the machine 111 to control the acceleration, deceleration, level, stop, etc. of the elevator car 103. The controller 115 may also be configured to receive a position signal from the position reference system 113 or any other desired position reference device. When the elevator car 103 moves up or down in the elevator shaft 117 along the guide rail 109, the elevator car 103 may stop at one or more landings 125 when controlled by the controller 115. Although shown in the controller room 121, those skilled in the art will appreciate that the controller 115 may be located and / or constructed in other places or locations within the elevator system 101. In one embodiment, the controller may be located remotely or in the cloud.

[0032] The machine 111 may include a motor or similar drive mechanism. According to an embodiment of the present 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 is combined with other components to supply the motor. The machine 111 may include a traction wheel that imparts force to the tension member 107 to move the elevator car 103 within the elevator shaft 117.

[0033] Although shown and described with a roping system including tension members 107, elevator systems that employ other methods and mechanisms for moving an elevator car within an elevator hoistway may employ embodiments of the present disclosure. For example, embodiments may be employed in ropeless elevator systems that use linear motors to impart motion to an elevator car. Embodiments may also be employed in ropeless elevator systems that use hydraulic hoists to impart motion to an elevator car. Embodiments may also be employed in ropeless elevator systems that use self-propelled elevator cars (e.g., friction wheels or beam climbers). Figure 1 These non-limiting examples are presented for illustrative and explanatory purposes only.

[0034] Now refer to FIG. 2, wherein continue to refer to Figure 1, a view of a sensor system 200 including a sensing device 210 according to an embodiment of the present disclosure is shown. The sensing device 210 is configured to detect sensor data 202 of the elevator car 103 and transmit the sensor data 202 to the remote system 280. The sensor data 202 may include, but is not limited to, pressure data 314, vibration signals (i.e., vibrations over a period of time) or acceleration 312, and derivatives or integrals of the acceleration 312 of the elevator car 103, such as, for example, distance, speed, jerk, bump, quick motion, etc. The pressure data 314 may include the atmospheric pressure within the elevator shaft 117. It should be understood that, although specific systems are defined individually in the schematic block diagram, each or any of the systems may be combined or separated via hardware and / or software in addition. For example, the sensing device 210 may be a single sensor or may be a plurality of individual sensors interconnected.

[0035] In an embodiment, the sensing device 210 is configured to transmit the raw and unprocessed sensor data 202 to the controller 115 of the elevator system 101 for processing. In another embodiment, the sensing device 210 is configured to process the sensor data 202 by a processing method such as, for example, edge processing before transmitting the sensor data 202 to the controller 115. In another embodiment, the sensing device 210 is configured to transmit the raw and unprocessed sensor data 202 to the remote system 280 for processing. In yet another embodiment, the sensing device 210 is configured to process the sensor data 202 by a processing method such as, for example, filtering before transmitting the sensor data 202 to the remote system 280.

[0036] Processing of the sensor data 202 may reveal data such as, for example, number of elevator door openings / closings, elevator door times, vibrations, vibration signatures, number of elevator rides, elevator ride performance, elevator travel time, relevel events, setbacks, x, y acceleration of the elevator car 103 at a location: (i.e., track topology), x, y vibration signatures of the elevator car 103 at a location: (i.e., track topology), door performance at a floor level, nudge events, vandalism events, emergency stops, etc.

[0037] The remote system 280 may be a computing device such as, for example, a desktop, a server, a cloud-based computer, and / or a cloud-based artificial intelligence (AI) computing system. The remote system 280 may include a processor 282 and an associated memory 284, the memory 284 including computer executable instructions that, when executed by the processor 282, cause the processor 282 to perform various operations. The processor 282 may be, but is not limited to, a single processor or multi-processor system in any of a wide variety of possible architectures, including uniformly or non-uniformly arranged field programmable gate arrays (FPGAs), central processing units (CPUs), application specific integrated circuits (ASICs), digital signal processors (DSPs), or graphics processing units (GPUs) hardware. The memory 284 may be, but is not limited to, random access memory (RAM), read-only memory (ROM), or other electronic, optical, magnetic, or any other computer-readable medium. The remote system 280 includes a network connection to communicate with the elevator system 101 via the network 250.

[0038] The sensing device 210 is configured to transmit the sensor data 202 to the controller 115 or the remote system 280 via the short-range wireless protocol 203 and / or the long-range wireless protocol 204. The short-range wireless protocol 203 may include, but is not limited to, Bluetooth, BLE Wi-Fi, HaLow (801.11ah), zWave, ZigBee, or wireless M-Bus. Using the short-range wireless protocol 203, the sensing device 210 is configured to transmit the sensor data 202 directly to the controller 115 or the local gateway device 240, and the local gateway device 240 is configured to transmit the sensor data 202 to the remote system 280 or to the controller 115 through the network 250. The network 250 may be a wired network or a wireless network. Using the long-range wireless protocol 204, the sensing device 210 is configured to transmit the sensor data 202 to the remote system 280 through the network 250. Long-range wireless protocols 204 may include, but are not limited to, cellular, LTE (NB-IoT, CAT M1), LoRa, Satellite, Ingenu, or SigFox. Network 250 may employ both wireless and / or wired connections. For example, data from sensing device 210 may be transmitted to local gateway device 240 using a wireless connection, which is then transmitted to remote system 280 via a wired / wireless connection.

[0039] The sensing device 210 may be configured to detect sensor data 202 including acceleration in any number of directions. In an embodiment, as shown in FIG. 2 , the sensing device may detect sensor data 202 including acceleration 312 along three axes (X axis, Y axis, and Z axis). As shown in FIG. 2 , the X axis may be perpendicular to the door 104 of the elevator car 103. As shown in FIG. 2 , the Y axis may be parallel to the door 104 of the elevator car 103. As shown in FIG. 2 , the Z axis may be aligned vertically parallel to the elevator shaft 117 and the gravity pull. The acceleration data 312 may show vibration signals generated along the X axis, the Y axis, and the Z axis.

[0040] The sensor system 200 includes a static pressure sensor 228A configured to detect static pressure data 314A including static atmospheric pressure. The static pressure sensor 228A is located at a static or stationary location outside the elevator car 103. Therefore, changes in static atmospheric pressure can be caused only by weather and not by movement of the elevator car 103.

[0041] The static pressure sensor 228A is configured to transmit the static pressure data 314A to the controller 115 or the remote system 280 via the short-range wireless protocol 203 and / or the long-range wireless protocol 204. The short-range wireless protocol 203 may include, but is not limited to, Bluetooth, Wi-Fi, HaLow (801.11ah), zWave, ZigBee, or wireless M-Bus. The long-range wireless protocol 204 may include, but is not limited to, cellular, LTE (NB-IoT, CAT M1), LoRa, satellite, Ingenu, or SigFox. Using the short-range wireless protocol 203, the static pressure sensor 228A is configured to transmit the static pressure data 314A directly to the controller 115 or the local gateway device 240. The local gateway device 240 is configured to transmit the static pressure data 314A to the remote system 280 through the network 250. The network 250 may be a wired network (e.g., the Internet) or a wireless network (e.g., cellular).

[0042] The remote system 280 may communicate with the maintenance system 500. The maintenance system 500 may be a computing device, such as, for example, a desktop, a server, a cloud-based computer, and / or a cloud-based artificial intelligence (AI) computing system. The maintenance system 500 may be implemented using the same device that implements the remote system 280. The maintenance system 500 uses the floor height map obtained from the remote system 280 to evaluate condition-based maintenance for the elevator system 101. The maintenance system 500 may also communicate with the sensing device 210 through the remote system 280 or directly through the network 250. The data from the sensing device 210 is communicated to the maintenance system 500. In this way, the maintenance system 500 may associate the data from the sensing device 210 with the floor map from the remote system 280. For example, the maintenance system 500 may receive an indication of excessive door noise at an absolute position of 3.1 meters in the hoistway 117. The maintenance system 500 uses the floor height map from the remote system 280 to determine that the absolute position of 3.1 meters corresponds to the 2nd floor of the building. This allows maintenance personnel to be directed to the correct floor of the elevator system 101 for evaluating the excess noise.

[0043] Figure 3 1 shows a possible installation location of the sensing device 210 within the elevator system 101. The sensing device 210 may include a magnet (not shown) to removably attach to the elevator car 103. Figure 3 In the illustrated embodiment shown in FIG. 1 , the sensing device 210 may be mounted on the door hanger 104a and / or the door 104 of the elevator system 101. It is to be understood that the sensing device 210 may also be mounted in other locations besides the door hanger 104a and the door 104 of the elevator system 101. It is also to be understood that in FIG. Figure 3 104 to illustrate various locations of the sensing devices 210, and embodiments disclosed herein may include one or more sensing devices 210. In another embodiment, the sensing device 210 may be attached to the door lintel 104e of the door 104 of the elevator car 103. In another embodiment, the sensing device 210 may be located on the door lintel 104e near the top 104f of the elevator car 103. In another embodiment, the sensing device 210 is mounted elsewhere on the elevator car 103, such as, for example, directly on the door 104.

[0044] like Figure 3 As shown in FIG. 1 , the sensing device 201 may be located in a selected area 106 on the elevator car 103, such as Figure 3104e. The door 104 is operably connected to the door lintel 104e by a door hanger 104a located near the top 104b of the door 104. The door hanger 104a includes a guide wheel 104c that allows the door 104 to slide open and closed along the guide rail 104d on the door lintel 104e. Advantageously, the door hanger 104a is an area that is easily accessible to attach the sensing device 210 because the door hanger 104a is accessible when the elevator car 103 is at the landing 125 and the elevator door 104 is open. Therefore, it is possible to install the sensing device 210 without taking special measures to take control of the elevator car 103. For example, because it is the normal operating mode for the door 104 to be open at the landing 125, the additional safety of an emergency door stop to keep the elevator door 104 open is unnecessary. The door hanger 104a also provides sufficient clearance for the sensing device 210 during operation of the elevator car 103, such as, for example, the opening and closing of the door 104. Due to the mounting location of the sensing device 210 on the door hanger 104a, the sensing device 210 can detect the opening and closing motion (i.e., acceleration) of the door 104 of the elevator car 103 and the door at the landing 125. In addition, mounting the sensing device 210 on the hanger 104a allows the ride quality of the elevator car 103 to be recorded.

[0045] Figure 4 Show Figure 2 and Figure 3 It should be understood that although in Figure 4 Specific systems are defined individually in the schematic block diagrams of the present invention, and each or any of the systems may be combined or separated via hardware and / or software. Figure 4 As shown in FIG. 2 , the sensing device 210 may include a controller 212 , a plurality of sensors 217 in communication with the controller 212 , a communication module 220 in communication with the controller 212 , and a power source 222 electrically connected to the controller 212 .

[0046] The plurality of sensors 217 include an inertial measurement unit (IMU) sensor 218 (e.g., an accelerometer) configured to detect sensor data 202 including acceleration 312 of the sensing device 210 and the elevator car 103 when the sensing device 210 is attached to the elevator car 103. The IMU sensor 218 may be a sensor such as, for example, an accelerometer, a gyroscope, or a similar sensor known to those skilled in the art. The acceleration 312 detected by the IMU sensor 218 may include the acceleration 312 and a derivative or integral of the acceleration, such as, for example, velocity, jerk, bump, jerk, etc. The IMU sensor 218 communicates with the controller 212 of the sensing device 210.

[0047] The plurality of sensors 217 includes a pressure sensor 228 configured to detect sensor data 202 including pressure data 314, such as, for example, the atmospheric pressure within the elevator shaft 117. In two non-limiting examples, the pressure sensor 228 can be a pressure altimeter or a barometric altimeter. The pressure sensor 228 can communicate with the controller 212.

[0048] The plurality of sensors 217 may also include additional sensors including, but not limited to, a microphone 230, a humidity sensor 232, and a temperature sensor 234. The microphone 230 is configured to detect sensor data 202 including audible sounds and sound levels. The microphone 230 may be in communication with the controller 212. The humidity sensor 232 is configured to detect sensor data 202 including humidity levels. The humidity sensor 232 may be in communication with the controller 212. The temperature sensor 234 is configured to detect sensor data 202 including temperature levels. The temperature sensor 234 may be in communication with the controller 212. The temperature data from the temperature sensor 234 and / or the humidity data from the humidity sensor 232 may be used to calibrate the pressure data received from the pressure sensor 228.

[0049] The controller 212 of the sensing device 210 includes a processor 214 and an associated memory 216, which includes computer executable instructions that, when executed by the processor 214, cause the processor 214 to perform various operations, such as, for example, pre-processing or processing sensor data 202 collected by the IMU sensor 218, the pressure sensor 228, the microphone 230, the humidity sensor 232, and the temperature sensor 234. The processor 214 can be, but is not limited to, a single processor or a multi-processor system in any of a wide variety of possible architectures, including uniformly or non-uniformly arranged field programmable gate arrays (FPGAs), central processing units (CPUs), application specific integrated circuits (ASICs), digital signal processors (DSPs), or graphics processing units (GPUs) hardware. The memory 216 can be a storage device such as, for example, a random access memory (RAM), a read-only memory (ROM), or other electronic, optical, magnetic, or any other computer-readable medium.

[0050] The power source 222 of the sensing device 210 is configured to store and supply electrical power to the sensing device 210. The power source 222 may include an energy storage system such as, for example, a battery system, a capacitor, or other energy storage systems known to those skilled in the art. The power source 222 may also generate electrical power for the sensing device 210. The power source 222 may also include an energy generation or power collection system such as, for example, a synchronous generator, an induction generator, or other types of generators known to those skilled in the art.

[0051] The sensing device 210 includes a communication module 220 configured to allow the controller 212 of the sensing device 210 to communicate with the remote system 280, the local gateway device 240, and / or the controller 115 via at least one of the short-range wireless protocol 203 and the long-range wireless protocol 204. The communication module 220 may be configured to communicate with the remote system 280 using the short-range wireless protocol 203, such as, for example, Bluetooth, BLE, Wi-Fi, HaLow (801.11ah), Wireless M-Bus, zWave, ZigBee, or other short-range wireless protocols known to those skilled in the art. As described above, using the short-range wireless protocol 203, the communication module 220 is configured to transmit the sensor data 202 to the local gateway device 240, and the local gateway device 240 is configured to transmit the sensor data 202 to the remote system 280 via the network 250. The communication module 220 can be configured to communicate with the remote system 280 using a long-range wireless protocol 204, such as, for example, cellular, LTE (NB-IoT, CAT M1), LoRa, Ingenu, SigFox, Satellite, or other long-range wireless protocols known to those skilled in the art. Using the long-range wireless protocol 204, the communication module 220 is configured to transmit the sensor data 202 to the remote system 280 through the network 250. In an embodiment, the short-range wireless protocol 203 is a sub-GHz wireless M-Bus. In another embodiment, the long-range wireless protocol is SigFox. In another embodiment, the long-range wireless protocol is LTE NB-IoT or CAT M1 with 2G, 3G backup.

[0052] Figure 5Components of a remote system 280 according to an embodiment of the present disclosure are depicted. The remote system 280 stores run group data 402, which includes information corresponding to multiple runs of the elevator car 103. A run of the elevator car 103 corresponds to the travel of the elevator car 103 from one floor (or landing) to another floor (or landing). Run data for one or more runs of the elevator car 103 can be collected into the run group data. The run group data can include the number of downward runs, the number of upward runs, and one or both of the following: (i) the sum of the relative positions of each run, and (ii) the final absolute position of the elevator car 103. The absolute position of the elevator car 103 can be determined from the pressure sensor 228 data. The relative position of the elevator car 103 can be determined from the IMU sensor 218 data. The relative position of the elevator car 103 is the distance traveled by the elevator car 103 from the starting position to the stopping position. As is known in the art, acceleration data from the IMU sensor may be processed (eg, integrated twice) to provide distance. The run set data 402 may be stored in the memory 284 of the remote system 280 .

[0053] The sensor accuracy information 404 provides data corresponding to the measurement tolerance of one or more sensors of the sensor device 210. The sensor accuracy information 404 may be represented as a positive or negative value to indicate the degree of measurement accuracy of the one or more sensors of the sensor device 210. The sensor accuracy information 404 may be stored in the memory 284 of the remote system 280.

[0054] The unit data 406 represents information related to the building in which the elevator car 103 is traveling. The unit data 406 may include a list of floors that are accessible by the elevator car 103. For example, a building may have 20 floors, but floors 3-7 are not accessible by the elevator car 103. As also described herein, the unit data 406 reflects that floors 3-7 are not accessible by the elevator car 103, and the unit data 406 is useful in mapping the heights of the elevator floors. The unit data 406 may be stored in the memory 284 of the remote system 280.

[0055] The estimation engine 408 performs a floor height mapping process to determine the height of each floor in the elevator system 101 that can be accessed by the elevator car 103. The estimation engine 408 can be implemented by the processor 282 of the remote system 280. The estimation engine 408 processes the run group data 402, which includes the number of downward runs, the number of upward runs, and one or both of the following for each run group: (i) the sum of the relative positions of each run of the run group, and (ii) the final absolute position of the elevator car 103 at the end of the run group. Each run of the elevator car 103 will include a starting and ending absolute position and / or relative position, indicating the distance traveled between the starting position and the ending position. The relative position at the end of the run group is determined by summing the relative travel of the elevator car 103 for each run of the run group.

[0056] From the operational group data, the estimation engine 408 evaluates potential floor heights and potential floor travel sequences, and selects the floor heights and floor travel sequences with the greatest likelihood of occurrence based on the operational group data. The selected floor heights and the selected floor travel sequences are used to derive a floor height map 410 that associates floor numbers with heights in the hoistway 117. The floor height map 410 is provided to the maintenance system 500. The maintenance system 500 uses the floor height map to determine at which floor a maintenance task is required.

[0057] Figure 6 An example of an elevator car 103 performing five runs is depicted, along with absolute and relative positions. Absolute position can be measured relative to a reference datum in the hoistway 117. Relative position will have a sign corresponding to the direction of travel (e.g., negative for downward travel and positive for upward travel). Relative position is measured from the immediately previous stopping location of the elevator car 103. Figure 6 , the elevator car 103 initially stops at the 3rd floor, where the absolute position is 0.1 m. The elevator car 103 travels to the 1st floor and stops, which results in an absolute position of -5.8 m and a relative position of -5.9 m. The elevator car 103 travels to the 2nd floor and stops, which results in an absolute position of -3 m and a relative position of 2.8 m. The elevator car 103 travels to the 3rd floor and stops, which results in an absolute position of 0.4 m and a relative position of 3.4 m. The elevator car 103 travels to the 1st floor and stops, which results in an absolute position of -5.7 m and a relative position of -6.1 m.

[0058] Run data (e.g., absolute position and / or relative position) about each run may be arranged into run group data. The run group data includes the number of down runs, the number of up runs, and one or both of: (i) the sum of the relative positions of each run, and (ii) the final absolute position of the elevator car 103. Figure 6In the example of , the first three runs are arranged in run group 1, and the final run is arranged in run group 2.

[0059] Figure 7 4 is a flow chart of a method of mapping floor heights performed by the estimation engine 408. At 702, the remote system 280 accesses the operation group data 402. The operation group data may be determined at the elevator system 101 (e.g., by the local gateway device 240) and then transmitted to the remote system 280. Alternatively, the operation data from the sensing device 210 may be transmitted to the remote system 280, which then organizes the operation data into the operation group data.

[0060] At 704, the estimation engine 408 evaluates potential floor heights and potential floor travel sequences in response to the operational set data. Figure 6 In the example of , the operation data includes absolute positions of 0.1m, -5.8m, -3m, 0.4m, -5.7m. The estimation engine 408 also determines that three floors are visited by the elevator car based on prior data about the expected distances between floors. The relative position provides the travel distance as -5.9m, 2.8m, 3.4m, and -6.1m, and the direction as down, up, up, down.

[0061] At 706, the estimation engine 408 determines the likelihood of a combination of potential floor heights and potential floor travel sequences obtained from the run group data in the observed floor walk. The estimation engine 408 searches through all possible floor travel sequences that make this possible in a prioritized manner, such as (3, 1, 2, 3, 1), (3, 1, 2, 3, 2), (2, 1, 2, 3, 2), etc. For each floor travel sequence, the estimation engine 408 determines the likelihood that the elevator car will travel in that floor travel sequence. The estimation engine 408 will know the total number of floors visited during the time period corresponding to the run group data. If the number of visited floors is not available, two options are considered. If the run group data covers a long period of time, the estimation engine 408 assumes that all floors have been visited at least once. In addition, the estimation engine 408 can learn the number of visited floors by trying num_floors = 2, 3, 4, etc. until an acceptable learning error is achieved (e.g., set by a threshold).

[0062] At 708, the estimation engine 408 selects the floor height and floor travel order that yields the greatest likelihood. Figure 6 In the example of , the estimation engine 408 will return the selected floor travel order (3, 1, 2, 3, 1), where the selected floor heights are (0, 2.9, 5.9).

[0063] At 710, the estimation engine generates a floor height map 410 based on the selected floor heights and the selected floor travel order. The floor height map associates floor numbers with heights in the hoistway 117. The floor height map may then be provided to the maintenance system 500 for CBM operations.

[0064] Although the above description describes the Figure 7 It should be understood that the order of the steps may vary unless otherwise specifically required in the appended claims.

[0065] As described above, embodiments may be in the form of processor-implemented processes and devices for practicing those processes, such as a processor in remote system 280. Embodiments may also be in the form of computer program code containing instructions embodied in tangible media, such as network cloud storage, SD card, flash drive, floppy disk, CD ROM, hard drive, or any other computer-readable storage medium. Embodiments may also be in the form of computer program code transmitted on some transmission medium, such as on a wire or cable, through optical fiber, or via electromagnetic radiation. When implemented on a general-purpose microprocessor, the computer program code configures the microprocessor to produce specific logic circuits.

[0066] The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit 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 also be 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 exclude the presence or addition of one or more other features, integers, steps, operations, element components, and / or groups thereof.

[0067] Those skilled in the art will appreciate that various exemplary embodiments are shown and described herein, each having certain features in a particular embodiment, but the present disclosure is not limited thereby. On the contrary, the present disclosure may be modified to incorporate any number of variations, alterations, substitutions, combinations, sub-combinations, or equivalent arrangements not previously described but commensurate with the scope of the present disclosure. In addition, although various embodiments of the present disclosure are described, it is to be understood that aspects of the present disclosure may include only some of the described embodiments. Therefore, the present disclosure is not to be considered as limited by the foregoing description, but only by the scope of the appended claims.

Claims

1. A method of generating a floor height map for an elevator system having an elevator car traveling in a hoistway, the method comprising: accessing run group data, the run group data comprising information corresponding to a plurality of runs of an elevator car for traversing a plurality of floors by the elevator car, wherein the run group data comprises a position of the elevator car at the end of each run group, and wherein the position of the elevator car at the end of each run group comprises an absolute position and / or a relative position; evaluating a potential floor height and a potential floor travel sequence for at least one floor of the hoistway in response to the operational set data; determining a likelihood of each combination of potential floor heights and potential floor travel sequences for the plurality of floor traversals; responsive to the likelihood, selecting a potential floor height and a potential floor travel sequence as a selected floor height and a selected floor travel sequence; The floor height map is generated in response to the selected floor heights and the selected floor travel order.

2. The method according to claim 1, characterized in that The operation group data includes the number of downward operations by the elevator car and the number of upward operations by the elevator car.

3. The method according to claim 1, characterized in that The method also includes providing the floor height map to a maintenance system.

4. An elevator system, comprising: an elevator car that travels in the hoistway; a sensing device secured to the elevator car, the sensor device generating operational data corresponding to travel of the elevator car from one floor to another; a remote system in communication with the sensing device, the remote system being configured to perform a process comprising: accessing run group data, the run group data comprising information corresponding to a plurality of runs of the elevator car for traversing a plurality of floors of the elevator car, wherein the run group data comprises a position of the elevator car at the end of each run group, and wherein the position of the elevator car at the end of each run group comprises an absolute position and / or a relative position; evaluating a potential floor height and a potential floor travel sequence for at least one floor of the hoistway in response to the operational set data; determining a likelihood of each combination of potential floor heights and potential floor travel sequences for the plurality of floor traversals; responsive to the likelihood, selecting a potential floor height and a potential floor travel sequence as a selected floor height and a selected floor travel sequence; A floor height map is generated in response to the selected floor heights and the selected floor travel order.

5. The elevator system according to claim 4, characterized in that The operational group data is generated by the remote system.

6. The elevator system according to claim 4, characterized in that The operation group data includes the number of downward operations by the elevator car and the number of upward operations by the elevator car.

7. The elevator system according to claim 4, characterized in that The remote system is also configured to provide the floor height map to a maintenance system.

8. A computer program product embodied on a non-transitory computer readable medium, the computer program product comprising instructions that, when executed by a processor, cause the processor to perform operations comprising: accessing run group data, the run group data comprising information corresponding to a plurality of runs of an elevator car for traversing a plurality of floors of the elevator car, wherein the run group data comprises a position of the elevator car at the end of each run group, and wherein the position of the elevator car at the end of each run group comprises an absolute position and / or a relative position; evaluating a potential floor height and a potential floor travel sequence for at least one floor of the hoistway in response to the operational set data; determining a likelihood of each combination of potential floor heights and potential floor travel sequences for the plurality of floor traversals; responsive to the likelihood, selecting a potential floor height and a potential floor travel sequence as a selected floor height and a selected floor travel sequence; A floor height map is generated in response to the selected floor heights and the selected floor travel order.

Images