JP2023164999A - Program creation assistance device for programmable logic controller - Google Patents

Abstract

To acquire a log of an event useful for solving a trouble.SOLUTION: A program creation assistance device includes: an event display control unit 14 that lists and displays, on a display unit 7, a plurality of events included in event data read from an operation-record-data holding unit 22b and respective occurrence times of the plurality of events; a selection receiving unit 16 that receives one selection from the plurality of events listed and displayed by the event display control unit 14; and a device display control unit 13 that superimposes and displays, on a user program, a device value that is included in log data read from the operation-record-data holding unit 22b and is recorded at a time corresponding to an occurrence time of an event selected by the selection receiving unit 16. The event display control unit 14 selectively lists and displays, on the display unit 7, specific events that change an operating state of a PLC 1 or an operating state of a device to be controlled by the PLC 1.SELECTED DRAWING: Figure 6

Description

The present invention relates to a program creation support device for a programmable logic controller.

A programmable logic controller (hereinafter referred to as "PLC") is a controller that controls manufacturing equipment, transport equipment, and inspection equipment in factory automation (FA). The PLC controls various expansion units and controlled devices by executing user programs such as ladder programs created by the user. When a user program is actually executed on a PLC, a phenomenon that was not anticipated when the user program was created may be discovered, and the user program may need to be modified. The user not only reviews the user program to identify correction points, but also refers to the log data generated by the PLC. Log data stores device values (device values) collected while a user program is running. In the field of PLC, a device means a storage area that stores information. Devices include relay devices that hold one bit of information, word devices that hold one word of information, and the like.

In order to perform sequence control in the FA field, we design programs for PLC and application programs for program editing. After designing a program, the designer simulates the sequence operation of the program, debugs the program while verifying the simulation results, and transfers the completed program to the PLC for execution. However, it is not always possible to realize the expected operation, and the program must be edited, such as debugging it again, based on actual operation. In particular, if the expected behavior is not achieved during actual operation, it is important to identify the cause and the event that caused the problem. For example, operations may be stopped for reasons other than the program design (for example, control may be stopped due to unexpected work flowing on the line).

Apart from such a technique of storing device values, a technique of storing an event log (for example, when a failure occurs) is known (for example, Patent Document 1).

However, since there are a large number of saved event log types (on the order of 1,000 types), there is a problem in that if important event logs are buried, it takes time for the user to search for the cause of a problem, making it inconvenient to use. On the other hand, it is conceivable that the user narrows down the event logs to be saved in advance, but it is difficult to select the events to be saved, and there is a risk that events useful for troubleshooting may not be saved.

JP2003-029829A

One object of the present invention is to provide a program creation support device for a programmable logic controller that is capable of acquiring event logs useful for troubleshooting.

Means for solving the problem and effects of the invention

According to the program creation support device for a programmable logic controller according to the first aspect of the present invention, the programmable logic controller is composed of one or more units, and includes a program execution section that repeatedly executes a user program, and a program execution section that repeatedly executes a user program. A device unit that has a device that is a referenced storage area, records device values stored in the device unit in chronological order as log data together with the current time, and is controlled by the programmable logic controller or the programmable logic controller. A temporary recording section that records multiple events occurring in the controlled device in chronological order as event data together with the time of occurrence, and log data and log data recorded in the temporary recording section when predetermined storage conditions are met during operation. A program creation support device for supporting the creation of the user program written in a graphical programming language, which is executed in the programmable logic controller and includes a storage memory for storing event data, the program creation support device comprising: a storage memory for storing event data; a driving record data holding unit that stores the log data and event data stored in the storage memory as driving record data; a display unit that displays the user program; and an event data read out from the driving record data holding unit. an event display control section that displays a list of a plurality of events and the times of occurrence of each of the plurality of events on the display section; and a selection of one from among the plurality of events displayed as a list by the event display control section. A selection reception unit and a device value recorded at a time that is included in the log data read from the driving record data storage unit and that corresponds to the time of occurrence of the event selected by the selection reception unit are displayed on the user program. and a device display control section that displays a specific event that changes the operating state of the programmable logic controller or the operating state of a controlled device controlled by the programmable logic controller. It can be configured to selectively display a list on the display section. With the above configuration, events useful for troubleshooting can be selectively displayed from among a wide variety of events, and can be useful for investigating the cause of troubles.

Further, according to the program creation support device for a programmable logic controller according to the second aspect, in addition to the above configuration, further:
Accordingly, it is possible to further include a recording setting section that configures the temporary recording section of the programmable logic controller to record only the specific event among the plurality of events.

Furthermore, according to the program creation support device for a programmable logic controller according to a third aspect, in addition to any of the above configurations, the specific event is executed by the user independently of the execution of the user program by the program execution unit. It can contain events related to operations performed.

Furthermore, according to the program creation support device for a programmable logic controller according to a fourth aspect, in addition to any of the above configurations, the event related to the user operation is configured to include at least configuration information of the user program and the programmable logic controller. rewriting project data including rewriting the project data, switching the mode between a setting mode in which the programmable logic controller is configured and an operation mode in which the user program is executed on the programmable logic controller, insertion and removal of a cable connectable to the programmable logic controller, This may include inserting and removing a storage medium that can be attached to the programmable logic controller, and turning on and off the power of the controlled device.

Furthermore, according to the program creation support device for a programmable logic controller according to a fifth aspect, in addition to any of the above configurations, the event display control section may cause the event display control section to display the program according to the execution of the user program by the program execution section. Events corresponding to processing automatically executed within the programmable logic controller can be hidden.

Furthermore, according to the program creation support device for a programmable logic controller according to the sixth aspect, in addition to any of the above configurations, an event corresponding to the automatically executed process is at least connected to the programmable logic controller. This may include starting or terminating communication when establishing a TCP connection or FTP connection with an external device that has been installed, and writing to a folder or file prepared in the programmable logic controller.

Furthermore, according to the program creation support device for a programmable logic controller according to the seventh aspect, in addition to any of the above configurations, the display target time in the device display control section and the display in the event display control section are further provided. A synchronization software module is provided for synchronizing the target time, and the synchronization software module can display the device display control section and the event display control section in conjunction with each other on the display section.

Furthermore, according to the program creation support device for a programmable logic controller according to the eighth aspect, in addition to any of the above configurations, the display section includes an event display field for displaying a list of events, and the user program. and a ladder monitor column for displaying a ladder diagram, and when an arbitrary event is selected from the event display column in the selection reception section, a ladder diagram corresponding to the time of the selected event is displayed in the ladder monitor column. Can be configured to be selected and displayed.

Furthermore, according to the program creation support device for a programmable logic controller according to the ninth aspect, in addition to any of the above configurations, the storage device can be an SD card (product name).

Furthermore, according to the program creation support device for a programmable logic controller according to the tenth aspect, in addition to any of the above configurations, the event display control section displays device values as a time series waveform on the display section. be able to.

1 is a conceptual diagram of a programmable logic controller system. FIG. 1 is a diagram showing a programmable logic controller system. It is a diagram explaining a ladder program. FIG. 2 is a diagram illustrating a program creation support device. It is a figure explaining PLC. FIG. 3 is a diagram illustrating scanning of a ladder program. FIG. 2 is a block diagram showing a program creation support device. It is an explanatory view showing association of driving record data and project data. FIG. 3 is a diagram illustrating a user interface. FIG. 3 is an image diagram showing a GUI screen of a user program creation support program in history playback mode. FIG. 3 is an image diagram showing a GUI screen of a user program creation support program in recording mode. It is an image diagram showing an example of a mode selection column. FIG. 2 is an image diagram of a GUI showing how a ladder program is edited. 14 is an image diagram of an editing screen displayed from the state of FIG. 13. FIG. FIG. 15 is an image diagram showing a ladder program in which the edits shown in FIG. 14 are reflected; FIG. 2 is an image diagram of a GUI of a user program creation support program showing how device values are edited. FIG. 2 is an image diagram of a GUI showing a project save screen. FIG. 3 is an image diagram showing a “save project under a different name” dialog screen. 12 is a flowchart illustrating an example of "overwrite storage prohibition" processing. 12 is a flowchart illustrating an example of a "save as new project data" process. FIG. 3 is an image diagram of a GUI screen showing a project data matching function. FIG. 3 is an image diagram of a GUI screen showing an example of a comparison result. It is a figure explaining the function of a program creation support device. It is a figure explaining the function of a CPU unit. FIG. 3 is a diagram illustrating a process for creating unit configuration information. 3 is a flowchart showing an overview of debugging processing. FIG. 3 is a diagram illustrating a project creation section. It is a figure explaining a log display control part. It is a figure explaining a program display module. FIG. 3 is a diagram illustrating a display module for project data and log data. FIG. 3 is a diagram illustrating a reproduction control module. FIG. 2 is a diagram illustrating a UI that displays a user program and device values. 3 is a flowchart showing a process for displaying a user program and device values. 7 is a flowchart showing a process for displaying a waveform of a device value. 3 is a flowchart showing playback control. FIG. 2 is a block diagram showing an example of a PLC engineering tool. FIG. 2 is a block diagram regarding an event log function of the programmable logic controller system. 3 is a flowchart showing an operation for recording events occurring in a CPU unit. 3 is a flowchart showing an operation for recording events occurring in an expansion unit. 3 is a flowchart showing a filter operation when displaying an event log. FIG. 3 is an image diagram showing a setting screen for setting display filtering. FIG. 2 is an image diagram showing a GUI of an engineering tool for a programmable logic controller according to an embodiment. FIG. 3 is an image diagram of a GUI in which the cursors of operation bars overlap. It is an image diagram of GUI. It is an image diagram of GUI. FIG. 2 is an image diagram showing a GUI of an engineering tool for a programmable logic controller having a camera monitor field.

Embodiments of the present invention will be described below based on the drawings. However, the embodiment shown below is an illustration for embodying the technical idea of the present invention, and the present invention is not limited to the following. Moreover, this specification does not in any way specify the members shown in the claims to the members of the embodiments. In particular, the dimensions, materials, shapes, relative arrangements, etc. of the components described in the embodiments are not intended to limit the scope of the present invention, unless otherwise specified, and are merely illustrative examples. It's nothing more than that. Note that the sizes, positional relationships, etc. of members shown in each drawing may be exaggerated for clarity of explanation. Furthermore, in the following description, the same names and symbols indicate the same or homogeneous members, and detailed descriptions will be omitted as appropriate. Furthermore, each element constituting the present invention may be configured so that a plurality of elements are made of the same member so that one member serves as a plurality of elements, or conversely, the function of one member may be performed by a plurality of members. It can also be accomplished by sharing.

FIG. 1 shows a schematic diagram of a programmable logic controller system. A programmable logic controller system 1000 shown in this figure exemplifies a system in which an object WK flowing on a line is imaged by a camera unit 98 and inspected. This programmable logic controller system 1000 is connected to the PC 2 and edits a project data editing program.

The programmable logic controller 1 is configured by connecting a plurality of units. The plurality of units are communicably connected 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 basic unit, and performs basic operations of the programmable logic controller. Further, the expansion unit 4 is a function expansion unit that expands the functions of the CPU unit 3. In the example of FIG. 1, the expansion unit 4 includes a camera input expansion unit 4c, a motion unit 4d, and a communication unit 4e. A camera input expansion unit 4c, which is one type of expansion unit 4, is connected to the camera section 98, takes an image of the object WK at a predetermined timing, and sends it to the CPU unit. The motion unit 4d is also called a positioning unit and controls the position of a controlled object called an axis. Generally, a drive source such as a motor exists for each axis. The communication unit 4e communicates with external equipment. The CPU unit 3 also collects data from these expansion units 4 and performs necessary control.
<System configuration>

Here, in order to help those skilled in the art better understand the programmable logic controller (hereinafter also referred to as "PLC"), the configuration and operation of a typical PLC will be described.

FIG. 2 is a conceptual diagram showing a configuration example of a programmable logic controller system according to an embodiment of the present invention. As shown in FIG. 2, this system includes a PC 2 for editing user programs such as ladder programs, and a PLC 1 for comprehensively controlling various control devices installed in a factory or the like. PC is an abbreviation for personal computer. The user program may be created using a graphical programming language such as a flowchart-style motion program such as a ladder language or 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 is assumed to be 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 can be attached to and detached from the CPU unit 3. For example, the extension unit 4a may be a positioning unit that positions a workpiece by driving a motor (field device 10a), and the extension unit 4b may be a counter unit. The counter unit counts signals from an encoder (field device 10b) such as a manual pulser. Note that the letters a, b, c, etc. appended to the end of the reference numerals may be omitted. Note that a system including PLC1 and PC2 may be called a programmable logic controller system.

The CPU unit 3 is equipped with a PLC side display section 5 and a PLC side operation section 6. The PLC side display section 5 can display the operating status of each expansion unit 4 attached to the CPU unit 3. The PLC side display section 5 switches the display contents according to the operation contents of the PLC side operation section 6. Further, the PLC-side operation section 6 may be a button or the like integrated with the CPU unit 3, or may be an external console, a mouse, a keyboard, or other input device. Alternatively, the PLC-side display section 5 can also be used as a touch panel to function as an operation section.

The PLC-side display unit 5 normally displays current values (device values) of devices within the PLC 1, error information that has occurred within the PLC 1, and the like. A device is a name indicating an area on a memory provided for storing device values (device data), and may also be called a device memory. The device value is information indicating the input state from the input device, the output state to the output device, and the state of internal relays (auxiliary relays), timers, counters, data memories, etc. set on the user program. There are two types of device values: bit type and word type. A bit device stores a 1-bit device value. A word device stores one word of device value.

The expansion unit 4 is prepared to expand the functions of the PLC 1. Each expansion unit 4 is connected to a field device (controlled device) 10 corresponding to the function of the expansion unit 4, and thereby 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 may be an output device such as an actuator. Further, a plurality of field devices may be connected to one expansion unit 4.
(Engineering tool for programmable logic controllers)

The PC 2 realizes an engineering tool for programmable logic controllers (hereinafter also referred to as "PLC engineering tool"). The PLC engineering tool is a member that connects to the PLC 1 to perform settings, control during operation, and operation confirmation. It is also possible to create various programs for operating the PLC 1 and the programmable logic controller system including this, and to edit and modify already created programs. In this sense, it may also be called a program creation support device. Furthermore, the PLC engineering tool can also reproduce the operational status of each device at that time based on operation record data that records the past operation of the programmable logic controller system. Operation record data includes user programs such as ladder programs, project data that includes setting data such as unit configuration information for each unit, and logs that are operational data such as device values of each device at the time of operation and image data of the camera unit. Contains data. This PLC engineering tool can also read and edit project data from the driving record data. In this sense, the PLC engineering tool may be called a project data editing program.

The PC 2 is, for example, a portable notebook-type or tablet-type personal computer, and includes a display section 7 and a PC-side operation section 8. A ladder program, which is an example of a user program for controlling the PLC 1, is created using the PC 2. The created ladder program is converted into a mnemonic code within the PC 2. The PC 2 is connected to the CPU unit 3 of the PLC 1 via a communication cable 9 such as a USB (Universal Serial Bus), and sends the ladder program converted into a 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 transmitted to the CPU unit 3 here, the present invention is not limited to this. For example, the PC 2 may convert the mnemonic code into an intermediate code and transmit the intermediate code to the CPU unit 3.

Although not shown in FIG. 2, the PC-side operation unit 8 of the PC 2 may include a pointing device such as a mouse connected to the PC 2. Further, 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 the USB. Alternatively, the configuration may be such that it is connected wirelessly to the CPU unit 3 of the PLC 1 without using the communication cable 9.
<Ladder program>

