Control of an elevator group

Abstract

The invention relates to a procedure for controlling an elevator group consisting of double-deck elevators. According to the invention, landing calls are allocated to the elevators and after that to the elevator decks in such a way that the passenger journey time is optimised. The procedure of the invention takes into account the time the call has been on and the estimated time of arrival to the destination floor.

Description

[0001] The present invention relates to a procedure for controlling an elevator group, as defined in the preamble of claim 1.

[0002] When a number of elevators form an elevator group that serves passengers arriving in the same lobby, the elevators are controlled by a common group controller. The group control system determines which elevator will serve a given landing call waiting to be served. The practical implementation of group control depends on how many elevators the group comprises and how the effects of different factors are weighted. Group control can be designed to optimise cost functions, which include considering e.g. the passenger waiting time, the number of departures of the elevators, the passenger ride time, the passenger journey time or combinations of these with different weighting of the various factors. The group control also defines the type of control policy to be followed by the elevator group.

[0003] Additional features will be added to group control when the elevators are double-deckers, where two decks are attached on top of each other in a frame and the elevator serves two building floors simultaneously when the elevator stops.

[0004] A conventional control solution is based on collective control, in which the elevator always stops to serve the nearest landing call in the drive direction. If the call is allocated to the trailing car, coincidences with possible landing calls from the next floor are maximised. Collective control in elevators with normal cars is ineffective in outgoing and mixed traffic. The consequence is bunching and bad service for the lowest floors. The same applies to collective control of double-deck elevators. For example, specification U.S. Pat. No. 4,632,224 presents a collective control system for double-deck elevators in which a landing call is allocated to the trailing car in the travelling direction of the elevator, in other words, when the elevator is moving down, the landing call is allocated to the upper deck, and when the elevator is moving up, the landing call is allocated to the lower deck. Another specification U.S. Pat. No. 4,582,173 discloses a group control for a double deck elevator calculating internal costs corresponding to the waiting times inside the car during the stops and external costs corresponding to the waiting times on the landing call floors. In this control only the operating costs consisting of these time losses of the passengers are minimised.

[0005] The object of the invention is to achieve a new procedure for controlling an elevator group in order to improve passenger journey times, i.e. the total time spent in an elevator system and to allow better utilisation of the capacity of the elevator group. To implement this, the invention is characterised by the features presented in the characterisation part of claim 1.

[0006] Certain other embodiments of the invention are characterised by the features presented in the characterisation parts of the sub-claims. According to one feature if the invention the journey time consisting of waiting time at the landing call floor and ride time inside a car to the destination floor, is optimised by minimising the passenger waiting time and ride time. Especially the journey time is optimised so that a landing call for an elevator comprising two decks is selected by minimising the passenger waiting time and the best deck to serve the landing call is selected by minimising the passenger journey time.

[0007] In a preferred application of the invention, the passenger waiting time is optimised by minimising a waiting time forecast WTFele, which comprises the current landing call time weighted by the number of persons waiting behind the call and the estimated time of arrival of a car to the landing call. All the passengers waiting the serving car is in this modification taken into account.

[0008] In another modification of the invention the passenger journey time is minimised by allocating the landing call to the deck that will cause the fewest additional stops to the elevator and least additional delay on the way to the passenger destination floor. Also the passenger ride comfort increases as the number of stops decreases.

[0009] In a further embodiment of the invention the elevator estimated time of arrival ETA to the destination floor is calculated separately for each deck, taking into account the stops already existing for the elevator and the additional stops caused by the selected landing call, and the landing call is allocated to the deck for which the estimated time of arrival to the destination floor is smallest.

[0010] In a preferred modification of the invention the best deck for each landing call is selected by minimising the cost function. The cost function may comprise the estimated time of arrival ETAd to the destination floor. Alternatively, the cost function may also comprise the estimated time of arrival ETAf to the furthest call floor.

[0011] Advantageously, when calculating the ETA, the future stops and stop times are based on the existing car calls and landing call stops and on the additional stops and delays caused by the call to be selected. The additional delays caused by the landing call to be selected are obtained from the statistical forecasts of passenger traffic, which includes passenger arrival and exit rates at each floors at each time of the day.

[0012] The solution of the invention allows a substantial increase in the capacity of an elevator group consisting of double-deck elevators as compared with solutions based on collective control. In the solution of the invention, passenger service is taken into consideration. Shorter journey and elevator round trip times are achieved which increases the handling capacity. The level of service to passengers is also substantially improved.

