Name of Document] DESCRIPTION
[Title of Invention] ELEVATOR CONTROL SYSTEM AND OPERATION
STATE OUTPUT METHOD
[Technical Field]
[0001]
The present invention relates to an elevator control
system and an operation state output method for managing an
operation state of an elevator.
[Background Art]
[0002]
A plurality of elevators are arranged in an office
building, a condominium, or the like, and operation control
is executed to carry out group management on the elevators
for transporting many people. In a typical group management
system, a hall call is registered by a user operating a
button arranged in a hall, and after a car of a unit
assigned by an elevator control device arrives and the user
rides on the car, a destination floor is registered.
[0003]
In recent years, there is provided a group management
system of destination floor reservation type in which a
destination floor is registered in a hall. The destination
floor reservation type is a type that allows a user to
register a hall call and a destination floor by using a
destination floor registration device arranged in the hall.
- 3 -
In the group management system of the destination floor
reservation type, since the destination floor is registered
simultaneously when the hall call is registered, the
elevator control device can recognize the destination floor
immediately. Accordingly, the elevator control device can
assign an elevator of an optimum unit to the user as
compared with typical group management.
[0004]
The operation state of an elevator is recognized with
use of an operation diagram displayed on a maintenance
terminal, in a management center, or the like. A
maintenance person or the like views the operation diagram
and hence can check whether or not the group management is
properly carried out by the elevator control device. For
example, a technology disclosed in PTL 1 is known as a
technology for outputting this operation diagram.
[0005]
This PTL 1 discloses a technology of outputting an
operation diagram in which a car position is displayed in a
display style in a condition in which a door is open and
while the door is in the middle of being opened and closed
so that the condition can be discriminated from the other
conditions.
[Citation List]
[Patent Literature]
- 4 -
[0006]
[PTL 1] Japanese Unexamined Patent Application
Publication No. 2002-68621
[Summary of Invention]
[Technical Problem]
[0007]
However, with the technology disclosed in PTL 1,
information obtained from an operation state output device
was limited. For example, although a unit was properly
assigned on the basis of registration by a destination floor
registration device, if an abnormal condition that
deteriorates operation efficiency of an elevator occurred
contrarily to input information by the destination floor
registration device, proper information which allows the
content of this abnormal condition to be recognized could
not be obtained. Also, the operation diagram of related art
indicated only the operation state of the elevator. Hence,
only by viewing the operation diagram, a maintenance person
or the like could not recognize occurrence of an abnormal
condition, such as a condition in which a user rode on a car
of a unit not assigned, or a condition in which a user did
not ride on a car of a unit assigned.
[0008]
The present invention is made in the light of
situations, and it is an object of the invention to allow
- 5 -
proper information to be provided when an abnormal condition
that may deteriorate operation efficiency of an elevator
occurs.
[Solution to Problem]
[0009]
The present invention outputs an operation state of an
elevator in accordance with a signal acquired from an
elevator control device that controls operation of the
elevator of each of units on the basis of information
relating to a destination floor registered by a destination
floor registration device.
Also, the invention outputs information indicative of
an operation condition of the elevator, as the operation
state of the elevator.
Also, the invention detects occurrence of an abnormal
condition that deteriorates operation efficiency of the
elevator, and outputs information indicative of the
occurrence of the detected abnormal condition, as the
operation state of the elevator.
[Advantageous Effects of Invention]
[0010]
With the present invention, if the abnormal condition
occurs, the information indicative of the occurrence of the
abnormal condition is provided. Accordingly, a maintenance
person or the like can easily recognize the deterioration in
- 6 -
operation efficiency of the elevator.
Problems, configurations, and advantageous effects
other than those described above will become apparent from
the following description of an exemplary embodiment.
[Brief Description of Drawings]
[0011]
[Fig. 1] Fig. 1 is an explanatory view showing a state of
a hall according to an exemplary embodiment of the invention.
[Fig. 2] Fig. 2 is a block configuration diagram showing
an inner configuration example of an elevator control system
according to the exemplary embodiment of the invention.
[Fig. 3] Fig. 3 provides explanatory views each showing
an example of an abnormal condition according to the
exemplary embodiment of the invention.
[Fig. 4] Fig. 4 provides explanatory views each showing
an example of an abnormal condition according to the
exemplary embodiment of the invention.
[Fig. 5] Fig. 5 is a block diagram showing a hardware
configuration example of a computing unit according to the
embodiment of the invention.
[Fig. 6] Fig. 6 is a configuration diagram of an
operation data table according to the exemplary embodiment
of the invention.
[Fig. 7] Fig. 7 is a data configuration diagram showing
the details of car condition data, call condition data,
- 7 -
waiting user number data, and registration device user data
according to the exemplary embodiment of the invention.
[Fig. 8] Fig. 8 is a flowchart showing a processing
example in an operation condition output unit of an
operation state output device according to the exemplary
embodiment of the invention.
[Fig. 9] Fig. 9 is a flowchart showing a specific example
of data creating and displaying processing indicated in step
S8 in Fig. 8.
[Fig. 10] Fig. 10 shows an example of an operation
diagram according to the exemplary embodiment of the
invention.
[Fig. 11] Fig. 11 is an explanatory view showing a
display example of two types of marks for discriminating
ascending and descending operations of an elevator from one
another according to the exemplary embodiment of the
invention.
[Fig. 12] Fig. 12 is a flowchart showing a processing
example in which an abnormal registration number diagnosis
processing unit makes a diagnosis of the an abnormal
registration number according to the exemplary embodiment of
the invention.
[Fig. 13] Fig. 13 is a flowchart showing a processing
example in which an incorrect ride diagnosis processing unit
makes a diagnosis of incorrect ride and a no-entry ride
- 8 -
diagnosis processing unit makes a diagnosis of no-entry ride
according to the exemplary embodiment of the invention.
[Fig. 14] Fig. 14 is a flowchart showing a processing
example in which a registered user no-ride departure
diagnosis processing unit makes a diagnosis of registered
user no-ride according to the exemplary embodiment of the
invention.
[Fig. 15] Fig. 15 shows an example of an operation
diagram that reflects an abnormal condition output from an
abnormal condition output processing unit according to the
exemplary embodiment of the invention.
[Description of Embodiments]
[0012]
An exemplary embodiment for implementing the invention
is described below with reference to the accompanying
drawings. In the specification and drawings, the same
reference sign is applied to components having substantially
equivalent functions or configurations, and hence redundant
description is omitted.
[0013]
[Exemplary Embodiment]
Fig. 1 is an explanatory view showing a state of a hall
H.
[0014]
An elevator control system 1 includes three elevators 2
- 9 -
and a destination floor registration device 3 provided on
each floor, and is used as a group management system
configured to carry out group management on the plurality of
elevators 2. Respective units of the elevators 2 can be
identified with unit numbers using alphabetical signs of "A"
to "C." The number of elevators 2 may be two, or four or
more. In the hall H, doors 4 are provided respectively for
the elevators 2. Each of the doors 4 is a hall door that is
opened and closed together with a car door of a car 5 (see
Fig. 3 described later) of the elevator 2 when the car 5
arrives at a floor.
[0015]
The destination floor registration device 3 is provided
near the exit/entrance of the hall H on each floor. A user
can register a destination floor on a user basis by
operating a destination floor reservation button displayed
on the destination floor registration device 3.
Simultaneously when the user registers the destination floor
by using the destination floor registration device 3, a
destination call and a hall call (a call reservation) are
generated. Then, with an elevator control device 10 (see
Fig. 2 described later), the unit number of the elevator 2
assigned in accordance with the destination floor registered
by the user is displayed on the destination floor
registration device 3.
- 10 -
[0016]
The user waits for arrival of the car 5 in front of the
door 4 with the unit number displayed on the destination
floor registration device 3. Then, when the car 5 arrives
and the door 4 is opened, the user rides on the car 5. Then,
the door 4 is closed, and the car 5 ascends or descends to
the registered destination floor. Since the group
management is carried out on the plurality of elevators 2
for each destination floor registered by a user, convenience
of the user can be improved.
[0017]
Fig. 2 is a block configuration diagram showing an
inner configuration example of the elevator control system 1.
[0018]
The elevator control system 1 includes, as
configurations that control the operation of the elevators 2,
the elevator control device 10, a signal processing device
20, and an operation state output device 30. The elevator
control device 10 is connected with the operation state
output device 30 with the signal processing device 20
interposed therebetween. Alternatively, the elevator
control device 10 may be connected with the operation state
output device 30 without the signal processing device 20
interposed therebetween.
[0019]
- 11 -
The elevator control device 10 executes operation
control on the elevator 2 of each of units, on the basis of
information relating to a destination floor registered by
the destination floor registration device 3. Then, the
elevator control device 10 acquires various signals relating
to elevator operation from the elevator 2, and outputs the
various signals to the signal processing device 20. When
the destination floor registration device 3 is operated, the
destination floor is registered, and hence a new call
reservation signal is generated, the elevator control device
10 assigns a unit of a proper elevator 2, and executes, for
example, processing on signals for controlling a reservation
lamp or the like arranged at the assigned unit or near the
hall.
[0020]
The signal processing device 20 stores the various
signals input from the elevator control device 10 in a
storage device 21. The signals configure required data
acquired by the signal processing device 20 from data stored
every constant time period in a storage unit (not shown) of
the elevator control device 10 (hereinafter, referred to as
"operation data"). The content of the operation data is
determined by an operation data table 50 shown in Fig. 6
described later, and the various signals acquired by the
signal processing device 20 are successively stored in a
- 12 -
storage medium 22 prepared in the storage device 21. Also,
the signal processing device 20 adds time information to the
signals acquired from the elevator control device 10, and
hence the generation date and time of the signals can be
figured out.
[0021]
The signal processing device 20 stores the operation
data including an ID signal and additional information as a
set in the storage medium 22 every time when a call
reservation is newly generated. The ID signal is
identification information of the destination floor
registration device 3 output from the destination floor
registration device 3 operated by a user. The additional
information includes information containing the generation
time, generation floor, registered destination floor, the
number of waiting users, etc., of the operation made in the
destination floor registration device 3.
[0022]
Also, the operation data stored in the storage medium
22 includes, for example, a call reservation signal
generated when a call reservation is made, and the number of
registrations by the destination floor registration, as a
result that a user registered a destination floor by
operating the destination floor registration device 3. In
addition, the operation data includes assigned unit
- 13 -
information when the elevator control device 10 assigned a
unit on the basis of the call reservation signal, a car call
registration signal when the car door of the assigned unit
was opened and the user rode on the car, etc. Further, the
operation data includes various operation conditions, such
as car condition signals indicative of the car position,
traveling direction, in-car load, door related signal, etc.,
of each unit; and the predicted number of users in car, etc.
[0023]
The operation state output device 30 outputs an
operation state of each elevator 2 controlled by the
elevator control device 10. To be specific, the operation
state output device 30 acquires the operation data stored in
the storage medium 22, and provides various information
detected on the basis of the operation data as the operation
state of the elevator 2 to the maintenance person or the
like through an operation condition output unit 31. Various
functions are executed in the operation state output device
30 by an application program executed by a PC terminal or
the like. The operation state output device 30 according to
the exemplary embodiment includes an operation efficiency
deterioration abnormality detection unit 32 and an abnormal
condition output processing unit 37 in addition to the
operation condition output unit 31 used in related art. The
operation state includes information indicative of
- 14 -
occurrence of an abnormal condition in addition to
information indicative of an operation condition of the
elevator 2.
[0024]
The operation condition output unit 31 outputs the
information indicative of the operation condition of each
elevator 2, as the operation state of the elevator 2. The
information indicative of the operation condition of the
elevator 2 includes an operation diagram etc. as described
later in detail. The operation diagram is used for
displaying the number of waiting users who made call
reservations by the destination floor registration device 3
provided on each floor on a floor basis, and for displaying
the number of waiting users who made call reservations on a
destination floor basis. Also, the operation diagram can be
used for application analysis of the elevator 2 by the
maintenance person, such as tendency of the application and
operation of the elevator 2 including times of arrival at
and departure from a building, without limiting to provision
of information to the users.
[0025]
The operation efficiency deterioration abnormality
detection unit 32 is added to the operation state output
device 30, to detect occurrence of an abnormal condition
that deteriorates operation efficiency of the elevator 2.
- 15 -
Specific examples of respective diagnosis processing units
33 to 36 included in the operation efficiency deterioration
abnormality detection unit 32 will be described later. The
abnormal condition detected by the operation efficiency
deterioration abnormality detection unit 32 includes at
least one of an abnormal condition of an abnormal
registration number, an abnormal condition of incorrect ride,
an abnormal condition of no-entry ride, and an abnormal
condition of registered user no-ride. An abnormal condition
output processing unit 37 outputs information indicative of
the occurrence of the abnormal condition detected by the
operation efficiency deterioration abnormality detection
unit 32. The information indicative of the occurrence of
the abnormal condition is displayed in a superimposed manner
on the operation diagram as indicated by a circle mark 63 in
Fig. 15 described later.
[0026]
The information provided to the maintenance person or
the like by the operation condition output unit 31 and the
operation efficiency deterioration abnormality detection
unit 32 is, for example, displayed on a display of the
destination floor registration device 3 or a maintenance
terminal provided in a monitoring center (display on a
display unit C5 shown in Fig. 5 described later), or printed
from a printer.
- 16 -
[0027]
An example of an abnormal condition the occurrence of
which is detected by the operation efficiency deterioration
abnormality detection unit 32 is described here with
reference to Figs. 3 and 4.
Figs. 3 and 4 are explanatory examples of abnormal
conditions.
[0028]
An abnormal condition is a condition that deteriorates
operation efficiency of the elevator 2. If an abnormal
condition occurs, in the elevator 2 of each unit assigned by
the elevator control device 10, a weight different from
expected may be applied, or the elevator 2 may not arrive at
the destination floor desired by a user. As the result, the
operation efficiency of the elevator 2 is deteriorated.
Hence, it is important that the operation efficiency
deterioration abnormality detection unit 32 detects
occurrence of an abnormal condition and the abnormal
condition output processing unit 37 outputs the abnormal
condition.
[0029]
In the following description, an elevator 2 with a unit
number A assigned by the elevator control device 10 is
abbreviated as "assigned unit A," and also an elevator 2
with a unit number B is abbreviated as "assigned unit B."
- 17 -
It is assumed that the capacity of riding users on each of
the assigned units A and B is 10 users.
[0030]
Fig. 3A shows a state in which two users U1 and U2
stand in front of the door 4 with the unit number A and two
users U3 and U4 stand in front of the door 4 with the unit
number B. The two users U1 and U2 who registered
destination floors are assigned to the unit number A by the
elevator control device 10. A region A1 indicates that,
since the two users U1 and U2 have registered the
destination floors, the number of destination calls
registered in the unit number A (hereinafter, referred to as
"the number of destination calls") is "2."
Similarly, the two users U3 and U4 who registered
destination floors are assigned to the unit number B by the
elevator control device 10. A region A2 indicates that,
since the two users U3 and U4 have registered the
destination floors, the number of destination calls
registered in the unit number B is "2."
Since the destination floors are registered by the
users, the total sum of the numbers of destination calls
registered in the respective units is "4" on the floor where
the call reservations are generated.
[0031]
Fig. 3B shows a state in which the two users U1 and U2
- 18 -
ride on the assigned unit A, and the two users U3 and U4
ride on the assigned unit B. In this case, the number of
riding users "2" of each of the assigned units A and B
included in a region A3 is the same as the number of
destination calls "2" registered in each of the units. Also,
the total sum of the numbers of riding users "4" in the
assigned units A and B is the same as the total sum of the
number of destination calls "4". Hence, Fig. 3B shows a
normal condition.
[0032]
Fig. 3C shows a state in which two users U1 and U2 ride
on the assigned unit A, and two users U3 and U4 ride on the
assigned unit B, similarly to Fig. 3B. However, one of the
users U1 and U2 improperly operates the destination floor
registration device 3 and registers the destination floor a
plurality of times, and hence a larger number of destination
calls than an actual number of users is registered. For
example, the number of riding users "2" of the assigned unit
A included in a region A3 is different from the number of
destination calls (for example, "5") registered in the unit
number A included in a region A4. In this way, if the
number of riding users of each unit is different from the
number of destination calls registered in each unit by a
predetermined threshold (for example, "3") or larger, an
abnormal condition of an abnormal registration number occurs,
- 19 -
in which the number of destination calls is abnormally
registered. If the abnormal condition of the abnormal
registration number occurs, users other than the users U1
and U2 are not assigned to the unit number A, and hence such
users cannot ride on the assigned unit A on which such users
could have ridden.
[0033]
Fig. 4D shows a state in which three users U1 to U3
ride on the assigned unit A. On the assigned unit A, the
user U3 who was expected to ride on the assigned unit B
rides in addition to the users U1 and U2. In this case, as
shown in a region A5 indicative of the users riding on the
assigned units A and B, the total sum of the numbers of
riding users is "4," which is equivalent to "4" being the
total sum of the number of destination calls registered in
the respective units as shown in the regions A1 and A2 in
Fig. 3A. However, the number of riding users "3" of the
assigned unit A is different from the number of destination
calls "2" registered in the unit number A included in the
region A1 in Fig. 3A. In this way, when an abnormal
condition of incorrect ride occurs, for example, if the
number of destination calls registered in the unit number A
is the same as the capacity of riding users of the car 5,
the users assigned to the unit number A may not occasionally
ride on the assigned unit A.
- 20 -
[0034]
Fig. 4E shows a state in which a user U5 who has not
registered a destination floor with the destination floor
registration device 3 rides on the assigned unit A. In the
state shown in Fig. 4E, while the number of destination
calls registered in the unit number A is "2," the user U5
who has not used the destination floor registration device 3
rides on the assigned unit A and hence the number of riding
users in the assigned unit A is "3." In this case, as shown
in a region A6 indicative of the users riding on the
assigned units A and B, the total sum of the numbers of
riding users riding on the assigned units A and B is "5."
Hence, "4" being the total sum of the numbers of destination
calls registered in the respective units is mismatched with
"5" being the total sum of the numbers of riding users. In
this way, when an abnormal condition of no-entry ride occurs,
for example, if the number of destination calls registered
in the assigned unit A is the same as the capacity of riding
users of the car 5, part of the users assigned to the unit
number A cannot ride on the assigned unit A.
[0035]
Fig. 4F shows a state in which only a user U1 of two
users U1 and U2 assigned to the unit number A rides on the
assigned unit A, and the user U2 does not ride on the
assigned unit A. The number of riding users "1" of the
- 21 -
assigned unit A is different from the number of destination
calls "2" registered in the unit number A included in the
region A1 in Fig. 3A. In this way, if an abnormal condition
of registered user no-ride occurs, the car 5 may ascend or
descend while being empty, or the user U2 who does not ride
may ride on another car 5. Also, when the user U2 rides on
the car 5, the user U2 has to register the destination floor
with the destination floor registration device 3 again.
However, the user U2 may not register the destination floor.
It is to be noted that, also in Fig. 4D, the abnormal
condition of the registered user no-ride is generated
because the user U3 does not ride on the assigned unit B.
[0036]
To detect various abnormal conditions shown in Figs. 3C,
and 4D to 4F, the operation efficiency deterioration
abnormality detection unit 32 includes an abnormal
registration number diagnosis processing unit 33, an
incorrect ride diagnosis processing unit 34, a no-entry ride
diagnosis processing unit 35, and a registered user no-ride
departure diagnosis processing unit 36. The abnormal
condition output processing unit 37 outputs the various
abnormal conditions detected by the operation efficiency
deterioration abnormality detection unit 32.
[0037]
The abnormal registration number diagnosis processing
- 22 -
unit 33 judges whether or not the difference between the
number of registrations of each unit assigned by the
elevator control device 10 and the number of riding users of
the unit is a predetermined threshold or larger (excessive
mismatch). Then, the abnormal registration number diagnosis
processing unit 33 diagnoses that the abnormal condition of
the abnormal registration number occurs if the difference is
the predetermined threshold or larger. The occurrence of
the abnormal condition of the abnormal registration number
as described above is shown in Fig. 3C.
[0038]
The incorrect ride diagnosis processing unit 34 judges
whether or not, on a certain departure floor in a certain
time period, the difference between the number of
registrations of each unit assigned by the elevator control
device 10 and the number of riding users of the assigned
unit is a predetermined threshold or larger. Then, the
incorrect ride diagnosis processing unit 34 diagnoses that
the abnormal condition of the incorrect ride occurs if the
difference is the predetermined threshold or larger, and if
the number of entire registrations is matched with the total
sum of the numbers of entire riding users on this departure
floor in this time period. The occurrence of the abnormal
condition of the incorrect ride as described above is shown
in Fig. 4D.
- 23 -
[0039]
The no-entry ride diagnosis processing unit 35 judges
whether or not, on a certain departure floor in a certain
time period, the difference between the number of
registrations of each unit assigned by the elevator control
device 10 and the number of riding users of the assigned
unit is a predetermined threshold or larger. Then, the noentry
ride diagnosis processing unit 35 diagnoses that the
abnormal condition of the no-entry ride occurs if the
difference is the predetermined threshold or larger, and if
the number of entire registrations is mismatched with the
total sum of the numbers of entire riding users on this
departure floor in this time period. The occurrence of the
abnormal condition of the no-entry ride as described above
is shown in Fig. 4E.
[0040]
The registered user no-ride departure diagnosis
processing unit 36 judges whether or not, on a certain
departure floor in a certain time period, the elevator 2 has
departed while the number of riding users of each assigned
unit assigned by the elevator control device 10 is smaller
than the number of registrations of the assigned unit. Then,
the registered user no-ride departure diagnosis processing
unit 36 diagnoses the occurrence of the abnormal condition
of the registered user no-ride if the registered user no-
24 -
ride departure diagnosis processing unit 36 judges that the
elevator 2 has departed in such a condition. The occurrence
of the abnormal condition of the registered user no-ride as
described above is shown in Fig. 4F.
[0041]
The abnormal condition output processing unit 37
outputs at least one of information relating to the unit of
the elevator 2 in which an abnormal condition occurs, an
occurrence time of the abnormal condition, and an occurrence
floor of the abnormal condition, as detection information by
the operation efficiency deterioration abnormality detection
unit 32. These pieces of information are extracted from
respective data shown in Fig. 7 described later by the
operation efficiency deterioration abnormality detection
unit 32. The information output from the abnormal condition
output processing unit 37 is displayed on, for example, the
display unit C5 shown in Fig. 5 described later.
[0042]
Next, a hardware configuration of a computing unit C
configuring the respective devices (the elevator control
device 10, the signal processing device 20, and the
operation state output device 30) of the elevator control
system 1 is described. In each of the devices, the
configuration required for the computing unit C is
appropriately selected.
- 25 -
Fig. 5 is a block diagram showing a hardware
configuration example of the computing unit C.
[0043]
The computing unit C is hardware used as so-called
computer. The computing unit C includes a CPU (Central
Processing Unit) C1, a ROM (Read Only Memory) C2, and a RAM
(Random Access Memory) C3 each connected with a bus C4.
Further, the computing unit C includes the display unit C5,
an operation unit C6, a non-volatile storage C7, and a
network interface C8.
[0044]
The CPU C1 reads out a program code of software that
realizes respective functions according to this exemplary
embodiment from the ROM C2 and executes the program code.
In the RAM C3, a variable generated in the middle of
arithmetic processing, a parameter, etc., are temporarily
written. The display unit C5 is, for example, a liquid
crystal display monitor, and displays the result of
processing etc. executed by the computing unit C to the user.
In the operation unit C6, for example, a keyboard, a mouse,
etc., is used. The user can make predetermined operation
input and instruction.
[0045]
For the non-volatile storage C7, for example, a HDD
(Hard disk drive), a SSD (Solid State Drive), a flexible
- 26 -
disk, an optical disc, a magneto-optical disk, a CD-ROM, a
CD-R, a magnetic tape, a non-volatile memory, etc., is used.
This non-volatile storage C7 stores OS (Operating System),
various parameters, and in addition, a program that causes
the computing unit C to function. For the network interface
C8, for example, a NIC (Network Interface Card) etc. is used,
and can transmit and receive various data through a LAN
(Local Area Network), a dedicated line, etc., to which a
terminal is connected.
[0046]
Fig. 6 is a configuration diagram of the operation data
table 50. As already described above, the operation data
table 50 is used for determining the content of the
operation data, and is stored in the storage medium 22.
[0047]
The operation data table 50 for determining the content
of the operation data is configured of collection date and
time data 51, car condition data 52, call condition data 53,
waiting user number data 54, registration device user data
55, call assignment evaluation value data 56, parameter data
57, etc.
[0048]
The collection date and time data 51 includes the date
and time that the operation data is collected.
The car condition data 52 indicates the car state of
- 27 -
the assigned unit. The car condition data 52 stores the
time that the signal processing device 20 acquires the car
condition of the elevator 2, the unit number applied to each
unit, the car moving direction, the floor indicative of the
car position, and the in-car load or the number of users in
the car. In addition, the car condition data 52 stores a
door condition etc. relating to a unit acquired by the
signal processing device 20 from signals, such as a door
open signal, a door close signal, an open button operation
signal, a close button operation signal, a re-open
activation signal, and a signal from a photoelectric device.
[0049]
The call condition data 53 stores a generation time of
a call reservation, a call assignment state of each floor in
each of different directions, a new call reservation state
of each riding floor, a call duration, or a ride completion
time, etc., on a call type basis.
The waiting user number data 54 stores a time that the
number of waiting users on a call reservation generation
floor and the number of waiting users on a destination floor
are increased or decreased, on a call type basis.
[0050]
The registration device user data 55 stores data
relating to a user who has operated the destination floor
registration device 3.
- 28 -
If a previously set abnormal condition occurs, the call
assignment evaluation value data 56 and the parameter data
57 sequentially store specific data at a time point that the
abnormal condition occurs and the occurring abnormal
condition. The call assignment evaluation value is a value
used by the elevator control device 10 to assign the proper
car 5 for a newly generated hall call and a destination call
generated simultaneously with the hall call.
[0051]
Fig. 7 is a data configuration diagram indicative of
the details of the car condition data 52, call condition
data 53, waiting user number data 54, and registration
device user data 55 shown in Fig. 6.
[0052]
The car condition data 52 is configured of respective
fields including a car condition time 52a, a unit number 52b,
a direction 52c, a floor 52d, an in-car load 52e, and a door
condition 52f.
The car condition time 52a stores a time that the
elevator control device 10 acquires the condition of the car
5.
The unit number 52b stores a number applied to each
unit of the elevator 2.
The direction 52c stores a moving direction of the car
5.
- 29 -
The floor 52d stores a car position of the car 5.
The in-car load 52e stores a load of users on the car 5,
or the number of users riding on the car 5.
The door condition 52f stores a door condition of a
unit, such as a door open signal, a door close signal, an
open button operation signal, a close button operation
signal, a re-open activation signal, and a signal from a
photoelectric device, etc., acquired for each unit of the
elevator 2.
[0053]
The call condition data 53 is configured of respective
fields including a call reservation generation time 53a, a
unit number 53b, a call type 53c, a direction 53d, a floor
53e, a call duration 53f. Data stored in the unit number
53b, direction 53d, and floor 53e is the same as the data
stored in the unit number 52b, direction 52c, and floor 52d
of the above-described car condition data 52.
The call reservation generation time 53a stores a time
that a call reservation is generated by the destination
floor registration device 3.
The unit number 53b stores a unit number assigned by
registration of a destination floor.
The call type 53c stores a call type for discriminating
which one of a wheelchair user, an ordinary user, a VIP
(Very Important Person), etc., corresponds to the user.
- 30 -
The call duration 53f stores a time period that the
call registration is continued.
[0054]
The waiting user number data 54 is configured of
respective fields including a waiting user number
increase/decrease generation time 54a, a call type 54b, a
generation floor 54c, a destination floor 54d, the number of
waiting users 54e, and a spare 54f.
The waiting user number increase/decrease generation
time 54a stores a time when the number of waiting users is
increased or decreased in each unit.
The data stored in the call type 54b stores the same
data as the data stored in the call type 53c of the abovedescribed
call condition data 53.
The generation floor 54c stores a generation floor that
the call reservation is generated.
The destination floor 54d stores a destination floor
the destination floor of which is registered by the call
reservation.
The number of waiting users 54e stores the number of
waiting users of each unit.
The spare 54f is an auxiliary region used when
information to be stored is increased, and is not currently
used.
[0055]
- 31 -
The registration device user data 55 is configured of
respective fields including a call reservation generation
time 55a, a call type 55b, a registration device ID 55c, a
generation floor 55d, a destination floor 55e, an assignment
exemption condition 55f, an assigned unit 55g, and a spare
55h.
The call reservation generation time 55a stores the
same data as the data of the call reservation generation
time 53a stored in the call condition data 53.
Also, the call type 55b, generation floor 55d,
destination floor 55e, and spare 55h store the same data as
the data of the call type 54b, generation floor 54c,
destination floor 54d, and spare 54f of the above-described
waiting user number data 54.
[0056]
The registration device ID 55c stores a registration
device ID applied to the destination floor registration
device 3 used for the call reservation. The registration
device ID is for identifying each of a plurality of
destination floor registration devices 3 arranged on
respective floors. For example, simplified numerical values
such as "1" to "10" are correspondingly assigned to the
destination floor registration devices 3 on the respective
floors.
[0057]
- 32 -
The assignment exemption condition 55f stores an
assignment exemption condition for inhibiting or limiting
assignment to the elevator 2 of a certain unit. The
assignment exemption condition 55f is used for, for example,
analyzing the cause when a plurality of calls having the
same generation floor and the same assigned floor and having
registration times close to one another are assigned with
different assigned units. In addition, the assignment
exemption condition 55f is used for cause analysis when
assignment different from a normal situation is performed,
for example, when a unit that arrives later is assigned even
through there is a unit that arrives earlier in response to
call reservation generation.
[0058]
The assigned unit 55g stores a unit number of the
elevator 2 assigned by the elevator control device 10 after
a call reservation for a destination floor.
The generation floor 55d is used in association with
the destination floor registration device 3. With the
generation floor 55d, the floor that the call reservation is
generated can be recognized even if the arrangement
positions and the numbers of the destination floor
registration devices 3 arranged in the halls of the
respective floors are different.
[0059]
- 33 -
In this way, the operation data table 50 is configured
to store data of at least the call reservation generation
time 55a, the registration device ID 55c of the destination
floor registration device 3 used for the call reservation,
and the assigned unit 55g. By using such an operation data
table 50, the operation condition output unit 31 can provide
information to the maintenance person or the like, and the
operation efficiency deterioration abnormality detection
unit 32, which is newly added, can detect the occurrence of
the abnormal condition that deteriorates the operation
efficiency.
[0060]
Processing for creating the operation diagram provided
by the operation condition output unit 31 is described below.
Then, processing for detecting the occurrence of the
abnormal condition that deteriorates the operation
efficiency of the elevator 2, by the newly added abnormal
registration number diagnosis processing unit 33, incorrect
ride diagnosis processing unit 34, no-entry ride diagnosis
processing unit 35, registered user no-ride departure
diagnosis processing unit 36, and abnormal condition output
processing unit 37 is described.
[0061]
Fig. 8 is a flowchart showing a processing example in
the operation condition output unit 31 of the operation
- 34 -
state output device 30. In this case, processing of
creating the operation diagram by the operation condition
output unit 31 is described.
[0062]
First, the operation state output device 30 designates
a data file stored in the storage medium 22 shown in Fig. 2,
and acquires operation data (S1).
[0063]
Then, the operation state output device 30 selects a
display form of the operation data (display of entire
designated time period, display at occurrence of designated
state). The operation state output device 30 analyzes the
operation state on the basis of the selected display form of
the operation data and creates a diagram. Also, the
operation state output device 30 selects a unit being an
object of analysis and creation of the diagram of the
operation state and a call type (for example, ordinary use,
wheelchair use, VIP use), and selects a diagnosis and
analysis list (S2).
[0064]
The display of entire designated time period selected
in step S2 is a display form in which a designated time
period is selected from a designated time period in a range
from 9 o'clock to 12 o'clock and a designated time period in
the other time range, and only the elevator 2 in the
- 35 -
designated time period serves as a display object. The
display at occurrence of designated state is a display form
in which only the elevator 2 of the unit number with a
waiting time of 30 seconds or more generated serves as a
display object. Also, the diagnosis and analysis list is a
list for allowing the operation state of the elevator 2 to
be diagnosed and analyzed by displaying the operation state
including, for example, the crowding level, load, and open
button condition.
[0065]
The various selections in step S2 may be automatically
executed by the operation state output device 30 with a
previously set program, or may be input by the maintenance
person or the like who operates the operation unit C6
connected with the operation state output device 30. Then,
only minimum required information is selected and displayed.
With this selection, for example, the operation diagram,
with difficulty in viewing because of excessive information,
can become easily viewed and easily analyzed by the
maintenance person or the like, by limiting the number of
designated units to one and limiting the call type to only
ordinary use.
[0066]
Then, the operation state output device 30 judges
whether or not the operation state output device 30 outputs
- 36 -
the diagnosis and analysis list (S3). If the operation
state output device 30 judges that the operation state
output device 30 does not output the diagnosis and analysis
list (NO in S3), the operation state output device 30 goes
to step S6.
[0067]
In contrast, if the operation state output device 30
judges to output the diagnosis and analysis list (YES in S3),
the operation state output device 30 analyzes the operation
data in time series on the basis of the content input in
step S2 (S4). After the operation state output device 30
ends the time-series analysis for the operation data, the
operation state output device 30 outputs the diagnosis and
analysis list selected in step S2 to the display of the
display unit C5, a printer not shown, or the like (S5).
Then, the operation state output device 30 judges whether or
not the operation diagram is required to be output (S6), and
if the operation state output device 30 judges not to output
the operation diagram (NO in S6), the operation state output
device 30 ends this processing.
[0068]
In contrast, if the operation state output device 30
outputs the operation diagram (YES in S6), the operation
state output device 30 selects display items (analysis
rules) on the basis of the condition input in step S2 (S7).
- 37 -
This display items include, for example, a long-wait hall
call, reservation change, pass in crowding, door open, etc.
The long-wait hall call indicates that the user waits for a
predetermined time period or longer in the hall where the
destination floor is registered. The reservation change
indicates that the unit assigned once by the elevator
control device 10 is changed. Also, the pass in crowding
indicates that the car 5 passes the middle floor without
stopping when the number of riding users reaches the
capacity of riding users of the car 5. The door open
indicates that the door 4 including the car door is open.
By properly selecting these conditions, information
displayed in the operation diagram is simplified, and the
maintenance person or the like can easily read the operation
diagram.
[0069]
After step S7, as shown in Fig. 8 described later, the
operation state output device 30 executes creating
processing and displaying processing of data indicative of
the detailed content of the operation state (S8), and
outputs the operation state (for example, the operation
diagram) to the display, printer, etc.
[0070]
Finally, the operation state output device 30 judges
whether or not the data creating and displaying processing
- 38 -
in step S8 is ended entirely for the time period designated
in step S2 (S9). If the operation state output device 30
judges that the data creating and displaying processing is
not ended (NO in S9), the operation state output device 30
returns to step S8, and continues the data creating and
displaying processing. In contrast, if the operation state
output device 30 judges that the data creating and
displaying processing is ended (YES in S9), the operation
state output device 30 ends this processing.
[0071]
Fig. 9 is a flowchart showing a specific example of the
data creating and displaying processing shown in step S8 in
Fig. 8.
[0072]
First, the operation state output device 30 designates
a display style of the operation diagram (percentage
indication of in-car crowding level or indication of the
number of users, indication of the number of waiting users
or the number of waiting users on a destination floor basis,
etc.) for the display items (the analysis rules) selected in
step S7 in Fig. 8 (S11). Then, the operation state output
device 30 transfers data of the designated time period
selected in step S2 ± 5 minutes, among the data created in
step S4 shown in Fig. 7, to a diagram creation work area
provided in the RAM C3 (S12). That is, the operation state
- 39 -
output device 30 acquires data before and after the
designated time period. In this case, the designated time
period is, for example, a time period for a one screen that
can be output as an operation diagram, and is a time period
(in a range from 9:00:00 to 9:01:10) as shown in Figs. 10
and 15 described later. The operation state output device
30 transfers the data of the designated time period ± 5
minutes to the RAM C3 is to cause the display of the display
unit C5 to display the joint portions of the segment at the
start and end of the designated time period in the operation
diagram created by using the data for one screen in the
designated time period.
[0073]
Then, the operation state output device 30 judges
whether or not the operation diagram in the designated time
period is entirely displayed with no condition (S13). No
condition represents, for example, there is no designated
condition, no designated time period, etc., from the
maintenance person or the like. If the operation state
output device 30 judges that no condition is designated (YES
in S13), the operation state output device 30 outputs the
operation diagram of one day, and hence goes to step S15.
[0074]
In contrast, if the operation state output device 30
judges that a condition is designated (NO in S13), the
- 40 -
operation state output device 30 judges whether or not the
state corresponding to the conditions selected in step S2
and step S7 in Fig. 8 is included in the designated time
period (S14).
[0075]
If the operation state output device 30 judges that the
designated time period includes the state corresponding to
the designated condition (YES in S14), the operation state
output device 30 creates graphic data for display (for
example, the operation diagram) for displaying the operation
state. Then, the operation state output device 30 displays
the graphic data for display on the display, or outputs the
graphic data for display to the printer (S15), and ends this
processing. In step S15, the information indicative of the
occurrence of the abnormal condition diagnosed by the
respective diagnosis processing units shown in Figs. 12 to
14 described later is acquired, an operation diagram that
reflects the information indicative of the occurrence of the
abnormal condition is displayed or output.
[0076]
In contrast, if the operation state output device 30
judges that the designated time period does not include the
state corresponding to the designated condition (NO in S14),
the operation state output device 30 ends this processing
without outputting the operation state. Thereafter, the
- 41 -
operation state output device 30 is shifted to step S9 in
Fig. 8.
[0077]
Fig. 10 is an example of an operation diagram.
Fig. 11 is an explanatory view showing a display
example of two types of marks for distinguishing ascending
and descending operations of the elevator 2 from one another.
[0078]
The operation diagram shown in Fig. 10 shows operation
states of units A and B of two elevators 2 in the designated
time period (9:00:00 to 9:01:10). This operation diagram is
used by the maintenance person or the like for analyzing how
the elevator 2 is operated for each unit, and for explaining
the operation state of the elevator 2. A building indicated
by this operation diagram includes a B1 floor being an
underground floor, a first floor, a second floor, a third
floor, and a fourth floor. The first floor is a reference
floor, and the fourth floor is a restaurant floor.
[0079]
The ascending and descending operations of the elevator
2 can be distinguished from one another by an ascending mark
M1 and a descending mark M2 as shown in Fig. 11.
The ascending mark M1 is a sign indicative of the
ascending operation of the elevator 2. The ascending mark
M1 includes a destination floor M11, a reverse U-shape M12,
- 42 -
a cumulative total of the numbers of waiting users M13, and
a registration device ID M14.
The destination floor M11 indicates a destination floor
registered by the destination floor registration device 3.
The reverse U-shape M12 indicates that the elevator 2
(the car 5) ascends.
The cumulative total M13 indicates a cumulative total
of users waiting for arrival of the car 5 by using the
destination floor registration device 3 on the floor on
which the destination floor registration device 3 is
arranged.
The registration device ID M14 indicates a registration
device ID for identifying the destination floor registration
device 3 used by the user.
The destination floor M11 of the ascending mark M1 is
arranged above the reverse U-shape M12, the cumulative total
M13 is arranged inside the reverse U-shape M12, and the
registration device ID M14 is arranged below the reverse Ushape
M12.
[0080]
The descending mark M2 is a sign indicative of the
descending operation of the elevator 2. The descending mark
M2 includes a destination floor M21, a U-shape M22, a
cumulative total of the numbers of waiting users M23, and a
registration device ID M24.
- 43 -
The destination floor M21, the cumulative total of the
numbers of waiting users M23, and the registration device ID
M24 indicate the same contents as those of the destination
floor M11, the cumulative total of the numbers of waiting
users M13, and the registration device ID M14 of the
ascending mark M1.
The U-shape M22 indicates that the elevator 2 (the car
5) descends.
The destination floor M21 of the descending mark M2 is
arranged below the U-shape M22, the cumulative total M23 is
arranged inside the U-shape M22, and the registration device
ID M24 is arranged above the U-shape M22.
[0081]
Referring back to Fig. 10, the description of the
operation diagram is continued.
Triangle marks 60a and 60b each show that the user who
enters the car 5 operates the open button and the door 4
including the car door is in the open state.
Numerical indication portions 61a to 61c each show the
in-car crowding level of each unit. The in-car crowding
level is indicated by percentage indication using a ratio of
the number of riding users to the capacity of riding users.
A rectangle mark 62a indicates a car call registered
when the door 4 of the assigned unit B is open and a user
enters the car 5. In this example, a car call to the fourth
- 44 -
floor is registered.
Double-line rectangle marks 62b and 62c each indicate a
car call registered when the door 4 of the assigned unit A
is open and a user enters the car 5. In this example, car
calls to the second and third floors are registered.
[0082]
Then, a state of a call reservation generated on the B1
floor is shown in a region 70, a state of a call reservation
generated on the first floor is shown in a region 71, a
state of a call reservation generated on the second floor is
shown in a region 72, and a state of a call reservation
generated on the fourth floor is shown in a region 73.
[0083]
First, as shown in the region 70, it is assumed that a
first user in the hall on the B1 floor operates the
destination floor reservation button to the second floor
being the destination floor by using the destination floor
registration device 3 at a user generation time 9:00:01. In
this case, the ascending mark M1 that represents the
ascending operation of the elevator 2 is displayed according
to the previously set display form, at a position near the
intersection between the B1 floor plotted along the vertical
axis and the time 9:00:01 plotted along the horizontal axis
in Fig. 10. A cumulative total "1" of the number of waiting
users, a registration device ID "1," and a destination floor
- 45 -
"2FL" are displayed in the ascending mark M1.
[0084]
Then, it is assumed that a second user in the hall on
the B1 floor operates the destination floor reservation
button to the third floor being the destination floor by
using the destination floor registration device 3 at a user
generation time 9:00:04. At this time point, the assigned
unit A for the first user is located near the second floor,
and does not arrive at the B1 floor yet. Hence, a
cumulative total "2" of the number of waiting users, the
registration device ID "1," and a destination floor "3FL"
are displayed in the ascending mark M1 displayed near the
intersection between the B1 floor plotted along the vertical
axis and the time 9:00:04 plotted along the horizontal axis
in Fig. 10.
[0085]
Then, it is assumed that a third user in the hall on
the B1 floor operates the destination floor reservation
button to the second floor being the destination floor by
using the destination floor registration device 3 at a user
generation time 9:00:08. In this case, a cumulative total
"3" of the number of waiting users, the registration device
ID "1," and the destination floor "2FL" are displayed in the
ascending mark M1 displayed near the intersection between
the B1 floor plotted along the vertical axis and the time
- 46 -
9:00:08 plotted along the horizontal axis in Fig. 10.
[0086]
Then, it is assumed that a fourth user in the hall on
the B1 floor operates the destination floor reservation
button to the second floor being the destination floor by
using the destination floor registration device 3 at a user
generation time 9:00:10. In this case, a cumulative total
"4" of the number of waiting users, the registration device
ID "1," and the destination floor "2FL" are displayed in the
ascending mark M1 displayed near the intersection between
the B1 floor plotted along the vertical axis and the time
9:00:10 plotted along the horizontal axis in Fig. 10.
[0087]
Then, it is assumed that a fifth user in the hall on
the B1 floor operates the destination floor reservation
button to the third floor being the destination floor by
using the destination floor registration device 3 at a user
generation time 9:00:16. At this time point, the assigned
unit A for the fourth user does not arrive at the B1 floor
yet. Hence, a cumulative total "5" of the number of waiting
users, the registration device ID "1," and the destination
floor "3FL" are displayed in the ascending mark M1 displayed
near the intersection between the B1 floor plotted along the
vertical axis and the time 9:00:16 plotted along the
horizontal axis in Fig. 10 for the call reservation of the
- 47 -
fifth user.
[0088]
Then, the assigned unit A arrives at the B1 floor at a
time 9:00:20, the door 4 including the car door is open, and
the five users ride on the assigned unit A while the door 4
is in the open state by the open button operation indicated
by the triangle mark 60a. Fig. 10 shows that the in-car
crowding level of the assigned unit A that has departed from
the B1 floor at a time 9:00:30 is "50"%.
[0089]
The assigned unit A arrives at the second floor at a
time 9:00:50, and the three users who have ridden on the B1
floor get off on the second floor being the destination
floor. Hence, it is indicated that the in-car crowding
level of the assigned unit A that has departed from the
second floor at a time 9:01:00 is "20"%.
[0090]
In contrast, it is assumed that users who are different
from the users riding on the assigned unit A on the basement
first floor and who ride on the assigned unit B on the first
floor operate the destination floor reservation button to
the fourth floor being the destination floor by using the
destination floor registration device 3 before the time
9:00:00. Hence, the assigned unit B is ascending at the
time point of the time 9:00:00.
- 48 -
[0091]
In this case, the destination floor registration device
3 specified by a registration device ID "2" is arranged in
the hall on the first floor. Hence, as shown in the region
71, a cumulative total "10" of the number of waiting users,
the registration device ID "2," and a destination floor
"4FL" are displayed in the ascending mark M1 displayed near
the intersection between the first floor plotted along the
vertical axis and the time 9:00:00 plotted along the
horizontal axis in Fig. 10. Then, the assigned unit B
arrives at the first floor at a time 9:00:08, the door 4
including the car door is open, and 10 users ride on the
assigned unit B while the door 4 is in the open state by the
open button operation indicated by the triangle mark 60b.
Fig. 10 shows that the in-car crowding level of the assigned
unit B that has departed from the first floor at a time
9:00:30 is "100"%. That is, the 10 users being the capacity
of riding users ride on the assigned unit B on the first
floor.
[0092]
Then, as indicated in the region 73, the destination
floor registration device 3 specified by a registration
device ID "5" is arranged in the hall on the fourth floor
being the arrival floor of the assigned unit B. Hence, a
cumulative total "5" of the number of waiting users, the
- 49 -
registration device ID "5," and a destination floor "B1F"
are displayed in the descending mark M2 displayed near the
intersection between the fourth floor plotted along the
vertical axis and a time 9:01:00 plotted along the
horizontal axis in Fig. 10. The users on the fourth floor
ride on the assigned unit B that is turned to the descending
operation after all the users get off on the fourth floor
being the destination floor of the assigned unit B.
[0093]
There is a user who operates the destination floor
reservation button to the fourth floor being the destination
floor by using the destination floor registration device 3
specified by a registration ID "3" on the second floor as
indicated in the region 72. Hence, a number of waiting
users "1," a destination floor "4FL," and the registration
device ID "3" are displayed in the ascending mark M1
displayed near the intersection between the second floor
plotted along the vertical axis and the time 9:00:16 plotted
along the horizontal axis in Fig. 10. It is easily found
that since the crowding level of the assigned unit B is
"100"%, the assigned unit B passes for the call reservation
registered on the second floor, and since the crowding level
of the assigned unit A is "50"%, the assigned unit A arrives
at the second floor and the user rides on the assigned unit
A.
- 50 -
[0094]
The operation condition output unit 31 outputs the
operation diagram shown in Fig. 10, and hence a user who
views the operation diagram can figure out the reservation
state of oneself, the position information of the assigned
unit, the number of waiting users, etc. Also, a management
person checks the operation diagram output from the
operation condition output unit 31, and hence the management
person can analyze the tendency of application and operation
of the elevators 2, including arrival at and departure from
a building.
[0095]
Next, detection processing for an abnormal condition
executed by the respective units of the operation efficiency
deterioration abnormality detection unit 32 is described
below with reference to Figs. 12 to 14. Respective
processing shown in Figs. 12 to 14 are executed by the
respective units of the operation efficiency deterioration
abnormality detection unit 32 at a timing when the operation
state output device 30 acquires operation data from the
signal processing device 20, continuously or in parallel.
However, the processing shown in Figs. 12 to 14 may be
executed every predetermined time by the respective units of
the operation efficiency deterioration abnormality detection
unit 32.
- 51 -
[0096]
Fig. 12 is a flowchart showing a processing example in
which the abnormal registration number diagnosis processing
unit 33 diagnoses the abnormal registration number.
[0097]
First, the abnormal registration number diagnosis
processing unit 33 judges whether or not the elevator 2
closes the door 4 and departs (S21). If the elevator 2 does
not depart (NO in S21), the abnormal registration number
diagnosis processing unit 33 ends this processing.
[0098]
In contrast, if the elevator 2 departs (YES in S21),
the abnormal registration number diagnosis processing unit
33 acquires the timing at which the elevator 2 departs, and
compares the number of destination calls registered in this
unit by the destination floor registration device 3 with the
number of riding users riding on the unit (S22). In the
following description, the unit of the elevator 2 that
departs is referred to as "the unit." Also, when a user
operates the destination floor registration device 3 and
registers the destination floor, a destination call is
registered in the unit assigned. In this way, the number of
destination calls registered in the unit is referred to as
"the number of destination calls."
[0099]
- 52 -
If the difference between the number of destination
calls registered in the unit and the number of riding users
is smaller than a predetermined threshold (for example, "3")
(NO in S22), an abnormal condition of the abnormal
registration number does not occur, and the abnormal
registration number diagnosis processing unit 33 ends this
processing. The threshold is set because, in many cases,
the number of riding users is measured by a load sensor in
the car, and an error may be generated in the number of
users to be judged in accordance with the sexes and body
shapes of users. If a sensor that measures the number of
users is arranged in the car instead of the load sensor to
correctly detect the number of users, this threshold may be
"1." In contrast, if the difference between the number of
destination calls registered in the unit and the number of
riding users is the threshold or larger (YES in S22), the
number of riding users is excessively mismatched. For
example, as shown in Fig. 3C, if the number of riding users
is two while the number of registrations is 5, the abnormal
registration number diagnosis processing unit 33 diagnoses
occurrence of an abnormal condition of the abnormal
registration number (S23), and ends this processing.
[0100]
Fig. 13 is a flowchart showing a processing example in
which the incorrect ride diagnosis processing unit 34
- 53 -
diagnoses incorrect ride, and the no-entry ride diagnosis
processing unit 35 diagnoses no-entry ride.
[0101]
First, the incorrect ride diagnosis processing unit 34
judges whether or not the elevator 2 closes the door 4 and
departs (S31). If the elevator 2 does not depart (NO in
S31), the incorrect ride diagnosis processing unit 34 ends
this processing.
[0102]
In contrast, if the elevator 2 departs (YES in S31),
the incorrect ride diagnosis processing unit 34 acquires the
timing at which the elevator 2 departs, and judges whether
or not the number of riding users is larger than the number
of destination calls registered in this unit (S32). If the
number of destination calls registered in the unit is the
number of riding users or smaller (NO in S32), the incorrect
ride diagnosis processing unit 34 ends this processing.
[0103]
If the number of riding users is larger than the number
of destination calls registered in the unit (YES in S32),
the incorrect ride diagnosis processing unit 34 judges
whether or not the number of call reservation generation
times is equal to the total sum of the numbers of riding
users (S33). In this case, the number of destination calls
on the floor where the call reservation to the destination
- 54 -
registered by the destination floor registration device 3 is
generated is referred to as "the number of call reservation
generation times."
[0104]
If the number of call reservation generation times is
equal to the total sum of the numbers of riding users (YES
in S33), the incorrect ride diagnosis processing unit 34
diagnoses occurrence of incorrect ride (S34) and ends this
processing. The incorrect ride is an abnormal condition
judged when mismatch is generated because part of users
assigned to the other unit rides on the unit. An example of
the incorrect ride is shown in Fig. 4D described above.
[0105]
In contrast, if a difference is generated between the
number of call reservation generation times and the total
sum of the numbers of riding users (NO in S33), the no-entry
ride diagnosis processing unit 35 diagnoses occurrence of
no-entry ride (S35) and ends this processing. The no-entry
ride is an abnormal condition judged when a user who does
not make an entry or who does not use the destination floor
registration device 3 or register the destination floor
rides on the unit and hence mismatch is generated. An
example of the no-entry ride is shown in Fig. 4E described
above.
[0106]
- 55 -
The processing from step S31 to step S33 is executed by
the incorrect ride diagnosis processing unit 34; however,
may be executed by the no-entry ride diagnosis processing
unit 35.
[0107]
Fig. 14 is a flowchart showing a processing example in
which the registered user no-ride departure diagnosis
processing unit 36 diagnoses registered user no-ride.
[0108]
First, the registered user no-ride departure diagnosis
processing unit 36 judges whether or not the elevator 2
closes the door 4 and departs (S41). If the elevator 2 does
not depart (NO in S41), the registered user no-ride
departure diagnosis processing unit 36 ends this processing.
[0109]
In contrast, if the elevator 2 departs (YES in S41),
the registered user no-ride departure diagnosis processing
unit 36 acquires the timing at which the elevator 2 departs,
and judges whether or not a destination call registered in
the unit is present (S42). If the destination call
registered in the unit is not present (NO in S42), the
registered user no-ride departure diagnosis processing unit
36 ends this processing.
[0110]
In contrast, if the destination call registered in the
- 56 -
unit is present (YES in S42), the registered user no-ride
departure diagnosis processing unit 36 judges whether or not
the number of riding users is present in the unit (S43). If
the number or riding users is present in the unit (YES in
S43), the registered user no-ride departure diagnosis
processing unit 36 ends this processing.
[0111]
In contrast, if the number of riding users is not
present in the unit (NO in S43), the registered user no-ride
departure diagnosis processing unit 36 diagnoses occurrence
of registered user no-ride (S44), and ends this processing.
An example of the registered user no-ride is shown in Fig.
4F described above.
[0112]
If occurrence of an abnormal condition is diagnosed by
any of the respective diagnosis processing units, the
operation efficiency deterioration abnormality detection
unit 32 stores information indicative of the occurrence of
the abnormal condition including, for example, the unit
information, occurrence time, occurrence floor, and
occurring abnormal condition type in the parameter data 57.
Then, the operation state output device 30 reflects the
information indicative of the occurrence of the abnormal
condition acquired from the parameter data 57 into the
operation diagram, and outputs the operation diagram.
- 57 -
[0113]
Fig. 15 is an example of an operation diagram that
reflects the abnormal condition output from the abnormal
condition output processing unit 37.
[0114]
In the operation diagram output from the operation
condition output unit 31, as indicated in the region 70, the
cumulative total "5" of the number of waiting users, the
registration device ID "1," and the destination floor "3FL"
are displayed in the ascending mark M1 displayed near the
intersection between the B1 floor plotted along the vertical
axis and the time 9:00:16 plotted along the horizontal axis
in Fig. 15.
[0115]
Then, the assigned unit A arrives at the B1 floor at
the time 9:00:20, and the assigned unit A departs from the
B1 floor at the time 9:00:30 if an abnormal judgment is not
generated. In this case, the in-car crowding level is
expressed by "50"% in the form of indication by percentage,
and "5" in the form of indication by the number of users.
[0116]
However, at the time point of the time 9:00:30, the
number of riding users is "2" while the number of call
reservation registrations is "5." In this case, the
abnormal registration number diagnosis processing unit 33
- 58 -
judges occurrence of the abnormal registration number by the
processing shown in step S23 in Fig. 12, and stores
predetermined information in the parameter data 57. Then,
abnormal judgment information is reflected with a high
priority on the operation diagram output from the abnormal
condition output processing unit 37. The abnormal judgment
information is displayed as, for example, "2" added with a
circle mark 63 at the time 9:00:30 in the case in which the
in-car crowding level is in the indication form by the
number of users. The circle mark 63 is displayed by a thick
solid line, and hence a maintenance person or the like can
easily notice the presence of the circle mark 63.
[0117]
With the above-described elevator control system 1
according to the exemplary embodiment, for the operation
state of the elevator 2, the information indicative of
occurrence of an abnormal condition detected by the
operation efficiency deterioration abnormality detection
unit 32 is output to the maintenance person or the like
together with the information indicative of the operation
condition of the elevator 2.
[0118]
In this case, if excessive mismatch is generated
between the number of registrations of each unit assigned by
the elevator control device 10 and the number of riding
- 59 -
users in the assigned unit, the abnormal registration number
diagnosis processing unit 33 diagnoses occurrence of an
abnormal condition of the abnormal registration number.
Then, the abnormal condition output processing unit 37
outputs the operation data including the parameter data 57,
and hence the operation state output device 30 can provide
the operation diagram reflecting the information on the
occurring abnormal condition to the maintenance person or
the like.
[0119]
Also, the incorrect ride diagnosis processing unit 34
diagnoses occurrence of an abnormal condition of the
incorrect ride if mismatch is generated between the number
of registrations of each unit and the number of riding users
in the unit, and if the number of registrations is matched
with the total sum of the numbers of riding users. Then,
the abnormal condition output processing unit 37 outputs the
occurrence of the abnormal condition of the incorrect ride.
[0120]
Also, the no-entry ride diagnosis processing unit 35
diagnoses occurrence of an abnormal condition of the noentry
ride if mismatch is generated between the number of
registrations of each unit and the number of riding users in
the unit, and if the number of registrations is not matched
with the total sum of the numbers of riding users. Then,
- 60 -
the abnormal condition output processing unit 37 outputs the
occurrence of the abnormal condition of the no-entry ride.
[0121]
Also, the registered user no-ride departure diagnosis
processing unit 36 diagnoses occurrence of an abnormal
condition of the registered user no-ride if a user does not
ride on the unit the destination of which is registered.
Then, the abnormal condition output processing unit 37
outputs the occurrence of the abnormal condition of the
registered user no-ride.
[0122]
In any of the cases, the abnormal condition output
processing unit 37 outputs the information indicative of the
occurrence of the abnormal condition detected by the
operation efficiency deterioration abnormality detection
unit 32, and hence, the occurrence of the abnormal condition
can be indicated for the maintenance person or the like,
like the operation diagram shown in Fig. 15. Then, the
maintenance person or the like can recognize the presence of
the occurrence of the abnormal condition and the content of
the abnormal condition that may deteriorate the operation
efficiency. Thus, the maintenance person or the like can
immediately figured out the cause of the occurrence of the
abnormal condition.
[0123]
- 61 -
The operation efficiency deterioration abnormality
detection unit 32 preferably includes all the aforementioned
abnormal registration number diagnosis processing unit 33,
incorrect ride diagnosis processing unit 34, no-entry ride
diagnosis processing unit 35, and registered user no-ride
departure diagnosis processing unit 36. However, the
operation efficiency deterioration abnormality detection
unit 32 may be configured to include at least one of the
abnormal registration number diagnosis processing unit 33,
incorrect ride diagnosis processing unit 34, no-entry ride
diagnosis processing unit 35, and registered user no-ride
departure diagnosis processing unit 36.
[0124]
Also, the abnormal condition output processing unit 37
may display an abnormal condition in the operation diagram
in accordance with the type of the detected abnormal
condition, for example, by using marks of various shapes,
coloring, blinking, etc. For example, in the circle mark 63
shown in Fig. 15, by changing the display color of the
number of riding users "2" to the mark and color different
from those of the other numerical values, the occurrence of
the abnormal condition can be indicated without the circle
mark 63 displayed. Also, the maintenance person or the like
can easily discriminate the generated abnormal condition.
Also, the information output from the abnormal condition
- 62 -
output processing unit 37 is not limited to the operation
diagram. For example, the content of the abnormal condition
may be output in text in time series.
[0125]
Also, the operation diagram output from the operation
state output device 30 may be one indicative of the past
operation state of the elevator 2 in a certain time range,
and may be one indicative of the current operation state of
the elevator 2.
[0126]
The present invention is not limited to the abovedescribed
exemplary embodiment, and of course may employ
other various application examples and modifications within
the scope of the invention described in the claims.
For example, the above-described exemplary embodiment
is provided for specifically describing the configurations
of the device and system for easier understanding of the
invention. The invention is not necessarily limited to one
including all the described configurations. Also, part of
the configurations described in the exemplary embodiment can
be replaced with a configuration of another exemplary
embodiment. Further, a configuration of a certain exemplary
embodiment may be added with a configuration of another
exemplary embodiment. Also, for part of the configuration
of each exemplary embodiment, another configuration may be
- 63 -
added, deleted, and replaced.
Also, control lines and information lines required for
the description are shown, and not all control lines and
information lines of a product are shown. Actually, it may
be conceived that almost all configurations are connected
with one another.
[Reference Signs List]
[0127]
1 … elevator control system, 2 … elevator, 3 …
destination floor registration device, 10 … elevator control
device, 30 … operation state output device, 31 … operation
condition output unit, 32 … operation efficiency
deterioration abnormality detection unit, 33 … abnormal
registration number diagnosis processing unit, 34 …
incorrect ride diagnosis processing unit, 35 … no-entry ride
diagnosis processing unit, 36 … registered user no-ride
departure diagnosis processing unit, 37 … abnormal condition
output processing unit, 50 … operation data table
- 64 -
We claim:
[Claim 1]
An elevator control system comprising:
an elevator control device that controls operation of
an elevator of each of units on the basis of information
relating to a destination floor registered by a destination
floor registration device; and
an operation state output device that outputs an
operation state of the elevator controlled by the elevator
control device,
wherein the operation state output device includes
an operation condition output unit that outputs
information indicative of an operation condition of the
elevator, as the operation state of the elevator,
an operation efficiency deterioration abnormality
detection unit that detects occurrence of an abnormal
condition that deteriorates operation efficiency of the
elevator, and
an abnormal condition output processing unit that
outputs information indicative of the occurrence of the
abnormal condition detected by the operation efficiency
deterioration abnormality detection unit, as the operation
state of the elevator.
[Claim 2]
The elevator control system according to Claim 1,
- 65 -
wherein the abnormal condition detected by the operation
efficiency deterioration abnormality detection unit includes
at least one of an abnormal condition of an abnormal
registration number, an abnormal condition of incorrect ride,
an abnormal condition of no-entry ride, and an abnormal
condition of registered user no-ride.
[Claim 3]
The elevator control system according to Claim 2,
wherein the operation efficiency deterioration abnormality
detection unit includes an abnormal registration number
diagnosis processing unit that diagnoses the occurrence of
the abnormal condition of the abnormal registration number
if a difference between a number of registrations of each of
the units assigned by the elevator control device and a
number of riding users of each of the units assigned by the
elevator control device is a predetermined threshold or
larger.
[Claim 4]
The elevator control system according to Claim 2,
wherein the operation efficiency deterioration abnormality
detection unit includes an incorrect ride diagnosis
processing unit that diagnoses the occurrence of the
abnormal condition of the incorrect ride if a difference
between a number of registrations of each of the units
assigned by the elevator control device and a number of
- 66 -
riding users of each of the units assigned by the elevator
control device is a predetermined threshold or larger on a
certain departure floor in a certain time period, and if a
number of entire registrations is matched with a total sum
of numbers of entire riding users on the departure floor in
the time period.
[Claim 5]
The elevator control system according to Claim 2,
wherein the operation efficiency deterioration abnormality
detection unit includes a no-entry ride diagnosis processing
unit that diagnoses the occurrence of the abnormal condition
of the no-entry ride if a difference between a number of
registrations of each of the units assigned by the elevator
control device and a number of riding users of each of the
units assigned by the elevator control device is a
predetermined threshold or larger on a certain departure
floor in a certain time period, and if a number of entire
registrations is not matched with a total sum of numbers of
entire riding users on the departure floor in the time
period.
[Claim 6]
The elevator control system according to Claim 2,
wherein the operation efficiency deterioration abnormality
detection unit includes a registered user no-ride departure
diagnosis processing unit that diagnoses the occurrence of
- 67 -
the abnormal condition of the registered user no-ride if the
elevator has departed while a number of riding users of each
of the units assigned by the elevator control device is
smaller than a number of registrations of each of the units
assigned by the elevator control device on a certain floor
in a certain time period.
[Claim 7]
The elevator control system according to any one of
Claims 1 to 6, wherein the information indicative of the
occurrence of the abnormal condition output from the
abnormal condition output processing unit includes at least
one of information relating to a unit of the elevator in
which the abnormal condition occurs, an occurrence time of
the abnormal condition, and an occurrence floor of the
abnormal condition.
[Claim 8]
An operation state output method comprising:
a step of outputting an operation state of an elevator
in accordance with a signal acquired from an elevator
control device that controls operation of the elevator of
each of units on the basis of information relating to a
destination floor registered by a destination floor
registration device;
a step of outputting information indicative of an
operation condition of the elevator, as the operation state
- 68 -
of the elevator;
a step of detecting occurrence of an abnormal condition
that deteriorates operation efficiency of the elevator; and
a step of outputting information indicative of the
occurrence the detected abnormal condition, as the operation
state of the elevator.