JP2001228916A - Method and device for performing and monitoring event- driven control program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a method and device for executing a plant control program, whose execution is controlled by an event, and monitoring its execution situation. SOLUTION: A logic diagram described by a function block corresponding to the control program of a monitoring object is displayed on a display device 11. As the occurring situation of the event related with a block element included in the logic diagram, the number of occurring times within a prescribed time of the event related with the block element is displayed at the prescribed position of the logic diagram displayed on the device 11.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a method of executing an event-driven control program in a controller for plant control and a method of monitoring the execution status of the event-driven control program in the controller.

[0002]

2. Description of the Related Art FA (Factory Automation)
In an automation system such as a computer or a PA (process automation), a plant is controlled by a control computer such as a controller or a PLC (programmable controller) (hereinafter, these computers are collectively referred to as a controller). These controllers operate according to a control program, thereby realizing a function of outputting an operation signal or the like to an actuator according to a signal observed from a plant. This control program is created based on a higher-level specification expressing a target function. A method using a block diagram as this specification, that is, a control logic description method is generally known. In this method, routine processing in a controller is grouped, associated with a function block (element), and control logic is graphically described by these elements and their connection relations. The connection relation between the elements at this time corresponds to the data input / output relation in each element. Based on the control logic described as a block diagram,
A control program can be created by expanding each block into processing (instructions) in the controller in consideration of the execution order relation between blocks and the input / output relation of data.

A control logic description method based on a block diagram includes a non-event driven type FB (function block) and an event driven type FB depending on an execution form of a control program.
B (function block).
The non-event-driven FB is a method of describing control logic used when a controller executes a control program created based on the FB at regular intervals.
On the other hand, the event-driven FB executes execution of a control program corresponding to each block by an event occurring in a plant or the like,
Alternatively, it is a method of describing control logic suitable for a case where the event is associated with an event such as a change in a data value inside the controller and the execution of the control program is managed by the event. Details of the non-event driven FB and the event driven FB are described in IEC 6113, respectively.
1-3: ProgrammableController
s-Part3: Programming Lang
uages, IEC (1993); H. Chirs
tensen: The Feature of IPMC
S programming and configur
ation, Function Block Block Preliminary Proceedings, The Japan Electrical Measurement Instruments Industry Association, pp. 29-60 (1996). In the following, portions related to the present invention will be briefly described.

[0004] As described above, the FB associates one or more processes to be executed by the controller with one block in advance, and describes the control logic by combining the blocks. In the following description, a block corresponding to the processing of the controller will be referred to as an FB element. A control logic diagram expressing the execution order of processing and the input / output relationship of signals or data inside the controller by connecting the FB elements with a line, that is, a path system, is called an FB logic diagram. And
The FB logic diagram shows all FBs included in the control logic.
The control program can be generated by developing the elements in the processing of the controller which is predetermined for each FB element and setting variables for exchanging data between the FB elements. These are features common to the non-event driven FB and the event driven FB. In the following description, a control program corresponding to each FB element is called an FB program.

On the other hand, the event-driven FB defines event input and event output signals for each FB element in order to manage a program by an event. As described above, when the control program based on the event-driven FB is executed, the occurrence of this event starts the FB program for each FB element. In addition, event-driven F
B can define a plurality of internal states and corresponding processes for each FB element, and can transition the internal states according to an input event. That is, the process can be switched for each FB element depending on the internal state and an event from the outside. Further, the event-driven FB outputs the above-described predefined event as an execution result of the FB program.

The following describes a control logic for controlling the operation and stop of two pumps in response to an increase / decrease command of the number of operation units input from the outside, in the case where an event-driven FB is used and a description method. The operation will be described using a specific example. FIG. 4 is an example of an FB logic diagram, that is, an example of a control logic diagram described in the event-driven FB. In this example, the FB logic diagram is a “number setting device” FB (100
a), "Pump 1 operation controller" FB (100b),
“Pump 2 operation controller” FB (not shown, “Pump 2 request” 102a, “Pump 2 operation” 104c,
An output destination of the “pump 2 stop” 104d is a “pump operation controller” having the same configuration as the “pump operation controller” 100a. ) Of the three FB elements. here,
"Number setting unit", "Pump 1 operation controller", "Pump 2
The “operation controller” is a name given to each FB element. The "number setting device" FB (100a) is an FB element which describes a control logic which is input from another FB element and determines the number of pumps to be operated according to the number increase / decrease command. "Pump 1 operation controller" FB (100b)
An FB element that describes control logic for processing start / stop of the pump 1 in response to a start / stop request from the “number setting unit” FB (100a). "Pump 2 operation controller" FB
Is omitted from FIG. 4 because it is the same as the “pump 1 operation controller” FB except that the operation target is the pump 2.

