JP2021060965A - Setting device and PLC system - Google Patents

Abstract

To facilitate work to create a data utilization program for collecting control data held by a PLC and a dashboard for displaying the program.SOLUTION: A setting device receives selection of a dashboard, receives designation of data to be collected, creates setting data including a set of a template of the dashboard and a template of a data utilization program, and transfers the setting data to a PLC. Second execution means of the PLC generates display target data by performing predetermined data processing for the data to be collected based on the setting data. The display target data is associated with a graph display component included in a template of display data of the dashboard.SELECTED DRAWING: Figure 4

Description

The present invention relates to a programmable logic controller setting device and a PLC system.

A programmable logic controller (PLC) is a controller that controls industrial machines such as manufacturing equipment, transfer equipment, and inspection equipment in factory automation (Patent Documents 1 and 2). The PLC controls various expansion units and controlled devices by executing a control program such as a ladder program created by a programmer.

Japanese Patent No. 5661222 JP-A-2018-097662

Since industrial machines have consumable parts, when the consumable parts deteriorate, the yield of products decreases. Therefore, it is required to replace consumable parts appropriately. For example, if the control data and control results held by the PLC can be collected and displayed, it will be useful for field personnel who are in charge of monitoring the operation of industrial machines to find errors and prevent errors. ..

By the way, the programmer who creates the control program and the person in charge of operating and monitoring the industrial machine in the factory where the industrial machine is installed (the person in charge at the site) belong to different in-house organizations, so they can communicate with each other. It was not easy to plan. For example, if the field personnel want to change the control data they want to see, or change the graphs that display the data, the field personnel cannot change the control program. Therefore, it is necessary to inform the programmer inside or outside the company of the request and wait for the control program to be repaired. Occasionally, various tasks such as securing a repair budget occur, and many days elapse from the request to the completion of the repair. Therefore, even if you do not have programming knowledge like the person in charge of the field, you can easily make a data utilization program such as a flow program for collecting display data and a dashboard that is a UI (user interface) for displaying display data. It would be convenient if it could be repaired. This may also be useful for programmers writing control programs.

Therefore, an object of the present invention is to facilitate the work of creating a data utilization program for collecting control data held by a PLC and a dashboard for displaying the data utilization program.

The present invention is, for example,
It is a setting device that sets the programmable logic controller.
The programmable logic controller is
The first means of executing the control program and
A storage means that is a storage area or variable accessed by the first execution means according to the control program.
A collection means that collects data designated as a collection target from the storage means, and
A second execution means that executes predetermined data processing according to a data utilization program for time-series data collected from the storage means at different timings.
A generation means for generating display data of a dashboard that displays the execution result of the data utilization program, and
A means of providing the display data to an external computer and
Have,
The setting device is
A storage means for storing templates for display data on multiple dashboards and templates for multiple data utilization programs,
The first reception means that accepts the selection of one of the plurality of dashboards, and
A second reception means that accepts the designation of data to be collected by the collection means, and
In order to display the display target data, which is the data obtained by executing the predetermined data processing according to the data utilization program, on the selected dashboard, the data to be collected is displayed on the selected dashboard. A means for creating setting data including a set of a template and the template of the data utilization program associated with the selected dashboard, and a means for creating setting data.
It has a transfer means for transferring the setting data to the programmable logic controller.
The second execution means generates the display target data by executing the predetermined data processing on the data to be collected based on the setting data.
Provided is a setting device characterized in that the display target data is associated with a graph display component included in the display data template of the selected dashboard.

According to the present invention, the work of creating a data utilization program for collecting control data held by a PLC and a dashboard for displaying the data utilization program is facilitated.

Diagram showing PLC system Diagram explaining a PC Diagram illustrating PLC The figure explaining the setting device realized by a PC Diagram explaining the data utilization unit Flowchart showing how to set up the application Diagram explaining the application selection screen The figure explaining the parameter setting screen Diagram illustrating data collection and display Diagram explaining the dashboard Diagram explaining the dashboard displayed in the browser Diagram illustrating dashboard reconfiguration Diagram explaining linked editing between dashboard and flow program The figure explaining the setting device realized by a PC Flowchart showing how to set up the application Diagram explaining the application setting screen Diagram explaining the dashboard display screen for status monitoring Diagram explaining the dashboard display screen for setting Flowchart showing real-time monitoring method Flowchart showing how to reset in the data utilization unit Diagram explaining the dashboard display screen of driving record analysis Flowchart showing operation record analysis method Diagram explaining the dashboard display screen for integrated monitoring Flowchart showing integrated monitoring method

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. The following embodiments do not limit the invention according to the claims, and not all combinations of features described in the embodiments are essential to the invention. Two or more of the plurality of features described in the embodiments may be arbitrarily combined. In addition, the same or similar configurations are given the same reference number, and duplicate explanations are omitted. A lowercase alphabet may be added to the end of the reference code indicating the same or similar elements. Lowercase alphabets are omitted when explaining things that are common to multiple elements.

<System configuration>
First, a general PLC configuration and its operation will be described so that a person skilled in the art can better understand a programmable logic controller (PLC, which may be simply referred to as a programmable controller).

FIG. 1 is a conceptual diagram showing a configuration example of a programmable logic controller system according to an embodiment of the present invention. As shown in FIG. 1, this system is a PLC (programmable logic controller) 1 for comprehensively controlling a PC2a for editing a user program such as a ladder program and various control devices installed in a factory or the like. And have. PC is an abbreviation for personal computer. The user program may be created using a graphical programming language such as a ladder language or a flowchart-type motion program such as SFC (sequential function chart), or may be created using a high-level programming language such as C language. .. In the following, for convenience of explanation, the user program will be a ladder program. The PLC 1 includes a basic unit 3 having a built-in CPU and one or a plurality of expansion units 4. One or more expansion units 4 can be attached to and detached from the basic unit 3.

The basic unit 3 includes a display unit 5 and an operation unit 6. The display unit 5 can display the operating status of each expansion unit 4 attached to the basic unit 3. The display unit 5 switches the display content according to the operation content of the operation unit 6. The display unit 5 usually displays the current value (device value) of the device in the PLC1, the error information generated in the PLC1, and the like. The device is a name indicating an area on a memory provided for storing a device value (device data), and may be called a device memory. The device value is information indicating the input state from the input device, the output state to the output device, and the state of the internal relay (auxiliary relay), timer, counter, data memory, etc. set on the user program. There are two types of device values: bit type and word type. The bit device stores a 1-bit device value. The word device stores the device value of one word.

The expansion unit 4 is prepared to expand the function of the PLC1. A field device (controlled device) 10 corresponding to the function of the expansion unit 4 may be connected to each expansion unit 4, whereby each field device 10 is connected to the basic unit 3 via the expansion unit 4. Be connected. The field device 10 may be an input device such as a sensor or a camera, or an output device such as an actuator. Further, a plurality of field devices may be connected to one expansion unit 4.

For example, the expansion unit 4b may be a positioning unit that drives a motor (field device 10) to position the work, or may be a counter unit. The counter unit counts signals from an encoder (field device 10) such as a manual pulsar.

By executing the flow, the expansion unit 4a collects the collection target data from the basic unit 3 and the expansion unit 4b, processes the collection target data to create the display target data, and displays the dashboard on the display unit 7 or It is a data collection unit that creates display data for display on PC2. The basic unit 3 is sometimes called a CPU unit. The system including PLC1 and PC2 may be called a programmable logic controller system.

PC2a is a computer mainly operated by a programmer. On the other hand, PC2b is a computer operated by a person in charge at the site. PC2a may be called a program creation support device (setting device). The PC 2 is, for example, a portable notebook-type or tablet-type personal computer or smartphone, and is an external computer including a display unit 7 and an operation unit 8. The external computer is a computer outside the PLC1. A ladder program, which is an example of a user program for controlling PLC1, is created using PC2a. The created ladder program is converted into a mnemonic code in PC2a. The PC 2 is connected to the basic unit 3 of the PLC 1 via a communication cable 9 such as a USB (Universal Serial Bus) cable. For example, PC2a sends a ladder program converted into a mnemonic code to the basic unit 3. The basic unit 3 converts the ladder program into machine code and stores it in the memory provided in the basic unit 3. Although the mnemonic code is transmitted to the basic unit 3 here, the present invention is not limited to this. For example, the PC 2a may convert the mnemonic code into an intermediate code and transmit the intermediate code to the basic unit 3.

Although not shown in FIG. 1, the operation unit 8 of the PC 2 may include a pointing device such as a mouse connected to the PC 2. Further, the PC 2 may be configured to be detachably connected to the basic unit 3 of the PLC 1 via a communication cable 9 other than the USB cable. Further, the PC 2 may be connected to the basic unit 3 of the PLC 1 by wireless communication without going through the communication cable 9.

<Program creation support device>
FIG. 2 is a block diagram for explaining the electrical configuration of the PC 2. As shown in FIG. 2, the PC 2 includes a CPU 11, a display unit 7, an operation unit 8, a storage device 12, and a communication unit 13. The display unit 7, the operation unit 8, the storage device 12, and the communication unit 13 are each electrically connected to the CPU 11. The storage device 12 includes a RAM, a ROM, an HDD, and an SSD, and may further include a removable memory card. CPU is an abbreviation for central processing unit. ROM is an abbreviation for read-only memory. RAM is an abbreviation for random access memory. HDD is an abbreviation for hard disk drive. SSD is an abbreviation for solid state drive.

The user of the PC 2a causes the CPU 11 to execute the project editing program 14a stored in the storage device 12, and edits the project data through the operation unit 8. The project data includes one or more user programs (eg, a ladder program) and configuration information of the basic unit 3 and the expansion unit 4. The configuration information includes information indicating the connection positions of a plurality of expansion units 4 with respect to the basic unit 3, functions provided in the basic unit 3 (example: communication function and positioning function), and functions of the expansion unit 4 (example: shooting function). It is information indicating such as. Here, editing the project data includes creating and modifying (re-editing) the project data. The user can read the project data stored in the storage device 12 as needed and change the project data by using the project editing program 14a. The communication unit 13 communicates with the basic unit 3 via the communication cable 9a. The CPU 11 transfers the project data to the basic unit 3 via the communication unit 13. The communication unit 13 communicates with the expansion unit 4a via the communication cable 9b. The CPU 11 transfers the flow and dashboard setting data to the expansion unit 4a via the communication unit 13.

<PLC>
FIG. 3 is a block diagram for explaining the electrical configuration of PLC1. As shown in FIG. 3, the basic unit 3 includes a CPU 31, a display unit 5, an operation unit 6, a storage device 32, and a communication unit 33. The display unit 5, the operation unit 6, the storage device 32, and the communication unit 33 are each electrically connected to the CPU 31. The storage device 32 may include a RAM, a ROM, a memory card, and the like. The storage device 32 has a plurality of storage areas such as a device unit 34 and a project storage unit 35. The device unit 34 has a bit device, a word device, and the like, and each device stores a device value. The project storage unit 35 stores the project data input from the PC 2a. The storage device 32 also stores the control program for the basic unit 3. As shown in FIG. 3, the basic unit 3 and the expansion unit 4 are connected via a unit internal bus 90, which is a type of expansion bus. Although the communication function related to the unit internal bus 90 is mounted on the CPU 31, it may be mounted as a part of the communication unit 33. The communication unit 33 may have a network communication circuit. The CPU 31 receives the project data from the PC 2a via the communication unit 33.

