CN117623021A - Elevator device - Google Patents

Abstract

The invention provides an elevator device, which allows landing call registration to other single ladders except the single ladder stopped at the landing under specific conditions, thereby improving the conveying efficiency. As information for alleviating restrictions on the landing call timing of the next single ladder, the congestion degree of the specific single ladder is calculated, and landing call registration, that is, landing call operation availability determination control is performed as needed. In a group management control device (20), a load-person number conversion table is prepared in advance with the average weight of an adult as one person, and the person number is calculated from the load detected by a load detection sensor (36).

Description

Elevator device

Technical Field

The present invention relates to an elevator apparatus for managing the lifting operation of a plurality of cars.

Background

A control technique for managing a plurality of cars of an elevator apparatus as a group for lifting and lowering operations thereof is known. For example, patent document 1 describes the following: when determining whether to activate or deactivate the re-opening of the door (the operation of re-opening from the closed state) based on the determination element based on the result of detecting the operation state of the car congestion degree detection device according to the operation of the landing button, a first determination element based on whether or not the car load value obtained via the single-step control device is equal to or greater than a predetermined value and a second determination element based on whether or not the subsequent single step reaches a landing call of a landing floor within a predetermined time are used.

The conventional elevator management control of patent document 1 is included, and when a specific single elevator is stopped at a landing call registration floor and a car congestion degree detection device detects a predetermined value or more, the door is not allowed to be reopened, that is, landing call registration is not allowed.

However, since the elevator user cannot register a landing call until the door of the car is closed, there is a problem in that the user must wait for a stop single elevator to start in order to call the next single elevator.

Patent document 1: japanese patent laid-open publication 2016-88647

Disclosure of Invention

Accordingly, an object of the present invention is to provide an elevator apparatus capable of improving both convenience in registering a landing call of a car by a user and efficiency in transporting the user.

An elevator device of the present invention includes: a group management control device that performs cooperative management of a plurality of elevator elevators each including a car provided with a door that can be opened and closed as a group; landing buttons provided on respective floors of a building for registering calls to the car; and a plurality of single-elevator control devices that individually control operations including lifting operations of the plurality of elevator lifts and opening and closing operations of the doors, wherein the elevator device includes: and a car congestion degree detection device provided for each of the plurality of elevator hoists, for determining a congestion degree of a person riding on the car, wherein the group management control device performs: in the process of opening the car at the stop layer, on the premise that the landing button is not allowed to be registered at the stop layer; when the door of the car of one of the elevator elevators is in the start state of the closing operation at the landing of a specific floor or when it is determined that the degree of congestion of the car stopped at the landing is equal to or greater than a predetermined threshold value, the landing button is permitted to be registered.

According to the present invention, an elevator apparatus is provided that can achieve both convenience in registering a landing call of a car by a user and improvement in efficiency in transporting the user.

Drawings

Fig. 1 is a hardware block diagram of an elevator apparatus according to an embodiment of the present invention.

Fig. 2 is a functional block diagram of the group management control device of the first embodiment.

Fig. 3 is a flowchart showing the operation of the group management control device.

Fig. 4 is a functional block diagram of a group management control device according to another embodiment of the present invention.

Fig. 5 is a flowchart illustrating the car assignment control.

Fig. 6 is a flowchart of another embodiment of additional allocation control.

Symbol description

An elevator apparatus;

12 (12A, 12B, 12C) cars;

14 elevator control means;

16 (16A, 16B, 16C) weights;

18 (18A, 18B, 18C) a cable;

20 (20A, 20B, 20C) windlass;

22 group management control devices;

24 (24A, 24B, 24C) single ladder control device;

26 (26A, 26B, 26C) speakers;

28 (28A, 28B, 28C) an in-car operation panel;

30 (30A, 30B, 30C) a door opening and closing mechanism section;

32 (32A, 32B, 32C) opening and closing the door;

34A, 34B landing buttons;

36 (36A, 36B, 36C) load detection sensors;

38 landing cameras;

40 an image analysis unit;

50 an information receiving unit;

52 an operation state determination unit;

54 an allocation determination unit;

56 running a control part;

58 crowding degree calculating part;

60 load-riding number conversion table memories;

the 62-landing button registration disclaimer.

Detailed Description

