JP6946804B2 - Control device, control system and control method - Google Patents

Description

The present invention relates to control devices, control systems and control methods.

There is known a control device that collects each analog input signal at a first predetermined cycle, attaches a time stamp, and stores it as sampling data (see, for example, Patent Document 1).
Patent Document 1 Japanese Unexamined Patent Publication No. 2008-20416

Conventionally, when updating the event detection conditions related to the control of the controlled device, it may not be possible to continuously monitor the events that have not changed from the current detection conditions.

In the first aspect, the control device renews the detection unit that detects the event and the current detection condition by repeatedly evaluating the predetermined detection conditions for detecting the event related to the control of the controlled device. When updating to the detection condition, the first detection condition in which the condition is not changed and the second detection condition in which the condition is changed are extracted from the current detection conditions, and the detection is performed by the first detection condition. It is provided with a condition update unit that holds information about the event to be detected and initializes the information about the event detected by the second detection condition.

The information may indicate the evaluation result of the detection condition.

The information may indicate the state of the event detected by the detection condition.

The detection unit may detect the transition of the state of the event by repeatedly evaluating the detection conditions. The control device may further include an event storage unit that stores the occurrence of the transition when the detection unit detects that the state of the event has changed.

When updating the current detection condition to a new detection condition, the condition update unit does not change the conditional expression for the detection condition including the conditional expression using the evaluation result of other detection conditions among the current detection conditions. Even in this case, if there is a change in other detection conditions, the detection condition including the conditional expression may be extracted as the second detection condition.

A detection condition storage unit having a first storage area and a second storage area capable of storing different detection conditions may be further provided. The current detection condition may be stored in one of the first storage area and the second storage area. The detection unit may refer to one of the storage areas and repeatedly evaluate the detection conditions for detecting the event. The condition update unit stores the detection condition reflecting at least a part of the new detection condition with respect to the current detection condition in the other storage area of the first storage area and the second storage area, and the detection unit. The storage area referenced by may be switched from one storage area to the other storage area.

The first storage area and the second storage area may include an effective setting area for storing a value indicating whether or not each of the plurality of detection conditions is valid. The detection unit may evaluate the detection condition in which a value indicating that the value is valid is stored in the valid setting area. The condition update unit stores a value indicating that the second detection condition is not valid in the valid setting area of the other storage area, and stores a value indicating that the first detection condition is valid, and detects the value. The storage area referenced by the unit may be switched from one storage area to the other storage area.

The condition update unit extracts a third detection condition to be deleted from the current detection condition when updating to a new detection condition, and changes the storage area referred to by the detection unit from one storage area to the other storage area. Before switching to, a value indicating that the third detection condition is not valid may be stored in the valid setting area of the other storage area.

In the second aspect, the control system includes the above-mentioned control device and a monitoring device, and the control device transmits an event detection result to the monitoring device.

In the third aspect, the control method renews the detection stage for detecting an event and the current detection condition by repeatedly evaluating a predetermined detection condition for detecting an event related to the control of the controlled device. When updating to the detection conditions, the first detection condition in which the conditions are not changed and the second detection condition in which the conditions are changed are extracted from the current detection conditions, and the first detection condition is used. It includes a stage of holding information about the event to be detected and initializing the information about the event detected by the second detection condition.

The outline of the above invention does not list all the features of the present invention. Sub-combinations of these feature groups can also be inventions.

The schematic configuration of the control system 10 in one embodiment is shown. The functional configuration of the CPU module 100 is shown schematically. An example of the event setting data set in the support / monitoring device 20 is shown. The event detection process performed by the control unit 200 is schematically shown. The data structure of the management data 500 for event detection is schematically shown. The data structure of the monitoring cycle management information 580 is shown. It is a flowchart which shows the process which the detection unit 202 detects an event in the control unit 200. It is a flowchart which shows the process of changing a detection condition. The event list information displayed by the support / monitoring device 20 is shown.

Hereinafter, the present invention will be described through embodiments of the invention, but the following embodiments do not limit the inventions that fall within the scope of the claims. Also, not all combinations of features described in the embodiments are essential to the means of solving the invention.

FIG. 1 shows a schematic configuration of the control system 10 in one embodiment. The control system 10 includes a support / monitoring device 20, a CPU module 100, an IO module 120a and an IO module 120b, and a controlled device 40a, a controlled device 40b, and a controlled device 40c.

In the present embodiment, the IO module 120a and the IO module 120b may be collectively referred to as the IO module 120. Further, the controlled device 40a, the controlled device 40b, and the controlled device 40c may be collectively referred to as the controlled device 40. The CPU module 100 is an example of a control device. The IO module 120 is an example of an input / output device that inputs / outputs data to / from the controlled device 40 under the control of the CPU module 100.

The support / monitoring device 20 is realized by a computer such as a personal computer. The support / monitoring device 20 communicates with the CPU module 100 through the network. The CPU module 100 communicates with the IO module 120a and the IO module 120b via a network or a bus. The IO module 120a is connected to the controlled device 40a. The IO module 120a is responsible for inputting and outputting data to and from the controlled device 40a. The IO module 120b is connected to the controlled device 40b and the controlled device 40c. The IO module 120b is responsible for input / output of data between each of the controlled device 40b and the controlled device 40c. The number of CPU modules 100, the number of IO modules 120, the total number of controlled devices 40, and the controlled devices 40 connected to the IO modules 120a and IO modules 120b are limited to the numbers shown in the present embodiment. Not done.

