JP7466319B2 - Programmable display and programmable logic controller system equipped with the same - Google Patents

Description

The present invention relates to a programmable display and a programmable logic controller system equipped with the same.

In FA (Factory Automation) systems, programmable logic controllers (hereafter referred to as "PLCs") are used as control devices to control input/output devices such as sensors, motors, and actuators. The system designer who builds the FA system considers the sequence in which each input/output device should operate, and creates a ladder program to achieve that sequence. Ladder programs are designed using a general-purpose PC with a dedicated application program for editing programs installed. After designing, debugging, and creating the ladder program, the system designer transfers the completed ladder program to the PLC and has it executed by the PLC.

On the other hand, the status of the input/output devices while the PLC is operating is monitored on-site using a programmable display connected to the PLC. Various functional parts such as lamps and switches are arranged on the display screen of the programmable display, and various functions are assigned to these functional parts. The display data for the display screen is designed using a general-purpose personal computer installed with a dedicated application program for editing the display data. The on-site staff who maintain the FA system usually understands in what sequence each input/output device should be operated, just like the system designer mentioned above. However, there are many different ways to write a ladder program to efficiently realize that sequence, so it takes a typical on-site staff a long time to read and understand the description of the ladder program.

When a problem occurs during the operation of a manufacturing line on which an FA system is installed, the production line may come to a halt. When a problem occurs on a typical programmable display, an alarm lamp (part image) located on the display screen lights up or flashes to notify on-site personnel that a problem has occurred.

However, there are many cases where the cause of a problem cannot be determined by just checking the alarm lamp. This includes simple problems that can be quickly resolved on-site, and in such cases, having on-site personnel quickly resolve the problem leads to early recovery of the system.

JP 2003-029829 A

One of the objectives of the present invention is to provide a programmable display that makes it easier to solve problems that occur at an FA site, and a programmable logic controller system equipped with the same.

Means for solving the problem and effects of the invention

A programmable display according to a first aspect of the present invention is connected to a programmable logic controller that collects device values of a plurality of devices that are memory areas referenced by a user program, associates information relating to the acquisition time of the device values with the device values and temporarily records them in chronological order, and when predetermined storage conditions are satisfied, stores the temporarily recorded time-series data relating to the device values of the plurality of devices in a storage memory . This programmable display device comprises a setting memory unit that stores, as a page, a screen on which a plurality of components for monitoring or changing the state of a device of the programmable logic controller are arranged, component settings for assigning the device to each of the components arranged on the screen, page settings for managing the component settings on a page-by-page basis using page identifiers that identify a plurality of different pages, and target device settings for identifying a target device among the plurality of devices for displaying a device waveform in which time-series data stored in the storage memory of the programmable logic controller is shown in a waveform shape based on a user designation, a display data generation unit that generates display data for each page corresponding to the plurality of different page identifiers based on the component settings and page settings stored in the setting memory unit, and a display unit that displays the page corresponding to the page identifier on the display screen based on the display data generated by the display data generation unit, and a touch detection unit that detects a touch operation on the display screen of the display unit. The display data generating unit generates display data for switching from the current page to another page based on the page setting when the touch detection unit detects a first touch operation preset on the display screen, and generates display data for displaying the device waveform of a device specified by the target device setting based on the time series data stored in the programmable logic controller and the target device setting stored in the setting storage unit when the touch detection unit detects a second touch operation preset on the display screen. The display unit displays the other page or the device waveform on the display screen based on the display data generated by the display data generating unit. With the above configuration, it is possible to selectively execute an operation of switching to a different page and an operation of displaying the device waveform of the time series data stored in the programmable logic controller by a touch operation on the programmable display. In particular, since the device waveform can be confirmed on the display screen of the programmable display, information for quickly solving a problem occurring at an FA site can be easily obtained on site.

In addition to the above configuration, the programmable display according to the second aspect of the present invention has the following features: the setting storage unit stores default screen information indicating a default screen having a predetermined format for displaying the device waveform; and when the touch detection unit detects the second preset touch operation on the display screen, the display data generation unit generates display data for displaying the device waveform of the device specified by the target device setting by overlaying the time series data on the default screen based on the default screen information and the time series data.

Furthermore, in a programmable display according to a third aspect of the present invention, in addition to any of the above configurations, when the touch detection unit detects a change operation (e.g., a slide operation of a time designation cursor) for changing the display range of the device waveform while the device waveform is displayed on the display screen by the display unit, the display data generation unit can generate display data for displaying the device waveform in the changed display range by extracting time series data corresponding to the changed display range specified by the change operation from the time series data.

Furthermore, in a programmable display according to a fourth aspect of the present invention, in addition to any one of the above configurations, the component settings stored in the setting memory unit further include settings for a waveform display component for displaying the device waveform, and the second touch operation is a touch operation on the waveform display component arranged on a first page displayed on the display screen.

Furthermore, in a programmable display according to a fifth aspect of the present invention, in addition to any of the configurations described above, the second touch operation is a specific operation on a non-placement area other than the area in which the component is placed on the first page displayed on the display screen.

Furthermore, in addition to any of the configurations described above, the programmable display according to a sixth aspect of the present invention is such that the specific operation is a long press, a flick, a pinch-in, or a pinch-out on the non-placement area.

Furthermore, in a programmable display according to a seventh aspect of the present invention, in addition to any of the above configurations, the component settings stored in the setting storage unit further include settings for an acquisition device that repeatedly acquires time-series data of device values temporarily recorded in the temporary recording unit of the programmable logic controller, and settings for a real-time display component for sequentially displaying the time-series data of the acquisition device, and the display data generation unit is configured to generate display data for sequentially displaying the device values on the display screen based on the time-series data of the device values of the acquisition device temporarily recorded in the temporary recording unit of the programmable logic controller when a touch operation on the real-time display component is detected.

Furthermore, in addition to any of the above configurations, the programmable display of an eighth aspect of the present invention is configured such that, when a predetermined storage condition is satisfied, image data input from an external camera connected to the programmable logic controller is temporarily stored in the programmable logic controller in association with information regarding the acquisition time at which the image data was acquired, and the programmable display acquires driving record data including log data stored in the storage memory during operation of the programmable logic controller , and displays an image based on the image data included in the driving record data on the display unit based on the information regarding the acquisition time included in the driving record data.

A ninth aspect of the present invention provides a programmable display device having any of the above configurations, which is configured to, when a predetermined storage condition is satisfied, store a user program that was being executed by the programmable logic controller when the storage condition was satisfied in association with driving record data including log data stored in the storage memory during operation of the programmable logic controller . The programmable display device is configured to acquire the stored driving record data from the programmable logic controller and, based on information regarding the acquisition time included in the driving record data, display a device value corresponding to the acquisition time on the user program included in the driving record data on the display unit.

Furthermore, in a programmable display according to a tenth aspect of the present invention, in addition to any of the above configurations, event data corresponding to a plurality of events occurring in the programmable logic controller or a controlled device controlled by the programmable logic controller is collected by the programmable logic controller, and the event data is associated with the occurrence time of the events and stored in chronological order; when a predetermined storage condition is satisfied, the stored event data is stored as part of driving record data so that it is associated with the driving record data including log data stored in the storage memory during operation of the programmable logic controller ; and the programmable display is configured to acquire the stored driving record data and display an event corresponding to the event data included in the driving record data on the display unit based on the occurrence time included in the driving record data.

Furthermore, in addition to any of the above configurations, the programmable display according to an eleventh aspect of the present invention is capable of displaying a selection screen for selecting the target device as the initial display when displaying the device waveform on the display screen.

Furthermore, in addition to any of the above configurations, the programmable display according to the twelfth aspect of the present invention can display one or more target devices based on identification information for identifying one or more target devices to be displayed when displaying the device waveforms on the display screen. With the above configuration, when some kind of trouble occurs during the operation of the FA system, the device waveforms of devices likely to be related to the cause of the trouble can be selectively displayed, thereby realizing a programmable display that presents information useful for identifying the cause of the trouble and is useful for early recovery.

Furthermore, in addition to any of the above configurations, the programmable display according to a thirteenth aspect of the present invention is capable of displaying one or more target devices and a setting screen for setting the display format when the device waveform is displayed on the display screen. With the above configuration, when some kind of trouble occurs during the operation of the FA system, the device waveform of a device likely to be related to the cause of the trouble can be selectively displayed, thereby realizing a programmable display that presents information useful for identifying the cause of the trouble and is useful for early recovery.

Furthermore, the programmable display according to the fourteenth aspect of the present invention, in addition to any of the above configurations, further includes a display-side communication unit that communicates with the programmable logic controller.

Furthermore, in addition to any of the above configurations, the programmable display according to the fifteenth aspect of the present invention further includes a display-side device unit that communicates with the programmable logic controller via the display-side communication unit and holds a device value synchronized with the device value of the programmable logic controller.

Furthermore, in addition to any of the above configurations, the programmable display according to a sixteenth aspect of the present invention further includes a guidance information storage unit that stores guidance information associated with a device specified by the target device setting and that guides a user in a countermeasure method for resolving an error event when the save condition is satisfied, and the display data generation unit is configured to generate display data that is stored in the guidance information storage unit and that displays the guidance information associated with the device specified by the target device setting when the touch detection unit detects the second touch operation on the display screen.

A programmable logic controller system according to a seventeenth aspect of the present invention includes a programmable logic controller that collects device values of a plurality of devices that are storage areas referenced by a user program, associates information regarding the acquisition times of the device values with the device values and temporarily records them in chronological order, and when a predetermined storage condition is satisfied, stores time-series data regarding the temporarily recorded device values of the plurality of devices in a storage memory , and a programmable display connected to the programmable logic controller. The programmable logic controller includes a program execution unit that repeatedly executes a user program, a device unit having devices that are storage areas referenced by the program execution unit, a temporary recording unit that collects device values of the devices stored in the device unit and temporarily records them in chronological order, associating information regarding the acquisition times of the device values with the device values, and a storage memory for storing the time-series data regarding the device values temporarily recorded in the temporary recording unit as driving record data when a predetermined storage condition is satisfied. The programmable display device includes a setting memory unit that stores, as a page, a screen on which a plurality of components for monitoring or changing the state of a device of the programmable logic controller are arranged, component settings in which the devices are assigned to each of the components arranged on the screen, page settings for managing the component settings on a page-by-page basis using page identifiers that identify a plurality of different pages, and target device settings for identifying a target device among the plurality of devices for displaying a device waveform in which time-series data stored in the storage memory of the programmable logic controller is shown in a waveform shape based on a user designation, a display data generation unit that generates display data for each page corresponding to the plurality of different page identifiers based on the component settings and page settings stored in the setting memory unit, and a display unit that displays a page corresponding to the page identifier on the display screen based on the display data generated by the display data generation unit, and a touch detection unit that detects a touch operation on the display screen of the display unit. The display data generating unit generates display data for switching from the current page to another page based on the page setting when the touch detection unit detects a first touch operation preset on the display screen, and generates display data for displaying the device waveform of the device specified by the target device setting based on the time series data stored in the programmable logic controller and the target device setting stored in the setting storage unit when the touch detection unit detects a second touch operation preset on the display screen, and the display unit displays the other page or the device waveform on the display screen based on the display data generated by the display data generating unit. With the above configuration, it is possible to selectively execute an operation of switching to a different page and an operation of displaying the device waveform of the time series data stored in the programmable logic controller by a touch operation on the programmable display. In particular, since the device waveform can be confirmed on the display screen of the programmable display, information for quickly solving a problem occurring at the FA site can be easily obtained on site.

Furthermore, in the programmable logic controller system according to the eighteenth aspect of the present invention, in addition to the above configuration, the component settings stored in the setting storage unit further include settings for a waveform display component for displaying the device waveform, and the second touch operation is a touch operation on the waveform display component arranged on the first page displayed on the display screen.

Furthermore, in a programmable logic controller system according to a nineteenth aspect of the present invention, in addition to any of the configurations described above, the second touch operation is a specific operation on a non-placement area on the display screen other than the area on the first page in which the display component is placed.

Furthermore, in the programmable logic controller system according to the twentieth aspect of the present invention, in addition to any of the configurations described above, the specific operation is any of a long press, a flick, a pinch in, and a pinch out on the non-placement area.

Furthermore, in a programmable logic controller system according to a twenty-first aspect of the present invention, in addition to any of the above configurations, the setting storage unit of the programmable display stores an acquisition device setting for identifying an acquisition device that repeatedly acquires the time series data of the device value temporarily recorded by the recording control unit, and the display data generation unit is configured to generate display data for sequentially displaying the device values of the acquisition device based on the time series data of the device value temporarily recorded by the recording control unit when a touch operation on a component for displaying the time series data of the acquisition device identified by the acquisition device setting is detected.

Furthermore, in the programmable logic controller system according to the twenty-second aspect of the present invention, in addition to any of the above configurations, the programmable logic controller further comprises an external interface connected to an external camera and receiving image data from the camera, an image recording unit that temporarily records the image data received from the camera via the external interface, and a camera unit processing unit that collects image data received from the camera via the external interface, associates the image data with information relating to the time the image data was obtained, and temporarily stores the image data in the image recording unit; when the storage condition is satisfied, the storage memory stores the image data temporarily stored in the image recording unit by the camera unit processing unit in association with the driving record data; and the programmable display device acquires the driving record data stored in the storage memory, and displays an image based on the image data included in the driving record data on the display unit based on information relating to the time the driving record data was obtained.

Furthermore, in a programmable logic controller system according to a twenty-third aspect of the present invention, in addition to any of the above configurations, the programmable logic controller is configured to, when the storage condition is satisfied, store in the storage memory the user program that was being executed by the program execution unit at the time the storage condition was met, including the user program in the driving record data so that it is associated with the driving record data, and the programmable display is configured to acquire the driving record data stored in the storage memory, and based on information regarding the acquisition time included in the driving record data, display a device value corresponding to the acquisition time on the user program included in the driving record data on the display unit.

Furthermore, in a programmable logic controller system according to a twenty-fourth aspect of the present invention, in addition to any of the above configurations, the programmable logic controller further includes an event collection unit that collects event data corresponding to a plurality of events that occur in the programmable logic controller or in a controlled device controlled by the programmable logic controller, associates the event data with the occurrence time of the event, and stores the event data in chronological order in the temporary recording unit, and when the storage condition is satisfied, the storage memory stores the event data stored by the event collection unit by including it in the driving record data so that it is associated with the driving record data, and the programmable display is configured to acquire the driving record data stored in the storage memory, and display an event corresponding to the event data included in the driving record data on the display unit based on the occurrence time included in the driving record data.

FIG. 1 is a functional block diagram of a programmable logic controller system. FIG. 13 is a schematic diagram showing an example of a user screen displayed on a programmable display device. FIG. 1 is a functional block diagram of a programmable logic controller system. FIG. 2 is a schematic diagram of a ladder program. FIG. 2 is a functional block diagram of the program creation device. FIG. 2 is a functional block diagram of a PLC. FIG. 13 is a schematic diagram for explaining scanning of a ladder program. FIG. 2 is a functional block diagram of a CPU unit. FIG. 1 is a functional block diagram of a programmable logic controller system equipped with a camera unit. FIG. 2 is a functional block diagram of an extension unit. FIG. 2 is a functional block diagram of a programmable display device. FIG. 13 is a schematic diagram showing a device waveform display screen in a replay mode. FIG. 2 is a schematic diagram showing a page setting screen of the screen data creating device. FIG. 2 is a schematic diagram showing a switch setting screen of the screen data creating device. FIG. 15 is a schematic diagram showing a state in which "replay mode activation" is selected on the switch setting screen of FIG. 14; FIG. 2 is a schematic diagram showing a target device setting screen of the screen data creating device; FIG. 13 is a schematic diagram illustrating an example of a display screen on which a page switching component is arranged. 13 is a schematic diagram showing another example of a display screen on which a page switching component is arranged. FIG. 13 is a schematic diagram showing another example of a display screen on which a page switching component is arranged. FIG. 13 is a schematic diagram showing another example of a display screen on which a page switching component is arranged. FIG. FIG. 2 is a schematic diagram showing a menu screen of a programmable display device. FIG. 2 is a schematic diagram showing an initial screen in a replay mode. FIG. 13 is a schematic diagram showing a state in which a camera and event display screen is selected on the replay mode screen. FIG. 13 is a schematic diagram showing the state in which a viewer display screen is selected on the replay mode screen. FIG. 13 is a schematic diagram showing the state in which a unit display screen is selected on the replay mode screen. FIG. 13 is a schematic diagram showing the state in which a unit display screen is selected on the replay mode screen. FIG. 13 is a schematic diagram showing a state in which a program display screen is selected on the replay mode screen. 10 is a flowchart showing a processing operation of the programmable display device. 28B is a flowchart showing details of step S2804 in the flowchart of FIG. 28A. 28B is a flowchart showing details of step S2809 in the flowchart of FIG. 28A. 28B is a flowchart showing details of step S2810 in the flowchart of FIG. 28A. FIG. 13 is a schematic diagram showing a device waveform display screen in a monitor mode. 10 is a flowchart showing a processing operation when a real-time chart monitor of a programmable display device is set to a monitor mode. FIG. 13 is a schematic diagram showing only the device waveform display screen in replay mode. 13 is a schematic diagram showing how a device waveform to be displayed is changed depending on a storage condition. FIG. 13 is a schematic diagram showing a user interface screen of a screen data creating device that links an alarm when a problem occurs with display data; FIG. 4 is a schematic diagram showing a data structure of screen data of a user screen; FIG. FIG. 4 is a schematic diagram showing a data structure of screen data of a system screen. 11 is a schematic diagram of a data structure in which an RTCMID and a device are linked. FIG. 2 is a functional block diagram of a programmable logic controller. FIG. 4 is a schematic diagram showing how the programmable display displays driving record data. FIG. 4 is a functional block diagram of a display processing unit. FIG. 2 is a diagram illustrating a program display module. 11A and 11B are diagrams illustrating a user interface screen displayed on a programmable display device. FIG. 13 is a diagram illustrating a display module of project data and log data. FIG. 13 is a schematic diagram showing the timing of acquiring device values, a workpiece image, and other images. 11 is a schematic diagram showing the display timing and display duration of log data. FIG. 10 is a flowchart showing a procedure for linking image data with time information. 13 is a flowchart showing a procedure for linking event data with time information. 4 is a flowchart showing a basic processing operation of the programmable display device when performing device monitoring. FIG. 11 is a schematic diagram showing a user screen of a programmable display device according to a second embodiment. FIG. 11 is a schematic diagram showing a user screen of a programmable display device according to a third embodiment. FIG. 13 is a schematic diagram showing a user screen of a programmable display device according to a fourth embodiment. FIG. 13 is a schematic diagram showing a switch setting screen of a screen data creating device for a programmable logic controller system according to a fifth embodiment. FIG. 13 is a schematic diagram showing a modified example of the device waveform display screen in the replay mode.

Hereinafter, an embodiment of the present invention will be described based on the drawings. However, the embodiment shown below is an example for embodying the technical idea of the present invention, and the present invention is not limited to the following. In addition, this specification never specifies the members shown in the claims to the members of the embodiment. In particular, the dimensions, materials, shapes, and relative positions of the components described in the embodiment are not intended to limit the scope of the present invention, and are merely explanatory examples, unless otherwise specified. Note that the size and positional relationship of the members shown in each drawing may be exaggerated to clarify the explanation. Furthermore, in the following explanation, the same name and symbol indicate the same or similar members, and detailed explanation will be omitted as appropriate. Furthermore, each element constituting the present invention may be configured as a form in which multiple elements are composed of the same member and one member serves multiple elements, or conversely, the function of one member can be shared by multiple members.
[Embodiment 1]

FIG. 1 shows a schematic diagram of a programmable logic controller system 1000. The programmable logic controller system 1000 shown in this figure illustrates a system in which an object WK moving along a line is imaged by a camera unit 98, processed by a motor MT, and 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 program creation device 70, and a screen data creation device 60. The programmable logic controller (hereinafter also referred to as "PLC") 1 is connected to the program creation device 70. The program creation device 70 creates and edits user programs such as ladder programs executed by the PLC 1. The programmable display 50 is also connected to the screen data creation device 60. The screen data creation device 60 sets the screen displayed on the programmable display 50, for example, the selection of parts to be placed and the layout for each page displayed on the display screen. The program creation device 70 and the screen data creation device 60 can be realized by dedicated devices or software installed on a general-purpose PC.
[PLC system configuration]

