WO2013128603A1 - Programmable controller, programmable controller system, and provision system for programmable controller - Google Patents

Abstract

A programmable controller having an application management means that: adds up the execution periods of a program; counts the number of times that the added-up value obtained by adding up exceeds a prescribed fixed time value; finds the cumulative execution time of the program on the basis of the count value; and prevents the execution of the program if the cumulative execution time exceeds a pre-set evaluation period.

Description

Programmable controller, programmable controller system, and system for providing programmable controller

The present invention relates to a programmable controller that controls an external device, a programmable controller system, and a system for providing a programmable controller.

The programmable controller executes a predetermined application and controls external devices and the like. The application is preprogrammed by the user using a programming device and downloaded to the programmable controller. Programmable controllers have been commercialized by various manufacturers, but controller performance, ease of use of application development tools, and the like vary from manufacturer to manufacturer, and there is a desire to determine the adoption after actually using it.

In order to meet such demands, controller manufacturers may provide actual programmable controller devices and application development tools as evaluation machines (trial versions) for the purpose of allowing users to evaluate programmable controllers. In such a case, the user evaluates the evaluator and purchases it regularly based on the evaluation result.

However, the provided evaluator is indistinguishable from a regular product and does not have any usage restrictions. Therefore, some users have a problem that a system is constructed using an evaluation machine, and the constructed system is directly delivered to the end user, so that the controller manufacturer cannot collect sales. Therefore, conventionally, for example, the evaluation period of the programmable controller (evaluator) is grasped by comparing the evaluation start time with the current date and time, and measures are taken so that the programmable controller is not activated after the period expires. Conventionally, there is a method of monitoring the execution time usage of the demo evaluation software, and when the elapsed execution time exceeds the predetermined evaluation time, the demo evaluation software cannot be executed until registered by the user. It is known (see, for example, Patent Document 1).

Japanese Patent Laid-Open No. 2001-1000085

However, with the conventional method of grasping the evaluation period by comparing the conventional evaluation start time with the current date and time, the operation of the calendar IC (Integrated Circuit) is stopped unless the battery is backed up when the programmable controller is turned off. And I don't know the exact date and time. Therefore, the above-described method has a problem that the evaluation period cannot be accurately grasped.

Also, unlike a PC (Personal Computer) equipped with an interactive application, a programmable controller is required to be continuously operated after the system is started up. For example, when a programmable controller is applied to a predetermined production line, it is not uncommon to perform continuous operation for 24 hours or more. Therefore, if the programmable controller is stopped immediately after the evaluation period expires as in the conventional method, an unexpected accident or the like may be induced.

The present invention has been made in view of the above points, and an object thereof is to provide a programmable controller, a programmable controller system, and a programmable controller providing system that appropriately control the use of the programmable controller for an evaluation period or the like. .

In order to solve the above problems, the present invention, in a programmable controller, integrates the program execution cycle, counts when the integrated value obtained by the integration exceeds a predetermined fixed time value, and based on the count value, Find the cumulative execution time of a program. The present invention further includes application management means for preventing the execution of the program when the obtained accumulated execution time exceeds a preset evaluation period.

In addition, what applied the arbitrary combination of the component of this invention, the expression, or the component to a method, an apparatus, a system, a computer program, a recording medium, a data structure, etc. is effective as an aspect of this invention.

According to the present invention, it is possible to appropriately control the use of the programmable controller.

It is a figure which shows an example of schematic structure of the provision system in this embodiment. It is a figure which shows an example of the function structure of PLC in this embodiment. It is a figure which shows an example of the hardware constitutions of PLC in this embodiment. It is a figure which shows an example of a function structure of a user terminal. It is a figure which shows an example of a function structure of a provider terminal. It is a figure which shows an example of the hardware constitutions of the user terminal and provider terminal in this embodiment. It is a figure for demonstrating the execution period example of the program in PLC. It is a flowchart for demonstrating the 1st Example of determination of an evaluation period, and execution control. It is a flowchart for demonstrating 2nd Example of determination of an evaluation period, and execution control. FIG. 10 is a diagram illustrating an example of flag writing corresponding to FIG. 9. It is a flowchart for demonstrating the 3rd Example of determination and execution control of an evaluation period. FIG. 12 is a diagram illustrating an example of flag writing corresponding to FIG. 11. It is a flowchart which shows an example of the notification process with respect to 3rd Example. It is a flowchart which shows an example of the process sequence in a user terminal. It is a flowchart which shows an example of the process sequence in a provider terminal.

<About the present invention>
For example, the present invention relates to the use of a programmable controller, for example, by accumulating the execution period of a program, counting when the integrated value obtained by the integration exceeds a predetermined fixed time value, and calculating the accumulated execution time of the program based on the counted value. The execution of the program is blocked when the accumulated execution time exceeds a preset evaluation period. The accumulated information of the execution time of the application (program) executed by the controller is stored, for example, in a memory (storage means), thereby solving the problem of time recording by the calendar IC or the like.

In the present invention, a flag is written in a predetermined data area every time the integrated value exceeds a fixed time, and the above-described accumulated execution time may be calculated based on the number of written flags. Further, the present invention performs control so that the programmable controller is not activated at an appropriate timing after the evaluation period has expired. For example, if the program is executed for the evaluation period or more by the determination of the number of flags described above, execution of the next program is blocked.

In the present invention, when the execution integration time exceeds the threshold, the user may be notified of the expiration of the evaluation period using, for example, a light emitting unit or a voice output unit provided in the programmable controller main body. In addition, as a light emission part, although there exists LED (Light Emitting Diode) etc., for example, it is not limited to this, Other light emitting elements may be sufficient. Moreover, as an audio | voice output part, although there exist a speaker etc., for example, it is not limited to this. Moreover, the light emission part and audio | voice output part which were mentioned above may be provided integrally in the programmable controller. In addition, the light emitting unit and the audio output unit are provided separately from the evaluation controller, and may be connected by an output terminal such as a USB (Universal Serial Bus) terminal or a speaker terminal, for example.

In the present invention, when the execution integration time is up, the support tool on the user terminal connected to the programmable controller may be notified of the expiration of the evaluation period. For example, the RAS information notification area provided in the memory area for the application can be notified of the expiration of the evaluation period to notify the user. The RAS information is information indicating the reliability (Reliability), availability (Availability), and maintainability (Serviceability) of the computer system. Note that when the above-described evaluation period expiration notification is made, the programmable controller that is the target module (target device) may be notified that there is a minor failure.

Hereinafter, embodiments in which a programmable controller, a programmable controller system, and a providing system according to the present invention are suitably implemented will be described with reference to the drawings. In the following description, a programmable logic controller (PLC) is used as an example of a programmable controller. However, the present invention is not limited to this.

<Schematic configuration example of a programmable controller providing system>
FIG. 1 is a diagram illustrating an example of a schematic configuration of a programmable controller providing system according to the present embodiment. The providing system 10 shown in FIG. 1 includes PLCs 11-1 to 11-3 (hereinafter collectively referred to as “PLC11” as necessary), a user terminal 12, and input / output modules 13-1 to 13-n (hereinafter referred to as “PLC11”). And collectively referred to as “I / O module 13” as necessary. Here, the providing system 10 shown in FIG. 1 has three PLCs 11-1 to 11-3 and a plurality of I / O modules 13-1 to 13-n as an example. Is not limited to the above.

The user terminal 12 and the PLC 11-1 are connected by, for example, a communication cable 14 or the like, and the PLCs 11-1 to 11-3 and the I / O modules 13-1 to 13-n are respectively used for control. Connected by a network 15.

Further, the providing system 10 shown in FIG. 1 includes a provider terminal 16 that provides the PLC 11, and the user terminal 12 and the provider terminal 16 can transmit and receive data via a communication network 17 typified by the Internet, for example. Connected as possible. One or more PLCs 11 (in the example of FIG. 1, PLCs 11-1 to 11-3) and one or more I / O modules 13 (in the example of FIG. 1, I / O modules 13-1 to 13- n) functions as the programmable controller system 18. Each of the plurality of PLCs 11 and the plurality of I / O modules 13 can be positioned as one node (station).

The PLC 11 executes predetermined processing using the I / O module 13 or the like that is the target device based on instructions from the user terminal 12 equipped with various support tools, and analyzes and controls execution results. A programmable controller to perform. That is, the PLC 11 is a support target device in the user terminal 12. Note that the PLC 11 uses, for example, a CPU (Central Processing Unit) module that performs application calculation or the like, but is not limited thereto.

