WO2020070873A1 - Cpu unit, programmable logic controller, method, program, and engineering tool - Google Patents

Abstract

In a CPU unit (100) of a programmable logic controller, a point storage unit (112) stores possessed points representing a limit to which execution of the paid application (12) is accepted in the CPU unit (100), the possessed points being maintained regardless of the number of times of execution of the paid application (12) and the execution time period of a program component. When the total countervalue points of the selected paid application (12) is equal to or less than the possessed points, an execution possibility determining unit (152) determines that execution of the paid application (12) is possible, and when the total countervalue points of the selected paid application (12) is greater than the possessed points, the execution possibility determining unit (152) determines that execution of the paid application (12) is impossible. When execution of the paid application (12) is possible, an execution managing unit (153) executes the paid application (12).

Description

CPU unit, programmable logic controller, method, program, and engineering tool

<< The present invention relates to a CPU unit, a programmable logic controller, a method, a program, and an engineering tool.

(4) The programmable logic controller controls the movement of the device to be controlled by executing a program created by the user according to the intended use. Creating a program from scratch requires creation time, creation skills, and the like. In order to support the creation of a program, a manufacturer of a programmable logic controller sells a program component, which is a software componentized to realize a specific function.

Conventionally, such program parts are often sold as a library in which a plurality of program parts are set, and the user has to purchase the library. However, in many cases, the user only needs a part of the program components included in the library, and there has been a request to purchase only some of the program components.

(4) In order to satisfy the above-mentioned demand, Patent Literature 1 describes that a user can execute only a selected program component. In Patent Literature 1, the amount charged for each program component in a period unit is determined. The user purchases in advance a usage right whose frequency exceeds the sum of the billing amounts of the selected program components. After the lapse of the determined period, the frequency corresponding to the charge for the program component selected by the user is subtracted from the frequency of the usage right purchased by the user.

Also, as another purchase mode, a user can purchase out-of-the-box program parts using points purchased in advance. When purchasing a program part, the points held by the user are used for the price of the program part. Since the program component is a purchase-out type, the user can continue to use the program component regardless of the number of times the program component is used and the period in which the program component is used.

JP-A-2003-22143

In the configuration of Patent Document 1, the frequency of the usage right purchased by the user is consumed as the period elapses. Therefore, when the frequency becomes zero, the program component cannot be executed. In order to prevent such a situation, Patent Document 1 describes that a warning is issued to a user when the frequency becomes equal to or less than a certain value. For this reason, the user needs to constantly monitor whether a warning has occurred. In addition, the user must purchase additional usage rights of an appropriate frequency before the frequency becomes zero. As described above, it takes time and effort to monitor the occurrence of the warning and frequently purchase the usage right, and the user is not convenient.

(4) When changing the combination of program parts after purchasing a purchase-type program part, the user needs to purchase a new necessary program part. For example, a trial period is provided for a program component, and if the purchase of the program component is canceled during the trial period, points used at the time of purchase may be returned. The user can perform a point return request procedure, and after the points have been returned, can use the returned points to purchase new necessary program parts. In this case, since the points are returned, the user does not waste the points. However, the procedure for requesting the return of points is complicated for the user, and is not convenient for the user.

The present invention has been made in view of the above circumstances, and when a programmable logic controller executes a charged program part, it is possible to freely combine a plurality of program parts within the range of points held by the programmable logic controller. It is possible to enhance convenience for the user.

In order to achieve the above object, in the CPU unit of the programmable logic controller according to the present invention, the value point storage means stores, for at least one program component, a value point indicating a price required to execute the program component. The limit point storage means stores a limit point which indicates a limit at which the execution of the program component is permitted in the CPU unit, and is maintained regardless of the number of times the program component is executed and the execution period of the program component. . The determining means determines that the program part can be executed if the total value points of the selected program part is equal to or less than the limit point, and determines that the program part can be executed if the total value point exceeds the limit point. It is determined that the component cannot be executed. The execution management unit executes the program component when the determination unit determines that the program component can be executed, and does not execute the program component when the determination unit determines that the execution of the program component is not possible.

The CPU unit of the present invention can execute the selected program component when the sum of the consideration points of the selected program component is equal to or less than the limit point indicating the limit of execution of the program component. Therefore, the user can freely combine a plurality of program parts within the range of the limit point. Further, the limit point is maintained regardless of the number of executions of the program component and the execution period of the program component. Therefore, even when the combination of the program parts is changed, if the sum of the consideration points is equal to or less than the limit point, the execution of the program parts can be continued without performing the point purchase.

FIG. 1 is a block diagram showing a hardware configuration of a CPU unit, an engineering tool, and a point management server according to an embodiment of the present invention. Functional block diagram of CPU unit and engineering tool according to the embodiment FIG. 3 is a diagram illustrating an example of a configuration of a user program according to the embodiment. The figure which shows the structure of the program storage part of the engineering tool concerning embodiment. 6 is a diagram illustrating an example of data of a point management table stored in a point storage unit of the engineering tool according to the embodiment. The figure which shows an example of the menu screen of the engineering tool concerning embodiment. The figure which shows an example of the download screen of the pay application which concerns on embodiment. The figure which shows an example of the login screen to the point management menu which concerns on embodiment. The figure which shows an example of the main screen of the point management which concerns on embodiment. FIG. 4 is a diagram showing an example of a serial code input screen according to the embodiment. The figure which shows an example of the point registration screen which concerns on embodiment. The figure which shows an example of the point allocation screen which concerns on embodiment. The figure which shows an example of the point writing screen concerning embodiment. The figure which shows an example of the point confirmation screen which concerns on embodiment. The figure which shows an example of the point deletion screen which concerns on embodiment. The figure which shows an example of the data writing screen which concerns on embodiment. Flow chart of initial processing according to the embodiment Flow chart of a program execution process according to the embodiment The figure which shows an example of the data registered into the consideration data concerning the modification 1. FIG. 9 is a diagram showing an example of data registered in the executable data according to the first modification. The figure which shows an example of the data registered into the category table which concerns on the modification 2. The figure which shows an example of the data registered into the executable data according to the modification 2.

(Embodiment)
Hereinafter, a CPU (Central Processing Unit) unit 100 of a programmable logic controller (hereinafter, referred to as a PLC) 1000 according to an embodiment of the present invention will be described.

As shown in FIG. 1, the PLC 1000 includes a CPU unit 100 that controls the entire PLC 1000, an input unit 200 that supplies an input from an external device to the CPU unit 100, and an output unit that supplies an output of the CPU unit 100 to the external device. 300. The CPU unit 100, the input unit 200, and the output unit 300 are connected via a field bus 400 and perform communication via the field bus 400. Although not shown, the CPU unit 100, the input unit 200, and the output unit 300 are connected to a power supply unit via a base unit, and operate with power supplied from the power supply unit. PLC1000 is used, for example, in the field of factory automation.

検 出 A detector 901 including a sensor, a switch, and the like is connected to the input unit 200. For example, when the detector 901 is a switch, the input unit 200 supplies a signal indicating ON / OFF of the switch to the CPU unit 100. A controlled device 902 including an actuator, an indicator light, and the like is connected to the output unit 300. For example, when the controlled device 902 is an indicator light, the output unit 300 outputs a control signal indicating on / off supplied from the CPU unit 100 to the indicator light. Therefore, the indicator light is turned on / off.