FIG. 3 is a diagram showing 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 plurality of cells arranged in a matrix on the display unit 7. A symbol of a virtual device is arranged in each cell. Symbols indicate input relays, output relays, etc. A relay circuit is formed by such a plurality of symbols. In the ladder diagram Ld, cells are arranged in, for example, 10 columns×N rows (N is an arbitrary natural number). Symbols of virtual devices are appropriately arranged in the cells of each row.

The relay circuit shown in FIG. 3 has symbols for three virtual devices (hereinafter referred to as "input devices") that are turned ON/OFF based on input signals from input devices, and a symbol for controlling the operation of an output device. It is configured by appropriately combining symbols of virtual devices (hereinafter referred to as "output devices") to be turned on and off.

The characters (“R0001,” “R0002,” and “R0003”) displayed above the symbol of each input device represent the device name (address name) of that input device. The characters (“flag 1,” “flag 2,” and “flag 3”) displayed below the symbol of each input device represent the device comment associated with that input device. The characters (“return to origin”) displayed above the symbol of the output device are labels consisting of a character string representing the function of the output device.

In the example shown in FIG. 3, the symbols of two input devices corresponding to device names "R0001" and "R0002" are connected in series to form an AND circuit. Furthermore, an OR circuit is constructed by connecting in parallel the symbol of the input device corresponding to the device name "R0003" to the AND circuit composed of the symbols of these two input devices. That is, in this relay circuit, the relay circuit corresponds to the symbol in the first row only when both input devices corresponding to the two symbols on the first row are turned on, or when an input device corresponding to the symbol on the second row is turned on. The output device turns on.
<Program creation support device>

FIG. 4 is a block diagram for explaining the electrical configuration of the PC 2. As shown in FIG. As shown in FIG. 4, the PC 2 includes a PC memory section 11, a PC CPU 21, a display section 7, a PC operation section 8, a PC storage device 22, and a PC communication section 23. The display unit 7, the PC-side operation unit 8, the PC-side storage device 22, and the PC-side communication unit 23 are each electrically connected to the PC-side CPU 21.

The PC-side memory unit 11 is a work memory that serves as a work space for the PC-side CPU 21 to execute processing, and is typically composed of a RAM or the like. The PC side storage device 22 realizes the function of a driving record data storage section 36B, which will be described later. The driving record data includes project data.

The PC side storage device 22 includes a hard disk, a semiconductor memory, a 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.
(project data)

The project data includes one or more user programs (for example, a ladder program), unit configuration information of the CPU unit 3 and the expansion unit 4, and the like. The project data may also include program configuration information indicating what kind of program parts the user program is composed of. Further, the unit configuration information includes information indicating the connection positions of the plurality of expansion units 4 to the CPU unit 3, functions provided in the CPU unit 3 (for example, communication function and positioning function), and functions of the expansion unit 4 (for example, shooting function). This is information indicating such things.

Here, editing the project data includes creating and changing the 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 the project data stored in the PC storage device 22 and change the project data using the project data editing program, if necessary. The PC-side communication unit 23 is for communicably 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 section 23.

The project data editing program has an editing mode, a monitor mode, and a history playback mode. The edit mode is also called an edit mode, and allows project data to be edited. Also, in the monitor mode, simulation operations can be performed for debugging the user program. Furthermore, the history playback mode is also called replay mode, time machine playback, etc., and allows playback and display. Switching between the editing mode, monitor mode, and history playback mode is performed by a mode selection section 50D, which will be described later.
<PLC1>

FIG. 5 is a block diagram for explaining the electrical configuration of the PLC 1. As shown in this figure, the CPU unit 3 includes a PLC side CPU 31, a PLC side display section 5, a PLC side operation section 6, a PLC side storage device 32, and a PLC side communication section 33. The PLC-side display section 5, the PLC-side operation section 6, the PLC-side storage device 32, and the PLC-side communication section 33 are electrically connected to the PLC-side CPU 31, respectively.
(PLC side storage device 32)

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

The project storage unit 35 stores project data input from the PC 2. The PLC side storage device 32 also stores a control program for the CPU unit 3.

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

The temporary recording section 91a records the device values stored in the device section 34 in chronological order. This temporary recording section 91a can be composed of a ring buffer or the like.

The storage memory 36 stores the device values recorded in chronological order in the temporary storage section 91a. The storage memory 36 is comprised of an internal memory 37, a removable memory card 36A, and the like as nonvolatile memory.

In this way, the PLC side storage device 32 has a plurality of storage areas. This PLC side storage device 32 may include a RAM, ROM, memory card, etc. For example, in the example shown in FIG. 5, the storage memory 36 is composed of a removable memory card 36A.
(PLC side CPU31)

The PLC side CPU 31 includes a program execution section 514, a storage condition setting section 45, a recording control section 39, and a storage control section 50C. The program execution unit 514 functions as a ladder execution engine that repeatedly executes a user program. The device unit 34, which is a storage area referenced by the program execution unit 514 according to the user program, stores each device value of a plurality of devices.

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

The storage condition setting section 45 can set, as a first trigger condition, a condition for a recording start trigger for starting recording to the temporary recording section 91a. Furthermore, the period from the 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 whose reference time is the point in time indicated by this recording trigger in the temporary recording unit 91a as log data. do. The recording control unit 39 also controls the recorded log data until the time when the second trigger condition for the save trigger is satisfied or the time when the first trigger condition for the recording trigger is satisfied, whichever is earlier. is temporarily held in the recording section 91a. Then, when the first trigger condition for the recording trigger is met, the time-series device values corresponding to the buffer recording period with the time point indicated by the recording trigger as the reference time are stored as log data in the temporary recording section 91a. Record.

The storage control unit 50C stores the log data temporarily held in the storage unit 91a by the recording control unit 39 in the storage memory 36 when the second trigger condition for the storage trigger is satisfied. Here, when the second trigger condition for the save trigger is satisfied, the save control unit 50C stores log data that is temporarily held in the recording unit 91a by the record control unit 39 and corresponds to the immediately previous record trigger from the perspective of the save trigger, into the save memory. It is preferable to store it in In this way, the storage control unit 50C retains the log data recorded during the buffer recording period even after the buffer recording period has elapsed, and when the storage trigger is activated, the log data stored in association with the recording trigger is stored. Save. However, the log data stored by the recording control unit 39 is not limited to the log data corresponding to the most recent recording trigger, but may be the two previous recording triggers or the third previous recording trigger.

As shown in FIG. 5, the CPU unit 3 and the expansion unit 4 are connected via an inter-unit bus 90, which is a type of expansion bus. Note that the communication function regarding the inter-unit bus 90 may be implemented as part of the PLC side communication section 33. Further, the PLC side communication section 33 may include a network communication circuit. The PLC-side CPU 31 may transmit log data and the like to the PC 2, the cloud, etc. via the PLC-side communication unit 33.

Here, a supplementary explanation will be given regarding the inter-unit bus 90. This inter-unit bus 90 is a bus on which input/output refresh, etc., which will be described next, is performed. Communication control on the inter-unit bus 90 is realized by a so-called bus master 38 (the bus master may be provided as a part of the PLC side communication section 33, or the bus master 38 may be provided as a part of the PLC side CPU 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 PLC side CPU 31, performs communication such as input/output refreshing, which will be described later, with the expansion unit 4. conduct.

The expansion unit 4 includes a CPU 41 and a memory 42. The CPU 41 controls the field device 10 according to instructions (device values) from the CPU unit 3 stored in the device. Further, the CPU 41 stores the control results of the field device 10 in a device called a buffer memory. The control results stored in the device are transferred to the CPU unit 3 by input/output refresh. Further, the control results stored in the device are 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 memory 42 includes RAM, ROM, etc. In particular, a storage area is reserved in the RAM to be used as a buffer memory. The memory 42 may also include a buffer that temporarily holds data (eg, still image data or video data) acquired by the field device 10.

FIG. 6 is a schematic diagram showing the scan time of the CPU unit 3. As shown in FIG. 6, one scan time T is composed of inter-unit communication 201 for refreshing input/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 PLC side storage device 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 PLC side storage device 32 within the CPU unit 3. In other words, the device value stored in the device 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. By input/output refresh in this manner, the devices of the CPU unit 3 and the devices of the expansion unit 4 are synchronized.

Note that a mechanism (inter-unit synchronization) in which device values are updated between units at a timing other than refresh may be adopted. However, the devices of the CPU unit 3 are rewritten by the CPU unit 3 at any time, and similarly, the devices of the expansion unit 4 are rewritten by the expansion unit 4 at any time. In other words, the devices of the CPU unit 3 can be accessed by devices inside the CPU unit 3 at any time. Similarly, devices in the expansion unit 4 can be accessed at any time by devices inside the expansion unit 4. The CPU unit 3 and expansion unit 4 basically update and synchronize their device values with each other at refresh timing. In program execution 202, the CPU unit 3 executes (computes) the program using the updated input data. As shown in FIG. 6, in program execution 202, a plurality of program modules or ladder programs may be executed in sequence according to project data. The CPU unit 3 processes data by executing programs. Note that the END processing refers to all processing related to peripheral services such as data communication with external devices such as a display device (not shown) connected to the PC 2 and the CPU unit 3, and system error checking.

In this way, the PC 2 creates a ladder program according to the user's operation, and transfers the created ladder program to the PLC 1. The PLC 1 considers input/output refresh, ladder program execution, and END processing as one cycle (one scan), and repeatedly executes this cycle periodically, that is, cyclically. Thereby, various output devices (motors, etc.) are controlled based on timing signals from various input devices (sensors, etc.). Note that, apart from the scan cycle, the CPU unit 3 and the expansion unit 4 each have an internal control cycle. The CPU unit 3 and expansion unit 4 control the functions of the field device 10 and the like based on the internal control cycle.
<Logging>

When a user improves or modifies a user program, the device values acquired while the PLC 1 is executing the user program may be useful. Therefore, the PLC 1 acquires a device value specified in advance and creates log data. Here, the devices managed by the PLC 1 include not only those used by the user program but also those not used by the user program. Additionally, some devices are useful for improving or modifying user programs, while others are useless. Since the number of devices is generally in the thousands, it has been a heavy burden for users to specify the devices they need. Therefore, the PC 2 analyzes the user program and extracts devices used or described in the user program as logging targets. This reduces the burden on the user.

If all devices managed by the PLC 1 are targeted for logging, the scan time will become long. This is because logging is executed as part of a user program or during input/output refresh. Sometimes, the delays caused by logging can prevent a user program from working as the user desires. Therefore, the number of devices to be logged should be maintained appropriately.

A user program may be composed of a plurality of program parts (eg, program modules (main ladder program and sub ladder program), function blocks). Of these, it may be sufficient for the user if devices related to the program component that the user desires to modify are logged. Furthermore, the user may desire to exclude a specific program component from being extracted from among a plurality of program components or to add a specific program component to be extracted. Therefore, it would be convenient for the user if devices could be added or deleted from the logging targets for each program component.

As described above, the CPU unit 3 and 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 logging targets based on these functions. For example, if an undesirable event related to the communication function of the CPU unit 3 occurs, 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.
(Program creation support device)

An example of the program creation support device is shown in the block diagram of FIG. A program creation support device 1200 shown in this figure supports creation of a user program to be executed on a PLC 1 composed of one or more units. The program creation support device 1200 may be realized by loading and executing a user program creation support program on the PC 2, or may be constructed using dedicated hardware. The example shown in FIG. 7 shows an example in which a user program creation support program is installed on the PC 2. This program creation support device 1200 includes a PC side CPU 21, a PC side memory section 11, a PC side storage device 22, a display section 7, a PC side operation section 8, and a communication section.

The PC side memory section 11 is a work space for the PC side CPU 21 to execute processing. A RAM or the like can be used as such a working memory.

The PC-side storage device 22 is a storage that can be read by the PC 2. Typically, it is a storage device such as a hard disk included in the PC 2, but it is not limited to a fixed type, and can also be a portable medium or medium. For example, the memory card 36A included in the PLC 1 may be removed from the PLC 1 side, inserted into the PC 2 side, and read. Alternatively, a mode may be adopted in which the PLC side storage device 32 of the PLC 1 connected to the PC 2 via a network is accessed.

This PC-side storage device 22 realizes the function of a driving record data storage section 36B that stores driving record data. The driving record data includes project data and log data. The project data includes a user program of the PLC 1 and unit configuration information of each unit. The unit configuration information includes information on the functions of each unit, connection positions between units, and the like. The log data is data such as device values during operation of the PLC 1. Driving record data in which these project data and log data are associated is stored in the driving record data storage section 36B.

The display unit 7 causes the log display control unit 61 to display the log. The log display control unit 61 reads the driving record data from the driving record data storage unit 36B to the PC side memory unit 11, and displays the log data and project data in the driving record data in association with each other.

The PC-side CPU 21 implements functions such as a project editing section 50B and a storage control section 50C. The project editing section 50B receives an instruction to edit the project data displayed on the display section 7 by the log display control section 61, and edits this project data. When the edited project data is saved, the project data and the corresponding log data are stored in the driving record data storage unit 36B as driving record data.

The storage control unit 50C restricts the project data in the driving record data stored in the driving record data storage unit 36B from being saved in the state edited by the project editing unit 50B. Thereby, it is possible to avoid a situation where the authenticity of the entire project data is unintentionally damaged due to the user's modification of the user program, etc. in the project data. Specifically, the storage control unit 50C prevents the project data in the driving record data stored in the driving record data storage unit 36B from being overwritten and saved in a state edited by the project editing unit 50B. For example, when the project editing section 50B detects that an attempt is made to overwrite the project data, an overwrite prohibition pop-up is displayed on the display section 7. Alternatively, when attempting to save the edited project data, the edited project data is saved as a separate file from the original project data included in the driving record data. For example, a save file name input dialog may be displayed to encourage saving under a different name, or the name may be automatically changed and a new copy may be saved.
(driving record data)

Driving record data is recorded at predetermined timing. Specifically, by specifying the time when a problem is likely to occur and storing the data during that period as driving record data, it can be used to analyze the cause of a problem when it occurs.

Driving record data can be a package of multiple files. Examples of the information included in the driving record data include management information data, project data, project identification information, device data, image data, and event data. The management information data is information about what is included in the driving record data. The extension is, for example, TMN. The project data is project data at the time of recording the driving record data (for example, when a trouble occurs). The extension is, for example, TPJ. Details will be described later.

The project identification information is information for identifying the project data at the time of recording this driving record data. The extension is, for example, TPI. The device data is data recording the devices at the time of recording the driving record data, and exists as many as the number of devices. The extension is, for example, TDV. The image data is data that records an image at the time of recording the driving record data. The extension is, for example, TCA. The event data is data recording events and errors that occurred at the time the driving record data was recorded. The extension is, for example, TEV. These are just examples, and only one of these pieces of information may be included in the driving record data, or other information may be added.
(Project data structure)

Project data consists of multiple pieces of data. If there is a large amount of data, it is preferable to save it in a compressed format. Project data can include project files, modules, function blocks, unit configuration files, email configuration files, and the like. The project file is information regarding project settings. For example, the extension is kpr. A module is information about a ladder program. The extension is, for example, mod. A function block is information of a ladder program made into components. The extension is, for example, kfb. The unit setting file is the configuration information of the unit. The extension is, for example, ue2. The email configuration file is email configuration information. The extension is, for example, mil. In addition to these, files with different extensions may be included for each unit. Further, these are just examples, and only one of these pieces of information may be included in the project data, or other information may be added.

A file extension can be used as identification information indicating the type of each data file. It is also possible to associate driving record data and project data using file extensions. For example, a TMN file for driving record data and a kpr file for project data are each associated with the user program creation support program on the PC 2. By double-clicking the corresponding file on the PC 2, the user program creation support program is started. This situation is shown in FIG. Here, the project editing section 50B of the user program creation support program includes an identification information interpretation section. Here, a TPJ interpreter 50B1 and a kpr interpreter 50B2 are shown as examples of identification information interpreters. When a TMN file is double-clicked on a filer screen such as an explorer on the display unit 7, the user program creation support program decompresses the TPJ file saved in a compressed format and loads it onto the PC side memory unit 11. Further, when the kpr file is double-clicked, the user program creation support program loads other setting files placed in the same folder as the kpr file onto the PC side memory unit 11. On the other hand, the TPJ file and the kpr file are interpreted as common model data by the TPJ interpretation section 50B1 and the kpr interpretation section 50B2, and are loaded onto the PC side memory section 11.
(Mode selection section 50D)

Furthermore, the PC side CPU 21 can also realize the function of the mode selection section 50D. The mode selection section 50D can select an editing mode or a history playback mode. The edit mode is a mode for editing project data, and is also called an edit mode. Further, the history playback mode is a mode in which the log display control unit 61 performs display, and is also called a replay mode or the like. In this way, the user program creation support program switches the operating mode within one program, plays back past events in order to solve the problem, and moves on to modifying the user program at the location that is thought to be the cause. be able to. Furthermore, by using a common GUI between the history playback mode and the edit mode, it is possible to perform a smooth transition of work.
(User program creation support program 1300)

First, FIG. 9 shows the GUI of the user program creation support program 1300 when the history playback mode is selected in the mode selection section 50D. The GUI shown in this figure includes a project display area 420, a ladder monitor 450, a camera monitor 430, and a unit monitor 440. In FIG. 9, 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, motion unit, analog input unit, camera input expansion unit, etc.) and program configuration (every scan module, fixed cycle module, inter-unit synchronization module, function block, macro, etc.) are displayed. There is. Regarding the motion unit, the axis configuration and axis control setting parameters are displayed as function settings. By double-clicking on the axis configuration or axis control on the GUI shown in FIG. 9, the user can check the settings for these setting parameters. Furthermore, in the project display area 420, Main and Sub are displayed for each scan module, and when the user clicks on Main, the Main program is displayed in the program display area 410 of the ladder monitor 450 at the center.
(history playback mode)

