DISPLAY PROGRAM, CLIENT DEVICE, NETWORK SYSTEM, AND DISPLAY CONTROL METHOD

Abstract

The program causes a support terminal (10) connected via a network to a PLC (23) having the function of a server unit (231) that distributes information to function as a client unit (11) that receives information indicating the operating status of the PLC (23) from the server unit (231), a display control unit (13) that causes a display unit (141) to display an image indicating the operating status using an icon corresponding to the PLC (23), a UI unit (14) that accepts operations on the icon, and a receiving unit (15) that receives from the PLC (23) an execution program (233) to be executed by the PLC (23) and a log (234) of execution data used in executing the execution program (233) when an operation is accepted by the UI unit (14). The display control unit (13) causes the execution program (233) and the log (234) received by the receiving unit (15) to be displayed on the display unit (141).

Description

[Technical field]

[0001] The present disclosure relates to a display program, a client device, a network system, and a display control method. [Background technology]

[0002] In FA (Factory Automation) sites, systems are constructed in which FA devices provided by various manufacturers are connected via a network. In such networks, communication standards that can be commonly used without depending on the FA devices or their manufacturers are becoming more widespread. One known example of this type of communication standard is OPC UA (Open Platform Communications Unified Architecture) (see, for example, Patent Document 1).

[0003] Patent Document 1 describes a process control system connected to a programmable logic controller (PLC) via OPC UA that detects a trigger bit that is turned ON in the PLC when a process on a production line is completed, and reads data from the PLC. The process control system also records and retrieves data between the PLC and a database. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2009-245435 A Summary of the Invention [Problem to be solved by the invention]

[0005] As typified by preventive maintenance and post-maintenance, a user may need to verify the operation history of a PLC. When a user checks data acquired from a PLC in the technology of Patent Document 1, the user is required to be familiar with database operations in order to read data from the database.

[0006] In addition, the process control system described in Patent Document 1 can acquire specific data from the data held by the PLC and record it in a database, but the data required by the user performing the verification work is not necessarily recorded in the database. Therefore, the user must use a separate tool to access the PLC and use the diagnostic or monitoring function for the PLC, which places a heavy burden on the user in verifying the operation history of the PLC.

[0007] The present disclosure has been made in light of the above-mentioned circumstances, and aims to reduce the workload required to verify the operation history of a PLC. [Means for solving the problem]

[0008] In order to achieve the above object, a display program disclosed herein causes a computer connected via a network to a programmable controller having a server function of encrypting and distributing information conforming to a predetermined information model to function as: client means for receiving information indicating the occurrence of an abnormality in the programmable controller in association with a time from the server; display control means for displaying on a display means an image including an icon corresponding to the occurrence of an abnormality in the programmable controller; user interface means for accepting operations on the icon; and receiving means for receiving from the programmable controller, when an operation is accepted by the user interface means, an execution program executed by the programmable controller and a log indicating the progress of execution data used when executing the execution program, The client means receives information including a value of a node in an information model and a status code associated with the value of the node; The display control means includes: displaying, on a display means, the occurrence of an abnormality notified as a node value and the occurrence of an abnormality indicated by a status code in different formats;When the execution program and the log received by the receiving means are displayed on the display means, the execution data at the time associated with the occurrence of the abnormality is displayed first together with a time seek bar, and the execution data corresponding to the time designated on the time seek bar is displayed. Effect of the Invention

