WO2020217345A1 - データ処理装置、データ処理方法およびプログラム - Google Patents

データ処理装置、データ処理方法およびプログラム Download PDF

Info

Publication number
WO2020217345A1
WO2020217345A1 PCT/JP2019/017455 JP2019017455W WO2020217345A1 WO 2020217345 A1 WO2020217345 A1 WO 2020217345A1 JP 2019017455 W JP2019017455 W JP 2019017455W WO 2020217345 A1 WO2020217345 A1 WO 2020217345A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
unit
data processing
real
collection
Prior art date
Application number
PCT/JP2019/017455
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
督 那須
Original Assignee
三菱電機株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 三菱電機株式会社 filed Critical 三菱電機株式会社
Priority to CN201980095568.7A priority Critical patent/CN113711187B/zh
Priority to PCT/JP2019/017455 priority patent/WO2020217345A1/ja
Priority to JP2020528194A priority patent/JP6833116B1/ja
Publication of WO2020217345A1 publication Critical patent/WO2020217345A1/ja

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication

Definitions

  • the present invention relates to a data processing apparatus, a data processing method and a program.
  • a data processing device that collects data from FA (Factory Automation) equipment at a manufacturing site and processes and diagnoses the collected data to be useful for device control is known.
  • FA Regenery Automation
  • the process of collecting continuous data sent from the FA device requires real-time performance, whereas the process of processing / diagnosis requires high scalability and high throughput.
  • Patent Document 1 discloses a system including a hybrid OS having two types of OS, a real-time OS (Operating System) that performs real-time processing and a general-purpose OS that performs multimedia processing and the like. This system realizes high real-time performance and high reliability of a real-time OS, and high scalability and high throughput of a general-purpose OS.
  • a hybrid OS having two types of OS
  • a real-time OS Operating System
  • a general-purpose OS that performs multimedia processing and the like.
  • This system realizes high real-time performance and high reliability of a real-time OS, and high scalability and high throughput of a general-purpose OS.
  • Patent Document 1 Even if the technique described in Patent Document 1 is simply applied to a data processing apparatus that collects, processes, diagnoses, etc. data from FA equipment, the processing speed differs between the data collection process and the processing, diagnosis, etc. , It is difficult to connect the two processes and transfer the collected data, and it is difficult to bring out sufficient performance.
  • the present invention has been made in view of the above circumstances, and an object of the present invention is to achieve both real-time data collection and appropriate supply for processing / diagnosis of the collected data.
  • the data processing apparatus of the present invention operates on a data collecting unit that collects data from a device and a non-real-time OS, and operates on a data processing unit that processes data and operates on a non-real-time OS. It also includes an execution control unit that controls data collection processing by the data collection unit, data processing by the data processing unit, and provision of the data collected by the data collection unit to the data processing unit based on the data processing flow.
  • the data collection unit operates on a real-time OS and collects data from the device, and a conversion unit that operates on a non-real-time OS and converts the collected data into a data format that can be received by the execution control unit. To be equipped.
  • the figure which shows the structure of the engineering tool which concerns on embodiment The figure which shows the hardware configuration of the data processing apparatus which concerns on embodiment.
  • the figure which shows an example of the data processing flow which concerns on embodiment The figure which shows an example of the flow setting information which concerns on embodiment
  • the figure which shows the detail of the data collection part which concerns on embodiment A flowchart showing a data collection process of the real-time data processing unit according to the embodiment. Flow chart showing data collection processing of non-real-time data processing unit according to the embodiment
  • the data processing device 1 is an edge device provided at a factory site located in an edge computing area between the area of the FA device and the cloud.
  • the data processing device 1 sucks up data from the FA device, performs processing / diagnosis processing, and returns the data to the FA device.
  • this process is executed by a cloud located remotely, there is a problem that the process takes a long time. Therefore, by having the data processing device 1 take charge of the real-time data processing, the processing delay of the real-time data is prevented and the amount of data transmitted to the cloud is optimized.
  • FIG. 1 is a diagram showing a software configuration of the data processing device 1 according to the embodiment of the present invention.
  • the data processing device 1 is an industrial computer that collects data from FA devices such as production machines, sensors, and drive devices at a production site, performs various processing, diagnosis, and feeds back.
  • the data processing device 1 constructs a virtual environment in which a plurality of virtual computers are operated on a physical computer.
  • the data processing device 1 includes a host OS 3 running on the hardware 2 and a hypervisor 4 running on the host OS 3.
  • the guest OS, the real-time OS 5 and the non-real-time OS 6, are operating on the hypervisor 4, respectively.
  • a plurality of files such as application programs and user data exist on the real-time OS5 and the non-real-time OS6, respectively.
  • a real-time data processing unit 7 for performing real-time data processing is configured on the real-time OS 5.
  • a non-real-time data processing unit 8 for performing non-real-time data processing is configured on the non-real-time OS 6.
  • the hypervisor 4 is a software program for realizing a plurality of virtual environments.
  • the hypervisor 4 uses the processing power of the CPU (Central Processing Unit), RAM (Random Access Memory), ROM (Read Only Memory), hardware resources such as the recording area of the hard disk, and the real-time data processing unit 7 which is a virtual machine. Allocate to the non-real-time data processing unit 8.
  • the host OS 3 is an operating system that starts and manages the hypervisor 4.
  • the real-time data processing unit 7 and the non-real-time data processing unit 8 are virtualized computers operating on the hypervisor 4. Therefore, the real-time data processing unit 7 and the non-real-time data processing unit 8 each behave like the hardware of one computer.
  • the real-time OS 5 is an OS that can be scheduled so that a predetermined process can be executed by a predetermined time.
  • the non-real-time OS 6 is a non-real-time general-purpose OS equipped with abundant application programs. A part of a data collection unit that collects data from a device described later is provided on the real-time OS 5 that constitutes the real-time data processing unit 7. Further, on the non-real-time OS 6 constituting the non-real-time data processing unit 8, another part of the data collection unit, which will be described later, an execution control unit, a data processing unit, and an engineering tool are provided.
  • FIG. 2 shows a functional configuration provided in the real-time data processing unit 7 and a functional configuration provided in the non-real-time data processing unit 8.
  • the non-real-time data processing unit 8 includes an engineering tool 11 for setting a data processing flow described later, an execution control unit 12 for controlling data processing execution based on the data processing flow, and a storage unit 13 for storing various data. It includes a plurality of data processing units 14 that perform various data processing on the collected data.
  • the engineering tool 11, the execution control unit 12, the storage unit 13, and the data processing unit 14 operate on the non-real-time OS 6.
  • there is a data collecting unit 15 that collects data from the device 17 across both the real-time data processing unit 7 and the non-real-time data processing unit 8. Of the data collection unit 15, the portion 15A existing in the real-time data processing unit 7 operates on the real-time OS 5.
  • the portion 15B existing in the non-real-time data processing unit 8 operates on the non-real-time OS 6.
  • the first part 15A existing in the real-time data processing unit 7 of the data collecting unit 15 is the data collecting unit 15A
  • the second part 15B of the data collecting unit 15 existing in the non-real-time data processing unit 8 is present. Is called a data collection unit 15B.
  • the engineering tool 11, the execution control unit 12, and the storage unit 13 form a platform 16 for executing the data processing flow.
  • each function can be easily changed for a series of functional processes such as data collection, processing, diagnosis, and feedback.
  • a series of real-time data processing consists of a combination of data collection, processing, diagnosis, feedback, etc.
  • Data processing includes data smoothing, sharpening, FFT (Fast Fourier Transform) processing, and the like.
  • Data diagnosis includes threshold determination, pattern matching, and the like.
  • the feedback is a notification of the diagnosis result, and includes a process of writing a command such as stopping, decelerating, and restarting the equipment at the production site. This combination is called a data processing flow.
  • the engineering tool 11 sets this data processing flow.
  • the user uses the engineering tool 11 to set the combination and execution order of the data processing unit 14, the type of data exchanged between the data processing unit 14 and the data collecting unit 15, and the format.
  • the engineering tool 11 includes a UI (User Interface) unit 111 for a user to input data processing flow settings and a reception unit 112 for receiving data processing flow settings.
  • the UI unit 111 displays a screen for inputting the data processing flow setting to the user according to the control by the reception unit 112.
  • the user operates the UI unit 111 to arbitrarily set the content and number of partial processes constituting the data processing flow, the parameters required for executing the partial processes, and the data processing unit 14 for executing the partial processes.
  • the UI unit 111 sends information indicating the setting of the data processing flow input by the user's operation to the reception unit 112.
  • the UI unit 111 may be realized by a display, a keyboard, and a pointing device represented by a mouse.
  • the reception unit 112 receives the data processing flow setting from the UI unit 111 and notifies the execution control unit 12 as flow setting information indicating the setting content.
  • the flow setting information notified to the execution control unit 12 is stored in the storage unit 13.
  • the data processing unit 14 is realized by a program preset in the data processing device 1 or plug-in software prepared by the user. Each of the data processing units 14 executes partial processing as an element constituting the data processing flow. Specifically, each of the data processing units 14 acquires data input by the execution control unit 12 as a target of partial processing, and outputs the result of performing partial processing on the acquired data to the execution control unit 12.
  • the execution control unit 12 causes the data processing unit 14 and the data collection unit 15 to execute partial processing in the order according to the flow setting information. Specifically, the execution control unit 12 acquires data to be partially processed from the data processing unit 14 and the data collecting unit 15, and applies the acquired data to the data processing unit 14 or the data. It is sent to the collecting unit 15.
  • the storage unit 13 stores the flow setting information and the data definition information.
  • the data collection unit 15 collects the data output from the device 17 and sends the collected data to the execution control unit 12.
  • the data collection unit 15A and the device 17 are connected to each other so as to be able to communicate with each other via the communication path 18.
  • the communication path 18 is an industrial control network realized by a communication line installed in the factory.
  • the communication path 18 may be an information network represented by a LAN (Local Area Network).
  • the communication path 18 may be a dedicated line or a wide area network represented by the Internet.
  • the device 17 is a PLC (Programmable Logic Controller) or the like that controls a sensor, an assembly robot, a drive device, or a controlled device such as a sensor or an assembly robot.
  • the data processing device 1 transmits information requesting various data and control information to the device 17, and the device 17 transmits various information such as sensor measurement data and requested data to the data processing device 1.
  • FIG. 2 the number of connected devices is not limited to this as an example.
  • the data collection unit 15 outputs output information.
  • the output information is information related to the execution result of the data processing flow.
  • the control command sent from the execution control unit 12 is transmitted to the device 17 to be controlled as output information.
  • the output information is not limited to the control instruction, and may be a notification for notifying the occurrence of an abnormality, or may be quality control information for being stored in an external server device.
  • the data processing device 1 includes a processor 21, a main storage unit 22, an auxiliary storage unit 23, an input unit 24, an output unit 25, and a communication unit 26, as shown in FIG. Have.
  • the main storage unit 22, the auxiliary storage unit 23, the input unit 24, the output unit 25, and the communication unit 26 are all connected to the processor 21 via the internal bus 27.
  • the processor 21 includes a CPU (Central Processing Unit).
  • the processor 21 realizes various functions of the data processing device 1 by executing the program P1 stored in the auxiliary storage unit 23.
  • the main storage unit 22 includes a RAM (RandomAccessMemory).
  • the program P1 is loaded into the main storage unit 22 from the auxiliary storage unit 23.
  • the main storage unit 22 is used as a work area of the processor 21.
  • the auxiliary storage unit 23 includes a non-volatile memory typified by an EEPROM (Electrically Erasable Programmable Read-Only Memory) and an HDD (Hard Disk Drive). In addition to the program P1, the auxiliary storage unit 23 stores various data used in the processing of the processor 21. The auxiliary storage unit 23 supplies the data used by the processor 21 to the processor 21 according to the instruction of the processor 21, and stores the data supplied from the processor 21. Although one program P1 is typically shown in FIG. 4, the auxiliary storage unit 23 may store a plurality of programs, and the main storage unit 22 is loaded with a plurality of programs. You may.
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • HDD Hard Disk Drive
  • the input unit 24 includes an input key and an input device typified by a pointing device.
  • the input unit 24 acquires the information input by the user of the data processing device 1 and notifies the processor 21 of the acquired information.
  • the output unit 25 includes an output device typified by an LCD (Liquid Crystal Display) and a speaker.
  • the output unit 25 presents various information to the user according to the instruction of the processor 21.
  • the communication unit 26 includes a network interface circuit for communicating with an external device.
  • the communication unit 26 receives a signal from the outside and outputs the data indicated by this signal to the processor 21. Further, the communication unit 26 transmits a signal indicating the data output from the processor 21 to an external device.
  • the data processing flow 30 executed by the data processing device 1 is illustrated in FIG.
  • the data processing flow 30 includes a series of partial processing performed on the data collected from the device 17.
  • the partial process 311 corresponds to a process in which the data collection unit 15 collects data from the device 17, and the partial process 312 corresponds to a process in which the data processing unit 14 processes the data output as a result of the partial process 311.
  • Data processing is, for example, noise reduction or rounding.
  • the execution control unit 12 acquires the data collected as a result of the partial processing 311 from the data collecting unit 15, and sends the acquired data to the data processing unit 14 that executes the partial processing 312. Further, the execution control unit 12 acquires the data output as a result of the partial processing 312 from the data processing unit 14, and sends the acquired data to the other data processing unit 14.
  • the partial process 313 corresponds to a process in which the data processing unit 14 diagnoses the data output as a result of the partial process 312.
  • the data diagnosis is, for example, determination of a control command for the device 17 and determination of the presence or absence of an abnormality.
  • the execution control unit 12 sends data indicating a diagnosis result output as a result of the partial process 313 to the data collection unit 15 that executes the partial process 314.
  • the partial process 314 corresponds to the external output of the data indicating the diagnostic result output as a result of the partial process 313.
  • the output of the diagnosis result includes transmission of a control command to the device 17.
  • the data collection unit 15 transmits the diagnosis result to the device 17. According to the data processing flow 30 shown in FIG. 5, a series of processes including partial processes 311, 312, 313, 314 are executed every time the measurement result is output from the device 17. Then, for example, the control content for the device 17 is determined according to the noise-reduced value included in the measurement result, and the control command is transmitted.
  • FIG. 6 illustrates the flow setting information 131 stored in the storage unit 13.
  • the flow setting information 131 is information indicating the settings required to execute the data processing flow shown in FIG.
  • the flow setting information 131 corresponds to a partial processing ID (Identifier) for identifying the partial processing, a name of the partial processing, a partial processing corresponding to the pre-processing of the partial processing, and a post-processing of the partial processing.
  • It is table data that associates the partial process, the type of data input to this partial process, and the type of data output from this partial process.
  • the names of the partial treatments are described as "collection", "processing", and “diagnosis” for convenience, but for example, there are various types of "processing” such as averaging and sharpening. Therefore, in practice, IDs subdivided into these types are used as the names of partial processes.
  • the ID of the partial process is also used for the pre-process and the post-process.
  • the flow setting information 131 may include information different from the information exemplified in FIG.
  • the flow setting information 131 may include a parameter that defines the content of the partial processing. This parameter is, for example, a threshold value used for rounding, an identifier of a device for which data is collected, a cycle for collecting data, and an identifier of a device for which control commands are transmitted.
  • FIG. 7 shows the details of the data collection unit 15. As described above, the data collection unit 15 exists across the real-time data processing unit 7 operating on the real-time OS 5 and the non-real-time data processing unit 8 operating on the non-real-time OS 6.
  • the data collection unit 15A existing in the real-time data processing unit 7 is connected to the device 17 via the communication path 18 and functions as a collection execution unit that collects data from the device 17.
  • the data collection unit 15A includes a data collection execution unit 41 that collects data from the device 17, an error management unit 42 that manages error information of the collected data, and a survival management unit 43 that manages the operating state of the data collection unit 15A. To be equipped.
  • the data collection execution unit 41 collects real-time data from the device 17 via the communication path 18, for example, sensor data from the sensor.
  • the data collection execution unit 41 must collect time-series data on the order of msec from the device 17. Therefore, high speed and punctuality are required for data collection, but a non-real-time OS, which is a general-purpose OS, cannot meet these demands. Therefore, among the data collection units 15, the data collection unit 15A including the data collection execution unit 41 that collects data operates on the real-time OS 5. That is, the data collection unit 15A on the real-time data processing unit 7 side executes processing that requires real-time performance.
  • the error management unit 42 detects the occurrence of an error during the execution process of data collection, and manages the error in the data collection of the data collection unit 15A.
  • the survival management unit 43 monitors that the function of the data collection unit 15A is working normally. The survival management unit 43 detects whether the data collection execution unit 41 is operating or stopped, and manages the operating state of the data collection unit 15A.
  • the data collection unit 15B existing in the non-real-time data processing unit 8 is connected to the execution control unit 12 and functions as a conversion unit that converts data so that it can be transmitted and received to and from the execution control unit 12.
  • the data collection unit 15B is an IF (Interface) conforming unit 45 which is an interface between the data collection control unit 44 which exchanges data and controls with the execution control unit 12 and the data collection control unit 44 and the execution control unit 12. And.
  • the data collection control unit 44 receives the data sent from the data collection unit 15A on the real-time data processing unit 7 side and sends it to the execution control unit 12. Further, the feedback data diagnosed and processed by the data processing unit 14 is received from the execution control unit 12 and sent to the data collecting unit 15A. The feedback data sent to the data collecting unit 15A is fed back to the device 17 via the communication path 18.
  • the data collection control unit 44 includes a function of managing errors in data collection of the data collection unit 15B, similarly to the error management unit 42 of the real-time data processing unit 7. Further, the data collection control unit 44 includes a function of managing the operation / stop of the data collection unit 15B, similarly to the survival management unit 43 of the real-time data processing unit 7. On the other hand, the real-time data processing unit 7 does not include the data collection control unit 44. This is because the data collection execution unit 41 only sends the collected data at a specific time interval, and therefore does not need to be particularly controlled.
  • the IF conforming unit 45 converts the data into a data format that can be received by the execution control unit 12. In addition, error information and data collection setting information are also exchanged. These communication formats and data formats are predetermined as interface specifications, and the IF conforming unit 45 implements processing in accordance with these specifications. In other words, as long as the IF conforming unit 45 is implemented according to this specification, the other functional blocks of the data collecting unit 15 can be incorporated into the data processing flow no matter how they are implemented. That is, by providing the IF conforming unit 45, the user can add / delete an arbitrary data collecting unit 15 after the system is constructed according to the network to be used or the device 17 to be connected.
  • the protocol for communicating with the device 17 and the protocol for communicating with the platform 16 are different, and the IF conforming unit 45 performs conversion between them. From the above, the data collection unit 15B on the non-real-time data processing unit 8 side executes the processing required for connectivity with the execution control unit 12.
  • the data collection unit 15A on the real-time data processing unit 7 side and the data collection unit 15B on the non-real-time data processing unit 8 side are OSs that exchange data between the real-time data processing unit 7 and the non-real-time data processing unit 8.
  • the inter-communication units 50A and 50B are provided, respectively.
  • the OS-to-OS communication units 50A and 50B perform data communication between the real-time data processing unit 7 and the non-real-time data processing unit 8. Since the OSs installed in the real-time data processing unit 7 and the non-real-time data processing unit 8 are different, direct data exchange cannot be performed. Therefore, the inter-OS communication units 50A and 50B relay the data communication.
  • the OS-to-OS communication units 50A and 50B include collection data communication units 51A and 51B for transmitting and receiving collected data, error information communication units 52A and 52B for transmitting and receiving error information, and survival information communication units 53A and 53B for transmitting and receiving survival information. And.
  • the collected data communication unit 51A transmits the data collected from the device 17 by the data collection execution unit 41 to the collected data communication unit 51B on the non-real-time data processing unit 8 side. Further, the collection data communication unit 51B transmits the feedback data sent from the execution control unit 12 through the IF conforming unit 45 and the data collection control unit 44 to the collection data communication unit 51A.
  • the error information communication unit 52A transmits the error information from the error management unit 42 to the error information communication unit 52B on the non-real-time data processing unit 8 side. Further, the error information from the error management function in the data collection control unit 44 is transmitted from the error information communication unit 52B to the error information communication unit 52A.
  • the survival information communication unit 53A transmits the survival information from the survival management unit 43 to the survival information communication unit 53B on the non-real-time data processing unit 8 side. Further, the survival information from the survival management function in the data collection control unit 44 is transmitted from the survival information communication unit 53B to the survival information communication unit 53A. Survival information is information indicating an operating state. Since the data collection unit 15 straddles the OSs, the task in the real-time data processing unit 7 and the task in the non-real-time data processing unit 8 are different from each other. Therefore, either task may be stopped. Therefore, the operating states of each other are confirmed by sending information indicating that they are in the operating state of each other at regular intervals.
  • the inter-OS communication units 50A and 50B have a buffering function that absorbs a difference in processing speed due to a difference in OS. Further, the inter-OS communication units 50A and 50B have a function of adjusting the transmission speed according to the data reception status of the other communication units 50B and 50A. Due to the characteristics of the real-time OS 5 and the non-real-time OS 6, different controls are used for scheduling various processes.
  • the real-time OS assigns a high priority to a process that requires real-time performance and realizes real-time performance.
  • the data collection execution unit 41 collects data at a constant speed from the device 17. On the other hand, in the non-real-time OS, the priority may be changed depending on the execution time of the process.
  • the processing execution time may be uneven, and the processing speed may be locally biased (difference in speed).
  • the data collected by the data collection execution unit 41 may not be processed smoothly. Since the inter-OS communication units 50A and 50B have a buffering function, the data collection control unit 44 can smoothly process the data collected by the data collection execution unit 41.
  • the inter-OS communication units 50A and 50B both have a memory and transmit and receive data in a bufferable manner.
  • the memory is composed of, for example, a ring buffer.
  • the data collected from the device 17 is stored in the memory of the inter-OS communication unit 50A, and the stored data is read out and transmitted to the inter-OS communication unit 50B.
  • the data received by the collected data communication unit 51B of the OS-to-OS communication unit 50B is stored in the memory of the OS-to-OS communication unit 50B.
  • the stored data is read out, converted by the IF conforming unit 45, and then sent to the execution control unit 12.
  • the inter-OS communication unit 50B monitors the memory while data is transmitted from the inter-OS communication unit 50A.
  • the data collection control unit 44 transmits the survival information indicating the operation stop from the survival information communication unit 53B of the inter-OS communication unit 50B to the survival information communication unit 53A of the inter-OS communication unit 50A. To do.
  • the inter-OS communication unit 50A stops transmitting data.
  • the data collected by the data collection execution unit 41 is buffered in the memory of the inter-OS communication unit 50A.
  • the inter-OS communication unit 50A transmits the data buffered in the memory to the inter-OS communication unit 50B. Therefore, when the data collection control unit 44 side resumes the operation, it is possible to resume the processing without interrupting the collected data.
  • the shared memory can read and write data from both the inter-OS communication units 50A and 50B.
  • the shared memory stores data transmitted from the OS-to-OS communication unit 50A to the OS-to-OS communication unit 50B and data to be transmitted from the OS-to-OS communication unit 50B to the OS-to-OS communication unit 50A.
  • the shared memory is provided in a part of the area of the main storage unit 22.
  • the collected data communication unit 51A stores the collected data in the shared memory, and notifies the data collecting unit 15B on the non-real-time data processing unit 8 side that the collected data is stored in the shared memory.
  • the collected data communication unit 51B receives the data by receiving the notification of the data transmission and reading the data stored in the shared memory.
  • the inter-OS communication units 50A and 50B execute access to the shared memory and exclusive control.
  • the inter-OS communication unit 50A buffers the data collected from the device 17 by storing it in the shared memory.
  • the inter-OS communication unit 50A confirms whether or not there is buffering data in the shared memory, and if there is buffering data, the collection data communication unit 51A sends the collection data communication unit 51B to the collection data communication unit 51B. Notify that data will be sent to.
  • the inter-OS communication unit 50B receives the data by reading the data stored in the shared memory.
  • FIG. 8 shows the operation of the data collection process of the data collection unit 15A on the real-time data processing unit 7 side.
  • the data collection unit 15A After the data collection unit 15A is started, it performs an initialization process (step S101). Next, it is confirmed whether or not there is buffering data already collected by the data collection execution unit 41 in the memory (step S102). When there is buffering data (step S102: Yes), it is confirmed via the survival information communication unit 53A whether or not the data collection unit 15B on the non-real-time data processing unit 8 side is operating (step S103). If the data collection unit 15B is in operation (step S103: Yes), the buffering data is transmitted to the data collection unit 15B via the collection data communication unit 51A of the inter-OS communication unit 50A (step S104).
  • step S105 it is confirmed whether or not it is the data collection timing (fixed cycle, timing when a specific condition is satisfied, etc.) set in advance by the engineering tool 11 (step S105). If there is no buffering data in step S102 (step S102: No), and if the data collection unit 15B is stopped in step S103 (step S103: No), the process proceeds to step S105. If the data collection timing is at the designated timing (step S105: Yes), the data collection execution unit 41 collects data from the device 17 (step S106). If the timing is not specified (step S105: No), the process returns to step S102.
  • step S105 the data collection timing set in advance by the engineering tool 11
  • step S107 When data is collected in step S106, it is then confirmed whether or not the data collection unit 15B is operating (step S107). At this time, if the data collection unit 15B is in operation (step S107: Yes), the collected data is transmitted via the collection data communication unit 51A of the inter-OS communication unit 50A (step S108). If it is stopped (step S107: No), the collected data is buffered (step S109). In step S107, the data may be buffered even when the processing speed of the data collecting unit 15B is slow and the collected data is retained in addition to being stopped.
  • step S110 it is determined whether or not the data processing flow has been stopped by the operation by the user (step S110).
  • the operation by the user is, for example, a case where a toggle switch provided in the device is operated, or a case where a stop operation is performed from the engineering tool 11.
  • step S110: Yes the stop instruction is received via the IF conforming unit 45, and the data collection control unit 44 ends the operation of the entire data collection units 15A and 15B. If the data processing flow is not stopped by the user operation (step S110: No), the process returns to step S102.
  • step S109 If the collected data is buffered in step S109, since the buffered data exists in the memory (step S102: Yes), the process proceeds to step S103, and the operating state of the data collecting unit 15A is confirmed. If the data collection unit 15A is operating (step S103: Yes), the buffering data is transmitted to the data collection unit 15B (step S104). In this way, it is possible to absorb the difference in processing speed between the data collecting unit 15A operating on the real-time OS 5 and the data collecting unit 15B operating on the non-real-time OS 6, and to connect the processing from data collection to processing / diagnosis.
  • FIG. 9 shows the operation of the data collection process of the data collection unit 15B on the non-real-time data processing unit 8 side.
  • the initialization process is performed (step S201), and the survival information of the data collection unit 15A on the real-time data processing unit 7 side acquired via the survival information communication unit 53B is confirmed (step S202). If the data collection unit 15A is alive (if it is in operation) (step S202: Yes), the error information is subsequently confirmed via the error information communication unit 52B (step S203). If the data collection unit 15A is not alive (if it is not in operation) (step S202: No), the process of confirming the existence of step S202 is repeated until it is alive (in operation).
  • step S203 if no error has occurred (step S203: Yes), the collected data is received via the collected data communication unit 51B of the inter-OS communication unit 50B (step S204). If an error is occurring (step S203: No), the process returns to step S202, and the confirmation processing of steps S202 and S203 is repeated until the error no longer occurs.
  • step S204 When the collected data is received in step S204, the acquired data is converted for the execution control unit 12 by the IF conforming unit 45 (step S205). The converted data is transmitted to the execution control unit 12 via the IF conforming unit 45 (step S206).
  • step S207 it is determined whether or not the data processing flow has been stopped by the operation by the user.
  • the operation by the user is, for example, a case where a toggle switch provided in the device is operated, or a case where a stop operation is performed from the engineering tool 11.
  • the data collection control unit 44 receives the stop instruction via the IF conforming unit 45, and ends the operation of the entire data collection units 15A and 15B. .. If the data processing flow is not stopped by the user operation (step S207: No), the process returns to step S202, and the subsequent processing is repeated.
  • the number of data collecting units 15 is one, but the number is not limited to this, and a plurality of data collecting units 15 may be provided.
  • Each data collection unit 15 is connected to a different device 17 via a communication path 18.
  • the device 17 and the device 17 that collect the data may be different from the data collection unit 15 and the device 17 that notify the result of processing and diagnosing the collected data. For example, the case where the result of diagnosing the data collected from the sensor is fed back to the motor is applicable.
  • the hypervisor 4 operates on the host OS 3, but the present invention is not limited to this, the hypervisor 4 operates directly on the hardware 2, and the real-time 0S5 and the non-real-time OS 6 are hyper. It may be applied in a virtual environment running on the visor 4. Further, the application is not limited to the hypervisor type in which the guest OS is executed on the hypervisor, and may be applied in a virtual environment composed of the host type in which the virtualization software is executed on the host OS and the guest OS is operated.
  • the function of the data processing device 1 can be realized by dedicated hardware or by a normal computer system.
  • the program P1 executed by the processor 21 is stored in a non-temporary recording medium readable by a computer and distributed, and the program P1 is installed in the computer to configure an apparatus for executing the above-mentioned processing.
  • a recording medium for example, a flexible disk, a CD-ROM (Compact Disc Read-Only Memory), a DVD (Digital Versatile Disc), and an MO (Magneto-Optical Disc) can be considered.
  • the program P1 may be stored in a disk device of a server device on a communication network represented by the Internet, superposed on a carrier wave, and downloaded to a computer, for example.
  • the above process can also be achieved by starting and executing the program P1 while transferring it via the communication network.
  • processing can also be achieved by executing all or a part of the program P1 on the server device and executing the program while the computer sends and receives information on the processing via the communication network.
  • the means for realizing the function of the data processing device 1 is not limited to software, and a part or all thereof may be realized by dedicated hardware including a circuit.
  • the present invention can be widely applied to a data processing apparatus that collects data and processes the collected data such as processing and diagnosis.
  • 1 data processing device 2 hardware, 3 host OS, 4 hypervisor, 5 real-time OS, 6 non-real-time OS, 7 real-time data processing unit, 8 non-real-time data processing unit, 11 engineering tool, 111 UI department, 112 reception department , 12 Execution control unit, 13 storage unit, 14 data processing unit, 15, 15A, 15B data collection unit, 16 platforms, 17 devices, 18 communication paths, 21 processors, 22 main storage units, 23 auxiliary storage units, 24 input units.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Testing And Monitoring For Control Systems (AREA)
  • Debugging And Monitoring (AREA)
