Software rewriting system and software rewriting method

The software rewriting system optimizes elevator software updates by aligning with building schedules and user patterns to reduce downtime and user inconvenience, ensuring efficient and reliable elevator operation.

JP7595518B2Active Publication Date: 2024-12-06HITACHI LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
JP2021085176
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-05-20
Publication Date
2024-12-06
Estimated Expiration
2041-05-20

AI Technical Summary

Technical Problem

Existing elevator software rewriting methods cause inconvenience to users due to unpredictable downtime and potential program rewrite failures, as they rely on remote monitoring and manual scheduling, failing to account for unoccupied times and building management schedules.

Method used

A software rewriting system that determines optimal switching timings based on building management information, user usage patterns, and program change size, allowing for remote software updates without user inconvenience by prioritizing times with minimal user impact.

Benefits of technology

Enables software updates at times that minimize elevator downtime and user disruption, ensuring quick response to failures and maintaining continuous elevator operation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007595518000001
    Figure 0007595518000001
  • Figure 0007595518000002
    Figure 0007595518000002
  • Figure 0007595518000003
    Figure 0007595518000003
Patent Text Reader

Abstract

To provide a system capable of rewriting software used for a control object of an elevator without inconveniencing an elevator user.SOLUTION: A software rewriting system 1 comprises: a program storage unit 34 that stores a program used for a control object of an elevator 10; a building management information storage unit 33 that stores building management information about a building in which the elevator 10 is installed; and a switching timing generation unit 31 that generates, on the basis of the building management information acquired from the building management information storage unit 33, a switching timing for switching the program used for the control object to a program provided for the control object from the program storage unit 34, and outputs the switching timing.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a system and method for rewriting software used in, for example, elevators. [Background technology]

[0002] Conventionally, the programs used in elevators were rewritten by programs distributed from a monitoring center that remotely monitors elevators. The files of the programs distributed to elevators are large, and it takes time to rewrite the programs. Therefore, elevator maintenance staff often decided on the date and time for program rewriting. For example, based on the maintenance staff's experience, they sometimes decided on a date and time when there were few users as the date and time for program rewriting.

[0003] When rewriting the program, the elevator needs to be stopped, which means that there is a period of time when users cannot use the elevator. For this reason, elevator managers and users requested that the time that the elevator is down while the program is being changed be minimized.

[0004] Patent document 1 states that "When it is determined that the cage is unoccupied (there is no user in the cage), the data regarding specifications stored in the memory unit of the control microcomputer can be rewritten to correspond to the specification information." [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2018-193146 A Summary of the Invention [Problem to be solved by the invention]

[0006] The technology described in Patent Document 1 can detect when the car is empty at a certain moment, but cannot determine whether the time the car is empty is longer than the time it takes to rewrite the program. Also, even if the car happens to be empty and program rewriting begins, a user who enters the elevator while the rewriting is in progress cannot use the elevator until the rewriting is complete.

[0007] Furthermore, if a program rewrite fails, the building manager must take action such as requesting the dispatch of an elevator maintenance worker and informing users that the elevator will be out of service for an extended period of time. However, if the building manager is not present, these actions will not be taken, and the elevator will be out of service for an extended period of time. Thus, if the building manager cannot manage when the program rewrite takes place, responses to unforeseen events will be delayed.

[0008] The present invention has been made in view of the above circumstances, and has an object to make it possible to rewrite software to be controlled at a timing that does not cause inconvenience to users. [Means for solving the problem]

[0009] The software rewriting system according to the present invention includes a software storage unit that stores software used in an elevator control object, and a building management information storage unit that stores building management information of a building in which the elevator is installed. When the changes to the software to be transferred to the controlled object are large, the longer the work time for the building or elevator, the higher the priority is assigned to the work content for the work on the building or elevator; when the changes to the software are small, the shorter the work time, the higher the priority is assigned to the work content; A timing for switching the software used in the controlled object to the software provided to the controlled object from the software storage unit based on the building management information acquired from the building management information storage unit. The timing of switching is determined based on the priority determined by the building management schedule included in the building management information and the time required to rewrite the software in the controlled object. Generate Based on the priority specified by the work content and work schedule included in the management schedule or the non-use time of the building, and the priority according to the size of the changes to the software, multiple candidate switching timings are generated in descending order of priority, the multiple candidate switching timings are output to the building manager, and approval of the switching timings is requested from the building manager. and a switching timing generation unit for generating a switching timing. Effect of the Invention

[0010] According to the present invention, it is possible to rewrite software that is a control target at a timing that does not cause inconvenience to users. Problems, configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0011] [Figure 1] 1 is a block diagram showing an example of a configuration of a software rewriting system according to a first embodiment of the present invention; [Diagram 2] 2 is a block diagram showing a configuration example of a hall terminal unit according to the first embodiment of the present invention; FIG. [Diagram 3] 1 is a block diagram showing an example of a hardware configuration of a computer according to a first embodiment of the present invention. [Figure 4] 5 is a flowchart showing an example of processing by a switching timing generation unit according to the first embodiment of the present invention. [Diagram 5] 5 is a flowchart showing an example of a process in which a switching timing generation unit according to the first embodiment of the present invention proposes a switching priority. [Figure 6] 4 is a list showing examples of priorities set in registration items of a scheduler according to the first embodiment of the present invention. [Figure 7] FIG. 11 is a diagram showing how priority changes depending on the amount of program changes, the type of work, and the work time according to the first embodiment of the present invention. [Figure 8] 5 is a flowchart showing an example of a program switching process performed by a hall terminal control unit of a machine control unit in the first embodiment of the present invention. [Figure 9] 5 is a flowchart showing an example of processing performed by a hall terminal unit according to the first embodiment of the present invention. [Figure 10] FIG. 11 is a block diagram showing a configuration example of a software rewriting system according to a second embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings. In this specification and the drawings, components having substantially the same functions or configurations are designated by the same reference numerals, and redundant description will be omitted.