In this embodiment, the PLCs 11-1 to 11-3 including the CPU modules and the like are connected to the I / O modules 13-1 to 13-n via, for example, the ring network 15 at a predetermined cycle. Exchange data. At this time, the PLCs 11-1 to 11-3 and the I / O modules 13-1 to 13-n start applications and the like in synchronization with, for example, a network communication cycle (for example, every 1 ms).

That is, the topology of the control network 15 is a ring type in which the PLCs 11-1 to 11-3 and the I / O modules 13-1 to 13-n in the programmable controller system 18 are daisy chain connected. The PLC 11 exchanges data among the I / O modules 13-1 to 13-n by circulating data frames in this ring topology at a predetermined cycle.

For example, in the above-described programmable controller system 18, the data frame transmitted by the PLC 11-1 is PLC 11-2 → PLC 11-3 → I / O module 13-1 → I / O module 13-2 → I / O module 13−. It is transmitted to n and transmitted sequentially like a bucket relay. Then, the data frame transmitted to the I / O module 13-n is turned back, and returns to the PLC 11-1 along the reverse route. The data frame that has returned through the network 15 in this manner is deleted at the source transmission source (in this case, the PLC 11-1). In this way, the PLC 11 on the ring transmits and receives data, and the I / O module 13 performs predetermined data processing based on the transmitted and received data.

The PLC 11 uses the network 15 to exchange not only input / output data, but also exchanges application data between other PLCs and controls the entire system such as system start / stop / reset. By transmitting these data on the ring, the system updates the data while synchronizing the timing.

In this embodiment, in order to output the expiration of the evaluation period (sample period) when the PLC 11 is given to the user as an evaluation (sample product), the operation of the application started in synchronization with the network communication cycle is output. Accumulate time. Specifically, for example, the evaluation period is determined by integrating the operating time of the application executed in synchronization with the exchange period of data circulating around the ring-shaped network 15 described above (program execution period).

Thereby, the evaluation period of each PLC 11 on the network 15 can be appropriately monitored in correspondence with the execution cycle of the program executed in synchronization with the data exchange cycle described above. Note that the method for acquiring the program execution cycle in the present embodiment is not limited to this.

In this embodiment, when the accumulated time exceeds a predetermined time, the evaluation period expires, for example, a process such as notifying the user and preventing the execution of the program is performed.

In other words, in the present embodiment, it is determined whether or not the PLC 11 can be used based on a preset condition for stopping the PLC 11, and when the PLC 11 cannot be used, for example, control is performed to prevent execution of the program. In addition, in this embodiment, it is not limited to this, For example, you may control use of PLC11 by control, such as power ON / OFF, a reset, stop / start. Further, in the present embodiment, when the providing system 10 is in operation, the PLC 11 may be provided with an interface that displays failure information or the like and prompts the user to take some measures when the PLC 11 cannot be used. .

Here, the user terminal 12 stores therein a support tool that supports execution of the PLC 11 and the like. The user terminal 12 executes a preset support tool according to a user instruction, and causes the PLC 11 or the like to execute a predetermined process. The above-described support tool may acquire support tools corresponding to the PLCs 11-1 to 11-3 from the provider terminal 16 through the communication network 17.

Here, the user terminal 12 can be a general general-purpose computer. Further, when the user terminal 12 receives a notification from the PLC 11 that a preset evaluation period has elapsed, the user terminal 12 can perform a process of displaying a message to that effect on the screen and notifying the user. Further, when the user terminal 12 regularly purchases or rents the PLC 11, the user terminal 12 transmits a notification to that effect to the provider terminal 16 and identification information (for example, MAC address) of the PLC 11. Further, the user terminal 12 transmits key information of the user terminal 12 set in advance to the provider terminal 16 when encryption is necessary when acquiring information from the provider terminal 16.

Further, the user terminal 12 acquires command information for regular purchase, command information for rental, etc. from the provider terminal 16 and executes each acquired command information on the target PLC 11 so that the evaluation period has elapsed. After that, the PLC 11 can be used as it is. In addition, it is preferable that each command information etc. which the user terminal 12 acquires from the provider terminal 16 are encrypted based on the key information mentioned above. As described above, the command is encrypted and transmitted in order to prevent the transmitted data from being stolen and diverted to other PLCs 11 and also to conceal the data content itself.

The user terminal 12 purchases the PLC 11 as a regular version by decrypting the encrypted command information obtained by the provider terminal 16 with its own key information and causing the predetermined PLC 11 to execute the obtained command. It can be used or rented for a predetermined time. The above-described command is preferably a command specific to each of the PLCs 11-1 to 11-3. By using a unique command for each PLC 11, control of individual devices can be performed. As the unique command, for example, a command including identification information of the PLC 11 such as a MAC address can be used. As a result, each PLC 11 that has acquired the command for circulating on the network 15 compares its own MAC address with the MAC address in the command, and executes the command if they are the same. Thereby, the change (rewriting etc.) of the mode information from the evaluation version of PLC11 to a regular version or a rental version can be performed individually.

The above-described command may be a shared command corresponding to a plurality of PLCs among the PLCs 11-1 to 11-3. Thereby, it is possible to efficiently control a plurality of devices with one command.

The I / O module 13 performs data input / output processing with other modules. For example, based on an instruction from the PLC 11, the I / O module 13 outputs (transmits), for example, data obtained from the connected device or the like to the PLC 11, or outputs a result processed by the PLC 11 to the connected device or the like. Or remember.

The provider terminal 16 generates a unique command that permits the use of each PLC 11 based on the information acquired from the user terminal 12 through the communication network so that the target PLC 11 can be used. The information acquired from the user terminal 12 includes, for example, a request notification as to whether the PLC 11 is properly purchased or used for rental, identification information (for example, a MAC address) of the target PLC 11, and the like. Further, when encryption is necessary, key information of the user terminal 12 set in advance is acquired.

The provider terminal 16 encrypts the generated command based on the key information obtained from the user terminal 12, and sends the encrypted information to the user terminal 12 via the communication network 17. Can be sent.

In the providing system 10 described above, the user terminal 12 and the provider terminal 16 may not be connected via the communication network 17 or the like. In such a case, the user terminal 12 sends a purchase request or key information for the PLC 11 to the provider terminal 16 by mail or the like. Further, the user terminal 12 receives a recording medium (for example, a CD-ROM) in which encrypted information including a unique command permitting use of the PLC 11 is recorded from the provider terminal 16 by mail, and stores the recording medium. The target information is acquired by reading the information.

<Example of functional configuration in PLC 11>
Next, a functional configuration example of the PLC 11 in the present embodiment will be described with reference to the drawings. FIG. 2 is a diagram illustrating an example of a functional configuration of the PLC according to the present embodiment. The PLC 11 shown in FIG. 2 includes a communication interface unit 21, a command providing unit 22, a storage management unit 23, an application management unit 24, a system management unit 25, a switch (SW) monitoring unit 26, a calendar IC (date and time). Acquisition means) 27, input / output (I / O) control means 28, and notification means 29.

The communication interface unit 21 transmits and receives data to and from the user terminal 12 connected to the communication cable 14, other PLC 11, I / O module 13, external device connected to the I / O module 13, and the like. It is a communication means. The communication interface means 21 includes identification information such as a MAC address. The communication interface means 21 includes a serial interface such as USB (Universal Serial Bus), an interface connectable with a LAN (Local Area Network) cable, and the like. However, the present invention is not limited to this. is not.

The command providing means 22 has a function as a loader command server, for example. Specifically, the command providing unit 22 acquires a command for exchanging data with the PLC 11 or the I / O module 13 or executing a preset process from the application management unit 24. The command providing unit 22 outputs a command related to the loader to a predetermined external device.

In this embodiment, the loader means, for example, a program that resides in a storage area used for reading a program from an external storage device into a storage area of a computer, but is not limited thereto. . In the present embodiment, the command means, for example, a command for giving predetermined execution or control to the above-described loader, but is not limited thereto. Each command may be acquired from, for example, the user terminal 12 described above, or may be acquired by the application management unit 24 or the system management unit 25.

The storage management unit 23 is a storage unit for storing identification information of the PLC 11 such as its own MAC address, contents operated in the PLC 11, output results, and the like. Further, the storage management means 23 has an area for determining the evaluation period and the like, and stores, for example, an integrated value of the program execution cycle in the area.