In FIG. 4, the upper left side of each FB element is an input, that is, an event signal which is a starting condition of the FB program, the upper right side is an event signal output as an execution result of the FB program, and the lower left side is an FB program. An input data signal to be read at the time of execution and an output data signal to be output as an execution result are described on the lower right side. In the case of the “number setting device” FB (100a), the input event is
"Number increase command" 101a, "Number decrease command" 101b,
"Alarm" 101c. The output events are “pump 1 request” 102a, “pump 1 request” 1
02b. The FB element has one and five input / output data as shown in the figure. The specific processing content of the "number setting device" FB (100a) will be described with reference to FIG. In this figure, 105a-
d indicates the internal state of the FB, 106a to 106d indicate processing at the time of transition of each internal state, and characters in parentheses with arrows between the internal states indicate events that are transition conditions between the states. However, the internal state “stop processing” 105 d and “0 operation” 10
"(1)" between 5a means that a transition occurs unconditionally.

For example, in the "single unit operation" state 105a, a "number increase command" event occurs, that is, when the "number increase command" event signal 101a changes from the "OFF" state to the "O" state.
If the state changes to “N”, the internal state is
5b, and at the same time, the output data “Pump 2 operation” 10
4c is "1", output data is "Pump 1 operation" 1
The value of “1” is output as the value of the “pump 1 request” event 102 a and the “pump 2 request” event 1
02b is generated. Here, the “pump 2 request” event 102b is connected to the “pump 2 operation controller” FB.

As described above, in the event driven type, the internal state is changed according to the event associated with each FB element,
Processing corresponding to the internal state can be executed.
In addition, the FB element generates an event for another FB element to which the signal is connected, and can execute an appropriate process according to the situation of the plant. In the case of FIG. 4, the “pump 1 request” event 102a generated in the “number setting device” FB (100a) corresponds to the “pump 1 operation controller” FB (100a).
b), and the “pump 1 operation” 104 in this FB
a, the process is executed in response to the “pump 1 stop” 104b.

In FIG. 4, a dotted line indicates that the FB is connected to another FB. FB
The type and number of the internal states of the elements can be freely set by the user who creates the control logic. From this fact, the user can freely create an FB element that realizes the intended function and combine it to form a control logic. Also, by creating a control program based on the FB logic diagram described using such FB elements,
The control program can be easily implemented as components, and a high-quality control program can be created in a short time.

As described above, creation of a control program based on FB has an advantage that a user can easily create a control program by selecting elements necessary for processing and connecting them in order. That is, the user who creates the control program can create the control program without editing detailed and complicated commands and variables in the control program.

On the other hand, when performing maintenance or debugging of a control program created based on the FB logic diagram,
It is necessary to check a path between the B elements, that is, a connection relation of signals and the like, a processing result by each FB element, and the like.
For the purpose of supporting such maintenance and debugging, a monitor of a control program for a non-event driven type has been devised. This is to display the corresponding FB logic diagram on the display device while executing the control program in the controller, and to set the path between each FB element, that is,
The present value of the signal data in the controller is collected from the controller at a constant cycle and displayed at a corresponding position. By using such a monitor, a user who performs maintenance or debugging of the control program can easily grasp the execution status of the control program actually being executed by the controller.

Japanese Patent Application Laid-Open Nos. 4-118704 and 4-1 disclose an example of an event-driven control program.
No. 82803, JP-A-8-115107, JP-A-11
-203154, JP-A-10-333935, JP-A-10-320353, JP-A-10-301664
JP-A-9-218793, JP-A-8-1294
No. 83 and JP-A-7-152567. But,
These have no concept of FB or block diagram.

[0014]

As described above, the FB program created by using the event-driven FB is started when an event occurs, and the internal state changes according to the type of the event. Processing according to the internal state is executed. When maintaining and debugging an FB program created using such an event-driven FB, maintenance or debugging of a certain FB element must be performed unless the internal state transition process and the type of executed processing are accurately known. Debugging is virtually impossible. In order to obtain such information, the occurrence status of all input / output events in the FB element to be monitored must be observed. However, the conventional monitor is intended for a non-event driven FB in which the processing of each FB element is fixed. That is, in the controller executing the FB program, the availability data on the FB element to be monitored at a certain moment is collected, the result is displayed at the position of the corresponding path in the FB logic diagram, and the processing content and the current state of the FB element are displayed. Monitor. On the other hand, in the event-driven FB, an event signal to be input to the FB element is reset upon activation of the FB program corresponding to the FB element after the occurrence of the event. Therefore, it is impossible to monitor the occurrence of an event even if data of a state at a certain moment in a controller is collected and displayed using the conventional monitoring device. That is, it is possible to display on the monitor that an event has occurred only when an event has occurred by chance when collecting data for monitoring. The inability to monitor the occurrence of an event means that the occurrence of the event cannot be accurately grasped, making maintenance and debugging practically difficult.

The present invention provides a method and an apparatus for executing an FB program created based on the FB logic diagram as described above and allowing a user to easily monitor the execution status of the FB program, particularly the event occurrence status. The purpose is to do.