[0013] The optimisation of passenger waiting times the invention has been compared with a prior-art method in which only the call times are optimised. Passenger waiting time starts when a passenger arrives to a lobby and ends when he enters a car. Call time starts when the passenger pushes a call button and ends when the landing call is cancelled. These times are different especially during heavy traffic intensity. Number of passengers is obtained from the statistical forecasts. The average waiting times for outgoing traffic especially in heavy traffic conditions were clearly shorter. As for waiting times of each floor, the average waiting times are shorter and better balanced at different floors, especially at the busiest floors. The control procedure keeps the elevators apart from each other, evenly spaced in different parts of the building. The best car to serve a landing call is so selected that coincident calls, i.e. car calls and allocated landing calls, will be taken into account

[0014] The average and maximum call times are also reduced. The invention produces effective service and short waiting times especially during lunch-time traffic and in buildings having several entrance floors, which is difficult to achieve with conventional control procedures.

[0015] In the following, the invention will be described by the aid of some of its embodiments by referring to the drawings, in which:

[0016] FIG. 1 presents a schematic illustration of a double-deck elevator group,

[0017] FIG. 2 presents a diagram representing the control of the elevator group, and

[0018] FIG. 3 illustrates the control of a group of double-deck elevators.

[0019] The diagram in FIG. 1 represents an elevator group 2 comprising four double-deck elevators 4. Each elevator comprises and elevator car 6, which has a lower deck 8 and above it an upper deck 10. The elevator car is moved in an elevator shaft 12 e.g. using a traction-sheave machine, and the cars are suspended on ropes (not shown). In the example in the figure, the building has fourteen floors, and the lower deck 8 can be used to travel between the first floor 14 and the thirteenth 18 floor and, correspondingly, the upper deck 10 can be used to travel between the second 16 and the fourteenth 20 floors. An escalator is provided at least between the first and second floors to let the passengers move to the second floor. In this case, the first and second floors are entrance floors, i.e. floors where people enter the building and take an elevator to go to upper floors.

[0020] Both elevator decks are provided with call buttons for the input of car calls to target floors, and the landings are provided with landing call buttons, by means of which passengers can order an elevator to the floor in question. In a preferred embodiment, on the first floor and on the lower deck it is only possible to give a car call to every other floor, e.g. to odd floors, and similarly on the second floor and on the upper deck it is only possible to give a car call to every other floor, e.g. to even floors. Car calls from higher floors to any floors are accepted The entrance floors are provided with signs to guide the passengers to the correct entrance floors. In addition, the call buttons for the non-allowed floors are hidden from view when the elevator is at the lowest stopping floor or the illuminated circle around the call button is caused to become a different colour. The cars and landings are provided with sufficient displays to inform the passengers about the target floors.

[0021] FIG. 2 is a schematic illustration of the control system of an elevator group, which controls the elevators to serve the calls given by passengers. Each elevator has its own elevator controller 22, to which the car calls entered by passengers using the car call buttons 26 are taken via a serial communication link 24. The car calls from both the lower and the upper decks are taken to the same elevator controller 22. The elevator controller also receives load data from the load weighing devices 28 of the elevator, and the drive control 30 of the elevator machinery also works under the elevator controller. The elevator controllers 22 are connected to a group controller 32, which-controls the functions of the entire elevator group, such as the allocation of landing calls to different elevators. The elevator controllers are provided with micro computers and memories for the calculation of cost functions during the call allocation. An essential part of this function is the landing calls 34, which are taken via serial links to the group controllers. The entire traffic flow and its distribution in the building are monitored by an elevator monitoring and command system 36.

[0022] Landing calls given from each floor for upward and downward transport are so served that the passenger waiting time and ride time, i.e. the time spent inside the car before reaching the destination floor, will be minimised. In this way, the journey time, i.e. the total time a passenger spends in the elevator system, is minimised which decreases the number of elevator stops and the capacity of the elevator group is maximised. Based on the status data concerning passengers and elevators and making use of statistics and history data, decisions are made about the allocation of landing calls to different elevators. A traffic forecaster produces forecasts of passenger traffic flows in the building. The prevailing traffic pattern is identified using fuzzy logic rules. Forecasts of future traffic patterns and passenger traffic flows are used in the selection of cars for different calls.

[0023] FIG. 3 illustrates the various stages of the acquisition and processing of data. From the passenger and elevator status data 38, the passenger flow is detected (block 40). Traffic flows can be detected in different ways. Passenger traffic information is obtained e.g. from detectors and cameras placed in the lobbies and having image processing functions. These methods are generally only used on the entrance floors and on certain special floors, and the entire traffic flow in the building cannot be measured. The stepwise changes in the load information can be measured, and it is used to calculate the number of entering and exiting passengers. The photocell signal is used to verify the calculation result. Passenger destination floors are deduced from the existing and given car calls.

[0024] Traffic statistics and traffic events are used to learn and forecast the traffic, block 42. Long-time statistics comprise entering and exiting passengers on the elevators at each floor during the day. Short-time statistics comprise traffic events, such as the states, directions and positions of car movement, landing calls and car calls as well as traffic events relating to passengers during the last five minutes. Data indicating the traffic components and required traffic capacity are also stored in the memory, In block 44, the traffic pattern is recognised using fuzzy logic. As for the implementation of this, reference is made to specification U.S. Pat. No. 5,229,559, in which it is described in detail.