Here, the unit internal bus 90 will be supplementarily described. The unit internal bus 90 is a communication bus used for input / output refresh. The input / output refresh is a process of updating the device value between the basic unit 3 and the expansion unit 4. I / O refresh is performed each time the ladder program is executed (that is, every scan).

The expansion unit 4 includes a CPU 41 and a memory 42. The CPU 41b of the expansion unit 4b controls the field device 10 according to an instruction (device value) from the basic unit 3 stored in the device. Further, the CPU 41b stores the control result of the field device 10 in a device called a buffer memory. The control result stored in the device is transferred to the basic unit 3 by input / output refresh. Further, the control result stored in the device is transferred to the basic unit 3 according to the read instruction from the basic unit 3 even at a timing different from the input / output refresh. The memory 42 includes a RAM, a ROM, and the like. In particular, the RAM has a storage area used as a buffer memory. The memory 42 may have a buffer that temporarily holds data (eg, still image data or moving image data) acquired by the field device 10.

The CPU 41a of the expansion unit 4a that functions as a data utilization unit communicates with the PC 2a via the communication unit 43 and the cable 9b. A data utilization unit is an expansion unit that executes a data utilization application. The data utilization application includes a data utilization program (eg, flow) that collects and processes control data, and a dashboard that displays the execution result of the data utilization program. Here, the flow is adopted as an example of the data utilization program, but it may be a user program in another language. The flow may have an arithmetic block for collecting data, an arithmetic block for executing data processing, an arithmetic block for creating display data, and the like. The dashboard has graph display parts, numerical display parts, and the like. These display components may be realized by HTML data, CSS data, Javascript® code, and the like. In this embodiment, the flow is realized by the flow template. The flow template is prepared in advance for each application, and has one or more calculation blocks in which parameters specified by the user are set. The dashboard is also realized by the template. The dashboard template has one or more display components to which parameters specified by the user are set. Parameters are a wide variety of information, such as dashboard names, device names, numbers, and unit variable names. The unit variable is a variable for the expansion unit 4a to hold the execution result of the flow.

The CPU 41a stores the flow and dashboard setting data received from the PC 2a in the memory 42a. The CPU 41a executes a flow according to the setting data, collects device values, and creates display data for displaying on the dashboard. The CPU 41a communicates with the PC 2b via the communication unit 43 and the cable 9b. The CPU 41a transmits the dashboard display data to the PC 2b. As a result, PC2b displays a dashboard containing various data related to PLC1.

FIG. 4 is a diagram illustrating a function realized by the CPU 11 of the PC 2. The project creation unit 50 is a function realized by the CPU 11 executing the project editing program 14a. The project creation unit 50 creates the project data 70 including the user program according to the user instruction input through the operation unit 8.

The flow dashboard creation unit 51 is a function realized by the CPU 11 executing the flow dashboard editing program 14b. The dashboard selection unit 52 displays a selection screen on the display unit 7 for assisting the user in selecting one dashboard from a plurality of dashboards, and accepts the user to select the dashboard. As the dashboard, there may be a dashboard for waveform monitoring, a dashboard for loss analysis, a dashboard for FFT, and the like. FFT is an abbreviation for Fast Fourier Transform. The parameter specification unit 53 accepts user specifications for parameters related to the flow associated with the dashboard selected by the user and parameters related to the dashboard display settings. The parameters include a device to be collected, a device to be analyzed, an analysis target period, a display target, a name of a display component, a unit, and the like. The creation unit 54 extracts a template for displaying the dashboard selected by the user from the dashboard template 71. The dashboard template 71 has various display components (graph modules) for realizing the dashboard. The creation unit 54 extracts from the flow template 72 a flow template that executes data processing necessary for displaying data on the dashboard selected by the user. The flow template 72 has arithmetic components (program modules) for executing data processing. The creation unit 54 creates a dashboard template, a flow template, and setting data 73 including parameters set in these templates, and stores the setting data 73 in the storage device 12.

The transfer unit 60 transfers the project data 70 to the basic unit 3 and transfers the setting data 73 to the expansion unit 4a. The Web browser 61 is a function realized by the CPU 11 executing the Web browser program 14d. The Web browser 61 accesses the Web server of the expansion unit 4a, acquires display data such as HTML data for displaying the dashboard, and displays the dashboard on the display unit 7. The flow dashboard editing program 14b may be created on a Web basis. In this case, the CPU 11 transmits data related to the UI of the flow dashboard editing program 14b to the Web browser 61 according to the Web server program 14c. The CPU 11 passes the user instruction input via the Web browser 61 to the flow dashboard editing program 14b via the Web server program 14c.

FIG. 5 shows the functions realized by the CPU 41a of the expansion unit 4a. The setting unit 80 stores the setting data 73 received from the PC 2a in the memory 42a. The setting unit 80 may set what kind of device value should be collected for the basic unit 3 according to the setting data 73. The setting data 73 includes a dashboard template 71a, a flow template 72a, and a parameter setting 74. The parameter setting 74 may be passed from the PC 2a to the expansion unit 4a in a state of being assigned to the dashboard template 71a and the flow template 72a, or may be passed from the PC 2a in a state of being separated from the dashboard template 71a and the flow template 72a. It may be passed to 4a. The flow execution unit 81 is a function realized by the CPU 41a executing the flow in the flow template 72a according to the parameter setting 74. The collection unit 82 collects the device value specified by the parameter setting 74 from the basic unit 3 and the expansion unit 4b, creates the collected data 75, and stores it in the memory 42a. The data processing unit 83 applies the data processing specified by the parameter setting 74 to the collected data 75, creates the analyzed data 76, and stores it in the memory 42a. The display processing unit 84 is based on the dashboard template 71a specified by the parameter setting 74 and the display target data, and the dashboard display data 77 (example: HTML data, image data, CSS (cascading style sheet), Javascript (registration). Create a code) for the trademark). The Web server 85 provides dashboard display data 77 to a Web browser 61 such as PC2b.

<Flowchart>
● Dashboard and flow settings (creation)
FIG. 6 is a flowchart showing a setting process executed by the CPU 11 of the PC 2a. The CPU 11 executes the following processing according to the flow dashboard editing program 14b.

In S1, the CPU 11 displays the dashboard (application) selection screen on the display unit 7. The flow dashboard creation unit 51 displays the selection screen 100 as illustrated in FIG. 7 on the display unit 7. If the setting data 73 already exists, the following processing corresponds to the resetting processing.

In FIG. 7, the pointer 101 is a display object that moves in conjunction with the operation of a pointing device such as a mouse. The loss analysis selection button 102a is a button for selecting a loss analysis application. The waveform monitoring selection button 102b is a button for selecting a waveform monitoring application. The FFT selection button 102c is a button for selecting an FFT application. A plurality of applications may be selected by pressing a plurality of selection buttons. The OK button 103 is a button for confirming the selection of the dashboard. The cancel button 104 is a button for canceling the selection of the dashboard. The user selects one of the dashboards by operating the pointer 101, and presses the OK button 103.

In S2, the CPU 11 accepts the dashboard selection. The dashboard selection unit 52 recognizes which selection button on the selection screen 100 is pressed down by the pointer 101.

In S3, the CPU 11 (parameter designation unit 53) displays the parameter setting screen corresponding to the selected dashboard on the display unit 7. FIG. 8 illustrates a parameter setting screen 110 for loss analysis. In FIG. 8, the name box 111 is a text box in which a name displayed on the loss analysis dashboard is input. The analysis target setting unit 112 inputs the device name to be analyzed (example: R000, R001, R002 AND R003), the display color of each device name in the graph (example: the color of the bar in the bar graph), the name of the analysis target, and the like. Accept. A single device may be specified, such as R000, which is an operating relay, or R001, which is a choco-stop relay, or logical operations of a plurality of devices may be specified, such as a failure relay. The operation relay is a bit device (relay device) that is turned on when the PLC1 is controlling the industrial machine and is turned off when the PLC1 is not controlling the industrial machine. The chocolate stop relay is a bit device that is turned on when the PLC1 is stopped in chocolate and turned off when the PLC1 is not stopped in chocolate. The failure relay is a bit device that turns on when the PLC1 is out of order and turns off when the PLC1 is not out of order. The flow may determine the time when the PLC1 is actually operating and the time when it is stopped by monitoring the ON / OFF of these relays. The analysis target setting unit 112 may accept that the currently set device name (example: R000) is reset to another device name (example: MR000). The operation period setting unit 113 accepts the input of the operation period of the production line. The screen selection unit 114 is a check box that accepts selection of a display screen displayed as a dashboard. A dashboard may consist of multiple display screens (eg, main screen and analysis screen). For example, the operating rate of the current day may be displayed on the main screen, and the operating rate of the past 12 days may be displayed in comparison with the analysis screen. The period setting unit 115 is a list box that accepts the setting of the unit of the data collection period (example: hourly, daily, weekly, monthly) to be displayed. The display number setting unit 116 is a numerical value box for receiving the display number of data. If the collection period is daily and the number of displays is 12, the dashboard displays the data for 12 days on a daily basis. When the additional object 117 is pressed, the parameter specification unit 53 adds an analysis target device (example: R004 indicating setup adjustment). The preview button 118 is a button that instructs the CPU 11 to display a preview of the dashboard on the display unit 7.

In S4, the CPU 11 (parameter designation unit 53) accepts the parameter designation (parameter setting 74) input through the setting screen 110 through the Web browser 61 and the Web server 85.

In S5, the CPU 11 (creating unit 54) creates the selected dashboard template 71, the flow template 72 corresponding to the dashboard, and the setting data 73 including the parameters input by the user. For example, when the loss analysis dashboard is selected, the creation unit 54 sets the input parameters for the collection flow (eg, equipment status update block) for collecting the devices to be analyzed. For example, as the operation period of the equipment state update block, a start time (example: 09:00) and an end time (example: 17:30) set by the operation period setting unit 113 are set. The device name (example: R000, R001, R002 AND R003) specified by the analysis target setting unit 112 is set as the monitoring target. The default setting may be adopted as the output of the equipment status update block (temporary data passed to the loss analysis block). In the default setting, a unit variable may be created and then the created variable may be specified as a storage destination for temporary data. Further, the creation unit 54 sets the input parameters for the data processing flow (example: loss analysis block) that executes the data processing. The default setting (eg machineStateTable) may be adopted as the input of the loss analysis block. Further, the time operation rate (example: wOperationTimeRatio) and the performance operation rate (example: wPerformanceEfficiency) may be adopted as the output of the loss analysis block. In this way, the output of the equipment status update block and the input of the loss analysis block are the same variables. That is, the equipment status update block and the loss analysis block are associated (linked) via the same parameter.

