Elevator control system

Abstract

Provided is an elevator control system in which a plurality of elevators (20) each execute stop control to stop a car (10) when an earthquake is sensed by an earthquake sensor (270), and after the stop control, travel control to control travel of the car (10) is executed based on a decision by a group management control device (220). The plurality of cars (10) include a car (A) and a car (B). The group management control device (220) decides to execute the travel control for the car (B) after the car (A) executes the travel control. The group management control device (220) decides whether or not to execute the travel control for the car (B) and a travel speed in a case where the travel control for the car (B) is executed, based on a result of execution of the travel control for the car (A).

Description

Technical Field

[0001] This invention relates to elevator control systems. Background Technology

[0002] As existing technology, there are known automatic recovery systems during earthquakes that automatically diagnose the elevator's condition while it is in motion, detecting earthquake shaking and stopping at the nearest floor. If no problems are found, the elevator restarts operation. Since there are no issues with the elevator equipment, maintenance personnel are not required to perform any work, thus allowing the elevator to be restored as quickly as possible.

[0003] Furthermore, if an elevator traveling in a fast-moving area, such as between non-service floors, detects a high-altitude earthquake, the elevator will stop between floors within that fast-moving area. Japanese Patent Application Publication No. 2004-359405 discloses a technology that allows for the rapid restoration of elevators through rescue operations based on remote earthquake rescue methods.

[0004] During diagnostic or emergency operations, the car is kept at a low speed to allow for an emergency stop in case of an elevator malfunction. Therefore, in high-rise buildings with long travel distances, time is required for the elevator to recover after the operation is completed, resulting in a slower recovery time. Furthermore, if an elevator malfunction is detected during operation, the car is stopped at a predetermined time, but further research is needed on methods for detecting / predicting malfunctions. Summary of the Invention

[0005] This invention was made to solve the above-mentioned problems, and its purpose is to provide an elevator control system that can safely and efficiently restore elevators during an earthquake.

[0006] The elevator control system of the present invention includes: multiple elevators, each with a corresponding multiple cars; and a group management control device for controlling the multiple elevators. When an earthquake is detected by an earthquake sensor, each of the multiple elevators executes a stop control to bring its car to a stop. After the stop control, based on a decision made by the group management control device, a travel control is executed to control the movement of the cars. The multiple cars include a first car and a second car. After executing travel control on the first car, the group management control device decides to execute travel control on the second car. Based on the execution result of the travel control on the first car, the group management control device determines whether the travel control on the second car can be executed and the travel speed if the travel control on the second car is executed.

[0007] The above and other objects, features, aspects and advantages of the present invention will become clear from the following detailed description of the invention as understood in conjunction with the accompanying drawings. Attached Figure Description

[0008] Figure 1 This is a diagram illustrating an example of the overall structure of a monitoring system.

[0009] Figure 2 This is a diagram illustrating an example of the hardware structure of a monitoring system.

[0010] Figure 3 It is the execution result DB of the diagnostic process.

[0011] Figure 4 It is the execution result DB of the diagnostic process.

[0012] Figure 5 It is a diagram used to illustrate the rescue operation.

[0013] Figure 6 This is a flowchart of the processes executed by the elevator control system.

[0014] Figure 7 DB is the execution result of the diagnostic operation of the variant example.

[0015] Figure 8 DB is the execution result of the diagnostic operation of the variant example.

[0016] Figure 9 This is a flowchart of the processing performed by a modified elevator control system. Detailed Implementation

[0017] The embodiments will now be described with reference to the accompanying drawings. In the following description, the same reference numerals are used to denote the same parts. Their names and functions are also the same. Therefore, detailed descriptions will not be repeated.

[0018] Figure 1 This is a diagram illustrating an example of the overall structure of the monitoring system 100. Figure 2 This is a diagram illustrating an example of the hardware structure of the monitoring system 100.

[0019] The monitoring system 100 includes a monitoring device 300 and an elevator control system 1. The elevator control system 1 includes multiple elevators 20, a group management control device 220 for controlling the multiple elevators 20, and an earthquake sensor 270 for sensing earthquakes. Figure 1 , Figure 2 Each elevator 20 has a corresponding car 10 (each elevator 20 has one car 10).

[0020] In this embodiment, elevator 20 refers to three or more elevators 20 installed in building 2, including elevator 20a (hereinafter also referred to as "Elevator A"), elevator 20b (hereinafter also referred to as "Elevator B"), and elevator 20c (hereinafter also referred to as "Elevator C"). The fourth elevator and thereafter are referred to as Elevator D, Elevator E, etc.

[0021] The monitoring device 300 is installed in the information center 3 of the maintenance company that performs the maintenance of elevators 20. The monitoring device 300, managed by this maintenance company, manages multiple elevators 20 located in multiple buildings (buildings 2, 2a, 2b, etc. in this example). The monitoring device 300 is configured to communicate with these multiple elevators 20. The monitoring device 300 monitors the occurrence of earthquakes in each elevator 20 and manages earthquake recovery responses in each elevator 20.

[0022] When an earthquake is detected by the earthquake sensor 270, each of the multiple elevators 20 (each with its own management control device 230) executes a stop control to bring the car 10 to a stop. After the stop control, based on the decision of the group management control device 220, a travel control is executed to control the movement of the car 10. The travel control includes a diagnostic operation to determine whether the elevator 20 can be restored and to move the car 10, which has stopped between floors (inter-floor stop), to the nearest floor as a rescue operation.