[0013] [First embodiment] FIG. 1 is a block diagram showing an example of a configuration of a software rewriting system 1 according to the first embodiment. The software rewriting system 1 includes a maintenance management unit 2, a unit control unit 3, a building management unit 4, and an elevator 10. Below, a process of rewriting and switching a program will be described as an example of software used in the elevator 10. The software includes a program executable by the car unit 5, the hall terminal unit 6, or the motor unit 7 (examples of objects to be controlled), as well as at least one of various parameters and data (e.g., threshold values) used in the program. The process of rewriting and switching the software includes the process of rewriting and switching the program, as well as the process of rewriting and switching parameters or data.

[0014] The maintenance management unit 2 is provided in a monitoring center that remotely monitors the operation of the elevator 10. The maintenance management unit 2 remotely monitors not only the operation of the elevator 10 shown in FIG. 1, but also the operation of other elevators 10 (not shown) installed in other buildings. This maintenance management unit 2 manages maintenance information for maintaining the elevator 10. The maintenance information includes, for example, the operation status of the elevator 10 as well as programs to be distributed to the elevator 10. For example, the maintenance management unit 2 distributes to the elevator control unit 3 a program used in the hall terminal unit 6 (an example of an object to be controlled) of the elevator 10.

[0015] The building management unit 4 is an information processing terminal installed, for example, in a management office of the building in which the elevator 10 is installed. The building management unit 4 manages building management information including a building management schedule. The building management schedule records power outage dates, maintenance dates, and the like. The building management unit 4 passes the building management schedule to the unit control unit 3 in accordance with a request from the unit control unit 3. The building management unit 4 also obtains the program switching timing (including rewriting and switching date and time) generated by the switching timing generation unit 31. The building manager can approve or disapprove the program switching timing through the building management unit 4. The building management unit 4 then outputs information indicating that the building manager has approved or disapproved the program switching timing to the switching timing generation unit 31.

[0016] The functions of the building management unit 4 may be realized by a scheduler including a calendar function provided in the cloud. For example, the unit control unit 3 can input a login ID and password to the cloud scheduler to obtain the building management schedule for a predetermined period of time.

[0017] The elevator 10 includes a car unit 5, a hall terminal unit 6, and a motor unit 7. The car unit 5, the hall terminal unit 6, and the motor unit 7 are examples of objects to be controlled according to the present embodiment. The car section 5 moves up and down in a hoistway (not shown) provided in the building. The hall terminal unit 6 is provided on the hall floor of the building and is used by users to register hall calls. The motor unit 7 winds a rope attached to the car unit 5 and the weight to raise and lower the car unit 5.

[0018] The elevator control unit 3 includes a switching timing generation unit 31, a user information analysis unit 32, a building management information storage unit 33, a program storage unit 34, a car control unit 35, a hall terminal control unit 36, and a motor control unit 37. The car control unit 35, the hall terminal control unit 36, and the motor control unit 37 are examples of the control unit according to this embodiment.

[0019] The user information analysis unit 32 analyzes the user information acquired from the elevator 10 to determine the time period during which the elevator 10 is used less frequently. The user information analysis unit 32 analyzes the car information acquired from the car control unit 35 (e.g., the presence or absence of a user in the car for each hour) and the hall terminal information acquired from the hall terminal control unit 36 ​​(e.g., the presence or absence of a user in the hall for each hour) as user information. Here, the user information analysis unit 32 analyzes the log of information acquired by sensors around the hall terminal unit 6, which is uploaded via the hall terminal control unit 36, as user information, and is able to grasp the time period during which the user uses the elevator 10. The analysis result of the user information by the user information analysis unit 32 (e.g., the time period during which the elevator 10 is used less frequently) is output to the switching timing generation unit 31.

[0020] The building management information storage unit 33 stores building management information of the building in which the elevator 10 is installed, which is acquired from the building management unit 4 at any timing. The building management information mainly includes a building management schedule. By storing the building management information in advance in the building management information storage unit 33, even if, for example, the PC in the management room that executes the functions of the building management unit 4 stops or communication with the building management unit 4 is cut off, the switching timing generation unit 31 can generate program switching timing using the building management information stored in advance in the building management information storage unit 33.

[0021] However, the unit control unit 3 may be configured not to include the building management information storage unit 33. In this case, the switching timing generation unit 31 may obtain the building management information directly from the building management unit 4 when generating the switching timing.

[0022] The program storage unit 34 is used as an example of a software storage unit that stores programs (software) used in the elevator 10, such as the car unit 5, hall terminal unit 6, and motor unit 7. The program storage unit 34 may store parameters, data, etc. associated with the programs used in the elevator 10. In this embodiment, the program for which switching timing is generated by the switching timing generation unit 31 is a program used in the hall terminal unit 6. However, the program for which switching timing is generated may also be a program used in the car unit 5 or the motor unit 7. The switching timing generation unit 31 may also generate switching timing for parameters, data, etc. associated with the programs used in the elevator 10.

[0023] The programs stored in the program storage unit 34 are distributed from the maintenance management unit 2 to the elevator control unit 3 and stored in the program storage unit 34. The hall terminal control unit 36 ​​transfers the programs supplied from the program storage unit 34 to the hall terminal unit 6 (an example of a controlled object) in accordance with the switching timing generated by the switching timing generation unit 31 and approved by the building manager. Then, the hall terminal control unit 36 ​​rewrites the program in the hall terminal unit 6, and then switches the program used by the hall terminal unit 6 to the rewritten program. For this reason, the program is transferred from the program storage unit 34 to the hall terminal control unit 36 ​​during the time period when the elevator 10 is not being used.