Next, a procedure for reproducing driving record data recorded when a trouble occurs in the history reproducing mode will be explained based on FIG. 10. For example, if you double-click a pre-saved driving record data file (the driving record data file with the extension TMN mentioned above) or a project file (the project data file with the extension kpr), the user program creation support program shown in FIG. 1300 is started, it analyzes the double-clicked file, expands the included file, calls another associated file, etc., and automatically reproduces the situation when the driving record data was saved. Ru. Alternatively, after starting the user program creation support program 1300, the user can select and expand a corresponding file such as a driving record data file from a file menu or the like.

In this example, the user program creation support program 1300 is configured to start in the history playback mode shown in FIG. 10 when driving record data is double-clicked. On the other hand, when project data is double-clicked, the user program creation support program 1300 is configured to start in the edit mode shown in FIG. 11. In this way, by varying the initially selected operation mode depending on the file selected by the user, it is possible to select in advance an operation mode that is in line with the expected user operation and provide a smooth operation environment.
(Switching between history playback mode and edit mode)

After starting the user program creation support program 1300, to switch between the two operating modes, edit mode and history playback mode, select the desired operating mode from the mode selection column 50D1, which is one form of the mode selection section 50D. For example, the mode selection field 50D1 may be configured with a pull-down menu as shown in FIG. 12, so that the user can easily select a desired operation mode. In the example of FIG. 12, selecting "Replay" switches to history playback mode (replay mode), and selecting "Editor" switches to editing mode (editor mode). Furthermore, the mode selection field 50D1 displays the currently selected operation mode, and also has the function of notifying the user of the current operation mode.

Note that when switching the user program creation support program started in edit mode by double-clicking the project data to history playback mode, the device data for use in history playback mode is not specified in the project data. You will be prompted to separately specify the driving record data including the data. For example, a dialog screen for selecting driving record data is displayed.

In this way, in the history playback mode, the saved driving record data is read and the event when the trouble occurred is played back, allowing the user to estimate the cause of the trouble and consider necessary measures to improve it. For example, edit the ladder program to resolve the problem.

In the history playback mode of FIG. 9, editing of the user program is prohibited. In other words, reproduction or viewing of the driving record data is permitted, but falsification is prohibited. This ensures the reliability of driving record data when trouble occurs. Note that the history playback mode in which editing of the user program is prohibited is called the log playback mode.
(edit mode)

Here, as a procedure for editing a user program using the user program creation support program 1300 in the edit mode, an example of modifying a ladder program will be described based on FIGS. 13 to 15. In this example, a user program is created that changes the operation to torque control if the value of the device indicating current coordinates exceeds 12,000 while positioning control of the motion unit is being performed using the user program creation support program 1300. We are considering. Here, as a result of verifying the cause of the trouble in the history playback mode, as shown in FIG. 13, if the operation is changed after the device value in the ladder diagram shown in the program display area 410 exceeds 12,000, the movable arm will come into contact with the workpiece. Let's assume a case where you want to change the threshold from 12,000 to 10,000 in the edit mode because it turns out that the threshold value is 12,000. First, in the user program creation support program 1300 shown in FIG. 13, select the part surrounded by the broken line and press the Enter key on the keyboard that constitutes the PC-side operation unit 8 to display the program editing screen 1310 shown in FIG. . From this program editing screen 1310, the value 12000 is corrected to 10000 in the device value input field 1312, and the "overwrite" button 1314 is pressed. As a result, the ladder program is changed as shown in the program display area 410 of the user program creation support program 1300 in FIG.

As another example of editing a user program, a procedure for modifying parameters for positioning control of a motion unit will be described based on the user program creation support program 1300 in FIG. 16. Here, as a result of verifying the cause of the trouble in history playback mode, it was found that the acceleration of the workpiece was too rapid, so we decided to switch the editing mode and reduce the speed of the workpiece when moving to point parameter No. 1. think. First, in the user program creation support program 1300 of FIG. 16, the "point parameter" of the motion unit is selected from the unit configuration displayed in a tree in the project display field 420 displayed on the left side. In this state, select the parameter you want to change and input the value from the keyboard or the like that is the PC side operation section 8. Here, in the point parameter editing field 1320 on the right side of the screen, change the speed to a lower value (for example, 300 mm/s) from the speed specification field 1322. Through such operations, the user program can be changed to desired values.

The procedure for saving the result of editing a user program in this way will be explained based on FIGS. 17 and 18. When saving a user program, if you edit the original user program included in the driving record data, you will not be able to reproduce the user program when a problem occurred in history playback mode, so it is necessary to save it separately from the original user program. There is. Here, we will consider the case of saving as separate project data. First, the project data is saved using the same procedure as for a normal project, as shown in the file menu 1330 of the user program creation support program 1300 shown in FIG. Here, when selecting "Save project as" 1332 from the file menu 1330, a "Save project as" dialog screen 1340 is displayed as shown in FIG. You will be prompted to specify. With this procedure, the user program included in the driving record data is preserved as new project data.

On the other hand, if an attempt is made to overwrite and save by using the "overwrite save project" 1334 or the general keyboard shortcut keys Ctrl+S in the file menu 1330 of FIG. 17, the save control unit 50C controls the overwrite save. That is, regardless of the overwrite save instruction, a "save project under a different name" dialog screen 1340 shown in FIG. 18 is displayed to prompt the user to save the project data under a different name. Alternatively, on the save screen in Figure 17, to prohibit overwriting, the corresponding "Save project" may be grayed out so that it cannot be selected, or "Save project" may not be displayed as an option in the file menu. You may also do so. Alternatively, you can automatically save project data under a different name. For example, a file with a different name is automatically generated by adding a branch number such as "-1" to the file name. Alternatively, when "overwrite save project" is selected, an overwrite prohibition pop-up may be displayed indicating that overwrite save operation is prohibited.

Note that if you instruct to overwrite and save a user program that has already been saved under a different name, the overwrite save will be executed as is since this is not an operation for the original user program included in the driving record data. That is, the operation of the save control unit 50C that regulates the overwrite save operation described above is executed when the original project data and user program included in the driving record data at the time of trouble occurrence have not yet been copied and saved under a different name. , once saved under a different name, overwrite save operations are allowed.
(Save operation of driving record data)

As described above, the user can reproduce the driving record data based on the backup project of the device stored in advance on the PC 2. Furthermore, if there is no backup project for the device, the driving record can be reproduced based on the project data saved in the driving record data. By playing back the driving record data in the history playback mode, the user finds a problem in the process targeted by the project data, and when the problem is corrected in the edit mode, the changes are saved on the PC2. operations can be performed.

On the other hand, if project data in the driving record data is used to play back the driving record, when executing the save operation for the project data edited in edit mode, the user program creation support program will display an overwrite save prohibition message in the save control section. You can block the save by issuing . Alternatively, the data may be saved as new project data on the hard disk of the PC.
(Procedure for "Prohibit overwriting")

An example of such "overwrite storage prohibition" processing by the storage control unit 50C will be explained based on the flowchart of FIG. 19. First, in step S1901, when a save operation is started, it is determined in step S1902 whether or not project data saved in driving record data is being edited. If editing is in progress, in step S1903, a message indicating that saving is not possible is displayed to the user, and the saving process is canceled. On the other hand, if editing is not in progress, the process advances to step S1904 and save processing is executed.
(Procedure for "Save as new project data")

An example of the "save as new project data" process by the storage control unit 50C will be described based on the flowchart of FIG. 20. First, in step S2001, when a save operation is started, in step S2002, it is determined whether or not project data saved in driving record data is being edited. If editing is in progress, in step S2003 the user is requested to input a file save path on the PC 2 in order to save it as a new project. Then, in step S2004, the project is saved to the input save path. On the other hand, if editing is not in progress in step S2002, the process advances to step S2005 and save processing is executed.
(Verification function for saved projects)

Like normal project data, the edited project data can be compared with the project currently displayed in the user program creation support program and the edited project data saved on the PC 2 using the collation function provided by the user program creation support program 1300. You can check the differences between project data. For example, on the screen of the user program creation support program 1300 in FIG. display on the screen. For example, parts that have been added to or changed from the target project data are highlighted, while deleted parts are grayed out. Alternatively, the differences may be displayed as a list and highlighted. As an example, FIG. 22 shows the results of executing the matching function on the ladder program edited in FIGS. 13 to 15. FIG. 22 shows an example of a comparison display screen 1350 for displaying a comparison of project data in the user program creation support program 1300. In the example shown in this figure, for items edited in the ladder program, the step number, collation source value, and collation destination value are shown in red. In this way, the user can easily visually grasp the edited portion of the referenced project data, for example, the user program at the time of trouble occurrence.
●Logging settings (automatic extraction and addition/subtraction)

FIG. 23 shows functions realized by the PC-side CPU 21 of the PC 2 executing the project data editing program stored in the PC-side storage device 22. Some or all of these functions may be realized by a hardware circuit such as ASIC or FPGA. ASIC is an abbreviation for application specific integrated circuit. FPGA is an abbreviation for field programmable gate array.

The PC-side CPU 21 in FIG. 23 realizes the functions of a project creation section 50, a log setting section 51, and a log display control section 61. In this embodiment, the functions shown in FIG. 23 are realized on the PC2, but the present invention is not limited to this, and may be realized on the PLC1.
(Project creation department 50)

The project creation section 50 realizes the functions of the program creation section 63 and the function setting section 62. This project creation unit 50 displays a UI for creating project data 71 on the display unit 7, creates project data 71 according to user instructions input from the PC side operation unit 8, and stores it in the PC side storage device 22. do. UI is an abbreviation for user interface. The project data 71 includes a user program, unit configuration information of the PLC 1, and the like.

The program creation unit 63 creates a plurality of program parts (each module) that constitute a user program based on user operations via the UI. The function setting section 62 executes settings regarding the functions of the CPU unit 3 and the functions of the expansion unit 4. For example, the function setting section 62 assigns any device to a function provided in the CPU unit 3, or assigns any device to a function provided in the expansion unit 4, and assigns a function and a device. Writes allocation information indicating the relationship with the unit configuration information. Note that the project creation unit 50 also stores program configuration information indicating what kind of program parts the user program is composed of as the project data 71. Unit configuration information indicating what kind of units the entire PLC 1 is composed of is also stored as project data 71.
(Log setting section 51)

The log setting section 51 realizes the functions of a component specifying section 52, a function specifying section 60, a device extracting section 53, a manual setting section 58, and an estimating section 59. The log setting unit 51 extracts the devices described in the project data 71 by analyzing the project data 71, and creates log setting data 72 for setting the extracted devices as logging targets. The log setting section 51 has various functions. The component designation unit 52 designates a program component to be extracted from a device according to a user instruction input from the PC-side operation unit 8. Further, the component designation unit 52 designates program components to be excluded from device extraction targets in accordance with user instructions input from the PC-side operation unit 8.

The device extracting section 53 realizes the functions of the adding section 54, the deleting section 55, the merging section 56, and the specifying section 57. The device extraction unit 53 extracts the devices described in the project data 71 by analyzing the project data 71, and creates log setting data 72. The adding unit 54 analyzes the program component specified as an extraction target by the component specifying unit 52, extracts the device described in the program component, and adds it to the extraction list. The deletion unit 55 analyzes the program component designated as an exclusion target by the component designation unit 52, extracts the device described in the program component, and deletes the extracted device from the extraction list. Alternatively, the deletion unit 55 adds the extracted device to the exclusion list. The merging unit 56 deletes duplicately extracted devices from the extraction list among the devices extracted from each of the plurality of program parts. The specifying unit 57 detects a command for a memory card in the project data 71, specifies the device targeted by the command, and adds the specified device to the extraction list.

In this embodiment, after the component specifying unit 52 specifies a program component, the adding unit 54 extracts and adds devices to be logged by analyzing the specified program component. The invention is not limited to this. For example, the adding unit 54 extracts a device by first analyzing one or more program parts included in the project data 71, adds the extracted device to an extraction list, and then specifies it using the part specifying unit 52. The device described in the program component may be extracted and added to the extraction list.

Similarly, the deletion unit 55 creates an extraction list by first analyzing one or more program parts included in the project data 71, and then deletes the information written in the program parts specified by the part specification unit 52. The device may be extracted and removed from the extraction list.

Note that in this embodiment, for convenience of explanation, the adding section 54 and the deleting section 55 are separated, but it goes without saying that they may be one functional block.

The manual setting unit 58 adds one device or a series of related devices to the extraction list according to user instructions input through the PC-side operation unit 8. The estimation unit 59 estimates the influence that the recording of device values by the PLC 1 has on the execution of the user program based on the number of devices extracted as recording targets by the device extraction unit 53. Logging adds a delay time correlated to the number of device values to the scan time. Therefore, the estimation unit 59 may calculate the delay time by multiplying the number of device values by a predetermined coefficient, and display the delay time on the display unit 7 as the estimation result. This delay time may be referred to as scan time elongation.

The function specifying section 60 specifies the function of the CPU unit 3 and the function of the expansion unit 4 from which devices are to be extracted, according to user instructions input from the PC-side operation section 8 . Further, the function specifying unit 60 specifies the functions of the CPU unit 3 and the functions of the expansion unit 4 to be excluded from the device extraction target according to user instructions input from the PC-side operation unit 8. The adding unit 54 analyzes the unit configuration information of the function specified as an extraction target by the function specifying unit 60, extracts the device assigned to the function based on the unit configuration information, and adds it to the extraction list. The deletion unit 55 analyzes the unit configuration information of the function specified as an exclusion target by the function specification unit 60, extracts the device assigned to the function based on the unit configuration information, and deletes the extracted device from the extraction list. do. The merging unit 56 deletes duplicately extracted devices from the extraction list among the devices extracted for each of the plurality of functions. The specifying unit 57 detects a command for a memory card in the project data 71, specifies the device targeted by the command, and adds the specified device to the extraction list.

