KR20190080684A - System for Integrating PLC and HMI Based on Multi Core Processor - Google Patents

Abstract

According to an embodiment of the present invention, the present invention relates to a PLC and HMI integrated system based on a multi-core processor. The system formed by integrating a PLC and an HMI application into single hardware by using the multi-core processor comprises: a first core processor in which a programmable logic controller (PLC) application is executed in real time; a second core processor in which a human machine interface (HMI) server application is executed in real time; a first scheduler which schedules a first task of the PLC application to be processed by the first core processor; and a second scheduler which schedules a second task of the HMI application to be processed by the second core processor. In addition, the first scheduler has scheduling priority over the second scheduler.

Description

[0001] The present invention relates to a PLC and an HMI integrated system based on a multicore processor,

The present invention relates to an industrial facility management system, and more particularly to a PLC and an HMI.

PLC (Programmable Logic Controller) and HMI (Human Machine Interface) are required for operation and control of various facilities installed in the industrial field.

PLC is a control device used for automatic control and monitoring of industrial plants. The PLC sequentially processes the input data by the program and controls the external device connected to the PLC by using the output result. At this time, since the PLC can process the input data in real time, the output responds within a fixed time to the input condition of the set time. These PLCs can be composed of a plurality of PLCs depending on the process scale. PLC is implemented as a program so that the desired control and operation can be realized by interfacing with various external devices according to the industrial field requiring control and operation, and such program is downloaded to the PLC dedicated hardware (H / W) and performs its function .

The HMI provides the control of various controllers (DCS, instruments, etc.) including the above-mentioned PLC as an easy-to-recognize screen, and provides the necessary data in various forms including a graph. The HMI is implemented as a program so that the above-described functions are realized. In particular, recently, such HMI programs have been mainly implemented so that the functions necessary for constructing the screen can be configured in a drag-and-drop manner or only by setting, such as Visual Basic or other programs, .

FIG. 1 shows a connection relationship between a general PLC and an HMI. As shown in FIG. 1, a general PLC 100 is implemented by installing a program for PLC in PLC-dedicated hardware, and the HMI 110 is also implemented by installing a program for HMI in a separate dedicated hardware. The HMI 110 is connected via a network 120 (e.g., Ethernet, Modbus / TCP, etc. 120).

However, in the case of the general PLC and the HMI shown in FIG. 1, since the program for the function of the PLC 100 and the HMI 110 is separately installed in the dedicated hardware, the specifications of various manufacturers of the PLC and the HMI to be applied are checked There is a problem in that it is not possible to actively cope with changes in the industry direction and also it is difficult to secure various product lineups having price competitiveness.

In addition, when a communication error occurs because the PLC and the HMI have to communicate through the communication interface, it is difficult to smoothly share data between the PLC and the HMI, so that control of the industrial site can not be efficiently performed.

SUMMARY OF THE INVENTION The present invention provides a PLC and an HMI integrated system based on a multicore processor in which a PLC application and an HMI application are integrated on a single hardware using a multicore processor.

It is another object of the present invention to provide a PLC and an HMI integrated system capable of executing a PLC application prior to an HMI application.

Another object of the present invention is to provide a PLC and HMI integrated system based on a multicore processor in which a PLC application and an HMI application can communicate using a shared memory.

Another object of the present invention is to provide a multi-core processor-based PLC and an HMI integrated system capable of isolating a core processor on which a PLC application is executed from a core processor on which an HMI application is executed.

Another object of the present invention is to provide a PLC and an HMI integrated system based on a multicore processor capable of giving a PLC application access priority to a shared memory.

Another object of the present invention is to provide a PLC and HMI integrated system based on a multicore processor that can be designed with a redundant structure.

According to an aspect of the present invention, there is provided a PLC and an HMI integrated system based on a multicore processor, including: a first core processor for executing a PLC (Programmable Logic Controller) application; A second core processor in which an HMI (Human Machine Interface) server application is executed; A first scheduler for scheduling a first task of the PLC application to be processed by the first core processor; And a second scheduler for scheduling a second task of the HMI application to be processed by the second core processor, wherein the first scheduler has a scheduling priority over the second scheduler.

According to the present invention, since the PLC application and the HMI application can be simultaneously implemented on a single hardware, it is not required to investigate the specification of the hardware for the PLC application and the HMI application to operate. Therefore, It can be prevented.