The PLC system includes a PLC 1 that provides overall control of input/output devices installed in a factory or the like, a program creation device 70 that creates a ladder program to operate the PLC 1, a programmable display 50 that monitors and changes the status of the PLC 1 devices, and a screen data creation device 60 that creates screen data to generate display data on the programmable display 50.

The term "device" refers to a storage area in the PLC 1 that is referenced by a ladder program. The device value of a device indicates the input or output state of an input/output device, or the state of an internal relay (auxiliary relay), timer, counter, etc., described in the ladder program.
There are two types of device values: bit type and word type. A bit device stores a 1-bit device value, and a word device stores a 1-word device value.

The PLC 1 is broadly divided into a CPU unit 3 and an expansion unit 4. The expansion unit 4 is a function expansion unit that expands the functions of the CPU unit 3. FIG. 1 shows an I/O unit 4f to which input/output devices including input devices such as sensors and output devices such as alarm lamps are connected, a camera unit 4c to which a camera that takes images of the workpieces moving through the production line at a predetermined timing is connected, and a motion unit 4d to which a motor that drives the production line and robots is connected. The motion unit 4d is also called a positioning unit, and controls the position of the control object called an axis, and generally there is a drive source such as a motor for each axis. The CPU unit 3 collects data from these expansion units 4, executes a ladder program to perform the necessary calculations, and controls each expansion unit 4.

The program creation device 70 can create ladder programs, and edit and modify ladder programs that have already been created. The program creation device 70 can also edit the configuration of one or more expansion units 4 connected to the CPU unit 3, and the operating parameters of the expansion units 4. Note that data including ladder programs and unit configuration information is called project data. The program creation device 70 creates project data based on user operations, converts the created project data into mnemonic code, and transfers the converted ladder program to the CPU unit 3.

The CPU unit 3 converts the ladder program into machine code, and while the PLC 1 is operating, the ladder program consisting of the machine code is repeatedly and periodically executed. Here, while the CPU unit 3 periodically executes the ladder program, it collects device values stored in multiple devices in association with the current time, and temporarily records them in a temporary recording unit 91a such as a ring buffer. When the ring buffer becomes full, the oldest device values are overwritten, so that time-series data of device values for a certain period of time is temporarily stored according to the storage capacity of the ring buffer. Then, when a predetermined storage condition is met, such as a trouble occurring on the production line, the time-series data of the device previously selected as the storage target in the program creation device 70 is automatically stored as log data in the storage memory 36 such as a flash memory or an SD card (see FIG. 6 described later).

At this time, image data collected in time series by the camera unit 4c is stored together with the time series data of the device as log data. In addition, the ladder program executed by the CPU unit 3 when the storage condition is satisfied and the unit configuration information at that time are also stored in association with the log data. In this way, when the predetermined storage condition is satisfied, the log data including the time series data of the device and the time series image data, the ladder program and the unit configuration information are stored in the storage memory 36 in association with each other, for example, by managing them as a file group having a common identifier. This file group is called "driving record data". In this embodiment, the contents of the driving record data can be confirmed not only by the program creation device 70 but also by the programmable display device 50. This will be described in detail later.
[System configuration of the programmable display device 50]

The programmable display 50 is connected to the PLC 1 by a communication cable, and the device values stored in the device of the PLC 1 are transferred to the programmable display 50 via the communication cable. As shown in FIG. 2, various functional parts FP such as lamps and switches are arranged on the display screen of the programmable display 50, and a device is assigned to each functional part FP. In general, a screen on which one or more functional parts FP are arranged is called a page, and multiple pages are managed by different screen IDs. The programmable display 50 displays a page corresponding to a screen ID on the display screen. The screen ID may also be displayed on the display screen. In the example of FIG. 2, a screen ID display field IA is provided in the upper right. The screen ID display field IA may be displayed only when necessary, in addition to being displayed all the time. For example, the screen ID display is called up by right-clicking on an empty area of the display screen. Alternatively, when switching pages by a flick operation, the screen ID may be displayed in a large overlay display on the display screen.

Now, the various components shown in FIG. 2 will be described in more detail. In addition to the various functional components FP described above, various other components are arranged on the screen shown in FIG. 2. The text "1" written in the "Screen ID Display Column 1A" described above and the text "Monitoring Screen" in the upper left corner are so-called text components TX. Generally, devices are not assigned to text components TX.

Below the "Monitoring screen" text component TX1 is placed a text component TX2 called "Production product number," and below that is placed a character display component CP as a numeric display field 241. 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 below) is assigned to the character display component CP, and a character or string of characters specified by that device is displayed on the character display component CP. In the example of FIG. 2, the string "ABC-123" is displayed as the character display component CP in the numeric display field 241.

To the right of the "Monitoring Screen" text component TX1 are lamp components RP (one of the functional components FP) that indicate "normal" and "abnormal," and each lamp component RP is assigned a specific device. Depending on the device value of the device, a component image indicating a lit state or an off state is displayed. In Figure 2, the lamp component RP1 indicating "normal" displays a component image indicating a lit state, and the lamp component RP2 indicating "abnormal" displays a component image indicating an off state.

A meter part MP consisting of a "temperature meter" is placed to the right of the lamp part RP. A specific device is also assigned to the meter part MP. The position of the pointer of the meter part MP changes dynamically depending on the device value of that device. Figure 2 shows the state when the device value is 60.

In the center of Figure 2, a text component TX3 with the title "Counter Set Value Current Value Reset Counter Graph" is placed. Below it are text components TX4, TX5, TX6, and TX7 with the titles "Product A", "Product B", "Product C", and "Product D", and to the right of them are numeric display components NP that show the set value and current value for each product. Specific devices are assigned to the numeric display components NP, and the device values of those devices are displayed on the numeric display components NP. In the example of Figure 2, numeric display components NP with the titles "100" and "80" for product A, "100" and "10" for product B, "100" and "100" for product C, and "100" and "80" for product D are placed in correspondence with each other.

To the right of the numeric display component NP, a switch component SP with "RESET" written on it is placed as a RESET switch 246. A specific device is also assigned to the switch component SP. The switch is switched ON or OFF depending on the device value of that device. In FIG. 2, by touching the RESET switch 246, the state of the specific assigned device can be changed (for example, from 1 to 0). This allows the current value of each product to be reset to 0 (i.e., the device value of the device assigned to the numeric display component NP can be rewritten to 0).

To the right of the switch part SP of the RESET switch 246 is placed a graph part GP that shows a counter graph. A specific device is also assigned to the graph part GP. The state of the bar graph changes dynamically depending on the device value of that device. In FIG. 2, the length of the bar changes depending on the current value of each product (in other words, the device assigned to the numeric display part NP that shows the current value is the same as the device assigned to the graph part GP that shows the counter graph).

In this way, there are a wide variety of components arranged on a screen (page) identified by a screen ID, including components with devices assigned, components with no devices assigned, components with component images assigned, and components with no component images assigned. The data structure of a screen will be described in detail later.

The programmable display 50 also detects touch operations by the user using a touch panel provided on the display screen. When the user touches any functional part FP, the state of the device assigned to that functional part FP can be changed. For example, when the user touches a switch functional part, the ON/OFF state of the device assigned to that switch can be changed, thereby realizing the function of the switch. The detection of the user's touch is performed by a touch detection unit 53 shown in FIG. 11, which will be described later.
(PLC1)

First, the configuration of the PLC 1 will be described. The PLC 1 shown in FIG. 1 is configured by connecting a plurality of units. The plurality of units are connected to each other so as to be able to communicate with each other via an inter-unit bus 90. The units are roughly divided into a CPU unit 3 and an expansion unit 4. The CPU unit 3 is also called a main unit or a basic unit, and performs the basic operation of the PLC 1. The expansion unit 4 is a function expansion unit that expands the function of the CPU unit 3. In the example of FIG. 1, the expansion unit 4 includes 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 the expansion unit 4, is connected to a camera unit 98, and captures an image of an object WK at a predetermined timing and sends it to the CPU unit 3. The motion unit 4d is also called a positioning unit, and controls the position of a control object called an axis. Generally, a driving source such as a motor exists for each axis. The communication unit 4e is provided with a communication unit processing unit 41e, and communicates with an external device. The I/O unit 4f is provided with an I/O unit processing unit 41f, and is connected to an input/output device SS such as a sensor. The CPU unit 3 also collects data from these expansion units 4 and performs the necessary control.
(System configuration of PLC system)

Here, to allow those skilled in the art to better understand PLC1, we will explain the general configuration of PLC1 and its operation.

An example of the configuration of a programmable logic controller system according to an embodiment of the present invention is shown in FIG. 3. As shown in this figure, the programmable logic controller system includes a PC 2 for editing user programs such as ladder programs, and a PLC 1 for overall control of various control devices installed in a factory or the like. PC is an abbreviation for personal computer. User programs may be created using a graphical programming language such as a ladder language or a motion program in a flow chart format such as SFC (Sequential Function Chart), or may be created using a high-level programming language such as C language. In the following, for convenience of explanation, the user program will be described as a ladder program, but the present invention does not limit the user program to a ladder program.

The PLC 1 includes a CPU unit 3 with a built-in CPU, and one or more expansion units 4. One or more expansion units 4 are detachable from the CPU unit 3. For example, the expansion unit 4a may be a positioning unit that drives a motor (field device 10a) to position 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 pulsar. The letters a, b, c, etc. added to the end of the reference numbers may be omitted. A system including the PLC 1 and PC 2 may be called a programmable logic controller system.

The CPU unit 3 is equipped with a PLC side display unit 5 and a PLC side operation unit 6. The PLC side display unit 5 can display the operating status of each expansion unit 4 attached to the CPU unit 3. The PLC side display unit 5 switches the display content depending on the operation content of the PLC side operation unit 6. The PLC side operation unit 6 may be a button or the like integrated into the CPU unit 3, or it may be an input device such as an external console, mouse, or keyboard. Alternatively, the PLC side display unit 5 can be a touch panel that also functions as the operation unit.

The PLC side display unit 5 normally displays the current values (device values) of devices within the PLC 1, error information that has occurred within the PLC 1, etc. A device is the name given to an area in memory provided to store device values (device data), and is also called a device memory. A device value is information that indicates the input status from an input device, the output status to an output device, and the status of internal relays (auxiliary relays), timers, counters, data memories, etc. that are set in a user program. Device values are classified into bit and word types. A bit device stores a 1-bit device value. A word device stores a 1-word device value.

The expansion units 4 are provided to expand the functions of the PLC 1. A field device (controlled device) 10 corresponding to the function of the expansion unit 4 is connected to each expansion unit 4, and each field device 10 is connected to the CPU unit 3 via the expansion unit 4. The field device 10 may be an input device such as a sensor or a camera unit, or an output device such as an actuator. In addition, a plurality of field devices 10 may be connected to one expansion unit 4.
(Programming device 70)

PC2 realizes the program creation device 70. The program creation device 70 is a device that connects to the PLC1 to set it, control it during operation, check its operation, etc. In addition, it can create various programs that operate the PLC1 and the programmable logic controller system including the PLC1, and edit and modify programs that have already been created. In this sense, the program creation device 70 is also called a program creation support device or a programmable logic controller engineering tool. Furthermore, the program creation device 70 can reproduce the operating status of each device at that time based on operation record data that records the operation of the programmable logic controller system in the past. The operation record data includes user programs such as ladder programs, project data including setting data such as unit configuration information of each unit, and log data that is operation data such as device values of each device at the time of operation and image data of the camera unit. This program creation device 70 can also read and edit the project data out of the operation record data. In this sense, the program creation device 70 is also called a project data editing program.

The PC2 is, for example, a portable notebook or tablet type personal computer, and includes a display unit 7 and a PC side operation unit 8. A ladder program, which is an example of a user program for controlling the PLC1, is created using the PC2. The created ladder program is converted into a mnemonic code in the PC2. The PC2 is connected to the CPU unit 3 of the PLC1 via a communication cable 9 such as a USB (Universal Serial Bus), and sends the ladder program converted into the mnemonic code to the CPU unit 3. The CPU unit 3 converts the ladder program into machine code and stores it in a memory provided in the CPU unit 3. Note that, although the mnemonic code is sent to the CPU unit 3 here, the present invention is not limited to this. For example, the PC2 may convert the mnemonic code into an intermediate code and send the intermediate code to the CPU unit 3.

The PC-side operation unit 8 of the PC 2 may include a pointing device such as a mouse connected to the PC 2. The PC 2 may be configured to be detachably connected to the CPU unit 3 of the PLC 1 via a communication cable 9 other than a USB. The PC 2 may also be connected to the PLC 1 wirelessly without a physical cable such as the communication cable 9.
(Ladder Program)

Figure 4 shows an example of a ladder diagram Ld displayed on the display unit 7 of the PC 2 when creating a ladder program. The PC 2 displays a number of cells arranged in a matrix on the display unit 7. A virtual device symbol is placed in each cell. The symbols indicate input relays, output relays, etc. A relay circuit is formed by such a number of symbols. The ladder diagram Ld has, for example, 10 columns x N rows (N is any natural number) of cells arranged. Then, virtual device symbols are appropriately placed within the cells of each row.

The relay circuit shown in Figure 4 is constructed by appropriately combining symbols of three virtual devices (hereafter referred to as "input devices") that are turned ON/OFF based on input signals from an input device, and symbols of virtual devices (hereafter referred to as "output devices") that are turned ON/OFF to control the operation of an output device.

The characters displayed above each input device symbol ("R0001", "R0002", and "R0003") represent the device name (address name) of that input device. The characters displayed below each input device symbol ("Flag 1", "Flag 2", and "Flag 3") represent the device comment associated with that input device. The characters displayed above the output device symbol ("Return to origin") are a label consisting of a string of characters that represent the function of that output device.

In the example shown in Fig. 4, two input device symbols corresponding to device names "R0001" and "R0002" are connected in series to form an AND circuit. An input device symbol corresponding to device name "R0003" is connected in parallel to the AND circuit consisting of these two input device symbols to form an OR circuit. That is, in this relay circuit, the output device corresponding to the symbol in the first row is turned ON only when both input devices corresponding to the two symbols in the first row are turned ON, or when the input device corresponding to the symbol in the second row is turned ON.
(Programming device 70)

A block diagram of the PC 2 that realizes the program creation device 70 is shown in FIG. 5. As shown in this figure, the PC 2 includes a PC memory unit 11, a PC CPU 21, a display unit 7, a PC operation unit 8, a PC storage device 22, and a PC communication unit 23. The display unit 7, the PC operation unit 8, the PC storage device 22, and the PC communication unit 23 are each electrically connected to the PC CPU 21.

The PC-side memory unit 11 is a working memory that serves as a working space for the PC-side CPU 21 to execute processes, and is typically composed of a RAM or the like. The driving record data includes project data.

The PC side storage device 22 includes a hard disk, semiconductor memory, ROM, etc., and may further include a removable memory card. CPU is an abbreviation for central processing unit. ROM is an abbreviation for read-only memory. RAM is an abbreviation for random access memory.

The user causes the PC CPU 21 to execute editing software, which is a computer program stored in the PC storage device 22, and edits the project data through the PC operation unit 8. This editing software corresponds to a project data editing program executed by the PC 2.
(Project Data)

The project data includes one or more user programs (e.g., ladder programs) and unit configuration information for the CPU unit 3 and the expansion unit 4. The project data may also include program configuration information indicating what program components the user program is made up of. Furthermore, the unit configuration information is information indicating the connection positions of the multiple expansion units 4 relative to the CPU unit 3, the functions provided in the CPU unit 3 (e.g., communication functions and positioning functions), the functions of the expansion units 4 (e.g., photography functions), etc.

Here, editing of project data includes creating and changing project data. Project data created using the project data editing program is stored in the PC side storage device 22. Furthermore, the user can read out project data stored in the PC side storage device 22 as necessary, and change the project data using the project data editing program. The PC side communication unit 23 is for communicatively connecting the PC 2 to the CPU unit 3 via the communication cable 9. The PC side CPU 21 transfers the project data to the CPU unit 3 via the PC side communication unit 23.

The project data editing program has an edit mode, a monitor mode, and a history playback mode. The edit mode is also called an edit mode, and allows editing of project data. The monitor mode allows simulation operations for debugging and the like when creating a user program, and real-time display of device waveforms showing changes in device values of controlled devices during operation of the FA system. The history playback mode is also called a replay mode or time machine playback, and allows playback display. Switching between the edit mode, monitor mode, and history playback mode is performed by a mode switching unit.
(PLC1)

A functional block diagram of the PLC 1 is shown in Fig. 6. As shown in this diagram, the CPU unit 3 includes a CPU unit processing unit 31, a PLC side display unit 5, a PLC side operation unit 6, a CPU unit storage unit 32, and a PLC side communication unit 33. The PLC side display unit 5, the PLC side operation unit 6, the CPU unit storage unit 32, and the PLC side communication unit 33 are each electrically connected to the CPU unit processing unit 31.
(CPU unit storage section 32)

The CPU unit memory section 32 includes a project memory section 35, a PLC side device section 34, a temporary recording section 91a, and a storage memory 36.

The project memory unit 35 stores project data input from the PC 2. The CPU unit memory unit 32 also stores the control program for the CPU unit 3.

The PLC side device section 34 has bit devices, word devices, etc., and each device stores a device value. This PLC side device section 34 functions as a device memory that stores each device value of multiple devices. It may also function as a storage area that is referenced according to a user program.

The temporary recording unit 91a records the device values stored in the PLC side device unit 34 in chronological order. This temporary recording unit 91a can be configured with a ring buffer or the like.

The storage memory 36 stores the device values recorded in chronological order in the temporary recording unit 91a. The storage memory 36 is composed of non-volatile memory such as an internal memory 37 or a removable memory card 36A.

In this way, the CPU unit storage section 32 has a plurality of storage areas. The CPU unit storage section 32 may include a RAM, a ROM, a memory card, etc. For example, in the example of Fig. 6, the storage memory 36 is configured by a removable memory card 36A called an SD card (product name).
(CPU unit processing section 31)

The CPU unit processing unit 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 a user program. The PLC side device unit 34, which is a storage area referenced by the program execution unit 40 according to the user program, stores the device values of multiple devices.

The storage condition setting unit 45 is a member for setting various conditions. Here, the storage condition setting unit 45 sets a first trigger condition for a recording trigger for recording in the temporary recording unit 91a, a second trigger condition for a storage trigger for storing in the storage memory 36, and a buffer recording period indicating a period during which temporary recording is performed in the temporary recording unit 91a, the period including at least one of the period up to the reference time and the period from the reference time, with the time indicated by the recording trigger as the reference time.

In the storage condition setting unit 45, a condition regarding a recording start trigger for starting recording in the temporary recording unit 91a can be set as the first trigger condition. In addition, a period from a reference time indicated by this recording start trigger can be set as the buffer recording period.

When the first trigger condition for the recording trigger is satisfied, the recording control unit 39 records the time-series device values corresponding to the buffer recording period with the time indicated by the recording trigger as the reference time in the temporary recording unit 91a as log data. The recording control unit 39 also holds the recorded log data in the temporary recording unit 91a until the time when the second trigger condition for the storage trigger is satisfied or the time when the first trigger condition for the recording trigger is next satisfied, whichever is earlier. Then, when the first trigger condition for the recording trigger is next satisfied, the recording control unit 39 records the time-series device values corresponding to the buffer recording period with the time indicated by the recording trigger as the reference time in the temporary recording unit 91a as log data.

When the second trigger condition for the save trigger is satisfied, the save control unit 39C saves the log data held in the temporary recording unit 91a by the recording control unit 39 in the save memory 36. Here, when the second trigger condition for the save trigger is satisfied, the save control unit 39C preferably saves the log data held in the temporary recording unit 91a by the recording control unit 39 and corresponding to the immediately preceding recording trigger from the save trigger in the save memory 36. In this way, the save control unit 39C holds the log data recorded during the buffer recording period even after the buffer recording period has elapsed, and when the save trigger is activated, it saves the log data held in association with the recording trigger. However, the log data saved by the recording control unit 39 is not limited to the log data corresponding to the most recent recording trigger, and may be the recording trigger two or three times before.