Fig. 1 shows an elevator apparatus 10 according to an embodiment of the present invention. In fig. 1 and the other drawings, a "attached with a numeral indicates the structure of the No. 1 elevator among the 3 elevators, B" indicates the structure of the No. 2 elevator, and C "indicates the structure of the No. 3 elevator.

The elevator apparatus 10 includes a plurality of cars 12. The elevator apparatus 10 manages the operation of lifting and lowering the plurality of cars 12 by the elevator control apparatus 14.

A counterweight 16 is attached to the car 12 via a rope 18, and the rope 18 is wound around a hoist 20. Car 12A functions as an elevator No. 1, car 12B functions as an elevator No. 2, and car 12C functions as an elevator No. 3.

The 3 cars 12 are collectively managed as 1 group by the group management control device 22 of the elevator control device 14. A single-elevator control device 24 that controls the elevation of the car 12 of each single elevator is connected to the group management control device 22.

The single-stage control device 24 controls driving of the hoist 20, and controls a speaker 26 provided in the car 12, an in-car operation panel 28 shown in fig. 2, and a door opening/closing mechanism unit 30.

The hoisting machine 20 operates based on a drive signal from the single-stage control device 24 to raise and lower the car 12.

The single-step control device 24 controls opening and closing of doors at a stop floor of the car 12. The opening and closing of the doors of the car 12 are linked with the respective opening and closing doors 32 of the respective floors.

The group management control device 24 is connected to the landing buttons 340 and 342 provided at the respective layers. Landing buttons 340, 342 correspond to calls to car 12.

The landing button 340 is provided with a main operation unit provided at a normal height position and a sub operation unit provided at a height position in consideration of operability from a wheelchair, for example. The sub operation unit may be provided on the landing button 342, or may be provided on both the landing buttons 340 and 342.

A load detection sensor 36 as a car congestion degree detection device is mounted on the lower part of the car 12. The load detection sensor 36 detects the load on the floor of the car 12, and transmits the detection result to the group management control device 22 via the single-step control device 24.

A landing camera 38 is provided at each layer of the landing. The hall camera 38 is connected to the group management control device 22 via an image analysis unit 40.

The image analysis unit 40 transmits the status of the person at the hall, for example, the congestion status based on the number of people count, to the group management control device 22 in real time based on the image captured by the hall camera 38. The camera 38 for image recognition, which can recognize the status of the user, for example, the number of people and the crowded status, is optimal because the user at the landing frequently increases and decreases and moves and there are some goods other than the user at the landing. Instead of this, a detection module such as an infrared camera or a load detection sensor may be used.

When the car 12 of a single elevator stops at a landing call registration floor and the degree of congestion is equal to or higher than a predetermined level, for example, the car is in a state of being nearly full, the group management control device 22 does not allow the door in the closing operation to be changed to the opening operation, that is, does not allow the door to be reopened even if the landing call operation is performed.

In this case, even if the user operates the landing buttons 340 and 342 before the door closing operation is completed, the landing call cannot be newly registered.

In other words, the user must wait until the specific single ladder starts in order to get to a single ladder (next single ladder) other than the specific single ladder in the call stop.

Therefore, in the first embodiment, as information for alleviating restrictions on the landing call timing of the next single ladder, the degree of congestion in the specific single ladder, for example, the number of passengers on a predetermined or more ladder, is calculated, and if necessary, landing call operation is permitted (landing call operation availability determination control).

In the first embodiment, the group management control device 20 prepares a load-person number conversion table in advance for an average weight of an adult of 1 unit, and calculates the person number from the load detected by the load detection sensor 36. In addition, the car congestion degree detection device may be a camera that photographs the inside of the car 12 instead of the load detection sensor 36, and in this case, the number of passengers may be calculated by analyzing the photographed information of the camera. The camera is not limited to an individual image pickup device (a CCD "Charge Coupled Device" sensor or a CMOS "Complementary Metal Oxide Semiconductor" sensor) that converts the density into an electric signal, and may be another sensor such as a thermal infrared imager as long as the passenger can be recognized.

Fig. 2 is a functional block diagram showing the functions of the group management control device 20, such as the hall call operation availability determination control. The blocks are not limited to the hardware configuration of the group management control device 20.

The single-stage control device 24 is connected to an in-car operation panel 28, a door opening and closing mechanism 30, the hoist 20, a load detection sensor 36, and a speaker 26 provided in the car 12 of the single stage.