In addition, according to the present invention, there is an effect that real-time processing of the PLC application can be ensured by allowing the PLC application to be executed prior to the HMI application by scheduling the task of the PLC application prior to the task of the HMI application.

According to the present invention, since the PLC application and the HMI application share data through the shared memory and a separate communication interface is not required, a communication error due to an error of the communication interface does not occur, and the PLC application and the HMI application It is possible to share the data smoothly, and the control of the industrial site can be performed efficiently.

Further, according to the present invention, since a communication interface is not required between the PLC application and the HMI application, the addition of a separate gateway or communication protocol development work for matching different communication interfaces is not required, thereby reducing system construction cost.

In addition, according to the present invention, the core processor on which the PLC application is executed is completely isolated from the core processor on which the HMI application is mounted, and the scheduling priority and the shared memory access priority are given to the PLC application, There is an effect that can be done.

In addition, according to the present invention, since the system is designed in a redundant structure, the stability of the system can be improved.

1 is a diagram showing a connection relationship between a general PLC and an HMI.
2 is a diagram illustrating a layer structure of a PLC and an HMI integrated system based on a multicore processor according to an embodiment of the present invention.
3 is a diagram showing an example of access to the shared memory of the PLC application and the HMI application when the PLC application has the priority of the access key.
4 is a diagram showing an example of allocating each new task to each core processor of the scheduler.
5 is a diagram showing a scheduling state being processed by a scheduler after a real time patch.
6 is a diagram showing an example in which a first task processed by a first core processor and a second task processed by a second core processor share an shared memory.
7 is a block diagram schematically showing the configuration of the HMI server application.
8 is a diagram showing an example of a mapping table.
9 is a diagram illustrating an example of an integrated system designed as a redundant structure according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

The meaning of the terms described herein should be understood as follows.

The word " first, "" second," and the like, used to distinguish one element from another, are to be understood to include plural representations unless the context clearly dictates otherwise. The scope of the right should not be limited by these terms.

It should be understood that the terms "comprises" or "having" does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

It should be understood that the term "at least one" includes all possible combinations from one or more related items. For example, the meaning of "at least one of the first item, the second item and the third item" means not only the first item, the second item or the third item, but also the second item and the second item among the first item, Means any combination of items that can be presented from more than one.

2 is a diagram illustrating a layer configuration of a PLC and an HMI integrated system based on a multicore processor according to an embodiment of the present invention. In one embodiment, the PLC and HMI integrated system 200 according to the present invention may be implemented as an industrial computer (IPC). The programmable logic controller (PLC) based on the industrial computer (IPC) according to the present invention can perform a deterministic function and a blue screen handling function.

The deterministic function is a function that guarantees a constant performance as in the PLC regardless of the number of application applications and the amount of network traffic, which is performed by an industrial computer. The ability of the system to guarantee a given cycle time within tolerance and whether the user can predict the time from the input request to the output to occur and have the processing capability when the process is actually done at that time . For a typical PLC, the scan period is in the range of 5-10 ms, and the tolerance is 1-4 ms.

The blue screen handling function means that the system continues to execute sequence logic even when the system is down.

2, the integrated system 200 includes a user space layer 202, an operating system (OS) space layer 204, and a device space layer 206. The user space layer 202 includes a user interface

In the user space layer 202, a PLC application 210 and an HMI application 220 are installed. The HMI application 220 may include an HMI client application 224 interfaced with the HMI server application 222 and the HMI server application 222 interlocking with the PLC application 210. In one embodiment,

The PLC application 210 performs a control operation according to logic implemented through a network interface, a digital input / output interface, and an analog input / output interface for controlling devices to be controlled. The PLC application 210 stores state data or sensing data (hereinafter referred to as "collected data") of each device collected by each device in the memory 250.