[0024] The cage control unit 35 controls cage operations of the cage unit 5. Examples of cage operations include turning on a lantern that notifies the arrival of the cage unit 5 at the hall floor, setting a destination call according to the registration of a destination floor button in the cage unit 5, and controlling the opening and closing of the cage door of the cage unit 5. In addition, a cage camera is provided in the cage unit 5, and the cage control unit 35 obtains the number of passengers in the cage unit 5 based on the cage interior image acquired from the cage interior camera, and outputs the number of passengers to the user information analysis unit 32. The cage control unit 35 may also output information on weight changes acquired from a weight sensor installed on the floor of the cage unit 5 to the user information analysis unit 32. The user information analysis unit 32 grasps the time when no passengers are in the cage unit 5 based on the number of passengers or the information on weight changes.

[0025] Furthermore, the car control unit 35 may output information indicating that a destination floor button in the car has been registered to the user information analysis unit 32. Normally, a user who gets into the car unit 5 registers a destination floor button. For this reason, the user information analysis unit 32 can grasp that a time period during which a destination floor button is not registered for a certain period of time or more (for example, one minute or more) after the car unit 5 arrives at a hall floor is a time period during which the car unit 5 is unoccupied.

[0026] The hall terminal control unit 36 ​​controls the operation of the hall terminal unit 6. Then, the hall terminal control unit 36 ​​transfers the program read from the program storage unit 34 to the hall terminal control unit 36 ​​in accordance with the switching timing approved by the building manager. Furthermore, the hall terminal control unit 36 ​​outputs a switching command to the hall terminal control unit 36 ​​to switch to the program at the switching timing.

[0027] The hall terminal control unit 36 ​​acquires hall call information registered in the hall terminal unit 6, and outputs the hall call information to the car control unit 35. The hall terminal control unit 36 ​​may output information indicating that the hall button has been pressed, and an image of the inside of the hall captured by the hall camera to the car control unit 35. This information is used by the user information analysis unit 32 to determine the time when a user is or is not staying in the hall. If a user is staying in the hall, it is considered that this user will use the elevator 10.

[0028] The motor control unit 37 controls the operation of the motor unit 7 so that the car unit 5 stops at a landing floor where a hall call is registered and at a destination floor where a destination call is registered. The operation of the motor control unit 37 is controlled by the car control unit 35. The motor unit 7 operates according to a program read out from the program storage unit 34.

[0029] The switching timing generation unit 31 generates a switching timing for switching a program used in the hall terminal unit 6 (one example of a controlled object) to a program provided to the controlled object from the program storage unit 34 based on the building management information acquired from the building management information storage unit 33, and outputs the switching timing. Therefore, the switching timing generation unit 31 generates a switching timing for the hall terminal unit 6 to switch a program based on the priority determined by the building management schedule included in the building management information and the time required to rewrite the program in the hall terminal unit 6. At this time, the switching timing generation unit 31 generates the switching timing based on the management schedule acquired from the building management unit 4 or the building management information storage unit 33. Then, the switching timing generation unit 31 outputs the switching timing to the building manager and requests the building manager to approve the switching timing. After the switching timing is approved by the building manager, the switching timing generation unit 31 outputs the switching timing approved by the building manager to the program storage unit 34.

[0030] When generating the switching timing of the program, the switching timing generation unit 31 generates multiple switching timing candidates according to the priority defined by the work content and work schedule of the work for the building or the elevator 10 included in the building management schedule, or the non-use time of the building, and outputs the multiple switching timing candidates to the building manager. As shown in Figs. 5 and 6 described later, the priority is determined in the order of decreasing order from the maintenance inspection day of the elevator 10 which is inspected every first period (monthly), the irregular renewal work of the elevator 10, the irregular power outage day of the building, and the inspection work of the elevator 10 which is inspected every second period (daily) which is shorter than the first period. In this embodiment, "1" is the highest priority and "4" is the lowest priority.

[0031] The switching timing generation unit 31 outputs the switching timing approved by the building manager from among multiple candidate switching timings to the program storage unit 34. The program storage unit 34 supplies the hall terminal unit 6 with a program to be rewritten in the hall terminal unit 6 prior to the switching timing. For example, the program supplied from the program storage unit 34 to the hall terminal control unit 36 ​​is transferred to the hall terminal unit 6 during a time period prior to the switching timing (30 minutes prior) when users rarely use the elevator 10.

[0032] FIG. 2 is a block diagram showing an example of the internal configuration of the hall terminal unit 6. As shown in FIG. The hall terminal unit 6 includes a communication unit 61, a program storage unit 62, a program switching unit 63, and an input / output control unit 64.

[0033] The communication unit 61 is capable of transmitting and receiving various data to and from the car control unit 3. For example, the communication unit 61 receives a program to be switched from the hall terminal control unit 36 ​​of the car control unit 3. The communication unit 61 also transmits hall call information input from the input / output control unit 64 to the hall terminal control unit 36 ​​of the car control unit 3. The hall call information is output from the hall terminal control unit 36 ​​to the car control unit 35 and the motor control unit 37, and the car unit 5 moves to the hall floor.

[0034] The program storage unit 62 has a function of storing the programs transferred from the hall terminal control unit 36 ​​and received by the communication unit 61, and is used as an example of a controlled-side software storage unit. The programs stored in the program storage unit 62 are read out from the program switching unit 63 at the switching timing in response to a switching command from the hall terminal control unit 36, and are applied operably by the input / output control unit 64.

