Group management control device for double-deck elevator and group management control method for double-deck elevator

Abstract

The invention provides a group management control device of a double-deck elevator and a group management control method of the double-deck elevator, which can execute distribution processing of a passenger car with high precision for a generated landing call in group management control of the double-deck elevator. According to the embodiment, the group management control device of the double-deck elevator is provided with a mistaken riding judgment part and an allocated lift car determination part. When information of a landing call with a designated destination floor is registered through operation of a user, and the destination floor of the landing call is the uppermost floor or the lowermost floor of service object floors of a plurality of double-deck elevators, the mistaken riding judgment part judges whether the elevator car can stop at the destination floor or not for each elevator car which can stop at the destination floor. When the landing call is assigned, it is determined whether or not there is a possibility that a user has entered another car of the same number as the assigned car by mistake. The assigned car determination unit assigns to the landing call any car other than the car determined to be likely to cause the erroneous riding.

Description

Technical Field

[0001] Embodiments of the present invention relate to a group management control device for double-deck elevators and a group management control method for double-deck elevators. Background Art

[0002] A system that centrally controls multiple elevators is called an elevator group management control system. In particular, a group management control system in which each elevator is composed of a double-deck elevator connecting an upper car and a lower car is called a double-deck group management control system.

[0003] In an elevator group management control system, when a user performs a registration operation for a landing call, a distribution process is performed to determine the passenger car (assigned car) that responds to the landing call so as to be able to transport the user most effectively. Summary of the Invention

[0004] In the case of performing a distribution process for a landing call related to a double-deck elevator, the upper car and the lower car are distinguished for processing. On the other hand, in the case of performing a call registration at a landing by inputting a destination floor by a landing destination floor registration device, the landing destination floor registration device displays an assigned car number to the user who has input the destination floor, but does not notify whether the assigned car number is for the upper car or the lower car.

[0005] When a call is registered using a landing destination floor registration device, when the assigned car responds at the departure floor, a call to the destination floor is automatically registered. Therefore, the user does not operate the destination floor call button in the car. Or, in such an elevator, sometimes there is no destination floor call button provided in the car.

[0006] At the landing on the floor where the user has performed a landing call operation, if another car of the same car number stops and opens the door earlier than the passenger car assigned to the user, it is considered that the user may accidentally board the opened passenger car. If a user who has input a destination floor to the landing destination floor registration device accidentally boards the opened car, since a call to the destination floor is not automatically registered in the accidentally boarded car, the user cannot get off at the destination floor.

[0007] To avoid such a situation, it is only necessary to perform the following distribution change, that is, when another car of the same car number arrives and opens the door earlier in the same direction as the registered call, change the assigned car to the car that arrives first.

[0008] On the other hand, in a double-deck elevator, there are floors such as the uppermost floor that can only be served by the upper car or floors such as the lowermost floor that can only be served by the lower car. Therefore, depending on the user, sometimes the destination floor can only be reached by either the upper car or the lower car. For such users, when the other car of the same elevator that has been assigned to the car arrives first and opens its doors, the user's call to the destination floor cannot be automatically registered in the car that arrived first, so the assignment of the car that arrived first cannot be changed.

[0009] Therefore, users moving to a destination floor that can only be reached by the upper car or the lower car need to avoid the car that arrives first and wait for the response of the originally assigned car before boarding. However, there is a possibility of accidentally boarding the car that arrives first, and there is a problem that it is difficult to use.

[0010] The present invention has been completed in view of the above circumstances, and its object is to provide a group management control device for a double-deck elevator and a group management control method for a double-deck elevator, which can accurately perform the assignment process of the passenger car for the generated landing calls in the group management control of the double-deck elevator.

[0011] According to an embodiment for achieving the above object, the group management control device for a double-deck elevator includes a misboarding determination unit and an assigned car determination unit. When the information of a landing call designating a destination floor is registered by the operation of a user and the destination floor of the landing call is the uppermost floor or the lowermost floor among the service target floors of multiple double-deck elevators, the misboarding determination unit determines whether there is a possibility of a user misboarding the other car of the same elevator assigned to the landing call for the car that can stop at the destination floor. The assigned car determination unit assigns any car other than the car determined to be likely to cause misboarding to the landing call.

[0012] According to the above configuration, it is possible to provide a group management control device for a double-deck elevator and a group management control method for a double-deck elevator, which can accurately perform the assignment process of the passenger car for the generated landing calls in the group management control of the double-deck elevator. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 is a block diagram of a double-deck group management control system using the group management control device for a double-deck elevator according to the embodiment.

[0014] Figure 2A is a flowchart showing the operation of the assigned car determination process executed by the group management control device for a double-deck elevator according to the embodiment.

[0015] Figure 2B is a flowchart showing the operation of the assigned car determination process executed by the group management control device for a double-deck elevator according to the embodiment.