[0023] If an earthquake occurs and the seismic sensor 270 installed in the elevator 20 detects a certain degree of shaking, a stop control (based on earthquake-controlled operation) is initiated while the elevator car 10 is in motion, causing the car 10 to travel to the nearest floor. The doors open when the car 10 reaches the nearest floor, allowing the user 89 to disembark. For example, if the aforementioned shaking is detected while the car 10 is traveling between the 6th and 7th floors, the doors open after the car 10 reaches the nearest floor, either the 6th or 7th floor.

[0024] After the elevator car 10 stops at the nearest floor, a diagnostic run is performed to check for any abnormalities in the elevator 20. For example, the diagnostic run causes the elevator car 10 to travel back and forth from the lowest to the highest floor to check for any abnormalities in the car's movement, door opening and closing, etc. If the diagnostic run of the elevator 20 indicates that everything is normal, the elevator car 10 is temporarily restarted without stopping. Thus, the elevator car 10 can be used.

[0025] On the other hand, in the event of a major earthquake of a certain magnitude, or in the event of an abnormality or power outage in the elevator 20 accompanying the earthquake, the elevator car 10 may be stopped between floors (inter-floor stop). In this situation, the user 89 may be trapped inside the elevator car 10 and unable to get off.

[0026] Although not shown in the diagram, an intercom is installed inside elevator car 10. By pressing the button on the intercom, one can communicate with the manager (or maintenance personnel) of elevator 20 in the monitoring room of building 2. In addition, the manager can also use the intercom to communicate with each elevator car 10.

[0027] In the event of a stoppage between floors, the operator can communicate with the user 89 inside car 10 via intercom while conducting a rescue operation. The rescue operation allows car 10 to be moved to the nearest floor, enabling the user 89 to exit. For example, in the event of a stoppage between floors in the fast-moving area described later, when the operator sets the low-speed operation switch during an earthquake to "on" and the user 89 continuously presses the door close button inside car 10, car 10 will travel at low speed away from the counterweight 12 and stop at the nearest floor.

[0028] Below, examples Figure 1 Building 2 shown will be described in detail. Building 2 is a 7-story building, and elevators 20a to 20c (units A to C, etc.) can stop at the designated floors. In this embodiment, floors 2 to 4 are non-stopping floors, and the travel distance from floor 1 to floor 5 is the fast travel zone.

[0029] In this embodiment, the multiple elevators 20 are all rope elevators. Each elevator 20 includes a car assembly 260. Figure 2 The system comprises a traction machine 50, a car 10, a counterweight 12, a rope 11, and a guide pulley 13. The rope (main rope) 11 is attached to the traction machine 50 and the guide pulley 13. The car 10 is suspended at one end of the rope 11. The counterweight 12 is suspended at the other end of the rope 11.

[0030] The traction machine 50 is a motor that drives the elevator car 10 of the elevator 20 to move up and down. The car device 260 includes various equipment installed in the car 10, including destination floor buttons (car call buttons) (not shown). Landing devices 250 are installed at each floor. Figure 2 The landing station device 250 consists of various devices installed at landing stations on each floor, including landing call buttons (not shown) for registering landing calls.

[0031] The car 10 is installed in the hoistway 8 located within the building 2. The car 10 moves up and down within the hoistway 8 and between multiple floors. In this embodiment, cars 10 such as A-type to C-type can stop at each floor from the 1st floor (1F) to the 5th floor (5F) to the 7th floor (7F).

[0032] A machine room 5 is located directly above the hoistway 8. A traction machine 50 and other equipment are installed in the machine room 5. The elevator 20, by driving the traction machine 50, enables the car 10, located within the hoistway 8, to travel upwards (also known as in the "UP direction") or downwards (also known as in the "DN direction"). A buffer 14 is installed at the bottom of the hoistway 8, i.e., the pit 6. The buffer 14 is a device that absorbs the impact of the car 10 falling in the event of an abnormality.

[0033] When a floor call button in the UP or DN direction is pressed, any car 10 from A to C is assigned. The assigned car 10 responds to the floor call and travels to the registered floor. When a car call button for each destination floor is pressed, the car 10 travels to the destination floor indicated by the pressed call button.

[0034] like Figure 2 As shown, in this embodiment, the elevator control system 1 is configured to include the elevators 20a to 20c (units A to C, etc.) described above. The elevator control system 1 includes a remote monitoring device 210 connected to each elevator 20, a group management control device 220, an individual elevator management control device 230, a car device 260, a landing device 250, and a monitoring panel 240 for each elevator 20. Each elevator 20 includes its own management control device 230, a car device 260, and a seismic sensor 270.

[0035] The group management control device 220 includes a processor 221, a memory 222, and a communication interface (not shown). They are interconnected via a bus.

[0036] The processor 221 is, for example, a CPU (Central Processing Unit). The memory 222 may also be configured to include ROM (Read Only Memory), RAM (Random Access Memory), and a storage unit. The storage unit is a non-volatile storage device. The storage unit may also be, for example, an HDD (Hard Disk Drive), an SSD (Solid State Drive), etc.

