JP2010262430A - Protection control device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a protection control device for easily and reliably executing the write-in operation of software by simplifying the complicated management of ID. <P>SOLUTION: The protection control device in which software includes a program and a database, and different functions are provided by changing the database is configured to, when the software to which model ID and device ID are attached is dispensed as write-in object software, verify the model ID in the dispensed software with the model ID attached to each device, and to, when those model IDs are matched with each other, permit the write-in processing of the program included in the dispensed software. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a protection control device that monitors an input control amount from a power system, and more particularly, to a software update method in a protection control device equipped with software.

  In the conventional software update method in the protection control device, one identifier (hereinafter referred to as “ID”) is set for each of the software to be written and the device to be written, and writing of all software is performed only when the respective IDs match. The operation is carried out. (For example, Patent Document 1)

JP 2004-274964 A

  By the way, when creating a protection control device having different functions, the software is configured by a program and a setting database (hereinafter referred to as “DB”), and the setting is changed in the DB by sharing the program, thereby having different functions. A method of creating a protection control device (hereinafter referred to as “conventional method”) is employed. On the other hand, as described above, in the conventional method disclosed in Patent Document 1, one ID is set for each of software to be written and a device to be written. Therefore, when the conventional method according to Patent Document 1 is applied to a conventional protection control device, even if the program is common, different DBs are given different IDs for different DB patterns.

  Here, consider a case where, when a program is changed due to a logic change or the like, only the changed program is rewritten to the corresponding protection control device all at once. In the case of the conventional method, different DBs are assigned different IDs for each DB pattern. Therefore, the task of finding the software including the corresponding program from a plurality of software having different IDs and extracting the ID is performed. I need it. Therefore, when performing the simultaneous rewriting, it is necessary to perform another management as to which program an ID corresponds to, which complicates the management and increases the amount of ID extraction work. There is.

  Further, when the ID extraction operation is performed by a human hand, there is a problem that the possibility of omission of extraction increases as the number of IDs increases.

  Further, when writing the changed program to the protection control device, even if only the program is rewritten as described above, any one of the one and the plurality of IDs extracted from the plurality of devices having different IDs. It is necessary to search for a device that matches this and write to that device. Therefore, if the number of extracted IDs is large, the amount of work for searching for the target device increases, and there is a problem that the possibility of writing leakage increases.

  The present invention has been made in view of the above, and an object of the present invention is to provide a protection control device that simplifies complicated management of IDs and can easily and reliably execute a software writing operation.

  In order to solve the above-described problems and achieve the object, a protection control apparatus according to the present invention is configured by software having a program and a database, and having a different function by changing the database. In the apparatus, a software storage unit that stores software, an instruction read from the software storage unit, an operation processing unit that decodes the instruction and executes an operation instructed by the instruction, and reads the software in the software storage unit, A software read / write unit that writes software to a software storage unit, a software payout unit that issues software to be stored in the software, and outputs the issued software to the software read / write unit, and a device-specific ID for each device And an ID storage unit for storing a second ID at a lower level than the first ID, and the first ID and the second ID as software to be written When the software with the ID attached is paid out, the first ID in the paid out software is compared with the first ID assigned to the device, and when the first IDs match, The writing process of the program out of the delivered software is permitted.

  According to the protective relay device according to the present invention, it is possible to simplify the complicated management of IDs and to easily and reliably execute software writing operations.

FIG. 1 is a block diagram of the configuration of the protection control device according to the first embodiment. FIG. 2 is a diagram showing a configuration of the write target software in the first embodiment. FIG. 3 is a diagram illustrating an example of an ID management method and a writing process according to the first embodiment. FIG. 4 is a flowchart showing a search process for the writing target device. FIG. 5 is a flowchart showing the operation of the payout process. FIG. 6 is a block diagram of the configuration of the protection control device according to the second embodiment. FIG. 7 is a block diagram of the configuration of the protection control device according to the third embodiment. FIG. 8 is a block diagram of the configuration of the protection control device according to the fourth embodiment. FIG. 9 is a diagram showing a configuration of software to be written in the fourth embodiment. FIG. 10 is a diagram illustrating an example of an ID management method and a write process according to the fourth embodiment.

  Hereinafter, a protection control device according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings. In addition, this invention is not limited by embodiment shown below.

