JP6948450B2 - Programmable logic controller and main unit - Google Patents

Description

The present invention relates to a programmable logic controller and a main unit.

A programmable logic controller (PLC) is a controller that controls manufacturing equipment, transfer equipment, and inspection equipment in factory automation. The PLC controls various expansion units and controlled devices by executing a user program such as a ladder program created by the user. When the user program is actually executed on the PLC, an event that was not expected when the user program was created may be found, and the user program may need to be modified. The user not only reviews the user program to identify the correction part, but also refers to the log data generated by the PLC. The device value (device value) collected while the user program is being executed is stored in the log data. In the field of PLC, a device means a storage area for storing information. Devices include a relay device that holds one bit of information and a word device that holds one word of information. According to Patent Document 1, it is proposed to log device values.

Japanese Unexamined Patent Publication No. 10-011118

By the way, there is a need to photograph the state of a field device or an inspection object (work) controlled by a user program with a camera and refer to it together with logging data. If the state of the field device and the work can be confirmed with an image, it is easy for the user to determine whether there is a bug in the user program, there is a problem in installing the field device, or there is a problem in transporting the work. Become. It will be easier for the user to decide which program part should be modified even if the user program needs to be modified. If there is a device value in addition to the image data (two-dimensional data) when the trouble occurs, the user will be able to solve the trouble more easily. However, the device value update cycle (scan cycle) and the two-dimensional data generation cycle (storage cycle) are generally different. Therefore, it is difficult for the user to identify which device value is related to which two-dimensional data. It should be noted that such a problem may occur not only in two-dimensional data such as image data but also in other data. For example, when explaining motion control, since the update cycle (so-called control cycle) of motion data such as the current value and the current speed is different from the scan cycle, which device value and which motion data are temporally related. It was difficult for the user to identify whether or not it was. In addition, for example, when communication control is described, since the update cycle of communication data (for example, one or more sensor values) acquired by cyclic communication is different from the scan cycle, which device value and which communication parameter are used. It was difficult for the user to identify whether and were temporally related. In this way, it is difficult for the user to identify which device value the data input from the monitoring device such as the camera, the motor amplifier for driving the motor, the sensor, and the communication controller is temporally related to. rice field.

Therefore, an object of the present invention is to make it easy to identify the temporal relationship between the device value and the data input from various monitoring devices such as a camera, a motor amplifier, a sensor, and a communication controller.

The present invention is, for example,
An interface that accepts log setting information, a program execution unit that repeatedly executes a ladder program, a device storage unit that has a plurality of devices that are storage areas referenced by the program execution unit , and a collection specified by the log setting information. for each cycle, have a recording section which records in association with information about the collection time a plurality of device values stored in the device memory unit, the condition specified in the log setting information is satisfied recorded It is connected to a programmable logic controller that reads out the information about the plurality of device values and the associated collection time from the unit and outputs it as log data.
An external setting device that displays the plurality of device values using the log data output by the programmable logic controller.
A transmitter that transmits the log setting information to the programmable logic controller, which specifies one scan of the ladder program as the collection cycle and specifies the timing determined by the state change of the specific device and the specific device as the condition. When,
A memory for storing the ladder program and the log data, and
The ladder program stored in the memory is displayed, and a plurality of device values are acquired from the log data stored in the memory based on the information regarding the collection time and displayed on the ladder program as the device value at a specific time. Log display and
With
When the log display unit receives a display update instruction via the first button, the log display unit advances the specific time according to the passage of time and is displayed on the ladder program based on the specific time and the collection time. Provided is an external setting device characterized by repeatedly updating a device value corresponding to the specific time.

According to the present invention, it becomes easy to identify the temporal relationship between the device value and the data input from various monitoring devices such as a camera, a motor amplifier, a sensor, and a communication controller.

Diagram showing a programmable logic controller system Diagram explaining the ladder program Diagram explaining the program creation support device Diagram illustrating PLC Diagram illustrating a scan of a ladder program Diagram explaining the function of the program creation support device Flowchart explaining how to set logging Diagram explaining how to select program parts Diagram explaining how to select a function Diagram illustrating a unit monitor The figure explaining the setting of the unit monitor Diagram illustrating the extraction list Diagram illustrating the extraction list Diagram illustrating merging of extraction lists Diagram explaining the estimation result of the effect on scan time Diagram explaining the device type selection UI Flowchart showing how to extract devices Diagram showing an example of a user program Diagram explaining the functions of the basic unit The figure explaining the process of creating the configuration information The figure explaining the function of the CPU of a basic unit The figure explaining the function of the CPU of an expansion unit Diagram showing an example of log data Flowchart showing logging process in basic unit Flowchart showing logging process in expansion unit The figure which shows the connection form of PLC The figure which shows the connection form of PLC Diagram illustrating logging timing Diagram illustrating the display of log data Diagram explaining the log data display UI Diagram explaining how to set the collection time Diagram explaining how to set the collection time Flowchart showing the outline of debugging process The figure explaining the output part Diagram explaining the project creation department The figure explaining the log display part Diagram illustrating the program display module Diagram illustrating the user interface Diagram illustrating the project data and log data display module Diagram explaining the warning screen The figure explaining the waveform display module Diagram illustrating the user interface Diagram illustrating a real-time chart monitor The figure explaining the reproduction control module A diagram illustrating a UI that displays a user program and device values. Diagram illustrating the HMI emulator Flowchart showing the process of displaying the user program and device value Flowchart showing the process of displaying the waveform of the device value Flowchart showing playback control Diagram illustrating multiple interrelated program components Diagram explaining the UI that displays the extraction results of program parts and devices Flowchart showing the extraction process of program parts and devices A flowchart explaining the flow of debugging Diagram illustrating the modified program component

An embodiment of the present invention is shown below. The individual embodiments described below will help to understand various concepts such as superordinate, intermediate and subordinate concepts of the present invention. Further, the technical scope of the present invention is determined by the scope of claims, and is not limited by the following individual embodiments.

<System configuration>
First, a general PLC configuration and its operation will be described so that a person skilled in the art can better understand a programmable logic controller (PLC, which may be simply referred to as a programmable controller).

FIG. 1 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. 1, this system is a PLC (programmable logic controller) 1 for comprehensively controlling a PC 2 for editing a user program such as a ladder program and various control devices installed in a factory or the like. And have. PC is an abbreviation for personal computer. The user program may be created using a graphical programming language such as a ladder language or a flowchart-type motion program such as SFC (sequential function chart), or may be created using a high-level programming language such as C language. .. In the following, for convenience of explanation, the user program will be a ladder program. The PLC 1 includes a basic unit 3 having a built-in CPU and one or a plurality of expansion units 4. One or more expansion units 4 can be attached to and detached from the basic unit 3. For example, the expansion unit 4a may be a positioning unit that drives a motor (field device 10a) to position the work, and the expansion unit 4b may be a counter unit. The counter unit counts signals from an encoder (field device 10b) such as a manual pulsar. The characters a, b, c ... Attached to the end of the reference code may be omitted. The basic unit 3 is sometimes called a CPU unit. The system including PLC1 and PC2 may be called a programmable logic controller system.

The basic unit 3 is provided with a display unit 5 and an operation unit 6. The display unit 5 can display the operating status of each expansion unit 4 attached to the basic unit 3. The display unit 5 switches the display content according to the operation content of the operation unit 6. The display unit 5 usually displays the current value (device value) of the device in the PLC1, the error information generated in the PLC1, and the like. The device is a name indicating an area on a memory provided for storing a device value (device data), and may be called a device memory. The device value is information indicating an input state from an input device, an output state to an output device, and a state of an internal relay (auxiliary relay), a timer, a counter, a data memory, etc. set on a user program. There are two types of device values: bit type and word type. The bit device stores a 1-bit device value. The word device stores the device value of one word.

The expansion unit 4 is prepared to expand the function of the PLC1. A field device (controlled device) 10 corresponding to the function of the expansion unit 4 is connected to each expansion unit 4, whereby each field device 10 is connected to the basic unit 3 via the expansion unit 4. The field device 10 may be an input device such as a sensor or a camera, or an output device such as an actuator. Further, a plurality of field devices may be connected to one expansion unit 4.

PC2 may be called a program creation support device. The PC 2 is, for example, a portable notebook type or tablet type personal computer, and includes a display unit 7 and an operation unit 8. A ladder program, which is an example of a user program for controlling PLC1, is created using PC2. The created ladder program is converted into a mnemonic code in PC2. The PC 2 is connected to the basic unit 3 of the PLC 1 via a communication cable 9 such as USB (Universal Serial Bus), and sends a ladder program converted into a mnemonic code to the basic unit 3. The basic unit 3 converts the ladder program into machine code and stores it in the memory provided in the basic unit 3. Although the mnemonic code is transmitted to the basic 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 basic unit 3.

Although not shown in FIG. 1, the 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 basic unit 3 of the PLC 1 via a communication cable 9 other than USB. Further, the configuration may be such that the basic unit 3 of the PLC 1 is wirelessly connected without the communication cable 9.

<Ladder program>
FIG. 2 is a diagram showing an example of the ladder diagram Ld displayed on the display unit 7 of the PC 2 when the ladder program is created. The PC 2 displays a plurality of cells arranged in a matrix on the display unit 7. A virtual device symbol is placed in each cell. Symbols indicate input relays, output relays, and the like. A relay circuit is formed by a plurality of symbols. In the ladder diagram Ld, for example, cells of 10 columns × N rows (N is an arbitrary natural number) are arranged. Then, the symbol of the virtual device is appropriately arranged in the cell of each row.

The relay circuit shown in FIG. 2 is used to control the symbols of three virtual devices (hereinafter, referred to as “input devices”) that are turned on / off based on the input signal from the input device and the operation of the output device. It is configured by appropriately combining the symbols of virtual devices (hereinafter, referred to as "output devices") that are turned on / off.

The characters (“R0001”, “R0002”, and “R0003”) displayed above the symbol of each input device represent the device name (address name) of the 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 character displayed above the symbol of the output device (“return to origin”) is a label consisting of a character string representing the function of the output device.

In the example shown in FIG. 2, the AND circuit is configured by connecting the symbols of the two input devices corresponding to the device names “R0001” and “R0002” in series. Further, the OR circuit is configured by connecting the symbols of the input devices corresponding to the device name "R0003" in parallel to the AND circuit composed of the symbols of these two input devices. That is, in this relay circuit, only when the input devices corresponding to the two symbols in the first line are turned on, or when the input devices corresponding to the symbols in the second line are turned on, the symbols in the first line are supported. Output device is turned on.

<Program creation support device>
FIG. 3 is a block diagram for explaining the electrical configuration of the PC 2. As shown in FIG. 3, the PC 2 includes a CPU 21, a display unit 7, an operation unit 8, a storage device 22, and a communication unit 23. The display unit 7, the operation unit 8, the storage device 22, and the communication unit 23 are each electrically connected to the CPU 21. The storage device 22 includes a RAM and a ROM, 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 CPU 21 to execute a computer program (editing software) stored in the storage device 22 and edits the project data through the operation unit 8. The project data includes one or more user programs (eg, a ladder program) and configuration information of the basic unit 3 and the expansion unit 4. The configuration information includes information indicating the connection positions of a plurality of expansion units 4 with respect to the basic unit 3, functions provided in the basic unit 3 (example: communication function and positioning function), and functions of the expansion unit 4 (example: shooting function). It is information indicating such as. Here, editing the project data includes creating and modifying the project data. The project data created by using the editing software is stored in the storage device 22. Further, the user can read the project data stored in the storage device 22 as needed and change the project data by using editing software. The communication unit 23 is for connecting the PC 2 to the basic unit 3 so as to be communicable via the communication cable 9. The CPU 21 transfers the project data to the basic unit 3 via the communication unit 23.

<PLC>
FIG. 4 is a block diagram for explaining the electrical configuration of PLC1. As shown in FIG. 4, the basic unit 3 includes a CPU 31, a display unit 5, an operation unit 6, a storage device 32, and a communication unit 33. The display unit 5, the operation unit 6, the storage device 32, and the communication unit 33 are each electrically connected to the CPU 31. The storage device 32 may include a RAM, a ROM, a memory card, and the like. The storage device 32 has a plurality of storage areas such as a device unit 34, a project storage unit 35, and a detachable memory card 36. The device unit 34 has a bit device, a word device, and the like, and each device stores a device value. The project storage unit 35 stores the project data input from the PC2. The storage device 32 also stores the control program for the basic unit 3. As shown in FIG. 4, the basic unit 3 and the expansion unit 4 are connected via a unit internal bus 90, which is a type of expansion bus. The communication function related to the unit internal bus 90 may be implemented as a part of the communication unit 33. The communication unit 33 may have a network communication circuit. The CPU 31 may transmit log data or the like to the PC 2 or the cloud via the communication unit 33.

Here, the unit internal bus 90 will be supplementarily described. The unit internal bus 90 is a bus on which input / output refresh and the like described below are performed, and communication control in the unit internal bus 90 is realized by a so-called bus master 38 (note that the bus master is a part of the communication unit 33). Or a bus master 38 may be provided as a part of the CPU 31). The bus master 38 is a control circuit for controlling communication on the unit internal bus 90, and receives a communication request from the CPU 31 and performs communication such as input / output refresh described later with the expansion unit 4.

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

FIG. 5 is a schematic diagram showing the scan time of the basic unit 3. As shown in FIG. 5, one scan time T is composed of inter-unit communication 201 for refreshing input / output, program execution 202, and END process 204. In the inter-unit communication 201, the basic unit 3 transmits the output data obtained by executing the ladder program from the storage device 32 in the basic unit 3 to an external device such as the expansion unit 4. Further, the basic unit 3 takes in the input data received from an external device such as the expansion unit 4 into the storage device 32 in the basic unit 3. That is, the device value stored in the device of the basic unit 3 is reflected in the device of the expansion unit 4 by the output refresh. Similarly, the device value stored in the device of the expansion unit 4 is reflected in the device of the basic unit 3 by the input refresh. In this way, the device of the basic unit 3 and the device of the expansion unit 4 are synchronized by the input / output refresh. A mechanism for updating device values between units at a timing other than refresh (synchronization between units) may be adopted. However, the device of the basic unit 3 is rewritten by the basic unit 3 at any time, and similarly, the device of the expansion unit 4 is rewritten by the expansion unit 4 at any time. That is, the device of the basic unit 3 can be accessed at any time by the device inside the basic unit 3. Similarly, the device of the expansion unit 4 is made accessible at any time by the device inside the expansion unit 4. The basic unit 3 and the expansion unit 4 basically update their device values and synchronize with each other at the refresh timing. In the program execution 202, the basic unit 3 executes (calculates) the program using the updated input data. As shown in FIG. 5, in the program execution 202, a plurality of program modules or ladder programs may be executed in order according to the project data. The basic unit 3 arithmetically processes data by executing a program. The END process means all processes related to peripheral services such as data communication with an external device such as a display (not shown) connected to the PC 2 or the basic unit 3 and system error check.

In this way, the PC2 creates a ladder program according to the user's operation, and transfers the created ladder program to the PLC1. The PLC1 sets the input / output refresh, the execution of the ladder program, and the END process as one cycle (one scan), and repeatedly executes this cycle periodically, that is, cyclically. As a result, various output devices (motors, etc.) are controlled based on timing signals from various input devices (sensors, etc.). In addition to the scan cycle, the basic unit 3 and the expansion unit 4 each have an internal control cycle. The basic unit 3 and the expansion unit 4 control functions such as the field device 10 with reference to the internal control cycle.

<Logging>
When the user improves or modifies the user program, the device values acquired while the PLC1 is executing the user program may be useful. Therefore, PLC1 acquires a device value specified in advance and creates log data. Here, the devices managed by the PLC1 include not only those used by the user program but also those not used by the user program. Also, some devices are useful in 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 the user to specify the required device. Therefore, the PC2 analyzes the user program and extracts the device used or described in the user program as a logging target. This reduces the burden on the user.

If all the devices managed by PLC1 are targeted for logging, the scan time will be long. This is because logging is executed as one of the user programs or at the time of I / O refresh. Occasionally, the delay caused by logging can cause the user program to not work as the user wants. Therefore, the number of devices to be logged should be maintained appropriately.

A user program may be composed of a plurality of program components (eg, a program module (main ladder program and sub ladder program), a function block). Of these, it may be sufficient for the user if the device related to the program component that the user wants to modify is logged. Further, among a plurality of program components, the user may wish to exclude a specific program component from the extraction target or add a specific program component to the extraction target. Therefore, it would be convenient for the user to be able to add or remove devices from the logging target in units of program parts.

As described above, the basic unit 3 and the expansion unit 4 have one or more functions. Various devices are assigned to each function. Therefore, it would be convenient for users to be able to add or remove devices from the logging target in units of these functions. For example, if an undesired event occurs regarding the communication function of the basic unit 3, the user can easily eliminate this event by referring to the device value of the device related to the communication function of the basic unit 3.

● Logging settings (automatic extraction and addition / removal)
FIG. 6 shows a function realized by the CPU 21 of the PC 2 executing the editing software stored in the storage device 22. Some or all of these functions may be realized by hardware circuits such as ASICs and FPGAs. ASIC is an abbreviation for a special purpose integrated circuit. FPGA is an abbreviation for field programmable gate array.

In the present embodiment, the functions shown in FIG. 6 are realized on the PC2, but the present invention is not limited to this, and may be realized on the PLC1.

The project creation unit 50 displays a UI for creating the project data 71 on the display unit 7, creates the project data 71 according to the user instruction input from the operation unit 8, and stores the project data 71 in the storage device 22. UI is an abbreviation for user interface. The project data 71 includes a user program, PLC1 configuration information, and the like. The program creation unit 63 creates a plurality of program components (each module) constituting the user program based on the user operation via the UI. The function setting unit 62 executes settings related to the functions of the basic unit 3 and the functions of the expansion unit 4. For example, the function setting unit 62 assigns one device to the function provided in the basic unit 3 or assigns any device to the function provided in the expansion unit 4, and the function and the device. The allocation information indicating the relationship with is written in the configuration information. The project creation unit 50 also stores the program configuration information indicating what kind of program components the user program is composed of as the project data 71. The unit configuration information indicating what kind of unit the entire PLC1 is composed of is also stored as the project data 71.