In S6, the CPU 11 (transfer unit 60) transfers the setting data 73 to the expansion unit 4a. As a result, the setting data 73 is written in the ROM area of the memory 42a of the expansion unit 4a.

FIG. 9 shows an example of the dashboard 120. In FIG. 9, the legend section 121 shows the color assigned to the device to be analyzed. The graph unit 122 includes one or more graphs that display the results of the loss analysis. The types of graphs are prepared in advance for each dashboard. The analysis result display unit 123 displays the calculation result of the loss analysis. The display target to be displayed on the analysis result display unit 123 is also prepared in advance for each dashboard. The current state display unit 124 shows the current state of the PLC1.

When the preview button 118 instructs the preview of the dashboard 120, the CPU 11 may display a graph or a numerical value using the default data for the preview prepared in advance. The creation unit 54 may accept customization of the dashboard 120 according to the operation of the pointer 101 with respect to the dashboard 120 for preview. For example, when the "hourly operating rate" as the numerical display component in FIG. 9 is double-clicked by the pointer 101, the CPU 11 may display the setting screen of the numerical display component. On this setting screen, the CPU 11 may accept editing of a prefix character (example: time operation rate), a suffix character (example:%), a reference device / unit variable (example: wOperationTimeRatio) of a numerical display component.

● Execution of Flow and Provision of Dashboard FIG. 10 is a flowchart showing execution of a flow executed by CPU 41a of the expansion unit 4a and provision of a dashboard.

In S11, the CPU 41a (collection unit 82 of the flow execution unit 81) executes the flow specified by the setting data 73 (example: equipment status update block) to collect device values (example: R000, R001, R002, R003). ) Is collected and stored in the memory 42 as the collected data 75. Here, the collected data 75 may be time-series data collected at different times.

In S12, the CPU 41a (data processing unit 83) processes data (example: time operation rate, performance operation rate, etc.) into data 75 (device value) collected according to the flow (example: loss analysis block) specified by the setting data 73. Calculate the non-defective rate and overall equipment effectiveness). As a result, the analyzed data 76 is created and stored in the memory 42a.

In S13, the CPU 41a (display processing unit 84) creates display data (eg, HTML data) for displaying the dashboard 120 by a flow. The display processing unit 84 creates display data using display target data such as collected data 75 and / or analyzed data 76.

In S14, the CPU 41a (Web server 85) provides the display data to the PC 2b. The CPU 41a may display the display data on the display device of the PLC1.

In S15, the CPU 41a determines whether or not the display end is instructed by the PC 2b. If the display end is not instructed, the CPU 41a may repeat S11 to S14. When the end of display is instructed, the execution of the flow and the provision of the dashboard are terminated.

FIG. 11 shows the UI 130 of the Web browser displayed on the display unit 7 of the PC 2b. The URL assigned to the Web server 85 of the expansion unit 4a is input to the URL input unit 131. The CPU 11 of the PC 2b accesses the Web server 85 of the expansion unit 4a according to the input URL. The CPU 11 displays the display data (HTML file, image data, etc.) of the dashboard 120 provided by the Web server 85 on the UI 130 of the Web browser.

● Customization of Display Parts of Dashboard As described with reference to FIG. 9, the creating unit 54 may accept customization of display parts of the dashboard 120. When the pie chart shown in FIG. 9 is right-clicked by the pointer 101, the creation unit 54 may display an edit menu. The CPU 11 may delete the right-clicked pie chart when the graph deletion (part deletion) included in the edit menu is selected by the pointer 101. FIG. 12 shows the dashboard 120 with the pie chart removed. In this case, the creation unit 54 updates the setting data 73 so as to delete or invalidate the calculation block for realizing the pie chart among the plurality of calculation blocks constituting the flow. In this way, the creation unit 54 may reflect the editing result of the display component in the flow. On the contrary, the creating unit 54 may reflect the editing result of the flow block constituting the flow on the display component.

Such customization of the dashboard 120 may be performed through the UI 130 of the Web browser 61 shown in FIG. The CPU 11 of the PC 2a notifies that the pie chart has been right-clicked by executing HTTP communication with the CPU 41a (setting unit 80) of the expansion unit 4a, receives the display data of the edit menu from the Web server 85, and deletes it. The instruction of may be transmitted to the setting unit 80. The setting unit 80 deletes or invalidates the calculation block corresponding to the pie chart among the plurality of calculation blocks constituting the flow. As a result, the setting data 73 is updated.

● Import of setting data The setting data 73 may be imported into another PLC1. In a factory, multiple production lines may be operating in parallel. In this case, the same type of PLC1 controls the industrial machine in each of the plurality of production lines. Therefore, the PC2a may copy or import the setting data 73 created for the first PLC1 into the second PLC1. At this time, the CPU 11 may transfer the setting data 73 to the second PLC 1 after resetting (re-editing) the setting data 73. As described above, the device name related to operation may be changed from R000 to MR000 by resetting.

Also, if a specific data utilization application already exists in the second PLC1 and the same data utilization application is imported from the first PLC1, duplication of unit variables will occur and the two data utilization applications will be normal. It may stop working. That is, if the unit variable (example: wOperationTimeRatio) in the setting data 73 that originally exists and the unit variable (example: wOperationTimeRatio) duplicated for import overlap, the flow may not operate correctly in the second PLC1. Might happen. In this case, the CPU 11 (creating unit 54) may change the unit variables so as to eliminate the duplication of the unit variables (example: change wOperationTimeRatio to wOperationTimeRatio2).

● Combination of multiple dashboards As mentioned above, multiple dashboards may be selected. In this case, a plurality of dashboards, that is, a plurality of flows may be linked. For example, a waveform monitoring application may collect vibration data for an industrial machine and display the waveform of the vibration data on a dashboard along the time axis. In this case, the flow associated with the waveform monitoring application collects the vibration data and holds the vibration data in the memory 42a. On the other hand, the flow of the FFT application may perform frequency analysis by FFT on this vibration data. The dashboard of the FFT application displays the frequency analysis result of the vibration data. The frequency analysis result is held in the memory 42a. Further, the flow of the loss analysis application acquires the previous frequency analysis result and the current frequency analysis result from the memory 42a, obtains the difference between them, and compares this difference with a predetermined error threshold to determine the presence or absence of an error. The analysis result may be obtained and displayed on the dashboard of the loss analysis application. In this way, a plurality of dashboards and a plurality of flows may be linked. A plurality of dashboards may be displayed side by side, or a plurality of dashboards may be displayed while being switched one by one according to the operation of a switching button provided on each dashboard.

● Change of setting data 73 following the change of project data 70 The creation unit 54 may change the setting data 73 according to the change of project data 70. For example, although R000 has already been exemplified as an operation relay, another device (eg, MR000) may be assigned as this operation relay by changing the project data 70. Therefore, the creation unit 54 compares the time stamp of the setting data 73 with the time stamp of the project data 70 to determine whether or not the project data 70 has been changed after the setting data 73 is saved. When the project data 70 is changed, the creation unit 54 further analyzes the project data 70 to determine whether or not the device allocation related to the setting data 73 has been changed. When the creation unit 54 detects that the device allocation related to the setting data 73 has been changed, the creation unit 54 reflects the change in the project data 70 in the setting data 73 (example: R000 → MR000). As a result, the user will be able to reduce the workload of resetting the setting data 73.

FIG. 14 is a diagram illustrating a function realized by the CPU 11 of the PC 2. The project creation unit 50 is a function realized by the CPU 11 executing the project editing program 14a. The project creation unit 50 includes a control program creation unit 150, a flow dashboard creation unit 51, and a collection setting unit 57. The project creation unit 50 creates project data 70 including a user program such as a ladder program according to a user instruction input through the operation unit 8.

The control program creation unit 150 creates a control program 155 such as a ladder program executed by the CPU 31 according to a user instruction input through the operation unit 8. The control program 155 is stored in the storage device 12 as a part of the project data 70.

The flow dashboard creation unit 51 is a function realized by the CPU 11 executing the flow dashboard editing program 14b. The flow dashboard creation unit 51 includes an application selection unit 55 and a setting data creation unit 56. The application selection unit 55 displays a selection screen on the display unit 7 that assists the user in selecting one application from a plurality of applications, and accepts the user's selection of the application. As the application, there may be a real-time monitoring application that monitors the device or variable to be monitored in real time, an operation record analysis application that analyzes an operation record for reproducing the operation state of the PLC1, and the like.

The following may exist as real-time monitoring applications.
(1) Waveform monitoring: A waveform whose amplitude changes within the range from a preset upper limit value to a lower limit value (monitored waveform) is monitored. (2) Timing monitoring: ON and / or of the monitored bit device. The OFF timing is monitored (3) Camera monitoring: It is monitored whether the feature amount data of the camera image to be monitored satisfies the preset detection condition (4) Cycle monitoring: Cycle operation is a plurality of cycle operations. It means that the process is repeatedly executed every cycle. In cycle monitoring, a bit device indicating the start timing and a bit device indicating the end timing of each of a plurality of processes constituting the cycle operation are set as monitoring target devices. The time interval from the start to the end of the operation of the entire cycle and the time interval from the start to the end of each process in one cycle are monitored. The whole cycle operation refers to the whole one cycle.

The setting data creation unit 56 creates application setting data 154 including parameters related to the data utilization program associated with the application selected by the user and parameters related to the display setting of the dashboard according to the user instruction. This parameter includes the device or variable to be monitored, the name of the monitoring item (example: process name), the monitoring conditions for each monitoring target, the file to be analyzed, the device to be analyzed, the analysis target period, the display target, and the display components. Name, unit, etc. The setting data creation unit 56 extracts a template for displaying the dashboard selected by the user from the dashboard template 151 as the dashboard template 151a of the setting data 73. The dashboard template 151 has various display components (graph modules) for realizing the dashboard. The setting data creation unit 56 uses the template of the data utilization program that executes the data processing necessary for displaying the data on the dashboard selected by the user as the utilization program template 152a of the setting data 73 from the utilization program template 152. Extract. The utilization program template 152 has arithmetic components (program modules) for executing data processing. The setting data creation unit 56 creates a dashboard template, a data utilization program template, and setting data 73 including application setting data 154 set in these templates, and stores the setting data 73 in the storage device 12. The setting data creation unit 56 may create collection setting data 153 including a device or variable to be collected, collection conditions, and the like.

The collection setting unit 57 defines the collection operation of devices and variables according to the user's instruction. Further, the collection setting unit 57 creates the collection setting data 153 including the device or variable to be collected, the collection conditions, and the like. The collection setting data 153 may be included in the setting data 73.

The transfer unit 60 transfers the project data 70 to the basic unit 3 and transfers the setting data 73 to the expansion unit 4a. The Web browser 61 is a function realized by the CPU 11 executing the Web browser program 14d.