[0037] The processor 221 reads the program stored in ROM into RAM and executes it to implement various functions of the group management control device 220. The ROM stores the program that records the processing procedure of the group management control device 220. The RAM becomes the working area of ​​the processor 221 when executing the program, temporarily storing the program, data during program execution, etc.

[0038] Group management control device 220 controls multiple elevators 20 (multiple cars 10). Group management control device 220 is configured to communicate with each management control device 230 (e.g., elevators A through C), and can send control commands to the car device 260 via each management control device 230, and receive signals output by the car device 260. Group management control device 220 is also configured to communicate with landing device 250, and can send control commands to the landing device 250, and receive signals output by the landing device 250.

[0039] The group management control device 220 is configured to communicate with the monitoring panel 240, sending signals output from the group management control device 220, each management control device 230 (such as Units A through C), and the floor station device 250 to the monitoring panel 240. The monitoring panel 240 displays the signals received from the group management control device 220.

[0040] The monitoring device 300 monitors elevator 20. Like the group management and control device 220, the monitoring device 300 also includes a processor (CPU), memory (ROM, RAM, storage unit), communication interface, display unit, and input unit (not shown). The monitoring device 300 can connect to remote monitoring devices 210 installed in each elevator of each building via the communication interface. The display unit displays various information. The display unit is, for example, an LCD or a monitor. The input unit accepts input from users to the monitoring device 300. The input unit is, for example, a keyboard or a mouse.

[0041] The remote monitoring device 210 is a communication device that sends (reports) various information about the elevator 20 obtained from each management control device 230 to the monitoring device 300. The remote monitoring device 210 also has a processor (CPU), memory (ROM, RAM), and communication interface (not shown). They are interconnected via a bus.

[0042] Each of the management and control devices 230 for machines A through C controls each car device 260 (including car 10). Each management and control device 230 also has a processor (CPU), memory (ROM, RAM), and communication interface (not shown). They are interconnected via a bus.

[0043] When a landing call is registered by pressing a landing button, the group management control device 220 assigns the landing call to any car 10 among machines A through C. For example, if a landing call for the 1st floor in the UP direction is registered, the group management control device 220 assigns that landing call to machine B. In this case, the group management control device 220 sends a response command for that landing call to each management control device 230 of machine B. Each management control device 230 of machine B causes the car 10 of machine B, which was assigned the 1st floor UP direction landing call, to travel to the 1st floor and respond to the landing call.

[0044] Earthquake sensor 270 is a device for sensing earthquakes. Each management control unit 230 acquires earthquake signals from earthquake sensor 270 (e.g., signals to determine P-waves or S-waves and signals to determine the intensity (intensity, weak, strong, etc.) of the earthquake). Each management control unit 230 can cause the car 10 to operate based on the earthquake signals detected by earthquake sensor 270 (earthquake-controlled operation). Specifically, when an earthquake signal is detected, each management control unit 230 moves the car 10 to the nearest floor. In the event of a large earthquake or the detection of certain anomalies, each management control unit 230 does not move the car 10 to the nearest floor but stops it immediately. In such cases, a trapped state may sometimes occur.

[0045] Furthermore, the monitoring device 300 can communicate with the elevators 20 (each management control device 230) in buildings 2a, 2b, etc., managed by the information center 3 via the remote monitoring devices 210 of each unit. Each management control device 230 can send various elevator signals, including seismic signals detected by seismic sensors, to the monitoring device 300. The monitoring device 300 obtains various elevator information, including seismic signals from the seismic sensors installed in each building.

[0046] Therefore, the monitoring device 300 can acquire various information about the elevator and can monitor the situation when an earthquake occurs in a building equipped with an elevator. The signals acquired by the monitoring device 300 are not limited to earthquake signals (P-waves, S-waves, earthquake magnitude, etc.), but may also include signals indicating that the elevator has stopped due to an earthquake, signals that can determine the trapped status, etc.

[0047] First, an example of a driving control system in "diagnostic operation" will be explained. Figure 3 This is the execution result DB 91 of the diagnostic operation. Execution result DB 91 is stored in the memory 222 of the group management control device 220. The execution result DB 91 records the execution result of the diagnostic operation.

[0048] In this embodiment, the group management control device 220 decides to execute travel control on car B after executing travel control on car A. Based on the execution result of the travel control on car A, the group management control device 220 determines a travel control command that includes whether travel control on car B can be executed and the travel speed if travel control on car B is executed. The execution result of the travel control includes whether any abnormality has occurred in elevator 20 detected during the travel control process.

[0049] The order in which diagnostic results are implemented is determined according to the sequence of Unit A, Unit B, Unit C, Unit D, and so on. If the driving control of Unit B ends, the execution result of the driving control of Unit B is also used to determine the driving control command for Unit C. Driving control will then be executed sequentially.

[0050] The execution result DB 91 records the implementation number of the diagnostic operation, whether the diagnostic operation can be executed, the travel speed of car 10, the success / failure of the diagnostic operation, the reason for failure (type of abnormality) in the case of failure, the floor where the diagnostic operation was interrupted in the case of failure (interrupted floor), the lifting distance from the lowest floor (1st floor) to the highest floor (7th floor) of car 10, and the current stopping floor of car 10.

