JP7356778B2 - Program creation support device for programmable logic controllers - Google Patents

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).

Therefore, the present applicant has previously developed a technique for reproducing a ladder program using device values recorded in advance (see Patent Document 1). According to this, by recording and reproducing changes over time in the states of devices such as switches, valves, and sensors that are displayed for monitoring sequence control states during simulation or actual control, changes over time can be changed with simple instruction operations. By displaying the program along with the change in the state of the device over time, it becomes easy to associate the program with the change in the state of the device over time.

Japanese Patent Application Publication No. 10-011118

However, according to the above technology, when trying to investigate the cause of a trouble when it occurs, it is possible to play back a specific ladder program using the recorded device values, but it is possible that the played ladder program is the one that caused the trouble in the first place. It was not possible to confirm whether it was the ladder program that caused the problem. Although it is conceivable to save the ladder program along with the device values, there is also a possibility that the ladder program will be modified during the process of debugging by trial and error in order to solve a problem. If even a portion of the project data were to change unintentionally in this way, there was a concern that the reliability would be compromised and troubleshooting such as correct operation verification would be hindered.
One object of the present invention is to provide a program creation support device for a programmable logic controller that improves the reliability of project data included in data that stores the situation at the time of trouble occurrence, in order to solve troubles.

Means for solving the problem and effects of the invention

According to a program creation support device for a programmable logic controller according to a first aspect of the present invention, the programmable logic controller is configured of one or more units, and includes a project storage section that stores project data including a user program, and a project storage section that stores project data including a user program. A program execution unit that repeatedly executes the user program included in the data, a device unit that has a device that is a storage area referenced by the program execution unit, and a device value stored in the device unit that is chronologically recorded as log data. said storage memory comprising: a temporary recording section for temporarily recording; and a storage memory for storing log data recorded in said temporary recording section together with said project data stored in said project storage section when a predetermined storage condition is met during operation; A program creation support device for supporting the creation of the user program executed by the programmable logic controller, the program creation support device comprising: log data stored in the storage memory during operation of the programmable logic controller; an operation record data storage unit that includes the user program being executed by the program execution unit when the log data is saved in the storage memory, and stores the project data saved in the storage memory as operation record data; a log display control unit that reads the driving record data from the driving record data storage unit and displays log data in the driving record data in association with project data; and a project displayed by the log display control unit. a project editing section that receives a data editing instruction and edits the project data; and the project data being edited by the project editing section is project data in the driving record data stored in the driving record data storage section. and, based on the determined result, edit project data edited by the project editing unit with respect to the project data in the driving record data stored in the driving record data storage unit. and an overwrite restriction control section that restricts overwriting of the . With the above configuration, 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.

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 overwrite restriction control unit is configured to control the overwrite restriction control unit when the project editing unit attempts an overwrite operation on the project data. It is possible to detect this and display an overwrite prohibition pop-up.

Furthermore, according to the program creation support device for a programmable logic controller according to a third aspect, in addition to any one of the above configurations, the overwrite restriction control section controls the driving record stored in the driving record data storage section. When receiving an instruction to save the project data edited by the project editing department for the project data in the data, the edited project data is saved as a separate file from the project data included in the operation record data. Can be configured to save.

Furthermore, according to the program creation support device for a programmable logic controller according to the fourth aspect, in addition to any of the above configurations, an editing mode for editing project data and display control by the log display control section are further provided. The project editing section may include a mode selection section that selects at least one of the history playback modes to be performed, and the project editing section can accept editing instructions in the editing mode and prohibit acceptance of editing instructions in the history playback mode.

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 driving record data includes first driving record data and second driving record data, The first driving record data and the second driving record data can be distinguished by identification information.

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, the identification information can be an extension of a data file.

Furthermore, according to the program creation support device for a programmable logic controller according to a seventh aspect, in addition to any of the above configurations, the first driving record data is compressed, and the log display control unit is configured to When reading the first driving record data, the first driving record data can be decompressed.

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, a comparison display of project data in the first operation record data and the second operation record data is provided. It is possible to include a comparison display section that performs the following.

Furthermore, according to the programmable logic controller program creation support device according to the ninth aspect, in addition to any of the above configurations, the programmable logic controller program creation support device further includes a work memory for performing editing work, and the log display control unit: The driving record data may be read from the driving record data storage unit to the working memory, and display control may be performed in association with log data and project data in the driving record data.

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 log data can include device data.