[0035] After all the divided programs have been stored in the program storage unit 62, when a program switching command is input from the hall terminal control unit 36 ​​of the machine control unit 3, the program switching unit 63 switches the program used in the hall terminal unit 6 to the program read from the program storage unit 62. The program switched by the program switching unit 63 is, for example, a program applied to the input / output control unit 64 in order to operate the input / output control unit 64 of the hall terminal unit 6.

[0036] The input / output control unit 64 operates according to the program switched by the program switching unit 63. The input / output control unit 64 outputs input / output control data corresponding to the switched program to the control object 65. The control object 65 may be, for example, a call registration button for registering a hall call connected to the hall terminal unit 6, a hall lantern that lights up to notify users that the car unit 5 has arrived at a hall floor, and a liquid crystal display that displays the floor number of the car unit 5 while it is moving. The input / output control data is used, for example, to change the blinking pattern of the hall lantern or to change the display form of the liquid crystal display. The contents of the input / output control data are updated by the program to be rewritten and switched.

[0037] Programs to be rewritten and switched in this embodiment include, for example, programs that enable the execution of functions that are added as options around the hall terminal unit 6. There is also a program that uploads a log of information acquired by sensors placed around the hall terminal unit 6 to the unit control unit 3. Here, newly added programs and upgraded programs are also included as examples of programs to be rewritten and switched.

[0038] <Example of computer hardware configuration> Next, the hardware configuration of the computer 20 constituting each device of the software rewriting system 1 will be described. Fig. 3 is a block diagram showing an example of the hardware configuration of calculator 20. Calculator 20 is an example of hardware used as a computer capable of operating as machine control unit 3 and hall terminal unit 6 according to this embodiment. Machine control unit 3 and hall terminal unit 6 according to this embodiment realize a program rewriting method in which each functional block shown in Figs. 1 and 2 cooperates with each other by having calculator 20 (computer) execute a program.

[0039] The computer 20 includes a CPU (Central Processing Unit) 21, a ROM (Read Only Memory) 22, and a RAM (Random Access Memory) 23, each of which is connected to a bus 24. The computer 20 further includes a display device 25, an input device 26, a non-volatile storage 27, and a network interface 28.

[0040] The CPU 21 reads out program code of software for realizing each function according to the present embodiment from the ROM 22, loads it into the RAM 23, and executes it. Variables, parameters, etc. generated during the arithmetic processing of the CPU 21 are temporarily written into the RAM 23, and these variables, parameters, etc. are read out by the CPU 21 as appropriate. However, an MPU (Micro Processing Unit) may be used instead of the CPU 21. The functions of each part of the unit control unit 3 are realized by the operation of the CPU 21.

[0041] The display device 25 is, for example, a liquid crystal display monitor, and displays the results of processing performed by the computer 20 to the building manager or maintenance staff. The input device 26 is, for example, a keyboard, a mouse, etc., and enables the building manager or maintenance staff to input predetermined operations and give instructions. The display device 25 and the input device 26 are used in the maintenance management department 2 and the building management department 4.

[0042] The nonvolatile storage 27 may be, for example, a hard disk drive (HDD), a solid state drive (SSD), a flexible disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, or a nonvolatile memory. In addition to an operating system (OS) and various parameters, a program for making the computer 20 function is recorded in the nonvolatile storage 27. The ROM 22 and the nonvolatile storage 27 record programs and data necessary for the CPU 21 to operate, and are used as an example of a computer-readable non-transient storage medium that stores a program executed by the computer 20. The function of the program storage unit 34 is realized by the nonvolatile storage 27.

[0043] For example, a NIC (Network Interface Card) or the like is used for the network interface 28, and various data can be transmitted and received between devices via a LAN (Local Area Network) or a dedicated line connected to a terminal of the NIC. The communication function from the unit control unit 3 to the maintenance management unit 2, the building management unit 4, and the elevator 10 is realized by the network interface 28.

[0044] <Example of processing in a software rewrite system> Next, an example of processing performed in each part of the software rewriting system 1 will be described with reference to FIGS. FIG. 4 is a flowchart showing an example of the process of the switching timing generation unit 31.

[0045] First, the switching timing generation unit 31 acquires a schedule (an example of building management information) from the building management unit 4 (S1), and generates switching timing based on the schedule priority shown in Fig. 6 (described later) (S2). At this time, based on the analysis result of the user information analyzed by the user information analysis unit 32, the switching timing generation unit 31 determines a time period when the elevator is used less frequently as the timing for the hall terminal control unit 36 ​​to transfer a program to the hall terminal unit 6 and rewrite the program of the hall terminal unit 6.

[0046] Next, the switching timing generation unit 31 outputs the generated switching timing to the building management unit 4 and waits for approval from the building manager (S3). Here, the building manager is, for example, a person who manages the management schedule of the building in which the elevator 10 is installed. Then, the building manager checks the switching timing generated in step S2 and approves or disapproves the switching timing.

[0047] If the building manager does not approve the switching timing (NO in S3), the switching timing generation unit 31 returns to step S1 and generates switching timing again. This switching timing is generated with a lower priority than the switching timing generated in the previous process of step S2.

[0048] On the other hand, if the building manager approves the switching timing (YES in S3), the switching timing generation unit 31 registers the switching timing in its own scheduler (S4). At this time, the switching timing generation unit 31 also notifies the building management unit 4 of the switching timing. For this reason, the switching timing is registered in the scheduler of the building management unit 4. In this flowchart, the date and time that includes the switching timing approved by the building manager is called the "approved date and time." In addition, the switching timing generation unit 31 registers the switching timing in the program storage unit 34.

