Elevator control device and control method

Abstract

To improve both transportation efficiency and convenience in an elevator. [Solution] The control device is a control device that assigns hall calls to cars in an elevator, and has the following configuration. The control device designates the end floor located in the direction of travel of the car as the first end floor, and the end floor opposite that as the second end floor, and sets a section from the current floor of the car to the first end floor and a section from the first end floor to the second end floor in the order that the car passes through. Then, each time it assigns a hall call to a car, it counts the scheduled number of new stops that the car will have to make as a result of that assignment as the scheduled number of stops of the car in the section where the hall call will be answered. Then, when the scheduled number of stops in each section reaches an upper limit, the control device limits the assignment of hall calls to cars that require stops in that section.

Description

[Technical Field]

[0001] The present invention relates to a control technology for improving the transport efficiency and convenience of elevators. [Background technology]

[0002] Some elevators assign hall calls to a car for a user each time the user registers a destination floor in a destination floor registration device. A known control technology for such elevators counts the number of scheduled stops (the number of scheduled stops per revolution when traveling around a route) that occur in a car due to the allocation of hall calls, and limits the allocation for cars whose scheduled number of stops has reached an upper limit (see, for example, Patent Document 1). This technology makes it possible to limit the number of stops per revolution of the car. This makes it possible to control the revolution time of the car (the time required to make one revolution around a route), so that it does not become too long, thereby improving transportation efficiency. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 5919898 Summary of the Invention [Problem to be solved by the invention]

[0004] However, while the above-mentioned technology can limit the number of stops the car makes per revolution, there can be a difference in the number of stops during that revolution depending on whether the car is traveling upward or downward, which can lead to a situation where the number of stops is heavily biased in one direction. When this happens, for users traveling in one direction, the number of stops becomes disproportionately greater, which can increase the time required for travel, and as a result, there is a risk of reduced convenience.

[0005] SUMMARY OF THE INVENTION It is therefore an object of the present invention to improve both the transport efficiency and convenience of elevators. [Means for solving the problem]

[0006] The control device according to the present invention is a control device that allocates hall calls to cars in an elevator, and has the following configuration (Aspect 1). The control device defines the end floor located in the direction of travel of the car as the first end floor, and the end floor opposite that as the second end floor, and sets a section from the current floor of the car to the first end floor and a section from the first end floor to the second end floor in the order that the car passes through. Then, each time the control device allocates hall calls to a car, it counts the scheduled number of new stops that the car will make as a result of the allocation as the scheduled number of stops of the car in the section where the hall calls will be answered. Then, when the scheduled number of stops in each section reaches an upper limit, the control device limits the allocation of hall calls to cars that require stops in that section.

[0007] According to the above-mentioned aspect 1, it is possible to limit the number of scheduled stops in each section, and as a result, it is possible to control the number of stops per revolution while the car travels around the operating section so that the number of stops is not significantly biased towards either the upward or downward direction of travel. Therefore, it is possible to achieve both improved transport efficiency obtained by limiting the number of stops per revolution in an elevator and improved convenience obtained by suppressing the bias in the number of stops.

[0008] The control device according to the above-mentioned aspect 1 may have the following configuration (aspect 2): The control device may further set a section from the second terminal floor to the first terminal floor according to the order in which the car passes, and then, each time it assigns hall calls to a car, it may count the scheduled number of times that the car will newly stop as a result of the assignment as the scheduled number of times that the car will stop in the section in which the hall calls are answered.

[0009] According to the above-mentioned aspect 2, even immediately after the elevator car turns around at or before the first terminal floor (immediately after passing the section from the current floor to the first terminal floor), it is possible to create a situation in which the number of stops during one rotation from there is already controlled so that the number of stops is not significantly biased towards either when the direction of travel is upward or downward.

[0010] The control device according to the above-mentioned aspect 1 or 2 may have the following configuration (aspect 3): In the section from the current floor to the first terminal floor, the control device may update the value of the number of scheduled stops in that section to a value obtained by subtracting one from the value of the number of scheduled stops in that section each time the elevator car arrives at a scheduled stop floor in that section.

[0011] According to the above-mentioned aspect 3, there is room to further increase the number of floors at which the train is scheduled to stop in the section from the current floor to the first terminal floor, which results in further improvement of transportation efficiency while improving convenience.

[0012] The control device according to any one of the above aspects 1 to 3 may have the following configuration (Aspect 4): When the elevator car reverses its direction of travel at the first terminal floor or a floor immediately before it, the control device may set the floor as the current floor, the second terminal floor as the new first terminal floor, and the first terminal floor as the new second terminal floor, and may reset the section.

[0013] According to the above-mentioned aspect 4, by resetting the section every time the car turns around, it is possible to continue to control so that the number of stops is not greatly biased.