[0009] According to the present disclosure, the user interface means accepts operations on the icons, the receiving means receives the execution program and the execution data log from the programmable controller, and the display control means displays the execution program and the log on the display means. Therefore, the user does not need to be familiar with databases, and can visually check the execution program and the execution data log. Therefore, the workload of verifying the operation history of the PLC can be reduced. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing a configuration of a network system according to an embodiment; [Diagram 2] FIG. 1 is a diagram showing a hardware configuration of an FA apparatus according to an embodiment. [Diagram 3] FIG. 2 is a diagram showing the functional configuration of a support terminal and a PLC according to an embodiment. [Figure 4] FIG. 1 is a diagram showing a first example of information distributed from a server device according to an embodiment; [Diagram 5] FIG. 11 is a diagram showing a second example of information distributed from the server device according to the embodiment; [Figure 6] FIG. 11 is a diagram showing a third example of information distributed from the server device according to the embodiment; [Figure 7] FIG. 1 is a diagram for explaining a log of an execution program and execution data according to an embodiment. [Figure 8] FIG. 1 is a diagram showing an example of a configuration diagram of a network system displayed by a UI unit according to an embodiment; [Figure 9] FIG. 13 is a diagram showing a first example of an operation performed on a UI unit according to an embodiment; [Figure 10] FIG. 1 is a diagram showing an example of details related to one server device displayed by a UI unit according to an embodiment; [Figure 11] FIG. 11 is a diagram showing a second example of an operation performed on the UI unit according to the embodiment; [Figure 12] FIG. 13 is a diagram showing an example of an execution program and a log displayed by a UI unit according to an embodiment; [Figure 13] FIG. 11 is a diagram showing a third example of an operation performed on the UI unit according to the embodiment; [Figure 14] FIG. 1 is a diagram showing a first example of a file according to an embodiment; [Figure 15] FIG. 2 is a diagram showing a second example of a file according to an embodiment; [Figure 16] 1 is a flowchart showing a display control process according to an embodiment. [Figure 17] FIG. 13 is a diagram showing a configuration of a support terminal according to a modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, a network system according to an embodiment of the present disclosure will be described in detail with reference to the drawings.

[0012] Embodiment 1, a network system 100 according to the present embodiment is a system that supports a user who uses a support terminal 10 to verify the operation history of a PLC 23. The network system 100 is constructed as a part of a control system that controls equipment in a factory using a network 30. This control system implements, for example, a manufacturing line, a processing line, an inspection line, and other processing steps.

[0013] The network system 100 includes communication devices 21 and 22 corresponding to a control device that controls equipment or a controlled device that is an object of control, a PLC 23 corresponding to a control device, and a support terminal 10 connected to the communication devices 21 and 22 and the PLC 23 via a network 30. The network 30 is an industrial network typified by a field network.

[0014] The control system for controlling the devices may include devices and apparatuses not shown. For example, the communication device 21, which corresponds to the controlled device, may be controlled by a control device not shown, and the communication device 22 and the PLC 23, which correspond to the control device, may control the devices not shown. The network system 100 can be said to be a control system in which a server that provides information via the network 30 and a client that acquires the information are extracted.

[0015] The communication devices 21, 22 and the PLC 23 have a server function. Hereinafter, the communication devices 21, 22 and the PLC 23 may be referred to as the server device 20 without distinction. The support terminal 10 corresponds to a client device having a client function for acquiring information from the server device 20. The support terminal 10 corresponds to a user interface terminal that provides the information acquired from the server device 20 to the user and presents information on the operation history of the PLC 23 to the user, thereby assisting the user in verifying the operation history. The support terminal 10 may be any of a PC represented by an industrial PC (Personal Computer), a tablet terminal, and a smartphone, or may be a dedicated user interface device in an FA system, also called a programmable display.

[0016] Each of the server device 20 and the support terminal 10 is configured with hardware elements for functioning as a computer. In detail, as shown in Fig. 2, an FA device 40 corresponding to each of the server device 20 and the support terminal 10 has a processor 41, a main memory unit 42, an auxiliary memory unit 43, an input unit 44, an output unit 45, and a communication unit 46. The main memory unit 42, the auxiliary memory unit 43, the input unit 44, the output unit 45, and the communication unit 46 are all connected to the processor 41 via an internal bus 47.

[0017] The processor 41 includes a CPU (Central Processing Unit) or an MPU (Micro Processing Unit) as a processing circuit. The processor 41 executes a program P1 stored in the auxiliary storage unit 43 to realize various functions and execute the processes described below. The program P1 of the support terminal 10 corresponds to a so-called engineering tool, and corresponds to an example of a display program that causes the support terminal 10 to function as described below.

