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

Abstract

PROBLEM TO BE SOLVED: To continuously monitor an event which has not changed from the current detection condition when updating the detection condition of an event related to the control of a controlled device. SOLUTION: A control device repeatedly evaluates a predetermined detection condition for detecting an event related to control of a controlled device, thereby detecting an event and a new detection condition for the current detection condition. When updating to, the first detection condition with no change in the condition and the second detection condition with the change in the condition are extracted from the current detection conditions, and the event detected by the first detection condition. It is provided with a condition update unit that holds information about the event and initializes the information about the event detected by the second detection condition. [Selection diagram] FIG. 8

Description

  The present invention relates to a control device, a control system, and a control method.

There is known a control device that collects each analog input signal at a first predetermined period, adds a time stamp, and stores it as sampling data (see, for example, Patent Document 1).
Japanese Patent Application Laid-Open No. 2008-204166

  Conventionally, when an event detection condition related to control of a controlled device is updated, an event that is not changed from the current detection condition may not be continuously monitored.

  In the first aspect, the control device repeatedly evaluates a predetermined detection condition for detecting an event related to control of the controlled device, thereby detecting a detection unit for detecting an event and a new detection condition. 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 are detected based on the first detection condition. And a condition update unit that initializes information related to the event detected by the second detection condition.

  The information may indicate an 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 event state by repeatedly evaluating the detection condition. The control device may further include an event storage unit that stores the occurrence of the transition when the detection unit detects the transition of the event state.

  When the current detection condition is updated 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 the other detection condition among the current detection conditions. Even in this case, when other detection conditions are changed, the detection condition including the conditional expression may be extracted as the second detection condition.

  You may further provide the detection condition memory | storage part which has the 1st storage area which can memorize | store a mutually different detection condition, and a 2nd storage area. The current detection condition may be stored in one of the first storage area and the second storage area. The detection unit may repeatedly evaluate the detection condition for detecting the event with reference to one storage area. The condition update unit stores a detection condition that reflects 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 section 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 that stores a value indicating whether each of the plurality of detection conditions is effective. The detection unit may evaluate a detection condition in which a value indicating that the effective setting area is effective is stored. 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 second detection condition. The storage area referenced by the unit may be switched from one storage area to the other storage area.

  When updating to a new detection condition, the condition update unit extracts a third detection condition that is deleted from the current 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, a control system includes the above-described 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 includes a detection stage for detecting an event by repeatedly evaluating a predetermined detection condition for detecting an event related to control of the controlled device, and a new detection condition. When updating to the detection condition, a step of extracting a first detection condition in which the condition is not changed and a second detection condition in which the condition is changed among the current detection conditions, and the first detection condition Holding information related to the detected event, and initializing information related to the event detected by the second detection condition.

  The summary of the invention does not enumerate all the features of the present invention. In addition, a sub-combination of these feature groups can also be an invention.