The in-car operation panel 28 transmits an operation signal to the single-step control device 24 in response to an operation of the passenger, for example, a stop floor instruction or an open/close instruction. In the case of providing a monitor, the information displayed on the monitor is transmitted from the single-stage control device 24.

The door opening/closing mechanism 30 is a mechanism for opening/closing the door 32 when the car 12 stops (stops) at a stop floor based on a drive signal from the single-stage control device 24.

The hoist 20 winds and unwinds the rope 18 to raise and lower the car 12 based on a drive signal from the single-step control device 24.

The load detection sensor 36 detects a load applied to the floor of the car 12, and transmits detected load information to the single-step control device 24.

The speaker 26 notifies the user of the boarding car 12 based on an output signal from the single-step control device 24. The notification is not limited to the sound, and may be displayed.

As shown in fig. 2, the group management control device 22 includes an information receiving unit 50, and is connected to the hall buttons 340 and 342 of each layer. The information receiving unit 50 receives signals based on the operations of the landing buttons 340 and 342.

The information receiving unit 50 is connected to the operation state determining unit 52. The operation state determination unit 52 sends an assignment instruction of the car to the assignment determination unit 54 based on the operation states of the hall buttons 340 and 342.

The assignment specification unit 54 specifies the car 12 to be assigned, determines the stop layer of the specified car 12, and sends the operation instruction information to the operation control unit 56. The operation control unit 56 selects the single-stage control device 24 corresponding to the specified car 12 and outputs an operation instruction.

The single-step control device 24, which receives the operation instruction, controls the driving of the hoist 20 to move (raise or lower) the car 12 to the stop floor.

After the car 12 stops (stops) at the stop floor, if the opening/closing door 32 of the stop floor is opened in conjunction with the opening of the door, the load detection sensor 36 detects the load applied to the floor.

In this case, even if the landing buttons 340 and 342 for stopping the landing are operated, the other car cannot be called. This is to prevent car concentration due to repeated car calls.

The detected load information is transmitted to the operation control unit 56 of the group management control device 22 via the single ladder control device 24. The operation control unit 56 is connected to the congestion degree calculation unit 58, and sends the load information to the congestion degree calculation unit 58.

The congestion degree calculation unit 58 is connected to a load-passenger number conversion table memory 60. The congestion degree calculating unit 58 reads the load-boarding number conversion table from the load-boarding number conversion table memory 60, and calculates the boarding number based on the load information received from the operation control unit 56. The calculated number of passengers is sent to the hall button registration disclaimer 62.

The hall button registration disclaimer 62 determines whether or not the number of passengers in the car 12 is a predetermined number (for example, 10 of the number of passengers 2/3 if the number of passengers is 15).

If the number is equal to or greater than the predetermined number, the user may not be riding the currently parked car 12 (the specific car 12), and thus the hall button registration-denied portion 62 may permit the hall buttons 340 and 342 to be operated even when the door of the specific car 12 is in the closing operation.

The group management control device is composed of hardware resources such as a computer, microcomputer, LSI, and the like. The controller executes a control program recorded in the memory to realize the "part" forming the various functions described above. The "part" may be modified as a "unit", "module", or the like. Next, from the viewpoint of the operation of the controller, the landing call registration of the car by the group management control device 22 will be described with reference to the flowchart of fig. 3. The controller starts the flow of fig. 3 every predetermined time.

In step 100, the controller determines whether the car 12 is stopped at the target floor, and determines whether the door is open. When the controller determines no in step 100, it is not necessary to determine whether or not landing call registration of the car is possible, and the flow ends.

If the controller determines "yes" in step 100, the process proceeds to step 102. In step 102, the controller sets the hall call registration of the car based on the operation of the hall buttons 340 and 342 of the target hall to be not permitted, and proceeds to step 104. In step 104, the controller calculates the degree of congestion of the car based on the load of the car 12.

In the next step 106, when the controller determines that the degree of congestion is not equal to or greater than the threshold value, the routine proceeds to step 108, where it is determined whether or not the door has operated from the open state to the closed state.

If the controller determines no in step 108, the routine returns to step 104, and repeats steps 104, 106, and 108 until the controller determines yes in step 106 or 108.

If the determination at step 106 or step 108 is yes, the controller proceeds to step 110, and allows landing call registration of the car by the operation of the landing buttons 340 and 342 of the target floor, and ends the flow.