The log setting unit 51 extracts the device described in the project data 71 by analyzing the project data 71, and creates the log setting data 72 for setting the extracted device as a logging target. The log setting unit 51 has various functions. The component designation unit 52 designates a program component to be extracted from the device according to a user instruction input from the operation unit 8. Further, the component designation unit 52 designates a program component to be excluded from the extraction target of the device according to the user instruction input from the operation unit 8.

The device extraction unit 53 extracts the device described in the project data 71 by analyzing the project data 71, and creates the log setting data 72. The addition unit 54 analyzes the program component designated as the extraction target by the component designation 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 the 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 the duplicately extracted devices from the extraction list among the devices extracted from the plurality of program components. The identification unit 57 detects a command word for the memory card in the project data 71, identifies a device that is the target of the command word, and adds the specified device to the extraction list.

In the present embodiment, after the component designation unit 52 specifies the program component, the additional unit 54 extracts and adds the device to be logged by analyzing the designated program component. The invention is not limited to this. For example, the addition unit 54 extracts a device by first analyzing one or more program parts included in the project data 71, adds the extracted device to the extraction list, and then designates the device by the part designation unit 52. The device described in the program component described in the program may be extracted and added to the extraction list.

Similarly, the deletion unit 55 is described in the program component designated by the component designation unit 52 after creating an extraction list by first analyzing one or more program components included in the project data 71. You may want to extract the device and remove it from the extraction list.

In the present embodiment, the addition unit 54 and the deletion unit 55 are separated for convenience of explanation, 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 a user instruction input through the operation unit 8. The estimation unit 59 estimates the influence of the recording of the device value by the PLC1 on the execution of the user program based on the number of devices extracted as the recording target by the device extraction unit 53. Logging adds a delay time that correlates to the number of device values to the scan time. Therefore, the estimation unit 59 may obtain the delay time by multiplying the number of device values by a predetermined coefficient, and display the delay time as the estimation result on the display unit 7. This delay time may be referred to as an increase in scan time.

The function designating unit 60 designates the function of the basic unit 3 and the function of the expansion unit 4 to be extracted from the device according to the user instruction input from the operation unit 8. Further, the function designating unit 60 designates the function of the basic unit 3 and the function of the expansion unit 4 to be excluded from the extraction target of the device according to the user instruction input from the operation unit 8. The addition unit 54 analyzes the configuration information of the function designated as the extraction target by the function designation unit 60, extracts the device assigned to the function based on the configuration information, and adds it to the extraction list. The deletion unit 55 analyzes the configuration information of the function designated as the exclusion target by the function designation unit 60, extracts the device assigned to the function based on the configuration information, and deletes the extracted device from the extraction list. The merging unit 56 deletes the duplicately extracted devices from the extraction list among the devices extracted for each of the plurality of functions. The identification unit 57 detects a command word for the memory card in the project data 71, identifies a device that is the target of the command word, and adds the specified device to the extraction list.

The log display unit 61 reads the log data 73 generated by the PLC 1 via the memory card 36, and displays the log data 73 on the display unit 7. For example, the log display unit 61 may display the device value recorded in the log data 73 on the display unit 7 in association with the program component of the project data 71. The log display unit 61 forms the core of an engineering tool for a programmable logic controller.

FIG. 7 is a flowchart showing a logging setting method. Here, it is assumed that the project data 71 including the user program has already been completed.

In S1, the CPU 21 (component designation unit 52) accepts the designation of the program component to be extracted from the device.

FIG. 8 shows the UI 100 for accepting the selection of the program component from which the device is extracted. The log setting unit 51 displays the UI 100 on the display unit 7 when the logging setting program is started. In UI100, a plurality of program parts are shown in a tree shape based on their respective classifications (modules / function blocks / macros). Further, a check box 102 is associated with each program component and displayed. When the pointer 101 gives a check to the check box 102 in response to the operation of the operation unit 8, the additional unit 54 adds the program component corresponding to the checked check box 102 to the extraction list. On the other hand, when the pointer 101 unchecks the check box 102 in response to the operation of the operation unit 8, the deletion unit 55 deletes (excludes) the program component corresponding to the unchecked check box 102 from the extraction list.

In FIG. 8, the scan module is a program component that is executed once each time the user program is scanned. In this example, each scan module has a main program and a submodule. A fixed-cycle module is a program component that is executed at regular intervals. The inter-unit synchronization module is a program component that is executed each time inter-unit synchronization is executed. The initialization module is not shown, but the initialization module is the first module to be executed when the user program is started. Therefore, the initialization module is less likely to cause trouble and may be excluded from the device extraction target.

The function block (FB) is called and used by the user program. Since function blocks are called from multiple modules, each creates a separate instance. In this case, a plurality of instances may be selected as the extraction target of the device, or all the instances generated in relation to the function block by selecting the original function block are selected as the extraction target of the device. May be good.

Macros are a type of program, and include macros for data formatting.

In S2, the CPU 21 (function designation unit 60) accepts the designation of the function to be extracted from the device.

FIG. 9 shows a UI 110 for accepting a selection of functions from which devices are extracted. The log setting unit 51 displays the UI 110 on the display unit 7 when the logging setting program is started. The UI 100 and the UI 110 may be displayed at the same time, or may be selectively displayed according to a user operation. In UI110, a plurality of functions are shown in a tree shape based on the unit to which each belongs. Further, a check box 102 is associated with each function and displayed. When the pointer 101 gives a check to the check box 102 in response to the operation of the operation unit 8, the additional unit 54 adds the function corresponding to the checked check box 102 to the extraction list. On the other hand, when the pointer 101 unchecks the check box 102 in response to the operation of the operation unit 8, the deletion unit 55 deletes (excludes) the function corresponding to the unchecked check box 102 from the extraction list.

In FIG. 9, the communication error monitor, which is a function of the basic unit 3, is a function of monitoring the communication error of the communication unit 33. The sensor I / O monitor is a function for monitoring the input / output of the sensor. The motion unit is also called a positioning unit and controls the position of a controlled object called an axis. Generally, there is a drive source such as a motor for each shaft. The analog input unit is a unit that samples an input analog signal and converts it into a digital signal. The unit monitor is a function of monitoring the operation of the expansion unit 4 such as the motion unit and the analog input unit.

Here, as an example of the unit monitor, the unit monitor of the motion unit will be described in more detail. FIG. 10A is a schematic view of the screen of the unit monitor 440 with respect to the axis 1 of the motion unit. FIG. 10B is a schematic view of a setting screen 441 for changing the monitoring target by the unit monitor 440.

As shown in FIG. 10A, items such as current coordinates, command coordinates, current speed, command speed, feedback torque, load factor, and peak current are set as monitoring targets by the unit monitor 440. A buffer memory (UG) is allocated to each item. For example, UG4 and UG5 are assigned to the current coordinates. In the present embodiment, 16 bits are secured for one UG, and two UGs are secured for expressing the current coordinates in 32 bits. The device value of UG is, for example, a numerical value such as 0PLS (pulse). Further, UG8 and UG9 are assigned to the command coordinates. Two UGs are secured for the same reason as described above (to secure a 32-bit representation). Since the unit designer can freely assign the UG, there are some unused UGs (UG6 and UG7). Similarly, UG10 and UG11 are assigned to the current speed, and UG12 and UG13 are assigned to the command speed, respectively. In addition, in FIG. 10A, UG is assigned to each item such as feedback torque, load factor, and peak current.

As shown in FIG. 10B, the user can freely select (set) which item is to be monitored by the unit monitor 440. For example, by selecting one item from the "hidden" column 442 shown in FIG. 10B and clicking the right arrow button 443, that one item moves to the "display" column 444 and is monitored by the unit monitor 440. It becomes. By clicking the OK button 445, the items listed in the "display" column 444 are confirmed as monitoring targets. Note that, in FIGS. 10A and 10B, only the axis 1 of the motion unit has been described, but the same applies when there are a plurality of axes 2 and 3. For each axis, the item selected by the user is monitored.

Generally, when a motion unit (expansion unit 4a) is used to drive a motor (field device 10a) to position a workpiece, the basic unit 3 turns on a relay device indicating a motor positioning start trigger. An operation start command is sent to the expansion unit 4a. Then, after the operation start command is sent, the expansion unit 4a is not involved in a specific processing operation (work positioning). In other words, the basic unit 3 does not recognize the current position and the current speed of the motor one by one in real time, and does not need to recognize them one by one. After that, when the processing operation in the expansion unit 4a is completed, the basic unit 3 recognizes the completion of the positioning of the motor through the ON of the relay device indicating the positioning completion trigger of the motor. For this reason, the device (UG) corresponding to the current coordinates and current speed of the motor is basically not described in the ladder program (however, the user is a special instruction for reading a small part of the UG). It is possible to write words in a ladder program).

However, when a trouble occurs during the operation of the PLC, it may be desired to grasp the current coordinates and the current speed of the motor at the time when the trouble occurs in order to investigate the cause. In such a case, as described above, the current coordinates and current speed of the motor are not basically described in the ladder program, so they are often not listed in the extraction list as the logging target, which is the cause. It was not easy to find out.

Therefore, in the present embodiment, the user can select the unit monitor of the motion unit through the UI 110 shown in FIG. As a result, the addition unit 54 can automatically add the UG to be monitored by the unit monitor 440 of the motion unit to the extraction list as described with reference to FIG. 10B. The same applies to the communication error monitor / sensor I / O monitor of the basic unit 3 and the unit monitor of the analog input unit. Devices or parameters monitored by each monitor can be automatically added to the extraction list.

Although not shown, the other monitors will be briefly described. The communication error monitor, which is a function of the basic unit 3, monitors, for example, the device assigned to the cyclic communication opening timeout error. The sensor I / O monitor that monitors the input / output of the sensor monitors, for example, the output of one or more sensors and the device assigned to the presence or absence of an error. The unit monitor of the analog input unit monitors the device (DM or R) assigned to various parameters such as AD conversion data, special data, offset value, zero shift, peak value, and bottom value. These devices are assigned as defaults (initial settings) by the unit designer in advance, but the monitoring target may be changed by the user as in the unit monitor of the motion unit described above. In short, the UI 110 shown in FIG. 9 is a setting screen capable of accepting a function selection input from a user. Then, a template (setting information) that defines a monitoring item to be displayed on the display unit (monitor) is associated with each function to be selected and input (the template is saved in the memory). The device specified by the template may be a device assigned by default in advance as described above, or may be a device after addition / subtraction (editing) by the user via the setting screen. When one or more functions are selected based on the user operation, the function designation unit 60 adds the device to be monitored to the extraction list according to the template associated with the function.

In S3, the device extraction unit 53 analyzes the program component designated by the component designation unit 52, and extracts the device described in the designated program component.

FIG. 10C shows an example of a device extracted from a designated program component among a plurality of program components included in the project data 71. According to FIG. 10C, the name of the program component extracted from the device, the name of the leading device (device number), the number of devices extracted based on the leading device, and the device name actually extracted as the logging target. Is shown. Generally, a number of devices corresponding to a specified number are extracted with the first device as a reference. However, the number of devices exceeding the specified number may be extracted. R34000 is a relay device, which holds 1-bit information, and a series of 16 devices from R34000 to R34015 are extracted. This is because logging 16-bit devices together is advantageous from the viewpoint of data processing speed. In FIG. 10C, the number of R34000 is "1", which indicates one word (16 bits). Further, the number of CR4001 is also "1", which also indicates one word (CR4001, CR4002, ..., 16 bits of CR4015 and CR4100). A global is a device commonly used by a plurality of program components. Main shows the main program. first_operation is the name of a function block. Sub indicates a subprogram (submodule).

In S4, the device extraction unit 53 analyzes the configuration information of the function specified by the function designation unit 60, and extracts the device associated with the function in the configuration information.

FIG. 11 shows an example of a device extracted from a designated function (unit) among a plurality of functions (basic unit 3 and expansion unit 4) provided in PLC1. In this example, some buffer memories (UG) are extracted from the motion unit designated by the function designating unit 60. According to FIG. 11, the name of the function extracted from the device, the name of the leading device (device number), the number of devices extracted based on the leading device, and the device name actually extracted as the logging target. It is shown. Here, devices that can be monitored by the unit monitor of the motion unit are extracted. That is, as described above with reference to FIG. 10A, UG4-UG5 indicates the current coordinates of the motor, UG8-UG9 indicates the command coordinates of the motor, and UG10-UG11 indicates the current speed of the motor. , UG12-UG13 indicate the command speed of the motor. The description of other UGs will be omitted.

In S5, the manual setting unit 58 adds the device manually specified by the user through the operation unit 8 to the extraction list. For example, the manual setting unit 58 may display a UI on which a device number or the like can be directly input on the display unit 7 to assist the user in designating the device.

In S6, the merging unit 56 merges the devices extracted from the program components, the devices extracted from the functions, and the devices added manually to create a logging target list. The logging target list may be called a device list.

FIG. 12 is a diagram illustrating the concept of the merge process. The device extraction unit 53 creates an extraction list L1 that describes the devices extracted from the program components. The device extraction unit 53 creates an extraction list L2 that describes the devices extracted from the function. The device extraction unit 53 creates an extraction list L3 that describes the devices manually added by the user. The merging unit 56 merges the extraction lists L1 to L3 to create the logging target list L0. In the extraction lists L1 to L3, there may be devices extracted in duplicate. When the same device is logged multiple times, the log data becomes bloated. Therefore, the merge process is executed in order to avoid duplicate logging of the same device. For example, in the extraction list L1, the data memory DM0-DM100, which is a kind of device, is registered. Further, the data memory DM50-DM200 is registered in the extraction list L3. That is, DM50-DM100 are duplicated. The merging unit 56 merges DM0-DM100 and DM50-DM200 and describes DM0-DM200 in the logging target list L0.

In S7, the estimation unit 59 analyzes the logging target list L0, estimates the influence on the scan time, and displays the estimation result on the display unit 7.

FIG. 13 shows a UI 140 for displaying the estimation result. The UI 140 displays the device size and the increase in scan time. The device size indicates the total size of the devices described in the logging target list L0. The increase in scan time is the delay time caused by logging. The estimation unit 59 analyzes the logging target list L0 and calculates the device size and the increase in scan time. When the list button 141 is operated through the operation unit 8, the estimation unit 59 may display the logging target list L0 on the display unit 7. The user determines whether to finalize or adjust the logging target list L0 in consideration of the estimation result. When confirming the logging target list L0, the user may operate a button indicating the intention of confirmation with the pointer 101.

In S8, the log setting unit 51 determines whether or not to confirm the logging target. For example, when the button for confirming the logging target list L0 is operated, the log setting unit 51 determines that the logging target is confirmed. On the other hand, when the button for modifying the logging target list L0 is operated, the log setting unit 51 determines that the logging target is modified. When modifying the logging target, the log setting unit 51 repeats S3 to S8 to accept additions and deletions of program parts and functions to be extracted from the device, and modifies the logging target list L0. For example, if scan time growth exceeds an acceptable threshold, some devices will be removed. Several devices may be added as long as the scan time growth is below the permissible threshold. When the logging target is confirmed, the CPU 21 proceeds to S9.

In S9, the log setting unit 51 creates the log setting data 72 including the logging target list L0 and stores it in the storage device 22. The CPU 21 controls the communication unit 23 so as to transmit the log setting data 72 together with the project data 71 to the basic unit 3.

Here, devices such as data memory and buffer memory are mainly targeted for logging, but the operating status and function setting status (eg, IP address, etc.) of each function may also be added as logging targets.

FIG. 14 shows a filter setting UI 120 used in the device extraction process. There are a plurality of types of devices related to PLC1. Users may want to focus on a particular type of device and ignore other types of devices. Therefore, the log setting unit 51 may display the filter setting UI 120 on the display unit 7 and accept the device type to be extracted and the device type to be excluded through the check box 102. For example, the device extraction unit 53 extracts the device type in which the check box 102 is checked from the program components and functions. The device extraction unit 53 does not extract the device type unchecked from the check box 102 from the program components and functions. This makes it possible to easily select the device to be logged according to the user's intention.

By the way, when the project data 71 is changed by the project creation unit 50, the CPU 21 may re-execute the device extraction process. This is because the description of the device in the user program may have been changed. The CPU 21 may execute the device extraction process when the project creation unit 50 transfers the project data 71. Since the project data 71 is finally written to PLC1, the number of executions of the device extraction process will be reduced by executing the device extraction process using this write as a trigger.

Although the device extraction unit 53 is mounted on the PC 2, it may be mounted on the basic unit 3. The CPU 31 extracts the device from the program parts and functions specified by the PC2 in the project data 71, and creates the log setting data 72. In this case, the estimation unit 59 will also be mounted on the basic unit 3. ● Device extraction process FIG. 15 is a flowchart showing a device extraction process from the program components executed by the device extraction unit 53. FIG. 16 shows an example of a ladder program. This ladder program is for controlling a motion unit that drives four axes as an expansion unit 4.