The log display control unit 61 stores the log data 73 generated in the PLC 1 in the log data storage unit 74. As the log data storage section 74, a memory card 36A or the like can be used. The log data 73 stored in the log data storage section 74 is read out via the memory card 36A, and the log data 73 is displayed on the display section 7. For example, the log display control section 61 may display the device values recorded in the log data 73 and the program components of the project data 71 in association with each other on the display section 7 . The log display control unit 61 forms the core of an engineering tool for programmable logic controllers. In addition to device values, the log data 73 may also include image data captured by a camera unit (details will be described later). These project data and log data are packaged and saved as operation record data. Alternatively, project data and log data may be associated and saved as separate files, and when either the project data or the log data is opened, the other file may also be readable by referring to the association information (details will be described later).
● Executing logging

FIG. 24 shows the functions of the PLC side CPU 31 of the CPU unit 3. Some or all of these functions may be realized by a hardware circuit such as ASIC or FPGA. ASIC is an abbreviation for application specific integrated circuit. FPGA is an abbreviation for field programmable gate array.

It is assumed that the PLC side CPU 31 stores the project data 71 and log setting data 72 received from the PC 2 in the PLC side storage device 32. The execution unit 80 includes a ladder execution engine 80a that repeatedly executes a user program, and a unit control unit 80b that controls the ladder execution engine 80a and performs input/output refresh with the expansion unit 4. There is. The ladder execution engine 80a of the execution unit 80 repeatedly executes the user program included in the project data 71, and controls the expansion unit 4 according to the user program. Note that the ladder execution engine 80a of the execution unit 80 writes device values to output devices held in the CPU unit device unit 34a of the device unit 34, and writes device values to output devices held in the CPU unit device unit 34a according to the user program. Read device values from input devices.

On the other hand, the unit control section 80b of the execution section 80 reads and writes the device value related to the expansion unit 4 obtained by input/output refresh to and from the expansion unit device section 34b. Further, the CPU unit 3 and the expansion unit 4 are electrically connected by an inter-unit bus 90, and the unit control section 80b has a function of controlling communication on this inter-unit bus 90, that is, a so-called bus master function. ing. When the unit control section 80b functions as a bus master, each expansion unit 4 and Perform refresh communication.

The recording unit 81 acquires a device value from the device unit 34 (CPU unit device unit 34a or expansion unit device unit 34b) according to the log setting data 72, or acquires a device value from the buffer memory of the expansion unit 4, It is written as log data 73 in a memory (for example, a ring buffer). As described above, the recording unit 81 executes the logging process during the END process and the like.

The logging process in the END process will be explained in more detail. The log setting data 72 includes devices written in program parts specified by the component specification section 52 and devices assigned to functions specified by the function specification section 60 (for example, targets for monitoring by a unit monitor). Included as a target. For the former device, the device value of the target device (UG) is read from the expansion unit 4 during the END process, and for the latter device, the device value is written to the log data 73 during the END process. Write to log data 73.

Here, the update cycle (so-called control cycle) of the current coordinates and command coordinates of the motor is much shorter than the scan cycle of the ladder program. Therefore, in this embodiment, since the device values of the UG are read out in synchronization with the scan cycle, not all current coordinates and command coordinates are written to the log data 73. However, the present invention is not limited to this, and for example, current coordinates and command coordinates are stored in the memory of the expansion unit 4 for each control cycle, and at the timing of the scan cycle, a plurality of previously stored current coordinates and command coordinates are stored in the memory of the expansion unit 4. It is also possible to configure it to read out coordinates and the like.

Furthermore, the recording unit 81 adds time information held by the time management unit 83 to each record of the log data 73. As a result, device values are arranged in chronological order in the log data 73.

Devices to be logged are basically designated by the logging target list of the log setting data 72, but additional devices may be designated by the detection unit 82. The detection unit 82 may detect, for example, rewriting of a device value from an external device to any device included in the device unit 34. Generally, device values may be rewritten according to a user program or may be rewritten by an external device. Such rewriting cannot be detected in advance simply by analyzing the user program. The recording unit 81 may add a device whose device value has been detected to be rewritten by the detection unit 82 as a logging target. Generally, rewriting device values from an external device tends to cause unexpected events for the user. Therefore, the recording unit 81 will be useful for the user to improve the program by logging the device values rewritten by the external device.

By the way, in the END process, a UG read command may be issued regardless of the user program. UG is a device type indicating a buffer memory. The detection unit 82 may detect a UG read command issued regardless of the user program. The recording unit 81 may identify the buffer memory that is the target of the UG read command detected by the detection unit 82, and add the identified buffer memory as a recording target. When the expansion unit 4 is a motion unit, such a buffer memory stores torque values, current coordinate positions, and the like.

The detection unit 82 may be realized by FPGA or the like. The execution unit 80 may be realized by ASIC. In this case, the execution unit 80 specifies the address of the device to be read/written to the PLC side storage device 32 using an address line. Therefore, the detection unit 82 may dynamically detect a device whose device value has been updated by monitoring this address line. This may be useful when adding a device that is not described in the user program as a recording target.

The detection unit 82 may be provided in the execution unit 80. In this case, the execution unit 80 may write a device value to a specific device in the device unit 34, and may also write this device value and the device name (device number) to the log data 73. This method is useful when adding a device that is not described in the user program and can be dynamically allocated as a recording target.

In this way, the recording unit 81 may record devices regardless of the device list included in the log setting data 72. In an extreme case, the user can obtain log data 73 without creating log setting data 72. For example, when the execution unit 80 is activated, the execution unit 80 acquires device values from all devices in the device unit 34. Since the detection unit 82 monitors the device, it detects that the execution unit 80 has read the device value, and transmits information (address information) about the device from which the device value has been read to the recording unit 81. The recording unit 81 reads device values from all devices included in the device unit 34 based on the address information transmitted by the detection unit 82 and writes them in the log data 73. Thereafter, every time the detection section 82 detects an access to the device section 34, the recording section 81 logs the device value.

By the way, the recording unit 81 may write the device value to the log data 73 every scan cycle or every predetermined collection cycle. For example, even if the detection unit 82 detects multiple accesses to the device within one cycle, the recording unit 81 may write to the log data 73 only the device value when the last access was detected. This makes it possible to reduce the data size of the log data 73.

The execution unit 80 may have a cache that holds devices. In this case, the detection unit 82 may detect writing by the device by monitoring the cache.

The log setting data 72 includes a device list indicating devices to be recorded, but may also include a device list indicating devices to be excluded from recording. In this case, when the detection unit 82 detects an access to a device to be excluded, the recording unit 81 skips recording the device value for that device.

The detection unit 82 may detect access by the execution unit 80 to the buffer memory of the expansion unit 4. In this case, the execution unit 80 writes the device value read from the buffer memory of the expansion unit 4 into a buffer etc. secured within the PLC side storage device 32. The recording unit 81 reads the device value from the buffer and writes it into the log data 73.

The execution unit 80 repeatedly executes the user program and rewrites device values according to the user program. When the detection unit 82 is installed in the execution unit 80, when the execution unit 80 detects a command word for rewriting a device value, it outputs the device value together with the command word to the recording unit 81. The recording unit 81 may write the command word, the device value, and the time stamp (time when the device value was acquired) to the log data 73.

Incidentally, the log setting data 72 may include the data format (eg, binary format or text format) of the log data 73. Data formats include 16-bit decimal, 32-bit decimal, 16-bit decimal, 32-bit decimal, 16-bit hexadecimal, 32-bit hexadecimal, character string, Float, DoubleFloat, etc., set for each device. may be done. Such a data format can be determined by analyzing the instruction words in the program component.

The output unit 84 outputs the project data 71, log data 73, and image data to the memory when a predetermined output condition is met, such as when the execution of the user program is finished or when the save trigger relay to the memory card is turned on. Write to card 36A. Until a predetermined output condition is met, log data 73 is recorded in a memory (for example, a ring buffer), and when the capacity is full, the oldest log data 73 is deleted and new log data 73 is added and recorded. (records in so-called FIFO format). This memory card 36A is removed from the CPU unit 3 and installed in the mounting section of the PC 2. As a result, the log data 73 comes to be displayed on the display section 7 of the PC 2. Note that the output unit 84 may transmit the log data 73 to the PC 2, the cloud, etc. via the PLC side communication unit 33.

Note that in this embodiment, the log data 73 and the like are written to the memory card 36A when a predetermined output condition is met; however, the present invention is not limited to this, and for example, It is also possible to save it in a non-volatile memory such as Furthermore, at least the log data 73 needs to be saved in the memory card 36A or internal memory 37 when a predetermined output condition is met, while the project data 71 needs to be saved when a predetermined output condition is met. Not limited to. For example, the information may be stored in the memory card 36A or internal memory 37 in advance at the timing when the PLC 1 changes from the setting mode (PROGRAM mode) to the operation mode (RUN mode).
●Creation of unit configuration information

FIG. 25 is a diagram illustrating the unit configuration information creation process (unit setting) executed by the function setting section 62. The function setting section 62 may be called a unit editor. When the function setting section 62 receives permission to start the unit editor, it displays the unit setting UI 150 on the display section 7. The name column 151 is a column for displaying the name (eg, model number, etc.) of each unit. Note that each unit is automatically assigned a unit number. In this example, "0" is assigned to the CPU unit 3 as a unit number. The input area column 152 is a column for allocating input devices. In this example, devices R000 to R015 are assigned to the CPU unit 3 as input devices. The output area column 153 is a column for allocating output-related devices. In this example, devices R500 to R507 are assigned to the CPU unit 3 as output devices. The occupied area column 154 is a column for allocating mixed input/output type devices. The end unit is a so-called terminal unit. The user sets the type of expansion unit 4, connection order, and assigned device through the PC-side operation unit 8. The function setting section 62 stores information indicating the type of expansion unit 4, the connection order (unit number), and the devices allocated to each of the CPU unit 3 and expansion unit 4 in the unit configuration information. Unit configuration information may be called unit setting information. Here, devices are assigned to each unit, but devices may be assigned to each function of each unit. The function setting section 62 manages unit configuration information as part of the project data 71.

In this way, the unit configuration information includes information indicating devices assigned to each unit and information indicating devices assigned to each function. Therefore, by referring to the unit configuration information, the device extraction unit 53 can extract the devices assigned to each unit and the devices assigned to each function.
<Debug>

FIG. 26 is a flowchart showing an overview of the user program debugging process executed by the user.

In step S2601, the user operates the PC 2, creates a user program composed of a plurality of program parts, and creates project data 71 including the user program. The program creation unit 63 creates a user program according to user input and stores it in the PC storage device 22. The project creation unit 50 creates project data 71 according to user input, and stores it in the PC storage device 22. The project data 71 includes identification information for identifying the project data 71 or the user program. The project creation unit 50 may perform calculations on the project data 71 or the user program to obtain a hash value or an error detection code, and add these to the project data 71 as identification information. Note that the identification information may be a GUID (globally unique identifier) or the like.

In step S2602, the user operates the PC 2 to transfer the project data 71 to the PLC 1. The project creation unit 50 reads project data 71 from the PC storage device 22 and transmits it to the PLC 1 via the PC communication unit 23. When the CPU unit 3 of the PLC 1 receives the project data 71, it writes it into the PLC side storage device 32.

In step S2603, the user operates the PLC side operation unit 6 of the CPU unit 3 (for example, by operating a mode changeover switch for switching from PROGRAM mode to RUN mode) to instruct execution of the project. The execution unit 80 executes the user program included in the project data 71. The recording unit 81 logs device values and the like, and temporarily stores (records) the logged device values in the recording unit 91a. The storage unit 93 of the output unit 84 stores the device values recorded in the temporary storage unit 91a and the above-mentioned image data in the memory card 36A or the internal memory 37 when a predetermined output condition is satisfied. Then, log data 73 is created.

In addition to the log data 73, the storage unit 93 stores the project data 71 in the memory. This allows the PC 2 to use the project data 71 at the time of the trouble to reproduce on the monitor the behavior at the time of the trouble. Details will be described later.

In addition to the project data 71, the storage unit 93 stores identification information (such as a hash value) of the project data 71 in the memory. This allows the PC 2 to use the identification information to verify whether the current project data (to be replayed) matches the project data 71 at the time of the actual trouble occurrence. Details will be described later.

Note that in this embodiment, the project data 71 and its identification information are stored in the memory in addition to the log data 73 at the timing when a predetermined output condition is met, but the present invention is not limited to this. . For example, the project data 71 and its identification information are stored in memory before, at the time of, or during operation of the PLC 1, and only the log data 73 is stored in the memory at the timing when a predetermined output condition is met. You may also save it. In short, it is only necessary that the log data 73, the project data 71, and their identification information be stored in the memory in a state in which they are associated with each other when a predetermined output condition is satisfied.

Further, in this embodiment, the project data 71 is stored in the memory, but the present invention is not limited to this. For example, instead of the project data 71, only the identification information of the project data 71 may be stored in the memory. It's okay. In this case, it is assumed that the current project data on the PC 2 matches the project data 71 at the time of the actual trouble occurrence. That is, it is assumed that the current project data is not edited or modified after the project data is transferred to the PLC 1. If it is determined that the two data do not match, the user can perform a replay after recognizing that the current project data is different from the project data 71 at the time of the actual trouble. This can prevent replays (inaccurate troubleshooting) from being performed without being aware of this.

In step S2604, the user operates the PLC side operation section 6 of the CPU unit 3 and instructs to transfer the project data 71 and log data 73 to the PC 2. Alternatively, the project data 71 written in the memory card 36A, the identification information of the project data 71, and the log data 73 may be read out by operating the PC-side operation unit 8 of the PC 2. The output unit 84 transmits the project data 71 and log data 73 to the PC 2. Note that the output unit 84 may adopt a configuration in which the identification information of the project data 71 is added to the log data 73 when it is determined that the transfer of the project data 71 is prohibited. The identification information of the project data 71 and the log data 73 may be transmitted separately. The output unit 84 executes an operation (for example, using a hash function) on the project data 71 or the user program to generate a hash value, an error detection code, etc. at the timing when a predetermined condition for writing to the memory card 36A is satisfied. may be obtained and added to the log data 73 as identification information. Note that any rule may be adopted as long as the identification information creation rule executed by the PC 2 and the identification information creation rule executed by the CPU unit 3 match.

In step S2605, the user operates the PC 2 to investigate the cause of the trouble while replaying the log data 73, and debugs the user program constituting the project data 71. Reproduction of the log data 73 includes displaying the time-series device values included in the log data 73 as waveforms on the display unit 7, displaying the device values in association with the user program, and displaying the device values included in the log data 73 in association with the user program. This includes displaying time-series image data on the display unit 7. The log display control section 61 has an internal clock that measures virtual time, acquires device values from the log data 73 in synchronization with the internal clock, and displays them on the display section 7 . The project data 71 may not be transmitted from the PLC 1. In this case, the log display control unit 61 may use the user program of the project data 71 (master data) held in the PC storage device 22 to display the device value in association with the user program. Details of investigating the cause of the trouble by reproducing the log data 73 will be described later.

It should be noted here that the version of the project data 71 used to obtain the log data 73 may be different from the version of the project data 71 held in the PC 2. In this case, it is possible that it becomes impossible to display the device value in association with the user program, or that the association between the user program and the device value becomes incorrect. In this case, the log display control unit 61 uses the identification information of the project data to determine whether the version of the project data 71 used to obtain the log data 73 and the version of the project data 71 held in the PC 2 are different from each other. A warning indicating the difference may be displayed on the display unit 7. Note that the log display control unit 61 determines whether to display the log data 73 acquired using the first version of the project data 71 in association with the second version of the project data 71 held in the PC 2. You can also ask the user. If the user desires such a display, the log display control unit 61 displays the log data 73 obtained using the first version of the project data 71 as the second version of the project held in the PC 2. It is displayed on the display section 7 in association with the data 71. Note that the version is managed using identification information. If the user confirms that there is no problem with the log data 73, debugging is unnecessary, and subsequent steps S2606 and S2607 are also unnecessary. The user analyzes the log data 73, discovers bugs, etc. in the user program, and corrects the user program. The project creation unit 50 modifies (updates) the project data 71 according to user input, and stores it in the PC storage device 22.

