Programmable display and programmable logic controller system

Abstract

The present invention relates to a programmable display and a programmable logic controller system. The programmable display includes: a display data generator for generating display data of a page corresponding to a page identifier; a display unit for displaying the page corresponding to the page identifier on a display screen based on the display data generated by the display data generator; and a touch detector for detecting a touch operation on the display screen of the display unit. When the touch detector detects a predetermined second touch operation on the display screen, the display unit generates display data for displaying a device wave of a device specified by an object device setting based on time sequence data stored in a PLC. The display unit displays the second page or the device wave on the display screen based on the display data generated by the display data generator.

Description

Technical Field

[0001] The invention relates to a programmable display and a programmable logic controller system comprising the programmable display. Background Art

[0002] In factory automation (FA), a programmable logic controller (hereinafter also referred to as "PLC") is used as a controller for controlling input / output devices such as sensors, electric motors, and actuators. When setting up an FA system, a system designer considers which sequences can be used to make the input / output devices work properly, and creates a ladder program that can implement the sequence. Such a ladder program is designed using a general-purpose personal computer installed with a programming application for ladder programs. The system designer creates a ladder program after designing and debugging, and then sends the created ladder program to the PLC. The PLC executes the program.

[0003] The status of the input / output device when the PLC is working can be monitored on site by using a programmable display connected to the PLC. Various functional components such as lights and switches are arranged in the display screen of the programmable display. Various functions are assigned to these functional components. The data to be displayed in the display screen is designed by using a general personal computer installed with a programming application for displaying data. Usually, like the above-mentioned system designers, field engineers who maintain FA systems on site know the sequence for making the input / output devices work properly. However, there are various description methods of ladder diagram programs that efficiently implement this sequence. For this reason, general field engineers will spend time to understand the description of the ladder diagram program.

[0004] In the event of a failure during the operation of a production line for establishing an FA system, the production line may be paralyzed. In the event of such a failure, a typical programmable display turns on or flashes an alarm lamp (component icon) arranged in the display screen to notify the on-site engineer of the occurrence of the failure.

[0005] However, field engineers often fail to diagnose the cause of a fault when they only check the warning light. Even in this case, the fault can sometimes be easily eliminated on site. It is important for field engineers to eliminate such simple faults immediately and restore the system quickly.

[0006] An object is to provide a programmable display that enables an engineer to easily eliminate a fault occurring at an FA site, and a programmable logic controller system including the programmable display. Summary of the invention

[0007] A programmable display according to a first aspect of the present invention is connectable to a programmable logic controller, the programmable logic controller being used to save time-sequential data related to a device value of a device as a storage area to be referenced by a user program based on a predefined saving condition. The programmable display includes a setting storage unit, a display data generator, a display unit, and a touch detector. The setting storage unit stores component settings, page settings, and object device settings. The component settings assign the device to a corresponding component of a plurality of components arranged on a screen image as a page to monitor or change the status of the device of the programmable logic controller. The page settings manage the component settings in units of pages by using page identifiers for identifying a plurality of pages. The object device settings specify an object device, which shows a device value to be stored in the programmable logic controller as time-sequential data in the form of a waveform as a device wave. The display data generator generates display data of a page corresponding to the page identifier in units of pages based on the component settings and the page settings stored in the setting storage unit. The display unit includes a display screen, and displays the page corresponding to the page identifier on the display screen based on the display data generated by the display data generator. The touch detector detects a touch operation on the display screen of the display unit. The display data generator generates display data that changes the image of the display screen from the current page to another page based on the page setting when the touch detector detects a predetermined first touch operation on the display screen. In addition, the display data generator generates display data for displaying the device wave of the device specified by the object device setting based on the time sequence data stored in the programmable logic controller when the touch detector detects a predetermined second touch operation on the display screen. The display unit displays the other page or the device wave on the display screen based on the display data generated by the display data generator. According to the programmable display, a page switching operation and a device wave showing operation can be selectively performed by such a touch operation on the programmable display, the page switching operation switches the screen from one page to another, and the device wave showing operation shows the device wave of the time sequence data stored in the programmable logic controller. In this case, the device wave can be seen on the display screen of the programmable display, and information useful for immediately eliminating the fault occurring at the FA site can be easily provided.

[0008] In the programmable display according to the second aspect of the present invention, in addition to the above aspects, the setting storage unit stores default screen information representing a predefined default screen having a format for displaying the device wave. In addition, when the touch detector detects a predetermined second touch operation on the display screen, the display data generator superimposes the time sequence data on the default screen based on the default screen information and the time sequence data to generate display data for displaying the device wave of the device specified by the object device setting.

[0009] In a programmable display according to the third aspect of the present invention, in addition to any of the above aspects, when the display unit displays the device wave on the display screen and the touch detector detects a change operation for changing the display portion of the device wave that has been displayed (for example, a sliding operation of a moment-specified cursor), the display data generator extracts a portion of the time sequence data corresponding to the display portion of the device wave requested by the change operation, and generates new display data for displaying the requested display portion of the device wave.

[0010] In the programmable display according to the fourth aspect of the present invention, in addition to any of the above aspects, the component settings stored in the setting storage unit also include settings for a wave display component for displaying the device wave. In addition, the second touch operation is a touch operation on the wave display component arranged on the first page displayed on the display screen.

[0011] In a programmable display according to a fifth aspect of the present invention, in addition to any of the above aspects, the second touch operation is a specific touch operation on a non-component arrangement portion on which a display component is not arranged on the first page displayed on the display screen.

[0012] In a programmable display according to a sixth aspect of the present invention, in addition to any of the above aspects, the specific touch operation is any one of long pressing, flicking, pinching in and out of the non-component arrangement portion.

[0013] In the programmable display according to the seventh aspect of the present invention, in addition to any of the above aspects, the component settings stored in the setting storage unit also include: the setting of the acquisition device, the acquisition device is used to repeatedly acquire the time sequence data of the device value temporarily recorded in the temporary recording unit of the programmable logic controller; and the setting of the real-time display component, the real-time display component is used to sequentially display the time sequence data of the acquisition device. In addition, when a touch operation is detected on the real-time display component, based on the time sequence data of the device value of the acquisition device temporarily recorded in the temporary recording unit of the programmable logic controller, the display data generator generates display data for sequentially displaying the device value on the display screen.

[0014] In the programmable display according to the eighth aspect of the present invention, in addition to any of the above aspects, under the condition that a predefined saving condition is satisfied, the programmable logic controller is able to associate image data provided from an external camera that can be connected to the programmable logic controller with information related to the acquisition time of shooting the image data, and temporarily store the image data associated with the information related to the acquisition time, and wherein the programmable display requests the programmable logic controller to send operation record data, and displays an image corresponding to the image data included in the operation record data on the display unit based on the information related to the acquisition time included in the operation record data.

[0015] In the programmable display according to the ninth aspect of the present invention, in addition to any of the above aspects, when a predefined saving condition is satisfied, the programmable logic controller is able to associate the operation log data with the user program executed when the predefined saving condition is satisfied, and save the user program associated with the operation log data. In addition, the programmable display requests the programmable logic controller to send the saved operation log data, and based on the information related to the acquisition time included in the operation log data, superimposes the device value acquired at the acquisition time on the user program included in the operation log data on the display unit.

[0016] In the programmable display according to the tenth aspect of the present invention, in addition to any of the above aspects, when the programmable logic controller collects event data corresponding to multiple events occurring in the programmable logic controller or the controlled device to be controlled by the programmable logic controller, and associates the event data with the time of occurrence of the event and stores the event data associated with the time of occurrence of the event in chronological order, when a predefined saving condition is met, the programmable logic controller saves the stored event data in the operation record data so that the stored event data can be associated with the operation record data. In addition, the programmable display requests the programmable logic controller to send the stored operation record data, and displays the event corresponding to the event data included in the operation record data on the display unit based on the time of occurrence included in the operation record data.

[0017] In a programmable display according to an eleventh aspect of the present invention, in addition to any of the above aspects, the programmable display can display a selection screen that enables selection of the target device as an initial display image when the device wave is displayed on the display screen.

[0018] In the programmable display according to the twelfth aspect of the present invention, in addition to any of the above aspects, in the case of displaying the device wave on the display screen, based on identification information for specifying one or more object devices having device values ​​to be shown as the device wave, the programmable display is capable of displaying the one or more object devices. According to the programmable display, in the event of a failure during actual operation of the FA system, the device wave of a device that may be related to the cause of the failure is selectively displayed. That is, the programmable display can show information useful for diagnosing the cause of the failure. As a result, the programmable display is useful for quickly restoring the system.

[0019] In the programmable display according to the thirteenth aspect of the present invention, in addition to any of the above aspects, when the device wave is displayed on the display screen, the programmable display is capable of displaying a setting screen that enables selection of one or more object devices and the representation style of the one or more object devices. According to the programmable display, in the event of a failure during actual operation of the FA system, the device wave of a device that may be related to the cause of the failure is selectively displayed. That is, the programmable display can show information useful for diagnosing the cause of the failure. As a result, the programmable display is useful for quickly restoring the system.

[0020] In a programmable display according to a fourteenth aspect of the present invention, in addition to any of the above aspects, a display-side communication unit capable of communicating with the programmable logic controller is further included.

[0021] The programmable display according to the fifteenth aspect of the present invention further includes a display-side device unit in addition to any of the above aspects. The display-side device unit communicates with the programmable logic controller via the display-side communication unit and maintains a device value synchronized with a device value of the programmable logic controller.

[0022] In the programmable display according to the sixteenth aspect of the present invention, in addition to any of the above aspects, a guidance information storage unit is further provided. The guidance information storage unit is used to store guidance information associated with the device specified by the object device setting and showing how to eliminate the error event that occurs when the saving condition is met. In the case where the touch detector detects the predetermined second touch operation on the display screen, the display data generator generates display data for displaying the guidance information, the guidance information stored in the guidance information storage unit and associated with the device specified by the object device setting.

[0023] According to a seventeenth aspect of the present invention, a programmable logic controller system, a programmable logic controller system, comprising: a programmable logic controller for saving time-sequential data related to a device value of a device as a storage area to be referenced by a user program based on a predefined saving condition; and a programmable display, which can be connected to the programmable logic controller. The programmable logic controller includes a program execution unit, a device unit, a temporary recording unit and a saving memory. The program execution unit repeatedly executes the user program. The device unit includes a device as a storage area to be referenced by the program execution unit. The temporary recording unit collects the device values ​​of the devices stored in the device unit, and associates the device values ​​with information related to the collection time of the device values, and temporarily records the device values ​​associated with the information related to the collection time in time sequence. The saving memory saves the time-sequential data related to the device values ​​temporarily recorded in the temporary recording unit as operation record data when the predefined saving condition is met. The programmable display includes a setting storage unit, a display data generator, a display unit and a touch detector. The setting storage unit stores component settings, page settings and object device settings. The component setting assigns the device to a corresponding component among a plurality of components arranged on a screen image as a page to monitor or change the status of the device of the programmable logic controller. The page setting manages the component setting in units of pages by using a page identifier for identifying a plurality of pages. The object device setting specifies an object device which shows a device value to be stored in the programmable logic controller as time-sequential data in the form of a waveform as a device wave. The display data generator generates display data of a page corresponding to the page identifier in units of pages based on the component setting and the page setting stored in the setting storage unit. The display unit includes a display screen, and displays a page corresponding to the page identifier on the display screen based on the display data generated by the display data generator. The touch detector detects a touch operation on the display screen of the display unit. The display data generator generates display data for changing the image of the display screen from a current page to another page based on the page setting when the touch detector detects a predetermined first touch operation on the display screen. Furthermore, the display data generator generates display data for displaying a device wave of a device specified by the object device setting based on the time sequence data stored in the programmable logic controller when the touch detector detects a predetermined second touch operation on the display screen. In addition, the display unit displays the other page or the device wave on the display screen based on the display data generated by the display data generator.According to the programmable display, a page switching operation and a device wave display operation can be selectively performed by such a touch operation on the programmable display, the page switching operation switching the screen from one page to another, and the device wave display operation displaying the device wave of the time sequence data stored in the programmable logic controller. In this case, the device wave can be seen on the display screen of the programmable display, and information useful for immediately eliminating a fault occurring at the FA site can be easily provided.

[0024] In the programmable logic controller system according to the eighteenth aspect of the present invention, in addition to the above aspects, the component settings stored in the setting storage unit also include settings of a wave display component for displaying the device wave. In addition, the second touch operation is a touch operation of the wave display component arranged on the first page displayed on the display screen.

[0025] In a programmable logic controller system according to a nineteenth aspect of the present invention, in addition to any of the above aspects, the second touch operation is a specific touch operation on a non-component arrangement portion of the first page displayed on the display screen where no display components are arranged.

[0026] In a programmable logic controller system according to a twentieth aspect of the present invention, in addition to any of the above aspects, the specific touch operation is any one of long pressing, flicking, pinching in and out of the non-component arrangement portion.

[0027] In the programmable logic controller system according to the twenty-first aspect of the present invention, in addition to any of the above aspects, the setting storage section of the programmable display stores an acquisition device setting for specifying an acquisition device having a device value as the time sequence data temporarily recorded by the recording control section. In addition, in the case where a touch operation is detected for a component for displaying the time sequence data of the acquisition device specified by the acquisition device setting, the display data generator generates display data for sequentially displaying the device value of the acquisition device based on the time sequence data of the device value temporarily recorded by the recording control section.

[0028] In the programmable logic controller system according to the twenty-second aspect of the present invention, in addition to any of the above aspects, the programmable logic controller further includes: an external interface connected to an external camera and receiving image data from the camera; an image recorder for temporarily recording image data received from the camera via the external interface; and a camera unit processor for collecting image data received from the camera via the external interface, and associating the image data with information related to the moment of image data acquisition, and temporarily storing the image data associated with the information related to the moment in the image recorder. When the saving condition is met, the saving memory saves the image data temporarily stored by the camera unit processor in the image recorder in association with the operation record data. The programmable display acquires the operation record data stored in the saving memory, and displays an image corresponding to the image data included in the operation record data on the display unit based on the information related to the acquisition moment included in the operation record data.

[0029] In the programmable logic controller system according to the twenty-third aspect of the present invention, in addition to any of the above aspects, when the saving condition is satisfied, the programmable logic controller associates the user processing currently executed by the program execution unit when the saving condition is satisfied with the operation record data, and saves the user program associated with the operation record data in the saving memory. The programmable display requests the programmable logic controller to send the operation record data saved in the saving memory, and based on the information related to the acquisition time included in the operation record data, superimposes the device value acquired at the acquisition time on the user program included in the operation record data on the display unit.

[0030] In a programmable logic controller system according to the twenty-fourth aspect of the present invention, in addition to any of the above aspects, the programmable logic controller also includes an event collection unit, which is used to collect event data related to multiple events occurring in the programmable logic controller or the controlled device controlled by the programmable logic controller. The collection unit associates the event data with the time of occurrence of the event, and stores the event data associated with the time of occurrence of the event in the temporary recording unit in chronological order. When the saving condition is met, the saving memory saves the event data collected by the event collection unit in association with the operation record data, so that the event data is included in the operation record data. The programmable display obtains the operation record data saved in the saving memory, and displays the event corresponding to the event data included in the operation record data on the display unit based on the information related to the time of occurrence included in the operation record data. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] A more complete appreciation of the present invention and many of the attendant advantages may be readily obtained and better understood by reference to the following detailed description taken in conjunction with the accompanying drawings, in which:

[0032] Figure 1 is a functional block diagram showing a programmable logic controller system;

[0033] Figure 2 is a schematic diagram showing an exemplary user screen displayed on a programmable display;

[0034] Figure 3 is a functional block diagram showing a programmable logic controller system;

[0035] Figure 4 It is a schematic diagram of a ladder diagram program;

[0036] Figure 5 It is a functional block diagram of the programming device;

[0037] Figure 6 It is the functional block diagram of PLC;

[0038] Figure 7 is a schematic diagram illustrating the scanning of a ladder diagram program;

[0039] Figure 8 This is a functional block diagram of a CPU mounting unit (CPU unit);

[0040] Fig. 9 is a functional block diagram showing a programmable logic controller system including a camera unit;

[0041] Fig.10is a functional block diagram of the expansion unit;

[0042] Fig.11 It is a functional block diagram of a programmable display;

[0043] Fig.12 is a schematic diagram showing a device wave display screen in playback mode;

[0044] Fig.13 is a schematic diagram showing a page setting screen of a screen data editing device;

[0045] Fig.14 is a schematic diagram showing a switching setting screen of a screen data editing device;

[0046] Fig.15 When "Playback Mode Start" is selected Fig.14 A schematic diagram of the switching setting screen;

[0047] Fig.16 is a schematic diagram showing an object device setting screen of a screen data editing device;

[0048] Fig.17 is a schematic diagram showing an exemplary display screen arranged with a page switching component;

[0049] Fig.18 is a schematic diagram showing another exemplary display screen in which a page switching component is arranged;

[0050] Fig.19 is a schematic diagram showing another exemplary display screen arranged with a page switching component;

[0051] Fig. 20 is a schematic diagram showing another exemplary display screen in which a page switching component is arranged;

[0052] Fig.21 is a schematic diagram showing a menu screen of a programmable display;

[0053] Fig. 22 is a schematic diagram showing an initial screen in playback mode;

[0054] Fig.23 is a schematic diagram showing a playback mode screen when a camera / event display screen is selected;

[0055] Fig.24 is a schematic diagram showing a playback mode screen when a viewer display screen is selected;

[0056] Fig.25 is a schematic diagram showing a playback mode screen when a unit display screen is selected;

[0057] Fig.26 is a schematic diagram showing a playback mode screen when a unit display screen is selected;

[0058] Fig. 27 is a schematic diagram showing a playback mode screen when a program screen is selected;

[0059] Fig.28A is a flowchart showing the processing of the programmable display;

[0060] Fig.28B It specifically shows Fig.28A The flowchart of step S2804 in the flowchart shown;

[0061] Fig.28C It specifically shows Fig.28A The flowchart of step S2809 in the flowchart shown;

[0062] Fig.28D It specifically shows Fig.28A The flowchart of step S2810 in the flowchart shown;

[0063] Fig.29 is a schematic diagram showing a device wave display screen in monitoring mode;

[0064] Fig.30 is a flowchart showing the processing of the programmable display when the real-time chart monitor is placed in monitoring mode;

[0065] Fig.31 is a schematic diagram showing only the device wave display screen in playback mode;

[0066] Fig.32 is a schematic diagram showing selection of device waves to be displayed according to storage conditions;

[0067] Fig.33 is a schematic diagram showing a user interface screen of a screen data editing device for associating an alarm with display data when a fault occurs;

[0068] Fig.34A is a schematic diagram showing the data structure of screen data of a user screen;

[0069] Fig.34B is a schematic diagram showing the data structure of screen data of a system screen;

[0070] Fig.34C is a schematic diagram of the data structure after associating the RTCMID with the device;

[0071] Fig.35 It is the functional block diagram of a programmable logic controller;

[0072] Fig.36 is a schematic diagram showing a mechanism of a programmable display for displaying operation log data;

[0073] Fig.37 is a functional block diagram of a display processor;

[0074] Fig.38 is a diagram illustrating a program display module;

[0075] Fig.39 A diagram illustrating a user interface screen displayed on a programmable display;

[0076] Fig.40 is a diagram illustrating a display module for project data and log data;

[0077] Fig.41 is a schematic diagram showing acquisition timings of device values, workpiece images, and other images;

[0078] Fig.42 is a schematic diagram illustrating display timing and display duration of log data;

[0079] Fig.43 is a flow chart illustrating the association of image data and its time information;

[0080] Fig.44 is a flow chart illustrating the association of events with their time information;

[0081] Fig.45 is a flowchart illustrating basic processing of a programmable display for monitoring a device;

[0082] Fig.46 1 is a schematic diagram showing a user screen of a programmable display according to a second embodiment;

[0083] Fig.47 1 is a schematic diagram showing a user screen of a programmable display according to a third embodiment;

[0084] Fig.48 1 is a schematic diagram showing a user screen of a programmable display according to a fourth embodiment;

[0085] Fig.49 is a schematic diagram showing a switching setting screen of a screen data editing device of a programmable logic controller system according to a fifth embodiment; and

[0086] Fig.50 2 is a schematic diagram showing a device wave display screen in a playback mode according to a modified embodiment. DETAILED DESCRIPTION

[0087] Embodiments will now be described with reference to the accompanying drawings, wherein in various drawings, the same reference numerals designate corresponding or identical elements. However, it should be understood that the embodiments described below are illustrations of programmable displays and programmable logic controller systems including the programmable displays, to specifically embody the technical ideas of the present invention, and the programmable displays of the present invention and the programmable logic controller systems including the programmable displays are not specifically limited to the following description. In addition, it should be understood that the components shown in the attached claims are not specifically limited to the components in the embodiments. Unless otherwise specified, any size, material, shape and relative arrangement of the components described in the embodiments are given as examples and not by way of limitation. In addition, for ease of explanation, the size and positional relationship of the components in the various figures are sometimes shown in an enlarged manner. The components identical or similar to the components of the present invention are attached with the same name and the same reference numerals, and the description of these components is omitted. In addition, multiple structural elements of the present invention can be configured to act as a single component of multiple elements, and on the other hand, a single structural element can be configured to act as multiple components of a single element.