1 shows a schematic configuration of a control system 10 according to an embodiment. 1 schematically shows a functional configuration of a CPU module 100. An example of event setting data set in the support / monitoring device 20 is shown. The event detection process performed in the control part 200 is shown schematically. The data structure of the management data 500 for event detection is shown typically. The data structure of the monitoring cycle management information 580 is shown. 5 is a flowchart illustrating processing in which a detection unit 202 detects an event in the control unit 200. It is a flowchart which shows the process which changes detection conditions. 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 invention according to the claims. In addition, not all the combinations of features described in the embodiments are essential for the solving means of the invention.

  FIG. 1 shows a schematic configuration of a control system 10 according to an embodiment. The control system 10 includes a support / monitoring device 20, a CPU module 100, an IO module 120a and an IO module 120b, 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. In addition, 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 and outputs data to and from the controlled device 40 according to control by 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 a network. The CPU module 100 communicates with the IO module 120a and the IO module 120b through a network or a bus. The IO module 120a is connected to the controlled device 40a. The IO module 120a is responsible for data input / output with 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 data input / output between 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 120b are limited to the numbers shown in this embodiment. Not.

  The control system 10 may be used in industrial facilities such as factories and plants. 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 an industrial machine, for example. Each of the CPU module 100 and the IO module 120 may be a programmable logic controller (PLC).

  The support / monitoring device 20 performs monitoring control of 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 performs various control instructions to the CPU module 100 according to the process controlled by the control system 10. Is output. The support / monitoring apparatus 20 has an event setting tool function. For example, the support / monitoring device 20 sets an event detection condition in the control system 10 based on an instruction from the user. The support / monitoring device 20 adds, updates, or deletes an event detection condition based on an instruction from the user.

  The IO module 120 acquires data such as information indicating the state of the controlled device 40 and information indicating a 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 for 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 determined by the detection condition exceeds the detection threshold value determined by the detection condition, and sets the internal event state variable to “occurring”. And stored in the event log data and transmitted to the support / monitoring device 20. Thereby, the user can recognize that the event has occurred.

  When the CPU module 100 receives an instruction to update the detection condition from the support / monitoring device 20, the CPU module 100 compares the new detection condition with the current detection condition, and sets the detection threshold value and the like among the current detection conditions. A detection condition with a change in the condition and a detection condition without a change are extracted. Then, the CPU module 100 initializes the value of the event state variable corresponding to the detection condition with the change, and holds the event state variable corresponding to the detection condition not changed without initializing the value. . Thereby, the event which has not changed from the present detection conditions can be detected continuously.

  Specifically, a case where an event with no detection condition change has occurred before the detection condition update instruction will be described. If all event state variables are initialized according to the update instruction, the event state variable of an event whose detection condition is not changed can change to “being generated” immediately after the update. Therefore, when analyzing the event log data collected by the monitoring device, the user has already generated whether an event has actually occurred based on the event state variables before and after the update, the update contents of the detection conditions, etc. It is necessary to analyze whether the detected event is detected with the update process of the detection condition. On the other hand, according to the CPU module 100, as described above, since the event state variable value of an event whose detection condition is not changed is held without being initialized, the event can be continuously monitored. become.

  FIG. 2 schematically shows a 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 nonvolatile memory unit 280, a communication unit 270, and a bus 290. The control unit 200 includes 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 nonvolatile memory unit 280, and the communication unit 270 through 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 nonvolatile memory unit 280, and the communication unit 270 through the bus 290.

  The control unit 200 may be a processor. The control unit 200 may be a microcontroller. The control unit 200 includes a semiconductor integrated circuit including a central processing unit (CPU), ROM, RAM, and the like. The nonvolatile 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 is written in the nonvolatile memory unit 280 of the CPU module 100. When the CPU module 100 is activated, the control unit 200 loads the system program and the control application program written in the nonvolatile memory unit 280 during the boot process. Note that the nonvolatile memory unit 280 may include an application memory for storing a control application program in addition to the system memory for storing a system program.

  The control unit 200 performs main processing in the CPU module 100. For example, the control unit 200 performs processing of input data acquired from the IO module 120 and processing of generating control data for the IO module 120 based on the input data, according to the control application program. In addition, the control unit 200 determines a control application program task to be executed according to a system program, acquires 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 transmitting / receiving a message to / from the support / monitoring apparatus 20 are performed.

  The input / output unit 240 performs data input / output with 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. Thus, the data memory unit 220 stores IO data with the controlled device 40.

  The control unit 200 reads 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 that are variables used by the control application program for calculation. The control unit 200 performs processing using the control internal variables stored in the work memory unit 210 in accordance with the control application program. The control internal variable may be a variable that defines an operation parameter of the control application program. The internal variable for control may be a variable representing the state of the control application program. The control unit 200 may operate according to the control application program and update the control internal variable 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 a message from the support / monitoring apparatus 20 and outputs the received message to the control unit 200. In addition, 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 an occurrence state of an event related to 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 include a work memory for storing control internal variables for the control application program, in addition to the work memory for storing 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. Data indicating the detection condition is provided from the support / monitoring device 20 to the CPU module 100 and stored in the nonvolatile memory unit 280. The control unit 200 can update the event detection condition 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 control internal variables, 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 control internal variable satisfies the detection condition. The control unit 200 detects an event when the input data satisfies the detection condition. In addition, the control unit 200 detects an event when the control data satisfies a 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 apparatus 20 through the communication unit 270.

  An operation related to the update of 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 the current detection condition is updated to a new detection condition, the condition update unit 204 includes a first detection condition in which the condition is not changed and a second detection condition in which the condition is changed among the current detection conditions. And extract. The condition update unit 204 holds information related to the event detected by the first detection condition. On the other hand, the condition update unit 204 initializes information related to the event detected by the second detection condition.

  As an example, the information regarding the event indicates the evaluation result of the detection condition. For example, the information regarding the event indicates a logical value of a conditional expression that constitutes the 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 regarding the event indicates the state of the event detected by the detection condition. For example, the information regarding the event indicates whether or not the event has occurred. Specifically, the information regarding the event indicates that an event has occurred when the logical value of the conditional expression constituting the detection condition is TRUE, and indicates that the logical value of the conditional expression constituting the detection condition is FALSE. Indicates that no event has occurred.

  The detection unit 202 detects transition of the event state by repeatedly evaluating the detection condition. When the detection unit 202 detects that the event state has transitioned, 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 the current detection condition is updated to a new detection condition, the condition update unit 204 changes the detection condition including the conditional expression using the evaluation result of the other detection condition to the conditional expression. Even if there is not, 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 condition is stored in at least one of the data memory unit 220, the work memory unit 210, and the nonvolatile memory unit 280. In the present embodiment, the data memory unit 220 will be described as an example of a detection condition storage unit.

  The data memory unit 220 includes a first storage area and a second storage area that can store different detection conditions. The current detection condition is 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 for detecting an event. Evaluate the condition repeatedly. Here, when updating the detection condition, the condition updating unit 204 sets the detection condition reflecting at least a part of the new detection condition with respect to the current detection condition to the first storage area and the second 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 that stores a value indicating whether or not each of the plurality of detection conditions is valid. A detection condition in which a value indicating that the area is valid is stored is evaluated. The detection unit 202 does not evaluate a 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 updating unit 204 stores a value indicating that the second detection condition is not valid in the valid setting area of the other storage area, A value indicating that the detection condition is valid is stored. 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, the event detection operation based on the detection condition having a change can be stopped in a batch while continuing the event detection operation based on the detection condition having no change.

  When updating to a new detection condition, the condition update unit 204 extracts a third detection condition that is deleted from the current detection condition. Then, the condition update unit 204 determines that the third detection condition is not valid in the valid setting area of the other storage area before switching the storage area referred to by the detection unit 202 from one storage area to the other storage area. A value indicating that is stored. As a result, the event detection operation based on the detection condition to be deleted and the event detection operation based on the detection condition having a change can be stopped in a lump while continuing the event detection operation based on the detection condition that does not change. it can.

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

  “Event number” is a value for identifying an event. “Event name” indicates a name given to the event. “Detection condition” is a description of a detection condition including one or more conditional expressions in a character string. For example, the detection condition includes 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 event detection variables. The detection conditions indicated by 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 expressed 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 or 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 Var01 that is an event detection variable is FALSE. Var 01 indicates a variable such as input data and control data stored in the data memory unit 220, or a control internal variable stored in the work memory unit 210. 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 event number 1 and the conditional expression of event number 2 are TRUE.

  “Cycle” indicates an event detection cycle. Each event can be detected at a different period.

  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 event setting data including an event number, a detection condition, and a period edited by the user to the CPU module 100.

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

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

  The data memory unit 220 stores current values of input data and control data. 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, a current evaluation result indicating the event state is obtained. The detection unit 202 performs a process 450 that compares the current evaluation result obtained in the process 440 with the previous evaluation result obtained in the previous evaluation. If the current evaluation result and the previous evaluation result are different from each other by 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”. It is generated and stored in the data memory unit 220. In addition, when the previous evaluation result is TRUE and the current evaluation result is FALSE, the detection unit 202 includes an event log 460 including an event number, a current time, and an event state indicating “not generated”. Is generated and stored in the data memory unit 220.

  In the present embodiment, the operation in which the detection unit 202 detects an event based on the detection condition and the operation in the case where the condition update unit 204 updates the detection condition will be mainly described. Here, “updating detection conditions” means, for example, when 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 is when adding detection conditions. When the user changes the detection condition in the support / monitoring apparatus 20, the support / monitoring apparatus 20 transmits event setting data for all events and a message for instructing update of the detection condition to the CPU module 100.

  FIG. 5 schematically shows the data structure of 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 and a monitoring event management area 511, and an event detection condition management data table 520. As an example, the management data 500 includes 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 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 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 data stored in the monitoring event management area 511.

  The monitoring event management area 510 includes an event detection condition management number 530 and monitoring event information 540. In the event detection condition management number 530, a value indicating the number N of event detection conditions is stored. 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 different events. The monitoring event management area 511 has a data structure similar to that of the monitoring event management area 510, and thus the details of the data structure are not described.

  The monitoring event information 540-1 includes a monitoring valid flag 570 and an event detection condition management data table number 571. The monitoring valid flag 570 indicates whether the detection of the corresponding event is valid or invalid. The event detection condition management data table number 571 indicates the number of the event detection condition management data table 520 described later. When the value of the monitoring valid flag 570 is 1 indicating “valid”, the detection unit 202 detects the corresponding event. When the value of the monitoring valid flag 570 is 0 indicating “invalid”, the detection unit 202 does not detect the corresponding event. Note that the monitoring event information 540-2 to the monitoring event information 540-N have the same data structure as that of the monitoring event information 540-1, and therefore, detailed description of the data structure is omitted.

  The event detection condition management data table 520-1 includes a data registration flag 551, an event number 552, an event type 553, an event state 554, an event occurrence / recovery variable value 555, a logical number 556, and logical data. 560.

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

  Event number 552 stores an event number. The event number 552 may store an event number included in the event setting data received from the support / monitoring device 20.

  The event type 553 indicates an operator for the operand constituting the conditional expression. For example, the event type 553 indicates information for identifying relational operators such as “=”, “>”, “<”, “≧”, “≦”, and logical operators such as “AND” and “OR”. .

  The event state 554 indicates whether or not the event is in an occurrence state. 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 a variable included in the detection condition when an event occurs. For example, the value of Var01 included in the detection condition corresponding to event number 1 in FIG. 3 is stored.

  The logical number 556 stores the number n of operands used in the conditional expression. The logical data 560 stores information indicating the operand used in the conditional expression. Information stored in the logical data 560 includes numerical values such as detection threshold values used in conditional expressions, addresses where variables are stored, event numbers, and the like. For example, the logical data 560 stores an address in which a variable “Var01” included in the conditional expression of event number 1 is stored, and a value of “FALSE”. 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. Omitted.

  A 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 event number 5 in FIG. 3 may be set by two event detection condition management data tables 520. As an example, the first event detection condition management data table 520 representing the OR operation of the event number 1 and the event number 2 is generated as the detection condition of the event number 5 in FIG. A second event detection condition management data table 520 that represents an AND operation between the event number assigned to event number 2 and 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 a monitoring cycle management number 581 and cycle information 582. The monitoring cycle management number 581 stores a value indicating the number M of cycle information. The monitoring cycle management information 580 includes the number of pieces of cycle information 582 indicated by the monitoring cycle management number 581.

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

  Note that the period information 582-2 to period information 582-M has the same data structure as the period information 582-1, and thus the description of the details of the data structure is omitted. Further, the information on the detection cycle may be managed with a data structure different from the data structure shown in FIG. For example, information on the detection cycle may be managed for each event in the event detection condition management data table 520.

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

  Subsequently, an event detection loop process from S604 to S620 is performed. In this loop process, an event detection condition that differs for each loop is selected from the events selected in S602.

  In step S606, the detection unit 202 determines whether event detection of the selected event is set to be valid. The detection unit 202 refers to the value of the monitoring valid flag 570 in the monitoring event information 540 and performs the determination in S606. When the detection condition is invalid, the process proceeds to the next event process in the loop process 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 refers to the event detection condition management data table 520 and calculates the evaluation result of the detection condition.

  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 is different from the evaluation result obtained in S610. In addition, the detection unit 202 determines that the event state has not changed when the value read from the event state 554 in S612 matches the evaluation result obtained in S610. If the event state has not changed, the process proceeds to the next event process in the loop process of “event detection”. If the event state has changed, 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 an event number, an event state, and current date and time information. The event status indicates “occurrence” or “not occurred”. If the evaluation result obtained in S610 is TRUE, it indicates that an event has occurred. If the evaluation result obtained in 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 for changing the detection condition. The process of this flowchart is started when the CPU module 100 receives from the support / monitoring device 20 a message for instructing new event setting data and detection condition update. Here, in the management data 500, it is assumed that 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 an event detection process according to the information stored in the monitoring event management area 510 until now. In addition, 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 step S <b> 802, the condition update unit 204 compares the current event setting data with the newly received event setting data, and identifies a deletion target, an addition target, a change target, and a non-change target event. Specifically, the condition update unit 204 generates a deletion event number list by extracting event numbers not included in the new event setting data from among event numbers included in the current event setting data. Further, the condition update unit 204 generates an additional event number list by extracting event numbers not included in the current event setting data from among 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 by 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 change target event number list. On the other hand, if the conditional expressions match, the condition update unit 204 adds the event number to the non-change target event number list.

  If the conditional expression constituting the corresponding detection condition includes another event number among the event numbers included in the event number list not to be changed, the condition update unit 204 indicates that the other event number is the change target event number. Determine whether 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 the event number from the non-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 event number 4 in FIG. Deletes the event number 4 from the non-change target event number list and adds the event number 4 to the change target event number list.

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

  In step S804, the condition update unit 204 performs processing for stopping 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 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 zero.

  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 an event based on the information stored in the monitoring event management area 511, so that an event corresponding to the event number included in the change target event number list and the deletion target event number list is detected. Is no longer detected. On the other hand, detection of an event corresponding to an event number included in the event number list not to be changed is continuously performed.

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

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

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

  In step S <b> 808, the condition update unit 204 performs event setting information addition and update processing for 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 storing the event numbers included in the deletion target event number list to 0.

  In addition, 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 in accordance with a conditional expression constituting a new detection condition designated by the new event setting data.

  In addition, the condition update unit 204 adds event setting information to the event detection condition management data table 520 based on event setting data corresponding to an event number included in the addition target event number list. 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 the value of the data registration flag 551 in the searched event detection condition management data table 520. 1 is stored, 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 variable value 555 at the time of event occurrence / recovery is set to NULL. In addition, the logical number 556, the logical data 560, and the event type 553 are set in accordance with the conditional expression constituting the corresponding detection condition specified by the new event setting data.

  In step S <b> 810, the condition update unit 204 adds and updates the monitoring event information 540 in the monitoring event management area 510 for 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 change target event in the monitoring event information 540 in the monitoring event management area 510. And the addition target event is added. More specifically, from 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.

  In addition, 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 information with the value of the monitoring valid flag 570 being 1 to the monitoring event information 540. .

  When the process of S810 ends, it is determined in S811 whether the process of S810 has succeeded. If unsuccessful, the process proceeds to S814. If successful, the process proceeds to S812.

  In step 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 processing, the detection unit 202 detects an event based on information stored in the monitoring event management area 510, and therefore corresponds to an event number included in one of the change target event number list and the deletion target event number list. Detection of the event to be started. On the other hand, the detection of the event corresponding to the event number included in the event number list not to be changed is still continued.

  When the process of S812 is completed, it is determined in S813 whether the process of S812 is successful. If unsuccessful, the process proceeds to S814. If successful, the process of the flowchart is terminated. In step S814, error processing is performed on the processing that caused the unsuccess, and then the processing of the flowchart ends.

  FIG. 9 shows event list information displayed by the support / monitoring device 20. The support / monitoring device 20 receives event log data from the CPU module 100 as a message. The support / monitoring apparatus 20 displays a list of the set event log data in a table format. The support / monitoring device 20 displays “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 a change type of the event occurrence state. When an event has changed from a state where an event has not occurred to a state where a new event has occurred, “occurrence” is displayed, and when an event has occurred, it has changed to a state where no event has occurred. Is displayed. The support / monitoring device 20 displays “occurrence” when the event state included in the event log data is “occurrence”, and displays “recovery” when the event state included in the event log data is “not occurred”. To do.

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

  With reference 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 “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 in the event detection condition management data table 520 corresponding to “event D” in the management data 500, while “event B” and “event C”. In the event state 554 corresponding to “event E”, a value 1 indicating “occurring” is held. Further, the event state 554 corresponding to “event A” holds a value 0 indicating “not generated”.

  Accordingly, immediately after the detection condition is updated by the event setting tool, it can be determined that the event states of “event B”, “event C”, and “event E” have not changed from “occurring”. Therefore, immediately after the event detection condition is changed, the “occurrence” of the event “event B”, “event C”, and “event E” is not notified. Thus, according to the control system 10, for example, even when a part of the detection condition is updated, it is possible to perform consistent event detection for an event in which the detection condition is 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 event state value of an event whose detection condition is not changed is retained without being initialized, the event can be continuously monitored.

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

  As mentioned above, although this invention was demonstrated using embodiment, the technical scope of this invention is not limited to the range as described in the said embodiment. It will be apparent to those skilled in the art that various modifications or improvements can be added to the above embodiment. It is apparent from the description of the scope of claims that embodiments with such changes or improvements can be included in the technical scope of the present invention.

  The execution order of each process such as operation, procedure, step, and stage in the apparatus, system, program, and method shown in the claims, the description, and the drawings is particularly “before” or “prior to”. It should be noted that the output can be realized in any order unless the output of the previous process is used in the subsequent process. Regarding the operation flow in the claims, the specification, and the drawings, even if it is described using “first”, “next”, etc. for the sake of convenience, it means that it is essential to carry out in this order. It is 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 nonvolatile memory unit 240 input / output unit 270 communication unit 290 bus 440, 450 Process 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 556 at the time of event occurrence / recovery Logical number 560 Logical data 570 Monitoring valid flag 571 Event detection condition management data Table number 580 monitoring period management information 581 monitoring cycle management number 582 cycle information 590 cycles 591 Event Management Number 592 event number