[0018] The main memory unit 42 includes a RAM (Random Access Memory). The program P1 is loaded into the main memory unit 42 from the auxiliary memory unit 43. The main memory unit 42 is used as a working area for the processor 41.

[0019] The auxiliary storage unit 43 includes a non-volatile memory represented by an EEPROM (Electrically Erasable Programmable Read-Only Memory) and an HDD (Hard Disk Drive). The auxiliary storage unit 43 stores various data used in the processing of the processor 41 in addition to the program P1. The auxiliary storage unit 43 supplies the data used by the processor 41 to the processor 41 according to an instruction from the processor 41. The auxiliary storage unit 43 also stores data supplied from the processor 41. The auxiliary storage unit 43 of the PLC 23 also stores an execution program for executing the control processing in addition to the program P1. The execution program is, for example, a ladder program or a program created using a high-level language such as the C language, and is executed by the processor 41 of the PLC 23.

[0020] The input unit 44 includes input devices such as a hardware switch, an input key, a keyboard, and a pointing device. The input unit 44 acquires information input by a user of the FA device 40, and notifies the processor 41 of the acquired information.

[0021] The output unit 45 includes output devices such as a light emitting diode (LED), a liquid crystal display (LCD), and a speaker. The output unit 45 presents various information to the user according to instructions from the processor 41. The output unit 45 of the support terminal 10 includes a display device such as an LCD, and functions as a part of a graphical user interface (GUI). In the support terminal 10, the display device corresponding to the output unit 45 and the pointing device corresponding to the input unit 44 may form a touch screen.

[0022] The communication unit 46 includes a communication interface circuit for communicating with an external device. The communication unit 46 receives a signal from the outside and outputs data indicated by the signal to the processor 41. The communication unit 46 also transmits a signal indicating the data output from the processor 41 to the external device.

[0023] The above-mentioned hardware configurations work together to allow the server device 20 and the support terminal 10 to perform various functions. In detail, as shown in Fig. 3, the communication device 21 has a server unit 211 that distributes information using a predetermined communication standard, and similarly, the communication device 22 has a server unit 221, and the PLC 23 has a server unit 231. All of these server units 211, 221, and 231 are realized mainly by the cooperation of the processor 41 and the communication unit 46. Each of the server units 211, 221, and 231 distributes information in a format conforming to the OPC UA standard as the above-mentioned communication standard. The PLC 23 corresponds to an example of a programmable controller having a function of a server that encrypts and distributes information conforming to a predetermined information model.

[0024] OPC UA is a communications standard used to notify the outside world of information from FA devices via industrial networks. OPC UA makes it possible to encrypt and distribute information that conforms to a predefined information model, independent of the OS (Operating System) on the server and client sides, and is therefore a standard standard that is often adopted by FA devices. Here, information encryption in OPC UA is performed using public key cryptography after application authentication using a certificate.

[0025] The information model in OPC UA is a model that recursively expresses the structure of information by having other nodes refer to nodes of types such as Object, Variable representing the state value of Object, and Method representing the behavior of Object. For example, an information model including a Variable node indicating the presence or absence of an abnormality in the server device 20 is defined in advance and shared by the server units 211, 221, 231 and the client unit 11 described below. The state value of the node is then distributed from the server device 20 in response to a request from the client unit 11, so that a user U1 of the support terminal 10 having the client unit 11 can know the operating state of the server device 20.

[0026] In addition, when the server device 20 provides information via OPC UA, a status code indicating whether or not there is a problem with the information is added to the information and provided to the client unit 11. The user U1 of the support terminal 10 can determine whether or not some abnormality has occurred in the server device 20 by referring to the status code.

[0027] 4 to 6 show examples of information provided by the server device 20. As shown in FIG. 4, this information is information in which the server providing the information, a node ID (Identifier) ​​for identifying a node in a predefined information model, a display name of the node, a value of the node, a data type of the value, a source timestamp, a server timestamp assigned by the server device 20, and a status code are associated with each other. In the example of FIG. 5, the value of the node is "ERROR", indicating that an abnormality has occurred in the server device 20. Also, in the example of FIG. 6, the status code is "Error", indicating that an abnormality has occurred in the server device 20.

