JP7451661B1 - Elevator control device, elevator control method and program - Google Patents

Abstract

[Problem] To improve the operating efficiency of an elevator while avoiding co-driving between users and autonomous vehicles. An elevator control device according to an embodiment is an elevator control device that controls calls for two cars connected vertically in an elevator hoistway. a reception unit that receives call information as a call including a type indicating whether the vehicle is a car or a departure floor; and a control unit that determines which of the two cars to place the person and the autonomous mobile body and allocates the car. [Selection diagram] Figure 2

Description

Embodiments of the present invention relate to an elevator control device, an elevator control method, and a program.

BACKGROUND ART Among elevators that use cars for both autonomous mobile objects such as robots and human users, so-called double-deck elevators in which two cars are connected vertically have been known. In such a double-deck elevator, a user can be placed in one of the upper and lower cars, and an autonomous mobile object can be placed in the other.

In addition, in elevators with a single car that can be used by both autonomous vehicles and users, group management control is used to operate exclusively for autonomous vehicles, in order to avoid contact between autonomous vehicles and users. Techniques for preventing autonomous mobile bodies and users from riding in the same car are also known.

International Publication 2018/066049 International Publication 2020/230305

However, in the elevator system described in Patent Document 1, the basic method is to place a person in one car and an autonomous mobile object in the other car. The call will not be answered and the autonomous vehicle will be unable to use the elevator. Furthermore, when autonomous mobile bodies are placed in both cars, they will not respond to a person's call to the platform, and the person will not be able to use the elevator. For this reason, in cases where there are multiple cars, there is a problem in that it is not possible to flexibly switch whether the upper or lower car is to be used by a user or by an autonomous mobile object.

Furthermore, the elevator system described in Patent Document 2 does not assume a double-deck elevator, and when a person is placed in one car and an autonomous mobile object is placed in the other car, Elevator operating efficiency is affected, such as long waiting times for users due to long boarding and alighting times, and inefficient car allocation due to not considering allowing passengers to board and alight from the upper and lower cars at the same time. Sometimes things got worse.

The elevator control device of the embodiment is an elevator control device that controls calls for two cars connected vertically in an elevator hoistway, and the elevator control device controls calls for two cars connected vertically in an elevator hoistway, and the elevator control device controls calls for two cars connected vertically in an elevator hoistway. a receiving unit that receives call information including a type indicating whether it is an autonomous mobile object and a departure floor as a call; and a control unit that determines which of the two cars to place the mobile object in and allocates the car.

FIG. 1 is a diagram showing an example of the overall configuration of an elevator control system according to an embodiment. FIG. 2 is a block diagram showing an example of the functional configuration of each device of the elevator control system according to the embodiment. FIG. 3 is a schematic diagram showing an example of the configuration of the operation panel according to the embodiment. FIG. 4 is a schematic diagram showing an example of the configuration of the destination floor registration device according to the embodiment. FIG. 5 is an explanatory diagram showing an example of the data structure of user call information according to the embodiment. FIG. 6 is an explanatory diagram showing an example of the data structure of robot call information according to the embodiment. FIG. 7 is an explanatory diagram showing an example of the data structure of car operation information according to the embodiment. FIG. 8 is a flowchart illustrating an example of the procedure of elevator control processing according to the embodiment. FIG. 9 is a flowchart illustrating an example of the procedure of the first process according to the embodiment. FIG. 10 is a flowchart illustrating an example of the second processing procedure according to the embodiment.

Embodiments will be described below with reference to the drawings.
(Embodiment)
FIG. 1 is a diagram showing an example of the overall configuration of an elevator control system according to an embodiment.
As shown in FIG. 1, the elevator control system 100 of this embodiment includes a plurality of elevators from No. 1 to No. N (N is an integer). In one elevator, as shown in FIG. 1, the elevator control system 100 includes two cars 1A and 1B connected vertically, a control device 10, a destination floor call device 30, and a plurality of hall call devices 50. It is mainly equipped with. A plurality of landing call devices 50 are provided for each landing on each floor.

FIG. 2 is a block diagram showing an example of the functional configuration of each device of the elevator control system 100 according to the embodiment. In FIG. 2, one elevator and one landing are shown for convenience of explanation.

