Detailed Description
Preferred embodiments of an elevator group control device and a group control method according to the present invention will be described below with reference to the accompanying drawings, in which the same or corresponding parts are denoted by the same reference numerals in the drawings.
First, before the embodiments are explained, an outline of an elevator group control device according to the present invention will be explained. The elevator group management control device of the invention performs the co-riding control of users according to the attributes of the destination floor registered by the destination floor registration device arranged at the entrance floor of the building and the floor set in advance.
Here, attributes of floors associated with entrance conditions of floors of the building or doors within the floors are set for the building. The attribute of the floor refers to floor information such as a woman-specific floor, a suite (suite room) floor, and a company that resides on a plurality of floors.
According to the group management control device for an elevator of the present invention, by using the attribute of the floor of the destination floor registered in the destination floor registration device as the attribute of the user and assigning different cars to a plurality of users having different attributes, it is possible to assign different cars to the user traveling to, for example, a female-only floor and other users with a simple configuration without performing personal authentication.
Embodiment mode 1
Fig. 1 is a front view showing a landing of an entrance floor of an elevator to which an elevator group control device according to embodiment 1 of the present invention is applied. Fig. 2 is a front view showing a landing on a floor other than the entrance floor of an elevator to which the group control device of an elevator according to embodiment 1 of the present invention is applied.
In fig. 1 and 2, two elevators are representatively shown, but normally, three or more elevators are provided. The entrance floor of the building is a floor provided with an entrance of the building. Further, the landing structure of the entrance floor shown in fig. 1 can be applied to floors other than the entrance floor.
In fig. 1 and 2, a landing door 1 is provided at each floor where an elevator stops. A hoistway, not shown, is provided on the inner side of the landing door 1, and the hoistway penetrates each floor of the building. A car, not shown, is provided in the hoistway, and the car is raised and lowered in the hoistway. When the car arrives at a landing, the landing door 1 is opened, and a user rides in and out.
When a destination floor is registered by a destination floor registration device 2 provided at a landing of an entrance floor shown in fig. 1, an elevator group management control device according to embodiment 1 of the present invention allocates an optimum elevator car to the floor, and displays an assigned elevator name corresponding to the destination floor on an assigned elevator display device 3. The elevator car name corresponds to the characters or symbols displayed on the car name display 4.
Here, in the landing of the entrance floor shown in fig. 1, the elevator name display 4 shows that the elevator name of the left elevator is a and the elevator name of the right elevator is B. Then, the assigned car display device 3 displays a car B on the right side of the hall destination call to the 7 th floor. In addition, a notification device 5 for notifying the state of the car is provided for each elevator at a landing on the entry floor.
In addition, when a hall call is registered by the hall call registration device 6 provided in a hall of a floor other than the entrance floor shown in fig. 2, the elevator group control device according to embodiment 1 allocates an optimum car to the floor.
Fig. 3 is a block diagram showing a configuration of an elevator group control device according to embodiment 1 of the present invention. In fig. 3, the group management control device for an elevator includes a destination floor registration device 2, a notification device 5, a hall call registration device 6, a car call registration device 7 provided in a car for registering a destination floor, and a control device 10, which are shown in fig. 1 and 2.
The control device 10 includes a user identification unit 11, a car assignment unit 12, a riding rule setting unit 13, and an operation control unit 14. Here, the control device 10 is composed of a microprocessor having a CPU (Central Processing Unit) and a storage Unit for storing a program, both of which are not shown. The units constituting the control device 10 are stored in the storage unit as software.
When a destination floor is registered by the destination floor registration device 2 of an entrance floor, the user identification unit 11 identifies the attribute of the floor of the destination floor as the attribute of the user. When a destination floor registration device 2 is installed in a landing on a floor other than the entrance floor, and a destination floor is registered by the destination floor registration device 2, the user identification unit 11 identifies the attribute of the floor on which the destination floor registration device 2 is installed as the attribute of the user.
When a hall call is registered by a hall call registration device 6 provided in a hall provided in a floor other than the entrance floor, the user recognition unit 11 recognizes the attribute of the floor on which the hall call registration device 6 is provided as the attribute of the user. The user recognition unit 11 outputs the registered destination call or hall call and the attribute of the user to the car assignment unit 12.
The car assignment section 12 selects an assignment candidate car based on the attribute of the user who operates the destination floor registration device 2 or the hall call registration device 6 and the attribute and the number of users who are scheduled to board each elevator or board, and determines an assigned car with reference to the boarding rule output by the boarding rule setting section 13. In this case, the car assignment unit 12 may determine an assigned car based on the agreement or disagreement of the attributes of each user.
The copulation rule setting unit 13 sets a copulation rule relating to copulation of users having different attributes. Specifically, the riding rule setting unit 13 sets the number of persons having the same attribute that allows assignment of the same car to a plurality of users having different attributes. Fig. 4 is an explanatory diagram illustrating attributes of floors of a building and a ride-sharing rule in an elevator group control device according to embodiment 1 of the present invention.
In fig. 4, the building is a 7-story building from floors B (underground floors) to 6 floors, where floor B is a parking lot, floor 1 is an entrance floor on the ground, floors 2 and 3 are floors dedicated to men, floors 4 and 5 are floors dedicated to women, floor 6 is a floor dedicated to homes, floors B and 1 are entrance floors, floors 2 and 3 are attributes a, floors 4 and 5 are attributes B, and floor 6 is an attribute c.
At this time, the copultiple rule is set to: for the elevator with the attribute of a, the user with other attribute is not allocated with the elevator, and for the elevator with the attribute of b above 3, the user with other attribute is allowed to be allocated with the elevator. Further, when a plurality of users having attributes different from each other have taken the elevator, the refining condition including 2 or more persons having the attribute of c can be set.
Returning to fig. 3, the car assignment section 12 outputs the attribute of the user to the notification device 5 provided at the landing on the entrance floor, for the elevator planned to be taken or the elevator currently being taken by the user with a single attribute. The notification device 5 performs notification corresponding to the input attribute of the user.
In addition, when the destination floor registration device 2 is installed in a landing on a floor other than the entrance floor, if the destination floor registered by the destination floor registration device 2 is a floor other than the entrance floor and the attribute of the floor on which the destination floor registration device 2 is installed does not match the attribute of the floor of the destination floor, the user recognition unit 11 outputs suspicious person information to the car assignment unit 12 together with the registered destination call and the attribute of the user.
Further, when the hall call registration device 6 is installed at a hall of a floor other than the entrance floor, and when the car reaches the floor operated by the hall call registration device 6, the destination floor registered by the car call registration device 7 is a floor other than the entrance floor, and the attribute of the floor on which the hall call registration device 6 is installed does not match the attribute of the floor of the destination floor, the user recognition section 11 outputs suspicious person information to the car assignment section 12 together with the registered destination call and the attribute of the user.
When a car is assigned to a user to whom suspicious person information is given, the car assignment unit 12 outputs an entry floor return command to the operation control unit 14. When an entry floor return command is input, the operation control unit 14 causes the car to travel to an entry floor, not a destination floor, temporarily opens the landing door 1 after reaching the entry floor, and then causes the car to travel to the destination floor. This can prompt the user to whom suspicious person information is given to get off at the entrance floor.
Next, the processing of the elevator group control system according to embodiment 1 of the present invention will be described with reference to the flowcharts of fig. 5 and 6. Fig. 5 shows a process in a configuration in which the co-multiplication rule setting unit 13 shown in fig. 3 is omitted, and fig. 6 shows a process in a configuration in which the co-multiplication rule setting unit 13 is not omitted.
In fig. 5, first, at the elevator hall, the destination floor registration device 2 or the hall call registration device 6 is operated, and the registered destination call or hall call is output to the user recognition portion 11 (step S101).
Next, the user recognition unit 11 determines whether or not the operated registration device is the destination floor registration device 2 installed on the entrance floor (step S102).
If it is determined in step S102 that the registration device is the destination floor registration device 2 installed on the entry floor (that is, yes), the user identification portion 11 identifies the attribute of the floor of the registered destination floor as the attribute of the user, and outputs the registered destination call and the attribute of the user to the car assignment portion 12 (step S103).
For example, in the building shown in fig. 4, when 4 floors are registered as destination floors by the destination floor registration device 2 provided on floor 1, the b attribute set for 4 floors is recognized as the attribute of the user, and the attribute of the user becomes the b attribute.
On the other hand, when it is determined in step S102 that the registration device is not the destination floor registration device 2 installed on the entrance floor (i.e., no), the user identification portion 11 identifies the attribute of the boarding floor, which is the floor on which the destination floor registration device 2 or the landing call registration device 6 is installed, as the attribute of the user, and outputs the registered destination call or landing call and the attribute of the user to the car assignment portion 12 (step S104).
That is, when it is determined in step S102 that the operated registration device is the hall call registration device 6, the hall call registration device 6 is installed in a hall of a floor other than the entrance floor, and therefore the process always proceeds to step S104.
For example, when a hall call in the downward direction is registered by the hall call registration device 6 provided on the 6 th floor, the attribute c set for the 6 th floor on which the hall call registration device 6 is provided is recognized as the attribute of the user, and the attribute of the user becomes the attribute c.
Next, the car assignment unit 12 determines whether or not there is an assignable car, that is, whether or not there is a car with a different attribute in all cars, with respect to the attribute of the newly input user (step S105).
Here, when a user is assigned to a certain car and another user takes the elevator while traveling from the elevator-taking floor to the elevator-descending floor, it is determined that the user takes the elevator together. However, when a hall call is registered, since the landing floor is unknown, the end floor in the direction of the hall call is treated as the landing floor.
For example, in the case where a hall call in the upward direction is registered by the hall call registration device 6 provided at the 4 th floor in the building shown in fig. 4, the attribute of the user becomes the b attribute. At this time, when the car assigned with the 6 th floor from the 1 st floor arrives at the 4 th floor, the user with the attribute of c already rides in the elevator, and thus the car will ride on the user with the attribute different from that of c. In addition, since the user assigned with the attribute a is scheduled to descend from the 3 rd floor, the user does not get on the floor with the user having the attribute different from that of the user assigned with the departure floor of 1 st floor and the destination floor of 3 rd floor.
In the building shown in fig. 4, when a hall call in the downward direction is registered by the hall call registration device 6 provided at the 5 th floor, the attribute of the user is the b attribute. At this time, when the car in which the hall call in the downward direction from the floor 3 is registered reaches the floor 3, the user with the attribute a is expected to ride the car, and thus the car will ride the user with the attribute different from that of the user. In addition, when a hall call in the downward direction is registered by the hall call registration device 6 provided on the 5 th floor, the user having the B-attribute cannot recognize whether the hall call is going down on the 4 th floor or the 1 st floor at the time when the hall call is registered, and therefore the B-floor, which is the end floor in the downward direction, is set as the down floor.
When it is determined in step S105 that all the cars will be the same as the users having different attributes (that is, yes), the car assignment section 12 assigns the car that is the empty car first from all the cars, but controls the car so as to avoid the same multiplication: the car is operated in a straight line until the car becomes empty, and the car is allocated after the car becomes empty (step S106).
On the other hand, if it is determined in step S105 that the condition that the users having different attributes will be present in all the car operators is not satisfied, that is, if there are assignable car operators (that is, no), the car assignment unit 12 assigns the most suitable car operator from among the car operators other than the car operators that will be present in the same car with the users having different attributes by using a normal assignment algorithm (step S107).
Next, the user recognition unit 11 determines again whether or not the operated registration device is the destination floor registration device 2 installed on the entrance floor (step S108).
If it is determined in step S108 that the registration device is the destination floor registration device 2 installed at the entrance floor (that is, yes), the car assignment section 12 outputs the attribute of the user to the notification device 5 located near the newly assigned elevator, and the notification device 5 performs notification corresponding to the input attribute of the user (step S109), and the processing of fig. 5 is ended. Here, the notification device 5 is, for example, a display of characters, and displays characters such as "in operation for female exclusive" when the attribute of the user corresponds to the floor for female exclusive.
On the other hand, if it is determined in step S108 that the registration device is not the destination floor registration device 2 installed on the entrance floor (i.e., no), the car assignment section 12 determines whether or not the registered destination floor is a floor other than the entrance floor and has a different attribute from the attribute of the user (step S110).
When it is determined in step S110 that the registered destination floor is a floor other than the entry floor and is different from the attribute of the user (that is, yes), the car assignment unit 12 outputs an entry floor return command to the operation control unit 14, and the operation control unit 14 performs the following control: the car is caused to travel to the entry floor, not the destination floor, and after reaching the entry floor, the landing door 1 is temporarily opened, and the car is caused to travel to the destination floor (step S111), and the process of fig. 5 is ended.
For example, in the building shown in fig. 4, when a hall call in the downward direction is registered by the hall call registration device 6 provided at the 6 th floor, after the car reaches the 6 th floor, even if 3 rd floors are registered as destination floors by the car call registration device 7, the car passes through the 3 rd floors without going straight, and once opens and closes the doors at the 1 st floor, the car reaches the 3 rd floors again.
On the other hand, if it is determined in step S110 that the registered destination floor is a floor other than the entrance floor and the condition for the user attribute is not satisfied (i.e., no), the process of fig. 5 is terminated as it is.
In addition, when the configuration of the ride rule setting unit 13 shown in fig. 3 is not omitted, steps S105 to S107 shown in fig. 5 may be replaced with steps S201 to S203 shown in fig. 6.
In fig. 6, first, the car assignment section 12 refers to the ride sharing rule set by the ride sharing rule setting section 13, and determines whether or not assignment is impossible due to the ride sharing rule in all cars (step S201).
When it is determined in step S201 that assignment cannot be performed due to the sharing rule among all the cars (that is, yes), the car assignment unit 12 assigns a car that is the empty car first from among all the cars, but controls the car so as to avoid the sharing: the car is operated in a straight line until the car becomes empty, and after the car becomes empty, the car is allocated (step S202), and the process of fig. 6 is ended.
On the other hand, when it is determined in step S201 that the condition that the assignment is not possible due to the copping rule among all the car nos, that is, there are car nos that can be assigned (that is, no), the car assignment unit 12 assigns the most suitable car nos among the car nos other than the car nos that can not be assigned due to the copping rule by using a normal assignment algorithm (step S203), and ends the processing of fig. 6.
However, when a plurality of users having different attributes ride on the stairs in step S203, the process of step S109 shown in fig. 5 may be omitted.
Fig. 7 is an explanatory view exemplifying an operation of an elevator group control device according to embodiment 1 of the present invention. Fig. 7 shows an example of the operation of the group control device for elevators in the building shown in fig. 4. That is, the building is a 7-story building from B-6 floors, the entry floors from B-1 floor and 3 floors are attributes a, the attributes B from 4 floors and 5 floors and the attributes c from 6 floors. The elevator is 3 machines No. A, B, C.
In fig. 7, it is assumed that the a-type machine takes the elevator by 2 users having a attribute on the B-floor, the B-type machine is an empty car on the 5-floor, and the C-type machine takes the elevator by 1 user having C attribute on the 3-floor. At this time, when the destination floor 3 is registered in the floor 1, it is determined that the user is the a attribute, and thus the a-number machine or the B-number machine can be assigned. Therefore, the machine a closer to layer 1 is assigned.
Next, when 4 floors and 5 floors are registered as destination floors in floor 1, it is determined that the user is B-attribute, and therefore only the B-machine can be assigned. Thus, machine number B is assigned.
Finally, when a hall call in the downward direction is registered at floor 6, the B-machine is already scheduled to be taken by the B-attribute user, but the B-attribute user can be assigned to the B-machine or the C-machine because the B-attribute user gets off before reaching floor 6. While machine C is traveling in the downstream direction, it is also more likely to arrive earlier than machine B, and machine C is assigned.
Note that, although the notification device 5 is a display in fig. 1, the notification may be performed by voice, and may be omitted. In fig. 1, the operation control unit 14 may be omitted.
As described above, according to embodiment 1, when a destination floor is registered by a destination floor registration device provided in a hall of an entrance floor, which is a floor where an entrance of a building is provided, an attribute of the floor of the destination floor is recognized as an attribute of a user, and when a destination floor or a hall call is registered by a destination floor registration device or a hall call registration device provided in a hall of a floor other than the entrance floor, an attribute of a floor other than the entrance floor on which a destination floor registration device or a hall call registration device is provided is recognized as an attribute of a user, and a car is assigned to the user based on the recognized attribute of the user.
Therefore, without performing personal authentication, the co-riding of users having different attributes can be eliminated, and the movement of the users to an unauthorized floor can be suppressed.
Further, it is no longer necessary to input an ID number or hold a card or tag storing ID information in order to identify the attribute of the user, and the user's convenience is improved. Further, since an authentication unit for performing personal authentication is not required, the system configuration becomes simple and the cost can be reduced.
The car assignment unit assigns different cars to each of a plurality of users whose attributes of the users identified by the user identification unit are different from each other. Therefore, it is possible to assign different cars to the user traveling to the female-only floor and the other users and the like with a simple configuration without using the authentication means.
The car assignment unit allows assignment of the car to users having different attributes when the attributes of the users identified by the user identification unit are the same for all of the users or when a plurality of users having the same attributes are riding in the car. Therefore, the operation efficiency of the elevator can be improved.
The system further includes a boarding rule setting unit that sets the number of persons having the same attribute for allowing assignment of the same car to a plurality of users having different attributes. Therefore, it is possible to set an allowance condition that allows the same car to be assigned for each attribute of the user.
The elevator system further includes a notification device that is provided at a landing on the entry floor and notifies the attribute of the user when the car assigned by the car assignment section is a car assigned to a user with a single attribute. Therefore, it is possible to suppress the passengers having significantly different attributes from riding in the car.
The elevator system further includes an operation control unit that causes the car to travel to the entry floor before the car stops at the destination floor having the different attribute, and causes the car to travel to the destination floor after the car reaches the entry floor and the landing door is temporarily opened. Therefore, the same safety as that of forced stopping of the hall floor can be ensured.