Further, the storage management unit 23 is connected to a non-volatile rewritable memory (storage unit) such as a flash memory or an SD card (registered trademark), for example, and stores predetermined information so that it can be read out as necessary. It may be. The storage management unit 23 outputs the acquired information to the application management unit 24, the system management unit 25, etc., and stores information obtained from the application management unit 24, the system management unit 25, etc.

The application management unit 24 manages the usage period of the PLC 11 in the present embodiment, and manages applications (programs) and the like for causing the user to use appropriately. Specifically, the application management unit 24 integrates, for example, program execution cycles, and executes an application (program) when the integrated value obtained by the integration exceeds a preset threshold value of the PLC 11. By stopping this, the use of the PLC 11 is stopped.

In that case, the application management means 24 first accumulates the execution period of the program, counts when the accumulated value obtained by the accumulation exceeds a predetermined fixed time value, and obtains the accumulated execution time of the program based on the counted value. . Next, the application management unit 24 stops the use of the PLC 11 by preventing the execution of the program when the accumulated execution time exceeds a preset evaluation period.

Further, the application management unit 24 may write a flag in a predetermined data area every time the above-described integrated value exceeds the above-described fixed time, and calculate the cumulative execution time based on the number of written flags. In that case, the application management means 24 may write a flag in a predetermined data area every time the number of executions of the program exceeds a set fixed number of times, and calculate an integrated value based on the number of written flags.

A specific example of writing a flag will be described later. The application management unit 24 prevents the next program from being executed when the program is executed for the evaluation period or more by the determination of the number of flags described above.

The system management means 25 manages the system operation of the entire PLC 11. Specifically, the system management unit 25 measures the usage time based on the switch information from the SW monitoring unit 26. The time information at this time can be acquired from, for example, the calendar IC 27. Further, the system management means 25 compares the measured actual use time with a preset use time, and if the actual use time exceeds the preset use time, the execution of the program is prevented. Prior to the notification, a user or the like in the vicinity is notified by light or voice. Note that the notification or the like can be performed by the notification unit 29 by causing the application management unit 24 to generate a notification command.

Also, the system management means 25 executes a predetermined command for regular purchase or rental acquired from the user terminal 12. Thereby, the system management means 25 can rewrite various setting information as the controller for evaluation stored in the storage management means 23, for example, and can realize continuous use of the PLC 11 even after the evaluation period expires. For example, the system management unit 25 compares the MAC address included in the unique command obtained from the outside with its own MAC address, and can execute the command if they are the same, but is not limited thereto. It is not a thing.

For example, the SW management unit 26 sends a signal to a switch selected by the user from each switch (for example, a power switch, a key switch (KeySW), a station number switch (SW), etc.) provided in the PLC 11 itself. Output to.

The calendar IC 27 acquires date and time information and outputs the acquired date and time information (for example, not only the date and time but also the day of the week, for example) to the system management means 25. The calendar IC 27 may be, for example, an RTC (Real Time Clock), but is not limited to this.

The I / O control means 28 controls transmission / reception of control data, message data, and the like to / from external devices such as the PLC 11 and the I / O module 13. Further, the I / O control unit 28 outputs the acquired data to the application management unit 24 and the system management unit 25.

The notifying unit 29 has a light emitting unit such as an LED and a sound output unit such as a speaker, for example, and performs notification to the outside in response to an instruction from the application management unit 24 when notification to the outside is necessary. The notification means 29 may be provided inside the PLC 11 or may be provided outside.

<Hardware configuration example in PLC 11>
Next, a hardware configuration example of the PLC 11 in the present embodiment will be described with reference to the drawings. FIG. 3 is a diagram illustrating an example of a hardware configuration of the PLC according to the present embodiment. The hardware configuration of the PLC 11 shown in FIG. 3 includes a CPU 31, a driver / receiver (network connection device) 32, a bus controller 33, a flash (FLASH) memory 34, a program memory 35, a data memory 36, and an RTC 37. , Switch 38, LED 39, speaker 40, battery 41, power source 42, and reset circuit 43. The CPU 31, driver / receiver 32, bus controller 33, flash memory 34, program memory 35, data memory 36, RTC 37, switch 38, LED 39, and speaker 40 are connected by a system bus B or the like.

CPU 31 controls the entire PLC 11. Specifically, the CPU 31 executes a system program and a user program corresponding to a preset support tool and the like. Note that the program is executed in synchronization with, for example, the exchange period of data circulating around the ring-shaped network 15 described above. As an example, the PLC 11-1 transmits a data frame to the network 15 every 1 ms, for example, and circulates it. When receiving the circulating data frame, the I / O module 13 adds its own I / O information to the data frame and transmits the data frame to the network 15 again. In this way, the network connecting the programmable controllers of the present invention transmits data frames like a bucket relay. The PLC 11-1 receives a data frame that has made a round of the network 15, acquires I / O information from the I / O module 13, and gives the I / O information to a program (application program) installed in the PLC 11-1 for control. An operation is being performed.

In the present embodiment, the system program and the user program described above can be stored in the flash memory 34, which is a non-volatile rewritable memory, in order to save the system program and the user program even when the power is turned off.

Further, a driver / receiver 32 is connected to the CPU 31. The driver / receiver 32 is a device for transmitting a user instruction obtained from the user terminal 12 having a support tool. The driver / receiver 32 acquires a support tool or the like that the user terminal 12 has via, for example, a serial bus, a network, Ethernet (registered trademark), or the like. Further, the driver / receiver 32 can obtain the support tool recorded on the above-described recording medium via a recording medium such as a USB or an SD card. In this case, the driver / receiver 32 outputs the acquired support tool or the like to the CPU 31.

The bus controller 33 exchanges data with the I / O module 13 that is the control target of the PLC 11. Specifically, the bus controller 33 issues a processing instruction to a predetermined I / O module 13 that is an evaluation target device, and acquires results such as processing speed and processing accuracy from the processing results. For example, a network LSI (Large Scale Integration) can be used as the bus controller 33, but the present invention is not limited to this.

The flash memory 34 stores a system program and a user program (for example, a program provided by the PLC 11) based on control by the CPU 31. Note that the flash memory 34 has a lower read / write speed than SRAM (Static Random Access Memory). Therefore, when executing the user program (and system program etc.) stored in the flash memory 34, the PLC 11 develops and executes it in the fast program memory 35. In the present embodiment, the data memory 36 is provided as a memory to be read / written by the user program and the system program. That is, both the program memory 35 and the data memory 36 are composed of SRAM or the like.

Here, although the program memory 35 and the data memory 36 are expressed as separate memories, they may be physically one memory, and a program memory for executing a higher-speed application, such as an SDRAM (Synchronous Dynamic Random), for example. You may implement | achieve using high-speed devices, such as Access Memory. As the memory, for example, a semiconductor memory or the like that can freely erase and write data and whose contents are not lost even when the power is turned off can be used. However, the present invention is not limited to this.

Further, in the present embodiment, the calendar IC 27 is mounted as described above in order to execute a user program of the PLC 11 as a controller and to record when an abnormality occurs. The calendar IC 27 can acquire accurate data such as date and time by the RTC 37.

Further, in the present embodiment, an operation device such as the switch 38 is provided, and the user can directly perform operations such as turning on / off the power supply and restarting the PLC 11. Further, in the present embodiment, as described above, the notification unit 29 for notifying the user such as the LED 39 and the speaker 40 is provided. The LED 39 notifies the user that the predetermined usage time has passed and that the PLC 11 cannot be used because the PLC 11 has exceeded the predetermined usage time. In addition, the speaker 40 notifies the user by sound that the predetermined usage time has elapsed and that the PLC 11 cannot be used because it has exceeded the predetermined usage time.

Here, the data memory 36 and the RTC 37 described above may be backed up using batteries 41-1 and 41-2, respectively. The batteries 41-1 and 41-2 may be the same battery or separate batteries. Normally, the PLC 11 is operated by supplying power from the power source 42. In the present embodiment, the use time of the PLC 11 can be reset by the reset circuit 43. Thereby, when purchasing PLC11, even if it exceeds predetermined use time, it can be used as it is.

<Example of functional configuration in user terminal 12>
Next, a functional configuration example of the above-described user terminal 12 will be described with reference to the drawings. FIG. 4 is a diagram illustrating an example of a functional configuration of the user terminal. The user terminal 12 shown in FIG. 4 includes an input unit 51, an output unit 52, a storage unit 53, a PLC (controller) execution unit 54, a notification unit 55, a purchase unit 56, a screen generation unit 57, It has a transmission / reception means 58 and a control means 59.