In S11, the device extraction unit 53 acquires the device number from the description of the i-th step of the program component designated as the extraction target. The initial value of i is 001. As shown in FIG. 16, a step number is assigned to the left end of the ladder program. In step 001, when the relay device called MR000 is turned on, the relay device called R34000 that gives operation permission to the motion unit is turned on, and the relay called R34305 for operating the servo of the first axis of the motion unit is turned on. It is described that the device is turned on. Therefore, the device extraction unit 53 extracts MR000, R34000, and R34305 as device numbers. The device number may be described by indirect reference or index reference. In this case, the device extraction unit 53 searches for the indirect reference destination or the program to which the index value is assigned, and specifies the actual device number. If the device extraction unit 53 fails to extract the actual device number, the device extraction unit 53 may display a message indicating the extraction failure on the display unit 7. Further, the device extraction unit 53 may display a UI for causing the user to input the actual device number on the display unit 7 and accept the user input. Furthermore, considering the indirect reference and index reference described above, the device extraction unit 53 not only extracts a specific device directly described in the program, but also a specific device used in the program (indirect reference or indirect reference). Devices identified by index reference, etc.) are also extracted.

In S12, the device extraction unit 53 acquires the device range from the access range of the instruction word. Some instruction words take the device number of the first device and the number of devices based on the first device as arguments. For example, step 003 describes that when the relay device MR000 is turned on, the command word FMOVE is executed. In this example, FMOVE is an instruction word (to initialize related devices) for substituting a specified value (0) into a specified number (10) of devices based on the first device (@ EM0). Command word). That is, the access range is defined by the start address and the specified number. The device extraction unit 53 determines the range from @ EM0 to @ EM9 as the device range. The access range may be described by indirect reference or index reference. In this case, the device extraction unit 53 searches for the indirect reference destination or the program to which the index value is assigned, and specifies the actual access range. If the device extraction unit 53 fails to extract the actual access range, the device extraction unit 53 may display a message indicating the extraction failure on the display unit 7. Further, the device extraction unit 53 may display a UI for causing the user to input the actual access range on the display unit 7 and accept the user input.

In S13, the device extraction unit 53 extracts a device based on the head device number and the device range, and adds the extracted device to the extraction list. For example, MR000, R34000 and R34005 are extracted from step 001 and added to the extraction list. From step 003, @ EM0 to @ EM9 are extracted and added to the extraction list.

In S14, the device extraction unit 53 determines whether or not the device analysis has been completed up to the end of the program for the designated program component. If the device analysis is not completed until the end of the program, the device extraction unit 53 proceeds to S15. In S15, the device extraction unit 53 adds 1 to the variable i and returns to S11. If the device analysis is completed until the end of the program, the device extraction unit 53 ends the device extraction process.

In the ladder program shown in FIG. 16, the devices extracted from the step 004 and thereafter will be briefly described below.

The 004,005 step is a motor origin return (operation) request, and R34310 is a relay device indicating a motor origin return start trigger. From this step, each device of MR001, R34310, R40905, R40910, and R34310 is extracted.

The steps 006 to 008 are processes for reading the home-origin completion code from the motion unit and determining whether or not the homing is correctly completed when the home-returning of the motor is completed. More specifically, the R40910 is a relay device that indicates a return-to-origin completion trigger of the motor. The basic unit 3 does not recognize the specific processing operation of the home return in the motion unit in real time, and determines whether the home return is completed by monitoring whether the flag R40910 is turned ON. do. When this flag R40910 is turned ON, a UREAD instruction for directly reading the buffer memory is executed. The UREAD instruction shown in FIG. 16 is an instruction to read the buffer memory No. 4060 in the unit No. 1 and assign one word to the device @ EM0. Here, the home return completion code is stored in the buffer memory No. 4060, and is 0 when the home return is completed normally, and a numerical value other than 0 (1 or 2) when the home return is abnormally completed. Etc.) are stored. Then, as shown in step 007, when the device value of @ EM0 is other than 0, the basic unit 3 sets the device MR000 and recognizes that the origin return has ended abnormally. On the other hand, as shown in step 008, when the device value of @ EM0 is 0, the basic unit 3 sets the device MR001 and recognizes that the home return has been normally completed. From this step, each device of R40910, @ EM0, @ MR000, @ MR001 is extracted.

The 009th step is a process of waiting for only one second when the home return is normally completed. The device T0 has 10 as a set value (corresponding to 1 second because it is in units of 100 ms) and has a current count value, and is turned on when the count value reaches the set value. From this step, each device of MR001 and T0 is extracted.

Finally, in the steps 010 to 011 when the device T0 is turned on, the function block "First_operation" is executed for the unit of the unit number 1. Then, the execution result is stored in @ MR002, and the completion code is stored in @ EM1. From this step, each device of @ MR002 and @ EM1 is extracted.

As described above in detail with reference to FIG. 16, in a general ladder program, the device corresponding to the start of operation and the completion of operation such as the servo ON of the axis, the home return request, the activation and result of the function block, etc. Only the device is described. However, when a trouble occurs, if there is information on the state during operation (current coordinates of the motor, current position, etc.), it will be useful for investigating the cause, so as described above, the UGs that are monitored by the unit monitor are also extracted. It is automatically added to the list.

This extraction process is executed for each of the specified program components.

● Execution of logging FIG. 17 shows the function of the CPU 31 of the basic unit 3. Some or all of these functions may be realized by hardware circuits such as ASICs and FPGAs. ASIC is an abbreviation for a special purpose integrated circuit. FPGA is an abbreviation for field programmable gate array.

It is assumed that the CPU 31 stores the project data 71 and the log setting data 72 received from the PC 2 in the storage device 32. The execution unit 80 includes a ladder execution engine 80a that repeatedly executes the user program, and a unit control unit 80b that controls the ladder execution engine 80a and executes 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. The ladder execution engine 80a of the execution unit 80 writes a device value to an output device held in the basic unit device unit 34a of the device unit 34 or is held in the basic unit device unit 34a according to a user program. Read the device value from the input device.

On the other hand, the unit control unit 80b of the execution unit 80 reads / writes the device value related to the expansion unit acquired by the input / output refresh to / from the expansion unit device unit 34b. Further, the basic unit and the expansion unit are electrically connected by the unit internal bus, and the unit control unit 80b has a function of performing communication control in the unit internal bus, that is, a function as a so-called bus master. When the unit control unit 80b functions as a bus master, each expansion unit and refresh are based on the unit configuration information described with reference to FIG. 6, that is, information indicating what kind of unit the entire PLC1 is composed of. Communicate.