[0016] Figure 3 This is an explanatory diagram showing a case where, in an elevator controlled by the group management control device of the double-deck elevator according to the embodiment, a temporarily assigned car travels forward relative to a landing call, and the floor difference between the forward floor of the temporarily assigned car and the floor where the landing call is generated is less than a specified value.

[0017] Figure 4 This is an explanatory diagram showing a case where, in an elevator controlled by the group management control device of the double-deck elevator according to the embodiment, a temporarily assigned car travels backward relative to a landing call, and another car of the same machine number travels forward.

[0018] Figure 5 This is an explanatory diagram showing a case where, in an elevator controlled by the group management control device of the double-deck elevator according to the embodiment, a temporarily assigned car and another car of the same machine number travel backward relative to a landing call.

[0019] Figure 6 This is an explanatory diagram showing a case where, in an elevator controlled by the group management control device of the double-deck elevator according to the embodiment, a temporarily assigned car travels in the reverse direction relative to a landing call, another car of the same machine number does not pass through the floor where the landing call is generated, and the floor difference between the forward floor of another car of the same machine number and the floor where the landing call is generated is less than a specified value. Detailed Embodiment

[0020] When explaining the embodiment of the present invention, the technical content of the elevator system, which is a prerequisite for this embodiment, will be explained.

[0021] A system that centrally controls multiple elevators is called an elevator group management control system. An elevator group management control system having a landing destination floor registration device (HDC; Hall Destination Controller) provided at the landing of an elevator is called a DCS (Destination Control System). The HDC is a device that, when a user inputs a destination floor, displays the elevator number that the user should take. A DCS in which each elevator has a double-deck building structure is called a double-deck DCS.

[0022] When a user performs a landing call operation by inputting a destination floor through the HDC, the elevator number that the user should take is displayed. The user waits in front of the elevator of the displayed elevator number at the landing. After the elevator of the displayed elevator number stops at the floor where the landing call operation is performed, that is, the floor where the landing call is generated, and the door is opened in the direction towards the destination floor, that is, the forward direction, the user takes the elevator. For example, when elevator A is assigned to a user going from the 2nd floor to the 8th floor, after the door of elevator A is opened in the upward direction, the user takes the elevator.

[0023] The double-deck elevator has an upper car and a lower car for each number machine. However, when a user makes a landing call operation, the user is not instructed which of the upper car and the lower car to board. Therefore, among the assigned number machines, the user boards the car that first opens its door in the forward direction at the landing where the landing call is generated. Here, the user can judge the direction in which the elevator travels based on the broadcast at the time of response, the display of the indicator light at the landing, etc.

[0024] In the double-deck DCS, for a newly generated landing call, allocation processing is performed so that not only the number machine but also which of the upper car and the lower car is used to transport the user is included in the dispatch schedule to determine the allocated car. For example, "A number machine upper car" is allocated to the landing call generated by the above-mentioned landing call operation by the user.

[0025] When the user boards the car, there is no need to press the button for the destination floor. Since the information of the destination floor input at the landing is sent to the elevator control device, the car on which the user boards opens its door at the user's destination floor. Therefore, the user can get off at the destination floor without performing any operation even in the car. However, there is also the following DCS: A car call button is provided in the car, and it is configured to be able to get off at the floor operated by this button. In particular, in a DCS (hybrid DCS) provided with a landing call registration device for registering calls in the up and down directions at a part of the floors, it is necessary to provide a car call button in the car.

[0026] In the double-deck DCS, the following situation is considered: Another car of the same number machine as the car assigned to the landing call of the user travels in the same direction as the direction in which the user goes to the destination floor, stops at the landing where the landing call is generated, and opens its door. In this case, it is highly possible that the user mistakes it for the allocated car and boards the car that opens its door. This is because the user is not instructed which of the upper car and the lower car to board, and the upper car and the lower car open their doors at the same landing door, so it is difficult to distinguish between the upper car and the lower car for boarding.

[0027] In addition, when the car stops at the landing and opens its door, basically, the user is notified by the indicator light or the broadcast which direction the car is going up and down. Therefore, even if another car of the same number machine as the car assigned to the landing call arrives first, when the car that travels in the direction opposite to the direction in which the user goes to the destination floor opens its door, the possibility of the user misboarding is low and it will not become a big problem. On the other hand, when another car of the same number machine as the car assigned to the landing call travels in the same direction as the direction in which the user goes to the destination floor and passes the landing where the landing call is generated earlier than the allocated car, the possibility of the user misboarding becomes high and a problem occurs.

[0028] In the case of such a situation, in principle, on the double-layer DCS side, the assignment of calls to the landing is switched from the upper car to the lower car, and the operation schedule is changed so that the lower car provides the service. Such a change in the schedule is called a change in the assignment to the first-arriving car. This idea also holds true even if the upper car and the lower car are swapped.