[0016]

According to the present invention, there is provided a method for executing / monitoring an event-driven control program which is started by the occurrence of one or more events accompanying a change in a data state. A block diagram showing the relationship between the control programs is displayed on the display device by a signal line to be displayed, and the number of times of occurrence of an event corresponding to an event signal line connected to a block element included in the block diagram within a predetermined time is stored, A method for executing / monitoring an event-driven control program, which is displayed at a predetermined position in the block diagram, is disclosed.

Further, the present invention relates to a method for executing / monitoring an event-driven control program which is started by the occurrence of one or more events accompanying a change in the data state, wherein a signal line representing an event for starting the control program is provided. A block diagram showing a relationship between control programs is displayed on a display device, and an event history corresponding to an event signal line connected to a block element included in the block diagram is stored. Based on the stored occurrence history, A method for executing / monitoring an event-driven control program, characterized by displaying a time chart showing a past occurrence state of an event corresponding to the displayed block element, is disclosed.

Further, the present invention provides a method for executing / monitoring an event-driven control program which is started by the occurrence of one or more events accompanying a change in the data state. First means for storing FB block diagram data corresponding to each FB program and clearly indicating an event input / output line and a data input / output line; and a first means for forming a control program according to an event to be generated. A second means for activating and executing the FB program stored in the first means, a display device, and a step of designating the FB program to be monitored and related information; Reading from the first means and displaying it as a block diagram on the screen of the display device; The event that occurred during the execution of the control program is checked to be the start event of the FB program to be monitored, and the event history including the start event and the input / output during execution of the FB program are checked. A method for executing / monitoring an event-driven control program, comprising the steps of: storing data; and extracting the stored event occurrence history and input / output data and displaying the data at a relevant portion of the block diagram being displayed on the display device. Disclose.

Further, the present invention relates to an apparatus for executing and monitoring an event-driven control program which is activated by the occurrence of one or more events accompanying a change in data state.
First storage means for storing block diagram data indicating a relationship between control programs by a signal line representing the control program and an event for starting the program, and an event connected to a specific block element included in the block diagram A second storage unit for storing data on the occurrence status of an event corresponding to the signal line; reading block diagram data from the first storage unit in response to externally input data; displaying a block diagram; An event-driven control program having means for reading data on the occurrence status of an event related to the displayed block diagram from the second storage means and displaying the data at a corresponding position in the block diagram being displayed. An execution / monitoring device of the invention is disclosed.

Further, according to the present invention, there is provided an event-driven control program execution device for executing control by an event-driven control program, wherein the first means for storing FB programs grouped by the control contents of the control program; A second means for storing block diagram data corresponding to FB, corresponding to the program and explicitly indicating an event input / output path and a data input / output path, and stored in a first means for forming a control program according to an event to be generated. Done F
A third means for activating and executing the B program, a fourth means for designating an FB program to be monitored, and a block diagram data corresponding to the designated FB is read from the second means and displayed as a block diagram on a screen. Fifth means and third
It is checked whether or not the event that occurred during the execution of the control program by the means is a start event of the FB program to be monitored specified by the fourth means. An occurrence history of an event relating to the FB program, input / output data during execution of the FB program activated by the event,
An event-driven control program execution monitor device comprising: a sixth means for storing the information; and a seventh means for reading out the corresponding information in the sixth means in accordance with the designated contents and displaying the information at a relevant location.

[0021]

FIG. 1 shows an example of the configuration of an execution / monitor device 1. The execution / monitoring device 1 of FIG. 1 includes an FB logic diagram, an FB program storage unit 14 that holds an FB program created based on the FB logic diagram, an FB program execution unit 18 having a function of executing the FB program, F
The occurrence of an event that gives the timing of starting the B program is detected, whereby the input of a signal between the FB program execution management unit 19 having a function of executing the FB program in the FB program execution unit and the plant to be controlled is performed. A signal input / output processing unit 20 having a function of processing an output,
A signal data storage unit 17 is provided for holding input signal data input from the signal input / output signal processing unit and output data resulting from execution of the FB program, and executes the FB program using these. Further, the execution / monitoring device 1 monitors the execution status of the FB program stored in the FB program storage unit for each event-driven FB element that is the basis of the FB program. An event occurrence history storage unit 15 that holds the occurrence status of the event, a monitor information storage unit 16 that holds the value of a signal when the FB program is activated by the event, and an event that triggered the activation, and an FB logic diagram. Monitor display unit 11 having a function of displaying data to be input, and an input processing unit 1 for processing an input from a user
FB program having a function of displaying data related to an FB logic diagram to be monitored on the monitor result display unit in accordance with information on an event-driven FB element input by a user via the input processing unit It has a monitor processing unit 13 and executes monitoring of the FB program. The processing at this time comprises the following monitor information collection processing and monitor result display processing.

