Elevator arrangement

Abstract

The present application provides an elevator device which, under certain conditions, allows a hall call registration for a single elevator other than a single elevator stopped at a hall, thereby improving the transportation efficiency. As information for relaxing the restriction on the hall call period of the next single elevator, the congestion degree of the certain single elevator is calculated, and the hall call registration is allowed as necessary, i.e., the hall call operation determination control is performed. In the group management control device (20), an average weight of an adult is used as one person, a load-person number conversion table is prepared in advance, and the number of persons is calculated based on the load detected by the load detection sensor (36).

Description

Technical Field

[0001] This invention relates to an elevator device for managing the lifting and lowering operation of multiple elevator cars. Background Technology

[0002] It is known that there are control technologies that manage the operation of multiple cars of an elevator system as a group for their lifting and lowering. For example, Patent Document 1 describes the following: when determining whether to make the door reopening (the action of reopening from a closed state) effective or ineffective based on the operation of the landing button and the result of the detection of the car's congestion detection device, a first determination element obtained via a single elevator control device is used, based on whether the load value inside the car is above a predetermined value, and a second determination element is used, based on whether the subsequent single elevator has reached the floor corresponding to the landing call of the landing floor within a predetermined time.

[0003] The existing elevator management control, including Patent Document 1, does not allow the door to reopen when a specific single elevator stops at the floor where the call registration is made and the car crowding detection device detects that it exceeds a predetermined value; that is, it does not allow floor call registration.

[0004] However, because elevator users cannot register a floor call before the car doors close, there is a problem that in order to call the next elevator, one must wait for the stopped elevator to depart.

[0005] Patent Document 1: Japanese Patent Application Publication No. 2016-88647 Summary of the Invention

[0006] Therefore, the purpose of this invention is to provide an elevator device that can balance the convenience of users registering for floor calls in the elevator car with the improvement of efficiency in transporting users.

[0007] The elevator device of the present invention comprises: a group management control device that manages multiple elevators, each equipped with a car having openable and closable doors, as a group; landing buttons located at landings for the cars on each floor of the building, for registering calls to the cars; and multiple individual elevator control devices that individually control the lifting and lowering actions of the multiple elevators and the opening and closing actions of the doors. The elevator device also includes: a car crowding detection device located at each of the multiple elevators to determine the crowding level of passengers in the car. The group management control device performs the following processing: during the opening of the car at a stopping floor, registration of the landing button at that stopping floor is prohibited; at a landing on a specific floor, registration of the landing button is permitted when the door of one of the elevators is in the beginning of a closing action, or when the crowding level of the car stopped at that landing is determined to be above a predetermined threshold.

[0008] According to the present invention, an elevator device is provided that can balance the convenience of users registering for floor calls in the elevator car with the improved efficiency of transporting users. Attached Figure Description

[0009] Figure 1 This is a hardware block diagram of an elevator device according to an embodiment of the present invention.

[0010] Figure 2 This is a functional block diagram of the group management control device in the first embodiment.

[0011] Figure 3 This is a flowchart illustrating the actions of the group management and control device.

[0012] Figure 4 This is a functional block diagram of a group management control device according to another embodiment of the present invention.

[0013] Figure 5 This is a flowchart illustrating the car allocation control.

[0014] Figure 6 This is a flowchart of another implementation of additional allocation control.

[0015] Symbol Explanation

[0016] 10. Elevator installations;

[0017] 12 (12A, 12B, 12C) car;

[0018] 14. Elevator control device;

[0019] 16 (16A, 16B, 16C) counterweights;

[0020] 18 (18A, 18B, 18C) cables;

[0021] 20 (20A, 20B, 20C) winches;

[0022] 22 sets of management and control devices;

[0023] 24 (24A, 24B, 24C) Single elevator control devices;

[0024] 26 (26A, 26B, 26C) loudspeakers;

[0025] 28 (28A, 28B, 28C) Car interior control panel;

[0026] 30 (30A, 30B, 30C) door opening and closing mechanism section;

[0027] 32 (32A, 32B, 32C) Opening and closing doors;

[0028] Station buttons on floors 34A and 34B;

[0029] 36 (36A, 36B, 36C) load detection sensors;

[0030] 38-story station camera;

[0031] 40 Image Resolution Unit;

[0032] 50. Information Reception Department;

[0033] 52. Operation Status Determination Unit;

[0034] 54. Allocation and Determination Department;