[0088] First embodiment

[0089] Figure 1 is a schematic diagram of a programmable logic controller system 1000. The illustrated programmable logic controller system 1000 is an exemplary system that captures an image of an object WK conveyed along a production line by using a camera 98. The object WK is processed by an electric motor MT. Subsequently, the object WK is inspected by an input / output device SS such as a sensor. The programmable logic controller system 1000 includes a programmable logic controller 1, a programmable display 50, a programming device 70, and a screen data editing device 60. The programmable logic controller (hereinafter also referred to as "PLC") 1 is connected to the programming device 70. The programming device 70 creates or edits a user program (e.g., a ladder diagram program) to be executed in the PLC 1. The programmable display 50 is connected to the screen data editing device 60. The screen data editing device 60 performs settings of a screen to be displayed on the programmable display 50, for example, selection and layout settings of components to be laid out for each page to be displayed in the display screen. The programming device 70 and the screen data editing device 60 may be dedicated devices or implemented by software installed in a general-purpose PC.

[0090] [PLC system structure]

[0091] The PLC system includes a PLC 1, a programming device 70, a programmable display 50, and a screen data editing device 60. The programming device 70 centrally controls input / output devices arranged in a factory or the like. The programming device 70 creates a ladder program that operates the PLC 1. The programmable display 50 monitors or changes the status of the devices of the PLC 1. The screen data editing device 60 creates screen data to generate display data in the programmable display 50.

[0092] The "device" of the PLC refers to a storage area in the PLC 1 to be referenced by the ladder program. The device value of the device represents the input or output status provided from the input / output device, or the status of the internal relay (auxiliary relay), timer, or counter defined in the ladder program. The device value can be classified into a bit type and a word type. A bit device stores a 1-bit device value. A word device stores a 1-word device value.

[0093] In a broad sense, the PLC 1 is composed of a CPU mounting unit 3 and an expansion unit 4. The expansion unit 4 is a function expansion unit for expanding the function of the CPU mounting unit 3. Figure 1 , an I / O unit 4f, a camera unit 4c, and a motion unit 4d are illustrated as the expansion unit 4. An input / output device including an input device (e.g., a sensor) and an output device (e.g., an alarm light) can be connected to the I / O unit 4f. A camera for taking images of workpieces conveyed along a production line at a predetermined timing can be connected to the camera unit 4c. An electric motor for driving a production line or a robot can be connected to the motion unit 4d. The motion unit 4d is also referred to as a positioning unit, and controls the position of an object to be controlled (also referred to as an axis). Typically, a drive source such as an electric motor is provided for each axis. The CPU mounting unit 3 collects data from the expansion unit 4, and controls the expansion unit 4 by executing a ladder diagram program to perform the required calculations.

[0094] The programming device 70 can create a ladder diagram program, and edit and correct the created ladder diagram program. In addition, the programming device 70 can edit the structure of one or more expansion units 4 connected to the CPU installation unit 3, and the operating parameters of the expansion unit 4. The data including the ladder diagram program and the unit configuration information is called project data. The programming device 70 creates the project data based on the user's input, and converts the created project data into a mnemonic code. After the conversion, the ladder diagram program is sent to the CPU installation unit 3.

[0095] The CPU installation unit 3 converts the ladder diagram program into machine code, and repeatedly and periodically executes the ladder diagram program in machine code during the operation of the PLC 1. When the ladder diagram program is periodically executed, the CPU installation unit 3 collects the device values ​​stored in the device, and associates these device values ​​with the collection time, and temporarily records the device values ​​associated with the collection time in a temporary recording section 91a such as a ring buffer. In the case where the ring buffer becomes full, the oldest device value is overwritten with the latest device value. That is, a certain amount of time sequence data of the device value corresponding to a specific time period is temporarily stored according to the storage capacity of the ring buffer. In the case where a predefined saving condition is met, for example, in the case of a failure on the production line, the time sequence data of the device pre-selected by the programming device 70 as the device to be saved is automatically stored as log data in a saving memory 36 such as a flash memory or an SD card (refer to the following Figure 6 described above).

[0096] In this case, the image data continuously collected by the camera unit 4c is stored as log data together with the chronological data of the device. In addition, the ladder diagram program executed by the CPU installation unit 3 when the saving condition is met and the unit configuration information in this case are saved and associated with the log data. Therefore, when the predefined saving condition is met, the log data including the chronological data of the device and a series of image data (chronological image data), the ladder diagram program, and the unit configuration information are associated with each other and saved in the storage memory 36, for example, by managing using a common identifier for identifying a file group. Hereinafter, this file group is referred to as "operation record data". In the present embodiment, the content of the operation record data can be checked not only by the programming device 70, but also by the programmable display 50. The details will be discussed later.

[0097] [System Configuration of Programmable Display 50]

[0098] The programmable display 50 is connected to the PLC 1 via a communication cable. The device values ​​stored in the devices of the PLC 1 are sent to the programmable display 50 via the communication cable. Figure 2 As shown, various functional components FP such as lights and switches are arranged in the display screen of the programmable display 50. Devices are assigned to these functional components FP. Generally, a screen image in which one or more components of various functional components FP are arranged is called a page. Two or more pages are managed by a unique screen ID. The programmable display 50 displays the page corresponding to the screen ID on the display screen. The screen ID can be displayed on the display screen. Figure 2The upper right portion of the exemplary display screen shown is provided with a screen ID display frame IA. The screen ID display frame IA may not be displayed all the time, but may be displayed only when requested. For example, such a screen ID display may be called by right-clicking a non-specified area in the display screen. Alternatively, such a display screen ID may be superimposed on the display screen in a large size by flicking to switch one page to another.

[0099] Now let’s explain it in more detail. Figure 2 The components shown. Figure 2 The screen shown has not only the above-mentioned functional component FP but also various other components. The text "1" shown in the above-mentioned "screen ID display frame IA" and the text "monitoring screen" in the upper left are so-called text components TX. Usually, no device is assigned to the text component TX.

[0100] Below the text component TX1 "Monitoring screen" is arranged the text component TX2 "Product number". Below the text component TX2 is arranged a numerical display box 241 as a character display component CP. A specific device (which may be an internal device in the programmable display 50 or an external device in the PLC 1; the same applies to the following parts) is assigned to the character display component CP. The character or a series of characters defining the corresponding device is displayed on the character display component CP. Figure 2 In the exemplary display screen shown, a series of characters “ABC-123” is displayed as character display components CP in the numerical display frame 241 .

[0101] On the right side of the text component TX1 "Monitoring screen", a lamp component RP indicating "normal" and "error" is arranged (the lamp component is one of the functional components FP). A specific device is assigned to the lamp component RP. Component icons indicating the lighting and extinguishing conditions are selectively displayed according to the device value of their corresponding device. Figure 2 In the exemplary display screen shown, a component icon indicating a lighting condition is displayed in the area of ​​the lamp assembly RP1 indicating "normal", and a component icon indicating a extinguishing condition is displayed in the area of ​​the lamp assembly RP2 indicating "error".

[0102] A meter assembly MP corresponding to a "thermometer" is arranged on the right side of the light assembly RP. A specific device is assigned to the meter assembly MP. The angular position of the pointer of the meter assembly MP dynamically swings according to the device value of its corresponding device. Figure 2 The situation where the device value is 60 is shown.

[0103] exist Figure 2A text component TX3 "Counter setting value current value reset counter chart" is arranged in the central part. Below the text component TX3, text components TX4, TX5, TX6 and TX7 of "Product A", "Product B", "Product C" and "Product D" are arranged. On the right side of the text components TX4, TX5, TX6 and TX7, a numerical display component NP indicating the setting value and current value of the corresponding product is arranged. A specific device is assigned to the numerical display component NP. The device value of the device is displayed in the area of ​​its corresponding numerical display component NP. Figure 2 In the exemplary display screen shown, the numerical display components NP "100" and "80" are arranged on the row corresponding to product A. In addition, the numerical display components "100" and "10" are arranged on the row corresponding to product B. In addition, the numerical display components "100" and "100" are arranged on the row corresponding to product C. In addition, the numerical display components "100" and "80" are arranged on the row corresponding to product D.

[0104] A switch component SP with "RESET" written thereon is arranged on the right side of the numerical display component NP as a reset switch 246. Likewise, a specific device is assigned to the switch component SP. The switch ON icon and the switch OFF icon in the area of ​​the switch component SP are switched from one to another according to the device value of their corresponding device. Figure 2 In the case of a touch operation on the reset switch 246, the state of the assigned specific device can be switched to another state (e.g., from 1 to 0) by a touch operation on the reset switch 246. The touch operation on the switch can reset the current value of its corresponding product to 0 (in other words, the device value assigned to the device of the touched numerical display component NP can be rewritten to 0).

[0105] A graph component GP representing a corresponding counter graph is arranged on the right side of the switch component SP as the reset switch 246. Likewise, a specific device is assigned to the graph component GP. The length of the bar of the bar graph changes dynamically according to the device value of its corresponding device. Figure 2 In this case, the length of the bar varies with the current value of its corresponding product (in other words, the device assigned to the numerical display component NP representing the current value is the same as the device assigned to the graph component GP representing the counter graph).

[0106] As described above, various components that can be arranged on a screen image (a page) identified by a corresponding screen ID include components to which corresponding devices are assigned, components to which corresponding devices are not assigned, components to which corresponding component icons / images are assigned, and components to which corresponding component icons / images are not assigned. The data structure of a screen image will be discussed in more detail later.

[0107] The programmable display 50 includes a touch panel arranged on the display screen, and detects the user's touch operation. When the user touches any functional component FP, the status of the device assigned to the functional component FP can be changed. For example, when the functional component of the switch is touched, the ON / OFF status of the device assigned to the switch will change. Therefore, the touch panel can realize the function of the switch. Fig.11 The touch detector 53 discussed above detects a touch operation by a user.

[0108] (PLC 1)

[0109] The structure of the PLC 1 will now be described. Figure 1 The PLC 1 shown includes a plurality of units connected to each other. These units can communicate with each other via an inter-unit bus 90. In a broad sense, the unit is composed of a CPU mounting unit 3 and an expansion unit 4. The CPU mounting unit 3 is also called a main unit or a basic unit, and performs the basic actions of the PLC 1. The expansion unit 4 is a function expansion unit for expanding the functions of the CPU mounting unit 3. Figure 1 In the exemplary system shown, the expansion unit 4 is a camera unit 4c, a motion unit 4d, a communication unit 4e, and an I / O unit 4f. The camera unit 4c, which is a type of expansion unit 4, is connected to a camera 98 so that an image of the object WK is captured based on a predetermined timing. The camera unit 4c provides the image to the CPU mounting unit 3. The motion unit 4d is also referred to as a positioning unit, and controls the position of the object to be controlled (also referred to as an axis). Typically, a drive source such as an electric motor is provided for each axis. The communication unit 4e includes a communication unit processor 41e, and can communicate with an external device. The I / O unit 4f includes an I / O unit processor 41f to which an input / output device SS such as a sensor is connected. The CPU mounting unit 3 collects data from the expansion unit 4, and controls the required operations of the expansion unit 4.

[0110] [System structure of PLC system]

[0111] In order for those skilled in the art to better understand the PLC 1, a typical structure of the PLC 1 and its operation are now described.

[0112] Figure 3 FIG. 2 shows an exemplary structure of a programmable logic controller system according to an embodiment of the present invention. Figure 3As shown, the programmable logic controller system includes a PC 2 that can edit user programs such as ladder diagram programs, and a PLC 1 for controlling various control devices installed in factories, etc. PC is the abbreviation name of a personal computer. The user program can be written by using a ladder diagram language, a graphical programming language such as a motion program using a flow chart format (e.g., SFC (sequential function chart)), or a high-level programming language such as C language. Hereinafter, for ease of explanation, a ladder diagram program is illustratively used as a user program. However, the user program according to the present invention is not limited to such a ladder diagram program.

[0113] The PLC 1 is composed of a CPU mounting unit 3 including a CPU and one or more expansion units 4. The one or more expansion units 4 are detachably mounted to the CPU mounting unit 3. For example, the expansion unit 4a may be a positioning unit for driving an electric motor (field device 10a) and positioning a workpiece, and the expansion unit 4b may be a counter unit. The counter unit counts signals from an encoder (field device 10b) such as a manual pulse generator. The letters a, b, c, ... attached to the last digit of the reference symbol are occasionally omitted. A system including the PLC 1 and the PC 2 may be referred to as a programmable logic controller system.

[0114] The CPU mounting unit 3 includes a PLC side display unit 5 and a PLC side console 6. The PLC side display unit 5 can display the operating status of the expansion unit 4 mounted to the CPU mounting unit 3, etc. The PLC side display unit 5 can change its screen according to the user's input on the PLC side console 6. The PLC side console 6 can be a button or the like integrally incorporated into the CPU mounting unit 3, or an external input unit such as a console, a mouse, or a keyboard, etc. Alternatively, the PLC side display unit 5 can be a touch panel that also serves as a console.

[0115] The PLC side display unit 5 usually displays the current value (device value) of the device in the PLC 1, and error information related to errors occurring in the PLC 1, etc. The device refers to an area set in the memory for storing device values ​​(device data). The device can also be called a device memory. The device value is information indicating the input status provided from the input device, the output status provided to the output device, or the status of the internal relay (auxiliary relay), timer, counter or data memory defined in the user program. The device value can be classified into a bit type and a word type. A bit device stores a 1-bit device value. A word device stores a 1-word device value.

[0116] The expansion unit 4 is prepared to expand the function of the PLC 1. A field device (device to be controlled) 10 corresponding to the function of the expansion unit 4 is connected to the corresponding expansion unit 4. As a result, the field device 10 is connected to the CPU mounting unit 3 via its expansion unit 4. The field device 10 may be an input device such as a sensor and a camera, or an output device such as an actuator. Two or more field devices 10 may be connected to one expansion unit 4.

[0117] (Programming device 70)

[0118] PC 2 implements programming device 70. Programming device 70 is a device connected to PLC 1 and performs settings, control during actual operation, confirmation of operation, etc. In addition, PLC engineering tools can create various programs for indicating the operation of PLC 1 or a programmable logic controller system including PLC 1, and edit and correct the created programs. In this sense, programming device 70 is also called a program writing support device and an engineering tool for programmable logic controller, etc. The programming device 70 can generate the operation of the device based on the operation record data for recording the past operation of the programmable logic controller system. The operation record data includes project data including user programs such as ladder diagram programs and setting data such as unit configuration information of units, and log data as actual operation data including device values ​​of the device during actual operation and image data of the camera. The programming device 70 can read the project data in the operation record data and edit the project data. In this sense, the programming device 70 is called a project data editing program.

[0119] For example, PC 2 is a portable notebook or tablet-type personal computer, including a display unit 7 and a PC-side console 8. A ladder diagram program as an exemplary user program for controlling PLC 1 is written by using PC 2. The written ladder diagram program is converted into mnemonic code in PC 2. PC 2 is connected to the CPU installation unit 3 of PLC 1 via a communication cable 9 such as USB (Universal Serial Bus), and provides the ladder diagram program converted into mnemonic code to CPU installation unit 3. CPU installation unit 3 converts the ladder diagram program into machine code and stores the machine code in a memory included in CPU installation unit 3. Although mnemonic code is provided to CPU installation unit 3 in the present embodiment, the present invention is not limited to this. For example, PC 2 can convert mnemonic code into intermediate code and provide the intermediate code to CPU installation unit 3.

[0120] The PC-side console 8 of the PC 2 may include a pointing device such as a mouse connected to the PC 2. The PC 2 may be removably connected to the CPU mounting unit 3 of the PLC 1 via a communication cable 9 other than the USB. The PC 2 may be wirelessly connected to the PLC 1 without any physical cable such as the communication cable 9.

[0121] (Ladder diagram program)

[0122] Figure 4 The figure shows the ladder diagram that will be displayed on the display unit 7 of the PC 2 when the ladder diagram program is written. Figure L d. PC 2 displays a plurality of cells arranged in a matrix shape on display unit 7. Symbols of virtual devices can be arranged in the cells. The symbols represent input relays or output relays, etc. A relay circuit is formed by such a plurality of symbols. For example, a trapezoidal Figure L d has 10 columns×N rows of cells (N is an arbitrary natural number). The symbols of the virtual devices can be arranged appropriately in the cells of each row.

[0123] Figure 4 The relay circuit shown is formed by appropriately connecting the following symbols to each other: three symbols of a virtual device (hereinafter referred to as "input device") that becomes on / off based on an input signal from an input device, and a symbol of a virtual device (hereinafter referred to as "output device") that becomes on / off in order to control the operation of an output device.

[0124] The alphanumeric characters ("R0001", "R0002", and "R0003") indicated above the symbols of the input devices indicate the device names (address names) of the input devices. The characters ("Mark 1", "Mark 2", and "Mark 3") indicated below the symbols of the input devices indicate device comments related to these input devices. The characters ("Return to Origin") indicated above the symbols of the output devices indicate labels that are texts indicating the functions of the output devices.

[0125] exist Figure 4 In the example shown, the two symbols of the input devices corresponding to the device names "R0001" and "R0002" are connected in series so as to form an AND circuit. In addition, the symbol of the input device corresponding to the device name "R0003" is connected in parallel with the AND circuit formed by the two symbols of the input devices so as to form an OR circuit. That is, in this relay circuit, when both input devices corresponding to the two symbols of the first row are turned on, or when the input device corresponding to the symbol of the second row is turned on, only the output device corresponding to the symbol of the first row is turned on.

[0126] (Programming device 70)

[0127] Figure 5 70 is a block diagram of the PC 2 that implements the programming device 70. Figure 5 As shown, the PC 2 includes a PC-side memory section 11, a PC-side CPU 21, a display section 7, a PC-side console 8, a PC-side storage device 22, and a PC-side communication section 23. The display section 7, the PC-side console 8, the PC-side storage device 22, and the PC-side communication section 23 are electrically connected to the PC-side CPU 21.

[0128] The PC-side memory section 11 is a scratch memory for providing a work space for processing by the PC-side CPU 21, and is generally constituted by a RAM, etc. The operation log data includes project data.

[0129] The PC side storage device 22 may include a hard disk drive, a semiconductor memory, a ROM, etc., and may additionally include a removable memory card. CPU is an abbreviation of a central processing unit. ROM is an abbreviation of a read-only memory. RAM is an abbreviation of a random access memory.

[0130] The user runs the editing software as a computer program stored in the PC-side storage device 22 on the PC-side CPU 21, thereby editing the project data by operating the PC-side console 8. The editing software corresponds to a project data editing program to be executed by the PC 2.

[0131] (Project data)

[0132] The project data includes one or more user programs (e.g., ladder diagram programs), and unit configuration information related to the CPU mounting unit 3 and the expansion unit 4. The project data may include program configuration information indicating what type of program components form the user program. The unit configuration information includes a connection point between the expansion unit 4 and the CPU mounting unit 3, information indicating the functions of the CPU mounting unit 3 (e.g., communication function and positioning function), information indicating the functions of the expansion unit 4 (e.g., camera function), and the like.

[0133] Project data editing includes creation and modification of project data. The project data created by using the project data editing program is stored in the PC-side storage device 22. The user can read the project data stored in the PC-side storage device 22 when necessary, and modify the project data by using the project data editing program. The PC 2 is connected to the CPU installation unit 3 via the communication cable 9, and can communicate with the CPU installation unit 3 via the PC-side communication unit 23. The PC-side CPU 21 sends the project data to the CPU installation unit 3 via the PC-side communication unit 23.

[0134] The project data editing program includes an editing mode, a monitoring mode, and a hysteresis mode. The editing mode is also referred to as the edit mode, etc. The project data can be edited in the editing mode. The simulation is run in the monitoring mode for user program debugging, etc. In addition, a real-time display of changes in the device values ​​of the device to be controlled when the FA system is operating can be performed in the monitoring mode. The hysteresis mode is also referred to as the replay mode and the time machine reproduction, etc. The hysteresis can be reproduced in the hysteresis mode. The editing mode, the monitoring mode, and the hysteresis mode can be switched from one mode to another using a mode switcher.

[0135] (PLC 1)

[0136] Figure 6 This is the functional block diagram of PLC 1. Figure 6 As shown, the CPU installation unit 3 includes a CPU installation unit processor 31, a PLC side display unit 5, a PLC side console 6, a CPU installation unit storage unit 32, and a PLC side communication unit 33. The PLC side display unit 5, the PLC side console 6, the CPU installation unit storage unit 32, and the PLC side communication unit 33 are electrically connected to the CPU installation unit processor 31.

[0137] (CPU mounting unit storage unit 32)

[0138] The CPU mounting unit storage section 32 includes a project storage section 35 , a PLC-side device section 34 , a temporary recording section 91 a , and a saving memory 36 .

[0139] The project storage section 35 stores project data supplied from the PC 2. Furthermore, the CPU mounting unit storage section 32 stores a control program used by the CPU mounting unit 3.

[0140] The PLC side device unit 34 includes a bit device and a word device, etc. Each device stores a device value. The PLC side device unit 34 is used as a device memory for storing device values ​​of the device. The device unit 34 can also be used as a storage area to be referenced based on a user program.

[0141] The temporary recording unit 91a records, in chronological order, the device values ​​stored in the PLC-side device unit 34. The temporary recording unit 91a can be constituted by a ring buffer or the like.