The event collection unit 92b collects event data corresponding to multiple events that occur in the PLC 1 or a controlled device (field device 10) controlled by the PLC 1, associates the occurrence time of the events with the event data, and stores them in chronological order in the temporary recording unit 91a.

As shown in FIG. 6, the CPU unit 3 and the expansion unit 4 are connected via an inter-unit bus 90, which is a type of expansion bus. The communication function related to the inter-unit bus 90 may be implemented as part of the PLC side communication unit 33. The PLC side communication unit 33 may also have a network communication circuit. The CPU unit processing unit 31 may transmit log data, etc. to the PC 2, a cloud, etc. via the PLC side communication unit 33.

Here, we will provide additional information about the inter-unit bus 90. This inter-unit bus 90 is a bus on which input/output refresh and the like described below are performed. Communication control on the inter-unit bus 90 is achieved by a so-called bus master 38. The bus master may be provided as part of the PLC side communication section 33, or as part of the CPU unit processing section 31. The bus master 38 is a control circuit for controlling communication on the inter-unit bus 90, and upon receiving a communication request from the CPU unit processing section 31, performs communication with the expansion unit 4, such as input/output refresh, which will be described later.

The expansion unit 4 includes an expansion unit processing unit 41 and an expansion unit memory 42. The expansion unit processing unit 41 controls the field device 10 according to an instruction (device value) from the CPU unit 3 stored in the device. The expansion unit processing unit 41 also stores the control result of the field device 10 in a device called a buffer memory. The control result stored in the device is transferred to the CPU unit 3 by input/output refresh. The control result stored in the device is also transferred to the CPU unit 3 according to a read command from the CPU unit 3, even at a timing different from the input/output refresh. The expansion unit memory 42 includes a RAM, a ROM, and the like. In particular, a storage area used as a buffer memory is secured in the RAM. The expansion unit memory 42 may also have a buffer that temporarily holds data (e.g., still image data and video data) acquired by the field device 10.
(CPU unit 3 scan time)

The scan time of the CPU unit 3 is shown in the schematic diagram of FIG. 7. As shown in this diagram, one scan time ST is composed of inter-unit communication 201 for refreshing input and output, program execution 202, and END processing 204. In inter-unit communication 201, the CPU unit 3 transmits output data obtained by executing the ladder program from the CPU unit storage section 32 in the CPU unit 3 to an external device such as the expansion unit 4. Furthermore, the CPU unit 3 takes in input data received from an external device such as the expansion unit 4 into the CPU unit storage section 32 in the CPU unit 3. In other words, the device value stored in the PLC side device section 34 of the CPU unit 3 is reflected in the device of the expansion unit 4 by output refresh. Similarly, the device value stored in the device of the expansion unit 4 is reflected in the device of the CPU unit 3 by input refresh. Similarly, the device value stored in the device of the programmable display 50 (display side device section 56a shown in FIG. 11 described later) is also reflected in the device of the CPU unit 3 by input refresh. In this way, input/output refresh synchronizes the devices in the CPU unit 3 and the expansion unit 4, achieving a so-called mirroring effect.

It is also possible to employ a mechanism for updating device values between units at times other than refresh (inter-unit synchronization). However, the devices in CPU unit 3 are rewritten by CPU unit 3 at any time, and similarly the devices in expansion unit 4 are rewritten by expansion unit 4 at any time. In other words, the devices in CPU unit 3 can be accessed at any time by the device inside CPU unit 3, and similarly the devices in expansion unit 4 can be accessed at any time by the device inside expansion unit 4. Basically, device values are updated and synchronized between the CPU unit 3 and expansion unit 4 at the timing of refresh.

The CPU unit 3 executes (calculates) the program using the updated input data at the timing of program execution 202 shown in FIG. 7. As shown in this figure, in program execution 202, multiple program modules or ladder programs can be executed in sequence according to project data. Note that a program module is one of multiple program components that make up a user program. For example, a program module includes a main ladder program and a sub ladder program. Programs are also sometimes called function blocks, where the programs are divided into blocks according to function. The CPU unit 3 processes data by executing such programs.

The END process 204 also refers to the overall processing related to peripheral services such as data communication with external devices such as the programmable display 50 connected to the PC 2 or the CPU unit 3, and system error checking.

In this way, the PC 2 creates a ladder program in response to user operations and transfers the created ladder program to the PLC 1. The PLC 1 executes input/output refresh, ladder program execution, and END processing as one cycle (one scan) periodically, i.e., cyclically. This allows it to control various output devices (motors, etc.) based on timing signals from various input devices (sensors, etc.). In addition to the scan period, the CPU unit 3 and the expansion unit 4 each have an internal control period. The CPU unit 3 and the expansion unit 4 control the functions of the field device 10, etc. based on the internal control period.
(Logging)

When a user improves or modifies a user program, the device values acquired while the PLC is executing the user program can be useful. Therefore, the PLC acquires pre-specified device values and creates log data. Here, the devices managed by the PLC include not only those used by the user program, but also those not used by the user program. Also, while some devices are useful when improving or modifying a user program, others are not. Since there are generally several thousand devices, it is a big burden for the user to specify the required devices. Therefore, the PC analyzes the user program and extracts the devices used or described in the user program as targets for logging. This reduces the burden on the user.

If all devices managed by a PLC are subject to logging, the scan time will be long. This is because logging is executed as part of a user program or during an I/O refresh. Sometimes, the delay caused by logging can prevent a user program from running as desired. Therefore, the number of devices subject to logging should be kept appropriate.

As mentioned above, a user program may be composed of multiple program parts. In some cases, it may be sufficient for the user to log the devices related to the program part that the user wishes to modify. In addition, the user may wish to exclude specific program parts from the targets for extraction, or add specific program parts to the targets for extraction. Therefore, it would be convenient for the user if they could add or delete devices from the targets for logging on a program part basis.

A detailed functional block diagram of the CPU unit processing unit 31 of the CPU unit 3 is shown in FIG. 8. The same components as those described above are given the same reference numerals, and detailed explanations will be omitted. Here, the CPU unit processing unit 31 stores project data 71 and log setting data 72 received from the PC 2 in the CPU unit memory unit 32. The PLC side device unit 34 of the CPU unit memory unit 32 includes a CPU unit device unit 34a and an extension unit device unit 34b.

The CPU unit processing section 31 shown in FIG. 8 includes a program execution section 40, a unit control section 80b, a detection section 82, a recording section 81, an event collection section 92a, a time management section 83a, and an output section 84. The detection section 82 detects, for example, rewriting of a device value from an external device for any device included in the PLC side device section 34. When a predetermined output condition is met, such as when the execution of a user program is completed or when a storage trigger relay for a memory card is turned ON, the output section 84 writes the project data 71, the log data 73, and the image data to the memory card 36A and the internal memory 37 constituting the storage memory 36. Until the predetermined output condition is met, the log data 73 is recorded in the memory (for example, a ring buffer), and when the capacity is full, the oldest log data 73 is erased and new log data 73 is additionally recorded (recorded in a so-called FIFO format). This memory card 36A is removed from the CPU unit 3 and attached to the mounting section of the PC 2. As a result, the log data 73 is displayed on the display unit 7 of the PC 2. The output unit 84 may transmit the log data 73 to the PC 2 or a cloud via the PLC side communication unit 33.

The program execution unit 40 repeatedly executes the user program as described above. The unit control unit 80b controls the program execution unit 40 and executes input/output refresh with the expansion unit 4. The program execution unit 40 repeatedly executes the user program included in the project data 71 and controls the expansion unit 4 according to the user program. The program execution unit 40 writes device values to output devices held in the CPU unit device section 34a of the PLC side device section 34 and reads device values from input devices held in the CPU unit device section 34a according to the user program.

The recording unit 81 obtains device values from the PLC side device unit 34 (CPU unit device unit 34a or expansion unit device unit 34b) according to the log setting data 72, or obtains device values from the buffer memory of the expansion unit 4, and writes them to the temporary recording unit 91a (e.g., a ring buffer). The recording unit 81 also executes logging processing at a predetermined timing, such as during END processing, as described above. The log data 73 and project data 71 are written to the storage memory 36 (e.g., memory card 36A or internal memory 37).

When a predetermined storage condition, i.e., a collection start condition for collecting data, is satisfied, the event collection unit 92a reads out from the device unit the device value specified by the log setting data 72 among the device values held in the PLC side device unit 34, and acquires time information from the time management unit 83a. The event collection unit 92a associates the device value with the time information and stores them in the temporary recording unit 91a. The event collection unit 92a may also acquire the device value and time information for each collection period (e.g., scan period) specified by the log setting data 72 and store them in the temporary recording unit 91a.

A ring buffer is preferably used for the temporary recording unit 91a. The reason for using a ring buffer is that not all data stored in the ring buffer is saved as log data 73 in the storage memory 36. For example, when a specified storage condition is met, the storage unit 93 may read device values and time information from the temporary recording unit 91a of the ring buffer, create log data 73, and save it in the storage memory 36. Similarly, when a specified storage condition is met, the storage unit 93 may read large amounts of data including many device values and time information from the expansion unit 4, create log data 73, and save it in the storage memory 36.

The storage unit 93 stores the device value and time information and the large-capacity data and time information in association with each other. Here, "associated" storage means that the data is stored in a form that is easy to reproduce on the PC 2, and for example, file management may be performed in which multiple files are associated with each other. To be more specific, in the case where a first subfolder in which device values and time information are stored and a second subfolder in which large-capacity data and time information are stored are placed under a specific folder in the storage memory 36, the path (directory path) to the specific folder becomes a common flag, and using this common flag, it becomes possible to store the files in the first subfolder and the files in the second subfolder in "association." In addition, if there is another folder placed at the same level (directory) as the specific folder described above, the other folder means a data package saved at a different timing. Of course, the other folder also has a subfolder similar to the above. In this way, the storage unit 93 may store the device value and time information and the data (large-capacity data) and time information in multiple files identified by a common flag (predetermined directory path) and save the multiple files. In addition, it is also possible to "associate" and save the data by, for example, using the file name as a common flag and generating files with the same or corresponding file names. In addition, it is also possible to "associate" and save the data by, for example, using time information as a key, associating device values with data (large volume data) and creating a list, and then consolidating this into a single file.

In this embodiment, large-volume data is considered as an example of data from a monitoring device, but it goes without saying that other types of data, such as continuous data such as motion data, communication data, and audio data, may also be used. The transmission unit 94 may transmit the log data 73 to the PC 2, the cloud, etc. When the temporary recording unit 91a of the ring buffer becomes full, the event collection unit 92a overwrites the oldest information stored in the ring buffer with the newest information. Here, a ring buffer is used as an example of a buffer for the temporary recording unit 91a, but this is merely an example. A FIFO type buffer would be sufficient as the buffer. Furthermore, the above-mentioned recording unit 81 and event collection unit 92a may be separate components or may be integrated into a single component.

As described above, the CPU unit 3 and the expansion unit 4 have one or more functions. Various devices are assigned to each function. Therefore, it would be convenient for the user if devices could be added or deleted from the logging targets for each of these functions. For example, if an undesirable event occurs related to the communication function of the CPU unit 3, the user can easily resolve this event by referring to the device value of the device related to the communication function of the CPU unit 3.
(Camera unit 4c)

A camera can be connected to the PLC 1. Therefore, the expansion unit 4 constituting the PLC 1 can include a camera unit 4c to which a camera can be connected. An example of such a PLC 1 is shown in the functional block diagram of FIG. 9. The PLC 1 shown in this figure includes an external interface 97, an image recording unit 520, and a camera unit processing unit 41c. The external interface 97 is connected to an external camera and receives image data input from the camera. The image recording unit temporarily records the image data input from the camera via the external interface 97. The camera unit processing unit 41c further collects image data input from the camera via the external interface 97, associates the image data with information about the time when the image data was acquired, and temporarily stores the image data in the image recording unit.

When the storage conditions are met, the PLC1 stores the image data temporarily stored in the image recording unit by the camera unit processing unit 41c in association with the driving record data. The storage may be, for example, in the storage memory 36 on the CPU unit 3 side, or in the camera setting information storage unit 530 on the camera unit side.

The programmable display 50 acquires the driving record data stored in the storage memory 36 and displays an image based on the image data contained in the driving record data on the display unit based on information about the acquisition time contained in the driving record data.

Here, the function of the expansion unit processing unit 41 of the camera unit 4c, which is an expansion unit 4 having a camera input function, will be described based on the functional block diagram of FIG. 10. The clock of the time management unit 83b is synchronized with the clock of the time management unit 83a of the CPU unit 3 shown in FIG. 8. For example, the time management unit 83a of the CPU unit 3 transmits time information to the time management unit 83b during END processing. The time management unit 83b synchronizes the clock of the time management unit 83b with the clock of the time management unit 83a of the CPU unit 3 based on the received time information. The clock may be realized by a counter that counts time based on the time information. When a predetermined collection condition (for example, a predetermined relay device has been turned ON) is satisfied, the event collection unit 92b outputs a trigger signal, for example, periodically. The time management unit 83b obtains time information when the trigger signal is input from the clock and stores it in the time information buffer 95. The expansion unit memory 42 has a time information buffer 95 and a temporary recording unit 91a. The external interface 97 is an interface for connecting the camera unit 98 to the camera unit 4c. The external interface 97 periodically outputs a trigger signal issued by the event collection unit 92b to the camera unit 98, and outputs image data output by the camera unit 98 to the image receiving unit 96a. Image data is an example of large-capacity data. The external interface 97 is connected to a monitoring device such as the camera unit 98, and is an example of an interface to which data (image data) is input from the monitoring device. The image receiving unit 96a is all or a part of the function executing unit 96 that executes an imaging function involving input of image data from the camera unit 98 via the external interface 97. In this embodiment, the function executing unit 96 (image receiving unit 96a) executes control of the camera unit 98 based on imaging parameters (an example of setting information) such as exposure time, gain, white balance, and contrast. Such imaging parameters are set as desired parameter values in the PC 2, and are sent to the function executing unit 96 via the PLC side communication unit 33 and the CPU unit processing unit 31 of the CPU unit 3 shown in FIG. 6. Therefore, the PLC side communication unit 33 shown in FIG. 6 is an example of another interface that receives setting information from an external setting device such as the PC 2 or a display. The PLC side communication unit 33 also accepts a user program created by the PC 2 as described above. The camera unit 98 captures images in response to a trigger signal and outputs image data. The image receiving unit 96a transfers the image data to the event collecting unit 92b. The event collecting unit 92b associates the time information stored in the time information buffer 95 with the image data output from the image receiving unit 96a and stores them in the ring buffer 91b. When the ring buffer 91b becomes full, the event collecting unit 92b overwrites the oldest information stored in the ring buffer 91b with the newest information. In this embodiment, the event collecting unit 92b automatically and periodically outputs an imaging trigger signal to the camera unit 98, but the present invention is not limited to this. The event collecting unit 92b may output an imaging trigger signal to the camera unit 98 based on, for example, a command from a user program.

The CPU unit 3 communicates with the expansion unit 4 using any of the following: refresh communication, which is executed for each scan; direct communication, which can be executed at any time; and message communication, which is executed on a best-effort basis for events. The storage unit, for example, reads image data and time information from the ring buffer 91b of the expansion unit 4 using direct communication, and adds it to the log data 73. Note that multiple direct communications with priorities may be implemented as direct communications. In this case, the priority of direct communications executed in relation to a user program may be set relatively high, and the priority of direct communications for logging may be set relatively low. This makes it possible to reduce the impact of logging on the execution of user programs.

As mentioned above, FIG. 9 shows a functional block diagram of a programmable logic controller system including a camera unit 4c. In the programmable logic controller system shown in this figure, a PLC 1 is configured with a CPU unit 3, a camera unit 4c, and an expansion unit 4. The CPU unit 3, the camera unit 4c, and the expansion unit 4 are connected via an inter-unit bus 90. The CPU unit 3 is also connected to a PC 2 via a communication line CL. The camera unit 4c is further connected to a camera section 98 via an imaging trigger line. The camera section 98 includes a camera setting recording section 575. Meanwhile, the CPU unit 3 includes a device section. The setting information of the camera section 98 is recorded in the camera setting recording section 575.

9 is connected to the CPU unit 3, which is a basic unit, via an inter-unit bus 90. An imaging trigger line and an image communication line are connected to an external interface 97 that connects the camera unit 4c to a camera section 98. By transmitting an ON/OFF signal that specifies an imaging trigger to the camera section 98 via the imaging trigger line, the synchronization timing in the inter-unit bus 90 can be extended to the camera section 98, and the recording time of the device value and the acquisition time of the camera image data can be precisely synchronized.
(Camera unit 4c)

The camera unit 4c is electrically connected to the CPU unit 3 via the inter-unit bus 90. This camera unit 4c is a unit for connecting a camera section 98 that captures an image of a specific area in response to an imaging trigger from the PLC 1 and generates image data corresponding to the captured specific area. The camera unit 4c shown in FIG. 9 includes an external interface 97, a camera setting information storage section 530, a camera unit processing section 41c, and an image recording section 520.

The camera setting information storage unit 530 stores setting information for the camera unit 98, including the imaging trigger conditions. The setting information for the camera unit 98 stored in the camera setting information storage unit 530 includes setting information created by the program creation device 70 and received via the CPU unit 3. The user program executed by the CPU unit 3 is created by the program creation device 70 connected to the CPU unit 3.

The camera unit processing unit 41c generates an ON/OFF signal that defines an imaging trigger based on the setting information of the camera unit 98 stored in the camera setting information storage unit 530, and processes the image data generated by the camera unit 98 using this ON/OFF signal as an imaging trigger.

The image recording unit 520 records the image data acquired by the camera unit processing unit 41c. The image recording unit 520 also records the image data acquired by the camera unit processing unit 41c in chronological order, associating it with information about the time when the image data was acquired. Furthermore, the image recording unit 520 transmits the image data and information about the time to the CPU unit 3 in response to an instruction from the CPU unit 3.

The external interface 97 is provided between the camera unit processing section 41c and the camera section 98. This external interface 97 includes an imaging trigger line and an image communication line.

The imaging trigger line is generated by the camera unit processing unit 41c and is an interface for sending to the camera unit 98 an ON/OFF signal that specifies an imaging trigger that causes the camera unit 98 to perform imaging. This imaging trigger line is preferably a non-communication line. This allows the imaging trigger to be instructed by ON/OFF I/O rather than communication, achieving extremely fast imaging trigger instruction compared to sending an imaging command via communication.

The camera connection cable 550 that connects the external interface 97 and the camera section 98 bundles the image communication line 502 and the imaging trigger line 501. As a result, all electrical signal exchange that operates the camera section 98 can be realized simply by connecting the camera unit 4c and the camera section 98 to the external interface 97, simplifying the wiring and simplifying the configuration.

The camera setting information storage unit 530 stores the setting information of the camera unit 98 received from the CPU unit 3 via the inter-unit bus 90. The setting information of the camera unit includes various information such as the frame rate at the time of image capture, image quality, rotation, exposure, gain, exposure time, white balance, contrast, gamma, sharpness, and anti-flicker. The camera unit processing unit 41c is connected to the CPU unit 3 and the expansion unit 4 via the inter-unit bus 90. The camera unit processing unit 41c acquires image data from the camera unit 98 via the external interface 97 based on the setting information of the camera unit 98 stored in the camera setting information storage unit 530. The image recording unit 520 collects image data acquired by the camera unit 98, and records the image data in association with information on the time when the image data was acquired. This configuration makes it possible to synchronize the device record related to the image data captured by the camera unit 98 with the time with high accuracy. In particular, by sending the image capture trigger that instructs image capture as an ON/OFF signal on the dedicated image capture trigger line without going through a communication line or command interpretation, high-precision time synchronization that avoids time delay can be realized.
(Data in chronological order)

Here, a configuration will be described in which device values are stored as time-series data and displayed as device waveforms on the programmable display 50 in the programmable logic controller system shown in FIG. 1. The PLC 1 stores time-series data on the device values of a device, which is a storage area referenced by a user program, based on a predetermined storage condition. As shown in FIG. 6, the PLC 1 includes a CPU unit processing section 31 and a CPU unit storage section. The CPU unit processing section 31 includes a program execution section 40 that repeatedly executes a user program, a recording control section 39, and a storage control section 39C. The CPU unit storage section includes a device section having a device, which is a storage area referenced by the program execution section 40, a temporary recording section 91a, and a storage memory 36. The recording of the temporary recording section 91a is controlled by the recording control section 39. Here, the recording control section 39 collects device values of the devices stored in the device section, associates information on the acquisition time of the device values with the device values, and temporarily records them in the temporary recording section 91a in a chronological order. The storage of the storage memory 36 is controlled by the storage control section 39C. Here, when a predetermined storage condition is satisfied, the storage control unit 39C stores the time-series data relating to the device values temporarily recorded in the temporary recording unit 91a in the storage memory 36 as driving record data.