FIG. 15 is a flowchart showing a setting process executed by the CPU 11 of the PC 2a. The CPU 11 executes the following processing according to the flow dashboard editing program 14b.

In S21, the CPU 11 (application selection unit 55) displays the application selection screen on the display unit 7. The application selection unit 55 displays a selection screen of a real-time monitoring application or an operation record analysis application on the display unit 7. If the setting data 73 already exists, the following processing corresponds to the resetting processing.

In S22, the CPU 11 (application selection unit 55) accepts application selection. The application selection unit 55 recognizes which selection button on the selection screen is pressed down by the pointer or the like. A select button is associated with each of the applications. That is, the application selection unit 55 recognizes the application corresponding to the pressed selection button.

In S23, the CPU 11 (setting data creation unit 56) displays the setting screen of the application setting data 154 (setting item) corresponding to the selected application on the display unit 7. FIG. 16 illustrates a setting wizard 161 which is a setting screen of application setting data for cycle monitoring. In FIG. 16, the monitoring check box 162a is a check box to which a check indicating that the user has selected the monitoring check box 162a is added. Each of the input fields 162b to 162f is an input field in which an item name, a start condition, an end condition, a caution value, and an alarm value are input. The item name is a name given to the process. The start condition is a change (falling / rising) of a signal (relay device or variable) that is a starting condition of each process. The end condition is a change (falling / rising) of a signal (relay device or variable) that is a ending condition of each process. The attention value is an upper limit value and a lower limit value defined as a caution state. The alarm value is an upper limit value and a lower limit value defined as an alarm state. The upper and lower limits may be referred to as thresholds. Each process in the cycle corresponds to the setting input line 163, and a monitoring item is set for each setting input line 163. The start condition and end condition are set by the device or variable that defines the start timing and end timing of each process in the cycle, and the device, variable, and condition that defines each timing are the start condition and the condition that defines the timing. It is set as an end condition. The condition that defines the timing is, for example, the rising timing. The caution value and the warning value are set by the upper limit value and / or the lower limit value, respectively. When the corresponding check box is checked, the set threshold value becomes valid. The OK button 164 is a button for the user to instruct the completion of the setting. The cancel button 165 is a button instructing to cancel the setting change input by the user.

In S24, the CPU 11 (setting data creation unit 56) accepts the designation of the application setting data 154 input through the setting wizard 161. For example, the setting data creation unit 56 accepts the setting input of each setting item.

In S25, the CPU 11 (collection setting unit 57) displays the data collection setting screen on the display unit 7. In S26, the CPU 11 (collection setting unit 57) accepts the designation (setting input) of the collection setting data 153 such as the device to be collected, the variable, and the collection condition input through the data collection setting screen. When the collection setting data 153 is set by the application setting data 154, S25 and S26 are not always necessary.

In S27, the CPU 11 (setting data creation unit 56) includes the template 151a of the selected dashboard, the template 152a of the data utilization program corresponding to the dashboard, the application setting data 154 input by the user, and the collection setting data 153. The setting data 73 is created.

In S28, the CPU 11 (setting data creation unit 56) stores the setting data 73 in the storage device 12. The CPU 11 (setting data creation unit 56) saves the setting data 73 including the dashboard template 151a, the utilization program template 152a, the collection setting data 153, and the application setting data 154 as a part of the project data 70 having the control program 155. May be good. The CPU 11 (transfer unit 60) transfers the setting data 73 to the expansion unit 4a as a part of the project data 70. As a result, the setting data 73 is written in the ROM area of the memory 42a of the expansion unit 4a. The project data 70 may be read from the PLC1 in order to set the selected application using the application setting data 154 which is a part of the project data 70. At this time, the application setting data 154 may be read together with the control program 155 and the data utilization program. The PC 2a may collate the application setting data 154 stored in the PC 2a with the application setting data 154 stored in the PLC 1 and display the collation result. Therefore, for example, when the application setting data 154 written in the PLC1 is rewritten in the PLC1 and then read from the PLC1 to the PC2a again, the rewritten application setting data 154 may be confirmed in the PC2a.

FIG. 17 shows an example of a dashboard 171 for a real-time monitoring application. In FIG. 17, the operation state display 172 shows the operation state of real-time monitoring. The display switching tab 173 is a tab button display for switching to another dashboard corresponding to the application when a plurality of dashboards are set for the application. FIG. 17 shows a state in which the monitor button is pressed. In this state, if the trend tab is pressed, the dashboard switches to the trend display dashboard. When the history tab is pressed, the dashboard switches to the history view dashboard. In each display column 174a to 174g, a graph related to the item name, the margin, the measured value, the caution value, the alarm value, the determination result, and the measured value is displayed for each monitoring item. The item name, caution value, and alarm value are displayed based on the application setting data 154. The measured value indicates the time width from the start timing to the end timing determined based on the start condition and the end condition of the application setting data 154. The margin indicates how much the measured value of the monitoring item has a margin. For example, the margin may indicate how much the measured value has a margin with respect to the alarm value or the caution value. The judgment result is a judgment result obtained based on the measured value and a valid alarm value or caution value. The determination result may indicate the status classification of the monitoring target such as normal, caution, and alarm. Even if the judgment result based on the latest measured value is normal, the judgment result may be once in the state of caution or warning in the past. In this case, a higher alert state may be maintained during a predetermined determination period from the past to the present. By pressing the clear button in the judgment display field 174f, the latest judgment result may be updated. The graph associated with the measured value is a visualization of the measured value. For example, a bar graph showing the time width from the start timing to the end timing may be displayed. A line corresponding to the caution value and the alarm value may be displayed at a position corresponding to the caution value and the alarm value. For example, when the threshold line display check box of the graph display field 174 g is checked, threshold lines corresponding to valid caution values and alarm values are displayed. When the setting button of the graph display field 174g is pressed, the setting dashboard among other dashboards corresponding to the application is displayed.

FIG. 18 shows an example of a configuration dashboard 181 for a real-time monitoring application. When the setting button of the graph display field 174g in FIG. 17 is pressed, the setting dashboard 181 is displayed. In FIG. 18, the operation state display 182 shows the operation state of real-time monitoring. The monitoring state changeover switch 183 is a switch for switching real-time monitoring between a monitoring state and a non-monitoring state. The threshold value batch setting button 184 is a button for shifting to a setting screen for collectively setting a plurality of threshold values provided for each monitoring item. In each of the input fields 185a to 185f, a monitoring check box, an item name, a start condition, an end condition, a caution value, and an alarm value are displayed for each monitoring item. A setting wizard for setting the application setting data of the project data 15 in FIG. 2 and a corresponding input field may be provided. When the add button 186a is pressed, an input line for inputting a new monitoring item is added. When the delete button 186b is pressed, the input line previously selected by the up / down buttons 186c is deleted. When the setting reflection button 187 is pressed, the updated setting contents are reflected in the application setting data (display setting 62). Subsequently, the dashboard 171 for the real-time monitoring application based on the updated application setting data (display setting 62) is displayed. When the cancel button 188 is pressed, the dashboard 171 for the real-time monitoring application based on the application setting data (display setting 62) is displayed without reflecting the updated setting contents in the application setting data (display setting 62). To.

FIG. 19 is a flowchart showing execution of a data utilization program for real-time monitoring processing executed by CPU 41a of the expansion unit 4a and provision of a dashboard.

In S41, the CPU 41a (collection unit 82 of the flow execution unit 81) monitors the device or variable corresponding to the start signal and the end signal according to the application setting data 154 of the setting data 73. The application setting data 154 holds a name of a device or variable used as a start signal and a predetermined value stored in the device or variable. The start timing is when the value of the device or variable changes to a predetermined value. As shown in FIG. 18, it may be set as a starting condition that the change in the device or variable is a rising edge or a falling edge. The same applies to the end signal. By executing the data utilization program based on the utilization program template 152a, the device value to be collected specified by the application setting data 154 is collected, and the collected data 75 is stored in the memory 42. Here, the collected data 75 may be time-series data collected at different times. In addition to the data utilization program, a collection program that executes a collection operation according to the collection setting data 153 may be provided. In this case, the collection setting data 153 is set according to the application setting data 154, the device value to be collected specified by the set collection setting data 153 is collected, and the collected data 75 is stored in the memory 42.

In S42, the CPU 41a (data processing unit 83) from the timing when the start signal condition is satisfied to the timing when the end signal condition is satisfied based on the data 75 (device value) collected according to the data utilization program specified by the setting data 73. Determine the time information of. The CPU 41a (data processing unit 83) monitors whether the device or variable set as the monitoring target satisfies the detection condition such as the rising edge according to the start condition 162c in FIG. 16 and the start condition 185c in FIG. Here, the timing that satisfies the detection condition, that is, the timing that satisfies the condition of the start signal is monitored. Similarly, the CPU 41a (data processing unit 83) monitors whether the device or variable set as the monitoring target satisfies the detection condition such as the rising edge according to the end condition 162d in FIG. 16 and the end condition 185d in FIG. Here, the timing that satisfies the detection condition, that is, the timing that satisfies the condition of the end signal is monitored. The time information determined by the CPU 41a (data processing unit 83) may be the time width from the timing satisfying the condition of the start signal to the timing satisfying the condition of the end signal.

In S43, the CPU 41a (data processing unit 83) determines the state based on the time information determined in S42 and the determination threshold value set according to the application setting data 154. The upper and lower limits of the caution value and the alarm value may be set as the judgment threshold. In this case, the CPU 41a (data processing unit 83) determines whether or not the determined time information, which is the measured value, exceeds the upper limit value. Further, the CPU 41a (data processing unit 83) determines whether or not the determined time information is below the lower limit value. The application setting data 154 may include a flag indicating whether or not each upper limit value and each lower limit value are used as a determination threshold value. In this case, the CPU 41a (data processing unit 83) compares the determined time information, which is a measured value, with each upper limit value and each lower limit value based on the flag included in the application setting data 154, and thus the state of the monitoring target. To judge. The value of this flag can be set by the user through a UI (user interface) such as a checkbox. The monitored states may include normal, caution, and alarm. Attention state and alarm state are distinguished based on the degree of deviation of the measured value from the normal state. The difference between the measured value in the normal state (normal value) and the measured value in the alarm state (alarm value) is larger than the difference between the measured value in the normal state and the measured value in the caution state (caution value). Therefore, the alarm value is set to a value that deviates from the normal value rather than the caution value. A caution value and an alarm value may be set as upper limit values. In this case, the CPU 41a (data processing unit 83) determines that the state of the monitoring target is "normal" when the determined time information is equal to or less than the caution value. The CPU 41a (data processing unit 83) determines the state of the monitoring target as "caution" when the determined time information exceeds the caution value and is equal to or less than the alarm value. When the determined time information exceeds the alarm value, the CPU 41a (data processing unit 83) determines the state of the monitoring target as "alarm". As a result, the analyzed data 76 is created and stored in the memory 42a.