[0014] A control method according to the present invention is a control method for allocating hall calls to cars in an elevator, and has the following configuration (Aspect 5). In this control method, the end floor located in the direction of travel of the car is designated as the first end floor, and the end floor opposite thereto is designated as the second end floor. In this control method, a section from the current floor of the car to the first end floor and a section from the first end floor to the second end floor are set according to the order in which the car passes. Then, each time a hall call is allocated to a car, the scheduled number of new stops that the car will make as a result of the allocation is counted as the scheduled number of stops of the car in the section in which the hall call is answered. Then, for each section, when the scheduled number of stops in that section reaches an upper limit, the allocation of hall calls that require stops in that section to the car is limited. [Effects of the Invention]

[0015] According to the present invention, it is possible to improve both the transport efficiency and convenience of an elevator. [Brief explanation of the drawings]

[0016] [Figure 1] 1 is a conceptual diagram showing the overall configuration of an elevator according to an embodiment. [Figure 2] 1A to 1D are conceptual diagrams illustrating (A) device management data, (B) car management data, (C) hall call management data, and (D) car call management data used in an embodiment. [Figure 3] (A) A conceptual diagram visualizing an example of information on platform calls and car calls in section W1 and an example of counting the number of scheduled stops Ns(W1), and (B) a conceptual diagram visualizing an example of information on platform calls in section W2 and an example of counting the number of scheduled stops Ns(W2). [Figure 4] 10 is a flowchart illustrating an allocation process executed in the embodiment. [Figure 5] 10 is a flowchart showing a part of a selection process executed in the embodiment. [Figure 6] 6 is a flowchart showing a part of the selection process continued from FIG. 5. [Figure 7] 10A and 10B are conceptual diagrams illustrating car management data and hall call management data used in a first modified example. [Figure 8] FIG. 10 is a conceptual diagram visualizing an example of information about hall calls in section W3 and an example of counting the number of scheduled stops Ns(W3). [Figure 9] 10 is a flowchart showing a part of a selection process executed in a first modified example. [Figure 10] 10A and 10B are conceptual diagrams each showing a visualized example of counting the planned number of stops Ns(W1) and the planned number of stops Ns(W2) in a second modified example. DETAILED DESCRIPTION OF THE INVENTION

[0017] [1] Implementation [1-1] Overall structure of the elevator FIG. 1 is a conceptual diagram showing the overall configuration of an elevator according to an embodiment. In this embodiment, a destination floor registration device 1 is installed on each floor of the elevator, and when a user uses the elevator, the user must register their destination floor Fd in advance with the destination floor registration device 1 installed on the floor where the user boards the elevator. This elevator also has multiple cars G, and further includes a group management control device 2 that manages them in an integrated manner. The configuration of each part will be specifically described below.

[0018] <Destination floor registration device> The destination floor registration device 1 is provided with a device, such as a touch panel, that functions as both an input unit and a display unit, and the user registers the destination floor Fd and is notified of various information through this device. The destination floor registration device 1 may be provided with an input unit and a display unit separately. For example, mechanical buttons (such as a numeric keypad) may be provided as the input unit, and a monitor dedicated to display may be provided as the display unit.

[0019] When a user operates a destination floor registration device 1 at any floor to register their own destination floor Fd, that destination floor Fd is transmitted to the group management control device 2. As a result, a request for allocation of a hall call X for that user is made to the group management control device 2. At this time, device information Pd for distinguishing the destination floor registration device 1 from other registration devices is also transmitted to the group management control device 2 so that the group management control device 2 can recognize which registration device is the operated destination floor registration device 1.

[0020] <Group management control device> The group management control device 2 centrally controls a plurality of cars G equipped in the elevator of this embodiment through an elevator control device provided for each car G (see FIG. 1).

[0021] Specifically, each time the group management control device 2 receives an allocation request from any of the destination floor registration devices 1, it treats the departure floor Fc and destination floor Fd of the user registered with that destination floor registration device 1 as one hall call X, selects an allocation destination for that hall call X from among multiple cars G, and then allocates the hall call X to that allocation destination (allocation process).The group management control device 2 then causes the car G to execute a response operation to the hall call X (response process).

[0022] Furthermore, when responding to a hall call X, the group management control device 2 registers the destination floor Fd indicated by the hall call X as a car call Y for the user for the car G at an appropriate timing after the car G arrives at the departure floor Fc indicated by the hall call X (for example, at the timing when the doors start opening or when a sensor in the door detects that the user has boarded), (registration processing). Then, the group management control device 2 causes the car G to execute a response operation to the car call Y (response processing).

[0023] In this embodiment, the group management control device 2 performs such control processing (processing for centrally managing a plurality of cars G) and also performs allocation processing to enable both improvement of transportation efficiency and improvement of convenience. Details of this allocation processing will be described later.

[0024] Specifically, the group management control device 2 includes a storage unit 21 and a control unit 22 (see FIG. 1).