Meanwhile, the programmable display device 50 connected to this PLC 1 displays a display screen, which has been set in advance by a screen data creation device 60, on the display unit 55. A functional block diagram of the programmable display device 50 connected to the screen data creation device 60 is shown in Fig. 11. As shown in this figure, the screen data creation device 60 can be connected to the programmable display device 50, and various screen data to be displayed on the programmable display device 50 is created using the screen data creation device 60. First, the screen data creation device 60 will be described.
(Screen Data Creation Device 60)

The screen data creation device 60 is realized, for example, by executing a drawing editor program that runs on an information processing terminal such as a personal computer. The user creates multiple pages in which various functional parts FP are arranged in a desired layout. The screen data creation device 60 transfers screen data created for these multiple pages to the programmable display device 50 based on the user's operation input. The programmable display device 50 stores the transferred screen data in a flash memory or the like, and displays a page corresponding to the screen ID based on the user's touch operation. As an example, a page corresponding to screen ID1 is displayed on the display screen of the display unit 55 of the programmable display device 50, and a switching part for switching to a page corresponding to screen ID2 is arranged on that page. In this case, when a touch operation on the switching part is detected by the user, display data for the page corresponding to screen ID2 is generated, and the page corresponding to screen ID2 is displayed based on the generated display data.

Here, as described above, the programmable display 50 according to this embodiment is configured to enable confirmation of the contents of the driving record data stored in the PLC 1. For example, a page corresponding to screen ID 1 is displayed on the display screen of the display unit 55 of the programmable display 50, and a waveform display component is arranged on that page for displaying a device waveform consisting of time-series data of the device included in the driving record data. When the waveform display component is touched by a user, the driving record data is read from the CPU unit 3 of the PLC 1, and display data for displaying the device waveform is generated. Then, based on the generated display data, the device waveform of the device to be displayed is displayed on the system screen.

At this time, the device to be displayed is determined by the target device setting 52c described later. The target device setting 52c is a setting for specifying the device to be displayed as the device waveform. In other words, the types of devices included in the log data of the driving record data are very large, and the types and number of device waveforms to be displayed on the programmable display 50 vary depending on the site where the programmable display 50 is installed. Therefore, in the programmable display 50 according to this embodiment, the device specified in advance by the user using the screen data creation device 60 is stored in the programmable display 50 as the target device setting 52c. As a result, when the waveform display component is touched by the user, the programmable display 50 can display the device waveforms of the optimal type and number of devices according to the site among the driving record data stored in the PLC 1, making it easier to immediately solve problems that occur at the FA site.
(Programmable Display 50)

Next, a description will be given of the programmable display device 50. The programmable display device 50 shown in Fig. 11 includes a setting storage unit 52, a display device processing unit 51, a touch detection unit 53, a display unit 55, a data memory 56, a screen data receiving unit 57, and a display device side communication unit 58.
(Settings storage unit 52)

The setting storage unit 52 is a component for storing various screen data required to generate display data in the programmable display device 50, such as part settings 52a, page settings 52b, target device settings 52c, acquisition device settings 52d, system default screen information 52f, and guidance information 52g. Note that the guidance information 52g is associated with the device specified by the target device settings, and is information for guiding a method of dealing with an error event when a saving condition is met. The setting storage unit 52 that stores the guidance information 52g functions as a guidance information storage unit.

Component settings 52a are settings that assign devices to each of the components arranged on a single screen on which multiple components for monitoring or changing the status of devices in PLC1 are arranged, with this screen being treated as a page. For example, component settings 52a sets the devices assigned to each component arranged on the display screen and the functions executed when each component is touched. Component settings 52a also include component images that show each component. For example, there are an image showing the lit state of a lamp and an image showing the off state of a lamp.

Page settings 52b are settings for managing part settings 52a on a page-by-page basis using a page identifier that identifies multiple different pages. The page identifier is, for example, a screen ID that indicates a page number. Page settings 52b allows a screen on which one or more parts are placed to be treated as a page, and for management on a page-by-page basis using multiple different screen IDs.

The target device setting 52c is a setting for identifying a target device for displaying a device waveform in which the time series data stored in the PLC 1 is shown in a waveform shape. The target device setting 52c selects and sets the target device for displaying the device waveform on the programmable display 50 from among the driving record data.

The acquisition device setting 52d is a setting for specifying the device to acquire as the device waveform to be displayed in the monitor mode of the real-time chart monitor described below. The system default screen information 52f is information related to the system default screen that is prepared in advance.

The display processing unit 51 may be realized by software using a CPU and a program, or by hardware such as an FPGA or ASIC, or by a mixture of both. Of course, the specific configuration for realizing the display processing unit 51 is not important, and may include using multiple CPUs or multiple pieces of hardware. This display processing unit 51 includes a display data generation unit 51a and a driving record data interpretation unit 51b.

The display data generating unit 51a is a component for generating display data for each page corresponding to a plurality of different page identifiers based on the part settings 52a and page settings 52b stored in the setting storage unit 52. The display data generating unit 51a generates display data to be displayed on the display screen of the display unit 55. Here, the touch detection unit 53 detects whether or not the user has performed a touch operation, and if there has been a touch operation, the display content is changed to correspond to the touch operation. Here, the display data generating unit determines whether or not a part (such as a switch part SP) to which a specific function is assigned exists at a position on the display screen designated by the user's touch operation. If a part exists at the touched position, the function corresponding to that part is executed. Specifically, for example, if it is a switch part SP, the state of the device assigned to the switch part SP is changed, and a part image corresponding to the state of the device (such as a part image indicating a switch ON or a part image indicating a switch OFF) is displayed on the display screen.

On the other hand, when there is no touch operation, the display data generating unit 51a generates display data for device monitoring. For example, the display data generating unit 51a generates display data for monitoring the state of the devices of the PLC1 so as to display a page as shown in FIG. 2 during operation of the PLC1. Specifically, the device values of the devices used in the display data are read from the data memory 56 at regular intervals, and new display data is generated by rewriting the contents of the display data. The display unit 55 displays a page corresponding to the newly generated display data on the display screen. The contents of the data memory 56 are mirrored with the device values of the devices of the PLC1 used in the display data by the display side communication unit 58 described later. Therefore, the state of the devices of the PLC1 can be monitored in real time and changed in real time. The basic processing operations during device monitoring will be described later.

The driving record data interpretation unit 51b reads the management information data from the driving record data and determines what is contained in the driving record data (details will be described later).
(Touch detection unit 53)

The touch detection unit 53 is a member for detecting a touch operation on the display screen of the display unit 55. The touch detection unit 53 detects a touch operation on the display screen in a touch panel manner. Types of touch operations include a long tap (long press), a double tap, a flick, a pinch in, a pinch out, and the like.
(Display unit 55)

The display unit 55 has a display screen. Based on the display data generated by the display data generating unit 51a, a page corresponding to a page identifier according to the display data is displayed on the display unit 55. The display unit 55 can be configured, for example, with an LCD or an organic EL having a touch panel function.
(Data Memory 56)

The data memory 56 is a member for storing various settings. Here, it includes a display-side device section 56a that stores device values. The display-side device section 56a stores device values of devices used in the display data among the devices of the PLC 1. The contents are updated as appropriate by a display-side communication section 58, which will be described later.
(Screen data receiving unit 57)

The screen data receiving unit 57 is an interface that receives screen data created and transferred by the screen data creating device 60. The display processing unit 51 stores the screen data received via the screen data receiving unit 57 in the setting storage unit 52.
(Display device communication unit 58)

The display-side communication unit 58 is a communication interface for communicating with an external device, for example, the PLC 1. The display-side communication unit 58 repeats communication with the PLC 1 at a predetermined cycle (for example, 10 ms) and synchronizes (mirrores) the contents of the data memory 56 with the device values of the devices of the PLC 1 used in the display data. For example, if one scan of the ladder program is about 100 μs and the communication cycle between the PLC 1 and the programmable display 50 is 10 ms, the programmable display 50 will read out the devices of the PLC 1 once every 100 scans of the ladder program. The display-side communication unit 58 can also perform protocol conversion, etc., as necessary.
(Display data generating unit 51a)

When the touch detection unit 53 detects a first touch operation on a page switching component 131 arranged on a first page displayed on the display screen, the display data generation unit 51a generates display data for a second page corresponding to the second page identifier based on the page setting 52b.

When the touch detection unit 53 detects a second touch operation that has been set in advance on the display screen, the display data generation unit 51a generates display data for displaying the device waveform of the device specified by the target device setting 52c based on the time series data stored in the PLC 1. The display unit 55 is configured to display the second page or the device waveform on the display screen based on the display data generated by the display data generation unit 51a.

For example, in the device waveform display screen 160 shown in FIG. 12, the device waveforms of pre-set devices are displayed on the display screen. In the example of FIG. 12, devices DM100, DM200, and R000 are displayed as graphs. By turning the checkboxes provided to the left of each device ON/OFF, the corresponding device waveforms can be displayed/hidden.

With this configuration, it is possible to selectively switch between different pages and display the device waveforms of the time series data stored in the PLC 1 by touching the programmable display 50. In particular, since the device waveforms can be confirmed on the display screen of the programmable display 50, it is easy to obtain information to quickly solve problems that occur at the FA site.

The device waveform display screen 160 shown in FIG. 12 is a type of system screen of the programmable display device 50, and therefore, when the "x" button 166 in the upper right of FIG. 12 is touched, the system screen returns to the normal monitoring screen (a screen created by the user in the screen data creation device 60). The device waveform display screen 160 shown in FIG. 12 is realized by overlaying time series data read from the driving record data on a system default screen (a so-called standard default specification screen) prepared in advance by the developer of the programmable display device 50. The data structure of the system screen will be described in detail later.

In the above example, the page is switched by the first touch operation of touching the page switching component, but the present invention does not limit the page switching means to a method using a dedicated page switching component. It goes without saying that the page may be switched by a predetermined touch operation set in advance, such as a flick operation. In this case, the predetermined operation for switching pages is the first touch operation.
(Functional block diagram of the screen data creation device 60)

Next, the screen data creation device 60 will be described. The screen data creation device 60 shown in FIG. 11 includes a screen data creation input unit 63, a screen data creation display unit 65, a screen data creation unit 61, a screen data creation storage unit 62, and a screen data transfer unit 67.

The screen data creation input unit 63 is an input device such as a mouse or a keyboard. A user can operate the screen data creation device 60 via the screen data creation input unit 63 to determine the layout of parts within a page and assign devices to parts.

The screen data creation display unit 65 is a display or the like connected to the screen data creation device 60, and is used to check the screen data.

The screen data creation unit 61 creates screen data including part settings 52a, page settings 52b, and target device settings 52c in accordance with user input via the screen data creation input unit 63. The screen data being edited is displayed on the screen data creation display unit 65 for the user to confirm.

The screen data creation side memory unit 62 stores screen data including part settings 52a, page settings 52b, and target device settings 52c.

The screen data transfer unit 67 reads out the screen data created by the screen data creation unit 61 from the screen data creation side storage unit 62 and transfers it to the programmable display device 50 .
(User interface screen of screen data creating device 60)

Examples of the user interface screen of the screen data creation device 60 are shown in Figures 13 to 16. Figure 13 shows a page setting screen 110 for setting the menu screen and the like. From this page setting screen 110, the user sets the buttons to be arranged on each screen (page) of the programmable display 50 and the functions of each button. On the right side of the page setting screen 110, a screen selection field 111 listing screens that can be set is provided, and on the right side, a screen display field 112 is provided. In the screen selection field 111, the screens that can be set are displayed together with the screen ID, which is the page identifier. The screen selected in the screen selection field 111 is displayed in the screen display field 112. In the example of Figure 13, the menu screen (screen ID is 0001) is shown in a selected state. In addition, a "screen" tab 113 and a "system setting" tab 114 are provided at the bottom of the screen selection field 111. When the "system setting" tab 114 is selected, the screen is switched to the system setting screen 130 of Figure 16. In addition, settings for display components such as switches to be placed in the screen display field 112 are performed from a switch setting screen 120 shown in FIG. 14. When an arbitrary switch is selected in the screen display field 112 of the page setting screen 110 in FIG. 13, or when properties are selected by right-clicking, the screen switches to the switch setting screen 120 shown in FIG. 14.

The switch setting screen 120 shown in FIG. 14 has a switch function selection field 121 for assigning switch functions. Switches that can be assigned include "bit set," "page change," "replay mode start," "real-time chart monitor (replay mode)," and "real-time chart monitor (monitor mode)." Here, the switch function selection field 121 allows the switch function to be selected from a drop-down list. The user selects the desired switch function from multiple candidates displayed in the drop-down list. When a switch function is selected in the switch function selection field 121, the switch setting screen 120 displays setting items corresponding to the selected switch function, as shown in FIG. 15. Here, "replay mode start" is selected in the switch function selection field 121, and accordingly, the initial display screen selection field 122, the driving record data selection field 123, and the real-time chart monitor (replay mode) detailed setting field 124 are displayed.

On the other hand, FIG. 16 shows the system setting screen 130. This system setting screen 130 displays a target device setting screen 220 for setting the target device for the device waveform to be displayed on the real-time chart monitor (in this example, replay mode). Details will be described later.

The screen data thus created by the screen data creating device 60 is transmitted to the programmable display device 50 through the screen data transfer unit 67. When the programmable display device 50 receives the screen data at the screen data receiving unit 57, the programmable display device 50 stores the screen data in the setting storage unit 52.
(Part setting 52a)

The component settings 52a stored in the setting storage unit 52 of the programmable display device 50 shown in FIG. 11 include at least any one of the settings of the waveform display component, the setting of the page switching component 131, the setting of the real-time display component, and the setting of the replay display component.
(Waveform display component)

The waveform display component is a display component for displaying a device waveform. Using the screen data creation device 60 of FIG. 11, the user defines a user screen from the screen data creation unit 61 by operating the screen data creation side input unit 63. Here, while displaying the user screen on the screen data creation side display unit 65, display components such as the waveform display component and the page switching component 131 stored in the screen data creation side storage unit 62 are selected, and the waveform display component and the page switching component 131 are arranged at desired positions on the page of the user screen. When the user screen is created in this manner, the screen data transfer unit 67 transfers the screen data to the screen data receiving unit 57 of the programmable display device 50. Based on the transferred screen data, the programmable display device 50 acquires information required for screen display, for example, a device value specified in the target device setting 52c, from the PLC 1 side via the display side communication unit 58, generates display data in the display data generation unit 51a of the display processing unit 51, and displays the data on the display unit 55. Then, the touch detection unit 53 detects that the user has touched a display component displayed on the display screen of the display unit 55, and the corresponding process is performed by the display processing unit 51. For example, when a touch operation is performed on the waveform display component, the device waveform display screen 120 in FIG.
(Page switching component 131)

The page switching component 131 is a component that is placed on a first page corresponding to an arbitrary first page identifier among a plurality of different page identifiers on the display screen, and is used to switch to a second page corresponding to a second page identifier that is different from the first page identifier.

Examples of user screens on which a page switching component 131 is arranged are shown in Figs. 17 to 20. In the example of a user screen 130A shown in Fig. 17, the page switching component 131 is a button 132 labeled "next page." By pressing this "next page" button 132 displayed on the display screen, the user can switch the display contents on the display screen to a specified page (for example, the page next to the currently displayed page by incrementing). In the example of a user screen 130B shown in Fig. 18, two buttons 133 and 134 labeled "→" and "←" are arranged as the page switching component 131. By pressing the "→" button 133, the display contents can be switched to the corresponding page with an increased page number, and by pressing the "←" button 134, the display contents can be switched to the corresponding page with a decreased page number. In the example of a user screen 130C shown in Fig. 19, the page switching component 131 has "△" and "▽" buttons 135 and 136 and a page number display field 137. When the user presses the "△" button 135, the page number displayed in the current page number display field 137 can be increased, and when the user presses the "▽" button 136, the page number displayed in the current page number display field 137 can be decreased. Furthermore, the page can be switched at the timing when the "△" button 135 or the "▽" button 136 is pressed to increase or decrease the page number, or a "move" button 138 can be provided separately from the "△" and "▽" buttons 135 and 136, and the user can move to a desired page by pressing the "move" button 138 in a state where a desired page number is displayed in the page number display field 137 by using the "△" and "▽" buttons 135 and 136. Furthermore, in the example of the user screen 130D shown in FIG. 20, thumbnail screens 139 of each page are displayed as the page switching component 131, and the user can switch the display content to the desired page by pressing the thumbnail screen 139 corresponding to the desired page.
(User interface screen of programmable display device 50)

Examples of user interface screens of the programmable display device 50 are shown in Figures 12, 21 to 27. In these figures, Figure 21 shows the menu screen 140 of the programmable display device 50, Figure 22 shows the initial screen 150 of the replay mode displayed when the "Replay mode start" button 141 is touched on the menu screen 140 of Figure 21, Figure 12 shows the device waveform display screen 160 displayed when the "Real-time chart monitor" tab 161 is selected in the replay mode, Figure 23 shows the camera event display screen 170 displayed when the "Camera event" tab 162 is selected, Figure 24 shows the viewer display screen 180 displayed when the "Viewer" tab 163 is selected, Figure 25 shows the unit display screen 190 displayed when the "Unit" tab 164 is selected, Figure 26 shows the unit display screen 190B displayed when the "Details" button 191 is touched on the unit display screen 190 of Figure 25, and Figure 27 shows the program display screen 200 displayed when the "Program" tab 165 is selected. User screens such as the "Maintenance screen" that are displayed when the "Viewer" tab 163 shown in FIG. 24 is touched are created by the user using the program creation device 70.

The camera/event display screen 170 shown in FIG. 23 is an example of a system screen in this embodiment, and similar to the device waveform display screen 160 described above, camera images read from the driving record data and events associated with the occurrence time are superimposed and displayed on the system default screen. This camera/event display screen 170 has a camera image display field 172 on the right side of the screen. The event/error history field 171 lists each event included in the driving record data together with the event content and the date and time of occurrence. In the example of FIG. 23, of the event group EV listed in the event/error history field 171, the row for "mode switching (PROG>RUN)" is highlighted. This indicates that the focus is on the time when the "mode switching (PROG>RUN)" event occurred.

At this time, the camera image displayed in the camera image display field 172 on the left side is the camera image captured closest to the time the event occurred, extracted from the driving record data and displayed. Furthermore, below the camera image display field 172, image information IX is displayed, such as the date and time the displayed camera image was captured and the number of images captured.

The time display area 409 also displays "20XX/4/20 11:26:23," which is synchronized with the time when the above-mentioned "Mode Switch (PROG>RUN)" event occurred. In other words, the time when the event that was touched in the event/error history column 171 occurred is displayed in the time display area 409.

Here, if any event other than "Mode switching (PROG>RUN)" is touched in the event error history field 171, the event is highlighted. Accordingly, the time when the event occurred is displayed in the time display area 409. In addition, the camera image displayed in the camera image display field 172 also switches. Specifically, it switches to the camera image captured closest to the time when the event occurred.

A time designation cursor 404 that can be moved left and right like a slider is displayed to the right of the time display area 409. The time designation cursor 404 indicates "20XX/4/20 11:26:23" displayed in the time display area 409. When the time designation cursor 404 is moved left and right, the camera image changes in response to this operation, and at the same time, the highlighted portion of the event/error history column 171 also changes.

In this way, the switching of camera images, the switching of highlighted events, and the position of the time designation cursor are all linked (synchronized) with one another. The user can change the reference time for the linked display by using the slider operation of the time designation cursor 404 left and right, or by touching a specific event in the event/error history column 171. Details of the linked display will be described later.