As shown in FIG. 2, the elevator control system 100 mainly includes a control device 10, a hall call device 50, and a destination floor call device 30. The elevator controlled by the elevator control system 100 includes two cars 1A and 1B, a drive device 2, a counterweight 3, a rope 4, and the like. The control device 10 and the landing call device 50 are connected by wire or wirelessly so that various signals can be exchanged. Further, the control device 10 and the destination floor calling device 30 are connected by wire or wirelessly so that various signals can be exchanged.

As shown in FIG. 2, the two cars 1A and 1B of this embodiment are vertically connected, and are a so-called double deck type car. The two cars 1A and 1B are connected and moved up and down in a hoistway (not shown), and the users or robots boarding the cars 1A and 1B are transported to other floors at landings provided on each floor. do. Here, when the cars 1A and 1B are not distinguished, they are collectively referred to as the car 1.

The car 1 and the counterweight 3 are connected by a rope 4. The rope 4 is spanned over the drive device 2. The drive device 2 is, for example, a hoist or the like, and by driving the drive device 2, the car 1 can be moved up and down within the hoistway.

The landing call device 50 is a device that receives call information as a landing call from a human user or the robot 400, and transmits the call information to the control device 10. An operation panel 320 and a destination floor registration device 330 are connected to the platform call device 50.

The operation panel 320 is provided on the wall of the boarding area and accepts boarding calls from users.
FIG. 3 is a schematic diagram showing an example of the configuration of the operation panel 320 according to the embodiment. As shown in FIG. 3, the operation panel 320 mainly includes two push buttons 321 and a liquid crystal display section 323.

The two push buttons 321 are pressed by the user to instruct upward and downward destination directions. When the push button 321 is pressed, a push signal corresponding to the direction is sent to the hall call device 50.
The liquid crystal display section 323 is a display device that displays the position of the car 1 and the like. The example in FIG. 3 shows that the car 1 is traveling near the third floor.

In this embodiment, the push button 321 is used to indicate the destination direction, but instead of the push button 321, a non-contact sensor section may be used to indicate the destination direction. Further, the push button 321 and the non-contact type sensor unit may be configured as an integrated type.

Returning to FIG. 2, the destination floor registration device 330 is a device for the user to specify the destination floor at the landing. The destination floor registration device 330 is provided at the landing.
FIG. 4 is a schematic diagram showing an example of the configuration of the destination floor registration device 330 according to the embodiment. As shown in FIG. 4, the destination floor registration device 330 mainly includes a plurality of push buttons 331 and a liquid crystal display section 333.

The plurality of push buttons 331 are pressed by the user to indicate the destination floor. In the example of FIG. 4, it is possible to specify the first to ninth floors. When the push button 331 is pressed, a press signal corresponding to the destination floor is sent to the hall call device 50.
The liquid crystal display section 333 is a display device that displays the position of the car 1 and the like. The example in FIG. 4 shows that the car 1 is traveling near the third floor.

In this embodiment, the destination floor is indicated by the push button 331, but instead of the push button 331, the destination floor may be indicated by a non-contact type sensor section. Further, the push button 331 and the non-contact type sensor unit may be configured as an integrated type.

Returning to FIG. 2, the robot 400 calls the car 1 by transmitting robot call information to the landing call device 50. Robot 400 is an example of an autonomous moving body.

The hall call device 50 mainly includes a detection section 51 and a communication section 54, as shown in FIG. The detection unit 51 detects when the user presses the push button 321 on the operation panel 320 or the push button 331 on the destination floor registration device 330 by receiving a press signal. Then, the detection unit 51 generates user call information from the press signal.

Here, user call information will be explained. User call information is an example of call information.

FIG. 5 is an explanatory diagram showing an example of the data structure of user call information according to the embodiment.
As shown in FIG. 5, the user call information includes the type of sender, the departure floor, and the destination floor. Since the detection unit 51 generates user call information by receiving a press signal from the operating panel 320 or the destination floor registration device 330, it sets "person" as the type of the sender.

