Software update system, software update method, and software update program
The software update system automatically updates plant control device modules by classifying and comparing state data to ensure normal operation, addressing inefficiencies and errors in manual updates, thus maintaining plant availability.
Patent Information
- Application Number
- JP2023084324
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-23
- Publication Date
- 2024-12-05
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing software update methods for plant control devices require manual intervention, leading to inefficiencies, increased downtime, and potential human errors, which can disrupt plant operations and reduce availability.
A software update system that automatically updates software in multiplexed modules by classifying modules as operating or non-operating, performing updates on non-operating modules, determining the absence of abnormalities through state data comparison, and switching module states only when no abnormalities are detected.
Enables high-quality software updates without reducing plant operation rates by ensuring normal operation is maintained during the update process, minimizing human errors and downtime.
Smart Images

Figure 2024167975000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a software update system, a software update method, and a software update program capable of updating software stored in a non-volatile memory included in a configuration module of a plant control device. [Background technology]
[0002] For example, in plant facilities such as thermal power plants, plant control devices are used to comprehensively control and monitor the plant, which is made up of many components. The plant control device includes an IO module for inputting and outputting data required for control calculations, a gate device for sending and receiving various digital signals to and from the IO module, and a controller for controlling the gate device. Each component of these plant control devices loads software such as firmware stored in non-volatile memory at startup and controls peripheral devices based on that data.
[0003] Software stored in non-volatile memory needs to be updated as necessary. Conventionally, this type of software update work required an operator to visit the site where the equipment equipped with the non-volatile memory was located. In particular, when there were multiple pieces of equipment to be updated, an operator had to move to the installation site of each piece of equipment to perform the update work, which took a lot of time and cost. In addition, during software update work, the operation of the equipment to be updated must be stopped, which can reduce plant operation rate. In addition, since software update work is performed manually by an operator, there is a possibility of human error occurring, such as mistaking the software to be updated.
[0004] As a means for solving such problems, a system for automatically performing software update work without relying on human labor has been proposed. For example, in Patent Document 1, in a plant control device including modules duplicated (multiplexed) into an operational system and a standby system, software installed in a standby system module is updated while the operational system module operates normally, thereby enabling automatic software update without reducing the plant operating rate. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2008-217201 A Summary of the Invention [Problem to be solved by the invention]
[0006] In the above-mentioned Patent Document 1, while continuing plant control by the operational module, software of the standby module is updated, and then the operational module and the standby module are switched, thereby updating the software of the initial operational module as well. However, in this document, switching between the operational module and the standby module is performed without verifying whether the software update was performed normally. Therefore, if the software update is not completed normally or if the software update causes an unintended change in the input / output characteristics of the module, there is a risk of disrupting the operation of the plant.
[0007] At least one embodiment of the present disclosure has been made in consideration of the above-mentioned circumstances, and aims to provide a software update system, a software update method, and a software update program that are capable of automatically performing high-quality software update work without reducing the operating rate of a plant control device. [Means for solving the problem]
[0008] In order to solve the above problem, a software update system according to at least one embodiment of the present disclosure includes: A software update system for updating software stored in a non-volatile memory included in a multiplexed first module and a multiplexed second module of a plant control device, comprising: an update information transmission unit for transmitting update information of the software; a module classification unit for classifying the first module and the second module into either an operating module or a non-operating module; an update execution unit for executing an update of the software of the non-operating module based on the update information; an anomaly determination unit for determining the presence or absence of an anomaly by comparing first status data indicating a status of the operating module with second status data indicating a status of the non-operating module whose software has been updated; an operation state change unit for changing the operation states of the first module and the second module so as to replace the operating module and the non-operating module with each other when the abnormality determination unit determines that there is no abnormality; Equipped with.
[0009] In order to solve the above problem, a software update method according to at least one embodiment of the present disclosure includes: A software update method for updating software stored in a non-volatile memory included in a multiplexed first module and a multiplexed second module included in a plant control device, comprising: transmitting update information of the software; classifying the first module and the second module as either an active module or an inactive module; performing an update of the software of the non-operating module based on the update information; determining whether or not an abnormality exists by comparing first status data indicating a status of the operating module with second status data indicating a status of the non-operating module whose software has been updated; changing the operation states of the first module and the second module so that the operating module and the non-operating module are interchanged when it is determined that there is no abnormality; Equipped with.
[0010] In order to solve the above problem, a software update program according to at least one embodiment of the present disclosure includes: A software update program for updating software stored in a non-volatile memory included in a first module and a second module multiplexed in a plant control device, A computer device includes: transmitting update information of the software; classifying the first module and the second module as either an active module or an inactive module; performing an update of the software of the non-operating module based on the update information; determining whether or not an abnormality exists by comparing first status data indicating a status of the operating module with second status data indicating a status of the non-operating module whose software has been updated; changing the operation states of the first module and the second module so that the operating module and the non-operating module are interchanged when it is determined that there is no abnormality; It is possible to execute the following. Effect of the Invention
[0011] According to at least one embodiment of the present disclosure, it is possible to provide a software update system, a software update method, and a software update program that can automatically perform high-quality software update work without reducing the operating rate of a plant control device. [Brief description of the drawings]
[0012] [Figure 1] 1 is an overall configuration diagram of a plant control device according to an embodiment; [Diagram 2] 1 is a block diagram of a software update system according to an embodiment; [Diagram 3] 3 shows examples of some determination criteria in the abnormality determination unit of FIG. 2. [Figure 4] 4 is a flowchart illustrating a software update method according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] Hereinafter, some embodiments of the present disclosure will be described with reference to the accompanying drawings. However, the dimensions, materials, shapes, relative arrangements, etc. of components described as the embodiments or shown in the drawings are merely illustrative examples and are not intended to limit the scope of the present disclosure.
[0014] First, a plant control device that is a target for which software update is performed by a software update system according to at least one embodiment of the present disclosure will be described. FIG. 1 is an overall configuration diagram of a plant control device 1 according to one embodiment. The plant control device 1 can broadly include elements constituting a plant facility as control targets, but this embodiment illustrates a case in which elements constituting a plant facility such as a power plant, such as a gas turbine, steam turbine, boiler, etc., are controlled. For example, the control target of the plant control device may be, for example, an ITS (Intelligent Transport Systems), a cooling and heating system (large chillers, air conditioners), vehicles (railroads, automobiles, construction machinery, etc.), etc.
[0015] The plant control device 1 is configured as an embedded system that controls each component of the plant equipment, and includes an OPS (operator station) 2, an EMS (engineering maintenance station) 4, an ACS (accessory station) 6, a distribution server 7, a controller 8, and IO devices 10-1 to 10-n (n is a natural number equal to or greater than 2).
[0016] Each of these products constituting the plant control device 1, which is an embedded system, is configured so as to be capable of transmitting and receiving data to each other via a communication network, and can be changed as needed to suit the operating mode of the plant equipment to be controlled.
[0017] The OPS 2 is a device that allows an operator to grasp the state of the plant equipment to be controlled and control each component of the plant equipment (for example, controlling the opening and closing of a valve). The EMS 4 is a device that creates a control program to be executed when operating the plant equipment and installs the control program in the controller 8. The ACS 6 is a device that stores and manages various data handled by the plant control device 1 and functions as an interface with peripheral devices such as printers.
[0018] The distribution server 7 is a server terminal for distributing update information for updating software installed in each component of the plant control device 1. The update information includes information related to updates for updating the software. The software to be updated may be a control program or firmware. As will be described later in more detail, the software to be updated may be a control program installed in each of the controller modules 8-1 to 8-m constituting the controller 8, or may be firmware installed in the IO adapter 12 or the IO module 14 constituting the IO devices 10-1 to 10-n. The distribution of these pieces of update information is performed when the distribution server 7 receives a command from a software update system 100 described later.
[0019] The controller 8 is a core device that performs control calculations for the plant control device 1, and includes a plurality of controller modules 8-1 to 8-m (m is a natural number equal to or greater than 2). The controller modules 8-1 to 8-m control the input / output and states of valves, sensors, etc., according to a control program installed by the EMS 4.
[0020] The controller modules 8-1 to 8-m are multiplexed by being connected in parallel. The control programs installed in the controller modules 8-1 to 8-m may be an example of software to be updated by a software update system described later. The control programs are stored in, for example, non-volatile memories mounted on the controller modules 8-1 to 8-m.
[0021] The OPS 2, EMS 4, ACS 6 and distribution server 7 are connected to the controller 8 via a communication network 22. The communication network 22 may be multiplexed.
[0022] The IO devices 10-1 to 10-n are interface devices for inputting and outputting various data between the upper controller 8 and each device to be controlled, and each includes an IO adapter 12 and an IO module 14.
[0023] The IO adapter 12 is a communication relay device of the IO network, and is provided in each of the IO devices 10-1 to 10-n. The IO adapter 12 includes a first IO adapter module 12a and a second IO adapter module 12b that are multiplexed with each other. Firmware required to fulfill the functions of the first IO adapter module 12a and the second IO adapter module 12b is installed. These firmware may be an example of software to be updated by a software update system described later. This firmware is stored, for example, in a non-volatile memory mounted in these IO adapter modules.
[0024] The first IO adaptor module 12a is connected to the controller 8 via the first ring network 16a so as to be able to transmit and receive various data, and is configured to be able to transmit and receive various data to and from each IO module 14. The second IO adaptor module 12b is connected to the controller 8 via the second ring network 16b so as to be able to transmit and receive various data, and is configured to be able to transmit and receive various data to and from each IO module 14. The first ring network 16a connects the first IO adaptor modules 12a in each of the IO devices 10-1 to 10-n in series. The second ring network 16b connects the second IO adaptor modules 12b in each of the IO devices 10-1 to 10-n in series. In this way, the first ring network 16a and the second ring network 16b are multiplexed by being connected in parallel to the controller 8.
[0025] The IO module 14 is a component for transmitting and receiving various data between each component (e.g., various sensors, actuators, etc.) of the plant equipment to be controlled. Each of the IO devices 10-1 to 10n has a first IO module 14a and a second IO module 14b that are multiplexed with each other. Firmware required to fulfill the functions of the first IO module 14a and the second IO module 14b is installed. These firmware may be an example of software to be updated by a software update system described later. This firmware is stored, for example, in a non-volatile memory mounted on these IO modules.
[0026] The first IO module 14a and the second IO module 14b, which are multiplexed with each other, are provided in a plurality of pairs in each of the IO devices 10-1 to 10n in correspondence with the configuration of the destination of transmission and reception of various data. Each of the first IO module 14a and the second IO module 14b is connected to the controller 8 via the above-mentioned first IO adapter module 12a or the second IO adapter module 12b. That is, the first IO adapter module 12a can access the first IO module 14a and the second IO module 14b, respectively, and the second IO adapter module 12b can also access the first IO module 14a and the second IO module 14b, respectively.
[0027] Next, a description will be given of a software update system 100 that is configured integrally with the plant control device 1 having the above configuration. The software update system 100 is connected to the OPS 2, the EMS 4, the ACS 6, the distribution server 7, the controller 8, and the IO devices 10-1 to 10-n via a communication network 22 so as to be able to communicate with each other.
[0028] 2 is a block diagram of a software update system 100 according to an embodiment. The software update system 100 includes an update information transmission unit 102, a module classification unit 104, an update execution unit 106, an abnormality determination unit 108, and an operation status change unit 110.
[0029] The update information transmission unit 102 is configured to transmit update information to modules that are the subject of software updates. The update information includes information for updating software (so-called upload data). The update information transmission unit 102 may transmit the update information itself, but in this embodiment, it transmits, for example, a command to instruct transmission of update information to a distribution server 7, which is a dedicated server for distributing update information. Upon receiving the command, the distribution server 7 distributes the update information to each module that is the subject of software updates.
[0030] The modules to be updated for software may be the multiple control modules 8-1 to 8-m constituting the controller 8. In this case, the update information is information for updating the control programs installed in these control modules 8-1 to 8-m. The modules to be updated for software may be the multiple IO adapters 12 or IO modules 14 constituting the IO devices 10-1 to 10-n. In this case, the update information is information for updating the firmware installed in these multiple IO adapters 12 or IO modules 14.
[0031] The modules to be updated may include at least one of the above-mentioned control modules 8-1 to 8-m, IO adapter module 12, or IO module 14, and are multiplexed with each other. In the following description, for convenience, any two multiplexed modules to be updated will be referred to as a first module M1 and a second module M2, and their types do not matter unless otherwise specified. The multiplexed first module M1 and second module M2 are each configured to be switchable between an operating state and a non-operating state, and when one is in an operating state, the other is in a non-operating state, so that it functions as a backup for the other.
[0032] The operating state means that the software installed in the module is executed and contributes to the operation of the plant control device 1. The non-operating state means that the software installed in the module is not executed and therefore does not contribute to the operation of the plant control device 1, or that the software is executed but the calculation result is not output and therefore does not contribute to the operation of the plant control device 1.
[0033] The module classification unit 104 is configured to classify the first module M1 and the second module M2 as either an operating module or a non-operating module. For example, status information including a flag indicating the operating state of each module is prepared for each module, and the module classification unit 104 accesses the status information to identify whether the first module M1 and the second module M2 are an operating module or a non-operating module.
[0034] The update execution unit 106 is configured to execute software update of a non-operating module based on the update information. Specifically, the update execution unit 106 updates the software by applying the update information transmitted by the update information transmission unit 102 to the non-operating module identified by the module classification unit 104. Since the software update by the update execution unit 106 is performed on a non-operating module that is in a non-operating state (i.e., a function that can be realized by the non-operating module is realized by an operating module multiplexed with the non-operating module), it does not affect the operating state of the plant control device 1.
[0035] The abnormality determination unit 108 is configured to determine the presence or absence of an abnormality by comparing first status data indicating the status of an operating module with second status data indicating the status of a non-operating module after a software update. The first status data and the second status data include data corresponding to mutually comparable determination items, and the abnormality determination unit 108 determines the presence or absence of an abnormality based on whether a preset determination criterion is satisfied.
[0036] Here, Fig. 3 shows examples of some judgment criteria in the abnormality judgment unit 108 in Fig. 2. Fig. 3 shows judgment criteria as common items regardless of the type of module that is the target of software update, and judgment criteria defined for each type of module.
[0037] First, the criteria corresponding to common items regardless of the type of module are specified as follows: (i) the type (version information) of the software installed in the non-operating module after the update is correct, and (ii) the CRC value in the flash ROM after the update matches the CRC value of the write data (FW data). In addition, the criteria corresponding to the case where the module to be updated is the IO module 14 are specified as follows: (iii) the output value of the output module matches between the operating module and the non-operating module, (iv) the input value of the input module matches between the operating module and the non-operating module, and (v) the status of the non-operating module after the update is normal.
[0038] Furthermore, the criteria for determining whether the module to be updated is an IO adapter module 12 include (vi) that the status of the non-operating module after the update is normal. Furthermore, the criteria for determining whether the module to be updated is a controller module 8-1 to 8-m are (vii) that the input / output data of the other controller modules is compared and that the values match, or (viii) that the status of the non-operating module after the update is normal.
[0039] The status of the non-operating module in (v), (vi), and (viii) above is determined based on the self-diagnosis result, for example, if the module has a self-diagnosis function. In this case, the first status data includes the self-diagnosis data of the operating module, and the second status data includes the self-diagnosis data of the non-operating module. In this way, if each module has a self-diagnosis function, it is possible to appropriately determine whether the software update for the non-operating module was performed normally by comparing the self-diagnosis data of the operating module and the non-operating module. Diagnostic items of the self-diagnosis include, for example, power supply abnormality, clock abnormality, heartbeat abnormality with other devices, communication abnormality, etc.
[0040] The first status data acquired from an operating module may be actual output data output from the module, and the second status data acquired from a non-operating module may be virtual output data calculated from the module. The operating module contributes to the operation of the plant control device 1 by actually functioning, so the first status data can be acquired as actual output data. On the other hand, the non-operating module is not actually functioning, but performs the same arithmetic processing as the operating module internally, and is in a standby state so that it can output the arithmetic processing result as actual output data instead when the operating module falls into an inoperable state. That is, in the non-operating module, the arithmetic processing result equivalent to the actual output data of the operating module is prepared as an internal value. Therefore, the presence or absence of an abnormality can be determined by acquiring the internal value of the non-operating module as virtual output data and comparing it with the actual output data output from the operating module.
[0041] The operation state switching unit 110 is configured to change the operation states of the first module M1 and the second module M2. In this embodiment, when the abnormality determination unit 108 determines that there is no abnormality, the operation state switching unit 110 is configured to change the operation states of the first module M1 and the second module M2 so as to replace the operating module with the non-operating module.
[0042] The software update system 100 having the above configuration may be configured integrally with the OPS 2, which is a terminal for operating and controlling the plant control device 1. Furthermore, the function of the software update system 100 may be incorporated into the EMS 4.
[0043] Next, a description will be given of a software updating method implemented by the software updating system 100 having the above configuration. Fig. 4 is a flowchart showing a software updating method according to an embodiment.
[0044] First, the update information transmission unit 102 transmits update information to each module to be updated (step S1). In this embodiment, a command is sent to the distribution server 7 to distribute the update information to the first module M1 and the second module M2 to be updated. As a result, the distribution server 7 distributes the update information to the first module M1 and the second module M2.
[0045] Next, the module classification unit 104 classifies the first module M1 and the second module M2 to be updated as either an operating module or a non-operating module (step S2). For example, the first module M1 and the second module M2 are provided with status information including a flag indicating their operating status, and the module classification unit 104 accesses the status information to identify whether each module is an operating module or a non-operating module.
[0046] Next, the update execution unit 106 executes software update for the module classified as a non-operating module in step S2 (step S3). If this module is a controller module 8-1 to 8-m, the control program, which is the installed software, is updated. If this module is an IO adapter module 12 or an IO module 14, the firmware, which is the installed software, is updated. In step S3, if there are multiple non-operating modules, software updates may be executed for the multiple non-operating modules.
[0047] Next, the abnormality determination unit 108 acquires first status data from the operating modules and acquires second status data from the non-operating modules (step S4). Then, the abnormality determination unit 108 determines the presence or absence of an abnormality based on the first status data and the second status data acquired in step S4 (step S5). In step S5, as described above with reference to FIG. 4, the presence or absence of an abnormality is determined for each item included in the first status data and the second status data.
[0048] As a result, if the abnormality determination unit 108 determines that there is no abnormality (step S5: YES), the operation state switching unit 110 changes the operation states of the first module M1 and the second module M2 so as to switch the operating module and the non-operating module with each other (step S6). In this way, switching between the operating module and the non-operating module is performed on the condition that it is determined that there is no abnormality due to the software update. This makes it possible to automatically perform high-quality software update work that avoids interference with the operation of the plant control device due to the software update.
[0049] After the operation state is switched, it is determined whether there are any other modules to be updated (step S7). If there are any modules to be updated (step S7: NO), the process returns to step S2, and the software of the other modules is updated according to the above-mentioned procedure. For example, when an update is executed on the first module M1 that was initially in a non-operating state among the first module M1 and the second module M2 to be updated, the first module M1 that was in a non-operating state is switched to an operating state, and the second module M2 that was in a operating state is switched to a non-operating state, and software update is executed again on the second module M2. That is, after the operating module and the non-operating module are switched, software update is also executed on the module that was operating as the operating module when the software update was performed on the original non-operating module. This makes it possible to complete the software update on both the multiplexed first module and the second module. Then, when there are no modules remaining to be updated and software updates have been completed on all modules to be updated (step S7: YES), the series of processes is terminated (END).
[0050] On the other hand, if the abnormality determination unit 108 determines that there is an abnormality (step S5: NO), the software update is interrupted (step S8). At this time, the operator may be notified by a visual display or a voice message that an abnormality has been found.
[0051] Among the modules to be updated, the IO adapter module 12 and the IO module 14 are connected via a multiplexed communication network (first ring network 16a and second ring network 16b) from the controller 8. The update information distributed from the distribution server 7 is provided via such a multiplexed communication network, thereby reducing the communication load on the communication network, improving the communication speed during the update, and effectively shortening the time required for the update.
[0052] As described above, according to the embodiment, among the multiplexed first module M1 and second module M2 constituting the plant control device 1, software is updated for the non-operating module. The second status data indicating the status of the non-operating module for which the software has been updated is compared with the first status data indicating the status of the operating module for which the software has not been updated, to determine whether or not there is an abnormality due to the software update. Then, on the condition that it is determined that there is no abnormality due to the software update, switching between the operating module and the non-operating module is performed. This makes it possible to automatically perform high-quality software update work that avoids the software update causing a disruption to the operation of the plant control device 1.
[0053] In addition, within the scope of the present disclosure, the components in the above-described embodiments may be replaced with well-known components as appropriate, and the above-described embodiments may be combined as appropriate.
[0054] The contents described in each of the above embodiments can be understood, for example, as follows.
[0055] (1) A software update system according to one aspect includes: A software update system for updating software stored in a non-volatile memory included in a multiplexed first module and a multiplexed second module of a plant control device, comprising: an update information transmission unit for transmitting update information of the software; a module classification unit for classifying the first module and the second module into either an operating module or a non-operating module; an update execution unit for executing an update of the software of the non-operating module based on the update information; an anomaly determination unit for determining the presence or absence of an anomaly by comparing first status data indicating a status of the operating module with second status data indicating a status of the non-operating module whose software has been updated; an operation state change unit for changing the operation states of the first module and the second module so as to replace the operating module and the non-operating module with each other when the abnormality determination unit determines that there is no abnormality; Equipped with.
[0056] According to the above aspect (1), of the multiplexed first and second modules constituting the plant control device, a software update is performed on a non-operating module. The second status data indicating the status of the non-operating module for which the software update has been performed is compared with the first status data indicating the status of the operating module for which the software update has not been performed, thereby determining whether or not there is an abnormality due to the software update. Then, on the condition that it is determined that there is no abnormality due to the software update, switching between the operating module and the non-operating module is performed. This makes it possible to automatically perform high-quality software update work that avoids the software update causing a disruption to the operation of the plant control device.
[0057] (2) In another embodiment, in the above embodiment (1), After the operating module and the non-operating module have been swapped with each other by the operation status change unit, the update execution unit executes the software update again on the non-operating module.
[0058] According to the above aspect (2), after the operating module and the non-operating module are switched as described above, the software of the module that was operating as the operating module when the software of the original non-operating module was being updated is also updated. This makes it possible to complete the software updates of both the multiplexed first module and second module without operating the plant control device.
[0059] (3) In another embodiment, in the above embodiment (1) or (2), The first status data includes actual output data output from the operating module, The second status data includes virtual output data that is virtually calculated by the non-operating module and corresponds to the actual output data.
[0060] According to the above aspect (3), by comparing the actual output data of the operating module with the virtual output data of the non-operating module, it is possible to appropriately determine whether or not the software update performed on the non-operating module was performed normally.
[0061] (4) In another embodiment, in any one of the above (1) to (3), The first status data includes self-diagnosis data of the operational module; The second status data includes self-diagnostic data on the non-operating module.
[0062] According to the above aspect (4), when each module has a self-diagnosis function, by comparing the self-diagnosis data of the operating module and the non-operating module, it is possible to appropriately determine whether or not the software update performed on the non-operating module was performed normally.
[0063] (5) In another embodiment, in any one of the above (1) to (4), The plant control device includes: A plurality of IO modules capable of transmitting and receiving analog signals between the plant's constituent devices; a plurality of IO adapter modules capable of transmitting and receiving digital signals between the plurality of IO module devices; a controller for controlling the plurality of IO adapter modules; Equipped with.
[0064] According to the above aspect (5), it is possible to preferably automatically update software for each module constituting a plant control device including an IO module, an IO adapter module, and a controller.
[0065] (6) In another embodiment, in the above embodiment (5), The plurality of IO modules includes the first module and the second module.
[0066] According to the above aspect (6), automatic software update can be preferably performed in the first module and the second module included in a plurality of IO modules capable of transmitting and receiving analog signals to and from the constituent devices of the plant.
[0067] (7) In another embodiment, in the above embodiment (5) or (6), The plurality of IO adapter modules includes the first module and the second module.
[0068] According to the above aspect (7), it is possible to preferably automatically update software in the first module and the second module included in a plurality of IO adapter modules capable of transmitting and receiving digital signals to and from a plurality of IO modules.
[0069] (8) In another embodiment, in any one of the above (5) to (7), The controller includes a plurality of controller modules including the first module and the second module.
[0070] According to the above aspect (8), it is possible to preferably automatically update software in the first module and the second module included in a plurality of controller modules of a controller for controlling a plurality of IO adaptor modules.
[0071] (9) In another embodiment, in any one of the above (1) to (8), The first module and the second module are configured to be able to acquire the update information via a multiplexed communication network.
[0072] According to the above aspect (9), the update information is acquired via a multiplexed communication network, which reduces the communication load on the communication network, thereby improving the communication speed during the update and effectively shortening the time required for the update.
[0073] (10) In another embodiment, in any one of the above (1) to (9), The software is firmware.
[0074] According to the above aspect (10), the firmware stored in the non-volatile memory mounted in each module constituting the plant control device can be suitably updated.
[0075] (11) In another embodiment, in any one of the above (1) to (10), The plant control device is configured integrally with a terminal for operating and controlling the plant control device.
[0076] According to the above aspect (11), by integrating each function related to software updating with a terminal for operating and controlling the plant control device, software updating can be preferably performed in an existing plant control device.
[0077] (12) A software update method according to one aspect includes the steps of: A software update method for updating software stored in a non-volatile memory included in a multiplexed first module and a multiplexed second module included in a plant control device, comprising: transmitting update information of the software; classifying the first module and the second module as either an active module or an inactive module; performing an update of the software of the non-operating module based on the update information; determining whether or not an abnormality exists by comparing first status data indicating a status of the operating module with second status data indicating a status of the non-operating module whose software has been updated; changing the operation states of the first module and the second module so that the operating module and the non-operating module are interchanged when it is determined that there is no abnormality; Equipped with.
[0078] According to the aspect (12) above, of the multiplexed first and second modules constituting the plant control device, a software update is performed on a non-operating module. The second status data indicating the status of the non-operating module for which the software has been updated is compared with the first status data indicating the status of the operating module for which the software has not been updated, thereby determining whether or not there is an abnormality due to the software update. Then, on condition that it is determined that there is no abnormality due to the software update, switching between the operating module and the non-operating module is performed. This makes it possible to automatically perform high-quality software update work that avoids the software update causing a disruption to the operation of the plant control device.
[0079] (13) A software update program according to one aspect of the present invention comprises: A software update program for updating software stored in a non-volatile memory included in a first module and a second module multiplexed in a plant control device, A computer device includes: transmitting update information of the software; classifying the first module and the second module as either an active module or an inactive module; performing an update of the software of the non-operating module based on the update information; determining whether or not an abnormality exists by comparing first status data indicating a status of the operating module with second status data indicating a status of the non-operating module whose software has been updated; changing the operation states of the first module and the second module so that the operating module and the non-operating module are interchanged when it is determined that there is no abnormality; It is possible to execute the following.
[0080] According to the aspect (13) above, of the multiplexed first and second modules constituting the plant control device, a software update is performed on a non-operating module. The second status data indicating the status of the non-operating module for which the software update has been performed is compared with the first status data indicating the status of the operating module for which the software update has not been performed, thereby determining whether or not there is an abnormality due to the software update. Then, on condition that it is determined that there is no abnormality due to the software update, switching between the operating module and the non-operating module is performed. This makes it possible to automatically perform high-quality software update work that avoids the software update causing a disruption to the operation of the plant control device. [Explanation of symbols]
[0081] 1 Plant control device 2 OPS 4. EMS 6 ACS 7. Distribution Server 8 Controller 8-1~8-m Controller Module 10-1~10-n IO equipment 12 IO Adapter 14 IO Module 16a First Ring Network 16b Second Ring Network 22 Communication Networks 100 Software Update System 102 Update information transmission unit 104 Module Classification Section 106 Update Execution Department 108 Abnormality determination section 110 Operation status change unit
Claims
1. A software update system for updating software stored in a non-volatile memory included in a multiplexed first module and a multiplexed second module of a plant control device, comprising: an update information transmission unit for transmitting update information of the software; a module classification unit for classifying the first module and the second module into either an operating module or a non-operating module; an update execution unit for executing an update of the software of the non-operating module based on the update information; an anomaly determination unit for determining the presence or absence of an anomaly by comparing first status data indicating a status of the operating module with second status data indicating a status of the non-operating module whose software has been updated; an operation state change unit for changing the operation states of the first module and the second module so as to replace the operating module and the non-operating module with each other when the abnormality determination unit determines that there is no abnormality; A software update system comprising:
2. The software update system according to claim 1 , wherein the update executor executes the software update again on the non-operating module after the operating module and the non-operating module have been swapped with each other by the operation status changer.
3. The first status data includes actual output data output from the operating module, The software update system according to claim 1 or 2, wherein the second status data includes virtual output data that is virtually calculated in the non-operating module and corresponds to the actual output data.
4. The first status data includes self-diagnosis data of the operational module; The software update system of claim 1 or 2, wherein the second status data includes self-diagnostic data on the non-operating module.
5. The plant control device includes: A plurality of IO modules capable of transmitting and receiving analog signals to and from constituent devices of the plant; a plurality of IO adapter modules capable of transmitting and receiving digital signals to and from the plurality of IO module devices; a controller for controlling the plurality of IO adapter modules; The software update system according to claim 1 or 2, comprising:
6. The software update system of claim 5 , wherein the plurality of IO modules includes the first module and the second module.
7. The software update system of claim 5 , wherein the plurality of IO adapter modules includes the first module and the second module.
8. The software update system of claim 5 , wherein the controller comprises a plurality of controller modules including the first module and the second module.
9. The software update system according to claim 1 , wherein the first module and the second module are configured to be able to acquire the update information via a multiplexed communication network.
10. The software update system according to claim 1 or 2, wherein the software is firmware.
11. 3. The software update system according to claim 1, which is configured integrally with a terminal for operating and controlling the plant control device.
12. A software update method for updating software stored in non-volatile memories included in a first module and a second module multiplexed in a plant control device, comprising: transmitting update information of the software; classifying the first module and the second module as either an active module or an inactive module; performing an update of the software of the non-operating module based on the update information; determining whether or not an abnormality exists by comparing first status data indicating a status of the operating module with second status data indicating a status of the non-operating module whose software has been updated; changing the operation states of the first module and the second module so that the operating module and the non-operating module are interchanged when it is determined that there is no abnormality; A software update method comprising:
13. A software update program for updating software stored in a non-volatile memory included in a multiplexed first module and a multiplexed second module of a plant control device, comprising: A computer device includes: transmitting update information of the software; classifying the first module and the second module as either an active module or an inactive module; performing an update of the software of the non-operating module based on the update information; determining whether or not an abnormality exists by comparing first status data indicating a status of the operating module with second status data indicating a status of the non-operating module whose software has been updated; changing the operation states of the first module and the second module so that the operating module and the non-operating module are interchanged when it is determined that there is no abnormality; Possible software updates.
Citation Information
Patent Citations
Automatic update method
JP2008217201A
