JP7412119B2 - Data utilization system - Google Patents

Description

The present invention relates to a data utilization system.

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

Patent No. 5661222 Japanese Patent Application Publication No. 2018-097662

Incidentally, in order to monitor the operation of the PLC and the operation of industrial machines controlled by the PLC, it is desired to collect and utilize data held by the PLC. A PLC has a basic unit (CPU unit) and an expansion unit connected to it. The basic unit controls the expansion unit by executing a user program such as a ladder program. The expansion unit controls the industrial machine according to instructions from the basic unit and returns control results to the basic unit. Here, in order to reduce the processing load on the basic unit, the inventors came up with the idea of connecting a data utilization unit to the basic unit as one of the expansion units. This will make it possible to collect all time-series data within one PLC.

By the way, a plurality of PLCs may control different industrial machines in one manufacturing line. In this case, if data can be collected and utilized from multiple PLCs, it will be easier to comprehensively monitor the entire production line. At this time, the higher-level data utilization unit collects data from a plurality of lower-level data utilization units. It is desirable that the higher-level data utilization unit collects time-series data from multiple lower-level data utilization units without exception. However, since multiple PLCs each operate asynchronously, it is not easy to collect time-series data without omission.

Therefore, an object of the present invention is to enable a higher-level data utilization unit to collect time-series data from one or more lower-level data utilization units without exception.

The present invention includes, for example,
A data utilization system having multiple data utilization units,
The upper unit among the plurality of data utilization units is
a setting means for setting specification information for specifying data to be collected for a lower unit among the plurality of data utilization units;
a collection means for collecting the data to be collected accumulated in the lower unit;
a creation unit that creates display data that displays the data collected by the collection unit or analysis results obtained by performing a predetermined analysis process on the data;
has
The lower unit further includes:
acquisition means for acquiring data acquired in a basic unit connected to the lower unit from the basic unit according to the specified information;
a buffer that is provided in the upper unit or the lower unit and stores the data acquired by the acquisition means in order to transfer the data from the lower unit to the upper unit;
has
The collection means of the upper unit is configured to read the data to be collected from the buffer ,
The data to be collected is specified by analyzing project data including a user program executed in the lower unit, and the specification information is created to include a specification of the specified data. We provide a data utilization system that is characterized by:

According to the present invention, it becomes possible for a higher-level data utilization unit to collect time-series data from one or more lower-level data utilization units without exception.

Diagram showing PLC system Diagram explaining a PC Diagram explaining a PC Diagram explaining PLC Diagram explaining the basic unit Diagram explaining data utilization unit Diagram explaining the expansion unit Diagram explaining the format of a data record Diagram explaining transfer timing Diagram explaining the format of a data record Diagram explaining information compression Diagram showing an example dashboard Flowchart showing collection and transfer method Flowchart showing collection and transfer method Flowchart showing collection and transfer methods Flowchart showing how to create a collection configuration Diagram explaining the setting UI for connection settings Diagram explaining variable editing UI Diagram explaining the collection target setting UI Flowchart showing lower unit collection processing Flowchart showing the collection process of the upper unit Diagram explaining the dashboard Diagram explaining display component setting UI Diagram explaining the arrangement of the transfer buffer Diagram explaining an example of how to use sub-buffers

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the claimed invention, and not all combinations of features described in the embodiments are essential to the invention. Two or more features among the plurality of features described in the embodiments may be arbitrarily combined. In addition, the same or similar configurations are given the same reference numerals, and duplicate explanations will be omitted. Reference symbols indicating the same or similar elements may be suffixed with a lowercase letter. When explaining something common to multiple elements, lowercase letters are omitted.

<System configuration>
First, in order to enable those skilled in the art to better understand a programmable logic controller (PLC, which may also be simply referred to as a programmable controller), the configuration and operation of a general PLC will be described.

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 Figure 1, this system includes a PC 2a for editing user programs such as ladder programs, and a PLC (programmable logic controller) 1a for comprehensively controlling various control devices installed in factories, etc. ~1c. PC is an abbreviation for personal computer. The user program may be created using a graphical programming language such as a flowchart-style motion program such as a ladder language or 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 is assumed to be a ladder program. The PLC 1 includes a basic unit 3 with a built-in CPU and one or more expansion units 4. One or more expansion units 4 can be attached to and detached from the basic unit 3.

In data utilization, the PLC 1 has an upper mode that functions as an upper system and a lower mode that functions as a lower system. For example, in FIG. 1, PLC1a is a higher-level system, and PLC1b and 1c are lower-level systems. The PLC 1a sets data to be collected in the PLCs 1b and 1c, and acquires data collected by the PLCs 1b and 1c. PLC1a is connected to PLC1b via a communication cable 9c. PLC1a is connected to PLC1c via communication cable 9d. However, the communication cable 9 may be a wired network or a wireless network.

The basic unit 3 includes a display section 5 and an operation section 6. The display section 5 can display the operating status of each expansion unit 4 attached to the basic unit 3. The display section 5 switches display contents according to the operation contents of the operation section 6. The display unit 5 normally displays current values (device values) of devices within the PLC 1, error information that has occurred within the PLC 1, and the like. A device is a name indicating an area on a memory provided for storing device values (device data), and may also 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 internal relays (auxiliary relays), timers, counters, data memories, etc. set on the user program. There are two types of device values: bit type and word type. A bit device stores a 1-bit device value. A word device stores one word of device value. Not only devices but also variables may be specified as collection targets for the data utilization program described in detail below. However, both devices and variables are storage means that hold information. Therefore, in the following description, devices also refer to variables. Note that the memory that holds the device may be called a device memory. The memory that holds the collected data may also be referred to as data memory.

The expansion unit 4 is prepared to expand the functions of the PLC 1. Each expansion unit 4 may be connected to a field device (controlled device) 10 that corresponds to the function of the expansion unit 4, so that each field device 10 is connected to the basic unit 3 via the expansion unit 4. Connected. The field device 10 may be an input device such as a sensor, a camera, or a barcode reader, or may be 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 positions a workpiece by driving a motor (field device 10), or may be a counter unit. The counter unit counts signals from an encoder (field device 10) such as a manual pulser.

The expansion unit 4a collects data to be collected from the basic unit 3 and expansion unit 4b, performs data processing on the data to be collected by executing a flow, creates data to be displayed, and displays the dashboard on the display unit 7 or PC 2. This is a data collection unit that creates display data to be displayed on the screen. The basic unit 3 is sometimes called a CPU unit. Note that a system including PLC1 and PC2 may be called a programmable logic controller system.

The PC 2a is a computer mainly operated by a programmer. On the other hand, the PC 2b is a computer mainly operated by the person in charge at the site. The PC 2a 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 a smartphone, and is an external computer that includes a display section 7 and an operation section 8 . The external computer is a computer located outside the PLC 1. A ladder program, which is an example of a user program for controlling the PLC 1, is created using the PC 2a. The created ladder program is converted into a mnemonic code within the PC 2a. 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, the PC 2a sends the 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. Note that 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 using the communication cable 9.