[0029] Such an assignment change is limited to the hoistways where the departure floor and the destination floor of the user can be served by both the lower car and the upper car. When the destination floor is the top floor, which is the 8th floor in this case, the 8th floor can only be served by the upper car. Therefore, if the lower car responds to the departure floor first and the user accidentally boards it, the user cannot reach the 8th floor. Thus, when inputting a call for boarding at the 2nd floor and alighting at the 8th floor in the HDC, it is necessary not to select the hoistway that has the risk of the lower car passing the 2nd floor before the upper car's response.

[0030] Generally, the floors that can only be served by either the upper car or the lower car are the top floor and the bottom floor. Therefore, the situation where there is a risk of the user accidentally boarding due to the other car of the same hoistway as the car assigned to the landing call passing the landing call generation floor in the same direction as the call is limited to the following cases:

[0031] (1) The direction indicated by the landing call is the upward direction, the destination floor is the top floor, the initially assigned car is the upper car of the specified hoistway, and the lower car of the same hoistway passes the landing call generation floor in the upward direction before the response of the upper car.

[0032] (2) The direction indicated by the landing call is the downward direction, the destination floor is the bottom floor, the initially assigned car is the lower car of the specified hoistway, and the upper car of the same hoistway passes the landing call generation floor in the downward direction before the response of the lower car.

[0033] In the cases of (1) and (2) above, if the direction indicated by the landing call is swapped, it represents the same situation. Therefore, the following explains the case where the direction indicated by the landing call is the upward direction.

[0034] Hereinafter, as an embodiment of the double-layer group management control system, the drawings are used to explain the case of determining whether there is a problem that the other car of the same hoistway as the assigned car arrives first and the user cannot reach the original destination floor in the case of a landing call that may cause the above problem.

[0035] <Configuration of the double-layer group management control system 1 of the group management control device using the embodiment>

[0036] Refer to Figure 1The configuration of the two - layer group management control system 1 of the group management control device using the embodiment will be described. The two - layer group management control system 1 of the embodiment includes multiple two - layer elevators (Elevator 10A of Machine A, Elevator 10B of Machine B, and Elevator 10C of Machine C) installed in a building with m floors, landing destination floor registration devices 20 - 1 to 20 - m installed at the landings of each floor, and a group management control device 30. The two - layer group management control system 1 is constituted by using a destination floor control system (DCS) with landing destination floor registration devices (HDC) 20 - 1 to 20 - m installed on each floor in the building. In this embodiment, the case where there are 3 two - layer elevators installed in the building is described, but it is not limited to this number, and it can also be 2 or 4 or more.

[0037] Elevator 10A of Machine A has an upper car 11A, a lower car 12A, and a control device 13A of Machine A. The control device 13A of Machine A outputs the position information, traveling status information, door opening and closing status information, load status information, car call registration information, etc. of the upper car 11A and the lower car 12A to the group management control device 30 as elevator information. In addition, the control device 13A of Machine A makes Elevator 10A of Machine A respond to the registered floor of the call according to the allocation instruction from the group management control device 30 and opens the corresponding car door.

[0038] Elevator 10B of Machine B and Elevator 10C of Machine C have the same configuration as Elevator 10A of Machine A, so detailed description is omitted.

[0039] The landing destination floor registration devices 20 - 1 to 20 - m are respectively devices for the users at the landings to specify the destination floor and register which of the cars 11A - 11C, 12A - 12C to call. The landing destination floor registration devices 20 - 1 to 20 - m respectively output the identification information of the machine number that the users who have registered the landing call should take.

[0040] Hereinafter, when it is not specified which one of the landing destination floor registration devices 20 - 1 to 20 - m it is, it is denoted as the landing destination floor registration device 20. Similarly, when it is not specified which one of the control devices 13A of Machine A, 13B of Machine B, and 13C of Machine C it is, it is denoted as the control device 13.

[0041] The group management control device 30 performs group management on Elevator 10A of Machine A, Elevator 10B of Machine B, and Elevator 10C of Machine C. The group management control device 30 has a landing call registration section 31, a determination rule storage section 32, an elevator information acquisition section 33, an allocated car determination section 34, an allocation information output section 35, an allocation change section 36, and a misboarding determination section 37.

[0042] The landing call registration unit 31 receives and registers the information of the landing calls obtained from the landing destination floor registration devices 20-1 to 20-m.

[0043] The determination rule storage unit 32 stores the information of a predetermined rule that is preset to determine whether there is a possibility that a user who has registered the landing call will mistakenly board another car of the same number as the assigned car when a predetermined car is assigned to a new landing call.

[0044] The elevator information acquisition unit 33 acquires the elevator information output from each of the control devices 13A, 13B, and 13C.