The monitor information collection process is executed when the FB program execution management unit 19 detects the occurrence of an event corresponding to the activation of the FB program, and is constituted by the following processing steps. (1) A processing step of determining whether the event detected by the FB program execution management unit 19 is an input event of the FB to be monitored. (2) A processing step of writing information of an event to be processed to the event occurrence history storage unit 15 when it is determined in the processing step (1) that the FB is a monitoring target FB. (3) A processing step of extracting the value of the input signal data for the monitoring target FB from the signal data storage unit 17 and writing the value to the monitor information storage unit 16. (4) The FB program corresponding to the FB to be monitored is
Processing steps executed by the B program execution unit 18. (5) A processing step of extracting the data value of the output signal from the monitoring target FB from the signal data storage unit 17 and writing the value into the monitor information storage unit 16. The monitor result display processing is performed by the FB program monitor processing unit 1.
In step 3, the process is executed when the user inputs data of the monitoring target FB via the input processing unit, and is configured by the following processing steps. (A) The monitoring target F is stored in the FB program storage unit 14 based on data input by the user through the input device.
A processing step of writing data for identifying B, its FB program, and events and signal data related to them to the monitor information storage unit 16 and the event occurrence history storage unit 15. (B) a processing step of displaying the monitoring target FB as an FB logic diagram on the monitoring result display unit 11 for monitoring the execution status. (C) The value of the signal data at the start of the FB program written in the processing step (3) of the FB program execution management unit 19 is stored in the monitor information storage unit 16.
And displaying the data value at the corresponding position in the FB logic diagram displayed in the processing step (B). (D) The data written in the event occurrence history storage unit 15 in the processing step (2) of the FB program execution management unit 19 is read, and the FB logic diagram displayed in the processing step (B) based on the data is read. A processing step of displaying the number of occurrences of an event at a position corresponding to each of the events. In this processing step, (C)
And (D) are repeatedly executed until the monitor is terminated.

The present invention makes it possible to execute and monitor an FB program based on an event-driven FB by the above-described monitor information collection processing and monitor result display processing. Further, in the present invention, in the processing step (2), an event that has occurred for each monitoring target FB and an occurrence time thereof are applied as information to be written to the event occurrence history storage unit 15. Then, as the event information to be displayed in the processing step (D), a time series of events related to the monitoring target FB is displayed.

Further, according to the present invention, the FB program monitor processing section 13 holds mode data for switching signal data to be displayed at the time of monitoring between “value at the time of executing the FB program” and “current value”. If this data is a value corresponding to the “current value”, the signal data storage unit 17 is used instead of the processing step (C).
, A processing step of extracting the value of the input / output data of the FB to be monitored from the FB logic diagram and displaying the value at a corresponding position in the FB logic diagram displayed on the monitor result display unit 11 is executed.

Further, according to the present invention, the user can use the input processing unit 12.
When the data for resetting the event information related to the FB being monitored is input via the CPU, a processing step for clearing the information related to the event, which is stored in the event occurrence history storage unit 15, is executed.

The execution / monitor device 1 of the present embodiment is configured to be divided into a plurality of parts for each processing function and connected by a data bus 21. This can be easily realized as a processing program and a storage device by one personal computer connected to a communication line.
The monitor result display unit 11 as described above displays information related to the result of monitoring the FB program. In the present embodiment, the monitor result display section 11 is constituted by a CRT. The input processing unit 12 processes input of data from a user of the execution / monitoring device of the present embodiment. In this embodiment, the input processing unit 12 includes a keyboard for inputting character string data and a mouse for designating and operating an operation switch to be displayed on the monitor result display unit 11.

The FB program monitor processing unit 13 is configured to monitor the F target according to data input by the user of the execution / monitor apparatus 1 of the present embodiment via the input processing unit 12.
It has a function of displaying the B logic diagram and related data on the monitor result display unit 11 and a function of writing data related to the FB to be monitored into the monitor information storage unit 16 and the event occurrence history storage unit 15 described below. Details of this function will be described later. FIG. 6 shows a monitor screen 11a displayed on the monitor result display unit 11 by the FB program monitor processing unit 13. This screen displays the FB to be monitored and its related information 100a and 100b, and operation switches 120a to 120f for controlling execution of the monitor.
It consists of. The display contents of 11a will be described later when the processing is described. Also, the FB program monitor processing unit 13
The input / output data of the FB to be monitored has a function of holding mode data for switching between displaying the current data value asynchronously with the execution of the FB or displaying the value at the time of the FB execution. In addition, the FB program monitor processing unit 13 has a function of holding mode data for switching whether to display data or not to display data of an FB event to be monitored during monitoring. Table 1 shows examples of these mode data. In the following description of the present embodiment, underlined portions of the data embodiments described in the table are portions to be written or read as a result of the processing. Other parts of the table are supplementarily added for the description of the embodiments.

[0028]