[0035] 56. Operation Control Department;

[0036] 58. Congestion Calculation Department;

[0037] 60 Load-Passenger Conversion Table Storage;

[0038] The decision on whether to register at the 62nd floor station button is made by the department. Detailed Implementation

[0039] Figure 1 An elevator device 10 representing an embodiment of the present invention. Hereafter, in... Figure 1 In the other accompanying figures, the letter “A” indicates the structure of elevator number 1 out of the three elevators, “B” indicates the structure of elevator number 2, and “C” indicates the structure of elevator number 3.

[0040] The elevator system 10 has multiple cars 12. The elevator system 10 manages the operation of raising and lowering the multiple cars 12 through the elevator control device 14.

[0041] A counterweight 16 is installed on the car 12 via a cable 18, which is wound around the winch 20. Car 12A functions as elevator No. 1, car 12B functions as elevator No. 2, and car 12C functions as elevator No. 3.

[0042] The three elevator cars 12 are grouped together and managed by the group management control device 22 of the elevator control device 14. A single elevator control device 24 is connected to the group management control device 22 to control the raising and lowering of each individual elevator car 12.

[0043] The single-elevator control device 24 controls the drive of the winch 20 and also controls the loudspeakers 26 installed in the car 12. Figure 2 The control panel 28 inside the car and the door opening and closing mechanism 30 shown are used for control.

[0044] The winch 20 operates based on the drive signal from the single elevator control device 24, causing the car 12 to rise and fall.

[0045] The single-elevator control device 24 controls the opening and closing of the doors at the landing of the car 12. The opening and closing of the doors of the car 12 are linked to the opening and closing doors 32 on each floor.

[0046] The group management control device 24 is connected to landing buttons 340 and 342, which are installed on each floor. The landing buttons 340 and 342 correspond to the call buttons of the car 12.

[0047] In addition, the landing button 340 is provided with a main operating part located at a normal height and a secondary operating part located at a height that takes into account the operability from a wheelchair. The secondary operating part may be provided on the landing button 342, or on both landing buttons 340 and 342.

[0048] A load detection sensor 36, serving as a car crowding detection device, is installed at the lower part of the car 12. The load detection sensor 36 detects the load on the floor of the car 12 and sends the detection result to the group management control device 22 via the single elevator control device 24.

[0049] Each floor station is equipped with a floor station camera 38. The floor station camera 38 is connected to the group management and control device 22 via the image analysis unit 40.

[0050] The image analysis unit 40 transmits real-time data on the status of people at the floor level, such as crowding conditions based on headcount, to the group management control device 22 based on images captured by the floor station camera 38. Since users at the floor level frequently increase, decrease, and move, and sometimes goods other than users are present at the floor level, the image recognition camera 38, capable of identifying user status such as headcount and crowding conditions in real time, is optimal. Alternatively, an infrared camera, a load detection sensor, or other detection module could be used.

[0051] When a single elevator car 12 stops at a floor where the call registration level is above a predetermined level, such as when it is close to full capacity, the group management control device 22 does not allow the door in the closing action to be changed to the opening action, i.e., it does not allow the door to be reopened, even if a floor call operation is performed.

[0052] In this situation, even if the user operates the floor buttons 340 and 342, a new floor call cannot be registered before the door closing action is completed.

[0053] In other words, in order to call a specific elevator that is not currently in service (the next elevator), the user must wait until the specific elevator departs.

[0054] Therefore, in the first embodiment, as information for mitigating the restrictions on the next single elevator's floor call period, the congestion level in a particular single elevator, such as a predetermined number of passengers, is calculated, and floor call operations are allowed as needed (the control of whether floor call operations can be performed).

[0055] In the first embodiment, the group management control device 20 prepares a load-person conversion table in advance, using the average weight of an adult as one unit, and calculates the number of passengers based on the load detected by the load detection sensor 36. Alternatively, the car crowding detection device can replace the load detection sensor 36 with a camera that captures images inside the car 12. In this case, the number of passengers can be calculated simply by analyzing the camera's captured information. Furthermore, the camera is not limited to individual imaging elements that convert density into electrical signals (CCD "Charge Coupled Device" sensor, CMOS "Complementary Metal Oxide Semiconductor" sensor); any sensor capable of identifying passengers, such as an infrared thermal imager, can also be used.