[0028] Here, the abnormality indicated to have occurred by the information provided by the server device 20 is an event that is detected in the server device 20 and meets a predetermined condition, and usually means an operating state of the server device 20 that deviates from the range assumed to be a normal operating state by the administrator of the server device 20. Examples of such abnormalities include memory abnormalities, temperature abnormalities, and communication abnormalities.

[0029] Returning to FIG. 3, the PLC 23 has a storage unit 232 that stores an execution program 233 and a log 234. The storage unit 232 is mainly realized by cooperation of at least one of the main memory unit 42 and the auxiliary memory unit 43 of the PLC 23, the processor 41, and the communication unit 46. The storage unit 232 stores the execution program 233 that has been executed or is currently being executed by the PLC 23, and a log 234 of execution data used when executing the execution program 233. Logging of the execution data is realized, for example, by periodically overwriting the value of the execution data in a ring buffer. The storage unit 232 then transmits the execution program 233 and the log 234 to the support terminal 10 in response to a request from the support terminal 10.

[0030] Fig. 7 shows simple examples of execution program 233 and log 234. As shown in Fig. 7, when execution program 233 is a ladder program, log 234 is log data that shows the transition of the value of the execution data by showing the value of a device or label corresponding to execution data used in the ladder program in association with the time when the device or label had that value.

[0031] Returning to Figure 3, the support terminal 10 has a client unit 11 that receives information from the server device 20, an analysis unit 12 that analyzes the information received by the client unit 11, a display control unit 13 that generates an image based on the analysis result by the analysis unit 12 and displays it on a display unit 141 of the UI unit 14, a UI (User Interface) unit 14 that presents the image to the user U1 and accepts information input by the user U1, a receiving unit 15 that receives an execution program 233 and a log 234 from the PLC 23 in accordance with a specific operation by the user U1, and an output unit 16 that outputs a file 161 showing the image generated by the display control unit 13.

[0032] The client unit 11 is realized mainly by cooperation between the processor 41 and the communication unit 46 of the support terminal 10. When communication according to OPC UA is established between the client unit 11 and the server units 211, 221, 231, the client unit 11 periodically receives information such as those illustrated in Figs. 5 to 7 from the server units 211, 221, 231. This period is, for example, one second or one minute. The information periodically received by the client unit 11 may be any information indicating the operating status of the server device 20. The client unit 11 corresponds to an example of a client means that receives information indicating the operating status of the programmable controller from the server.

[0033] The analysis unit 12 is mainly realized by the processor 41 of the support terminal 10. The analysis unit 12 analyzes the information received by the client unit 11, determines the operation status of each server device 20, and notifies the display control unit 13 of the determination result.

[0034] The display control unit 13 is mainly realized by the processor 41 of the support terminal 10. The display control unit 13 generates an image showing the operation states of the server devices 20 determined by the analysis unit 12 using icons corresponding to each server device 20, and displays the image on the display unit 141 of the UI unit 14. FIG. 8 shows an example of an image displayed on the display unit 141. This image shows a configuration of a network system 100 including a plurality of server devices 20. This image may also show the connection relationships of the server devices 20 by connecting the icons corresponding to the server devices 20 with lines. This icon corresponds to an example of a device icon corresponding to a server device.

[0035] In Fig. 8, icons 51, 52, 53 of "MASTER 1", "MASTER 2", and "MASTER 3" corresponding to the communication devices 21, 22 and the PLC 23, respectively, are connected by lines to an icon 54 of "LOCAL 1" corresponding to the support terminal 10. Also, a mark 55 indicating that an abnormality has occurred in communication with the communication device 22 is displayed on the line connecting "MASTER 2" and "LOCAL 1", and a mark 56 indicating that an abnormality has occurred in the PLC 23 is displayed superimposed on the icon of "MASTER 3". The mark 55 corresponds to an abnormality indicated by a status code, and the mark 56 corresponds to an abnormality of the PLC 23 notified as a node value. The display control unit 13 corresponds to an example of a display control means for displaying an image indicating an operating state on a display means using an icon corresponding to a programmable controller.