The CPU unit 100 executes each command of a program (hereinafter, may be referred to as a user program) created by a user of the PLC 1000 according to a signal indicating on / off supplied from the input unit 200, and outputs an actuator, a display, and the like. A signal for controlling the controlled device 902 including a lamp and the like is supplied to the output unit 300. The user of the PLC 1000 is, for example, an administrator of the PLC 1000.

(4) In order to realize a specific function, a user program may call and execute a program component in which the function is mounted. A program component is a componentized software. Hereinafter, calling a program component from a user program and executing it may be called a call. The program parts are commercially available, paid program parts (hereinafter referred to as “paid program parts”) which must be paid to the creator of the program parts for execution, and program parts created by the user himself. (Hereinafter, referred to as self-made program components). There is no need to pay for execution of self-made program components created by the user himself.

に お い て In the embodiment, the following rules must be followed for execution of paid program components. The price for executing the pay program component is represented by points (hereinafter referred to as price points). The user of the PLC 1000 must have at least the same number of points as the value points indicating the price of the paid program component so that the CPU unit 100 can execute the paid program component. In order to hold the points, the user must pay the amount corresponding to the value points of the paid program parts to the creator of the paid program parts and purchase the points. Further, the user needs to register the purchased points in the CPU unit 100. In addition, in order for the CPU unit 100 to execute the pay program component, it is necessary that points equal to or more than the sum of the consideration points of the pay program component are registered in the CPU unit 100 as possessed points possessed by the CPU unit 100. .

The CPU unit 100 determines whether or not to execute a pay program component according to points registered in the CPU unit 100 and points indicating the value of the pay program component to be called from the user program when executing the program component. I do.

The points purchased by the user and registered in the CPU unit 100 do not change according to the number of executions and the execution period of the paid program component. The CPU unit 100 can execute the plurality of payable program components indefinitely as long as the total value of the plurality of payable program components to be called does not exceed the holding points.

As shown in FIG. 1, the CPU unit 100 has, as a hardware configuration, a storage unit 110 that stores various data, a communication unit 120 that communicates with the input unit 200 and the output unit 300, and receives an input operation by a user. It includes an input receiving unit 130, a display unit 140 for displaying an image on a display device, an arithmetic unit 150 for controlling the entire CPU unit 100, and a tool communication unit 160 for communicating with the engineering tool 500. The storage unit 110, the communication unit 120, the input receiving unit 130, the display unit 140, and the tool communication unit 160 are all connected to the arithmetic unit 150 via the bus 190, and communicate with the arithmetic unit 150. .

(4) The storage unit 110 includes a volatile memory and a nonvolatile memory. The storage unit 110 stores various programs and data. The storage unit 110 implements a program 001 for realizing a function of an execution possibility determination unit 152 described later when executed by the arithmetic unit 150, and realizes a function of an execution management unit 153 described later when executed by the arithmetic unit 150. And a program 002 for storing. The storage unit 110 stores a serial number as identification information for identifying the CPU unit 100 itself.

(4) The possessed point information registered in the CPU unit 100 is supplied as encrypted data from the engineering tool 500 described later to the CPU unit 100. For this reason, the storage unit 110 stores a decryption key for decrypting the encrypted data.

The communication unit 120 includes a network interface circuit for communicating with the input unit 200 and the output unit 300 via the field bus 400. The communication unit 120 outputs the data received from the input unit 200 to the arithmetic unit 150, and transmits the data supplied from the arithmetic unit 150 to the output unit 300.

The input receiving unit 130 includes buttons, operation keys, and the like, receives an operation input from a user, and outputs a signal indicating the user's operation input to the calculation unit 150.

The display unit 140 includes a display device such as an indicator lamp and a display. The display unit 140 turns on / off the indicator lamp under the control of the arithmetic unit 150, for example, and displays an image based on the signal supplied from the arithmetic unit 150 on the display.

The operation unit 150 includes an MPU (Micro Processing Unit). The arithmetic unit 150 executes various programs stored in the storage unit 110 to implement various functions of the CPU unit 100.

The tool communication unit 160 includes a communication interface for communicating with the engineering tool 500 described below via the communication cable 600. The tool communication unit 160 outputs the data received from the engineering tool 500 to the arithmetic unit 150, and transmits the data supplied from the arithmetic unit 150 to the engineering tool 500.

As shown in FIG. 2A, the CPU unit 100 functionally includes a program storage unit 111 that stores a user program and various libraries, and a point storage that stores points held by the CPU unit 100 (hereinafter, held points). Unit 112, an executable flag 113 that holds a value indicating whether a paid program component can be executed, a file operation unit 151 that writes files of various programs supplied from an engineering tool 500 described later into the program storage unit 111, An executable / non-executable determining unit 152 for determining whether the component can be executed, an execution managing unit 153 for managing the execution of the paid program component, and a point managing unit 154 for writing the points allocated to the CPU unit 100 as the holding points in the point storage unit 112 And the engineer And a communication interface 161 to communicate with the packaging tool 500.

The program storage unit 111 stores the first library file 10, the second library file 20, and the user program file 30. The program storage unit 111 is realized by the storage unit 110 illustrated in FIG. The program storage unit 111 is an example of a program storage unit according to the present invention.

The first library file 10 includes a file header 11 and a pay application 12. The file header 11 includes information on consideration points required for execution of the pay application 12. The file header 11 is an example of a value point storage unit of the present invention. The pay application 12 is a pay program component called from the user program 32.

The second library file 20 includes a file header 21 and a free application 22. The file header 21 includes various information on the free application 22 in the second library file 20. Note that, unlike the file header 11 of the first library file 10, the file header 21 does not include information on the value points. This is because the free application 22 is an application created by the user and does not require a fee for execution. The free application 22 is a free program component called from the user program 32.

The user program file 30 includes a file header 31 and a user program 32 created by the user. In the PLC 1000, the user program 32 is executed as follows. The CPU unit 100 sequentially processes the user program 32 as shown in FIG. 2B from the first instruction, and upon reading an END instruction indicating the end of the program, terminates the execution of the user program 32 and restarts the user program 32 in the next cycle. Process sequentially from the first instruction.

(4) The point storage unit 112 stores retained points, which are points purchased by the user and allocated to the CPU unit 100. The holding points indicate a limit in which the CPU unit 100 is allowed to execute the pay application 12. The point storage unit 112 is realized by the storage unit 110 illustrated in FIG. The point storage unit 112 is an example of the limit point storage unit of the present invention. Holding points are an example of the limit points of the present invention. The CPU unit 100 can execute the pay application 12 when the total value points of the pay application 12 called by the user program 32 do not exceed the holding points held by the CPU unit 100. The point management unit 154 writes the retained point information supplied from the engineering tool 500 into the point storage unit 112. The holding point information includes the holding points assigned to the CPU unit 100 and the serial number of the CPU unit 100.

The executable flag 113 holds a flag value indicating whether or not the CPU unit 100 can execute the pay application 12. The executable flag 113 is realized by the storage unit 110 shown in FIG. This flag value is determined depending on whether or not the possessed points are equal to or greater than the sum of the consideration points of the pay application 12 called by the user program 32. In the execution possibility flag 113 shown in FIG. 2A, a flag value indicating the execution possibility is set by the execution possibility determination unit 152 described later.