The specific operation of the user will be described based on the flowchart of fig. 3. When the user operates the landing buttons 340, 342 to register it, the particular car 12 moves to the corresponding landing and stops, opening the door 32 (step 100). At this point in time, the group management control device 22 does not permit registration of the landing call (step 102).

If the degree of congestion of the car 12 is 40% or more (yes in step 106) based on the load information from the detection sensor 36 (step 104), the car 12 may be in a full or nearly full state, and thus, it may be impossible or desirable to avoid the user from getting on the car by all users waiting at the hall.

Therefore, even before the stopped car starts, the user can register a landing call so that the user of the floor where the car 12 is stopped can access the car of the next single elevator as early as possible (step 106: yes). As in the prior art described above, if the elevator car is stopped at the hall call registration hall and the car congestion level is equal to or higher than the predetermined value, the elevator car is not allowed to be re-opened, and the hall call cannot be newly registered until the door is closed, so that there is a problem in that the user waits until the elevator car of the single elevator stopped at the hall starts to call the next single elevator.

If the car stopped at the hall call registration hall is not congested (step 106: no), the user cannot immediately perform the call registration of the car. If the operation is allowed to be performed without limitation, the car stopped at the call registration floor cannot be carried forward, and the efficiency of transporting the user is deteriorated.

The user cannot perform the call registration of the car until the door of the car stopped at the hall call registration hall is changed from the open to the closed state (step 108: no).

However, since the call registration may be permitted at least from the point in time when the car is to be started, the user can perform the call registration after the door of the car starts to move from the open state to the closed state (yes in step 108).

This makes it possible to improve both the convenience of the user in registering a landing call of the car and the efficiency of the user in transporting the car.

Hereinafter, other embodiments of the present invention will be described. In the description of the second embodiment, the same reference numerals are given to the same constituent parts as those of the first embodiment in the drawings, and the description thereof is omitted.

The second embodiment is characterized in that image information captured by a hall camera 38 provided at a hall is used for control of assignment of the car 12. Fig. 4 is a functional block diagram for realizing the group management control device 20. Fig. 2 and 4 are examples of functional block diagrams of the group management control device 22, and do not limit the hardware configuration of the group management control device 20.

The image analysis unit 40 analyzes an image obtained by capturing a landing by the landing camera 38 provided at the landing, and transmits analysis information to the information reception unit 50 of the group management control device 20. The image analysis information is, for example, real-time information related to the congestion state (the number of users) of the hall.

The congestion status determination unit 64 receives the image analysis information from the information reception unit 50, and sends the determination result of whether the currently stopped car 12 can adequately accommodate the user of the hall to the cancellation determination unit 66 based on a predetermined threshold. The cancellation determining unit 66 obtains the congestion degree information of the user in the car 12 from the congestion degree calculating unit 58.

The group management control device 22 registers the assigned car for a call based on the operation of the landing buttons 340, 342. This is referred to as normal allocation. On the other hand, when the number of floors in which call registration is performed is large due to congestion of a large number of users, and the cars are insufficient only by normal assignment of the cars, the group management control device 22 assigns additional cars. This is referred to as additional allocation. As will be described in detail later, when the congestion state of the hall is smaller than the threshold value, the cancellation determination unit 66 performs cancellation without maintaining additional allocation.

The cancellation judging section 66 is connected to the information outputting section 68. The cancellation judging unit 66 generates information related to maintenance or cancellation of the additional allocation and transmits the information to the information outputting unit 68. The information output unit 68 notifies the relevant information from the speaker in the car 12 via the single-step control device 24.

Next, the allocation control is described based on the flowchart of fig. 5. The controller of the group management control device 22 starts the flow of fig. 5 upon detecting the operation of the landing buttons 340, 342. In step 200, the controller starts the above-described normal distribution control. In step 202, the controller grasps the number of users at the hall based on the detection information of the hall camera 38, and determines whether or not the number of hall persons is equal to or greater than a predetermined congestion.

When the controller determines no in step 202, the flow ends after executing the normal allocation control. If the controller determines "yes" in step 202, the routine proceeds to step 206, where the above-described additional allocation control is started.

In step 208, the controller determines whether or not the first car is stopped at the destination floor in accordance with the normal allocation control, and if yes, the process proceeds to step 210, the number of users at the destination floor is grasped from the detection information of the destination floor camera 38, and the process proceeds to step 212.

