JP2011046495A - Group supervisory operation device of elevator - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a group supervisory operation system for securing convenience of passengers in crowded time, and preventing confusion in a landing hall. <P>SOLUTION: This group supervisory operation device includes a landing hall destination call registering device for registering a destination story designated by operation of a landing hall destination story button arranged in the landing hall as a destination call, an operation command device for allocating the registered destination call of an elevator group to an optimal car, a car call operation panel arranged in a car of respective cars and accepting car call operation, a car call mask control device for generating car call mask information for controlling car call registration with every story in the car of the respective cars, and a car call registering device for registering a car call when car call registration of the destination story is permitted by being collated with the car call mask information held in the car call mask control device by inputting a car call signal from the car call operation panel. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to an elevator group management apparatus having a landing destination floor button that can directly designate a destination floor in an elevator hall.

  In general elevators, hall call buttons are installed in the elevator hall (depot), and when the hall call button is pressed, the elevator arrives, gets into the car, and the car call is registered. On the other hand, the elevator destination hall button can be set directly at the elevator hall to save the trouble of registering the destination floor when the passenger gets in the car and at the same time operating the elevator. A group management system with improved efficiency has been put into practical use. This type of group management system is called DCS (Destination Control System) group management, which collects users by destination floor and realizes shortening of the time required for one round of the car from rising to lowering to the reference floor. Thus, the transportation capacity and waiting time are improved (see, for example, Patent Document 1).

Special table 2009-515797

  In the above-mentioned elevators under the control of the DCS group, it is possible to get on the unassigned number of landing destination floor calls due to congestion on crowded floors such as the standard floor for working hours and the cafeteria floor for lunch hours.

  In addition, passengers who are unfamiliar with the elevators under the control of the DCS group may be wrongly boarded. In such a case, passengers who erroneously board the unassigned unit cannot register a car call on the operation panel in the elevator, so they can either get off from the car to the hall or go directly to the nearest floor and change the elevator. is required. When getting off, confusion occurs on the hall side, but changing elevators is not convenient for the user.

  Therefore, the present invention has been made in view of the above points, and an object thereof is to provide an elevator group management control device capable of ensuring the convenience of passengers at the time of congestion and preventing confusion at a landing. To do.

  According to one aspect of the present invention, there is provided an elevator group management control device that controls the operation of a plurality of elevators, and registers a destination floor designated by an operation of a landing destination floor button provided at a landing as a destination call. A landing destination call registration device, an operation command device that assigns a destination call registered in the elevator group to the optimal car, a car call operation panel that is installed in each car and accepts car call operations, and a car for each car The car call mask control device for generating car call mask information for controlling car call registration for each floor in the car and the car call signal from the car call operation panel are inputted and held in the car call mask control device. A car call registration device for checking the car call mask information and registering the car call if the car call registration on the destination floor is permitted. Group control device for an elevator according to symptoms is provided.

  Further, according to another aspect of the present invention, the car call mask control device performs a logical sum of a destination floor car call assignment in which a car call is assigned to each destination floor and a destination floor call registered on that floor. An elevator group management control device is provided, which takes (OR) and controls car call registration of each unit.

  ADVANTAGE OF THE INVENTION According to this invention, the convenience of the passenger at the time of congestion can be ensured, and the confusion at a landing can be prevented.