A caution value and an alarm value may be set as lower limit values, respectively. In this case, the CPU 41a (data processing unit 83) determines that the state of the monitoring target is "normal" when the determined time information is equal to or greater than the caution value. The CPU 41a (data processing unit 83) determines the state of the monitoring target as "caution" when the determined time information is less than the caution value and equal to or more than the alarm value. When the determined time information is less than the alarm value, the CPU 41a (data processing unit 83) determines the state of the monitoring target as "alarm". As a result, the analyzed data is created and saved in the memory.

The caution value and the alarm value may be set by the upper limit value and the lower limit value, respectively. In this case, the CPU 41a (data processing unit 83) sets the state of the monitoring target as "normal" when the determined time information is equal to or greater than the lower limit caution value and the determined time information is equal to or less than the upper limit caution value. judge. The CPU 41a (data processing unit 83) determines the state of the monitoring target as "caution" when the determined time information is less than the upper limit alarm value and equal to or more than the upper limit caution value.
Similarly, the CPU 41a (data processing unit 83) determines the state of the monitoring target as "caution" when the determined time information is less than the lower limit caution value and equal to or more than the lower limit alarm value.
The CPU 41a (data processing unit 83) sets the status of the monitoring target as "alarm" when the determined time information is less than the lower limit alarm value or the determined time information exceeds the upper limit alarm value. judge. As a result, the analyzed data is created and saved in the memory.

The CPU 41a (data processing unit 83) may calculate a margin degree indicating how much the measured value has a margin with respect to the alarm value and the caution value. The margin may be defined, for example, to be 100 when there is sufficient margin, 50 when in the caution state, and 0 when in the alarm state. In this way, the margin may be defined so that the value changes stepwise according to the distance (difference) between the caution value and the measured value. The margin is stored in the memory 42a as the analyzed data 76. When the measured value exceeds the alarm value, the CPU 41a (data processing unit 83) may generate a signal indicating that the measured value exceeds the alarm value. For example, when the measured value exceeds the alarm value, the CPU 41a (data processing unit 83) changes the value of the device or variable indicating that the measured value exceeds the alarm value. A device or variable indicating that the measured value has exceeded the alarm value may be assigned as a trigger. For example, it may be assigned to a logging save trigger. As a result, the operation record of the PLC1 and the like are saved with reference to the timing when the alarm is generated.

In S44, the CPU 41a (display processing unit 84) generates source data of the dashboard 171 including the time information determined in S42, the determination threshold value, and the state of the monitoring target determined in S43. The CPU 41a (display processing unit 84) reflects the time information determined based on the dashboard template 151a of the setting data 73, the determination threshold value, and the determined state of the monitoring target in the variables assigned to the dashboard template 151a. For example, the CPU 41a (display processing unit 84) displays in the graph display field 174g in FIG. 17 a measured value indicating the time width from the timing satisfying the condition of the start signal to the timing satisfying the condition of the end signal in the form of a bar graph. Create display data so that. At this time, the time from the timing satisfying the condition of the start signal to the timing satisfying the condition of the end signal may be displayed in a band shape. As a result, not only the time width but also the dashboard showing at what timing in the cycle each monitored object is operating in the control of the cycle operation is displayed. For example, the right end to the left end of the graph display field 174 g may correspond to one cycle of the monitoring target. The start position of the band (bar in the bar graph) corresponds to the timing when the condition of the start signal in one cycle is satisfied. The end position of the band corresponds to the timing when the condition of the end signal in one cycle is satisfied. Therefore, the length of the band indicates the time width.

The margin may be displayed along with the measured value. The CPU 41a (display processing unit 84) creates display data (eg, HTML data) for displaying the dashboard 171 based on the variables assigned to the dashboard template 151a. The CPU 41a (display processing unit 84) may separately manage the screen data that is the base of the dashboard 171 and the updated data such as the measured value and the state information. In this case, the CPU 41a (display processing unit 84) individually manages the screen data to which the referenced device or variable is assigned and the display target data which is the value of the referenced device or variable. The CPU 41a may create display data by periodically updating the display target data. The display processing unit 84 creates display data using display target data such as collected data 75 and / or analyzed data 76.

In S45, the CPU 41a (Web server 85) provides the display data to the PC 2b. The CPU 41a may display the display data on the display device of the PLC1. The display device of the PLC1 may be built in the PLC1 or may be connected to the PLC1 by wire or wirelessly. The CPU 41a (display processing unit 84) may separately manage the screen data to which the referenced device or variable is assigned and the display target data which is the value of the referenced device or variable. In this case, the CPU 41a (Web server 85) selectively provides the screen data and the display target data among the display data according to the update request and the update schedule of the dashboard 171. In response to the display request of the dashboard 171, the CPU 41a (Web server 85) provides display data including screen data and display target data. In response to the display update request of the dashboard 171, the CPU 41a (Web server 85) selectively provides the updated display target data as display data.

FIG. 20 shows a flowchart showing a setting process via the dashboard of real-time monitoring executed by the CPU 11 of the PC 2a.

In S51, the CPU 41a (display processing unit 84) displays the dashboard 181 for setting. For example, the display processing unit 84 creates display data for displaying the dashboard 181 for setting shown in FIG. 18, and the CPU 41a (Web server 85) displays the dashboard 181 for setting. The data is provided to PC2b.

In S52, the CPU 41a (setting unit 80) accepts user input for adding / deleting / changing the monitoring target and / or setting the determination threshold value. When the CPU 41a (setting unit 80) detects that the add button 186a has been pressed, it adds an input line for setting a new monitoring target. The CPU 41a (display processing unit 84) creates display data to display the dashboard 181 for setting to which an input line for setting a new monitoring target is added. The CPU 41a (Web server 85) provides the PC 2b with display data for displaying the updated dashboard 181 for setting. Here, the setting unit 80 may be provided in the flow execution unit 81 to accept the setting as a part of executing the data utilization program. When the CPU 41a (setting unit 80) detects that the delete button 186b is pressed, the CPU 41a (setting unit 80) deletes the selected input line. The CPU 41a (display processing unit 84) creates display data to display the dashboard 181 for setting in which the selected input line has been deleted. The CPU 41a (Web server 85) provides the PC 2b with display data for displaying the updated dashboard 181 for setting. At this time, the selection operation to the input line by the up / down buttons 186c may be displayed. When the CPU 41a (setting unit 80) receives the change input to each input field 185a to 185d, the CPU 41a (display processing unit 84) displays the dashboard 181 for setting reflecting the change input to each input field 185a to 185d. Display data is created for display, and the CPU 41a (Web server 85) provides the PC 2b with display data for displaying the updated dashboard 181 for setting. When the CPU 41a (setting unit 80) receives the change input to each input field 185e to 185f of the determination threshold value, the CPU 41a (display processing unit 84) is set to reflect the change input to each input field 185e to 185f of the determination threshold value. Create display data to display the dashboard 181 for. The CPU 41a (Web server 85) provides the PC 2b with display data for displaying the updated dashboard 181 for setting.

In S53, the CPU 41a (setting unit 80) updates the corresponding application setting data 154 according to the user input. When the CPU 41a (setting unit 80) detects that the setting reflection button 187 has been pressed, it reflects the updated setting contents in the application setting data 154. On the other hand, when the CPU 41a (setting unit 80) detects that the cancel button 188 has been pressed, the updated setting contents are not reflected in the application setting data 154, and the updated setting contents are discarded. The CPU 41a (display processing unit 84) creates display data for displaying the dashboard 171 for the real-time monitoring application based on the application setting data 154 without reflecting the updated setting contents. The CPU 41a (Web server 85) provides the PC 2b with display data for displaying the dashboard 171 for the real-time monitoring application.

In S54, the CPU 41a (data processing unit 83) determines the state of the monitoring target based on the determined time information regarding the monitoring target and the set determination threshold value according to the application setting data 154 updated in S53. The CPU 41a (data processing unit 83) determines the state of the monitoring target based on the time information determined in the same manner as S42 according to the updated application setting data 154 and the determination threshold value set according to the updated application setting data 154. The determination is made in the same manner as in S53.

In S55, the CPU 41a (display processing unit 84) shows the time information determined according to the updated application setting data 154, the determination threshold value set according to the updated application setting data 154, and the state of the monitoring target determined in S54. Create display data for displaying the status monitoring dashboard shown in 18. The CPU 41a (Web server 85) provides the PC 2b with display data for displaying the dashboard 171 for status monitoring.

FIG. 21 shows an example of dashboard 221 for a driving record analysis application. The dashboard 221 for the driving record analysis application has a camera image reproduction view 222, an occurrence status time series view 223, an unusual device view 224, and an unusual waveform view 225. The operation record analysis application analyzes the operation record of the PLC1 stored in advance by the CPU 41a (data processing unit 83), and presents devices and variables having different operations by the CPU 41a (display processing unit 84). The CPU 41a (data processing unit 83) sets a detection algorithm and a detection threshold value for each monitoring target by analyzing the normal operation record. The CPU 41a (data processing unit 83) applies a detection algorithm and a detection threshold set for each monitoring target to the operation record to be analyzed to determine devices and variables that operate differently than usual. The operation record analysis application may, for example, rank display devices and variables that behave differently according to the degree of deviation from the normal state. For example, the device or variable that holds the most divergent value from the normal value may be displayed or highlighted at the top.

The operation record of the PLC1 is a collection target device or variable collected according to the collection setting data 153 that defines the collection target and the storage condition, and is stored in the basic unit 3 or the expansion units 4a and 4b in the PLC1 according to the storage condition. Is. For example, the CPU 31 collects devices and variables to be collected according to the collection setting data 153. When the establishment of the storage condition is detected, the CPU 31 stores the devices and variables collected based on the timing at which the storage condition is satisfied in the storage device 32 as the operation record of the PLC1. The operation record is saved every time the storage condition is satisfied. For example, the operation record may be stored in the storage device 32 as a file together with the time when the storage condition is satisfied. The collection target of the operation record of the PLC 1 may be collectively set for each program such as the control program 155 or for each unit such as the basic unit 3 and the expansion units 4a and 4b. As a result, the devices and variables related to the operation of the PLC1 are collectively recorded. Therefore, the user can record the devices and variables related to the operation of the PLC1 without specifying the individual monitoring target in advance. It is possible to reproduce the operating state of the PLC1 based on the timing when the storage condition is satisfied, and to analyze the operating state of the PLC1 based on the timing when the storage condition is satisfied. The storage condition may be selected from a storage command of the control program 155, a storage trigger by an assigned device or variable, a time trigger that occurs at a predetermined time, and the like. The storage conditions are set according to user input.