The viewer display screen 180 shown in FIG. 24 is an example of a system screen in this embodiment, and like the device waveform display screen 160 described above, the device values read from the driving record data are superimposed and displayed on the system default screen. In the viewer display screen 180, a "maintenance screen" drawn by the user in the screen data creation device 60 is incorporated into the system default screen. As described in detail with reference to FIG. 2, text components TX such as "maintenance screen" and "replay in progress" are arranged on the maintenance screen. In addition, character display components CP such as "general", "AD conversion data", "special data", "offset value", "analog data", "disconnection detection", "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. Numeric display components NP (displaying 12345, 3452, etc.) or character display components CP (displaying ON or OFF) are arranged corresponding to some character display components CP.

In addition, in the viewer display screen 180 shown in FIG. 24, the position of the time specification cursor 404 and the device value displayed by the numeric display component NP are linked. In other words, by moving the time specification cursor 404 left or right, the display content of the numeric display component NP or the text display component CP can be changed. For example, in FIG. 24, "20XX/4/20 11:26:23" is displayed in the time display area 409, so the numeric display component NP or the text display component CP displays the device value at "20XX/4/20 11:26:23".

Furthermore, the viewer display screen 180 shown in FIG. 24 is linked (synchronized) with the camera/event display screen 170 shown in FIG. 23 described above. As described above, the time display area 409 of the camera/event display screen 170 shown in FIG. 23 displays "20XX/4/20 11:26:23". When the user touches the "Viewer" tab 163 in this state, the time display area 409 displays "20XX/4/20 11:26:23", and the viewer display screen 180 (FIG. 24) is displayed with the device value corresponding to this time displayed in the numeric display component NP or text display component CP.

The "Waveform Check" button 181 in FIG. 24 is a so-called switch part SP, and when the user touches it, a real-time chart monitor (replay mode) is displayed that displays the device being used on the "Maintenance screen" shown in FIG. 24.

The unit display screen 190 shown in FIG. 25 is an example of a system screen in this embodiment, and like the device waveform display screen 160 described above, the unit configuration read from the driving record data is superimposed and displayed on the system default screen. The "Details" button 191 and the "Confirm Waveform" button 181 are also built into the system default screen in advance (they are not drawn by the user) and are displayed according to the number of unit configurations. In FIG. 25, it is assumed that the unit configuration UL included in the driving record data includes four units: "CPU unit", "I/O unit", "camera unit", and "motion unit". Therefore, four sets of the "Details" button 191 and the "Confirm Waveform" button 181 are also displayed. For example, when the "Details" button 191 corresponding to the "motion unit" is touched, the unit display screen shown in FIG. 26 is displayed.

The unit display screen 190B shown in FIG. 26 is an example of a system screen in this embodiment, and similar to the device waveform display screen 160 described above, the buffer memory (UG), which is a device in the motion unit read from the driving record data, and its device values are displayed on the system default screen. In FIG. 26, "current coordinate", "command coordinate", "current speed", "command speed", and "feedback torque" are displayed as examples of UG, and the device values are displayed to the right of each UG.

The time display area 409 in FIG. 26 displays "20XX/4/20 11:26:23", which is the same time as in FIG. 23 to FIG. 25 described above. In other words, the time shown on the unit display screen 190B in FIG. 26 is linked (synchronized) with the time shown on the camera/event display screen 170 in FIG. 23 described above and the time shown on the viewer display screen 180 in FIG. 24. In addition, when the time designation cursor 404 in FIG. 26 is operated left or right as a slider, the time is specified by the position of the time designation cursor 404 after the slider operation, and the device value at the specified time is displayed. In other words, in response to the slider operation of the time designation cursor 404, the device value corresponding to the position of the time designation cursor 404 is read from the driving record data and displayed.

When the "Waveform Check" button 181 shown in FIG. 26 is touched, a real-time chart monitor (replay mode) is displayed that displays the device being used on the unit display screen 190B shown in FIG. 26.

The program display screen 200 shown in FIG. 27 is an example of a system screen in this embodiment, and similar to the device waveform display screen 160 described above, the unit configuration and ladder program read from the operation record data are superimposed and displayed on the system default screen. In FIG. 27, a unit configuration display field 207 is provided on the left side, and a ladder program display field 208 is provided on the right side.

The time display area 409 in Fig. 27 displays "20XX/4/20 11:26:23", which is the same time as Figs. 23 to 26 described above. That is, the time shown on the program display screen 200 in Fig. 27 is linked (synchronized) with the time shown on the camera/event display screen 170 in Fig. 23 described above, the time shown on the viewer display screen 180 in Fig. 24, and the unit display screens 190 and 190B in Figs. 25 and 26. Also, when the time designation cursor 404 shown in Fig. 27 is operated left or right as a slider, the time is specified by the position of the time designation cursor 404 after the slider operation, and the device value at the specified time is superimposed on the ladder program displayed in the ladder program display field 208. That is, in response to the slider operation of the time designation cursor 404, the device value corresponding to the position of the time designation cursor 404 is read from the driving record data and superimposed on the ladder program.
(Processing Operation of Programmable Display Device 50)

Here, the processing operation for displaying the device waveform in the replay mode of FIG. 12 on the programmable display 50 will be described based on the flowchart of FIG. 28A. First, in step S2801, a touch operation by the user is accepted. Next, in step S2802, it is determined whether or not this touch operation is a touch operation on a waveform display component. If it is not a touch operation on the waveform display component, the process proceeds to step S2803, where it is determined whether or not it is a touch operation on a switch component. If it is not a touch operation on any other component, the process ends without performing any processing. On the other hand, if it is a touch operation on any other component in step S2803, the process proceeds to step S2804, where a function corresponding to the touched component is executed, and the process ends.

On the other hand, if it is determined in step S2802 that the touch operation is on the waveform display component, the process proceeds to step S2806, where the selection of driving record data is accepted. Here, the user is prompted to select which driving record data waveform to display. Then, when any driving record data is selected, the corresponding driving record data is read in step S2807. More specifically, the display data generation unit 51a of the programmable display 50 acquires the driving record data from the driving record data stored in the storage memory of the PLC 1, or from the driving record data previously stored in the data memory 56 of the programmable display 50.

Further, in step S2808, a device to be displayed is specified, and further in step S2809, display data is generated by the display data generating section 51a. Finally, in step S2810, the device waveform is displayed on the display section 55, and the process ends.
(Perform functions according to parts)

Here, the details of step S2804 shown in FIG. 28A will be described based on the flowchart in FIG. 28B. The "execution of function according to part" performed in FIG. 28B is executed when the user touches the switch part in step S2803 in FIG. 28A. There are two types of functions for switch parts. One is the bit set function described above with reference to FIG. 2. The other is the page switching function. A switch part with the bit set function is assigned a specific device, while a switch part with the page switching function is assigned a specific page (screen ID). For example, the RESET switch 246 shown in FIG. 2 has a bit set function and is assigned a specific device. Also, the page switching part 131 shown in FIG. 17 has a page switching function and is assigned a page number (screen ID) of the switching destination (jump destination).

In FIG. 28B, first, in step S2804-1, it is determined whether the function of the switch part is a bit set function. If it is a bit set function, the process proceeds to step S2804-2, where the device value of the device assigned to the switch part is rewritten (1 to 0, etc.) in response to the touch operation. On the other hand, if it is not a bit set function, the process proceeds to step S2804-3, where it is determined whether the function of the switch part is a page switching function. If it is a page switching function, in step S2804-4, page switching is performed to the page number (screen ID) assigned to the switch part in response to the touch operation. On the other hand, if it is not a page switching function, the process returns to the flowchart of FIG. 28A, and the process ends.
(Display data generation)

Details of step S2809 shown in FIG. 28 will be described based on the flowchart in FIG. 28C. In the flowchart in FIG. 28C, display data is generated. First, in step S2809-1, system default screen information 52f for displaying the system default screen is read. This system default screen information 52f is created by the developer of the programmable display device 50, and is stored in the setting storage unit 52 shown in FIG. 11. The display data generation unit 51a of the programmable display device 50 reads the system default screen information 52f from the setting storage unit 52.

Next, in S2809-2, time series data of device values is extracted from the driving record data. More specifically, the display data generating unit 51a of the programmable display device 50 extracts time series data of device values of the device identified in step S2808 from the driving record data acquired in step S2807. Then, in S2809-3, the display data generating unit 51a generates display data in which the time series data is superimposed on the system default screen, based on the read system default screen information 52f and the extracted time series data of the device values.
(Device waveform display)

Furthermore, the details of step S2810 shown in FIG. 28A will be described based on the flowchart in FIG. 28D. FIG. 28D shows the procedure for displaying the device waveform. First, in step S2810-1, the display processing unit 51 displays the device waveform based on the display data generated by the display data generating unit 51a in step S2809.

Next, in step S2810-2, the display processing unit 51 determines whether the time designation cursor 404 has been moved while the device waveform is being displayed. If the time designation cursor 404 has not been moved, no particular processing is performed and the processing of step S2810-2 is repeated.

On the other hand, if the time designation cursor 404 has been moved, the process proceeds to step S2810-3, where the display data generation unit 51a of the display processing unit 51 extracts time series data corresponding to the time of the moved time designation cursor 404 from the driving record data. The extraction range may be, for example, centered on the time of the moved time designation cursor, and only the time range in which a waveform can be displayed may be extracted. Then, in step S2810-4, the display data generation unit 51a uses the extracted time series data to generate display data and update the display content.

For example, in the example of FIG. 12, the time designation cursor 404 is at a position corresponding to the time "20XX/4/20 11:26:23" (scan count 35,000), and the user operates the slider to the right to advance the time. For example, assume that the time is advanced from scan count 35,000 to the time corresponding to scan count 40,000. Then, the display data generation unit 51a of the display processing unit 51 extracts time series data corresponding to a predetermined number of scans before and after scan count 40,000 from the driving record data. Then, the display data generation unit 51a uses the extracted time series data to generate display data such that scan count 40,000 overlaps with the identification line IL, and updates the display content.

When the one-step playback button 408 is touched, the display data generating unit 51a of the display processing unit 51 uses the time specified by this touch operation as a reference, extracts time series data corresponding to a predetermined number of scans before and after this reference, generates display data, and updates the display content. When the playback button 406 is touched, the display data generating unit 51a sequentially extracts time series data from the driving record data and sequentially updates the display content so that the corresponding device waveform is displayed (this causes the device waveform to scroll horizontally).

In addition, in FIG. 28D, the processing operation when the time specification cursor is moved while the device waveform is displayed is described, but the processing is the same when a touch operation is performed on any event from among a plurality of event groups EV in the event error history column 171 shown in the camera event display screen 170 shown in FIG. 23, for example.

Specifically, the display data generating unit 51a of the display processing unit 51 judges whether or not a touch operation has been performed on an arbitrary event in the event error history column 171 while the camera event display screen 170 shown in Fig. 23 is being displayed. If it is judged that a touch operation has been performed, the display data generating unit 51a not only switches the highlighted portion in the event error history column 171 to the arbitrary event, but also specifies the occurrence time of the arbitrary event and displays it in the time display area 409. The display data generating unit 51a also changes the display position of the time designation cursor 404 to match the occurrence time of the arbitrary event. Furthermore, the display data generating unit 51a extracts the camera image acquired at the time closest to the occurrence time of the arbitrary event from the driving record data and displays it in the camera image display column 172.
(Real-time chart monitor)

The programmable display 50 can also acquire device waveforms via the PLC 1 and display them in real time. Such real-time display is realized as a monitor mode of a real-time chart monitor displayed on the programmable display 50. The real-time chart monitor has a monitor mode in which current device values are collected sequentially and displayed in real time as moving images, as well as a replay mode in which previously acquired time-series data is read and displayed. That is, the real-time chart monitor has a monitor mode in which the current state is displayed as it is, and a replay mode in which a state at a certain point in the past is reproduced. These modes can be switched by a mode switching unit. The mode switching unit can be realized by switching a "real-time chart monitor (replay mode)" button 142 and a "real-time chart monitor (monitor mode)" button 143, which are display components displayed on the menu screen 140 of FIG. 21, for example. When the "real-time chart monitor (monitor mode)" button 143 is touched on the screen of FIG. 21, the monitor mode of the real-time chart monitor is executed on the programmable display 50, and the device waveform display screen 210 of FIG. 29 is displayed. The device waveform display screen 210 in FIG. 29 is displayed as a moving image whose display contents are updated in real time.
(Acquisition device setting 52d)

The setting storage unit 52 of the programmable display 50 shown in FIG. 11 also stores an acquisition device setting 52d for identifying an acquisition device as a device waveform to be displayed in the monitor mode of the real-time chart monitor. The PLC 1 temporarily records the device value of the device identified in the acquisition device setting 52d as time-series data in the temporary recording unit 91a by the recording control unit 39. The programmable display 50 then acquires this time-series data via the display-side communication unit 58, and displays the device value as a moving image on the device waveform display screen 210 shown in FIG. 29, updating it successively.

In this manner, the setting storage unit 52 stores the acquisition device setting 52d that specifies the acquisition device from which the time-series data of the device value is to be repeatedly acquired. The setting storage unit 52 also includes the setting of a real-time display component for sequentially displaying the time-series data of the acquisition device.
(Monitor mode)

As described above, in the monitor mode of the real-time chart monitor, the programmable display 50 sequentially displays the time series data of the device values temporarily recorded in the temporary recording unit 91a of the PLC 1 on the display unit 55. For this purpose, the programmable display 50 performs in advance the setting of the acquisition device setting 52d for specifying the acquisition device to be repeatedly acquired, and the setting of the real-time display component for sequentially displaying the time series data of the acquisition device, and stores the setting in the setting storage unit 52. As a result, when the user touches the real-time display component on the user screen, the touch detection unit 53 detects the touch operation, and the display data generation unit 51a generates display data for sequentially displaying the device values on the display screen based on the time series data of the device values of the acquisition device temporarily recorded in the temporary recording unit 91a of the PLC 1. In the example of FIG. 21, the real-time display component corresponds to the "real-time chart monitor (monitor mode)" button 143.
(Target device setting screen)

In the real-time chart monitor, the target device for the device waveform to be displayed in the monitor mode or replay mode is set on the target device setting screen. FIG. 16 shows an example of the target device setting screen 220 for setting such a target device. The target device setting screen 220 can be set for each mode, i.e., for the replay mode and the monitor mode, separately. If multiple user screens are set in each mode, the user can set it for each surface, i.e., for each RTCMID. In the example of FIG. 16, the target device to be displayed is set for RTCMID0 in the replay mode. Here, the candidate target devices are displayed in a list in the unit selection field 221, and the unit name, device name, and display format are displayed for each device. The display format indicates the format when displayed on the display unit 55 (for example, whether decimal or binary display, the number of bits, the presence or absence of a positive or negative sign, etc.). The display format may be a preset format, or the user may be allowed to arbitrarily specify the display format for each device. For example, the user selects the desired device from the screen of FIG. 16 and specifies the display format.

Display on the real-time chart monitor is performed according to the settings on this target device setting screen 220. For example, in the example of Fig. 16, DM100, DM200, and R000 are selected as target devices, and when displaying in replay mode on the real-time chart monitor of Fig. 12, the device waveforms of DM100, DM200, and R000 designated as these target devices are displayed.
(Real-time chart monitor (monitor mode))

The programmable display 50 according to this embodiment can display a real-time chart monitor (monitor mode). The real-time chart monitor (monitor mode) uses a temporary recording unit 91a (ring buffer) provided in the CPU unit memory unit 32 separately from the PLD side device unit 34 in the PLC 1 shown in FIG. 6.

Here, the processing operation when the real-time chart monitor of the programmable display 50 is set to monitor mode will be described based on the flowchart in Figure 30. First, the display processing unit 51 of the programmable display 50 requests the PLC 1 to monitor the device waveform via the display side communication unit 58 (step S3001). When the CPU unit processing unit 31 receives this monitoring request, it stores the device value of the device that is the subject of the monitoring request in the ring buffer for a certain period of time. As a result, the ring buffer stores time series data of the device value for the certain period of time for the device that is the subject of the monitoring request.

The display unit processing unit 51 periodically requests the PLC 1 to transfer data via the display unit communication unit 58 (step S3002). This data transfer request is a request to transfer a predetermined amount of data from the previously read position of the time series data of the device values stored in the ring buffer, which is the temporary recording unit 91a provided in the CPU unit storage unit 32. The CPU unit processing unit 31 transfers a predetermined amount of data from the previously read position of the time series data of the device values stored in the ring buffer to the programmable display unit 50 (step S3003). In addition, in order to display the device waveform (horizontal axis is the time axis) on the programmable display unit 50, information on the time when the device values were stored in the ring buffer is obtained from an internal clock (time management unit 83b in FIG. 8) or the like. Then, the time series data of the device values and information on the time when each device value was stored in the ring buffer are transferred to the programmable display unit 50. The display unit processing unit 51 then receives these data and performs additional display of the device waveform based on the time information (step S3004). In this manner, the additional display of device waveforms is repeated until monitoring of the device waveforms is completed (step S3005).
(Monitor mode display example)

Next, a display example of the real-time chart monitor (monitor mode) is shown in the device waveform display screen 210 of FIG. 29. In this way, in the monitor mode of the real-time chart monitor, the device waveform is displayed in a graph. In this graph, the time axis indicates the number of scans, and it may be switched to a time display. The left side of the graph is older in terms of time, and the right side of the graph is newer in terms of time. In the example of the device waveform display screen 210 of FIG. 29, the device waveforms of the devices DM100, DM200, and R000 are displayed. For each device waveform, the right end indicates the latest device value. After this, the display processing unit 51 adds and displays the time series data of the device value received from the PLC to the right end of each device waveform. This extends to the right of each device waveform. When the device waveform reaches the right end of the real-time chart monitor column, the monitor screen including the graph scrolls to the left, and the device values are hidden one after another from the left end of the device waveform.

Here, the real-time chart monitor (monitor mode) shown in FIG. 29 can be displayed on the display unit 55 of the programmable display device 50 by performing the following settings. That is, first, in the screen data creation device 60, the "real-time chart monitor (monitor mode)" is assigned as a switch function to the switch part of the "real-time chart monitor (monitor mode)". Then, in the target device setting screen 220 of the system setting screen 130 shown in FIG. 16, the RTCMID to be displayed in the "real-time chart monitor (monitor mode)" is specified, and the type and number of devices whose device waveforms should be displayed on the screen corresponding to the RTCMID are set. Note that the type and number of devices whose device waveforms should be displayed may be the same as the contents set in the above-mentioned "real-time chart monitor (replay mode)". The screen data created in this way is transferred from the screen data creation device 60 to the programmable display device 50. As a result, by touching the "real-time chart monitor (monitor mode)" button 143 on the menu screen 140 of FIG. 21, the time-series data (device waveforms) of the desired type and number of devices can be displayed on the system screen of the programmable display device 50.
(Replay display part)

To switch to the replay mode, touch the replay display component. In the example of the menu screen 140 in FIG. 21 described above, two replay display components are provided: a "real-time chart monitor (replay mode)" button 142 and a "replay mode start" button 141. When the "replay mode start" button 141 is touched, a replay mode screen (such as FIG. 12, FIG. 23 to FIG. 27, etc.) is displayed according to the previous settings. From these replay mode screens, the user can perform various settings related to the replay mode and switch the display contents. Specifically, by touching the tabs provided at the top of the screen, a different display screen can be switched. For example, when the "real-time chart monitor" tab 161 is selected, the device waveform display screen 160 in FIG. 12 is displayed. When the "camera/event" tab 162 is selected, the camera/event display screen 170 in FIG. 23 is displayed. When the "viewer" tab 163 is selected, the viewer display screen 180 in FIG. 24 is displayed. Furthermore, when the "Unit" tab 164 is selected, the unit display screens 190 and 190B in FIG. 25 and FIG. 26 are displayed. When the "Program" tab 165 is further selected, the program display screen 200 in FIG. 27 is displayed.

On the other hand, when the "Real-time chart monitor (replay mode)" button 142 is touched, a device waveform display screen 160B in Fig. 31 is displayed. On this screen, multiple tabs like those in Fig. 12 and Fig. 23 to Fig. 27 are not displayed, and only the device waveform display screen is displayed.
This can be called up in a single click when you just want to display real-time device waveforms without having to go through detailed settings.
(Initial display screen setting section)