[0142] The saving memory 36 saves the device values ​​recorded in the temporary recording section 91a in chronological order. The saving memory 36 is configured as a nonvolatile memory such as the internal memory 37 or the removable memory card 36A.

[0143] The CPU installation unit storage unit 32 has multiple storage areas. The CPU installation unit storage unit 32 may also include RAM, ROM, or a memory card. Figure 6In the illustrated example, the saving memory 36 is constituted by a removable memory card 36A which is an SD card (SD card, trade name).

[0144] (CPU mounting unit processor 31)

[0145] The CPU mounting unit processor 31 includes a program execution unit 40, a storage condition setting unit 45, a recording control unit 39, a storage control unit 39C and an event collection unit 92b. The program execution unit 40 repeatedly executes the user program. The PLC side device unit 34 as a storage area to be referenced by the program execution unit 40 based on the device value of the device.

[0146] The save condition setting unit 45 is a component that defines various conditions. In the present embodiment, the save condition setting unit 45 defines a first trigger condition, a second trigger condition, and a buffer recording time period. The first trigger condition relates to a recording trigger for triggering the temporary recording unit 91a to record a device value. The second trigger condition relates to a saving trigger for triggering the storage memory 36 to save the device value. The buffer recording time period relates to a time period during which the temporary recording unit 91a temporarily records the device value. The buffer recording time period includes at least one of a time period until a reference time and a time period from a reference time. The reference time is determined by the recording trigger.

[0147] The saving condition setting section 45 may define a recording start trigger condition for starting recording of device values ​​in the temporary recording section 91a as a first trigger condition. In addition, the saving condition setting section 45 may define a certain period of time from a reference time determined by the recording start trigger as a buffer recording period.

[0148] When the first trigger condition related to the record trigger is satisfied, the record control section 39 records the time sequence device value corresponding to the buffer recording time period which is a certain time period from the reference time determined by the record trigger as log data in the temporary record section 91a. The record control section 39 keeps the recorded log data in the temporary record section 91a until the second trigger condition related to the save trigger is satisfied or the first trigger condition related to the record trigger is satisfied again at an earlier time. When the first trigger condition related to the record trigger is satisfied again, the record control section 39 records the time sequence device value corresponding to the buffer recording time period which is a certain time period from the reference time determined by the new record trigger as log data in the temporary record section 91a.

[0149] In the case where the second trigger condition related to the save trigger is satisfied, the save control section 39C saves the log data held in the temporary recording section 91a by the record control section 39 into the save memory 36. At this time, in the case where the second trigger condition related to the save trigger is satisfied so that a new save trigger is generated, the save control section 39C preferably saves the log data held in the temporary recording section 91a by the record control section 39 and corresponding to the latest record trigger before the new save trigger is generated into the save memory 36. In this case, the save control section 39C holds the log data recorded during the buffer recording time period even after the buffer recording time period has passed, and then saves the log data held corresponding to the latest record trigger when a new save trigger is generated. It should be noted that the log data held in the record control section 39 is not limited to the log data held corresponding to the latest record trigger, but may be the log data held corresponding to the second latest or third latest record trigger.

[0150] The event collection unit 92b collects event data related to a plurality of events occurring in the PLC 1 or the device to be controlled (field device 10) controlled by the PLC 1. The event collection unit 92b associates device values ​​with corresponding event occurrence times, and stores the device values ​​associated with the corresponding event occurrence times in the temporary recording unit 91a in chronological order.

[0151] like Figure 6 As shown, the CPU installation unit 3 and the expansion unit 4 are connected via an inter-unit bus 90 which is a kind of expansion bus. The communication function related to the inter-unit bus 90 can be included as a part of the PLC side communication unit 33. In addition, the PLC side communication unit 33 can have a network communication circuit. The CPU installation unit processor 31 can send log data and the like to the PC 2 and the cloud via the PLC side communication unit 33.

[0152] The inter-unit bus 90 is now further described. The inter-unit bus 90 is a bus that performs input / output refreshing and the like as described below. Communication control in the inter-unit bus 90 is implemented by a so-called bus master 38. The bus master may be provided as a part of the PLC-side communication section 33, or the bus master 38 may be formed as a part of the CPU-mounted unit processor 31. The bus master 38 is a control circuit for controlling communication via the inter-unit bus 90, and performs communication such as input / output refreshing and the like described later between the expansion units 4 based on a communication request from the CPU-mounted unit processor 31.

[0153] The extension unit 4 includes an extension unit processor 41 and an extension unit memory 42. The extension unit processor 41 controls the field device 10 based on the instructions (device values) stored in the device from the CPU installation unit 3. The extension unit processor 41 stores the control results of the field device 10 in a device called a buffer memory. The control results stored in the device are sent to the CPU installation unit 3 in the input / output refresh. The control results stored in the device are sent to the CPU installation unit 3 based on the read instructions from the CPU installation unit 3 even when it is not the timing of the input / output refresh. The extension unit memory 42 includes RAM and ROM, etc. In particular, the RAM can provide a storage area to be used as a buffer memory with certainty. In addition, the extension unit memory 42 can have a buffer for temporarily holding the data (e.g., still image data or motion image data) acquired by the field device 10.

[0154] (Scan time of CPU mounted unit 3)

[0155] exist Figure 7 The schematic diagram of FIG. 1 shows the scan time of the CPU installation unit 3. Figure 7 As shown, the scan time ST of a single cycle is formed by the inter-unit communication 201 for input / output refresh, the program execution 202 and the end (END) processing 204. In the inter-unit communication 201, the CPU mounting unit 3 sends the output data obtained by executing the ladder diagram program from the CPU mounting unit storage section 32 in the CPU mounting unit 3 to an external device such as an expansion unit 4. In addition, the CPU mounting unit 3 receives input data from an external device such as the expansion unit 4, and stores the input data in the CPU mounting unit storage section 32 in the CPU mounting unit 3. In other words, by output refresh, the device of the expansion unit 4 is changed with respect to the device value stored in the PLC-side device section 34 of the CPU mounting unit 3. Similarly, by input refresh, the device of the CPU mounting unit 3 is changed with respect to the device value stored in the device of the expansion unit 4. Similarly, by input refresh, the device of the programmable display 50 (refer to Fig.11 The device value stored in the display side device part 56a) is changed to the device of the CPU mounting unit 3. As a result, the device of the CPU mounting unit 3 and the device of the expansion unit 4 are synchronized with each other by input / output refreshing, that is, so-called mirroring is realized.

[0156] It should be noted that another method that can exchange device values ​​between units to update device values ​​other than refresh timing (inter-unit synchronization) can be used. However, the CPU mounting unit 3 rewrites the device of the CPU mounting unit 3 at any time, and the expansion unit 4 rewrites the device of the expansion unit 4 at any time. That is, the device of the CPU mounting unit 3 can be accessed by the internal components of the CPU mounting unit 3 at any time. Similarly, the device of the expansion unit 4 can be accessed by the internal components of the expansion unit 4 at any time. The device values ​​are exchanged between the CPU mounting unit 3 and the expansion unit 4 basically at the time of refreshing to update the device values, so that the CPU mounting unit 3 and the expansion unit 4 can be synchronized with each other.

[0157] exist Figure 7 At the timing of program execution 202 shown in FIG. 1 , the CPU mounting unit 3 executes the program (calculation) by using the updated input data. Figure 7 As shown, in the program execution 202, multiple program modules or ladder programs can be executed based on the project data. A program module refers to one of the program components that constitute a user program. For example, such a program module includes a main ladder program and a sub-ladder program. A program module is also called a functional block divided from a program based on a function. The CPU installation unit 3 calculates data by executing such a program.

[0158] The end process 204 refers to general processing related to data communication with an external device such as the programmable display 50 connected to the PC 2 or the CPU mounting unit 3 , and peripheral services such as system error checking.

[0159] As described above, PC 2 creates a ladder program corresponding to the user's input and sends the created ladder program to PLC 1. Input / output refreshing, ladder program execution and end processing form a cycle (cycle) (one scan). PLC 1 periodically executes this cycle, in other words, repeatedly executes this cycle in a cyclic manner. This periodic scan execution can control various output devices (motors, etc.) based on timing signals from various input devices (sensors, etc.). In addition, CPU installation unit 3 and expansion unit 4 have an internal control cycle in addition to the scan cycle. CPU installation unit 3 and expansion unit 4 control the functions of field device 10, etc. based on the internal control cycle.

[0160] (Logging)

[0161] The device values ​​obtained when the PLC executes the user program often help the user to improve or correct the user program. To this end, the PLC obtains the pre-specified device values ​​and creates log data. Here, the devices managed by the PLC 1 include not only the devices used by the user program, but also the devices not used by the user program. In addition, some devices can help the user to improve or correct the user program, while other devices may not be helpful. Typically, the PLC manages thousands of devices. Therefore, the selection of the required device becomes a burden for the user. For this reason, the PC analyzes the user program and extracts the devices used by the user program or described in the user program as the load log object. As a result, the burden on the user can be reduced.

[0162] In the case where all devices managed by PLC 1 are extracted as load log objects, the scan time will be very long. The reason is that the load log is performed as one of the user programs or when the input / output is refreshed. There may be a situation where the delay caused by the load log interferes with the user's desired operation of the user program. Therefore, it is necessary to appropriately limit the number of devices to be extracted as load log objects.

[0163] As mentioned above, the user program may include a plurality of program components. It may be sufficient for the user to selectively load the log with the device associated with the program component that the user desires to revise from the plurality of program components. In addition, the user may wish to withdraw a specific program component from the object to be extracted, or to add other specific program components to the object to be extracted. Therefore, it may be convenient for the user to select one or more program components to add or withdraw the device associated with the selected program component relative to the loaded log object.

[0164] Figure 8 2 is a detailed functional block diagram showing the CPU mounting unit processor 31 of the CPU mounting unit 3. The same components as those described above are attached with the same reference symbols, and the description of these components is omitted. The CPU mounting unit processor 31 will be described as storing the project data 71 and log setting data 72 received from the PC 2 in the CPU mounting unit storage section 32. The device section 34 of the CPU mounting unit storage section 32 includes a CPU mounting unit device section (CPU unit device section) 34a and an expansion unit device section 34b.

[0165] Figure 8The CPU installation unit processor 31 shown includes a program execution unit 40, a unit control unit 80b, a detection unit 82, a recording unit 81, an event collection unit 92a, a time management unit 83a and an output unit 84. The detection unit 82 detects an external device rewriting operation to any device included in the PLC side device unit 34. When the user program execution is terminated, or when a predetermined output condition is met (such as when the storage trigger relay of the memory card is turned on), the output unit 84 writes the project data 71, the log data 73 and the image data to the removable memory card 36A or the internal memory 37 corresponding to the storage memory 36. The log data 73 is recorded in sequence in the memory (for example, a ring buffer) until the predetermined output condition is met. In the case where the capacity of the memory becomes full, the oldest log data 73 will be erased so that the new log data 73 is additionally recorded in the memory (recording log data in a so-called FIFO manner). The removable memory card 36A can be removed from the CPU installation unit 3 and installed in the installation unit of the PC 2. Therefore, the log data 73 can be displayed on the display unit 7 of the PC 2. The output unit 84 can transmit the log data 73 to the PC 2, the cloud, or the like via the PLC-side communication unit 33.

[0166] As described above, the program execution section 40 repeatedly executes the user program. The unit control section 80b controls the program execution section 40, and performs input / output refreshing between the unit control section 80b and the expansion unit 4. The program execution section 40 repeatedly executes the user program included in the project data 71, thereby controlling the expansion unit 4 based on the user program. The program execution section 40 writes the device value into the output type device to be held in the CPU mounting unit device section 34a of the PLC side device section 34, and reads the device value from the input type device held in the CPU mounting unit device section 34a, based on the user program.

[0167] Based on the log setting data 72, the recording section 81 reads the device value from the PLC side device section 34 (CPU mounting unit device section 34a and expansion unit device section 34b), reads the device value from the buffer memory of the expansion unit 4, and writes the read device value to the temporary recording section 91a (for example, a ring buffer). The recording section 81 loads the log based on a predetermined timing in the end processing as described above. The log data 73 and the project data 71 are written to the save memory 36 (for example, the removable memory card 36A and the internal memory 37).

[0168] When a predetermined saving condition or a collection start condition for data collection is satisfied, the event collection unit 92a reads the device value specified by the log setting data 72 from the device value stored in the PLC side device unit 34, and obtains the time information from the time management unit 83a. The event collection unit 92a stores the device value and its corresponding time information associated with each other in the temporary recording unit 91a. The event collection unit 92a can obtain the device value and its corresponding time information, and store them in the temporary recording unit 91a according to each collection cycle (for example, scanning cycle) specified by the log setting data 72.

[0169] A ring buffer is used appropriately as the temporary recording section 91a. The reason for using the ring buffer is that all data stored in the ring buffer is not saved as log data 73 in the saving memory 36. For example, when a predetermined saving condition is satisfied, the saving section 93 can read the device value and time information from the temporary recording section 91a constituted by the ring buffer, and can create log data 73. The saving section 93 can save the created log data 73 in the saving memory 36. In addition, when a predetermined saving condition is satisfied, the saving section 93 can read a large volume of data including a large number of device values ​​and time information from the expansion unit 4, and can create log data 73 and save the log data 73 in the saving memory 36.

[0170] The storage unit 93 stores the above-mentioned device value and time information and the above-mentioned bulk data and time information in a manner related to each other (in a related manner). Here, "related manner" storage refers to storage that enables easy reproduction in the PC 2, and may be, for example, file management that makes multiple files related to each other. Specifically, in the case where a first subfolder and a second subfolder storing device values ​​and their time information and bulk data and their time information are placed under a specific folder in the storage memory 36, the path (directory path) to the specific folder is used as a common mark, and the files in the first subfolder and the second subfolder can be saved in a "related manner" by using the common mark. In the case where other folders are placed at the same level (directory) as the above-mentioned specific folder, the other folders mean data packets saved at other moments (different timings). Needless to say, similar subfolders can be placed under the other folders. Therefore, the storage unit 93 can store the above-mentioned device value and time information and the above-mentioned data (bulk data) and time information in multiple files identified by a common mark (predetermined directory path), and save these files. Furthermore, a file name may be used as a common identifier, and, for example, a device value and its time information and data and its time information may be saved in a "related manner" by creating a file with a common file name or a related file name. In addition, a device value and data may be related to each other by using the device value and the time information of the data (large volume data) as a keyword, and listed and then stored in a single file. In this case, the device value and its time information and the data and its time information may be saved in a "related manner".

[0171] It is needless to say that although in the present embodiment, large-capacity data is considered as an example of data from a monitoring device, the data from the monitoring device may be continuous data such as motion data, communication data, and audio data. The sending unit 94 may send the log data 73 to PC 2, the cloud, and the like. When the temporary recording unit 91a constituted by a ring buffer becomes full, the event collection unit 92a overwrites the oldest information already maintained in the ring buffer with the latest information. Although a ring buffer is used as an example of a buffer for the temporary recording unit 91a, this is merely illustrative. A FIFO-type buffer will be well used as a buffer for the temporary recording unit 91a. The above-mentioned recording unit 81 and event collection unit 92a may be separate components, or may be integrally constituted as a single component with each other.

[0172] As described above, the CPU mounting unit 3 and the expansion unit 4 have one or more functions. Various devices are assigned to these functions. Therefore, it may be convenient for the user to select one or more functions to add or withdraw the devices assigned to the selected functions with respect to the loaded log object. For example, in the event of an unexpected event related to the communication function of the CPU mounting unit 3, the user can easily resolve the unexpected event by referring to the device value of the device related to the communication function of the CPU mounting unit 3.

[0173] (Camera unit 4c)

[0174] The camera can be connected to the PLC 1. To this end, the extension unit 4 constituting the PLC 1 may include a camera unit 4c to which the camera can be connected. Fig. 9 The PLC 1 is shown in a functional block diagram of FIG. 1. The illustrated PLC 1 includes an external orientation interface 97, an image recorder 520, and a camera unit processor 41c. The external orientation interface 97 is connected to an external camera and receives image data from the camera. The image recorder temporarily records the image data received from the camera via the external orientation interface 97. The camera unit processor 41c collects the image data received from the camera via the external orientation interface 97, associates the image data with information related to the moment when the image data was acquired, and temporarily stores the image data associated with the information related to the moment in the image recorder.

[0175] When the saving condition is satisfied, the PLC 1 associates the image data temporarily stored in the image recorder by the camera unit processor 41c with the operation record data, and saves the image data associated with the operation record data. The image data associated with the operation record data may be saved, for example, in the saving memory 36 in the CPU mounting unit 3, or in the camera setting information storage section 530 in the camera unit.

[0176] The programmable display 50 acquires the operation log data stored in the storage memory 36, and displays an image corresponding to the image data included in the operation log data on the display unit based on the information about the acquisition time included in the operation log data.

[0177] Reference now Fig.10 The function of the extension unit processor 41 of the camera unit 4c, which is one of the extension units 4 having a camera input function, is described with reference to the functional block diagram of FIG. Figure 8The clock of the moment management unit 83a of the CPU installation unit 3 shown in the figure is synchronized. For example, the moment management unit 83a of the CPU installation unit 3 sends the moment information to the moment management unit 83b in the end processing. The moment management unit 83b synchronizes the clock of the moment management unit 83b with the clock of the moment management unit 83a of the CPU installation unit 3 based on the received moment information. The clock can be implemented by a counter that counts time based on moment information. For example, when a predetermined collection condition (for example, a predetermined relay device is turned on (ON)) is met, the event collection unit 92b will periodically provide a trigger signal. The moment management unit 83b obtains the moment information corresponding to the instant of receiving the trigger signal from the clock, and stores the moment information in the moment information buffer 95. The expansion unit memory 42 includes a moment information buffer 95 and a ring buffer 91b. The external directional interface 97 is an interface for connecting a camera 98 to the camera unit 4c. The external directional interface 97 periodically provides a trigger signal issued by the event collection section 92b to the camera 98, or provides image data provided by the camera 98 to the image receiving section 96a. Image data is an example of large-volume data. The external directional interface 97 is an example of an interface that is connected to a monitoring device such as a camera 98 and is provided with data (image data) from the monitoring device. The image receiving section 96a is all or part of the function execution section 96 that performs a camera function, which includes receiving image data from the camera 98 via the external directional interface 97. In the present embodiment, the function execution section 96 (image receiving section 96a) controls the camera 98 based on camera parameters (an example of setting information) such as exposure time, gain, white balance, and contrast. These camera parameters are specified by setting desired parameter values ​​in the PC 2, and are controlled via the external directional interface 97. Figure 6 The PLC side communication section 33 and the CPU mounting unit processor 31 of the CPU mounting unit 3 shown are sent to the function execution section 96. From this point of view, Figure 6The PLC side communication unit 33 shown is another example of an interface for receiving setting information from an external setting device such as a PC 2 and a display. In addition, the PLC side communication unit 33 receives the user program created in the PC 2 as described above. The camera 98 captures an image based on a trigger signal and provides image data corresponding to the captured image. The image receiving unit 96a transmits the image data to the event collection unit 92b. The event collection unit 92b associates the moment information maintained in the moment information buffer 95 with the image data provided from the image receiving unit 96a, and stores the associated moment information and image data in the ring buffer 91b. When the ring buffer 91b becomes full, the event collection unit 92b overwrites the oldest information maintained in the ring buffer 91b with the latest information. Although the event collection unit 92b automatically and periodically provides the imaging trigger signal to the camera 98 in the present embodiment, the present invention is not limited thereto. The event collection unit 92b can, for example, provide the imaging trigger signal to the camera 98 based on an instruction from a user program.

[0178] The CPU installation unit 3 communicates with the expansion unit 4 by using one of the refresh communication performed for each scan, the direct communication that can be performed at any time, and the message communication performed by best efforts when an event occurs. For example, the preservation unit reads the image data and its corresponding time information from the ring buffer 91b of the expansion unit 4 by using direct communication, and adds these image data and time information to the log data 73. A plurality of direct communications with priority levels can be installed as direct communications. In this case, the direct communication related to the user program can have a relatively high priority level, and the direct communication related to the loading log can have a relatively low priority level. This priority assignment can reduce the impact of the loading log on the execution of the user program.

[0179] As mentioned above, Fig. 9 1 shows a functional block diagram of a programmable logic controller system including a camera unit 4c. In the illustrated programmable logic controller system, a PLC 1 is composed of a CPU mounting unit 3, a camera unit 4c, and another extension unit 4. The CPU mounting unit 3, the camera unit 4c, and the extension unit 4 are connected to each other via an inter-unit bus 90. The PC 2 is connected to the CPU mounting unit 3 via a communication line CL. The camera 98 is connected to the camera unit 4c via an imaging trigger line. The camera 98 includes a camera setting recording section 575. The CPU mounting unit 3 includes a device section. The camera setting recording section 575 records setting information related to the camera 98.

[0180] Fig. 9The camera unit 4c shown is connected to the CPU mounting unit 3 as a base unit via the inter-unit bus 90. An imaging trigger line and an image communication line are connected to an external orientation interface 97 that connects a camera 98 to the camera unit 4c. By sending an ON / OFF signal for defining an imaging trigger for the camera 98 via the imaging trigger line, the synchronization timing in the inter-unit bus 90 can be extended even to the camera 98. As a result, the recording timing of the device value and the acquisition timing of the camera image data can be accurately synchronized with each other.