In step 212, the controller determines congestion of the hall in the same manner as in step 202. If the controller determines "yes" in step 212, the flow proceeds to step 214, where the load of the car is measured to calculate the degree of congestion of the car, and the flow proceeds to step 216.

In step 216, the controller determines whether or not the degree of congestion is less than a threshold value, and if yes, the process proceeds to step 218, where a notification prompting the user to get in the car is executed via the speaker 26. Then, the controller executes the normal allocation control and the additional allocation control, and then ends the flow. If the controller determines "no" in step 216, the routine ends after the normal allocation control and the additional allocation control are executed without executing step 218.

If the controller determines "no" in step 212, the process proceeds to step 220, where it is determined whether the second car stops at the destination floor with additional allocation control. If the controller determines "no" in step 220, the routine proceeds to step 222, where the additional allocation control is canceled in the middle of the execution of the normal allocation control, and the flow ends.

If the controller determines "yes" in step 220, it determines that the cancellation of the additional allocation control is not completed, and ends the flow after the normal allocation control and the additional allocation control are completed.

The effect will be described by summarizing the flowchart of fig. 5. When the call registration of the car is performed by the hall buttons 340 and 342, if the hall of the destination hall is crowded by the user, the entire user may not be transported by using 1 car under the normal allocation control.

Therefore, in the second embodiment, the group management control device 22 performs additional allocation control of allocating additional cars to the destination floors. By adding the allocation control, congestion of the landing can be eliminated.

However, at a timing other than the completion of the closing of the car, i.e., during the opening of the door, during the completion of the opening of the door, or during the closing of the door, the landing camera 38 cannot accurately detect the number of waiting persons at the landing due to the user getting on or off the car.

Therefore, the group management control device 22 determines whether or not to perform additional allocation control at the timing when the door closing of the car is completed, and does not perform this determination at other timings.

However, if the congestion of the destination floor is alleviated after the determination of the additional allocation, if the car allocation is continued which is different from the car allocation in the normal allocation control, the number of users who use the additional car is small, and as a result, the additional car allocation is not required.

Therefore, the group management control device 22 can cancel the additional allocation control before the additional car reaches the destination floor after the additional allocation determination. As a result, the group management control device 22 can suppress wasteful allocation of the cars, and as a result, the conveyance efficiency of the user can be improved.

Even if additional allocation is performed, if the congestion level in the car is low, that is, if the user's boarding rate to the car is low, there is a possibility that the congestion level of the hall cannot be relieved at a glance and further additional allocation is increased. Accordingly, notification prompting boarding is performed (step 218). As a result, the riding rate of the user in the car increases, and the transportation efficiency of the user can be improved.

The hall camera 38 cannot distinguish between a person waiting for the car 12 and a person who is at the hall occasionally even if the hall is crowded with a large number of people. When the group management control device 22 performs additional allocation control based on the information of the hall congestion, as a result, allocation of the second car may not be required.

However, according to the flowchart of fig. 5, even if the additional allocation is determined temporarily, it can be canceled (step 222), and therefore, a decrease in conveying efficiency associated with the additional allocation of the car can be suppressed.

Next, another embodiment of additional allocation control will be described. When there are fewer than 1 additionally assignable cars 12, the group management control device 22 determines from which floor to which to give priority to additional assignment of cars, not in the order of the cars, but with a priority according to the situation when a phenomenon that additional assignment of cars to a plurality of floors is required occurs.

For example, in a 7-story building, if a plurality of floors (for example, 1 floor and 5 floors) are simultaneously crowded, additional allocation control is required.

In the case of the working hours (for example, at 7 a.m.), since the demand for the car 12 in the landing of the 1 floor is high, if additional allocation control of the car 12 is performed at 5 floors, the congestion condition of the 1 floor is deteriorated, and this causes a disturbance of the traffic flow in the building. Therefore, as shown in the flowchart of fig. 6, the group management control device 22 determines the floor to which the car is preferentially additionally assigned according to the time zone. The controller of the group management control device 22 starts the flow every predetermined time.

In step 300, the controller determines whether congestion is detected at multiple floors simultaneously. If the controller determines "no" in step 300, the flow ends. If the controller determines "yes" in step 300, the controller sets a priority for additional allocation to each of the crowded floors, and performs additional allocation of cars for each floor according to the priority. As a parameter for priority, there is time. The controller transitions to step 302 to determine whether it is a shift-in period (e.g., from 7 am to 9 am).