Embodiment 1 FIG.
FIG. 1 is a block diagram showing a configuration of a protection control device (also referred to as “control device” or simply “device”) according to the first embodiment of the present invention. As shown in FIG. 1, the protection control device 1 according to the first embodiment includes a protection control device 1, a software storage unit 2, an arithmetic processing unit 3, a software read / write unit 4, a software payout unit 5, an ID storage unit 8, And a display output unit 9.

  In FIG. 1, the software storage unit 2 stores a program and a DB. The arithmetic processing unit 3 reads a processing instruction described in the program in the software storage unit 2, decodes the instruction, and executes an operation designated by the instruction. The software payout unit 5 pays out software to be stored in the software storage unit 2 and outputs the software to the software read / write unit 4. When writing software, the software write instruction signal a 1 is output to the software read / write unit 4 and the arithmetic processing unit. Output to part 3. The software read / write unit 4 reads the software from the software storage unit 2 and performs the process of writing the software delivered from the software delivery unit 5 to the software storage unit 2.

  The ID storage unit 8 is a unique ID of the control device itself, and stores a model ID 6 as a first ID and a device ID 7 as a second ID. The display output unit 9 displays or externally outputs the model ID 6 and the device ID 7 stored in the ID storage unit 8. Here, the display function of the display output unit 9 can be realized by, for example, a liquid crystal display panel (LCD), a human machine interface (HMI), or the like.

  Here, the basic operation of the protection control device 1 shown in FIG. 1 will be described. The software payout unit 5 reads software stored in, for example, a medium (not shown), and transmits a software write instruction signal a1 to the software read / write unit 4 and the arithmetic processing unit 3. The arithmetic processing unit 3 uses the software write instruction signal a1 as one of interrupt processes, and when there is an interrupt, interrupts other processes and switches to the software write mode. Further, in response to the software write instruction signal a1, the software read / write unit 4 starts downloading the software from the software payout unit 5, and writes the downloaded software into the software storage unit 2.

  FIG. 2 is a diagram showing a configuration of the write target software in the first embodiment. As shown in FIG. 2, the software 10 to be written has a program 11 to which the model ID 13 is attached and a DB (DB-1, DB-2,..., DB-N) 12 to which the apparatus ID 14 is attached. Configured. In FIG. 2, the model ID 13 is an ID for determining the type of a writable program, and the device ID 14 is an ID for determining the type of a writable DB. These model ID 13 and device ID 14 are hierarchically divided as shown in the figure. That is, the model ID 13 is an upper level ID, and the device ID 14 is a lower level ID.

  The details of the process for writing software will be described later. For example, the model ID and device ID of the software to be written are compared with the model ID and device ID unique to the device attached to the device, and the model ID matches. In this case, the program writing process is permitted, and if the device IDs match, the DB writing process is also permitted. The reason why the model ID is a higher-level ID than the device ID is that when only the program writing process is determined, whether or not the writing can be performed can be determined by comparing only the model ID.

  Next, the ID management method and the relationship between the write target software and each device in the first embodiment will be described with reference to FIG. Here, FIG. 3 is a diagram illustrating an example of an ID management method and a writing process according to the first embodiment.

  In FIG. 3, each device (devices 15 to 18) is given a model ID and device ID unique to the device. Here, the same model ID is assigned to apparatuses having a common program type. Furthermore, the same device ID is assigned to the devices having the same model ID and the same DB type. For example, since the devices 15, 16, and 17 have a common program (Type_I), the same model ID (0xAA) is assigned, and the device 18 has a different program (Type_II). Different model IDs (0xBB) are assigned. Since the devices 15 and 16 have the same DB, the same device ID (0xBB) is assigned, while the device 17 has a different DB (Type_II). 0xCC).

  For example, in the software 10 to be written managed by a personal computer (PC) (not shown) or the like, a model ID and a device ID corresponding to the program and DB type are assigned. Specifically, in the example of FIG. 3, the writing target software 19 is given a model ID (0xAA) corresponding to the program type (Type_I) and a device ID (0xBB) corresponding to the DB type (Type_I). The program can be written to the devices 15, 16, and 17 having the same model ID. Furthermore, DB writing is also possible for the devices 15 and 16 having the same device ID.

  Next, a method for searching for a write target apparatus according to the first embodiment will be described with reference to FIG. FIG. 4 is a flowchart showing the search process for the writing target device.

  First, the model ID and device ID of the software to be written are acquired (step S11), and the model ID and device ID of the search device are also acquired (step S12). Next, each model ID is collated (step S13). Here, if the model IDs match (step S13, Yes), it is determined that the program is a device to be written (step S14). If the model IDs do not match in this determination process (No at Step S13), it is determined that both the program and DB are not write targets (Step S15), and the current search process is terminated.

  If it is determined in step S14 that the program is a device to be written, device ID matching processing is performed (step S16). If the device IDs match (step S16, Yes), both the program and DB are written. If it is determined that the device is a target device (step S17) and the device IDs do not match (step S16, No), it is determined that only the program is a target device for writing (step S18).

  According to the search process described above, when only the program is written, the determination process up to step S14 is executed. When both the program and the DB are written, the determination process is executed until step S17, and when only the DB is written. In step S18, the determination process is executed. Therefore, if a medium storing software is loaded only on a device that is determined as a write target in the search process, a payout process described in the following paragraphs is automatically executed.

  Next, the payout process in the first embodiment will be described with reference to FIG. FIG. 5 is a flowchart showing the operation of the payout process.

  First, the software payout unit 5 reads the model ID and device ID assigned to the write target software from, for example, a medium in which software (software other than the write target may be included) is stored (step S21). Further, the model ID and device ID of the search device are read from the device-specific ID data (step S22). Next, the software payout unit 5 collates the model ID of the software to be written with the model ID of the search device (step S23), and if the model IDs match (step S23, Yes), permits the payout of the program. However, if the model IDs do not match (No at Step S23), both the program and DB cannot be paid out (Step S25), and this processing flow ends.

  When program payout is permitted in step S24, the software payout unit 5 collates the device ID of the write target software with the device ID of the search device (step S26), and if the device IDs match (step S26). , Yes), DB payout is permitted (step S27), program and DB payout processing is executed (step S28), and the process proceeds to step S30. On the other hand, if the device IDs do not match (step S26, No), the software payout unit 5 executes only the program writing process (step S29), and proceeds to step S30. The software payout unit 5 performs verification that the software has been correctly written in the software storage unit 2 (step S30). If the software has been written correctly (step S30, Yes), the payout process is terminated and the software is written correctly. If not (No at Step S30), the payout is not completed and the process returns to Step S21.

  As described above, according to the protection control device of the first embodiment, the device-specific ID is divided into the higher-level model ID (first ID) and the lower-level device ID (second ID). Managed by model ID, DB is managed by device ID, and the model ID and device ID assigned to the software to be written are compared with the model ID and device ID unique to the device, and the model ID matches As long as the program is written and both the model ID and the device ID match, both the program and the DB write processing are executed. And a system that is composed of DBs and that prepares devices with different functions by changing DBs In the effect that the program and DB can be simplified management method ID for managing a different ID.

  Further, according to the protection control device of the first embodiment, when only the program is rewritten, since the model ID is the same even if the DB is different, the amount of work for extracting the ID including the program is reduced. The effect that it can be made small is acquired.

  Further, according to the protection control device of the first embodiment, in the search process for the write target device, the IDs serving as the search keys are the model ID and the device ID, and since the maximum is two, the work amount can be reduced. The effect that it can be obtained.

  Further, according to the protection control device of the first embodiment, the device unique ID and the software ID are collated, and the payout process is executed only when they match, so that the software writing process can be executed easily and without problems. The effect that it can do is acquired.

