JP2009153324A - System of designing di/o monitoring data and designing method thereof - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To surely and easily design DI/O monitoring data by automatically setting the DI/O monitoring data and check duplicate of signal names, etc. <P>SOLUTION: Many DI/O monitoring data are associated with DI/O signals by using a computer device. Signal names are extracted as they are from a DI/O drawing to create a text file. From this text file, data set in a "DI" sheet and a "DO" sheet is created as a bit definition data file. A net list file is created by connecting lines and recognizing symbols and characters in a monitoring sequence drawing. Based on the bit definition data file and the net list file, monitoring data and a monitoring sequence are created by net list-POL (problem-oriented language) conversion. From a drawing of an abnormal code list, abnormal code list data is extracted. From the monitoring data and the abnormal code list data, DI/O monitoring data for each abnormal code is output as a file. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a design method and a design method for DI / O monitoring data in a digital processing system such as a digital type protective relay system.

  Digital protective relay systems are, for example, the state of a number of system equipment (switch on / off, transformer operation / stop, etc.) at each substation to be protected, and the voltage / Current measurement information is collected in a computer system as DI / AI data, and the software installed in the computer system is used to monitor the presence and state of an accident and to perform protection control against the occurrence of the accident.

  One of the software designs in this type of digital protection relay system is the design of DI / O monitoring data. This design is a correspondence between a large number of DI / O monitoring data required by the software-designed monitoring sequence side and DI / O signals.

  FIG. 15 shows a conventional software design procedure for DI / O monitoring data, and a designer in charge individually checks the validity of the DI / O monitoring data. First, a DI / O drawing is prepared (S1). In this DI / O drawing, as shown in FIG. 2, the signal name (IB152T, etc.), address (DO1, etc.), and bit (bit position on the format data corresponding to the address DO1) of the DI / O monitoring data are described. It has been done. Next, a monitoring sequence drawing is prepared (S2). As shown in the example of FIG. 6, this monitoring sequence diagram describes the logical operation of the monitoring sequence, the DI / O data name used (1B189a, 1B189b, etc.) and the abnormal code name (7080, 7081, etc.). is there.

  The person in charge checks (collates) the DI / O drawing and the monitoring sequence drawing (S3). This check is performed for signal name inconsistency, double definition, and double definition of error codes. If it is determined that there is an error in this check, the drawing having the error is corrected (S4, S5). When it is determined that there is no error, the input signal of the monitoring sequence drawing is searched from the DI / O drawing, the address and bit are acquired (S6), and the DI / O monitoring data is set (S7). An example of a DI / O monitoring data file is shown in the figure, and has item names such as an abnormal code, a monitoring time, a monitoring type, an address 1, 2 and bits 1 and 2.

There is a method of automating program design and human interface screen design of the protective relay system (see, for example, Patent Document 1). Using this method, the DI / O monitoring data can be automatically created.
JP 2002-374616 A

  In the conventional design procedure of DI / O monitoring data, the setting of DI / O monitoring data (S7) and the check of each drawing (S3) are performed by the designer while collating the DI / O drawing and the monitoring sequence drawing. It will be. These operations require a larger work load and work time as the number of monitoring increases, and mistakes are more likely to occur.

  An object of the present invention is to provide a design method and a design method for automating checks such as setting of DI / O monitoring data and double definition of signal names, and ensuring and facilitating the design of DI / O monitoring data. is there.

  In order to solve the above-mentioned problem, the present invention automatically creates a netlist file from a monitoring sequence drawing, automatically creates monitoring sequence data from this and bit definition data, and extracts an abnormal code from the abnormal code list drawing. The DI / O monitoring data is automatically created in association with each other, and is characterized by the following method and method.