<Program creation support device>
FIG. 2 is a block diagram for explaining the electrical configuration of the PC 2a. As shown in FIG. 2, the PC 2a includes a CPU 11a, a display section 7a, an operation section 8a, a storage device 12a, and a communication section 13a. The display section 7a, the operation section 8a, the storage device 12a, and the communication section 13a are each electrically connected to the CPU 11a. The storage device 12a includes a RAM, ROM, HDD, and SSD, and may also 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 11a to execute the project editing program 14a stored in the storage device 12a, and edits the project data 15 through the operation unit 8a. The project creation section 16 and the project transfer section 17 are realized by the CPU 11a executing the project editing program 14a. The project creation unit 16 creates project data 15 according to user input. The project transfer unit 17 transfers the project data 15 to the PLC 1. The project data 15 includes one or more user programs (eg, ladder program), configuration information of the basic unit 3 and expansion unit 4, and the like. The configuration information includes information indicating the connection positions of multiple expansion units 4 to the basic unit 3, functions provided in the basic unit 3 (e.g. communication function and positioning function), and functions of the expansion unit 4 (e.g. shooting function). This is information that shows things like. Here, editing the project data 15 includes creating and changing (re-editing) the project data 15. The user can read out the project data 15 stored in the storage device 12a and change the project data 15 using the project editing program 14a as needed. The communication section 13a communicates with the basic unit 3 via the communication cable 9a. The project transfer section 17 transfers the project data to the basic unit 3 via the communication section 13a. The communication section 13a communicates with the expansion unit 4a via the communication cable 9b.

The variable information 19 is part of the project data 15, and is information including variables used in the user program, devices assigned to them, data types, initial values, comments, and the like. The variable information 19 is useful when setting devices to be collected when utilizing data. For example, when a list of variables is created from the variable information 19 and a user specifies any variable from the variable list, the device assigned to the specified variable is identified from the variable information 19 or the list; The device is determined to be a collection target. Note that instead of the PC 2, the data utilization unit of the PLC 1a functioning as the upper system may read the variable information 19 of the lower system and determine the collection target device. When the PC 2 functions as a setting device (program creation support device) for the three PLCs 1, the PC 2 may create the collection settings. An example of this is shown in FIG. The project data 15a is project data for the PLC 1a, and the variable information 19a is variable information for the PLC 1a. The project data 15b is project data for the PLC 1b, and the variable information 19b is variable information for the PLC 1b. The project data 15c is project data for the PLC1c, and the variable information 19c is variable information for the PLC1c. If the three PLCs 1 are set by different setting devices, the higher-level system will create the collection settings in an integrated manner. This will streamline the creation of collection settings. The collection target may be not only devices but also variables themselves.

<PC used to display the dashboard>
FIG. 3 is a block diagram for explaining the electrical configuration of the PC 2b. As shown in FIG. 3, the PC 2b includes a CPU 11b, a display section 7b, an operation section 8b, a storage device 12b, and a communication section 13b. The display section 7b, the operation section 8b, the storage device 12b, and the communication section 13b are each electrically connected to the CPU 11b. The storage device 12b includes a RAM, ROM, HDD, and SSD, and may further include a removable memory card.

The CPU 11b realizes the web browser 18 by executing the web browser program 14d. The web browser 18 accesses the setting page of the data utilization application provided by the expansion unit 4a or the dashboard page via the communication unit 13b.

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

Here, a supplementary explanation will be given regarding the expansion bus 90. This expansion bus 90 is a communication bus used for input/output refresh. The input/output refresh is a process of updating device values between the basic unit 3 and the expansion unit 4. Input/output refresh is performed each time the ladder program is executed (ie, each scan). Note that one scan cycle includes an input/output refresh execution period, a user program execution period, and an end processing execution period.

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 instructions (device values) from the basic unit 3 stored in the device. Further, the CPU 41b stores the control results of the field device 10 in a device called a buffer memory. The control results stored in the device are transferred to the basic unit 3 by input/output refresh. Furthermore, the control results stored in the device are transferred to the basic unit 3 in accordance with a read command from the basic unit 3 even if the timing is different from the input/output refresh. The memory 42 includes RAM, ROM, and the like. In particular, a storage area is reserved in the RAM to be used as a buffer memory. The memory 42 may have a buffer that temporarily holds data (eg, still image data or video data) acquired by the field device 10.

The CPU 41a of the expansion unit 4a functioning as a data utilization unit communicates with the PC 2b via the communication section 43 and the cable 9b. The data utilization unit is an expansion unit that executes a data utilization application. The data utilization application includes flows that collect control data and process data, and a dashboard that displays execution results of the flows. Note that the function of collecting control data may be realized by a user program other than the data utilization application. A flow may include a calculation block that collects data, a calculation block that performs data processing, a calculation block that creates display data, and the like. The dashboard includes graph display parts, numerical display parts, and the like. These display components may be realized using HTML data, CSS data, JavaScript (registered trademark) code, and the like. Note that a collection of HTML data, CSS data, and JavaScript (registered trademark) code may be called a Web application. In this embodiment, flows are realized by flow templates. The flow template is prepared in advance for each application, and includes one or more calculation blocks in which parameters specified by the user are set. Dashboards are also realized using templates. The dashboard template has one or more display components in which parameters specified by the user are set. Parameters include a wide variety of information such as dashboard names, device names, numerical values, and unit variable names. A unit variable is a variable used by the expansion unit 4a to hold the execution result of a flow.

●Functions realized by the CPU of the basic unit FIG. 5 shows the functions realized by the CPU 31 regarding data utilization. The execution engine 51 repeatedly executes the user program every scan cycle. The execution engine 51 may be realized by an ASIC or FPGA provided outside the CPU 31. ASIC is an abbreviation for application specific integrated circuit. FPGA is an abbreviation for field programmable gate array. These dedicated circuits can often perform specific data processing faster than a combination of a CPU and a program. The collection unit 52a collects device values to be collected from the device unit 34 during the end processing period of the scan cycle, creates a data record, and stores the data record in the first buffer 37a. Note that it is not essential to collect data during the end processing period, and the user program executed by the execution engine 51 may include a description (program code such as a trigger instruction) for collecting data. However, in the case where data is collected through end processing, there is an advantage that there is no need to change the user program. Further, the collection period may be a period specified by the collection setting 36a. By providing the first buffer 37a, the execution engine 51 is less affected by the increase in scan time due to collection and transfer processing. The device values to be collected are specified by the collection settings 36a. The collection settings 36a can be stored in the basic unit 3 by the PC 2a or the expansion unit 4a. The transfer unit 53a transfers one or more data records stored in the first buffer 37a to the expansion unit 4a via the expansion bus 90. Note that the transfer unit 53a executes the transfer process when the communication traffic on the expansion bus 90 is idle. Therefore, the transfer process is executed while avoiding the period when the execution engine 51a is performing input/output refresh or the period when data is being read from the buffer memory of the expansion unit 4 according to the read command written in the user program. . Note that the communication traffic of the expansion bus 90 is monitored by the monitoring unit 54a. Note that the compression engine 55a may compress a plurality of data records in order to shorten the data record transfer time. Note that the compression engine 55a does not need to be implemented by the CPU 31, and may be implemented by an ASIC, FPGA, or the like. In this way, by employing the first buffer 37a, it becomes possible to execute the transfer process and the user program asynchronously.

●Functions of Data Utilization Unit FIG. 6 is a diagram illustrating the functions realized by the CPU 41a of the expansion unit 4a. Note that the expansion unit 4a of the upper system may be called an upper unit, and the expansion unit 4a of the lower system may be called a lower unit. First, the functions realized by the CPU 41a of the lower unit will be explained. However, the CPU 41a of the host unit may also collect data in the PLC 1a to which it is connected.