PCT/JP2019/017455 2019-04-24 2019-04-24 データ処理装置、データ処理方法およびプログラム WO2020217345A1 (ja)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201980095568.7A CN113711187B (zh) 2019-04-24 2019-04-24 数据处理装置、数据处理方法及储存有程序的记录介质
PCT/JP2019/017455 WO2020217345A1 (ja) 2019-04-24 2019-04-24 データ処理装置、データ処理方法およびプログラム
JP2020528194A JP6833116B1 (ja) 2019-04-24 2019-04-24 データ処理装置、データ処理方法およびプログラム

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2019/017455 WO2020217345A1 (ja) 2019-04-24 2019-04-24 データ処理装置、データ処理方法およびプログラム

Publications (1)

Publication Number Publication Date
WO2020217345A1 true WO2020217345A1 (ja) 2020-10-29

Family

ID=72941129

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2019/017455 WO2020217345A1 (ja) 2019-04-24 2019-04-24 データ処理装置、データ処理方法およびプログラム

Country Status (3)

Country Link
JP (1) JP6833116B1 (zh)
CN (1) CN113711187B (zh)
WO (1) WO2020217345A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11307561B2 (en) * 2017-02-28 2022-04-19 Sap Se Manufacturing process data collection and analytics

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009095812A1 (en) * 2008-01-28 2009-08-06 Nxp B.V. Dual operating systems on a single processor
WO2019026139A1 (ja) * 2017-07-31 2019-02-07 三菱電機株式会社 情報処理装置および情報処理方法
WO2019026136A1 (ja) * 2017-07-31 2019-02-07 三菱電機株式会社 情報処理装置および情報処理方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011257904A (ja) * 2010-06-08 2011-12-22 Hitachi Ltd 制御装置及びそのデータ処理方法
JP5562468B1 (ja) * 2013-04-26 2014-07-30 三菱電機株式会社 コントローラ、エネルギーマネジメントシステム、遠隔制御方法、及び、プログラム
DE102018003324A1 (de) * 2017-04-27 2018-10-31 Yokogawa Electric Corporation Datensammelvorrichtung, Datensammelsystem, Datenserver, Datensammelverfahren und nicht-flüchtiges computerlesbares Speichermedium

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009095812A1 (en) * 2008-01-28 2009-08-06 Nxp B.V. Dual operating systems on a single processor
WO2019026139A1 (ja) * 2017-07-31 2019-02-07 三菱電機株式会社 情報処理装置および情報処理方法
WO2019026136A1 (ja) * 2017-07-31 2019-02-07 三菱電機株式会社 情報処理装置および情報処理方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11307561B2 (en) * 2017-02-28 2022-04-19 Sap Se Manufacturing process data collection and analytics