[Table 1] Further, in this embodiment, the user can change the mode data of Table 1 by operating the operation switches 120 (120a to 120f) shown in FIG. That is, when the user clicks the “display current value data” switch 120 a using a mouse, the FB program monitor processing unit 13
Writes "1" as the value of the "current value data display" mode in Table 1. "Runtime data display" switch 10
When 2b is clicked, “0” is written. Also, “event display” 102d, “event non-display” 1
When the 20d switch is clicked, “1” and “0” are written as the values of the “event display” mode, respectively.

Next, in FIG. 1, the FB program storage unit 14 stores an FB program to be executed / monitored,
The corresponding FB logic diagram data is held. F
The B program execution unit 18 stores the FB program storage unit 14
Has a function of actually executing the FB program stored in the FB. The FB program execution management unit 19 has a function of storing an event that triggers activation of all FB programs stored in the FB program storage unit 14 and executing the FB program corresponding to the event occurrence in the FB program execution unit 18. . The signal data storage unit 17 stores FB program input / output data values held in the FB program storage unit 14. The corresponding data is updated by the FB program execution unit 18 every time the FB program is executed.

The monitor information storage unit 16 stores the name of the FB program being monitored, the name of the event signal that triggered the start of the FB program when the FB program was last executed, and the name of the FB program used for executing the FB program. It has a function of retaining the value of the input data obtained and the value of the output data output as a result of the processing. The event occurrence history storage unit 15
And has a function of storing input / output events for each FB program to be monitored and its occurrence history data. The execution / monitoring device 20 according to the present embodiment is a signal input / output process for reading a signal from a detector and an operation panel installed in the plant 2 to be controlled and outputting a command signal to an actuator such as a pump also installed in the plant 2. Department. The signal input / output processing unit 20 has a function of generating an event according to the read signal. The processing function of each unit will be described later in detail when describing the processing.

In the execution / monitoring device 1 of this embodiment, when the user monitors the execution status of the FB program while executing the FB program, the user inputs the name of the FB element to be monitored via the input processing unit 12. input. For example, a list of FB names is displayed, and is selected with a mouse. The FB program monitor processing unit 13 writes the input monitor FB element name and related data into the monitor information storage unit 16. Further, the FB program monitor processing unit 13 writes the name of the input event to the monitored FB in the event occurrence history storage unit 14. Hereinafter, the FB for controlling the number of operating pumps in FIG. 4 used in the description of the FB will be used as an example. Table 2 shows that the user sets the “number setting device” FB element as the FB element to be monitored (FIG. 4,
As a result of selecting 100a), an example of data written by the FB program monitor processing unit 13 to the monitor information storage unit 16 is shown.

[Table 2]

Table 3 shows the monitor information storage unit 16.
FB program monitor processing unit 13 following writing to
Shows an example of data to be written to the event occurrence history storage unit 15.

[Table 3]

Next, the flow of the execution process of the FB program when an event occurs in the execution / monitoring device 1 of the present embodiment will be described with reference to the flowchart of FIG. 2 is performed when the signal input / output processing unit 20 detects an event signal from the detector or the operation panel of the plant 20 in the execution / monitoring device 1 of the present embodiment, or other FBs.
When an event occurs as a result of processing of the program, the FB program execution management unit 19 executes the event.

First, in step 200, it is determined whether or not the generated event is an input (activation) event of the monitoring target FB by referring to the event occurrence history storage unit 15. If the generated event is an input event of the monitoring target FB, the process proceeds to step 202. If the event is not the input event of the monitoring target FB, the process proceeds to step 201.

In step 201, the FB corresponding to the event that has occurred is read from the FB program storage unit 14,
The FB program is executed by the FB program execution unit 18. If the event that has occurred is not an input event of the monitoring target FB, the process ends here.

If it is determined in step 200 that the event is an input event of the monitoring target FB, in step 202, the event occurrence history is updated. That is, 1 is added to the number of occurrences of the corresponding event in the event occurrence history storage unit 15. For example, when the “number increase command” event occurs, the data of the number of occurrences of the input event “number increase command” in Table 2 is rewritten from “0” to “1”.

Next, at step 203, the FB to be monitored
Is written into the monitor information storage unit 16. An example is shown in Table 2 below. That is, the input data name for the monitoring target FB is read from the monitor information storage unit 16, the current value of the input data is extracted from the signal data storage unit 17, and the result is written in the execution value of the monitor information storage unit 16. Subsequently, the data of the “last event name” in the monitor information storage unit 16 is updated. For example, in the case of the above example, the “number increase command” is written as data of the “final occurrence event name”.

Next, in step 201, the FB to be monitored
Execute the processing of This processing is the same as the case where the generated event is not the one of the monitoring target FB. Although the last event has been described, there is also an example of an intermediate event.