(4) The file operation unit 151 writes various program files into the program storage unit 111. The file operation unit 151 is realized by the arithmetic unit 150 and the tool communication unit 160 shown in FIG. The file operation unit 151 stores all or a part of the first library file 10, the second library file 20, and the user program file 30 supplied from the engineering tool 500 in the program storage unit 111. When the engineering tool 500 instructs to delete the specified file in the program storage unit 111, the file operation unit 151 deletes the specified file in the program storage unit 111.

(2) The execution availability determination unit 152 shown in FIG. 2A analyzes the user program file 30 and obtains the total value points of the pay application 12 called by the user program 32. The execution possibility determination unit 152 determines whether or not the possessed points held by the point storage unit 112 is equal to or greater than the total of the obtained consideration points, and sets a value in the execution possibility flag 113 according to the result of the determination. The execution possibility determination unit 152 is realized by the calculation unit 150 illustrated in FIG. 1 executing the program 001 in the storage unit 110. The execution availability determination unit 152 is an example of a determination unit according to the present invention.

2A, when determining that the possessed points are equal to or more than the total value points of the pay application 12, sets the value indicating that the pay application 12 can be executed in the executable flag 113. I do. On the other hand, when determining that the possessed points held by the point storage unit 112 is less than the total of the consideration points of the pay application 12, the execution possibility determination unit 152 executes a value indicating that the execution of the pay application 12 is impossible. The flag is set in the availability flag 113. In the embodiment, if it is determined that the pay application 12 can be executed, the execution determination unit 152 sets the execution determination flag 113 to “1”, which is a value indicating “executable”. When determining that the execution of the pay application 12 is not possible, the execution possibility determination unit 152 sets “0”, which is a value indicating “executable”, in the execution possibility flag 113.

The execution management unit 153 executes the pay application 12 based on the value set in the executable flag 113 when the execution target instruction is an instruction to call the pay application 12 when the user program 32 is executed. Control whether or not to do so. The execution management unit 153 is realized by the calculation unit 150 illustrated in FIG. 1 executing the program 002 in the storage unit 110. The execution management unit 153 is an example of the execution management unit of the present invention.

The execution management unit 153 illustrated in FIG. 2A restricts the execution of the pay application 12 when, for example, the pay application 12 is called and the execution permission flag 113 is set to “0” which is a value indicating “non-execution”. I do. Therefore, the paid application 12 is not executed. On the other hand, when “1” which is a value indicating “executable” is set in the executable flag 113, the execution management unit 153 does not limit the execution of the pay application 12.

(4) The point management unit 154 writes the owned point information supplied from the engineering tool 500 into the point storage unit 112. Further, when the updated holding point information is supplied from the engineering tool 500, the point management unit 154 rewrites the points held by the point storage unit 112.

In the embodiment, the possessed point information is exchanged between the engineering tool 500 and the CPU unit 100 as described below in order to prevent falsification of the possessed point information. The engineering tool 500 encrypts the possessed point information and supplies the encrypted data to the CPU unit 100. The point management unit 154 stores the encrypted possessed point information supplied from the engineering tool 500 in the point storage unit 112. The retained point information is decrypted at the time of the initial processing of the CPU unit 100. When the engineering tool 500 requests the possessed point information of the point storage unit 112, the CPU unit 100 transmits the encrypted possessed point information to the engineering tool 500.

The communication interface 161 communicates with the communication interface 521 of the engineering tool 500. The communication interface 161 outputs the data received from the engineering tool 500 to the file operation unit 151 or the point management unit 154. The communication interface 161 is realized by the tool communication unit 160 shown in FIG.

Next, the engineering tool 500 and the point management server 700 will be described. The engineering tool 500 is a tool that supports development, setting, and the like related to the PLC 1000, and is a device in which a dedicated application is installed on a personal computer. As shown in FIG. 1, the engineering tool 500 is connected to the CPU unit 100 by a communication cable 600 and communicates with the CPU unit 100.

The user creates the user program 32 to be executed by the CPU unit 100 using the engineering tool 500, and writes the created user program 32 into the program storage unit 111 of the CPU unit 100 shown in FIG. 2A. Further, in the embodiment, the user uses the engineering tool 500 to purchase points necessary for executing the pay application 12, which is a pay program component, and uses the purchased points as holding points in the CPU unit 100. You can register. Further, the user can use the engineering tool 500 to write the paid application 12 as a paid program component and the free application 22 as a self-made program component in the program storage unit 111 of the CPU unit 100.

The point management server 700 shown in FIG. 1 manages data relating to points registered in the CPU unit 100. The point management server 700 is, for example, a computer that is located at the origin of a paid program component. The point management server 700 is connected to the engineering tool 500 via the network 800 and communicates with the engineering tool 500. The user accesses the point management server 700 via the engineering tool 500, and purchases points, allocates points to the CPU unit 100, and the like.

The engineering tool 500 has, as a hardware configuration, a storage unit 510 for storing various data, a communication unit 520 for communicating with the CPU unit 100, an input receiving unit 530 for receiving a user's input operation, and outputting an image to a display. And a computing unit 550 for controlling the entire engineering tool 500, and a server communication unit 560 for communicating with the point management server 700. The storage unit 510, the communication unit 520, the input reception unit 530, the display unit 540, and the server communication unit 560 are all connected to the calculation unit 550 via the bus 590, and communicate with the calculation unit 550. .

Storage unit 510 includes a volatile memory and a nonvolatile memory. The storage unit 510 stores various programs and data. The storage unit 510 stores a serial number as identification information of each of the CPU units 100 to be managed.

The communication unit 520 includes a network interface circuit, and communicates with the CPU unit 100 connected by the communication cable 600 under the control of the arithmetic unit 550. For example, the communication unit 520 transmits a program file, various setting parameters, and the like to the CPU unit 100 under the control of the arithmetic unit 550. The input receiving unit 530 includes a mouse, operation keys, and the like, receives an operation input from a user, and outputs a signal indicating the user's operation input to the calculation unit 550. Display unit 540 includes a display, and displays an image based on the signal supplied from operation unit 550 on the display.

Operation unit 550 includes a CPU. The arithmetic unit 550 executes various programs stored in the storage unit 510 to implement various functions of the engineering tool 500. The server communication unit 560 includes a communication interface for communicating with a point management server 700 described below via the network 800.

Next, the point management server 700 will be described. The point management server 700 includes, as a hardware configuration, a storage unit 710 for storing various data, a communication unit 720 for communicating with the engineering tool 500, and a calculation unit 730 for controlling the entire point management server 700. Both the storage unit 710 and the communication unit 720 are connected to the calculation unit 730 via the bus 790, and communicate with the calculation unit 730.

(4) The storage unit 710 includes a volatile memory and a nonvolatile memory. The storage unit 710 stores various programs and data. The communication unit 720 includes a network interface circuit, and communicates with the engineering tool 500 via the network 800 under the control of the arithmetic unit 730. Arithmetic unit 730 includes a CPU. The arithmetic unit 730 executes various programs stored in the storage unit 710 to realize various functions of the point management server 700.