[0025] The memory unit 21 is a part configured with storage devices such as ROM and RAM, and stores information necessary for the control processing performed by the group management control device 2. In this embodiment, the memory unit 21 stores such information as device management data Dp, car management data Dq, hall call management data Dx, and car call management data Dy.

[0026] Here, the device management data Dp is a database for managing, for each destination floor registration device 1, a plurality of pieces of information related to that registration device by linking them together (see FIG. 2(A)). The car management data Dq is a database for managing, for each car G, a plurality of pieces of information related to that car G by linking them together (see FIG. 2(B)). The hall call management data Dx and the car call management data Dy are data for managing, for each car G, the information on hall calls X and car calls Y for users, respectively (see FIG. 2(C) and FIG. 2(D)).

[0027] 2A is a conceptual diagram illustrating the device management data Dp used in this embodiment. In the device management data Dp, for each destination floor registration device 1, the device information Pd of the registration device and the installation floor Fs are recorded in a mutually associated state.

[0028] As a result, when the group management control device 2 receives device information Pd together with the destination floor Fd from any of the destination floor registration devices 1, it becomes possible to identify the floor Fs where the destination floor registration device 1 (the registration device where the destination floor Fd is registered) is installed from the device information Pd. In this embodiment, the floor Fs where the destination floor registration device 1 is installed is used as the departure floor Fc (boarding floor) of the user who operated the registration device to register the destination floor Fd.

[0029] 2(B) is a conceptual diagram illustrating the car management data Dq used in this embodiment. In the car management data Dq, for each car G, car information Pg for distinguishing the car G from other cars, the current floor Fg and current direction Kg of the car G, and the expected number of stops Ns(W) for each section W generated by the allocation of the hall call X to the car G are recorded in a mutually associated state.

[0030] Here, the current floor Fg is the floor where the car G is currently stopped, or if the car G is currently moving, the nearest floor where the car G can stop if it is determined to decelerate at that time. The current direction Kg is the current direction of travel of the car G. These pieces of information (current floor Fg and current direction Kg) are updated each time the car G moves.

[0031] The section W includes a plurality of sections Wn (n is an index for distinguishing between different sections W) set for each car G (see Figures 3(A) and 3(B)). In this embodiment, for each car G, the terminal floor located in the direction of travel of that car G is designated as the first terminal floor Fe1, and the terminal floor on the opposite side is designated as the second terminal floor Fe2. Furthermore, as a plurality of sections Wn, a section W1 (n=1, see Figure 3(A)) from the current floor Fg of that car G to the first terminal floor Fe1, and a section W2 (n=2, see Figure 3(B)) from the first terminal floor Fe1 to the second terminal floor Fe2 are set in the order that the car G passes through.

[0032] The scheduled number of stops Ns (W = Wn) is the count of the scheduled number of stops of the car G in the section Wn. In this embodiment, the scheduled number of stops Ns (W = Wn) includes both the scheduled number of stops of the car G at the departure floor Fc and the scheduled number of stops of the car G at the destination floor Fd, and stops at the same floor are combined into one. Therefore, in this embodiment, the scheduled number of stops Ns (Wn) in each section Wn coincides with the number of floors (scheduled stop floors) at which the car G is scheduled to stop in that section Wn (see Figures 3(A) and 3(B)). The value of the scheduled number of stops Ns (W = Wn) recorded for each car G in the car management data Dq is updated each time allocation to the car G is performed (see steps S111 to S112 in Figure 4).

[0033] 2(C) is a conceptual diagram illustrating the hall call management data Dx used in this embodiment. In the hall call management data Dx, for each car G identified by the car information Pg, information on the hall call X assigned to that car G (departure floor Fc and destination floor Fd) is recorded, and further, the information on each hall call X is recorded after being allocated to the section Wn in which the car G responds to that hall call X. Then, when that hall call X has completed its role (when the destination floor Fd indicated by that hall call X is registered as a car call Y), the information on each hall call X is deleted from the hall call management data Dx (deletion of the hall call X).

[0034] 2(C) shows a specific example of information on hall calls X (departure floor Fc and destination floor Fd) for each section Wn recorded in the hall call management data Dx for car G whose car information Pg is "G-01." In addition, in FIGS. 3(A) and 3(B), for each hall call X for each section Wn, the departure floor Fc is shown as a black circle, the destination floor Fd is shown as a white circle, and the direction from the departure floor Fc to the destination floor Fd is shown as an arrow (arrow pointing from the black circle to the white circle), thereby visualizing the information on each hall call X.

[0035] 2(D) is a conceptual diagram illustrating the car call management data Dy used in this embodiment. In the car call management data Dy, for each car G identified by the car information Pg, information on car calls Y (destination floor Fd) that have been registered in the car G by stopping in section W1 is recorded. Then, when the car call Y has completed its role (when the car G arrives at the destination floor Fd indicated by the car call Y), the information on each car call Y is deleted from the car call management data Dy (deletion of the car call Y).

