Technical Field
[0001] The present invention relates to an elevator running operating system that performs
a running operation by a touch panel disposed inside a cage or on a platform.
Background Art
[0002] Usually, a hardware contact point such as a push button or a key switch is used as
an input device for elevator call registration and running operation commands. Further,
there are also elevators that extremely rarely use a touch panel as an input device,
but these have only been for receiving call registrations of destination floors. (Patent
Document 1, etc.)
In Patent Document 1, there is described an invention where platform call information
is conveyed to an input control device by operating an input screen of a touch screen
configured such that a destination floor registration screen and an up and down direction
button screen are switched between.
In Patent Document 2, there is described an invention where a touch panel that is
disposed on a cage operating panel and displays floor buttons during normal times
is operated to register calls of destination floors and display a message indicating
that the elevator is running during an emergency when a fire or an earthquake is detected.
Disclosure of the Invention
Problem that the Invention is to Solve
[0004] The intended purpose of a hardware contact point such as a push button or a key switch
is set, and when the hardware contact point is to be used for various purposes, many
hardware contact points have been necessary.
The invention of Patent Document 1 has been for nothing more than performing call
registration on a touch screen.
Further, in the invention of Patent Document 2 also, although a touch panel that can
perform call registration and displays a message during an emergency is described,
the touch panel has only had the functions of call registration and message display.
Consequently, Patent Documents 1 and 2 have not been inventions where not just the
operating function of registering calls of destination floors but other operating
functions are given to a touch panel to realize uniform management of the running
operation of the elevator by the touch panel.
[0005] The present invention has been made in order to solve this problem, and it is an
object thereof to obtain an elevator running operating system that realizes uniform
management of the running operation of an elevator by a touch panel inside a cage
or on a platform.
Means for Solving the Problems
[0006] An elevator running operating system pertaining to this invention comprises a touch
panel that is disposed inside a cage of an elevator or on a platform and is used for
the running operation of the elevator, wherein during ordinary running of the elevator,
the touch panel displays a destination button and a switch button for switching the
running operation of the elevator, performs destination call registration as a result
of the destination button being operated, and the running operation of the elevator
is switched as a result of the switch button being operated.
Effects of the Invention
[0007] As described above, this invention includes a touch panel that is disposed inside
a cage of an elevator or on a platform and is used for the running operation of the
elevator, wherein during ordinary running of the elevator, the touch panel displays
a destination button and a switch button for switching the running operation of the
elevator, performs destination call registration as a result of the destination button
being operated, and the running operation of the elevator is switched as a result
of the switch button being operated. Thus, the running operation can be uniformly
performed by the touch panel, and the addition or deletion of optional operations
becomes easily implementable without having to change hardware devices.
Best Mode for Implementing the Invention
First Embodiment
[0008] A first embodiment is one configured to receive various running operation commands
of an elevator using a touch panel disposed inside a cage of the elevator or on a
platform.
FIG. 1 is a block diagram showing a system diagram of an elevator running operating
system according to the first embodiment of this invention, in which a touch panel
is used as an input device not only for call registration but also for other running
operation commands.
In FIG. 1, a group management panel 20 is connected to elevator control panels 15
and manages and controls plural elevators as a group. Cage touch panels 18 are disposed
inside cages and are connected to the elevator control panels 15 through cage stations
16 that include a local CPU. Platform touch panels 19 are disposed on each floor platform
and are connected to the elevator control panels 15 through platform stations 17 that
include a local CPU.
It will be noted that the cage touch panels 18 and the platform touch panels 19 may
also be directly connected to the elevator control panels 15 by dedicated cables without
the intervention of the cage stations 16 or the platform stations 17. Input/output
information of the cage touch panels 18 and the platform touch panels 19 is managed
by the elevator control panels 15 and the group management panel 14.
[0009] FIG. 2 is a diagram showing an example of a basic screen of a touch panel of the
elevator running operating system according to the first embodiment of this invention,
and the touch panel is in the state shown in FIG. 2 during ordinary running of the
elevator.
In FIG. 2, a touch panel 1 of the cage touch panels 18 and the platform touch panels
19 receives the input of running operation commands as the result of a passenger touching
displayed buttons. Buttons and messages 2 to 5 are displayed on the touch panel 1,
a message 2 explains the method of use, and destination buttons 3 display numbers
corresponding to the destinations of a first floor to a sixth floor. A wheelchair
button 4 (switch button) displays a wheelchair symbol, so that, for example, when
a passenger touches the wheelchair button 4 and touches one of the destination buttons
3, the elevator moves to an elevator operation corresponding to a handicapped person
where the door opening/closing time is extended, and the floor of the destination
button 3 is call-registered. A menu button 5 (switch button) is a button for moving
to FIG. 3, which is a screen that displays special running command buttons for selecting
various kinds of special running operations of the elevator.
[0010] FIG. 3 is a diagram showing an example of a menu screen of the touch panel of the
elevator running operating system according to the first embodiment of this invention,
and is a screen that is displayed as a result of a passenger touching the menu button
5 of FIG. 2.
In FIG. 3, special running command buttons 6 for selecting various kinds of special
running operations of the elevator include a dedicated running button 6a, a callback
button 6b, a halt button 6c, a maintenance button 6d, and an operator-driven running
button 6e. When a passenger touches these buttons, the running operation commands
are received and the elevator moves to the running operations. Further, when a passenger
touches the maintenance button 6d or the operator-driven running button 6e, the touch
panel moves to a screen where buttons and messages necessary in order to implement
these commands are displayed, so that the passenger can command maintenance or operator-driven
running on the screens.
[0011] The dedicated running button 6a is a button that is used to carry cargo and the like
and performs running where just button operation inside the cage is made effective.
The callback button 6b is a button that is operated from a touch panel disposed on
a platform so that the cage of the elevator is called back to that platform when it
becomes free. The halt button 6c is a button that calls back the elevator cage to
the platform, dims the lights, and halts the elevator cage, for example. The maintenance
button 6d is a button that halts the cage for the purpose of maintenance or causes
the cage to perform running for maintenance. The operator-driven running button 6e
is a button that gives running authority to an operator and performs running.
A schedule button 7 is a button that displays schedule functions and is a button for
switching to FIG. 4, which is a screen when one wants to schedule and perform a halt
command, for example. A return button 8 is a button for returning to the basic screen
of FIG. 2.
[0012] FIG. 4 is a diagram showing an example of a schedule screen of the touch panel of
the elevator running operating system according to the first embodiment of this invention,
and is a screen that is displayed as a result of a passenger touching the schedule
button 7 of FIG. 3.
In FIG. 4, a time period 9 represents a time period to schedule the halt operation,
and in this case indicates that the elevator will perform the halt operation for one
hour from 18 : 00 to 19: 00. Time setting buttons 10 displaying up and down directions
are buttons for setting the time, and it is possible to advance or turn back the time
by touching up and down triangular buttons. A setting button 11 is a button for performing
setting for causing the halt running operation to be performed in the actually designated
scheduled time period, and a cancel button 12 is a button that cancels settings made
by the setting button 11.
[0013] FIG. 5 is a diagram showing an example of a screen of the touch panel when the elevator
running operating system according to the first embodiment of this invention is coupled
to a security system.
In FIG. 5, destination buttons 13 display only destination floors that are allowed
to a passenger who has been authenticated by authenticating means such as a security
card. A message 14 represents an explanation with respect to the fact that the destination
floors are limited.
[0014] Next, the operation will be described.
The running operating system of the present invention is realized by connecting the
touch panel of FIG. 2 to FIG. 5 to a control panel that performs control of the elevator
or a group management panel that manages a group of plural elevators.
FIG. 6 is a flowchart showing an operation during usual call registration of the elevator
running operating system according to the first embodiment of this invention.
Next, the operation during ordinary running of the elevator will be described in accordance
with FIG. 6.
Ordinarily, the touch panel is in the state shown in FIG. 2. In FIG. 2, when a passenger
touches one of the destination buttons 3 on which floor names are displayed (step
S1), the call is registered in accordance with the floor name of that destination
button 3 (step S2). Thus, the elevator is run in accordance with the call registration.
[0015] FIG. 7 is a flowchart showing an operation during dedicated call registration of
the elevator running operating system according to the first embodiment of this invention.
Next, the dedicated call registration will be described by FIG. 7.
In the basic screen of FIG. 2, when a passenger touches one of the destination buttons
3 after touching the wheelchair button 4 (step S11), the dedicated call of a wheelchair
user is registered in accordance with the floor name of the destination button 3 (step
S12). Thus, the elevator moves to wheelchair-dedicated running.
[0016] FIG. 8 is a flowchart showing an operation during special running command registration
of the elevator running operating system according to the first embodiment of this
invention.
Next, the special running command registration will be described by FIG. 8.
First, when a passenger touches the menu button 5 of the basic screen of FIG. 2 (step
S21), a security check for qualification holder verification is performed by authenticating
means using a password or a card (step S22), or the menu screen of FIG. 3 is displayed
without this security check being performed (S23).
In the menu screen of FIG. 3, when the passenger touches one of the special running
command buttons 6 (dedicated running button 6a, callback button 6b, etc.) to the elevator
(step S24), the elevator moves to the inputted special running operation (step S26).
In step 24, depending on the running command such as the maintenance button 6d or
the operator-driven running button 6e, the touch panel switches to another input screen
(step S25) and then the flow moves to step S26.
Further, in the menu screen of FIG. 3, when the passenger touches the schedule button
7 (step S27), the schedule screen of FIG. 4 is displayed (step S28). In the schedule
screen of FIG. 4, setting of the schedule of the halt operation or cancellation thereof
is performed (step S29).
Further, in the menu screen of FIG. 3, when the passenger touches the return button
8 (step S30), the basic screen of FIG. 2 is displayed (step S31).
[0017] FIG. 9 is a flowchart showing an operation when the elevator running operating system
according to the first embodiment of this invention is coupled to a security system.
Next, the operation during security system coupling will be described.
For example, when a passenger holding a security card checks that card with a card
reader device (authenticating means), only the destination buttons 13 displaying destination
floors allowed to the passenger holding that card are displayed on the touch panel,
and buttons of other floors are not displayed. In the case of FIG. 5, the fourth floor
and the sixth floor are displayed as the destination buttons 13. The message 14 is
an explanation with respect to the fact that the destination floors are limited.
In FIG. 9, first, a security check of the passenger is performed by checking a password
or a card (step S41). Next, just the destination buttons 13 displaying the destination
floors allowed to that passenger are displayed as shown in FIG. 5 (step S42). Next,
the allowed destination buttons 13 are operated, whereby the call is registered (step
S43).
Thus, the elevator goes only to the floors allowed to the passenger and can contribute
to the assurance of security.
[0018] It will be noted that, as the security block (authenticating means) for displaying
the screen shown in FIG. 5, applications such as password input, voice recognition,
and fingerprint matching are conceivable in addition to a card.
Further, it is of course conceivable to apply a security block that limits users with
respect also to the display of the menu button 5 of FIG. 2 and the display of the
schedule button 7 of FIG. 3. Depending on the situation, it is also possible for the
buttons and screens that can be used to be changed in accordance with differences
such as whether the passenger is a common passenger, a company executive, a building
equipment manager, or an elevator maintenance person.
[0019] According to the first embodiment, a running operating system that is excellent in
design and excellent also in expandability of functions can be obtained because it
is possible to move all of the buttons and switches disposed inside the cage and on
the platform to a touch panel.
Further, the addition or deletion of optional operations becomes easily implementable
without having to change hardware devices.
Further, the content that can be operated by the touch panel can be restricted depending
on the person and improvement of the security level is possible by switching and using
screens depending on the user via a security system and password input.
Brief Description of the Drawings
[0020]
[FIG. 1] A block diagram showing a system diagram of an elevator running operating
system according to a first embodiment of this invention.
[FIG. 2] A diagram showing an example of a basic screen of a touch panel of the elevator
running operating system according to the first embodiment of this invention.
[FIG. 3] A diagram showing an example of a menu screen of the touch panel of the elevator
running operating system according to the first embodiment of this invention.
[FIG. 4] A diagram showing an example of a schedule screen of the touch panel of the
elevator running operating system according to the first embodiment of this invention.
[FIG. 5] A diagram showing an example of a screen of the touch panel when the elevator
running operating system according to the first embodiment of this invention is coupled
to a security system.
[FIG. 6] A flowchart showing an operation during common call registration of the elevator
running operating system according to the first embodiment of this invention.
[FIG. 7] A flowchart showing an operation during dedicated call registration of the
elevator running operating system according to the first embodiment of this invention.
[FIG. 8] A flowchart showing an operation during special running command registration
of the elevator running operating system according to the first embodiment of this
invention.
[FIG. 9] A flowchart showing an operation when the elevator running operating system
according to the first embodiment of this invention is coupled to a security system.
Description of the Reference Numerals
[0021]
- 1
- Touch Panel
- 2
- Message
- 3
- Destination Buttons
- 4
- Wheelchair Button
- 5
- Menu Button
- 6
- Special Running Command Buttons
- 7
- Schedule Button
- 8
- Return Button
- 9
- Time Period
- 10
- Time Setting Button
- 11
- Setting Button
- 12
- Cancel Button
- 13
- Destination Buttons
- 14
- Message
- 15
- Elevator Control Panels
- 16
- Cage Stations
- 17
- Platform Stations
- 18
- Cage Touch Panels
- 19
- Platform Touch Panels
- 20
- Group Management Panel