The detection unit 51 sets the floor where the landing call device 50 is installed on the departure floor, and sets the destination direction according to the pressed button. If the detection unit 51 detects a press from the operation panel 320, the destination floor is not specified, and therefore sets NULL to the destination floor. When detecting a press from the destination floor registration device 330, the detection unit 51 sets the floor number corresponding to the press signal as the destination floor, and sets the destination method based on the vertical relationship between the departure floor and the destination floor. . In this way, the detection unit 51 generates user call information.

Returning to FIG. 2, the communication unit 54 controls communication with the control device 10 and the robot 400. Specifically, the communication unit 54 transmits the user call information generated by the detection unit 51 to the control device 10. Further, the communication unit 54 receives robot call information as a call from the robot 400 and transmits the received robot call information to the control device 10. Furthermore, the communication unit 54 receives assignment information that is the assignment result for the car 1 from the control device 10 .

Here, robot call information will be explained. Robot call information is an example of call information.

FIG. 6 is an explanatory diagram showing an example of the data structure of robot call information according to the embodiment.
As shown in FIG. 6, the user call information includes the type of sender, departure floor, destination floor, robot size, and boarding/alighting time. In the robot call information, "robot" is set as the type of the sender. The landing floor where the robot 400 is located is set as the departure floor. The floor number of the destination floor of the robot 400 is set in the destination floor.

The size of the robot 400 is set in the robot size. The time taken for the robot 400 to get on and off the car 1 is set as the getting on/off time.

Returning to FIG. 2, the destination floor calling device 30 receives a call for the user's destination floor from an operation panel (not shown) in the car 1. Further, the destination floor calling device 30 transmits car operation information to the control device 10.

Here, car operation information will be explained.
FIG. 7 is an explanatory diagram showing an example of the data structure of car operation information according to the embodiment. As shown in FIG. 7, the car operation information is composed of operation information for the car 1A and operation information for the car 1B.

The operation information for the car 1A is composed of the upper car position, robot/person, and current assignment. The upper car position is set to the floor at which the car 1A is traveling. The robot/person field is set to indicate whether the person riding in the car 1A is the robot 400 or the user. The current allocation indicates whether car 1 is allocated or not. If the current allocation is "none", this indicates that this car 1 is an empty car.

The operation information for the car 1B is composed of the lower car position, robot/person, and current assignment. The floor at which the car 1B is traveling is set as the lower car position. The robot/human and current assignments are the same as the operation information for the car 1A.

Returning to FIG. 2, the control device 10 includes a control section 11, a communication section 12, a group management control section 14, and a storage section 13, and controls the entire elevator. The control device 10 is connected to the drive device 2 by wire or wirelessly so that various signals can be sent and received. The control device 10 is an example of an elevator control device.

The control unit 11 performs call registration when there is a landing call from a user at a landing, or when a destination floor call is received from a user in the car 1, or the like. The control unit 11 may store the contents of the call registration in the storage unit 13.

Here, a platform call is an operation performed by a user of a platform in order to have the car 1 headed for either the upper or lower destination arrive at the platform. A platform call may also be referred to as a destination call. A landing call is performed by transmitting user call information and robot call information. Further, the destination floor call is an operation performed by the user in the car 1 to direct the car 1 to a desired destination floor.

The control unit 11 registers the received landing call and the received destination floor call.
When the group management control unit 14 determines that the car 1 is to be assigned to the car 1, the control unit 11 causes the car 1 to respond to the hall call. Then, the control unit 11 drives the drive device 2 to direct the car 1 assigned to the destination direction registered in the landing call registration to the landing where the landing call was made.

Further, the control unit 11 causes the car 1 to respond to the destination floor call according to the contents of the destination floor call registration. That is, the control unit 11 drives the drive device 2 to direct the car 1 scheduled to travel to the destination floor registered in the destination floor call registration. Furthermore, when the car 1 arrives at a predetermined floor, the control unit 11 opens and closes the doors of the car 1 and the landing area.

The control unit 11 of this embodiment further includes the following functions.
The control unit 11 allows the group management control unit 14 to communicate between the user and the robot 400 based on the user call information or robot call information received as the received landing call and the car operation information received from the destination floor call device 30. It is determined which of the two cars 1A and 1B the car should be placed in, and the cars 1A and 1B are allocated.

Specifically, when the control unit 11 receives robot call information as a landing call from the robot 400 from the landing call device 50, and when the received robot call information is longer than a predetermined fixed time, When a user is riding in one of the cars 1, the cars 1A and 1B are allocated so that the robot 400 that has transmitted the robot call information is not placed in the other car 1.