The input means 51 accepts input from a user or the like to start or end various instructions such as a predetermined program execution instruction to each PLC 11, a notification instruction, a purchase instruction, a screen generation instruction, and a transmission / reception instruction. The input means 51 is composed of a pointing device such as a keyboard and a mouse. Further, the input means 51 may have a voice input function for inputting voice or the like.

The output means 52 outputs the contents input by the input means 51, the results and progress made based on the input contents. Note that the output unit 52 includes, for example, a display or a speaker.

The storage unit 53 stores various pieces of information (for example, a support tool or system program that causes the PLC 11 to perform predetermined execution, a user program, identification information of the PLC 11, key information, various setting information, and the like) necessary in the present embodiment. Further, the storage means 53 can read out various data stored as necessary.

The PLC execution unit 54 causes the PLC 11 to execute a predetermined process (program or the like) based on a support tool or the like stored in the storage unit 53 or the like. At this time, the PLC execution means 54 may individually execute predetermined processing for each of the PLCs 11-1 to 11-3, or may execute predetermined processing for a plurality of PLCs. The PLC execution unit 54 can obtain the latest support tool from the provider terminal 16 via the communication network 17 as necessary.

The notification means 55 performs a predetermined notification (for example, alarm output) to the user by the output means 52 when the evaluation period preset from the PLC 11 has expired. Note that the notification contents by the notification means 55 may be generated and displayed by the screen generation means 57 based on the notification contents obtained from the PLC 11, or may be notified by light or voice.

The purchase means 56 connects to the provider terminal 16 via the communication network 17 and performs a predetermined purchase procedure when the user actually purchases the evaluation PLC 11. Further, the purchase means 56 can perform not only purchase by purchase as a predetermined purchase procedure, but also a procedure for rental use of the PLC 11 for a predetermined period.

The predetermined purchase procedure is, for example, transmitting notification information indicating whether the PLC 11 is purchased, rented, or not purchased to the provider terminal 16. In this embodiment, the identification information (for example, MAC address) of the PLC 11 is also transmitted to the provider terminal 16. Further, in the present embodiment, for example, at the time of purchase or rental, encryption is performed when acquiring predetermined information (for example, command information, etc.) that can be used continuously after the evaluation period of the PLC 11 has elapsed. For this purpose, preset key information may be transmitted to the provider terminal 16.

Further, the purchase means 56 performs a decryption process corresponding to preset key information when information acquired from the provider terminal 16 via the communication network 17 is encrypted. In addition, the purchasing unit 56 causes the PLC executing unit 54 to execute a process of performing regular use or rental use on the predetermined PLC 11 based on information obtained from the provider terminal 16 obtained by the decryption process.

The screen generation means 57 generates a setting screen for the support tool such as what kind of processing the user performs on each PLC 11 connected to the communication cable 14 or the like. Further, the screen generation unit 57 generates a screen for displaying notification information for notifying the expiration of the evaluation period from the PLC 11. The screen generation means 57 can also generate a screen or the like indicating how much evaluation period remains.

The transmission / reception means 58 receives various information (for example, support tools (various programs, etc.), command information, various setting information, execution results of predetermined processing, etc.) from an external device that can be connected using the communication cable 14 or the communication network 17. It is an interface for obtaining. Further, the transmission / reception means 58 can also transmit various information such as notification information obtained by the notification means 55 and the execution result of the PLC 11 to the external device.

The control unit 59 controls the entire components of the user terminal 12. Specifically, the control unit 59 performs control in each process such as execution of a predetermined process for the PLC 11 and purchase process of the PLC 11 based on an instruction from the input unit 51 by a user or the like.

<Example of functional configuration of provider terminal 16>
Next, a functional configuration example in the provider terminal 16 described above will be described with reference to the drawings. FIG. 5 is a diagram illustrating an example of a functional configuration of the provider terminal. The provider terminal 16 user terminal 12 shown in FIG. 5 includes an input means 61, an output means 62, a storage means 63, a PLC (controller) management means 64, a key acquisition means 65, a command generation means 66, An encryption unit 67, a transmission / reception unit 68, and a control unit 69 are included.

The input means 61 accepts inputs such as start / end of various instructions such as a PLC management instruction, a key acquisition instruction, a command generation instruction, an encryption instruction, and a transmission / reception instruction from a provider. The input means 61 is composed of a pointing device such as a keyboard and a mouse. Further, the input means 61 may have a voice input function for inputting voice or the like.

The output means 62 outputs the contents input by the input means 61, the results executed based on the input contents, progress, and the like. Note that the output unit 62 includes, for example, a display or a speaker.

The storage unit 63 stores various information necessary in the present embodiment (for example, a support tool, a system program, a user program, various setting information, and the like that are transmitted to the user terminal 12 and cause the PLC 11 to perform predetermined execution). Further, the storage means 53 can read out various data stored as necessary.

The PLC management means 64 manages the identification information, the number of units, the purchase history, and the like of the PLC 11 provided as an evaluation version for each user terminal 12. The purchase history includes, for example, history information that can be separately managed when purchased or rented, but is not limited thereto.

The key acquisition means 65 encrypts command information for continuously using the PLC 11 currently used after the evaluation period expires when purchasing or renting at least one PLC 11 from the user terminal 12. Get key information of. The key information is transmitted from the user terminal 12 when the PLC 12 is purchased or used for rental. If the key information is not transmitted, the key information acquisition unit 65 requests the user terminal 12 for the key information. You can also.

The command generation means 66 generates a corresponding command based on a purchase (regular version) request or a rental request obtained from the user terminal 12. The command is, for example, a command that allows the PLC 11 to be used indefinitely as a regular version after the evaluation period expires, or can be used as a rental version for a predetermined period after the evaluation period expires. Contains commands to turn on.

The command generation means 66 includes the identification information of the PLC 11 in the generated command. The identification information can be a MAC address or the like, but is not limited to this. This identification information is transmitted from the user terminal 12, for example.

The encryption unit 67 performs encryption based on the key information acquired by the key acquisition unit 65 described above when the command generated by the command generation unit 66 is transmitted. By encrypting the command, it is possible to prevent the transmitted data from being diverted to another PLC 11 even if the transmitted data is stolen. In the present embodiment, for example, when the user terminal 12 and the provider terminal 16 communicate with each other via a dedicated line, the command may be transmitted to the user terminal 12 without being encrypted. Therefore, in such a case, the functions of the key acquisition unit 65 and the encryption unit 67 are not necessary.

The transmission / reception means 68 is an interface for acquiring various types of information (for example, purchase request etc.) from one or a plurality of user terminals 12 connectable via the communication network 17. Further, the transmission / reception unit 68 transmits, for example, a command generated by the command generation unit 66 to the user terminal 12 via the communication network 17. The transmission / reception means 68 can acquire and transmit various necessary information from an external device connected to the communication network 17.

The control means 69 controls the entire components of the provider terminal 16. Specifically, the control unit 69 performs control in each process such as management of the PLC 11 and issuance of commands to the user terminal 12 based on, for example, an instruction from the input unit 61 by a provider or the like.

<Hardware Configuration Example in User Terminal 12 and Provider Terminal 16>
Next, a hardware configuration example in the user terminal 12 and the provider terminal 16 will be described with reference to the drawings. FIG. 6 is a diagram illustrating an example of a hardware configuration of the user terminal and the provider terminal in the present embodiment.

The user terminal 12 and the provider terminal 16 in FIG. 6 include an input device 71, an output device 72, a drive device 73, an auxiliary storage device 74, a memory device 75, a CPU 76 for performing various controls, and a network connection. Device 77 and these are connected to each other by a system bus B.

The input device 71 has a pointing device such as a keyboard and a mouse operated by a user or the like, and inputs various operation signals such as execution of a program from the user or the like.

The output device 72 has a display for displaying various windows, data, and the like necessary for operating the computer main body for performing processing in the present invention, and displays the program execution progress and results by the control program of the CPU 76. can do.

Here, the execution program installed in the computer main body in the present invention is provided by a portable recording medium 78 such as a USB memory or a CD-ROM, for example. The recording medium 78 on which the program is recorded can be set in the drive device 73, and the execution program included in the recording medium 78 is installed from the recording medium 78 to the auxiliary storage device 74 via the drive device 73.