The initial display screen that is initially displayed in the replay mode is set by the screen data creation device 60. When displaying the device waveform on the initial display screen, the target device to be displayed can be selected. In addition, the target device to be initially displayed can be changed according to conditions. The replay mode is used to investigate the cause of a problem, and it is believed that the device that is considered to be the cause of the problem often differs depending on the type of problem. Therefore, by changing the target device to be initially displayed in the replay mode depending on the type of storage condition at the time of the problem, the state of the target device can be quickly examined, which is believed to contribute to the investigation of the cause of the problem. Therefore, for example, as shown in FIG. 32, the screen data creation device 60 is set in advance to change the device waveform to be displayed on the programmable display device 50 in the replay mode depending on the cause of the problem. As a result, when some kind of problem occurs during the operation of the FA system, the device waveform of a device that is likely to be related to the cause of the problem can be selectively displayed, thereby realizing a programmable display device 50 that presents information useful for identifying the cause of the problem and is useful for early recovery. Furthermore, when displaying the device waveform on the display screen, it is possible to display one or more target devices and a setting screen for setting the display format.

Such settings are made from an initial display screen setting section 230 of the screen data creation device 60 as shown in FIG. 33. The initial display screen setting section 230 shown in this figure is common to the switch setting screen 120 shown in FIG. 15, and detailed description will be omitted. Here, a "method of designating RTCMID" section 126 is provided in the real-time chart monitor (replay mode) detailed setting section 124. The method of designating RTCMID can be external designation. In the case of external designation, the location and device name of the target device are designated from a location selection section 127 and a device name selection section 128, respectively. In the example of FIG. 33, the device values of "PLC1" as the location and "DM300" as the device name are designated as RTCMID. In this case, if the device value of DM300 is 0, RTCMID=0 is designated, and if the device value of DM300 is 1, RTCMID=1 is designated. In this way, by using the device allocation mechanism as a method for specifying the RTCMID, when a problem occurs, it is possible to dynamically change the RTCMID of the real time chart monitor (replay mode) displayed on the programmable display 50. Note that "external specification" and "internal specification" can be selected as the method for specifying the RTCMID in the "RTCMID specification method" field 126, and "internal specification" may be selected when it is desired to set the RTCMID to a fixed value as described above.
(data structure)

Next, in this embodiment, the data structure of the screen data of the user screen created by the screen data creation device 60 is shown in FIG. 34A, the data structure of the system screen pre-installed by the developer of the programmable display device 50 is shown in FIG. 34B, and a schematic diagram of the data structure in which the RTCMID and device are linked as described above is shown in FIG. 34C.

As shown in Figure 34A, the data structure of screen data created by the user has page settings for each page managed by a screen ID (e.g., 0001 to 0003), and part settings for various parts arranged on one page. As described in detail using Figure 2, the part types of parts arranged on one page include text parts TX, character display parts CP, numeric display parts NP, switch parts SP (including page switching parts), lamp parts RP, meter parts MP, graph parts GP, etc. In addition, part IDs are assigned to distinguish between multiple parts of the same type. For example, if there are two text parts, different part IDs are assigned to them.

In addition, each component is assigned a device, except for the text component TX. For example, in the example in Figure 34A, the character display component CP with component ID 0002 is assigned the device DM1001, the numeric display component NP with component ID 0003 is assigned the device DM1002, the switch component SP with component ID 0004 is assigned the device R1001, the lamp component RP with component ID 0005 is assigned the device R1002, the meter component MP with component ID 0006 is assigned the device DM1003, and the graph component GP with component ID 0007 is assigned the device DM1004.

All parts are also associated with the X and Y coordinates at which they are placed on a page. For example, in the example in Figure 34A, a text part is shown to be placed at coordinates (10, 10) on a page. The same is true for the other parts.

Furthermore, with the exception of text components, each component is assigned one or more component images. For example, in the example of FIG. 34A, in the case of the character display component CP and the number display component NP, a component image of a frame in which characters or numbers are displayed is assigned, and the thickness and color of this frame can be freely set by the user. The same applies to the other components.

As shown in FIG. 34B, information for displaying the system default screen (system default screen information 52f) is stored in advance in the setting storage unit 52 by the developer of the programmable display device 50 (or may be stored in the data memory 56 or other system memories). As described with reference to FIG. 28A, the display data generating unit 51a of the programmable display device 50 reads out this system default screen information 52f, extracts the necessary time series data of device values from the driving record data, and generates display data DP for superimposing the time series data of device values on the system default screen. Then, the display processing unit 51 performs the desired screen display based on the display data DP generated by the display data generating unit 51a. In FIG. 34B, the data structure for displaying the device waveform display screen 160 shown in FIG. 12 was described, but the same applies to the data structures for displaying each screen shown in FIG. 23 to FIG. 27.

As shown in FIG. 34C, a designated device that specifies the RTCMID and a target device that is displayed in the real-time chart monitor replay mode are assigned to each different RTCMID.

In this way, an alarm at the time of occurrence of a trouble can be linked with the display data. For example, when the "replay mode start" button 141 is touched on the system screen of Fig. 21, a user screen according to the device value of the specified target device (DM300) is displayed according to the setting in Fig. 33. As described above, when the device value of DM300 is 0, the page of RTCMID0 is selected as the initial screen 150 (Fig. 22) of the replay mode, and when the device value of DM300 is 1, the page of RTCMID1 is selected as the initial screen 150 (Fig. 22). This allows an appropriate user screen (displayed device) to be selected and initially displayed according to the state of the trouble, and by previously associating a highly related device according to the trouble phenomenon, it is useful for smooth trouble solving.
(Ladder Monitor)

The programmable display 50 may also have a ladder monitor function that displays a ladder program as shown in the program display screen 200 of FIG. 27 in the replay mode of the real-time chart monitor. Specifically, when the storage condition is satisfied, the PLC 1 stores the user program that was being executed by the program execution unit 40 when the storage condition was satisfied in the storage memory 36, including the user program in the operation record data so that the user program is associated with the operation record data. The programmable display 50 then acquires the operation record data stored in the storage memory 36 of the PLC 1, and displays the user program on the display unit 55 based on information about the acquisition time included in the operation record data. At this time, the device value corresponding to the acquisition time is displayed on the user program (e.g., ladder program) included in the operation record data. As shown in FIG. 27, the device value is displayed for each device shown in the ladder diagram display field 206.
(Event Monitor)

The programmable display 50 may further include an event monitor function for displaying events. The event collection unit 92b of the PLC 1 collects event data corresponding to a plurality of events that occur in the PLC 1 or in a controlled device controlled by the PLC 1, and stores the event data in chronological order in the temporary recording unit 91a by associating the event occurrence time with the event data. When the storage conditions are met, the event data stored by the event collection unit 92b is stored in the storage memory 36, included in the driving record data so that it is associated with the driving record data.

The programmable display device 50 then acquires the driving record data stored in the storage memory 36, and displays on the display unit 55 an event corresponding to the event data included in the driving record data, based on the occurrence time included in the driving record data. Figure 23 shows the state in which the event monitor function is executed in the replay mode of the real-time chart monitor. In this example, an event/error history column 171 is provided on the left of the camera/event display screen 170, and a camera image display column 172 is provided on the right. In the event/error history column 171, each event included in the driving record data is displayed in a list together with the event content and the date and time of occurrence. Furthermore, when a desired event is selected in the event/error history column 171, a camera image captured by a camera corresponding to this event is displayed in the camera image display column 172.
(Playback control column 402)

Furthermore, a playback control field 402 is provided at the bottom of the camera/event display screen 170 for controlling playback of log data such as saved device values. A slider-like time designation cursor 404 can be moved left and right. The time designation cursor 404 is assigned according to time, linked to the time information included in the driving record data, with the left being the past and the right being the future. When the time designation cursor 404 is tapped to move it, the event at the corresponding time is selected in the event/error history field 171, and the camera image in the camera image display field 172 is switched. The currently selected time information is displayed in the time display area 409.

The play button 406 is a button for instructing the chronological display of device values. When the play button 406 is tapped, the event changes over time, and the camera image in the camera image display field 172 is displayed like a moving image. The one-step reverse play button 407 is a button for instructing the chronological display of device values while updating (rewinding) the display time one step at a time. The one-step play button 408 is a button for instructing the chronological display of device values while updating the display time one step at a time.
(Function block diagram of PLC1)

User programs such as ladder programs executed by the above PLC1 are created by the program creation device 70. The user programs created by the program creation device 70 are transferred to the PLC1. Figure 35 shows a functional block diagram of the PLC1 connected to the program creation device 70. The PLC1 shown in Figure 35 includes a CPU unit storage unit 32, a CPU unit processing unit 31, a bus master 38, a PLC side communication unit 33, and a program receiving unit 47. The CPU unit storage unit 32 includes a project storage unit 35, a PLC side device unit 34, a temporary recording unit 91a, and a storage memory 36.

The project storage unit 35 is a member for storing project data including a ladder program input from the program creation device 70. The PLC side device unit 34 has bit devices and word devices, and each device is a member for storing device values. The PLC side device unit 34 functions as a device memory that stores each device value of a plurality of devices. This PLC side device unit 34 becomes a storage area referenced according to a user program. The temporary recording unit 91a is a member for recording the device values stored in the PLC side device unit 34 in chronological order for each scan. The temporary recording unit 91a is composed of a ring buffer or the like. The storage memory 36 is a member for storing the time series data of the device values stored in the temporary recording unit 91a when a predetermined storage condition is met. The storage memory 36 is composed of an internal memory, a removable memory card, or the like.

The CPU unit processing section 31 includes a program execution section 40, a recording control section 39, a storage control section 39C, and an event management section 76. The program execution section 40 is an execution engine for the ladder program. When a recording start trigger condition for starting recording in the temporary recording section 91a is satisfied, the recording control section 39 collects device values of a predetermined device, and records information on the acquisition time of the device values (which may be the current time or the number of scans of the ladder program) in association with the device values in the temporary recording section 91a. Here, the recording start trigger condition may be when the PLC 1 transitions from the setting mode to the RUN mode. However, the recording start trigger condition is not limited to this, and may be other conditions. When a storage trigger condition for performing storage in the storage memory 36 is satisfied, the storage control section 39C stores the device values temporarily recorded in the recording control section 39 as log data together with information on the acquisition time. The event management section 76 is a member for detecting an event. The details of the event management section 76 will be described later.

The bus master 38 is a member that controls communication of the inter-unit bus that connects the CPU unit 3 and the expansion unit 4. The bus master 38 performs input/output refresh. The CPU unit 3 performs input/output refresh, execution of the ladder program, and END processing as one scan, and repeatedly executes this scan processing at high speed. The input/output refresh synchronizes the devices of the CPU unit 3 and the devices of the expansion unit 4. The result of the ladder program executed by the program execution unit 40 is reflected in the devices of the expansion unit 4 by the input/output refresh. The END processing performs peripheral services such as system error checks, and performs data communication with the programmable display 50 by the PLC side communication unit 33. The PLC side communication unit 33 is a member for repeating communication with the programmable display 50 at a predetermined cycle with the PLC 1. The program receiving unit 47 is a member for receiving project data including the ladder program transferred from the program creation device 70.
(Functional block diagram of program creation device 70)

On the other hand, the program creation device 70 shown in FIG. 35 includes a program creation input unit 74, a program creation display unit 75, a program creation storage unit 76, a program creation unit 77, and a program transfer unit 78. The program creation device 70 may be installed on a PC that also serves as the screen data creation device 60. The program creation input unit 74 may be a mouse, a keyboard, or the like. A user can edit and input ladder programs and set unit configurations via the program creation input unit 74. The program creation display unit 75 is a display or the like connected to the PC.

The program creation unit 77 creates a ladder program according to user operation input via the program creation input unit 74. It also sets the unit configuration. The ladder program and unit configuration are collectively called project data. The program creation memory unit 76 stores the project data created by the program creation unit 77. The program creation memory unit 76 also stores the operation record data of the PLC 1. The program transfer unit 78 is a member for transferring the project data including the ladder program stored in the program creation memory unit 76 to the PLC 1.
(Driving record data)

Here, the driving record data stored in the storage memory 36 will be described in detail. The driving record data includes project data and log data. An example of the configuration of the driving record data is shown in FIG. 36. The project data included in the driving record data is project data during driving that was executed by the program execution unit 40 when the storage trigger condition was met. The log data is time-series data of device values associated with information relating to acquisition time, time-series image data from the camera unit 4c, event data, etc. This image data and event data are also associated with information relating to the acquisition time of the image data and the occurrence time of the event data, and the details of these associations will be described later.

The driving record data is a package of multiple files, and includes management information data and project identification information. Here, the management information data is information about what is included in the driving record data. The extension can be, for example, TMN. The identifier for the project data included in the driving record data can be, for example, TPJ. The project identification information is information for identifying the project data when the driving record data is saved. The extension can be, for example, TPI. The extension for the time-series data of device values can be, for example, TDV. The extension for the time-series image data can be, for example, TCA. The extension for the event data can be, for example, TEV. These examples of extensions are merely examples, and any character string can be used for the extension.

Furthermore, the project data (extension TPJ) includes a project file, a module file, a function block, a unit setting file, etc. The project file is information related to the project settings, and the extension is, for example, kpr. The module file is information related to the so-called ladder program, and the extension is, for example, mod. The function block is information related to a modularized ladder program, and the extension is, for example, kfb. The unit setting file is configuration information of a unit, and the extension is ue2. Only a portion of this information may be included in the project data, or other information may be added. The program creation unit 77 in FIG. 35 can interpret the management information data included in the driving record data and display the contents of the driving record data on the program creation side display unit 75.
(Driving record data interpretation unit 51b)

As described above, the contents of the driving record data can be displayed not only on the PLC 1 but also on the programmable display 50. For this reason, the programmable display 50 is provided with a driving record data interpretation unit 51b. Here, the manner in which the contents of the driving record data are displayed on the programmable display 50 side will be described with reference to FIG. 36. The display processing unit 51 of the programmable display 50 shown in this figure is provided with a driving record data interpretation unit 51b. The driving record data interpretation unit 51b reads out the management information data from the driving record data and judges what is included in the driving record data. In addition, it reads out the project data corresponding to the project identification information and reads in the project file, module file, function block, unit setting file, etc. that constitute the project data. This allows the display processing unit 51 to synchronously display (linked display) various user interfaces in the replay mode.
(Synchronized display of driving record data (linked display))

A functional block diagram of the display processing unit 51 of the programmable display unit 50 is shown in FIG. 37. As shown in this figure, the display processing unit 51 has a waveform 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 replay synchronization control module 324. The waveform display module 322 is a module that displays the time series data of the device values contained in the log data as a device waveform on the display unit 55.

In the device waveform display screen 160 shown in FIG. 12, when the time specification cursor 404 is dragged left and right, the device waveform moves left and right in tandem. A thick vertical identification line IL is displayed in the center of the device waveform display screen 160 (position of scan count 35,000), and the device waveform moves left and right so that the time (scan count) specified by the time specification cursor 404 overlaps with the identification line IL. For example, when the time specification cursor 404 is moved rightward from the state shown in FIG. 12 to the position of scan count 40,000, the device waveform moves left so that the position of scan count 40,000 in the device waveform overlaps with the identification line IL. Note that the device value of the device waveform that overlaps with the identification line IL may be displayed on the screen.

Details of the image display module 323, event display module 326, viewer display module 327, unit display module 325, and program display module 321 are explained with reference to Figures 37 to 40.

The display processing unit 51 shown in FIG. 37 includes a program display module 321. The program display module 321 is a module that displays the device values included in the log data 73 on the display unit 55 along with the user program included in the project data 71. The program display module 321 may also be capable of displaying not only the user program but also various information that allows the user to visually confirm the settings of the project data 71, such as program configuration information included in the project data 71, multiple program parts, unit configuration, and function settings for each unit. The image display module 323 displays time-series image data included in the log data 73 on the display unit 55.

The waveform display module 322 is a module that converts the time-series device values contained in the log data 73 into waveforms and displays them on the display unit 55. The replay synchronization control module 324 synchronizes the information displayed by the program display module 321 and the information displayed by the waveform display module 322 in time. The replay synchronization control module 324 can replay-display the device waveform on the device waveform display screen 160 in FIG. 12. The event display module 326 also extracts events in chronological order from the driving record data as shown in FIG. 23, and displays them in a list in the event/error history column 171. The viewer display module 327 also extracts maintenance information from the driving record data as shown in FIG. 24, and displays a maintenance screen, etc.

These modules may be called engineering software. The image display module 323 may be embodied as one function (image display unit) of the program display module 321, or may be embodied as one function (image display unit) of the waveform display module 322.
(Program Display Module 321)

Figure 38 shows the details of the program display module 321. The time UI 330a provides a UI (e.g., a slide bar, a cursor, etc.) for manipulating the acquisition time (display time) of the device displayed together with the user program. The display time control unit 331a sends the display time specified by the time UI 330a to the replay synchronization control module 324, and sets the display time notified from the replay synchronization control module 324 to the time UI 330a. The program display unit 332 displays the project data 71 on the display unit 55, and reads the project data 71 corresponding to the identification information from the PC side storage device 22 and displays it on the display unit 55. In addition, the program display unit 332 displays the device value acquired by the device value acquisition unit 333a in association with the device used or described in the user program. The device value acquisition unit 333a has a real-time playback mode and a history playback mode (log playback mode). In the real-time playback mode, the device value acquisition unit 333a accesses the real-time transmission unit of the PLC 1, acquires the device value, and passes it to the program display unit 332. In log playback mode, the device value acquisition unit 333a accesses the replay synchronization control module 324 in FIG. 37, acquires the display time and device value, and passes them to the program display unit 332.

Figure 39 is a schematic diagram showing an example of a user interface screen 1300 displayed on the display unit 55 of the programmable display 50 by the program display unit 332 or the like. In Figure 39, various information constituting the project data 71 is displayed in the project display area 420 in the left column. From the top, the unit configuration (CPU unit 3, motion unit 4d, analog input unit, camera unit 4c), program configuration (each scan module, fixed cycle module, inter-unit synchronization module, function block, macro) are displayed. For the motion unit 4d, the axis configuration and axis control setting parameters are displayed as function settings. The user can check the setting contents of these setting parameters by double-clicking the axis configuration and axis control on the user interface screen 1300 shown in Figure 39. In addition, in the project display area 420, Main and Sub are displayed for each scan module. When the user clicks Main, the Main program is displayed in the program display area 410 of the ladder monitor 450 in the center.

The program display module 321 shown in FIG. 37 reads the project data 71 from the memory card 36A and displays various information in the project display area 420 and displays the desired program in the program display area 410.

The program display area 410 is a part of the so-called ladder monitor 450, and can be operated independently in real-time playback mode. It is also possible to hide only the ladder monitor 450 by clicking the cross mark. On the other hand, in log playback mode, the program display unit 332 can reproduce the ladder program included in the project when the driving record was saved. In addition, in log playback mode, the program display unit 332 displays the device values included in the log data 73 via the device value acquisition unit 333a in association with the devices described in the Main program. The device values to be displayed are the device values corresponding to the time specified by the time specification cursor 404.

In the example of FIG. 39, the device value associated with 18:52:54 on 10/01/20XX displayed in the time display area 409 is displayed in association with the device described in the Main program. [35000/74286] displayed to the right of this date indicates that the current number of scans is 35000 out of a total of 74286 scans. The user can drag and move the time specification cursor 404 to update the display time and number of scans, as well as the display of the device value. For example, at the updated display time, relay devices that are ON are displayed as ON (for example, filled in with a color), and relay devices that are OFF are displayed as OFF (for example, colored out).

In FIG. 39, the upper right column is provided with an image display area of the camera monitor 430. The image display module 323 reads image data from the log data 73 in synchronization with the display time displayed on the ladder monitor 450 by the program display module 321, and displays the image data in the image display area of the camera monitor 430. In FIG. 39, image data associated with the display time of 18:52:54 on 10/1/20XX is displayed on the camera monitor 430. Also, to the right of this display time, 282/601 is displayed, which indicates the current order of image data (the 282nd image) relative to the total number of images captured 601. The user can update the display time and the current order of image data by dragging and moving the time designation cursor 404a on the camera monitor 430.