In step S2606, the user operates the PC 2 to transfer the project data 71 to the PLC 1. Note that when the user program in the project data 71 is changed, the identification information is updated. This makes it possible to distinguish between the project data 71 before modification and the project data 71 after modification.

In step S2607, the user operates the CPU unit 3 to instruct execution of the user program included in the project data 71, thereby verifying the project data 71. The execution unit 80 executes the user program included in the project data 71. If the PLC 1 is operating as expected by the user, the user determines that the project data 71 has been successfully debugged. Note that if the PLC 1 is not operating as expected by the user, the recording unit 81 logs the device values and the like again, and the storage unit 93 creates log data 73. Then, the user executes steps S2604 to S2607 again.

In this way, the user can debug the project data 71 while referring to the log data 73. Therefore, it is thought that debugging efficiency will improve.

Note that the project data 71 may be transferred via the memory card 36A. That is, the PC 2 writes to the memory card 36A. The user removes the memory card 36A from the PC 2 and attaches the memory card 36A to the CPU unit 3. The CPU unit 3 reads the project data 71 from the memory card 36A and writes it to the PLC side storage device 32. Similarly, the transfer of log data 73 may also be performed via the memory card 36A.
<Project creation department 50>

FIG. 27 shows details of the project creation section 50. The function setting unit 62 sets the unit configuration information of the expansion unit 4, the functions of the CPU unit 3, and the functions of the expansion unit 4 based on information input from the PC-side operation unit 8, and creates unit configuration information indicating the setting contents. . Functional settings of the CPU unit 3 include IP address settings, FTP client settings, access authority settings for the project data 71, and the like. Settings for the functions of the expansion unit 4 include settings for input channels, settings for communication between PLCs, and the like. The unit configuration information is part of the project data 71. The editing unit 311 (which may also serve as the program creation unit 63 shown in FIG. 23) displays an editing UI for the user program on the display unit 7 and edits the user program based on information input from the PC-side operation unit 8. . The debug unit 314 debugs the user program using the project data 71. The adding unit 312 adds identification information to the project data 71. The calculation unit 313 calculates identification information (eg, a hash value or an error detection code) by calculation. Note that the output unit 84 may perform the same function as the identification information calculation function performed by the calculation unit 313.
<Log display control unit 61>

FIG. 28 shows details of the log display control section 61. The program display module 321 is a module that displays the user program included in the project data 71 as well as device values included in the log data 73 on the display unit 7. Further, the program display module 321 allows the user to visually check the setting contents of the project data 71, such as not only the user program but also the program configuration information included in the project data 71, multiple program parts, unit configurations, and function settings for each unit. Various information can be displayed. The image display module 323 displays time-series image data included in the log data 73 on the display unit 7. The waveform display module 322 is a module that converts time-series device values included in the log data 73 into a waveform and displays the waveform on the display unit 7. The reproduction control module 324 temporally synchronizes the information displayed by the program display module 321 and the information displayed by the waveform display module 322. These modules may be called engineering software. Note that the image display module 323 may be realized as one function (image display section) of the program display module 321, or may be realized as one function (image display section) of the waveform display module 322.
●Program display module

FIG. 29 shows details of the program display module 321. The time UI 330a provides a UI (eg, a slide bar, a cursor, etc.) for operating the device acquisition time (display time) displayed together with the user program. The display time control unit 331a sends the display time specified by the time UI 330a to the playback control module 324, and sets the display time notified from the playback control module 324 to the time UI 330a. The program display section 332 displays the project data 71 on the display section 7 or reads out the project data 71 corresponding to the identification information from the PC storage device 22 and displays it on the display section 7 . Further, 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). The device value acquisition unit 333a accesses the real-time transmission unit of the PLC 1 in real-time playback mode, acquires the device value, and passes it to the program display unit 332. In the log playback mode, the device value acquisition unit 333a accesses the playback control module 324 in FIG. 28, acquires the display time and device value, and passes them to the program display unit 332.

FIG. 9 is a schematic diagram showing an example of a GUI displayed on the display section 7 by the program display section 332 or the like. In FIG. 9, 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, motion unit, analog input unit, camera input expansion unit) and program configuration (every scan module, fixed cycle module, inter-unit synchronization module, function block, macro) are displayed. Regarding the motion unit, the axis configuration and axis control setting parameters are displayed as function settings. By double-clicking on the axis configuration or axis control on the GUI shown in FIG. 9, the user can check the settings for these setting parameters. Furthermore, in the project display area 420, Main and Sub are displayed for each scan module, and when the user clicks on Main, the Main program is displayed in the program display area 410 of the ladder monitor 450 at the center. In this way, the program display module 321 shown in FIG. 28 reads the project data 71 from the memory card 36A, displays various information in the project display area 420, and displays a desired program in the program display area 410.

Here, the program display area 410 is a part of a 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 x mark. On the other hand, in the log reproduction mode, the program display section 332 can reproduce the ladder program included in the project when the driving record was saved. Furthermore, in the log playback mode, the program display section 332 displays the device value included in the log data 73 via the device value acquisition section 333a in association with the device described in the Main program. The device value to be displayed is the device value corresponding to the time specified by the time designation cursor 404 (more details will be explained later using FIG. 32).

In FIG. 9, the device value associated with 18:52:54 on 20XX/10/01 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 the current number of scans of 35,000 compared to the total number of scans of 74,286. By dragging and moving the time designation cursor 404, the user not only updates the display time and number of scans, but also updates the display of the device value. For example, at the updated display time, relay devices that are ON are displayed as ON (for example, by filling them in color), and relay devices that are OFF are displayed as OFF (for example, by removing color). will be done. Details of the function of the playback button 406 will be described later using FIG. 32.

In FIG. 9, an image display area of the camera monitor 430 is provided in the upper right column. The image display module 323 reads image data from the log data 73 and displays it on the image display area of the camera monitor 430 in synchronization with the display time displayed on the ladder monitor 450 by the program display module 321. In FIG. 9, image data associated with the display time 18:52:54 on 20XX/10/01 is displayed on the camera monitor 430. Moreover, 282/601 is displayed to the right of this display time, which represents the order of the current image data (282nd image) with respect to the total number of captured images 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, as the time designation cursor 404a moves, the time designation cursor 404 on the ladder monitor 450 described above also moves in conjunction with the movement. For example, when the time designation cursor 404a is set to the display time 19:00:00 on 20XX/10/01, the time designation cursor 404 on the ladder monitor 450 also moves to the display time 19:00:00 on 20XX/10/01. Moves to follow position 00. As the time designation cursor 404 moves, the device value on the ladder monitor 450 is also updated. Although the time designation cursor 404a is moved here, the reverse is also true. For example, when the time designation cursor 404 on the ladder monitor 450 is moved, the time designation cursor 404a on the camera monitor 430 also moves accordingly. Such a processing operation is possible because the program display module 321 and the image display module 323 execute synchronized control regarding the display time via the playback control module 324.

Further, in FIG. 9, a unit monitor 440 is displayed in the lower right column. For example, the unit monitor 440 displays the device value of the buffer memory (UG) in the motion unit. More specifically, when the unit display module 325 of the log display control unit 61 receives the display time to be currently played from the playback control module 324, it reads the device value associated with that time from the memory card 36A, and It is displayed on the unit monitor 440. Therefore, for example, in FIG. 9, a list of device values associated with the display time 18:52:54 on 20XX/10/01 is displayed on the unit monitor 440.

FIG. 30 is a diagram schematically showing a data source for displaying a GUI in log playback mode. As shown in FIG. 30, the project display area 420 reads 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 the program configuration (what kind of program parts are included) and the program parts from the memory, displays the program parts specified by the user, and also retrieves the device value corresponding to the display time from the log data 73. Read and display. The camera monitor 430 logs data based on information such as unit configuration (whether there is a camera monitor or not) and function settings (camera monitor functions; for example, if there are multiple ports, the port number, imaging cycle, gain settings, etc.). Image data corresponding to the display time is read out from the data 73 and displayed. The unit monitor 440 extracts 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 are there) and function settings (for motion units, axis configuration, axis control, etc.). Read and display.

As can be seen from FIGS. 9 and 30, the function of the playback control module 324 allows the program display module 321, image display module 323, and unit display module 325 to be synchronously controlled and made to work together. Note that details of the cooperation 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 actual trouble occurrence. More specifically, the collation unit 334 in the program display module 321 shown in FIG. The data 71 (user program) is compared with the identification information, and the comparison result is output to the warning section 335. The warning unit 335 outputs the identification information of the project data 71 (user program) when the driving record was saved, which is output from the PLC 1, and the identification information of the project data (user program) stored in the PC side storage device 22. If they do not match, a warning is displayed on the display unit 7.

Note that in this embodiment, the identification information of two pieces of project data are compared to verify whether they match or do not match. 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 by checking whether all of them match. And so. However, the present invention is not limited to this, and at least the identification information of user programs composed of a plurality of program parts may be compared to verify whether they match or do not match.
●Reproduction control module 324

FIG. 31 shows details of the playback control module 324. The device value providing unit 341 provides the program display module 321 and the waveform display module 322 with the device value acquired from the log data 73 by the log data acquisition unit 344. The device value providing unit 341 also provides the unit display module 325 with the device value acquired from the log data 73. Note that the device value acquired from the log data 73 may be temporarily stored in the log device 345. The device value acquisition section 333a of the program display module 321 and the waveform display module 322 requests a device value from the device value providing section 341. The device value acquisition unit 333a acquires a device value from the log device 345 and transmits it to the device value acquisition unit 333a. The time device 342 is a device that holds the display time set by the playback control section 343. The device value providing section 341 may also transmit the device value (time information) held in the time device 342 to the device value obtaining section 333a. Alternatively, the playback control section 343 may provide the time information to the display time control section 331a of the program display module 321 or the display time control section of the waveform display module 322. The playback control unit 343 has a virtual internal clock for measuring the displayed time, and updates the time information held in the time device 342 according to this internal clock. The playback control section 343 transmits the time information held in the time device 342 to the display time control section 331a and the display time control section of the waveform display module 322. When the playback control unit 343 receives the display time designation from the display time control unit 331a and the display time control unit of the waveform display module 322, the playback control unit 343 sets the received display time in the internal clock (time adjustment). Therefore, when a display time is specified by the display time control section 331a of the program display module 321, this display time is transmitted to the display time control section of the waveform display module 322 via the playback control section 343. Similarly, when a display time is specified by the display time control section of the waveform display module 322, this display time is transmitted to the display time control section 331a via the playback control section 343. As a result, the display time of the program display module 321 and the display time of the waveform display module 322 are synchronized. In order to realize slow playback, fast forward playback, rewind playback, etc., the playback control unit 343 changes the update speed of the internal clock according to user input from the PC-side operation unit 8. The playback control unit 343 may set the time information of the oldest record included in the log data 73 as the initial value of the internal clock. The log data acquisition unit 344 acquires the device value associated with the display time held in the time device 342 from the log data 73 and passes it to the device value providing unit 341.

Similarly, the playback control section 343 may synchronize the display time of the program display module 321 and the display time of the waveform display module 322, as well as the time of the image display module 323 and the unit display module 325.

In this embodiment, the display times of the program display module 321, waveform display module 322, image display module 323, and unit display module 325 are always synchronized in the log playback mode, but the present invention is not limited to this. For example, the user may be able to select whether or not to synchronize. For example, a check box indicating whether synchronization is present may be provided on each monitor screen, and the check box may be set to a checked state by default. Then, by unchecking a module that the user does not want to synchronize, it is possible to prevent only that module from being synchronized. In this way, the log display control unit 61 may have a selection function to select a module to be synchronously controlled (followed control) by the playback control module.
<Program display UI>

FIG. 32 shows a display UI 400 provided by the program display module 321. The display UI 400 described with reference to FIG. 9 and the like will be described in further detail from another perspective. The program display area 410 is an area where the user program of the project data 71 is displayed. In this example, the program display area 410 displays a ladder program (ladder diagram). The program display unit 332 uses the device value acquisition unit 333a to acquire the device value of the device used or described in the user program, and displays it together with the user program. For example, if the relay device is ON, the program display unit 332 may display an icon 401a indicating ON over the user program. If the relay device is OFF, the program display section 332 may display an icon 401b indicating OFF over the user program. The program display unit 332 may acquire the device value of the DM 100, which is an output device, using the device value acquisition unit 333a, and display the device value overlappingly with the description of the DM 100 in the user program. In this example, a device value display area 403 is provided below the description of DM 100. The program display section 332 displays device values in the display area 403. Note that since the playback control module 324 updates the device value as well as the display time, the program display section 332 updates the device value displayed together with the user program.
(Playback control column 402)

At the bottom of the program display area 410, a playback control field 402 is provided for operating the playback of saved log data such as device values. Specifically, the time UI 330a moves the time designation cursor 404 from right to left according to the display time acquired from the time device 342. The time designation cursor 404 can be dragged by the pointer 101. When the time UI 330a detects that the time designation cursor 404 has been dragged by the pointer 101, the display time control unit 331a causes the playback control unit 343 to stop updating the display time, and adjusts the dragging amount of the time designation cursor 404 to the playback control unit 343. to notify. The playback control unit 343 adjusts the count value (display time) of the internal clock according to the drag amount. The time UI 330a may display the update speed of the display time (for example, ..., 2.0 times, 1.0 times, 0.5 times, 0.1 times, ...) in the speed specification section 405. good. Note that the speed designation unit 405 may be realized by a pull-down menu that displays a list of a plurality of update speeds and allows one of the update speeds to be selected. When the time UI 330a detects a click by the pointer 101 on the speed specification section 405, the time UI 330a may display such a pull-down menu and accept a selection of an update speed.

A play button 406 is a button for instructing to display device values in chronological order. When the time UI 330a detects that the playback button 406 has been clicked by the pointer 101, the time UI 330a instructs the playback control unit 343 to start updating the display time in the display time control unit 331a. This instruction corresponds to an instruction to start displaying device values or an instruction to restart display. The one-step reverse playback button 407 is a button for instructing to display device values in chronological order while updating (rewinding) the display time one step at a time. When the time UI 330a detects that the one-step reverse playback button 407 has been clicked by the pointer 101, it instructs the display time control unit 331a to move the display time back one step. The one-step playback button 408 is a button for instructing to display device values in chronological order while updating the display time one step at a time. When the time UI 330a detects that the one-step playback button 408 has been clicked by the pointer 101, it instructs the display time control unit 331a to advance the display time by one step. Note that when one-step playback is being executed, the playback control unit 343 does not update the display time unless the one-step reverse playback button 407 or the one-step playback button 408 is operated. When the playback button 406 is operated while one-step playback is being executed, the playback control unit 343 resumes updating the display time at the update speed specified by the speed designation unit 405. The time display area 409 is an area for displaying the display time held in the time device 342. The display time control unit 331a displays the display time acquired from the time device 342 in the time display area 409.
<Display HMI emulator>

The PLC 1 can be connected to a display HMI which is an external display device. The display HMI may have a touch panel type input device. The display HMI reads device values held in the device section 34 of the PLC 1 and displays them on the display device. The project creation unit 50 sets the UI displayed on the display HMI and the device values displayed on the UI, and saves them in the project data 71. The debug unit 314 has an emulator for the display HMI, and checks the operation of the display HMI by operating the emulator according to the project data 71. The log display control unit 61 supplies the device value of the log data 73 to the emulator of the display HMI. The display HMI emulator displays device values provided in chronological order on the UI.
<Flowchart regarding log display>
●Program display module