[0051] Specifically, the execution result DB 91 records: the first implementation machine is machine A (car A), the lifting stroke is L [m], the stop floor before the diagnostic operation is floor 1, and car A is operated at speed V2 for diagnostic operation. The result of performing the diagnostic operation on car A is that an abnormality of rope interference was detected near floor N, and the diagnostic operation was interrupted. For example, speed V2 is a speed slower than the rated speed of car A.

[0052] For example, rope 11 may become snagged on some elevator equipment due to an earthquake, causing an anomaly of rope interference. On the elevator 20 side, the torque value of the traction machine 50 is continuously measured during the movement of the car 10. The measured torque value is compared with the torque reference value stored during the learning operation. If a value exceeding the torque reference value by a specified amount (a higher torque value due to the load caused by the snag of rope 11) is detected, an anomaly of rope interference is detected. The result of detecting this anomaly is that the diagnostic operation of car A is deemed a "failure." Therefore, car A cannot resume operation.

[0053] Thus, during diagnostic operation, the system checks for any abnormalities related to rope 11, which is a long object, such as interference. Furthermore, it checks for any abnormalities related to the control cable, such as cable interference, derailment, rope slippage, and door opening abnormalities. If any abnormality is detected, the diagnostic operation is deemed a "failure," and if no abnormality is detected, the diagnostic operation is deemed a "success."

[0054] Next, the travel control command for car B, the second implementing unit, is determined based on the execution results of the diagnostic operation of car A. Car B has a lifting stroke of L [m] and stops at floor 1, therefore it can be inferred that the damage caused by the earthquake is similar to that of car A (presumably, rope 11 swayed similarly). Therefore, given that the lifting stroke and stopping floor are the same (or close), it is also possible that an anomaly of rope interference could be detected near floor N in car B.

[0055] Therefore, instead of running at the same time as car A (waiting for a certain period of time for the shaking to subside), the diagnostic operation of car B begins after the diagnostic operation of car A is completed (in the prior art, the diagnostic operation of all cars 10 begins at the same time).

[0056] Furthermore, by moving car B at a speed V1 slower than speed V2, the diagnostic operation of car B is set to be executable. By performing the diagnostic operation slowly, it can be stopped immediately even if an abnormality is found, thus reducing the risk of equipment damage.

[0057] The diagnostic operation of car B yielded the same result as car A: an anomaly of cable interference was detected near floor N, interrupting the diagnostic operation. Therefore, car B could not resume operation. Alternatively, instead of traveling at speed V1 for the entire journey, it could only reduce to speed V1 near floor N where the anomaly occurred.

[0058] Next, the travel control command for car C, the third implementing unit, is determined based on the execution results of the diagnostic operations of cars A and B. Car C's lifting stroke is L [m], and it stops at the first floor; therefore, it can be inferred that the damage caused by the earthquake is similar to that of cars A and B. Since the same anomaly was detected in cars A and B, the probability that the same anomaly was detected in the third car C is increased. Therefore, the diagnostic operation for car C is set to be unexecutable. Consequently, car C cannot be restored.

[0059] In the above scenario, if the diagnostic operation of one car 10 fails, the diagnostic operation is performed by reducing the travel speed of the cars 10 with similar conditions. Furthermore, if multiple cars 10 with similar conditions fail, the diagnostic operation is set to be unexecutable. The above is one example of determining whether a diagnostic operation can be performed; other methods may also be used for determination.

[0060] This section describes an example where the execution result DB 91 differs from the actual result. Figure 4 This is the execution result DB 92 of the diagnostic operation. It is the same as the execution result DB 91, and the diagnostic operation is performed in the order of car A, car B, car C... In addition, the lifting stroke and the stop floor are the same.

[0061] In this example, no abnormality was detected during the diagnostic run of car A (execution result DB 92). Therefore, the execution result of the diagnostic run of car A is determined to be "successful". Consequently, the execution result of the diagnostic run of car B, which has similar conditions, is also considered highly likely to be successful. Therefore, the diagnostic run of car B is set to be executable, and the diagnostic run is performed at a speed V3, which is faster than speed V2. For example, speed V3 is the rated speed of car B.

[0062] As a result, no abnormalities were detected during the diagnostic operation of car B, and the execution result of the diagnostic operation of car B was judged as "successful". Similarly, the diagnostic operation of car C was set to be executable and performed at speed V3. As a result, cars A to C resumed operation.

[0063] Next, an example of a situation where the driving control is set to "rescue operation" will be explained. Figure 5 This diagram illustrates the rescue operation. The travel routes of vehicles A through C include a fast-travel area (area with a long lifting stroke) where the distance between floors where the car 10 can stop is greater than a specified distance. In this example, building 2 has floors 1 through 7, and vehicles A through C can stop on floors 1, 5, 6, and 7.

[0064] For example, suppose the distance between floors 1 through 7 is 3.5m. In this case, the distance between the 1st and 5th floors that can be used for parking is 14m (4 floors × 3.5m). The distance between the 5th and 6th floors that can be used for parking is 3.5m. The distance between the 6th and 7th floors that can be used for parking is 3.5m. For example, the above "specified distance" = 10m. In this case, the area between the 1st and 5th floors that can be used for parking is a fast-moving zone (the distance between the 1st and 5th floors is 14m ≥ 10m).