At this time, the time designation cursor 404 in the ladder monitor 450 described above moves in conjunction with the movement of the time designation cursor 404a. For example, if the time designation cursor 404a is set to 19:00:00 on the display time 20XX/10/01, the time designation cursor 404 in the ladder monitor 450 also moves to the position of 19:00:00 on the display time 20XX/10/01. Then, as the time designation cursor 404 moves, the device value in the ladder monitor 450 is also updated. Here, the time designation cursor 404a is moved, but the reverse is also true. For example, when the time designation cursor 404 in the ladder monitor 450 is moved, the time designation cursor 404a in the camera monitor 430 also moves accordingly. Such processing operations are possible because the program display module 321 and the image display module 323 execute synchronization control regarding the display time via the replay synchronization control module 324.

Also, in FIG. 39, the unit monitor 440 is displayed in the lower right column. For example, the unit monitor 440 displays the device values of the buffer memory (UG) in the motion unit 4d. More specifically, when the unit display module 325 of the display processing unit 51 receives the display time to be currently played back from the replay synchronization control module 324, it reads the device values associated with that time from the memory card 36A and displays them on the unit monitor 440. Therefore, for example, in FIG. 39, a list of device values associated with the display time 20XX/10/01 18:52:54 is displayed on the unit monitor 440.

Figure 40 is a diagram showing a schematic of a data source for displaying a user interface screen in the log playback mode. As shown in Figure 40, the project display area 420 reads out the unit configuration, function settings, program configuration, and program parts included in the project data 71 from memory and displays them in a tree format. The ladder monitor 450 reads out the program configuration (what kind of program parts it consists of) and program parts from memory, displays the program parts specified by the user, and reads out and displays the device value corresponding to the display time from the log data 73. The camera monitor 430 reads out and displays image data corresponding to the display time from the log data 73 based on information such as the unit configuration (whether or not there is a camera monitor) and function settings (functions of the camera monitor. For example, port numbers, imaging cycle, gain settings, etc., if there are multiple ports). The unit monitor 440 reads out and displays the device value corresponding to the display time from the log data 73 based on information such as the unit configuration (what kind of units there are) and function settings (axis configuration, axis control, etc., if it is a motion unit 4d).

As can be seen from Figures 39 and 40, the replay synchronization control module 324 can synchronize and control the program display module 321, image display module 323, and unit display module 325 to link them together. Details of the linkage of the waveform display module 322 will be described later.

Here, in this embodiment, it is possible to verify whether the current project data matches the project data 71 at the time of the actual occurrence of a problem. More specifically, the collation unit 334 in the program display module 321 shown in FIG. 38 collates the identification information of the project data 71 (user program) output from the PLC 1 with the identification information of the project data 71 (user program) stored in the PC-side storage device 22, and outputs the collation result to the warning unit 335. The warning unit 335 displays a warning on the display unit 55 when the identification information of the project data 71 (user program) output from the PLC 1 when the operation record is saved does not match the identification information of the project data (user program) stored in the PC-side storage device 22.

In this embodiment, the identification information of the two project data is compared to verify whether they match or not. More specifically, identification information is added to the program configuration, multiple program parts, unit configuration, and function settings for each unit included in the project data, and verification is performed based on whether all of these match. However, the present invention is not limited to this, and it is sufficient to compare at least the identification information of a user program composed of multiple program parts to verify whether they match or not.

In addition to the device values and image data of the camera unit 98 when the driving record was saved, the log data also includes user programs such as ladder programs included in the project data when the driving record was saved, and setting files for each unit. For example, the log data includes image data captured by the camera unit 98 when a problem occurred, the state of each unit, and information such as the angle and coordinates of the motion unit 4d. This allows the log data to store the past state and connection state of each device, information about each unit, etc., so that past states can be reproduced by saving the log data. In other words, it is possible to go back to the time when the problem occurred and check what settings were used and what output was produced, which is useful for identifying the cause of the problem. In addition, by reading the log data with the program creation device 70, the settings stored in the log data can be analyzed and reproduced.

Figure 41 shows an example of log data 73. In this example, device values d1 to d10, the acquisition timings of workpiece images i1 to i3 acquired by camera unit 98a, and other images j1 to j3 acquired by camera unit 98b are shown. Device values d1 to d10 are acquired for each scan cycle. Workpiece images i1 to i3 are acquired at the timing when a trigger signal is generated. Workpiece images j1 to j3 are acquired at the timing when a trigger signal is generated. The position of each piece of data indicates its respective time information. As shown in Figure 41, the acquisition times and acquisition cycles of each piece of data do not match. Therefore, the display processing unit 51 adjusts the display timing of each piece of data based on the time information of each piece of data.

Figure 42 is a diagram explaining the display timing and display duration of log data 73. The display processing unit 51 displays each device value on the display unit 55 according to the time information of each device value. For example, the display processing unit 51 determines the difference time between the time information of device value d1 and the time information of device value d2 as the display duration of device value d1. The display processing unit 51 starts displaying device value d2 when the display duration has elapsed since starting to display device value d1. Thereafter, the display duration is calculated in a similar manner, and the displayed device value is switched according to the time information and display duration.

As already shown in FIG. 41, the acquisition time of the device value d1 does not match the acquisition time of the work image i1. Therefore, the display processing unit 51 compares the acquisition time of the work image i1 with the acquisition time of the device values d1 to d10, and obtains the acquisition time of the device value dx that is closest to the acquisition time of the work image i1. In this example, the acquisition time of the device value d1 is closest to the acquisition time of the work image i1. Therefore, the display processing unit 51 starts displaying the device value d1 and also starts displaying the work image i1. Next, the display processing unit 51 obtains the acquisition time of the device value dx that is closest to the acquisition time of the work image i2. In this example, the acquisition time of the device value d4 is closest to the acquisition time of the work image i2. Therefore, when the display timing of the device value d4 arrives, the display processing unit 51 starts displaying the device value d4 and the work image i2. The display processing unit 51 obtains the acquisition time of the device value dx that is closest to the acquisition time of the other image j1. In this example, the acquisition time of the device value d2 is closest to the acquisition time of the other image j1. Therefore, when the timing to display device value d2 arrives, the display processing unit 51 starts displaying device value d2 and also starts displaying another image j1.

In this way, among the multiple data included in the log data 73, the display timing of each data may be adjusted based on the data with the shortest logging period.
(An example of linking image data with acquisition time)

In this embodiment, as described above, the image data captured by the camera and the event can be displayed in synchronization. When an arbitrary event is selected in the "Camera Event" tab 162 in the replay mode, a camera image based on the image data captured at the time corresponding to the time of the selected event is displayed, and the time designation cursor is also moved to the corresponding playback time. When the playback button is pressed, a video is played in the camera monitor field, and the event selection is switched over as time passes. The device value of the ladder program in the "Program" tab 165 is also updated. Such a synchronous display is possible because the image data and the acquisition time are linked and stored. The correspondence between the image data and the acquisition time and the device value will be described in detail below with reference to FIG. 41 and FIG. 42.
(Example of log data (device values and image data))

Figure 41 shows the timing of logging to collect device values and images using the camera unit 4c as shown in Figure 1. Note that up to two cameras can be connected to the camera unit 4c here. Each camera may have a different imaging field of view.

FIG. 41 shows device values d1 to d10, and the acquisition timing of workpiece images i1 to i3 acquired by camera 1, and other images j1 to j3 acquired by camera 2. Device values d1 to d10 are acquired for each scan cycle. Workpiece images i1 to i3 are acquired at the timing when a trigger signal (image acquisition signal) is generated. Workpiece images j1 to j3 are acquired at the timing when another trigger signal is generated. The position of each data indicates its respective time information. Generally, as shown in FIG. 41, the acquisition times and acquisition cycles of each data do not match. Therefore, the display processing unit 51 of the programmable display 50 adjusts the display timing of each data based on the time information of each data.
(Explanation of the timing and duration of log data display)

The display timing and display duration of the log data are shown in FIG. 42. The display processing unit 51 displays each device value on the display unit 55 according to the time information of each device value. For example, the display processing unit 51 determines the difference time between the time information of device value d1 and the time information of device value d2 as the display duration of device value d1. When the display duration has elapsed since the display of device value d1 was started, the display processing unit 51 starts displaying device value d2. Thereafter, the display duration is calculated in the same manner, and the displayed device value is switched according to the time information and the display duration.

As already explained, the acquisition time of the device value d1 does not match the acquisition time of the workpiece image i1. Therefore, the display processing unit 51 compares the acquisition time of the workpiece image i1 with the acquisition time of the device values d1 to d10, and obtains the acquisition time of the device value dx that is closest to the acquisition time of the workpiece image i1. In this example, the acquisition time of the device value d1 is closest to the acquisition time of the workpiece image i1. Therefore, the display processing unit 51 starts displaying the device value d1 and also starts displaying the workpiece image i1. Next, the display processing unit 51 obtains the acquisition time of the device value dx that is closest to the acquisition time of the workpiece image i2. 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 display timing of the device value d4 arrives, the display processing unit 51 starts displaying the device value d4 and the workpiece image i2. The display processing unit 51 obtains the acquisition time of the device value dx that is closest to the acquisition time of the other image j1. In this example, the acquisition time of the device value d2 is closest to the acquisition time of the other image j1. Therefore, when the display timing of the device value d2 arrives, the display processing unit 51 starts displaying the device value d2 and also starts displaying the other image j1. In this manner, the display timing of each data is adjusted based on the data with the shortest logging cycle among the multiple data included in the log data.
(Linking image data and time information)

In the camera event display screen 170 in FIG. 23, image data and time information are displayed in a linked manner. The procedure for linking image data and time information will now be described with reference to the flowchart in FIG. 43. Here, the procedure for logging in the camera unit 4c using the ring buffer 91b shown in FIG. 10 is shown. First, in step S4301, it is determined whether the acquisition relay is ON. Here, the camera unit processing unit 41c (CPU, etc.) of the camera unit 4c determines whether the image data acquisition conditions (for example, whether the PLC1 has been switched from PROG mode (setting mode) to RUN mode (execution mode) and the acquisition relay has been turned ON) are met. If the acquisition relay is not ON, the process of step S4301 is repeated.

When the acquisition relay is turned ON, the process proceeds to step S4302, where it is determined whether the acquisition timing has arrived. Here, the camera unit processing unit 41c determines whether the acquisition timing for image data has arrived. The acquisition timing is, for example, an image capture period (internal control period) that is predetermined in the camera unit 4c. If it is not the acquisition timing, the process returns to step S4302 and the process is repeated.

When the acquisition timing arrives, the process proceeds to step S4303, where image data and time information are acquired and written to the ring buffer. Here, an image capture command is issued to the camera, and image data is acquired from the camera. Also, in order to link the time when the image data was acquired, current time information is read from a time management unit such as an internal timer, and the image data and time information are associated and written to the ring buffer.

Next, in step S4304, it is determined whether or not there is a read request. Here, the camera unit processing unit 41c determines whether or not a read request (read command) has been issued from the CPU unit 3 to the ring buffer of the camera unit 4c. If there is no read request, the process returns to step S4302 and repeats.

On the other hand, if a read request is received, the process proceeds to step S4305, where image data and time information are obtained from the ring buffer and sent to the CPU unit 3. The CPU unit 3 adds the image data and time information to the driving record data as log data. In this way, the image data and time information are linked in the driving record data.
(Linking motion data and time information)

In addition, although the linking of image data captured by a camera with time information has been described in the above-mentioned FIG. 43, the linking of motion data with time information can also be performed in a similar manner. Specifically, the motion unit 4d stores setting information of programs and parameters (parameters related to axis configuration and axis control, etc.) that define the operation of the motion unit 4d. The motion unit 4d shown in FIG. 1 includes a motion unit processing unit 41d. The motion unit processing unit 41d transmits operation command values such as target coordinates and target speed to an externally connected motor (motor amplifier) according to the setting information. From the motor amplifier, the motion unit processing unit receives motion data such as current coordinates and current speed via an encoder. The control period for receiving motion data such as current coordinates and current speed is shorter than the scan period of the ladder program and is asynchronous with the scan period of the ladder program. Therefore, the motion unit processing unit 41d collects motion data at a predetermined period, associates information regarding the reception time when the motion data was received with the motion data and time information (read from a time management unit such as an internal timer), and writes the information into its own ring buffer. 43, when it is time to save the data, the motion data (current coordinates, current speed, etc.) and time information are obtained from the ring buffer and sent to the CPU unit 3. The CPU unit 3 adds the motion data and time information to the driving record data as log data. In this way, the motion data and time information are linked in the driving record data.
(Linking event data with time information)

Next, the procedure for linking event data and time information on the camera event display screen 170 in FIG. 23 will be described with reference to the flowchart in FIG. 44. First, in step S4401, the event management unit of the CPU unit processing unit 31 detects an event. The events referred to here include various things. For example, rewriting project data including the user program of PLC1 and unit configuration information of each unit, powering on/off input/output devices, switching between a setting mode for setting PLC1 and an operation mode for executing (operating) PLC1, clearing various histories, inserting/removing a storage device (memory card, etc.), inserting/removing an Ethernet cable for communicating with other devices, a device rewrite signal requested by the programmable display device 50 connected to PLC1, or a motion error of a motion unit in PLC1.

Events that occur in an expansion unit 4 such as a motion unit can be detected, for example, as follows. That is, the motion unit processing unit 41d sends a message communication command containing the event to the CPU unit 3 via the inter-unit bus. The CPU unit processing unit 31 then receives the message communication command containing the event by using interrupt processing. Upon receiving this, the CPU unit processing unit 31 can extract the event from the message communication command and recognize various events that occur in the motion unit in a timely manner.

Next, in step S4402, the event management unit of the CPU unit 3 checks the remaining capacity of the event log. In this embodiment, a predetermined storage area of the temporary recording unit 91a is used as the event log memory. It goes without saying that a separate memory for the event log may be provided independent of the temporary recording unit 91a. If there is no remaining capacity in the event log, the process proceeds to step S4403, where old events are deleted from the event log memory. On the other hand, if there is remaining capacity, the process proceeds to step S4404, where time information on the order of μs is obtained, linked to the event, and stored in the event log memory.
(Device monitoring by programmable display 50)

Here, the basic processing operation of the programmable display 50 for device monitoring will be described based on the flowchart in FIG. 45. The programmable display 50 monitors the devices of PLC 1. The devices displayed on the programmable display 50 are not known on the PLC 1 side. For this reason, the display side communication unit 58 of the programmable display 50 accesses the PLC 1 at regular intervals (e.g., 10 ms) and reads out the device values of the devices used in the display data (step S4501). The read out device values are stored in the data memory 56 of the programmable display 50.

Then, the display processing unit 51 of the programmable display unit 50 determines whether the read device values have changed from the current device values (step S4502). If they have not changed, the current screen can be maintained as is, and nothing in particular is done. On the other hand, if they have changed, display data is generated using the read device values, and the display content is updated using the read device values (step S4503).

The above is the basic processing operation. Note that while the focus here is on reading device values, writing device values is also performed in communication with the PLC 1, such as by touching a switch component. In other words, when a device whose device value has changed is recognized in the data memory 56 of the programmable display 50, that information is sent to the PLC 1 side by communication with the PLC 1, and the CPU unit processing unit 31 performs processing to write the information to the PLC side device unit 34 of the CPU unit memory unit 32.

Figure 2 is a user interface screen of the monitoring screen 240. The monitoring screen 240 of Figure 2 can be displayed by touching the "Monitoring screen" button 144 in the menu screen 140 of Figure 21 described above. Various parts such as switches, meters, and lamps are arranged on this monitoring screen 240. "ABC-123" is displayed in the production part number numerical display column 241, and this numerical display column 241 is a column to which the device of PLC1 is assigned. To the right of it, lamps 242 and 243 indicating normal or abnormal are arranged, and in the example of Figure 2, the normal lamp 242 is lit and the abnormal lamp 243 is off. The normal lamp 242 and the abnormal lamp 243 are each given a part label (part identification number) and are assigned a device and part image, respectively, and the display form of the part changes depending on the state of the device. In other words, two part images, a part image in a lit state and a part image in an unlit state, are assigned to the normal lamp 242, and which part image is displayed is determined depending on the state of the device. A temperature meter 244 is located to the right of the lamps 242 and 243, and indicates 60°C. A part label is also attached to the temperature meter 244, and a device and part image are assigned to it. The pointer of the temperature meter 244 moves according to the device value of the device.

2, a progress management table 245 for products A to D is displayed, and a set value and a current value are displayed in a numerical display field 241 for each product. A RESET switch 246 is disposed to the right of the current value. A part label is also attached to the RESET switch 246, and a device and a part image are assigned to it. The part images include an image of the RESET switch 246 pressed down, and an image of the RESET switch 246 with the finger released. A counter graph is disposed to the right of the RESET switch 246, as described above. In this manner, a part label is attached to each of the various parts, and a device and a part image are assigned to them.
[Embodiment 2]

In the above-described first embodiment, a configuration has been described in which the system screen, which is a prescribed page provided by the programmable display device 50, is switched to the device waveform display screen by a touch operation. That is, the touch detection unit 53 detects that a touch operation has been performed on a waveform display component arranged on the system screen, and the device waveform of the target device is displayed based on the time series data stored in the PLC 1. Specifically, when the user touches the "replay mode start" button 141 or the "real-time chart monitor (replay mode)" corresponding to the waveform display component on the menu screen 140 shown in FIG. 21, the device waveform display screen 160 (real-time chart monitor screen) shown in FIG. 12 is displayed, and the previously recorded driving record data is displayed in replay mode.

However, the present invention is not necessarily limited to a configuration in which the device waveform display screen is called from a page provided in advance, such as a system screen, and for example, a waveform display component for switching to the device waveform display screen may be arranged on a user screen created by the user. Such an example is shown in FIG. 46 as a user screen 250 of a programmable display device according to the second embodiment. On the user screen 250 shown in this figure, various display components created by the user are arranged. When the "replay mode start" button 251, which is a waveform display component arranged on the lower right of this user screen 250, is pressed, the device waveform display screen 160 shown in FIG. 12 is displayed. In this way, it is possible to quickly switch to the device waveform display screen 160 not only on the system screen but also on the user screen created by the user, and it becomes easy to easily call up information useful for solving a problem, and it becomes easier to move to a recovery work, improving convenience.
[Embodiment 3]

In addition, in the above-described first and second embodiments, in either the system screen or the user screen, the touch detection unit 53 detects that a touch operation has been performed on a waveform display component arranged on a page displayed on the display screen, and displays the device waveform of the target device based on the time series data stored in the PLC 1.

However, the present invention is not limited to this configuration, and may be configured to display the device waveform by detecting a predetermined special touch operation. Such an example is shown in FIG. 47 as a user screen 260 of a programmable display according to embodiment 3. The programmable display displays an arbitrary user screen 260 created by the user on the display unit. In this state, the user can call up the device waveform display screen 160 by performing a specific operation on the non-placement area NA (area indicated by diagonal lines in FIG. 47) where no display components are placed on the page. The specific operation can be, for example, a long press, flick, pinch-in, pinch-out, etc. on the non-placement area NA. Here, the device waveform display screen 160 of FIG. 12 is configured to be switched to by the user flicking the non-placement area NA upward from the state of FIG. 47. To return to the original page, a user flicks downward on any position on the display screen of FIG. 12 to return to the screen of FIG. 47. Furthermore, the screen switching operation may be assigned according to the direction of the flick on the display screen. For example, on any page, an upward flick will display the device waveform display screen 160, and a downward flick will return to the original page.

Furthermore, left and right flicks may be assigned to page switching operations. For example, flicking to the right will display a page with a screen ID that is incremented by one (the next page), and flicking to the left will display a page with a screen ID that is decremented by one (the previous page). By configuring in this way, it is possible to switch to different pages depending on the direction of the flick, allowing the user to intuitively switch pages with simple operations, improving convenience.

In the above example, the condition for switching the device waveform display screen is a touch operation on a non-placement area, but the present invention is not limited to this, and the device waveform display screen may be switched including an area where a display component is placed. For example, in the case of a flick operation, even if the position touched by the user with a finger or the like is an even-even placement area where a display component is placed, it is not considered to be an operation on the display component, so that it can be distinguished from an operation that the user consciously selects on the display component, such as a normal tap or long press.
[Embodiment 4]