[0056] Figure 2 This is a functional block diagram of the group management control device 20, showing the various functions such as whether a floor call operation can be determined and controlled. Furthermore, each block does not limit the hardware structure of the group management control device 20.

[0057] The single-elevator control device 24 is connected to the operating panel 28, door opening and closing mechanism 30, winch 20, load detection sensor 36 and speaker 26 inside the car 12 of the single-elevator.

[0058] The control panel 28 inside the elevator car sends operation signals to the single elevator control device 24 based on passenger operations, such as stop floor indication and open / close indication. Furthermore, if a monitor is available, the single elevator control device 24 sends information displayed on the monitor.

[0059] The door opening and closing mechanism 30 is a mechanism for opening and closing the door 32 when the car 12 stops (parks) at the stop floor, based on the drive signal from the single elevator control device 24.

[0060] The winch 20 winds or unwinds the cable 18 based on the drive signal from the single elevator control device 24, causing the car 12 to rise or fall.

[0061] The load detection sensor 36 detects the load applied to the ground of the car 12 and sends the detected load information to the single elevator control device 24.

[0062] The speaker 26 notifies users of the elevator car 12 of information based on the output signal from the single elevator control device 24. The notification is not limited to sound and may also be displayed.

[0063] like Figure 2 As shown, the group management control device 22 includes an information receiving unit 50, which is connected to the floor station buttons 340 and 342 on each floor. The information receiving unit 50 receives signals based on the operations of the floor station buttons 340 and 342.

[0064] The information receiving unit 50 is connected to the operation status determination unit 52. Based on the operation status of the floor buttons 340 and 342, the operation status determination unit 52 sends a car allocation instruction to the allocation determination unit 54.

[0065] The allocation determination unit 54 determines the car 12 to be allocated and the stop floor of the determined car 12, and sends the operation instruction information to the operation control unit 56. The operation control unit 56 selects the single elevator control device 24 corresponding to the determined car 12 and outputs the operation instruction.

[0066] Upon receiving the operating instruction, the single-elevator control device 24 controls the drive of the winch 20, causing the car 12 to move (rise or fall) to the stop floor.

[0067] After the car 12 stops (parks) at the stop floor, if the door 32 of the stop floor opens in conjunction with the door opening, the load detection sensor 36 detects the load applied to the ground.

[0068] Additionally, at this point, even if the landing buttons 340 and 342 at the stop floor are pressed, other cars cannot be called. This is to prevent car congestion caused by repeated car calls.

[0069] The detected load information is sent to the operation control unit 56 of the group management control unit 22 via the single elevator control device 24. The operation control unit 56 is connected to the congestion calculation unit 58 and sends the load information to the congestion calculation unit 58.

[0070] The congestion calculation unit 58 is connected to the load-passenger-count conversion table memory 60. In the congestion calculation unit 58, the load-passenger-countenger conversion table is read from the memory 60, and the number of passengers is calculated based on the load information received from the operation control unit 56. The calculated number of passengers is then sent to the floor button registration confirmation unit 62.

[0071] The floor button registration system determines whether the number of passengers in the elevator car 12 is at or above the predetermined number (e.g., if the capacity is 15 passengers, then 10 passengers, which is 2 / 3 of the capacity).

[0072] In cases where the number of users exceeds the predetermined number, there may be situations where not all users board the currently stopped car 12 (specific car 12). Therefore, even if the door of the specific car 12 is closed, the landing button registration decision unit 62 allows the operation of the landing buttons 340 and 342.

[0073] The group management and control device consists of hardware resources such as computers, microcomputers, and LSIs. The controller executes control programs recorded in memory to realize the various functions described above in the "units." These "units" can also be referred to as "cells," "modules," etc. The following discussion, from the perspective of the controller's operation, follows... Figure 3 The flowchart illustrates the car's floor call registration performed by the group management control device 22. The controller starts at predetermined intervals. Figure 3 The process.

[0074] In step 100, the controller determines whether the car 12 has stopped at the target floor and whether the door is open. When the controller determines "no" in step 100, the process ends because it is not necessary to determine whether the car can register a floor call.

[0075] If the controller determines "yes" in step 100, it proceeds to step 102. In step 102, the controller sets the car's landing call registration based on the operation of landing buttons 340 and 342 at the object layer to disallow, and proceeds to step 104. In step 104, the controller calculates the car's congestion level based on the load of car 12.