The collection unit 52c is a function for the CPU 41a to collect data according to the collection settings 39. The collection unit 52c can be realized by the CPU 41a executing a control program such as a user program. The collection unit 52c sets the basic unit 3 so that the basic unit 3 collects the device values specified by the collection settings 39 and transfers them to the second buffer 37b of the expansion unit 4a. Note that the collection unit 52c may write the collection settings 36a of the basic unit 3 included in the collection settings 39 to the storage device 32 of the basic unit 3. The collection settings 39 can be written into the memory 42a by the PC 2 or another data utilization unit operating as a host system. It is desirable that the collection unit 52c and the data processing unit 73 basically be able to operate asynchronously. A buffer may be provided to achieve this.

The collection unit 52c may configure the expansion unit 4b so that the expansion unit 4b collects the device values specified by the collection settings 39 and transfers them to the third buffer 37c of the expansion unit 4a. By providing the second buffer 37b and the third buffer 37c, even if the processing load on the data processing section 73 changes, data can be collected without being missed. The collection unit 52c may write the collection settings 36b (FIG. 7) of the expansion unit 4b included in the collection settings 39 to the memory 42b of the expansion unit 4b. Note that these setting functions may be realized by the setting section 71. The setting unit 71 receives collection settings 39, processing settings 61, and display settings 62 from the PC 2a or PC 2b, and writes them into the memory 42a. The processing settings 61 include information and flows (programs) that define data processing to be performed on collected data by the data processing unit 73. The display settings 62 include a dashboard template (HTML data, CSS, JavaScript (registered trademark) code, etc.) that provides data processing results to the web browser 18 through the web server 70. The generation unit 74 creates dashboard display data by substituting data processing results into a dashboard template according to display settings 62 that define display components of the dashboard. The display data may be, for example, HTML data, image data, CSS (cascading style sheets), JavaScript (registered trademark) code, or the like. Examples of display components include pie chart components, bar graph components, line graph components, numerical display components, and the like. When the web page of the dashboard is accessed by the web browser 18, the web server 70 transmits dashboard display data to the web browser 18. Web browser 18 receives the display data and displays the dashboard.

Note that multiple data utilization applications may be provided. In this case, the required data and read timing may differ depending on the data utilization application. In this case, a sub-buffer may be secured in the memory 42a for each data utilization application. The collection unit 52c reads data records stored in the second buffer 37b, and stores data for the first data utilization application in the first sub-buffer 38a. The collection unit 52c reads the data records stored in the second buffer 37b, and stores data for the second data utilization application in the second sub-buffer 38b. Note that the collection unit 52c may read data records stored in the third buffer 37c and store data for the first data utilization application in the first sub-buffer 38a. The collection unit 52c may read the data records stored in the third buffer 37c, and store data for the second data utilization application in the second sub-buffer 38b. The data processing unit 73 reads data from the first sub-buffer 38a according to the first data utilization application, executes data processing, and generates a processing result. The data processing unit 73 reads data from the second sub-buffer 38b according to the second data utilization application, executes data processing, and generates a processing result. The decompression engine 75 is a function that forms a pair with the compression engine 55a of the basic unit 3 and the compression engine 55b of the expansion unit 4b. The decompression engine 75 decompresses the data compressed and transferred by the basic unit 3 and stores it in the second buffer 37b. The decompression engine 75 decompresses the data compressed and transferred by the expansion unit 4b and stores it in the third buffer 37c. This will ease communication traffic congestion on the expansion bus 90. The decompression engine 75 may be implemented using ASIC, FPGA, or the like. In this way, data transmission between the basic unit 3 and the expansion units 4a, 4b is performed via the expansion bus 90.

There are cases where multiple pieces of data are required for each data utilization application. In that case, a plurality of pieces of necessary data may be stored in a sub-buffer while maintaining a chunk of data collected in each scan in a buffer. Furthermore, when distributing data to sub-buffers, a timestamp or the like may be added to each record. As shown in FIG. 25, the second buffer 37b (which may also be the third buffer 37c) holds a chunk of collected data. One record contains the scan number, timer value (timestamp), and collected data. In this example, the collected data includes relays RL1-RL3, devices Dev1, Dev2. The first data utilization application 2501 requires relays RL1 to RL3 among the collected data. Therefore, the scan number, timer value, and relays RL1 to RL3 are read from the second buffer 37b and stored in the first sub-buffer 38a. The first data utilization application 2501 reads the scan number, timer value, and relays RL1 to RL3 from the first sub-buffer 38a to create a display screen (source data). The second data utilization application 2502 requires relay RL3 and devices Dev1 and Dev2 from among the collected data. Therefore, the scan number, timer value, relay RL3, devices Dev1, Dev2 are read from the second buffer 37b and stored in the second sub-buffer 38b. The second data utilization application 2502 reads the scan number, timer value, relay RL3, and devices Dev1 and Dev2 from the second sub-buffer 38b to create a display screen (source data). By utilizing sub-buffers in this way, it is possible to maintain the original data in the buffer without changing it. The original data held in the buffer becomes available for other purposes.

The transfer buffer 40 is used when transferring collected data between the upper system and the lower system. The transfer buffer 40 may be provided in at least one of the upper system and the lower system. For example, the data utilization unit of the PLC 1b functioning as a lower system transfers and stores time series data collected within the PLC 1b in the buffer 40. The data utilization unit of the PLC 1a, which functions as the upper system, acquires time-series data regarding the PLC 1b from the transfer buffer 40 of the lower system. If the PLC 1b operates at a higher speed than the PLC 1a, there is a possibility that the device value of a bit device that is ON only for a very short period of time cannot be obtained in the PLC 1b. Therefore, by providing the transfer buffer 40, it becomes less likely that time-series data will be omitted. This buffer arrangement may also be advantageous in cases where data processing such as statistical processing is executed in a lower system and the processing results are transferred to an upper system. The lower system receives the processing results and stores them in the buffer 40 . The host system periodically checks the transfer buffer 40. If the processing result is stored in the transfer buffer 40, the host system reads the processing result. In this case, a FIFO type would be suitable for the transfer buffer 40.

The delivery buffer 40 may be provided in the data utilization unit of the PLC 1a. The data utilization unit of PLC1b, which functions as a lower system, stores the time series data collected within PLC1b in the transfer buffer 40 of the data utilization unit of PLC1a, which is an upper system.

●Functions of the expansion unit 4b related to data utilization FIG. 7 is a diagram illustrating the functions realized by the CPU 41b of the expansion unit 4b.

The execution engine 51b executes the basic functions of the expansion unit 4b (eg, execution of motion flow in the case of a motion unit). The collection unit 52b collects the data specified by the collection settings 36 from the device unit 34b at the timing specified by the collection settings 36, and stores the data in the fourth buffer 37d. The transfer unit 53b reads the data record stored in the fourth buffer 37d at the timing specified by the collection setting 36 or at the timing when the transfer request is received by the expansion unit 4a, and transfers the data record via the expansion bus 90. , and transferred to the third buffer 37c of the expansion unit 4a. Note that the transfer unit 53b may transfer the data record at a timing when the communication traffic of the expansion bus 90 monitored by the monitoring unit 54 is low. Compression engine 55b compresses data records according to collection settings 36. That is, the transfer unit 53b may transfer the data record whose information has been compressed by the compression engine 55b to the expansion unit 4a. The compression engine 55b may be realized by the CPU 41b, but may also be realized by an ASIC or FPGA from the viewpoint of high-speed processing and reducing the processing load on the CPU 41b.