[0025] The allocation of landing calls (block 46) in a group consisting of double-deck elevators, carried out by the group control system, utilises the above-described forecasts and passenger and elevator status data. Traffic forecasts are used in the recognition of the traffic pattern, optimisation of passenger waiting time and the balancing of service in buildings with more than one entrance. Traffic forecasts also influence parking policies and door speed control.

[0026] The best double-deck elevator is selected by optimising the passenger waiting time at the landing call floor and ride time inside the car. To optimise the waiting time, landing call time is weighted by the number of waiting passengers behind the call. The weighting coefficients depend on the estimated number of waiting passengers on each floor. When the landing call time and traffic flow on each floor are known, an estimate of the number of passengers behind the call is obtained by multiplying the call time by the passenger arrival rate at that floor. A probable destination floor for each passenger is obtained from the statistical forecasts of the number of exiting passengers at each floor. Car calls given from the landing call floor can then be estimated. By minimising the time from passenger arrival floor to destination floor, the passenger ride time is optimised. The maximum ride time is minimised by minimising the longest car call time, or the time to the furthest car call.

[0027] The better deck to serve a landing call is selected by comparing the journey times internally for the elevator. The effects of a new landing call and new car calls are estimated separately for each deck The passenger waiting and ride times are predicted and the landing call is allocated to the deck with the shortest journey time. According to one modification passenger waiting time and ride time to the furthest car call is predicted and the landing call is selected to the deck with minimum costs.

[0028] When the building has more than one entrance floor, in up-peak traffic and in two-way traffic, free elevators are returned to an entrance floor according to the prevailing traffic flow forecasts for these floors. During up-peak hours, cars going up can stop at entrance floors where an up-call is not on, if another elevator is loading at the floor.

[0029] Next, we shall consider the minimisation of passenger journey time, waiting time and ride time in a case according to the invention. During landing call allocation, the existing landing calls are sorted into descending order according to age. For each landing call and for each elevator the waiting time forecast WTF is calculated and the call is selected to the elevator with the shortest waiting time forecast. WTFele is defined by the formula:

[0030] WTFele=σ*(CT+ETAele), where

[0031] CT=current landing call time, i.e. the time the landing call has been active

[0032] σ=weight factor correlating to the estimated number of passengers behind call

[0033] ETAele=Σ(td)+Σ(ts)+tr+ta

[0034] td=drive time of one floor flight

[0035] ts=predicted time to stop at a floor

[0036] tr=predicted time that a car remains standing at floor

[0037] ta=additional time delay if e.g. the elevator has been ordered to park on certain conditions.

[0038] In the ETAele expression, the summing expression Σ(td) means the time required for the car to reach the landing call floor in its route while the summing expression Σ(ts) means the time required for the stops before the reaching the landing call floor. The terms tr and ta can be omitted in less accurate approximations.

[0039] The drive times for each floor have been calculated for each elevator in the group at the time of start-up of the group control program, using floor heights and nominal elevator speeds. The predicted stop time for an elevator is calculated by considering the door times and possible number of passengers transfers. The current landing call time is weighted by a factor σ in proportion to the number of persons behind the call. In this regard, reference is made to the patent U.S. Pat. No. 5,616,896. The number of persons on each floor and for each travel direction is obtained from statistical forecasts. In the calculation of ETA times, only those elevators that can serve the call are taken into account. The calculation does not include elevators that are not operating under group control or are fully loaded.

[0040] To optimise the journey time for persons, a landing call for a double-deck elevator is selected by minimising the passenger waiting time, and, the best deck to serve the landing call is selected by minimising the total time that passengers spend in the elevator system, the journey time.

[0041] Passenger waiting time is optimised by minimising the waiting time forecast WTFele for each elevator, where the current landing call time CT is weighted by the number σ of persons waiting behind the call, and the cost function is of the form

minele WTFele=minele(σ*(CT+ETAele)),

[0042] where ETAele is the estimated time of arrival of the elevator to the landing call.

[0043] Passenger journey time is minimised by allocating a landing call to the deck for which the landing call will cause the fewest additional stops and least additional delay on its way to the destination calls.

[0044] The estimated time of arrival to the destination floor is calculated separately for each deck by taking into account the existing stops of the elevator and the additional stops caused by the selected landing call. The landing call is allocated to the deck for which the sum of the waiting time forecast and the estimated time of arrival at the destination floor is smallest.

[0045] For each landing call, the best deck is selected by minimising the cost function. In the cost function J, the sum of waiting time forecast and estimated time of arrival ETAd to the destination floors is minimised, and the function is of the form