[0076] In the next step 106, if the controller determines that the congestion level is not above the threshold, it proceeds to step 108 to determine whether the door has changed from the open state to the closed state.

[0077] If the controller determines "no" in step 108, it returns to step 104 and repeats steps 104, 106, and 108 until it determines "yes" in step 106 or step 108.

[0078] If the determination is "yes" in step 106 or step 108, the controller moves to step 110, allowing car floor call registration via the operation of floor buttons 340 and 342 on the object layer, and ends the process.

[0079] based on Figure 3 The flowchart illustrates the user's specific actions. When a user registers a floor call by operating floor buttons 340 and 342, the specific car 12 moves to the corresponding floor and stops, opening door 32 (step 100). At this point, the group management control device 22 does not allow floor call registration (step 102).

[0080] Based on the load information from the detection sensor 36 (step 104), if the crowding level of the car 12 is, for example, 40% or more (step 106: Yes), since the car 12 is full or nearly full, sometimes all users waiting at the floor cannot board the car, or it is desirable to prevent users from boarding the car.

[0081] Therefore, even before the stopped elevator car departs, users can register a floor call so that users at the floor where elevator car 12 is stopped can access the next elevator car as soon as possible (step 106: Yes). As with the prior art described above, if the elevator is configured to not reopen if it stops at the floor where the floor call registration is made and the car congestion level is above a predetermined value, then new floor calls cannot be registered until the doors close. Therefore, there is a problem that users have to wait until the elevator car that is stopped at that floor departs in order to call the next elevator.

[0082] If the car that stops at the call registration level is not crowded (step 106: No), the user cannot immediately register to call the car. If it were possible to do so without restriction, there would be no progress in boarding the car that stops at the call registration level, and the efficiency of transporting users would decrease.

[0083] Users cannot register a call for a car until the car door at the call registration floor changes from open to closed (step 108: No).

[0084] However, call registration can also be permitted at least from the time the car is about to depart, so that the user can register the call after the car door begins to move from the open to the closed state (step 108: Yes).

[0085] This allows for a balance between the convenience of users registering and calling at different floors in the elevator car and the increased efficiency of transporting users.

[0086] Hereinafter, other embodiments of the present invention will be described. Regarding the description of the second embodiment, for components identical to those in the first embodiment, the same reference numerals are used in the drawings and their descriptions are omitted.

[0087] The second embodiment is characterized in that the control of the allocation of the car 12 utilizes image information captured by the floor camera 38 installed at the floor. Figure 4 This is a functional block diagram for implementing the group management control device 20. Additionally, Figure 2 , Figure 4 These are examples of functional block diagrams for group management control device 22, and do not limit the hardware structure of group management control device 20.

[0088] The image analysis unit 40 analyzes the images captured by the floor station camera 38 installed at the floor station and sends the analyzed information to the information receiving unit 50 of the group management control device 20. The image analysis information may be, for example, real-time information related to the congestion status of the floor station (number of users).

[0089] The congestion determination unit 64 receives image analysis information from the information receiving unit 50 and, based on a pre-defined threshold, sends a determination result on whether the currently stopped car 12 can adequately accommodate the users of the floor to the cancellation determination unit 66. The cancellation determination unit 66 obtains congestion information of the users inside the car 12 from the congestion calculation unit 58.

[0090] The group management control device 22 allocates cars based on call registrations made through the operation of floor buttons 340 and 342. This is referred to as normal allocation. On the other hand, if the number of floors with registered calls is too high and there are insufficient cars through normal allocation alone, the group management control device 22 allocates additional cars. This is referred to as additional allocation. As will be explained in detail later, if the congestion at a floor is less than a threshold, the cancellation determination unit 66 cancels the additional allocation instead of continuing it.

[0091] The cancellation determination unit 66 is connected to the information output unit 68. The cancellation determination unit 66 generates and sends information regarding maintaining or canceling the association, along with any additional assignments, to the information output unit 68. The information output unit 68 then notifies the association information via a loudspeaker inside the elevator car 12 through the single elevator control device 24.

[0092] Next, based on Figure 5 The flowchart illustrates the allocation control. The controller of group management control device 22 starts upon detecting operation of floor buttons 340 and 342. Figure 5 The process is as follows: In step 200, the controller begins the normal allocation control described above. In step 202, the controller determines the number of users at the floor level based on the detection information from the floor station camera 38, and makes a congestion judgment on whether the number of people at the floor level exceeds the predetermined limit.