[0036] Returning to FIG. 3, the UI unit 14 is mainly realized by the cooperation of the input unit 44 and the output unit 45 of the support terminal 10. The UI unit 14 has a display unit 141 realized by the output unit 45, and acquires information input by the user U1 using an image displayed on the display unit 141. For example, as shown in FIG. 9, the UI unit 14 accepts an operation of selecting an item of "display details" from a submenu 61 displayed by placing a cursor on an icon 51 and pressing the right button of the mouse. The UI unit 14 that has accepted this operation notifies the display control unit 13 that the operation has been accepted, and the display control unit 13 causes the display unit 141 to display a history of information received from the server device 20 corresponding to the selected icon 51, as exemplified in FIG. 10.

[0037] 11, the UI unit 14 accepts an operation of selecting an item "Start monitoring" from a submenu 62 that is displayed by placing the cursor on the icon 53 and pressing the right button of the mouse. The UI unit 14 that has accepted this operation notifies the receiving unit 15 that the operation has been accepted. The item "Start monitoring" may be omitted in the submenu of a server device 20 in which no abnormality has occurred, or may be omitted in the submenu of a server device 20 other than the PLC 23 that can provide the execution program 233 and the log 234. The UI unit 14 corresponds to an example of a user interface means that accepts an operation on an icon.

[0038] Returning to Fig. 3, the receiving unit 15 is realized mainly by cooperation between the processor 41 and the communication unit 46. When the UI unit 14 accepts the operation of "start monitoring", the receiving unit 15 requests the server device 20 corresponding to the selected icon to transmit the execution program 233 and the log 234, and receives the execution program 233 and the log 234. In the case shown in Fig. 11, the receiving unit 15 receives the execution program 233 and the log 234 stored in the storage unit 232 of the PLC 23. The receiving unit 15 corresponds to an example of a receiving means that receives, from the programmable controller, the execution program executed by the programmable controller and a log of execution data used in executing the execution program, when an operation is accepted by the user interface means.

[0039] Returning to FIG. 3, the receiving unit 15 provides the received execution program 233 and log 234 to the display control unit 13, and the display control unit 13 generates a monitoring image for the user U1 to observe the execution program 233 and log 234, and displays the image on the display unit 141. FIG. 12 shows an example of the monitoring image. In the example of FIG. 12, a monitoring image showing a ladder diagram as the execution program 233 and a time seek bar 63 are displayed. In the ladder diagram, the value of the execution data corresponding to the time specified in the time seek bar 63 is shown at the contact point. Specifically, the contact point "M1" is hatched to indicate that the device value of the contact point is "1", and the contact point "M3" is left blank without hatching to indicate that the device value of the contact point is zero. However, the expression of the value of the execution data in the execution program 233 is not limited to the example of FIG. 12, and may be changed arbitrarily.

[0040] In the ladder diagram of Fig. 12, the execution data of "M1000", "M1001" and "M1002" indicate whether or not a specific abnormality has occurred, as labeled "power supply abnormality", "temperature abnormality" and "servo abnormality", respectively. By observing the transition of the values ​​of such execution data, the user U1 may verify the operation history of the PLC 23 and investigate the cause of the abnormality in the control system. The display control unit 13 corresponds to an example of a display control means that displays the execution program and log received by the receiving means on the display means.

[0041] By placing the cursor on the monitoring image exemplified in Fig. 12 and right-clicking the mouse, a submenu 64 is displayed as shown in Fig. 13. When an operation is performed to select the item "Image File Output" from this submenu 64, the UI unit 14 notifies the output unit 16 that the operation has been accepted. Similarly, when the submenu 64 is displayed for the image exemplified in Fig. 8 and an operation is performed to select the item "Image File Output", the UI unit 14 notifies the output unit 16 that the operation has been accepted.