It is a figure for demonstrating the structure of the elevator which has a hall destination floor button with which the group management apparatus which concerns on this embodiment is applied. It is an enlarged view of a landing destination floor registration apparatus. It is a block diagram which shows schematic structure of the group management apparatus which concerns on this embodiment. It is a flowchart which shows the flow of the control processing in the group management apparatus which concerns on this embodiment. It is a schematic diagram of each table used with a group management apparatus. It is a schematic diagram of a car call registration table. It is a schematic diagram of a car call registration table. It is a figure explaining the relationship of each table used in this embodiment.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In addition, in each figure, the same code | symbol is attached | subjected about the same location and the overlapping description is abbreviate | omitted.

  First, before describing an embodiment of the present invention, an elevator having a landing destination floor button will be described.

  FIG. 1A is a diagram for explaining a configuration of an elevator having a landing destination floor button to which the group management apparatus according to the present embodiment is applied. Here, as an example, a configuration is shown in which the number of groups is composed of four units from Unit A to Unit D. In FIG. 1A, 1a to 1d are landing doors on specific floors of Units A to D. Here, the specific floor is a floor on which elevator users are concentrated, such as a standard floor for working hours or a cafeteria floor for lunch hours. Destination floor display devices 2a to 2d indicating the destination floors of the respective units on the landing are arranged on the upper right wall surfaces of the landing doors 1a to 1d. Furthermore, hall lanterns 3a to 3d are installed above the destination floor display devices 2a to 2d. The hall lanterns 3a to 3d present to the user whether to move (up) from a specific floor to an upper floor or to move to a lower floor (down). At the landing, landing destination floor registration devices 4 and 5 are installed for the user to register the destination floor. For example, in the group management of 3 groups, it can be said that even one landing destination floor registration device is realistic, but in the group management of more than 4 groups, since it takes charge of the input work of many users, it is convenient. Therefore, it is preferable to install a plurality of units.

  FIG. 1B is an enlarged view of the landing destination floor registration device. As shown in FIG. 1B, the landing destination floor registration device 4 includes a landing destination floor registration button 4a, and a display unit 4b for displaying an explanation and an assigned machine for operating the landing destination floor registration to the user. ing. The landing destination floor registration device 5 has the same configuration.

  In such a configuration, the user inputs a desired destination floor from the landing destination floor registration devices 4 and 5 at the landing. When the destination floor is registered, the optimum number machine responding to the destination floor is displayed on the destination floor display devices 2a to 2d of the corresponding number machine. The user of the hall confirms the display on the destination floor display devices 2a to 2d, waits in front of the corresponding unit, the unit decelerates, and the hall lanterns 3a to 3d of the corresponding unit blink. In addition, the destination floor call is automatically registered as a car call for the corresponding car.

  FIG. 2 is a configuration diagram illustrating a schematic configuration of the group management apparatus according to the present embodiment. The group management device includes an operation command device 11, a landing destination call registration device 10, a car call mask control device 9, car call registration devices 8a to 8d, and car call operation panels 7a to 7d.

  The operation command device 11 determines an optimal allocation number for a destination call generated by an elevator group composed of Units A to D. The landing destination call registration device 10 is connected to the operation command device 11 and registers the destination floor designated at the landing as a destination call. The landing destination call registration device 10 is connected to landing destination floor registration devices 4 and 5.

  The car call mask control device 9 is connected to the operation command device 11 and performs a car call mask switching process. Here, the car call mask is mask information for controlling car call registration on the destination floor in the elevator car.

  The car call operation panels 7a to 7d are installed in the car and receive a car call operation by a passenger.

  The car call registration devices 8a to 8d receive the car call signals from the car call operation panels 7a to 7d, collate with the car call mask held in the car call mask control device 9, and register the car call on the destination floor. If this is permitted, the car call is registered.

  In such a configuration, the landing user operates the landing destination floor registration button 4a of the landing destination floor registration device 4 and inputs the destination floor. The input destination floor is registered in the landing destination call registration device 10. The registered destination floor is transmitted from the landing destination call registration device 10 to the operation command device 11 as a destination floor call signal. In the operation command device 11, the optimum car number for the registered destination floor call is determined, and in the car call mask control device 9, car call mask information is generated in order to determine whether or not car call registration for each floor is possible. Is done. Under the control of the car call mask control device 9, the destination floor calls are registered in the car call registration devices 8a to 8d.

  Next, processing in the county management system configured as described above will be described in the case of four groups and four floors.

  First, Fig. 4 shows whether the destination floor car call assignment table CCAT (n), destination floor car call master table CCMT (n), and the destination floor car call registration on each floor used in the county management device. It is a schematic diagram of the car call service permission table CSFT (i) shown. Here, n is an index indicating a floor, and a CCAT (n) table and a CCMT (n) table are generated for each floor. i is an index indicating a machine, and a CSFT (i) table is generated for each machine. The car call service permission table CSFT (i) is updated by the car call mask control device 9.

  The destination floor car call allocation table CCAT (n) is composed of 4 bytes corresponding to 4 units managed by the units A to D. In the destination floor car call assignment table CCAT (n), the <7> to <4> bits of each byte correspond to 1K (first floor destination call) to 4K (4th floor destination call), respectively. In the example shown in FIG. 4, the fourth floor is assigned as the destination floor in Unit A, the second floor in Unit B, and the third floor in Unit D.

  In the destination floor car call master table CCMT (n), a logical OR value of each byte corresponding to the first floor of the destination floor car call assignment table CCAT (n) is set. In the example shown in FIG. 4, flags are set in the <4> bit, the <5> bit, and the <6> bit.

  Here, since the 4th floor is taken as an example, the car call service permission table CSFT (i) is composed of a 4-byte area for each unit. Each byte corresponds to 1K-4K. In the example shown in FIG. 4, the cars A, B, and D can call a car on the second floor, the third floor, and the fourth floor, and the car call is not permitted on the first floor. On the other hand, at C, car calls are not allowed on all floors.

  Based on the table configuration shown in FIG. 4, the process flow of the county management system will be described with reference to the flowchart shown in FIG.

  First, in the operation command device 11, it is determined whether or not there are a plurality of destination call registrations on the same floor (step A10). If YES, the operation command device 11 determines whether or not the degree of congestion such as the next working hour is high (step A11). In the present embodiment, as an example, it is determined whether or not the degree of congestion is high depending on whether or not it is a working hour. If it is a working time zone, the destination floor registration of other units on that floor is permitted to the unassigned unit on the corresponding floor when it arrives (step A12). The process of step A12 is executed by the operation command device 11 and the car call mask control device 9.

  As shown in Fig. 4, the CCAT (n) table is registered as a car call for the 4th floor for Unit A, the 2nd floor for Unit B, and the 3rd floor for Unit D. The CCMT (n) table The OR value is set in the 4th to 6th bits. Based on these tables, a car call service permission table CSFT (i) is set for each unit. Therefore, for Cars A, B and D, car calls can be registered on the 2nd, 3rd and 4th floors, respectively. On the other hand, car call registration on all floors is not possible for Unit C.

  As described above, under the situation where each table value is set, it is next determined in the non-assigned car whether the car call of the destination floor of the other car is pushed on the corresponding floor (step A13). The process of step A13 is executed by the operation command device 11, the car call mask control device 9, and the car call registration devices 8a, ..., 8d. If a passenger who has accidentally boarded an unassigned car on that floor is not registered, the car call service permission table CSFT (i) for each car will already have A, 2nd, 3rd, and 4th floors. Because it is set to Units B, B, and D, car call registration is possible. When the destination floor car call is pressed, the car call is additionally registered at the unassigned unit (step A14). The process of step A14 is executed by the operation command device 11, the car call mask control device 9, and the car call registration devices 8a, ..., 8d. Next, the information is additionally displayed on the destination floor display devices 2a to 2d of the hall (step A15). Next, in the operation command device 11, it is determined whether or not the series of processes described above has been completed for all floors (step A16). If NO in step A10, step A11, or step A13, the process immediately proceeds to step A16.

  Next, table processing when car call registration is performed will be described. 5 and 6 are schematic diagrams of the car call registration table CCRT (i). Here, i is an index indicating the number machine, and a table is generated for each number machine. The car call registration table CCRT (i) is updated by the car call mask control device 9. FIG. 5 shows a state where the destination floor car call registration is normally performed, and FIG. 6 shows a registration acceptance state when the destination floor car call is pressed.

  Under such circumstances, for example, when a passenger who wants to go to the third floor of Unit A erroneously gets on the car, the passenger presses the car call button on the third floor of the destination floor. The CSFT (A) table shown in Fig. 4 has already been granted service on the 2nd to 4th floors. If a passenger who has boarded the car pushes the car call button on the 3rd floor, the CCRT (A) shown in Fig. 6 Data corresponding to the third floor is set in the table, and the car call registration on the third floor becomes possible.

  Similarly, if a passenger who wants to go to the 4th floor in Unit D gets on board wrongly, the service of the 2nd to 4th floors is permitted at the CSFT (D) table shown in FIG. 4, and the CCRT (D ) The data corresponding to the fourth floor is set in the table, and the car call registration on the fourth floor becomes possible.

  FIG. 7 is a diagram for explaining the relationship between the tables used in the present embodiment. FIG. 7 shows processing steps related to each table.

  As described above, according to the present embodiment, in the crowded floor such as the standard floor in the working hours zone or the cafeteria floor in the lunch hour zone, there was an erroneous boarding on the unassigned number of the landing destination floor call due to the congestion. If multiple destination floors are registered on that floor, unassigned units that arrive on that floor will be allowed to register multiple destination floor calls on that floor as serviceable floors. Since the elevator user can go to a predetermined destination floor and effectively deal with erroneous boarding at the time of congestion, the convenience of passengers can be ensured and confusion at the landing can be prevented.

  Note that the present invention is not limited to the above-described embodiments as they are, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. Moreover, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above embodiments. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, constituent elements over different embodiments may be appropriately combined.