Next, at step 204, the FB to be monitored
Is written into the monitor information storage unit 16. That is, the output data name from the monitoring target FB is read from the monitor information storage unit 16, the current value of the output data is extracted from the signal data storage unit 17, and the result is written to the execution value of the monitor information storage unit 16.
The execution / monitoring device of the present embodiment performs F
Execute the B program. Next, the flow of processing when the user of the execution / monitoring device inputs a monitored FB program in order to monitor the execution status of the FB program will be described in detail with reference to the flowchart of FIG.

The processing shown in FIG. 3 is executed by the FB program monitor processing section 13 when the user inputs the FB program to be monitored to the input processing section 12 in the execution / monitor apparatus 1 of the present embodiment. First, in step 300, the information of the FB program input by the user to the input processing unit 12 is written to the monitor information storage unit 16 and the event occurrence history storage unit 15. That is, before FB
As described in the description of the function of the program monitor processing unit 13, the input monitor FB element name and related data are written in the monitor information storage unit 16, and the event occurrence history storage unit 15 is input to the monitor target FB. Write the name of the event. That is, in the case of this embodiment, Table 2,
The data shown in Table 3 is written in each storage unit.

Next, at step 301, the FB program input by the user is read from the FB program storage unit 11, and the read FB program is displayed as an FB logic diagram on the monitor result display unit 1.
1 is displayed. At this time, the monitor result display unit 11 shown in FIG.
Is an embodiment in which the same FB logic diagram as the example of FIG. 3 used for describing the FB is displayed.

Next, in step 302, it is determined whether or not the display mode of the monitor is the present value data display mode, that is, whether the data of "present value data display" of the mode data (Table 1) is "1". . As a result, if the monitor display mode is the current value data display mode, the process proceeds to step 303; otherwise, the process proceeds to step 304.

In step 303, the F / Bs of all input / output data for the FB included in the FB program to be monitored
The data used at the time of executing B is read from the monitor information storage unit 16, and each read data value is displayed in the vicinity of an input or output link line in a corresponding FB of the FB logic diagram displayed on the monitor result display unit 11. FIG.
The screen 11a of the monitor result display section 11 is a display example when the data stored in the monitor information storage section 16 is as shown in Table 4. This indicates that the value of the “emergency stop” data at the time of executing the FB is “0”, the value of the “pump 1 stop” data is “1”, and the like.

[Table 4]

In step 304, the current values of all input / output data for the FB included in the FB program to be monitored are read from the signal data storage unit 17, and the read data values are displayed on the monitor result display unit 11. It is displayed near the input or output link line of the corresponding FB in the figure. Monitor result display section 11 in this case
Are displayed in FIG. 6 except that the data value 140 is not the value at the time of executing the FB, but the current value held in the signal data storage unit 17.
Is the same as the display.

Next, in step 305, it is determined whether or not the event display mode of the monitor, that is, the data of "event display" in the mode data (Table 1) is "1". As a result, if the monitor is in the event display mode, the process proceeds to step 306; otherwise, the process proceeds to step 307. In step 306, the event histories of all events for the FB included in the FB program to be monitored are read from the event occurrence history storage unit 15,
Each of the read occurrence histories is displayed near the link line of the corresponding FB event in the FB logic diagram being displayed on the monitor result display unit 11. In this embodiment, the number of occurrences of an event is displayed as an occurrence history. The screen 11a of the monitor result display unit 11 in FIG. 6 is a display example when the data stored in the event occurrence history storage unit 15 is as shown in Table 5. This is because the “number increase command” event has been performed twice since the monitor started,
This indicates that the "number decrease command" event has occurred once.

[Table 5]

Next, at step 307, it is determined whether or not there is an event reset request from the user. In the present embodiment, when the user clicks the “event reset” button 120e on the display screen 11a in FIG.
It is determined that an event reset request has occurred. If it is determined in step 307 that there is no event reset request, the process proceeds to step 309. If it is determined in step 307 that there is an event reset request, step 30
Proceeding to S8, the event occurrence history data in the event occurrence history storage unit 15 is cleared. In this embodiment, “0” is written in the “occurrence count” data for all the events in Table 3.

Next, in step 309, it is determined whether or not there is a monitor termination request from the user. In this embodiment, when the user clicks the "end monitor" button 120f of the embodiment 11a on the display screen of FIG.
It is determined that a monitor termination request has occurred. Step 30
If it is determined in step 9 that there is no monitor end request, the process returns to step 302. If it is determined in step 309 that there is a monitor end request, the process proceeds to step 310. In step 310, all the monitoring target FB information written in the monitor information storage unit 16 and the event occurrence history storage unit 15 in step 301 is deleted.

As described above, the execution / monitor apparatus 1 according to the present embodiment performs the processing of steps 200 to 204 to generate an event regarding the monitored FB,
Collect the data used during the run and at the same time step 30
The data collected by the processing of 0 to 310 is displayed. The user of the execution / monitoring device 1 of the present embodiment can use such F
By referring to the result of monitoring the execution status of B,
Debugging and maintenance of the B program can be easily performed.