[0045] For a newly generated landing call and the registered calls, the assigned car determination unit 34 determines the car (assigned car) to be assigned to the newly generated landing call so that users can be transported most effectively as a whole. When determining the assigned car, the assigned car determination unit 34 assigns any car other than the car that is determined by the misboarding determination unit 37 as described later to be likely to cause misboarding to the landing call.

[0046] Based on the information of the assigned car determined by the assigned car determination unit 34, the assignment information output unit 35 outputs an assignment instruction to the control device of the corresponding elevator, and notifies the landing destination floor registration device 20 that has performed the landing call registration operation of the car number information corresponding to the determined assigned car.

[0047] When another car of the same number as the assigned car determined by the assigned car determination unit 34 for a landing call arrives at the landing call generation floor in the same direction as the direction indicated by the landing call and opens its door first, the assignment change unit 36 changes the assigned car for the landing call to the other car of the same number that arrives first, and makes it respond immediately. However, when the destination floor of the landing call is the uppermost or lowermost floor among the service floors of the elevators 10A, 10B, and 10C, the assignment change unit 36 does not change the assigned car for the landing call.

[0048] When the destination floor of the landing call is the uppermost or lowermost floor among the service floors of the elevators 10A, 10B, and 10C, for each car that can stop at the destination floor, the misboarding determination unit 37 determines whether there is a possibility that a user who has registered the landing call will mistakenly board another car of the same number as the assigned car when the car is assigned to the landing call.

[0049] <Operation of the double-deck group management control system 1>

[0050] The operation of the double-deck group management control system 1 will be described. In the following description, the "advance floor" means, when the elevator is in motion, the floor at which deceleration starts and the elevator can stop at the current moment; when the elevator is in deceleration, the floor at which it is determined to stop when deceleration starts; and when the elevator is at a stop, the floor at which it is stopped. In addition, "assigned candidate car" means the car to be assigned in the current assignment process for the generated landing call. However, it is still in the stage before determining the assignment to this car. In addition, "forward direction" means the traveling direction in which the car can respond to the landing call without changing direction, and it holds when the current traveling direction of the car is the same as the direction of the landing call, and when the car stops without a direction, that is, in a state where the next traveling direction is undetermined. In addition, "reverse direction" means the traveling direction in which the car can respond to the landing call when it changes direction once, and it holds when the current traveling direction of the car is different from the direction of the landing call. In addition, "backward direction" means the traveling direction in which the car can respond to the landing call when it changes direction twice, and it holds when the current traveling direction of the car is the same as the direction of the landing call but the car is located at a position past the floor where the landing call is generated.

[0051] Figure 2A 、 Figure 2B It is a flowchart showing the operation of the car assignment determination process executed by the group management control device 30 when the double-deck group management control system 1 is operating.

[0052] When a user inputs the information of the uppermost floor of the service target floor as the destination floor through the landing destination floor registration device 20 on any floor in the building to perform a landing call registration operation, the information of this landing call X is registered in the landing call registration unit 31 of the group management control device 30 ("Yes" in step S1).

[0053] When the information of the landing call X is registered, the car assignment determination unit 34 determines whether the destination floor of the landing call X is the terminal floor, that is, the uppermost or lowermost floor in the service target floors of the elevators 10A, 10B, and 10C (step S2). Here, the car assignment determination unit 34 determines that the destination floor of the landing call X is the uppermost floor in the service target floors. At this moment, the car assignment determination unit 34 identifies all the upper cars 11A, 11B, and 11C that can stop at the uppermost floor as the assigned candidate cars for the landing call X.

[0054] When the car allocation determination unit 34 determines that the destination floor of the landing call X is the top floor (Yes in step S2), the misboarding determination unit 37 starts a loop process of performing misboarding determination processing for each elevator (unit). In the misboarding determination processing, it is determined whether misboarding of a user is likely to occur when the upper car of each unit is temporarily allocated to the landing call X.

[0055] First, as the misboarding determination processing related to elevator 10A of unit A, the misboarding determination unit 37 determines whether misboarding of a user is likely to occur when the upper car 11A is temporarily allocated to the landing call X.

[0056] When elevator 10A of unit A is in the stopped state or decelerating state (Yes in step S3), the misboarding determination unit 37 determines whether the upper car 11A satisfies either one of the two conditions of [Condition 1] and [Condition 2]. [Condition 1] is that the upper car 11A is decelerating, and the forward floor of the other car of the same unit as the upper car 11A that is temporarily allocated as the car, that is, the lower car 12A, is the landing call generation floor where a new landing call operation has been performed. [Condition 2] is that the upper car 11A is in the stopped state and the lower car 12A is not in the state of being unmanned and having an undetermined next traveling direction (step S4). Here, when either condition is satisfied (Yes in step S4), for the upper car 11A, it is determined that misboarding is likely to occur when the landing call X is allocated (step S5).