[0036] Fig. 2(D) shows a specific example of information about car call Y (destination floor Fd) recorded in the car call management data Dy for car G, whose car information Pg is "G-01." In Fig. 3(A), the destination floor Fd for that car call Y is shown with a double circle, thereby visualizing the information about that car call Y.

[0037] In this embodiment, in order to achieve both improved transport efficiency and improved convenience, the number of scheduled stops Ns (W=Wn) is limited in each section W (=Wn). Specifically, to enable such a limitation, an upper limit value Nt is set for the number of scheduled stops Ns (Wn) for each section Wn. In this embodiment, the upper limit value Nt is set to the same value (for example, Nt=6 times) for all sections Wn and all cars G, and the upper limit value Nt is stored in the memory unit 21. Note that the upper limit value Nt may be set to a different value for each section Wn, or may be set to a different value for each car G, as appropriate.

[0038] Furthermore, in the section W1, each time the car G arrives at a scheduled stop floor in the section W1 (departure floor Fc or destination floor Fd), the value of the scheduled number of stops Ns(W1) in that section W1 is updated to a value obtained by subtracting one from the value. By updating the value of the scheduled number of stops Ns(W1) in the section W1 in this way, there is room to further increase the scheduled stop floors in the section W1, which results in further improving the convenience of the elevator and transportation efficiency. Note that the value of the scheduled number of stops Ns(W1) in the section W1 may be maintained, including floors that have already been stopped, without being updated, even when the car G arrives at a scheduled stop floor.

[0039] Furthermore, in the car management data Dq, if the car G reverses its direction of travel at the first terminal floor Fe1 or a floor just before it, that floor is set as the current floor Fg, the second terminal floor Fe2 is set as the new first terminal floor Fe1, and the first terminal floor Fe1 is set as the new second terminal floor Fe2, and all sections Wn are reset. At this time, the planned number of stops Ns(W2) in the section W2 before being reset is carried over to the planned number of stops Ns(W1) in the new reset section W1. Meanwhile, the planned number of stops Ns(W2) in the new reset section W2 is reset to Ns(W2)=0.

[0040] The control unit 22 is a part that is responsible for executing the control processes (including allocation processes, registration processes, and response processes) performed by the group management control device 2. Specifically, the control unit 22 is made up of processing devices such as a CPU or MPU, and executes a control program installed in the group management control device 2 to realize the execution of its own control processes in software. Note that, before being installed in the group management control device 2, this control program may be stored in a readable state on a portable storage medium (for example, a flash memory, etc.), or may be stored in a downloadable state on a server, etc. Furthermore, the control processes performed by the group management control device 2 are not limited to being realized in software by executing a program, but may also be realized in hardware by a processing circuit built into the group management control device 2.

[0041] [1-2] Control processing performed by the group management control device <Allocation process> 4 is a flowchart showing the allocation process executed in this embodiment. This allocation process is started each time the group management control device 2 receives an allocation request from one of the destination floor registration devices 1. Hereinafter, a user who has registered with that destination floor registration device 1 will be referred to as a "target user." Furthermore, the information received by the group management control device 2 each time an allocation request is received (destination floor Fd and device information Pd) will be collectively referred to as "received information Pr."

[0042] When the allocation process starts, the group management control device 2 first determines the hall call X of the target user to which allocation should be performed (step S101). Specifically, the group management control device 2 uses the device management data Dp to find device information Pd recorded therein that matches the device information Pd in ​​the received information Pr, and then extracts the installation floor Fs associated with it. The group management control device 2 then sets the extracted installation floor Fs as the departure floor Fc of the target user, and determines that departure floor Fc (= installation floor Fs) and the destination floor Fd in the received information Pr (destination floor Fd of the target user) as one hall call X for the target user. Hereinafter, this hall call X of the target user will be referred to as the "target call Xk."

[0043] After step S101, the group management control device 2 executes a selection process for selecting allocation candidates for the target call Xk for each of all the cars G (step S102). Specifically, the process is as follows.

[0044] <Sorting process> 5 and 6 are flowcharts showing the sorting process executed in this embodiment. This sorting process is executed for each of all the cars G. Specifically, the group management control device 2 focuses on all of the car information Pg recorded in the car management data Dq one by one, and each time it focuses on one of the car information Pg, it executes the sorting process for the car G identified by that car information Pg (hereinafter referred to as the "car of interest Gk").

[0045] In the selection process, the group management control device 2 first acquires information about a target car Gk (step S201). Specifically, the group management control device 2 uses the car management data Dq to acquire the car information Pg of the target car Gk, and the current floor Fg, current direction Kg, and the scheduled number of stops Ns(Wn) for each section Wn associated therewith.