Furthermore, in the above-mentioned embodiments 1 to 3, the configuration in which the display content of the display unit 55 is switched to the device waveform display screen 160 has been described. However, the present invention may be configured to display the device waveform on a page such as a system screen or a user screen without necessarily switching to a dedicated device waveform display screen. Such an example is shown in FIG. 48 as a user screen 270 of a programmable display according to embodiment 4. Here, as one of the display components that the user can select and arrange, a waveform area display component 271 having a waveform display area for displaying the device waveform is provided in the display component itself. The user screen shown in FIG. 48 shows an example in which the waveform area display component 271 is arranged in the lower right. The waveform area display component 271 has a relatively large size of the display component to ensure a waveform display area in which the device waveform is displayed at a size that can be seen. The display data generating unit 51a displays the operation record data acquired from the PLC 1 as a device waveform in the waveform display area of the waveform area display component 271. The device waveform displayed in the waveform area display component 271 can be displayed as a moving image, or the waveform at a specific time can be displayed as a still image.

The waveform area display component 271 may also have a function for selecting the device to be displayed as the device waveform and changing the time to be displayed. For example, in the example of FIG. 48, a "Details" button 272 is provided, and touching this "Details" button 272 may display a device selection menu or a slider-shaped operation bar representing the time axis. Alternatively, touching the "Details" button 272 may display a real-time chart monitor in replay mode as shown in FIG. 12.

In this way, by making it possible to easily check the device waveforms when a problem occurs on the programmable display 50, when a problem occurs, it becomes possible for on-site personnel to check and consider a solution on the spot for problems that can be solved without having to ask the engineer who designed the FA system program for analysis. This shortens the time it takes to recover from the problem. In addition, the device waveforms of the necessary devices can be selectively displayed, which can be useful in identifying the cause of the problem.
[Embodiment 5]

The programmable display device according to the present invention may also be configured to guide the user on how to deal with problems when they occur. For example, a guidance display screen may be prepared and a method for dealing with problems when they occur may be displayed to guide the user. Such an example will be described with reference to FIG. 49 as a programmable display device according to embodiment 5. FIG. 49 is a schematic diagram showing an example of a switch setting screen 120B displayed on a screen data creation device constituting a programmable logic controller system. Note that the switch setting screen 120B in FIG. 49 may be configured to be displayed when "replay mode start" is selected in the switch function selection field 121 on the switch setting screen 120 of the screen data creation device shown in FIG. 14.

When the "RTCM" tab 125a is clicked in the real-time chart monitor (replay mode) detailed settings field 124 on the switch setting screen 120B in FIG. 49, the contents corresponding to the detailed settings of the real-time chart monitor (replay mode) in FIG. 15 are displayed. The switch setting screen 120B shown in FIG. 49 also shows the state in which the "Guidance" tab 125b is clicked in the real-time chart monitor (replay mode) detailed settings field 124.

In FIG. 49, the real-time chart monitor (replay mode) detailed setting field 124 has a content specification field 124A, a message block No. specification field 124B, and a block No. field 124C. In the content specification field 124A, a message or an image is selected. Here, an example is shown in which a message is selected. In the message block No. specification field 124B, internal and external designations can be selected, and here, an example is shown in which internal designation is selected. When internal designation is selected, 0 is selected in the block No. field 124C as the block No. to be used. Then, the guidance message display field 124D provided below the real-time chart monitor (replay mode) detailed setting field 124 displays the guidance message that has already been input (the field is blank in the initial state). The display content of the guidance message on the programmable display device 50 can be edited by clicking the message edit button 129.

In this way, if a guidance message is set in advance from the screen of FIG. 49 in association with the "Replay mode start" button 141b shown in the menu screen displayed in the screen display area 112 of FIG. 13, the device waveform display screen 160C shown in FIG. 50 is displayed in a pop-up display (floating window display) 280 on the replay mode screen shown in FIG. 12 on the programmable display 50 during operation. In other words, this guidance message is an example of guidance information for instructing a method of dealing with an error event when a storage condition is met. This guidance information is associated with a device (DM100, DM200, R000) that is set in advance to display the device waveform, as shown in FIG. 16, for example. Then, when the "Replay mode start" button 141b is clicked in FIG. 13, display data for displaying this guidance information is generated, so that the device waveform display screen 160C of FIG. 50 displays the guidance message together with the device waveform.

Figure 50 is a schematic diagram showing a modified example of the device waveform display screen in replay mode. As shown in this figure, the guidance message set in the switch setting screen 120B in Figure 49 is displayed as a pop-up in the foreground of the device waveform display screen 160C. In Figure 50, when the "Real-time chart monitor" tab 161 is selected, it is displayed superimposed on the device waveform. In particular, among the guidance messages displayed in the pop-up display 280 shown in Figure 50, 3. displays a message such as "Please check the situation around the last ON in the device waveform of R000 with a camera." On-site personnel who see this display can attempt to solve the problem by checking the situation around the last ON in the device waveform of R000 with a camera.

For example, when an image is selected in the content specification field 124A in FIG. 49, a file number specification field is displayed instead of the message block number specification field 124B. This file number specification field is a field for specifying a specific image file. In the file number specification field, the file name of an image file located in a specific directory may be specified, an identifier for identifying a specific image file may be specified, or a path indicating the location where the image file is stored may be specified. In this case, the image specified in the file number specification field is displayed in a pop-up display 280 in FIG. 50 instead of a guidance message. The image file is created in advance by the user, and may include a message as shown in the pop-up display 280 in FIG. 49 or an illustration that guides the user on how to deal with a problem when it occurs.

For example, if external designation is selected in the message block number designation field 124B in FIG. 49, the device value of a specific device in the PLC can be referenced and the message block number can be dynamically designated with the device value currently in operation. This is the same as the external designation described in the RTCMID designation method in the "RTCMID designation method" field 126 in FIG. 33.

Note that while FIG. 34C shows a schematic diagram of a data structure in which the RTCMID and device are linked, the message block number and device are also linked (associated) when the settings shown in FIG. 49 are made. That is, for example, the message block number = 0 explained using FIG. 49 is associated with the specified device DM300 = 0 in addition to the RTCMID = 0. Similarly, the file number and device are linked (associated) when an image is selected in the content designation.

In addition, a selection field for switching between displaying and hiding the guidance display may be provided in the switch setting screen 120B shown in FIG. 49. In this case, if the user selects not to display the guidance display, the guidance message shown in the pop-up display 280 in FIG. 50 will not be displayed.

In the above embodiment, when the storage conditions are satisfied in the PLC 1, the programmable display 50 is configured to acquire the driving record data stored in the storage memory 36 of the PLC 1. At this time, an e-mail indicating that the driving record data has been acquired may be automatically sent to a predetermined specific address (so-called e-mail notification function). This allows, for example, a field staff member to know that some abnormality has occurred in the production line. In addition, when this e-mail is sent to the outside, the driving record data may be automatically attached. Furthermore, if the data volume of the driving record data is large, it may be divided into multiple driving record data, and multiple e-mails with each driving record data attached may be sent in sequence. It may also be configured to send the data with screen capture image data attached. This allows, for example, a system designer to not only know that an abnormality has occurred, but also receive the driving record data and analyze the cause.

The programmable display device and the programmable logic controller system equipped with the programmable display device according to the present invention can be suitably used for troubleshooting, or the investigation of the cause of problems that occur in FA systems.

1...PLC
2...PC
3...CPU unit 4, 4a, 4b...Expansion unit 4c...Camera unit 4d...Motion unit 4e...Communication unit 4f...I/O unit 5...PLC side display unit 6...PLC side operation unit 7...Display unit 8...PC side operation unit 9...Communication cable 10, 10a, 10b...Field device 11...PC side memory unit 21, 21B...PC side CPU
22...PC side storage device 23...PC side communication section 31...CPU unit processing section 32...CPU unit storage section 33...PLC side communication section 34...PLC side device section 34a...CPU unit device section; 34b...Expansion unit device section 35...Project storage section 36...Storage memory; 36A...Memory card 37...Internal memory 38...Bus master 39...Recording control section 39C...Storage control section 40...Program execution section 41...Expansion unit processing section 41c...Camera unit processing section 41d...Motion unit processing section 41e...Communication unit processing section 41f...I/O unit processing section 42...Expansion unit memory 45...Storage condition setting section 47...Program receiving section 50...Programmable display 51...Display processing section; 51a...Display data generation section; 51b...Drive record data interpretation section 52...Settings storage section; 52a...Parts setting; 52b...Page setting;
52c...target device setting; 52d...acquired device setting; 52f...system default screen information 53...touch detection unit 55...display unit 56...data memory; 56a...display device unit 57...screen data receiving unit 58...display device communication unit 60...screen data creation device 61...screen data creation unit 62...screen data creation side storage unit 63...screen data creation side input unit 65...screen data creation side display unit 67...screen data transfer unit 70...program creation device 71...project data 72...log setting data 73...log data 74...program creation side input unit 75...program creation side display unit 76...program creation side storage unit 77...program creation unit 78...program transfer unit 80b...unit control unit 81...recording unit 82...detection Notification unit 83a...time management unit 83b...time management unit 84...output unit 90...inter-unit bus 91a...temporary recording unit; 91b...ring buffer 92b...collection unit 92a...collection unit 93...storage unit 94...transmission unit 95...time information buffer 96...function execution unit 96a...image reception unit 97...external interface 98...camera unit 110...page setting screen 111...screen selection field 112...screen display field 113..."screen" tab 114..."system setting" tab 120, 120B...switch setting screen 121...switch function selection field 122...initial display screen selection field 123...driving record data selection field 124...real-time chart monitor (replay mode) detailed setting field 124A...content designation field; 124B...message block No. designation field;
124C: Block No. column; 124D: Guidance message display column 125a: “RTCM” tab; 125b: “Guidance” tab 126: “Screen ID designation method” column 127: Location selection column 128: Device name selection column 129: Message edit button 130: System setting screens 130A, 130B, 130C, 130D: User screen 131: Page switching component 132: “Next page” button 133: “→” button 134: “←” button 135: “△” button 136: “▽” button 137: Page number display column 138: “Move” button 139: Thumbnail screen 140 ... Menu screens 141, 141b... "Replay mode start" button 142... "Real-time chart monitor (replay mode)" button 143... "Real-time chart monitor (monitor mode)" button 144... "Monitoring screen" button 150... Initial screens of replay mode 160, 160B, 160C... Device waveform display screen 161... "Real-time chart monitor" tab 162... "Camera/event" tab 163... "Viewer" tab 164... "Unit" tab 165... "Program" tab 166... "X" button 170... Camera/event Event display screen 171...Event/error history column 172...Camera image display column 180...Viewer display screen 181..."Check waveform" button 190, 190B...Unit display screen 191..."Details" button 200...Program display screen 201...Inter-unit communication 202...Program execution 204...END processing 206...Ladder diagram display column 207...Unit configuration display column 208...Ladder program display column 210...Device waveform display screen 220...Target device setting screen 221...Unit selection column 230...Initial display screen setting section 240...Monitoring screen 241...Numerical value display column 242...Normal lamp 243...Abnormal lamp 244...Temperature meter 245...Progress management table 246...RESET switch 250...User screen 251..."Start replay mode" button 260...User screen 270...User screen 271...Waveform area display component 272..."Details" button 280...Pop-up display 321...Program display module 322...Waveform display module 323...Image display module 324...Playback control module 325...Unit display module 326...Event display module 327...Viewer display module 330a...Time UI
331a...display time control unit 332...program display unit 333a...device value acquisition unit 334...collation unit 335...warning unit 402...playback control field 404, 404a...time designation cursor 406...play button 407...one-step reverse play button 408...one-step play button 409...time display area 410...program display area 420...project display area 430...camera monitor 440...unit monitor 450...ladder monitor 520...image recording unit 530...camera setting information storage unit 550...camera connection cable 575...camera setting recording unit 1000...programmable logic controller system 130 0...User interface screen WK...Object MT...Motor; SS...Input/output device FP...Functional part IA...Screen ID display field Ld...Ladder diagram d1 to d10...Device value CL...Communication lines i1 to i3...Work image j1 to j3...Work image ST...Scan time IL...Identification line NA...Non-placement area TX, TX1, TX2, TX3, TX4, TX5, TX6, TX7...Text part CP...Character display part RP, RP1, RP2...Lamp part MP...Meter part NP...Numerical display part SP...Switch part GP...Graph part IX...Image information EV...Event group UL...Unit configuration UG...Buffer memory DP...Display data

Claims (17)

A programmable display connected to a programmable logic controller, which collects device values of a plurality of devices that are storage areas referenced by a user program, associates information relating to the acquisition time of the device values with the device values and temporarily records them in chronological order, and when a predetermined storage condition is satisfied, stores in a storage memory the temporarily recorded time-series data relating to the device values of the plurality of devices,
a part setting in which a screen on which a plurality of parts for monitoring or changing the state of a device of the programmable logic controller are arranged is regarded as a page, and the device is assigned to each of the parts arranged on the screen;
A page setting for managing the part setting on a page basis using a page identifier that identifies a plurality of different pages; and
a setting storage unit that stores a target device setting for identifying a target device among the plurality of devices for displaying a device waveform in which the time-series data stored in the storage memory of the programmable logic controller is represented as a waveform shape based on a user designation; and
a display data generating unit that generates display data for each page corresponding to the plurality of different page identifiers based on the part settings and page settings stored in the setting storage unit;
a display unit including a display screen, the display unit displaying a page corresponding to the page identifier on the display screen based on the display data generated by the display data generating unit;
a touch detection unit that detects a touch operation on the display screen of the display unit;
Equipped with
The display data generating unit
When a first touch operation set in advance is detected by the touch detection unit on the display screen, display data for switching from a current page to another page is generated based on the page setting, and
when a second touch operation that is set in advance is detected by the touch detection unit on the display screen, generating display data for displaying the device waveform of a device specified by the target device setting based on the time-series data stored in the programmable logic controller and the target device setting stored in the setting storage unit ;
The display unit is configured to display the other page or the device waveform on the display screen based on the display data generated by the display data generating unit. 2. The programmable display according to claim 1,
the setting storage unit stores default screen information indicating a default screen having a predetermined format for displaying the device waveform;
The display data generating unit
When the touch detection unit detects the second predetermined touch operation on the display screen, the programmable display generates display data for displaying the device waveform of the device specified by the target device setting by overlaying the time series data on the default screen based on the default screen information and the time series data. 3. The programmable display according to claim 2,
The display data generating unit
When the touch detection unit detects a change operation for changing a display range of the device waveform while the device waveform is displayed on the display screen by the display unit, the programmable display device generates display data for displaying the device waveform in the changed display range by extracting time series data from the time series data that corresponds to the changed display range specified by the change operation. The programmable display according to any one of claims 1 to 3,
The part settings stored in the setting storage unit further include:
Setting a waveform display component for displaying the device waveform;
A programmable display device, wherein the second touch operation is a touch operation on the waveform display component arranged on a first page displayed on the display screen. The programmable display according to any one of claims 1 to 3,
A programmable display device in which the second touch operation is a specific operation on a non-placement area other than the area in which the component is placed on the first page displayed on the display screen. 6. The programmable display according to claim 5,
A programmable display device, wherein the specific operation is any one of a long press, a flick, a pinch-in, and a pinch-out on the non-location area. A programmable display according to any one of claims 1 to 6,
The part settings stored in the setting storage unit further include
Setting an acquisition device for repeatedly acquiring time-series data of device values temporarily recorded in a temporary recording unit of the programmable logic controller;
Setting a real-time display component for sequentially displaying the time series data of the acquisition device;
The programmable display device is configured so that, when a touch operation on the real-time display component is detected, the display data generation unit generates display data for sequentially displaying the device values of the acquired device on the display screen based on the time series data of the device values temporarily recorded in the temporary recording unit of the programmable logic controller. A programmable display according to any one of claims 1 to 7,
A programmable display configured such that, when predetermined storage conditions are met, image data input from an external camera connected to the programmable logic controller is temporarily stored in the programmable logic controller in association with information regarding the acquisition time when the image data was acquired, and the programmable display acquires driving record data including log data stored in the storage memory while the programmable logic controller is operating , and displays an image based on the image data included in the driving record data on the display unit based on the information regarding the acquisition time included in the driving record data. A programmable display according to any one of claims 1 to 8,
When a predetermined storage condition is satisfied, the user program executed by the programmable logic controller at the time the storage condition is satisfied is stored in association with driving record data including log data stored in the storage memory during operation of the programmable logic controller ,
The programmable display is configured to acquire the stored driving record data from the programmable logic controller, and based on information regarding the acquisition time contained in the driving record data, display a device value corresponding to the acquisition time on the display unit on a user program contained in the driving record data. A programmable display according to any one of claims 1 to 9,
A programmable display device configured to collect event data corresponding to a plurality of events that occur in the programmable logic controller or a controlled device controlled by the programmable logic controller, and store the event data in chronological order in association with the occurrence time of the events.When a predetermined storage condition is satisfied, the stored event data is stored as part of driving record data so that the stored event data is associated with the driving record data including log data stored in the storage memory during operation of the programmable logic controller , and the programmable display device is configured to acquire the stored driving record data and display an event corresponding to the event data included in the driving record data on the display unit based on the occurrence time included in the driving record data. A programmable display according to any one of claims 1 to 10,
A programmable display capable of displaying a selection screen for selecting the target device as an initial display when the device waveform is displayed on the display screen. A programmable display according to any one of claims 1 to 11,
A programmable display that, when displaying the device waveform on the display screen, is capable of displaying one or more target devices based on identification information for specifying the one or more target devices to be displayed. A programmable display according to any one of claims 1 to 12,
A programmable display capable of displaying one or more target devices and a setting screen for setting the display format thereof when the device waveform is displayed on the display screen. The programmable display according to any one of claims 1 to 13, further comprising:
A programmable display device comprising a display device side communication unit that communicates with the programmable logic controller. 15. The programmable display according to claim 14, further comprising:
a programmable display including a display-side device section that communicates with the programmable logic controller via the display-side communication section and holds a device value synchronized with a device value of the programmable logic controller; The programmable display according to any one of claims 1 to 15, further comprising:
a guidance information storage unit that stores guidance information associated with the device specified by the target device setting, the guidance information providing guidance for resolving an error event when the storage condition is satisfied;
The display data generating unit
a programmable display configured to generate display data for displaying guidance information stored in the guidance information storage unit and associated with a device identified by the target device setting when the touch detection unit detects the second touch operation on the display screen. a programmable logic controller that collects device values of a plurality of devices that are storage areas referenced by a user program, associates information relating to the acquisition time of the device values with the device values and temporarily records them in chronological order, and when a predetermined storage condition is satisfied, stores the temporarily recorded time-series data relating to the device values of the plurality of devices in a storage memory ;
a programmable display connected to the programmable logic controller,
The programmable logic controller includes:
a program execution unit that repeatedly executes a user program;
a device unit having a device which is a storage area referenced by the program execution unit;
a temporary recording unit that collects device values of the devices stored in the device unit, and temporarily records the device values in chronological order in association with information on the acquisition time of the device values;
a storage memory for storing the time series data relating to the device values temporarily recorded in the temporary recording unit as driving record data when a predetermined storage condition is satisfied,
The programmable display comprises:
a part setting in which a screen on which a plurality of parts for monitoring or changing the state of a device of the programmable logic controller are arranged is regarded as a page, and the device is assigned to each of the parts arranged on the screen;
A page setting for managing the part setting on a page basis using a page identifier that identifies a plurality of different pages; and
a setting storage unit that stores a target device setting for identifying a target device among the plurality of devices for displaying a device waveform in which the time-series data stored in the storage memory of the programmable logic controller is represented as a waveform shape based on a user designation; and
a display data generating unit that generates display data for each page corresponding to the plurality of different page identifiers based on the part settings and page settings stored in the setting storage unit;
a display unit including a display screen, the display unit displaying a page corresponding to the page identifier on the display screen based on the display data generated by the display data generating unit;
a touch detection unit that detects a touch operation on the display screen of the display unit;
Equipped with
The display data generating unit
When a first touch operation set in advance is detected by the touch detection unit on the display screen, display data for switching from a current page to another page is generated based on the page setting, and
when a second touch operation that is set in advance is detected by the touch detection unit on the display screen, generating display data for displaying the device waveform of a device specified by the target device setting based on the time-series data stored in the programmable logic controller and the target device setting stored in the setting storage unit ;
The display unit is configured to display the other page or the device waveform on the display screen based on the display data generated by the display data generation unit.

Images