[0057] In step S4, when neither [Condition 1] nor [Condition 2] is satisfied (No in step S4), after the lower car 12 stops at a floor other than the landing call generation floor, elevator 10A of unit A continues to run until the upper car 11A stops at the landing call generation floor. In this case, it is difficult to imagine that the lower car 12A travels in the direction of the landing call X before the upper car 11A and passes through the landing call generation floor, so the upper car 11A is left as a candidate car for allocation.

[0058] When it is determined in step S3 that elevator 10A of unit A is not in the stopped state or decelerating state (No in step S3), the process proceeds to step S6. In step S6, the misboarding determination unit 37 performs misboarding determination processing using the "dead zone check" method used in normal elevator group management control.

[0059] Hereinafter, "dead zone check" will be described. Generally, in a group management control system, it is often the case that the elevator control device that controls an individual car and the group management control device are different devices. In this case, a time delay occurs from when the group management control device determines the car to be assigned to the landing call until the elevator control device starts to reflect the control based on this determination. In addition, when the group management control device determines the car to be assigned, the information indicating the status of each car (such as the floor ahead, traveling condition, traveling direction, etc.) that it has grasped is the information sent from each elevator control device. However, since the transmission is accompanied by a delay, this information becomes somewhat outdated at the stage of the assignment process.

[0060] Therefore, even if the group management control device assigns a car whose floor ahead is the floor where the landing call is generated and is traveling to the landing call, due to the freshness of the car information and the control delay, sometimes the assigned car will pass the floor where the landing call is generated.

[0061] To address this problem, when the floor difference between the floor ahead of the candidate car for assignment during the assignment process and the floor where the landing call is generated is less than the threshold Th, a measure is taken to reduce the priority of the assignment to this candidate car for assignment. For example, when the threshold Th = 2, in the case where a landing call from the 6th floor to the 8th floor is registered, for a car traveling in the upward direction and whose floor ahead is the 5th floor or the 6th floor, considering the risk of having passed the 6th floor, it is difficult to assign it to this landing call. For a car whose floor ahead is below the 4th floor, it is determined that it can reliably stop at the 6th floor, and thus the assignment can be made as usual.

[0062] In this way, the situation where the assignment to the landing call is controlled because the car whose floor ahead is positive with respect to the floor where the landing call is generated but the floor ahead is too close to the floor where the landing call is generated is likely to pass is called "dead zone check". Dead zone check is also adopted in a normal group management control system. In step S6, the misboarding determination unit 37 applies this dead zone check method to the misboarding determination process.

[0063] The misboarding determination unit 37 determines whether the temporarily assigned upper car 11A travels in the positive direction - that is, the upward direction - with respect to the landing call X, and whether the floor difference between the floor ahead of the upper car 11A and the floor where the landing call is generated is less than the threshold Th1 = 2 (step S6).

[0064] When the upper car 11A travels in the upward direction but the floor difference between the floor ahead of the upper car 11A and the floor where the landing call is generated is less than the threshold Th1 = 2 (Yes in step S6), it is feared that the upper car 11A will not have time to stop and will pass the floor where the landing call is generated, and the lower car 12A will stop at the floor where the landing call is generated.

[0065] Figure 3This is an explanatory diagram showing the relationship between the positions of the upper car 11A and the lower car 12A of Elevator 10A of Machine A and the floor where the landing call X1 is generated when user U1 registers a landing call X1 with the top floor 8 as the destination floor on the 6th floor as an example. In the figure, the △ mark indicates the floor where the landing call is generated, that is, the departure floor of the car when responding to the landing call, and the ○ mark indicates the destination floor of the landing call. When the landing call X1 is registered in the landing call registration unit 31, the upper car 11A and the lower car 12A are moving upward, and the forward floor of the upper car 11A is the 5th floor.

[0066] In the case where the landing call X1 is temporarily assigned to the upper car 11A in this state, since the floor difference "1" between the forward floor "5th floor" of the upper car 11A and the floor where the landing call is generated "6th floor" is less than the threshold Th1 = 2, the upper car 11A does not have time to stop at the 6th floor, and the lower car 12A stops at the 6th floor and opens the door earlier than the upper car 11A, and user U1 may mistakenly board the lower car 12A. In this case, since the lower car 12A in which user U1 boards turns back at the 7th floor, user U1 cannot go to the 8th floor. After that, the upper car 11A stops and opens the door in the order of the 6th floor → the 8th floor, but when the door is opened at the 6th floor, it is after user U1 has boarded the lower car 12A.

[0067] To avoid such a situation from occurring, when the upper car 11A is moving upward but the floor difference between the forward floor of the upper car 11A and the floor where the landing call is generated is less than the threshold Th1 = 2, the misboarding determination unit 37 determines that misboarding may occur when the landing call X1 is assigned to the upper car 11A (step S5).