The control system 10 may be used in an industrial facility such as a factory or a plant. The control system 10 may be used as at least part of factory automation. The support / monitoring device 20, the CPU module 100, and the IO module 120 may be an industrial control system. The controlled device 40 is a device to be controlled by the support / monitoring device 20, the CPU module 100, and the IO module 120. The controlled device 40 may be a motor, an encoder, a pump, a valve, a camera, various sensors, or the like. The controlled device 40 may be, for example, an industrial machine. The CPU module 100 and the IO module 120 may be programmable logic controllers (PLCs), respectively.

The support / monitoring device 20 monitors and controls the control system 10. The support / monitoring device 20 monitors and controls the control system 10 by transmitting and receiving messages to and from the CPU module 100. The support / monitoring device 20 receives at least one status information of the controlled device 40, the CPU module 100, and the IO module 120 from the CPU module 100, and gives various control instructions to the CPU module 100 according to a process controlled by the control system 10. Is output. Further, the support / monitoring device 20 has an event setting tool function. For example, the support / monitoring device 20 sets the event detection conditions in the control system 10 based on the instruction from the user. The support / monitoring device 20 adds, updates, or deletes event detection conditions based on instructions from the user.

The IO module 120 acquires data such as information indicating the state of the controlled device 40 and information indicating the result measured by the controlled device 40 from the controlled device 40 as input data. The IO module 120 outputs the input data input from the controlled device 40 to the CPU module 100.

The CPU module 100 has a control application program for sequence control generated through a ladder diagram or the like. The control application program is an example of a control program for controlling the controlled device 40. The CPU module 100 generates control data to the controlled device 40 based on the message acquired from the support / monitoring device 20 and the input data acquired through the IO module 120, and outputs the control data to the IO module 120. The IO module 120 outputs a control signal to the controlled device 40 based on the control data acquired from the CPU module 100.

The CPU module 100 detects an event according to the event detection condition specified by the support / monitoring device 20. For example, the CPU module 100 determines that an event has occurred when the value of the variable defined by the detection condition exceeds the detection threshold value defined by the detection condition, and sets the internal event status variable to "currently occurring". Then, it is stored in the event log data and transmitted to the support / monitoring device 20. As a result, the user can recognize that the event has occurred.

When the CPU module 100 receives an instruction to update the detection conditions from the support / monitoring device 20, the CPU module 100 compares the new detection conditions with the current detection conditions, and among the current detection conditions, the detection threshold value and the like. Extract the detection conditions with changes in the conditions and the detection conditions without changes. Then, the CPU module 100 initializes the value of the event state variable corresponding to the changed detection condition, while holding the event state variable corresponding to the unchanged detection condition without initializing the value. .. As a result, it is possible to continuously detect events that have not changed from the current detection conditions.

Specifically, a case where an event in which the detection condition is not changed occurs before the detection condition update instruction will be described will be described. If all event state variables are initialized in response to the update instruction, the event state variables of the event for which the detection condition has not changed may change to "currently occurring" immediately after the update. Therefore, when the user analyzes the event log data collected by the monitoring device, whether a new event has actually occurred or has already occurred based on the event status variables before and after the update and the updated contents of the detection conditions. It becomes necessary to analyze whether or not the event was detected as a result of the detection condition update process. On the other hand, according to the CPU module 100, as described above, since the value of the event state variable of the event whose detection condition does not change is held without being initialized, the event can be continuously monitored. become.

FIG. 2 schematically shows the functional configuration of the CPU module 100. The CPU module 100 includes a control unit 200, a data memory unit 220, a work memory unit 210, an input / output unit 240, a non-volatile memory unit 280, a communication unit 270, and a bus 290. The control unit 200 has a detection unit 202 and a condition update unit 204.

The control unit 200 is connected to the work memory unit 210, the data memory unit 220, the input / output unit 240, the non-volatile memory unit 280, and the communication unit 270 via the bus 290. The control unit 200 transmits / receives data to / from the work memory unit 210, the data memory unit 220, the input / output unit 240, the non-volatile memory unit 280, and the communication unit 270 via the bus 290.

The control unit 200 may be a processor. The control unit 200 may be a microcontroller. The control unit 200 is composed of a semiconductor integrated circuit including a central processing unit (CPU), a ROM, a RAM, and the like. The non-volatile memory unit 280 stores a system program and a control application program. The CPU module 100 may be shipped with the system program written in the non-volatile memory unit 280.

The control application program is provided by the user of the control system 10. The control application program is provided from the support / monitoring device 20 to the CPU module 100 and written to the non-volatile memory unit 280 of the CPU module 100. When the CPU module 100 is started, the control unit 200 loads the system program and the control application program written in the non-volatile memory unit 280 during the boot process. The non-volatile memory unit 280 may have an application memory for storing the control application program in addition to the system memory for storing the system program.

The control unit 200 is responsible for the main processing in the CPU module 100. For example, the control unit 200 processes the input data acquired from the IO module 120 according to the control application program, and performs the process of generating the control data for the IO module 120 based on the input data. Further, the control unit 200 performs a process of determining a task of the control application program to be executed according to the system program, a process of acquiring input data from the controlled device 40, and a controlled device generated by executing the control application program. A process for outputting control data for 40 to the controlled device 40 and a process for sending and receiving a message to and from the support / monitoring device 20 are performed.

