JPH0321471B2 - - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Application of the Invention] The present invention relates to an elevator control device, and more particularly to a group management elevator control device having a management function for centrally managing a plurality of elevators.

[Background of the invention]

In recent years, computer technology has improved, especially microcomputers, with improvements in functionality and cost optimization.
It is widely used as an industrial control device.

Furthermore, due to the widespread use of 16-bit microcomputers, these control devices are sometimes equipped with various functions based on advanced control in addition to conventional functions.

In particular, many of these additional functions have been developed and put into practical use, including learning functions, adaptive abilities, and diagnostic functions.

However, it is generally difficult to grasp malfunctions or operating conditions of these control devices, and this also poses a problem when applied to elevator control devices.

In other words, conventional maintenance equipment for elevator control equipment specifies the address of the data you want to check,
The data was output to a display such as a CRT or a printer, or continuously recorded on magnetic tape.

In addition, the location of each elevator and the registration status of hall calls can be displayed and monitored on a CRT, or the constantly changing operation status can be printed out one after another on a printer, or the operation monitor data can be recorded on a magnetic tape or the like. Various maintenance measures were taken, such as reproducing the elevator operation monitor data on a separate device and plotting it on an X-Y plotter.

However, these conventional methods simply output current elevator control information or group management information, and could not be used as a means for confirming data related to learning functions or the like.

That is, operators, maintenance personnel, and the like often do not know how the management control processing is executed by the microcomputer. Furthermore, each partial function of a group of processes is often completed within one second, and there are many cases where confirmation cannot be made.

Therefore, there is no effective means of collecting maintenance data for checking the execution control status of functions that are executed only once a day or a month, or for debugging in the unlikely event that a program defect occurs.

In addition, when evaluating the service status of each elevator and selecting the most suitable elevator, there was no means of collecting processing data to judge the control status, and it was not possible to check the processing operation process of the elevator control device in the operating state. .

In other words, the control status was simply determined based on which elevator the generated hall call was assigned to, and the quality of the elevator control was conceptually determined based on the call generation record and the operation record data of each elevator. .

[Purpose of the invention]

In computer group management control, this invention provides:
It is an object of the present invention to provide a group management elevator control device that allows for highly efficient and reliable debugging, maintenance, adjustment, and monitoring of actual equipment by entering arithmetic processing inside a computer.

[Summary of the invention]

To achieve this objective, according to the invention:
An output request signal for data to be confirmed from the maintenance device is inputted to the elevator control device in advance, and a data output means provided in the elevator control device detects that the necessary data has been created, that is, the data has been updated. The requested data is output to the maintenance device.

[Embodiments of the invention]

Embodiments of the present invention will be described below with reference to the accompanying drawings.

FIG. 1 shows a system diagram according to an embodiment of the present invention.

According to the figure, three elevator control devices 1
Elevator H, 2H, 3H, elevator maintenance device 1D, group control elevator management device M, and elevator monitoring device 1U are provided.

The elevator maintenance device 1D is equipped with a microcomputer (hereinafter referred to as a microcomputer), and is connected to a data adapter S of the group management elevator management device M via a serial data adapter (hereinafter referred to as a data adapter S1D) of a communication device.
Connected to 9M, elevator maintenance equipment 1
It is possible to send and receive data necessary for the D screen display and test mode data.

Regarding this data adapter,
For details, refer to No. 56-37972 and JP-A No. 56-37973.

The group control elevator management device M includes an operating microcomputer MG and a standby microcomputer ML that operates when the operating microcomputer MG fails. The operation system microcomputer MG is connected to the data adapter S11 of the elevator control device 1H via the data adapter S1M, making it possible to send and receive data such as car position and call allocation control.

Although this embodiment shows only three elevator control devices 1H, 2H, and 3H as described above, it goes without saying that four or more elevator control devices may be used.

Inside the elevator control devices 1H to 3H, there is a main control microcomputer 1Z that processes call service control, etc.
(Although only the device 1H will be explained, it goes without saying that the same applies to the others).
It is connected via a data adapter S14 to a data adapter S15 of a slave control microcomputer 1V that processes speed control, elevator position control, etc., and allows data such as car weight to be sent and received.

It is also connected to a microcomputer adapter S17 for controlling the voice guidance device via a data adapter S13. Furthermore, it is connected via a data adapter S12 to a data adapter S16 in the on-car control microcomputer 1C that controls the in-car operation panel switch, making it possible to send and receive data for door stops, dedicated switches, etc.

With the above configuration, elevator maintenance device 1
It is possible to monitor the contents of the operation system microcomputer MG of the group management elevator control device M by operating commands from D.