Embodiment 2. FIG.
FIG. 6 is a block diagram illustrating a configuration of the protection control device according to the second embodiment of the present invention. Parts that are the same as or equivalent to those in the first embodiment are given the same reference numerals, and descriptions thereof are omitted. The difference from the first embodiment shown in FIG. 1 is that the software payout unit 5 and the ID storage unit 8 are separated from other components and are installed in a remote terminal 20 installed in a remote place. . As shown in FIG. 6, the software payout unit 5 is connected to the first communication processing unit 21, and the software read / write unit 4 and the arithmetic processing unit 3 are provided on the protection control device 1 side. It is connected to the communication processing unit 22. The first communication processing unit 21 and the second communication processing unit 22 are connected via a communication network 23. The communication network 23 is configured by, for example, a local area network (LAN), a serial line (for example, RS485), or the like. The software to be written that is paid out from the software payout unit 5 is transmitted to the second communication processing unit 22 via the first communication processing unit 21. The write target software received by the second communication processing unit 22 is transferred to the software read / write unit 4. Since the subsequent processing is the same as that of the first embodiment, description thereof is omitted.

  In the protection control device of the second embodiment configured as described above, the software can be written without going to the site where the protection control device is installed when updating the software. Therefore, according to the protection control apparatus of the second embodiment, in addition to the same effects as those of the first embodiment, effects such as improvement in maintainability and cost reduction can be obtained.