[0181] (Camera unit 4c)

[0182] The camera unit 4c is electrically connected to the CPU mounting unit 3 via the inter-unit bus 90. The camera unit 4c is a unit for connecting to a camera 98 that can capture an image of a predetermined area based on an imaging trigger from the PLC 1 and generate image data corresponding to the captured predetermined area. Fig. 9 The illustrated camera unit 4 c includes an external orientation interface 97 , a camera setting information storage section 530 , a camera unit processor 41 c , and an image recorder 520 .

[0183] The camera setting information storage section 530 stores setting information related to the camera 98 including conditions for image pickup triggering. The setting information related to the camera 98 stored in the camera setting information storage section 530 includes setting information created by the programming device 70 and received via the CPU mount unit 3. The user program executed by the CPU mount unit 3 is written in the programming device 70 that can be connected to the CPU mount unit 3.

[0184] The camera unit processor 41c generates an ON / OFF signal for defining an imaging trigger based on the setting information of the camera 98 stored in the camera setting information storage section 530. The camera unit processor 41c acquires image data generated by the camera 98 based on the ON / OFF signal as an imaging trigger.

[0185] The image recorder 520 records the image data acquired by the camera unit processor 41c. The image recorder 520 records the image data acquired by the camera unit processor 41c in chronological order and information about the time when the corresponding image data was acquired. In addition, the image recorder 520 provides the CPU mounting unit 3 with the image data and information about the time when the corresponding image data was acquired based on an instruction from the CPU mounting unit 3.

[0186] The external orientation interface 97 is provided between the camera unit processor 41c and the camera 98. The external orientation interface 97 has an imaging trigger line and an image communication line.

[0187] The imaging trigger line is an interface for providing an ON / OFF signal to the camera 98, the ON / OFF signal being generated in the camera unit processor 41c and defining an imaging trigger for triggering the camera 98 to capture an image. The imaging trigger line is preferably a non-communication line. In this case, since the imaging trigger is provided not through communication but through the I / O of ON / OFF, the imaging trigger can be provided at a very high speed compared to the transmission of the imaging command through communication.

[0188] The external orientation interface 97 and the imaging trigger line are bundled together and form a camera connection cable for connecting the imaging interface and the camera 98 to each other. Therefore, the transmission / reception of all electrical signals for operating the camera 98 can be performed only by connecting the camera unit 4c and the camera 98 to the external orientation interface 97. As a result, the wiring can be made simple. Therefore, the structure of the programmable logic controller can be simplified.

[0189] The camera setting information storage section 530 stores setting information related to the camera 98 received from the CPU installation unit 3 via the inter-unit bus 90. Examples of the setting information of the camera can be provided by various types of information such as frame rate, image quality, rotation, exposure, gain, exposure time, white balance, contrast, gamma, sharpness, and anti-flicker. The camera unit processor 41c is connected to the CPU installation unit 3 or the extension unit 4 via the inter-unit bus 90. The camera unit processor 41c receives image data from the camera 98 via the external directional interface 97 based on the setting information related to the camera 98 stored in the camera setting information storage section 530. The image recorder 520 collects the image data acquired by the camera 98 and records the image data and information related to the time when the image data was acquired in association with each other. Therefore, the programmable logic controller can obtain accurate time synchronization of the device record related to the captured image data generated by the camera 98. In particular, since the ON / OFF signal is transmitted via a dedicated imaging trigger line rather than via a communication line and without command interpretation, time delay can be avoided by such accurate time synchronization.

[0190] (Time series data)

[0191] Now explain Figure 1 The programmable logic controller system shown in the figure stores device values ​​as time-sequential data and displays the device values ​​on the programmable display 50. The PLC 1 stores the time-sequential data related to the device values ​​of the device as a storage area to be referenced by the user program based on the predefined storage conditions. Figure 6The CPU installation unit processor 31 and the CPU installation unit storage unit are shown. The CPU installation unit processor 31 includes a program execution unit 40 that repeatedly executes a user program, a recording control unit 39, and a saving control unit 39C. The CPU installation unit storage unit includes a device unit containing a device as a storage area to be referred to by the program execution unit 30, a temporary recording unit 91a, and a saving memory 36. The temporary recording unit 91a is controlled by the recording control unit 39 when recording. The temporary recording unit 39 collects the device values ​​of the devices stored in the device unit, and associates the device values ​​with information related to the collection time of the device values, and temporarily records the device values ​​associated with the information related to the collection time in the temporary recording unit 91a in time sequence. The saving memory 36 is controlled by the saving control unit 39C when saving. When a predefined saving condition is met, the saving control unit 39C saves the time sequence data related to the device values ​​temporarily recorded in the temporary recording unit 91a as operation record data in the saving memory 36.

[0192] The programmable display 50 connected to the PLC 1 displays the display screen previously defined by the screen data editing device 60 on the display unit 55 . Fig.11 5 is a functional block diagram of a programmable display 50 connected to a screen data editing device 60. Fig.11 As shown, the screen data editing device 60 can be connected to the programmable display 50. Various screen data to be displayed by the programmable display 50 are created by using the screen data editing device 60. The following description will describe the screen data editing device 60.

[0193] (Screen data editing device 60)

[0194] The screen data editing device 60 can be implemented by executing a graphic editing program running on an information processing terminal such as a personal computer. The user creates multiple pages including various functional components FP arranged in a desired layout. The screen data editing device 60 sends the screen data corresponding to the multiple pages created based on the user's input to the programmable display 50. The programmable display 50 stores the sent screen data in its flash memory, etc., and displays the page identified by its screen ID based on the user's touch operation. In an exemplary case, the page corresponding to the screen ID1 is displayed on the display screen of the display unit 55 of the programmable display 50, and a switching component for switching the page to the page corresponding to the screen ID2 is arranged on the page. In this case, when a touch operation on the switching component is detected, the display data of the page corresponding to the screen ID2 is generated, and the page corresponding to the screen ID2 is displayed based on the generated display data.

[0195] As described above, the user can check the contents of the operation log data saved in the PLC 1 through the programmable display 50 according to the present embodiment. For example, a page corresponding to the screen ID 1 is displayed on the display screen of the display unit 55 of the programmable display 50, and a wave display component representing a device wave in the form of time sequence data of the device included in the operation log data is arranged on the page. When the user touches one of the wave display components, the operation log data is read from the CPU mounting unit 3 of the PLC 1, and display data is generated to display the device wave. The device wave of the device to be displayed is displayed on the system screen based on the generated display data.

[0196] The device to be displayed can be defined by the object device setting 52c described later. The object device setting 52c can define the object device for displaying the device wave. A large number of devices are included in the log data of the operation record data. The type and number of device waves of the device to be displayed on the programmable display 50 depend on the site where the programmable display 50 is set. To this end, the programmable display 50 according to the present embodiment stores the devices pre-defined by the user using the screen data editing device 60 as the object device setting 52c. When the user touches one of the wave display components, the programmable display 50 can display the device waves of the appropriate type and multiple devices in the operation record data saved by the PLC 1 according to the site. As a result, faults occurring at the FA site can be immediately and easily eliminated.

[0197] (Programmable display 50)

[0198] The programmable display 50 will now be described. Fig.11 The illustrated programmable display 50 includes a setting storage section 52 , a display processor 51 , a touch detector 53 , a display section 55 , a data memory 56 , a screen data receiver 57 , and a display-side communication section 58 .

[0199] (Storage unit 52 is provided)

[0200] The setting storage unit 52 stores various screen data required for generating display data in the programmable display 50, such as component setting 52a, page setting 52b, object device setting 52c, acquisition device setting 52d, system default screen information 52f, and guidance information 52g. The guidance information 52g is associated with the device specified by the object device setting, and shows how to eliminate the error event that occurs when the saving condition is met. The setting storage unit 52 storing the guidance information 52g serves as a guidance information storage unit.

[0201] The component setting 52a assigns the device to a corresponding component among a plurality of components arranged as a page on one screen image to monitor or change the status of the device of the PLC 1. For example, the assignment of the device to the component arranged on the display screen and the function performed when the touch operation is performed on the corresponding component are defined as the component setting 52a. In addition, the component setting 52a includes a component image corresponding to the component. For example, the component image includes an image indicating the lighting status and the extinguishing status of the lamp, etc.

[0202] The page setting manages the component setting 52a in units of pages by using a page identifier for identifying a plurality of pages. The page identifier may be, for example, a screen ID indicating a corresponding page number. Multiple pages corresponding to a screen image in which one or more components are arranged, each as a page, may be managed in units of pages using a unique screen ID based on the page setting 52b.

[0203] The object device setting 52c specifies an object device that shows a device value to be stored as time-sequential data in the PLC 1 in a wave form as a device wave. The object device having a device wave to be displayed on the programmable display 50 in the operation log data is defined based on selection by the object device setting 52c.

[0204] The acquisition device setting 52d specifies a device having a device value to be acquired as a device wave to be displayed on a real-time graph monitor in a monitoring mode described later. The system default screen information 52f is information on a system default screen prepared in advance.

[0205] The display processor 51 can be implemented by a CPU and software as a program, by hardware such as an FPGA and an ASIC, or by a combination of software and hardware. Needless to say, a plurality of CPUs and a plurality of hardware devices can be used for the display processor 51. In other words, the display processor 51 can be composed of any structure. The display processor 51 includes a display data generator 51a and an operation record data interpretation unit 51b.

[0206] The display data generator 51a can generate display data of a page corresponding to a page identifier in units of pages based on the component settings 52a and the page settings 52b stored in the setting storage unit 52. The display data to be displayed on the display screen of the display unit 55 is generated by the display data generator 51a. In the present embodiment, the touch detector 53 detects a touch operation of the user. When a touch operation is detected, the display data to be displayed is changed according to the touch operation. Specifically, the display data generator determines whether a component (e.g., a switch component SP, etc.) having an assigned function is located at a position indicated by a touch operation of the user on the display screen. In the case where any component is located at the touched position, the function corresponding to the component is performed. More specifically, for example, in the case where the switch component SP is located at the touched position, the status of the device assigned to the switch component SP changes, and a component icon (e.g., a component icon indicating a switch ON or switch OFF status) is displayed on the display screen according to the status of the changed device.

[0207] In the case where no touch operation is detected, the display data generator 51a generates display data to be used for device monitoring. For example, the display data generator 51a generates display data for monitoring the status of the device of the PLC 1 so that the display during the operation of the PLC 1 Figure 2 The page shown. Specifically, the display data generator 51a reads the device value of the device to be used in the display data from the data memory 56 at fixed intervals, and rewrites the value of the display data to generate new display data. The display unit 55 displays the page based on the generated new display data on the display screen. The value in the data memory 56 is synchronized with the device value of the device to be used for display data selected from the devices of the PLC 1, that is, the so-called mirroring is achieved by the display side communication unit 58 described later. Therefore, the status of the device in the PLC 1 can be monitored or changed in real time. The basic processing in device monitoring will be discussed later.

[0208] The operation log data interpretation section 51b reads the management information data in the operation log data, and determines the type of data included in the operation log data (the details will be discussed later).

[0209] (Touch detector 53)

[0210] The touch detector 53 detects a touch operation on the display screen of the display unit 55. The touch detector 53 detects such a touch operation on the display screen using a touch panel. Examples of the touch operation can be provided by long tapping (long pressing), double tapping, flicking, pinching in and out, and the like.

[0211] (Display unit 55)

[0212] The display unit 55 includes a display screen. Based on the display data generated by the display data generator 51a, the page corresponding to the page identifier is displayed on the display unit 55 according to the display data. The display unit 55 may be composed of, for example, an LCD with a touch panel function or an organic electroluminescent device.

[0213] (Data storage 56)

[0214] The data memory 56 holds various settings. In the present embodiment, the data memory 56 includes a display side device section 56a for holding device values. The display side device section 56a stores the device values ​​of the device to be used for displaying data in the device of the PLC 1. The values ​​in the display side device section 56a are appropriately updated by the display side communication section 58 described later.

[0215] (Picture data receiver 57)

[0216] The screen data receiver 57 is an interface for receiving the screen data created and transmitted by the screen data editing device 60. The display processor 51 stores the screen data received by the screen data receiver 57 in the setting storage unit 52.

[0217] (Display side communication unit 58)

[0218] The display side communication unit 58 is a communication interface for communicating with an external device (for example, with PLC 1). The display side communication unit 58 repeatedly communicates with PLC 1 at a predetermined interval (for example, 10 ms) so that the value in the data memory 56 and the device value of the device to be used for displaying data in the device of PLC 1 are synchronized (mirrored) with each other. For example, when one scan of the ladder program is about 100 μs and the communication interval between PLC 1 and the programmable display 50 is 10 ms, the programmable display 50 will read the device in PLC 1 for every 100 scans of the ladder program. In addition, the display side communication unit 58 can perform protocol conversion, etc., if necessary.

[0219] (Display Data Generator 51a)

[0220] When the touch detector 53 detects a first touch operation on the page switching component 131 arranged on the first page displayed on the display screen, the display data generator 51a generates second page display data corresponding to the second page identifier based on the page setting 52b.

[0221] Furthermore, when the touch detector 53 detects a predetermined second touch operation on the display screen, the display data generator 51a generates display data for displaying the device wave of the device specified by the object device setting 52c based on the time sequence data stored in the PLC 1. Then, the display unit 55 displays the second page or the display wave on the display screen based on the display data generated by the display data generator 51a.

[0222] For example, in Fig.12 In the device wave display screen 160 shown in FIG. 1 , the device wave of a predetermined device is displayed on the display screen. Fig.12 In the exemplary image of , devices DM100, DM200, and R000 are graphically displayed. On / off switching of check boxes arranged on the left side of a device enables / disables display of the corresponding device wave.

[0223] According to this configuration, a page switching operation for switching a screen from one page to another and a device wave display operation for displaying a device wave of time-sequential data stored in the PLC 1 can be selectively performed by such a touch operation on the programmable display 50. In this case, the device wave can be seen on the display screen of the programmable display 50, and information useful for immediately eliminating a fault occurring at the FA site can be easily provided.

[0224] Fig.12 The device wave display screen 160 shown is a system screen of the programmable display 50. Fig.12 When the "×" button (cross button) 166 on the upper right is touched, the display screen returns from the system screen to the normal monitoring screen (a screen created by the user in the screen data editing device 60). Fig.12 The device wave display screen 160 shown can be realized by superimposing the time-sequential data read from the operation log data on a system default screen (so-called default template) prepared in advance by a system designer of the programmable display 50. The data structure of the system screen will be discussed in more detail later.

[0225] Although it has been described that the screen is switched from one page to another by touching the page switching component (first touch operation), such a page switcher is not limited to a component dedicated to page switching. Needless to say, for example, the screen is switched from one page to another by a predetermined touch operation such as flicking. In this case, the predetermined operation of switching the screen from one page to another is used as the first touch operation.

[0226] (Functional Block Diagram of Screen Data Editing Device 60)

[0227] The screen data editing device 60 will now be described. Fig.11 The screen data editing device 60 shown includes a screen data editing input unit 63 , a screen data editing display unit 65 , a screen data editing unit 61 , a screen data editing storage unit 62 , and a screen data sending unit 67 .

[0228] The screen data editing input section 63 is an input device such as a mouse and a keyboard, etc. The user operates the screen data editing device 60 via the screen data editing input section 63 to design the layout of components on a page or assign devices to the components.

[0229] The screen data edit display section 65 is a display or the like connected to the screen data edit device 60. On the screen data edit display section 65, the edited screen data can be viewed.

[0230] The screen data editing section 61 edits the screen data including the component setting 52a, the page setting 52b and the object device setting 52c based on the user's input via the screen data editing input section 63. The edited screen data is displayed on the screen data editing display section 65. The user can check the edited screen data on the screen data editing display section 65.

[0231] The screen data edit storage section 62 stores screen data including component settings 52 a , page settings 52 b , and object device settings 52 c .

[0232] The screen data transmission part 67 reads the screen data edited by the screen data editing part 61 from the screen data editing storage part 62 , and transmits the edited screen data to the programmable display 50 .

[0233] (User Interface Screen of Screen Data Editing Device 60)

[0234] Figure 13 to Figure 16 An exemplary user interface screen of the screen data editing device 60 is shown. Fig.13 A page setting screen 110 is shown in which a menu screen and the like can be defined. Through the page setting screen 110, the user can create buttons to be arranged on the screen image (page) of the programmable display 50 and define the functions of the buttons. A screen selection box 111 showing screens that the user can edit is arranged in the left area of ​​the page setting screen 110. A screen display box 112 is arranged in the right area of ​​the page setting screen 110. The editable screens are listed in the screen selection box 111 together with the screen IDs of these screens as page identifiers. The screen selected from the screen selection box 111 is displayed in the screen display box 112. Fig.13In the menu screen (screen ID 0001), the menu screen is selected. In addition, a "Screen" tab 113 and a "System Settings" tab 114 are arranged in the lower area of ​​the screen selection frame 111. When the "System Settings" tab 114 is selected, the display screen switches to Fig.16 The system settings screen 130 is shown. Fig.14 The switch setting screen 120 shown is used to specify display components such as switches to be arranged in the screen display frame 112. Fig.13 When the user selects one of the switches or right-clicks one of the switches and then selects properties in the screen display frame 112 of the page setting screen 110, the display screen switches to Fig.14 The switch settings screen 120 is shown.

[0235] exist Fig.14 The switch setting screen 120 shown is provided with a switch function selection box 121 to which a function can be assigned to a switch. Examples of assignable switch functions can be provided by "bit setting", "page switching", "playback mode start", "real-time graph monitor (playback mode)" and "real-time graph monitor (monitoring mode)". Fig.14 In the example shown, one of the switch functions can be selected through the drop-down list in the switch function selection box 121. Therefore, the user can select a desired switch function from a plurality of candidates shown in the drop-down list. In the case where one of the switch functions is selected in the switch function selection box 121, as shown in FIG. Fig.15 As shown, the setting items of the selected switch function are shown on the switch setting screen 120. In this example, "playback mode start" is selected in the switch function selection box 121. Accordingly, an initial display screen selection box 122, an operation record data selection box 123, and a real-time chart monitor (playback mode) description & setting box 124 are shown.

[0236] Fig.16 The system setting screen 130 is shown. In the system setting screen 130, the target device setting screen section 220 is shown, which can specify the target device as the device having the device wave to be displayed in the real-time chart monitor (in the playback mode in this example). The details will be discussed later.

[0237] The screen data edited by the screen data editing device 60 is transmitted to the programmable display 50 via the screen data transmitting unit 67 . When the screen data receiver 57 receives the screen data, the programmable display 50 stores the received screen data in the setting storage unit 52 .

[0238] (Component Setting 52a)

[0239] Fig.11The component settings 52a stored in the setting storage unit 52 of the programmable display 50 shown include at least any of the settings of the wave display component, the page switching component 131, the real-time display component, and the playback display component.

[0240] (Wave Display Components)

[0241] The wave display component is used to display the device wave on the screen. Fig.11 The screen data editing device 60 shown is used to define the user screen via the screen data editing unit 61 by manipulating the screen data editing input unit 63. In the present embodiment, the user screen to be defined is shown on the screen data editing display unit 65, and the user selects a display component from the wave display component and the page switching component 131, etc. held in the screen data editing storage unit 62, and arranges the selected wave display component and the page switching component 131, etc. at a desired position on the page of the user screen. After editing the user screen, the screen data is sent from the screen data sending unit 67 to the screen data receiver 57 of the programmable display 50. The programmable display 50 obtains the information required for screen display (for example, the device value specified by the object device setting 52c) from the PLC 1 via the display side communication unit 58 based on the received screen data, and generates display data in the display data generator 51a of the display processor 51. An image is displayed on the display unit 55 based on the generated display data. When the touch detector 53 detects the user's touch operation on the display component shown on the display screen of the display unit 55, its corresponding processing is performed by the display processor 51. For example, when you touch the wave display component, the display Fig.12 The device wave displays screen 120.

[0242] (Page switching component 131)

[0243] The page switching component 131 is a component that is arranged in a first page corresponding to a first page identifier to change a display screen from the first page to a second page corresponding to a second page identifier different from the first page identifier.

[0244] Figures 17 to 20 An exemplary user interface including one or more page switching components 131 is shown. Fig.17 In the exemplary user screen 130A shown, the page switching component 131 is a button 132 indicated as "next page". When the user touches the "next page" button 132 shown on the display screen, the display screen can flip to the designated page (e.g., the next page corresponding to the page number that increments the currently displayed page number). Fig.18In the exemplary user screen 130B shown, two buttons (right arrow and left arrow) 133 and 134 are arranged as page switching components 131. When the user touches the right arrow button 133, the display screen can flip to the next page corresponding to the page number that increases the currently displayed page number. When the user touches the left arrow button 134, the display screen can flip to the previous page corresponding to the page number that decreases the currently displayed page number. Fig.19 In the exemplary user screen 130C shown, a triangle button 135 and an inverted triangle button 136 and a page number indicator frame 137 are arranged as the page switch component 131. When the user touches the triangle button 135, the display screen can flip to the next page corresponding to the page number that increments the page number currently shown in the page number indicator frame 137. When the user touches the inverted triangle button 136, the display screen can flip to the previous page corresponding to the page number that decrements the page number currently shown in the page number indicator frame 137. Page turning can be performed at the timing of the touch operation of the triangle button 135 or the inverted triangle button 136 to increase or decrement the current page number. Alternatively, a "jump" button 138 can be additionally arranged. After the desired page number is displayed in the page number indicator frame 137 by touching the triangle button 135 or the inverted triangle button 136, page turning can be performed at the timing of the touch operation of the "jump" button 138. Fig. 20 In the exemplary user screen 130D shown, thumbnail icons 139 corresponding to all pages are shown as the page switching component 131. When the user touches a desired thumbnail icon among the thumbnail icons 139, the display screen can be flipped to a page corresponding to the page number corresponding to the touched icon.