The recording unit 81 acquires a device value from the device unit 34 (basic 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. , Write to memory (for example, ring buffer) as log data 73. As described above, the recording unit 81 executes the logging process at the time of the END process or the like.

The logging process in the END process will be described in more detail. In the log setting data 72, as described with reference to FIGS. 10C and 11, the device described in the program component designated by the component designation unit 52 and the function specified by the function designation unit 60 (for example, the unit monitor) are included in the log setting data 72. Devices assigned to (monitored by) are included as logging targets. For the former device, the log data 73 is written during the END processing, while for the latter device, the device value of the target device (UG) is read from the expansion unit 4 during the END processing. 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 the present embodiment, since the device value of the UG is read out in synchronization with the scan cycle, not all the current coordinates and the command coordinates are written in the log data 73. However, the present invention is not limited to this. For example, the current coordinates and command coordinates are stored in the memory of the expansion unit 4 for each control cycle, and a plurality of current coordinates and commands stored up to that point are stored at the timing of the scan cycle. It is also possible to configure the coordinates and the like to be read out.

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

The device to be logged is basically specified by the logging target list L0 of the log setting data 72, but an additional device may be specified by the detection unit 82. The detection unit 82 may detect, for example, rewriting the device value from an external device for any of the devices included in the device unit 34. Generally, the device value may be rewritten according to the user program or may be rewritten by an external device. Such rewriting cannot be grasped in advance only by analyzing the user program. The recording unit 81 may add a device whose device value rewriting is detected by the detection unit 82 to the logging target. In general, rewriting device values from an external device tends to cause unexpected events for the user. Therefore, the recording unit 81 will be useful for improving the program by the user by logging the device value rewritten by the external device.

By the way, in the END process, a UG read instruction that is issued regardless of the user program may be issued. UG is a device type indicating a buffer memory. The detection unit 82 may detect the UG read instruction issued independently of the user program. The recording unit 81 may specify the buffer memory that is the target of the UG read instruction detected by the detection unit 82, and add the specified buffer memory as the recording target. When the expansion unit 4 is a motion unit, a torque value, a current coordinate position, and the like are stored in such a buffer memory.

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

The detection unit 82 may be provided in the execution unit 80. In this case, the execution unit 80 may write the device value to the specific device of the device unit 34, and may write the device value and the device name (device number) to the log data 73. This method will be 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 the device regardless of the device list included in the log setting data 72. In an extreme case, the user can acquire the log data 73 without creating the log setting data 72. For example, when the execution unit 80 is activated, the execution unit 80 acquires device values from all the 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 the device information (address information) of the read device value to the recording unit 81. The recording unit 81 reads device values from all the 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. After that, every time the detection unit 82 detects access to the device unit 34, the recording unit 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 access to the device a plurality of times within one cycle, the recording unit 81 may write to the log data 73 only with the device value when the last access is detected. This makes it possible to reduce the data size of the log data 73.

The execution unit 80 may have a cache for holding the device. In this case, the detection unit 82 may detect the writing of the device by monitoring the cache.

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

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

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

By the way, the log setting data 72 may include the data format (eg, binary format or text format) of the log data 73. As the data format, decimal 16 bits, decimal 32 bits, ± decimal 16 bits, ± decimal 32 bits, hexadecimal 16 bits, hexadecimal 32 bits, character string, Float, DoubleFloat, etc. are set for each device. May be done. Such a data format can be identified by analyzing the instruction word in the program component.

The output unit 84 stores the project data 71, the log data 73, and the image data in the memory when a predetermined output condition is satisfied, such as when the execution of the user program is completed or when the save trigger relay to the memory card is turned on. Write to card 36. Until the predetermined output condition is satisfied, the log data 73 is recorded in the memory (for example, a ring buffer), and when the capacity is full, the oldest log data 73 is deleted and new log data 73 is additionally recorded. (Record in so-called FIFO format). The memory card 36 is removed from the basic unit 3 and mounted on the mounting portion of the PC 2. As a result, the log data 73 is displayed on the display unit 7 of the PC 2. The output unit 84 may transmit the log data 73 to the PC2, the cloud, or the like via the communication unit 33.

In the present embodiment, the log data 73 and the like are written to the memory card 36 when a predetermined output condition is satisfied, but the present invention is not limited to this, and for example, the internal memory 37 (flash memory or It may be saved in a non-volatile memory such as a hard disk). Further, at least the log data 73 needs to be saved in the memory card 36 or the internal memory 37 when the predetermined output condition is satisfied, while the project data 71 needs to be stored in the internal memory 37 when the predetermined output condition is satisfied. Not limited to. For example, it may be saved in the memory card 36 or the internal memory 37 in advance at the timing when the PLC1 changes from the setting mode (PROGRAM mode) to the operation mode (RUN mode).

● Creation of Configuration Information FIG. 18 is a diagram illustrating a configuration information creation process (unit setting) executed by the function setting unit 62. The function setting unit 62 may be called a unit editor. When the function setting unit 62 is supported to start the unit editor, the function setting unit 62 displays the unit setting UI 150 on the display unit 7. The name column 151 is a column for displaying the name of each unit (example: model number, etc.). A unit number is automatically assigned to each unit. In this example, "0" is assigned to the basic unit 3 as a unit number. The input area field 152 is a field for allocating input devices. In this example, devices R000 to R015 are assigned to the basic unit 3 as input devices. The output area column 153 is a column for allocating an output device. In this example, devices R500 to R507 are assigned to the basic unit 3 as output devices. The occupied area column 154 is a column for allocating an input / output mixed system device. The end unit is a so-called terminal unit. The user sets the type of expansion unit 4, the connection order, and the devices to be assigned through the operation unit 8. The function setting unit 62 stores information indicating the type of the expansion unit 4, the connection order (unit number), and the devices assigned to each of the basic unit 3 and the expansion unit 4 in the configuration information. The configuration information may be referred to as unit setting information. Here, the device is assigned to each unit, but the device may be assigned to each function of each unit. The function setting unit 62 manages the configuration information as a part of the project data 71.

As described above, the configuration information includes information indicating the device assigned to each unit and information indicating the device assigned to each function. Therefore, the device extraction unit 53 can extract the device assigned to each unit and the device assigned to each function by referring to the configuration information.

<Logging of large volumes of data>
A camera exists as a field device 10. The user may want to improve the user program by acquiring the state of the work or the controlled object by the camera and comparing the image with the device value. Therefore, the problem is how to manage the images and device values that are related to each other. This is because the image is generally acquired by the expansion unit 4 and the device value is generally acquired by the basic unit 3. Further, the image acquisition cycle and the device value acquisition cycle are generally different. Under these circumstances, the problem is how to manage a large amount of data such as an image by associating it with a relatively small amount of data such as a device value.

FIG. 19 shows the function of the CPU 31 of the basic unit 3. The same reference numerals are given to the parts already described. In this example, the recording unit 81 has a collecting unit 92a. When the predetermined collection start condition is satisfied, the collection unit 92a reads the device value specified by the log setting data 72 among the device values held in the device unit 34 from the device unit, and also reads the device value specified by the log setting data 72 from the device unit and from the time management unit 83a. Get time information. The collecting unit 92a associates the device value with the time information and stores it in the ring buffer 91a. The collection unit 92a acquires the device value and the time information for each collection cycle (example: scan cycle) specified by the log setting data 72 and stores them in the ring buffer 91a. The reason why the ring buffer 91a is adopted is that not all the data stored in the ring buffer 91a is stored in the memory card 36 as the log data 73. For example, the storage unit 93 may read the device value and the time information from the ring buffer 91a, create the log data 73, and store it in the memory card 36 when a predetermined storage condition is satisfied. Similarly, when the predetermined storage condition is satisfied, the storage unit 93 may read the large-capacity data and the time information from the expansion unit 4, create the log data 73, and store it in the memory card 36. The storage unit 93 stores the above-mentioned device value and time information in association with the above-mentioned large-capacity data and time information. Here, "associating" saving means that the file is saved in a form that can be easily played back on the PC 2, and for example, file management in which a plurality of files are associated with each other may be performed. Specifically, in the memory card 36, 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 to a specific folder (directory path) becomes a common flag, and this common flag can be used to "associate" and save files in the first subfolder and files in the second subfolder. It will be possible. If there is another folder placed at the same level (directory) as the above-mentioned specific folder, the other folder means a data package saved at another timing. Of course, the same subfolders as described above are also placed under this separate 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 a common flag (predetermined directory path). , You may save those multiple files. In addition, for example, by adopting a file name as a common flag and generating a file having the same or corresponding file name, it is possible to save the file "in association with each other". In addition, for example, it is possible to "associate" and save the device value and the data (large amount of data) by associating them with each other and collecting them in one file by using the time information as a key. .. In the present embodiment, a large amount of data is considered as an example of data from the monitoring device, but it goes without saying that it may be continuous data such as motion data, communication data, and voice data. The transmission unit 94 may transmit the log data 73 to the PC2, the cloud, or the like. When the ring buffer 91a is full, the collecting unit 92a overwrites the oldest information held in the ring buffer 91a with the newest information.

Here, the ring buffer 91a is adopted as an example of the buffer, but this is only an example. As a buffer, it will be sufficient if a FIFO format buffer is adopted.

FIG. 20 is a diagram illustrating the function of the CPU 41 of the expansion unit 4 having the camera input function. The clock of the time management unit 83b is synchronized with the clock of the time management unit 83a of the basic unit 3. For example, the time management unit 83a transmits time information to the time management unit 83b during the END process. The time management unit 83b synchronizes the clock of the time management unit 83b with the clock of the time management unit 83a based on the received time information. The clock may be realized by a counter that counts the time based on the time information. When a predetermined collection condition (eg, a predetermined relay device is turned on) is satisfied, the collection unit 92b periodically outputs a trigger signal, for example. The time management unit 83b acquires the time information when the trigger signal is input from the clock and stores it in the time information buffer 95. The memory 42 has a time information buffer 95 and a ring buffer 91a. The connection port 97 is an interface for connecting the camera 98 to the expansion unit 4. The connection port 97 periodically outputs the trigger signal issued by the collecting unit 92b to the camera 98, and outputs the image data output by the camera 98 to the image receiving unit 96a. Image data is an example of large-capacity data. The connection port 97 is an example of a second external interface that is connected to a monitoring device such as a camera 98 and data (image data) is input from the monitoring device. The image receiving unit 96a is all or a part of the function executing unit 96 that executes an imaging function accompanied by input of image data from the camera 98 via the connection port 97. In the present embodiment, the function executing unit 96 (image receiving unit 96a) controls the camera 98 based on imaging parameters (example of setting information) such as exposure time, gain, white balance, and contrast. Desirable parameter values are set in the PC 2 and such imaging parameters are sent to the function execution unit 96 via the communication unit 33 and the CPU 31 of the basic unit 3 shown in FIG. Therefore, the communication unit 33 shown in FIG. 4 is an example of a first external interface that receives setting information from an external setting device such as a PC2 or a display. The communication unit 33 as the first external interface also accepts the user program created by the PC 2 as described above. The camera 98 executes imaging according to the trigger signal and outputs image data. The image receiving unit 96a transfers the image data to the collecting unit 92b. The collecting unit 92b stores the time information held in the time information buffer 95 and the image data output from the image receiving unit 96a in the ring buffer 91a in association with each other. When the ring buffer 91b is full, the collecting unit 92b overwrites the oldest information held in the ring buffer 91b with the newest information. In the present embodiment, the collection unit 92b automatically and periodically outputs the image pickup trigger signal to the camera 98, but the present invention is not limited to this, and the collection unit 92b is, for example, a command from a user program. The image pickup trigger signal may be output to the camera 98 based on the above.

By the way, the basic unit 3 communicates with the expansion unit 4 by using either refresh communication executed for each scan, direct communication that can be executed at any time, or message communication executed as an event. For example, the storage unit 93 reads out the image data and the time information from the ring buffer 91b of the expansion unit 4 by using direct communication, and adds them to the log data 73. As the direct communication, a plurality of direct communications with priorities may be implemented. In this case, the priority of the direct communication executed in relation to the user program may be set relatively high, and the priority of the direct communication for logging may be set relatively low. This makes it possible to reduce the effect of logging on the execution of the user program.

<Logging using a ring buffer>
FIG. 21 shows the device value and the time information held in the ring buffer 91a of the basic unit 3. One record has the acquired device value and time information indicating the time when the device value was acquired.

FIG. 21 further shows the image data and the time information held in the ring buffer 91b of the expansion unit 4. One record has acquired image data and time information indicating the time when the image data was acquired.

FIG. 22 shows logging using the ring buffer 91a in the basic unit 3.

In S21, the CPU 31 (collecting unit 92a) determines whether or not the device value acquisition condition is satisfied. The acquisition condition is a condition for starting the storage of the device value and the time information in the ring buffer 91a. The acquisition condition may be described in the user program (eg, the start relay is turned on) or in the log setting data 72. When the acquisition condition is satisfied, the CPU 31 proceeds to S22.

In S22, the CPU 31 (collecting unit 92a) turns on the acquisition relay. The acquisition relay is a one-bit device, and is a relay for instructing the expansion unit 4 to store data in the ring buffer 91b.

In S23, the CPU 31 (collecting unit 92a) determines whether or not the device value acquisition timing has arrived. The acquisition timing is, for example, every scan cycle (for example, is acquired in the END process in each scan), and is defined by the log setting data 72. When the acquisition timing arrives, the CPU 31 proceeds to S24.

In S24, the CPU 31 (collection unit 92a) acquires the device value specified by the log setting data 72 from the device unit 34, acquires the time information from the time management unit 83a, and writes these to the ring buffer 91a.

In S25, the CPU 31 (collecting unit 92a) determines whether or not the storage timing has arrived. The save timing is a timing for saving the information held in the ring buffer 91a in the log data 73. The save timing may be, for example, the occurrence of a predetermined event (eg, save trigger). The save timing is also defined by the log setting data 72. If the save timing has not arrived, the CPU 31 returns to S23. If the save timing has arrived, the CPU 31 proceeds to S26.

In S26, the CPU 31 (collecting unit 92a) saves the information held in the ring buffer 91a in the log data 73. Of the information held in the ring buffer 91a, the information to be saved may be defined by the log setting data 72. For example, the storage target may be information acquired from the timing when a certain event occurs to the elapse of a predetermined time. Further, the storage target is information acquired from the start time, which is a predetermined time before the timing when a certain event occurs, to the end time, which is the time when the predetermined time elapses from the timing when the event occurs. You may.

In S27, (collecting unit 92a) stores the information held in the ring buffer 91b of the expansion unit 4 in the log data 73. The collecting unit 92a may read the information held in the ring buffer 91b of the expansion unit 4 by using direct communication. More specifically, the collecting unit 92a may issue an instruction for reading information from the buffer memory. Of the information held in the ring buffer 91b, the information to be saved may also be defined by the log setting data 72. For example, the storage target may be information acquired from the timing when a certain event occurs to the elapse of a predetermined time. Further, the storage target is information acquired from the start time, which is a predetermined time before the timing when a certain event occurs, to the end time, which is the time when the predetermined time elapses from the timing when the event occurs. You may.

In S28, (collecting unit 92a) determines whether or not the termination condition is satisfied. The end condition is the end condition of logging. The end condition may also be defined by the log setting data 72. If the end condition is not satisfied, the CPU 31 returns to S23. If the end condition is satisfied, the CPU 31 ends the logging process.

FIG. 23 shows logging using the ring buffer 91b in the expansion unit 4.

In S31, the CPU 41 (collecting unit 92b) determines whether or not the image data acquisition condition (eg, the acquisition relay is turned on) is satisfied. When the acquisition relay is turned on, the CPU 41 proceeds to S32. In the present embodiment, when the acquisition relay is turned on, it is determined that the image data acquisition condition is satisfied, but this is only an example. Alternatively, for example, when the mode of PLC1 is switched to the operation mode, it may be determined that the image data acquisition condition is satisfied. More specifically, the PLC1 is provided with a mode changeover switch for switching between a setting mode (program mode) for performing various settings and an operation mode (RUN mode) for repeatedly executing a ladder program to perform actual operation. May be done. In this case, if the user switches the mode changeover switch from the program mode to the RUN mode, it may be determined that the image data acquisition condition is satisfied.

In S32, the CPU 41 (collecting unit 92b) determines whether or not the image data acquisition timing has arrived. The acquisition timing is, for example, each internal control cycle (imaging cycle) of the expansion unit 4. When the acquisition timing arrives, the CPU 41 proceeds to S33.

In S33, the CPU 41 (collecting unit 92b) acquires a large amount of data and time information and stores them in the ring buffer 91b. For example, the collection unit 92b issues a trigger signal and outputs it to the camera 98 and the time management unit 83b. When the time management unit 83b receives the trigger signal, it reads the time information from the internal clock and writes it in the time information buffer 95. The camera 98 executes imaging according to the imaging conditions specified in advance, and outputs image data. The image receiving unit 96a outputs the image data to the collecting unit 92b. The image receiving unit 96a may write the image data directly to the ring buffer 91b. The collecting unit 92b associates the time information read from the time information buffer 95 with the image data acquired by the camera 98 and writes the time information to the ring buffer 91b.

In S34, the CPU 41 (collecting unit 92b) determines whether or not a read request (read instruction) to the ring buffer 91b has been issued from the basic unit 3. If the read request is received, the CPU 41 proceeds to S35. If no read request has been issued, the CPU 41 returns to S32.

In S35, the CPU 41 (collecting unit 92b) acquires image data and time information, which are large volumes of data, from the ring buffer 91b and transmits them to the basic unit 3.

In S36, the CPU 41 (collecting unit 92b) determines whether or not the end condition is satisfied. For example, the collecting unit 92b determines whether or not the acquisition relay is turned off. If the end condition is not satisfied, the CPU 41 returns to S32. If the end condition is satisfied, the CPU 41 ends the logging process.

<Connection form>
FIG. 24 shows the connection form of the building block type PLC1. An IF99a for connecting to and communicating with the expansion unit 4 is provided on the right side surface of the basic unit 3. IF is an abbreviation for interface. In this example, the expansion unit 4a is connected to the basic unit 3, and the expansion unit 4b is connected to the expansion unit 4a. The expansion unit 4 has IF99 on both the right side surface and the left side surface. The right side surface of the basic unit 3 faces the left side surface of the expansion unit 4a. Therefore, the IF99a of the basic unit 3 is connected to the IF99b provided on the left side surface of the expansion unit 4a. The right side surface of the expansion unit 4a faces the left side surface of the expansion unit 4b. Therefore, the IF99c of the expansion unit 4a is connected to the IF99d provided on the left side surface of the expansion unit 4b. The 99e provided on the right side surface of the expansion unit 4b may be connected to the end unit. In this way, IF99a to IF99e form the unit internal bus 90. For example, the image data acquired by the camera 98a connected to the expansion unit 4a can be transferred to the basic unit 3 via the unit internal bus 90. The image data acquired by the camera 98b connected to the expansion unit 4b can be transferred to the basic unit 3 via the unit internal bus 90.

As described above, in the building block type PLC1, the side surface of each unit serves as a connecting surface (connecting surface). IF99 for forming a part of the unit internal bus 90 is also provided on the side surface of each unit. As described above, the communication on the unit internal bus 90 is controlled by the bus master 38 shown in FIG.

FIG. 25 shows the connection form of the PLC1 having the backplane 200. The backplane 200 is connected to the bottom surface of the basic unit 3 and the bottom surface of the expansion unit 4, or is connected to the back surface of the basic unit 3 and the back surface of the expansion unit 4. The backplane 200 functions as a support plate (base plate) that supports the basic unit 3 and the expansion unit 4. Here, as an example, the back surface is described as a connecting surface. The back surface of the basic unit 3 faces the front surface of the backplane 200. Therefore, the IF99f provided on the back surface of the basic unit 3 is connected to the IF99g provided on the front surface of the backplane 200. The back surface of the expansion unit 4 faces the front surface of the backplane 200. The IF99h provided on the back surface of the expansion unit 4a is connected to the IF99i provided on the front surface of the backplane 200. The IF99j provided on the back surface of the expansion unit 4b is connected to the IF99k provided on the front surface of the backplane 200. IF99f to IF99k form a unit internal bus 90.

The backplane 200 may have a communication control unit 213 for controlling bus communication via the unit internal bus 90. Further, the backplane 200 may have a CPU 211 and a memory 212. The memory 212 may have a memory card 36 in addition to the RAM and ROM. In this case, the CPU 211 may function as a collecting unit 92a or a storage unit 93. Further, the memory 212 may be provided with a ring buffer 91a. Alternatively, the CPU 211 may have a time management unit 83b and a collection unit 92. In this case, the memory 212 has a ring buffer 91b.

<Log display example>
FIG. 26 shows an example of the log data 73. In this example, the device values d1 to d10, the work images i1 to i3 acquired by the camera 98a, and the acquisition timings of the other images j1 to j3 acquired by the camera 98b are shown. The device values d1 to d10 are acquired for each scan cycle. The work images i1 to i3 are acquired at the timing when the trigger signal is generated. The work images j1 to j3 are acquired at the timing when the trigger signal is generated. The position of each data indicates each time information. As shown in FIG. 26, the acquisition time and acquisition cycle of each data do not match. Therefore, the log display unit 61 adjusts the display timing of each data based on the time information of each data.

FIG. 27 is a diagram for explaining the display timing and the display duration of the log data 73. The log display unit 61 displays each device value on the display unit 7 according to the time information of each device value. For example, the log display unit 61 determines the difference time between the time information of the device value d1 and the time information of the device value d2 as the display duration of the device value d1. The log display unit 61 starts displaying the device value d2 when the display duration has elapsed since the display of the device value d1 was started. Hereinafter, the display duration is obtained in the same manner, and the displayed device value is switched according to the time information and the display duration.

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

In this way, the display timing of each data may be adjusted based on the data having the shortest logging cycle among the plurality of data included in the log data 73.

FIG. 28 is a diagram illustrating a display method of the log data 73. In this example, the relay device R000 and the data memory DM100 are acquired as the device value dx (x takes a value from 1 to 10). In this way, a plurality of device values are associated with one work image ix according to the time information. The log display unit 61 may display the device value dx, the work image ix, and the other image jx in one window, or may display each in a separate window. Further, the log display unit 61 may read the user program from the project data 71, map the device value dx to the user program, and display the user program. For example, the log display unit 61 may search for a step including a command word related to the device value dx to be displayed, display the found step, and display the device value under the command word in the step. .. The display target device may be a relay device. The log display unit 61 may change the display color of the instruction word or the icon image (example: arrow) according to the on / off of the relay device. There are two types of icon images, one showing on and the other showing off. Further, the log display unit 61 may display the device values as a graph. In this case, the log display unit 61 always displays the device values d1 to d10 in one window, and displays the work image in the other window. The log display unit 61 switches the work image with the passage of time. Here, the log display unit 61 may display a bar 103 that can be moved in the time axis direction. The bar 103 may be called a timeline bar. The log display unit 61 may display the bar 103 so as to move from left to right with the passage of time. The bar 103 may be moved by the user. In this case, the log display unit 61 accepts the movement operation of the bar 103 (eg, the drag operation by the pointer 101) through the operation unit 8, and updates the display time according to the movement operation. The log display unit 61 may extract the device value, the work image, and other images whose acquisition time is closest to the display time specified by the bar 103 from the log data 73 and display them on the display unit 7.

In the present embodiment, the camera 98 is illustrated as an example of the monitoring device, and the image pickup function of the camera 98 is exemplified as the function of the function execution unit 96. The present invention is not limited to this, and the function of the function execution unit 96 may be a motion function or a communication function. First, the former motion function will be described in detail. Consider a case where a motion unit is connected to the basic unit 3 as an expansion unit 4. In this case, in the PC2, a program (motion flow program) and parameters (axis configuration, axis control setting parameters, etc.) that define the operation of the motion unit are set, and so-called setting information is created. Then, the setting information is sent to the function execution unit of the motion unit via the first external interface (communication unit 33) and reflected in the motion unit. The function execution unit of the motion unit transmits operation command values such as target coordinates and target speed to the motor amplifier connected to the outside according to the setting information. Motion data such as current coordinates and current speed is received from the motor amplifier via an encoder. The control cycle for receiving motion data such as the current coordinates and the current speed is shorter than the scan cycle of the ladder program and is asynchronous with the scan cycle of the ladder program. Therefore, the collecting unit of the motion unit collects the motion data at a predetermined cycle, and stores the information regarding the reception time when the motion data is received in the ring buffer 91b in association with the motion data. After that, at the save timing (similar to step S25 in FIG. 22), motion data (current coordinates, current speed, etc.) and time information are acquired from the ring buffer 91b, as in the process described with reference to FIG. Add to log data. This makes it possible to easily identify which device value is associated with which motion data. On the other hand, to explain the latter communication control in detail, consider a case where a communication unit is connected to the basic unit 3 as an expansion unit 4. In this case, in the PC2, a program (communication flow program) and parameters (communication cycle, transfer speed, etc.) that define the operation of the communication unit are set, and setting information is created. Then, as in the motion control described above, the setting information is reflected in the communication unit via the communication unit 33. Then, the function execution unit of the communication unit receives communication data such as a plurality of sensor values from a sensor group connected to the outside (such as one in which a plurality of photoelectric sensors are connected) according to the setting information. The reception cycle of such communication data (cyclic communication cycle) is asynchronous with the scan cycle of the ladder program. When the number of sensors constituting the sensor group is large, the communication data itself may constitute a large amount of data. The collecting unit of the communication unit collects communication data in a predetermined cycle (so-called cyclic communication cycle), and stores the communication data in the ring buffer 91b in association with the information regarding the reception time when the communication data is received. After that, as in the process described with reference to FIG. 22, when the save timing comes (similar to step S25 in FIG. 22), communication data (sensor value, etc.) and time information are acquired from the ring buffer 91b, and log data. Add to.

<Setting of collection period>
The log setting unit 51 may accept the setting of the collection period of the log data 73.

FIG. 29 shows the UI 160 for setting the collection period. The UI 160, UI 110, and UI 100 may be switched by selecting the corresponding tabs with the pointer 101. The UI 160 has a pull-down menu 161 for specifying a collection method. The collection method is a collection method of log data 73. In this example, a collection method called before and after the save trigger and a collection method called a start relay are described. Before and after the save trigger is a method of collecting log data 73 at a collection time Ta before the timing when the save trigger is turned on and a collection time Tb after the timing when the save trigger is turned on. The text box 162 accepts the input of the collection time T. The collection time T is the total value of the collection time Ta and the collection time Tb. The text box 163 accepts the input of the collection time Tb after the trigger. The save trigger setting unit 164 accepts the device name of the relay device used as the save trigger and the setting of the condition (eg, switching from off to on). The up arrow means that the relay device specified as the save trigger has switched from off to on. Guidance unit 165 is a UI for explaining the collection period. In this example, it is shown that the log data 73 is collected with the save trigger as a boundary. The log setting unit 51 may also display the above-mentioned information on the device size and the increase in the scan time on the UI 160.

In the collection method called before and after the save trigger, device values and image data are always stored in the ring buffer 91. When the relay device R200, which is a storage trigger, is turned on, the storage unit 93 creates the log data 73 of 20 seconds specified as the collection time. The storage unit 93 reads from the data recorded 18 seconds before the timing when the relay device R200 is turned on, the data recorded up to 2 seconds after the timing, from the ring buffer 91, and creates the log data 73. ..

FIG. 30 shows the UI 160 for setting the collection period. In this example, the pointer 101 selects the start relay as the collection method from the pull-down menu 161. The log setting unit 51 changes the UI 160 according to the collection method selected by the user. The text box 166 accepts the device name of the relay device used as the start relay. As shown by the guidance unit 165, in the collection method called the start relay, the timing at which the start relay is turned on is the starting point (starting point) of the collection time. For example, suppose it takes 30 seconds to press a piece of work flowing down a production line. Further, it is assumed that the time during which the trouble can occur is the first 20 seconds of the processing time of 30 seconds. The relay device R000 is a relay that defines the timing at which the press process is started. When the relay device R000 is turned on, the collecting unit 92 stores the device value and the image data in the ring buffer 91 for 20 seconds. When the relay device R000 is turned on again when the next work arrives, the collecting unit 92 stores the device value and the image data in the ring buffer 91 for 20 seconds. When the relay device R200, which is a storage trigger, is turned on, the storage unit 93 acquires the latest device values and image data for 20 seconds stored in the ring buffer 91 and creates log data 73. The relay device R200, which is a storage trigger, is a relay device that is turned on when a trouble occurs.

The log setting unit 51 stores the information set through the UI 160 in the log setting data 72, and transfers the information together with the project data 71 to the basic unit 3.

<Debugging>
FIG. 31 is a flowchart showing an outline of the debugging process of the user program executed by the user.

In S41, the user operates the PC 2, creates a user program composed of a plurality of program components, and creates project data 71 including the user program. The program creation unit 63 creates a user program according to the user input and stores it in the storage device 22. The project creation unit 50 creates the project data 71 according to the user input and stores it in the 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 execute an operation on the project data 71 or the user program to obtain a hash value, an error detection code, or the like, and add these as identification information to the project data 71. The identification information may be a GUID (global unique identifier) or the like.

In S42, the user operates the PC2 and transfers the project data 71 to the PLC1. The project creation unit 50 reads the project data 71 from the storage device 22 and transmits it to the PLC 1 via the communication unit 23. When the basic unit 3 of the PLC1 receives the project data 71, it writes it to the storage device 32.

In S43, the user operates the operation unit 6 of the basic unit 3 (for example, by operating the mode changeover switch for switching from the PROGRAM mode to the RUN mode), and instructs the execution of the project. The execution unit 80 executes the user program included in the project data 71. The recording unit 81 logs the device value and the like, and stores (records) the logged device value in the ring buffer 91a. When a predetermined output condition is satisfied, the storage unit 93 of the output units 84 stores the device value recorded in the ring buffer 91a and the above-mentioned image data in the memory card 36 or the internal memory 37. , Create log data 73.

Further, as shown in FIG. 19, the storage unit 93 stores the project data 71 in the memory in addition to the log data 73. As a result, in the PC2, the movement at the time of the trouble can be reproduced on the monitor by using the project data 71 at the time of the trouble. Details will be described later.

Further, the storage unit 93 stores the identification information (hash value, etc.) of the project data 71 in the memory in addition to the project data 71. As a result, the PC2 can use the identification information to verify whether or not the current project data (which is to be replayed) matches the project data 71 when the actual trouble occurs. Details will be described later.

In the present 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 the predetermined output conditions are satisfied, but the present invention is not limited to this. .. For example, the project data 71 and its identification information are stored in the memory before, during, or during the operation of the PLC1, and only the log data 73 is stored in the memory when a predetermined output condition is satisfied. You may want to save it. In short, when the predetermined output condition is satisfied, the log data 73, the project data 71, and the identification information may be associated with each other and stored in the memory.

Further, in the present 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 is stored in the memory. You may. In this case, it is assumed that the current project data on the PC2 matches the project data 71 at the time of the actual trouble occurrence. That is, it is assumed that the current project data has not been edited or modified after the project data has been transferred to PLC1. If it is determined that both data do not match, the user may replay after recognizing that the current project data is different from the project data 71 at the time of the actual trouble. It is possible to prevent replay (inaccurate troubleshooting) from being performed without recognizing this.

In S44, the user operates the operation unit 6 of the basic unit 3 and instructs to transfer the project data 71 and the log data 73 to the PC 2. Alternatively, the operation unit 8 of the PC 2 may be operated to read the project data 71, the identification information of the project data 71, and the log data 73 written in the memory card 36. The output unit 84 transmits the project data 71 and the log data 73 to the PC2. 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 at the timing when a predetermined condition for writing to the memory card 36 is satisfied, and the hash value or an error detection code or the like is executed. And these may be added to the log data 73 as identification information. Any rule may be adopted as long as the rules for creating the identification information executed by the PC 2 and the rules for creating the identification information executed by the basic unit 3 match.

In S45, the user operates the PC2, investigates the cause of the trouble while playing back (replaying) the log data 73, and debugs the user program constituting the project data 71. The 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 including the log data 73. This includes displaying the time-series image data in the display unit 7. The log display unit 61 has an internal clock that measures a virtual time, acquires a device value from the log data 73 in synchronization with the internal clock, and displays it on the display unit 7. The project data 71 may not be transmitted from the PLC1. In this case, the log display unit 61 may display the device value in association with the user program by using the user program of the project data 71 (master data) stored in the storage device 22. Details of investigating the cause of the trouble caused 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 acquire the log data 73 and the version of the project data 71 held in the PC 2 may be different. In this case, it may be impossible to display the device value in association with the user program, or the association between the user program and the device value may be incorrect. In this case, the log display unit 61 uses the identification information of the project data, and the version of the project data 71 used to acquire the log data 73 is different from the version of the project data 71 held in the PC 2. A warning indicating that may be displayed on the display unit 7. The log display unit 61 determines whether or not the log data 73 acquired by using the first version project data 71 is displayed in association with the second version project data 71 held in the PC 2. You may also contact the user. When the user desires such a display, the log display unit 61 uses the log data 73 acquired by using the first version project data 71 to store the log data 73 in the second version project data stored in the PC 2. It is displayed on the display unit 7 in association with 71. The version is managed by the identification information. When the user confirms that there is no problem with the log data 73, debugging is unnecessary, and subsequent S46 and S47 are also unnecessary. The user analyzes the log data 73, finds a bug in the user program, and corrects the user program. The project creation unit 50 modifies (updates) the project data 71 according to the user input and stores it in the storage device 22.

In S46, the user operates the PC2 and transfers the project data 71 to the PLC1. When the user program in the project data 71 is changed, the identification information is updated. As a result, the project data 71 before the modification and the project data 71 after the modification can be distinguished.

In S47, the user operates the basic unit 3 and instructs the execution of the user program included in the project data 71 to verify the project data 71. The execution unit 80 executes the user program included in the project data 71. If the PLC1 is operating as expected by the user, the user determines that the project data 71 has been successfully debugged. If the PLC1 is not operating as expected by the user, the recording unit 81 logs the device value and the like again, and the storage unit 93 creates the log data 73. Then, the user executes S44 to S47 again.

In this way, the user can debug the project data 71 while referring to the log data 73. Therefore, it is considered that the efficiency of debugging is improved.

The transfer of the project data 71 may be executed via the memory card 36. That is, the PC 2 writes to the memory card 36. The user removes the memory card 36 from the PC 2 and attaches the memory card 36 to the basic unit 3. The basic unit 3 reads the project data 71 from the memory card 36 and writes it to the storage device 32. Similarly, the transfer of the log data 73 may also be executed via the memory card 36.

<Output section>
FIG. 32 shows an output unit 84 mounted on the basic unit 3. In addition to the log data 73, the output unit 84 may transfer the project data 71 used when acquiring the log data 73 to the PC2. However, in order to prevent information leakage of the project data 71, an access authority (protection) for prohibiting writing to the memory card 36 and transmission to the PC 2 may be set in the project data 71. Therefore, the determination unit 301 refers to the access authority given to the project data 71 and determines whether or not the output of the project data 71 is prohibited. When the output of the project data 71 is prohibited, the output unit 84 outputs the log data 73, but does not output the project data 71. On the other hand, if the output of the project data 71 is not prohibited, the output unit 84 outputs the log data 73 and the project data 71. When the output of the project data 71 is prohibited, the addition unit 302 may output the identification information of the project data 71 held in the storage device 32 together with the log data 73. This identification information may be a part of the project data 71, or the identification information may be obtained by the calculation unit 303 executing a predetermined calculation on the project data 71 or the user program. The predetermined operation may be, for example, a hash operation or an error detection code operation. The real-time transmission unit 304 transmits the device value held in the device unit 34 in real time. This is useful when displaying device values in real time on a display device such as a PC2 or HMI (human interface).

<Project Creation Department 50>
FIG. 33 shows the details of the project creation unit 50. The function setting unit 62 sets the configuration information of the expansion unit 4, the function of the basic unit 3, and the function of the expansion unit 4 based on the information input from the operation unit 8, and creates the configuration information indicating the setting contents. The function settings of the basic unit 3 include IP address settings, FTP client settings, and access authority settings for project data 71. The function settings of the expansion unit 4 include input channel settings and settings related to communication between PLCs. The configuration information is a part of the project data 71. The editing unit 311 (which may also serve as the program creating unit 63 shown in FIG. 6) displays the editing UI of the user program on the display unit 7 and edits the user program based on the information input from the operation unit 8. The debug unit 314 debugs the user program using the project data 71. The addition unit 312 adds identification information to the project data 71. The calculation unit 313 obtains identification information (eg, hash value or error detection code) by calculation. Regarding the calculation (calculation) function of the identification information by the calculation unit 313, the output unit 84 may exert the same function.

<Log display unit 61>
FIG. 34 shows the details of the log display unit 61. The program display module 321 is a module that displays the device value included in the log data 73 on the display unit 7 together with the user program included in the project data 71. Further, in the program display module 321, not only the user program but also the user visually recognizes the setting contents of the project data 71 such as the program configuration information included in the project data 71, a plurality of program parts, the unit configuration, and the function setting for each unit. It is possible to display various information for the purpose. The image display module 323 displays the time-series image data included in the log data 73 on the display unit 7. The waveform display module 322 is a module that waveforms the time-series device values included in the log data 73 and displays them on the display unit 7. The reproduction control module 324 synchronizes the information displayed by the program display module 321 with the information displayed by the waveform display module 322 in time. These modules may be referred to as engineering software. The image display module 323 may be embodied as one function (image display unit) of the program display module 321 or as a function (image display unit) of the waveform display module 322.

● Program display module FIG. 35A shows the details of the program display module 321. The time UI 330a provides a UI (eg, a slide bar, a cursor, etc.) for operating the acquisition time (display time) of the device displayed together with the user program. The display time control unit 331a sends the display time specified by the time UI 330a to the reproduction control module 324, and sets the display time notified from the reproduction control module 324 to the time UI 330a. The program display unit 332 displays the project data 71 on the display unit 7, or reads the project data 71 corresponding to the identification information from the storage device 22 and displays it on the display unit 7. Further, the program display unit 332 displays the device value acquired by the device value acquisition unit 333a in association with the device used or described in the user program. The device value acquisition unit 333a has a real-time reproduction mode and a log reproduction mode. The device value acquisition unit 333a accesses the real-time transmission unit 304 of the PLC1 in the real-time reproduction mode, acquires the device value, and passes it to the program display unit 332. The device value acquisition unit 333a accesses the reproduction control module 324 in the log reproduction mode, acquires the display time and the device value, and passes the display time and the device value to the program display unit 332.

FIG. 35B is a schematic diagram showing an example of the GUI displayed on the display unit 7 by the program display unit 332 and the like.

In FIG. 35B, 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 (basic unit, motion unit, analog input unit, camera unit) and program configuration (every scan module, fixed cycle module, inter-unit synchronization module, function block, macro) are displayed. For the motion unit, the axis configuration and axis control setting parameters are displayed as function settings. By double-clicking the axis configuration and axis control on the GUI shown in FIG. 35B, the user can confirm what kind of setting contents are set for these setting parameters. Further, in the project display area 420, when Main and Sub are displayed for each scan module, when the user clicks Main, the Main program is displayed in the program display area 410 of the central ladder monitor 450. As described above, the program display module 321 shown in FIG. 34 reads the project data 71 from the memory card 36, displays various information in the project display area 420, and displays a desired program in the program display area 410.

Here, the program display area 410 is a part of the so-called ladder monitor 450, and can be operated independently in the real-time reproduction mode. It is also possible to hide only the ladder monitor 450 by clicking the x mark. On the other hand, in the log reproduction mode, the program display unit 332 can reproduce the ladder program included in the project when the operation record is saved. Further, in the log reproduction mode, the program display unit 332 displays the device value included in the log data 73 via the device value acquisition unit 333a in association with the device described in the Main program. The device value to be displayed is the device value corresponding to the time specified by the time designation cursor 404 (more details will be described with reference to FIG. 38 described later).

In FIG. 35B, the device value associated with 18:52:54 of 20XX / 10/01 displayed in the time display area 409 is displayed in association with the device described in the Main program. [35000/74286] displayed on the right side of this date indicates the current number of scans 35,000 for the total number of scans 74286. By dragging and moving the time designation cursor 404, the user updates the display time and the number of scans, and also updates the display of the device value. For example, at the updated display time, an ON display (for example, painting with a color) is made on the part of the relay device that is ON, and an OFF display (for example, color removal, etc.) is made on the part of the relay device that is OFF. Is done. Details of the function of the play button 406 and the like will be described later with reference to FIG. 38.

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

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

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

FIG. 35C is a diagram illustrating a data source for displaying the GUI in the log reproduction mode. As shown in FIG. 35C, the project display area 420 reads the unit configuration, function setting, program configuration, and program component included in the project data 71 from the memory and displays them in a tree format. The ladder monitor 450 reads the program configuration (what kind of program component it is composed of) and the program component from the memory, displays the program component specified by the user, and displays the device value corresponding to the display time from the log data 73. Read and display. The camera monitor 430 logs based on information such as unit configuration (whether or not there is a camera monitor) and function settings (camera monitor functions. For example, if there are multiple ports, port number, image pickup cycle, gain setting, etc.). The image data corresponding to the display time is read from the data 73 and displayed. The unit monitor 440 has a device value corresponding to the display time from the log data 73 based on information such as the unit configuration (what kind of unit is present) and the function setting (axis configuration, axis control, etc. in the case of a motion unit). Is read and displayed.

As can be seen from FIGS. 35B and 35C, the program display module 321 and the image display module 323 and the unit display module 325 can be synchronously controlled and linked by the function of the reproduction control module 324. The details of the cooperation of the waveform display module 322 will be described later.

Here, in the present embodiment, it is possible to verify whether or not the current project data matches the project data 71 at the time of actual trouble occurrence. More specifically, the collating unit 334 of the program display module 321 shown in FIG. 35 has the identification information of the project data 71 (user program) output from the PLC 1 and the project data 71 stored in the storage device 22. The identification information of (user program) is collated, and the collation result is output to the warning unit 335. In the warning unit 335, the identification information of the project data 71 (user program) output from the PLC 1 when the operation record is saved and the identification information of the project data (user program) stored in the storage device 22 do not match. If, a warning is displayed on the display unit 7.

For example, the warning unit 335 causes the display unit 7 to display a warning screen 470 as shown in FIG. 35D. To give a specific example, it is assumed that the identification information of the project data 71 when the operation record is saved and the identification information of the current project data (which is to be replayed) do not match. For example, after transferring the project data to PLC1, the user edits the project data (program, function setting, etc.). In this case, when the real-time reproduction mode is changed to the log reproduction mode based on the user operation, the warning screen 470 shown in FIG. 35D is displayed.

On the warning screen 470 shown in FIG. 35D, the user is made to select whether to perform log reproduction using the current project data as it is or to perform log reproduction using the operation record project. In the former case, the user recognizes that the current project data is different from the project data 71 at the time of the actual trouble, and then performs the log reproduction. On the other hand, in the latter case, for example, the user specifies the path (folder or directory) in the storage device 22 in which the operation record project is stored, so that the log is reproduced using the operation record project. be able to.

In this embodiment, the identification information of the two project data is compared to verify the match / mismatch. More specifically, identification information is added to each of the program configuration, multiple program parts, unit configuration, and function settings included in the project data, and it is verified by checking whether all of them match. And said. However, the present invention is not limited to this, and at least the identification information of the user program composed of a plurality of program components may be compared to verify the match / mismatch.

● Waveform display module FIG. 36A shows the details of the waveform display module 322. The time UI 330b provides a UI (eg, a slide bar, etc.) for operating the acquisition time (display time) of the device displayed together with the user program. As shown in FIG. 28, the time UI 330b basically moves the bar 103 from left to right according to the display time provided by the playback control module 324. However, the time UI 330b accepts the operation of the bar 103 through the operation unit 8 and passes the operation amount of the bar 103 to the reproduction control module 324 through the display time control unit 331b. The display time control unit 331b sends the display time specified by the time UI 330b to the reproduction control module 324, and sets the display time notified from the reproduction control module 324 to the time UI 330b. The device value acquisition unit 333b has a real-time reproduction mode and a log reproduction mode. The device value acquisition unit 333b accesses the real-time transmission unit 304 of the PLC1 in the real-time reproduction mode, acquires the device value, and passes it to the waveform display unit 336. The device value acquisition unit 333b accesses the reproduction control module 324 in the log reproduction mode, acquires the display time and the device value, and passes the display time and the device value to the waveform display unit 336. As shown in FIG. 28, the waveform display unit 336 waveforms the device value acquired by the device value acquisition unit 333b and displays it on the display unit 7. Waveformation of the device value is not essential, and the device value may be displayed as a numerical value. As shown in FIG. 28, the image display module 323 displays the image data output from the reproduction control module 324 on the display unit 7. As described above, the image display module 323 may be realized as one function of the waveform display module 322, but as shown in FIG. 34, the image display module 323 may have another function as the image display module 323 (camera monitor). good.

FIG. 36B is a schematic diagram showing an example of a GUI displayed on the display unit 7 by the waveform display module 322 and the like. In particular, the GUI displayed by the waveform display module 322 is the so-called real-time chart monitor 460 displayed in the pop-up window at the lower right.

In FIG. 36B, the project display area 420 in the left column, the program display area 410 (ladder monitor 450) in the center, and the image display area (camera monitor 430) in the upper right column are the same as those shown in FIG. 35B. That is, these displays are made by the program display module 321 and the image display module 323. In FIG. 36B, the unit monitor 440 by the unit display module 325 omits the display, but this may be displayed.

The outline of the real-time chart monitor 460 shown in FIG. 36B is as described with reference to FIG. 28. In FIG. 36B, the waveform data of the relay device R000 and the waveform data of the data memory DM100 are read from the memory and displayed. The device to be displayed on the real-time chart monitor 460 can be freely adjusted by the user through a setting screen (not shown).

A time designation cursor 404b (corresponding to bar 103 shown in FIG. 28, which may be called a playback position cursor) is displayed below the real-time chart monitor 460, and the user clicks the position of the time designation cursor 404b. It can be moved. At this time, when the position of the time designation cursor 404b moves, the time designation cursor 404 on the ladder monitor 450 and the time designation cursor 404a on the camera monitor 430 move in conjunction with each other by the function of the playback control module 324. .. Specifically, in FIG. 36B, the horizontal axis in the waveform display area of the real-time chart monitor 460 indicates the number of scans (may be switched to the time and displayed), but the user clicks the time designation cursor 404b to determine the number of scans. When the slide is moved to the position of the number of scans, the time designation cursor 404 on the ladder monitor 450 and the time designation cursor 404a on the camera monitor 430 move to the position of the display time corresponding to the number of scans, respectively. Then, the device value and the image data corresponding to the display position after the movement are displayed. Of course, the reverse is also true. That is, when the time designation cursor 404 on the ladder monitor 450 or the time designation cursor 404a on the camera monitor 430 is clicked and slid to a desired position, the time designation cursor 404b also moves to the position of the number of scans corresponding to the desired position. .. At this time, if the time designation cursor 404 or the time designation cursor 404a is moved by a certain amount or more, the position indicated by the time designation cursor 404b is out of the display range of the current real-time chart monitor 460. The display range follows so that it is always within the display range.

Here, as shown in FIG. 36B, in the real-time chart monitor 460, the time designation cursor 404b includes a vertical line superimposed on the waveform display area, a triangular mark added to the lower end of the vertical line, and a figure of a triangle mark. The display area bar 404c is further displayed below the time designation cursor 404b. A square indicator indicating the current position is displayed in the center of the display area bar 404c. The user can change the range displayed on the real-time chart monitor 460 by dragging this indicator and moving it left and right. Then, the user can perform troubleshooting to investigate the cause of the trouble by making good use of the display area bar 404c. This point will be described in more detail with reference to FIG. 36C.

FIG. 36C is an explanatory diagram for explaining the relationship between the display range displayed on the real-time chart monitor 460 and the time designation cursor 404b.

In FIG. 36C, it is assumed that the relay devices R000 and R001, the data memories DM100 and DM101 are displayed on the real-time chart monitor 460. In FIG. 36C, for convenience of explanation, it is assumed that 15 device values (black circles) are displayed on the real-time chart monitor 460 for each device. Further, among these device values, the device value corresponding to a specific time for each device becomes the device value specified by the time designation cursor 404b. In FIG. 36C, the device values correspond to the time in the center of the range displayed on the real-time chart monitor 460. When the user drags the time designation cursor 404b and moves it to the right, for example, the display range is set so that the time designation cursor 404b fits within the display range in the same manner as the time designation cursor 404 and the time designation cursor 404a described above. Will follow. On the other hand, when the user drags the square indicator of the display area bar 404c and moves it to the right, for example, the display range of the real-time chart monitor moves to the right, and when it moves by a certain amount (8 device values). When moving to the right by a minute), the time specification cursor 404b is hidden. However, in the present embodiment, even if the time designation cursor 404b is hidden, the time designation cursor 404b jumps to the desired position by double-clicking the desired position in the waveform display area so that troubleshooting can be easily performed. It is designed to do. In other words, the waveform display unit 336 shown in FIG. 36A has a function of accepting the designation of a desired position from the user in the waveform display area and moving the time designation cursor 404b to the accepted designated position.