Claims (10)

A detection unit that detects the event by repeatedly evaluating a predetermined detection condition for detecting an event related to the control of the controlled device;
When updating the current detection condition to a new detection condition, a first detection condition in which the condition is not changed and a second detection condition in which the condition is changed are extracted from the current detection conditions. And a condition updating unit that holds information related to the event detected by the first detection condition and initializes information related to 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 condition. The control device according to claim 1, wherein the information indicates a state of the event detected by the detection condition. The detection unit detects transition of the event state by repeatedly evaluating the detection condition,
The control device includes:
The control device according to claim 3, further comprising an event storage unit that stores that the transition has occurred when the detection unit detects that the state of the event has transitioned. The condition update unit, when updating the current detection condition to a new detection condition, for the detection condition including a conditional expression using an evaluation result of another detection condition among the current detection conditions, the conditional expression The detection condition including the conditional expression is extracted as the second detection condition when there is a change in the other detection conditions even if there is no change in the detection conditions. The control device described in 1. A detection condition storage unit having a first storage area and a second storage area that can store different detection conditions;
The current detection condition is stored in one storage area of the first storage area and the second storage area,
The detection unit repeatedly evaluates a detection condition for detecting the event with reference to the one storage area,
The condition update unit may detect a detection condition that reflects 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. The control device according to any one of claims 1 to 5, wherein the control unit is configured to store and switch a storage area referred to by the detection unit 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 each of a plurality of detection conditions is valid,
The detection unit evaluates a detection condition in which a value indicating that the effective setting area is effective is stored,
The condition update unit
In the effective setting area of the other storage area, a value indicating that the second detection condition is not effective is stored, and a value indicating that the first detection condition is effective 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, extract a third detection condition to be deleted from the current detection condition,
Before the storage area referred to by the detection unit is switched from the one storage area to the other storage area, it indicates that the third detection condition is not valid in the valid setting area of the other storage area The control device according to claim 7, wherein a value is stored. A control device according to any one of claims 1 to 7,
A monitoring device,
The control device transmits a detection result of the event to the monitoring device. A detection step of detecting the event by repeatedly evaluating a predetermined detection condition for detecting an event related to the control of the controlled device;
When updating the current detection condition to a new detection condition, a first detection condition in which the condition is not changed and a second detection condition in which the condition is changed are extracted from the current detection conditions. Stages,
Holding the information related to the event detected by the first detection condition and initializing the information related to the event detected by the second detection condition.

Images