[0042] Returning to FIG. 3, the output unit 16 is mainly realized by the cooperation of the processor 41, the auxiliary storage unit 43, and the communication unit 46 of the support terminal 10. When the output unit 16 receives a notification about a monitoring image from the UI unit 14, it outputs a file 161 showing the monitoring image as shown in FIG. 14. Similarly, when the output unit 16 receives a notification about the image of FIG. 8, it outputs a file 161 showing a configuration diagram of the network system 100 as shown in FIG. 15. The output destination of the file 161 may be the auxiliary storage unit 43 of the support terminal 10, an external storage device of the support terminal 10, or a recording medium such as a memory card inserted into the support terminal 10. The file 161 is used, for example, when the user U1 in charge of the verification work conveys the verification result to another person. The output unit 16 corresponds to an example of an output means for outputting a file showing an image.

[0043] Next, the display control process executed by the support terminal 10 will be described with reference to Fig. 16. The display control process corresponds to an example of a display control method executed by the support terminal 10 as a client device.

[0044] In the display control process, the client unit 11 acquires information from each server device 20 (step S1), and the display control unit 13 displays an image equivalent to a network configuration diagram showing the operating status of each server device 20, as shown in FIG. 8 (step S2).

[0045] Next, the UI unit 14 of the support terminal 10 selects any of the server devices 20 in the network configuration diagram and determines whether or not a detailed check operation has been performed (step S3). Here, the detailed check operation corresponds to selecting the "Detailed display" item shown in Fig. 9. If it is determined that a detailed check operation has not been performed (step S3; No), the process by the support terminal 10 proceeds to step S5.

[0046] On the other hand, when it is determined that the operation for checking details has been performed (step S3; Yes), the history of information received from the selected server device 20 is displayed as detailed information (step S4). Specifically, the display unit 141 displays a list of information received in the past in a table format, as shown in FIG.

[0047] Next, the UI unit 14 of the support terminal 10 selects any one of the server devices 20 in the network configuration diagram and determines whether or not a program monitor startup operation has been performed (step S5). Here, the program monitor startup operation corresponds to selecting the "Start Monitor" item shown in Fig. 11. If it is determined that a program monitor startup operation has not been performed (step S5; No), the process by the support terminal 10 proceeds to step S7.

[0048] On the other hand, when it is determined that the program monitor has been started (step S5; Yes), the display unit 141 displays the execution program 233 and the execution data log 234 on the program monitor (step S6). Specifically, the display unit 141 displays an image in which the log 234 is applied to the execution program 233, as shown in FIG.

[0049] Next, the UI unit 14 of the support terminal 10 judges whether or not a file output operation has been performed in the network configuration diagram or in the program monitor displayed in step S6 (step S7). Here, the file output operation corresponds to selecting the item "Image File Output" shown in Fig. 13. If it is judged that a file output operation has not been performed (step S7; No), the support terminal 10 repeats the processes from step S1 onwards.

[0050] On the other hand, if it is determined that the file output operation has been performed (step S7; Yes), the output unit 16 outputs the file 161 showing the image for which the file output operation has been performed (step S8). After that, the support terminal 10 repeats the processes from step S1 onward.

[0051] As described above, in the support terminal 10 according to this embodiment, the UI unit 14 accepts an operation on an icon, the receiving unit 15 receives the execution program 233 and the execution data log 234 from the PLC 23, and the display control unit 13 displays the execution program 233 and the log 234 on the display unit 141. Therefore, the user U1 does not need to be familiar with databases, and can visually check the execution program 233 and the execution data log 234. This reduces the workload for verifying the operation history of the PLC 23.

[0052] Also, there is known a tool that allows an operator to check the received information on the OPC UA client side in a table format or text format as shown in Fig. 10, but such a tool has poor viewability and it takes time to check the contents. In contrast, the support terminal 10 according to the present embodiment shows the operating status of the server device 20 in the configuration of the network system 100 using icons and accepts operations by the user U1 using a pointing device. By providing such a GUI to the user U1, the workload of the user U1 can be significantly reduced.