The troubleshooting procedure (one example) using the GUI shown in FIG. 36C will be described more specifically.

(1) The user first investigates the cause of the trouble while visually recognizing the device waveform displayed in the waveform display area by dragging the square indicator to the left or right on the display area bar 404c of the real-time chart monitor 460. Find a time that might be useful for you. At this time, as described above, the time designation cursor 404b may be hidden from the display range of the real-time chart monitor 460.

(2) When a time with an abnormal device value is found in the device waveform, double-click the time in the waveform display area. Then, the time designation cursor 404b jumps to that time, and the time designation cursor 404 on the ladder monitor 450 and the time designation cursor 404a on the camera monitor 430 both jump to that time.

(3) As a result, the reproduction control module 324 displays the device value corresponding to the time on the ladder monitor 450, and the image data corresponding to the time on the camera monitor 430. Therefore, the user can investigate the cause of the trouble while visually recognizing these device values and image data.

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

Similarly, the reproduction control unit 343 may synchronize the time of the image display module 323 and the unit display module 325 in addition to the display time of the program display module 321 and the display time of the waveform display module 322.

In the present embodiment, the display times of the program display module 321 and the waveform display module 322, the image display module 323, and the unit display module 325 are always synchronized in the log reproduction mode, but the present invention is limited to this. Instead, for example, the user may be able to select whether or not to synchronize. For example, a check box for synchronization may be provided on each monitor screen so that the check box is set by default. Then, the user can not synchronize only the module that he / she does not want to synchronize by unchecking the module. As described above, the log display unit 61 may have a selection function for selecting a module to be synchronously controlled (follow-up control) by the reproduction control module.