In the above description of the embodiment, the information of the event occurrence history displayed on the monitor screen is the input / output event of the monitored FB after the start of the monitor or after the user executes the event reset. Only the number of occurrences. However, this is the same as in step 20 above.
By changing the information to be written in the event occurrence history storage unit 15 in step 2 and the information to be displayed on the monitor result display unit in step 306, it is possible to obtain not only the number of occurrences of the event but also information of the time series of the occurrence. In the following, a description will be given of a process executed in addition to the above-described embodiment to display time-series information.

First, the event occurrence history storage unit 15 holds data including the event name and the time of occurrence, in addition to the data on the number of occurrences of the event of the monitoring target FB as shown in the embodiment in Table 2 above. I do. Table 6 shows an example of the result of holding the occurrence time when monitoring the "speed setting device" FB. The event occurrence time data is executed by the FB program execution management unit 19 in step 202 at the same time as the update of the event occurrence count, and is sequentially added in the order in which the monitored events occur.

[Table 6]

Next, information on the occurrence time of this event is as follows:
In step 306, the FB program monitor processing unit 13
Displays a time chart on the monitor result display unit 11 for each event to be monitored. FIG. 7 shows a time chart displayed on the monitor result display section 11, that is, an example 11b of a display screen of an event occurrence history in the case of monitoring the "speed setting device" FB. As shown in this figure, on the event occurrence history display screen,
For each event of the monitoring target FB, a marker 150 is displayed at the time of occurrence.

When the information of the event occurrence time is monitored, when the FB program monitor processing section 13 executes the clearing of the event occurrence history in the step 308, the information is simultaneously stored in the event occurrence history storage section 15. Clear the information on the occurrence time of the event.

As described above, according to the present embodiment, at the time of executing the FB program, the user can confirm the event occurrence history for the specified FB on the display device. This is realized by writing the input / output event occurrence history into the event occurrence history storage unit every time the FB to be monitored is executed according to the present invention, and sequentially displaying this information on the display device. As described above, by monitoring the event occurrence history of the monitoring target FB, the user can easily debug and maintain the event-driven control program. For example, the monitor makes it easy for the user to determine whether or not a certain FB has been executed, how frequently the FB has been executed, and which event has triggered the FB. You can get to. As described above, the event-driven control program can be monitored at a higher level of abstraction than the control logic described in the FB, that is, the control program actually executed. -The user of the monitor device can debug the control program in a shorter time than before.

Although the occurrence history data is the number of times, time, time chart, etc., other data examples are also possible. Although the example of the plant control has been described, the present invention can be applied to data processing. In this case, it can be used for event occurrence and tracking thereof during the execution of data processing.

According to the present invention, the execution status of the event-driven control program can be monitored during execution.

[Brief description of the drawings]

FIG. 1 is a block diagram.

FIG. 2 is a flowchart illustrating a flow of processing of a monitor device of a control program according to an embodiment of the present invention.

FIG. 3 is a flowchart showing a process flow of a monitor device of a control program according to an embodiment of the present invention.

FIG. 4 is a diagram illustrating an example of a control logic diagram described using an event-driven FB.

FIG. 5 is a diagram showing details of processing by the FB element in the example of FIG. 4;

FIG. 6 is a diagram showing an embodiment of a display screen.

FIG. 7 is a diagram showing an embodiment of a display screen.

[Explanation of symbols]

 Reference Signs List 1 Control program execution / monitoring device 2 Plant 11 Monitor result display unit 12 Input processing unit 13 FB program monitor processing unit 14 FB program storage unit 15 Event occurrence history storage unit 16 Monitor information storage unit 17 Signal data storage unit 18 FB program execution Unit 19 FB program execution management unit 20 signal input / output processing unit 100 FB element 101, 102 event signal 103, 104, 105 data signal 106 internal state 107 processing 120 operation button 130 event monitor value 140 data monitor value 200 to 204, 300 to 310 processing steps

Claims (12)