[0065] Furthermore, if there is one (or more) floors between floors where stopping is not possible, the area between those floors can be designated as a fast-moving zone. In this embodiment, for convenience, the area with a long lifting stroke is defined as the "fast-moving zone".

[0066] If an earthquake occurs while the car is traveling in a fast-moving zone, the car 10 may stop midway through the fast-moving zone (inter-floor stop) and become trapped. Specifically, if the earthquake sensor "high" is activated while the car is traveling in the fast-moving zone, an inter-floor stop will be performed.

[0067] In this situation, in order to rescue user 89, the manager (or maintenance personnel) needs to move car 10 to the nearest floor, either the 1st or 5th floor. If the entrapment occurs midway through the fast-moving area, the distance car 10 must travel is longer compared to the entrapment occurring between the 5th and 7th floors, thus requiring a longer rescue time.

[0068] In this embodiment, the group management control device 220 determines, based on the execution result of the rescue operation of the first-executed car A, whether the car B should travel to the nearest upper or lower floor during the subsequent rescue operation. The determined direction is then set as the travel control command.

[0069] During a rescue operation, the elevator travels to the nearest floor located above or below the car 10. If the car 10 stops between floors in the fast travel zone, for safety, a rescue operation is performed to move the car 10 to the nearest floor located in the direction away from the counterweight 12 (hereinafter referred to as the "anti-counterweight direction"). However, even with this operation, sometimes an anomaly in the elevator 20 is detected during the rescue operation, causing the rescue operation to fail.

[0070] In this case, for other cars 10, if they are moved in the anti-weight direction, an anomaly may also be detected for the same reason. Therefore, if the group management control device 220 detects an anomaly in elevator 20 as a result of the rescue operation of car A to the nearest floor in the anti-weight direction, it decides to move car B to the nearest floor in the direction close to the counterweight 12 (hereinafter referred to as "counterweight direction") during the rescue operation.

[0071] like Figure 5 As shown, floors 2 through 4 are non-stopping floors, and floors 1 through 5 are fast-moving areas. In this example, due to the earthquake, car A of aircraft A stopped between floors 3 and 4. Counterweight 12 is located above car A.

[0072] Car B of machine B also stops between floors 3 and 4, and counterweight 12 is also located above car B. Car C of machine C stops between floors 2 and 3, and counterweight 12 is also located above car C.

[0073] In this state, rescue operations are performed on cars A through C. In this example, the group management control device 220 determines the travel control command to perform rescue operations in the order of cars A, B, C, etc., with all cars 10 performing rescue operations at a predetermined speed. Alternatively, the execution order of the rescue operations can be arbitrarily determined by the manager. The group management control device 220 determines the travel control command for car A, which is initially performing the rescue operation, to travel in the opposite direction.

[0074] Therefore, elevator car A of unit A begins rescue operation, facing the opposite direction, i.e., the nearest floor (floor 1) below. Furthermore, in this case, an anomaly was detected in elevator 20 during the rescue operation, and the rescue operation was deemed a "failure."

[0075] Therefore, for car B of elevator B, the second elevator to perform a rescue operation, the rescue operation was initiated towards the nearest floor (5th floor) in the counterweight direction, i.e., above, based on the decision that the operation was feasible. If no abnormality was detected in elevator 20 during the rescue operation of car B, the rescue operation was deemed "successful." Similarly, for car C of elevator C, the third elevator to perform a rescue operation, the rescue operation was also initiated towards the nearest floor (5th floor) in the counterweight direction, i.e., above, based on the decision that the operation was feasible.

[0076] On the other hand, if an anomaly is detected in elevator 20 during the rescue operation of car B, the rescue operation is deemed a "failure". In this case, for car C of machine C, which is the third to perform a rescue operation, the probability of detecting an anomaly is high, regardless of whether it is traveling upwards or downwards, therefore it is decided that the rescue operation cannot be performed.

[0077] As explained above, the driving control command for rescue operations is determined, but this is only one example, and other methods can also be used to determine the driving control command. In addition, during rescue operations, the rescue operations of all cars 10 can be determined as executable regardless of the execution results of the rescue operations of other cars 10.

[0078] The following explanation uses a flowchart. Figure 6 This is a flowchart of the processes executed by the elevator control system 1. This process includes the processes executed by the group management control device 220 and the processes executed by each individual management control device 230. These processes can be initiated periodically (e.g., every 100 ms). Hereinafter, "step" will be abbreviated as "S".

[0079] As described above, when the earthquake sensor 270 detects an earthquake, earthquake control operation is performed, and the car 10 stops and opens its doors after reaching the nearest floor.

[0080] After this process begins, in each process A, each management control device 230 of machine A executes stop control (S101) because the earthquake sensor 270 senses an earthquake, and sends the result of the stop control to the group management control device 220 (S102).

[0081] Similarly, in each of the B units, the management control devices 230 of B unit also execute stop control (S301) when the earthquake sensor 270 senses an earthquake, and send the stop control result to the group management control device 220 (S302). Although not shown, the same process is performed on units such as C unit.

[0082] In the group management process, the group management control device 220 determines the type of travel control, the travel sequence, and the travel control command for the first car 10 (S201). If car 10 stops at the nearest floor, the type of travel control is set to "diagnostic operation." If car 10 stops between floors, the type of travel control is set to "rescue operation." The determination of S201 is as follows: Figures 3-5 As shown.