Furthermore, according to the programmable logic controller program creation support device according to the eleventh aspect, in addition to any of the above configurations, the driving record data is an image captured by a camera input expansion unit that captures an image of a target object. Can contain files.

Furthermore, according to the program creation support device for a programmable logic controller according to the twelfth aspect, in addition to any of the above configurations, the user program can include a ladder program.

Furthermore, according to the program creation support device for a programmable logic controller according to the thirteenth aspect, in addition to any of the above configurations, the programmable logic controller of each unit is configured with a plurality of units, and the unit configuration information is , the functions of each unit, and information on connection positions between units.

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 field. 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. It is a figure explaining the function of CPU of a CPU unit. 3 is a flowchart showing an overview of debugging processing. FIG. 3 is a diagram illustrating a project creation section.

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 composed of an internal memory, a removable memory card 36A, and the like as a 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. When the second trigger condition for the save trigger is met, the save control unit 50C saves log data, which is temporarily held in the recording unit 91a by the record control unit 39 and corresponds to the immediately previous record trigger viewed from the save trigger, in the save memory. do. 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 media. 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 operation record data storage section 36B stores the log data saved in the storage memory 36 during operation of the PLC 1 and the project data including the user program being executed by the program execution section 514 when the log data was saved. Store as recorded data.

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. Note that the log display control unit 61 does not necessarily need to associate the project data and the log data.

The PC-side CPU 21 implements functions such as a project editing section 50B, a log display control section 61, and an overwrite restriction control section 50E. 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 overwrite restriction control unit 60E restricts overwriting of the edited project data edited by the project editing unit 50B over the project data in the driving record data stored in the driving record data storage unit 36B.
(Overwrite regulation control unit 50E)