In addition, when the control unit 11 receives user call information as a hall call from a user from the hall call device 50, the control unit 11 determines that the boarding and alighting time of the robot 400 riding on one of the cars 1 is longer than a certain time. In this case, the other car 1 is assigned to the cars 1A and 1B so that it does not carry any passengers.

Furthermore, when the control unit 11 receives robot call information as a landing call from the robot 400 from the landing calling device 50, the control unit 11 is configured to control the robot when there is already a robot in one of the two cars 1A and 1B. 400, and if the door of car 1 opens at the same time on the departure floor or destination floor of robot 400 that sent the robot call information, the robot 400 that sent the robot call information is given the other car 1. assign.

The group management control section 14 cooperates with the control devices 10 of other cars via the communication section 12 to make a landing call based on the assignment result of the car 1 of the control section 11 as described above based on the assignment evaluation. Group management control is performed to allocate the car 1 closest to the landing area.

The communication unit 12 transmits the information to the platform call device 50 and the destination floor call device 30 when there is a platform call from a user of the platform, or when a destination floor call is received from a user in the car 1, etc. Obtained from etc. When the group management control unit 14 registers a hall call and assigns car 1, the communication unit 12 transmits the number of the assigned car 1 and the fact that the hall call has been registered to the hall call device 50. Send. The communication unit 12 also transmits various commands and the like from the control unit 11 to the car 1 and the like. The communication unit 12 is an example of a receiving unit.

The storage unit 13 stores various programs for causing the control device 10 to control the elevator. As described above, the storage unit 13 may store destination floor call registration, landing call registration, and the like.

Next, the hardware configuration of the elevator control system 100 according to this embodiment will be explained.
The control device 10 is configured as a computer including a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a storage device, and the like.

The ROM stores various programs related to elevator control, such as a control program and a call registration program. These programs stored in the ROM are read out and developed in the RAM, and the CPU executes these programs, thereby realizing the function of the control device 10 as an elevator control device.

By executing this call registration program by the CPU, the above-mentioned control section 11, communication section 12, group management control section 14, etc. are realized.

The platform call device 50 is configured as a computer including a CPU, ROM, RAM, and the like.

The ROM stores, for example, a landing call program related to accepting a landing call. The hall call program and the like stored in the ROM are read out, expanded to the RAM, and executed by the CPU, thereby realizing the detection unit 51, the communication unit 54, etc. of the hall call device 50.

The destination floor calling device 30 is configured as a computer including a CPU, ROM, RAM, and the like. The ROM stores, for example, a destination floor call program related to receiving a destination floor call. A destination floor call program, etc. stored in the ROM is read out, developed in the RAM, and executed by the CPU.

Here, the control program, call registration program, landing call program, destination floor call program, etc. are computer programs that are executable by a computer and have a computer-readable and non-transitional recording medium that includes a plurality of instructions related to elevator control. It is a product. The control program, call registration program, landing call program, destination floor call program, etc. have, for example, a module structure, and these modules are loaded onto the main storage device.

The control program, call registration program, landing call program, destination floor call program, etc. are provided, for example, stored in a recording medium or the like so as to be readable by a computer. The recording medium is, for example, a magnetic disk, an optical disk, a magneto-optical disk, or a flash memory. However, the control program, call registration program, platform call program, signal control program, etc. may be distributed by a server placed on a network, or may be configured to be downloadable, or may be provided by various other methods. may be done.

The elevator control program executed by the elevator control system 100 is mainly composed of a control program, a call registration program, etc. executed by the control device 10, and a landing call program, etc. executed by the landing call device 50. Ru.

Next, elevator control processing by the elevator control system 100 configured as above will be explained.
FIG. 8 is a flowchart illustrating an example of the procedure of elevator control processing according to the embodiment. The control unit 11 of the control device 10 determines whether call information, that is, user call information or robot call information has been received (S101). If the call information has not been received (S101: No), the control unit 11 waits to receive the call information.

When the control unit 11 receives the call information (S101: Yes), the control unit 11 determines the received call information (S103). If the received call information is user call information (S103: user), the control unit 11 executes the first process (S105). On the other hand, when the received call information is robot call information (S103: robot), the control unit 11 executes the second process (S107).