FIG. 33 shows display processing executed by the program display module 321. Note that steps S3301, S3302, and S3309 may be executed only when the project data 71 cannot be acquired from the PLC 1. If the project data 71 can be acquired from the PLC 1, the project data 71 from the PLC 1 is used. If the project data 71 cannot be acquired from the PLC 1, the project data 71 held in the PC 2 is used.

In step S3301, the PC side CPU 21 (verification unit 334) acquires the identification information of the project data 71 held in the PLC 1 and the identification information of the project data 71 held in the PC 2.

In step S3302, the PC side CPU 21 (verification unit 334) determines whether the identification information of the project data 71 held in the PLC 1 and the identification information of the project data 71 held in the PC 2 match. If the two do not match, the PC side CPU 21 proceeds to step S3309. In step S3309, the PC side CPU 21 (warning section 335) displays a warning on the display section 7 indicating that the identification information of the project data 71 held in the PLC 1 and the identification information of the project data 71 held in the PC 2 do not match. to be displayed. If the two match, the PC side CPU 21 proceeds to step S3303.

In step S3303, the PC side CPU 21 (program display unit 332) acquires the project data 71 from the PLC 1 or the PC side storage device 22.

In step S3304, the PC-side CPU 21 (program display section 332) determines whether the log playback mode or the real-time playback mode is selected based on the information input from the PC-side operation section 8. If the real-time playback mode is selected, the PC side CPU 21 advances to step S3310. In step S3310, the PC-side CPU 21 (device value acquisition section 333a) acquires the device value from the real-time transmission section of the PLC 1 without going through the playback control module 324. In step S3311, the PC side CPU 21 (program display section 332) displays the device value on the display section 7 along with the user program included in the project data 71. If the log playback mode is selected, the PC side CPU 21 advances to step S3305.

In step S3305, the PC side CPU 21 (device value acquisition unit 333a) activates the playback control module 324 and acquires the display time and the device value of the log data 73 from the playback control module 324.

In step S3306, the PC side CPU 21 (program display section 332) displays the user program included in the project data 71, as well as the device value and display time on the display section 7.

In step S3307, the PC-side CPU 21 (display time control unit 331a) determines whether time designation is detected by the time UI 330a. As described above, time specification is performed by operating the time specification cursor 404. If the time designation is not detected, the PC side CPU 21 returns to step S3305. If the time designation is detected, the PC side CPU 21 advances to step S3308.

In step S3308, the PC side CPU 21 (display time control unit 331a) notifies the playback control unit 343 of the playback control module 324 of the designated time input using the time designation cursor 404. The PC side CPU 21 returns to step S3305.
●Waveform display module

FIG. 34 shows display processing performed by the waveform display module 322.

In step S3401, the PC-side CPU 21 (waveform display section 336) determines whether the log playback mode or the real-time playback mode is selected based on the information input from the PC-side operation section 8. If the real-time playback mode is selected, the PC side CPU 21 advances to step S3406. In step S3406, the PC-side CPU 21 (device value acquisition unit of the waveform display module 322) acquires the device value from the real-time transmission unit of the PLC 1 without going through the playback control module 324. In step S3407, the PC side CPU 21 (waveform display section 336) displays the device value on the display section 7. If the log playback mode is selected, the PC side CPU 21 advances to step S3402.

In step S3402, the PC-side CPU 21 (device value acquisition unit of the waveform display module 322) starts the playback control module 324 and acquires the device value and display time from the playback control module 324.

In step S3403, the PC side CPU 21 (waveform display section 336) displays the device value and display time on the display section 7.

In step S3404, the PC-side CPU 21 (display time control unit of the waveform display module 322) determines whether time designation is detected by the time UI 330b. As described above, the time specification is performed using the bar 103. If the time designation is not detected, the PC-side CPU 21 returns to step S3402. If the time designation is detected, the PC side CPU 21 advances to step S3405.

In step S3405, the PC-side CPU 21 (display time control unit of the waveform display module 322) notifies the playback control unit 343 of the playback control module 324 of the specified time input via the bar 103. The PC side CPU 21 returns to step S3402.
●Reproduction control module

FIG. 35 shows the playback control performed by the playback control module 324.

In step S3501, the PC side CPU 21 (log data acquisition unit 344) acquires the log data 73 from the PLC 1 and stores it in the PC side storage device 22.

In step S3502, the PC side CPU 21 (playback control unit 343) initializes the time of the internal clock.

In step S3503, the PC side CPU 21 (playback control unit 343) obtains the time of the internal clock and stores the time in the time device 342.

In step S3504, the PC side CPU 21 (playback control unit 343) obtains the device value corresponding to the display time held in the time device 342 from the log data 73, and stores it in the log device 345. This allows the device value providing unit 341 to provide the program display module 321 and waveform display module 322 with device values and display times.

In step S3505, the PC side CPU 21 (playback control unit 343) determines whether or not a time designation has been received from the display time control unit 331a. If the time designation has been received, the PC side CPU 21 advances to step S3506. If the time designation has not been received, the PC side CPU 21 advances to step S3507.

In step S3506, the PC side CPU 21 (playback control section 343) changes the time of the internal clock according to the time specification from the display time control section 331a.

In step S3507, the PC side CPU 21 (playback control unit 343) determines whether an instruction to change the update speed has been received from the display time control unit 331a. If the change instruction has been received, the PC side CPU 21 advances to step S3508. If no change instruction has been received, the PC side CPU 21 advances to step S3503.

In step S3508, the PC side CPU 21 (playback control section 343) changes the update speed of the internal clock according to the update speed specified by the display time control section 331a. Thereafter, the PC side CPU 21 proceeds to step S3503.
(Event history display function)

Furthermore, the PLC engineering tool according to the present embodiment can carefully select and record event logs that can lead to troubleshooting, and display the logs. The PLC and its expansion unit 4 have an event log function for recording various events that occur. There is also a logging function that records device values at every control cycle, arbitrary cycle, every rewrite, etc. When a problem occurs, the user can find the cause after the fact by combining these functions. However, various log functions are often recorded mainly in a non-volatile storage area on a PLC, and the size of such a non-volatile storage area of a PLC is often limited. Furthermore, when the number of logs increases and the storage area reaches its upper limit, it is common to delete the oldest logs in order to leave new logs. Therefore, when the number of logs that occur is on the order of thousands or tens of thousands of logs, there is a high possibility that the logs that lead to the resolution of the problem have been deleted, making it difficult to trace the cause of the problem. Ta. On the other hand, if the user narrows down the events to be saved in order to extend the recording time, there is a risk that events useful for troubleshooting may not be saved. On the other hand, even if the records remain without being deleted, if a large number of events are displayed, events that can lead to troubleshooting will be buried among other events, making them difficult to find.

Therefore, the PLC engineering tool according to the present embodiment carefully selects and records events that lead to troubleshooting. In addition, when displaying the carefully selected recorded events, it is possible to filter them and display related log information, making it easier for users to troubleshoot problems. Become. An example of such a PLC engineering tool is shown in the block diagram of FIG. 36.

The PLC engineering tool is a tool for evaluating a user program that defines the operation of the PLC 1. FIG. 36 shows a programmable logic controller system in which a PLC 1 is connected to a PC 2 in which a dedicated program, which is an engineering tool for PLC, is installed. Although this PLC engineering tool is implemented on a PC2 with a dedicated program installed, the present invention does not limit the PLC engineering tool to a PC with a dedicated program installed; may be realized. Further, in the example of FIG. 36, the PC2 and PLC1 are configured separately, but they may be integrated.

The PLC 1 shown in FIG. 36 also has the same configuration as the PLC described above. That is, a program execution section 514 that repeatedly executes a user program, a device section 34 having a device that is a storage area referenced by this program execution section 514, and a device value stored in this device section 34 as log data along with the current time. a temporary recording section 91a that records a plurality of events occurring in the PLC 1 or a controlled device controlled by the PLC 1 in chronological order as event data together with the time of occurrence, and a predetermined storage during operation. A storage memory 36 is provided for storing log data and event data recorded in the temporary recording section 91a when conditions are met. The PLC engineering tool is a program creation support device that is executed in the PLC 1 and supports the creation of a user program written in a graphical programming language.

The PLC engineering tool shown in FIG. 36 includes a display section 7, a PC-side CPU 21, a PC-side storage device 22, a PC-side memory section 11, a PC-side operation section 8, and a PC-side communication section 23. There is. The display unit 7 displays user programs such as ladder diagrams. Further, the display section 7 may be a monitor connected to the PC 2, or a display HMI may be used.

The PC side storage device 22 realizes the function of the driving record data holding section 22b. The driving record data holding unit 22b stores the log data and event data stored in the storage memory 36 during operation of the PLC 1 as driving record data.

The PC-side CPU 21 realizes the functions of the recording setting section 12, the device display control section 13, the event display control section 14, and the selection reception section 16. The event display control unit 14 displays a list on the display unit 7 of a plurality of events included in the event data read from the driving record data holding unit 22b and the times of occurrence of each of the plurality of events. The selection accepting unit 16 accepts the selection of one event from among the plurality of events displayed as a list by the event display control unit 14. The device display control unit 13 displays the device value recorded at the time corresponding to the time of occurrence of the event that is included in the log data read from the driving record data holding unit 22b and selected by the selection reception unit 16 in the user program. Display on top of each other. The event display control unit 14 is configured to selectively display a list of specific events that change the operating state of the PLC 1 or the operating state of a controlled device controlled by the PLC 1 on the display unit 7.

The recording setting section 12 also sets the temporary recording section 91a of the PLC 1 to record only a specific event among the plurality of events.

Here, the specific event includes an event related to an operation performed by the user independently of execution of the user program by the program execution unit 514. Events related to user operations include, for example, rewriting project data including the user program and PLC1 configuration information, mode switching between a setting mode for configuring PLC1 and an operation mode for executing a user program on PLC1, and connection to PLC1. Examples include insertion and removal of cables, insertion and removal of storage media that can be attached to the PLC 1, and turning on and off the power of controlled devices.

On the other hand, the event display control unit 14 hides events corresponding to processes automatically executed within the PLC 1 in accordance with execution of the user program by the program execution unit 514. Events corresponding to such automatically executed processes include, for example, the start or disconnection of communication when establishing a TCP connection or FTP connection with an external device connected to PLC1, or the opening or disconnection of communication to a folder or file prepared in PLC1. Examples include writing. In this way, the event display control unit 14 displays events corresponding to user operations, since they are useful for troubleshooting. On the other hand, events corresponding to processes that are automatically executed without user intervention are hidden. The reason why it is hidden is that automatically executed processes are too frequent, so if they were to be kept as a log, it would be huge. Also, since it is an internal process, I looked at the event log and found out how to troubleshoot based on this. This is because it is difficult to know whether this will lead to problems or not, so there are likely to be few situations where these are useful for troubleshooting. In this way, it is expected that the display content of events will be classified into those that are considered useful for troubleshooting and those that are not, and will be selectively displayed on the display unit 7 to assist the user in troubleshooting. can.

Hereinafter, details of each member will be explained based on FIG. 36. The record setting unit 12 sets various data such as driving record data to be stored in the PLC side storage device 32. The data stored in the PLC side storage device 32 includes a plurality of time-series device values recorded by the PLC 1 during operation of the PLC 1, first time data according to the recording time of each device value, and data controlled by the PLC 1 or the PLC 1. Examples include a plurality of events occurring in the controlled device, second time data corresponding to the time of occurrence of each event, and the like. As the PLC side storage device 32, a rewritable non-volatile memory inside the PLC 1, a removable SD card (trade name), etc. can be used. In particular, SD cards are preferable because data can be easily transferred. For example, even if the PC 2 is not connected to the PLC 1, it is possible to access data stored in the PLC side storage device 32.

The device display control unit 13 displays device values on the ladder diagram displayed on the display unit 7. The event display control unit 14 displays a list of multiple events on the display unit 7. At this time, the event display control unit 14 can selectively display a specific event that changes the operating state of the PLC 1 or the operating state of a controlled device such as a motor controlled by the PLC 1.

After making settings for the PLC using the PLC engineering tool shown in FIG. 36, the project data is transferred to the PLC side. Specifically, project data defining events to be recorded and their priorities is transferred from the PC-side communication unit 23 to the PLC-side communication unit 33 of the PLC 1. The project data may also include settings related to driving record data, user programs, settings for each function, and the like.
(Display section 7)

The display unit 7 displays a ladder diagram or the like. Specifically, the display unit 7 can include an event display field 1400 that displays a list of events, and a ladder monitor field 1500 that displays a ladder diagram. Then, in the event display field 1400, when the user selects an arbitrary event from the GUI using the selection reception unit 16, here by operating the PC side operation unit 8, a ladder diagram corresponding to the time of the selected event is displayed. is selected and displayed in the ladder monitor field 1500.

Further, the display section 7 may further include a camera monitor column 1600. The camera monitor column 1600 displays a plurality of image data captured in chronological order by the camera unit 98 connected to the programmable logic controller system. When an arbitrary event is selected in the event display column 1400, a ladder diagram corresponding to the time of the selected event is selected in the ladder monitor column 1500, and image data corresponding to the time of the selected event is displayed on the camera. It is displayed in the monitor column 1600.

The PLC 1 includes a PLC side CPU, a PLC side storage device 32, and a PLC side communication section 33. The PLC side storage device 32 stores a plurality of time-series device values recorded in the PLC 1, first time data corresponding to the recording time of each device value, and PLC 1 or A plurality of events occurring in the controlled device controlled by the PLC 1, second time data corresponding to the time of occurrence of each event, etc. are stored.

A plurality of device values and events are recorded separately in the PLC side storage device 32. After a certain amount of device values and events have been collected, old data is deleted, but events are preferably left for a longer period of time than device values. This corresponds to the fact that the cause of trouble may be caused not only by recent events but also by past changes. Furthermore, by saving the first time data of these device values and the second time data of the specific event, it is possible to synchronize them (details will be described later).

Here, the event display control section 14 selectively displays on the display section 7 a specific event that changes the operating state of the PLC 1 or the operating state of a controlled device controlled by the PLC 1. For example, an engineering tool for a programmable logic controller records carefully selected events that lead to troubleshooting in the PLC side storage device 32, and when displaying them, only those events may be filtered and displayed. This makes it possible to selectively display events that are useful for troubleshooting from among a wide variety of events, thereby making them useful for investigating the cause of troubles. Further, the event display control section 14 can display the device values as a time series waveform on the display section 7.

The PLC engineering tool may also include a synchronization software module 15. The synchronization software module 15 synchronizes the first time data, which is the display target time in the device display control unit 13, and the second time data, which is the display target time in the event display control unit 14, and displays the synchronized data in the display unit 7. It can be displayed.

Alternatively, instead of recording all events, only specific events selected from among the events may be recorded in the PLC storage device 32. For example, the recording setting unit 12 can be configured to record only specific events in the PLC storage device 32. As a result, by storing only specific events useful for troubleshooting in the storage device and displaying them on the display unit 7, it is possible to prevent events from being buried in events unrelated to troubleshooting without performing a search or narrowing down. It can be avoided. In this case, while all device values are recorded as driving record data, only specific events that change the operating state of the PLC 1 or the operating state of a controlled device such as a motor controlled by the PLC 1 are recorded. . This makes it possible to selectively display only the selected specific events in the event display column 1400. Also, by synchronizing specific events with separately recorded device values, it is useful for trouble analysis. Additionally, specific events that are selectively displayed may be prioritized.
(Specific event)

