Disclosure of Invention
Problems to be solved by the invention
Here, the power supply on the elevator side may be turned off. The reason why the power supply is turned off is as follows. First, according to the use of a building (e.g., a station, a residential exhibition hall, etc.) in which an elevator is installed, a power supply is disconnected during a night time when the building is not used. Second, the power supply is disconnected for equipment servicing during the stationary period of not using the building (e.g., labrum sections, new years, etc.). Thirdly, power failure occurs in the building due to heavy rain, lightning, and the like, and the power supply is disconnected.
In this way, when the power supply on the elevator side is turned off, a new program cannot be transmitted, and therefore, the program cannot be rewritten or even if a new program can be transmitted, the program may disappear before rewriting.
That is, even if program rewriting from the remote monitoring center side is attempted during a period in which the power supply on the elevator side is turned off, the rewriting may fail. As a result, there are problems that wasteful telephone charges are incurred, or, when program rewriting is performed for a plurality of managed objects, program rewriting for other managed objects is delayed, and thus program rewriting cannot be performed efficiently.
In the conventional technique described in patent document 1, a time zone of whether or not the telephone line is used is recorded, and the time zone of use of the telephone line is shifted to rewrite the program from the outside. However, in such a configuration, even when the power supply on the elevator side is turned off, if the time period is not the use period of the telephone line, the rewriting of the program may fail as a result of an attempt from the outside. In this way, the conventional technique described in patent document 1 still has room for improvement from the viewpoint of efficiency of program rewriting.
The present invention has been made to solve the above-described problems, and an object of the present invention is to obtain a control data rewriting system that realizes high efficiency of rewriting control data for a management object.
Means for solving the problems
The control data rewriting system of the present invention includes: a control device for controlling the operation of the equipment according to the control data, as a control power supply signal indicating the power supply state of the control device power supply, outputting a control power failure signal when the control device power supply is switched from on to off, and outputting a control power restoration signal when the control device power supply is switched from off to on; a monitoring device for monitoring the state of the equipment, as a monitoring power supply signal indicating the power supply state of the monitoring device power supply, outputting a monitoring power failure signal when the monitoring device power supply is switched from on to off, and outputting a monitoring power restoration signal when the monitoring device power supply is switched from off to on; and a control data rewriting device that executes control data rewriting processing for rewriting control data of the control device to the control device, the control device and the monitoring device being provided for each managed object, the control data rewriting device including: a storage device; a power history data generation unit that acquires a control power signal output from the control device and a monitor power signal output from the monitor device, associates the acquired control power signal and monitor power signal with an acquisition date and time at which the control power signal and monitor power signal were acquired, respectively, and stores the acquired control power signal and monitor power signal as power history data for each management object in the storage device; a power on/off history data generation unit that generates control power on/off history data corresponding to a power supply of the control device and monitor power on/off history data corresponding to a power supply of the monitor device for each management object, based on the power history data of each management object; a control data rewriting setting unit that sets, as an object management object, a management object provided with a control device that is an object of execution of the control data rewriting process, and sets a scheduled execution date and time for execution of the control data rewriting process; a control data rewriting date and time determining unit that determines, as an execution date and time, a date and time included in a specific date and time period in which both the control device power supply and the monitoring device power supply are on, the date and time being a date and time at which the control data rewriting process is executed or a date and time after the execution of the predetermined date and time, so that the date and time at which the control data rewriting process is executed do not overlap with the history data of monitoring power supply on/off for each of the target management objects; and a control data rewriting unit that executes control data rewriting processing for each execution date and time of the object management object.
Effects of the invention
According to the present invention, a control data rewriting system can be obtained that realizes efficiency of rewriting control data for a management object.
Detailed Description
Next, a control data rewriting system according to the present invention will be described with reference to the drawings according to a preferred embodiment. In the description of the drawings, the same or corresponding portions are denoted by the same reference numerals, and redundant description thereof is omitted. In the embodiment, the case where the present invention is applied to an elevator is exemplified.
Embodiment mode 1
Fig. 1 is a configuration diagram showing a control data rewriting system according to embodiment 1 of the present invention. Fig. 1 illustrates a case where three management objects, i.e., management objects a to C, exist in the control data rewriting system.
In fig. 1, the control data rewriting system includes a control device 1 and a monitoring device 2 provided for an administrative object a, a control device 1 and a monitoring device 2 provided for an administrative object B, a control device 1 and a monitoring device 2 provided for an administrative object C, a monitoring center device 3, and a control data rewriting device 4. In this way, the control device 1 and the monitoring device 2 are provided for each of the management objects a to C.
The monitoring apparatus 2 is connected to the control apparatus 1 so as to be able to communicate with each other, and is further connected to the monitoring center apparatus 3 so as to be able to communicate with each other. The control data rewriting device 4 is communicably connected to the monitoring center device 3, and is further communicably connected to the monitoring apparatus 2. In addition, a wire line or a wireless line may be used to connect the devices so as to enable communication.
The control device 1 includes a storage device (not shown) that stores control data for controlling the operation of an elevator as a facility. The control data is data used when the control device 1 controls the operation of the elevator, and examples of the control data include a control program, a control parameter, and the like.
The control device 1 controls the operation of the elevator in accordance with the control data stored in the storage device. Specifically, the control device 1 controls, for example, the operation of an elevator hoisting machine, the operation of an elevator car door, and the like as the operation of an elevator.
The control device 1 outputs 2 kinds of power supply signals to the monitoring device 2 as control power supply signals indicating the power supply state of the power supply of the control device. As the control power supply signal, the control device 1 outputs a control power failure signal when the control device power supply is switched from on to off, and outputs a control power restoration signal when the control device power supply is switched from off to on.
The monitoring device 2 monitors the state of the elevator as a device, and outputs the monitoring result to the monitoring center device 3. Specifically, when an abnormality occurs in the elevator to be monitored by the monitoring device 2, an abnormality detection signal is output from the control device 1 that controls the operation of the elevator. The monitoring apparatus 2 acquires the abnormality detection signal output from the control apparatus 1 and outputs the abnormality detection signal to the monitoring center apparatus 3.
The monitoring apparatus 2 outputs 2 kinds of power supply signals to the monitoring center apparatus 3 as monitoring power supply signals indicating the power supply state of the monitoring apparatus power supply. The monitoring device 2 outputs a monitoring power failure signal when the monitoring device power supply is switched from on to off as a monitoring power supply signal, and outputs a monitoring power restoration signal when the monitoring device power supply is switched from off to on. The monitoring apparatus 2 outputs the control power supply signal obtained from the control apparatus 1 to the monitoring center apparatus 3.
The monitoring center device 3 is provided in a monitoring center for monitoring elevators for managing objects collectively. The monitoring center is usually installed at a remote place with respect to each of the management objects a to C. When the monitoring center device 3 acquires the abnormality detection signal from the monitoring device 2, it notifies that the elevator of the management object corresponding to the abnormality detection signal is abnormal.
The monitoring center apparatus 3 outputs the control power supply signal obtained from the monitoring apparatus 2 to the control data rewriting apparatus 4. Similarly, the monitoring center apparatus 3 outputs the monitoring power supply signal acquired from the monitoring apparatus 2 to the control data rewriting apparatus 4.
The control data rewriting device 4 includes a storage device 41, a power supply history data generation unit 42, a power supply on/off history data generation unit 43, a control data rewriting setting unit 44, a control data rewriting date and time determination unit 45, and a control data rewriting processing unit 46. The control data rewriting device 4 is realized by a processing circuit such as a CPU or a system LSI that executes a program stored in a memory. The control data rewriting device 4 may be provided in a facility different from the monitoring center, or may be provided in the monitoring center.
The power history data generation unit 42 acquires the control power signal output from the control device 1 and the monitor power signal output from the monitor device 2. The power history data generation unit 42 associates the acquired control power signal and monitoring power signal with the acquisition date and time at which the control power signal and monitoring power signal were acquired, respectively, as power history data for each of the management objects a to C.
Specifically, the power history data generation unit 42 acquires the control power signal output from the control device 1 of each of the managed objects a to C and the monitor power signal output from the monitor device 2 of each of the managed objects a to C. The power history data generation unit 42 stores the power history data in the storage device 41 for each of the managed objects a to C.
The power on/off history data generation unit 43 generates control power on/off history data corresponding to the control device power supply and monitoring power on/off history data corresponding to the monitoring device power supply for each of the management objects a to C based on the power history data of each of the management objects a to C stored in the storage device 41. The power on/off history data generation unit 43 stores the generated control power on/off history data and monitoring power on/off history data for each of the managed objects a to C in the storage device 41.
Here, the control power on/off history data and the monitoring power on/off history data of each of the management objects a to C are explained with reference to fig. 2 to 4.
Fig. 2 is an explanatory diagram showing an example of control power on/off history data of the managed object a generated by the power on/off history data generation unit 43 in fig. 1. Fig. 3 is an explanatory diagram showing an example of control power on/off history data of the management object B generated by the power on/off history data generation unit 43 in fig. 1. Fig. 4 is an explanatory diagram showing an example of control power on/off history data of the management object C generated by the power on/off history data generation unit 43 in fig. 1.
In fig. 2 to 4, the time period of the non-shaded portion corresponds to a control power on time period during which the control device is powered on, and the time period of the shaded portion corresponds to a control power off time period during which the control device is powered off.
Here, the following operation of the power history data generation unit 42 during the period from "0 at 1 month and 1 day" to "24 at 31 month and 12 days" in the previous year is considered.
< management article A >
The power supply history data generation unit 42 does not obtain the control stop signal and the control reset signal in the previous year.
< management object B >
The power source history data generation unit 42 obtains the control power failure signal at "day 22/8 month 14" in the previous year, and obtains the control power restoration signal at "day 6/8 month 15".
The power source history data generation unit 42 obtains the control power failure signal at "day 22/8/15" in the previous year, and obtains the control power restoration signal at "day 6/8/16".
< management object C >
The power source history data generation unit 42 obtains the control power failure signal at "day 12/8/14" in the previous year, and obtains the control power restoration signal at "day 12/8/16".
In the above case, the power on/off history data generation unit 43 generates control power on/off history data shown in fig. 2 for the management object a. The power on/off history data generation unit 43 generates power on/off history data shown in fig. 3 in which the time period from "22/8/14 to" 6/8/15 and the time period from "22/8/15 to" 6/8/16 as the control power off time period and the other time periods as the control power on time period are set for the managed object B. The power on/off history data generation unit 43 generates power on/off history data shown in fig. 4 in which the time period from "12 at 12 in month 8 to" 12 at 12 in month 8 "to" 12 at day 8 and 16 "is set as the control power off time period and the other time periods are set as the control power on time periods for the managed object C.
The power on/off history data generation unit 43 generates monitoring power on/off history data for each of the management objects a to C by the same processing as the above-described generation of the control power on/off history data.
And, every time the power supply history data generation section 42 stores the latest power supply history data in the storage device 41, the power supply on/off history data generation section 43 updates the control power supply on/off history data and the monitoring power supply on/off history data using the latest power supply history data.
In this way, the power on/off history data generation unit 43 generates control power on/off history data corresponding to the control device power supply and monitoring power on/off history data corresponding to the monitoring device power supply for each of the management objects a to C based on the power history data of each of the management objects a to C stored in the storage device 41.
Returning to the description of fig. 1, the control data rewrite setting unit 44 sets, as the target management object, a management object to which the control device 1 is set, the control data rewrite processing for rewriting the control data of the control device 1. Specifically, the control data rewrite setting unit 44 sets the target management object in accordance with an instruction from the outside. For example, if an operator inputs an object management object for which the control device 1 is expected to execute the control data rewriting process via a terminal device (not shown) or the like, the control data rewriting setting unit 44 sets the object management object.
The control data rewrite setting unit 44 sets a date and time scheduled for execution of the control data rewrite processing. For example, the control data rewriting setting unit 44 may be configured to set the date and time at which the operator inputs the object management object via the terminal device as the scheduled execution date and time, or may be configured to set the date and time designated by the operator via the terminal device as the scheduled execution date and time.
The control data rewriting date and time determination unit 45 determines the execution date and time at which the control data rewriting process is executed for each target management object, based on the control power on/off history data and the monitoring power on/off history data for each target management object. In this case, the control data rewriting date and time determining unit 45 determines to make the execution dates and times of the respective target managed objects not coincide with each other.
More specifically, the control data rewriting date and time determination unit 45 determines, as the execution date and time, the date and time included in the time period during which both the control device power supply and the monitoring device power supply are on, which is the date and time set by the control data rewriting setting unit 44 as the scheduled execution date and time or the date and time after the scheduled execution date and time, so that the execution date and time do not overlap for each target management object. In addition, hereinafter, a period during which both the control device power supply and the monitoring device power supply are turned on is referred to as a "specific date period".
Specifically, when the execution scheduled date and time is included in the specific date and time period in the control power on/off history data and the monitoring power on/off history data, the control data rewriting date and time determining section 45 sets the execution scheduled date and time as the execution date and time.
On the other hand, when the scheduled execution date and time is not included in the specific date and time zone, the control data rewriting date and time determination unit 45 sets, as the execution date and time, a date and time that is later than the scheduled execution date and time and is included in the specific date and time zone. In particular, if the control data rewriting process is configured such that the date and time closest to the scheduled execution date and time included in the specific date and time zone after the scheduled execution date and time is set as the scheduled execution date and time, the control data rewriting process can be performed quickly.
In addition, when there is no on/off history data after the execution of the scheduled day or the scheduled day set by the control data rewrite setting unit 44 out of the control power on/off history data and the monitoring power on/off history data, the on/off history data after the execution of the scheduled day or the scheduled day may be predicted using the on/off history data obtained before the current time, and the execution date and time may be determined based on the prediction result.
The control data rewriting processing unit 46 executes the control data rewriting process according to the execution date and time of each target managed object determined by the control data rewriting date and time determining unit 45.
Specifically, the control data rewrite processing unit 46 outputs new control data and a rewrite instruction signal to the monitoring apparatus 2 in order from the target management object whose execution date and time is earlier. The monitoring device 2 outputs the new control data and the rewrite command signal to the control device 1.
When new control data and a rewrite instruction signal are input, the control device 1 rewrites the control data stored in the storage device at the present time to the new control data in accordance with the rewrite instruction signal. In this case, the control device 1 controls the operation of the elevator using the new control data.
Next, an example of the operation of the control data rewriting date and time determining unit 45 and the control data rewriting processing unit 46 will be described with reference to fig. 2 to 4.
Here, it is assumed that the power on/off history data generation unit 43 generates the control power on/off history data shown in the foregoing fig. 2 to 4, and further generates the monitoring power on/off history data similar to the control power on/off history data shown in the foregoing fig. 2 to 4. The target managed objects set by the control data rewrite setting unit 44 are managed objects a to C, and the scheduled execution date and time set by the control data rewrite setting unit 44 is "13 days 8 months and 15 days" of the present year.
In the above case, the control data rewriting date and time determination unit 45 determines the execution date and time of the management object a based on the control power on/off history data and the monitoring power on/off history data (see fig. 2) corresponding to the management object a. As can be seen from fig. 2, in the control power on/off history data and the monitoring power on/off history data corresponding to the management article a, "8 months, 15 days, and 3 hours" as the execution scheduled date and time are included in the specific date period. In this case, the control data rewriting date and time determination unit 45 sets the execution date and time of the managed object a to "8 months, 15 days, and 3 hours".
The control data rewriting date and time determination unit 45 determines the execution date and time of the management object B based on the control power on/off history data and the monitoring power on/off history data (see fig. 3) corresponding to the management object B. As can be seen from fig. 3, in the control power on/off history data and the monitoring power on/off history data corresponding to the management object B, "8 months, 15 days, and 3 hours" as the execution scheduled date time is not included in the specific date period. In this case, the control data rewriting date and time determination unit 45 sets the execution date and time of the managed object B to "8 months, 15 days, and 6 hours". The "8 th, 15 th, and 6 th" is a date and time later than the execution scheduled date and time and included in the specific date and time period.
The control data rewriting date and time determination unit 45 determines the execution date and time of the management object C based on the control power on/off history data and the monitoring power on/off history data (see fig. 4) corresponding to the management object C. As can be seen from fig. 3, in the control power on/off history data and the monitoring power on/off history data corresponding to the management object C, "8 months, 15 days, and 3 hours" as the execution scheduled date time is not included in the specific date period. In this case, the control data rewriting date and time determination unit 45 sets the execution date and time of the managed object B to "12 hours on day 16/8 month". The "8 th, 16 th, and 12 th hour" is a date and time later than the execution scheduled date and time and included in the specific date and time period.
In this way, the control data rewriting processing unit 46 executes the control data rewriting process in accordance with the execution date and time of each target managed object determined by the control data rewriting date and time determining unit 45. That is, the control data rewrite processing unit 46 executes the control data rewrite processing in the order of "time 8/15/3" is management object a, "time 8/15/6" is management object B, "time 8/16/12" is management object C.
Next, another example of the operation of the control data rewriting date and time determining unit 45 and the control data rewriting processing unit 46 will be described with reference to fig. 2 to 4, as in the above description.
Here, the power on/off history data generation unit 43 generates the control power on/off history data shown in the foregoing fig. 2 to 4, and further generates the monitoring power on/off history data similar to the control power on/off history data shown in the foregoing fig. 2 to 4. The target management object set by the control data rewrite setting unit 44 is the management object B, C, and the scheduled execution date and time set by the control data rewrite setting unit 44 is "8 months, 16 days, and 15 days" of the present year.
In the above case, the control data rewriting date and time determination unit 45 determines the execution date and time of the management object B based on the control power on/off history data and the monitoring power on/off history data (see fig. 3) corresponding to the management object B. As can be seen from fig. 3, in the control power on/off history data and the monitoring power on/off history data corresponding to the management object B, "day 15 of 16 months of 8" as the execution scheduled date time is included in the specific date period.
The control data rewriting date and time determination unit 45 determines the execution date and time of the management object C based on the control power on/off history data and the monitoring power on/off history data (see fig. 4) corresponding to the management object C. As can be seen from fig. 4, in the control power on/off history data and the monitoring power on/off history data corresponding to the management object C, "8 months, 16 days, and 15 hours" as the execution scheduled date and time are included in the specific date period.
As described above, when the execution scheduled dates and times are included in the specific date and time periods in the respective object management objects, the adjustment is made so that the execution dates and times do not coincide with each other in the respective object management objects. For example, the control data rewriting date and time determination unit 45 sets the execution date and time of the management object B to "8 month, 16 th and 15 th", and shifts the execution date and time of the management object C by an arbitrary time from "8 month, 16 th and 15 th", for example, to "8 month, 16 th and 16 th".
In the above case, the control data rewrite processing unit 46 executes the control data rewrite processing in the order of "day 16/8" and "day 16/8" being the management object B and "day 16/8" being the management object C. In the management object a, since the target management object is not set, the control data rewriting process is not executed.
In embodiment 1, when the control data rewriting process is executed for each execution date and time of the target management object, it is confirmed that both the control device power supply and the monitoring device power supply are turned on at the time of the execution date and time, and the execution of the control data rewriting process for the target management object whose control device power supply or monitoring device power supply is turned off may be suspended.
In this case, the control data rewriting processing unit 46 stops execution of the control data rewriting process with respect to the control device of the management object to which the power supply of the control device or the power supply of the monitoring device is turned off when the control data rewriting process is executed. Further, it is possible to confirm whether the control device power supply and the monitoring device power supply are each turned on or off, based on the control power supply signal and the monitoring power supply signal input to the control data rewriting device 4.
In addition, embodiment 1 exemplifies a case where the following structure is used: the control data rewriting system includes a monitoring center device 3 that acquires a monitoring result of an elevator as equipment from a monitoring device 2, and a power supply history data generation unit 42 acquires a control power supply signal from the control device 1 via the monitoring device 2 and the monitoring center device 3, and acquires a monitoring power supply signal from the monitoring device 2 via the monitoring center device 3. However, in the control data rewriting system, the monitoring device 2 may be configured to directly output the control power supply signal and the monitoring power supply signal to the control data rewriting device 4 without passing through the monitoring center device 3.
As described above, according to embodiment 1, the control data rewriting process is executed for each target management object by determining, as the execution date and time, the date and time included in the specific date and time period in which the control device power supply and the monitoring device power supply are both on, which is the execution scheduled date and time or the date and time after the execution scheduled date and time, so that the execution date and time do not overlap for each target management object, based on the control power on/off history data and the monitoring power on/off history data for each target management object.
With this configuration, since the control data rewriting process can be executed with a date and time slot shifted from the previous power-off date and time slot, wasteful telephone charges can be reduced, and the execution of the control data rewriting process when the power is off can be reduced. In addition, when control data is rewritten for a plurality of managed objects, the time for completing rewriting of control data for all the objects can be shortened. Thus, the efficiency of rewriting control data for the managed object can be improved.
In embodiment 1, the present invention is applied to an elevator as an example, but the present invention is not limited to this, and the present invention can be applied to any equipment other than an elevator as long as the control data of a control device that controls the equipment can be remotely rewritten.
Description of the reference symbols
1 a control device; 2 a monitoring device; 3 monitoring the central device; 4 controlling the data rewriting device; 41 a storage device; 42 a power source history data generating unit; 43 a power on/off history data generating section; 44 a control data rewrite setting unit; 45 a control data rewriting date and time determining part; 46 controls the data rewrite processing section.