Here, the first process of S105 will be explained.
FIG. 9 is a flowchart illustrating an example of the procedure of the first process according to the embodiment. The first process is the process of allocating the car 1 when a user calls the car.

The control unit 11 sets the car 1 of its own car as a determination target, refers to the type of car operation information, and determines whether the robot 400 is using the car 1 to be determined (S201 ). Then, if the robot 400 is using the car 1 to be determined (S201: Yes), the control unit 11 determines that the car 1 is not to be assigned and evaluated (S207), and the process is called. Return to the original.

On the other hand, in S201, if the robot 400 is not using the car 1 to be determined (S201: No), the control unit 11 selects a car 1 of the same model as the car 1 to be determined, that is, if the car 1 is connected. It is determined whether the robot 400 is currently using the other car 1 and the time taken for the robot 400 to get on and off the car 1 is longer than a certain time (S203).

If the robot 400 is using the car 1 of the same model as the car 1 to be determined, and the time for getting on and off the car 1 of the robot 400 is longer than a certain time (S203: Yes), the control unit 11 determines that the car 1 is not subject to allocation evaluation (S207), and the process returns to the calling source.

On the other hand, in S203, the robot 400 is not using the car 1 of the same machine as the car 1 to be determined, or the robot 400 is using it, but the time taken to get on and off the car 1 of the robot 400 is less than a certain time. If so (S203: No), the control unit 11 determines that the car 1 is to be assigned and evaluated (S205), and the process returns to the calling source.

Next, the second process of S107 will be explained.
FIG. 10 is a flowchart illustrating an example of the second processing procedure according to the embodiment. The second process is the process of allocating the car 1 when the robot 400 makes a landing call.

The control unit 11 determines whether the car 1 of its own car is being used by a user, that is, by a person, by referring to the type of car operation information. (S301). Then, if the car 1 to be determined is in use by a person (S301: Yes), the control unit 11 determines that the car 1 is not to be subjected to allocation evaluation (S317), and the process is continued by the caller. Return to

On the other hand, in S301, if the car 1 to be determined is not in use by a person (S301: No), the group management control unit 14 inquires the group management control units 14 of all other cars, and It is determined whether or not the number of cars 1 used by the robot 400 among the cars 1 is greater than or equal to a certain number (S303). Here, the fixed number can be, for example, half the number of all the cars 1, but is not limited to this. In this way, it is determined whether or not the number of cars 1 used by the robot 400 is a certain number or more. This is to limit the number of cages that can be used by the robot 400 to prevent this from occurring. Therefore, if more than a certain number of cages are used for robots, only the cages that are already used for robot 400 are to be allocated.

Therefore, if the number of cars 1 used by the robot 400 is a certain number or more among the cars 1 of all cars (S303: Yes), the control unit 11 controls the current car operation information. With reference to the allocation, it is determined whether the car 1 to be determined is an empty car (S309). Then, if the car 1 to be determined is an empty car (S309: Yes), the control unit 11 determines that the car 1 is not to be subjected to allocation evaluation (S317), and the process returns to the calling source. .

In S303, if the number of cars 1 used by the robot 400 is less than a certain number among the cars 1 of all machines (S303: No), and in S309, the number of cars 1 to be determined is If the car 1 is not empty (S309: No), the control unit 11 refers to the boarding and alighting time of the robot call information and determines whether the boarding and alighting time of the car 1 of the robot 400 that made the call is longer than a certain time. (S305).

If the boarding and alighting time of the car 1 of the robot 400 that made the call is longer than a certain time (S305: Yes), the control unit 11 refers to the car operation information and selects the same car as the car 1 to be determined. It is determined whether or not a person is using the car 1, that is, the other connected car 1 (S311). If a person is using the car 1 of the same car as the car 1 to be determined (S311: Yes), the control unit 11 determines that the car 1 is not to be subjected to allocation evaluation (S317). , processing returns to the caller.