[0083] In this embodiment, the travel sequence is predetermined, set as A, B, C, etc. However, when the travel control category is "rescue operation," the group management control device 220 determines the car 10 without users 89 among the multiple cars 10 as the first car 10 (car A) to perform the rescue operation. In this example, it is assumed that car A is empty. When the travel control category is "rescue operation," the rescue operation can also be performed in any order according to the manager's wishes.

[0084] Group management control device 220 sends the travel control command determined in S201 to the first car 10 (Car A) (S202). Each management control device 230 of Car A executes travel control according to the travel control command determined by group management control device 220 (S103), sends the execution result of travel control to group management control device 220 (S104), and ends the process. In diagnostic operation, travel control is performed automatically. On the other hand, in rescue operation, for example, the manager (maintenance personnel) sets the low-speed operation switch during an earthquake to on and continuously presses the door close button inside car 10, thereby causing car 10 to travel.

[0085] The group management control device 220 determines, based on the execution result of the travel control of the first car 10 (machine A), whether the travel control of the second car 10 (machine B) can be executed, and its travel speed, etc. (S203). The example of the decision in S203 is as follows... Figures 3-5 As shown.

[0086] When the travel control category is "rescue operation", if the group management control device 220 detects an abnormality in elevator 20 when the execution result of the rescue operation of car A to the nearest floor in the counterweight direction is a rescue operation, it decides to travel to the nearest floor in the counterweight direction in the rescue operation of car B.

[0087] Group management control device 220 sends the driving control command determined in S203 to the second car 10 (Car B) (S204). Each management control device 230 of Car B executes the driving control according to the driving control command determined by group management control device 220 (S303), sends the execution result of the driving control to group management control device 220 (S304), and ends the process.

[0088] Based on the execution result of the travel control of the second car 10 (Car B), the group management control device 220 determines whether the travel control of the third car 10 (Car C) can be executed, its travel speed, etc. (S205). Similarly, the group management control device 220 sends the travel control command determined in S205 to the third car 10 (Car C). The same process is performed for cars C and later. Once the processing of all cars is completed, the processing of the group management control device 220 ends.

[0089] [Variation Example]

[0090] Figure 7 This is the execution result DB 93 of the diagnostic operation of the modified example. The status of each car 10 in the execution result DB 93 after the earthquake is shown. Figure 3 The execution results described in the documentation are the same as those for DB 91. Both have a lifting stroke of L[m] and a stopping level of 1.

[0091] In this embodiment, firstly, a diagnostic run of one car A is performed. Based on the result of the diagnostic run of car A, a driving control command for the diagnostic run of the next car B is determined. In this variant, diagnostic runs of N (a predetermined number) cars 10 are performed. Based on the result of the diagnostic runs of the N cars 10, a driving control command for the diagnostic run of the next car 10 is determined. In this variant, N = 2 cars; initially, the two cars performing diagnostic runs are cars A and C, and then car B performs the diagnostic run next.

[0092] After the group management control device 220 has executed the driving control of a predetermined number of cars (=N = 2 cars) including cars A and C without referring to the execution results of the driving control of other cars 10, it decides to execute the driving control of car B. Based on the execution results of the driving control of the predetermined number of cars, the group management control device 220 determines the driving control command, including whether the driving control of car B can be executed and the driving speed if the driving control of car B is executed.

[0093] In this way, by determining the travel control command for the next car 10 based on the diagnostic results of N cars 10, the accuracy of anomaly prediction can be further improved. Furthermore, the diagnostic results are not limited to those of the car 10 based on the current earthquake; they can also utilize diagnostic results from past earthquakes that occurred within the building. Additionally, they are not limited to this building; past diagnostic results from other objects with similar elevator specifications can also be used.

[0094] exist Figure 7 In this scenario, car A of machine A and car C of machine C were subjected to diagnostic runs at speed V2. As a result, both cars A and C experienced anomalies near floor N caused by cable interference, and the runs were deemed "failed." Since anomalies occurred in both cars, there is a high probability that anomalies will also occur in car B, which is scheduled to undergo the next diagnostic run. Therefore, the diagnostic run for car B is deemed unsuitable.

[0095] Figure 8 This is the execution result DB 94 of the diagnostic operation of the modified example. The status of each car 10 in the execution result DB 94 after the earthquake is also consistent with... Figure 7 The execution result described in the document is the same as that of DB 93.

[0096] In this scenario, the diagnostic runs of car A of machine A and car C of machine C at speed V2 resulted in no abnormalities, and the execution was deemed "successful." Since no abnormalities occurred, there is a high probability that no abnormalities will also occur in car B, which is scheduled to undergo the next diagnostic run. Therefore, it is determined that the diagnostic run of car B can be performed, and the travel speed is set to V3, which is faster than speed V2.

[0097] Figure 9 This is a flowchart illustrating the processing steps performed by the elevator control system in a modified example. In this modified example, the processing in this flowchart is similar to... Figure 6 The processing is similar to that described in the flowchart, and each process is the same as... Figure 6 The flowchart is also periodically activated. Processing A and C refer to the processing executed by each management and control device 230 of machine A and machine C, respectively.