[0053] Moreover, the information that the client unit 11 receives from the server units 211, 221, and 231 indicates the presence or absence of an abnormality in the server device 20 as the operating state of the server device 20, and the display control unit 13 causes the display unit 141 to display an icon for the server device 20 together with marks 55 and 56 indicating the occurrence of an abnormality, as shown in FIG. 8. This allows the user U1 to easily recognize the location of the abnormality in the network system 100. Note that the method of expressing the presence or absence of an abnormality in the server device 20 is not limited to adding a mark to the icon. For example, the icon of the server device 20 in which an abnormality has occurred and the icon of the server device 20 in which an abnormality has not occurred may be different. The icon may be displayed in a form corresponding to the presence or absence of an abnormality.

[0054] Also, an example has been described in which the user U1 verifies the operation history of the PLC 23 based on the log 234 of the execution data stored by the storage unit 232 of the PLC 23. This log 234 may include log data that is constantly recorded regardless of the presence or absence of an abnormality, and log data that is recorded before and after the point in time when an abnormality is detected in the PLC 23.

[0055] Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments.

[0056] For example, although an example has been described in which the communication between the server units 211, 221, and 231 and the client unit 11 complies with OPC UA, this communication may also comply with other communication standards. However, it is preferable to comply with a communication standard having characteristics equivalent to or similar to OPC UA. Such characteristics include having a security function including encryption, making it easy to interpret information between devices with different OSs, models, and manufacturers by transmitting information according to a predetermined information model, and being able to incorporate a server function or a client function regardless of the OS, model, and manufacturer of the device to be communicated with.

[0057] 12, the display control unit 13 may generate an image in which execution data at a time associated with the occurrence of an abnormality in the information received by the client unit 11 is applied to the execution program 233, and may initially display the image on the display unit 141. This allows the user U1 to easily verify the transition of the execution data before and after the occurrence of the abnormality.

[0058] Also, an example in which the support terminal 10 has the display unit 141 has been described, but the present invention is not limited to this. For example, as shown in Fig. 17, the user U1 operates the UI device 10a based on information provided from a UI device 10a different from the support terminal 10, and the UI unit 14 may function as an interface unit with the user U1 in the support terminal 10 by communicating with the UI device 10a. In the example of Fig. 17, the UI unit 14 is realized by the communication unit 46 of the support terminal 10, and the display control unit 13 causes the display unit 141 of the UI device 10a to display an image.

[0059] In addition, the operation state of the server device 20 has been described mainly as a state indicating the presence or absence of an abnormality, but is not limited thereto. The operation state of the server device 20 may be a state in which the operation mode of the server device 20 indicates one of a plurality of predetermined modes.

[0060] The functions of the support terminal 10 and the PLC 23 according to the above-mentioned embodiment can be realized by dedicated hardware or by a general computer system.

[0061] For example, the program P1 can be stored and distributed on a computer-readable recording medium such as a flexible disk, a CD-ROM (Compact Disk Read-Only Memory), a DVD (Digital Versatile Disk), or an MO (Magneto-Optical disk), and the program P1 can be installed on a computer to configure an apparatus that executes the above-mentioned processing.

[0062] Also, the program P1 may be stored in a disk device of a server device on a communication network such as the Internet, and may be downloaded to a computer, for example, by being superimposed on a carrier wave.

[0063] The above-mentioned processing can also be achieved by starting and executing the program P1 while transferring it via a network such as the Internet.

[0064] Furthermore, the above-mentioned processing can also be achieved by executing all or part of the program P1 on a server device, and executing the program P1 while the computer transmits and receives information related to the processing via a communications network.

[0065] In addition, when the above-mentioned functions are shared and realized by the OS (Operating System) or by the OS working together with an application, only the parts other than the OS may be stored on a medium and distributed, or may be downloaded to a computer.

[0066] Furthermore, the means for realizing the functions of the support terminal 10 and the PLC 23 is not limited to software, and a part or the whole of the functions may be realized by dedicated hardware or circuits.