[0049] Next, the program storage unit 34 starts the program rewrite process, for example, when the current date and time is 30 minutes before the approved date and time (S5). In the following explanation, the program provided from the program storage unit 34 to the hall terminal unit 6 is called the "rewrite program." The rewrite program is sent from the program storage unit 34 to the hall terminal control unit 36, but in this embodiment, a test program with a smaller amount of data than the rewrite program is sent before the rewrite program.

[0050] Then, the hall terminal control unit 36 ​​transfers the test program from the hall terminal control unit 36 ​​to the hall terminal unit 6, and checks whether the test program is correctly rewritten in the hall terminal unit 6. In this flowchart, the program that is actually rewritten in the hall terminal unit 6 and switched by the program switching unit 63 is called the production program, and will be explained to be distinguished from the test program.

[0051] When the rewriting process of the test program in the hall terminal unit 6 begins, the hall terminal control unit 36 ​​obtains the rewriting result of the test program in the hall terminal unit 6 from the hall terminal unit 6 and determines whether the rewriting result is OK or not (S6).

[0052] If the test program has been rewritten correctly and the rewrite result of the test program is OK (YES in S6), the hall terminal control unit 36 ​​transfers the live program provided from the program storage unit 34 to the hall terminal unit 6 (S7). When all live programs have been transferred to the hall terminal unit 6, the hall terminal control unit 36 ​​outputs a switch command to the hall terminal unit 6 in accordance with the switch timing. In the hall terminal unit 6 to which the switch command has been input, the currently used program is switched to the live program.

[0053] Then, the hall terminal control unit 36 ​​stores the rewriting results of the test program and the main program in the program storage unit 34. The switching timing generation unit 31 refers to the rewriting results stored in the program storage unit 34 and determines whether or not the rewriting of the main program in the hall terminal unit 6 has been completed successfully (S8). If the rewriting of the main program has been completed successfully (YES in S8), the switching timing generation unit 31 notifies the maintenance management unit 2 and the building management unit 4 that the rewriting of the main program has been completed successfully (S9), and ends this process.

[0054] On the other hand, if the switching timing generation unit 31 determines in step S6 that a problem occurred in the rewriting of the test program and the rewriting result was NG (NO in S6), or if it determines in step S8 that the rewriting of the production program was not completed normally (NO in S8), it notifies the maintenance management unit 2 and building management unit 4 of a problem in rewriting the test program or the production program (S10). The manager of the maintenance management unit 2 or the building manager who received the report handles the problem (S11) and ends this process.

[0055] To deal with a malfunction, for example, the building manager may check for a malfunction in the hall terminal unit 6. If a malfunction occurs when rewriting the test program or the production program, the hall terminal control unit 36 ​​stops transferring the production program to the hall terminal unit 6. The maintenance management unit 2 also instructs the unit control unit 3 to stop rewriting the production program. After the rewriting malfunction is resolved, the switching timing generation unit 31 generates new switching timing and receives approval for the switching timing from the building manager.

[0056] 5 is a flowchart showing an example of a process in which the switching timing generation unit 31 proposes a program switching timing to a building manager according to priority. This process is a detailed version of the switching timing generation process in step S2 in FIG.

[0057] The switching timing generation unit 31 refers to the building management schedule and the analysis results of the user information, and generates switching timing in the order of priority based on the frequency of use of the elevator 10 and the least impact on the building maintenance schedule.

[0058] First, the switching timing generation unit 31 judges whether the elevator maintenance inspection date is in the target month in which the program is to be rewritten and switched (S21). If the elevator maintenance inspection date is in the target month (YES in S21), the switching timing generation unit 31 proposes to the building management unit 4 to switch the program in conjunction with the maintenance inspection (S22), and ends this process.

[0059] On the other hand, if the elevator maintenance inspection date does not fall within the target month (NO in S21), it is determined whether or not renovation work is scheduled for the elevator 10 (S23). If renovation work is scheduled for the elevator 10 (YES in S23), the switching timing generation unit 31 proposes to the building management unit 4 to switch the program in conjunction with the renovation work (S24), and ends this process.

[0060] On the other hand, if no renovation work is scheduled for the elevator 10 (NO in S23), it is determined whether or not a power outage date is scheduled in the target month (S25). If a power outage date is scheduled in the target month (YES in S25), the switching timing generation unit 31 proposes to the building management unit 4 to switch the program around the time of the power outage (S26), and ends this process.

[0061] On the other hand, if the power outage date is not in the target month (NO in S25), the switching timing generation unit 31 proposes to the building management unit 4 to switch the program at a time when there are fewer users of the elevator 10, in line with inspection work (S27), and ends this process. The switching timing proposed in step S27 differs from the switching timing proposed in steps S22, S24, and S26, and may be included in the time period when users use the elevator 10. If this switching timing is approved by the building manager, users will be temporarily unable to use the elevator 10 on the approved date and time, but since the frequency of use of the elevator 10 is lower than other dates and times, convenience for users will not be significantly reduced.

[0062] FIG. 6 is a list showing examples of priorities set in the registration items of the scheduler. This list is composed of the following items: scheduler registration item, frequency, worker, elevator usage status, and priority. As shown in the flowchart in Figure 5, the priorities are set from "1" to "4" for elevator maintenance inspection, equipment renewal work, power outage, and inspection work, in that order. The contents of the scheduler registration items will be explained below in order of priority.

[0063] The frequency of elevator maintenance inspection is monthly (every first period), and the worker is an elevator maintenance contractor. During the elevator maintenance inspection, the elevator 10 is out of operation, which is the most suitable time for switching the program.