[0098] After this process begins, in processes A and C, the management control devices 230 of unit A execute stop control (S401) upon detecting an earthquake by the earthquake sensor 270, and send the stop control result to the group management control device 220 (S402). The management control devices 230 of unit C also execute the same process (S401, S402). In process B, the management control devices 230 of unit B also execute the same process (S601, S602). Although not shown, the other units also perform the same process.

[0099] In the group management process, the group management control device 220 determines the type of travel control, the travel sequence, and the travel control command for the first N cars 10 to travel (S501). This process is basically the same as the process in S201. However, the travel command is sent to N cars 10 (a specified number) instead of one car. In this example, N = specified number = 2, and the N cars are identified as cars A and C. The travel sequence is set to car A, car C, car B, ...

[0100] Group management control device 220 sends the driving control command determined in S501 to N cars 10 (cars A and C) (S502). Each management control device 230 of car A executes the driving control according to the driving control command determined by group management control device 220 (S403), sends the execution result of the driving control to group management control device 220 (S404), and ends the process. Each management control device 230 of car C also executes the same process (S404, S405) and ends the process.

[0101] The group management control device 220 determines whether the driving control of the (N+1)th car 10 (car B) can be executed, its driving speed, etc., based on the execution results of the driving control of N cars 10 (cars A and C) (S503). The difference between this process and the process in S203 is that the decision is based on the execution results of the driving control of N cars 10, not on one car 10.

[0102] Group management control device 220 sends the driving control command determined in S503 to the N+1th car 10 (Car B) (S504), and the process ends. Each management control device 230 of Car B executes the driving control according to the driving control command determined by group management control device 220 (S603), sends the execution result of the driving control to group management control device 220 (S604), and the process ends.

[0103] Based on the execution result of the travel control of the (N+1)th car 10 (car B), the group management control device 220 determines whether the travel control of the (N+2)th car 10 (car D) can be executed, its travel speed, etc. (S505). Similarly, the group management control device 220 sends the travel control command determined in S505 to the (N+2)th car 10 (car D). The same process is performed for cars D and subsequent cars. Once the processing of all cars is completed, the processing of the group management control device 220 ends.

[0104] As explained above, the elevator control system 1 includes multiple elevators 20, each with multiple cars 10, and a group management control device 220 for controlling the multiple elevators 20. When an earthquake is detected by the earthquake sensor 270, each of the multiple elevators 20 executes a stop control to stop the car 10. After the stop control, based on the decision of the group management control device 220, it executes a travel control to control the movement of the car 10. The multiple cars 10 include car A and car B. After executing travel control for car A, the group management control device 220 decides to execute travel control for car B. Based on the execution result of the travel control for car A, the group management control device 220 determines whether the travel control for car B can be executed and the travel speed if the travel control for car B is executed.

[0105] If an abnormality is detected in the elevator equipment during the travel control, the car 10 is brought to an emergency stop at the time the abnormality is detected. If the abnormality is detected at that time, the elevator equipment may be damaged, depending on the circumstances. In this case, the restoration of the elevator 20 may be delayed. On the other hand, as described above, by determining whether the travel control of car B can be executed and the travel speed if the travel control of car B is executed based on the execution result of the travel control of car A, the risk of equipment damage to the following car 10 can be reduced based on the results of the travel control of other cars, thereby improving the safety and success rate of travel control. By reducing the expansion of equipment damage, the restoration workload of maintenance personnel can be reduced, and the restoration time can be shortened. As a result, the elevator can be restored safely and efficiently during an earthquake.

[0106] The execution result of the travel control includes whether any abnormalities have occurred in the elevator 20 detected during the travel control process. The travel control includes diagnostic operations to diagnose whether the elevator 20 can be restored, which involve moving the car, and rescue operations to move the car from a stop between floors to the nearest floor. Therefore, in the event of an earthquake, if diagnostic or rescue operations are performed, the elevator can be restored safely and efficiently.

[0107] Travel control is for rescue operations. The group management control device 220, based on the execution results of the rescue operation of car A, determines whether car B should travel to the nearest upper or lower floor during its rescue operation. Thus, based on the execution results of the rescue operations of other cars, it can guide them to travel in a safe direction to perform rescue operations.

[0108] Multiple elevators 20 are rope elevators, each with a car 10 suspended at one end of a rope 11 and a counterweight 12 suspended at the other end. If the group management control device 220 detects an anomaly in elevator 20 during a rescue operation where car A travels to the nearest floor in a direction away from the counterweight 12, it determines that car B should travel to the nearest floor in a direction close to the counterweight 12 during the rescue operation. Considering the safety of user 89, the direction of the rescue operation in the event of a stop between floors in the fast-moving zone is determined to move car 10 away from the counterweight 12. However, depending on the extent of damage to the elevator equipment, this direction may not be the safest for rescue. By configuring the system as described above, the rescue operation can be performed based on the results of the rescue operations of other elevators, directing them to a safe direction and improving the success rate of the rescue operation. By improving the success rate of the rescue operation, the time user 89 is trapped can be shortened.