Embodiment 3 FIG.
FIG. 7 is a block diagram illustrating a configuration of the protection control device according to the third embodiment of the present invention. Portions that are the same as or equivalent to those of the first and second embodiments are denoted by the same reference numerals, and description thereof is omitted. The difference from Embodiment 2 shown in FIG. 6 is that the ID storage unit 8 is installed on the protection control device side, and the first communication processing unit 21 is provided in a plurality of protection control devices. It is connected to the processing unit 22. The software delivery unit 5 of the remote terminal 20 issues a model ID and device ID acquisition request b1 to the protection control device to be rewritten, and acquires the device model ID 6 and device ID 7 by the acquisition response b2 from the device. . These acquired model ID and device ID are set as device-specific IDs. Since the subsequent processing is the same as that of the second embodiment, description thereof is omitted.

  In the second embodiment, the number of remote terminals required for the number of protection control devices installed in the field is required. However, in the protection control device according to the third embodiment, one remote terminal supports a plurality of protection control devices. be able to. Therefore, according to the protection control device of the third embodiment, in addition to the same effects as those of the second embodiment, further costs can be reduced. Further, in the protection control device according to the third embodiment, since the payout process for a plurality of devices can be executed simultaneously, the time required for payout can be shortened.

Embodiment 4 FIG.
FIG. 8 is a block diagram showing a configuration of the protection control device according to the fourth embodiment of the present invention, and FIG. 9 is a diagram showing a configuration of the software to be written in the fourth embodiment. Parts that are the same as or equivalent to those in the first embodiment are given the same reference numerals, and descriptions thereof are omitted. The difference from Embodiment 1 shown in FIG. 1 is that H / W_ID (third ID) for distinguishing the type of hardware (H / W) is added as the type of ID, and the program is H / W is divided into a basic program that absorbs the difference in W and an application program that corresponds to the logic part of the device. Specifically, the H / W_ID 24 and the basic program 25 are added to the software 10 to be written, and the program area of the software storage unit 2 on the apparatus is divided into a basic program area and an application program area. H / W_ID 26 is added to the storage unit 8. As shown in FIG. 9, the H / W_ID 24 attached to the software to be written is in a side-by-side relationship with the model ID 13 and is not in a higher-order relationship with the device ID 14.

  Next, the ID management method and the relationship between the write target software and each device in the fourth embodiment will be described with reference to FIG. Here, FIG. 10 is a diagram illustrating an example of an ID management method and a write process according to the fourth embodiment.

  In FIG. 10, devices having the same H / W have the same basic program and are given the same H / W_ID. Specifically, since the devices 27, 29, and 30 have the same H / W (H / W version 1), the basic program is the same, the same H / W_ID (0xAA) is assigned, and the device 28 is H / W. Since W is different (H / W version 2), H / W_ID (0xBB) different from the devices 27, 29, and 30 is assigned. The model ID and device ID are the same as in the case of FIG. 3 except that the management target of the model ID is an application program, and a description thereof will be omitted.

  For example, in the write target software 31 managed by a personal computer (PC) (not shown), when the target H / W is common, the basic program is common and a common H / W_ID is assigned. ing. Note that the model ID and device ID are the same as in the case of FIG. 3 except that the management target of the model ID is an application program, and a description thereof will be omitted.

  Thus, in the protection control device of the fourth embodiment, the software program in the first embodiment is divided into a basic program that absorbs the difference in H / W and an application program corresponding to the logic portion of the device. Since the program depending on / W can be separated, there is an effect that the robustness of the program portion corresponding to the logic portion of the apparatus can be improved. In addition, since the model ID and the device ID are set separately from the H / W dependent part, the effect that the management of the model ID and the device ID can be simplified can be obtained.

  In the fourth embodiment, the program has been described as being divided into a basic program that absorbs the difference in H / W and an application program that corresponds to the logic part of the apparatus. However, the present invention is not necessarily limited to these categories. . For example, a program corresponding to middleware interposed between a basic program and an application program may be defined, and an I / D may be assigned to the program corresponding to this middleware for management. A program corresponding to this middleware may be included in the basic program and managed, or may be included in the application program and managed.

  In the first embodiment, the device-specific IDs are two types, ie, the model ID that is the first ID and the device ID that is the second ID. In the fourth embodiment, the ID of H / W_ID that is the third ID is used. Although it is set as three types, it is not limited only to two types and three types, It is good also as N (N is a natural number of 2 or more) types.

  In the fourth embodiment, H / W_ID (third ID) that is in a side-by-side relationship with the model ID (first ID) is added. However, the apparatus ID and the side-by-side fourth ID are subordinate to the model ID. May be added, or a fifth ID may be added below the device ID. Further, a sixth ID may be added below the newly added H / W_ID.

  As described above, the protection control device according to the present invention is useful as an invention that simplifies complicated management of IDs and can easily and reliably execute software writing operations.