The input / output unit 240 is responsible for inputting / outputting data to / from the IO module 120. The input / output unit 240 outputs control data to the IO module 120. For example, the input / output unit 240 outputs the control data stored in the data memory unit 220 to the IO module 120. Further, the input / output unit 240 acquires input data from the IO module 120. The input data acquired from the input / output unit 240 is stored in the data memory unit 220. In this way, the data memory unit 220 stores IO data with the controlled device 40.

The control unit 200 reads the input data stored in the data memory unit 220. The control unit 200 generates control data based on the input data according to the control application program. The control unit 200 stores the generated control data in the data memory unit 220. The input / output unit 240 outputs the control data stored in the data memory unit 220 to the IO module 120.

The work memory unit 210 stores control internal variables, which are variables used by the control application program for calculation. The control unit 200 performs processing using the internal control variables stored in the work memory unit 210 according to the control application program. The internal control variable may be a variable that defines the operating parameters of the control application program. The internal control variable may be a variable that represents the state of the control application program or the like. The control unit 200 may operate according to the control application program to update the internal control variables stored in the work memory unit 210.

The communication unit 270 is responsible for communication with the support / monitoring device 20. The communication unit 270 receives the message from the support / monitoring device 20 and outputs the received message to the control unit 200. Further, the communication unit 270 receives a message to the support / monitoring device 20 from the control unit 200, and transmits the received message to the support / monitoring device 20. The message transmitted to the support / monitoring device 20 includes information indicating the occurrence state of an event related to the control of the controlled device 40.

The work memory unit 210 and the data memory unit 220 may be volatile memories. The work memory unit 210 and the data memory unit 220 may be SRAM or the like. The work memory unit 210 may have a work memory for storing the control internal variables of the control application program in addition to the work memory for storing the control internal variables for the system program.

The non-volatile memory unit 280 also stores a data file indicating detection conditions for detecting an event related to the control of the controlled device 40. The data indicating the detection conditions is provided from the support / monitoring device 20 to the CPU module 100 and stored in the non-volatile memory unit 280. The control unit 200 can update the event detection conditions according to the event setting data received from the support / monitoring device 20 while the CPU module 100 is controlling the IO module 120.

The event detection conditions include detection conditions for internal variables for control, detection conditions for input data, detection conditions for control data, and the like. The control unit 200 detects the occurrence of an event when the internal control variable satisfies the detection condition. Further, the control unit 200 detects an event when the input data satisfies the detection condition. Further, the control unit 200 detects an event when the control data satisfies the detection condition. The detection condition may include two or more of input data, control data, and control internal variables.

The data memory unit 220 also stores log data of events detected by the control unit 200. The communication unit 270 transmits the event detected by the control unit 200 to the support / monitoring device 20. For example, the control unit 200 may read the event log data stored in the data memory unit 220 and transmit the read event log data to the support / monitoring device 20 through the communication unit 270.

The operation related to updating the event detection condition in the CPU module 100 will be described. The detection unit 202 detects an event by repeatedly evaluating a predetermined detection condition for detecting an event related to the control of the controlled device 40. When updating the current detection condition to a new detection condition, the condition update unit 204 sets the first detection condition in which the condition is unchanged and the second detection condition in which the condition is changed among the current detection conditions. And extract. The condition update unit 204 holds information about the event detected by the first detection condition. On the other hand, the condition update unit 204 initializes the information regarding the event detected by the second detection condition.

As an example, the information about the event shows the evaluation result of the detection condition. For example, information about an event indicates a logical value of a conditional expression that constitutes a detection condition. When the logical value is TRUE, it indicates that the detection condition is satisfied, and when the logical value is FALSE, it indicates that the detection condition is not satisfied.

As an example, the information about the event indicates the state of the event detected by the detection condition. For example, information about an event indicates whether or not an event has occurred. Specifically, the information about the event indicates that an event has occurred when the logical value of the conditional expression constituting the detection condition is TRUE, and when the logical value of the conditional expression constituting the detection condition is FALSE. Indicates that no event has occurred.

The detection unit 202 detects the transition of the event state by repeatedly evaluating the detection conditions. When the detection unit 202 detects that the state of the event has changed, the data memory unit 220 stores that the transition has occurred. The data memory unit 220 is an example of an event storage unit.

When updating the current detection condition to a new detection condition, the condition update unit 204 changes the conditional expression for the detection condition including the conditional expression using the evaluation result of the other detection conditions among the current detection conditions. Even if there is no change, if there is a change in the other detection conditions, the detection condition including the conditional expression is extracted as the second detection condition.

The detection conditions are stored in at least one of the data memory unit 220, the work memory unit 210, and the non-volatile memory unit 280. In the present embodiment, the data memory unit 220 will be described as an example of the detection condition storage unit.

The data memory unit 220 has a first storage area and a second storage area that can store different detection conditions. The current detection conditions are stored in one of the first storage area and the second storage area, and the detection unit 202 refers to the one storage area and detects an event. Evaluate the condition repeatedly. Here, when updating the detection conditions, the condition update unit 204 sets the detection conditions that reflect at least a part of the new detection conditions with respect to the current detection conditions in the first storage area and the second storage area. Of these, the storage area is stored in the other storage area, and the storage area referred to by the detection unit 202 is switched from one storage area to the other storage area.