If the controller determines "yes" in step 302, the process proceeds to step 304, and the additional allocation is preferentially performed on the floor (for example, 1 floor) on which the users are concentrated during the working hours, and the process proceeds to step 306. If the controller determines "no" in step 302, step 304 is skipped and the process moves to step 306. In step 306, control determines whether it is a off-hours period (e.g., from 4 pm to 6 pm).

If the controller determines "yes" in step 306, the flow proceeds to step 308, and the controller preferably performs additional allocation to the floor (e.g., 5 floors) on which the users are concentrated during the next shift, and proceeds to step 310. If the controller determines "no" in step 306, step 308 is skipped and the process moves to step 310.

The controller determines in step 310 whether there is an event that should change priority. For example, it is determined whether or not the first car to be additionally assigned passes through another crowded floor that is not prioritized earlier than stopping to the floor that is preferentially assigned. In this case, from the viewpoint of the transport efficiency of the user, it is preferable to stop the car at another crowded floor first.

If the controller determines "yes" in step 310, the flow proceeds to step 312, where the controller preferentially performs additional allocation to the other congestion layer not prioritized in step 304 or step 308, and ends the flow. If the controller determines "no" in step 310, the process ends by skipping step 312. If the controller determines no in step 310, the additional allocation of cars to each of the plurality of floors can be performed equally and uniformly regardless of the priority.

According to the flowchart of fig. 6, priority is given to each of a plurality of floors that are simultaneously crowded, and additional allocation of cars is performed based on parameters such as time and time slots, so that it is possible to smooth the flow of people in the building and to improve the transportation efficiency of users. The parameter is not limited to time, and is not particularly limited to the number of users per floor.

In a 7-story building, for example, if congestion of a landing occurs at both 1 story and 5 stories during a working period and all of the cars 12 stop at 5 or more stories, the transportation efficiency of the user is lowered if the car of the first single elevator moves to 1 story by the congested 5 stories. Therefore, even if the group management control device 22 temporarily determines to prioritize the layer 1 (step 304), it can change to prioritize the layer 5. This improves the operation rate for additional allocation of the car, and improves the transport efficiency of the user.

The embodiments described above are examples of the present invention, and are not intended to limit the present invention. Other configurations and functions are also included in the technical scope of the present invention, as are modifications, deletions, substitutions, and other configurations and functions of some of the above-described embodiments. The following will further explain.

When the car 12A of the No. 1 elevator of the 3 cars 12 has a wheelchair function, if a call to the car is registered after the above-described additional allocation control is determined, the car 12A having the wheelchair function is used as a third car for the user service to the destination floor, in addition to the 2 cars used for the additional allocation control. In this case, the 3 cars 12A, 12B, 12C are concentrated on the same floor, and service is stopped for other floors.

Therefore, when a call for a car of a wheelchair is registered after the additional allocation is determined, the group management control device 22 can change the second station of the additional allocation control from the No. 3 elevator (car 12C) to the No. 1 elevator (car 12A) if a predetermined condition, for example, a time required to reach the destination floor of the additional allocated car is 20 seconds or more. Thus, the elevator apparatus can cope with wheelchair users without impairing the transport efficiency of the users in additional allocation of the cars.

On the other hand, after a plurality of cars are additionally allocated, the first car reaches the destination floor and then the user service is completed, but even if the next car cannot reach the destination floor after a predetermined time, the traffic on the floor is not eliminated, and the traffic in the building is hindered.

Therefore, even after the additional allocation is determined, the group management control device 22 can change the allocation of the car including the car 12 that starts as the first station of the additional allocation, depending on the hall call or the car call condition of the other floor. This allows cars of a plurality of elevator amounts to be allocated to a destination floor, and thus can eliminate congestion of landing calls.

Next, in case the landing call registration is allowed (fig. 1: step 110), it can be said that there is a need for landing calls for the floor at this point in time. When no hall congestion is detected other than the door-closed state (fig. 5: step 202), even if the hall call is operated, the group management control device 22 cannot set the additional allocation control.

Therefore, in the case where the hall call registration is permitted, the group management control device 22 can detect congestion of the hall from the completion of opening the door to the completion of closing the door. This makes it possible to start additional allocation at an early stage for congestion at a landing, and to additionally allocate a car to a destination landing.

The present specification includes the invention having the structure described in the following additional notes.

(additionally remembered)