[0093] If the controller determines "No" in step 202, the process ends after performing the normal allocation control. If the controller determines "Yes" in step 202, the process proceeds to step 206 and begins the additional allocation control as described above.

[0094] In step 208, the controller determines whether the first car has stopped at the destination floor according to the normal allocation control. If the determination is "yes", the process proceeds to step 210, where the number of users at the destination floor is determined based on the detection information from the floor camera 38, and then the process proceeds to step 212.

[0095] In step 212, the controller determines the congestion of the landing in the same way as in step 202. If the controller determines "yes" in step 212, it proceeds to step 214, measures the load of the car to calculate the congestion level of the car, and then proceeds to step 216.

[0096] In step 216, the controller determines whether the congestion level is less than a threshold. If the determination is "yes," the process proceeds to step 218, where a notification urging the user to board the elevator is delivered via speaker 26. Afterward, the controller terminates the process after performing normal allocation control and additional allocation control. If the controller determines "no" in step 216, step 218 is not executed, and the process terminates after performing normal allocation control and additional allocation control.

[0097] If the controller determines "No" in step 212, it proceeds to step 220 to determine whether the second car will stop at the destination floor with additional allocation control. If the controller determines "No" in step 220, it proceeds to step 222, cancels the additional allocation control midway, and ends the process after the execution of the normal allocation control.

[0098] When the controller determines "yes" in step 220, it is determined that the cancellation of the additional allocation control is too late, and the process ends after the normal allocation control and the additional allocation control are completed.

[0099] Summarize Figure 5 The flowchart illustrates its effect. When a call registration for a car is made based on floor buttons 340 and 342, if the destination floor is crowded with users, it may be impossible to use one car based on normal allocation control to transport all users.

[0100] Therefore, in the second embodiment, the group management control device 22 performs additional allocation control for cars added to the destination floor. This additional allocation control helps to eliminate congestion at the floors.

[0101] However, during the timed periods other than when the car doors are closed, i.e., during the opening or closing of the doors, the floor camera 38 cannot accurately detect the number of people waiting at the floor because users are getting on and off the car.

[0102] Therefore, the group management control device 22 determines whether to perform additional allocation control at the time when the car door is closed, and does not perform this determination at other times.

[0103] However, if the additional allocation alleviates the congestion at the destination floor, and if car allocation continues to be different from the car allocation in the normal allocation control, then few users will utilize the additional cars, and as a result, the allocation of additional cars will not be necessary.

[0104] Therefore, the group management control device 22 can cancel the additional allocation control before the additional car arrives at the destination floor after the additional allocation decision is made. As a result, the group management control device 22 can suppress useless allocation of cars, thereby improving the user's transportation efficiency.

[0105] Even if the group management control device 22 implements additional allocation, if the congestion level inside the car is low despite the crowded floor, meaning the passenger boarding rate is low, it may not be able to immediately alleviate the congestion at the floor and increase further allocation. Therefore, it implements a notification to urge passengers to board (step 218). As a result, the passenger boarding rate inside the car increases, thereby improving the passenger transport efficiency.

[0106] Even if the floor is crowded, the floor camera 38 cannot distinguish whether all passengers are waiting for car 12 or are only occasionally on the floor. When the group management control device 22 performs additional allocation control based on the floor crowding information, the allocation of a second car may not be necessary.

[0107] However, according to Figure 5 The flowchart allows for the cancellation of additional allocations even if a temporary decision is made (step 222), thus suppressing the decrease in transport efficiency associated with additional car allocations.

[0108] Next, other implementations of the additional allocation control will be described. When there are only a few cars 12 that can be added or allocated, the group management control device 22, when a situation arises where multiple floors need to be added and allocated cars, does not follow the order of allocation, but rather determines from which floor to prioritize the addition of cars based on the priority corresponding to the situation.

[0109] For example, suppose there is a case in a 7-story building where multiple floors (e.g., floors 1 and 5) are crowded at the same time, requiring additional allocation control.

[0110] During rush hour (e.g., 7:00 AM), the demand for elevator car 12 on floor 1 is high. Therefore, if additional elevator car 12 allocation control is implemented on floor 5, the congestion on floor 1 will worsen, hindering the flow of people in the building. Therefore, as... Figure 6 As shown in the flowchart, the group management control device 22 determines the floors for priority allocation of elevator cars based on time periods. The controller of the group management control device 22 starts the process at predetermined intervals.