[0068] When the state in step S6 is not "the temporarily assigned upper car 11A is moving upward and the floor difference between the forward floor of the upper car 11A and the floor where the landing call is generated is less than the threshold Th1 = 2" (the "no" in step S6), the misboarding determination unit 37 determines whether the upper car 11A is moving in the reverse direction with respect to the landing call X1 and the lower car 12A, which is the other car of the same machine number, is moving in the forward direction (step S7).

[0069] In the case of "the upper car 11A is moving in the reverse direction with respect to the landing call X1 and the lower car 12A, which is the other car of the same machine number, is moving in the forward direction" as described above, as Figure 4 shown, it is equivalent to the situation where the forward floor of the upper car 11A has passed the floor where the landing call is generated, but the forward floor of the lower car 12A has not passed the floor where the landing call is generated, and it may be possible to stop in time.

[0070] In this case, the lower car 12A stops at the floor where the floor call is generated and opens its door earlier than the upper car 11A, and there is a possibility that the user U1 may board the wrong car. Therefore, when the upper car 11A travels away from the floor call and the lower car 12A travels in the forward direction (Yes in step S6), the misboarding determination unit 37 determines that there is a possibility of misboarding for the upper car 11A when the floor call X1 is assigned (step S5).

[0071] As Figure 5 shown, when the forward floor of the lower car 12A has also passed the floor where the floor call is generated, since neither the upper car 11A nor the lower car 12A can stop at the 6th floor in time and they have passed the floor where the floor call is generated, it is okay even if the floor call X1 is assigned to the upper car 11A.

[0072] When the condition in step S7 is not "the upper car 11A travels away from the floor call and the lower car 12A travels in the forward direction" (No in step S7), the misboarding determination unit 37 examines the possibility of misboarding when the upper car 11A travels in the reverse direction, that is, the downward direction, with respect to the floor call.

[0073] When the upward floor call X1 is registered and the upper car 11A located above the floor where the floor call is generated and traveling downward is temporarily assigned, since the lower car 12A travels downward and passes the floor where the floor call is generated, the possibility of misboarding by the user U1 is relatively low. However, since it takes time until the control of the call machine assigned to the floor call X1 starts, the lower car 12A may stop at the floor where the floor call is generated and reverse its traveling direction during this period. In this case, the lower car 12A becomes the first to be in the state of opening its door in the upward traveling direction at the floor where the floor call is generated, ahead of the upper car 11A.

[0074] Figure 6 FIG. is a diagram showing the relationship between the positions of the upper car 11A and the lower car 12A and the floor where the floor call X3 is generated when the user U2 performs a registration operation for the floor call X3 in a state where the floor call X2 assigned to the upper car 11A already exists. The floor call X2 is a call whose departure floor of the car at the time of response, that is, the floor where the floor call is generated, is the 7th floor and the destination floor is the 2nd floor. The floor call X3 is a call whose floor where the floor call is generated is the 3rd floor and the destination floor is the 8th floor. When the floor call X3 is registered in the floor call registration unit 31, the upper car 11A and the lower car 12A are traveling downward, and the forward floor of the lower car 12A is the 4th floor.

[0075] When the upper car 11A is assigned to the landing call X3 in this state, before the decision of this assignment, in order to make the upper car 11A respond to the landing call X2, it is determined that the upper car 11A stops at any floor and reverses the traveling direction to the upward direction. Here, if the floor difference between the forward floor of the lower car 12A and the floor where the landing call of the landing call X3 is generated is less than the threshold Th2, the lower car 12A may stop at the floor where the landing call of the landing call X3 is generated and reverse the traveling direction. Specifically, if the floor difference "1" between the forward floor "4th floor" of the lower car 12A and the floor "3rd floor" where the landing call of the landing call X2 is generated is less than the threshold Th2 = 2, the lower car 12A may stop at the 3rd floor and reverse the traveling direction.

[0076] In this case, since the lower car 12A stops at the 3rd floor with the traveling direction reversed to the upward direction, the user U2 may mistakenly board the lower car 12A.

[0077] To avoid such a situation from occurring, when the upper car 11A travels in the reverse direction with respect to the landing call X3, the lower car 12A does not pass through the floor where the landing call is generated, and the floor difference between the forward floor of the lower car 12A and the floor where the landing call is generated is less than the threshold Th2 ( "Yes" in step S8), for the upper car 11A, it is determined that there may be a misboarding when the landing call X3 is assigned (step S5).