[0064] Equipment renovation work is carried out irregularly, and depending on the equipment to be renovated, it may be in an inoperative state or in an operational state. Furthermore, power outages in the building may occur irregularly, causing the elevator 10 to be out of operation. For this reason, equipment renovation work and power outages are set to have a lower priority than elevator maintenance and inspection.

[0065] The frequency of the inspection work is every day (every second period). The inspection work is performed while the elevator 10 is in operation. For this reason, the lowest priority is set for the inspection work.

[0066] 7 is a diagram showing how priority changes depending on the amount of program changes, as well as the type of work and the work time. This list is made up of items for scheduler registration item, type of work, work time, and priority.

[0067] The time required for hall terminal control unit 36 ​​to complete the transfer of the rewrite program to hall terminal unit 6 varies depending on the size of the changes in the rewrite program. For example, if changes that only affect hall terminal unit 6 have been made and there are few changes to the rewrite program, the file size of the rewrite program will be small and the time required to complete the transfer of the rewrite program will be short. On the other hand, if changes that affect not only hall terminal unit 6 but also unit control unit 3 have been made and there are many changes to the rewrite program, the file size of the rewrite program will be large and the time required to complete the transfer of the rewrite program will be long.

[0068] In principle, the software rewriting system 1 aims to minimize the downtime of the elevator 10 in the event of an unexpected incident during program rewriting. Therefore, even if a malfunction occurs during program rewriting and the downtime of the elevator 10 is prolonged, if the work time required for the work performed on the elevator 10 is long, a maintenance worker can ensure time to recover the program within the work time, thereby minimizing the impact on users of the elevator 10. Therefore, the switching timing generation unit 31 can set a high priority to work items that require a large work time for the work performed on the elevator 10, based on the management schedule registered in the scheduler and the magnitude of changes in the program for rewriting.

[0069] Table (a) in FIG. 7 shows an example of the work time and priority when the changes in the rewrite program are large. Since the changes in the rewrite program are large, there is a possibility of some malfunction when rewriting the program. Therefore, the priority of the work type items that require a large amount of work time is increased. For example, in table (a), the work times for tower interior inspection, car top inspection, car interior inspection, and operation check are specified as "large," "medium," "small," and "small," respectively. Therefore, the priorities are set from "1" to "4" in order of the longest work time, that is, for work times "large," "medium," "small," and "small."

[0070] Table (b) in FIG. 7 shows an example of the work time and priority when the changes in the rewrite program are small. If there are few changes to the program to be rewritten, the possibility of defects occurring when rewriting the program is extremely low. For this reason, the priority of work items that require a small amount of work time is set high. For example, in table (b), the priorities are set from "1" to "4" in order of shortest work time, that is, for work times "small," "small," "medium," and "large."

[0071] In this way, when the changes to the software transferred to the hall terminal unit 6 are large, the longer the work time in the building or elevator 10, the higher the priority is assigned to the work content, and when the changes to the software are small, the shorter the work time, the higher the priority is assigned to the work content. Therefore, the switching timing generation unit 31 can generate multiple switching timing candidates in descending order of priority based on information on the size of the changes to the rewrite program obtained from the maintenance management unit 2.

[0072] Next, an example of a program switching process will be described. FIG. 8 is a flowchart showing an example of a program switching process performed by the hall terminal control unit 36 ​​of the machine control unit 3. When a switching timing is registered in the scheduler of the switching timing generating unit 31, the hall terminal control unit 36 ​​transfers a program to the hall terminal unit 6 during intervals between normal processing performed by the hall terminal unit 6. Then, when the current time becomes the switching timing, the hall terminal control unit 36 ​​transmits a program switching command to the hall terminal unit 6.

[0073] First, the hall terminal control unit 36 ​​determines whether or not a program rewrite has been registered (S31). If a program rewrite has not been registered (NO in S31), the hall terminal control unit 36 ​​performs normal processing (S33) and returns to step S31 again.

[0074] If a program rewrite has been registered (YES in S31), the hall terminal control unit 36 ​​determines whether the current time is an idle time when the hall terminal unit 6 is not processing (S32). If the current time is not an idle time (NO in S32), the hall terminal control unit 36 ​​performs normal processing (S33) and returns to step S31.

[0075] On the other hand, if the current time is free for processing (YES in S32), the hall terminal control unit 36 ​​transmits a rewrite program (production program) to the hall terminal unit 6 (S34). This process is performed if the transmission and rewrite of the test program are OK (YES in step S6 shown in FIG. 4).

[0076] As mentioned above, the file size of the actual program is large, so it may not be possible to transfer the actual program in its entirety during the idle time of the elevator 10. For this reason, the hall terminal control unit 36 ​​divides the program read from the program storage unit 34 into portions of a predetermined file size, and transfers the divided programs in sequence during times when the elevator 10 is used less frequently, for example, during idle time when the hall terminal unit 6 is not processing. The hall terminal control unit 36 ​​then determines whether or not the transfer of all the divided rewrite programs has been completed (S35).

[0077] If the transfer of all the divided rewrite programs has not been completed (NO in S35), the hall terminal control unit 36 ​​returns to step S32. The time required to complete the transfer of the rewrite programs corresponds to the time it takes for the processes in steps S34 to S35 to be repeated.

[0078] On the other hand, when the transfer of all the divided rewrite programs is completed (YES in S35), the hall terminal control unit 36 ​​judges whether the current time is the timing to switch the programs (S36). If the current time is not the timing to switch the programs (NO in S36), the hall terminal control unit 36 ​​performs normal processing (S33) and returns to step S31 again.