The overwrite restriction control unit 50E restricts overwriting of the edited project data edited by the project editing unit 50B over the project data in the driving record data stored in the driving record data storage unit 36B. 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 overwrite restriction control unit 50E restricts the project data in the driving record data stored in the driving record data storage unit 36B from being overwritten and saved in the state edited by the project editing unit 50B. do. 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. The extension is, for example, 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 the file menu 1330 in FIG. 17 by using the "Save Project" button 1334 or the general keyboard shortcut keys Ctrl+S, the overwrite restriction control unit 50E 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 can also do this. 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 overwrite restriction control unit 50E that restricts the overwrite storage operation described above is performed when the original project data and user program included in the driving record data at the time of trouble occurrence have not been copied and saved under a different name. Once executed and 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 overwrite restriction control unit 50E will be described 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 overwrite restriction control unit 50E 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. Note that if you save the project to the input save path, a new file corresponding to different project data from the project data in the driving record data (a file with the same extension kpr but a different file name) will be created. ) is generated. For convenience, this file will be referred to as an "edited file." It is also possible to replay log data using the edited file. In this case, the user opens the edited file on the UI of the display unit 7 and specifies the path where the log data in the driving record data is saved. This allows the log data to be played back on the ladder program included in the edited file. Note that by automatically associating the edited file with the path where the log data in the driving record data is saved (such as automatically embedding the path in the edited file), the user can Specifying the log data path above is no longer necessary. Also, for example, when comparing user program A included in the project data in the driving record data and user program B included in the edited file, it is possible to see that there are some things written in user program A but not in user program B. For devices that are not described, the device value is not displayed in the first place, while for devices that are described in user program B but not in user program A, the device value is recorded in the driving record data. A visual indication (for example, a red color display) will be provided to indicate that this is not the case.
(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.

In this embodiment, the log data 73 and the like are written to the memory card 36A when a predetermined output condition is met, but the present invention is not limited to this, and for example, the internal memory 37 (flash memory, etc.) is written to the memory card 36A. It may also be saved in a non-volatile memory such as a hard disk. 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.
<Logging large amounts of data>

A camera section 98 exists as the field device 10. The user may desire to improve the user program by acquiring the state of the workpiece or the controlled object using the camera unit 98 and comparing the image with device values. Therefore, the problem is how to manage images and device values that are related to each other. This is because images are generally acquired by the expansion unit 4 and device values are acquired by the CPU unit 3. Furthermore, the image acquisition cycle and the device value acquisition cycle are generally different. Under these circumstances, a problem arises as to how to link and manage large-capacity data such as images and relatively small-capacity data such as device values.

FIG. 26 shows the functions of the PLC side CPU 31 of the CPU unit 3. The same reference numerals are given to parts that have already been explained. In this example, the recording section 81 has a collecting section 92a. When a predetermined collection start condition is satisfied, the collection unit 92a reads out the device value specified by the log setting data 72 from among the device values held in the device unit 34, and also reads the device value from the time management unit 83a. Get time information. The collection unit 92a associates the device value and time information and stores them in the temporary storage unit 91a. Note that the collection unit 92a acquires device values and time information at every collection cycle (eg, scan cycle) specified by the log setting data 72, and stores them in the temporary recording unit 91a. A ring buffer is preferably employed as the temporary recording section 91a. The reason why a ring buffer is employed is that not all data stored in the ring buffer is saved as log data 73 in the memory card 36A. For example, when a predetermined storage condition is met, the storage unit 93 reads the device value and time information from the temporary storage unit 91a of the ring buffer, creates log data 73, and stores it in the memory card 36A. good. Similarly, when a predetermined storage condition is met, the storage unit 93 may read the large-capacity data and time information from the expansion unit 4, create log data 73, and store the log data 73 in the memory card 36A. The storage unit 93 stores the above-mentioned device value and time information, and the above-mentioned large-capacity data and time information in association with each other. Here, "storing in association" means that the files may be saved in a format that is easy to play on the PC 2, and for example, file management may be performed in which a plurality of files are associated with each other. Specifically, in the memory card 36A, a first subfolder in which device values and time information are stored and a second subfolder in which large capacity data and time information are stored are placed under a specific folder. If so, the path (directory path) to a specific folder becomes a common flag, and this common flag can be used to "correspond" and save files in the first subfolder and files in the second subfolder. It becomes possible. Further, if there is another folder placed at the same level (directory) as the above-mentioned specific folder, that other folder means a data package saved at another time. Of course, subfolders similar to those described above are also placed under this other folder. In this way, the storage unit 93 stores the above-mentioned device value and time information, and the above-mentioned data (large capacity data) and time information in a plurality of files identified by the common flag (predetermined directory path). , you may save multiple files. In addition, for example, it is also possible to save files in a "corresponding manner" by using a file name as a common flag and generating files with the same or corresponding file names. For example, it is also possible to associate device values and data (large amount of data) using time information as a key, create a list, and compile them into a single file to save them in an "associated" manner. . In this embodiment, large-capacity data is considered as an example of data from the monitoring equipment, but it goes without saying that continuous data such as motion data, communication data, audio data, etc. may also be used. The transmitter 94 may transmit the log data 73 to the PC 2, the cloud, or the like. When the temporary recording section 91a of the ring buffer becomes full, the collection section 92a overwrites the oldest information held in the ring buffer with the newest information.

Here, a ring buffer is employed as an example of a buffer in the temporary recording section 91a, but this is only an example. It would be sufficient to use a FIFO format buffer as the buffer.
<Debug>

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

In step S2701, 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 S2702, 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 S2703, 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.

Furthermore, as shown in FIG. 26, the storage unit 93 stores project data 71 in memory in addition to the log data 73. 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 S2704, 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 S2705, 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 S2706 and S2707 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 S2706, the user operates the PC2 to transfer the project data 71 to the PLC1. 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 S2707, 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 S2704 to S2707 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. 28 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 uses the project data 71 to debug the user program. 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.

The program creation support device for a programmable logic controller of 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 21, 21B...PC side CPU
22...PC side storage device 23...PC side communication unit 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 35... project storage section 36... storage memory; 36A... memory card 36B... operation record data storage Unit 37... Internal memory 38... Bus master 39... Recording 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 50E...Overwrite restriction control section 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 74...Log data storage section 80...Execution Section 80a... Ladder execution engine 80b... Unit control section 81... Recording section 82... Detection section 83, 83a... Time management section 84... Output section 90... Inter-unit bus 91a... Temporary recording section 92a... Collection section 93... Storage section 94... Transmission unit 98...Camera unit 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 404, 404a... Time designation cursor 406... Play button 407... One step reverse play button 408... One step play button 409... Time display area 410... Program display area 420... Project display area 430... Camera monitor 440... Unit monitor 450... Ladder monitor 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..."Save project under another name"
1334..."Save project"
1340..."Save project under another name" dialog screen 1336..."Project - project matching"
1350...Comparison display screen Ld...Ladder diagram T...Scan time WK...Target

Claims (13)

A programmable logic controller composed of one or more units, including a project storage section that stores project data including a user program, a program execution section that repeatedly executes the user program included in the project data, and a program execution section that is referenced by the program execution section. a device section that has a device that is a storage area for storage; a temporary storage section that temporarily records the device values stored in the device section in chronological order as log data; Supporting the creation of a user program for the user program executed by the programmable logic controller, which includes a storage memory that stores log data recorded in the recording unit together with the project data stored in the project storage unit. A program creation support device for
log data stored in the storage memory during operation of the programmable logic controller;
Driving record data storage that includes the user program being executed by the program execution unit when the log data was stored in the storage memory, and stores the project data stored in the storage memory as driving record data. Department and
a log display control unit that reads the driving record data from the driving record data storage unit and displays log data and project data in the driving record data in association with each other;
a project editing section that receives an editing instruction for the project data displayed by the log display control section and edits the project data;
The project editing unit determines whether or not the project data being edited is the project data in the driving record data stored in the driving record data storage unit, and based on the determined result, the driving record data is edited. an overwrite restriction control unit that restricts overwriting of edited project data edited by the project editing unit with respect to project data in the driving record data stored in a storage unit;
A program creation support device for a programmable logic controller. The program creation support device for a programmable logic controller according to claim 1,
The program creation support device for a programmable logic controller, wherein the overwrite restriction control unit detects that the project editing unit attempts an overwrite operation on project data and displays an overwrite prohibition popup. The program creation support device for a programmable logic controller according to claim 2,
When the overwriting restriction control unit receives an instruction to save project data edited by the project editing unit with respect to project data in the driving record data stored in the driving record data storage unit, the overwriting restriction control unit controls the editing process. A program creation support device for a programmable logic controller configured to save subsequent project data as a file separate from the project data included in the driving record data. A program creation support device for a programmable logic controller according to any one of claims 1 to 3, further comprising:
comprising a mode selection section for selecting at least one of an editing mode for editing project data, and a history playback mode for controlling display by the log display control section;
The project editorial department is
Accepting an editing instruction in the editing mode,
A program creation support device for a programmable logic controller that prohibits reception of editing instructions in the history playback mode. A program creation support device for a programmable logic controller according to any one of claims 1 to 4,
The driving record data includes first driving record data and second driving record data,
A program creation support device for a programmable logic controller, wherein the first driving record data and the second driving record data are distinguished by identification information. The program creation support device for a programmable logic controller according to claim 5,
A program creation support device for a programmable logic controller, wherein the identification information is an extension of a data file. A program creation support device for a programmable logic controller according to claim 5 or 6,
The first driving record data is compressed,
A program creation support device for a programmable logic controller, wherein the log display control section is configured to decompress the first driving record data when reading the first driving record data. The program creation support device for a programmable logic controller according to any one of claims 5 to 7, further comprising:
A program creation support device for a programmable logic controller, comprising a comparison display unit that compares and displays project data in the first operation record data and the second operation record data. A program creation support device for a programmable logic controller according to any one of claims 1 to 8, further comprising:
Equipped with working memory for editing work,
The log display control unit is configured to read the driving record data from the driving record data storage unit to the working memory, and to display and control log data and project data in association with each other in the driving record data. Program creation support device for programmable logic controllers. A program creation support device for a programmable logic controller according to any one of claims 1 to 9,
A program creation support device for a programmable logic controller, wherein the log data includes device data. 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 driving record data includes an image file captured by a camera input expansion unit that captures an image of a target object. A program creation support device for a programmable logic controller according to any one of claims 1 to 11,
A program creation support device for a programmable logic controller, wherein the user program includes a ladder program. A program creation support device for a programmable logic controller according to any one of claims 1 to 12,
The programmable logic controller is composed of a plurality of units,
A program creation support device for a programmable logic controller, wherein unit configuration information of each unit includes at least one of the functions of each unit and information on connection positions between units.

Images