Specific events to be displayed on the display unit 7 include rewriting of project data including the user program of the PLC 1 and unit configuration information of each unit, power ON/OFF of a controlled device, and setting mode or programmable logic controller setting. Switching the operating mode that runs the logic controller, clearing various history, inserting and removing storage devices, inserting and removing Ethernet cables that communicate with other devices, device rewriting signals requested from the display HMI connected to the PLC system, Another example is a motion error in a motion unit connected to the PLC system. For example, mode switching indicates the timing of switching between the PROGRAM mode, which is the operating mode when the PLC 1 is set, and the RUN mode during actual operation. Further, the device rewrite signal from the display HMI is useful when it is desired to confirm whether or not the operation has been performed in accordance with a predetermined recovery procedure when a trouble occurs.
(Event log recording operation)

Here, the event log recording operation will be explained based on FIG. 37, which is a functional block diagram of the programmable logic controller system. The programmable logic controller system shown in this figure includes a CPU unit 3 and an expansion unit 4.
(CPU unit 3)

The CPU unit 3 includes a PLC-side CPU 31, a PLC-side time management section 83, an event management section 76, an event log memory section 75, a log memory section 73B, and a device memory section 34B. The PLC side CPU 31 executes user programs, exchanges data with the expansion unit 4, and performs data collection processing.
(PLC side time management section 83)

The PLC-side time management unit 83 is a member for managing the time at which events and log data are recorded.
(Device memory section 34B)

The device memory section 34B is a memory in which devices storing values used in programs and various functions are arranged. The device memory unit 34B can also record device rewriting from communication as an event. Detection is performed by the PLC side CPU 31.
(Event management department 76)

The event management unit 76 records the generated event in the event log memory unit 75. This event management section 76 receives an event issued from the PLC side CPU 31 asynchronously with the scan operation of the PLC 1, and stores it in an event log. That is, the event log can be recorded at any timing, independent of the repetition cycle of the END process of the PLC1. The event management section 76 also performs arbitration when a plurality of events occur at the same time, and control to sequentially erase data starting from the oldest data when the memory capacity of the event log memory section 75 becomes full.
(Event log memory section 75)

The event log memory section 75 is a memory that stores events that have occurred. The event log memory section 75 stores events together with second time data.
(Log memory section 73B)

The log memory unit 73B is a memory that stores collected data. These event log memory section 75 and log memory section 73B have common time data on the μs order, and can be linked at the scan level when displayed. Therefore, the log memory unit 73B records data collected as part of the scan operation in synchronization with the scan operation. Furthermore, when recording log data, it is recorded together with the first time data.
(Expansion unit 4)

The expansion unit 4 is one or more units to which controlled devices such as the camera section 98 and motion unit are connected. Each expansion unit 4 includes a buffer memory section 77 and a function execution section 96. The buffer memory section 77 is a memory in which values and monitor values for controlling the functions of the expansion unit 4 are stored. The function execution unit 96 executes the functions of the expansion unit 4. The function execution unit 96 also communicates information with the expansion bus-CPU unit control unit. For example, upon receiving a request from the PLC side CPU 31 or automatically operating, the status and results are stored in the buffer memory section 77. As an example, in the case of a motion-related expansion unit, if a motion-related error occurs, such as when the workpiece reaches the limit of the device, the function execution unit 96 detects it. It is also possible to issue an event from the expansion unit 4 side.
(Flowchart of event log recording operation (for events occurring in CPU unit 3))

In the programmable logic controller system of FIG. 37, the operation of recording an event log can be performed for events occurring on the CPU unit 3 side or for events occurring on the expansion unit 4 side.

Next, the operation of recording events occurring in the CPU unit 3 will be explained based on the flowchart of FIG. 38. First, in step S3801, the PLC side CPU 31 of the CPU unit 3 detects an event. Next, in step S3802, the event management section 76 receives an event from the PLC side CPU 31 of the CPU unit 3. Then, in step S3803, the remaining capacity of the event log memory unit 75 is confirmed. If there is no remaining capacity, the process advances to step S3804, and old events are deleted from the event log memory unit 75. On the other hand, if there is remaining capacity, the process advances to step S3805, where time data on the μs order is acquired and the event is stored in the event log memory unit 75.

Next, the operation of recording events occurring in the expansion unit 4 will be explained based on the flowchart of FIG. 39. First, in step S3901, the function execution unit 96 of the expansion unit 4 detects an event. Next, in step S3902, the function execution unit 96 of the expansion unit 4 transmits the message communication containing the event to the expansion bus. Furthermore, in step S3903, the PLC side CPU 31 of the CPU unit 3 uses interrupt processing to receive message communication containing an event from the expansion bus. Next, in step S3904, the PLC side CPU 31 of the CPU unit 3 extracts the event from the message communication. Furthermore, in step S3905, the event management section 76 receives an event from the PLC side CPU 31 of the CPU unit 3. Then, in step S3906, the remaining capacity of the event log memory unit 75 is confirmed. If there is no remaining capacity, old events are deleted from the event log memory unit 75 in step S3907, and the process advances to step S3908. On the other hand, if there is remaining capacity in step S3906, the process advances to step S3908 to acquire time data in μs order and store the event in the event log.

Next, the filtering operation when displaying the event log will be explained based on the flowchart of FIG. 40. First, in step S4001, all event logs are read into memory. Next, in step S4002, a group of events to be filtered when displaying events is selected using the UI. Furthermore, in step S4003, one event is extracted from the event log. In step S4004, if the extracted event corresponds to the event selected on the UI, it is stored in the display event log. Furthermore, in step S4005, it is determined whether or not there are any events left in the event log memory section 75. If any events remain, the process returns to step S4003 and repeats the process. On the other hand, if there are no event logs remaining, the process advances to step S4006, and all event logs for display are displayed on the GUI.
(Example of events to be selectively displayed)

Examples of events that are selectively displayed are shown below. First, a severe error is a serious error that prevents the PLC 1 from continuing operation. The main body for detecting severe errors is the CPU unit 3 (control unit/peripheral control).

Moreover, a minor error is a minor error that allows the PLC 1 to continue operating. However, minor errors may not lead to a solution to the problem. The CPU unit 3 (control unit/peripheral control) and the expansion unit 4 are responsible for detecting longitude errors.

Power ON/OFF is an event related to power on and off. It may occur around trouble. The main body for detecting power ON/OFF is the CPU unit 3 (peripheral control).

Alarm relay is a user-specified alarm history. The main body that detects the alarm relay is the CPU unit 3 (PLC side CPU 31).

Device value modification is rewriting of device values through communication. Depending on the device, this may occur regardless of the problem, but it may also be the starting point of the problem. The main body that detects this device value change is the CPU unit 3 (PLC side CPU 31).

Driving record storage relates to the timing of a storage trigger and recording of driving record data. This driving record data can also serve as a starting point for trouble analysis. The main body that detects the storage of driving records is the CPU unit 3 (PLC side CPU 31).

The RUN/PROGRAM switching is information related to switching the operation mode of the PLC1. Trouble may occur when switching modes, but it also occurs during normal operation. The main body that detects the RUN/PROGRAM switching is the CPU unit 3 (PLC side CPU 31).

Project changes are considered useful for trouble analysis because troubles often occur due to changes in the program of the PLC 1, for example. The main body that detects the project change is the CPU unit 3 (PLC side CPU 31).

Clearing the history can also be used as a basis for determining troubleshooting. In particular, when it was deleted can be an important factor. The CPU unit 3 (event management section 76) also detects the history clearing.

Inserting and removing a memory card may be the key to solving problems. On the other hand, depending on how the device is operated, events may occur every day even when no trouble occurs. The main body for detecting the memory card is the CPU unit 3 (peripheral control).

The calendar timer is a candidate because it may be important to record changes in the calendar timer value in order to analyze troubleshooting based on historical data. On the other hand, if you operate a system that automatically adjusts the time, events will occur periodically. The detection main body of the calendar timer is the CPU unit 3 (peripheral control).

Ethernet communication is a candidate because connection events at the Ethernet hardware level may occur as a sign of a failure such as a poor contact. However, it occurs every day even when the power is turned on and off. The main body that detects Ethernet communication is the CPU unit 3 (peripheral control) and the expansion unit 4.

Serial communication is considered beneficial because serial hardware-level connections can be a sign of failure, such as poor contact. The main body that detects serial communication is the expansion unit 4.

An event error is an error that occurs when a large number of events occur. The main body that detects event errors is the CPU unit 3 (event management section 76).

As described in the discussion on such problems, depending on the type of event, there are times when you want to mask it, and there are times when you want to display it without masking it. In other words, the necessity of a mask changes depending on how the user operates the device. Therefore, we made it possible for the user to select the display for each group.

When selecting an event, display filtering settings can be made individually for each group, for example, in the error event history filter setting section 1370 shown in FIG. Here, you select an error or event to hide from among the displayed candidate errors or events. In this example, events to be displayed are listed on the left side of the screen in a display list 1371, and events to be hidden are listed on the right side in a hidden list 1372, and each event can be displayed or hidden by moving freely. You can choose which.
(Example of an event that is recorded as an event but not displayed)

Next, an example of an event that is recorded as an event but intentionally not displayed will be explained. These are events that, even if disclosed to the user, do not directly lead to disclosure of troubles by the user.

First, detailed information when a program compilation error occurs on the PLC 1 is not displayed even if it is disclosed to the user because it is difficult to show how to deal with it.

Firmware update information is not displayed because the recording format may change due to firmware updates and it may not be possible to continue recording.

The self-test implementation history is not displayed because it is difficult to show users how to deal with it even if it is made public.
(List of events that are intentionally not recorded (high priority))

Next, examples of events with high priority among the events that are intentionally not recorded are shown below. First, depending on how the user program is configured, the number of events can easily overflow the log, so the start/end of TCP connection communication is excluded from the record. In the case of a system that disconnects communication after each communication, events may occur on the order of multiple times per second.

Furthermore, when starting/disconnecting an FTP connection, the number of events will increase if the FTP connection is used in such a way that a file is updated to a higher level every time one piece of data is collected.

Furthermore, when writing to a folder/file, the number of events increases if data is recorded on a memory card each time data is collected.

Next, we will explain examples of events that are excluded from recording because they are unlikely to occur during system operation and may not lead to troubleshooting. First, remote operation request reception is excluded from the record because it is a function that is likely to be used not during operation but during device programming, startup, and debugging. In addition, setting forced value refresh, resetting forced value refresh, canceling all forced value refresh, canceling forced value refresh, etc. can all be used not during operation, but when debugging the device or analyzing after a problem occurs. This function is highly sensitive, so it will be excluded from recording.
(Example of an event that is intentionally not recorded (low priority))

Furthermore, an example of a low priority event that is intentionally not recorded will be explained. First, depending on how the system is set up, recipe execution operations can cause an event to occur for each work, easily overflowing the log capacity.

Furthermore, the start of the DB connection service, the stop of the DB connection service, and the end of the DB connection service are all events that occur frequently during operation, and the log capacity may easily overflow.

In addition, user authentication enable/disable, logon success, logon failure, CPU unit backup success, CPU unit backup failure, CPU unit restore success, CPU unit restore failure, etc. all occur during device programming, not during operation. This is a function that is likely to be used when starting up or debugging.

Here, how the device display control section 13 and the event display control section 14 selectively display specific events on the display section 7 will be described based on the GUI screen of the PLC engineering tool 1380 in FIG. 42. The PLC engineering tool 1380 shown in this figure represents a project data editing program or a display UI provided by the program display module 321. This project data editing program has the log playback mode (replay mode) selected in the mode selection section 50D, and functions as a project data playback program in which editing is prohibited. Note that a project data reproducing program that only reproduces project data without an editing function is also included in a type of PLC engineering tool.

This project data editing program has a project display area 420 on the left, a program display area 410 in the center, and an event display column 1400 on the right. Further, the program display area 410 has a ladder monitor field 1500 in the upper part and a playback control field 402 in the lower part. A ladder monitor column 1500 displays a ladder program (ladder diagram).
(Playback control column 402)

In the playback control field 402, playback control for playing back the event selected in the event display field 1400 or the like is performed. Specifically, the function of the reproduction control module 324 in FIG. 31 reads driving record data including recorded device values and image data corresponding to the selected event from the PLC storage device 32 and reproduces it. The playback control field 402 includes a slider-like operation bar 404d representing a time axis, a time designation cursor 404 that can be moved on the operation bar 404d, a speed designation section 405, and a playback button 406, as described in FIG. 32 and the like. , a one-step reverse playback button 407, a one-step playback button 408, and the like.

By pressing the playback button 408, the state of past events can be played back. Furthermore, by operating the time designation cursor 404 on the operation bar 404d, it is possible to select which time state to reproduce. Further, the device display control section 13 and the event display control section 14 are linked, and the display of each part is linked depending on the item selected by either of them. For example, when a playback time is specified by clicking on the operation bar 404d in the playback control field 402, the device value at the specified playback time is displayed on the ladder diagram in the ladder monitor field 1500. Similarly, in the event display column 1400, events that occurred at the playback time specified on the operation bar 404d are displayed in reverse video. On the other hand, by clicking on any of the events listed in the event display column 1400, the playback time on the operation bar 404d moves in conjunction. In this way, by interlocking ESMs, trouble analysis becomes easier.

Note that it may be possible to determine whether the event displayed in the event display field 1400 is an event that occurred within the collected driving record data. For example, by coloring and displaying events that occur in driving record data, the user can visually distinguish them.

FIG. 43 shows an example of displaying a specific event in the event display column 1400. Here, in the event display column 1400, Ethernet link up and Ethernet link down are displayed as a list. Ethernet link up indicates that an Ethernet connection has started. This Ethernet link-up occurs, for example, when an Ethernet cable is connected, when a hub is powered on, and the like. Further, "Ethernet link down" indicates that the Ethernet connection has been terminated. For example, this occurs when the Ethernet cable is disconnected or when the power to the hub is turned off. In the example in Figure 43, the Ethernet link up and down are repeated in a short period of time, making the Ethernet connection unstable, and as a result, it is assumed that a trouble has occurred and the save trigger is turned ON. Ru.

Note that in FIG. 43, among the events displayed in the event display field 1400, an event 1402 highlighted, such as colored, indicates that the event occurred during the recording time of the device display control section 13. Furthermore, an event 1401 highlighted in the event display field 1400 is an event related to the currently selected playback display. The position of the time designation cursor 404 in the playback control field 402 is moved in accordance with the playback time selected in the event display field 1400. Similarly, device values are displayed in the corresponding ladder diagram in the ladder monitor column 1500. Furthermore, when the time designation cursor 404 in the playback control field 402 is moved, the displays in the event display field 1400 and the ladder monitor field 1500 are updated accordingly to display the corresponding playback time.

The operation bar 404d in the playback control field 402 may display a save trigger bar 404e at the time when an event that causes a save trigger (save trigger occurrence event) occurs. The storage trigger bar 404e is shown in red or the like to make it easier to see. In the example of FIG. 43, since the trigger event is selected in the event display field 1400, the gray time designation cursor 404 and the red trigger event are displayed overlappingly on the operation bar 404d. Therefore, in the time display area 409 indicating the playback time specified by the time designation cursor 404, 2018/11/20 11:20:46 is displayed, which is the same as the second time data selected and highlighted in the event display field 1400. has been done.

Further, in the playback control column 402, a scan number display area 409b may be provided in parallel with the time display area 409, indicating the total number of scans and the number of scans currently being displayed. In the example of FIG. 43, it can be seen that device value sets for a total of 360,629 scans are stored as driving record data. Also, in the time display area 409, the playback time (11:20:46) currently specified by the current time designation cursor 404 is displayed, and at this playback time, the device value set of the 193526th scan is displayed on the ladder monitor. What is displayed in the display field is shown in the scan number display area 409b.