Specifically, the first storage area and the second storage area include an effective setting area for storing a value indicating whether or not each of the plurality of detection conditions is valid, and the detection unit 202 sets the valid setting. Evaluate the detection conditions in which a value indicating that the area is valid is stored. The detection unit 202 does not evaluate the detection condition in which a value indicating invalidity is stored in the valid setting area. Here, when updating to a new detection condition, the condition update unit 204 stores a value indicating that the second detection condition is not valid in the valid setting area of the other storage area, and also stores the first value. Store a value indicating that the detection condition is valid. Then, the condition update unit 204 switches the storage area referred to by the detection unit 202 from one storage area to the other storage area. As a result, it is possible to stop the event detection operation under the changed detection condition at once while continuing the event detection operation under the unchanged detection condition.

The condition update unit 204 extracts a third detection condition that is deleted from the current detection condition when updating to a new detection condition. Then, before switching the storage area referred to by the detection unit 202 from one storage area to the other storage area, the condition update unit 204 does not have the third detection condition valid in the valid setting area of the other storage area. Store the value indicating that. As a result, while continuing the event detection operation based on the detection condition that has not changed, the event detection operation based on the deleted detection condition and the event detection operation based on the changed detection condition can be stopped at once. can.

FIG. 3 shows an example of event setting data set in the support / monitoring device 20. The event setting data includes event number, event name, detection condition, and cycle information. The support / monitoring device 20 displays the detection condition data in a table format so that the user can edit it.

The "event number" is a value that identifies an event. The "event name" indicates the name given to the event. The "detection condition" is a character string of detection conditions including one or more conditional expressions. For example, detection conditions include one or more equations, inequalities or logical expressions.

As shown in the figure, the event detection condition is set by one or more conditional expressions using the event detection variable. The detection conditions shown in event numbers 1 to 3 are represented by a single conditional expression using a single event detection variable. The detection conditions shown in event numbers 4 to 5 are represented by conditional expressions using the evaluation results of other detection conditions. The evaluation result of each conditional expression is obtained as a logical value of true (TRUE) or false (FALSE).

For example, the detection condition of event number 1 includes one conditional expression "Var01 = FALSE". This detection condition indicates that an event with the event name "event A" has occurred when the value of the event detection variable Var01 is FALSE. Var01 indicates variables such as input data and control data stored in the data memory unit 220, or internal control variables stored in the work memory unit 210. Further, the detection condition of event number 4 is given by AND combination of the evaluation result of the detection condition of event number 1 and the evaluation result of the detection condition of event number 2. This detection condition indicates that an event with the event name "event D" has occurred when both the conditional expression of the event number 1 and the conditional expression of the event number 2 are TRUE.

"Period" indicates an event detection cycle. Each event can be detected at different cycles.

In the support / monitoring device 20, the user edits the event setting data through the event setting tool function of the support / monitoring device 20. The support / monitoring device 20 transmits the event setting data including the event number, the detection condition, and the cycle edited by the user to the CPU module 100.

In the CPU module 100, the address information indicating the address of the event detection variable in the work memory unit 210 and the data memory unit 220 is stored in the non-volatile memory unit 280. The detection unit 202 acquires the value of the event detection variable with reference to the address indicated by the address information, and evaluates the conditional expression included in each detection condition.

FIG. 4 schematically shows an event detection process performed by the control unit 200.

The data memory unit 220 stores the current values of the input data and the control data. Further, the work memory unit 210 stores the current value of the control variable. In the process 440, the detection unit 202 applies the event detection value specified by the event setting data among the values stored in the data memory unit 220 and the work memory unit 210 to the conditional expression included in the detection condition. Then, by evaluating the conditional expression, the evaluation result of this time indicating the event state is obtained. The detection unit 202 performs a process 450 for comparing the current evaluation result obtained by the process 440 with the previous evaluation result obtained in the previous evaluation. When the current evaluation result and the previous evaluation result differ depending on the process 450, the detection unit 202 generates an event log 460 and stores it in the data memory unit 220. For example, when the previous evaluation result is FALSE and the current evaluation result is TRUE, the detection unit 202 displays an event log 460 including an event number, a current time, and an event state indicating "occurrence". Generate and store in the data memory unit 220. Further, when the previous evaluation result is TRUE and the current evaluation result is FALSE, the detection unit 202 includes an event number, a current time, and an event log 460 indicating "not occurring". Is generated and stored in the data memory unit 220.

In the present embodiment, an operation in which the detection unit 202 detects an event based on the detection conditions and an operation in which the condition update unit 204 updates the detection conditions will be mainly described. Here, "updating the detection condition" means, for example, changing or deleting at least one detection condition among a plurality of detection conditions corresponding to a plurality of event numbers, or corresponding to a new event number. This refers to the case where detection conditions are added. When the user changes the detection conditions in the support / monitoring device 20, the support / monitoring device 20 transmits the event setting data of all the events and the message instructing the update of the detection conditions to the CPU module 100.