In the embodiment, the point management server 700 realizes each function of the engineering tool 500 in cooperation with the engineering tool 500.

As shown in FIG. 2A, the engineering tool 500 functionally includes a program storage unit 511 that stores various programs, a point storage unit 512 that stores owned points, a communication interface 521 that communicates with the CPU unit 100, A file operation unit 551 for writing files of various programs to the CPU unit 100 and a point management unit 552 for managing possessed points are included.

(3) The program storage unit 511 stores a pay library file 1, a self-made library file 2, a user program file 3, and consideration data 4, as shown in FIG. 3A. The program storage unit 511 is realized by the storage unit 510 illustrated in FIG. The program storage unit 511 is an example of a storage unit according to the present invention.

有 料 The pay library file 1 shown in FIG. 3A includes a pay application 12 which is a pay program component. The pay application 12 is downloaded by a user at a site for providing the pay application 12 via the engineering tool 500. The pay application 12 is a program component in a format executable by the CPU unit 100 and is encrypted data. The pay library file 1 may include the pay application 12 that is not called from the user program 32.

The self-made library file 2 includes a free application 22, which is a self-made program component. The free application 22 is created by a user using a program creation function of the engineering tool 500. Therefore, there is no need to pay for the execution of the free application 22. The user program file 3 includes a user program 32 created by the user.

The consideration data 4 includes data in which consideration points of each of the paid applications 12 downloaded by the user are set. The consideration data 4 is downloaded by the user via the engineering tool 500 at the site where the paid application 12 is provided.

3A, the point storage unit 512 shown in FIG. 2A includes a point management table 5120 storing data on points, as shown in FIG. 3B. The point management table 5120 stores a user ID for identifying a user, the total points owned by the user, the serial number of the CPU unit 100, and the owned points assigned to each CPU unit 100. The point storage unit 512 is realized by the storage unit 710 of the point management server 700 illustrated in FIG. The point storage unit 512 is an example of a storage unit of the present invention.

The communication interface 521 communicates with the communication interface 161 of the CPU unit 100. The communication interface 521 transmits the file output from the file operation unit 551 to the CPU unit 100. The communication interface 521 transmits the owned point information output from the point management unit 552 to the CPU unit 100. The communication interface 521 is realized by the communication unit 520 of the engineering tool 500 shown in FIG.

(2) The file operation unit 551 shown in FIG. 2A writes files of various programs stored in the program storage unit 511 to the CPU unit 100 in accordance with a user's instruction. The file operation unit 551 is realized by the communication unit 520 and the calculation unit 550 shown in FIG.

Specifically, the file operation unit 551 reads the price points of the designated pay application 12 from the price data 4 of the program storage unit 511 shown in FIG. 3A, and stores the file header 11 including the read price point information. create. The file operation unit 551 outputs a file including the paid application 12 and the created file header 11 to the communication interface 521 for transmission to the CPU unit 100 as the first library file 10.

(4) The file operation unit 551 creates the file header 21 including information on the free application 22. The file operation unit 551 outputs a file including the free application 22 and the file header 21 to the communication interface 521 for transmission to the CPU unit 100 as the second library file 20.

(4) The file operation unit 551 creates the file header 31 including information for specifying the pay application 12 which is a pay program component called by the user program 32. The file operation unit 551 outputs a file including the user program 32 and the created file header 31 to the communication interface 521 for transmission to the CPU unit 100 as the user program file 30.

2) The point management unit 552 shown in FIG. 2A manages the retained points stored in the point storage unit 512 in accordance with a user's instruction. The point management unit 552 is realized by the communication unit 520 and the operation unit 550 of the engineering tool 500 illustrated in FIG. 1 and the communication unit 720 and the operation unit 730 of the point management server 700. The point management unit 552 is an example of the updating unit of the present invention.

The functions realized by the point management unit 552 are (1) point registration, (2) point allocation, (3) point writing, (4) point confirmation, and (5) point deletion. Hereinafter, each function will be described in order.

(Point registration)
The point management unit 552 registers the points purchased by the user in the point management server 700 as purchased points of the user. It is assumed that the user has paid in advance the necessary amount for purchasing the required points to the creator of the paid program component, and has acquired a serial code for identifying the user and the purchased points at the time of payment. The point management unit 552 stores the information for identifying the user in the point storage unit 512 in association with the points purchased by the user. Note that in (1) point registration, points cannot be written to the CPU unit 100. Writing of points to the CPU unit 100 is performed by (3) point writing described later.

(4) The user uses the engineering tool 500 to register points in the following procedure. First, the user presses a “to point management screen” button from the menu screen shown in FIG. In response to the user's operation, operation unit 550 of engineering tool 500 displays a login screen for performing user authentication shown in FIG. 6A on display unit 540. The user inputs a user name and a password on the login screen.

The entered user name and password are transmitted from the engineering tool 500 to the point management server 700. The point management server 700 performs an authentication process. If the authentication is successful, the main screen of the point management shown in FIG. 6B is displayed on the display unit 540 of the engineering tool 500. After the user authentication, the point management server 700 is accessed, and the engineering tool 500 and the point management server 700 perform the following processing in cooperation with each other.

の た め For point registration, the user presses the “point registration” button on the main screen. In response to the user's operation, arithmetic unit 550 of engineering tool 500 displays a serial code input screen shown in FIG. 6C on display unit 540. The user inputs the serial code acquired at the time of point purchase on the serial code input screen, and presses the “OK” button. In response to the user's operation, the arithmetic unit 550 requests the contractor name specified from the serial code and the purchased points, and converts the input serial code and the user ID for identifying the user into a server ID. The data is transmitted to the point management server 700 via the communication unit 560. The calculation unit 730 of the point management server 700 transmits the contractor name and the purchased points specified from the received serial code to the engineering tool 500.

When receiving the response from the point management server 700, the calculation unit 550 of the engineering tool 500 displays a point registration screen as shown in FIG. 6D on the display unit 540. The calculation unit 550 displays the contractor name and the purchased points received from the point management server 700 on the point registration screen. It is assumed that the user has pressed the “register” button on the point registration screen. In response to the user's operation, the arithmetic unit 550 transmits the serial code and the user ID for identifying the user to the point management server 700 via the server communication unit 560. The calculation unit 730 of the point management server 700 stores the purchased points identified from the received serial code in association with the user ID in the point storage unit 512 illustrated in FIG. 3B.

(Point allocation)
In addition, the point management unit 552 allocates possessed points to each of the CPU units 100 according to a user instruction. Note that in (2) point allocation, points cannot be written to the CPU unit 100. Writing of points to the CPU unit 100 is performed by (3) point writing described later.

It is assumed that the user presses the “point assignment” button on the main screen shown in FIG. 6B to open the point assignment screen after performing the point registration. In response to the user's operation, the arithmetic unit 550 of the engineering tool 500 requests the point management server 700 to present the purchased points associated with the user ID. The calculation unit 730 of the point management server 700 reads out purchased points associated with the user ID from the point storage unit 512, and transmits the read points to the engineering tool 500. The calculation unit 550 of the engineering tool 500 displays a point assignment screen as shown in FIG. 7A on the display unit 540. The calculation unit 550 displays, on the point assignment screen, a list of purchased points supplied from the point management server 700 and a list of the serial numbers of the CPU units 100 stored in the storage unit 510 as a PLC list.