The auxiliary storage device 74 is a storage means such as a hard disk, and stores an execution program according to the present invention, a control program provided in a computer, and the like, and can perform input / output as necessary.

The memory device 75 stores the execution program read from the auxiliary storage device 74 by the CPU 76. The memory device 75 includes a ROM (Read Only Memory), a RAM (Random Access Memory), and the like.

The CPU 76 controls processing of the entire computer such as various operations and data input / output with each hardware component based on a control program such as an OS (Operating System) and an execution program stored in the memory device 75. Thus, each process in the present embodiment can be realized. Various information necessary during the execution of the program can be acquired from the auxiliary storage device 74, and the execution result and the like can also be stored.

The network connection device 77 obtains an execution program from another terminal connected to the communication network by connecting to a communication network or the like, or an execution result obtained by executing the program or an execution in the present invention The program itself can be provided to other terminals.

<Relationship between data exchange with I / O module 13 and execution procedure of user application>
Next, the relationship between the data exchange with the I / O module 13 and the execution procedure of the user application (program) will be described with reference to the drawings. FIG. 7 is a diagram for explaining an example of a program execution cycle in the PLC.

In the present embodiment, the user application shown in the example of FIG. 7 takes a series of computations by, for example, fetching data from the I / O module 13 and executing computations, and then sending computation result data to the I / O module 13. Complete the process. In the description of FIG. 7, a period during which the above-described series of processing is performed is referred to as “scan”.

As shown in FIG. 7, in a period 81 between scans, controller management (for example, abnormality monitoring and system control processing) is performed. In the following description, this period 81 is referred to as a “scan end process period”.

In order to provide input data to the application before the start of scanning, the PLC 11 as a controller first reads the input data 82 and copies the read input data 82 to the input data area of the application (input from the input data 82 shown in FIG. 7). Processing to data 83).

In the example of FIG. 7, the previous output data 84 is written (processing from the output data 84 to the output data 85 shown in FIG. 7). Here, a period 86 from the input data reading to the next input data reading or from the application execution input to the next application execution input is a numerical value defined by the user and is called a scan cycle. The PLC 11, which is a controller, performs predetermined arithmetic processing and input / output data processing (user program processing period 87 shown in FIG. 7) based on this scan cycle. In bus processing, processing such as message transmission 88 is performed as arithmetic processing.

Note that the series of processes described above are executed in a constant cycle as shown in FIG. 7, and this cycle is executed in synchronization with, for example, the exchange period of data circulating around the ring network 15 described above.

Here, in the present embodiment, in providing the PLC 11 that is the controller for evaluation, the evaluation period is determined based on the integrated execution time of the application. Note that the evaluation period can be determined by date using the calendar IC 27 described above, for example. However, for example, if the user does not perform actual machine evaluation (the controller is not turned on), the evaluation period is shortened, and it is necessary to set an evaluation completion date every time an evaluation machine is lent. This is not a preferable method because it may be operated without a battery.

Therefore, in the present embodiment, it is determined whether the application is being executed in the controller management process in the scan end processing period 81 for the PLC 11 used as the evaluation controller. Specifically, the present embodiment integrates program execution cycles under the control of the CPU 31, for example, and prevents execution of the program when the integrated value obtained by the integration exceeds a preset threshold value. , Stop using the PLC 11. The integrated value and the like are stored and managed in the above-described flash memory 34 and the like.

<Example of evaluation period determination and execution control in PLC 11>
Here, the evaluation period determination and execution control example in the PLC 11 described above will be specifically described.

<First embodiment>
FIG. 8 is a flowchart for explaining a first example of evaluation period determination and execution control.

In the example of FIG. 8, in the first embodiment, the above-described scan time is first added to the accumulated time (S01). As described above, by accumulating on the basis of the scan time described above, for example, the execution cycle of the program executed in synchronization with the exchange cycle of the data circulating around the ring-shaped network 15 can be accumulated.

In the first embodiment, it is determined whether or not the integration time (integration value) integrated in S01 is equal to or greater than a preset threshold value (S02). As the threshold value, for example, a time such as 5 to 10 hours, 1 to 2 weeks, or 1 to 3 months can be set, and this setting can be set, for example, by the provider providing the PLC 11. In the case of the first embodiment, this threshold is the above-described evaluation period. Here, in the first embodiment, when the accumulated time is equal to or greater than the threshold value (YES in S02), the user is notified by a preset notification means (S03), and thereafter the execution of the program is prevented. (S04). In the first embodiment, if the accumulated time is not equal to or greater than the threshold in the process of S02 (NO in S02), the program can be executed by returning to S01. The accumulated time can be managed by storing it in the above-described flash memory 34 or the like in correspondence with the program execution cycle.

Thereby, the PLC 11 can be stopped at an appropriate timing with respect to the expiration of the evaluation period. Note that the processing shown in FIG. 8 is performed by, for example, the application management unit 24 described above.

Normally, the PLC 11 executes an application by turning on / off the power, resetting, or an application activation instruction from a support tool obtained from the user terminal 12 or the like. In this case, in the first embodiment, when the program is executed by the PLC 11, the accumulated time on the flash memory 34 described above is checked, and the application is not executed if the threshold corresponding to the evaluation period is exceeded. To.

In the first embodiment described above, for example, one or a plurality of PLCs 11 and one or a plurality of I / O modules 13 exchange data at a predetermined cycle via a data exchange bus, and the PLC 11 replaces the I / O module 13 with each other. The programmable controller system 18 that controls an external device connected to the I / O module can be applied. In this case, the PLC 11 integrates the execution period of the program executed in synchronization with the predetermined period of data exchange described above, and executes the program when the integrated value obtained by the integration exceeds a preset threshold value. Stop. Thereby, in 1st Example, the unauthorized use of the programmable controller by a user can be prevented.

<Second embodiment>
Next, a second embodiment will be described. In the second embodiment, a time (fixed time) for a plurality of program executions is set based on the program execution cycle. For example, if the program execution cycle is 100 ms, 1 minute is set as the fixed time. In the second embodiment, the execution period of the program is integrated, and when the integrated integration time (integrated value) exceeds a fixed time, the program is counted, and the cumulative execution time of the program is obtained based on this count value. In the second embodiment, the execution of the program is prevented when the accumulated execution time exceeds a preset evaluation period.

In the second embodiment, for example, every time the above-described integration time exceeds a fixed time, a flag is written in a predetermined data area provided in advance in storage means such as a memory, and the above-described number of flags is written. The accumulated execution time may be calculated. In the second embodiment, for example, one flag is written every time one minute of program execution. That is, the setting of the flag means the number of times that the accumulated time described above exceeds the fixed time described above. In the second embodiment, the evaluation time is determined based on the accumulated execution time obtained from the number of flags set in the data area and the threshold value corresponding to the evaluation period described above, and execution control is performed.

Here, FIG. 9 is a flowchart for explaining a second embodiment of evaluation period determination and execution control. FIG. 10 is a diagram showing an example of flag writing corresponding to FIG.

Here, in the example of FIG. 10, the flash memory 34 is used as a non-volatile memory area for writing a flag, but the present invention is not limited to this. The flash memory 34 shown in FIG. 10 includes an area for storing each information of the bit under evaluation 91, the threshold 92, and the determination area 93 in a part of the entire area. The in-evaluation bit 91 includes an identification flag for identifying mode information such as a regular version, an evaluation version, and a rental version. In the example of FIG. 10, the regular version is classified as “0”, the evaluation version as “1”, and the rental version as “2”, but the classification contents are not limited to this.

Also, as the threshold 92, a threshold corresponding to the evaluation period is set. The threshold value 92 can be set by the provider of the PLC 11, but is not limited to this, and for example, a predetermined time (for example, 10 hours) may be set as an initial state.

Further, the determination area 93 indicates the above-described flag writing area, and an area corresponding to the time of the threshold 92 and the above-described fixed time is set. In the example of FIG. 10, in the initial state, “1” is set to all bits, and writing is performed to “0” bit by bit for each unit time set by the threshold 92. For example, when the above-mentioned fixed time is 1 minute, 1 minute = 1 bit, and 1 month = 30 days = 720 hours = 43200 minutes. Therefore, the amount of data used at that time sets an information storage area of about 5400 bytes (less than about 6 Kbytes).

In the example of FIG. 9, the process for the PLC 11 in which the information indicating that it is an evaluation version is included in the predetermined area of the bit under evaluation 91 is shown. Before the process of FIG. A determination is made as to whether it is a version. Therefore, in the present embodiment, the content of the bit under evaluation 91 is first confirmed, and when the PLC 11 is a regular version, the following processing is not performed.