[0067] Various embodiments and modifications of the present disclosure are possible without departing from the broad spirit and scope of the present disclosure. The above-described embodiments are for explaining the present disclosure and do not limit the scope of the present disclosure. In other words, the scope of the present disclosure is indicated by the claims, not the embodiments. Various modifications made within the scope of the claims and within the scope of the disclosure equivalent thereto are considered to be within the scope of the present disclosure. [Industrial Applicability]

[0068] The present disclosure is suitable for verifying the operation history of PLCs at FA sites. [Explanation of symbols]

[0069] 100 network system, 10 support terminal, 10a UI device, 11 client unit, 12 analysis unit, 13 display control unit, 14 UI unit, 141 display unit, 15 receiving unit, 16 output unit, 161 file, 20 server device, 21, 22 communication device, 211, 221, 231 server unit, 23 PLC, 232 storage unit, 233 execution program, 234 log, 30 network, 40 FA device, 41 processor, 42 main memory unit, 43 auxiliary memory unit, 44 input unit, 45 output unit, 46 communication unit, 47 internal bus, 51 to 54 icon, 55, 56 mark, 61, 62, 64 submenu, 63 time seek bar, P1 program, U1 user.

Claims

1. A computer connected via a network to a programmable controller having a server function for encrypting and distributing information conforming to a predetermined information model, a client means for receiving from the server the information indicating the occurrence of an abnormality in the programmable controller in association with a time; a display control means for causing a display means to display an image including an icon corresponding to the occurrence of the abnormality in the programmable controller; a user interface means for accepting an operation on the icon; a receiving means for receiving from the programmable controller, when the operation is accepted by the user interface means, a log indicating a transition of an execution program executed by the programmable controller and execution data used when executing the execution program; Function as a the display control means, when causing the display means to display the execution program and the log received by the receiving means, causes the display control means to first display, together with a time seek bar, the execution data at the time associated with the occurrence of the abnormality, and causes the display control means to display the execution data corresponding to the time specified in the time seek bar. Display program.

2. the computer is connected via the network to a plurality of server devices having the server functions, including the programmable controller; the image displayed on the display means indicates the configuration of the network using device icons corresponding to the respective server devices; The display program according to claim 1 .

3. an output means for outputting a file showing the image from the computer; Further functioning as The display program according to claim 1 .

4. A client device connected via a network to a programmable controller having a server function of encrypting and distributing information conforming to a predetermined information model, a client means for receiving from the server the information indicating the occurrence of an abnormality in the programmable controller in association with a time; a display control means for causing a display means to display an image including an icon corresponding to the occurrence of the abnormality in the programmable controller; a user interface means for accepting an operation on the icon; receiving means for receiving from the programmable controller, when the operation is accepted by the user interface means, an execution program executed by the programmable controller and a log indicating a transition of execution data used when executing the execution program; the display control means, when causing the display means to display the execution program and the log received by the receiving means, causes the display control means to first display, together with a time seek bar, the execution data at the time associated with the occurrence of the abnormality, and causes the display control means to display the execution data corresponding to the time specified in the time seek bar. Client device.

5. A client device according to claim 4; the programmable controller connected to the client device via the network; A network system including:

6. A display control method executed by a client device connected via a network to a programmable controller having a server function of encrypting and distributing information conforming to a predetermined information model, comprising: a client means for receiving from the server the information indicating the occurrence of an abnormality in the programmable controller in association with a time; a display control means for controlling a display means to display an image including an icon corresponding to the occurrence of the abnormality in the programmable controller; A user interface means receives an operation on the icon, a receiving means for receiving, when the operation is accepted by the user interface means, from the programmable controller, a log indicating a transition of an execution program executed by the programmable controller and execution data used when executing the execution program; when the display control means causes the display means to display the execution program and the log received by the receiving means, the display control means causes the display means to first display, together with a time seek bar, the execution data at the time associated with the occurrence of the abnormality, and to display the execution data corresponding to the time specified in the time seek bar. A display control method comprising:

Images