J =mindeck(σ*(CT+ETAele+ETAd))

=mindeck(σ*(CTlanding call floordeck position+Σ(td+ta)landing call floor+Σ(td+ts)))

[0046] where td is the drive time for one floor flight and ts is the predicted stop time at a floor. In the summing functions, the time required for the drive from one floor to another and the time consumed during stops on the route are calculated. In the waiting time forecast the estimated time of arrival from the deck position to the landing call floor is calculated, and the estimated time of the arrival ETAd to the destination floor is calculated from the landing call floor to the destination floor.

[0047] In a practical application the estimated time of arrival of the destination floor is optimised to the furthest car call floor. Accordingly, the estimated time of arrival ETAf to the furthest call floor is minimised, and the cost function Jf is of the form

J r =mindeck(ETAf)

=mindeck(σdeck position(td+ts)

[0048] where

[0049] ETAf=estimated time of arrival of a car to the furthest call floor when starting from the deck position floor

[0050] td=drive time for one floor flight

[0051] ts=forecast stop time at a call floor.

[0052] In the calculation of ETA, the future stops and stop times are based on the existing car call and landing call stops and on the additional stops and additional delays caused by the call to be selected. The additional delays caused by the landing call to be selected are obtained from the statistical forecasts of the passenger traffic, which are based on passenger arrival and departure floors at that time of the day. The car load is monitored and if the load exceeds the full load limit, then no more landing calls are allocated for that deck. In the entrance lobby, the upper deck can only be given car calls to even floors while the lower deck can only be given car calls to odd floors. After leaving the entrance floor each deck can serve any of the floors.

[0053] According to these cost functions whole the passenger journey time is optimised for each deck. Also here the additional delays tr and ta can be added if it is considered necessary.

[0054] The invention has been described above by the aid of some of its embodiments. However, the description is not to be regarded as constituting a limitation, but the embodiments of the invention may be varied within the limits defined by the following claims.

Claims

1. Procedure for controlling an elevator group comprising at least two double-deck elevators, each double-deck elevator comprising an upper deck and a lower deck, said decks serving successive floors in the building when the elevator stops, characterised in that, in the procedure, the best deck to serve a landing call is selected by optimising passenger journey time.

2. Procedure as defined in claim 1, characterised in that the journey time, which consists of waiting time at the landing call floor and ride time inside a car to the destination floor, is optimised by minimising the passenger waiting time and ride time.

3. Procedure as defined in claim 1 or 2, characterised in that, to optimise the journey time, a landing call for an elevator comprising two decks is selected by minimising the passenger waiting time and the best deck to serve the landing call is selected by minimising the passenger journey time.

4. Procedure as defined in claim 3, characterised in that the passenger waiting time is optimised by minimising a waiting time forecast WTFele, where the current landing call time CT is weighted by the number of persons waiting behind the call a and the cost function is of the form

5. Procedure as defined in any one claims 1-4, characterised in that the passenger journey time is minimised by allocating the landing call to the deck that will cause the fewest additional stops to the elevator and least additional delay on the way to the passenger destination floor.

6. Procedure as defined in any one claims 1-5, characterised in that the elevator estimated time of arrival ETA to the destination floor is calculated separately for each deck, taking into account the stops already existing for the elevator and the additional stops caused by the selected landing call, and the landing call is allocated to the deck for which the estimated time of arrival to the destination floor is smallest.

7. Procedure as defined in any one claims 1-6, characterised in that the best deck for each landing call is selected by minimising the cost function.

8. Procedure as defined in any one claims 7, characterised in that, in the cost function J, the estimated time of arrival ETAd to the destination floor is minimised, and the function is of the form

9. Procedure as defined in any one claims 7, characterised in hat, in the cost function J, the estimated time of arrival ETAf to the furthest call floor is minimised, and the function is of the form

10. Procedure as defined in claim 8 or 9, characterised in that, in the calculation of ETA, the future stops and stop times are based on the existing car calls and landing call stops and on the additional stops and delays caused by the call to be selected.

11. Procedure as defined in claim 10, characterised in that the additional delays caused by the landing call to be selected are obtained from the statistical forecasts of passenger traffic, which includes passenger arrival and exit rates at each floors at each time of the day.

12. Procedure as defined in any one claims 1-11, characterised in that the car load is monitored and if the load exceeds the full load limit, then no more landing calls are allocated for that deck.

13. Procedure as defined in any one claims 1-12, characterised in that, at the main lobby, the upper deck and the lower deck accept car calls only to every other floor.

14. Procedure as defined in claim 13, characterised in that when leaving the entrance floor the lower deck serves odd floors and the upper deck serves the even floors when the lowest floor is marked by number 1.

15. Procedure as defined in any one claims 1-14, characterised in that, at the upper floors each deck can stop to any floor when serving the calls.