In FIG. 21, the camera image reproduction view 222 includes an abnormal image reproduction display unit 222a, a normal image reproduction display unit 222b, and a reproduction control view 222c. Among the camera images included in the operation record to be analyzed, the image reproduction display unit 222a at the time of abnormality displays the camera image acquired at the timing when the operation record analysis application detects a device or a variable whose operation is different from usual. To. Further, the normal image reproduction display unit 222b displays a camera image time-synchronized with the camera image displayed on the abnormal image reproduction display unit 222a among the camera images included in the operation record corresponding to the normal time. The PLC1 may execute cycle control, which is a periodic control. In this case, the time series data of at least some devices or variables included in the operation record corresponding to the cycle control has periodicity according to the cycle control. The CPU 41a (data processing unit 83) analyzes the periodicity of the devices and variables included in the operation record from the time series data, and determines the devices and variables that define the cycle of cycle control. The CPU 41a (setting unit 80) may select a device that defines the cycle of cycle control or a reference device that is a variable according to user input. The camera image displayed on the abnormal image reproduction display unit 222a and the camera image displayed on the normal image reproduction display unit 222b are based on the periodicity of cycle control and the time information associated with each camera image. Played in sync. For example, the display of the two camera images may be updated at regular intervals. In this case, the two camera images will be displayed as if they were moving images.

The reproduction control view 222c has an operation button for synchronously operating the display of the two camera images displayed in the camera image reproduction view 222. The operation buttons include a stop button, a forward button, a back button, and the like. When the "stop button" is pressed, the camera image displayed on the abnormal image reproduction display unit 222a and the camera image displayed on the normal image reproduction display unit 222 are synchronized and paused. When the "forward button" or "back button" is pressed, the display time of the camera image displayed on the abnormal image reproduction display unit 222a and the display time of the camera image displayed on the normal image reproduction display unit 222b are changed. It changes synchronously.

The occurrence status time series view 223 is a screen for displaying the analysis result of the operation record. The analysis result includes, for example, a device or a variable having an unusual behavior detected by applying a detection algorithm and a detection threshold set for each monitoring target to a plurality of devices stored as an operation record.

In the cycle display field 223a, each cycle of cycle control is displayed in chronological order. The break of each cycle may be specified by the reference device. The CPU 41a (data processing unit 83) detects that a change in the state or value of the reference device included in the operation record satisfies a condition (which may be called a cycle condition or a delimiter condition). The timing at which the delimiter condition is satisfied corresponds to the delimiter of each cycle. The CPU 41a determines the period of each cycle corresponding to the determined cycle break, and displays each cycle in the cycle display column 223a. In this example, three cycles such as cycle 1, cycle 2, and cycle 3 are displayed. In the generated device display field 223b, the number of generated devices different from the usual one is displayed in chronological order corresponding to each cycle. The CPU 41a (data processing unit 83) applies a detection algorithm and a detection threshold set for each monitoring target to the operation record to be analyzed, and sets the number of devices and variables (number of occurrences) exceeding the detection threshold in chronological order. Tally. In this example, it is shown that unusual devices are occurring in cycles 1 and 3.

In the pattern-specific occurrence status display column 223c, the occurrence status of an unusual device for each pattern is displayed. The CPU 41a (data processing unit 83) applies the detection algorithm and the detection threshold set for each monitoring target to the operation record of the analysis target, and sets the generation period of the device or variable exceeding the detection threshold in a different state from usual. Aggregate by pattern. In this example, the pattern-based occurrence status display column 223c has an upper row, a middle row, and a lower row. In the upper row, an ON / OFF pattern is adopted as a pattern in a state different from usual. That is, in the upper row, the occurrence status of the ON / OFF pattern different from the usual ON / OFF pattern is displayed. In the middle row, the occurrence status of constant values different from normal is displayed. In the lower row, the occurrence status of ON / OFF timing different from the usual ON / OFF timing is displayed. In the camera feature amount display field 223d, the number of times a camera feature amount different from the usual camera feature amount is generated is displayed. Saving of logging The operation record saved when the trigger occurs may include image data of the camera. The CPU 41a (data processing unit 83) generates feature amount data related to the amount of received light and brightness included in the camera image, and analyzes the feature amount data according to periodicity to display the number of times that a feature amount different from the usual one occurs. You may.

The unusual device view 224 displays details about unusual device occurrences on a cycle-by-cycle or scan-by-scan basis. In each display column 224a to 224c, the device name in which the unusual situation occurred, the outline when the unusual situation occurred, and the occurrence time are displayed. The target period of the information displayed in the device view 224 different from the usual one may be selected according to the user input. For example, when the CPU 41a (setting unit 80) receives the user input in the occurrence status time series view 223, the CPU 41a selects the cycle corresponding to the user input. The CPU 41a (data processing unit 83) analyzes the cycle selected from the operation record to be analyzed, and extracts the device in which a situation different from the usual one occurs in the cycle. The CPU 41a (display processing unit 84) displays a list of extracted devices in a device view 224 different from the usual one. In the unusual device view 224, you can see in a list what kind of change occurred on which device.

In the unusual waveform view 225, the waveform of the time series data is displayed for a specific device among the devices in the unusual situation. The device displayed in the unusual waveform view 225 may be selected according to user input. For example, when the CPU 41a (setting unit 80) accepts a user input in a device view 224 different from the usual one, the CPU 41a (setting unit 80) selects a device corresponding to the user input. The CPU 41a (data processing unit 83) extracts the selected device from the operation record to be analyzed. The CPU 41a (display processing unit 84) displays the waveform of the time-series data about the extracted device in the device view 224 different from the usual one. This allows the user to see when and how the device displayed in the unusual device view 224 has changed. Of the plurality of devices included in the operation record acquired at the normal time, the time series data of a predetermined device may be simultaneously displayed in the device view 224 different from the usual one. A given device corresponds to a device in a different situation than usual. In this way, for a certain device, the time-series data at the normal time and the time-series data at the irregular time (when a situation different from usual occurs) may be displayed in a comparable manner.

FIG. 22 shows a flowchart showing a setting process via the dashboard of operation record analysis executed by the CPU 41a of the data utilization unit 4a.

In S61, the CPU 41a (setting unit 80) receives a learning instruction from the user. When the CPU 41a (setting unit 80) receives the instruction to start learning according to the user input, the CPU 41a starts saving the operation record. For example, the CPU 41a (setting unit 80) changes the value of the variable assigned to the storage condition of the operation record to a value that satisfies the storage condition. The CPU 41a (setting unit 80) automatically selects the operation record saved according to the instruction to start learning as the normal operation record for learning. The CPU 41a (setting unit 80) may select the normal operation record data saved in advance according to the user input. In this case, the CPU 41a (display processing unit 84) creates display data on a screen for selecting normal operation record data in order to set a device detection algorithm and a detection threshold that are different from usual. The CPU 41a (Web server 85) provides the PC 2b with display data for displaying the selection screen. The CPU 41a (setting unit 80) accepts the user selection of the normal operation record data.

In S62, the CPU 41a (flow execution unit 81) learns the normal operation record data based on the cycle recorded in the operation record, and determines the analysis algorithm for each device. For example, the CPU 41a (flow execution unit 81) determines the analysis algorithm for each device based on the normal operation record data selected in S61 and the cycle recorded in the operation record. The CPU 41a (flow execution unit 81) may specify a steady change pattern of the device signal related to the cycle of the cycle operation from the operation record data at the normal time. The CPU 41a (flow execution unit 81) may determine the analysis algorithm for each change pattern of the specified device signal.

In S63, the CPU 41a (setting unit 80) selects the operation record data to be analyzed, which is saved according to the storage conditions. When the storage conditions for saving the operation record data to be analyzed are satisfied and the operation record data is saved, the CPU 41a (setting unit 80) automatically selects the saved operation record data as the operation record data to be analyzed. To do. The CPU 41a (setting unit 80) may select the operation record data to be analyzed according to the user input. In this case, the CPU 41a (display processing unit 84) creates display data on a screen for selecting operation record data to be analyzed, which is an object to analyze a state different from usual. The CPU 41a (Web server 85) provides the PC 2b with display data for displaying the selection screen. The CPU 41a (setting unit 80) accepts the user selection of the operation record data to be analyzed.

According to the analysis algorithm determined in S64, the CPU 41a (data processing unit 83) detects a device in which an unusual state has occurred and records it together with the occurrence time. For example, the CPU 41a (data processing unit 83) analyzes the operation record data selected in S63 according to the analysis algorithm determined in S62. The CPU 41a (data processing unit 83) analyzes the operation record data to detect a device in which an unusual state occurs, and records the device in the memory 42a together with the time when the unusual state occurs.

In S65, the CPU 41a (data processing unit 83) aggregates the occurrence status based on the occurrence time and / or the occurrence pattern of a state different from usual. The CPU 41a (data processing unit 83) aggregates the occurrence status of the unusual state based on at least one of the time when the unusual state occurs and the occurrence pattern of the unusual state.

In S66, the CPU 41a (display processing unit 84) displays the aggregation result and information on the device in which an unusual state has occurred on the dashboard. The CPU 41a (display processing unit 84) creates display data for displaying the aggregation result and information on the device in which an unusual state has occurred on the operation record analysis dashboard 221. The CPU 41a (Web server 85) provides the PC 2b with display data for displaying the updated operation record analysis dashboard 221. When the CPU 41a determines in S67 that the end condition of the operation record analysis is satisfied, the operation record analysis ends. The CPU 41a repeatedly executes the processes S63 to S66 until the end condition of the operation record analysis is satisfied.

FIG. 23 shows an example of the dashboard 241 for the data utilization application. The dashboard 241 for the data utilization application has a display unit 242 for a real-time monitoring application and a display unit 246 for an operation record analysis application. The dashboard 241 for the data utilization application is a dashboard for integrating and monitoring the set real-time monitoring application and the operation record analysis application. The dashboard 241 may display an overview of each application and may function as a portal to the dashboard corresponding to each application. When each application is set, the set application is automatically added as a display target on the dashboard 241 for the data utilization application.

The display unit 242 for a real-time monitoring application has a monitoring status screen 243 and an individual status screen 244. The graph 243a and the aggregation icon 243b are displayed on the monitoring status screen 243. Graph 243a shows the ratio of normal state, attention state, and abnormal state (alarm state) applications among the monitoring applications. In FIG. 23, the graph 243a is a pie chart, but it may be a graph of another format as long as it can display the ratio. The aggregation icon 243b represents the number of normal state, attention state, and abnormal state applications among the monitoring applications.

On the individual status screen 244, the application name 244a, the state 244b, the margin 244c, the margin trend 244d, the link button 244e, and the setting button 245 are displayed. The application name 244a represents the name of the application displayed on the individual status screen 244. The state 244b represents a monitoring state corresponding to the application name 244a. As shown in FIG. 23, there may be three types of monitoring states: normal, caution, and abnormality (alarm). In this case, different hatching may be given to each of the three types of states. Alternatively, different colors may be given to each of the three types of states, such as green in the normal case, yellow in the case of caution, and red in the case of abnormalities. Such highlighting may be adopted.