Furthermore, it is possible to monitor the contents of the main control microcomputer 1Z via the operation system microcomputer MG.

Furthermore, the elevator maintenance device 1D is provided with functions similar to those of a general computer, and can execute interactive operation commands based on the key input rate and the monitor unit. Using the key operation input function, input a data output command that requests data output in a predetermined format, send it to the group management control elevator, and when the predetermined condition is met, send the requested data to the maintenance device 1D, It is possible to check and monitor a group of data that changes from moment to moment.

In particular, as shown by dotted lines in FIG. 1, the elevator monitoring device 1U and the elevator maintenance device 1D
All elevator controls can be monitored via the microcomputer not only in the elevator machine room but also in the building monitoring room, and the data collected and organized in the elevator monitoring device 1U can also be requested to the maintenance device 1D. can be automatically output according to the

Figure 2 shows the elevator maintenance equipment 1D in Figure 1.
This is an outline of the flowchart that is executed. Note that the numbers inside the brackets correspond to the numbers of each step.

In the same flowchart, data is exchanged with the group control elevator management device M for group control status monitor control processing (D400) or test pattern generation (D150).

Further, an operation command such as a data transmission request to the maintenance device 1D is created by operating a switch or a keyboard (D200), and preparations are made for the subsequent transmission process ((D500)).

Other treatments are conventionally known.

Therefore, by inputting a key, the data to be received is specified and a data transmission request flag is transmitted to the group control elevator management device M. Furthermore, at the same time as the device M starts receiving the requested data, the data is printed out by output processing to the printer (D380). It is also possible to request output to a cassette instead of a printer (D360).

FIG. 3 is an outline of a flowchart executed by the group control elevator management device M of FIG.

According to the same flowchart, after initialization processing (M100), simulation (M200) is always performed, creating a multitasking configuration.

FIG. 4 is a schematic flowchart of group management elevator control that is periodically activated by an interrupt (IRQ).

According to the same flowchart, based on the data transmission request flag received through communication processing (M340) with the elevator maintenance device 1D, it is determined whether or not the requested data is to be transmitted to the elevator maintenance device 1D, and the data transmission is performed. Control preparation (M500A,
M500B, M500Z), and also controls communication with maintenance equipment 1D (M320, M520).

Other processing can be performed using conventional programs.

FIG. 5 is a flowchart for determining whether the conditions for data transmission to the maintenance device 1D are satisfied and for preparing for data transmission.

This program is a common subroutine called with arguments from the maintenance data transmission control (M500A to M500Z) shown in FIG.

First, create a transmission request register as shown in Figure 6.
Depending on whether the DO bit of TXCBiR is "1", it is determined whether there is a request to transmit the data (M900).
Whether or not other data is being transmitted is determined based on whether the buffer flag TXBF in FIG. 6 is "0" (M910). Furthermore, whether a predetermined condition such as whether the data has been updated or not is determined by checking whether the product of the data transmission condition flag 1 in FIG. 6 and the TXCIBiTR flag shown in FIG. 7 and D2 is "1". (M920) and prepares for data transmission (M240A).

Furthermore, a transmission request can be made immediately upon table control when the second predetermined condition is satisfied.

For example, as shown in FIG. 6, 15 of the data transmission request flag register TXCBiTR is
When the bit is set to “1”, the step shown in Figure 4
From the M500Z, set the 15th bit to “1” in the argument DO, and when a predetermined number of passengers (approximately 100) are detected, D2
The 15th bit is set to "1" and the data transmission control routine (M500) shown in FIG. 5 is called.

According to the interrupt processing shown in Fig. 4, since a high-speed response is required, step M910 is specially provided to suspend the 1st transmission processing, and then repeat the step when processing the next interrupt.
Determine whether other data output processing is completed using M910.

Therefore, when preparing for data transmission in step M240A, the argument DO is set to a small value (for example, "0") and the flowchart program M240 shown in FIG. 10 is called.

Figure 10 is a simulation (M200) described later.
9 shows a data transmission preparation flow that is also called from the flowchart (FIG. 9).

First, it is determined whether the transmission buffer is free (241), and if it is in use, it waits for it to become free until the cutoff time specified by argument D1 has elapsed. Then, to prevent the data from being updated, data update prohibition processing is performed (244). This is mainly effective when calling from FIG.