In the example of FIG. 9, the second embodiment first adds the scan time described above to the accumulated time (S11), and then determines whether the accumulated time is equal to or greater than the fixed time (eg, 1 minute) described above. (S12). In the second embodiment, when the accumulated time is equal to or longer than the fixed time (YES in S12), the write position of a predetermined flag in the determination area 93 is incremented (+1) (S13), and a non-volatile memory (for example, a flash memory) The flag is written to (34) (S14). Thereafter, the second embodiment clears the accumulated time (S15).

Here, the second embodiment determines whether or not writing of all the flags is completed after the process of S15 is completed or when the integration time is not longer than the fixed time in the process of S12 (NO in S12) ( S16). In other words, this processing means that it is determined whether or not the cumulative execution time of the program obtained based on the number of written flags is equal to or greater than the threshold 92 described above.

In the second embodiment, when all the flags have been written (YES in S16), the user is notified by a preset notification means (S17), and thereafter the execution of the program is blocked (S17). S18). In the second embodiment, if all the flags have not been written in the process of S16 (NO in S16), the program can be executed by returning to S11. The accumulated time can be managed by storing it in the above-described flash memory 34 or the like, for example, corresponding to the execution cycle of the program.

The time monitoring in the PLC 11 can be appropriately performed by the processing described above. Note that the processing shown in FIG. 9 is performed by, for example, the application management unit 24 described above.

As described above, in the second embodiment, the flash memory 34, which is a non-volatile memory, is initialized with all bits ON (bit "1"), for example, in units of sectors, and bits are written from ON to OFF in units of words. I do. Therefore, in the present embodiment, the time for turning off the bits is set in advance by the system program, and is turned off by one bit every time that time elapses. Thereby, for example, even when the controller power is turned on / off, the elapsed time up to that time remains as a record.

According to the second embodiment described above, by setting a flag corresponding to a fixed time and managing the time used by the user, the flag writing process can have a certain time interval. Can be reduced. In addition, since it is managed not by time but by a flag, it is not noticed that another person is managing the evaluation period even when viewing this data, so that it is possible to prevent unauthorized use due to data tampering by others.

<Third embodiment>
Next, a third embodiment will be described. The PLC 11 is an industrial computer and is a module capable of continuous operation. Therefore, there is a possibility that the application (program) to be evaluated using the PLC 11 is an application that operates continuously for 24 hours. In this case, if the evaluation expiration period is determined only at the application activation timing, the PLC 11 in continuous operation cannot recognize the expiration of the evaluation period.

It is also possible to forcibly terminate the application when the evaluation period expires, but in such a case, depending on the system being evaluated, there is a possibility of causing a serious accident. May cause serious loss.

Therefore, in the third embodiment, the PLC 11 used for evaluation is notified to the user at a predetermined timing before the expiration of the above-described evaluation period, and the user is prompted to shift to a regular product. Further, in the third example, when the above-described notification is performed but the user continues to use it, the user is determined to be a malicious user, and the execution of the program is prevented after the evaluation period expires.

Specifically, in the third embodiment, a threshold value (second threshold value) for second period expiration determination is provided on the flash memory 34 separately from the above-described threshold value for evaluation expiration period determination (first threshold value). ). Further, in the third embodiment, even after the first threshold value has elapsed, the continuous use time of the program is integrated, and if this integrated value has passed a certain period (for example, two weeks), the application (program) is forcibly used. Is stopped and the use of the PLC 11 is stopped. In the third embodiment described above, the sum of the first threshold value and the second threshold value corresponds to the evaluation time until the execution of the program is blocked.

Thereby, in the third embodiment, notification is made before the expiration of the evaluation period, and the PLC 11 can be used for a predetermined period thereafter, so that it can also be applied to a system operating continuously for 24 hours. Further, in the third embodiment, it is possible to prevent the PLC 11 from being used continuously and to lead to sales by purchasing a regular product.

In addition, as a notification mentioned above, a minor failure display etc. can be performed, for example. For example, the LED 39 provided on the front surface of the module of the PLC 11, the speaker 40 provided therein, the display of a failure display screen by the support tool on the user terminal 12, and the RAS area on the application data memory are displayed. Here, the PLC 11 has a RAS notification function (hereinafter referred to as “mild failure display”) for notifying the user of a problem that needs to be dealt with, although it does not affect the execution of the application. This is notified, for example, when “the voltage of the backup battery is low”, “a temporary application congestion has occurred” or the like. Thus, by performing a light failure display, it is possible to notify the user of the expiration of the evaluation period.

Here, FIG. 11 is a flowchart for explaining a third embodiment of evaluation period determination and execution control. FIG. 12 is a diagram showing an example of flag writing corresponding to FIG.

In the example of FIG. 12, compared with the example shown in FIG. 10 described above, two threshold values (first threshold value, second threshold value) 92-1 and 92-2 and two determination areas (first data area) are compared. (Hereinafter simply referred to as “first area”) and second data area (hereinafter simply referred to as “second area”) 93-1 and 93-2.

That is, in the example of FIG. 11 and FIG. 12, it has a threshold value corresponding to each of two types of write flags (first flag and second flag) and a determination area. The two threshold values 92-1 and 92-2 may be different times or the same time. The sizes of the two determination areas 93-1 and 93-2 are set based on the threshold values 92-1 and 92-2 and the fixed time shown in the second embodiment described above. For example, one month or the like is set as the threshold 92-1 used in the determination for the evaluation period and the determination for notification after the expiration of the period, and the determination and use of a predetermined period after the evaluation period expires (forcible stop period expiration) Two weeks or the like can be set as the threshold value 92-2, but is not limited to this.

Therefore, in the third embodiment, when the flag is written every time the integrated value exceeds the fixed time, the flag is first written in the first area, and after all the flags in the first area are written, A flag is written in a second area different from the above, and the expiration of the evaluation period is determined by the number of flags written in the second area.

Specifically, in the example of FIG. 11, in the third embodiment, the scan time described above is first added to the integrated time (S21), and then the integrated time is equal to or longer than the fixed time (for example, 1 minute) described above. It is determined whether or not (S22). In the third embodiment, if the integration time is equal to or longer than the fixed time (YES in S22), whether or not the writing to the first area (for example, the determination area 93-1 shown in FIG. 12) has been completed. Is determined (S23).

In the third embodiment, when the writing to the first area is not completed (NO in S23), the writing position of the first flag is incremented (+1) (S24), and the flag is written to the first area. (S25). That is, in the processes of S24 and S25, the flag is written at a position in the first area where the first flag has not yet been written.

In the third embodiment, when the writing to the first area is completed in the process of S23 (YES in S23), the writing position of the second flag is incremented (+1) (S26), and the second area ( For example, a flag is written in the determination area 93-2) shown in FIG. 12 (S27). That is, in the processing of S26 and S27, the flag is written at a position in the second area where the second flag has not yet been written.

Thereafter, the third embodiment clears the accumulated time (S28). Here, in the third embodiment, whether the writing of all the flags in the second area is completed after the processing of S28 is completed or when the integration time is not longer than the fixed time in the processing of S22 (NO in S22). Is determined (S29). In other words, in this process, the cumulative execution time of the program obtained by the number of flags written in the first area and the second area is equal to or longer than the total time of the threshold value 92-1 and the threshold value 92-2. It means to judge.

In the third embodiment, when all the flags in the second area have been written (YES in S29), the execution of the program is blocked (S30). In the third embodiment, if all the flags have not been written in the process of S29 (NO in S29), the program can be executed by returning to S21. The accumulated time can be managed by storing it in the above-described flash memory 34 or the like in correspondence with the program execution cycle.

The time monitoring in the PLC 11 using the two threshold values can be appropriately performed by the processing described above. Note that the processing shown in FIG. 11 is performed by, for example, the application management unit 24 described above.

Here, in the third embodiment, the notification process to the user is performed after the writing to the first area is completed, but the notification process is not shown in FIG. Therefore, an example of notification processing for the third embodiment will be described below. FIG. 13 is a flowchart illustrating an example of notification processing for the third embodiment. In the example shown in FIG. 13, an example of notification in the LED is shown, but the present invention is not limited to this. For example, notification by output of a predetermined sound or the like may be used, and other alarm outputs may be used. Good.