●Example of data record FIG. 8 shows a data record 91 written to the first buffer 37a by the collection unit 52a. The plurality of data records 91 is an example of time series data. In this example, the collection unit 52a collects device values with device names Dev0, Dev1, and Dev10 from the device unit 34a every scan cycle, adds the collection count and time information obtained from the timer, and creates one data. A record is created and stored in the first buffer 37a. Note that the data to be collected may be data stored in a buffer memory or device allocated to the expansion unit 4b. In this example, the first buffer 37a is a FIFO (first in, first out) type buffer. The collection count is a count value of a counter that is incremented by 1 each time one data record is collected. Since the collection count is a number assigned sequentially, it is useful for detecting data record omissions and compression.

Time information such as a timestamp is useful, for example, when displaying data acquired by the basic unit 3 and data acquired by the expansion unit 4b on a dashboard in a comparable manner. Generally, the collection timing in the basic unit 3 and the collection timing in the expansion unit 4b do not match. Therefore, in order to compare the operation of the basic unit 3 and the operation of the expansion unit 4b, information for linking the data of the basic unit 3 and the data of the expansion unit 4b is required. Generally, the basic unit 3 and the expansion units 4a and 4b can synchronize time information through inter-unit synchronization. Therefore, the basic unit 3 and the expansion unit 4b each add time information when the data records are collected to the data records, so that the data processing unit 73 can process multiple data records acquired by different units on the time axis. Can be aligned.

●Transfer timing FIG. 9 is a diagram illustrating the transfer timing of data records. As shown in FIG. 9, the PLC 1 repeatedly performs input/output refresh, user program execution, and end processing. In order to reduce the length of the scan cycle, the transfer process is performed while avoiding the input/output refresh period. Similarly, to reduce scan period elongation, transfer processing is performed avoiding the UREAD and UWRIT execution periods. UREAD is an instruction to read data from the buffer memory allocated to the expansion unit 4, and is written in the user program. Therefore, the basic unit 3 accesses the expansion unit 4 according to UREAD and acquires data from the buffer memory during the execution period of the user program. UWRIT is an instruction to write data to the buffer memory allocated to the expansion unit 4, and is written in the user program. The basic unit 3 accesses the expansion unit 4 according to UWRIT and writes data to the buffer memory during the execution of the user program.

As shown in FIG. 9, transfer processing is performed on the expansion bus 90 during the remaining transferable period excluding input/output refresh, UREAD, and UWRIT. For example, assume that the collection settings 36a have been set to transfer five data records at a time. In this case, the transfer unit 53a executes the transfer process after the accumulation of five data records in the first buffer 37a is completed, during the first transferable period or at the timing when the expansion unit 4a receives a transfer request. do.

●Changing collection settings Data collection may be performed constantly, for example, during the operating period of the factory. In this case, the collection settings used in the morning may be different from the collection settings used in the afternoon. In this case, it would be convenient to be able to easily identify which of the plurality of data records were acquired based on the first collection configuration and which data records were acquired based on the second collection configuration.

FIG. 10 shows a format of a data record 91 that can accommodate changes in collection settings midway. In this example, identification information for distinguishing between multiple collection settings is added to the data record 91. Setting identification information "1" corresponds to the first collection setting. In the first collection setting, the devices to be collected are Dev1 and Dev10. Setting identification information "2" corresponds to the second collection setting. First, in the collection settings, the devices to be collected are Dev1, Dev10, and Dev11. By adopting such a format, the data processing unit 73 can perform data processing by dividing data processing targets for each collection setting. For example, setting identification information "1" may correspond to a first data processing setting, and setting identification information "2" may correspond to a second data processing setting. The data processing unit 73 may acquire data processing settings corresponding to the setting identification information from the processing settings 61 and perform data processing on the data record according to the acquired data processing settings.

Note that a system ID may be assigned to the data record 91 by the CPU 41a when the data record 91 is stored in the transfer buffer 40. The system ID is identification information for identifying the PLCs 1a to 1c.

●Information compression FIG. 11 is a diagram illustrating information compression of data records. A data record group 91a shows data records before information compression. Here, four relay devices RL1, RL2, RL3, and RL4 are designated as collection targets. Additionally, scan numbers are used as collection counts. The counter may be time information obtained by a timer or the like (eg, a numerical value indicating a time interval from when a certain relay is turned on until it is turned off). In the data record group 91a, there is no change point in the relay device between the data record with scan number "1" and the data record with scan number "2". In other words, the data record with scan number "2" can be compressed (discarded or deleted). However, the relay device RL1 of the data record with scan number "3" and the relay device RL1 of the data record with scan number "1" are different. In this way, since scan number "3" has a change point, the data record of scan number "3" is not compressed. Since there is no relay device change point between the data record with scan number "3" and the data record with scan number "4", the data record with scan number "4" can be compressed. Similarly, since there is no relay device change point between the data record with scan number "5" and the data record with scan number "6", the data record with scan number "6" can be compressed. By performing information compression focusing on such change points, a compressed data record group 91b is realized. Each data record constituting the compressed data record group 91b has a change point.

●Example of Dashboard FIG. 12 shows the UI 130 of the web browser 18. The UI 130 includes a URL input section 131 and a dashboard display area 105. A URL assigned to the dashboard is input into the URL input section 131. The display area 105 shows data processing results obtained from the data to be collected by the data processing unit 73. In this example, waveforms of relay devices RL1 and RL2 are included. Because data records are collected every scan period, for example, if data collection continues over a day, a large number of data records will be collected. The data processing unit 73 displays a plurality of waveforms acquired for the relay device RL1 in a superimposed manner based on the rise of the relay device RL1. In this example, there is a shift in the falling timing of relay device RL1. For example, the data processing unit 73 may calculate the average value of a plurality of waveforms, and display the waveform corresponding to the average value as a thick line. There may be an acceptable range dX1 for the falling edge deviation. The data processing unit 73 may determine that the signal is passed if the timing of each fall is included in the pass range dX1. Data processing unit 73 may perform similar processing for relay device RL2. However, since the start-up deviation of relay device RL2 is not included in the pass range dX2, data processing unit 73 may determine that the relay device RL2 is not passed.

When a failure occurs in this way, the CPU 41a may send an error report email to a predetermined email address. The error report email may include a link including the URL of the dashboard. By clicking on this link, the recipient of the error report email may launch the web browser 18, display the dashboard, check the waveform, and eliminate the cause of the error.

Note that there is a motion unit as the extension unit 4b. The motion unit operates the industrial machine according to command values from the basic unit 3 and holds the operation results of the industrial machine. The command value may be, for example, the coordinates of an arm of an arm-type robot. The operation result (current value) may be the actual arm coordinates obtained by a sensor or the like. The expansion unit 4a may acquire the command value and the current value corresponding thereto from the expansion unit 4b as time series data, and display the deviation between the command value and the current value on the dashboard. The data processing unit 73 may calculate the difference between the command value and the current value, and display on the dashboard a graph showing how the difference changes over time. By checking such waveforms, the user can easily determine whether the cause of the error is due to the end of the life of a consumable item or a sudden event applied from the outside. For example, as a consumable item approaches its end of life, the waveform response may gradually become delayed. On the other hand, when an error occurs due to a sudden event, the waveform changes only at the time the event occurs. Therefore, by observing the waveform, the user will be able to discover the cause of the error and take countermeasures.