For example, it is assumed that among the pay applications 12 included in the pay library file 1 shown in FIG. 3A, the CPU unit 100 executes the application 1001, the application 1002, and the application 1003. In this case, the total value points required to execute these applications is 800 points obtained by adding 100 points, 500 points, and 200 points, as shown in the price data 4 shown in FIG. 3A. In this case, the user needs to purchase at least 800 points and allocate at least 800 points to the CPU unit 100 on the point allocation screen shown in FIG. 7A. It is assumed that the user inputs a point to be assigned to each CPU unit 100 and presses a “register” button.

When the user presses the “register” button, the arithmetic unit 550 of the engineering tool 500 registers the serial number for identifying each CPU unit 100 and the input point in association with the user ID so as to register it. Request to. The calculation unit 730 of the point management server 700 stores the points assigned to each of the CPU units 100 in the point storage unit 512 illustrated in FIG. 3B.

(Point writing)
The point management unit 552 writes points to the CPU unit 100 specified by the user. The writing of points to the CPU unit 100 needs to be performed in a state where the engineering tool 500 and the CPU unit 100 to which the points are to be written are connected by the communication cable 600.

In a state where the engineering tool 500 and the CPU unit 100 to which a point is to be written are connected by the communication cable 600, the user opens the point writing screen, so that the "point writing" button is pressed on the main screen shown in FIG. 6B. .

(4) In response to the user's operation, the arithmetic unit 550 of the engineering tool 500 requests the point management server 700 for the data of the possessed points for each CPU unit associated with the user ID. The calculation unit 730 of the point management server 700 reads data of points for each CPU unit 100 associated with the user ID from the point management table 5120 shown in FIG. 3B, and transmits the read data to the engineering tool 500.

When receiving the response from the point management server 700, the calculation unit 550 of the engineering tool 500 displays a point writing screen as shown in FIG. 7B on the display unit 540. The calculation unit 550 displays the possessed points for each CPU unit 100 supplied from the point management server 700 on the point writing screen. Here, it is assumed that the user has selected the PLC 1000 having the CPU unit 100 to which the point is to be written on the screen and pressed the “execute” button. In response to the user's operation, the arithmetic unit 550 of the engineering tool 500 encrypts the possessed point information including the serial number, which is the identification information of the designated CPU unit 100, and the points assigned to the CPU unit 100. , And transmits the encrypted data to the CPU unit 100 via the communication interface 521 in FIG. 2A.

When the arithmetic unit 150 functioning as the point management unit 154 of the CPU unit 100 receives the possessed point information from the engineering tool 500 via the communication interface 161, the computing unit 150 stores the received possessed point information in the point storage unit 112.

(Point confirmation)
The point management unit 552 reads the points owned by the CPU unit 100 connected to the engineering tool 500 from the CPU unit 100 so that the user can check the points written in the CPU unit 100. It is necessary to check the points of the CPU unit 100 in a state where the engineering tool 500 and the CPU unit 100 to which the points are to be written are connected by the communication cable 600.

(6) It is assumed that the user presses the “point confirmation” button on the main screen shown in FIG. 6B with the engineering tool 500 and the CPU unit 100 connected with the communication cable 600. In response to the user's operation, the arithmetic unit 550 of the engineering tool 500 transmits a command for requesting possessed point information to the CPU unit 100 via the communication interface 521.

When receiving the command for requesting possessed point information from the engineering tool 500 via the communication interface 161, the arithmetic unit 150 of the CPU unit 100 converts the possessed point information stored in the point storage unit 112 via the communication interface 161. The data is transmitted to the engineering tool 500. When receiving the possessed point information from the CPU unit 100 via the communication interface 521, the computing unit 550 of the engineering tool 500 decodes the received possessed point information, and decodes the decrypted point and serial number as shown in FIG. 7C. Display on the point confirmation screen.

(Delete points)
When instructed by the user, the point management unit 552 deletes the retained points written in the CPU unit 100 connected to the engineering tool 500. It is necessary to delete the points of the CPU unit 100 in a state where the engineering tool 500 and the CPU unit 100 to which the points are to be written are connected by the communication cable 600.

(6) It is assumed that the user presses the “point delete” button on the main screen shown in FIG. 6B to open the point delete screen in a state where the engineering tool 500 and the CPU unit 100 are connected by the communication cable 600.

In response to the user's operation, the arithmetic unit 550 of the engineering tool 500 transmits a command for requesting possessed point information to the CPU unit 100 via the communication interface 521, and from the CPU unit 100 to the point storage unit 112. Get stored holding point information. The calculation unit 550 of the engineering tool 500 displays a point deletion screen as shown in FIG. The calculation unit 550 displays the point and the serial number on the point deletion screen. The points and the serial number are obtained by decoding the held point information in the point storage unit 112.

When the user presses the “Yes” button on the point deletion screen, the arithmetic unit 550 of the engineering tool 500 transmits a command for instructing the CPU unit 100 to delete points via the communication interface 521.

When the arithmetic unit 150 of the CPU unit 100 receives a command for instructing deletion of a point from the engineering tool 500 via the communication interface 161, the arithmetic unit 150 deletes possessed point information stored in the point storage unit 112. Further, the calculation unit 150 transmits a notification of completion of deletion of the possessed point information to the engineering tool 500 via the communication interface 161.

When receiving the notification of the completion of the deletion of the possessed point information from the CPU unit 100 via the communication interface 521, the arithmetic unit 550 of the engineering tool 500 sends the notification of the point deletion together with the serial number of the corresponding CPU unit 100 to the point management server. Send to 700.

When the arithmetic unit 730 of the point management server 700 receives the notification of the deletion of the point from the engineering tool 500, the arithmetic unit 730 deletes the point assigned to the target serial number in the point storage unit 512 shown in FIG. 3B. The calculation unit 730 may set the point of the target serial number to “0”, for example. The functions realized by the point management unit 552 have been described above.

Hereinafter, a procedure to be performed by the user before executing the user program 32 will be described. First, the user needs to create the user program 32 and the necessary free application 22. For this reason, the user creates the user program 32 using the “create program” menu of the engineering tool 500 shown in FIG. The created user program 32 is stored in the program storage unit 511 shown in FIG. 3A. Further, the user creates the free application 22 with the engineering tool 500 as necessary. The created free application 22 is stored in the program storage unit 511.

When the user program 32 calls the pay application 12, the user needs to download the pay application 12. For this reason, the user presses the “download paid application” button from the menu screen of the engineering tool 500 shown in FIG. In response to the user's operation, the arithmetic unit 550 of the engineering tool 500 accesses the site for providing the pay application 12, and displays a download screen of the pay application as shown in FIG. It is assumed that the user selects the desired paid application 12 and presses a “download” button. In response to the user's operation, operation unit 550 downloads pay application 12 and stores pay application 12 in program storage unit 511. The user may download the paid application 12 that is not called from the user program 32 to the engineering tool 500.