[0111] In step 300, the controller determines whether congestion is detected simultaneously on multiple floors. If the controller determines "no" in step 300, the process ends. If the controller determines "yes" in step 300, it prioritizes the additional allocation to each of the multiple congested floors and allocates additional cars to each floor according to the priority. Time is used as a parameter for prioritization. The controller then proceeds to step 302 to determine whether it is during working hours (e.g., from 7:00 AM to 9:00 AM).

[0112] If the controller determines "yes" in step 302, it proceeds to step 304, prioritizing additional allocations to floors with high user concentration during working hours (e.g., floor 1), and then proceeds to step 306. If the controller determines "no" in step 302, it skips step 304 and proceeds to step 306. In step 306, the controller determines whether it is the off-hours period (e.g., from 4 PM to 6 PM).

[0113] If the controller determines "yes" in step 306, it proceeds to step 308, prioritizes adding allocations to floors with high user concentration during off-hours (e.g., the 5th floor), and then proceeds to step 310. If the controller determines "no" in step 306, it skips step 308 and proceeds to step 310.

[0114] In step 310, the controller determines whether there is an event that should change the priority. For example, it determines whether the first car to be assigned passes through other congested floors with lower priority before stopping at the floor with higher priority. In this case, from the perspective of user transport efficiency, it is preferable to stop the car on the other congested floors first.

[0115] If the controller determines "yes" in step 310, it proceeds to step 312, prioritizing additional allocations for other congested floors not prioritized in step 304 or 308, and ends the process. If the controller determines "no" in step 310, it skips step 312 and ends the process. If the controller determines "no" in step 310, it can perform additional allocations of elevator cars to each floor of multiple floors equally and uniformly, regardless of priority.

[0116] according to Figure 6 The flowchart uses parameters such as time and time period to assign priorities, and allocates additional elevator cars to multiple floors that are simultaneously crowded, thus smoothing the flow of people in the building and improving the transportation efficiency for users. In addition, the parameters are not limited to time, and there is no specific limit to the number of users on each floor.

[0117] Furthermore, for example, in a 7-story building, if congestion occurs simultaneously on the 1st and 5th floors during rush hour, and all elevator cars 12 stop on floors above the 5th floor, if the first single elevator car moves from the congested 5th floor to the 1st floor, the user's transportation efficiency will decrease. Therefore, even if the group management control device 22 temporarily decides to prioritize the 1st floor (step 304), it can change to prioritize the 5th floor. As a result, the operating rate for additional car allocation is increased, and the user's transportation efficiency is improved.

[0118] The embodiments described above are examples of the present invention and do not limit the present invention. Modifications, deletions, substitutions, or additions of other structures or functions to a portion of the described embodiments are also included within the technical scope of the present invention. Further description follows.

[0119] If car 12A of elevator number 1 out of the three cars 12 is wheelchair-accessible, and a call for that car is registered after the aforementioned additional allocation control has been determined, then, in addition to the two cars used for additional allocation control, car 12A with wheelchair access will serve as a third car to serve users on the destination floor. In this case, the three cars 12A, 12B, and 12C are concentrated on the same floor, and service to other floors is suspended.

[0120] Therefore, after deciding on additional allocation, if the group management control device 22 registers a call for a wheelchair-accessible car, and if predetermined conditions, such as the time required to reach the destination floor of the additionally allocated car, are more than 20 seconds, it can change the second elevator controlled for additional allocation from elevator number 3 (car 12C) to elevator number 1 (car 12A). Thus, the elevator system can handle additional car allocations for wheelchair users without compromising the user's transportation efficiency.

[0121] On the other hand, after multiple elevator cars are allocated, the first car completes the service for the user after reaching the destination floor. However, if the next elevator car cannot reach the destination floor even after the scheduled time, the congestion on that floor will not be eliminated, and the flow of people in the building will be hindered.

[0122] Therefore, even after deciding on an additional allocation, the group management control device 22 can change the allocation of cars based on the lobby calls and car calls from other floors, including the car 12 that departed as the first car in the additional allocation. This allows for the allocation of a larger number of cars to the destination floor, thus eliminating congestion during floor calls.