In the example of FIG. 13, in the notification process in the third embodiment, first, the determination area 93 provided in the nonvolatile memory such as the flash memory 34 is confirmed (S31), and the second area (determination area 93- It is determined whether writing to 2) is completed (S32).

Here, in the notification process, when the writing to the second area is not completed (NO in S32), whether or not the writing to the first area (determination area 93-1) described above is completed next. Is determined (S33). In S33, when the writing to the first area is completed in S33 (YES in S33), the failure RAS is notified (S34), and the failure LED is displayed (S35).

Further, in the notification process, when the writing to the first area is not completed (NO in S33), the process ends as it is. In addition, in the above-described processing of S32, when the writing to the second area is completed (YES in S32), the notification processing is performed without performing notification so that the use as the evaluation controller is stopped. finish. In addition, when the writing to the second area is completed, another notification different from S34 and S35 may be performed.

The process shown in FIG. 13 may be integrated into the process shown in FIG. 11 described above, or only the notification process shown in FIG. 13 may be performed at a predetermined interval separately from the process shown in FIG. By separating the process of FIG. 13 from the process of FIG. 11, only the notification shown in FIG. 13 can be notified to the user regardless of the execution of the program. Thereby, the user can grasp | ascertain easily the present condition of PLC11. The above-described processing is performed by, for example, the above-described application management unit 24.

That is, in the third embodiment described above, when the first area and the second area are provided and the flag is written, the flag starts to be written from the first area, and the flag is written to all the areas of the first area. A predetermined notification (for example, alarm output or the like) is performed, and thereafter, a flag is written in the second area. In the third embodiment, the cumulative execution time is calculated based on the total number of flags including the number of flags written in the first area and the number of flags written in the second area, and the calculated cumulative execution time is evaluated. The program execution is prevented by exceeding.

In the third embodiment, execution control can be performed with the first threshold value described above as the evaluation period and the second threshold value as the grace period. Specifically, in the third embodiment, when writing a flag, the flag begins to be written from the first area corresponding to the evaluation period, and the evaluation period expires when the flag has been written to all areas of the first area. A predetermined notification is performed. In subsequent processing, the flag is written in the second area corresponding to the grace period, and the cumulative time calculated by the number of flags written in the second area exceeds the grace time, thereby preventing the execution of the program. May be.

Furthermore, in the third embodiment, as shown in FIGS. 11 and 12, a second area (determination area 93-2) is separately provided. However, the present invention is not limited to this, and for example, It is possible to cope with this by continuously using one area and providing criteria for evaluation expiration notification determination and forced stop determination. In the present embodiment, for example, a large number of areas such as the third area and the fourth area are provided, and the user can be notified step by step every time the flag of each area is rewritten. In the present embodiment, the content of the bit under evaluation 91 is first confirmed, and the above-described processing is not performed when the PLC 11 is a regular version.

<Evaluation state release method (specific example of command)>
Here, in this embodiment, when the user who actually purchased the PLC 11 uses it as a regular version or a rental version instead of an evaluation version, the PLC 11 may be reused without being collected later. Therefore, in the present embodiment, a state of evaluation version (hereinafter referred to as “evaluation state”) is canceled to provide a mechanism for changing from evaluation to regular use.

Specifically, as described above, the user terminal 12 obtains a command for canceling the evaluation state of the predetermined PLC 11 by performing a purchase procedure for the provider terminal 16. For example, in this embodiment, the provider terminal 16 creates a command based on device-specific information such as an Ethernet MAC address and transmits it to the user terminal 12. The user terminal 12 causes the target PLC 11 to execute this command.

The user terminal 12 circulates the command on the network 15 so that each PLC 11 that has acquired the command compares its own MAC address with the MAC address in the command, and the command is executed if they are the same. Thereby, the change (rewriting etc.) of the mode information from the evaluation version of PLC11 to a regular version or a rental version can be performed individually.

Further, for example, the command operation is rewritten from the evaluation version to the identification information of the regular version or the rental version with respect to the evaluation bit 91 shown in FIGS. initialize.

<How to set a flag when an application is reused for other devices>
In the present embodiment, how to set a flag when an application (program) is reused for another device (PLC) will be described. When the application is reused for other devices, for example, the controller application (program) is illegally used instead of the PLC 11 itself. Therefore, in this embodiment, for example, when an application is copied from the PLC 11, a copy flag is set for the copied application. This flag is set in the flash memory 34, for example, but is not limited to this. Here, another PLC 11 to which the application with the copy flag is downloaded is operated as an evaluation controller.

On the other hand, if the file is properly downloaded, a file that is a preset key is separately downloaded from the external device, and this file cannot be transferred by copying. The above-described processing is performed by, for example, the application management unit 24 of the PLC 11.

<How to set a flag when assuming a rental PLC>
Next, how to set a flag when a rental PLC is assumed will be described. When a rental PLC is assumed, it is assumed that the PLC 11 is purchased from the evaluation of the PLC 11 as an evaluation controller. However, the rental PLC may be used.

Even in such a case, it is possible to cope by downloading a command based on identification information (for example, MAC address) for each device in the same manner as described above. For example, in the case of the rental PLC 11, it is possible to cope with various usage contents of the PLC 11 by setting flags such as addition / deletion of a determination area as an evaluation period, reset of the determination area, and transition to a regular version. Can respond appropriately to the needs of users.

<Processing procedure in user terminal 12>
Here, a processing procedure in the user terminal 12 will be described using a flowchart. FIG. 14 is a flowchart illustrating an example of a processing procedure in the user terminal. In FIG. 14, the user terminal 12 first instructs the PLC 11 used as an evaluation version (evaluation controller) to execute a predetermined program or the like (S41), and obtains an execution result or the like (S42). . In addition to the processing result, for example, acquisition of error information, information on the remaining evaluation period, and the like can be acquired as the execution result.

Here, the user terminal 12 determines whether or not there is a notification from the PLC 11 that the evaluation period has expired (S43). If there is a notification (YES in S43), the user terminal 12 displays it on the screen or the like. And whether or not there has been an instruction to purchase from the user is determined (S44).

Here, the user terminal 12 receives a purchase instruction (YES in S44), purchase request (including rental), identification information (for example, MAC address) of the PLC 11, and key information as necessary. It transmits to the provider terminal 16 (S45). Next, the user terminal 12 determines whether or not a command corresponding to the encrypted purchase request has been acquired from the provider terminal 16 (S46), and if not acquired (NO in S46), the acquisition is performed. Wait until If the user terminal 12 obtains an encrypted command in the process of S45 (YES in S45), the user terminal 12 performs a decryption process (S47), and executes the processed command (S48).

Here, after the process of S48, when there is no notification from the PLC 11 in the process of S43 (NO in S43), or when there is no purchase instruction from the user in the process of S44 (NO in S44), The process ends. In addition, after the process of S48 is completed and when there is no notification from the PLC 11 in the process of S43 (NO in S43), the above-described process can be repeated. On the other hand, in the process of S44, when there is no purchase instruction from the user (NO in S44), the execution of the program in the PLC 11 is blocked and the PLC 11 cannot be used.

<Processing procedure in provider terminal 16>
Here, a processing procedure in the provider terminal 16 will be described using a flowchart. FIG. 15 is a flowchart illustrating an example of a processing procedure in the provider terminal. In FIG. 15, the provider terminal 16 first determines whether or not there is a purchase request (including rental) from the user terminal 12 (S51). If there is a purchase request (YES in S51), A predetermined command for the target PLC 11 is generated in response to the purchase request (S52).

Next, the provider terminal 16 encrypts the command generated in the process of S52 based on the key information obtained from the user terminal 12 (S53), and sends the encrypted command to the user terminal 12. Transmit (S54). If there is no purchase request from the user terminal 12 in the process of S51 (NO in S51), the provider terminal 16 ends the process. In addition, the process in the provider terminal 16 mentioned above is processed for every PLC11 with respect to the user terminal 12 which provides PLC11.

Moreover, although the process shown in FIG. 15 has shown the process in case the user terminal 12 and the provider terminal 16 are connected by the communication network 17 grade | etc., In this embodiment, it is limited to this. is not. For example, when the user terminal 12 and the provider terminal 16 are not connected via the communication network 17, data exchange between the two is performed by mail or the like.

As described above, according to the present invention, it is possible to appropriately control the use of the programmable controller. That is, the present invention can monitor the evaluation period with high accuracy in providing the programmable controller as a programmable controller.