The margin 244c indicates the total margin for each application calculated based on the margin of the monitored device or variable corresponding to the application name 244a. The margin for each application may be defined, for example, to be 100 when there is a sufficient margin, 50 when the caution value is set, and 0 when the alarm value is set. For example, the total margin may be calculated by averaging the margins of each of the plurality of monitoring targets. The margin 244c may be displayed in a different display format as the distance from the value indicating the state with sufficient margin is increased. For example, a display format may be adopted in which a margin of more than 50 is displayed in black, a margin of more than 10 and 50 or less is displayed in yellow, and a margin of 10 or less is displayed in red.

The margin trend 244d represents the time course of the margin corresponding to the application name 244a. In this example, the right end of the margin trend 244d represents the current margin, and as it advances to the left, it indicates the past margin. By confirming the margin trend 244d, the user can confirm from what timing the margin has decreased. The link button 244e is a link to the dashboard 171 for the individual real-time monitoring application corresponding to the application name 244a. When the link button 244e is pressed, the CPU 41a displays the detailed monitoring status of each application on the PC 2b. The setting button 245 is a button for displaying a screen for setting the display unit 242 for the real-time monitoring application. When the setting button 245 is pressed, the CPU 41a determines whether or not the display format of the graph 243a, the display / non-display of the columns displayed on the individual status screen 244, and the margin 244c are sorted according to the size of the margin. Make settings such as according to user input.

The operation record analysis application display unit 246 has an application name 246a, a final analysis time 246b, a target operation record 246c, an abnormality detection number 246d, an abnormality detection number trend 246e, and a link button 246f. The application name 246a displays the name of the application to be displayed on the operation record analysis application display unit 246. The final analysis time 246b displays the time when the operation record analysis was last performed. The operation record analysis may include an analysis of the operation records stored at predetermined time intervals and an analysis of the operation records stored when the logging storage trigger occurs. By confirming the final analysis time 246b, the user can confirm up to what point in time the operation record has been analyzed. The target operation record 246c represents the data that was the subject of the analysis in the analysis performed at the time displayed at the final analysis time 246b.

The abnormality detection number 246d represents the number of devices and variables in which an abnormality is detected in the analysis performed at the time displayed at the final analysis time 246b. The abnormality detection number trend 246e represents the time course of the abnormality detection number detected in the operation record analysis. In this example, the right end of the abnormality detection number trend 246e represents the current abnormality detection number. In the abnormality detection number trend 246e, the number of abnormality detections in the past is shown as it progresses from the right side to the left side. By confirming the abnormality detection number trend 246e, the user can confirm from what timing the abnormality detection number has increased. The link button 246f is a link to the dashboard 221 for the driving record analysis application corresponding to the application name 246a. When the link button 246f is pressed, the CPU 41a may display the detailed result of the operation record analysis corresponding to the final analysis time 246b on the PC 2b.

FIG. 24 shows a flowchart showing an integrated monitor process that generates the data utilization application dashboard 241. In S71, the CPU 41a (data processing unit 83) determines the monitoring state for each set monitoring application. For example, the CPU 41a (data processing unit 83) determines a monitoring state representing each application for each set monitoring application. The representative monitoring state is determined from the monitoring state for each monitoring target, which is determined according to the detection algorithm defined for each device or variable to be monitored. For example, the worst monitoring state among the monitoring states for each monitoring target may be determined as the monitoring state representing the application.

In S72, the CPU 41a (data processing unit 83) aggregates the monitoring status of the monitoring application. The CPU 41a (data processing unit 83) aggregates the monitoring states representing each monitoring application for each state. Aggregating by state includes individually totaling the number of normal states, the number of attention states, and the number of abnormal states. In S73, the CPU 41a (data processing unit 83) collects a value indicating a margin for each set monitoring application. For example, the CPU 41a (data processing unit 83) collects a margin value representing each application for a monitoring application having a margin. The lowest margin among the monitoring states for each monitoring target is determined as the margin that represents the application. In S74, the CPU 41a (data processing unit 83) aggregates the values related to the abnormal occurrence state of the operation record analysis application. For example, the CPU 41a (data processing unit 83) collects the number of devices and variables in a situation different from usual.

In S75, the CPU 41a (display processing unit 84) displays the status information for each individual application and the aggregated status information on the integrated monitor dashboard (data utilization application dashboard 241). For example, the CPU 41a (display processing unit 84) creates the display data of the data utilization application dashboard 241. The CPU 41a (Web server 85) provides the PC 2b with display data for displaying the selection screen. The CPU 41a (display processing unit 84) may separately manage the screen data to which the referenced device or variable is assigned and the display target data which is the value of the referenced device or variable. In this case, the CPU 41a (Web server 85) selectively provides the screen data and the display target data among the display data according to the update request and the update schedule of the dashboard 241. The CPU 41a (Web server 85) provides display data including screen data and display target data in response to a display request of the dashboard 241. The CPU 41a (Web server 85) selectively provides the updated display target data as display data in response to the display update request of the dashboard 241.

In S76, the CPU 41a (setting unit 80) switches the display to the dashboard corresponding to each application according to the user input. For example, the CPU 41a (setting unit 80) accepts user input for switching dashboards. When the CPU 41a (setting unit 80) detects that the switching button has been pressed, it creates display data for displaying the selection screens of the dashboard 171 for the real-time monitoring application and the dashboard 221 for the operation record analysis application. Further, the CPU 41a (Web server 85) provides the PC 2b with display data for displaying the selection screen. The CPU 41a (setting unit 80) may detect that whether to display the dashboard 171 for the real-time monitoring application or the dashboard 221 for the operation record analysis application is selected on the selection screen. The CPU 41a (display processing unit 84) creates display data for displaying the selected dashboard. The CPU 41a (Web server 85) provides the PC 2b with display data for displaying the selected dashboard.

As a data utilization program, an example of a flow program created according to user input and a program module set by application setting data has been described, but the present invention is not limited to this. For example, the data utilization program may be created in a text language such as C language, or may be composed of a library written in C language and a library execution block that executes the library.

<Summary>
[Viewpoint 1]
PC2 is an example of a setting device for setting a programmable logic controller. PLC1 is an example of a programmable logic controller. The CPU 31 functions as a first execution means for executing a user program (eg, a control program). The control program is, for example, a ladder program or the like, and is a user program for executing control (eg, position control of a positioning device) which is a main purpose of PLC. The storage device 32 and the device unit 34 function as storage means which are devices or variables which are storage areas accessed by the first execution means according to the control program. The collection unit 82 functions as a collection means for collecting data designated as a collection target from the storage means. The flow execution unit 81 functions as a second execution means for executing predetermined data processing according to a data utilization program (example: flow) for time-series data collected from the storage means at different timings. A data utilization program is a user program that collects data (eg, information stored in a device or variable) specified as a collection target by a user. The data utilization program stores the device value acquired from the device in a variable, and stores this variable in a data memory (example: memory 42a). Further, the data utilization program may read the variables stored in the data memory, execute the analysis process, or create the display data. The display processing unit 84 functions as a generation means for generating display data of a dashboard that displays the execution result of the data utilization program. The Web server 85 functions as a providing means for providing display data to an external computer (eg, PC2b). The storage device 12 functions as a storage means for storing templates for display data of a plurality of dashboards and templates for a plurality of data utilization programs. The CPU 11, the operation unit 8, the dashboard selection unit 52, the selection screen 100, and the like function as a first reception means for accepting the selection of one dashboard among the plurality of dashboards. The CPU 11, the operation unit 8, the parameter specification unit 53, the setting screen 110, and the like function as a second reception means for receiving the designation of the data to be collected by the collection means. The creation unit 54 of the selected dashboard in order to display the display target data, which is the data required by executing the predetermined data processing according to the data utilization program for the data to be collected, by the selected dashboard. It functions as a creation means to create setting data including a set of a template and a template of a data utilization program associated with the selected dashboard. The transfer unit 60 functions as a transfer means for transferring the setting data to the programmable logic controller. The flow execution unit 81 may generate display target data by executing predetermined data processing on the data to be collected based on the set data. The display target data (example: wOperationRatio) is associated with the graph display component included in the display data template of the selected dashboard. Since the dashboard template and the data utilization program template are prepared in advance in this way, the user can complete the dashboard and the data utilization program simply by setting the necessary parameters for them. That is, according to the present invention, the work of creating a data utilization program for collecting control data held by the PLC and a dashboard for displaying the data utilization program is facilitated.

It is understood that the device memory can be handled by the "control program (user program)" and the "data utilization program (user program)" is a storage means that can be the target of data collection. May be good. Even if it is understood that the data memory can be handled by the "data utilization program (user program)" and is a storage means for storing data that can be displayed as the value of the display component of the "dashboard". Good.

[Viewpoint 2]
The display unit 7 may function as a display means for displaying a setting screen for accepting the selection of one dashboard among the plurality of dashboards and the designation of the data to be collected by the collection means. As shown in FIG. 7, the first reception means may accept the dashboard designation through the setting screen. As shown in FIG. 8, the second receiving means may accept the designation of the data to be collected through the setting screen. This will make it easier for users with little programming knowledge to select dashboards and specify parameters.

[Viewpoint 3]
As described with respect to the preview button 118, the storage device 12 may store dummy data input to the dashboard display data template. The CPU 11 may display a preview of the dashboard on the display unit 7 by inputting dummy data into the template of the display data of the dashboard.

[Viewpoint 4]
The display data may be display data that can be displayed on a Web browser (eg, HTML data, CSS data, Javascript (registered trademark) code). The providing means may be a Web server 85. This will allow the dashboard to be displayed even on a general computer such as PC2b.

[Viewpoint 5]
Multiple dashboards may be associated with different data processing applications (eg, loss analysis, waveform monitoring, FFT). The flow dashboard creation unit 51 may accept the selection of one data processing application among the plurality of data processing applications as the selection of the dashboard corresponding to the one data processing application. If the data utilization application consists of a dashboard and a data utilization program as described above, the selection of the application and the selection of the dashboard will be synonymous.

[Viewpoint 6]
The flow dashboard creation unit 51 selects the template of the data utilization program corresponding to the selection of the dashboard and the specification of the data to be collected from the templates of the plurality of data utilization programs, and the selected data utilization program. The data utilization program may be completed based on the template of.

[Viewpoint 7]
As shown in FIG. 1, the programmable logic controller may have a basic unit 3 and an expansion unit 4 connected to the basic unit. The basic unit 3 may have a first execution means and a storage means. Of the expansion units 4, the data utilization unit may have a collecting means, a second executing means, a generating means, and a providing means. By connecting the expansion unit 4a that operates as the data utilization unit to the basic unit 3 in this way, the user can easily realize the data utilization. In addition, the load related to data processing of the basic unit 3 is reduced.

[Viewpoints 8 to 10]
The flow dashboard creation unit 51 accepts re-editing of the display components constituting the dashboard, and among the plurality of arithmetic blocks constituting the data utilization program corresponding to the dashboard, the display components are displayed in the arithmetic blocks corresponding to the re-editing. The result of re-editing of may be reflected. For example, the flow dashboard creation unit 51 accepts re-editing of display components constituting the dashboard, and is no longer required in response to the re-editing of a plurality of arithmetic blocks constituting the data utilization program corresponding to the dashboard. The arithmetic block may be configured to be deleted or invalidated in the setting data. This will allow users to easily customize the dashboard.