[0046] Next, the group management control device 2 uses the current floor Fg and current direction Kg of the target car Gk acquired in step S201 to identify the current sections W1 and W2 set for the target car Gk (step S202). Specifically, the group management control device 2 designates the end floor located in the current direction Kg (current traveling direction) of the target car Gk as the first end floor Fe1, and the end floor on the opposite side as the second end floor Fe2, and then, in accordance with the order in which the target car Gk passes, identifies the section W from the current floor Fg of the target car Gk to the first end floor Fe1 as the section W1 (see FIG. 3(A)), and identifies the section W from the first end floor Fe1 to the second end floor Fe2 as the section W2 (see FIG. 3(B)).

[0047] After step S202, assuming that the target call Xk has been assigned to the target car Gk, the group management control device 2 determines in which section Wn the target car Gk can respond to the target call Xk (step S203).

[0048] Specifically, if the condition [J1] is satisfied that the departure floor Fc and destination floor Fd indicated by the target call Xk are both within section W1 and the direction from the departure floor Fc to the destination floor Fd matches the direction of travel of the target car Gk in section W1 (the direction from the current floor Fg to the first terminal floor Fe1), the group management control device 2 determines that the relevant section Wg (section Wn (n = g) in which the target car Gk can respond to the target call Xk) is "section W1" (see Figure 3(A)). Furthermore, the group management control device 2 determines that the relevant section Wg is "section W2" if the condition [J2] is satisfied that the departure floor Fc and destination floor Fd indicated by the target call Xk are both within section W2 and the direction from the departure floor Fc to the destination floor Fd matches the traveling direction of the target car Gk in section W2 (the direction from the first terminal floor Fe1 to the second terminal floor Fe2) (see Figure 3(B)). On the other hand, if neither the conditions [J1] nor [J2] are satisfied for the departure floor Fc and destination floor Fd indicated by the target call Xk, the group management control device 2 determines that the relevant section Wg is "not present."

[0049] If the group management control device 2 determines in step S203 that the relevant section Wg is "section W1" or "section W2," it proceeds to the next step S211 (see FIG. 6). On the other hand, if the group management control device 2 determines in step S203 that the relevant section Wg "does not exist," it ends the selection process for the target car Gk without adding the target car Gk to the allocation candidates.

[0050] In step S211, the group management control device 2 determines whether there is a floor (departure floor Fc or destination floor Fd; see Figures 3(A) and 3(B)) at which the target car Gk is scheduled to stop in the relevant section Wg that is the same as the ``departure floor Fc'' indicated by the target call Xk.

[0051] If the group management control device 2 determines "Yes" in step S211, it can determine that the value of the planned number of stops Ns(Wg) in the relevant section Wg among the planned number of stops Ns(Wn) acquired in step S201 has already counted the number of stops at the departure floor Fc indicated by the target call Xk. In this case, the group management control device 2 leaves the value of the planned number of stops Ns(Wg) as it is without performing a new count (step S212A), and proceeds to the next step S213.

[0052] On the other hand, if the group management control device 2 determines "No" in step S211, it can determine that the value of the scheduled number of stops Ns(Wg) has not yet counted the number of stops at the departure floor Fc indicated by the target call Xk. In this case, the group management control device 2 determines whether the value of the scheduled number of stops Ns(Wg) is smaller than the upper limit value Nt for the corresponding section Wg (step S211X) in order to determine whether or not it is possible to allow the target call Xk to be assigned to the target car Gk (in other words, whether or not the target car Gk is likely to be an assignment candidate).

[0053] If the group management control device 2 determines "small (Yes)" in step S211X, it can determine that the value of the planned number of stops Ns(Wg) has not reached the upper limit value Nt, and therefore that there is a possibility that allocation of the target call Xk to the target car Gk is acceptable. In this case, the group management control device 2 counts the number of stops at the departure floor Fc indicated by the target call Xk (=1 stop; the planned number of new stops that the target car Gk will make as a result of the allocation of the target call Xk) as the planned number of stops Ns(Wg) (step S212B), and then proceeds to the next step S213.

[0054] On the other hand, if the group management control device 2 determines "not small (Yes)" in step S211X, it can determine that the value of the scheduled number of stops Ns(Wg) has reached the upper limit Nt, and therefore it can determine that it is not possible to allow the target call Xk to be assigned to the target car Gk. In this case, the group management control device 2 terminates the selection process for the target car Gk without adding the target car Gk to the assignment candidates so as not to execute the assignment to the target car Gk. In this way, the assignment of the target call Xk to the target car Gk (in other words, the assignment of the hall call X that requires a stop in the relevant section Wg to the target car Gk) is limited, and the scheduled number of stops Ns(Wg) of the target car Gk in the relevant section Wg is controlled so as not to exceed the upper limit Nt.

[0055] In step S213, the group management control device 2 determines whether there is a floor (departure floor Fc or destination floor Fd; see Figures 3(A) and 3(B)) at which the target car Gk is scheduled to stop in the relevant section Wg that is the same as the ``destination floor Fd'' indicated by the target call Xk.