(4) Further, the user needs to write the paid library file 1, the self-made library file 2, and the user program file 3 into the CPU unit 100. For this reason, the user presses a “write data” button from the menu screen of the engineering tool 500 shown in FIG. In response to the user's operation, the arithmetic unit 550 of the engineering tool 500 displays a data writing screen shown in FIG. 9 on the display unit 540. The user selects a desired file from the paid library file 1, the self-made library file 2, and the user program file 3 on the data writing screen, and presses an "execute" button.

When the user presses the “execute” button, the arithmetic unit 550 of the engineering tool 500 functioning as the file operation unit 551 transmits the file specified by the user to the CPU unit 100 via the communication interface 521.

When the pay library file 1 shown in FIG. 3A is selected, the calculation unit 550 creates the file header 11 including the price points of the pay application 12 read from the price data 4. The calculation unit 550 adds the file header 11 to the pay library file 1, creates the first library file 10, and transmits the first library file 10 to the CPU unit 100. As shown in FIG. 2A, the arithmetic unit 150 of the CPU unit 100 functioning as the file operation unit 151 stores the received first library file 10 in the program storage unit 111.

When the self-made library file 2 shown in FIG. 3A is selected, the calculation unit 550 creates the second library file 20 in which the file header 21 is added to the self-made library file 2. The calculation unit 550 transmits the second library file 20 to the CPU unit 100. As shown in FIG. 2A, the calculation unit 150 of the CPU unit 100 functioning as the file operation unit 151 stores the received second library file 20 in the program storage unit 111.

(3) When the user program file 3 shown in FIG. 3A is selected, the arithmetic unit 550 creates the user program file 30 in which an appropriate file header 31 is added to the user program file 3. The arithmetic unit 550 transmits the user program file 30 to the CPU unit 100. As shown in FIG. 2A, the arithmetic unit 150 of the CPU unit 100 functioning as the file operation unit 151 stores the received user program file 30 in the program storage unit 111.

As described above, the execution of the user program 32 in the CPU unit 100 is restricted by the relationship between the holding points registered in the CPU unit 100 and the total value points of the pay application 12 called from the user program 32. . Therefore, as described above, the user needs to perform (1) point registration, (2) point allocation, and (3) point writing using the engineering tool 500.

The above is the procedure to be performed by the user in the CPU unit 100 prior to the execution of the user program 32. Since the above-described procedure is an example, some procedures may be omitted and the procedures may be interchanged.

Next, the arithmetic unit 150 functions as the execution determination unit 152 illustrated in FIG. 2A, and performs processing related to execution determination for determining whether the pay application 12 called from the user program 32 can be executed. explain. The process for determining whether or not execution is possible is executed as part of the initial process of the CPU unit 100.

Therefore, the user needs to turn off the power of the CPU unit 100 and then turn on the power of the CPU unit 100 again. This is for starting the initial processing by the firmware of the CPU unit 100 by turning on the power again. It is assumed that the program writing, (1) point registration, (2) point allocation, and (3) point writing have already been performed. It is assumed that 800 points are registered in the point storage unit 112 in advance. Also, it is assumed that the execution permission flag 113 is set to “0” which is a default value indicating “non-execution”.

イ Initial processing of the CPU unit 100 will be described with reference to FIG. The arithmetic unit 150 initializes various memories of the CPU unit 100 (step S1). The operation unit 150 checks the program file stored in the program storage unit 111 (Step S2). Specifically, the calculation unit 150 checks whether the file stored in the program storage unit 111 among the first library file 10, the second library file 20, and the user program file 30 is damaged.

The calculation unit 150 determines whether the possessed point information is stored in the point storage unit 112 (step S3). If it is determined that the possessed point information is stored in the point storage unit 112 (Step S3; Yes), the arithmetic unit 150 decrypts the possessed point information using the decryption key (Step S4).

The calculation unit 150 determines whether or not the possessed points are valid (step S5). More specifically, if the serial number included in the decrypted holding point information matches the serial number stored in the storage unit 110 of the CPU unit 100, the calculation unit 150 determines that the holding points are valid. Is determined (Step S5; Yes), and the process of Step S6 is executed. On the other hand, if the serial number included in the decrypted holding point information does not match the serial number stored in the storage unit 110 of the CPU unit 100, the calculating unit 150 determines that the holding point is invalid. (Step S5; No), the initial processing ends. At this time, the calculation unit 150 may display an error regarding the owned points on the display unit 140.

If the calculation unit 150 determines in step S3 that the stored point information is not stored in the point storage unit 112 (step S3; No), the processing in step S6 is performed without executing the processing in steps S4 and S5. Execute

The calculation unit 150 determines whether the first library file 10 which is a paid library file is stored in the program storage unit 111 (step S6). When the first library file 10 is stored in the program storage unit 111 (Step S6; Yes), the calculation unit 150 decrypts the first library file 10 that is a paid library file (Step S7).

The calculation unit 150 obtains the total value points of the pay application 12 called by the user program 32 (step S8). Specifically, the calculation unit 150 reads the value points of the pay application 12 called by the user program 32 from the file header 11 of FIG. 2A, and calculates the total value points. For example, when the application program 1001, the application program 1002, and the application program 1003 shown in FIG. 2A are called from the user program 32, the consideration value of the application 1001 is 100 points, the consideration value of the application 1002 is 500 points, and the value of the application 1003 is Since the consideration points are 200 points, the total of the consideration points is 800 points.

Subsequently, the arithmetic unit 150 determines whether or not the possessed points included in the possessed point information decrypted in step S4 are equal to or greater than the sum of the consideration points of the pay application 12 obtained in step S8 (step S9). ). If the calculation unit 150 determines that the possessed points are equal to or greater than the sum of the consideration points (step S9; Yes), the calculation unit 150 sets “1”, which is a value indicating “executable”, to the executable flag 113. (Step S10). For example, assuming that the possessed points are 800 points and the total value points of the paid application 12 called by the user program 32 are 800 points, the arithmetic unit 150 sets the executable flag 113 to “executable” with a value indicating “executable”. A certain “1” is set, and the initial processing ends.

On the other hand, when determining that the possessed points are less than the total of the consideration points (Step S9; No), the arithmetic unit 150 sets “0” which is a value indicating “executable” to the executable flag 113 (Step S9). S11), the initial processing ends. For example, in a case where the owned points are 500 points and the total of the consideration points of the pay application 12 called by the user program 32 is 800 points, the calculation unit 150 determines that the possession points are less than the total of the consideration points. Determine.

{Circle around (5)} If the calculation unit 150 determines in step S5 that the possessed points are not valid (step S5; No), the initial processing ends. Also in this case, the value of the execution permission flag 113 is not changed and remains at the default. At this time, the arithmetic unit 150 may, for example, turn on an indicator lamp of the display unit 140 to notify the user of the error.

After the initial processing is completed, the arithmetic unit 150 sequentially processes each instruction of the user program 32. In the embodiment, the arithmetic unit 150 functions as the execution management unit 153 by processing each instruction of the user program 32 according to the procedure shown in FIG.

As shown in FIG. 11, the arithmetic unit 150 determines whether the CPU unit 100 is in the RUN state (step S21). When the RUN switch of the CPU unit 100 is on, the arithmetic unit 150 determines that the CPU unit 100 is in the RUN state (Step S21; Yes), and executes the process of Step S22. On the other hand, when the RUN switch is not turned on, the arithmetic unit 150 determines that the RUN state is not established (step S21; No), and ends the program execution process. The RUN switch is a hardware switch of the CPU unit 100 and is manually operated by a user.