FIG. 5 schematically shows the data structure of the management data 500 for event detection. The management data 500 is stored in the data memory unit 220 or the work memory unit 210.

The management data 500 includes a monitoring event management area number 501, a monitoring event management area 510, a monitoring event management area 511, and an event detection condition management data table 520. As an example, the management data 500 has 1024 event detection condition management data tables 520.

The value of the monitoring event management area number 501 indicates a monitoring event management area in which the data used by the detection unit 202 for event detection is stored. When the value of the monitoring event management area number 501 is 0, the detection unit 202 detects an event using the data stored in the monitoring event management area 510. When the value of the monitoring event management area number 501 is 1, the detection unit 202 detects an event using the data stored in the monitoring event management area 511.

The monitoring event management area 510 includes the number of event detection condition management 530 and the monitoring event information 540. The event detection condition management number 530 stores a value indicating the number N of event detection conditions. The monitoring event management area 510 includes the number of monitoring event information 540 indicated by the event detection condition management number 530. The monitoring event information 540 corresponds to a different event. Since the monitoring event management area 511 has the same data structure as the monitoring event management area 510, the details of the data structure will be omitted.

The monitoring event information 540-1 has a monitoring valid flag 570 and an event detection condition management data table number 571. The monitoring enable flag 570 indicates whether to enable or disable the detection of the corresponding event. The event detection condition management data table number 571 indicates the number of the event detection condition management data table 520, which will be described later. When the value of the monitoring valid flag 570 is 1, which indicates "valid", the detection unit 202 detects the corresponding event. When the value of the monitoring enable flag 570 is 0 indicating "invalid", the detection unit 202 does not detect the corresponding event. Since the monitoring event information 540-2 to the monitoring event information 540-N have the same data structure as the monitoring event information 540-1, the details of the data structure will be omitted.

The event detection condition management data table 520-1 contains data registration flag 551, event number 552, event type 553, event state 554, variable value 555 at the time of event occurrence / recovery, logical number 556, and logical data. It has 560 and.

The data registration flag 551 indicates whether or not an event is registered in the corresponding storage area. When the value of the data registration flag 551 is 1, it indicates that the event is registered in the corresponding storage area. When the value of the data registration flag 551 is 0, it indicates that no event has been registered in the corresponding storage area. That is, it indicates that this storage area is free.

The event number is stored in the event number 552. The event number 552 may store the event number included in the event setting data received from the support / monitoring device 20.

Event type 553 indicates an operator for the operand that constitutes the conditional expression. For example, event type 553 indicates information that identifies relational operators such as "=", ">", "<", "≧", and "≦" and logical operators such as "AND" and "OR". ..

The event state 554 indicates whether or not an event has occurred. When the value of the event state 554 is 1, it indicates that an event has occurred. When the value of the event state 554 is 0, it indicates that no event has occurred. The variable value 555 at the time of event occurrence / recovery stores the value of the variable included in the detection condition when the event occurs. For example, the value of Var01 included in the detection condition corresponding to the event number 1 in FIG. 3 is stored.

In the logical number 556, the number n of the operands used in the conditional expression is stored. Information indicating the operand used in the conditional expression is stored in the logical data 560. The information stored in the logical data 560 includes numerical values such as detection thresholds used in conditional expressions, addresses in which variables are stored, event numbers, and the like. For example, in the logical data 560, the address where the variable of "Var01" included in the conditional expression of the event number 1 is stored and the value of "FALSE" are stored. Since the event detection condition management data table 520-2 to the event detection condition management data table 520-1023 have the same data structure as the event detection condition management data table 520-1, the details of the data structure will be described. Omit.

The single event detection condition may be set by a combination of a plurality of event detection condition management data tables 520. For example, the detection condition of the event number 5 in FIG. 3 may be set by the two event detection condition management data tables 520. As an example, the detection condition of the event number 5 in FIG. 3 is generated as the first event detection condition management data table 520 representing the OR operation of the event number 1 and the event number 2, and the event detection condition management data table 520 is generated. A second event detection condition management data table 520 representing an AND operation between the event number assigned to and the event number 2 may be generated. In this case, the event of event number 5 in FIG. 3 is represented by the evaluation result of the detection condition in the second event detection condition management data table 520.

FIG. 6 shows the data structure of the monitoring cycle management information 580. The monitoring cycle management information 580 includes the monitoring cycle management number 581 and the cycle information 582. In the monitoring cycle management number 581, a value indicating the number M of the cycle information is stored. The monitoring cycle management information 580 includes the number of cycle information 582 indicated by the monitoring cycle management number 581.

The cycle information 582-1 includes a cycle 590, an event management number 591, and an event number 592. In the cycle 590, a numerical value indicating the cycle is stored. The event management number 591 indicates the number m of the event for which the event is detected in the cycle indicated by the cycle 590. The event number 592 stores the event numbers of the number of events indicated by the event management number 591.

Since the periodic information 582-2-M has the same data structure as the periodic information 582-1, the details of the data structure will be omitted. Further, the information of the detection cycle may be managed by a data structure different from the data structure shown in FIG. For example, the information of the detection cycle may be managed for each event in the event detection condition management data table 520.

FIG. 7 is a flowchart showing a process in which the detection unit 202 detects an event in the control unit 200. In S600, the detection unit 202 acquires the current date and time information. Subsequently, in S602, the detection unit 202 selects the event to be detected. Specifically, the detection unit 202 refers to the monitoring cycle management information 580 and specifies the event number in which the event should be detected in the current tact.