1a ~ 1d ... landing door
2a-2d ... Destination floor display device
3a-3d ... Hall lanterns 4, 5 ... Landing destination floor registration device 4a ... Landing destination floor registration button 4b ... Display
7a-7d ... Cage call operation panel
8a-8d ... car call registration device 9 ... car call mask control device 10 ... landing destination call registration device 11 ... operation command device

Claims (5)

An elevator group management control device for controlling the operation of a plurality of elevators,
A landing destination call registration device for registering a destination floor designated by the operation of a landing destination floor button provided at the landing as a destination call;
An operation command device for assigning the registered destination call of the elevator group to the optimal unit;
A car call operation panel that is installed in the car of each unit and accepts car call operations;
A car call mask control device for generating car call mask information for controlling car call registration for each floor in the car of each unit;
The car call signal from the car call operation panel is input, checked with the car call mask information stored in the car call mask control device, and if the car call registration on the destination floor is permitted, the car call A car call registration device to register
An elevator group management control device comprising:   The car call mask control device takes the logical sum (OR) of the destination floor car call assignment to which the car call is assigned for each destination floor and the destination floor call registered on that floor, and registers the car call for each car. The elevator group management control apparatus according to claim 1, wherein:   2. A non-assigned unit that is not assigned a service to a specific floor is allowed to register a car call registration of a destination floor of another unit on that floor when the non-assigned unit arrives at the corresponding floor. Or the elevator group management control apparatus of Claim 2.   If multiple destination floors are registered on a crowded floor during peak hours, allow a non-assigned unit that has arrived at the crowded floor to register a car call for multiple destination floors on that floor. The elevator group management control device according to any one of claims 1 to 3.   The elevator group management control device according to claim 4, wherein the crowded floor in the peak time zone is a reference floor in a work hour zone and a cafeteria floor in a lunch hour zone.

Images