In S311, if the car 1 of the same car as the judgment target car 1 is not in use by a person (S311: No), the control unit 11 selects the car 1 of the same car as the judgment target car 1, That is, the robot 400 is using the other connected car 1, and the robot call information of both the robot 400 using the car and the robot 400 that made the call is the respective departure floor and destination floor. With reference to , it is determined whether the doors of the upper and lower cars 1A and 1B open simultaneously on the departure floor or destination floor of the robot 400 that made the call (S313).

When the robot 400 is using the car 1 of the same machine as the car 1 to be judged, and the doors of the upper and lower cars 1A and 1B open simultaneously on the departure floor or destination floor of the robot 400 that made the call. (S313: Yes), the control unit 11 sets the car 1 as a priority allocation target (S315), and the process returns to the calling source.

In S305, if the boarding and alighting time of the car 1 of the robot 400 that made the call is less than a certain time (S305: No), and in S313, the robot 400 transfers the car 1 of the same number as the car 1 to be determined. is not in use, or if the doors of the upper and lower cars 1A and 1B do not open at the same time on the departure floor or destination floor of the robot 400 that made the call (S313: No), the control unit 11 It is determined that car 1 is to be subjected to normal allocation evaluation (S307), and the process returns to the calling source.

In addition, in S303, if the cars 1 of all the car numbers are used by people and there is no car 1 that the robot 400 can use, the robot 400 is notified to call the platform again after a certain period of time has passed, or The control unit 11 may be configured to allocate a landing call to the robot 400 after an empty car is available.

Returning to FIG. 8, when the first process of S105 or the second process of S107 is completed, the group management control unit 14 selects the allocation evaluation target, the normal allocation evaluation target, and the priority allocation evaluation target determined by the control unit 11. Based on the evaluation result, the allocation of the car 1 is determined in cooperation with the group management control unit 14 of the control device 10 of the other car number (S109). The group management control unit 14 preferentially allocates car 1 to be evaluated for priority allocation among all cars. Here, if there are a plurality of cars 1 to be evaluated for priority allocation, the group management control unit 14 gives priority to the car 1 that has the closest boarding and alighting time for the robot 400.

As described above, in the present embodiment, the communication unit 12 of the control device 10 that controls the hall calls of the two cars 1A and 1B connected vertically in the elevator hoistway receives calls from the user or the robot 400. The control unit 11 receives call information including the type and departure floor indicating whether it is a robot or a robot 400, and based on the received call information and the car operation information of the cars 1A and 1B, It is determined which of the two cars 1A and 1B the user and the robot 400 should be placed in, and the cars 1A and 1B are allocated.

Therefore, according to the present embodiment, when both a user and the robot 400 use an elevator having two cars 1A and 1B connected vertically, the user and the robot 400 can avoid riding together. , the operating efficiency of elevators can be improved. Furthermore, in this embodiment, even if there are multiple cars as elevator cars, unlike the conventional technology, it is possible to flexibly switch whether the upper or lower cars are used by the user or the robot 400, and the elevator operation Efficiency can be further improved.

Specifically, in the present embodiment, when a call is received from the robot 400, the control unit 11 of the control device 10 controls whether one of the elevator cars If a user is riding in car 1, the car 1 is allocated so that the robot 400 that has transmitted the robot call information is not placed in the other car 1.

Further, when the control unit 11 receives a call from a user, if the boarding and alighting time of the robot 400 riding in one car is longer than a predetermined certain time, the other car 1 is not used. Allocate car 1 so that no one is allowed to board the car.

Therefore, according to the present embodiment, when both the user and the robot 400 use an elevator having two cars 1A and 1B connected vertically, the user has to take a long time to get on and off the robot 400. It is possible to avoid having to wait for a long time.

Furthermore, in this embodiment, when the control unit 11 of the control device 10 receives a call from the robot 400, if there is already another robot 400 in one of the two cars 1A and 1B, , and if the car doors open at the same time on the departure floor or destination floor of the robot 400 that made the call, the other car is assigned to the robot 400 that sent the robot call information.

Therefore, according to the present embodiment, when both a user and the robot 400 use an elevator having two cars 1A and 1B connected vertically, they are allowed to board and exit the two cars 1A and 1B at the same time. Therefore, the operation efficiency of the elevator can be further improved.