[0245] (User interface screen of programmable display 50)

[0246] Fig.12 and Figure 21 to Figure 27 An exemplary user interface screen of the programmable display 50 is shown. Fig.21 A menu screen 140 of the programmable display 50 is shown. Fig. 22 Shows when the user is Fig.21 The initial screen 150 in the playback mode is displayed when the "playback mode start" button 141 is touched in the menu screen 140. Fig.12 The device wave display screen 160 displayed when the “real-time graph monitor” tab 161 is selected in the playback mode is shown. Fig.23 A camera / event display screen 170 is shown which is displayed when the user selects the “CAMERA / EVENT” tab 162 . Fig.24A viewer display screen 180 is shown that is displayed when the user selects the “Viewer” tab 163 . Fig.25 The unit display screen 190 displayed when the user selects the “Unit” tab 164 is shown. Fig.26 Shown when the user touches Fig.25 When the “Description” button 191 in the unit display screen 190 is pressed, the unit display screen 190B is displayed. Fig. 27 The program display screen 200 is shown when the user selects the "Program" tab 165. The user uses the programming device 70 to edit the program displayed when the user touches the Fig.24 The “Viewer” tab 163 shown is a user screen such as a “Maintenance screen” that is displayed.

[0247] Fig.23 The camera / event display screen 170 shown is an example of a system screen in the present embodiment. Similar to the device wave display screen 160 described above, the camera / event display screen 170 can be displayed by superimposing a camera image read from the operation log data or an event associated with the time of its occurrence on the system default screen. The camera / event display screen 170 includes a camera image display frame 172 on the left side of the screen. In the event / error history frame 171, the events included in the operation log data are listed together with their detailed contents and the time of occurrence. Fig.23 In the example of FIG. 1 , the row of “mode switch (PROG>RUN)” is highlighted in the event group EV listed in the event / error history box 171. This highlighting shows the time when the system focuses on the event of “mode switch (PROG>RUN)”.

[0248] In this case, a camera image captured at a time closest to the time when the event occurred is selected from the operation record data for the camera image shown in the camera image display frame 172 on the left. Below the camera image display frame 172, picture information IX is shown, which includes the shooting date and time of the camera image shown, and the serial number of the camera image shown in the total number of camera images captured, etc.

[0249] In addition, “20XX / 4 / 20 11:26:23” is indicated in time stamp area 409. This time corresponds to the occurrence of the above-mentioned “mode switching (PROG>RUN)” event. That is, in event / error history box 171, time stamp area 409 indicates the occurrence time of the event selected by the user's touch operation.

[0250] When the user touches and selects an event other than "mode switching (PROG>RUN)" in the event / error history frame 171, the selected event is highlighted. Accordingly, the time of occurrence of the selected event is indicated in the time stamp area 409. In addition, the camera image shown in the camera image display frame 172 will change. Specifically, the camera image will change to a camera image captured at a time closest to the time of occurrence of the selected event.

[0251] A movable time designation cursor 404 that can slide in the horizontal direction is shown on the right side of the time stamp area 409. This time designation cursor 404 indicates "20XX / 4 / 2011:26:23" shown in the time stamp area 409. In the case where the user moves the time designation cursor 404 to the right or left, the camera image will change according to the movement of the cursor 404, and the highlighted portion in the event / error history box 171 will change accordingly (related display).

[0252] The change of the camera image, the change of the highlighted event, and the position of the time designation cursor are correlated (synchronized) with each other. The user can change the correlation reference time by sliding the time designation cursor 404 to the right or left or by touching one of the events shown in the event / error history box 171. The correlation display (the correlation relationship between the change of the camera image, the change of the highlighted event, and the position of the time designation cursor) is controlled based on the correlation reference time. The details of the correlation display will be discussed later.

[0253] Fig.24 The viewer display screen 180 shown is an example of a system screen in the present embodiment. As with the device wave display screen 160 described above, the viewer display screen 180 can be displayed by superimposing the device value read from the operation log data on the system default screen. In the viewer display screen 180, the "maintenance screen" edited by the user in the screen data editing device 60 is incorporated into the system default screen. Figure 2 As described in detail, text components TX such as "Maintenance screen" and "Playback now" are arranged in the maintenance screen. In addition, character display components CP such as "General", "AD conversion data", "Special data", "Offset value", "Analog data", "Disconnect detector", "Scaling", "Upper limit value", "Lower limit value", "Comparator", "Item", "Value", "Relay", "Upper limit value on level", "Upper limit value off level", "Lower limit value off level" and "Lower limit value on level" are arranged. Numerical display components NP (12345, 3452, etc.) or other character display components (ON and OFF) are arranged at positions corresponding to some of the above-mentioned character display components CP.

[0254] In addition, Fig.24 In the viewer display screen 180 shown, the position of the time designation cursor 404 and the device value represented by the numerical display component NP are related to each other. That is, the numerical value of the numerical display component NP or the character of the character display component CP can be changed by sliding the time designation cursor 404 to the right or left. Fig.24 In the example of , since “20XX / 4 / 2011:26:23” is indicated in the time stamp area 409 , the numerical value display component NP and the character display component CP show the device value at “20XX / 4 / 20 11:26:23”.

[0255] Fig.24 The viewer display 180 shown is similar to the Fig.23 The camera / event display screen 170 shown is related (synchronized). As described above, Fig.23 The time stamp area 409 of the camera / event display screen 170 shown in the figure indicates "20XX / 4 / 20 11:26:23". In this case, when the user touches the "Viewer" tab 163, the viewer display screen 180 (which indicates "20XX / 4 / 20 11:26:23" in the time stamp area 409) is displayed. Fig.24 ), and the device value corresponding to that moment is shown in the numerical display component NP and the character display component CP.

[0256] Fig.24 The "wave check" button 181 is a so-called switch component SP. When the user touches the "wave check" button 181, the Fig.24 The "Maintenance Screen" shown is a real-time graph monitor of the device being used (playback mode).

[0257] Fig.25 The unit display screen 190 shown is an example of a system screen in the present embodiment, and is displayed by superimposing the unit configuration read from the operation log data on the system default screen in the same manner as the device wave display screen 160 described above. The "Description" button 191 and the "Wave Check" button 181 are incorporated in advance into the system default screen (not edited by the user), and are displayed according to the number of unit configurations. Fig.25 In the example of FIG. 1 , it is assumed that four units “CPU installation unit”, “I / O unit”, “camera unit”, and “motion unit” are included as the unit configuration UL included in the operation record data. Accordingly, four sets of “description” buttons 191 and “wave check” buttons 181 are shown. For example, in the case where the user touches the “description” button corresponding to the “motion unit” among the “description” buttons 191, the “motion unit” will be displayed. Fig.26 The unit display screen is shown.

[0258] Fig.26 The unit display screen 190B shown is an example of a system screen in this embodiment. Like the device wave display screen 160 described above, the unit display screen 190B can be displayed by superimposing the buffer storage area (UG) of the device in the motion unit read from the operation record data and its device value on the system default screen. Fig.26 In the example of , “current coordinates”, “command coordinates”, “current speed”, “command speed”, and “feedback torque” are shown as examples of UGs, and device values ​​of these five are shown on the right side of these UGs.

[0259] In addition, Fig.26 The time stamp area 409 shows "20XX / 4 / 20 11:26:23". This time is Figure 23 to Figure 25 That is, Fig.26 The time shown in the unit display screen 190B shown in the figure is also the same as that in the above Fig.23 The camera / event display screen 170 and Fig.24 The times shown in the viewer display 180 are related (synchronized). Fig.26 In the case of the time designation cursor 404 being set, the time is designated by sliding the position of the time designation cursor 404 so that the device value corresponding to the designated time is displayed. In other words, the device value corresponding to the position of the time designation cursor 404 is read from the operation record data according to the slider operation of the time designation cursor 404, and the device value is displayed.

[0260] When the user touches Fig.26 When the "Wave Check" button 181 is clicked, it will be displayed in Fig.26 The unit display screen 190B is shown as a real-time graphical monitor of the device being used (playback mode).

[0261] Fig. 27 The program display screen 200 shown is an example of a system screen in the present embodiment, and is displayed by superimposing the unit configuration and ladder program read from the operation log data on the system default screen in the same manner as the device wave display screen 160 described above. Fig. 27 In the example of , a unit configuration display frame 207 and a ladder program display frame 208 are arranged on the left and right sides of the screen, respectively.

[0262] In addition, Fig.26 The time stamp area 409 indicates "20XX / 4 / 20 11:26:23". Figure 23 to Figure 26 That is, Fig. 27 The time shown in the program display screen 200 is also the same as that in the above Fig.23The camera / event display screen 170 shown, Fig.24 The viewer display 180 shown, and Fig.25 and Fig.26 The time shown in the unit display screens 190 and 190B is related (synchronized). When the user slides to the right or left Fig. 27 In the case where the time designation cursor 404 is shown, the time is designated by sliding the position of the time designation cursor 404, so that the device value corresponding to the designated time is superimposed on the ladder program shown in the ladder program display frame 208. In other words, the device value corresponding to the position of the time designation cursor 404 is read from the operation record data according to the slider operation of the time designation cursor 404 and is superimposed on the ladder program.

[0263] (Processing of Programmable Display 50)

[0264] Reference now Fig.28A The flowchart is used to illustrate the Fig.12 Processing of the programmable display 50 of the display device wave in the playback mode. In step S2801, the user's touch operation is first accepted. Then, in step S2802, it is determined whether the touch operation is performed on the wave display component. In the case where the touch operation is not performed on the wave display component, the process enters step S2803, wherein in step S2803, it is determined whether the touch operation is performed on the switch component. In the case where no touch operation is performed on any component, the process ends without performing any processing. In step S2803, in the case where a touch operation is performed on other components, the process enters step S2804, wherein in step S2804, the function corresponding to the touched component is performed, and then the process ends.

[0265] In step S2802, when the wave display component is touched, the process enters S2806, wherein in S2806, the selection of the operation record data is accepted. In this step, the user is urged to select the waveform to be displayed from the operation record data. When the waveform to be displayed is selected from the operation record data, the corresponding part of the operation record data is read in step S2807. More specifically, the display data generator 51a of the programmable display 50 obtains the corresponding part of the operation record data from the operation record data stored in the storage memory of the PLC 1 or the operation record data pre-stored in the data memory 56 of the programmable display 50.

[0266] Subsequently, in step S2808, the target device having the device wave to be displayed is specified. In step S2809, the corresponding display data is generated in the display data generator 51a. Finally, in step S2810, the device wave is displayed on the display section 55, and the process ends.

[0267] (Function corresponding to the component touched)

[0268] Reference now Fig.28B The flowchart is used to illustrate Fig.28A The details of step S2804 are shown in FIG. 1. When the user touches the switch component, Fig.28A In step S2804, the "function corresponding to the touched component" is performed. The functions of the switch component can be classified into two types. One type is the above reference Figure 2 The bit setting function described above. Another type is the page switching function. Assign a specific device to a switch component with a bit setting function. Assign a specific page (screen ID) to a switch component with a page switching function. For example, Figure 2 The reset switch 246 shown has a bit setting function, and a specific device is assigned to the reset switch 246 . Fig.17 The page switching component 131 shown has a page switching function. The page number (screen ID) of the switching destination (jump destination) is assigned to the page switching component 131 .

[0269] exist Fig.28B In the process, first, in step S2804-1, it is determined whether the switch component has a bit setting function. In the case where the switch component has a bit setting function, the process proceeds to step S2804-2, wherein in step S2804-2, the device value of the device assigned to the switch component is rewritten according to the touch operation (changed from 1 to 0, etc.). In the case where the switch component does not have a bit setting function, the process proceeds to step S2804-3, wherein in step S2804-3, it is determined whether the switch component has a page switching function. In the case where the switch component has a page switching function, the process proceeds to step S2804-4, wherein in step S2804-4, the page is switched to the page number (screen ID) assigned to the switch component. In the case where the switch component does not have a page switching function, the process returns to Fig.28A Flowchart of (end of process).

[0270] (Show data generation)

[0271] Reference now Fig.28C The flowchart is used to illustrate Fig.28A The details of step S2809 are shown in FIG. Fig.28C First, in step S2809-1, the system default screen information 52f for displaying the system default screen is read. The system default screen information 52f is created by the system designer of the programmable display 50 and is stored in Fig.11The display data generator 51 a of the programmable display 50 reads the system default screen information 52 f from the setting storage unit 52 .

[0272] Subsequently, in S2809-2, the time sequence data of the device value is extracted from the operation record data. More specifically, the display data generator 51a of the programmable display 50 extracts the time sequence data of the device value of the device specified by step S2808 from the operation record data acquired in step S2807. In S2809-3, based on the read system default screen information 52f and the extracted time sequence data of the device value, the display data generator 51a generates display data created by superimposing the time sequence data on the system default screen.

[0273] (Device wave display)

[0274] Reference now Fig.28D The flowchart is used to illustrate Fig.28A The details of step S2810 are shown. Fig.28D The flow for displaying the device wave is shown. In step S2810-1, the display processor 51 first displays the device wave based on the display data generated by the display data generator 51a in step S2809.

[0275] Then, in step S2810-2, the display processor 51 determines whether the time designation cursor 404 has moved during the device wave display. In a case where the time designation cursor 404 has not moved, step S2810-2 is repeated without performing any processing.

[0276] In the case where the time designation cursor 404 is moved, the process proceeds to step S2810-3, where in step S2810-3, the display data generator 51a of the display processor 51 extracts the time sequence data corresponding to the time defined by the time designation cursor 404 after the movement from the operation record data. The extraction range of the time sequence data may be, for example, a time range that can be displayed in the device wave and is centered on the time defined by the time designation cursor after the movement. In step S2810-4, the display data generator 51a generates display data based on the extracted time sequence data and updates the device wave.

[0277] exist Fig.12In the example of , the time designation cursor 404 points to the time "20XX / 4 / 20 11:26:23" (scan number 35000). Now discuss the case where the user slides the time designation cursor 404 to the right (the time designation cursor advances in time). For example, the user slides the time designation cursor 404 from the scan number 35000 to the scan number 40000. In this case, the display data generator 51a of the display processor 51 extracts the time sequence data corresponding to the predetermined range centered on the scan number 40000 (from the scan number 40000 minus the predetermined scan number until the scan number 40000 plus the predetermined scan number) from the operation record data. The display data generator 51a generates display data of the identification line IL including the scan number 40000 based on the extracted time sequence data, and updates the device wave.

[0278] In the case where the user touches the one-step forward reproduction button 408, the display data generator 51a of the display processor 51 extracts time sequence data corresponding to a predetermined range centered on the scan number specified by the touch operation. Then, the display data generator 51a generates display data based on the extracted time sequence data and updates the device wave. In addition, in the case where the user touches the reproduction button 406, the display data generator 51a sequentially extracts time sequence data from the operation record data and sequentially updates the corresponding device wave (lateral scroll device wave).

[0279] Explanation has been given for the case where the cursor movement is specified at the time during the device wave display. Fig.28D For example, this also applies to Fig.23 The processing is performed when one of the event groups EV in the event / error history box 171 shown in the camera / event display screen 170 is selected.

[0280] Specifically, in the display Fig.23 In the case of the camera / event display screen 170 shown in FIG. 1 , the display data generator 51a of the display processor 51 determines whether the user has touched one of the events in the event / error history box 171. In the case where it is determined that the user's touch operation has been performed, the display data generator 51a switches the currently highlighted event in the event / error history box 171 to the touched event, and additionally specifies the occurrence time of the touched event to be shown in the time stamp area 409. In addition, the display data generator 51a changes the position of the time specifying cursor 404 according to the occurrence time of the touched event. In addition, the display data generator 51a extracts a camera image captured at the time closest to the time when the touched event occurred from the operation record data, and displays the extracted camera image in the camera image display box 172.

[0281] (Real-time chart monitor)

[0282] The programmable display 50 can receive the device wave via the PLC 1 and display the device wave in real time. The real-time display of the device wave is implemented in the real-time chart monitor in the monitoring mode displayed on the programmable display 50. The real-time chart monitor has a monitoring mode for showing the current device values ​​collected sequentially in real time as a motion video, and a replay mode for reading and displaying the time-sequential data acquired in the past. That is, the real-time chart monitor includes a monitoring mode that directly shows the current situation and a replay mode that plays back the situation at a certain point in time in the past. These modes can be switched from one mode to another by a mode switcher. The mode switcher can be switched, for example, by switching as Fig.21 The menu screen 140 of the display component is displayed in the "Real-time graph monitor (playback mode)" button 142 and the "Real-time graph monitor (monitoring mode)" button 143 to achieve. Fig.21 When the "Real-time graph monitor (monitoring mode)" button 143 is touched on the screen, the programmable display 50 is placed in the monitoring mode of the real-time graph monitor so that the display Fig.29 The device wave displays screen 210. Fig.29 The device wave display screen 210 is a motion video display updated in real time by the device wave.

[0283] (Get device settings 52d)

[0284] Fig.11 The setting storage unit 52 of the programmable display 50 shown stores acquisition device settings 52d, which specify acquisition devices having device waves to be displayed in the real-time graph monitor in the monitoring mode. The PLC 1 temporarily records the device values ​​of the devices specified by the acquisition device settings 52d in the temporary recording unit 91a as time-sequential data using the recording control unit 39. The programmable display 50 acquires the time-sequential data via the display-side communication unit 58, and displays the device values ​​in the form of a motion video by sequentially updating the device values. Fig.29 The device wave display screen 210 is shown.

[0285] The setting storage section 52 stores acquisition device settings 52d for specifying acquisition devices that provide time-sequential data of device values ​​to be repeatedly acquired. Furthermore, the setting storage section 52 includes settings for a real-time display component for sequentially showing time-sequential data of acquisition devices.

[0286] (Monitoring Mode)

[0287] As described above, in the real-time chart monitor in the monitoring mode, the programmable display 50 sequentially displays the time sequence data of the device values ​​temporarily recorded in the temporary recording section 91a of the PLC 1 on the display section 55. The programmable display 50 preliminarily performs settings for an acquisition device setting 52d for specifying an acquisition device that provides time sequence data of device values ​​to be repeatedly acquired, and a real-time display component for sequentially displaying the time sequence data of the acquisition device, and saves these settings in the setting storage section 52. When a user touches the real-time display component on the user screen, the touch detector 53 detects the touch operation. Based on the time sequence data of the device values ​​of the acquisition device temporarily recorded in the temporary recording section 91a of the PLC 1, the display data generator 51a generates display data that sequentially displays the device values ​​on the display screen. Fig.21 In the example of , the real-time display component corresponds to the “real-time chart monitor (monitoring mode)” button 143 .

[0288] (Target device settings screen)

[0289] The target device for providing the device wave to be displayed in the monitoring or playback mode in the real-time graph monitor is specified in the target device setting screen. Fig.16 An example of the object device setting screen section 220 for specifying an object device is shown. An object device can be specified for each mode, that is, an object device can be specified separately for the playback mode and the monitoring mode. In addition, when multiple user screens are defined, an object device can be specified for each user screen (that is, for each RTCMID). Fig.16 In the example of , the object device to be displayed in RTCMID0 in the playback mode can be specified. Candidates for the object device are listed in the unit selection box 221. The unit name, device name and display style are shown for each device. The display style indicates the style to be displayed on the display unit 55 (for example, decimal / binary number, number of digits, with / without a sign, etc.). The display style of the device can be predefined. Alternatively, the user can specify the display style of the device. For example, the user can select the display style of the device via Fig.16 Select a device from the screen and specify the display style for the selected device.

[0290] The device wave is displayed on the real-time graph monitor based on the settings made in the target device setting screen section 220. For example, Fig.16 In the example, DM100, DM200, and R000 are selected as the target devices. Fig.12 In the playback mode of the real-time graph monitor, the device waves of DM100, DM200, and R000 designated as the target devices of the playback mode of the real-time graph monitor are displayed.

[0291] (Real-time chart monitor (monitor mode))

[0292] The programmable display 50 according to this embodiment can display a real-time graph monitor (monitoring mode). In the real-time graph monitor (monitoring mode), Figure 6 In the PLC 1 of FIG. 1 , a temporary recording section 91 (ring buffer) provided separately from the PLC-side device section 34 in the CPU-mounted unit storage section 32 is used.