The flow dashboard creation unit 51 may accept re-editing of arithmetic blocks constituting the data utilization program corresponding to the dashboard. The flow dashboard creation unit 51 may reflect the result of re-editing of the calculation block on the display component corresponding to the re-edited calculation block among the display parts constituting the dashboard. This allows the user to easily customize the data utilization program.

FIG. 13 is a diagram illustrating re-editing. In this example, the flow program is composed of a plurality of flow blocks. When any of the flow blocks is clicked, the flow dashboard creation unit 51 displays the parameter setting screen for the flow block. In this example, since the flow block for executing the loss analysis is specified, the parameter setting screen for the loss analysis is displayed. The user re-edits the parameter through the parameter setting screen.

As shown in FIG. 13, this flow program is associated with a dashboard. When the display component constituting this dashboard is clicked, the flow dashboard creation unit 51 displays the parameter setting screen of the display component. The user re-edits the parameter through the parameter setting screen.

Here, the parameter setting of the flow block has a storage destination variable of the analysis result. In this example, ResultData is set as the save destination variable of the analysis result. On the other hand, the setting parameter of the display component of the dashboard has a reference data designation unit for designating the data to be displayed on the display component. In this example, the reference data specification part and the storage destination variable of the analysis result are linked to each other. Therefore, when the storage destination variable of the analysis result is changed from ResultData to ProcessData in the flow block, the flow dashboard creation unit 51 also changes the reference data specification unit of the display component from ResultData to ProcessData. Similarly, when the reference data specification unit of the display component is changed from ResultData to ProcessData, the flow dashboard creation unit 51 also changes the storage destination variable of the analysis result from ResultData to ProcessData in the flow block. Since one change is automatically reflected in the other in this way, when the user changes one parameter, the user can save the trouble of finding and changing the other parameter.

[Viewpoint 11]
As described with respect to the additional object 117, the flow dashboard creation unit 51 may be configured to accept the addition of data to be collected by the collecting means. The flow dashboard creation unit 51 is configured to be reflected in the display component of the dashboard in the setting data and the calculation block of the data utilization program according to the addition of the data to be collected received by the second reception means. You may. The user can edit the dashboard and the data utilization program simply by instructing the user to add the data to be collected (data to be analyzed).

[Viewpoint 12]
The creation unit 54 may further have an import means for importing the setting data created for the first programmable logic controller for the second programmable logic controller. The import means duplicates the setting data created for the first programmable logic controller and edits a part of the duplicated setting data to create the setting data for the second programmable logic controller. You may. As a result, the setting data can be reused among a plurality of PLCs, so that the work load on the user can be reduced.

[Viewpoint 13]
The dashboard may be a dashboard that displays the results of loss analysis, waveform monitoring or frequency analysis. Of course, other types of data utilization applications may be adopted.

[Viewpoint 14]
The flow execution unit 81 passes the calculation result generated by the data utilization program for the first dashboard to the data utilization program for the second dashboard, and the data utilization program for the second dashboard. The analysis process may be executed for the calculation result according to the above. In this way, a plurality of data utilization applications may cooperate to provide analysis results.

[Viewpoint 15]
The creation unit 54 determines whether or not the monitoring means for monitoring the re-editing of the control program and the device name of the re-edited part of the control program and the device name included in the setting data match when the control program is re-edited. If the determination means for determination matches the device name of the re-edited part of the control program and the device name included in the setting data, the device name included in the setting data is replaced with the device name of the re-edited part of the control program. It may have means. Further, when the control program is re-edited and the storage means used in the control program is changed from the first storage means to the second storage means, the creation unit 54 determines the identification information of the first storage means ( Example: A determination means for determining whether or not the identification information of the storage means included in the setting data (the device name before re-editing) matches may be provided. When the identification information of the first storage means and the identification information of the storage means included in the setting data match, the creation unit 54 uses the identification information of the storage means included in the setting data as the identification information of the second storage means (eg). : A replacement means for replacing the device name after re-editing) may be provided. This will reduce the time and effort required to manually reflect the setting data of the data utilization application for the re-editing result of the control program.

[Viewpoint 16]
The display connected to the PC2 or PLC1 functions as a display device that displays the execution result of the data utilization program related to the data utilization executed by the programmable logic controller on the dashboard. PLC1 is an example of a PLC system.

The invention is not limited to the above-described embodiment, and various modifications and changes can be made within the scope of the gist of the invention.

Claims (16)

It is a setting device that sets the programmable logic controller.
The programmable logic controller is
The first means of executing the control program and
A storage means that is a storage area or variable accessed by the first execution means according to the control program.
A collection means that collects data designated as a collection target from the storage means, and
A second execution means that executes predetermined data processing according to a data utilization program for time-series data collected from the storage means at different timings.
A generation means for generating display data of a dashboard that displays the execution result of the data utilization program, and
A means of providing the display data to an external computer and
Have,
The setting device is
A storage means for storing templates for display data on multiple dashboards and templates for multiple data utilization programs,
The first reception means that accepts the selection of one of the plurality of dashboards, and
A second reception means that accepts the designation of data to be collected by the collection means, and
In order to display the display target data, which is the data obtained by executing the predetermined data processing according to the data utilization program, on the selected dashboard, the data to be collected is displayed on the selected dashboard. A means for creating setting data including a set of a template and the template of the data utilization program associated with the selected dashboard, and a means for creating setting data.
It has a transfer means for transferring the setting data to the programmable logic controller.
The second execution means generates the display target data by executing the predetermined data processing on the data to be collected based on the setting data.
A setting device characterized in that the display target data is associated with a graph display component included in the display data template of the selected dashboard. The setting device is
Further having a display means for displaying a setting screen for accepting the selection of one dashboard among the plurality of dashboards and the designation of the data to be collected by the collection means.
The setting according to claim 1, wherein the first receiving means accepts the designation of the dashboard through the setting screen, and the second receiving means accepts the designation of the data to be collected through the setting screen. apparatus. The storage means stores dummy data input to the display data template of the dashboard.
The setting device according to claim 2, wherein the display means displays a preview of the dashboard by inputting the dummy data into a template of display data of the dashboard. The display data is display data that can be displayed on a Web browser.
The setting device according to any one of claims 1 to 3, wherein the providing means is a Web server. The multiple dashboards are associated with different data processing applications.
Any of claims 1 to 4, wherein the first receiving means accepts a selection of one data processing application among a plurality of data processing applications as a selection of a dashboard corresponding to the one data processing application. The setting device according to item 1. The creation means selects the template of the data utilization program corresponding to the selection of the dashboard and the designation of the data to be collected from the templates of the plurality of data utilization programs, and selects the template of the data utilization program of the selected data utilization program. The setting device according to any one of claims 1 to 5, wherein the data utilization program is completed based on a template. The programmable logic controller is
Basic unit and
Has an expansion unit connected to the basic unit
The basic unit has the first executing means and the storage means.
Any one of claims 1 to 6, wherein the data utilization unit among the expansion units has the collecting means, the second executing means, the generating means, and the providing means. The setting device described in the section. The creating means accepts re-editing of the display component constituting the dashboard, and among a plurality of arithmetic blocks constituting the data utilization program corresponding to the dashboard, the display component is placed in the arithmetic block corresponding to the re-editing. The setting device according to any one of claims 1 to 7, wherein the setting device is configured to reflect the result of re-editing. The creating means accepts re-editing of display components constituting the dashboard, and among a plurality of arithmetic blocks constituting the data utilization program corresponding to the dashboard, arithmetic blocks that are no longer needed in response to the re-editing are selected. The setting device according to any one of claims 1 to 7, wherein the setting data is configured to be deleted or invalidated. The creation means accepts re-editing of the arithmetic blocks constituting the data utilization program corresponding to the dashboard, and among the display components constituting the dashboard, the display components corresponding to the re-edited arithmetic blocks are subjected to. The setting device according to any one of claims 1 to 7, wherein the setting device is configured to reflect the result of re-editing of the calculation block. The second receiving means is configured to receive the addition of data to be collected by the collecting means.
The creating means is configured to be reflected in the display component of the dashboard and the calculation block of the data utilization program in the setting data in response to the addition of the data to be collected received by the second receiving means. The setting device according to any one of claims 1 to 10, wherein the setting device is provided. The creation means further comprises an import means for importing the configuration data created for the first programmable logic controller for the second programmable logic controller.
The import means duplicates the setting data created for the first programmable logic controller and edits a part of the duplicated setting data to set the settings for the second programmable logic controller. The setting device according to any one of claims 1 to 11, wherein data is created. The setting device according to any one of claims 1 to 12, wherein the dashboard is a dashboard that displays the results of loss analysis, waveform monitoring, or frequency analysis. The second execution means passes the calculation result generated by the data utilization program for the first dashboard to the data utilization program for the second dashboard, and the data for the second dashboard. The setting device according to any one of claims 1 to 11, wherein an analysis process is executed on the calculation result according to a utilization program. The creation means
A monitoring means for monitoring the re-editing of the control program, and
When the storage means used in the control program is changed from the first storage means to the second storage means by re-editing the control program, the identification information of the first storage means and the setting data are displayed. A determination means for determining whether or not the identification information of the included storage means matches, and
When the identification information of the first storage means and the identification information of the storage means included in the setting data match, the identification information of the storage means included in the setting data is replaced with the identification information of the second storage means. The setting device according to any one of claims 1 to 12, further comprising a replacement means. Programmable logic controller and
A setting device for setting the programmable logic controller and
A display device that displays the execution result of the data utilization program related to data utilization executed by the programmable logic controller on the dashboard, and
PLC system with
The programmable logic controller is
The first means of executing the control program and
A storage means that is a storage area or variable accessed by the first execution means according to the control program.
A collection means that collects data designated as a collection target from the storage means, and
A second execution means that executes predetermined data processing according to a data utilization program for time-series data collected from the storage means at different timings.
A generation means for generating display data of a dashboard that displays the execution result of the data utilization program, and
A providing means for providing the display data to the display device, and
Have,
The setting device is
A storage means for storing templates for display data on multiple dashboards and templates for multiple data utilization programs,
The first reception means that accepts the selection of one of the plurality of dashboards, and
A second reception means that accepts the designation of data to be collected by the collection means, and
In order to display the display target data, which is the data obtained by executing the predetermined data processing according to the data utilization program, on the selected dashboard, the data to be collected is displayed on the selected dashboard. A means for creating setting data including a set of a template and the template of the data utilization program associated with the selected dashboard, and a means for creating setting data.
It has a transfer means for transferring the setting data to the programmable logic controller.
The second execution means generates the display target data by executing the predetermined data processing on the data to be collected based on the setting data.
A PLC system characterized in that the display target data is associated with a graph display component included in the display data template of the selected dashboard.

Images