The HMI server application 222 acquires the collected data collected by the PLC application 210 from the memory 250 and provides it to the HMI client application 224. [

The HMI client application 224 shares the collected data with the HMI server application 222. In one embodiment, the HMI client application 224 includes a historical DB application 224a for recording the collection data in a time series order, a monitoring module 224a for monitoring whether the value of the collection data exceeds a predetermined threshold, An alarm DB application 224b that generates an alarm if a predetermined threshold is exceeded, and a runtime client application 224c that provides the collected data to the user via a predetermined GUI (Graphic User Interface) .

In particular, the runtime client application 224c may generate control data for controlling devices controlled by the PLC application 210 or the PLC application 210, if necessary, and may transmit the control data to the HMI server client 222. In this case, the HMI server client 222 records the control data in the memory 250 so that the PLC application 210 can share the control data.

A kernel (kernel) 230 of the integrated system 200 is disposed in the OS spatial layer 204. In one embodiment, the OS may be implemented on an open source Linux basis, and the kernel 230 may be implemented in a Linux kernel.

 The kernel 230 supports the PLC application 210 installed in the user space and the HMI application 220 to be normally operated. The kernel 230 is a core core of the OS and is a program that operates in priority to all tasks. The PLC application 210 and the HMI application 220 are operated by the operating system so that many parts such as reading a file, writing a file, or displaying a message on the screen are performed through the kernel 230.

The operation of the kernel 230 is performed by an interrupt or a system call 208. At this time, the system call 208 serves to make the function of the area of the kernel 230 available to the user, that is, to allow the processes of the respective applications 21 and 220 to access the device directly, .

2, the kernel 230 may include a file management unit 232, a device management unit 230, and a file management unit 230 for performing process management, memory management, file system management, device management, 234, a memory management unit 236, a scheduler 238, and a network device management unit 239. [

The file management unit 232 manages a plurality of file systems. Linux manages all devices including a general file in a file format, and the file management unit 232 plays a role of managing such files

The device management unit 234 controls the mutual relationship among various devices and devices in the device space layer 206. [

The memory management unit 236 manages the memory 250. In one embodiment, memory 250 may be utilized in the form of a shared memory, in which case memory manager 236 may provide an access key for accessing memory 250 to applications 210 and 220, 210, and 220, respectively.

If the HMI server application 222 simultaneously accesses the memory 250 while the PLC application 210 is accessing the memory 250, the data may be corrupted. Therefore, the memory management unit 250 according to the present invention, Uses an access key that can access the memory 250 in the kernel 230 to allow only one application at a time to access the memory 250. [

Particularly, the memory management unit 236 according to the present invention gives the PLC application 210 priority over the access keys so that the PLC application 210 can access the memory (or the memory) in advance of the HMI application 220, 250).

As described above, in the present invention, the PLC application 210 and the HMI application 220 use one access key, and the PLC application 210 gives priority to the access key to the PLC application 210, It is possible to ensure real-time control of the PLC application 210 because the access can be granted.

In accordance with this embodiment, when the HMI application 220 connects to the memory 250 and receives a connection request from the PLC application 210 to the memory 250 when performing an operation "1 " The memory management unit 250 immediately retrieves the access key from the HMI application 220 and allocates the access key to the PLC application 210. The HMI application 220 thus obtains the first time the work is stopped at the time t1, and the PLC application 210 accesses the memory 250 using the access key to perform a task of "1 ".

At this time, since the process operation cycle of the PLC application 210 is shorter than the process operation cycle of the HMI server application 224, the PLC application 222 continues to operate until the access key is retrieved from the HMI server application 224 Respectively.

The HMI server application 224 confirms the first time point t1 at which the access key is retrieved when the access key is retrieved by the memory management unit 250 and the process of the PLC application 210 is completed, When the data is provided to the server application 224, the data is read or written again after the first time point t1.

3, when the control data including the emergency stop command is generated by the HMI application 220 at the second time point t2, the control data including the emergency stop command is transmitted within a short period of time The HMI application 220 fails to record control data until the access key is retrieved from the PLC application 210 because the HMI application 220 does not have the priority of the access key. Even if the HMI application 220 has the access key, since the control data is processed in the queue of the HMI application 220 according to the first-in first-out (FIFO) method, Quot; 2 "which is the processing task of the control data including the emergency stop command must be processed at the third time point t3 after the completion of the processing of the"

In order to solve this problem, according to the present invention, when control data including an emergency stop command is generated, the HMI application 220 places the corresponding control data in the first queue of the queue so that the corresponding control data can be processed first in the queue do. The memory management unit 250 gives priority to the access key to the HMI server application 224 when generating the control data including the emergency stop command so that even if the PLC application 210 is connected to the memory 250, The HMI application 220 accesses the memory 250 with the provided access key to record the control data and then returns the access key to the memory management unit 250 do.

Accordingly, the control data including the emergency stop command can be transmitted from the HMI application 220 to the PLC application 210 without delay and processed immediately.

Referring again to FIG. 2, the scheduler 238 allocates a task according to the execution of each of the applications 210 and 220 to a plurality of core processors 240. In one embodiment, the scheduler 238 includes a first scheduler 283a for processing a first task, which is a task of the PLC application 210, and a second scheduler 283a, which is a task of the HMI server application 222, And a second scheduler 283b for processing two tasks. In addition, the scheduler 238 may further include a third scheduler 238c for processing a third task, which is a task of the HMI client application.

In FIG. 4, the first through third schedulers 238a through 238c are physically divided. However, this is only one example, and one physical scheduler performs the functions of three schedulers as shown in FIG. 4 It would be possible.

Although the second scheduler 238b and the third scheduler 238c are shown as being separated in FIG. 4, the second scheduler 238b and the third scheduler 238c may be implemented as a single scheduler.

In particular, according to the present invention, the first scheduler 283a that processes the first task, which is a task of the PLC application 210, has scheduling priority over the other schedulers 238b and 238c. Accordingly, since the first task is processed first by the first scheduler 238 rather than other tasks, the PLC application 210 can be executed first in comparison with the other applications 220.

5, the first task 410 is processed with the highest priority by the first scheduler 238a after the execution of the scheduling operation specific to the scheduler 238, and then the second scheduler 238a, The second task 420 is processed by the third task 238b and then the third task 430 and other tasks are processed by the third scheduler 238c so that the PLC application 210 is controlled first So that the operation can be performed.

On the other hand, when a new task is generated, the scheduler 238 can assign each task to any one of the core processors 240 based on the identifier of the task.

4, if the task has an identifier assigned to the PLC application 210, the first scheduler 238a determines that the task is the first task 410 of the PLC application 210 And allocates it to the first core processor 242.

If the task has an identifier assigned to the HMI server application 222, the second scheduler 238b determines that the task is the second task 420 of the HMI server application 222, (244).

If the task has an identifier assigned to the HMI client application 224, the third scheduler 238c determines that the task is the third task 430 of the HMI client application 224, To the idle core processor 246 except for the two-core processor.

The first task 410 of the PLC application 210 is all processed only by the first core processor 242 and the second task 420 of the HMI server application 222 is all processed by the second core processor 244, And the third task 430 of the HMI client application 224 may all be processed in the idle core processor 246 to transfer the PLC application 210 to the HMI server application 222 and the HMI client application 224. [ As shown in FIG.

The reason for isolating the PLC application 210 from the HMI server application 222 and the HMI client application 224 in the present invention is that in the case of the PLC application 210 the control logic or the operation logic is in operation, The PLC application 210 can not perform stable control if it affects the control operation. Therefore, the present invention allows the PLC application 210 to perform stable control by designating the core processor 242 that can only process tasks of the PLC application 210 exclusively.

In one embodiment, the scheduler 238 in accordance with the present invention may be implemented as a Linux OS (registered trademark) in order to allow PLC application 210 to operate correctly within a predetermined task execution time without being affected by any interrupt or event, Through the affinity setting of the kernel, the task of the PLC application 210 can be processed only in the first core processor 242 and can be processed in real time through a real time patch.

2, the network device management unit 239 manages the setting and operation of the network device, and the device interface 210 interfaces with the devices 240 to 260 disposed in the device space layer 206 and the interfaces .

Device space layer 206 is comprised of devices such as core processor 240, memory 250, and network device 260, and so on. In FIG. 2, only some of the devices are illustrated only for convenience of explanation, and other devices such as a hard disk and the like other than the devices shown in FIG. 2 may be disposed in the device space layer 206.

The core processor 240 executes the application. The integrated system 200 according to the present invention includes a plurality of core processors 240 so that the PLC application 210 and the HMI application 220 can both be installed and operated in one hardware (H / W) 242, 244, 246).

The first core processor 242 processes the first task of the PLC application 210 through the scheduling of the first scheduler 238a and the second core processor 244 processes the second task of the second scheduler 238b And the remaining core processors 246 except for the first and second core processors 242 and 244 process the scheduling of the third scheduler 238b And other tasks, including the third task of the HMI client application 224. At this time, one of the valid core processors 246 processes the task of the historical DB application 224a, the other of the valid core processors 246 processes the task of the alarm DB application 224b, Another of the core processors 246 may handle the task of the runtime client application 224c.

In the memory 250, collected data is recorded by the PLC application 210 or control data is recorded by the HMI server application 222. 6, the memory 250 is implemented as a shared memory so that the PLC application 210 and the HMI server application 222 share the collected data and control data through the memory 250 . Hereinafter, for convenience of explanation, the memory 250 is used in combination with the expression shared memory 250.

If the PLC application and the HMI server application are implemented in separate hardware as in the conventional case, the PLC application and the HMI server application must perform communication through the network interface, so that it may be delayed due to the error of the network interface or data sharing may not be possible .

However, since the PLC application 210 and the HMI server application 222 are installed in one hardware, the present invention can be interfaced through a method of sharing the internal memory 250 without requiring a network interface.

The PLC application 210 and the HMI server application 222 may share the metadata 500 for use of the shared memory 250 as shown in Figure 6 for use of the shared memory 250 . In the metadata 500, an address of the shared memory 250 in which the corresponding collected data is to be stored for each collected data, or an address of the shared memory 250 in which the corresponding control data is stored for each control data.

Accordingly, when the collected data is generated, the PLC application 210 refers to the metadata 500 to check the address at which the collected data is to be written, and records the collected data at the identified address. In addition, the HMI server application 222 refers to the metadata 500 when the reading time of specific collected data arrives, checks the address where the collected data is recorded, and reads the collected data from the identified address.

As described above, according to the present invention, since the PLC application 210 and the HMI server application 222 share one memory 250, unnecessary overhead such as data copying does not occur and data can be used quickly Do.

Referring again to FIG. 2, the network device 260 serves as an interface between the integrated system 200 and devices controlled by the PLC application 210.

On the other hand, as described above, the HMI server application 222 shares the collected data with the HMI client application 224. Hereinafter, the configuration of the HMI server application 222 for collecting data sharing with the HMI client application 224 will be described in more detail with reference to FIG.

7 is a block diagram showing the configuration of the HMI server application 222 for sharing collected data with the HMI client application 224. [ 7, the HMI server application 222 includes a collection data obtaining unit 610, a link forming unit 620, a monitoring unit 630, and a periodical setting unit 640.

The collection data acquisition unit 610 accesses the shared memory 250 and reads collected data from the shared memory 250 when a monitoring period set by the periodical configuration unit 640 arrives. The collected data acquisition unit 310 transfers the acquired collected data to the monitoring unit 630 or to the link forming unit 620.

The link forming unit 620 forms a link with the HMI client application 224 for sharing collected data. The link forming unit 620 receives the collected data request message from the HMI client application 224 via the formed link, generates a collected data response message according to the received collected data request message, and transmits the collected data response message to the corresponding HMI client application 224 do.

In one embodiment, the link forming unit 620 may generate a mapping table 650 and may share collected data with the HMI client application 224 with reference to the generated mapping table 650.

An example of the mapping table 650 is shown in FIG. As shown in FIG. 8, in the mapping table 650, the name of the collected data, the first identifier given by the HMI client application 224 to the collected data, the HMI server client 222 for the collected data, And a link identifier of a link formed between the HMI server application 222 and the HMI client application 224 are mapped. In this case, the first identifier may be a counting number of the corresponding collected data calculated by the HMI client application 224, and the second identifier may be a counting number of the collected data calculated by the HMI server application 222.

The link forming unit 620 receives the collection data retrieval request transmitted from the HMI client application 224 in a broadcasting manner to generate the mapping table 650 described above. The collected data search request includes the name of the collected data to be monitored by the HMI client application 224 and the first identifier assigned by the HMI client application 224 to the collected data.

If the HMI server application 224 has collected data of the name included in the collected data search request, the link forming unit 620 forms a link with the HMI client application 224 that transmitted the collected data search request, Assigns an identifier to the link, and assigns a second identifier to the collected data included in the collected data search request. Then, the link forming unit 620 generates a mapping table composed of the name, the first identifier, the link identifier, and the second identifier of the collected data included in the collected data search request.

Meanwhile, when the mapping table is generated, the HMI client application 224 that has transmitted the collected data search request also generates the name of the collected data, the first identifier, the link identifier, Generates a collected data search response composed of the second identifier and forwards it to the HMI client application 224.

Through the above-described process, the HMI server application 222 and the HMI client application 224 generate and hold a mapping table for communication with each other.

On the other hand, when the collection data monitoring request is received from the HMI client application 224, the link forming unit 620 checks the collection data to be monitored with reference to the mapping table 650. [ At this time, the collected data monitoring request is composed of the first identifier, the link identifier, and the second identifier, and the name of the collected data is not included. Therefore, the link forming unit 620 determines, as the collected data to be monitored, the collected data mapped to the first identifier, the link identifier, and the second identifier included in the collected data monitoring request in the mapping table 650 . The link forming unit 620 notifies the collected data acquisition unit 610 of the collected collected data, so that the collected data obtaining unit 610 can acquire the collected data from the shared memory 250 .

When the value of the collected data to be monitored is acquired according to the reception of the collected data monitoring request or the arrival of the monitoring period, the link forming unit 620 refers to the mapping table 650, Acquires a first identifier, a link identifier, a second identifier, and generates a collected data monitoring response consisting of the obtained first identifier, the link identifier, the second identifier, and the value of the acquired collected data and forwards it to the HMI client application 224 do.

As described above, according to the present invention, the HMI client application 224 and the link forming unit 620 do not send and receive a String main sentence such as the name of the collected data as a message when sharing the collected collected data, Since data can be shared using a message composed of the first identifier, the second identifier, and the link identifier, the overhead required for data sharing can be minimized, thereby minimizing the packet length and reducing the communication throughput .

When the value of the collected data to be monitored is received from the collected data obtaining unit 610, the monitoring unit 630 compares the value of the received collected data with the previously obtained value of the corresponding collected data, Monitor whether the value changes. If the value of the collected data is changed as a result of the monitoring, the monitoring unit 630 transmits the value of the collected data to the link forming unit 620, so that the link forming unit 620 transmits the value of the collected data to the HMI client application 224).

As described above, according to the present invention, only when the collected data value is changed through the monitoring unit 630, the value of the collected data is transmitted in an event-driven manner and the unchanged information is not transmitted. Since overhead can be minimized, overall communication throughput can be reduced.

The periodical setup unit 640 sets a period for which the collected data acquisition unit 610 acquires the collected data to be monitored from the shared memory 250. Accordingly, the collected data obtaining unit 610 reads the value of the collected data from the shared memory 250 whenever the period set by the periodical setting unit 640 arrives, and provides the read value to the monitoring unit 630.

Meanwhile, the integrated system 200 according to the present invention can be designed as a redundant structure as shown in FIG. 9 is a diagram illustrating an example of an integrated system designed as a redundant structure according to an embodiment of the present invention.

As shown in FIG. 9, the integrated system 200 according to the present invention is configured to be redundant to the master device 810 and the slave device 820 for stable operation even if there is a problem with the system function. The master device 810 and the slave device 820 perform the same operation, but the operation of the master device 810 is central. The redundancy can be effectively applied even when the integrated system 200 is expanded.

In particular, according to the present invention, each of the devices 810 and 820 may include a failure detection unit 212 to implement redundancy of the integrated system 200. The failure detection unit 212 implemented in each of the devices 810 and 810 may detect a failure occurring in hardware (H / W) such as the core processor 240 or the shared memory 250 included in each of the devices 810 and 820, Or a failure occurring in the kernel 230 of the OS.

In one embodiment, the fault detection unit 212 can determine whether the PLC application 210 is defective through application program error diagnosis, field bus status diagnosis, and input / output module status diagnosis. The fault detection unit 212 may also check the functions of the HMI server application 222, the historical DB application 224a, the alarm DB application 224b, and the runtime client application 224c. The failure detection unit 212 may diagnose defects of the kernel 230 through the system call 208 of the kernel 230 or may diagnose defects of the kernel 230 through a hardware check of the OS. In addition, the failure detection unit 212 can diagnose the core processor 2420, diagnose the shared memory 250, check the internal temperature of the system, check the status of the power supply unit, and other devices through the system call 208 of the kernel 230 And the timeout (Timeout) information of the devices to determine the defects of the devices.

When the failure detection unit 212 of the master device 810 detects that a failure has occurred in the master device 810, the failure detection unit 212 of the slave device 820 detects a failure of the master device 810 To the PLC application 210 of the slave device 820. Accordingly, the PLC application 210 of the slave device 820 performs the same input / output process that the PLC application 210 of the master device 810 has processed by switching the operation to the master.

When the failure detection unit 212 of the slave device 820 operating in the master mode detects that the slave device 820 has failed, the failure of the slave device 820 is detected by the master device 820, To the PLC application 210 of the master device 810 through the failure detection unit 212 of the master device 810. Accordingly, the PLC application 210 of the master device 810 operating in the standby mode or the slave mode switches the operation to the master again so that the input / output process that the PLC application 210 of the slave device 820 has processed .

It will be understood by those skilled in the art that the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof.

It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive. The scope of the present invention is defined by the appended claims rather than the detailed description and all changes or modifications derived from the meaning and scope of the claims and their equivalents are to be construed as being included within the scope of the present invention do.

200: Integrated system 210: PLC application
222: HMI server application 224: HMI client application
230: kernel 240: core processor
250: Memory

Claims (14)

A first core processor in which a PLC (Programmable Logic Controller) application is executed;
A second core processor in which an HMI (Human Machine Interface) server application is executed;
A first scheduler for scheduling a first task of the PLC application to be processed by the first core processor; And
And a second scheduler for scheduling a second task of the HMI server application to be processed by the second core processor,
Wherein the first scheduler has a scheduling priority over the second scheduler. The method according to claim 1,
Wherein the first scheduler receives the scheduling priority and schedules the first task in real time. The method according to claim 1,
Wherein the first scheduler schedules the new task to be assigned to the first core processor if the new task has an identifier assigned to the PLC application and the second scheduler notifies the new task that the new task has an identifier assigned to the HMI server application And isolating execution of the PLC application and the HMI application so that the new task is assigned to the second core processor if the new task is assigned to the second core processor. The method according to claim 1,
A shared memory for sharing data between the PLC application and the HMI server application; And
And a memory management unit for managing an access key for accessing the shared memory and giving the PLC application a priority of the access key. 5. The method of claim 4,
The memory management unit,
When the access request to the shared memory is received from the PLC application when the HMI server application is accessing the shared memory using the access key, the access key is retrieved from the HMI server application and provided to the PLC application PLC and HMI integrated system using multi-core CPU. 5. The method of claim 4,
The HMI server application stops reading or writing data at a first time point when the access key is retrieved by the memory management unit, and when the access key is received again from the memory management unit, And restarts reading or writing of data that has been read or stopped after the point in time. 5. The method of claim 4,
The memory management unit,
When the HMI server application receives a write request of control data including an emergency stop command from the HMI server application when the PLC application is accessing the shared memory using the access key, Wherein the HMI server application retrieves the access key from the PLC application so as to write the data in the shared memory, and provides the access key to the HMI server application. 5. The method of claim 4,
The HMI server application,
When the control data including the emergency stop command is generated, the control data including the emergency stop command is stored in the first queue of the queue processed by the first-in first-out method,
And the control data including the emergency stop command stored in the first queue of the queue is written to the shared memory when the access key is provided from the memory management unit. The method according to claim 1,
Further comprising at least one third core processor for processing the HMI client application sharing the collection data recorded in the shared memory via a link formed with the HMI server application. HMI integration system. 10. The method of claim 9,
The HMI client application
A historical DB application for recording the collected data in a time series order;
An alarm DB application that generates an alarm when the value of the collected data exceeds a predetermined threshold; And
And a runtime client application that provides the collected data to a user using a predetermined GUI. The integrated PLC and HMI system using the multi-core CPU. The method according to claim 1,
A first identifier given to the collected data by the HMI client application sharing the collected data with the HMI server client, a second identifier given to the collected data by the HMI server application, and a second identifier given to the HMI server application Further comprising a mapping table in which link identifiers of links formed between HMI client applications are mapped,
Wherein the HMI server application and the HMI client application share the collected data with reference to the mapping table. 12. The method of claim 11,
The HMI server application refers to the mapping table when a monitoring cycle of target collection data to be monitored arrives, and generates a first identifier, a link identifier, a second identifier, and a second identifier, which are mapped to the name of the target collection data, And transmits the generated collected data monitoring response to the HMI client application. The PLC and HMI integrated system utilizing the multicore CPU. 12. The method of claim 11,
Wherein the HMI server application refers to the mapping table when the value of the target collection data differs from the value obtained previously when a monitoring cycle of target collection data to be monitored arrives, And the collected data monitoring response including the identifier, the link identifier, the second identifier, and the value of the target collected data is generated and transmitted to the HMI client application. 10. The method of claim 9,
Wherein the HMI server application and the HMI client application include a name of target collection data to be monitored, a first identifier given by the HMI client application to the target collection data, a link identifier of a link formed between the HMI client application and the HMI server application And a mapping table for sharing the collected data by sharing a second identifier given by the HMI server application with respect to the target collected data. Integrated system.

Images