This realizes a function capable of determining the evaluation period as a total of the application (program) execution time of the user without changing the hardware or the like with respect to the existing controller, and limiting the activation of the controller after the evaluation period expires. . In addition, when the evaluation period expires during execution of the user application, the expiration of the period is notified to the predetermined notification means, application, support tool, etc. without stopping the application, and the user is encouraged to purchase a genuine product. be able to. As a result, the system that does not replace the genuine product is regarded as malicious use, and the execution of the controller can be stopped after a certain period of time.

The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to the specific embodiments, and various modifications, It can be changed.

10 Providing system 11 PLC
DESCRIPTION OF SYMBOLS 12 User terminal 13 Input / output module 14 Communication cable 15 Network 16 Provider terminal 17 Communication network 18 Programmable controller system 21 Communication interface means 22 Command providing means 23 Storage management means 24 Application management means 25 System management means 26 Switch (SW) monitoring Means 27 Calendar IC (Date and time acquisition means)
28 Input / output (I / O) control means 29 Notification means 31 CPU
32 Driver / receiver (network connection device)
33 Bus controller 34 Flash (FLASH) memory 35 Program memory 36 Data memory 37 RTC
38 switch 39 LED
40 speaker 41 battery 42 power supply 43 reset circuit 51, 61 input means 52, 62 output means 53, 63 storage means 54 PLC (controller) execution means 55 notification means 56 purchase means 57 screen generation means 58, 68 transmission / reception means 59, 69 control Means 64 PLC (controller) management means 65 Key acquisition means 66 Command generation means 67 Encryption means 71 Input device 72 Output device 73 Drive device 74 Auxiliary storage device 75 Memory device 76 CPU
77 Network connection device 78 Recording medium 81, 86 Period 82, 83 Input data 84, 85 Output data 87 User program processing period 88 Message transmission 91 Bit under evaluation 92 Threshold 93 Determination area

Claims (19)

1. The program execution cycle is accumulated, and the accumulated value obtained by the accumulation is counted when it exceeds a predetermined fixed time value. The accumulated execution time of the program is obtained based on the counted value, and the accumulated execution time is preset. A programmable controller comprising application management means for preventing the execution of the program by exceeding an evaluation period.
2. The application management means includes
   2. The programmable controller according to claim 1, wherein a flag is written in a predetermined data area each time the integrated value exceeds the fixed time, and the cumulative execution time is calculated based on the number of the written flags.
3. The data area is composed of a first data area and a second data area,
   The application management means includes
   When writing the flag, the flag starts to be written from the first data area, and when the flag has been written to all areas of the first data area, a predetermined notification is given, and thereafter the second data area The cumulative execution time is calculated from the total number of flags of the number of flags written to the first data area and the number of flags written to the second data area. 2. The programmable controller according to 2.
4. Every time the program execution cycle is integrated, and the integrated value obtained by the integration exceeds a predetermined fixed time value, a flag is written in a predetermined data area, and the cumulative execution time is calculated by the number of the written flags, After the accumulated execution time exceeds a preset evaluation period, application management means for waiting for a predetermined grace period and preventing the execution of the program,
   The data area includes a first data area and a second data area,
   The application management means starts writing the flag from the first data area corresponding to the evaluation period when writing the flag, and finishes writing the flag to all areas of the first data area. A predetermined notification indicating the expiration of the period is performed, and thereafter, a flag is written in the second data area corresponding to the grace period, and the cumulative time calculated only by the number of flags written in the second data area A programmable controller characterized in that execution of a program is prevented by exceeding a grace period.
5. The programmable controller includes communication means including a MAC address;
   A command including a MAC address is received from the outside, the MAC address included in the received command is compared with the MAC address included in the communication means, and the command is executed when both MAC addresses are the same. And system management means for rewriting the mode information of the programmable controller by the execution and causing the application management means to continue execution of the program even if the accumulated execution time exceeds the evaluation period. The programmable controller of any one of Claims 1 thru | or 4.
6. The programmable controller according to any one of claims 1 to 5, further comprising notification means for notifying execution stop of the program prior to preventing execution of the program.
7. The programmable controller is connected to a ring-shaped data exchange bus and periodically exchanges data with a plurality of nodes connected to the data exchange bus.
   7. The programmable controller according to claim 1, wherein the program is started in synchronization with the data exchange cycle.
8. One or more programmable controllers for executing a program and one or more I / O modules for inputting / outputting data exchange data at a predetermined cycle via a data exchange bus, and the programmable controller In a programmable controller system that controls an external device connected to the I / O module via the O module,
   The programmable controller integrates the execution cycle of the program executed in synchronization with the predetermined cycle of the data exchange, and executes the program when the integrated value obtained by the integration exceeds a preset threshold value. A programmable controller system comprising application management means for blocking.
9. The application management means includes
   9. The flag is written in a predetermined data area every time the number of executions of the program exceeds a set fixed number of times, and the integrated value is calculated based on the number of written flags. Programmable controller system.
10. The data area is composed of a first data area and a second data area,
    The application management means includes
    When writing the flag, the flag starts to be written from the first data area, and when the flag has been written to all areas of the first data area, a predetermined notification is given, and thereafter the second data area The integrated value is calculated from the number of flags written in the second data area and the total number of flags written in the first data area. The programmable controller system described.
11. The programmable controller further includes communication means including a MAC address,
    A command including a MAC address is received from the outside, the MAC address included in the received command is compared with the MAC address included in the communication means, and the command is executed when both MAC addresses are the same. The system further comprises system management means for rewriting the mode information of the programmable controller by executing this command and causing the application management means to continue execution of the program even if the integrated value exceeds the threshold value. Item 11. The programmable controller system according to any one of Items 8 to 10.
12. The programmable controller system according to any one of claims 8 to 11, further comprising notification means for notifying execution stop of the program prior to preventing execution of the program.
13. A programmable controller providing system in which a programmable controller that executes a program, a user terminal that instructs the programmable controller to execute the program, and a provider terminal that provides the programmable controller are connected on a network. ,
    The programmable controller integrates the execution period of the program, counts when the integrated value obtained by the integration exceeds a predetermined fixed time value, obtains an accumulated execution time of the program based on the counted value, and performs the accumulated execution A providing system comprising application management means for preventing execution of the program when time exceeds a preset evaluation period.
14. The application management means includes
    14. The providing system according to claim 13, wherein a flag is written in a predetermined data area every time the integrated value exceeds the fixed time, and the cumulative execution time is calculated based on the number of the written flags.
15. The data area is composed of a first data area and a second data area,
    The application management means includes
    When writing the flag, the flag starts to be written from the first data area, and when the flag has been written to all areas of the first data area, a predetermined notification is given, and thereafter the second data area The cumulative execution time is calculated from the total number of flags of the number of flags written to the first data area and the number of flags written to the second data area. 14. The providing system according to 14.
16. A programmable controller providing system in which a programmable controller that executes a program, a user terminal that instructs the programmable controller to execute the program, and a provider terminal that provides the programmable controller are connected on a network. ,
    The programmable controller integrates the program execution cycle, writes a flag in a predetermined data area every time the integrated value obtained by the integration exceeds a predetermined fixed time value, and performs cumulative execution according to the number of the written flags An application management means for calculating a time and waiting for a predetermined grace period after the accumulated execution time exceeds a preset evaluation period, and preventing execution of the program;
    The data area includes a first data area and a second data area,
    The application management means starts writing the flag from the first data area corresponding to the evaluation period when writing the flag, and finishes writing the flag to all areas of the first data area. A predetermined notification indicating the expiration of the period is performed, and thereafter, a flag is written in the second data area corresponding to the grace period, and the cumulative time calculated only by the number of flags written in the second data area A providing system characterized in that execution of a program is prevented by exceeding a grace period.
17. The programmable controller includes communication means including a MAC address;
    A command including a MAC address is received from the outside, the MAC address included in the received command is compared with the MAC address included in the communication means, and the command is executed when both MAC addresses are the same. And system management means for rewriting the mode information of the programmable controller by the execution and causing the application management means to continue execution of the program even if the accumulated execution time exceeds the evaluation period. The providing system according to any one of claims 13 to 16.
18. The providing system according to any one of claims 13 to 17, further comprising notification means for notifying execution stop of the program prior to preventing execution of the program.
19. The programmable controller is connected to a ring-shaped data exchange bus and periodically exchanges data with a plurality of nodes connected to the data exchange bus.
    The system according to any one of claims 13 to 18, wherein the program is started in synchronization with the data exchange cycle.

Images