[0123] Next, if floor station call registration is permitted ( Figure 1 Step 110) indicates that there is a demand for a floor call at that time. When no floor congestion is detected outside the door closing state ( Figure 5 (Step 202) Even if a floor call is operated, the group management control device 22 cannot set additional allocation control.

[0124] Therefore, when floor call registration is permitted, the group management control device 22 can detect floor congestion even during the period from door opening to door closing. This allows for additional allocation of cars to the destination floor at an earlier stage to address floor congestion.

[0125] In addition, this specification includes the invention of the structure described in the following notes.

[0126] (Postscript)

[0127] An elevator system includes: a group management control device that manages multiple elevators, each equipped with a car having openable and closable doors, as a group; floor buttons located at each floor of a building for each car, registering calls to the car; and multiple individual elevator control devices that individually control the lifting and lowering actions of the multiple elevators and the opening and closing actions of the doors. The elevator system also includes a floor congestion detection device that detects congestion at each floor. This device simultaneously detects congestion at multiple floors. When additional car allocation is performed on predetermined floors with predefined priority and on floors different from the predetermined floors, the group management control device prioritizes allocating cars to the predetermined floors or the different floors according to a time period. If one of the additionally allocated cars passes a non-priority floor earlier than a floor that is supposed to stop at a priority floor, the non-priority floor is then prioritized for additional allocation control and reallocated.

Claims

1. An elevator system comprising: a group management control device for collaboratively managing multiple elevators, each equipped with a car having openable and closable doors, as a group; floor buttons located at floors of a building for each car, for registering calls from the cars; and multiple individual elevator control devices for individually controlling the lifting and lowering movements of the multiple elevators and the opening and closing movements of the doors, characterized in that... The elevator system includes a car crowding detection device, which is installed in each of the plurality of elevators to determine the crowding level of the passengers in the car. The group management and control device performs the following processing: During the process of opening the car at the stop floor, it is on the premise that the floor button is not allowed to be registered at that stop floor; At a specific floor stop, if the door of one of the elevator cars is in the beginning of its closing action, or if it is determined that the crowding level of the car stopped at that floor exceeds a predetermined threshold, then registering the floor button is permitted. The elevator system also includes a floor congestion detection device for detecting the congestion level of the floors. The group management and control device performs the following processing: When a specific car stops at a predetermined stop floor and the door is in the beginning of the closing action, if the floor congestion detection device determines that the congestion level of the floor is above a predetermined threshold, additional allocation control is performed to allocate additional cars of the elevator other than the specific car to the predetermined stop floor. After deciding to add allocation control, if the congestion detection device at the floor determines that the congestion has been eliminated, the control to cancel the additional allocation control will be executed.

2. The elevator device according to claim 1, characterized in that, The elevator system also includes a notification unit located in the car, used to urge passengers to board the car. When the group management control device determines that the crowding level of the car is less than a predetermined threshold and the crowding level of the floor is above a predetermined threshold, it executes a notification control to urge passengers to board through the notification unit.

3. The elevator device according to claim 1, characterized in that, After the additional allocation control is determined and the first car stops at the corresponding floor, if a predetermined time has elapsed while the occupancy rate is below a predetermined level and the congestion at the floor is above a predetermined level, the additional allocation is cancelled.

4. The elevator device according to claim 1, characterized in that, When the congestion detection device detects congestion on multiple floors simultaneously and performs additional car allocation for predetermined floors with set priority and floors different from the predetermined floors, the group management control device prioritizes allocating the cars to the predetermined floors or the different floors according to the time period. If any of the additionally allocated cars passes through a non-priority allocated floor before stopping at the priority allocated floor, the non-priority allocated floor is reassigned as the priority object for additional allocation control.

5. The elevator device according to claim 1, characterized in that, Some of the aforementioned elevators are equipped with wheelchair-accessible cars, and each floor has wheelchair-accessible landing buttons for calling the wheelchair-accessible cars. After deciding to add additional allocation control, the group management control device, when the wheelchair-accessible floor button is pressed and under predetermined conditions, will reassign the single elevator with wheelchair functionality as the second elevator to be added for allocation control.

6. The elevator device according to claim 1, characterized in that, After deciding to add an additional allocation control, if the second elevator, which is the additional allocation control, fails to reach the corresponding floor even after a predetermined time, the group management control device will reassign the second elevator, which is the additional allocation control, to other single elevators.

7. The elevator device according to claim 1, characterized in that, The group management control device, after allowing the registration of floor station calls, also detects whether there is congestion in the floor station calls from the time the door is opened to the time the door is closed.

Images