DESCRIPTION OF SYMBOLS 1 Protection control apparatus 2 Software memory | storage part 3 Arithmetic processing part 4 Software read / write part 5 Software issue part 8 ID memory | storage part 9 Display output part 10 Software 11 Program (application program)
12 Database (DB)
6,13 Model ID
7, 14 Device ID
19, 31 Software to be written 20 Remote terminal 21 First communication processing unit 22 Second communication processing unit 23 Communication network 24, 26 Hardware ID (HW_ID)
25 Basic program

Claims (9)

In the protection control device of the system in which the software is configured to have a program and a database and has different functions by changing the database,
A software storage unit for storing software;
An operation processing unit that reads an instruction from the software storage unit, decodes the instruction, and executes an operation instructed by the instruction;
A software read / write unit that reads the software in the software storage unit and writes the software in the software storage unit;
A software payout unit for paying out software to be stored in the software, and outputting the payout software to the software read / write unit;
An ID storage unit for storing a first ID at a higher level assigned to each device as an ID unique to the device and a second ID at a lower level than the first ID;
With
When the software with the first ID and the second ID is issued as the software to be written,
The first ID in the paid-out software is compared with the first ID assigned to the device, and when the first IDs match, the program of the paid-out software is written. A protection control device that permits processing.   The database write processing of the paid out software is permitted when a second ID in the paid out software matches a second ID attached to the apparatus. The protection control device according to 1. While connecting the software payout unit with a first communication processing unit, connecting the software read / write unit and the arithmetic processing unit with a second communication processing unit,
The protection control device according to claim 1, wherein the first communication processing unit and the second communication processing unit are connected by a communication line. The second communication processing unit is provided corresponding to one or a plurality of devices,
The first communication processing unit and one or more of the second communication processing units are connected via a communication line, and software can be paid out simultaneously to the one or more devices. The protection control device according to any one of claims 1 to 3.   The protection control apparatus according to claim 1, further comprising a display output unit that reads out the first ID and the second ID, and outputs or displays the first ID and the second ID.   The software read / write unit verifies whether or not the software paid out from the software payout unit is correctly written in the software storage unit. Protection control device. The program is divided into a basic program that absorbs the difference in H / W and a program other than the basic program,
The ID storage unit stores a third ID corresponding to the basic program as an apparatus-specific ID,
When the software with the third ID is paid out as the write target software,
When the third ID in the paid-out software is compared with the third ID assigned to the device, and the third IDs match, the basic program of the paid-out software The protection control device according to claim 1, wherein write processing is permitted. The program is divided into an application program corresponding to the logic of the device and a program other than the application program,
The protection control device according to claim 1, wherein, when the first IDs coincide with each other, write processing of an application program of the paid out software is permitted.   7. The protection control device according to claim 1, wherein N types (N is a natural number of 2 or more) of IDs are set as the device-specific ID.

Images