[0078] In Figure 6 In this case, when the forward floor of the lower car 12A is the 3rd floor or the 4th floor, and the floor difference "1" from the floor "3rd floor" where the landing call is generated is less than the threshold Th2 = 2, it is determined that there may be a misboarding of the user U2. On the other hand, when the forward floor of the lower car 12A is a floor of 5th floor or above, since the response to the landing call X3 is reflected in the operation schedule before the traveling directions of the upper car 11A and the lower car 12A are reversed, the lower car 12A becomes in a state with the traveling direction downward when it stops at the 3rd floor. Therefore, the possibility of the user U2 mistakenly boarding the lower car 12A is low. In this case, the upper car 11A opens the door at the 3rd floor with the traveling direction upward, and then moves and opens the door in the order of the 8th floor → the 7th floor → the 2nd floor, thereby responding to the landing calls X3 and X2.

[0079] In addition, when the forward floor of the lower car 12A is the 2nd floor or the 1st floor, since the lower car 12A passes through the floor "3rd floor" where the landing call of the landing call X3 is generated with the traveling direction downward, there is no possibility that the lower car 12A travels upward toward the upper direction before the upper car 11A and passes through the 3rd floor, and there is no possibility of the user U2 mistakenly boarding the lower car 12A.

[0080] The misboarding determination unit 37 maintains the determination result of whether misboarding of a user is likely to occur when the upper car 11A is temporarily assigned to the landing call X through the processes of steps S3 to S8. After that, the misboarding determination unit 37 processes steps S3 to S8 in a loop for each car number, and also determines whether misboarding of a user is likely to occur when the upper cars 11B and 11C are temporarily assigned to the landing call X and maintains the determination result.

[0081] When the misboarding determination process for all car numbers is completed, the process proceeds to step S9. The car assignment determination unit 34 determines the assigned car for the landing call X, using as assignment candidates the car numbers other than those determined by the misboarding determination unit 37 to be likely to cause misboarding (step S9). The method for determining the assigned car here uses an existing method. For example, it is also possible to calculate predicted values of the waiting times of users for the newly registered landing call X and the other registered calls respectively, and when adding the newly registered landing call X to the operation schedule of a specified car, assign the car that minimizes the total increase in the waiting times of all car numbers to the landing call X.

[0082] The assignment information output unit 35 notifies the landing destination floor registration device 20 that has performed the landing call registration operation of the information of the car number corresponding to the assigned car determined by the car assignment determination unit 34. The landing destination floor registration device 20 that has received the information of the car number notifies the user of the car number to be boarded by outputting the received information.

[0083] In addition, the assignment information output unit 35 outputs an assignment instruction for the landing call X to the control device 13 corresponding to the information of the assigned car determined by the car assignment determination unit 34. The control device 13 that has received the assignment instruction performs control so that the corresponding car stops at the landing call generation floor of the landing call X and then moves to the destination floor.

[0084] In step S2, when the car assignment determination unit 34 determines that the destination floor of the landing call X is not the terminal floor (No in step S2), it determines the assigned car from the upper car 11A, the upper car 11B, and the upper car 11C, which are the assignment candidate cars for the landing call X (step S9).

[0085] As described above, when performing the assignment process, when the assignment change unit 36 detects that another car of the same car number as the assigned car for the landing call determined by the car assignment determination unit 34 arrives at the landing call generation floor in the same direction as the direction indicated by the landing call and opens the door first, it changes the assigned car for the landing call to the other car of the same car number that arrives first and makes it respond immediately. However, the assignment change unit 36 does not change the assigned car for the landing call when the destination floor of the landing call is the uppermost or lowermost floor among the service floors of the elevators 10A, 10B, and 10C.

[0086] According to the above-described embodiment, in the group management control of a double-deck elevator, when determining the car to be assigned for a newly registered landing call to the terminal floor, it is possible to determine the car to be assigned by avoiding the risk of another car with the same machine number passing by first. Thus, it is possible to prevent a situation where a user mistakenly boards a car different from the assigned car and cannot get off at the destination floor. In particular, in the present embodiment, by using the idea of dead zone inspection that takes into account the freshness of information in the group management control device and the time delay until the allocation information for the landing call is reflected in the control, it is possible to determine the possibility of a misboarding with higher accuracy.

[0087] Several embodiments of the present invention have been described. These embodiments are presented as examples and are not intended to limit the scope of the invention. These new embodiments can be implemented in various other ways, and various omissions, substitutions, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are included in the invention described in the claims and the scope equivalent thereto.

Claims

1. A group management control device for group management of a plurality of double-deck elevators consisting of a plurality of upper and lower elevator cars, comprising: A landing call registration section registers information on landing calls with designated destination floors; a wrong ride determination unit for determining, when information of a new landing call is registered in the landing call registration unit by an operation of a user and a destination floor of the new landing call is the uppermost floor or the lowermost floor among service target floors of the plurality of double-deck elevators, whether or not there is a possibility that the user will board another car of the same car number as the car to which the new landing call is assigned, if each of the plurality of cars of the plurality of double-deck elevators that can stop at the destination floor is assigned to the new landing call; and The assigned car determining unit assigns any one of the plurality of cars of the plurality of double-deck elevators, other than the car determined by the wrong boarding determining unit as having a possibility of causing the wrong boarding, to the new landing call.