Subsequently, the event detection loop processing in S604 to S620 is performed. In this loop processing, different event detection conditions are selected for each loop from the events selected in S602.

In S606, the detection unit 202 determines whether or not the event detection of the selected event is effectively set. The detection unit 202 makes a determination in S606 with reference to the value of the monitoring valid flag 570 of the monitoring event information 540. If the detection condition is invalid, the process proceeds to the processing of the next event in the loop processing of "event detection". If the detection condition is valid, the process proceeds to S610.

In S610, the detection unit 202 evaluates the conditional expression included in the detection condition and calculates the evaluation result. The detection unit 202 calculates the evaluation result of the detection condition with reference to the event detection condition management data table 520.

Subsequently, in S612, the detection unit 202 reads the current value stored in the event state 554 of the event detection condition management data table 520, and stores the evaluation result obtained in S610 in the event state 554.

In S614, the detection unit 202 determines whether or not the event state has changed. Specifically, the detection unit 202 determines that the event state has changed when the value read from the event state 554 in S612 and the evaluation result obtained in S610 are different. Further, the detection unit 202 determines that the event state has not changed when the value read from the event state 554 in S612 and the evaluation result obtained in S610 match. If the event state has not changed, the process proceeds to the processing of the next event in the loop processing of "event detection". If the event state changes, the process proceeds to S616.

In S616, the detection unit 202 stores the value of the variable used in the conditional expression included in the corresponding detection condition in the variable value 555 at the time of event occurrence / recovery. Subsequently, the detection unit 202 generates event log data including the event number, the event status, and the current date and time information. The state of the event indicates "occurred" or "not occurred". If the evaluation result obtained by S610 is TRUE, it indicates that an event has occurred. When the evaluation result obtained by S610 is FALSE, it indicates that the event that has occurred has ended. For example, when the evaluation result is FALSE, it indicates that the abnormal event has been recovered.

FIG. 8 is a flowchart showing a process of changing the detection condition. The processing of this flowchart is started when the CPU module 100 receives from the support / monitoring device 20 a message instructing to update new event setting data and detection conditions. Here, in the management data 500, it is assumed that the information based on the current event setting data is stored in the monitoring event management area 510 and the event detection condition management data table 520. That is, it is assumed that the detection unit 202 has performed the event detection process according to the information stored in the monitoring event management area 510 until now. Further, in order to update the information stored in the monitoring event management area 510, it is assumed that the same information as the monitoring event management area 510 is stored in the monitoring event management area 511.

In S802, the condition update unit 204 collates the current event setting data with the newly received event setting data, and identifies the deletion target, the addition target, the change target, and the event not to be changed. Specifically, the condition update unit 204 generates a deletion event number list by extracting event numbers that are not included in the new event setting data from the event numbers included in the current event setting data. Further, the condition update unit 204 generates an additional event number list by extracting the event numbers not included in the current event setting data from the event numbers included in the new event setting data. Here, when the same event number is included in both the current event setting data and the new event setting data, the condition update unit 204 sets the conditional expression specified in the new event setting data and the current event setting data. If the conditional expression does not match, the event number is added to the event number list to be changed. On the other hand, if the conditional expressions match, the conditional update unit 204 adds the event number to the non-changeable event number list.

Further, among the event numbers included in the non-change target event number list, when the conditional expression constituting the corresponding detection condition includes another event number, the condition update unit 204 indicates that the other event number is the change target event number. Determine if it is included in the list. When another event number is included in the change target event number list, the condition update unit 204 deletes it from the change target event number list and adds it to the change target event number list. For example, if there is no change in the conditional expression "event number 1 AND event number 2" of the detection condition corresponding to the event number 4 in FIG. 3, and there is a change in the conditional expression of the event number 1, the condition update unit 204 Deletes the event number 4 from the non-changeable event number list and adds the event number 4 to the changeable event number list.

When the processing of S802 is completed, it is determined in S803 whether or not the processing of S802 is successful. If unsuccessful, the process proceeds to S814, and if successful, the process proceeds to S804.

In S804, the condition update unit 204 performs a process of stopping the monitoring of the change target event and the deletion target event. Specifically, the condition update unit 204 sets the event number stored in the event detection condition management data table 520 indicated by the event detection condition management data table number 571 for each monitoring event information 540 in the monitoring event management area 511. When it is included in the change target event number list or the deletion target event number list, the value of the monitoring valid flag 570 of the monitoring event information 540 is changed to 0.

Then, the condition update unit 204 changes the value of the monitoring event management area number 501 to a value indicating the monitoring event management area 511. After the completion of this process, the detection unit 202 detects the event based on the information stored in the monitoring event management area 511. Therefore, the event corresponding to the event number included in the change target event number list and the deletion target event number list. Will not be detected. On the other hand, the event corresponding to the event number included in the non-changeable event number list is continuously detected.

When the processing of S804 is completed, it is determined in S805 whether or not the processing of S804 is successful. If unsuccessful, the process proceeds to S814, and if successful, the process proceeds to S806.