(1) A DI / O monitoring data design method in which a computer apparatus associates a large number of DI / O monitoring data and DI / O signals required by the designed monitoring sequence side,
The computer device includes:
A bit definition data creating means that creates a text file in which the signal name of the designed DI / O drawing is taken out as it is, and uses the data set in the “DI” sheet and “DO” sheet from this text file as a bit definition data file. When,
A netlist file creation means for reading a monitoring sequence diagram and creating a netlist file by drawing line connection and symbol recognition and character recognition;
Monitoring sequence data creating means for creating monitoring sequence data by netlist-POL (problem-oriented language) conversion based on the bit definition data file and the netlist file;
An abnormal code list extracting means for extracting abnormal code list data from the abnormal code list drawing;
DI / O monitoring data creating means for outputting, as a file, DI / O monitoring data classified by monitoring sequence and error code from the monitoring sequence data and the error code list data;
It is provided with.

(2) A method for designing DI / O monitoring data in which a computer apparatus associates a large number of DI / O monitoring data and DI / O signals required by the designed monitoring sequence side,
The computer device includes:
A bit definition data creation step of creating a text file in which the signal name of the designed DI / O drawing is extracted as it is, and using the data set in the “DI” sheet and “DO” sheet from this text file as a bit definition data file When,
A netlist file creation step of reading a monitoring sequence diagram and creating a netlist file by drawing line connection and symbol recognition and character recognition;
A monitoring sequence data creation step for creating monitoring sequence data by netlist-POL (problem language) conversion based on the bit definition data file and the netlist file;
An abnormal code list extracting step for extracting abnormal code list data from the abnormal code list drawing;
A DI / O monitoring data creation step for outputting, as a file, DI / O monitoring data classified by monitoring sequence and error code from the monitoring sequence data and the error code list data;
It is characterized by having.

  As described above, according to the present invention, a netlist file is automatically created from a monitoring sequence drawing, monitoring sequence data is automatically created from this and bit definition data, and an abnormal code extracted from the abnormal code list drawing is associated with this. In addition, since the DI / O monitoring data is automatically created, checks such as setting of DI / O monitoring data and double definition of signal names are automated, and the design of the DI / O monitoring data is surely and easily performed.

  Specifically, since the DI / O monitoring data is not created manually, errors are eliminated and the quality is improved. In addition, the number of production steps is reduced.

  FIG. 1 is a design procedure of DI / O monitoring data showing an embodiment of the present invention, and each procedure is realized by computer resources and software using the same. Hereinafter, each procedure will be described.

(S11) Bit definition data creation Bit definition data is created using a bit definition data creation tool. In this process, first, a DIO data extraction tool is used to output a DIO data file from a DI / O drawing. FIG. 2 shows an example of a designed DI / O drawing, and a text file is obtained by extracting the signal name of this drawing as it is. An example of this text file is shown in FIG. Next, the text file is read and set in the “DI” sheet and “DO” sheet of the bit definition data creation tool. An example of the “DI” sheet is shown in FIG. 4 and the signal names described in the DI / O drawing are set as they are. The data set in this sheet is obtained as a bit definition data file. An example of this file is shown in FIG.

(S12) Netlist file creation A netlist file is created from a monitoring sequence diagram using a netlist file creation tool having drawing reading, drawing line connection, symbol recognition and character recognition functions. In the monitoring sequence diagram, as shown in an example in FIG. 6, a failure detection method (abnormality detection logic) is described as a circuit diagram for each monitoring item. The net list creates a file as connection information for each input / output signal line in each circuit diagram of the monitoring sequence diagram as shown in FIG.

  The items included in the net list shown in FIG. 7 include symbol page, instrument number (circuit number), PINNo (connection pin number), IDENT, symbol name, terminal attribute, terminal number, wire number, etc. Symbols and numerical values are expanded in items.

  For example, when the abnormality detection logic of the monitoring sequence is as shown in FIG. 8, the input signal of the exclusive OR of E26 is “BGFLOCK” and “BGFUSE” and the output signal is “23% 26” in the netlist. , The netlist describes that an input signal of exclusive OR is input to terminals 1 and 3 and an output signal is obtained from terminal 2.