[0056] If the group management control device 2 determines "Yes" in step S213, it can determine that the value of the scheduled number of stops Ns(Wg) obtained via step S212A or S212B has already counted the number of stops at the destination floor Fd indicated by the target call Xk. In this case, the group management control device 2 leaves the value of the scheduled number of stops Ns(Wg) as it is without performing a new count (step S214A), and adds the target car Gk to the allocation candidates for the target call Xk (step S215). Thereafter, the group management control device 2 ends the selection process for the target car Gk.

[0057] On the other hand, if the group management control device 2 determines "No" in step S213, it can determine that the value of the scheduled number of stops Ns(Wg) has not yet counted the number of stops at the destination floor Fd indicated by the target call Xk. In this case, the group management control device 2 determines whether the value of the scheduled number of stops Ns(Wg) is smaller than the upper limit value Nt for the corresponding section Wg (step S213X) to determine whether or not the target call Xk can be allocated to the target car Gk (in other words, whether or not the target car Gk is a candidate for allocation).

[0058] If the group management control device 2 determines "small (Yes)" in step S213X, it can determine that the value of the scheduled number of stops Ns(Wg) has not reached the upper limit value Nt, and therefore that it is acceptable to allocate the target call Xk to the target car Gk. In this case, the group management control device 2 counts the number of stops at the destination floor Fd indicated by the target call Xk (=1 stop; the scheduled number of new stops the target car Gk will make as a result of the allocation of the target call Xk) as the scheduled number of stops Ns(Wg) (step S214B), and then adds the target car Gk to the allocation candidates for the target call Xk (step S215). At this time, if the number of stops at the destination floor Fd indicated by the target call Xk (=1 stop) has been counted in step S212B, a total of two stops will be counted as the scheduled number of stops Ns(Wg) in this sorting process. Thereafter, the group management control device 2 ends the selection process for the target car Gk.

[0059] On the other hand, if the group management control device 2 determines "not small (No)" in step S213X, it can determine that the value of the scheduled number of stops Ns(Wg) has reached the upper limit Nt and therefore cannot allow the target call Xk to be assigned to the target car Gk. In this case, the group management control device 2 terminates the selection process for the target car Gk without adding the target car Gk to the assignment candidates so as not to execute the assignment to the target car Gk. In this way, the assignment of the target call Xk to the target car Gk (in other words, the assignment of the hall call X that requires a stop in the relevant section Wg to the target car Gk) is limited, and the scheduled number of stops Ns(Wg) of the target car Gk in the relevant section Wg is controlled so as not to exceed the upper limit Nt.

[0060] <Allocation process (continued)> After step S102 (see FIG. 4), the group management control device 2 determines whether or not an allocation candidate has been found by executing step S102 (step S103).

[0061] Here, if the group management control device 2 is unable to add any car G to the allocation candidates in the selection process (see Figures 5 and 6), it will end step S102 without being able to find an allocation candidate. In this case, the group management control device 2 determines "unable to add any car G (No)" in step S103, returns to step S102 again, and executes a new selection process for each of the cars G. At this time, the group management control device 2 may relax the upper limit value Nt (for example, add "1" to the upper limit value Nt to set it as a new upper limit value Nt) so that it becomes possible to find an allocation candidate, and then return to step S102.

[0062] If the group management control device 2 determines that it has been completed (Yes) in step S103, it selects the most suitable car G from the allocation candidates found in step S102 and allocates the target call Xk to that car G (step S111).

[0063] Thereafter, the group management control device 2 updates the value of the scheduled number of stops Ns(Wg) in the corresponding section Wg among the scheduled number of stops Ns(W) for the car G selected in step S111 (car G to which the target call Xk is assigned) in the car management data Dq to the value obtained for that car G in step S214A or S214B in Fig. 6 (step S112). Thereafter, the group management control device 2 ends the allocation process.

[0064] According to this allocation process, it becomes possible to limit the number of planned stops Ns(Wn) in each section Wn for any car G, and as a result, it becomes possible to control the number of stops per revolution of each car G while preventing the number of stops from being significantly biased toward either the upward or downward direction of travel. Thus, it becomes possible to achieve both improved transport efficiency obtained by limiting the number of stops per revolution in an elevator and improved convenience obtained by suppressing bias in the number of stops.

[0065] Furthermore, in this embodiment, when each car G reverses its direction of travel at the first terminal floor Fe1 or a floor immediately before it, the group management control device 2 sets that floor as the current floor Fg, sets the second terminal floor Fe2 as the new first terminal floor Fe1, and sets the first terminal floor Fe1 as the new second terminal floor Fe2, and resets the section Wn for that car G. This makes it possible to continue control so that the number of stops is not significantly biased at all times.