In S806, the condition update unit 204 deletes the monitoring cycle information of the event to be deleted and registers the monitoring cycle information of the event to be added. Specifically, the condition update unit 204 deletes the event number 592 that stores the value corresponding to the event number included in the deletion target event number list in the monitoring cycle management information 580. Further, the condition update unit 204 adds each event number to the cycle information corresponding to the cycle specified in the new event setting data for each event number included in the addition target event number list in the monitoring cycle management information 580. do.

When the processing of S806 is completed, it is determined in S807 whether or not the processing of S806 is successful. If unsuccessful, the process proceeds to S814, and if successful, the process proceeds to S808.

In S808, the condition update unit 204 adds and updates event setting information to the event detection condition management data table 520 for the deletion target event, the addition target event, and the change target event. Specifically, the condition update unit 204 changes the data registration flag 551 of the event detection condition management data table 520 that stores the event numbers included in the deletion target event number list to 0.

Further, the condition update unit 204 initializes the event detection condition management data table 520 that stores the event numbers included in the change target event number list. Specifically, the condition update unit 204 sets the value of the event state 554 to 0 and sets the value of the variable value 555 at the time of event occurrence / recovery to NULL. Further, the logical number 556, the logical data 560, and the event type 553 are changed according to the conditional expression constituting the new detection condition specified by the new event setting data.

Further, the condition update unit 204 adds the event setting information to the event detection condition management data table 520 based on the event setting data corresponding to the event number included in the event number list to be added. Specifically, the condition update unit 204 searches the event detection condition management data table 520 in which the value of the data registration flag 551 is 0, and in the searched event detection condition management data table 520, the value of the data registration flag 551. Is set to 1, the event number of the event number list to be added is stored in the event number 552, the value of the event state 554 is set to 0, and the value of the variable value 555 at the time of event occurrence / recovery is set to NULL. Further, the logical number 556, the logical data 560, and the event type 553 are set according to the conditional expression that constitutes the corresponding detection condition specified by the new event setting data.

In S810, the condition update unit 204 adds and updates the monitoring event information 540 in the monitoring event management area 510 with respect to the addition target event and the change target event. Specifically, the condition update unit 204 stores the same information as the monitoring event management area 511 in the monitoring event management area 510, and changes the information about the event to be changed in the monitoring event information 540 in the monitoring event management area 510. And add the event to be added. More specifically, among the monitoring event information 540 in the monitoring event management area 510, the monitoring event information 540 whose corresponding event number is included in the change target event number list is selected, and the monitoring valid flag of the monitoring event information 540 is selected. Change the value of 570 to 1.

Further, the condition update unit 204 adds the number of the event detection condition management data table 520 to which the new event detection condition is added in S808 and the information in which the value of the monitoring valid flag 570 is 1 to the monitoring event information 540. ..

When the processing of S810 is completed, it is determined in S811 whether or not the processing of S810 is successful. If unsuccessful, the process proceeds to S814, and if successful, the process proceeds to S812.

In S812, the condition update unit 204 sets the management data 500 so as to start monitoring based on the updated and added monitoring event information. Specifically, the condition update unit 204 changes the value of the monitoring event management area number 501 to a value indicating the monitoring event management area 510. After the completion of this process, the detection unit 202 detects the event based on the information stored in the monitoring event management area 510, and therefore corresponds to the event number included in either the change target event number list or the deletion target event number list. The detection of the event to be performed is started. On the other hand, the detection of the event corresponding to the event number included in the non-changeable event number list is still continued.

When the processing of S812 is completed, it is determined in S813 whether or not the processing of S812 is successful. If unsuccessful, the process proceeds to S814, and if successful, the flowchart processing ends. In S814, after performing error processing for the processing that caused the failure, the processing of the flowchart is terminated.

FIG. 9 shows event list information displayed by the support / monitoring device 20. The support / monitoring device 20 receives the event log data from the CPU module 100 as a message. The support / monitoring device 20 displays a list of the set event log data in a table format. The support / monitoring device 20 displays the "event name", "occurrence / recovery", and "time" based on the event log data.

The event name is an event name corresponding to the event number in which the event occurrence state has changed. The support / monitoring device 20 displays the event name corresponding to the event number included in the event log data.

"Occurrence / recovery" indicates the type of change in the event occurrence status. "Occurrence" is displayed when the state changes from the state where no event has occurred to the state where the event has newly occurred, and "Recovery" when the state has changed from the state where the event has occurred to the state where the event has not occurred. Is displayed. The support / monitoring device 20 displays "occurrence" when the event status included in the event log data is "occurred", and displays "recovery" when the event status included in the event log data is "not occurred". do.

“Time” indicates the time when a change in the event occurrence state is detected. The support / monitoring device 20 displays the time included in the event log data.

In relation to FIG. 9, it is assumed that after the time "03:21:22 342", the user performs an operation of changing only the conditional expression of "event D" through the event setting tool of the support / monitoring device 20. In this case, the support / monitoring device 20 transmits event setting data including detection conditions for all events to the CPU module 100. In the CPU module 100, the condition update unit 204 initializes the value of the event state 554 of the event detection condition management data table 520 corresponding to the "event D" in the management data 500, while "event B" and "event C". And, in the event state 554 corresponding to "event E", a value 1 indicating "occurring" is held. Further, in the event state 554 corresponding to "event A", a value 0 indicating "not occurred" is held.