FIG. 44 shows a state in which the time designation cursor 404 is moved to the right side, that is, to a time advanced from FIG. 43 from the state shown in FIG. Here, the time designation cursor 404 is positioned later than the save trigger bar 404e on the operation bar 404d. That is, as the time designation cursor 404 is moved to the right, the time advances, and as it moves to the left, the time advances.

Further, the operation bar 404d corresponds to the recording time of the driving record data stored in the PLC side storage device 32. That is, the left end of the operation bar 404d is the time when recording of driving record data starts, and the right end is when recording of driving record data is finished. As described above, the save trigger bar 404e is displayed on the operation bar 404d at the time when the save trigger event for recording driving record data occurs. That is, in the operation bar 404d, the left side of the save trigger bar 404e shows the collection time Ta before the save trigger, and the right side of the save trigger bar 404e shows the collection time Tb after the save trigger.

In the example of FIG. 44, the second time data of the event "Ethernet link down", which is the event selected in the event display field 1400, is 11:20:49 on 2018/11/20, so this is linked. The time displayed in the time display area 409 of the playback control field 402 is also displayed to match this time. Note that in the ladder monitor field of FIG. 44, some input contacts and some output elements are displayed in color. This indicates that these input contacts and output elements are ON at the time when the time designation cursor 404 is at the position shown in FIG.

Further, FIG. 45 shows an example in which an event other than the highlighted event 1402 is selected in the event display field 1400. For events that are not highlighted in the event display column 1400, driving record data such as device values are not stored, so the storage period is exceeded, and corresponding driving record data does not exist. In this example, 2018/11/20 10:38:08 is selected in the event display field 1400, but since driving record data for this time is not saved, the time designation cursor 404 is selected in the playback control field 402. is stuck to the left end, which is the lower limit of the operation bar 404d. In other words, since the operation bar 404d cannot express times before or after the storage period, if a time outside the storage period is selected in the event display field 1400, linked display cannot be performed, so the operation bar 404d displays the nearest corresponding time. moved to value. Specifically, the time designation cursor 404 is positioned at the left end of the operation bar 404d if the time is older than the retention period, and at the right end of the operation bar 404d if the time is newer than the retention period.

In addition, the time display area 409 displays the time 2018/11/20 11:20:20, which corresponds to the right end of the operation bar 404d, and the driving record data saved by the save trigger indicated by the save trigger bar 404e is 2018/11/20 11:20:20. /11/20 11:20:20 onwards. Further, the scan count display area 409b indicates the first scan count, which is the oldest scan count.

Note that in the event display column 1400, events after 2018/11/20 11:20:38 are highlighted. This is because there was no particular event from 2018/11/20 11:20:20 to 11:20:37 within the retention period, and since there are no events recorded during this period, the event display field 1400 is also in a state where there is no display. Furthermore, in FIG. 45, the number of input contacts and output elements displayed in color is increased compared to FIG. 44. This indicates that at the time when the time designation cursor 404 is at the position shown in FIG. 45, the number of input contacts and output elements that are turned ON is greater than in FIG. 44.
(Camera monitor column 1600)

In the above example, the display of the event display field 1400, the playback control field 402, and the ladder monitor field 1500 is synchronized, but in addition to this, the image data captured by the camera unit 98 is also synchronized. It can be displayed. Such an example is shown in the GUI of FIG. In this example, a camera monitor column 1600 for displaying image data is provided at the upper right of the screen. Similarly in this example, when an arbitrary event is selected in the event display field 1400, image data captured at a time corresponding to the time of the selected event is displayed, and the time designation cursor 404 in the playback control field 402 is also will be moved to the corresponding playback time. Further, when the play button 406 is pressed, the video is played in the camera monitor field 1600, and the selection in the event display field 1400 switches to the corresponding event as time passes, and the device in the ladder diagram in the ladder monitor field 1500 is changed. The values will also be updated. This makes it possible to dynamically reproduce the behavior when a trouble occurs, which can be effective in investigating the cause of the trouble.

The program creation support device for a programmable logic controller according to the present invention can be suitably used for troubleshooting a PLC system in an FA.

1...PLC
2...PC
3...CPU units 4, 4a, 4b...Extension unit 4c...Camera input extension unit 4d...Motion unit 4e...Communication unit 5...PLC side display section 6...PLC side operation section 7...Display section 8...PC side operation section 9... Communication cables 10, 10a, 10b...Field device 11...PC side memory section 12...Record setting section 13...Device display control section 14...Event display control section 15...Synchronization software module 16...Selection reception section 21, 21B...PC side CPU
22...PC side storage device 22b...driving record data holding section 23...PC side communication section 31...PLC side CPU
32... PLC side storage device 33... PLC side communication section 34... device section; 34a... CPU unit device section; 34b... expansion unit device section 34B... device memory section 35... project storage section 36... storage memory; 36A... memory card 36B ...Driving record data storage unit 37...Internal memory 38...Bus master 39...Record control unit 41...CPU
42...Memory 45...Save condition setting unit 46...Record buffer setting unit 47...Save trigger setting unit 50...Project creation unit 50B...Project editing unit 50B1...TPJ interpretation unit; 50B2...kpr interpretation unit 50C...Save control unit 50D...Mode Selection section; 50D1...Mode selection field 51, 51B...Log setting section 52...Component specification section 53...Device extraction section 54...Addition section 55...Deletion section 56...Merge section 57...Identification section 58...Manual setting section 59...Estimation section 60...Function specification section 61...Log display control section 62...Function setting section 63...Program creation section 71...Project data 72...Log setting data 73...Log data 73B...Log memory section 74...Log data storage section 75...Event log memory Unit 76...Event management unit 77...Buffer memory unit 80...Execution unit 80a...Ladder execution engine 80b...Unit control unit 81...Recording unit 82...Detection unit 83...Time management unit 84...Output unit 90...Inter-unit bus 91a...Temporary Recording section 93...Storage section 96...Function execution section 98...Camera section 101...Pointer 150...Unit setting UI
151...Name column 152...Input area column 153...Output area column 154...Occupied area column 201...Inter-unit communication 202...Program execution 204...END processing 311...Editing section 312...Adding section 313...Calculating section 314...Debug section 321... Program display module 322... Waveform display module 323... Image display module 324... Playback control module 325... Unit display module 330a... Time UI
331a...Display time control section 332...Program display section 333a...Device value acquisition section 334...Verification section 335...Warning section 341...Device value provision section 342...Time device 343...Reproduction control section 344...Log data acquisition section 345...Log device 400...Display UI
401a...Icon 401b...Icon 402...Playback control field 403...Display area 404, 404a...Time specification cursor 404d...Operation bar 404e...Save trigger bar 405...Speed specification section 406...Playback button 407...One step reverse playback button 408...One step Play button 409...Time display area 409b...Scan count display area 410...Program display area 420...Project display area 430...Camera monitor 440...Unit monitor 450...Ladder monitor 514...Program execution unit 1000, 2000...Programmable logic controller system 1200... Program creation support device 1300...User program creation support program 1310...Program editing screen 1312...Device value input field 1314..."Overwrite" button 1320...Point parameter editing field 1322...Speed specification field 1330...File menu 1332..."Project by another name"keep"
1334..."Saveproject"
1340..."Save project under another name" dialog screen 1336..."Project - project matching"
1350... Comparison display screen 1370... Error event history filter setting section 1371... Display list 1372... Hidden list 1400... Event display column 1401... Highlighted event 1402... Highlighted event 1500... Ladder monitor column 1600... Camera monitor Column Ld...Ladder diagram T...Scan time Ta...Collection time Tb...Collection time WK...Object

According to the program creation support device for a programmable logic controller according to the first aspect of the present invention, the programmable logic controller is composed of one or more units including a unit to which a camera section is connected , and repeatedly executes a user program. a program execution unit; a device unit having a device that is a storage area referenced by the program execution unit; and a device unit that records device values stored in the device unit in chronological order as log data together with the current time; or a temporary recording unit that records multiple events occurring in a controlled device controlled by the programmable logic controller in chronological order as event data together with the time of occurrence, and the temporary recording when predetermined storage conditions are met during operation. Executed in the programmable logic controller, which includes a storage unit that stores log data and event data recorded in the unit in a storage memory, and stores a plurality of image data captured in chronological order by the camera unit in the storage memory. A program creation support device for supporting the creation of the user program written in a graphical programming language, the program creation support device comprising: log data and event data stored in the storage memory during operation of the programmable logic controller; image data from a driving record data storage unit that stores the image data as driving record data, an event display field that displays a list of the events, a ladder monitor field that displays the ladder diagram that is the user program, and the driving record data storage unit. a display unit that displays a camera monitor field that displays the plurality of read image data in chronological order ; a plurality of events included in the event data read from the driving record data storage unit; and times of occurrence of each of the plurality of events. an event display control unit that displays a list of events in the event display field , a selection reception unit that receives a selection from among a plurality of events listed by the event display control unit, and reads out the driving record data from the driving record data storage unit. displaying a device value included in the selected log data and recorded at a time corresponding to the time of occurrence of the event selected by the selection reception unit over the user program displayed in the ladder monitor field; and a device display control section, when one event is selected by the selection reception section in the event display field, the display of the device value in the ladder monitor field is linked according to the occurrence time of the selected event. The image data may be updated and the image data corresponding to the time of occurrence of the selected event may be displayed in the camera monitor field . With the above configuration, events useful for troubleshooting can be selectively displayed from among a wide variety of events, and can be useful for investigating the cause of troubles.

Further, according to the program creation support device for a programmable logic controller according to the second aspect, in addition to the above configuration , the display target time in the device display control section, the display target time in the event display field, and the camera monitor A synchronization software module may be provided for synchronizing the display of image data displayed in the column.

Furthermore, according to the program creation support device for a programmable logic controller according to a third aspect, in addition to any of the above configurations , the display section operates the display target time of the device value displayed in the ladder monitor field. When one event is selected by the selection reception unit in the event display field, the time UI display area displays a time UI for The display of the time UI in is updated in conjunction, and image data corresponding to the time of occurrence of the selected event can be displayed in the camera monitor field.

Furthermore, according to the program creation support device for a programmable logic controller according to a fourth aspect, in addition to any of the above configurations, the time UI includes a play button, and the play button is operated in the time UI display area. Then, device values are displayed and updated in chronological order in the ladder monitor field, a video consisting of the plurality of image data is played in the camera monitor field, and a response is displayed in the event display field according to the passage of time. The events to be performed can be switched .

Furthermore, according to the program creation support device for a programmable logic controller according to the fifth aspect, in addition to any of the above configurations , the display section is further configured to be associated with image data to be displayed in the camera monitor column. A time designation cursor for designating the time specified by the time designation cursor is displayed, and the image data displayed in the camera monitor field is updated according to the time designated by the time designation cursor, and the time UI in the time UI display area is updated. The display can be updated accordingly .

Furthermore, according to the program creation support device for a programmable logic controller according to a sixth aspect, in addition to any of the above configurations , the storage section of the programmable logic controller stores the log data, the event data, and the plurality of log data. image data is stored in the storage memory as a package made up of a plurality of files, and the driving record data holding unit stores the package made up of the plurality of files stored in the storage memory as the driving record data. can.

Furthermore, according to the program creation support device for a programmable logic controller according to the seventh aspect, in addition to any of the above configurations , the driving record data includes management information data indicating the contents of the package consisting of the plurality of files. can include .

Furthermore, according to the program creation support device for a programmable logic controller according to an eighth aspect, in addition to any of the above configurations , the storage unit stores the log data, the event data, and the plurality of image data. storing project data including configuration information of the user program and the unit in a storage memory;
The display section displays the user program and the configuration information of the unit included in the project data read from the driving record data holding section, and the device display control section displays the log data read from the driving record data holding section. and is recorded at a time corresponding to the time of occurrence of the event selected by the selection receiving unit, on the user program included in the project data read from the driving record data holding unit. can be displayed .

Claims (11)

A programmable logic controller composed of one or more units, including a program execution unit that repeatedly executes a user program, a device unit that has a device that is a storage area referenced by the program execution unit, and a device that is stored in the device unit. Device values are recorded in chronological order as log data together with the current time, and multiple events occurring in the programmable logic controller or a controlled device controlled by the programmable logic controller are recorded in chronological order as event data together with the time of occurrence. A graphical programming language executed in the programmable logic controller, comprising a temporary recording section for storing log data and event data recorded in the temporary recording section when predetermined storage conditions are met during operation. A program creation support device for supporting the creation of the user program described in
an operation record data holding unit that stores log data and event data stored in the storage memory during operation of the programmable logic controller as operation record data;
a display unit that displays the user program;
an event display control unit that displays a list of a plurality of events included in the event data read from the driving record data holding unit and the occurrence times of each of the plurality of events on the display unit;
a selection reception unit that accepts one selection from among the plurality of events listed by the event display control unit;
Displaying a device value included in the log data read from the driving record data holding unit and recorded at a time corresponding to the time of occurrence of the event selected by the selection reception unit over the user program. a device display control section;
A program creation support device for a programmable logic controller. The program creation support device for a programmable logic controller according to claim 1, further comprising:
A program creation support device for a programmable logic controller, comprising a recording setting section configured to set the temporary recording section of the programmable logic controller to record only the specific event among the plurality of events. The program creation support device for a programmable logic controller according to claim 1,
A program creation support device for a programmable logic controller, wherein the specific event includes an event related to an operation performed by a user independently of execution of the user program by the program execution unit. The program creation support device for a programmable logic controller according to claim 3,
The event related to the user operation includes at least
rewriting project data including configuration information of the user program and the programmable logic controller;
mode switching between a setting mode for setting the programmable logic controller and an operation mode for executing the user program on the programmable logic controller;
Insertion and removal of a cable connectable to the programmable logic controller;
Inserting and removing a storage medium that can be attached to the programmable logic controller, and turning on/off the power of the controlled device
A program creation support device for programmable logic controllers, including: The program creation support device for a programmable logic controller according to claim 1,
The event display control unit is configured to hide events corresponding to processing automatically executed within the programmable logic controller in accordance with execution of the user program by the program execution unit. The program creation support device for a programmable logic controller according to claim 5,
The event corresponding to the automatically executed process includes at least the following:
Program creation support for the programmable logic controller, including starting or disconnecting communication when making a TCP connection or FTP connection with an external device connected to the programmable logic controller, and writing to a folder or file prepared in the programmable logic controller. Device. The program creation support device for a programmable logic controller according to claim 1, further comprising:
comprising a synchronization software module that synchronizes the display target time in the device display control unit and the display target time in the event display control unit,
A program creation support device for a programmable logic controller, wherein the synchronization software module causes the device display control section and the event display control section to be displayed in conjunction with each other on the display section. The program creation support device for a programmable logic controller according to claim 7,
The display section is
an event display field for displaying a list of the events;
and a ladder monitor field for displaying the ladder diagram that is the user program,
Creating a program for a programmable logic controller in which, when an arbitrary event is selected from the event display field in the selection reception section, a ladder diagram corresponding to the time of the selected event is selected and displayed in the ladder monitor field. Support equipment. The program creation support device for a programmable logic controller according to claim 8,
The recording setting unit is configured to store a plurality of image data captured in chronological order by a camera unit connected to the programmable logic controller in the storage memory,
The display unit further includes a camera monitor field for displaying a plurality of image data captured in chronological order by the camera unit,
When an arbitrary event is selected from the event display column in the selection reception section, a ladder diagram corresponding to the time of the selected event is selected in the ladder monitor column, and a ladder diagram corresponding to the time of the selected event is selected. A program creation support device for a programmable logic controller in which corresponding image data is displayed in the camera monitor field. A program creation support device for a programmable logic controller according to claim 9,
A program creation support device for a programmable logic controller, wherein the storage memory is an SD card (product name). A program creation support device for a programmable logic controller according to any one of claims 1 to 10,
A program creation support device for a programmable logic controller, wherein the event display control section displays device values as time-series waveforms on the display section.

Images