[0066] [2] Variation [2-1] First modified example Fig. 7(A) is a conceptual diagram illustrating car management data Dq used in the first modified example. As shown in this figure, in the car management data Dq, each car G may be further associated with a scheduled number of stops Ns (W = W3) in a third section W3 different from sections W1 and W2. Here, section W3 is set as the section W that the car G passes through next after sections W1 and W2 in the order of passage, and is the section W from the second terminal floor Fe2 to the first terminal floor Fe1 (see Fig. 8). The scheduled number of stops Ns (W = W3) is the count of the scheduled number of times the car G will stop in section W3.

[0067] In the cage management data Dq of this modified example, when cage G reverses its direction of travel at the first terminal floor Fe1 or a floor immediately before it, that floor is designated as the current floor Fg, the second terminal floor Fe2 is designated as the new first terminal floor Fe1, and the first terminal floor Fe1 is designated as the new second terminal floor Fe2, and all sections Wn are reset. In this modified example, the planned number of stops Ns(W2) in the section W2 before resetting is carried over to the planned number of stops Ns(W1) in the new reset section W1. Furthermore, the planned number of stops Ns(W3) in the section W3 before resetting is carried over to the planned number of stops Ns(W2) in the new reset section W2. Meanwhile, the planned number of stops Ns(W3) in the new reset section W3 is reset to Ns(W3)=0.

[0068] 7(B) is a conceptual diagram illustrating the hall call management data Dx used in the first modified example. In the hall call management data Dx of this modified example, information on each hall call X is recorded by allocating it to the section W3 if the car G can respond to the hall call X in the section W3.

[0069] 7(B) shows a specific example of information (departure floor Fc and destination floor Fd) of hall call X in section W3 recorded in hall call management data Dx for car G with Pg="G-01", along with other specific examples. In FIG. 8, the information of hall call X in section W3 is visualized in the same way as in FIGS. 3(A) and 3(B).

[0070] 9 is a flowchart showing a part of the selection process executed in Modification 1. In Modification 1, after step S201, the group management control device 2 uses the current floor Fg and current direction Kg of the target car Gk acquired in step S201 to identify the current section W1 to W3 set for the target car Gk (step S230). Specifically, the group management control device 2 designates the terminal floor located in the current direction Kg (current direction of travel) of the target car Gk as the first terminal floor Fe1, and the terminal floor on the opposite side as the second terminal floor Fe2.Then, according to the order in which the target car Gk passes, it identifies the section W from the current floor Fg of the target car Gk to the first terminal floor Fe1 as section W1 (see Figure 3(A)), identifies the section W from the first terminal floor Fe1 to the second terminal floor Fe2 as section W2 (see Figure 3(B)), and identifies the section W from the second terminal floor Fe2 to the first terminal floor Fe1 as section W3 (see Figure 8).

[0071] After step S230, assuming that the target call Xk has been assigned to the target car Gk, the group management control device 2 identifies which section Wn is the corresponding section Wg in which the target car Gk can respond to the target call Xk (step S231).

[0072] Specifically, for the departure floor Fc and destination floor Fd indicated by the target call Xk, if condition [J1] is satisfied, the group management control device 2 identifies the corresponding section Wg as "section W1" (see FIG. 3(A)), and if condition [J2] is satisfied, the group management control device 2 identifies the corresponding section Wg as "section W2" (see FIG. 3(B)). Furthermore, for the departure floor Fc and destination floor Fd indicated by the target call Xk, if condition [J3] is satisfied that the departure floor Fc is any floor between the second terminal floor Fe2 and the current floor Fg, and the direction from the departure floor Fc to the destination floor Fd matches the traveling direction of the target car Gk in section W3 (the direction from the second terminal floor Fe2 to the first terminal floor Fe1), the group management control device 2 identifies the corresponding section Wg as "section W3" (see FIG. 8).

[0073] In this way, by providing the third section W3 as the corresponding section Wg in which the target car Gk can respond to the target call Xk, if it is assumed that the target call Xk has been assigned to the target car Gk, the target car Gk will always respond to the target call Xk in one of the three sections W1 to W3. Therefore, in step S231, any one of the three sections W1 to W3 will always be specified as the corresponding section Wg.

[0074] Then, the group management control device 2 identifies the relevant section Wg in step S231, and then executes the processing from step S211 (see FIG. 6). This enables the group management control device 2 to count the planned number of stops Ns(W3) in the section W3, and also to limit the allocation to the elevator car G so that the planned number of stops Ns(W3) does not exceed the upper limit value Nt.

[0075] According to the first variant, even immediately after the elevator car G turns around at or before the first terminal floor Fe1 (immediately after passing through section W1), it is possible to create a situation in which the number of stops during the course of one rotation from there is already controlled so that the number of stops is not significantly biased towards either the upward or downward direction of travel.