2. The group management control device according to claim 1, wherein: When the above-mentioned wrong ride determination unit registers the information of the above-mentioned new floor station call in the above-mentioned floor station call registration unit through the operation of the above-mentioned user, and the above-mentioned destination floor associated with the above-mentioned new floor station call is the above-mentioned uppermost floor or the above-mentioned lowermost floor among the above-mentioned service object floors of the above-mentioned multiple double-deck elevators, for the above-mentioned multiple cars of the above-mentioned multiple double-deck elevators that can stop at the above-mentioned destination floor and satisfy any one of the first condition and the second condition, it is determined that the above-mentioned wrong ride may occur when assigned to the above-mentioned new floor station call, the above-mentioned first condition being that when the car is decelerating, the floor at which the other car of the same car decides to stop when starting to decelerate is the floor at which the above-mentioned new floor station call operation was performed, and the above-mentioned second condition is that when the car is stopping, the other car of the same car is not in a state where no one is present and the next direction of travel is undetermined.

3. The group management control device according to claim 1, wherein: When the above-mentioned wrong ride determination unit registers the information of the above-mentioned new floor station call in the above-mentioned floor station call registration unit through the operation of the above-mentioned user, and the above-mentioned destination floor associated with the above-mentioned new floor station call is the above-mentioned uppermost floor or the above-mentioned lowermost floor among the above-mentioned service object floors of the above-mentioned multiple double-deck elevators, for the above-mentioned multiple cars of the above-mentioned multiple double-deck elevators that can stop at the above-mentioned destination floor, and the car that travels in the same direction as the direction from the floor station call generation floor where the above-mentioned new floor station call operation is performed toward the above-mentioned destination floor, and the floor difference between the floor that can stop when starting to decelerate at the current moment and the floor station call generation floor is less than a specified value, it is determined that the above-mentioned wrong ride is likely to occur when assigned to the above-mentioned new floor station call.

4. The group management control device according to claim 1, wherein: When the above-mentioned wrong ride determination unit registers the information of the above-mentioned new floor call in the above-mentioned floor call registration unit through the operation of the above-mentioned user, and the above-mentioned destination floor associated with the above-mentioned new floor call is the above-mentioned uppermost floor or the above-mentioned lowermost floor among the above-mentioned service object floors of the above-mentioned multiple double-deck elevators, for the above-mentioned multiple cars of the above-mentioned multiple double-deck elevators that can stop at the above-mentioned destination floor, for a car that is located in a position that has passed the above-mentioned floor call generation floor by traveling in the same direction as the direction from the floor call generation floor where the above-mentioned new floor call operation was performed toward the above-mentioned destination floor where the above-mentioned new floor call was performed, but another car of the same car is located in a position that has not passed the above-mentioned floor call generation floor, it is determined that the above-mentioned wrong ride may occur if assigned to the above-mentioned new floor call.

5. The group management control device according to claim 1, wherein: When the above-mentioned wrong ride determination unit registers the information of the above-mentioned new floor call in the above-mentioned floor call registration unit through the operation of the above-mentioned user, and the above-mentioned destination floor associated with the above-mentioned new floor call is the uppermost floor or the lowermost floor among the above-mentioned service object floors of the above-mentioned multiple double-deck elevators, for a car among the above-mentioned multiple cars of the above-mentioned multiple double-deck elevators that can stop at the above-mentioned destination floor, a car that travels in a direction opposite to the direction from the floor where the above-mentioned new floor call operation is performed toward the above-mentioned destination floor of the above-mentioned new floor call, and another car of the same car has not passed the above-mentioned floor where the call is generated, but the floor at which the other car of the same car can stop when starting to decelerate at the current moment and the floor where the floor call is generated have a floor difference less than a specified value, it is determined that the above-mentioned wrong ride may occur if assigned to the above-mentioned new floor call.

6. A group management control method, comprising: a group management control device having a landing call registration unit for registering information of a landing call specifying a destination floor, for group management of a plurality of double-deck elevators consisting of a plurality of upper and lower cages, comprising: When information of a new landing call is registered in the landing call registration unit by an operation of the user, and the destination floor of the new landing call is the uppermost floor or the lowermost floor among the service target floors of the plurality of double-deck elevators, for each of the plurality of cars of the plurality of double-deck elevators that can stop at the destination floor, determining whether there is a possibility that the user may mistakenly board another car of the same car number as the car to which the new landing call is assigned if the new landing call is assigned; and Any one of the cars of the plurality of double-deck elevators other than the car determined to be likely to cause the wrong ride is allocated to the new landing call.

Images