An elevator device is provided with: a group management control device that performs cooperative management of a plurality of elevator elevators each having a car provided with a door that can be opened and closed as a group; landing buttons provided on respective floors of a building for registering calls to the car; and a plurality of single-elevator control devices that individually control operations including lifting operations of the plurality of elevator elevators and opening/closing operations of the doors, wherein the elevator device includes a landing congestion degree detection device that detects a congestion degree of the landing, the landing congestion degree detection device simultaneously detects congestion of a plurality of floors, and when additional allocation of cars is performed for each of a predetermined floor and a floor different from the predetermined floor, in which priorities are set, the group management control device preferentially allocates the cars to the predetermined floor or the different floors according to a time zone, and when one of 1 of the additionally allocated cars passes through a floor that is not preferentially allocated earlier than a floor that stops at the priority allocation, the group management control device performs reassignment of the non-preferentially allocated floor as a priority target of additional allocation control.

Claims (8)

1. An elevator device is provided with: a group management control device that performs cooperative management of a plurality of elevator elevators each having a car provided with a door that can be opened and closed as a group; landing buttons provided on respective floors of a building for registering calls to the car; and a plurality of single-step control devices for individually controlling the lifting operation of the plurality of elevator lifts and the opening and closing operation of the doors,

the elevator device comprises: a car crowding degree detection device provided for each of the plurality of elevator elevators, for determining the crowding degree of a person riding on the car,

the group management control device performs the following processing:

in the process of opening the car at the stop layer, on the premise that the landing button is not allowed to be registered at the stop layer;

when the door of the car of one of the elevator elevators is in the start state of the closing operation at the landing of a specific floor or when it is determined that the degree of congestion of the car stopped at the landing is equal to or greater than a predetermined threshold value, the landing button is permitted to be registered.

2. Elevator arrangement according to claim 1, characterized in that,

the elevator apparatus further has a landing congestion degree detection device that detects a congestion degree of the landing,

the group management control device performs the following processing:

when a specific car stops at a landing of a predetermined stop floor and a door is in a state of starting a closing operation, if the landing congestion level detection device determines that the congestion level of the landing is equal to or higher than a predetermined threshold value, an additional allocation control is executed to additionally allocate a car of the elevator other than the specific car to the predetermined stop floor;

after the additional allocation control is determined, if the congestion degree detection device of the landing determines that congestion is eliminated, control to cancel the additional allocation control is performed.

3. Elevator arrangement according to claim 2, characterized in that,

the elevator apparatus further comprises a notification unit provided in the car for urging the car to ride,

the group management control device executes notification control for prompting boarding by the notification unit when it is determined that the degree of congestion of the car is less than a predetermined threshold value and the degree of congestion of the hall is equal to or greater than the predetermined threshold value.

4. Elevator arrangement according to claim 2, characterized in that,

when a predetermined time has elapsed while the boarding rate is equal to or less than a predetermined value and the congestion of the landing is equal to or more than a predetermined value after the additional allocation control is determined and the first car stops at the corresponding floor, cancellation of additional allocation is performed.

5. Elevator arrangement according to claim 2, characterized in that,

when the floor congestion degree detection device detects congestion of a plurality of floors at the same time and performs additional allocation of cars to each of a predetermined floor and a floor different from the predetermined floor, the group management control device preferentially allocates the cars to the predetermined floor or the different floors according to a time zone, and reallocates the non-preferentially allocated floor as a priority target for additional allocation control when any 1 of the additionally allocated cars passes through the non-preferentially allocated floor before stopping at the preferentially allocated floor.

6. Elevator arrangement according to claim 2, characterized in that,

some of the plurality of the elevator elevators are provided with a car having a wheelchair function, each floor is provided with a landing button for a wheelchair for calling the car having the wheelchair function,

the group management control device, after determining the additional allocation control, when the wheelchair landing button is pressed, reallocates the single ladder with the wheelchair function to the second station of the additional allocation control when a predetermined condition is satisfied.

7. Elevator arrangement according to claim 2, characterized in that,

the group management control device, after determining the additional allocation control, when the second station as the additional allocation control does not reach the corresponding floor even if a predetermined time has elapsed, reassigns the second station as the additional allocation control to another single ladder.

8. Elevator arrangement according to claim 2, characterized in that,

the group management control device detects whether or not the landing call is crowded from the completion of opening the door to the completion of closing the door when the registration of the landing call is permitted.