Next, in step 242, the 15th bit of the flag TXCRBiTR (argument
If the request is a one-time request, the 15th bit (the bit indicated by the argument DO) of the data transmission request flag register TXCBiTR is set to “0” in step 243. Clear and control to limit data transmission to one time.

Next, send buffer in use flag with 245
The 15th bit of TXBF (the bit indicated by the argument DO) is set to "1", and in step 246, the data on the number of passengers collected for a predetermined period for each floor direction is sent to the buffer.
Temporarily stored in TXBUF.

In addition, in step 247, the maintenance device 1D waits while determining whether the termination time has elapsed in step 248 until the reception preparation completion flag TXROKF, which indicates that the process of outputting the data previously transmitted to the printer, etc., has been completed returns to "1". (This is also useful when calling from Figure 9).

If the transmission preparation is completed within the cutoff time (argument D1), the transmission register TXBiTR is set in step 249.
Set the 15th bit (bit of argument DO) to “1”.

By setting the transmit register TXBiTR, the fourth
Step M520 shown in FIG.
The data on the number of people getting on and off the train temporarily recorded in the maintenance device 1D is sequentially transmitted to the maintenance device 1D.

First, in step 522, it is determined whether or not data is being transmitted, and if the data is currently being transmitted (TXCNT = 0), the data transmission register to the maintenance device 1D is
It is determined whether TXBiTR is greater than "1" (523), and 15 bytes of data are set in the reception register of the data adapter from the beginning of the transmission buffer TXBF (525). At this time, the transmission counter TXCNT is counted up one by one (529) until there is a determination that the transmission is complete (527).

The data sent to the maintenance device 1D is used to print out the number of people getting on and off each floor or the weight of people getting on and off each floor as shown in FIG. 8 by a printer T connected to the maintenance device 1D.

Furthermore, there are various ways to determine whether the predetermined condition is satisfied (M920), that is, how to create the argument D2, depending on the nature of the transmission data.

For example, in step M500B,
As shown in , it is determined separately in response to requests whether the reallocation is a long-waiting reassignment or a full-occupancy reassignment.

In step M500B, for example, the first bit of D2 is set to "1" if there is a long wait, the second bit is set to "1" if it is a full reassignment, and the third bit is set to "1" if it is an additional assignment.

Also, at this time, a step can be set to request not only one transmission permission flag but also multiple types of data transmission.
M240 may also be configured.

For example, in step M500A, it is determined that hall call allocation has been executed due to the generation of a new hall call, and the transmission permission register shown in FIG.
The configuration is such that the 14th bit and 0th bit of TXBiTR are set, and both the predicted arrival time data for all floors of each elevator unit at the time of allocation, the call assignment evaluation value for each elevator unit, and the data that is its element are temporarily stored. It is recorded (246) and sent to the maintenance device 1D (M520).

The call allocation evaluation value and its elemental data are: (1) Predicted arrival time to the relevant hall call (2) Predicted car load value at the time of the relevant hall call service (main input data for crowd prediction control) (3) ) Predicted number of passengers at the time of the relevant hall call service (main input data for passenger count weighted waiting time control) (4) Predicted number of passengers remaining at the time of the relevant hall call service (main input data for centralized service control) (5) Number of passengers expected for the relevant hall call service Predicted number of people getting off at the time (6) Hall call duration at the time of the hall call assignment (7) Car load at the time of the hall call assignment (8) Service priority value for the hall call assignment (9) Area at the time of the hall call assignment Priority value (10) This is the maximum overall evaluation and the floor (maximum waiting time evaluation value) when the relevant hall call is assigned, and these data are organized and created separately for all elevator stands.

These data are temporarily stored in the transmission buffer at high speed at the same time as hall call assignment, and the temporarily recorded data is sent to the maintenance device 1D in parallel with other hall call registration and assignment processing.

Transmission can be from 1 byte to 16 bytes per IRQ. This varies depending on what type of communication circuit is used between the management control device M and the maintenance device 1D. Here, since the aforementioned data adapter is used, 15 bytes can be sent every 30 ms, which is sufficient to send data to the maintenance device 1D.

FIG. 9 is a flowchart of a program for executing simulation (M200).

There is an area priority parameter which is a weighting coefficient as a simulation parameter, and simulation is executed for each parameter case.

First, simulation data such as destination traffic volume is set (M205). Next, area priority parameters are set (M210) and simulation is executed (M220).

Next, each time the simulation ends, it is checked whether there is a data transmission request flag for the simulation result using the register TXCBiTR.
Determine whether the first bit of TXC2BiTR is both “1” (M225), and if the above flag is present,
It is determined whether it is possible to send data to the elevator maintenance device 1D, and preparations are made to send simulation result data such as the average waiting time for each floor.

FIG. 10 is a flowchart showing this detailed process.