<Flowchart>
●Extension unit 4a
FIG. 13 is a flowchart showing the collection process executed by the CPU 41a of the expansion unit 4a. The CPU 41a executes the following process when a specific relay device is turned on.

In S1, the CPU 41a (setting section 71) sets the basic unit 3 and the expansion unit 4b. For example, the CPU 41a transfers the collection settings 36a for the basic unit 3 to the basic unit 3. The basic unit 3 stores the collection settings 36a in the storage device 32. The CPU 41a transfers the collection settings 36b for the basic unit 3 to the expansion unit 4b. The expansion unit 4b stores the collection settings 36b in the memory 42b.

In S2, the CPU 41a (data processing section 73 or collection section 52c) determines whether a predetermined amount of collected data is stored in the second buffer 37b or third buffer 37c (first sub-buffer 38a or second sub-buffer 38b). do. The predetermined amount is defined by processing settings 61. Here, it is sufficient to check the buffer specified by the processing settings 61, and it is not always the case that both the second buffer 37b and the third buffer 37c are checked. The CPU 41 waits until a predetermined amount of data is stored in the buffer. When a predetermined amount of data is stored in the buffer, the CPU 41a proceeds to S3.

In S3, the CPU 41a (data processing unit 73) executes data processing on a predetermined amount of data read from the buffer, and obtains a data processing result. The content of data processing is defined by processing settings 61. Data processing results are held in memory 42a.

In S4, the CPU 41a (generation unit 74) determines whether there is a dashboard display request (web access) from the web browser 18 of the PC 2b. If there is no display request, the CPU 41a proceeds to S2 and continues data collection and data processing. If there is a display request, the CPU 41a proceeds to S5.

In S5, the CPU 41a (generation unit 74) creates dashboard display data corresponding to the display request. For example, the CPU 41a creates display data by substituting the data processing results stored in the memory 42a into a dashboard template.

In S6, the CPU 41a (Web server 70) transmits display data to the Web browser 18 of the PC 2b. This allows the web browser 18 of the PC 2b to display the dashboard.

●Basic unit 3
FIG. 14 is a flowchart showing the collection process executed by the CPU 31 of the basic unit 3. When a specific relay device is turned on, the CPU 31 executes the following process.

In S11, the CPU 31 (collection unit 52a) determines whether the collection timing specified by the collection setting 36a (eg, every scan cycle, every time a trigger signal is input, every predetermined cycle) has arrived. When the collection timing arrives, the CPU 31 proceeds to S12.

In S12, the CPU 31 (collection section 52a) collects the collection target data specified by the collection settings 36a from the device section 34a and stores it in the first buffer 37a.

In S13, the CPU 31 (transfer unit 53a) determines whether the transfer conditions specified by the collection settings 36a are satisfied. The transfer condition may be, for example, the number of data records stored in the first buffer 37a. If the transfer conditions are not met, the CPU 31 returns to S11 and continues collecting data. If the transfer conditions are satisfied, the CPU 31 proceeds to S14.

In S14, the CPU 31 (monitoring unit 54a) determines whether the communication traffic on the expansion bus 90 is low. If the communication traffic is large, the CPU 31 returns to S11 and continues collecting data. If the communication traffic is small, the CPU 31 proceeds to S15.

In S15, the CPU 31 (transfer unit 53a) reads a predetermined amount of data records from the first buffer 37a and transfers them to the second buffer 37b. The predetermined amount is also defined by collection settings 36a.

●Extension unit 4b
FIG. 15 is a flowchart showing the collection process executed by the CPU 41b of the expansion unit 4b. When a specific relay device is turned on, the CPU 41b executes the following process.

In S21, the CPU 41b (collection unit 52b) determines whether the collection timing specified by the collection setting 36b (eg, every time a trigger signal is input, every predetermined period) has arrived. When the collection timing arrives, the CPU 41b proceeds to S22.

In S22, the CPU 41b (collection section 52b) collects the collection target data specified by the collection setting 36a from the device section 34a and stores it in the fourth buffer 37d.

In S23, the CPU 41b (transfer unit 53b) determines whether the transfer conditions specified by the collection settings 36b are satisfied. The transfer condition may be, for example, the number of data records stored in the fourth buffer 37d. If the transfer conditions are not met, the CPU 41b returns to S21 and continues collecting data. If the transfer conditions are satisfied, the CPU 41b proceeds to S24.

In S24, the CPU 41b (monitoring unit 54b) determines whether the communication traffic on the expansion bus 90 is low. If the communication traffic is large, the CPU 41b returns to S21 and continues collecting data. If the communication traffic is small, the CPU 41b proceeds to S25.

In S25, the CPU 41b (transfer unit 53b) reads a predetermined amount of data records from the fourth buffer 37d and transfers them to the third buffer 37c. The predetermined amount is also defined by collection settings 36b.

<Collection and utilization of data from lower-level systems by higher-level systems>
As already explained, the data utilization unit may have a higher mode and a lower mode. Here, the PLC 1a functions as a host system operating in a host mode. The PLCs 1b and 1c function as a lower system operating in a lower mode. The expansion unit 4a of the PC 2a or the PLC 1a creates collection settings 39 for the PLCs 1b and 1c.

●Creation of collection settings FIG. 16 shows a setting method executed by the CPU 11a of the PC 2a or the CPU 41a of the expansion unit 4a of the PLC 1a. Although the setting method is executed by the CPU 41a here, it may also be executed by the CPU 11a. Instructions by the user are input to the CPU 41a through the web browser of the PC 2b. The web server 70 of the CPU 41a provides a web page useful for creating the collection settings 39 and accepts user input.

In S31, the CPU 41a (setting unit 71) obtains variable information 19a to 19c of the PLCs 1a to 1c. For example, the CPU 41a displays a setting UI 1700 as shown in FIG. 17 on the display unit 7a of the PC 2b. The settings UI 1700 includes a system ID, a network address, a file name of variable information, and the like. The system ID is identification information for identifying the PLCs 1a to 1c. The network address is, for example, an IP address assigned to the expansion unit 4a of the PLCs 1b and 1c. The variable information is the file name of the file holding the variable information 19b, 19c in the PLCs 1b, 1c. The CPU 41a receives the system ID, network address, and file name of variable information through the setting UI 1700, creates connection setting information, and stores it in the memory 42a. The CPU 41a connects to the PLC 1b, which is a lower system, according to the network address included in the connection setting information, and reads out the variable information 19b. The CPU 41a connects to the PLC 1c, which is a lower system, according to the network address included in the connection setting information, and reads the variable information 19c. When the CPU 11a executes the settings, the CPU 11a reads variable information 19a to 19c from the storage device 12a.

FIG. 18 shows a variable editing UI 1800 for creating variable information 19. The CPU 11a of the PC 2a extracts global variables and local variables from the project data 15, and creates variable information 19 including a list of the extracted variables. The variable information 19 includes, for example, information such as a variable name, a data type of the variable, a device name assigned to the variable (assigned device), and an initial value. The user edits the variable information 19 by operating the operation unit 8a. The variable information 19 may constitute a part of the project data 15 or may be independent from the project data 15. In any case, the variable information 19 is transferred from the PC 2a to the PLC 1. This allows the CPU 41a of the higher-level system to acquire the variable information 19 of the lower-level system from the lower-level system. The variable information 19 also includes the system ID of each PLC.