Also Published As

Publication number Publication date
CN113711187B (zh) 2022-07-01
CN113711187A (zh) 2021-11-26
JPWO2020217345A1 (ja) 2021-05-06
JP6833116B1 (ja) 2021-02-24

Similar Documents

Publication Publication Date Title
JP4477365B2 (ja) 複数インタフェースを有する記憶装置、および、その記憶装置の制御方法
JP7161262B2 (ja) 自動化プロセスの処理の分散を最適化するシステム
US20130138818A1 (en) Method for accessing an automation system and system operating according to the method
CN107272549B (zh) 控制装置、控制方法以及记录介质
JP6833116B1 (ja) データ処理装置、データ処理方法およびプログラム
JP6927089B2 (ja) 制御装置、システムプログラム、制御方法
JP5609308B2 (ja) 画像処理システム、画像処理装置、情報処理装置、及び画像処理方法
CN112579253B (zh) 一种管理容器的方法及系统
JP5549733B2 (ja) 計算機管理装置、計算機管理システム及び計算機システム
JP2007221364A (ja) コントローラ、制御システム及び制御装置の拡張方法
CN103529816A (zh) 一种基于Qt的上位机控制系统
JP6861895B1 (ja) データ処理装置、データ処理システム、データ処理方法およびプログラム
JP6878697B2 (ja) データ処理装置、データ処理方法およびプログラム
JP6904075B2 (ja) 状態予測装置、状態予測方法および状態予測プログラム
JP2021009604A5 (zh)
JP4883492B2 (ja) 仮想マシン管理システムおよび計算機、並びに、プログラム
JP2015215669A (ja) 数値制御装置および制御システム
WO2020235174A1 (ja) 転送装置、情報処理装置、および、データ転送方法
JP5504651B2 (ja) 仮想マシンシステム、情報処理装置、リソース管理方法、プログラム及び記録媒体
JP6402484B2 (ja) 情報処理装置及び情報処理プログラム
JP7324315B2 (ja) データ収集装置
JP2009176228A (ja) 仮想マシンサーバ、仮想マシンサーバの情報保存方法及び仮想マシンサーバの情報保存用プログラム
WO2022264424A1 (ja) 制御装置及び制御方法
US20240078128A1 (en) Control device, control system, and control method
CN117319368A (zh) 一种远程控制管理方法及相关装置

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2020528194

Country of ref document: JP

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19926089

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19926089

Country of ref document: EP

Kind code of ref document: A1