<Program display UI>
FIG. 38 shows the display UI 400 provided by the program display module 321. The display UI 400 described with reference to FIGS. 35B and 36A will be described in more detail from another viewpoint. The program display area 410 is an area for displaying the user program of the project data 71. In this example, the program display area 410 displays a ladder program (ladder diagram). The program display unit 332 acquires the device value of the device used or described in the user program by the device value acquisition unit 333a and displays it together with the user program. For example, the program display unit 332 may display the icon 401a indicating ON on the user program if the relay device is ON. If the relay device is OFF, the program display unit 332 may display the icon 401b indicating OFF on the user program. The program display unit 332 may acquire the device value of the DM100, which is an output device, by the device value acquisition unit 333a and display it in an overlapping manner with the description of the DM100 in the user program. In this example, a device value display area 403 is provided under the description of DM100. The program display unit 332 displays the device value in the display area 403. Since the playback control module 324 updates the device value as well as the display time, the program display unit 332 updates the device value displayed together with the user program. The time UI 330a moves the time designation cursor 404 from right to left according to the display time acquired from the time device 342. The time designation cursor 404 can be dragged by the pointer 101. When the time UI 330a detects that the time designation cursor 404 has been dragged by the pointer 101, the display time control unit 331a stops the playback control unit 343 from updating the display time, and the drag amount of the time designation cursor 404 is adjusted to the playback control unit 343. Notify to. The reproduction control unit 343 adjusts the count value (display time) of the internal clock according to the drag amount. Even if the time UI330a displays the update speed of the display time (example: ..., 2.0 times, 1.0 times, 0.5 times, 0.1 times, ...) On the speed designation unit 405. good. The speed designation unit 405 may be realized by a pull-down menu that displays a list of a plurality of update speeds and can select one of the update speeds. When the time UI 330a detects a click by the pointer 101 on the speed designation unit 405, such a pull-down menu may be displayed and the selection of the update speed may be accepted. The play button 406 is a button for instructing the time-series display of the device value. When the time UI 330a detects that the play button 406 is clicked by the pointer 101, the time UI 330a instructs the display time control unit 331a to start updating the display time. This instruction corresponds to an instruction to start displaying the device value or an instruction to restart the display. The one-step reverse playback button 407 is a button for instructing the display of device values in chronological order while updating (rewinding) the display time step by step. When the time UI 330a detects that the one-step reverse playback button 407 is clicked by the pointer 101, the time UI 330a instructs the display time control unit 331a to move the display time back one step. The one-step playback button 408 is a button for instructing the device values to be displayed in chronological order while updating the display time step by step. When the time UI 330a detects that the one-step playback button 408 is clicked by the pointer 101, the time UI 330a instructs the display time control unit 331a to advance the display time by one step. When one-step playback is being executed, the playback control unit 343 does not update the display time unless the one-step reverse playback button 407 or the one-step playback button 408 is operated. If the playback button 406 is operated while one-step playback is being executed, the playback control unit 343 restarts the update of the display time at the update speed specified by the speed designation unit 405. The time display area 409 is an area for displaying the display time held in the time device 342. The display time control unit 331a displays the display time acquired from the time device 342 in the time display area 409.

<HMI emulator>
The PLC1 can be connected to an external display device called an HMI. The HMI may have a touch panel type input device. The HMI reads out the device value held in the device unit 34 of the PLC1 and displays it on the display device. The project creation unit 50 sets the UI displayed on the HMI and the device value displayed on the UI, and saves it in the project data 71. The debug unit 314 has an HMI emulator, and confirms the operation of the HMI by operating the emulator according to the project data 71. The log display unit 61 supplies the device value of the log data 73 to the HMI emulator. The HMI emulator displays the device values provided in chronological order on the UI.

FIG. 39 shows the UI490 of the HMI emulator. In this example, the HMI emulator is included in the program display module 321. The program display unit 332 reflects the device value provided by the playback control unit 343 in the display area of the UI 490. The UI 490 may have a time control object related to the playback control included in the UI 400, such as a time designation cursor 404 and a play button 406. The operation of the time control object in the UI 490 is reflected in the UI 400 and the UI shown in FIG. 28 through the playback control unit 343. For example, when the time designation cursor 404 is operated to the left in the UI 490, the time designation cursor 404 of the UI 400 also moves to the left in conjunction with the display time provided by the playback control unit 343, and the bar shown in FIG. 28 103 also moves to the left. Further, if the bar 103 shown in FIG. 28 is operated to the left, the time designation cursors 404 of the UI 400 and 450 also move to the left in conjunction with the display time provided by the reproduction control unit 343. This is because they are all synchronized with the same display time held in the time device 342.

<Flowchart related to log display>
● Program display module FIG. 40 shows the display process executed by the program display module 321. Note that S50, S51 and S60 may be executed only when the project data 71 cannot be acquired from the PLC1. If the project data 71 can be obtained from the PLC1, the project data 71 is used from the PLC1. If the project data 71 cannot be acquired from the PLC 1, the project data 71 held in the PC 2 is used.

In S50, the CPU 21 (collation unit 334) acquires the identification information of the project data 71 held in the PLC1 and the identification information of the project data 71 held in the PC2.

In S51, the CPU 21 (collation unit 334) determines whether or not the identification information of the project data 71 held in the PLC1 matches the identification information of the project data 71 held in the PC2. If they do not match, the CPU 21 proceeds to S60. In S60, the CPU 21 (warning unit 335) displays a warning on the display unit 7 indicating that the identification information of the project data 71 held in the PLC1 and the identification information of the project data 71 held in the PC2 do not match. .. If both match, the CPU 21 proceeds to S52.

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

In S53, the CPU 21 (program display unit 332) determines whether the log reproduction mode is selected or the real-time reproduction mode is selected based on the information input from the operation unit 8. If the real-time playback mode is selected, the CPU 21 proceeds to S58. In S58, the CPU 21 (device value acquisition unit 333a) acquires the device value from the real-time transmission unit 304 of the PLC1 without going through the reproduction control module 324. In S59, the CPU 21 (program display unit 332) displays the device value on the display unit 7 together with the user program included in the project data 71. If the log reproduction mode is selected, the CPU 21 proceeds to S54.

In S54, the CPU 21 (device value acquisition unit 333a) activates the reproduction control module 324 and acquires the display time and the device value of the log data 73 from the reproduction control module 324.

In S55, the CPU 21 (program display unit 332) displays the device value and the display time on the display unit 7 together with the user program included in the project data 71.

In S56, the CPU 21 (display time control unit 331a) determines whether or not the time designation is detected by the time UI 330a. As described above, the time designation is executed by the operation of the time designation cursor 404. If the time designation is not detected, the CPU 21 returns to S54. If the time designation is detected, the CPU 21 proceeds to S57.

In S57, the CPU 21 (display time control unit 331a) notifies the reproduction control unit 343 of the reproduction control module 324 of the designated time input by the time designation cursor 404. The CPU 21 returns to S54.

● Waveform display module FIG. 41 shows a display process executed by the waveform display module 322.

In S61, the CPU 21 (waveform display unit 336) determines whether the log reproduction mode is selected or the real-time reproduction mode is selected based on the information input from the operation unit 8. If the real-time playback mode is selected, the CPU 21 proceeds to S66. In S66, the CPU 21 (device value acquisition unit 333b) acquires the device value from the real-time transmission unit 304 of the PLC1 without going through the reproduction control module 324. In S67, the CPU 21 (waveform display unit 336) displays the device value on the display unit 7. If the log reproduction mode is selected, the CPU 21 proceeds to S62.

In S62, the CPU 21 (device value acquisition unit 333b) activates the reproduction control module 324 and acquires the device value and the display time from the reproduction control module 324.

In S63, the CPU 21 (waveform display unit 336) displays the device value and the display time on the display unit 7.

In S64, the CPU 21 (display time control unit 331b) determines whether or not the time designation is detected by the time UI 330b. As described above, the time designation is executed by the bar 103. If the time designation is not detected, the CPU 21 returns to S62. If the time designation is detected, the CPU 21 proceeds to S65.

In S65, the CPU 21 (display time control unit 331b) notifies the reproduction control unit 343 of the reproduction control module 324 of the designated time input by the bar 103. The CPU 21 returns to S62.

● Reproduction control module FIG. 42 shows the reproduction control executed by the reproduction control module 324.

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

In S72, the CPU 21 (reproduction control unit 343) initializes the time of the internal clock.

In S73, the CPU 21 (reproduction control unit 343) acquires the time of the internal clock and stores the time in the time device 342.

In S74, the CPU 21 (reproduction control unit 343) acquires the device value corresponding to the display time held in the time device 342 from the log data 73 and stores it in the log device 345. As a result, the device value providing unit 341 can provide the device value and the display time to the program display module 321 and the waveform display module 322.

In S75, the CPU 21 (reproduction control unit 343) determines whether or not the time designation has been received from the display time control unit 331. If the time designation is received, the CPU 21 proceeds to S76. If the time designation has not been received, the CPU 21 proceeds to S77.

In S76, the CPU 21 (reproduction control unit 343) changes the time of the internal clock according to the time designation from the display time control unit 331.

In S77, the CPU 21 (reproduction control unit 343) determines whether or not the update speed change instruction has been received from the display time control unit 331. If the change instruction is received, the CPU 21 proceeds to S78. If the change instruction has not been received, the CPU 21 proceeds to S73.

In S78, the CPU 21 (reproduction control unit 343) changes the update speed of the internal clock according to the update speed specified by the display time control unit 331. After that, the CPU 21 proceeds to S73.

<Narrowing down program parts>
The PC 2 extracts the device to be logged when setting the log, and extracts other devices related to the specific device when displaying the log. In order to explain this extraction process, the following example is adopted.

FIG. 43 shows a plurality of modules constituting the ladder program. In this example, the following PLC1 is assumed. The work is conveyed by the transfer belt. When the work detection sensor detects the work, the height sensor measures the height of the work, and the depth sensor measures the depth of the work. If the height of the work is not within the predetermined range, it is determined that the measurement is NG. Similarly, if the depth of the work is not within the predetermined range, it is determined that the measurement is NG. FIG. 43 shows a program module for realizing these series of processes. Each module includes contact system commands (input system commands) and output system commands. The contact system instruction is a condition for executing the output system instruction.

In the work detection module B1, the device MR000 is a relay device that turns ON when a work is detected. This is a relay device that turns ON when the device MR0002PLC1 is in automatic operation. The device MR001 is a relay device for instructing the expansion unit 4 to start measurement. The device MR000 turns ON when a work is detected during automatic operation.

In the measurement module B2, the contact system instruction describes that the output system instruction is executed when MR001 is turned ON. In this example, the height measurement value acquired by the expansion unit 4 is stored in the device EM0, and it is described that the measured value is copied to the device TM100. Similarly, it is described that the measured value of the depth acquired by the expansion unit 4 is stored in the device EM2, and this is copied to the device TM101. Further, the device MR003 for managing the measurement completion is set to ON.

The determination module B3 is a module that is executed when the device MR003 is turned on, that is, when the measurement is completed. Here, if the measurement result does not satisfy the pass condition, the device MR010 is turned on. This means measurement NG. More specifically, if the measured height stored in the device TM100 is less than 95, MR010 is turned ON. If the measured height stored in the device TM100 exceeds 105, MR010 is turned on. If the measured depth stored in the device TM101 is less than 35, MR010 is turned on. If the measured depth value stored in the device TM100 exceeds 45, MR010 is turned on.

The error processing module B4 is a module for stopping the transfer of the transfer belt when an error occurs. In this example, when MR010 is turned ON (measurement NG), MR012 is turned ON (forced stop), or MR013 is turned ON (transport NG), MR011 is turned ON (convey stop).

As can be seen from FIG. 43, the device described in the contact system instruction of a certain module is described in the output system instruction of another module. On the contrary, the device described in the output system instruction of a certain module is described in the contact system instruction of another module. For example, the device MR001 described in the output system instruction of the work detection module B1 is described in the contact system instruction of the measurement module B2. Therefore, the work detection module B1 and the measurement module B2 are extracted as interconnected modules. Next, paying attention to the device MR003 described in the output system instruction of the measurement module B2, it can be seen that MR003 is described in the contact system instruction of the determination module B3. Therefore, the measurement module B2 and the determination module B3 are extracted as mutually related modules. Next, paying attention to the device MR010 described in the output system instruction of the determination module B3, it can be seen that MR010 is described in the contact system instruction of the error processing module B4. Therefore, the determination module B3 and the error processing module B4 are extracted as mutually related modules. In this way, a plurality of modules involved in a specific process and a plurality of devices described inside the plurality of modules are extracted. These extraction processes are executed by the device extraction unit 53. The device extraction unit 53 may be mounted on the log display unit 61. That is, the log display unit 61 extracts a plurality of modules related to each other, further extracts a plurality of devices described in the extracted plurality of modules, and sets each device value of the extracted plurality of devices. It may be acquired from the log data 73 and displayed on the display unit 7.

FIG. 44 shows the UI 500 that displays the extraction result. The log display unit 61 and the device extraction unit 53 may create a UI 500 for displaying the device and the block (program component) extracted from the user program, and display the UI 500 on the display unit 7. The UI500 can easily display the extraction result of the device and the program component. Therefore, the user will be able to easily grasp the whole picture of the extraction result. When any block included in the UI 500 is clicked by the pointer 101, the log display unit 61 or the device extraction unit 53 may display the details of the clicked block on the UI 501. This will give the user quick access to the details of the extracted blocks. The log display unit 61 and the device extraction unit 53 may display the extraction result using the UI illustrated in FIG. 43.

<Block and device extraction process>
FIG. 45 shows a block and device extraction process executed by the device extraction unit 53. Here, the project data 71 includes a plurality of blocks (program parts). Therefore, the device extraction unit 53 refers to the project data 71 and extracts blocks and devices.