[0079] On the other hand, if the current time is the timing to switch programs (YES in S36), the hall terminal control unit 36 ​​sends a program switching command to the hall terminal unit 6 (S37), causes the hall terminal unit 6 to switch programs, and then returns to step S31.

[0080] Next, an example of the processing of the hall terminal unit 6 will be described. FIG. 9 is a flowchart showing an example of the process performed by the hall terminal unit 6. The hall terminal unit 6 identifies the data received from the unit control unit 3 and performs processing according to the type of data.

[0081] First, the communication unit 61 of the hall terminal 6 determines whether the data received from the hall terminal control unit 36 ​​is input / output control data used in normal processing of the hall terminal 6 (S41). If the communication unit 61 determines that the received data is input / output control data (YES in S41), it outputs the input / output control data to the input / output control unit 64. Then, the input / output control unit 64 performs input / output control processing based on the input / output control data (S42) and returns to step S41.

[0082] In step S41, when the communication unit 61 determines that the received data is not input / output control data (NO in S41), it determines whether or not the received data is a program (S43). When the communication unit 61 determines that the received data is a program (YES in S43), it outputs the program to the program storage unit 62. Then, the program storage unit 62 performs a process of storing the input program (S44), and returns to step S41.

[0083] In step S43, if the communication unit 61 determines that the received data is not a program (NO in S43), it determines that the received data is a program switching command. Therefore, the communication unit 61 outputs a program switching command to the program switching unit 63. Then, the program switching unit 63 reads out a program from the program storage unit 62, performs program switching processing (S45), and returns to step S41.

[0084] In the software rewriting system 1 according to the first embodiment described above, when a program switching timing is generated, the switching timing is output. The switching timing is output to the building manager. The switching timing is then determined based on the date and time approved by the building manager. The date and time approved by the building manager is usually the date and time when the manager is in the building. This allows the building manager to manage the switching timing. In addition, the building manager and maintenance personnel are aware of the program rewriting date and time, and can immediately respond and quickly recover if a program rewriting or switching problem occurs.

[0085] The switching timing generation unit 31 generates the program switching timing based on the priority of the building management schedule. In this way, the program switching timing is generated based on the priority determined by the building management schedule and the time required to rewrite the program in the controlled object, so that the program is rewritten and switched on a date and time when there are few users and the priority is high. This makes it difficult for the usage time period of the elevator 10 users to overlap with the non-operational time of the elevator 10, so that the users of the elevator 10 can use the elevator 10 almost without causing inconvenience to the users.

[0086] In addition, the test program is transferred to the hall terminal unit 6 before the actual program to be rewritten is transferred to the hall terminal unit 6. Then, the hall terminal control unit 36 ​​transfers the actual program to the hall terminal unit 6 if the hall terminal unit 6 is capable of rewriting the test program. In this way, the hall terminal control unit 36 ​​transfers the actual program after confirming whether the test program has been correctly rewritten by the hall terminal unit 6, so the risk of a malfunction occurring when rewriting the actual program can be reduced compared to when the actual program is transferred from the beginning. In addition, the switching timing generation unit 31 outputs the switching timing approved by the administrator to the program storage unit 34. The program storage unit 34 can provide the hall terminal control unit 36 ​​with a program in accordance with the switching timing, so that the program in the hall terminal unit 6 can be switched at a time and date when there are few users of the elevator 10 and the priority is high.

[0087] The priority determined for each scheduler registration item shown in Fig. 6 may be changed by the switching timing generation unit 31. For example, when a new program is distributed from the maintenance management unit 2 to the unit control unit 3, the building manager may request that the hall terminal unit 6 be quickly switched to the new program. In this case, the switching timing generation unit 31 may give a higher priority to inspection work that is performed daily than to scheduler registration items that are performed monthly or irregularly. When the priority is changed in this way, the processing order is also changed in the flowchart shown in Fig. 5 so that the processing of the scheduler registration item that has been changed to a higher priority is performed at the beginning of the flow.

[0088] [Second embodiment] Next, a configuration example of a software rewriting system according to a second embodiment will be described with reference to Fig. 10. The software rewriting system according to the first embodiment is applied to an elevator system equipped with a pair of car control units 3 and elevators 10. On the other hand, the software rewriting system according to the second embodiment is applied to a group management elevator system that controls a plurality of car control units 3 and elevators 10.

[0089] FIG. 10 is a block diagram showing an example of a configuration of a software rewriting system 1A according to the second embodiment.

[0090] The software rewriting system 1A includes a maintenance management unit 2, unit control units 3(1) to 3(n), a building management unit 4, a group management control unit 50, and elevators 10(1) to 10(n).

[0091] The group management control unit 50 performs group management control of the elevators 10(1)-10(n) through the elevator control units 3(1)-3(n). For example, the group management control unit 50 controls the car units 5 to run in a dispersed manner so that the car units 5 do not concentrate on the hall floor during a specific time period, and controls the car units 5 to be available for use on each specific floor.

[0092] The group management control unit 50 includes a switching timing generation unit 51 and a building management information storage unit 52. The functions of the switching timing generation unit 51 and the building management information storage unit 52 are similar to the functions of the switching timing generation unit 31 and the building management information storage unit 33 shown in FIG.

[0093] However, the switching timing generation unit 51 generates the switching timing based on the building management information acquired directly from the building management unit 4 or the building management information acquired from the building management information storage unit 52, and the analysis result of the user information analyzed by the user information analysis unit 32. Then, the switching timing generation unit 51 transmits the switching timing to the unit control units 3(1) to 3(n).