As a result, it can be determined that the event states of "event B", "event C", and "event E" have not changed from "currently occurring" immediately after the detection condition is updated by the event setting tool. Therefore, immediately after the event detection condition is changed, the "occurrence" of the "event B", "event C", and "event E" events is not notified. In this way, according to the control system 10, even when a part of the detection conditions is updated, for example, it is possible to perform consistent event detection for the events for which the detection conditions are not changed. Therefore, as described above, it is possible to reduce the time and effort for the user to analyze the event log as the detection condition is updated.

As described above, according to the CPU module 100, since the value of the event state of the event for which the detection condition is not changed is held without being initialized, the event can be continuously monitored.

The control system 10 in one embodiment is a PLC system using a PLC as a control device. In other forms, the control system can be a distributed control system (DCS).

Although the present invention has been described above using the embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments. It will be apparent to those skilled in the art that various changes or improvements can be made to the above embodiments. It is clear from the description of the claims that such modified or improved forms may also be included in the technical scope of the present invention.

The execution order of each process such as operation, procedure, step, and step in the device, system, program, and method shown in the claims, the specification, and the drawing is particularly "before" and "prior to". It should be noted that it can be realized in any order unless the output of the previous process is used in the subsequent process. Even if the scope of claims, the specification, and the operation flow in the drawings are explained using "first", "next", etc. for convenience, it means that it is essential to carry out in this order. It's not a thing.

10 Control system 20 Support / monitoring device 40 Controlled device 100 CPU module 120 IO module 200 Control unit 202 Detection unit 204 Condition update unit 210 Work memory unit 220 Data memory unit 280 Non-volatile memory unit 240 Input / output unit 270 Communication unit 290 Bus 440, 450 Processing 460 Event log 500 Management data 501 Monitoring event management area number 510 Monitoring event management area 511 Monitoring event management area 520 Event detection condition management data table 530 Event detection condition management number 540 Monitoring event information 551 Data registration flag 552 Event number 553 Event type 554 Event status 555 Variable value at the time of event occurrence / recovery 556 Logical number 560 Logical data 570 Monitoring valid flag 571 Event detection condition management data Table number 580 Monitoring cycle management information 581 Monitoring cycle management number 582 Cycle information 590 Cycle 591 Event Number of management 592 Event number

Claims (10)

A detection unit that detects an event by repeatedly evaluating predetermined detection conditions for detecting an event related to control of a controlled device, and a detection unit that detects the event.
When updating the current detection condition to a new detection condition, the first detection condition in which the condition is not changed and the second detection condition in which the condition is changed are extracted from the current detection conditions. A control device including a condition updating unit that holds information about the event detected by the first detection condition and initializes information about the event detected by the second detection condition. The control device according to claim 1, wherein the information indicates an evaluation result of the detection conditions. The control device according to claim 1 or 2, wherein the information indicates a state of the event detected by the detection conditions. The detection unit detects the transition of the state of the event by repeatedly evaluating the detection conditions.
The control device is
The control device according to claim 3, further comprising an event storage unit that stores the occurrence of the transition when the detection unit detects that the state of the event has changed. When updating the current detection condition to a new detection condition, the condition update unit describes the conditional expression for the detection condition including the conditional expression using the evaluation result of the other detection condition among the current detection conditions. If there is a change in the other detection conditions even if there is no change in, any one of claims 1 to 4 for extracting the detection condition including the conditional expression as the second detection condition. The control device described in. Further, a detection condition storage unit having a first storage area and a second storage area capable of storing different detection conditions is provided.
The current detection condition is stored in one of the first storage area and the second storage area.
The detection unit repeatedly evaluates the detection conditions for detecting the event with reference to the one storage area.
The condition update unit applies a detection condition that reflects at least a part of the new detection condition to the current detection condition to the other storage area of the first storage area and the second storage area. The control device according to any one of claims 1 to 5, which is stored and the storage area referred to by the detection unit is switched from the one storage area to the other storage area. The first storage area and the second storage area include an effective setting area for storing a value indicating whether or not each of the plurality of detection conditions is valid.
The detection unit evaluates the detection condition in which a value indicating that the value is valid is stored in the valid setting area.
The condition update unit
In the effective setting area of the other storage area, a value indicating that the second detection condition is not valid is stored, and a value indicating that the first detection condition is valid is stored.
The control device according to claim 6, wherein the storage area referred to by the detection unit is switched from the one storage area to the other storage area. The condition update unit
When updating to the new detection condition, a third detection condition to be deleted from the current detection condition is extracted.
Before switching the storage area referred to by the detection unit from the one storage area to the other storage area, it is shown that the third detection condition is not valid in the effective setting area of the other storage area. The control device according to claim 7, wherein the value is stored. The control device according to any one of claims 1 to 7.
Equipped with a monitoring device
The control device is a control system that transmits the detection result of the event to the monitoring device. A detection stage for detecting an event by repeatedly evaluating a predetermined detection condition for detecting an event related to control of a controlled device, and a detection stage for detecting the event.
When updating the current detection condition to a new detection condition, the first detection condition in which the condition is not changed and the second detection condition in which the condition is changed are extracted from the current detection conditions. Stages and
A control method including a step of holding information about the event detected by the first detection condition and initializing the information about the event detected by the second detection condition.

Images