In S81, the CPU 21 (device extraction unit 53) accepts block selection through the operation unit 8. The device extraction unit 53 may accept the designation of the device through the operation unit 8. In this case, the device extraction unit 53 may extract one or more blocks describing the specified device. When a plurality of blocks are extracted, the device extraction unit 53 may accept user selection for one block from the plurality of blocks. Such a device may be, for example, a device that the user pays attention to in debugging. The user sets a condition (example: save trigger) for outputting the log data 73 to the output unit 84 of the PLC1 through the log setting unit 51. More specifically, it is set on the condition that a specific relay device is turned on. Therefore, the device extraction unit 53 may specify the relay device set as the save trigger.

In S82, the CPU 21 (device extraction unit 53) extracts the device described in the contact system instruction of the selected block.

In S83, the CPU 21 (device extraction unit 53) searches the extracted device for other blocks described in the output system instruction.

In S84, the CPU 21 (device extraction unit 53) determines whether or not another block described in the output system instruction has been found in the extracted device. If no other block is found, the CPU 21 ends the extraction process. When another block is found, the CPU 21 proceeds to S85.

In S85, the CPU 21 (device extraction unit 53) extracts the found block as a related block. For example, the device extraction unit 53 registers the identification information (eg, name, file name, etc.) of the found block in the list for managing the related blocks.

In S86, the CPU 21 (device extraction unit 53) selects a related block as the block from which the device is extracted. After that, the CPU 21 returns to S82 in order to execute the extraction process for the newly selected block. The related block selected in S86 is a block that has not yet been selected as a device extraction target. If the device extraction process is completed for all the blocks registered in the list, the device extraction unit 53 ends the extraction process. The CPU 21 (device extraction unit 53) may create a list showing the relationship between the extracted device and the extracted block of the device. The device extraction unit 53 or the log display unit 61 may refer to these lists and create the UI shown in FIG. 43 and the UIs 500 and 501 shown in FIG. 44.

<Specific example of debugging>
FIG. 46 shows the debugging process executed by the user.

In S91, the user sets the NG determination as the storage condition of the log data 73 through the log setting unit 51. According to FIG. 43, it is determined as the storage condition of the log data 73 that the device MR010 that manages the NG determination is turned on. The user transfers the project data 71 and the log setting data 72 to the PLC1.

In S92, the user runs PLC1. The PLC1 executes the project data 71, and saves the log data 73 in the memory card 36 when the storage conditions in the log setting data 72 are satisfied. In the example shown in FIG. 43, when the NG determination occurs, the conveyor belt stops, so that the user knows that some error has occurred.

In S93, the user confirms the work and determines whether the NG determination is a false positive. For example, the user actually measures the height and depth of the work to determine whether or not the passing conditions are satisfied. If the work does not satisfy the pass condition, the user determines that the NG determination is a false positive.

In S94, the user removes the memory card 36 from the PLC 1, connects the memory card 36 to the PC 2, and reproduces the log data 73 stored in the memory card 36. The program display module 321 displays the device value included in the log data 73 in association with the user program. More specifically, the program display module 321 specifies the device MR010 adopted as the storage condition, causes the device extraction unit 53 to execute the block and device extraction process, and the UI shown in FIG. 43 and FIG. 44. UI500 and 501 shown in the above are displayed. Further, the waveform display module 322 displays the device value displayed by the program display module 321 as a waveform. For example, the measured value of the height of the work held in EM0 and the depth of the work held in EM2 are waveformized and displayed on the display unit 7. In addition, the device value of the device MR000 that manages the work detection is also displayed as a waveform. The user observes these waveforms and finds out that the chattering of the work detection sensor is the cause of the false detection. The user operates the editorial unit 311 to prevent chattering, and modifies the work detection module B1 as shown in FIG. 47. According to this modification, when the work is continuously detected by the work detection sensor for 1 second or longer, the device MR001 for starting the measurement is turned on. The user transfers the updated project data 71 to the PLC1, operates the PLC1, and determines whether or not the chattering countermeasure is successful.

By displaying the user program and the waveform of the device value in synchronization in this way, the user can efficiently identify the cause of the false positive and debug the user program to eliminate the cause.

<Summary>
As shown in FIG. 17, the execution unit 80 is an example of a program execution unit that repeatedly executes the user program. The device unit 34 is an example of a device storage unit having a plurality of devices, which is a storage area referred to by the program execution unit. The recording unit 81 is an example of a device recording unit that records device values stored in any of a plurality of devices in time series. The PC 2 is an example of a program creation support device that is connected to a programmable logic controller and supports the creation of a user program.

As shown in FIG. 6, the project creation unit 50 is a plurality of program components constituting the user program based on the user input via the display unit 7, and includes a command word relating to any one of the plurality of devices. This is an example of a program creation unit that creates. The component designation unit 52 is an example of a program component designation unit that specifies a program component from which a specific device to be recorded by the device recording unit is extracted from among a plurality of program components. The device extraction unit 53 is an example of a device extraction unit that analyzes a program component designated by the program component designation unit and extracts the device described in the program component. The recording unit 81 of the basic unit 3 is configured to record the device values stored in the specific device extracted as the recording target by the device extraction unit in chronological order.

By specifying the program component in this way, the user extracts the device from the designated program component. The user can also exclude specific program components from the device extraction target. Therefore, the registration burden on the user of the device to be logged in the PLC is reduced.

The extraction unit 53 may analyze the program component created by the program creation unit 63 and extract the device described in the program component. The component designation unit 52 uses a program component as a unit (program component) in which a program component used or described by a specific device to be recorded by the recording unit 81 among a plurality of program components created by the program creation unit 63. It may be specified (for each). In this case, the recording unit 81 is a device extracted by the extraction unit 53, and the device value stored in a specific device used or described in the program component specified by the component designation unit 52 is timed. Record in series.

The extraction unit 53 may analyze a plurality of program components created by the program creation unit 63 and extract devices used or described for each program component. The component designation unit 52 may specify at least one program component among the plurality of program components created by the program creation unit 63. The recording unit 81 records the device values stored in the device used or described in the program component designated by the component designation unit 52 among the plurality of program components analyzed by the extraction unit 53 in chronological order. For example, a plurality of program components may be analyzed in advance and a plurality of devices may be extracted. That is, a list showing the extracted devices may be created for each program component. Further, when the user specifies one of the program parts, a list of the specified program parts may be read out, and the device on the list may be selected as the recording target.

The component designation unit 52 may be configured to designate at least one program component among a plurality of program components created by the program creation unit 63. The extraction unit 53 may analyze the program component designated by the component designation unit 52 and extract the device used or described for each program component. The recording unit 81 records the device values stored in the specific device extracted by the extraction unit 53 in chronological order. In this way, device extraction may be performed after the program component is specified. This will make the extraction process lighter.

The extraction unit 53 may analyze a plurality of program components created by the program creation unit 63 and extract devices used or described for each program component. The component designation unit 52 may specify at least one program component to be recorded or excluded from the plurality of program components created by the program creation unit 63. The recording unit 81 is a device stored in a specific device used or described in the program component designated as the recording target by the component designation unit 52 among the devices extracted from the plurality of program components by the extraction unit 53. The values may be recorded in chronological order, and devices used for program parts other than the program parts designated as exclusion targets by the part designation unit 52 may be recorded. For example, when the module A uses the device memories DM0 and DM1 and the module B uses the device memories DM1 and DM2, the device memories DM0, DM1 and DM2 are extracted from the modules A and B. Here, when module B is designated as an exclusion target, DM2 is excluded, but DM1 is also used in module A, so DM1 remains as a recording target. In this way, device addition / subtraction may be executed on a program component basis (that is, for each program component). Further, after the devices are extracted from all the program parts, the program parts to be recorded or the program parts to be excluded may be specified.

The component designation unit 52 may be configured to designate a program component from which a specific device is not extracted from a plurality of program components as an exclusion target. The device extraction unit 53 analyzes the program component designated as the device extraction target by the component specification unit 52, extracts the device used or described in the program component, and extracts the device from the program component designated as the exclusion target. It may be configured not to be extracted. That is, the deletion unit 55 and the addition unit 54 delete some specific devices among the specific devices extracted by the device extraction unit for each program component, or the devices that are not extracted by the device extraction unit. It may function as a device addition / subtraction unit added for each program component.

The program component may be, for example, a reusable program module. The plurality of program parts may be stored in individual files. Access privileges (editing privileges) may be set individually for each of the plurality of program components.

The user program may be, for example, a ladder program. In this case, the plurality of program components may be a plurality of function blocks used or described in the ladder program.

The detection unit 82 is an example of a detection unit that detects rewriting of a device value from an external device for any device among a plurality of devices. The recording unit 81 may add a device whose device value rewriting is detected by the detection unit 82 to the recording target.

The PLC 1 may further include a detachable memory card 36 and a specific unit 57 that detects an instruction to the memory card 36 and identifies a device that is the target of the instruction. Although the specific unit 57 is provided on the PC 2 in FIG. 6, it may be mounted on the CPU 31 of the basic unit 3. The recording unit 81 may add the device specified by the specific unit 57 to the recording target.

The expansion unit 4 of the PLC 1 may be a motion unit (positioning unit) having a positioning function. The recording unit 81 or the device extraction unit 53 may add a device used for the positioning function and not described in the user program (eg, a buffer memory in the motion unit) to the recording target.

The estimation unit 59 is an example of an estimation unit that estimates the influence of the recording of the device value by the recording unit 81 on the execution of the user program based on the number of devices extracted as the recording target by the device extraction unit 53. The display unit 7 may be configured to display this effect. This allows the user to add or remove devices while taking into account the effect on scan time.

In FIG. 7, device extraction from the selected program component, device extraction from the selected function, and manual addition of the device by the user are described. However, not all of these are essential. It would be sufficient if two or more of these were adopted. Alternatively, only device extraction from the selected program component may be employed, or only device extraction from the selected function may be employed.

The CPU 31 and the execution unit 80 are examples of a program execution engine that repeatedly executes a user program. The CPU 31, the execution unit 80, and the CPU 41 are examples of a plurality of function execution engines, each of which executes a different function (eg, a function program) related to the user program based on a command from the user program. This suggests that the basic unit 3 may include the functions of the expansion unit 4. The functional program is, for example, a motion control program. The program execution engine and the plurality of function execution engines may be executed by a single CPU, may be executed by a plurality of CPUs, and may be realized by an ASIC or an FPGA. Further, a single CPU may be equipped with multi-cores, and each core may be in charge of a different function.

The device unit 34 is an example of a device storage unit having a plurality of devices which are storage areas referred to by a program execution engine and a plurality of function execution engines. The recording unit 81 is an example of a device recording unit that records device values stored in any of a plurality of devices in time series. The function setting unit 62 may function as an allocation unit for allocating a plurality of devices used in each of the plurality of function execution engines. The function designation unit 60 may function as a designation unit for designating one or more of a plurality of functions corresponding to a plurality of function execution engines. The device extraction unit 53 may extract a device used for one or more functions designated by the designated unit from a plurality of devices allocated by the allocation unit as a recording target of the device recording unit.

The program execution engine may be provided in the main unit. At least one of the plurality of function execution engines may be provided in the function expansion unit electrically connected to the main unit in order to expand the function of the main unit. All of the plurality of function execution engines may be provided in the main unit.

The basic unit 3 is an example of a main unit having a program execution unit, a device storage unit, and a device recording unit. The expansion unit 4 is an example of a function expansion unit that is electrically connected to the main unit in order to expand the function of the main unit.

The function setting unit 62 functions as an allocation unit that allocates a device used for the function of the main unit and a device used for the function of the function expansion unit based on the user input via the display unit 7. do. The function setting unit 62 may display a UI for allocating a device to a function on the display unit 7.

The function designation unit 60 is an example of a designation unit that designates one or more of a plurality of functions including the function provided in the main unit and the function provided in the function expansion unit. The additional unit 54 of the device extraction unit 53 extracts the device used for the function specified by the designated unit as the recording target of the device recording unit. The deletion unit 55 of the device extraction unit 53 excludes the device used for the function specified by the designation unit from the recording target of the device recording unit. The communication unit 23 functions as a transmission unit that transmits setting data for recording the device values stored in the specific device extracted as the recording target in the device recording unit in time series to the PLC1. The recording unit 81 is configured to record the device values stored in the device extracted as the recording target by the device extraction unit 53 in chronological order.

The project creation unit 50 functions as a program creation unit that creates a user program including a command word related to any of a plurality of devices based on user input via the display unit 7. The device extraction unit 53 may analyze the user program, extract the devices used or described in the user program, and create a device list (extraction list) including the extracted devices. Further, the device extraction unit 53 may add the device used for the function designated as the recording target (extraction target) by the function designation unit 60 to the device list. Further, the deletion unit 55 may be configured to delete the device used for the function designated as the exclusion target by the function designation unit 60 from the device list. The device list is included in the log setting data 72. The recording unit 81 is configured to record the device values stored in the devices registered in the device list in chronological order.

The function designation unit 60 may be further configured to designate any one of the main unit and the function expansion unit. That is, a function may be selected or a unit may be selected. When one unit has a plurality of functions, the user selects one function, and all the functions included in the unit are selected as the extraction target of the device. The device extraction unit 53 may extract the device used for the unit designated as the recording target (extraction target) by the function designation unit 60 as the recording target of the device recording unit. Further, the device extraction unit 53 may be configured to exclude the device used for the unit designated as the exclusion target by the function designation unit 60 from the recording target of the device recording unit. In this way, the extraction target and the exclusion target may be specified in units of the main unit and the function expansion unit.

As shown in FIG. 14, the function designation unit 60 may be further configured to specify the device type of the device to be recorded or the device type of the device to be excluded. The device extraction unit 53 extracts a device of the device type designated as a recording target by the function designation unit 60 as a recording target of the device recording unit. The device extraction unit 53 may be configured to exclude the device of the device type designated as the exclusion target by the designation unit from the recording target of the device recording unit.

As described with reference to FIG. 19, the collecting unit 92a collects the device values stored in any of the plurality of devices, and associates the information on the collection time of the device values with the device values. This is an example of the first collection unit stored in the buffer. The device value to be collected may be preset by the log setting data 72. The ring buffer 91a is an example of the first buffer. The information regarding the collection time may be, for example, time information supplied from the time management unit 83a. IF99a and 99f are examples of the first interface for communicating with the expansion unit 4. The communication unit 33 is an example of a first external interface that receives a user program and setting information from an external setting device.

IF99b, 99d, 99h, 99j and the like are examples of a second interface that communicates with the main unit. The image receiving unit 96a and the connection port 97 are an example of a third interface (two-dimensional data receiving unit) that is connected to a monitoring device that acquires two-dimensional data and receives the two-dimensional data from the monitoring device. The connection port 97 may function as a second external interface that is connected to the monitoring device and data is input from the monitoring device. The camera 98 is an example of a surveillance device. The monitoring device may be a barcode reader. In this case, the barcode reading result is an example of two-dimensional data. The monitoring device may be an image processing device that generates a height image or a distance image of the work. Height images and distance images are examples of two-dimensional data. The two-dimensional data may be moving image data. In addition, a large amount of data whose size is large compared to the device value is also an example of two-dimensional data. For example, the numerical data acquired by the high-speed analog input unit is also an example of two-dimensional data. The function execution unit 96 may function as a function execution unit that executes a function that involves inputting data from the monitoring device via the second external interface based on the received setting information.

The collection unit 92b collects the two-dimensional data received via the third interface, associates the information on the acquisition time when the two-dimensional data was acquired with the two-dimensional data, and stores the two-dimensional data in the second buffer. This is an example. The time information provided by the time management unit 83 is an example of information related to the acquisition time. The ring buffer 91b is an example of a second buffer.

When the predetermined storage condition is satisfied, the storage unit 93 stores the device value stored in the first buffer and the information regarding the collection time, and the two-dimensional data stored in the second buffer and the information regarding the acquisition time. This is an example of a storage unit.

In this way, information about the acquisition time is associated with the device value and the two-dimensional data, respectively. Therefore, it becomes easy to identify the temporal relationship between a relatively large amount of data such as two-dimensional data and a device value.

The monitoring device may be a camera that acquires image data of a still image or a moving image. The function execution unit 96 executes a function involving input of image data from the camera 98. The collection unit 92b, which is the second collection unit, stores the information regarding the acquisition time when the image data is acquired and the image data in the second buffer in association with each other. The storage unit 93 may store the device value, the information regarding the collection time, the image data stored in the second buffer, and the information regarding the acquisition time in association with each other. The function execution unit 96 may execute a function that involves inputting data from the monitoring device, asynchronously with the execution cycle of the user program. The storage unit 93 may also store the project data including the user program and the setting information. The storage unit 93 stores the information on the device value and the collection time, the data stored in the second buffer, and the information on the acquisition time in a plurality of files identified by the common flag, and stores the plurality of files. You may save it.

The information regarding the collection time may be any information that can specify the collection time for each of the plurality of device values collected in the time series. The collection time may be associated with each of the plurality of device values. Alternatively, for example, the collection time may be associated only for the first device value. In the latter case, the collection time for device values other than the first device value may be calculated based on other information (scan count, scan time, etc.). Since the device values are recorded in the same number as the number of scans, the collection time of any device value can be specified by storing the processing time (scan time) in each scan. For example, when trying to specify the collection time of the device value recorded in the 100th scan, the collection time of the device value recorded in the first scan is 10:10:00, and the 2nd to 100th times. It is assumed that each scan took 100 microseconds. In this case, the time when 100 microseconds × 99 has elapsed from 10:10:00 is calculated as the collection time of the device value recorded in the 100th scan. In this way, it is not essential to record the collection time in association with all device values.