[Claims] 1. A method for executing / monitoring an event-driven control program which is started by the occurrence of one or more events accompanying a change in a data state. A block diagram showing the relationship is displayed on a display device, and the number of occurrences of an event corresponding to an event signal line connected to a block element included in the block diagram within a predetermined time is stored, and at a predetermined position in the block diagram. An execution / monitoring method of an event-driven control program characterized by displaying. 2. A method for executing / monitoring an event-driven control program which is started by the occurrence of one or more events accompanying a change in a data state. A block diagram showing the relationship is displayed on a display device, an event history corresponding to an event signal line connected to a block element included in the block diagram is stored, and the display is performed based on the stored occurrence history. A method of executing / monitoring an event-driven control program, characterized by displaying a time chart showing a past occurrence state of an event corresponding to an element. 3. A method for executing / monitoring an event-driven control program which is started by the occurrence of one or more events accompanying a change in a data state, wherein the control program is controlled by a signal line representing input and output data to the control program. A block diagram showing the relationship between the two is displayed on the display device, and the value of input data at the start of the control program corresponding to the block element included in the block diagram and the value of output data at the end of processing of the control program And displaying it at a predetermined position in the block diagram. 4. A method for executing / monitoring an event-driven control program activated by the occurrence of one or more events accompanying a change in a data state, the method comprising: storing an FB program grouped by control contents of the control program; First means for storing block diagram data corresponding to the FB, corresponding to each FB program and explicitly indicating an event input / output line and a data input / output line, and first means for configuring a control program according to an event to be generated. A second means for activating and executing the stored FB program; a display device; a step of designating the FB program to be monitored and related information; and a program figure data corresponding to the designated FB from the first means. Reading and displaying a block diagram on the screen of the display device; It is checked whether the event occurred during the execution of the FB program is a start event of the FB program to be specified and monitored, an occurrence history of an event relating to the FB program including the start event, and input / output data during execution of the FB program. And a step of extracting the stored event occurrence history and input / output data and displaying the data at a relevant portion of the block diagram being displayed on the display device, and executing and monitoring the event-driven control program. 5. The event occurrence history includes an event related to a specific control program and an occurrence time thereof, and the display device displays a time series of the event. How to run and monitor event driven control programs. 6. The method according to claim 4, further comprising the step of clearing information relating to the event stored in the event when the user inputs data for resetting the event information via an input device. How to execute and monitor event-driven control programs. 7. An event-driven control program execution / monitoring device which is started by the occurrence of one or more events accompanying a change in a data state, wherein the control program and a signal line representing an event for starting the program are provided. A first storage unit for storing block diagram data indicating a relationship between control programs, and a second storage unit for storing data of an occurrence state of an event corresponding to an event signal line connected to a specific block element included in the block diagram. A block diagram data is read from the first storage unit in accordance with input data from the outside and a block diagram is displayed, and data on an occurrence state of an event related to the displayed block diagram is stored. , Read from the second storage means,
An execution / monitoring device for an event-driven control program, comprising: means for displaying at a position corresponding to a block diagram being displayed. 8. An apparatus for executing and monitoring an event-driven control program, which is activated by the occurrence of one or more events accompanying a change in data state, wherein the means for displaying the block diagram includes: A function of reading a data of an occurrence state of a related event from the second storage means and displaying a time chart showing a relation between the occurrence event and the occurrence time based on the data. 7. An event-driven control program execution / monitoring device. 9. An execution / monitoring device for an event-driven control program, which is activated by the occurrence of one or more events associated with a change in data state, and a signal line representing an event that activates the control program. FB program storage means for holding block diagram data indicating the relationship between control programs, FB program execution means having a function of executing processing based on the control program, and generation of an event giving the timing of starting the control program FB, whereby the control program is executed by the FB program execution means.
A program execution management means, a signal data storage means for holding output data obtained as a result of execution of the control program, an event occurrence history storage means for holding an occurrence state of an event which triggers activation of a specific control program, Monitor information storage means for holding the value of input data when the control program is started by an event and information on the event; monitor result display means having a function of displaying the block diagram and related data; input from a user Processing, and a block diagram corresponding to the monitor result display according to the control program input by the user via the input processing or information for specifying the FB program. FB program monitor processing means having a function of displaying data is provided. Execution and monitoring device for event-driven control program to. 10. An execution / monitoring device for an event-driven control program, comprising: means for clearing data on the occurrence status of an event relating to a specific control program held in said event occurrence history storage means. 11. The value of the input data of the block diagram displayed on the monitor result display means may be any one of a past value used at the time of execution of the control program or a current value held in the signal data storage unit. Means for selecting whether to display, and when the current value is selected by the selecting means, extracts the value of input data relating to the control program from the signal data storage unit and displays the value at a corresponding position on the monitor result display means 10. The apparatus for executing and monitoring an event-driven control program according to claim 9, further comprising means for executing. 12. An event-driven control program execution device for executing control by an event-driven control program, wherein the first means for storing FB programs grouped by the control content of the control program; Means for storing block diagram data corresponding to the FB, which explicitly specifies an event input / output path and a data input / output path, and an FB program stored in the first means for configuring a control program according to an event to be generated A third means for activating and executing the program; a fourth means for designating the FB program to be monitored; and a fifth means for reading the block diagram data corresponding to the designated FB from the second means and displaying the data as a block diagram on a screen. And an event generated during the execution of the control program by the third means is monitored by the monitor designated by the fourth means. -Check whether the event is an activation event of the target FB program, and if the event is an activation event, an occurrence history of an event relating to the FB program including the activation event, and the execution of the FB program activated by this event An event-driven control program execution monitor device, comprising: sixth means for storing the input / output data of the above; and seventh means for reading out the corresponding information in the sixth means in accordance with the designated contents and displaying the information at a relevant location.