(Modified example)
Various modifications can be applied to the above embodiment.
For example, when a call specifying a destination floor is received from the destination floor registration device 330, which section is used by the user or the robot 400 for the car 1 based on the section between the departure floor and the destination floor? The control unit 11 and the group management control unit 14 may be configured to perform control to allocate the car 1 based on whether the car 1 is to be assigned.

Further, for example, when a camera or the like is provided to take an image of the boarding area and robot call information is received from the robot 400, the number of users waiting at the boarding area is detected from the captured image of the camera, and the number of users and the robot The control unit 11 may be configured to permit the user and the robot 400 to ride together in the car 1 based on the size of the robot in the call information. For example, if the number of users waiting at the platform is less than a certain number and the size of the robot 400 is less than a certain size, the control unit may allow the users and the robot 400 to ride together in the car 1. 11 can be configured.

Although several embodiments of the invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included within the scope and gist of the invention, as well as within the scope of the invention described in the claims and its equivalents.

1, 1A, 1B... Car, 2... Drive device, 3... Counterweight, 4... Rope, 10... Control device, 11... Control unit, 12... Communication unit, 13... Storage unit, 14... Group management control unit, 30... Destination floor call device, 50... Platform call device, 51... Detection unit, 54... Communication unit, 100... Elevator control system, 320... Operation panel, 321... Push button, 323... Liquid crystal display unit, 330... Destination floor registration Device, 331...Push button, 333...Liquid crystal display section, 400...Robot.

Claims (8)

An elevator control device that controls calls for two cars connected vertically in an elevator hoistway,
a receiving unit that receives call information as a call from a user or an autonomous mobile body, including a type indicating whether the user is the user or the autonomous mobile body and a departure floor;
Based on the received call information and the operation information of the car, it is determined which of the two cars the user and the autonomous mobile object should be placed in, and the car is assigned. a control unit;
Elevator control equipment with. The call information includes the time required for the autonomous mobile body to get on and off the car,
When the control unit receives the call from the autonomous mobile body, when the boarding and alighting time based on the received call information is longer than a predetermined time, and when the user is in one of the cars, , allocating the car so that the autonomous mobile object that has transmitted the call information is not placed in the other car;
The elevator control device according to claim 1. When the control unit receives the call from the user, if the boarding and alighting time of the autonomous mobile body riding in one car is longer than the predetermined time, the control unit is configured to: allocating the car so as not to board the user;
The elevator control device according to claim 2. The call information includes a departure floor and a destination floor,
When the control unit receives the call from the autonomous mobile object, the controller determines that there is already another autonomous mobile object in one of the two cars and that the call has been made. If car doors open simultaneously on the departure floor or the destination floor of the autonomous mobile body, allocating the other car to the autonomous mobile body that has transmitted the call information;
The elevator control device according to claim 1. When the control unit receives a call specifying the destination floor from a destination floor registration device that receives input of the destination floor from the user, the control unit determines the destination floor based on the section between the departure floor and the destination floor. determining which section of the car is to be used by the user or the autonomous mobile body, and controlling the allocation of the car;
The elevator control device according to claim 1. further comprising a detection unit that detects the number of the users waiting at the boarding point,
The call information includes the size of the autonomous mobile body,
When the control unit receives the call from the autonomous mobile body, the control unit makes a connection between the users and the autonomous mobile body based on the number of users waiting at the platform and the size of the autonomous mobile body. permitting passengers to ride in said car;
The elevator control device according to claim 1. An elevator control method executed by an elevator control device that controls calls for two cars connected vertically in an elevator hoistway, the method comprising:
a step in which the receiving unit receives, as a call, call information including a type indicating whether the call is the user or the autonomous moving body and a departure floor from the user or the autonomous moving body;
The control unit determines which of the two cars to place the user and the autonomous mobile object on based on the received call information and the operation information of the car, and places the user and the autonomous mobile object in the car. a control step for allocating
An elevator control method including: A program to be executed by a computer of an elevator control device that controls calls for two cars connected vertically in an elevator hoistway,
receiving, as a call, call information including a type indicating whether the call is the user or the autonomous mobile body and a departure floor from the user or the autonomous mobile body;
Based on the received call information and the operation information of the car, it is determined which of the two cars the user and the autonomous mobile object should be placed in, and the car is assigned. a control step;
A program for causing the computer to execute.

Images