In S32, the CPU 41a (setting unit 71, web server 70) displays the setting UI to be collected on the display unit 7a of the PC 2b. The CPU 41a (web server 70) transmits a web page corresponding to the settings UI to the PC 2b. On the other hand, when the CPU 11a executes settings, the CPU 11a displays a settings UI on the display unit 7a.

In S33, the CPU 41a (setting unit 71, web server 70) accepts the designation of the collection target etc. through the collection target setting UI. The CPU 41a (Web server 70) accepts user input via HTTP communication. On the other hand, when the CPU 11a executes the settings, the CPU 11a receives user input through the operation unit 8a.

In S34, the CPU 41a (setting unit 71) creates collection settings 39 based on the designation of collection targets and the like. On the other hand, when the CPU 11a executes the settings, the CPU 11a creates the collection settings 39 according to user input.

In S35, the CPU 41a (setting unit 71) transfers the collection settings 39 to the lower system (eg, PLC1b, PLC1c). On the other hand, when the CPU 11a executes the settings, the CPU 11a transfers the collection settings 39 to the PLCs 1a to 1c.

FIG. 19 shows a collection target setting UI 1900. The settings UI 1900 includes a pull-down menu 1901 for selecting a system to be set, and a collection target designation section 1902. The CPU 41a obtains the system ID from the variable information 19 and lists the system ID in the pull-down menu 1901. In this example, "PLC1b" is selected as the system ID, but "PLC1c" or "PLC1a" may also be selected. The CPU 41a reads out the variable information 19b associated with the system ID specified by the pull-down menu 1901 from the memory 42a, and causes the collection target specification section 1902 to reflect the variable information 19b. The collection target designation unit 1902 has a pull-down menu 1903 for selecting variables or devices to be collected. The CPU 41a lists variable names and device names included in the variable information 19b associated with the PLC 1b in a pull-down menu 1903. The CPU 41a may accept specifications of data types of variables and devices. The storage destination designation unit 1904 accepts the designation of the name of the buffer that stores the data to be collected (eg, the transfer buffer 40 of the PLC 1b or the transfer buffer 40 of the PLC 1a). The CPU 41a may accept a designation of the buffer type (eg, FIFO, ring, etc.). The CPU 41a creates the collection settings 39 using the specification information received through the settings UI 1900.

●Collection operation in the lower system FIG. 20 is a flowchart showing the collection operation in the lower system. Note that processes that are the same as or similar to those already described are given the same reference numerals and will be briefly described. Regarding data collection within the PLC 1a, the PLC 1a collects data according to the flowchart shown in FIG.

In S1, the CPU 41a (setting unit 71) of the lower system sets the basic unit 3 and expansion unit 4 of the lower system according to the collection settings 39 created by the higher system or PC 2a.

In S2, the CPU 41a (data processing section 73 or collection section 52c) determines whether a predetermined amount of collected data is stored in the second buffer 37b or third buffer 37c (first sub-buffer 38a or second sub-buffer 38b). do. The predetermined amount is defined by processing settings 61. Here, it is sufficient to check the buffer specified by the processing settings 61, and it is not always the case that both the second buffer 37b and the third buffer 37c are checked. The CPU 41 waits until a predetermined amount of data is stored in the buffer. When a predetermined amount of data is stored in the buffer, the CPU 41a proceeds to S3.

In S3, the CPU 41a (data processing unit 73) executes data processing on a predetermined amount of data read from the buffer, and obtains a data processing result. The content of data processing is defined by processing settings 61. Data processing results are held in memory 42a. In FIG. 20, S9 is provided next to S3.

In S9, the CPU 41a (data processing unit 73 or collection unit 52c) stores the data specified by the collection settings 39 (e.g. data collected in the PLC 1 and data processing results) in the transfer buffer 40 specified by the collection settings 39. do. The delivery buffer 40 may be provided in the data utilization unit (expansion unit 4a) of the lower system, or may be provided in the data utilization unit (expansion unit 4a) of the upper system. The location of the transfer buffer 40 is specified by the collection settings 39.

●Collection operation in the upper system FIG. 21 is a flowchart showing the collection operation in the lower system. Note that processes that are the same as or similar to those already described are given the same reference numerals and will be briefly described.

In S41, the CPU 41a (collection unit 52c) of the host system determines whether the read conditions included in the collection settings 39 of the host system are satisfied. The read condition may be a regular timing, or may be that a predetermined amount of data is stored in the transfer buffer 40. When the read conditions are satisfied, the CPU 41a proceeds to S42.

In S42, the CPU 41a (data processing unit 73 or collection unit 52c) reads data from the transfer buffer 40. The CPU 41a of the host system executes S3 to S6 on the data acquired from the PLCs 1a to 1c. Although the amount of data increases, the basic processing flow remains the same.

Before executing data processing, the CPU 41a may integrate the time-series data collected within the PLC 1a and the time-series data collected within the PLCs 1b and 1c using time stamps. This will make it easier to compare data acquired by different PLCs 1a to 1c at the same time.

●Use of variable information The dashboard that displays collected time-series data and its analysis results has multiple display parts. On the other hand, the PC 2 may have variable information 19a to 19c. Therefore, the PC 2 may use the variable information 19a to 19c to facilitate the setting of display components that make up the dashboard.

FIG. 22 shows an example of the dashboard 120. In FIG. 22, a legend section 121 shows the colors assigned to the data to be analyzed and the analysis results. The graph section 122 includes one or more graphs that display data processing results such as loss analysis. The type of graph may be prepared in advance for each dashboard. The analysis result display section 123 displays data processing results such as loss analysis. Display targets displayed on the analysis result display section 123 may also be prepared in advance for each dashboard. The current state display section 124 shows the current state of the PLC 1. The current status display section 124 may be prepared individually for each of the PLCs 1a, 1b, and 1c. The PLC selection section 125 is a pull-down menu for selecting a PLC whose data processing results are to be displayed on the dashboard among the PLCs 1a, 1b, and 1c. In this example, since PLC1b is selected in PLC selection section 125, dashboard 120 displays data processing results for PLC1b. When the PLC 1c is selected in the PLC selection unit 125, the CPU 41a switches the display data so that the dashboard 120 displays the data processing results for the PLC 1c.

The CPU 41a and the CPU 11a of the PC 2 may set the dashboard 120. When setting the dashboard 120, the CPU 11a may display a preview of the dashboard 120 on the display unit 7a. Here, when the CPU 11a detects that any display component is right-clicked by the pointer 101, it may display a setting UI for the display component.

FIG. 23 is a diagram showing the settings UI 2300. The settings UI 2300 is a UI for setting the display component that is right-clicked in the preview. The reference destination designation unit 2301 accepts designation of variables and device values to be displayed on display components. When "PLC1b" is input to the reference destination designation unit 2301, the CPU 11a sets the variable information 19b as a search target for variables and the like. When "PLC1b" followed by "." and "E" are input through the operation unit 8a, the CPU 11a extracts variables starting with "E" from the variable information 19b, and inputs the name "ErrorNo" of the extracted variable. It is input to the reference destination designation section 2301. In other words, the user can specify a variable name without inputting the entire variable name. In this way, by using the variable information 19, setting of the dashboard may be facilitated.