[0076] [2-2] Second variant In both the above-mentioned embodiment and the first variant example, the planned number of stops Ns(Wn) for each section Wn is not limited to counting both the planned number of stops of the elevator G at the departure floor Fc and the planned number of stops of the elevator G at the destination floor Fd, but may be appropriately changed to counting only one of the planned numbers.

[0077] Specifically, after determining in step S203 in the selection process (FIGS. 5 and 6) that the relevant section Wg is "section W1" or "section W2," the group management control device 2 executes only the process from step S213, thereby making it possible to count only the scheduled number of times the car G stops at the destination floor Fd as the scheduled number of stops Ns(Wn). In this case, in step S213, the group management control device 2 may determine whether or not there is a destination floor Fd at which the target car Gk is scheduled to stop in the relevant section Wg (see FIG. 10(A) and FIG. 10(B)), instead of the scheduled stop floor (departure floor Fc or destination floor Fd) of the target car Gk in the relevant section Wg.

[0078] Furthermore, in the selection process (FIGS. 5 and 6), after determining in step S203 that the relevant section Wg is "section W1" or "section W2," the group management control device 2 executes the process from step S211, while executing step S215 immediately after step S212A or S212B, thereby making it possible to count only the scheduled number of times that the car G stops at the departure floor Fc as the scheduled number of stops Ns(Wn). In this case, in step S213, instead of the scheduled stop floor (departure floor Fc or destination floor Fd) of the target car Gk in the relevant section Wg, the group management control device 2 may target only the departure floor Fc at which the target car Gk is scheduled to stop in the relevant section Wg, and determine whether or not the departure floor Fc is the same as the "departure floor Fc" indicated by the target call Xk.

[0079] The above-described embodiments and modifications should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined not by the above-described embodiments and modifications, but by the claims. Furthermore, the scope of the present invention is intended to include all modifications that are equivalent to the scope of the claims and fall within the scope thereof.

[0080] From the above-described embodiments and modifications, the subject of the invention is not limited to the group management control device 2, but may be extracted individually from part or all of the control processes (including the control methods corresponding to the control processes) and programs executed by the group management control device 2. Also, part or all of the above-described elevators may be extracted as the subject of the invention. [Explanation of symbols]

[0081] 1. Destination floor registration device 2 Group management control device G car W section X Platform call 21 Memory section 22 Control Unit Dp Equipment Management Data Dq car management data Dx Hall call management data Dy Cage call management data Fc Departure Floor Fd Destination floor Fg Current floor Fs Installation floor GK Focus Basket Kg Current direction Ns Planned number of stops Nt upper limit Pd device information Pg Basket Information Pr Reception Information Wn, W1, W2, W3 sections Wg applicable section Xk target call Fe1 1st floor Fe2 2nd end floor

Claims

1. A control device that assigns hall calls to elevator cars in an elevator, The terminal floor located in the direction of travel of the car is designated as the first terminal floor, and the terminal floor opposite thereto is designated as the second terminal floor, and a section from the current floor of the car to the first terminal floor and a section from the first terminal floor to the second terminal floor are set according to the order in which the car passes, and then, each time a hall call is assigned to the car, the scheduled number of times that the car will newly stop as a result of the assignment is counted as the scheduled number of stops of the car in the section in which the hall call is answered, An elevator control device that, for each section, when the scheduled number of stops in that section reaches an upper limit, limits the allocation of hall calls that require stops in that section to the elevator car.

2. 2. An elevator control device as described in claim 1, further setting a section from the second end floor to the first end floor according to the order in which the elevator car passes, and then, each time a hall call is assigned to the elevator car, counting the scheduled number of times that the elevator car will newly stop as a result of the assignment as the scheduled number of times that the elevator car will stop in the section in which the hall call is answered.

3. 3. An elevator control device as described in claim 1 or 2, wherein, in the section from the current floor to the first end floor, the value of the number of scheduled stops in that section is updated to a value subtracted by one each time the elevator car arrives at a scheduled stopping floor in that section.

4. 3. An elevator control device as described in claim 1 or 2, wherein when the elevator car reverses its direction of travel at the first terminal floor or a floor just before it, that floor is set as the current floor, the second terminal floor is set as the new first terminal floor, and the first terminal floor is set as the new second terminal floor, and the section is newly set.

5. A control method for assigning hall calls to elevator cars, The terminal floor located in the direction of travel of the car is designated as the first terminal floor, and the terminal floor opposite thereto is designated as the second terminal floor, and a section from the current floor of the car to the first terminal floor and a section from the first terminal floor to the second terminal floor are set according to the order in which the car passes, and then, each time a hall call is assigned to the car, the scheduled number of times that the car will newly stop as a result of the assignment is counted as the scheduled number of stops of the car in the section in which the hall call is answered, An elevator control method that, for each section, when the number of scheduled stops in that section reaches an upper limit, limits the allocation of hall calls that require stops in that section to the elevator car.

Images