If a problem occurs such as maintenance device 1D breaking down or printer T running out of paper, and data transmission abort time exceeds the value of argument D1 and a data output error is detected (M244), the next simulation process etc. will start. In order to enable this, the system is configured so that the inhibition of data updating is canceled in response to a data output abnormality detection signal, so that the management control function does not go down.

Furthermore, after completing the simulation for all area priority parameters (M230), a request can be made to output the last simulated result (M235, M247D). It is now possible to output the optimal area priority parameter value (M280), etc. in the same way as the above process (M290,
M240E).

For example, if you want to send the simulation result data from the first to third times of the area priority parameter and the data at the end of all cases of the above parameters during simulation execution, repeat the transmission request as shown in Figure 13. The first bit of the flag TXCRBiT is set to "1", and the second bit of the data transmission request condition flag TXC2BiTR is set to "1".

If you perform the above operation, request data will be sent every time one simulation case is completed (M225,
M240C). Furthermore, upon completion of a predetermined number of simulations (three times in this case), request data such as the optimum calculation result is transmitted (M290, M240E).

FIG. 12 shows this example in elevator maintenance equipment 1.
A case is shown in which the image is printed out using a printer T connected to D. This makes it easy to monitor the simulation situation and improves debugging and confirmation efficiency.

In the above embodiment, the operation microcomputer MG has been described as including advanced intelligent processing for diagnosing simulation and its results.In order to perform these processes at high speed, the standby microcomputer ML
It is also possible to have a configuration in which these processes are moved to.

In addition, as shown in FIG. 1, in the embodiment, the maintenance device 1D was connected to the group management microcomputer via the data adapter, but a recording device such as a printer T and the management control device M may be directly connected to each other. By adding all or part of the processing functions shown in FIG. 2 to the microcomputer MG or ML in the control device, the maintenance device S1D shown in FIG. 1 can be made unnecessary and the configuration can be simplified.

〔Effect of the invention〕

According to the present invention, with the above configuration, it is possible to easily and reliably output the data necessary for debugging, maintenance, adjustment, and monitoring of the actual machine, and for this purpose, elevator control equipped with advanced control functions is possible. It is possible to provide an apparatus, particularly a group management elevator control apparatus, which includes means for controlling call assignment to a plurality of elevators.

[Brief explanation of the drawing]

FIG. 1 is a system diagram of an embodiment of the present invention, FIGS. 2 to 5 are flowcharts explaining the main operations of the embodiment of FIG. 1, and FIGS. A configuration diagram of a flag register, FIG. 8 is a diagram showing an example of data printout according to the present invention, and FIG.
10 and 11 are flowcharts illustrating the operation of other main parts of the embodiment of the present invention.
FIG. 2 is a diagram showing an example of data printout according to the present invention, and FIG. 13 is an explanatory diagram of a table for controlling transmission of data to main parts of the embodiment of the present invention. M...Group control elevator management device, MG...
Operation system control microcomputer, ML...Standby system microcomputer,
1U...Elevator monitoring device, 1D...Elevator maintenance device, 1H, 2H, 3H...Elevator control device, T...Printer.

Claims (1)

[Scope of Claims] 1. An elevator control device that controls a plurality of elevators serving multiple floors, a management control device that is connected to this control device and manages and controls each of the elevators, and a maintenance device that maintains and manages the elevators. In an elevator control device comprising a data transmitting/receiving means for transmitting and receiving data of the device, the management control device includes a storage means for storing a data output request signal inputted from the maintenance device;
The present invention further comprises means for automatically outputting the data requested to be outputted after the update to the maintenance device when an update of the data requested for outputting the data stored in the storage means to the maintenance device is detected. Characteristic group management elevator control device. 2. In the device according to claim 1,
The data output is ensured by including means for prohibiting updating of the data in the storage means from the time when the update of the data requested for data output is detected until the data output to the maintenance device is completed. A group control elevator control device characterized by: 3. In the device according to claim 2,
comprising data output abnormality detection means for detecting that data output to the maintenance device exceeds a predetermined time limit;
The group management elevator control device is characterized in that the prohibition of updating the data is canceled by this detection signal, and the elevator control function is prevented from stopping when an abnormality occurs in the maintenance device. 4. In the device according to claim 1,
A group management elevator control device, wherein the elevator control device has a function of erasing the memory of the data output request signal when the data output is executed in response to a data output request. 5. In the device according to claim 1,
The data transmitting/receiving means temporarily stores the data to be transmitted when the data outputting means detects an update of data requested for data output in a storage means exclusively for transmission, and then sequentially transmits this stored data to the maintenance device. A group management elevator control device characterized in that the time lag of data to be transmitted is suppressed.