<Summary>
[Viewpoint 1]
As shown in FIG. 1, according to this embodiment, a data utilization system having a plurality of data utilization units (eg, expansion units 4a of PLCs 1a to 1c) is provided. The CPU 41a and the setting unit 71 in the upper unit (e.g. expansion unit 4a of PLC 1a) among the plurality of data utilization units (example: expansion unit 4a of PLC 1b, 1c) It functions as a setting means for setting specification information (eg, collection settings 39) that specifies data to be collected. The CPU 41a and the collection unit 52c function as a collection unit that collects data to be collected (eg, device values, variables, analysis results, etc.) accumulated in lower units. The data to be collected may form time-series data. The data processing unit 73 and the generation unit 74 function as a creation unit that creates display data that displays data collected by the collection unit or analysis results obtained by performing a predetermined analysis process on the data. . The lower unit may be an expansion unit that constitutes a programmable logic controller (eg, PLC 1b, 1c), but may also be another unit. The CPU 41a and the collection unit 52c of the PLCs 1b and 1c function as an acquisition means for acquiring data acquired in the basic unit 3 connected to the lower unit from the basic unit 3 according to the specified information. The transfer buffer 40 is an example of a buffer that is provided in an upper unit or a lower unit and stores data acquired by the acquisition means in order to transfer the data from the lower unit to the upper unit. The collection means (eg, collection section 52c or data processing section 73) of the upper unit is configured to read data to be collected from the buffer. By employing such a transfer buffer 40, it will be possible to collect time-series data without omission. Furthermore, it will be possible to transfer the data to be collected between the upper unit and the lower unit without executing a complicated handshake.

[Viewpoint 2]
As shown in FIG. 24(A), the lower unit may have a transfer buffer 40. The lower units write data collected within the lower system and data processing results obtained within the lower system to the transfer buffers 40b and 40c. The upper unit collects data from the transfer buffers 40b and 40c of the lower unit. The creation means (eg, data processing section 73) of the upper unit functions as an analysis means that performs a predetermined analysis process on the data to be collected collected from the transfer buffers 40a and 40b. Note that the display data may include an analysis result of a predetermined analysis process executed in the higher-level unit. Since the lower unit has the transfer buffer 40, data collection is less likely to be missed even if the lower unit operates faster than the upper unit.

As shown in FIG. 24(B), the upper unit may have a transfer buffer 40a. The lower unit writes data collected within the lower system and data processing results obtained within the lower system to the transfer buffer 40a of the upper unit. The upper unit reads data from the transfer buffer 40a of the upper unit and executes data processing. In this case as well, omissions in data collection are less likely to occur. The transfer buffer 40a may be provided separately for the PLC1b and the PLC1c. When one transfer buffer 40a is provided in common for PLC1b and PLC1c, it is necessary for the upper unit to arbitrate between data writing from PLC1b and data writing from PLC1b. On the other hand, if separate transfer buffers 40a are provided for PLC1b and PLC1c, such arbitration will become unnecessary. Further, the upper unit can handle the transfer buffer 40a for PLC1b and the transfer buffer 40a for PLC1c in the same manner as the second buffer 37b and third buffer 37b.

[Viewpoint 3]
The lower unit may further include a generation unit (eg, CPU 41a of PLC 1b, 1c) that generates data to be collected based on the data acquired by the acquisition unit. The generation means may include an analysis means (eg, data processing section 73) that executes a predetermined analysis process. In this case, the data to be collected can include the analysis results of a predetermined analysis process. Furthermore, the display data can include analysis results of predetermined analysis processing performed in the lower unit. By executing the analysis process in the lower unit in this way, the computational load on the upper unit is reduced. It is also thought that omissions in data collection will be less likely to occur.

[Viewpoint 4]
The setting means (for example, the setting unit 71 of the PLC 1a) specifies the data to be collected by analyzing the project data 15 including the user program executed in the lower unit, and specifies the data to be collected so as to include the specification of the specified data. Specification information (eg, collection settings 39) may be created. This will reduce the burden on the user when creating specification information.

[Viewpoint 5]
The setting means (for example, the setting unit 71 of the PLC 1a) identifies variables that are candidates for collection by analyzing the project data 15, and stores the variable specified by the user or the variable concerned among the identified variables. Specification information may be created to include the device that is used. This will reduce the burden on the user when creating specification information. In addition, it will be possible to specify not only device values but also variables as collection targets.

[Viewpoint 6]
The acquisition means (eg, the collecting unit 52c of the PLC 1b, 1c) may assign identification information (eg, system ID) of a lower unit to the data to be collected and store the data in the transfer buffer 40. This will make it easier for the higher-level unit to distinguish between time-series data collected from multiple lower-level units.

[Viewpoint 7]
The upper unit may be a computer different from the programmable logic controller.
The upper unit may be an expansion unit in another programmable logic controller (eg, PLC 1a) that is different from the programmable logic controller (eg, PLC 1b, 1c) that includes the lower unit. In this case, the manufacturer that delivers PLC1a to the customer, the manufacturer that delivers PLC1b to the customer, and the manufacturer that delivers PLC1c to the customer may be different or may be the same.

[Viewpoint 8]
A plurality of PLCs 1a to 1c may control a production line for workpieces (products manufactured in a factory). PLC1b functions as a first programmable logic controller that controls a first industrial machine (eg, field device 10 of PLC1b) arranged upstream in a workpiece production line. Moreover, the expansion unit 4 of PLC1b functions as a first lower unit mounted on PLC1b. PLC1c functions as a second programmable logic controller that controls a second industrial machine (eg, field device 10 of PLC1c) placed downstream in the production line. The PLC1bc expansion unit 4 functions as a second lower unit mounted on the PLC1c. In this case, the data to be collected from the first lower unit and the second lower unit may include work identification information for identifying each work. Workpiece identification information such as a barcode or QR code (registered trademark) may be affixed or engraved on the workpiece. One of the field devices 10 may be a code reader. In this case, the time series data stored in the transfer buffer 40 will include the work identification information acquired by the code reader. The creation means (for example, the CPU 41a of the PLC 1a) of the upper unit refers to the work identification information of the data collected from the first lower unit and the data collected from the second lower unit, thereby creating a Data may be integrated into. This will make it possible to easily obtain analysis data for each workpiece based on data acquired across multiple PLCs.

[Viewpoint 9]
The data to be collected from the first lower unit (example: expansion unit 4 of PLC 1b) and the second lower unit (example: expansion unit 4 of PLC 1c) include a time indicating the collection time of each data. Stamps may also be included. That is, the CPUs 41a of the PLCs 1b and 1c may add such a timestamp to the time-series data and store it in the transfer buffer 40. The creation means (for example, the CPU 41a of the PLC 1a) integrates data with similar time stamps by referring to the time stamps of the data collected from the first lower unit and the data collected from the second lower unit. You may. This will be useful for comparing time series data that are close in time.

[Viewpoint 10]
The creation means (for example, the CPU 41a of the PLC 1a) shifts the time stamp of one of the data collected from the first lower unit and the second lower unit by a certain period of time. After that, the data may be integrated based on the timestamp.

[Viewpoint 11]
As explained using FIG. 22 and FIG. 23, the CPUs 11a and 41a and the reference destination specifying unit 2301 function as a specifying means for specifying collected data for the display component of the dashboard that displays display data. You may. As explained with reference to FIG. 23, when associating display data with display parts of the dashboard, the CPUs 11a and 41a and the reference destination specifying unit 2301 add variables or devices obtained by analyzing the project data 15 to the display data. may be displayed as a candidate. This will reduce the burden on the user in specifying data to be displayed on the display component.

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