[0109] After the group management control device 220 has executed the travel control of a predetermined number of cars, including cars A and C, without referring to the execution results of the travel control of other cars 10, it decides to execute the travel control of car B. Based on the execution results of the travel control of the predetermined number of cars, the group management control device 220 determines whether the travel control of car B can be executed and the travel speed if the travel control of car B is executed. In this way, by determining the next travel control command for car B based on the diagnostic results of the predetermined number of cars 10, the accuracy of anomaly prediction can be further improved. Therefore, the elevator can be safely and efficiently restored in the event of an earthquake.

[0110] The group management control device 220 determines the car 10 (car A) that is not occupied by users 89 from among the multiple cars 10 as the car 10 that will initially carry out the rescue operation. In this way, by simulating the rescue operation with the car 10 that is not occupied by users 89, the optimal driving direction when the actual rescue operation is carried out can be simulated in advance.

[0111] [Postscript]

[0112] The above-described implementation methods are specific examples of the following notes.

[0113] (Postscript 1)

[0114] An elevator control system includes: multiple elevators, each with a corresponding multiple cars; and a group management control device that controls the multiple elevators. When an earthquake is detected by an earthquake sensor, each of the multiple elevators executes a stop control to bring its car to a stop. After the stop control, based on a decision made by the group management control device, a travel control is executed to control the movement of the cars. The multiple cars include a first car and a second car. After the first car executes the travel control, the group management control device decides to execute the travel control for the second car. Based on the execution result of the travel control for the first car, it determines whether the travel control for the second car can be executed and the travel speed under the condition that the travel control for the second car is executed.

[0115] (Postscript 2)

[0116] According to the elevator control system described in Appendix 1, the execution result of the travel control includes whether an elevator malfunction has occurred as detected in the travel control, and the travel control includes a diagnostic operation to diagnose whether the elevator can be restored and a rescue operation to move the car from the nearest floor to the floor where the car has stopped between floors.

[0117] (Note 3)

[0118] According to the elevator control system described in Appendix 1 or Appendix 2, after the group management control device has enabled a predetermined number of cars, including the first car and the third car, to perform the travel control without referring to the execution results of the travel control of other cars, it decides to enable the second car to perform the travel control. Based on the execution results of the travel control of the predetermined number of cars, it determines whether the travel control of the second car can be performed and the travel speed when the travel control of the second car is performed.

[0119] (Postscript 4)

[0120] According to the elevator control system described in Appendix 2 or 3, wherein the travel control is the rescue operation, and the group management control device determines, based on the execution result of the rescue operation of the first car, which of the upper and lower nearest floors the second car will travel to during the rescue operation.

[0121] (Note 5)

[0122] According to the elevator control system described in Appendix 4, the multiple elevators are rope elevators with a car suspended at one end of a rope and a counterweight suspended at the other end of the rope. If the group management control device detects an elevator malfunction during the rescue operation of the first car, which is traveling to the nearest floor in the direction away from the counterweight, it decides that the second car will travel to the nearest floor in the direction close to the counterweight during the rescue operation.

[0123] (Note 6)

[0124] According to the elevator control system described in Appendix 4 or Appendix 5, the group management control device determines the car among the plurality of cars that is not occupied by any user as the first car to initially perform the rescue operation.

[0125] Embodiments of the present invention have been described, but should be considered as illustrative rather than restrictive in all respects. The scope of the invention is defined by the claims, which are intended to include all modifications within the meaning and scope equivalent to the claims.

Claims

1. An elevator control system, comprising: Multiple elevators, each with its own set of multiple cars; and A group management and control device that controls the multiple elevators. When the earthquake sensors detect an earthquake, each of the multiple elevators executes a stop control to bring the car to a halt. Following the stop control, based on the decision of the group management control device, a travel control is executed to regulate the movement of the car. The plurality of cars includes car 1 and car 2. After the group management and control device causes the first car to perform the driving control, it decides to cause the second car to perform the driving control. Based on the execution result of the driving control of the first car, it determines whether the driving control of the second car can be executed and the driving speed when the driving control of the second car is executed.

2. The elevator control system according to claim 1, wherein, The execution result of the travel control includes whether any abnormalities have occurred in the elevator as detected during the travel control process. The travel control includes a diagnostic operation to diagnose whether the elevator can be restored by moving the car, and a rescue operation to move the car, which has stopped between floors, to the nearest floor.

3. The elevator control system according to claim 1, wherein, After the group management control device has enabled a predetermined number of cars, including the first and third cars, to perform the driving control without referring to the execution results of the driving control of other cars, it decides to enable the second car to perform the driving control. Based on the execution results of the driving control of the predetermined number of cars, it determines whether the driving control of the second car can be performed and the driving speed if the driving control of the second car is performed.

4. The elevator control system according to claim 2, wherein, The driving control mentioned above is the rescue operation. The group management and control device determines, based on the execution result of the rescue operation of the first car, whether the second car should travel to the nearest floor above or below during the rescue operation.

5. The elevator control system according to claim 4, wherein, The multiple elevators are rope elevators, each with a car suspended at one end of a rope and a counterweight suspended at the other end of the rope. If the result of the rescue operation in which the first car travels to the nearest floor in the direction away from the counterweight is that an elevator malfunction is detected, the group management control device decides that the second car will travel to the nearest floor in the direction close to the counterweight during the rescue operation.

6. The elevator control system according to claim 4 or 5, wherein, The group management control device determines the car among the plurality of cars that is not occupied by any user as the first car to initially carry out the rescue operation.

Images