(S13) Monitoring sequence data creation Based on the bit definition data file created in step S11 and the netlist file created in step S12, a monitoring sequence is created using a netlist-POL (problem language) conversion tool. Data is created (see FIG. 6).

  FIG. 9 shows an example of netlist conversion by the netlist-POL conversion tool. In this conversion, the netlist description can be shortened by the sequence shortening tool. FIG. 10 shows a shortened example. When the logic shown in (a) is simply POL-converted, the result is as shown in (b), and the shortened sequence can be converted into that shown in (c).

  FIG. 11 shows an example of creating monitoring sequence data. In order to create monitoring sequence data combining the three logics shown in (a) of the figure, first, a shortened monitoring sequence is created for each logic as shown in (b) of the figure, A signal having the same signal name as the signal name is extracted from the bit definition data, and the monitoring data and the monitoring sequence shown in FIG. The monitoring data is also used for monitoring data creation processing (S15) in which an abnormal code described later is combined with the monitoring data.

(S14) Abnormal code list extraction Abnormal code list data is extracted from the abnormal code list drawing using the abnormal code list extraction tool.

  For example, as shown in an example in FIG. 12, abnormal codes are designed in advance according to differences in monitoring contents, main detection (M), accident detection (FD), and the like. Create as an abnormal code list data file as shown.

(S15) DI / O monitoring data creation Using the monitoring data creation tool, DI / O monitoring data is created from the monitoring data created in process S13 and the abnormal code list data extracted in process S14, as shown in FIG. In addition, DI / O monitoring data classified by error code is output as a file.

The design procedure of the DI / O monitoring data which shows embodiment of this invention. Example of DI / O drawing. Example of text file. Example of “DI” sheet. Example of bit definition data file. An example of a monitoring sequence diagram. Netlist example. Monitoring sequence error detection logic. Netlist conversion example. An example of shortening the netlist description. Example of creating monitoring sequence data. Example of error code list data. Example of error code list data file. An example of DI / O monitoring data. Software design procedure for conventional DI / O monitoring data.

Claims (2)

A design method of DI / O monitoring data in which a computer apparatus associates a large number of DI / O monitoring data and DI / O signals required by the designed monitoring sequence side,
The computer device includes:
A bit definition data creating means that creates a text file in which the signal name of the designed DI / O drawing is taken out as it is, and uses the data set in the “DI” sheet and “DO” sheet from this text file as a bit definition data file. When,
A netlist file creation means for reading a monitoring sequence diagram and creating a netlist file by drawing line connection and symbol recognition and character recognition;
Monitoring sequence data creating means for creating monitoring sequence data by netlist-POL (problem language) conversion based on the bit definition data file and the netlist file;
An abnormal code list extracting means for extracting abnormal code list data from the abnormal code list drawing;
DI / O monitoring data creating means for outputting, as a file, DI / O monitoring data classified by monitoring sequence and error code from the monitoring sequence data and the error code list data;
A design method for DI / O monitoring data characterized by comprising: A method of designing DI / O monitoring data in which a computer apparatus associates a large number of DI / O monitoring data and DI / O signals required by the designed monitoring sequence side,
The computer device includes:
A bit definition data creation step of creating a text file in which the signal name of the designed DI / O drawing is extracted as it is, and using the data set in the “DI” sheet and the “DO” sheet from this text file as a bit definition data file When,
A netlist file creation step of reading a monitoring sequence diagram and creating a netlist file by drawing line connection and symbol recognition and character recognition;
A monitoring sequence data creation step for creating monitoring sequence data by netlist-POL (problem language) conversion based on the bit definition data file and the netlist file;
An abnormal code list extracting step for extracting abnormal code list data from the abnormal code list drawing;
A DI / O monitoring data creation step for outputting, as a file, DI / O monitoring data classified by monitoring sequence and error code from the monitoring sequence data and the error code list data;
A method for designing DI / O monitoring data, comprising:

Images