Claims (14)

A data utilization system having multiple data utilization units,
The upper unit among the plurality of data utilization units is
a setting means for setting specification information for specifying data to be collected for a lower unit among the plurality of data utilization units;
a collection means for collecting the data to be collected accumulated in the lower unit;
a creation unit that creates display data that displays the data collected by the collection unit or analysis results obtained by performing a predetermined analysis process on the data;
has
The lower unit further includes:
acquisition means for acquiring data acquired in a basic unit connected to the lower unit from the basic unit according to the specified information;
a buffer that is provided in the upper unit or the lower unit and stores the data acquired by the acquisition means in order to transfer the data from the lower unit to the upper unit;
has
The collection means of the upper unit is configured to read the data to be collected from the buffer ,
The data to be collected is specified by analyzing project data including a user program executed in the lower unit, and the specification information is created to include a specification of the specified data. A data utilization system characterized by: the lower unit has the buffer;
The creation means of the upper unit includes an analysis means for executing the predetermined analysis process on the data to be collected collected from the buffer,
2. The data utilization system according to claim 1, wherein the display data includes an analysis result of the predetermined analysis process executed in the higher-level unit. The lower unit further includes:
a generation means for generating the data to be collected based on the data acquired by the acquisition means;
The generation means includes an analysis means for executing the predetermined analysis process,
The data to be collected includes the analysis results of the predetermined analysis process,
The data utilization system according to claim 1, wherein the display data includes an analysis result of the predetermined analysis process executed in the lower unit. The setting means identifies variables that are candidates for collection by analyzing the project data, and sets the specified variables to include a variable designated by the user or a device storing the variable among the identified variables. The data utilization system according to claim 1, wherein the data utilization system is configured to create information. The data utilization system according to any one of claims 1 to 4 , wherein the acquisition means adds identification information of the lower unit to the data to be collected and stores the data in the buffer. . 6. The data utilization system according to claim 1, wherein the upper unit is an expansion unit in a programmable logic controller different from the programmable logic controller including the lower unit. As the lower unit,
a first lower unit installed in a first programmable logic controller that controls a first industrial machine located upstream in a workpiece production line;
and a second lower unit mounted on a second programmable logic controller that controls a second industrial machine located downstream in the production line,
The data to be collected respectively collected from the first lower unit and the second lower unit include work identification information for identifying each work,
The creation means integrates data for each work by referring to the work identification information for each of the data collected from the first lower unit and the data collected from the second lower unit. 7. The data utilization system according to claim 1, wherein the data utilization system is configured as follows. The lower unit includes a first lower unit and a second lower unit,
The data to be collected respectively collected from the first lower unit and the second lower unit include a time stamp indicating the collection time of each data,
The creation means integrates data having similar time stamps by referring to the time stamps of the data collected from the first lower unit and the data collected from the second lower unit. 7. The data utilization system according to claim 1, wherein the data utilization system is configured as follows. The creation means shifts the time stamp of one of the data collected from the first lower unit and the second lower unit by a certain time, and then 9. The data utilization system according to claim 8 , wherein data integration is executed based on the time stamp. further comprising specifying means for specifying the collected data to a display component of a dashboard that displays the display data,
3. The designation means, when associating the display data with a display component of the dashboard, displays a variable or a device obtained by analyzing the project data as a candidate for the display data. 10. The data utilization system according to any one of 1 to 9 . A data utilization system having multiple data utilization units,
The upper unit among the plurality of data utilization units is
a setting means for setting specification information for specifying data to be collected for a lower unit among the plurality of data utilization units;
a collection means for collecting the data to be collected accumulated in the lower unit;
a creation unit that creates display data that displays the data collected by the collection unit or analysis results obtained by performing a predetermined analysis process on the data;
has
The lower unit further includes:
acquisition means for acquiring data acquired in a basic unit connected to the lower unit from the basic unit according to the specified information;
a buffer that is provided in the upper unit or the lower unit and stores the data acquired by the acquisition means in order to transfer the data from the lower unit to the upper unit;
has
The collection means of the upper unit is configured to read the data to be collected from the buffer,
The data utilization system is characterized in that the acquisition means adds identification information of the lower unit to the data to be collected and stores the data in the buffer. A data utilization system having multiple data utilization units,
The upper unit among the plurality of data utilization units is
a setting means for setting specification information for specifying data to be collected for a lower unit among the plurality of data utilization units;
a collection means for collecting the data to be collected accumulated in the lower unit;
a creation unit that creates display data that displays the data collected by the collection unit or analysis results obtained by performing a predetermined analysis process on the data;
has
The lower unit further includes:
acquisition means for acquiring data acquired in a basic unit connected to the lower unit from the basic unit according to the specified information;
a buffer that is provided in the upper unit or the lower unit and stores the data acquired by the acquisition means in order to transfer the data from the lower unit to the upper unit;
has
The collection means of the upper unit is configured to read the data to be collected from the buffer,
The upper unit includes a programmable logic controller including the lower unit.
A data utilization system characterized in that is an expansion unit in a different programmable logic controller. A data utilization system having multiple data utilization units,
The upper unit among the plurality of data utilization units is
a setting means for setting specification information for specifying data to be collected for a lower unit among the plurality of data utilization units;
a collection means for collecting the data to be collected accumulated in the lower unit;
a creation unit that creates display data that displays the data collected by the collection unit or analysis results obtained by performing a predetermined analysis process on the data;
has
The lower unit further includes:
acquisition means for acquiring data acquired in a basic unit connected to the lower unit from the basic unit according to the specified information;
a buffer that is provided in the upper unit or the lower unit and stores the data acquired by the acquisition means in order to transfer the data from the lower unit to the upper unit;
has
The collection means of the upper unit is configured to read the data to be collected from the buffer,
As the lower unit,
a first lower unit installed in a first programmable logic controller that controls a first industrial machine located upstream in a workpiece production line;
a second lower unit mounted on a second programmable logic controller that controls a second industrial machine located downstream in the manufacturing line;
has
The data to be collected respectively collected from the first lower unit and the second lower unit include work identification information for identifying each work,
The creation means integrates data for each work by referring to the work identification information for each of the data collected from the first lower unit and the data collected from the second lower unit. A data utilization system characterized by being configured as follows. A data utilization system having multiple data utilization units,
The upper unit among the plurality of data utilization units is
a setting means for setting specification information for specifying data to be collected for a lower unit among the plurality of data utilization units;
a collection means for collecting the data to be collected accumulated in the lower unit;
a creation unit that creates display data that displays the data collected by the collection unit or analysis results obtained by performing a predetermined analysis process on the data;
has
The lower unit further includes:
acquisition means for acquiring data acquired in a basic unit connected to the lower unit from the basic unit according to the specified information;
a buffer that is provided in the upper unit or the lower unit and stores the data acquired by the acquisition means in order to transfer the data from the lower unit to the upper unit;
has
The collection means of the upper unit is configured to read the data to be collected from the buffer,
The lower unit includes a first lower unit and a second lower unit,
The data to be collected respectively collected from the first lower unit and the second lower unit include a time stamp indicating the collection time of each data,
The creation means integrates data having similar time stamps by referring to the time stamps of the data collected from the first lower unit and the data collected from the second lower unit. A data utilization system characterized by being configured as follows.

Images