[0094] Furthermore, the building management information storage unit 52 stores the building management information acquired from the building management unit 4. In this embodiment, the unit control units 3(1) to 3(n) are configured not to include the building management information storage unit 33. By including the building management information storage unit 52 in the group management control unit 50, the unit control units 3(1) to 3(n) do not need to have building management information with the same content.

[0095] In the software rewriting system 1A according to the second embodiment described above, even in a group management elevator system, the programs of the hall terminal units 6 of the elevators 10(1)-10(n) are rewritten through the elevator control units 3(1)-3(n). Therefore, even in a building in which many elevators 10(1)-10(n) are installed, programs are rewritten and switched according to the building management schedule so as not to cause inconvenience to users.

[0096] Incidentally, the present invention is not limited to the above-described embodiment, and it goes without saying that various other applications and modifications are possible without departing from the gist of the present invention as set forth in the claims. For example, the above-mentioned embodiment describes the system configuration in detail and specifically in order to explain the present invention in an easily understandable manner, and is not necessarily limited to a system having all of the described configurations. In addition, it is also possible to add, delete, or replace part of the configuration of the present embodiment with other configurations. In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and not all control lines and information lines in the product are necessarily shown. In reality, it can be considered that almost all components are connected to each other. [Explanation of symbols]

[0097] 1...software rewriting system, 2...maintenance management unit, 3...unit control unit, 4...building management unit, 5...car unit, 6...hall terminal unit, 7...motor unit, 10...elevator, 31...switching timing generation unit, 32...user information analysis unit, 33...building management information storage unit, 34...program storage unit, 35...car control unit, 36...hall terminal control unit, 37...motor control unit

Claims

1. a software storage unit for storing software used in the elevator control object; a building management information storage unit in which building management information of the building in which the elevator is installed is stored; a switching timing generation unit which, when the changes to the software transferred to the control target are large, assigns a higher priority to the work content for the building or the elevator as the work time for the building or the elevator is longer, and, when the changes to the software are small, assigns a higher priority to the work content as the work time is shorter, generates a switching timing based on the building management information acquired from the building management information storage unit as a switching timing for switching the software used in the control target to software provided to the control target from the software storage unit based on the priority determined by a management schedule of the building included in the building management information and the time required to rewrite the software in the control target, generates a plurality of switching timing candidates in descending order of priority based on the priority determined by the work content and work schedule included in the management schedule or the non-use time of the building and the priority according to the size of the changes to the software, outputs the plurality of switching timing candidates to a manager of the building, and requests the manager of the building to approve the switching timing; Equipped Software rewriting system.

2. a control unit that transfers the software supplied from the software storage unit to the control target in accordance with the switching timing approved by the building manager, rewrites the software of the control target, and then switches the software used by the control target to the rewritten software.

2. The software rewriting system according to claim 1.

3. The switching timing generation unit outputs the switching timing approved by the building manager from among a plurality of switching timing candidates to the software storage unit.

3. The software rewriting system according to claim 2.

4. The priority is determined in the following order: a maintenance inspection date for the elevator, which is inspected every first period, irregular renovation work for the elevator, irregular power outage days for the building, and an inspection work for the elevator, which is inspected every second period that is shorter than the first period.

3. The software rewriting system according to claim 2.

5. a user information analysis unit that analyzes user information acquired from the elevator and determines a time period when the elevator is least frequently used; The switching timing generation unit causes the control unit to transfer the software during a time period before the switching timing when the elevator is less frequently used.

3. The software rewriting system according to claim 2.

6. The control unit sequentially transfers the divided software during a time period when the elevator is used less frequently, and after transferring all of the divided software, causes the control target to switch the software in accordance with the switching timing.

3. The software rewriting system according to claim 2.

7. The control unit transfers test software, which has a smaller amount of data than the software provided from the software storage unit to the control target, to the control target, and transfers the software to the control target when the test software is correctly rewritten.

3. The software rewriting system according to claim 2.

8. a building management unit that manages the management schedule; the building management information storage unit stores the management schedule acquired from the building management unit; The switching timing generation unit generates the switching timing based on the management schedule acquired from the building management unit or the building management information storage unit.

3. The software rewriting system according to claim 2.

9. the controlled object includes a controlled object side software storage unit for storing the software transferred from the control unit; and a software switching unit that switches the software used in the control target to the software read from the control target software storage unit in response to a command from the control unit after the software is stored in the control target software storage unit.

3. The software rewriting system according to claim 2.

10. The software includes at least one of a program executable on the control target, data used in the program, and parameters. The software rewriting system according to any one of claims 1 to 9.

11. a process of: transferring the software to a control target of an elevator, and when a change to the software used in the control target is large, assigning a higher priority to the work content for the building in which the elevator is installed or the elevator as the work time for the building or the elevator is longer, and when a change to the software is small, assigning a higher priority to the work content as the work time is shorter; generating a switching timing based on the building management information acquired from a building management information storage unit in which building management information of the building is stored, as a switching timing for switching the software used in the control target to software provided to the control target from a software storage unit, based on the priority determined by a management schedule of the building included in the building management information and the time required to rewrite the software in the control target; generating a plurality of candidates for the switching timing in descending order of priority based on the priority determined by the work content and work schedule included in the management schedule, or the priority determined by the non-use time of the building, and the priority according to the size of the change to the software, outputting the plurality of candidates for the switching timing to a manager of the building, and requesting the manager of the building to approve the switching timing. How to rewrite software.

Citation Information

Patent Citations

  • Elevator control program rewriting device

    JP2007001734A

  • Elevator

    JP2007302388A

  • Control system of elevator

    JP2008254885A

  • Control data rewriting system

    JP2017186126A

  • BIM system, method and program

    JP2017215692A