The operation unit 150 reads the next command of the user program 32 in step S22 (step S22). For example, in the execution of the user program 32 immediately after the initial processing, the first instruction of the user program 32 is read.

The operation unit 150 determines whether the command read in step S22 is a command for calling the pay application 12 in the first library file 10 (step S23).

When determining that the read command is a command for calling the pay application 12 of the first library file 10 (step S23; Yes), the arithmetic unit 150 sets the value of the execution flag 113 to “executable”. It is determined whether it is "1" (step S24).

If it is determined that the value of the executable flag 113 is “1” indicating “executable” (step S24; Yes), the arithmetic unit 150 converts the paid application 12 specified by the instruction read in step S22 into Call (step S25). For example, if the command read in step S22 is a command for calling the application 1002 shown in FIG. 2A, the arithmetic unit 150 calls the application 1002. After that, the arithmetic unit 150 performs the process of step S26.

In step S24, when the value of the execution permission flag 113 is not “1” which is a value indicating “executable”, that is, when the value of the execution permission flag 113 is “0” which is a value indicating “non-execution” ( (Step S24; No), the arithmetic unit 150 executes the processing of step S26 without calling the pay application 12 specified by the instruction read in step S22.

On the other hand, in step S23, when the arithmetic unit 150 determines that the instruction read in step S22 is not an instruction to call the pay application 12 (step S23; No), the arithmetic unit 150 executes the instruction (step S27). For example, when the read instruction is an instruction for calling the free application 22, the arithmetic unit 150 calls the free application 22. After that, the arithmetic unit 150 performs the process of step S26.

(4) In step S26, the arithmetic unit 150 determines whether the next instruction is an END instruction (step S26). When determining that the read instruction is an END instruction (Step S26; Yes), the arithmetic unit 150 executes the processing of the preset END instruction, and thereafter executes the processing from Step S21 again. On the other hand, in step S26, when the arithmetic unit 150 determines that the read instruction is not the END instruction (step S26; No), the processing unit 150 executes the processing from step S22 again.

As described above, when the CPU unit 100 has possessed points equal to or more than the sum of the consideration points of the pay application 12 called from the user program 32, the CPU unit 100 may execute the pay application 12. it can. On the other hand, if the CPU unit 100 does not have the possessed points equal to or greater than the sum of the consideration points of the pay application 12 called from the user program 32, the CPU unit 100 cannot execute any pay application 12. Therefore, when the instruction of the user program 32 is an instruction to call the pay application 12, the CPU unit 100 skips the execution of the instruction.

In the configuration according to the embodiment, the possessed points do not decrease according to the number of times of execution of the application and the execution period. Therefore, the user does not need to monitor the remaining number of owned points while the programmable logic controller is operating. In addition, since the number of retained points does not decrease, the user does not need to purchase additional points due to the shortage of the remaining number. In this way, despite the fact that only the selected program component can be used, there is no need for the user to perform complicated work, and the convenience is high. In addition, the user can continue to execute the pay application 12 within the range of the purchased points. As described above, the execution of the pay application 12 cannot be prevented due to the elapse of the period.

Even if the possessed points are smaller than the sum of the consideration points of the pay application 12, only the call instruction of the pay application 12 is not executed in the user program 32, and the execution of the user program 32 of the CPU unit 100 is interrupted. Never.

Further, for the pay application 12 of the consideration points within the range of the holding points, the CPU unit 100 can execute the pay application 12 indefinitely. As described above, in the embodiment, the pay application 12 is written in the CPU unit 100 in file units. Even if the user program 32 is modified and the combination of the called pay applications 12 is changed, if the sum of the consideration points of the called pay application 12 does not exceed the retained points, the CPU unit 100 deletes the charged application 12. Can be performed. In this case, the user does not need to purchase additional points. Note that the process for determining whether the pay application 12 can be executed is executed as a part of the initial process. Therefore, after the user program 32 is modified, the initial process needs to be executed again.

In the case where the possessed points become insufficient due to the modification or replacement of the user program 32, the user may purchase additional necessary points and register them in the CPU unit 100.

Note that, in the embodiment, the CPU unit 100 describes that the possessed points are written to the CPU unit 100 in the procedure to be performed by the user before the execution of the user program 32 is started. Once written, the point writing procedure is not required as long as it is not necessary to change or delete the owned points.

Further, the engineering tool 500 reads the holding points assigned to the CPU unit 100 from the point storage unit 512 of the CPU unit 100, and calculates the difference between the total of the consideration points of the pay application 12 called in the user program 32 and the holding points. May be displayed on the display unit 540. Therefore, the user can know whether or not the pay application 12 has been called, and can make an adjustment by additionally purchasing points, modifying the user program 32, and the like.

In the embodiment, when the holding points held by the point storage unit 112 are equal to or more than the sum of the consideration points of the pay application 12 called by the user program 32, the execution of the pay application 12 is permitted. In this case, an example has been described in which execution of the pay application 12 is not permitted at all. However, the configuration of the execution restriction of the pay application 12 is not limited to this.

(Modification 1)
Alternatively, information indicating the priority of each pay application 12 may be added to the consideration data 4 in FIG. 3A. FIG. 12 shows an example of data stored in the consideration data 4a to which information indicating the priority is added. In this case, the execution availability determination unit 152 determines whether the paid applications 12 stored in the consideration data 4a can be executed in the order of priority in the process related to the execution availability determination within a range permitted by the holding points. It is determined whether or not. For example, it is assumed that the priorities are defined as shown in FIG. 12 and the possessed points are 700 points. In this case, the execution availability determination unit 152 determines that the applications 1002 and 1003 can be executed according to the priority within the range of the holding points. The execution determination unit 152 determines that the application 1001, the application 1004, and the application 1005 cannot be executed.

Alternatively, it is assumed that the possessed points are 800 points. In this case, the execution possibility determination unit 152 determines that the applications 1001 to 1003 can be executed according to the priority order within the range of the holding points, and the applications 1004 and 1005 cannot be executed. Further, the execution possibility determination unit 152 may store information indicating the execution possibility in the execution possibility data 113a as shown in FIG. FIG. 13 shows information stored in the executable data 113a when the possessed points are 800 points. In FIG. 13, information indicating that the applications 1001 to 1003 can be executed is stored in the execution possibility data 113a. The execution management unit 153 controls whether or not to execute the pay application 12 based on the information indicating whether or not execution is possible, which is stored in the execution possibility data 113a. In this case, the execution enable / disable flag 113 shown in FIG. 2A is unnecessary.

(Modification 2)
Alternatively, instead of setting the consideration points for each of the paid applications 12, the applications may be classified by category, and control may be performed so that the paid application 12 of a predetermined category can be executed according to the number of possessed points. FIG. 14 shows an example of the category table 4b storing data indicating the association between the pay application 12 and the category. In this case, the value data 4 shown in FIG. 3A is unnecessary.

For example, suppose that the possession points of 500 points or more is a condition under which the execution of the category 1 pay application 12 is permitted. It is assumed that the possession points of 800 points or more are the conditions under which the execution of the category 1 and category 2 pay applications 12 is permitted. It is assumed that the holding point of 1200 points or more is a condition under which the execution of the pay applications 12 of the categories 1 to 3, that is, all the pay applications 12 is permitted. It is assumed that data indicating these conditions is stored in the storage unit 110 in advance. Here, it is assumed that the possessed points are 900 points. In this case, the execution availability determination unit 152 determines that the paid application 12 of the category 1 and the category 2 can be executed in the process related to the determination of the availability. From the categories shown in FIG. 14, applications 1002 to 1005 can be executed. The execution possibility determination unit 152 stores information indicating the execution possibility in the execution possibility data 113b as shown in FIG. The execution management unit 153 controls whether or not to execute the pay application 12 based on the information indicating whether or not execution is possible, which is stored in the execution possibility data 113b. In this case, the execution enable / disable flag 113 shown in FIG. 2A is unnecessary.

In the embodiment, the example in which the PLC 1000 includes one CPU unit 100 has been described. However, the PLC 1000 may include two or more CPU units 100. Even in such a case, as shown in FIG. 3B, there is no problem because the holding points are assigned to the serial number of the CPU unit 100.

The CPU unit 100 may operate on two or more virtual machines operating on one information processing device. For example, one of the plurality of CPU units 100 operates on the host machine, and the other CPU units operate on the virtual machine. In this case, the point storage unit 512 may store data in which information for identifying each CPU unit 100 is associated with the possessed points of each CPU unit 100.

In the embodiment, an example has been described in which a program and a program component are written in the CPU unit 100 in file units. However, it is not limited to this. For example, the file operation unit 551 may analyze the user program 32 and write only the pay application 12 called by the user program 32 to the CPU unit 100. In this case, the used capacity of the storage unit 110 is not increased unnecessarily.

In the embodiment, the example in which the arithmetic unit 150 illustrated in FIG. 1 includes an MPU has been described. However, the arithmetic unit 150 includes an ASIC (Application Specific Integrated Circuit) that is an application-specific integrated circuit in addition to the MPU. May be. The operation unit 150 may further include an FPGA (Field Programmable Gate Array).

As described above, as a recording medium for recording a program for causing the operation unit 150 to function as the execution availability determination unit 152 and a program for causing the operation unit 150 to function as the execution management unit 153, a magnetic disk, an optical disk, a magneto-optical disk A computer-readable recording medium including a flash memory, a semiconductor memory, and a magnetic tape can be used.

The present invention is capable of various embodiments and modifications without departing from the broad spirit and scope. Further, the above-described embodiments are for explaining the present invention, and do not limit the scope of the present invention. That is, the scope of the present invention is shown not by the embodiment but by the claims. Various modifications made within the scope of the claims and the equivalents of the invention are considered to be within the scope of the present invention.

1 {paid library file, 2} self-made library file, 3, 30 # user program file, 4, 4a # price data, 4b # category table, 10 # first library file, 11, 21, 31 # file header, 111, 511 # program storage unit, 12, 22 application, 20 second library file, 30, 30A user program file, 32 user program, 100 CPU unit, 110, 510, 710 storage unit, 111 program storage unit, 112, 512 point storage unit, 113 execution enable / disable flag, 113a , 113b {executability data, 120, 520, 720} communication unit, 130, 530 {input reception unit, 140, 540} display unit, 150, 550, 730 {operation unit, 151, 551} File operation unit, 152 execution executable determination unit, 153 execution management unit, 154,552 point management unit, 160 communication unit for tool, 161,521 communication interface, 190, 590, 790 bus, 200 input unit, 300 output unit, 400 Fieldbus, 500 engineering tool, 560 server communication unit, 600 communication cable, 700 point management server, 800 network, 901 detector, 902 controlled equipment, 1000 programmable logic controller, 5120 point management table

Claims (10)

1. A CPU unit of a programmable logic controller,
   Price point storage means for storing, for at least one program component, a price point indicating a price required to execute the program component;
   In the CPU unit, a limit point indicating a limit at which execution of the program component is permitted, the limit point storing a limit point maintained irrespective of the number of times the program component is executed and an execution period of the program component. Storage means;
   If the sum of the consideration points of the selected program part is less than or equal to the limit point, it is determined that the execution of the program part is possible, and the sum of the consideration points exceeds the limit point. A determination unit that determines that execution of the program component is impossible;
   If the determining means determines that the program component can be executed, the program component is executed.If the determining means determines that the program component cannot be executed, the program component is not executed. Execution management means;
   Comprising,
   CPU unit.
2. Program storage means for storing a program to be executed by the CPU unit,
   Further comprising
   The selected program part is the program part called from the program,
   The CPU unit according to claim 1.
3. The limit points include points purchased by the user for payment,
   The CPU unit according to claim 1.
4. When the combination of the selected program components is changed, the determination unit determines whether the limit point is equal to or greater than the total of the consideration points of the program components included in the changed combination. ,
   The CPU unit according to claim 1.
5. Price point storage means for storing, for at least one program component, a price point indicating a price required to execute the program component;
   In the CPU unit, a limit point storage for storing a limit indicating a limit at which execution of the program component is permitted, the limit point being maintained regardless of the number of times the program component is executed and the execution period of the program component. Means,
   If the sum of the consideration points of the selected program part is less than or equal to the limit point, it is determined that the execution of the program part is possible, and the sum of the consideration points exceeds the limit point. A determination unit that determines that execution of the program component is impossible;
   If the determining means determines that the program component can be executed, the program component is executed.If the determining means determines that the program component cannot be executed, the program component is not executed. Execution management means;
   A programmable logic controller having a CPU unit comprising:
6. The CPU unit of the programmable logic controller is
   For the selected program part, the sum of the consideration points, which is the sum of the consideration points indicating the consideration required for the execution of the program part, is a point indicating the limit of execution of the program part in the CPU unit. The number of executions of the program part, and the execution period of the program part, if it is less than or equal to the limit point maintained, it is determined that the execution of the program part is possible, and the sum of the consideration points is Determining that the execution of the program component is impossible if the limit point is exceeded;
   Executing the program component if the execution of the program component is possible;
   How to do.
7. In the CPU unit,
   For the selected program part, the sum of the consideration points, which is the sum of the consideration points indicating the consideration required for the execution of the program part, is a point indicating the limit of execution of the program part in the CPU unit. The number of executions of the program component, and the execution period of the program component, if it is less than or equal to the limit point maintained, it is determined that the execution of the program component is possible, the sum of the consideration points is If the limit point is exceeded, it is determined that the execution of the program component is impossible,
   When the execution of the program component is possible, the program component is executed,
   program.
8. An engineering tool connectable to the CPU unit according to any one of claims 1 to 4,
   Storage means for storing the limit points and the consideration points;
   The limit points stored in the limit point storage means of the CPU unit are updated with the limit points stored in the storage means, and the consideration points stored in the consideration point storage means of the CPU unit are stored in the storage means. Updating means for updating with the consideration points stored by
   Engineering tools with
9. The limit point stored in the storage means is added by a user,
   An engineering tool according to claim 8.
10. Further comprising a display device,
    Displaying, on the display device, a state of execution of the program component by the execution management unit in accordance with the determination of whether the program component is executable by the determination unit;
    The engineering tool according to claim 8.

Images