The information regarding the acquisition time may be any information for specifying the acquisition time for each of the plurality of two-dimensional data acquired in the time series. The acquisition time may be associated with each of the plurality of two-dimensional data. Alternatively, for example, the acquisition time may be associated only with the first two-dimensional data. In the latter case, the acquisition time for two-dimensional data other than the first two-dimensional data can be calculated based on other information (number of imaging times, imaging cycle, etc.). Specifically, the acquisition time can be associated only with the first two-dimensional data among the plurality of two-dimensional data. The cycle for acquiring two-dimensional data (imaging cycle) is almost constant. Therefore, the acquisition time of arbitrary two-dimensional data can be specified. For example, when trying to specify the acquisition time of the image data recorded in the 10th imaging, the acquisition time of the image data recorded in the 1st imaging is 10:10:00, and the 2nd to 10th times. It is assumed that each imaging took 100 milliseconds. In this case, the acquisition time of the image data recorded in the 10th imaging is the time when 100 milliseconds × 9 has elapsed from 10:10:00. In this way, it is not essential to record the acquisition time in association with all the two-dimensional data.

The storage unit 93 may include a memory card 36 that can be attached to and detached from the main unit. The storage unit 93 may store the device value and the collection time information stored in the first buffer and the two-dimensional data and the acquisition time information stored in the second buffer in the memory card 36. This makes it easier to transfer the log data 73 to the PC2. As shown in FIG. 19, the first buffer may be provided in the main unit. As shown in FIG. 20, the second buffer may be provided in the expansion unit.

As shown in FIG. 24, the first interface is a side surface of the main unit and may be arranged on a side surface facing the side surface of the expansion unit. The second interface may be provided on the side surface of the expansion unit so as to be connected to the first interface.

As shown in FIG. 25, the backplane 200 is an example of a support plate that supports the main unit and the expansion unit. In this case, at least one of the first buffer, the second buffer and the storage unit may be provided on the support plate.

The transmission unit 94 is an example of a transmission unit that transmits the device value, the information regarding the collection time, the two-dimensional data, and the information regarding the acquisition time stored in the storage device 32 to the external device. The external device may be a cloud or a PC2. The PC 2 may receive the log data 73 in real time and display the log data 73 on the display unit 7.

The first buffer or the second buffer may be configured to further store information generated in a cycle shorter than the execution cycle of the user program (eg, scan cycle).

The storage unit 93 may be configured to read and store the two-dimensional data and the information related to the acquisition time from the second buffer during the period in which the end processing (END processing) related to the user program is being executed in the main unit. ..

As described with respect to the time management units 83a and 83b, the clock of the main unit that clocks the collection time and the clock of the expansion unit that clocks the acquisition time are synchronized. This synchronization may be achieved, for example, by inter-unit synchronization.

As shown in FIG. 29, the storage unit 93 stores device values, information on collection time, two-dimensional data, and information on acquisition time collected at a predetermined collection time before and after a preset storage trigger on the memory card 36. It may be configured to be stored in.

As shown in FIG. 30, the storage unit 93 collects device values, information on the collection time, two-dimensional data, and acquisition at a predetermined collection time starting from the timing when the preset start relay is turned on. Information about the time may be stored in the memory card 36.

As described in connection with FIG. 32, when a predetermined storage condition is satisfied, the storage unit 93 sets the device value recorded in the device recording unit and the user program or user program stored in the program storage unit. It may be stored in a memory (eg, a memory card 36 or an internal memory 37) in association with the identification information of. Further, when a predetermined output condition is satisfied, the output unit 84 stores the device value recorded in the device recording unit and the user program stored in the program storage unit or the identification information of the user program in an external memory (eg,). : May be output to the memory card 36). As described above, it is important which project data 71 was used to acquire the log data 73. Therefore, the output unit 84 outputs the project data 71 itself used for acquiring the log data 73 or the identification information thereof. That is, by outputting the log data 73 and the project data 71 or its identification information, it becomes easy to identify the relationship between the log data 73 and the project data 71. As a result, the user can efficiently debug the project data 71.

The user program is composed of a plurality of program components. In addition, the project data manages a plurality of program parts. The storage device 32 functions as a program storage unit that stores the user program as a part of the project data 71. The output unit 84 may be configured to output the project data 71 including the user program and to output the identification information of the project data 71 as the identification information of the user program. This makes it easier to determine whether the project data 71 (master data) stored in the PC 2 and the project data 71 stored in the PLC 1 match.

The project data 71 may include the setting information of the expansion unit 4. This is because the setting information of the expansion unit 4 may be required when debugging the project data 71. For example, when a plurality of expansion units 4 are connected to the basic unit 3, the connection order of the plurality of expansion units 4 is included in the setting information of the expansion unit 4. Information about this connection order may be needed when debugging.

The determination unit 301 functions as a determination unit for determining whether or not the output of the user program (project data 71) is prohibited. When the determination unit 301 determines that the output of the user program is prohibited, the output unit 84 uses the device value recorded in the device recording unit and the identification information of the user program stored in the program storage unit. May be output to an external memory. As a result, the master data of the PC2 can be used based on the identification information while protecting the user program.

As described in connection with the appendix 312, the user program identification information is the identification information that is updated when the user program is changed. Therefore, the project data 71 of another version different from the project data 71 held in the PLC1 will not be mistakenly used for debugging.

As described in connection with the calculation unit 313, the identification information of the user program may be an error detection code or a hash value calculated from the user program. In this way, when the project data 71 is updated, the identification information calculation method may be adopted so that the identification information is also updated. The identification information may be a time stamp or the like.

The storage device 22 of the PC 2 is an example of a program memory that stores the user program and the identification information of the user program. The collation unit 334 is an example of a collation unit that collates the user program identification information output from the programmable logic controller with the user program identification information stored in the program memory and displays the collation result on the display unit. The warning unit 335 outputs a warning when the two do not match, but if the two match, a message or an image indicating that they match may be displayed on the display unit 7.

As shown in FIG. 38, the display unit 7 may display the device value output from the programmable logic controller in association with the portion of the user program in which the instruction word related to the device value is described. This makes it easier for the user to understand the relationship between changes in device values and user programs. This will improve the efficiency of debugging.

The storage device 22 and the memory card 36 are examples of storage means for storing a plurality of time-series device values collected by the programmable logic controller and time data indicating the collection time of each device value. The program display module 321 is an example of a first engineering software module that displays device values on a ladder diagram. The waveform display module 322 is an example of a second engineering software module that displays device values as a time-series waveform. The reproduction control module 324 is an example of a synchronization software module that synchronizes the display target time in the first engineering software module and the display target time in the second engineering software module. This will make it easier for the user to understand the relationship between changes in a particular device value and the program.

The first engineering software module acquires the device value from the programmable logic controller in the real-time playback mode, displays the device value on the ladder diagram, and saves the device value corresponding to the display target time based on the time data in the history playback mode. The first display control means which is acquired from the means and displayed on the ladder diagram may be provided. The program display unit 332, the display time control unit 331, and the device value acquisition unit 333 function as the first display control means. The log playback mode is an example of the history playback mode.

The second engineering software module acquires the device value from the programmable logic controller in the real-time reproduction mode and displays the time-series waveform, and acquires the device value corresponding to the display target time based on the time data in the history reproduction mode from the storage means. The second display control means for displaying the time series waveform may be provided. The waveform display unit 336, the display time control unit 331, and the device value acquisition unit 333 are examples of the second display control means.

The synchronization software module may have a synchronization means for synchronizing the display target time in the first engineering software module and the display target time in the second engineering software module in the history reproduction mode. The reproduction control unit 343 is an example of the synchronization means.

The first engineering software module may further have a first update means for updating the display target time in the history reproduction mode. The time designation cursor 404, the time UI 330, and the display time control unit 331 are examples of the first update means. The reproduction control unit 343, which is a synchronization means, reflects the display target time updated by the first update means in the display target time of the second engineering software module.

The second engineering software module may further have a second update means for updating the display target time in the history reproduction mode. The bar 103, the time UI 330, and the display time control unit 331 are examples of the second update means. The reproduction control unit 343, which is a synchronization means, reflects the display target time updated by the second update means in the display target time of the first engineering software module.

As shown in FIG. 43, the first display control means searches the ladder diagram for a command word related to the device to be displayed in the second engineering software module among the plurality of devices referred to in the programmable logic controller. You may. For example, the device may be specified by designating the device shown in FIG. 28 (eg, R000, DM100, etc.) with the pointer 101. As shown in FIG. 38, the first display control means may be configured to display the device value of the device together with the instruction word found in the ladder diagram. Further, the pointer 101 is an example of a designation means for designating an arbitrary device. The first display control means searches the ladder diagram for a command word related to the device designated by the designated means among the plurality of devices referred to in the programmable logic controller, and together with the command word found in the ladder diagram, of the device. The device value may be displayed.

As shown in FIG. 43, in the programmable logic controller, the ladder program may be composed of a plurality of program components. The first display control means (eg, log display unit 61 or device extraction unit 53) searches for one or more blocks including instruction words related to the device from a plurality of program components, and finds the found blocks in a ladder diagram. It may be configured to be displayed as.

As shown in FIG. 43, when the first display control means finds a plurality of blocks including the instruction word related to the device, the ladder diagram corresponding to the plurality of blocks may be displayed side by side.

As shown in FIG. 43, in the ladder program, the instruction word related to the first device (example: MR001) in the first block (example: measurement module B2) is an input system instruction word. In this case, the second device (example: MR003) that is the target of the output system command word described corresponding to the input system command word is specified, and the input system that targets the second device is specified. The second block (eg, determination module B3) in which the command word of is described may be specified.

In the ladder program, when the instruction word related to the first device (example: MR010) in the first block (example: determination module B3) is the instruction word of the output system, the first display control means of the output system. The second device (example: MR001) that is the target of the input system command word described corresponding to the command word is specified, and the output system command word that targets the second device is described. A second block (eg, measurement module B2) may be specified.

The synchronization means may have a setting means for setting the update speed of the display target time. The speed designation unit 405 is an example of the setting means. As a result, slow playback, fast forward playback, and the like may be realized.

Even if the first display control means and the second display control means are configured to further display device values set based on user input input from a human interface (HMI) that displays information about the programmable logic controller. good. HMI may be implemented by an emulator. As described in connection with FIG. 39, the UI 490 displays a plurality of device values. When any device value is clicked by the pointer 101, the log display unit 61 adds the clicked device value as a display target of the program display unit 332 or as a display target of the waveform display unit 336. May be good. This makes it possible to display waveforms of HMI, user programs, and device values in a coordinated and synchronized manner.

The storage means may further store a plurality of time-series image data acquired from the camera unit and time data indicating the acquisition time of each image data. As shown in FIG. 28, the second engineering software module may acquire the device value from the programmable logic controller and display the time series waveform in the real-time reproduction mode, and may display the image data acquired from the camera unit. Similarly, the second engineering software module may acquire and display the device value and the image data corresponding to the display target time from the storage means in the history reproduction mode. Image data has more information than numerical values. Therefore, by displaying the image data, the user will be able to find the problem at an early stage.

Further, the first engineering software module may acquire the device value from the programmable logic controller in the real-time reproduction mode, display the device value on the ladder diagram, and display the image data acquired from the camera unit. The first engineering software module may acquire the device value and the image data corresponding to the display target time from the storage means in the history reproduction mode and display them on the ladder diagram.

The plurality of expansion units 4 operate according to different internal control cycles. Therefore, the acquisition time of the device value acquired from the plurality of expansion units 4 and the acquisition time of the image data often do not match. Therefore, as described in connection with FIGS. 26 to 28, the first display control means and the second display control means are device values associated with the time data closest to the display target time in the history reproduction mode. May be configured to read.

Claims (22)

An interface that accepts log setting information, a program execution unit that repeatedly executes a ladder program, a device storage unit that has a plurality of devices that are storage areas referenced by the program execution unit , and a collection specified by the log setting information. for each cycle, have a recording section which records in association with information about the collection time a plurality of device values stored in the device memory unit, the condition specified in the log setting information is satisfied recorded It is connected to a programmable logic controller that reads out the information about the plurality of device values and the associated collection time from the unit and outputs it as log data.
An external setting device that displays the plurality of device values using the log data output by the programmable logic controller.
A transmitter that transmits the log setting information to the programmable logic controller, which specifies one scan of the ladder program as the collection cycle and specifies the timing determined by the state change of the specific device and the specific device as the condition. When,
A memory for storing the ladder program and the log data, and
The ladder program stored in the memory is displayed, and a plurality of device values are acquired from the log data stored in the memory based on the information regarding the collection time and displayed on the ladder program as the device value at a specific time. Log display and
With
When the log display unit receives a display update instruction via the first button, the log display unit advances the specific time according to the passage of time and is displayed on the ladder program based on the specific time and the collection time. An external setting device that is a device value and is characterized in that the device value corresponding to the specific time is repeatedly updated. The external setting device according to claim 1, wherein the log display unit displays a device value whose collection time is close to the specific time on the ladder program. When the log display unit further receives a display update instruction via the second button, the log display unit collects the device value displayed on the ladder program at the collection time one step next to the collection time corresponding to the specific time. The external setting device according to claim 1 or 2, wherein the device value is updated to the value of the device. The external setting device according to claim 3, wherein the log display unit displays a collection time of a device value displayed on the ladder program. The external setting device according to claim 3 or 4, wherein the log display unit displays the first button and the second button side by side below a program display area for displaying the ladder program. When the device value displayed on the ladder program is repeatedly updated, the log display unit displays the device value of a part of the collection times of the plurality of time-series collection times on the ladder program. The external setting device according to any one of claims 1 to 5, characterized in that. When the log display unit further receives a display update instruction via the third button, the log display unit collects the device value displayed on the ladder program at the collection time one step before the collection time corresponding to the specific time. The external setting device according to any one of claims 1 to 6, wherein the device value is updated to the value of the device. When the log display unit displays the collection time corresponding to the specific time and receives the display update instruction via the first button, the specific time corresponds to the passage of time after receiving the display update instruction. The external setting device according to any one of claims 1 to 7, wherein the display of the collection time corresponding to the above is repeatedly updated. When the log display unit displays the number of scans corresponding to the specific time and receives a display update instruction via the first button, the log display unit receives the display update instruction, and the specific time corresponds to the lapse of time after receiving the display update instruction. The external setting device according to any one of claims 1 to 8, wherein the display of the number of scans corresponding to the above is repeatedly updated. The log display unit can receive a time designation instruction by a user, and any one of claims 1 to 9 is characterized in that it displays a first time designation cursor that moves according to the specific time. Described external setting device. The external setting device according to claim 10, wherein the log display unit adjusts the specific time according to the drag amount of the drag operation when the drag operation of the first time designation cursor is received. When the log display unit receives a drag operation of the first time designation cursor when the specific time is updated at a predetermined update speed by a display update instruction via the first button, the log display unit receives the drag operation of the specific time. The external setting device according to claim 11, wherein the update of the display of the device value corresponding to the specific time is stopped by stopping the update. The log display unit further includes a waveform display unit that displays a time-series waveform of device values acquired from log data stored in the memory based on information regarding the collection time.
When the waveform display unit receives the display update instruction via the first button, the waveform display unit sets the display range of the time-series waveform of the device value along the time axis direction according to the passage of time after receiving the display update instruction. The external setting device according to any one of claims 10 to 12, wherein the external setting device is moved. The waveform display unit displays a second time designation cursor for designating a time in the time series waveform of the device value overlaid on the time series waveform.
The external setting device according to claim 13, wherein the time specified by the second time designation cursor and the collection time corresponding to the specific time are configured to be the same. The waveform display unit can accept a time designation instruction by a user, and displays the first time designation cursor that moves according to the specific time.
The external setting device according to claim 14, wherein when the drag operation of the second time designation cursor is accepted, the first time designation cursor is moved according to the drag amount of the drag operation. The recording unit records a plurality of device values stored in the device storage unit as one record in association with information regarding the collection time.
The log display unit is characterized in that the display is repeatedly updated so that the device value associated with the collection time in the record and the information related to the collection time close to the specific time is displayed on the ladder program. The external setting device according to any one of claims 1 to 15. The log display unit has an internal clock that keeps time.
The external setting device according to any one of claims 1 to 16, wherein the specific time is advanced according to the internal clock. When the condition specified in the log setting information is satisfied, the programmable logic controller reads out the information on the plurality of device values for the target period and the associated collection time from the recording unit and outputs the log data.
The external setting device according to any one of claims 1 to 17, wherein the log setting information includes designation of the target period based on the timing. The external setting device according to claim 18, wherein the target period includes a predetermined period prior to the timing. The external setting device is
A log setting unit for creating the log setting information in which a specific device and a timing determined by a state change of the specific device are specified as the condition based on a user operation is provided.
The claim is characterized in that the transmission unit includes the designation of one scan of the ladder program as the collection cycle, and transmits the log setting information created by the log setting unit to the programmable logic controller. The external setting device according to any one of 1 to 19. The external setting device is
Equipped with a program creation unit that creates a ladder program based on user operations
The external setting according to any one of claims 1 to 20, wherein the transmission unit transmits the log setting information to the programmable logic controller together with a ladder program created by the program creation unit. device. An interface that accepts log setting information, a program execution unit that repeatedly executes a ladder program, a device storage unit that has a plurality of devices that are storage areas referred to by the program execution unit , and a collection specified by the log setting information. for each cycle, have a recording section which records in association with information about the collection time a plurality of device values stored in the device memory unit, the condition specified in the log setting information is satisfied recorded It is connected to a programmable logic controller that reads out the information about the plurality of device values and the associated collection time from the unit and outputs it as log data.
A program executed in a computer that displays the plurality of device values using the log data output by the programmable logic controller.
A transmission step of transmitting the log setting information to the programmable logic controller, which specifies one scan of the ladder program as the collection cycle and specifies the timing determined by the state change of the specific device and the specific device as the condition. When,
While displaying the ladder program stored in the memory of the computer, a plurality of device values are acquired from the log data stored in the memory based on the information regarding the collection time, and the device values at the specific time are displayed on the ladder program. Let the computer execute the log display process to be displayed in
The log display process is
When the display update instruction via the first button is received, the specific time is advanced according to the passage of time, and the device value displayed on the ladder program based on the specific time and the collection time is described above. A program characterized by repeatedly updating the device value corresponding to a specific time.

Images