[0293] Reference now Fig.30 The flowchart of the programmable display 50 is used to explain the processing of the programmable display 50 when the real-time chart monitor is placed in the monitoring mode. The display processor 51 of the programmable display 50 first requests the PLC 1 to monitor the device wave via the display side communication unit 58 (step S3001). Upon receiving the monitoring request, the CPU mounting unit processor 31 keeps the device value of the device to be monitored in the ring buffer for a fixed period of time. Therefore, the time sequence data of the device value of the device to be monitored in the fixed period of time is stored in the ring buffer.

[0294] The display processor 51 requests the PLC 1 to send data at fixed intervals via the display side communication unit 58 (step S3002). In the data transmission request, the requested data is a predetermined amount of data from the last point of the area read in the previous data transmission request, among the time sequence data of the device values ​​sequentially stored in the ring buffer of the temporary recording unit 91a provided in the CPU installation unit storage unit 32. Accordingly, the CPU installation unit processor 31 sends a predetermined amount of data from the last point of the area read in the previous data transmission request, among the time sequence data of the device values ​​sequentially stored in the ring buffer. To the programmable display 50 (step S3003). In order to display the device wave (the horizontal axis is the time axis) in the programmable display 50, the CPU installation unit processor 31 starts from the internal clock ( Figure 8 The CPU installation unit processor 31 sends the time sequence data of the device value and the information about the time when the device value is stored in the ring buffer to the programmable display 50. The display processor 51 receives the data and displays the additional part of the device wave based on the information about the time (step S3004). Such additional parts of the device wave are repeatedly added to the device wave (updated device wave) until the device wave monitoring stops (step S3005).

[0295] (Example of monitoring mode screen)

[0296] exist Fig.29An example of a real-time graph monitor (monitoring mode) screen is shown in the device wave display screen 210 of FIG. In the real-time graph monitor in monitoring mode, the device wave is displayed in the form of a graph. In this graph, the time axis represents the number of scans (scan numbers). Instead of the scan numbers, the time axis may represent the time. In this graph, the time advances from left to right. Fig.29 In the exemplary device wave display screen 210 of FIG. 2 , the device waves of devices DM100, DM200, and R000 are displayed. The right end of the device wave represents the latest device value. The display processor 51 adds the additional part of the time sequence data of the device value received from the PLC to the right end of the device wave. Therefore, the device wave will extend to the right. In the case where the device wave reaches the right end of the real-time chart monitor frame, the monitoring screen containing the chart will scroll the device wave to the left so that the device value at the left end of the device wave is removed from the monitoring screen in sequence.

[0297] You can use the following settings to Fig.29 The real-time graph monitor (monitoring mode) shown is displayed on the display unit 55 of the programmable display 50. First, in the screen data editing device 60, the "real-time graph monitor (monitoring mode)" as a switch function is assigned to the switch component of the "real-time graph monitor (monitoring mode)". Fig.16 In the object device setting screen section 220 of the system setting screen 130 shown, it is specified that the RTCMID is displayed in the "Real-time Chart Monitor (Monitoring Mode)", and the type and number of devices to be displayed in the device wave on the screen corresponding to the selected RTCMID are set. The type and number of devices to be displayed in the device wave can be commonly specified for the above-mentioned "Real-time Chart Monitor (Playback Mode)". The edited screen data is sent from the screen data editing device 60 to the programmable display 50. When the user touches Fig.21 By clicking the “Real-time graph monitor (monitoring mode)” button 143 in the menu screen 140 of the programmable display 50, time-sequential data (device wave) of the desired type and number of devices can be displayed on the system screen of the programmable display 50.

[0298] (Replay Display Component)

[0299] In the case of further switching the screen to the playback mode, the user touches the playback display component. Fig.21 In the example of the menu screen 140 of FIG. 1 , two playback display components are prepared, namely, a “real-time chart monitor (playback mode)” button 142 and a “playback mode start” button 141. When the “playback mode start” button 141 is touched, the playback mode screen (for example, Fig.12 and Figure 23 to Figure 27The user can make various settings related to the playback mode or select a desired screen in the playback mode screen. Specifically, the user can select a desired screen by touching one of the tabs arranged in the upper area of ​​the screen. For example, when the user selects the "Real-time Chart Monitor" tab 161, the display Fig.12 When the user selects the "Camera / Event" tab 162, the display Fig.23 For example, when the user selects the "Viewer" tab 163, the camera / event display screen 170 is displayed. Fig.24 When the user selects the "Unit" tab 164, the Fig.25 or 26. In addition, when the user selects the "Program" tab 165, the display Fig. 27 The program displays screen 200.

[0300] When the user selects the "Real-time Chart Monitor (Replay Mode)" button 142, the Fig.31 The device wave display screen 160B is shown. Fig.12 and Figure 23 to Figure 27 The "Real-time graph monitor (playback mode)" button 142 enables the user to directly display only the device wave in real time without detailed settings.

[0301] (Initial display screen setting section)

[0302] The initial display screen to be displayed first in the playback mode is defined by the screen data editing device 60. The object device to be displayed with the device wave in the initial display screen can be selected by the screen data editing device 60. The object device to be displayed first in the initial display screen can be changed according to the conditions. In the event of a malfunction, the playback mode will be used to diagnose the cause of the malfunction. In such a case, the device considered as the cause often depends on the type of malfunction. For this reason, it will be useful to diagnose the cause of the malfunction (i.e., change the object device to be displayed first in the initial display screen according to the type of malfunction or the saved conditions). This is because the user can immediately check the condition of the object device. To this end, for example, Fig.32As shown, the screen data editing device 60 is pre-set to change the device wave to be displayed on the programmable display 50 in playback mode according to the type of fault. Therefore, in the event of a fault in the actual operation of the FA system, the device wave of the device that may be related to the cause of the fault is selectively displayed. That is, the programmable display 50 can show information useful for diagnosing the cause of the fault. As a result, the programmable display 50 can be used to quickly restore the system. The programmable display can display a setting screen when displaying the device wave on the display screen, which enables selection of one or more object devices and the representation style of the one or more object devices.

[0303] You can Fig.33 Such settings are performed in the initial display screen setting unit 230 of the screen data editing device 60 shown in FIG. Fig.15 The switching setting screen 120 shown is similar, and its description is omitted. An "RTCMID specification" box 126 is arranged in the real-time chart monitor (playback mode) description & setting box 124. External specification can be selected for RTCMID specification. In the case of external specification, the location and device name of the object device are specified in the location specification box 127 and the device name specification box 128, respectively. Fig.33 In the example, "PLC1" and the device value "DM300" are specified as the place and device name for RTCMID, respectively. In this case, when the device value of DM300 is 0, RTCMID=0 is specified. When the device value of DM300 is 1, RTCMID=1 is specified. Assigning the device to the RTCMID as the RTCMID designation can dynamically change the RTCMID of the real-time chart monitor (playback mode) displayed on the programmable display 50 in the event of a failure. The RTCMID designation can be selected from "External designation" and "Internal designation" in the "RTCMID designation" box 126. In the case where the RTCMID is specified to be fixed as described above, select "Internal designation".

[0304] (Data Structure)

[0305] Fig.34A The data structure of the screen data of the user screen edited in the screen data editing device 60 according to the present embodiment is shown. Fig.34B The data structure of the system screen incorporated in advance by the system engineer of the programmable display 50 is shown. Fig.34C It is a schematic diagram of the data structure that associates the above-mentioned RTCMID with the device.

[0306] like Fig.34AAs shown, the data structure of the screen data edited by the user includes the page settings of the pages managed by the screen IDs (eg, 0001 to 0003) and the component settings of various components arranged in the corresponding pages. Figure 2 The types of components arranged in the corresponding page may include a text component TX, a character display component CP, a numerical display component NP, a switch component SP (including a page switching component), a light component RP, a meter component MP, and a chart component GP, etc. In addition, component IDs are assigned to these components to distinguish two or more components of the same type from each other. For example, in the case of including two text components, different component IDs are assigned to the two text components.

[0307] Assign devices to components other than text components TX. Fig.34A In the example of , device DM1001 is assigned to the character display component CP of component ID0002. Device DM1002 is assigned to the numerical display component NP of component ID0003. Device R1001 is assigned to the switch component SP of component ID0004. Device R1002 is assigned to the light component RP of component ID0005. Device DM1003 is assigned to the meter component MP of component ID0006. Device DM1004 is assigned to the chart component GP of component ID0007.

[0308] These components have XY coordinates that represent where they are to be placed in the corresponding page. Fig.34A In the example of , the text component has coordinates (10, 10) indicating the position where the text component is to be arranged in the corresponding page. The same applies to other components.

[0309] Components other than text components have one or more component icons / images. For example, in Fig.34A In the example of FIG. 5 , the character display component CP and the numerical display component NP have component images of a frame surrounding the characters and numerical values ​​to be displayed inside. The user can select the thickness and color of the frame. The same applies to other components.

[0310] Fig.34B The information on the system default screen shown (system default screen information 52f) is pre-designed by a system engineer of the programmable display 50 and is stored in the setting storage unit 52 (or alternatively in the data storage 56 or other system storage). Fig.28AAs described above, the display data generator 51a of the programmable display 50 reads the system default screen information 52f and extracts the time sequence data of the required device values ​​from the operation record data, so as to generate the display data DP by superimposing the time sequence data of the device values ​​on the system default screen. The display processor 51 displays an image corresponding to the display data DP generated by the display data generator 51a. Although referring to Fig.34B To illustrate the use of display Fig.12 The data structure of the device wave display screen 160 is shown, but the same applies to the data structure for displaying Figure 23 to Figure 27 The data structure of the screen shown.

[0311] like Fig.34C As shown, a designated device is designated to the RTCMID, and an object device to be displayed in the real-time chart monitor playback mode is assigned to the RTCMID.

[0312] Thus, in the event of a fault, the alarm and the displayed data can be related to each other. Fig.21 When the "playback mode start" button 141 is touched on the system screen, the Fig.33 The user screen according to the device value of the designated target device (DM300) is displayed by the settings shown. As described above, when the device value of DM300 is 0, the page of RTCMID0 is selected, and when the device value of DM300 is 1, the page of RTCMID1 is selected as the initial screen 150 in the playback mode ( Fig. 22 ). As a result, an appropriate user screen (displayed with an appropriate device) can be selectively initially displayed according to the fault. In other words, since the device is previously associated with a fault closely related to the device, such an initial screen can be used to eliminate the fault.

[0313] (Ladder Monitor)

[0314] The programmable display 50 may include a ladder diagram monitoring function for displaying the programmable display 50 in a playback mode of a real-time chart monitor. Fig. 27 The ladder diagram program is displayed as shown in the program display screen 200. Specifically, when the saving condition is met, PLC 1 will associate the user program currently executed by the program execution unit 40 with the operation record data when the saving condition is met, and save the user program associated with the operation record data in the saving memory 36. The programmable display 50 obtains the operation record data saved in the saving memory 36 of PLC 1, and displays the user program on the display unit 55 based on the information related to the acquisition time included in the operation record data. In this case, the device value corresponding to the acquisition time is shown on the user program (for example, the ladder diagram program) included in the operation record data. As Fig. 27As shown, device values ​​are represented on corresponding devices shown in the ladder diagram display box 206.

[0315] (Event Monitor)

[0316] The programmable display 50 may include an event monitoring function for showing events. The event collection unit 92b of the PLC 1 collects event data related to a plurality of events occurring in the PLC 1 or the controlled device controlled by the PLC 1. The event collection unit 92b associates the device value with the time of occurrence of the corresponding event, and stores the device value associated with the time of occurrence of the corresponding event in the temporary recording unit 91a in chronological order. When the preservation condition is met, the event data stored in the event collection unit 92b is associated with the operation record data, so that the event data is included in the operation record data and is saved in the preservation memory 36.

[0317] The programmable display 50 acquires the operation log data stored in the storage memory 36 , and displays an event corresponding to the event data included in the operation log data on the display unit 55 based on the information on the occurrence time included in the operation log data. Fig.23 1 shows an event monitoring function executed in the replay mode of the real-time chart monitor. In this example, an event / error history frame 171 and a camera image display frame 172 are arranged on the left and right sides of the camera / event display screen 170, respectively. In the event / error history frame 171, the events included in the operation log data are listed together with the details of these events and the time of occurrence. When one of these events is selected in the event / error history frame 171, the camera image captured by the camera corresponding to the selected event is displayed in the camera image display frame 172.

[0318] (Reproduction control line 402)

[0319] In addition, a reproduction control line 402 is arranged at the bottom of the camera / event display screen 170 to control the reproduction of log data such as saved device values. A time designation cursor 404 shown in the form of a slider can be moved left and right. The time designation cursor 404 is related to the time information included in the operation record data. The time advances from left to right in the slider. When the time designation cursor 404 is moved by tapping, an event at the time corresponding to the time designation cursor 404 is selected in the event / error history frame 171, and the camera image of the camera image display frame 172 is switched to the camera image corresponding to the event. The currently selected time information is shown in the time stamp area 409.

[0320] The reproduction button 406 is a button for showing the device values ​​in chronological order. When the reproduction button 406 is tapped, the event changes over time so that the camera image in the camera image display frame 172 will be displayed like a moving video. The one-step reverse reproduction button 407 is a button for showing the device values ​​in chronological order while rewinding (rewinding) one step at the selected time. The one-step forward reproduction button 408 is a button for showing the device values ​​in chronological order while advancing the selected time by one step.

[0321] (Functional block diagram of PLC 1)

[0322] The user program such as a ladder program to be executed by the above-mentioned PLC 1 is created by the programming device 70. The user program created by the programming device 70 is sent to the PLC 1. Fig.35 It is a functional block diagram of the PLC 1 connected to the programming device 70. Fig.35 The PLC 1 shown includes a CPU mounting unit storage section 32, a CPU mounting unit processor 31, a bus master 38, a PLC side communication section 33, and a program receiving section 47. The CPU mounting unit storage section 32 includes a project storage section 35, a PLC side device section 34, a temporary recording section 91a, and a saving memory 36.

[0323] The project storage unit 35 stores project data provided from the programming device 70 and including a ladder diagram program. The PLC side device unit 34 includes a bit device and a word device. Each device stores a device value. The PLC side device unit 34 is used as a device memory for storing device values ​​of the device. The PLC side device unit 34 is used as a storage area to be referenced based on the user program. The temporary recording unit 91a records the device values ​​stored in the PLC side device unit 34 in chronological order in each scan. The temporary recording unit 91a can be composed of a ring buffer or the like. When a predetermined saving condition is met, the saving memory 36 saves the chronological data of the device values ​​stored in the temporary recording unit 91a. The saving memory 36 is composed of an internal memory or a removable memory card or the like.

[0324] The CPU installation unit processor 31 includes a program execution unit 40, a record control unit 39, a storage control unit 39C and an event management unit. The program execution unit 40 is an execution engine of a ladder diagram program. When the record trigger condition for starting the record to the temporary recording unit 91a is met, the record control unit 39 collects the device value of the predefined device. The record control unit 39 associates the device value with the information related to the acquisition time of the same device value (time and date, or the scan sequence number of the ladder diagram program), and records the device value associated with the information in the temporary recording unit 91a. The record trigger condition can be a condition that the PLC 1 is placed in the RUN (running) mode from the setting mode. However, the record trigger condition is not limited to this condition. Other conditions can be applied to the record trigger condition. When the storage trigger condition for saving the device value in the storage memory 36 is met, the storage control unit 39C saves the device value temporarily recorded in the record control unit 39 as log data together with the information related to the acquisition time. The event management unit detects events. The details of the event management unit will be discussed later.

[0325] The bus master 38 controls the communication of the inter-unit bus connecting the CPU installation unit 3 to the expansion unit 4. The input / output refresh is performed by the bus master 38. The input / output refresh, the ladder program execution and the end processing form a cycle (one scan). The CPU installation unit 3 repeatedly performs the scan at high speed. As a result, the device of the CPU installation unit 3 and the device of the expansion unit 4 are synchronized with each other through the input / output refresh. The result obtained by executing the ladder program by the program execution unit 40 is reflected in the device of the expansion unit 4 through the input / output refresh. In the end processing, peripheral services such as system error checking and data communication with the programmable display 50 through the PLC side communication unit 33 are performed. The PLC side communication unit 33 is used to repeatedly provide communication between the PLC 1 and the programmable display 50 according to a predetermined time period. The program receiving unit 47 receives project data including the ladder program sent from the programming device 70.

[0326] (Functional Block Diagram of Programming Device 70)

[0327] Fig.35 The programming device 70 shown includes a programming side input section 74, a programming side display section 75, a programming side storage section 76, a programming section 77, and a program sending section 78. A PC installed with the screen data editing device 60 software can also be used for the programming device 70. A mouse and a keyboard, etc. can be used as the programming side input section 74. The user can input editing data related to the ladder program via the programming side input section 74 and perform settings of the unit configuration. The programming side display section 75 is a display, etc. connected to the PC.

[0328] The programming section 77 creates a ladder diagram program based on user data input by the user via the programming side input section 74. In addition, the programming section 77 performs settings for unit configuration. Project data includes a ladder diagram program and a unit configuration. The programming side storage section 76 stores the project data created by the programming section 77. The programming side storage section 76 also stores operation record data of the PLC 1. The program sending section 78 sends the project data including the ladder diagram program stored in the programming side storage section 76 to the PLC 1.

[0329] (Operation record data)

[0330] The operation record data stored in the storage memory 36 will now be described in detail. The operation record data includes project data and log data. Fig.36 1 shows an exemplary structure of the operation log data. The item data included in the operation log data is the item data executed by the program execution unit 40 when the save trigger condition is satisfied. The log data is the time sequence data of the device value associated with the information related to the collection time, the time sequence image data captured by the camera unit 4c, and the event data. The image data and the event data are also associated with the information related to the acquisition time of the image data and the occurrence time of the event data. The details of this association will be discussed later.

[0331] A plurality of files including management information data and project identification information are packaged as operation record data. Management information data is information related to the type of data included in the operation record data. Its extension name may be, for example, TMN. An identifier of project data included in the operation record data may be, for example, TPJ. Project identification information is information related to the identification of project data when the operation record data is saved. Its extension name may be, for example, TPI. An extension name of the time sequence data of device values ​​may be, for example, TDV. An extension name of the time sequence image data may be, for example, TCA. An extension name of the event data may be, for example, TEV. These extension names are for illustrative purposes only. Any set of text / numbers, etc. may be used for their extension names.

[0332] Project data (extension TPJ) includes project files, module files, function blocks, and unit configuration files, etc. The project file includes information related to the settings of the project, and its extension may be, for example, kpr. The module file is the so-called ladder program information, and its extension may be, for example, mod. The function block is information related to the componentized ladder program, and its extension may be, for example, kfb. The unit configuration file is configuration information related to the unit, and its extension may be ue2. Only part of this information may be included in the project data. Alternatively, other information may be added to the project data. Fig.35The programming section 77 can interpret the management information data included in the operation log data, and can display the contents of the operation log data on the programming-side display section 75.

[0333] (Operation Record Data Interpretation Unit 51b)

[0334] As described above, not only the PLC 1 but also the programmable display 50 can display the contents of the operation log data. For this purpose, the programmable display 50 includes an operation log data interpretation unit 51b. Fig.36 To illustrate the content of the operation record data to be displayed by the programmable display 50. The display processor 51 of the illustrated programmable display 50 includes an operation record data interpretation unit 51b. The operation record data interpretation unit 51b reads the management information data in the operation record data, and determines the type of data included in the operation record data. In addition, the operation record data interpretation unit 51b reads the project data corresponding to the project identification information, and then imports the project files, module files, function blocks and unit configuration files, etc. included in the project data. Therefore, the display processor 51 can display various user interfaces synchronously with each other in playback mode (related display).

[0335] (Synchronous display of operation record data (correlated display))

[0336] Fig.37 50 is a functional block diagram of the display processor 51 of the programmable display 50. Fig.37 As shown, the display processor 51 includes a wave display module 322, an image display module 323, an event display module 326, a viewer display module 327, a unit display module 325, a program display module 321, and a playback synchronization control module 324. The wave display module 322 is a module for displaying the time sequence data of the device value included in the log data on the display unit 55 as a device wave.

[0337] exist Fig.12 In the device wave display screen 160 shown, when the time designation cursor 404 is dragged to the left or right, the device wave moves to the left or right accordingly. A thick vertical line as the identification line IL is shown in the center of the device wave display screen 160 (the position corresponding to the scan number 35000). The device wave can be moved to the left or right so that the identification line IL covers the time (scan number) designated by the time designation cursor 404. For example, when the time designation cursor 404 is moved from Fig.12 When the position shown moves rightward to scan number 40000, the device wave moves leftward accordingly so that the point corresponding to scan number 40000 in the device wave coincides with the identification line IL. In addition, the device value in the device wave that coincides with the identification line IL can be displayed on the screen.

[0338] Reference now Figures 37 to 40 The image display module 323, the event display module 326, the viewer display module 327, the unit display module 325 and the program display module 321 are described in detail.

[0339] Fig.37 The display processor 51 shown includes a program display module 321. The program display module 321 is a module for displaying the device values ​​included in the log data 73 together with the user program included in the project data 71 on the display section 55. In addition to the user program, the program display module 321 can also display various information that enables the user to check the setting information of the project data 71, such as program configuration information, a plurality of program parts, unit configurations, and function settings of the units included in the project data 71. The image display module 323 displays the time-sequential image data included in the log data 73 on the display section 55.

[0340] The wave display module 322 is a module for displaying the time sequence data of the device values ​​included in the log data 73 in a wave shape on the display unit 55. The playback synchronization control module 324 synchronizes the information displayed by the program display module 321 with the information displayed by the wave display module 322. Fig.12 The device wave is played back on the device wave display screen 160. The event display module 326 is as follows Fig.23 The viewer display module 327 extracts events from the operation log data in chronological order and lists these events in the event / error history box 171. Fig.24 As shown, information related to maintenance is extracted from the operation record data, and a maintenance screen is displayed.

[0341] These modules may be referred to as engineering software. The image display module 323 may be implemented as one function (image display section) of the program display module 321 or one function (image display section) of the wave display module 322 .

[0342] (Program display module 321)

[0343] Fig.38The details of the program display module 321 are shown. The moment UI 330a provides a UI (e.g., a slide bar, a cursor, etc.) for operating the acquisition moment (display moment) of the device to be displayed together with the user program. The display moment control unit 331a sends the display moment specified by the moment UI 330a to the playback synchronization control module 324, and provides the display moment received from the playback synchronization control module 324 to the moment UI 330a. The program display unit 332 displays the project data 71 on the display unit 55, or reads the project data 71 corresponding to the identification information from the PC-side storage device 22 to display the read project data 71 on the display unit 55. In addition, the program display unit 332 associates the device value acquired by the device value acquisition unit 333a with the device used or described in the user program, and displays the device value associated with the device. The device value acquisition unit 333a includes a real-time reproduction mode and a historical reproduction mode (log reproduction mode). In the real-time playback mode, the device value acquisition unit 333a accesses the real-time transmission unit of the PLC 1 to acquire the device value, and transmits the acquired device value to the program display unit 332. In the log playback mode, the device value acquisition unit 333a accesses the real-time transmission unit of the PLC 1 to acquire the device value, and transmits the acquired device value to the program display unit 332. Fig.37 The playback synchronization control module 324 shown is used to obtain the display time and the corresponding device value, and transmit the obtained display time and device value to the program display unit 332.

[0344] Fig.39 1 is a schematic diagram showing an exemplary user interface screen 1300 displayed on the display unit 55 of the programmable display 50 by the program display unit 332 and the like. Fig.39 In the project display area 420 on the left side of the screen, various information included in the project data 71 is displayed. The unit configuration (CPU mounting unit 3, motion unit 4d, analog input unit, and camera unit 4c) and the program configuration (each scan module, fixed cycle module, inter-unit synchronization module, function block, and macro) are displayed from top to bottom in this order. Configuration parameters such as axis configuration and axis control are shown below the motion unit 4d as function settings. Fig.39 The user can check the current specified settings of the configuration parameters by double clicking on the axis configuration or axis control on the user interface screen 1300 shown. Main and Sub are shown below each scan module in the project display area 420. When the user clicks on Main, the Main program is displayed in the program display area 410 of the central ladder monitor 450.

[0345] Fig.37 The illustrated program display module 321 reads the project data 71 from the removable memory card 36A to display various types of information in the project display area 420 or to display a desired program in the program display area 410 .

[0346] The program display area 410 is a part of the so-called ladder monitor 450. The program display area 410 can work alone in the real-time reproduction mode. The ladder monitor 450 can be hidden by clicking the corresponding cross symbol. In the log reproduction mode, the program display section 332 can reproduce the ladder program included in the project when the operation record is saved. In addition, in the log reproduction mode, the program display section 332 associates the device value included in the log data 73 via the device value acquisition section 333a with the device described in the Main program, and displays the device value associated with the device. The device value to be displayed is the device value corresponding to the moment specified by the moment specifying cursor 404.

[0347] exist Fig.39 In the case where the device value corresponding to the date and time 20XX / 10 / 01 18:52:54 shown in the timestamp area 409 is associated with the device described in the Main program and displayed. [35000 / 74286] shown on the right side of the date and time indicates the currently displayed scan number 35000 relative to the total scan number 74286. In the case where the user drags the time designation cursor 404, the displayed time and scan number are updated accordingly, and the corresponding device value is also updated. For example, after the display time is updated, the position of the relay device switched to ON is indicated by an ON representation (e.g., a solid filled with a specific color, etc.), and the position of the relay device switched to OFF is indicated by an OFF representation (e.g., a solid filled with white or black, etc.).

[0348] exist Fig.39 The image display area of ​​the camera monitor 430 is arranged in the upper right part of the screen. The image display module 323 reads the image data corresponding to the display time indicated by the program display module 321 on the ladder monitor 450 from the log data 73, and displays the read image data in the image display area of ​​the camera monitor 430. Fig.39 , the image data corresponding to the display time 20XX / 10 / 01 18:52:54 is displayed on the camera monitor 430. In addition, 282 / 601 is also shown on the right side of the display time. This indicates the sequence number (282) of the currently displayed image data relative to the total number of captured images 601. When the user drags the time designation cursor 404a on the camera monitor 430, the display time and the sequence number of the image data to be displayed can be changed.

[0349] In this case, the time designation cursor 404 in the above-mentioned ladder monitor 450 will move according to the movement of the time designation cursor 404a. For example, in the case where the time designation cursor 404a moves to the display time 20XX / 10 / 01 19:00:00, the time designation cursor 404 in the ladder monitor 450 follows the movement and moves to the point where the display time 20XX / 10 / 01 19:00:00 is displayed. The device value in the ladder monitor 450 is updated accordingly according to the movement of the time designation cursor 404. Although the time designation cursor 404a is illustratively moved by the user, the time designation cursor 404a will be linked with the movement of the time designation cursor 404. That is, in the case where the time designation cursor 404 in the ladder monitor 450 moves, the time designation cursor 404a in the camera monitor 430 will move accordingly. Such linkage can be achieved by synchronization control between the program display module 321 and the image display module 323 based on the display time by the playback synchronization control module 324.

[0350] exist Fig.39 The unit monitor 440 is displayed at the lower right part of the screen shown. For example, the unit monitor 440 displays the device value of the buffer storage area (UG) in the motion unit 4d. More specifically, when receiving the display time to be reproduced from the playback synchronization control module 324, the unit display module 325 of the display processor 51 reads the device value corresponding to the received time from the removable memory card 36A, and displays the read device value on the unit monitor 440. Fig.39 In this case, the device values ​​corresponding to the display time 20XX / 10 / 01 18:52:54 are listed on the unit monitor 440.

[0351] Fig.40 Schematic diagram schematically showing a data source for displaying a user interface screen in log reproduction mode. Fig.40As shown, the project display area 420 reads the unit configuration, function setting, program configuration and program components included in the project data 71 from the memory and displays them in a tree form. The ladder diagram monitor 450 reads the program configuration (type of program components included in the program) and program components from the memory to display the program components specified by the user, and reads the device value corresponding to the display time from the log data 73 to display the read device value. The camera monitor 430 reads the image data corresponding to the display time from the log data 73 based on information including the unit configuration (whether the camera monitor is included) and the function setting (functions of the camera monitor, such as (in the case of including two or more ports) port number, imaging cycle, gain setting, etc.). The unit monitor 440 reads the device value corresponding to the display time from the log data 73 based on information including the unit configuration (type of unit) and the function setting (axis configuration, axis control, etc. in the case of the motion unit 4d), and displays the read device value.

[0352] As from Fig.39 and Fig.40 It can be seen that the program display module 321, the image display module 323 and the unit display module 325 can be linked to each other through synchronization control performed by the function of the playback synchronization control module 324. The linkage of the wave display module 322 will be discussed in more detail later.

[0353] In this embodiment, it can be determined whether the current project data is the same as the project data 71 when the actual fault occurs. More specifically, Fig.38 The comparison section 334 of the program display module 321 shown compares the identification information of the project data 71 (user program) provided from the PLC 1 with the identification information of the project data 71 (user program) stored in the PC-side storage device 22, and provides the comparison result to the warning section 335. In the case where the identification information of the project data 71 (user program) provided from the PLC 1 and as information when saving the operation record is different from the identification information of the project data 71 (user program) stored in the PC-side storage device 22, the warning section 335 displays a warning on the display section 55.

[0354] In the present embodiment, it has been exemplarily explained that whether the current project data and the stored project data are identical to each other is judged based on the comparison between the identification information of the current project data and the identification information of the stored project data. More specifically, in the present embodiment, identification information items are added to the program configuration, multiple program components, unit configuration, and unit function settings included in the project data. Whether the current project data and the stored project data are identical to each other is judged based on whether all identification information items of the current project data and the stored project data are identical to each other. However, the present invention is not limited to this. Whether the current project data and the stored project data are identical to each other can be judged based on whether the identification information items of the user program of the current project data including multiple program components and the stored project data are identical to each other.

[0355] In addition to the device values ​​and the image data of the camera 98 when the operation record is saved, the log data also includes user programs such as ladder diagram programs included in the project data when the operation record is saved, and setting files of each unit. For example, the log data includes information such as image data captured by the camera 98 when the fault occurs, the status of each unit, and the angle and coordinates of the motion unit 4d. Therefore, the past status and connection conditions of the device, as well as past information related to the unit, can be saved in the log data. Therefore, the past state can be reproduced by saving the log data. That is, since it can be confirmed what settings have been made and what outputs are provided, this is useful for determining the cause of the fault. By reading these log data using the programming device 70, the settings saved in the log data can be analyzed, and the state can be reproduced and displayed.

[0356] Fig.41 An example of log data 73 is shown. This example shows the acquisition timing of device values ​​d1 to d10, workpiece images i1 to i3 acquired by camera 98a, and other images j1 to j3 acquired by camera 98b. Device values ​​d1 to d10 are acquired in each scanning cycle. Workpiece images i1 to i3 are captured when a trigger signal is generated. Workpiece images j1 to j3 are captured when a trigger signal is generated. The horizontal position of the data represents the time information. Fig.41 As shown, the acquisition time or acquisition cycle of the data does not coincide with each other. For this reason, the display processor 51 adjusts the display timing of the data based on the time information of the data.

[0357] Fig.4273 is a diagram illustrating the display timing and display duration of the log data 73. The display processor 51 displays the device value on the display unit 55 based on the time information of the device value. For example, the display processor 51 determines the display duration of the device value d1 by calculating the time difference between the time information of the device value d1 and the time information of the device value d2. When the display duration has elapsed after the display of the device value d1 starts, the display processor 51 starts the display of the device value d2. Thereafter, the display duration is calculated in the same manner, and the displayed device value is successively changed according to the time information and the display duration.

[0358] As in Fig.41 As shown in FIG. 5 , the acquisition time of the device value d1 is inconsistent with the acquisition time of the workpiece image i1. For this reason, the display processor 51 compares the acquisition time of the workpiece image i1 with the acquisition time of the device values ​​d1 to d10, and selects the time closest to the acquisition time of the workpiece image i1 as the closest device value dx. In this example, the time closest to the shooting time of the workpiece image i1 is the acquisition time of the device value d1. Therefore, the display processor 51 starts to display the workpiece image i1 and the device value d1 at the same time. Subsequently, the display processor 51 determines that the time corresponding to the acquisition time closest to the acquisition time of the workpiece image i2 is closest to the device value dx. In this example, the acquisition time of the device value d4 is closest to the acquisition time of the workpiece image i2. Therefore, when the time to display the device value d4 arrives, the display processor 51 starts to display the device value d4 and the workpiece image i2 at the same time. In addition, the display processor 51 determines that the time corresponding to the acquisition time closest to the acquisition time of another image j1 is closest to the device value dx. In this example, the closest device value at a time closest to the acquisition time of another image j1 is the acquisition time of the device value d2. Therefore, when the time to display the device value d2 arrives, the display processor 51 starts displaying the device value d2 and another image j1 at the same time.

[0359] The display timing of the data items may be adjusted based on the data item having the shortest loading log cycle among the data items included in the log data 73 as described above.

[0360] (Example association between image data and acquisition time)

[0361] In this embodiment, as described above, the image data captured by the camera can be displayed synchronously with the event. On the "Camera / Event" tab 162 in the playback mode, when the user selects one of the events, the camera image is displayed based on the image data captured at the time corresponding to the selected event, and the time designation cursor is also moved to the corresponding reproduction time. In addition, when the play button is pressed, the motion video is reproduced in the camera monitor frame, and the selected event will change according to the elapsed time. Accordingly, the device values ​​of the ladder program in the "Program" tab 165 are also updated. Such synchronized display can be achieved by associating the image data with the acquisition time when the image data is stored. The following reference Fig.41 and Fig.42 To illustrate the association between image data and its acquisition time and device value.

[0362] (Exemplary log data (device value and image data))

[0363] Fig.41 Show Figure 1 The camera unit 4c is shown for collecting device values ​​and loading log timing of images. Up to two cameras can be connected to the camera unit 4c. The cameras can take images from different angles.

[0364] Fig.41 The device values ​​d1 to d10, the workpiece images i1 to i3 acquired by the camera 98, and the acquisition timing of other images j1 to j3 acquired by the camera 2 are shown. The device values ​​d1 to d10 are acquired in each scanning cycle. The workpiece images i1 to i3 are captured when the trigger signal (image acquisition signal) is generated. The workpiece images j1 to j3 are captured when other trigger signals are generated. The horizontal position of the data represents the time information. Fig.41 As shown, the acquisition time or acquisition cycle of data generally does not coincide with each other. For this reason, the display processor 51 of the programmable display 50 adjusts the display timing of the data based on the time information of the data.

[0365] (Explanation of display timing and display duration of log data)

[0366] Fig.42The display timing and display duration of the log data are shown. The display processor 51 displays the device value on the display unit 55 based on the time information of the device value. For example, the display processor 51 determines the display duration of the device value d1 by calculating the time difference between the time information of the device value d1 and the time information of the device value d2. When the display duration has passed after the display of the device value d1 starts, the display processor 51 starts the display of the device value d2. Thereafter, the display duration is calculated in the same manner, and the displayed device value is successively changed according to the time information and the display duration.

[0367] As described above, the acquisition time of the device value d1 is inconsistent with the acquisition time of the workpiece image i1. For this reason, the display processor 51 compares the acquisition time of the workpiece image i1 with the acquisition time of the device values ​​d1 to d10, and selects the time closest to the acquisition time of the workpiece image i1 to be closest to the device value dx. In this example, the time closest to the shooting time of the workpiece image i1 is the acquisition time of the device value d1. Therefore, the display processor 51 starts to display the workpiece image i1 and the device value d1 at the same time. Subsequently, the display processor 51 determines that the time corresponding to the acquisition time closest to the acquisition time of the workpiece image i2 is closest to the device value dx. In this example, the acquisition time of the device value d4 is closest to the acquisition time of the workpiece image i2. Therefore, when the time to display the device value d4 arrives, the display processor 51 starts to display the device value d4 and the workpiece image i2 at the same time. In addition, the display processor 51 determines that the time corresponding to the acquisition time closest to the acquisition time of another image j1 is closest to the device value dx. In this example, the closest device value at the time closest to the acquisition time of another image j1 is the acquisition time of the device value d2. Therefore, when the time to display the device value d2 arrives, the display processor 51 starts to display the device value d2 and another image j1 at the same time. The display timing of the data item is adjusted based on the data item with the shortest loading log cycle among the data items included in the log data as described above.

[0368] (Linkage between image data and time information)

[0369] exist Fig.23 The image data and the time information are displayed synchronously with each other in the camera / event display screen 170 of FIG. Fig.43 The flowchart shows the process of linking image data and time information. Fig.104c using the ring buffer 91b. In step S4301, it is first determined whether the acquisition relay is ON. Specifically, the camera unit processor 41c (CPU, etc.) of the camera unit 4c determines whether the image data acquisition condition is satisfied (for example, whether the PLC 1 switches from PROG mode (setting mode) to RUN mode (execution mode), and whether the acquisition relay becomes ON). In the case where the acquisition relay is not ON, the process returns to step S4301 and repeats the routine.

[0370] In the case where the acquisition relay is turned ON, the process proceeds to step S4302, where it is determined whether the moment to acquire image data (image data acquisition timing) has arrived. Specifically, the camera unit processor 41c determines whether the moment to acquire image data has arrived. The acquisition timing can be defined, for example, by a shooting cycle (internal control cycle) predefined in the camera unit 4c. In the case where it is not the acquisition timing, the process returns to step S4302 and repeats the routine.

[0371] In the case of acquisition timing, the process proceeds to step S4303, wherein in step S4303, image data and time information are acquired and written into the ring buffer. Specifically, a shooting instruction is sent to the camera so that the camera shoots image data. In order to associate the image data with its shooting time, the current time information is read from a time management unit such as an internal timer so that the image data associated with its time information is written into the ring buffer.

[0372] Subsequently, it is determined in step S4304 whether a read request has occurred. Specifically, the camera unit processor 41c determines whether the CPU-mounted unit 3 has issued a read request (read instruction) to the ring buffer of the camera unit 4c. In the case where a read request has not been issued, the process returns to step S4302.

[0373] In the case where the read request is received, the process proceeds to step S4305, where the image data and its time information are acquired from the ring buffer and sent to the CPU mounting unit 3. The CPU mounting unit 3 adds the image data and its time information as log data to the operation record data. Thus, the image data and its time information are associated in the operation record data.

[0374] (Relationship between exercise data and time information)

[0375] As mentioned above Fig.43As described above, similar to the association between the image data captured by the camera and its time information, the motion data can also be associated with its time information. Specifically, the motion unit 4d stores setting information of programs and parameters (axis configuration, axis control, etc.) for defining the operation of the motion unit 4d. Figure 1 The motion unit 4d shown includes a motion unit processor 41d. The motion unit processor 41d sends operation instruction values ​​such as target coordinates and speed to an externally connected electric motor (motor amplifier) ​​based on setting information. Motion data including current coordinates and current speed are received from the electric motor amplifier via an encoder. The control cycle for receiving motion data including current coordinates and current speed is shorter than the scanning cycle of the ladder program and is not synchronized with the scanning cycle of the ladder program. The motion unit processor 41d collects motion data at a predetermined cycle. The motion unit processor 41d associates information related to the reception time of the motion data, the motion data and the time information (read from a time management unit such as an internal timer), and writes the three into its own ring buffer. Subsequently, with the reference Fig.43 The same as the case of the camera unit 4c, the motion unit 4d obtains the motion data (current coordinates, current speed, etc.) and its time information from the ring buffer, and sends both to the CPU installation unit 3 at the saving timing. The CPU installation unit 3 adds the motion data and its time information as log data to the operation record data. Therefore, the motion data and its time information are associated in the operation record data.

[0376] (Linkage between event data and time information)

[0377] Reference now Fig.44 The flowchart is used to illustrate Fig.23 The process of linkage between event data and time information in the camera / event display screen 170. In step S4401, the event management unit of the CPU installation unit processor 31 first detects an event. Various events can be the event to be detected. Examples of events to be detected can be provided by: rewriting of project data including user programs of PLC 1 and unit configuration information related to each unit; power on / off switching of input / output devices; mode switching between setting modes for setting PLC 1 or operating modes for making PLC 1 run (work); clearing of various histories; insertion / removal of memory (memory card, etc.); insertion / removal of Ethernet cables used for communication with other devices; device rewrite signals required for the programmable display 50 connected to PLC 1; and motion errors of motion units in PLC 1; etc.

[0378] An event occurring in the expansion unit 4 such as a motion unit can be detected as follows. The motion unit processor 41d sends a message communication command including an event to the CPU mounting unit 3 via the inter-unit bus. The CPU mounting unit processor 31 uses an interrupt to receive a message communication command including an event. The CPU mounting unit processor 31 extracts the event from the received message communication command. Therefore, the CPU mounting unit processor 31 can recognize various events occurring in the motion unit at appropriate timing.

[0379] Subsequently, in step S4402, the event management section of the CPU installation unit 3 checks the remaining capacity of its event log. In the present embodiment, a predetermined storage area of ​​the temporary recording section 91a is used as an event log memory. Needless to say, the event log memory may be provided separately from the temporary recording section 91a. In the event that the remaining capacity of the event log is insufficient, the process proceeds to step S4403, wherein in step S4403, the oldest event is deleted from the event log memory. In the event that the remaining capacity of the event log is sufficient, the process proceeds to step S4404, wherein in step S4404, microsecond-level moment information is acquired and the moment information is associated with the event, so that the associated moment information and event are stored in the event log memory.

[0380] (Device monitoring using programmable display 50)

[0381] Reference now Fig.45 The basic processing of the programmable display 50 when monitoring a device is described by the flowchart of . The programmable display 50 monitors the device of PLC 1. PLC 1 cannot grasp the device displayed on the programmable display 50. For this reason, the display side communication unit 58 of the programmable display 50 accesses PLC 1 at a fixed interval (for example, 10ms) and reads the device value of the device that can be used to display data (step S4501). The read device value is stored in the data memory 56 of the programmable display 50.

[0382] The display processor 51 of the programmable display 50 determines whether any of the device values ​​read has changed from its corresponding current device value (step S4502). In the case where there is no device value change, since the currently displayed screen is maintained, the process will end without any processing. In the case where any of the device values ​​read has changed, display data is generated based on the read device value so that the screen is updated to a screen corresponding to the read device value (step S4503).

[0383] The basic processing has been described. The basic processing described focuses on the reading of the device value. However, at the time of the touch operation of the switch component, etc., the device value is written in the communication between the programmable display 50 and the PLC 1. That is, when it is recognized that the device value of the device in the data storage 56 has changed, the programmable display 50 notifies the PLC 1 that the device value of the device has changed in the communication with the PLC 1, so that the CPU installation unit processor 31 writes the changed device value of the device into the PLC side device section 34 of the CPU installation unit storage section 32.

[0384] Figure 2 The user interface screen of the monitoring screen 240 is shown. Fig.21 When the user touches the "monitoring screen" button 144 in the menu screen 140 of Figure 2 Some types of components such as switches, meters, and lamps are arranged on the monitoring screen 240. "ABC-123" is indicated in the numerical display box 241 of the production number. The device of PLC 1 is assigned to the numerical display box 241. Lamps 242 and 243 indicating normal and error are arranged on the left side of the numerical display box 241. Figure 2 In the example of , the normal light 242 is in a lit state, and the error light 243 is in an extinguished state. Component labels (component identification numbers) are assigned to the normal light 242 and the error light 243. In addition, device and component icons are assigned to the normal light 242 and the error light 243. The display style of the component will change according to the status of its corresponding device. Specifically, two component icons (a lit icon and an extinguished icon) are provided to the normal light 242. One of these component icons is shown according to the status of the corresponding device based on a predefined setting. A thermometer 244 is arranged on the right side of the lights 242 and 243, and the thermometer 244 indicates 60°C. In addition, a component label is provided to the thermometer 244. In addition, a device and component image is provided to the thermometer 244. The pointer of the thermometer 244 can swing according to the device value of the corresponding device.

[0385] exist Figure 2 The progress management box 245 for products A to D is displayed at the lower part. The target value and the current value are indicated in the numerical display box of the corresponding product. A reset switch 246 is arranged on the right side of the current value. In addition, a component label is provided to the reset switch 246. In addition, a device and a component image are provided to the reset switch 246. The component image includes an image when the reset switch 246 is touched and an image when the reset switch 246 is not touched. The above-mentioned counter chart is arranged on the right side of the reset switch 246. As described above, component labels, devices, and component images are provided to various components.

[0386] Second embodiment

[0387] In the first embodiment described above, the screen has been described as switching to the device wave display screen by a touch operation on the system screen which is a predetermined page provided by the programmable display 50. That is, the touch detector 53 detects a touch operation on the wave display component arranged on the system screen, so that the device wave of the target device is displayed based on the corresponding time sequence data stored in the PLC 1. Specifically, when the user touches the system screen, the device wave display screen is displayed. Fig.21 When the "playback mode start" button 141 or the "real-time graph monitor (playback mode)" button corresponding to the wave display component is touched on the menu screen 140 shown in FIG. Fig.12 The device wave display screen 160 (real-time graph monitor display) shown enables display of the operation record data recorded in the past in the playback mode.

[0388] However, the present invention is not limited to an activation structure that calls a device wave display screen from a predefined page such as a system screen, etc. For example, a wave display component that switches the screen to the device wave display screen may be arranged on a user screen created by a user. Fig.46 Such a user screen 250 of the programmable display according to the second embodiment is shown. In the illustrated user screen 250, various display components created by the user are arranged. When the user touches the "playback mode start" button 251 of the wave display component arranged at the lower right part of the user screen 250, the display Fig.12 The device wave display screen 160 shown. In this case, the screen can be immediately switched to the device wave display screen 160 not only on the system screen but also in the user screen created by the user. Therefore, the user can easily obtain information useful for eliminating the fault. That is, the user can easily start to restore the system. Therefore, this can improve user convenience.

[0389] Third embodiment

[0390] In the above-described first and second embodiments, the touch detector 53 has been described as detecting a touch operation on the wave display component arranged on the system screen and the user screen so that the device wave of the target device is displayed based on the corresponding time-sequential data saved in the PLC 1.

[0391] However, the present invention is not limited thereto. When a specific touch operation pre-defined as displaying a device wave is detected, the device wave may be displayed. Fig.47 Such a user screen 260 of the programmable display according to the third embodiment is shown. The programmable display displays the user screen 260 created by the user on the display unit. In the user screen 260, the non-component arrangement part NA ( Fig.47When a specific touch operation is performed (in the oblique line shaded area in the figure), the device wave display screen 160 can be called. The specific operation can be, for example, a long press, flick, pinch, and split on the non-component arrangement part NA. Fig.47 In the case of , when the user flicks upward on a point on the non-component arrangement part NA, the screen may switch to Fig.12 The device wave displays screen 160. If the user wants to return to the page, he can flick down Fig.12 Any point on the display screen can be switched back to Fig.47 In addition, the screen can be switched to a different page according to the flicking direction on the display screen. For example, the screen is switched to the device wave display screen 160 by flicking upward at any point on any page, and is switched back to the previous page by flicking downward at any point on the device wave display screen 160.

[0392] In addition, the screen can be switched by flicking to the left or right. For example, the screen can be switched to the page corresponding to the screen ID+1 (next page) by flicking to the right, and the screen can be switched to the page corresponding to the screen ID-1 (previous page) by flicking to the left. In this case, since the screen can be switched to a different page according to the flick direction on the display screen, the user can intuitively switch the screen through easy operations. Therefore, this can improve user convenience.

[0393] Although it has been explained in the above example that such a touch operation only for the non-component arrangement part switches the screen to the device wave display screen, the present invention is not limited thereto. The screen can be switched to the device wave display screen by such a touch operation for the area including the part where the display component is arranged. For example, in the case where the user flicks a point on the display screen, even when the user touches the part where the display component is arranged, it is assumed that the display component is not flicked. As a result, such a flick operation can be distinguished from an intentional selection operation of the display component such as a normal tap and a long press.

[0394] Fourth embodiment

[0395] In the first to third embodiments described above, the screen of the display unit 55 is switched to the device wave display screen 160. However, the present invention is not limited thereto. The device wave may be displayed on the system screen or the user screen without switching to the dedicated device wave display screen. Fig.48 Such a user screen of the programmable display 270 according to the fourth embodiment is shown. In this embodiment, a wave area display component 271 including a wave display area for displaying device waves is provided as one of the display components that the user can select and arrange. The wave area display component 271 is displayed on the Fig.48 The wave area display component 271 is a relatively large display component used as a wave display area that enables the user to see the device wave with certainty. The display data generator 51a displays the operation record data acquired from the PLC 1 as a device wave in the wave display area of ​​the wave area display component 271. The device wave displayed in the wave area display component 271 can also be displayed as a motion video or as a still image within a specified time range.

[0396] The wave area display component 271 may have a function for selecting devices to be displayed with device waves and specifying the display time of these devices. Fig.48 In the example of FIG. 2 , a “description” button 272 is included in the wave region display component 271. When the user touches the “description” button 272, a device selection menu or a slider-shaped operation bar representing the time axis may be displayed. Alternatively, when the user touches the “description” button 272, a Fig.12 The real-time chart monitor in replay mode is shown.

[0397] Since the device wave when a fault occurs can be easily checked on the programmable display 50, the field engineer can try to eliminate the fault if the fault can be solved at the FA site without requiring the system engineer who designed the FA system to analyze the fault. Therefore, the time required to restore the FA system can be shortened. In addition, since the device wave of the device required for diagnosing the cause of the fault can be selectively displayed, such selective display of the device wave is useful for diagnosing the fault.

[0398] Fifth embodiment

[0399] The programmable display according to the present invention can show how to eliminate the fault when a fault occurs. For example, a guide display screen is prepared and displayed to show how to eliminate such a fault. Now refer to Fig.49 Such a programmable display according to a fifth embodiment will be described. Fig.49 1 is a schematic diagram showing a switching setting screen 120B displayed on a screen data editing device included in a programmable logic controller system. Fig.14 When "playback mode start" is selected in the switch function selection box 121 in the switching setting screen 120 of the screen data editing device shown in FIG. Fig.49 The switching settings screen 120B is shown.

[0400] exist Fig.49 In the switching setting screen 120B shown in the figure, when the "RTCM" tab 125a is clicked in the real-time chart monitor (playback mode) description & setting box 124, the Fig.15When the "Guide" tab 125b is clicked in the Real-time Chart Monitor (Replay Mode) Description & Settings box 124, the following will be displayed: Fig.50 The switch settings screen is shown.

[0401] exist Fig.49 The real-time chart monitor (playback mode) description & setting box 124 shown is provided with a content selection radio button 124A, a message block number designation box 124B, and a block number box 124C. Select the message button or the image button in the content selection radio button 124A. Fig.49 In the exemplary screen shown, the message button is selected. In the message block number designation box 124B, select internal or external designation. Fig.49 In the exemplary screen shown, internal designation is selected. In the block number box 124C, 0 (zero) is selected for the block number to be used when internal designation is selected. Then, the guidance message is displayed on the guidance message display box 124D set in the lower area of ​​the real-time chart monitor (playback mode) description & setting box 124. When the message edit button 129 is clicked, the guidance message to be displayed in the programmable display 50 can be edited.

[0402] As mentioned above, the boot message is pre- Fig.13 In the case where the "playback mode start" button 141b set in the menu screen displayed in the screen display frame 112 is associated, as shown in FIG. Fig.50 As shown, in the device wave display screen 160C on the programmable display 50, Fig.12 A pop-up image (floating window image) 280 appears in the foreground of the playback mode screen image shown. In other words, the guidance message is exemplary guidance information showing how to eliminate an error event that occurs when the save condition is met. The guidance information is, for example, similar to the information predefined to show the device value as Fig.16 The device values ​​shown are associated with the devices (DM100, DM200, R000). Fig.13 When the "playback mode start" button 141b is clicked in the playback mode, display data for displaying the guide information is created. As a result, the guide message will be displayed together with the device wave. Fig.50 The device wave shown is displayed on screen 160C.

[0403] Fig.50 2 is a schematic diagram showing a device wave display screen in playback mode according to a modified example. Fig.50 As shown, in Fig.49 The guidance message created in the switching setting screen 120B shown in FIG. 120B appears (in a pop-up manner) in the foreground of the device wave display screen 160C. Fig.50In the example, after selecting the "Real-time Graph Monitor" tab 161, a guidance message is shown in the foreground of the device wave screen. More specifically, for example, Fig.50 Among the guidance messages shown in the pop-up image 280, the third message (3.) "Check the camera image near the latest ON timing in the device wave of R000" is indicated. After reading this message, the field engineer will check the camera image near the latest ON timing in the device wave of R000 and can try to eliminate the fault.

[0404] In addition, from Fig.49 In the case where the image button is selected from the content selection radio button 124A, a file number designation box will be displayed in place of the message block number designation box 124B. The user can designate one or more specific image files via the file number designation box. The user can designate one or more specific image files by designating an image file name in a specific directory or an identifier for identifying a specific image file via the file number designation box. Alternatively, the user can designate a specific image file by designating a specific path indicating the location where the image file is located. In this case, Fig.50 In the pop-up image 280 shown, instead of the guide message, one or more images specified via the file number designation box are popped up. Such an image file can be created in advance by the user and can include, for example, Fig.49 The pop-up image 280 shows a message and an explanation of how to eliminate the fault.

[0405] In addition, for example, in Fig.49 In the message block number designation box 124B shown, when external designation is selected, the device value of a specific device in the PLC is referenced, and the message block number can be dynamically designated based on the device value in operation. Fig.33 The external specification is the same as described in the RTCMID specification in the "RTCMID Specification" box 126 shown.

[0406] exist Fig.49 When specifying a message or image in the Fig.34C The same data structure as above is shown, and the message block number is assigned to the device (associated with the device). More specifically, for example, the reference Fig.49 The message block number = 0 is assigned to the designated device DM300 = 0 together with RTCMID = 0. In the case where a message or an image is designated in the content selection, a file number is similarly assigned to the device (device-dependent).

[0407] In addition, you can Fig.49In the switching setting screen 120B shown in FIG. 1 , a selection box or a selection button is provided for switching between ON and OFF of the guide display. In this case, if the user chooses not to display the guide, the guide is not displayed. Fig.50 A guidance message in a pop-up image 280 is shown.

[0408] In the above embodiment, when the preservation condition is met in PLC 1, the programmable display 50 obtains the operation record data stored in the storage memory 36 of PLC 1. When the operation record data is obtained, the e-mail for notifying the acquisition of the operation record data can be automatically sent to a predetermined e-mail address (so-called e-mail notification). According to the e-mail notification, for example, an error can be notified to the field engineer on the production line. In addition, in the case of sending an e-mail to the outside, the operation record data can be automatically attached to the e-mail. In the case where the data volume of the operation record data is large, the operation record data can be divided into multiple parts, so that the operation record data parts can be attached to multiple e-mails and sent to a predetermined e-mail address by e-mail. In addition, the image data of the image related to the error can be attached to the e-mail and sent to a predetermined e-mail address by e-mail. In this case, for example, the field engineer can not only be informed that an error has occurred, but also receive the operation record data and analyze the cause of the error.

[0409] The programmable display and the programmable logic controller system including the programmable display can be suitably used for diagnosis of a fault in the FA system, that is, for so-called troubleshooting.

[0410] It should be apparent to those skilled in the art that, although various preferred embodiments of the present invention have been shown and described, it should be appreciated that the present invention is not limited to the specific embodiments disclosed, wherein these specific embodiments are regarded as merely illustrative of the inventive concept and should not be construed as limiting the scope of the invention, and are applicable to all modifications and changes that fall within the scope of the invention as defined in the appended claims.

Claims

1. A programmable display device that can be connected to a programmable logic controller, the programmable logic controller collecting device values ​​of a plurality of devices as a storage area to be referenced by a user program, and temporarily recording information related to the acquisition time of the device values ​​in association with the device values ​​in chronological order, and saving the chronological data related to the temporarily recorded device values ​​of the plurality of devices in a saving memory when a predefined saving condition is satisfied, the programmable display comprising: A storage unit is provided to store: component setting for assigning the device to a corresponding component among a plurality of components arranged on one screen image as a page to monitor or change the status of the device of the programmable logic controller, a page setting for managing the component setting in units of pages by using a page identifier for identifying a plurality of pages, and an object device setting for specifying, based on user designation, an object device among the plurality of devices, the object device showing a device value to be stored in the saving memory of the programmable logic controller as time-sequential data in a waveform as a device wave; a display data generator for generating display data of a page corresponding to the page identifier in units of pages based on the component settings and the page settings stored in the settings storage unit; a display unit including a display screen, and displaying a page corresponding to the page identifier on the display screen based on the display data generated by the display data generator; as well as a touch detector for detecting a touch operation on the display screen of the display unit, wherein the display data generator generates display data for changing an image of the display screen from a current page to another page based on the page setting when the touch detector detects a predetermined first touch operation on the display screen, and generates display data for displaying a device wave of a device specified by the object device setting based on the time sequence data stored in the programmable logic controller and the object device setting stored in the setting storage unit when the touch detector detects a predetermined second touch operation on the display screen, and The display unit displays the other page or the device wave on the display screen based on the display data generated by the display data generator.

2. The programmable display according to claim 1, in, The setting storage section stores default screen information indicating a predefined default screen having a format for displaying the device wave, and Wherein, when the touch detector detects the predetermined second touch operation on the display screen, the display data generator superimposes the time sequence data on the default screen based on the default screen information and the time sequence data to generate display data for displaying the device wave of the device specified by the object device setting.

3. The programmable display according to claim 2, wherein: When the display unit displays the device wave on the display screen and the touch detector detects a change operation for changing a display portion of the device wave that has been displayed, the display data generator extracts a portion of the time sequence data corresponding to the display portion of the device wave requested by the change operation, and generates new display data for displaying the requested display portion of the device wave.

4. The programmable display according to claim 1, in, The component settings stored in the setting storage unit also include settings of a wave display component for displaying the device wave, and The second touch operation is a touch operation on the wave display component arranged on the first page displayed on the display screen.

5. The programmable display according to claim 1, wherein: The second touch operation is a specific touch operation on a non-component arrangement portion of the first page displayed on the display screen where no display components are arranged.

6. The programmable display according to claim 5, wherein: The specific touch operation is any one of long pressing, flicking, pinching in, and breaking out of the non-component arrangement portion.

7. The programmable display according to claim 1, in, The component settings stored in the setting storage unit also include: an acquisition device for repeatedly acquiring time-sequential data of device values ​​temporarily recorded in a temporary recording section of the programmable logic controller, and The setting of a real-time display component, wherein the real-time display component is used to sequentially display the time sequence data of the acquisition device, Among them, when a touch operation on the real-time display component is detected, based on the time sequence data of the device value of the acquisition device temporarily recorded in the temporary recording unit of the programmable logic controller, the display data generator generates display data for sequentially displaying the device value on the display screen.

8. The programmable display according to claim 1, in, The programmable logic controller is capable of associating image data provided from an external camera connectable to the programmable logic controller with information on an acquisition time of photographing the image data, and temporarily storing the image data associated with the information on the acquisition time, when a predefined saving condition is satisfied; and The programmable display requests the programmable logic controller to send operation log data, and displays an image corresponding to image data included in the operation log data on the display unit based on information related to an acquisition time included in the operation log data.

9. The programmable display according to claim 1, in, In the case where a predefined saving condition is satisfied, the programmable logic controller is capable of associating the operation log data with a user program executed when the predefined saving condition is satisfied, and saving the user program associated with the operation log data, and In which, the programmable display requests the programmable logic controller to send the saved operation record data, and based on the information related to the acquisition time included in the operation record data, superimposes the device value acquired at the acquisition time on the user program included in the operation record data on the display unit.

10. The programmable display according to claim 1, in, In a case where the programmable logic controller collects event data corresponding to a plurality of events occurring in the programmable logic controller or a controlled device to be controlled by the programmable logic controller, and associates the event data with the occurrence time of the event and stores the event data associated with the occurrence time of the event in chronological order, when a predefined saving condition is satisfied, the programmable logic controller is capable of saving the stored event data in the operation log data so that the stored event data can be associated with the operation log data, and The programmable display requests the programmable logic controller to send the stored operation record data, and displays an event corresponding to the event data included in the operation record data on the display unit based on the occurrence time included in the operation record data.

11. The programmable display according to claim 1, wherein: The programmable display displays a selection screen that enables selection of the target device as an initial display image when the device wave is displayed on the display screen.

12. The programmable display according to claim 1, wherein: In a case where the device wave is displayed on the display screen, the programmable display displays the one or more target devices based on identification information for specifying one or more target devices having a device value to be shown as the device wave.

13. The programmable display according to claim 1, wherein: The programmable display displays a setting screen that enables selection of one or more target devices and a representation style of the one or more target devices, when the device wave is displayed on the display screen. 14 . The programmable display according to claim 1 , further comprising a display-side communication unit capable of communicating with the programmable logic controller. 15 . The programmable display according to claim 14 , further comprising a display-side device unit that communicates with the programmable logic controller via the display-side communication unit and maintains a device value synchronized with a device value of the programmable logic controller.

16. The programmable display according to claim 1 further comprises a guidance information storage unit for storing guidance information associated with the device specified by the object device setting and showing how to eliminate an error event that occurs when the saving condition is satisfied, in, The display data generator generates display data for displaying the guide information stored in the guide information storage section and associated with the device specified by the target device setting when the touch detector detects the predetermined second touch operation on the display screen.

17. A programmable logic controller system, comprising: A programmable logic controller for collecting device values ​​of a plurality of devices as a storage area to be referenced by a user program, and associating the device values ​​with information related to a time of collection of the device values, and temporarily recording the device values ​​associated with the information related to the collection time in chronological order, and saving the chronological order data related to the temporarily recorded device values ​​of the plurality of devices in a saving memory when a predefined saving condition is satisfied; as well as a programmable display connectable to the programmable logic controller, Wherein, the programmable logic controller comprises: A program execution unit, used for repeatedly executing the user program; a device section including a device as a storage area to be referenced by the program execution section; a temporary recording unit for collecting device values ​​of devices stored in the device unit, associating the device values ​​with information related to the collection time of the device values, and temporarily recording the device values ​​associated with the information related to the collection time in chronological order; The storage memory is used to store the time-sequential data related to the device values ​​of the plurality of devices temporarily recorded in the temporary recording unit as operation record data when a predefined storage condition is satisfied, Wherein, the programmable display comprises: A storage unit is provided to store: component setting for assigning the device to a corresponding component among a plurality of components arranged on one screen image as a page to monitor or change the status of the device of the programmable logic controller, a page setting for managing the component setting in units of pages by using a page identifier for identifying a plurality of pages, and an object device setting for specifying, based on user designation, an object device among the plurality of devices, the object device showing a device value to be stored in the saving memory of the programmable logic controller as time-sequential data in a waveform as a device wave; a display data generator for generating display data of a page corresponding to the page identifier in units of pages based on the component settings and the page settings stored in the settings storage unit; a display unit including a display screen, and displaying the page corresponding to the page identifier on the display screen based on the display data generated by the display data generator; and a touch detector for detecting a touch operation on the display screen of the display unit, wherein the display data generator generates display data for changing an image of the display screen from a current page to another page based on the page setting when the touch detector detects a predetermined first touch operation on the display screen, and generates display data for displaying a device wave of a device specified by the object device setting based on the time sequence data stored in the programmable logic controller and the object device setting stored in the setting storage unit when the touch detector detects a predetermined second touch operation on the display screen, and The display unit displays the other page or the device wave on the display screen based on the display data generated by the display data generator.

Images