JP2010277316A - Programmable controller - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a programmable controller that identifies a range affected by a failure of a control program detected in a production site, without using a special server. <P>SOLUTION: The programmable controller 100 includes a first storage part 110 and a use history retrieval part 140. In the first storage part 110, a first circuit block identification code 121 for uniquely identifying a circuit block 102 and a second circuit block identification code 122 for uniquely identifying the circuit block 102 used until the circuit block is created are set in association with each other. The use history retrieval part 140 retrieves data in the first storage part 110 according to the predetermined circuit block identification code. Thereby, the use history retrieval part 140 acquires a circuit block identification code of a circuit block that uses the predetermined circuit block. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a programmable controller capable of managing a control program in the field of equipment control systems used for controlling, for example, factory devices and equipment.

  A control program is used to control the apparatus and system. The control program is composed of a plurality of circuit blocks. On the other hand, if the device or system is modified, the version of the control program is changed accordingly. In the version change, a predetermined circuit block constituting a new control program is created / edited using the existing circuit block so that new code creation is reduced.

  As a method for managing a change history of a sequence program in a programmable controller that manages a control program, for example, Patent Document 1 exists. The technology according to Patent Document 1 discloses a distribution management system that manages a distribution destination using a component management server and includes a trace ID in a binary of a component (circuit block).

JP 2008-22605 A

  However, in the technique according to Patent Document 1, when a defect in the control program in the programmable controller is found in an environment where it is not possible to connect to the component management server, it is not possible to detect the affected range due to the defect on site.

  Further, in the technology according to Patent Document 1, when a part of a control program other than a part that is assumed to be shared among a plurality of programs is diverted, a part management server such as defining a part anew Action on the side is necessary. For this reason, even if a defect is mixed in a control program in another programmable controller that is actually operating, it is difficult to identify and deal with it in the field where there is no management server.

  Accordingly, an object of the present invention is to provide a programmable controller that can identify the range of influence of a malfunction of a control program discovered at a production site or the like without using a special server. To do.

  In order to achieve the above object, a programmable controller according to claim 1 of the present invention is a programmable controller that manages a program composed of a plurality of circuit blocks that are program modules, and is provided for each circuit block. And a diversion history search unit that searches for data in the first storage unit, and the file includes a unique circuit block. A first circuit block identification code for identifying the circuit block and a second circuit block identification code for uniquely identifying the circuit block used until the circuit block is created are set in association with each other. The diversion history search unit searches for data in the first storage unit in accordance with a predetermined circuit block identification code inputted. It allows the predetermined circuit block uniquely determined diverted destination circuit block diverted predetermined circuit blocks from the identification code, obtains the diverted destination circuit block identification code to uniquely determine that.

  Moreover, the programmable controller according to claim 6 of the present invention is a programmable controller that manages a program composed of a plurality of circuit blocks that are program modules, and is created corresponding to each circuit block. A first storage unit for holding a file; and a diversion history search unit for searching for data in the first storage unit. The file includes a first storage unit for uniquely identifying the circuit block. Circuit block identification code, first editing source identification code for uniquely identifying the environment used for editing the circuit block, and editing of the circuit block used until the circuit block is created And a second editing source identification code for uniquely identifying the environment used at the time of The search unit searches the data in the first storage unit according to a predetermined editing source identification code for uniquely identifying an environment in which the predetermined circuit block is edited, and thereby the predetermined circuit A diversion destination circuit block identification code that uniquely determines a diversion destination circuit block that diverts a circuit block created in the same environment as the environment in which the block is edited is acquired.

  In the programmable controller according to claim 1 or 6 of the present invention, the diversion history is stored as information of the identification code in the first storage unit. Further, the diversion history search unit acquires the diversion destination circuit block identification code by searching the data in the first storage unit according to the input predetermined circuit block identification code or the predetermined editing source identification code. .

  Accordingly, it is possible to search for a diversion destination circuit block (a circuit block that needs to be corrected) using the identification code input from the outside and the first circuit block identification code as keys. Therefore, even in an environment such as a site where connection with a special server is not possible, it is possible to perform defect tracking that identifies the range of influence due to a defect.

It is a figure which shows the structure of the programmable controller which concerns on Embodiment 1 and Embodiment 2. FIG. It is a figure for demonstrating the storage mode of the data in a 1st memory | storage part. It is a figure for demonstrating the storage mode of the data in a 1st memory | storage part. 3 is a flowchart for explaining an operation of the programmable controller according to the first embodiment. It is a figure for demonstrating the storage mode of the data in a 1st memory | storage part. 10 is a flowchart for explaining an operation of the programmable controller according to the second embodiment. It is a figure for demonstrating the storage mode of the data in a 1st memory | storage part. FIG. 10 is a diagram illustrating a configuration of a programmable controller according to a third embodiment.

  The present invention relates to a programmable controller that manages a control program. The control program is composed of a plurality of circuit blocks. In addition, when a new control program is created, an existing circuit block is used.

  Hereinafter, the present invention will be specifically described with reference to the drawings showing embodiments thereof.

<Embodiment 1>
FIG. 1 is a block diagram showing a configuration of a programmable controller 100 according to the present embodiment.

  As shown in FIG. 1, the programmable controller 100 manages a plurality of control programs 101. Each control program 101 is composed of a plurality of circuit blocks 102. The programmable controller 100 includes a first storage unit 110, a diversion history search unit 140, and a programmable display (which can be grasped as a display unit) 300.

  Here, the programmable display device 300 functions as a display unit that displays predetermined information so as to be visible from the outside, and when searching for a circuit block that needs to be corrected, an identification code of the defective circuit block is displayed. It also functions as an input unit that can be input from the outside. Note that the input information is transmitted to the diversion history search unit 140.

  The circuit block 102 is a component of the control program 101 and is a so-called program module. In the present application, the program module is referred to as a circuit block 102.

  The circuit block identification code storage unit 110 holds a plurality of files 111. Here, each file 111 is created corresponding to each circuit block 102 managed in the programmable controller 101. For example, if the circuit blocks 102A, 102B, and 102C are managed in the programmable controller 101, the number of files 111 held in the first storage unit 110 is three. That is, the file 111A corresponding to the circuit block 102A, the file 111B corresponding to the circuit block 102B, and the file 111C corresponding to the circuit block 102C.

  In each file 111, a first circuit block identification code 121, a first editing source identification code 131, a second circuit block identification code 122, and a second editing source identification code 132 are set in association with each other. Yes. In the present embodiment, the first circuit block identification code 121 and the second circuit block identification code 122 are general-purpose unique identification codes.

  Here, the first circuit block identification code 121 and the first editing source identification code 131 are identification codes related to the circuit block 102 managed by the file 111 in which these identification codes 121 and 131 are set. . On the other hand, the second circuit block identification code 122 and the second editing source identification code 132 are the circuits in the circuit block 102 managed by the file 111 in which these identification codes 122 and 132 are set. This is an identification code related to the circuit block 102 of the diversion source diverted when creating / editing the block 102.

  Specifically, the first circuit block identification code 121 is an identification code that uniquely identifies the circuit block 102 corresponding to the file 111 in which the first circuit block identification code 121 is set.

  The first editing source identification code 131 is an identification code that uniquely identifies the environment in which the circuit block 102 corresponding to the file 111 in which the first editing source identification code 131 is set is edited. .

  In addition, the second circuit block identification code 122 is a unique identification of the circuit block 202 used until the circuit block 102 corresponding to the file 111 in which the second circuit block identification code 122 is set is created. It is an identification code for identifying.

  The second editing source identification code 132 is the circuit block 202 that has been used until the circuit block 102 corresponding to the file 111 in which the second editing source identification code 132 is set is created. This is an identification code for uniquely identifying the environment.

  For example, it is assumed that the identification code of the circuit block 102A is “102A” and the identification code of the control program development environment 200A in which the circuit block 102A is edited is “200A”. Further, it is assumed that the circuit block 102A is edited by using the circuit block 102A '. It is assumed that the identification code of the diverted circuit block 102A ′ is “102A ′” and the identification code of the control program development environment 200A ′ in which the circuit block 102A ′ is edited is “200A ′”.

  In this case, the following codes 121, 122, 131, 132 are set in the file 111A held in the first storage unit 111 corresponding to the circuit block 102A. That is, in the file 111A, “102A” is set as the first circuit block identification code 121, and “200A” is set as the first editing source identification code 131. Further, in the file 111A, the second “102A ′” is set as the circuit block identification code 122, and “200A ′” is set as the second editing source identification code 131.

  Here, the editing process of the circuit block 102 and the update process of the data held in the first storage unit 110 will be described.

  For example, it is assumed that the control program 101 includes a predetermined circuit block 102X (identification code: 102X), and the circuit block 102X is created in the control program development environment 200X (identification code: 200X). Further, it is assumed that the circuit block 102X is originally created without using any circuit block.

  In this case, “102X” is set as the first circuit block identification code 121 in the file 111 corresponding to the circuit block 102X held in the first storage unit 110, as shown in FIG. “200X” is set as the first editing source identification code 131, and no identification code is set for the second circuit block identification code 122 and the second editing source identification code 132.

  In this situation, it is assumed that the circuit block 102Y is diverted and edited (created) in the control program development environment 200Y (identification code: 200Y). Then, it is assumed that the edited circuit block 102Y is downloaded to the programmable controller 100, and a new control program 101 in which the circuit block 102X is replaced with the circuit block 102Y is newly managed in the programmable controller 100.

  Before the download, in the control program development environment 200Y, an identification code, for example, a UUID (Universally Unique Identifier) is assigned to the circuit block 102Y. Then, along with the download, the control program development environment 200Y transmits the following information to the programmable controller 100.

  That is, the identification code (for example, 102Y) of the circuit block 102Y given above, the start step of the circuit block 102Y, the number of steps of the circuit block 102Y, and the control program development environment 200Y that edited the circuit block 102Y are identified. For example, the ID of the user who was involved in the editing, and the time stamp at the time of the editing.

  The control program development environment 200Y transmits the above information to the programmable controller 100. Then, the file 111 corresponding to the circuit block 102Y as shown in FIG. 3 is newly held in the first storage unit 110 using the file 111 of FIG. That is, “102Y” is set as the first circuit block identification code 121, “200Y” is set as the first editing source identification code 131, “102X” is set as the second circuit block identification code 122, The file 111 in which “200X” is set as the second editing source identification code 132 is newly held in the first storage unit 110.

  In this way, each time the circuit block 102 is edited, a file 111 corresponding to the edited circuit block 102 is newly created and held in the first storage unit 110. Here, as described above, the newly created file 111 includes the file 111 corresponding to the circuit block 102 used in the editing held in the first storage unit 110, and the edited circuit block. It is created using information transmitted when downloading to the programmable controller 100 of 102.

  When a problem is found in a certain circuit block 102, there is a possibility that the problem is also mixed in each circuit block 102 using the circuit block 102. Then, it is necessary to identify each circuit block 102 in which the defect may be mixed as a candidate for the circuit block 102 that needs to be corrected. For this reason, the programmable controller 100 according to the present embodiment includes a diversion history search unit 140.

  For example, it is assumed that the circuit block 102A is diverted, the circuit block 102B is created, the circuit block 102B is diverted, and the circuit block 102C is created. Furthermore, it is assumed that the circuit block 102C is diverted to create the circuit block 102D, and the circuit block 102D is diverted to create the circuit block 102E. Then, it is assumed that a problem is found in the circuit block 102C. In this case, it is necessary to search for the circuit block 102D and the circuit block 102E that have been edited and created using the circuit block 102C as candidates for the circuit block 102 that needs to be corrected.

  When specifying (searching) a candidate for the circuit block 102 that needs to be corrected, the user inputs a predetermined circuit block identification code of the circuit block 102 that has found the defect to the programmable display 300. The programmable display 300 transmits the inputted predetermined circuit block identification code to the diversion history search unit 140. That is, the programmable display 300 inquires the diversion history search unit 140 about a circuit block that needs to be corrected.

  Then, the diversion history search unit 140 searches for data in the first storage unit 110 in accordance with the input predetermined circuit block identification code. As a result, the diversion history search unit 140 uniquely determines the diversion destination circuit block identification code that diverts the circuit block 102 in which the defect uniquely determined from the predetermined circuit block identification code is found. To get.

  Thereafter, the diversion history search unit 140 transmits the acquisition result to the programmable display device 300. And the programmable display 300 displays the diversion destination circuit block uniquely specified from the said diversion destination circuit block identification code so that it can be visually recognized from the outside. Here, in order to display the corresponding diversion destination circuit block from the received diversion destination circuit block identification code, for example, the programmable display 300 has a table indicating the correspondence between the circuit block identification code and the circuit block in advance. Yes. Since the programmable controller 100 manages the correspondence between the circuit block identification code and the circuit block, the programmable controller 100 may convert the corresponding diversion destination circuit block from the diversion destination circuit block identification code.

  Here, the programmable display 300 is taken as an example, but a personal computer or the like in which software capable of displaying a sequence program is installed can be substituted.

  Next, the operation of the programmable controller 100 according to the present embodiment, particularly the operations of the diversion history search unit 140 and the programmable display 300 will be described. FIG. 4 is a flowchart showing operations of the diversion history search unit 140 and the programmable display 300.

  Assume that a failure is found in a predetermined circuit block 102. At this time, the diversion history search unit 140 acquires a predetermined circuit block identification code for uniquely specifying the predetermined circuit block 102 from the programmable display device 300 (step S1).

  Next, the diversion history search unit 140 performs list initialization processing when the diversion destination circuit block identification code is written in the list in a later step (step S2).

  Next, the diversion history search unit 140 searches the data in the first storage unit 110 using the predetermined circuit block identification code acquired in step S1 as a key, and acquires the diversion destination circuit block identification code. Specifically, the diversion history search unit 140 performs the predetermined circuit block identification code and the second circuit block identification set in the file 111 for each file 111 held in the first storage unit 110. It is determined whether or not the code 122 matches (step S3).

  It is assumed that the second circuit block identification code 122 that matches the predetermined circuit block identification code is not set in all the files 111 (“N” in step S3). In this case, the acquisition of the diversion destination circuit block identification code is terminated, and the process proceeds to step S9. As will be described later, in step S9, a list of diversion destination circuit block identification codes (or a list of diversion destination circuit blocks) is transmitted, and in step S10, a list of diversion destination circuit blocks is displayed so as to be visible. In the case of “N” in step S3, the list remains in the state initialized in step S2, so that no diversion destination circuit block is displayed in step S10.

  On the other hand, it is assumed that there is a file 111 in which the second circuit block identification code 122 that matches the predetermined circuit block identification code exists (“Y” in step S3). In this case, the diversion history search unit 140 uses the first circuit block identification code 121 set in the file 111 corresponding to the matching second circuit block identification code 122 as the diversion destination circuit block identification code. (Step S4). Then, the diversion history search unit 140 describes the diversion destination circuit block identification code acquired in step S4 in the list initialized in step S2 (step S5).

  In step S4, the first circuit block identification code 121 is acquired as a diversion destination circuit block identification code. Therefore, the diversion history search unit 140 searches the data in the first storage unit 110 using the first circuit block identification code 121 acquired in step S4 as a key, and uses the diversion destination circuit block identification code. To get. Specifically, the diversion history search unit 140 is set for each file 111 held in the first storage unit 110 in the first circuit block identification code 121 acquired in step S4 and the file 111. It is determined whether or not the second circuit block identification code 122 matches (step S6).

  It is assumed that the second circuit block identification code 122 that matches the first circuit block identification code 121 acquired in step S4 is not set in all the files 111 (“N” in step S6). In this case, the acquisition of the diversion destination circuit block identification code is terminated, and the process proceeds to step S9.

  In step S9, the diversion history search unit 140 transmits a list (or a list of diversion destination circuit blocks) in which the diversion destination circuit block identification code is described in step S5 to the programmable display device 300. Then, the programmable display 300 displays the diversion destination circuit block uniquely identified from the diversion destination circuit block identification code acquired by the diversion history search unit 140 in accordance with the list received from the diversion history search unit 140 in a visible manner. (Step S10).

  On the other hand, it is assumed that there is a file 111 in which the second circuit block identification code 122 that matches the first circuit block identification code 121 acquired in step S4 exists (“Y” in step S6). ). In this case, the diversion history search unit 140 uses the first circuit block identification code 121 set in the file 111 corresponding to the matching second circuit block identification code 122 as the diversion destination circuit block identification code. (Step S7). Then, the diversion history search unit 140 additionally describes the diversion destination circuit block identification code acquired in step S7 in the list (step S8).

  In step S7, the first circuit block identification code 121 is acquired as a diversion destination circuit block identification code. Therefore, the diversion history search unit 140 searches for data in the first storage unit 110 using the first circuit block identification code 121 acquired in step S7 as a key, and uses the diversion destination circuit block identification code. To get. Specifically, the diversion history search unit 140 is set in the first circuit block identification code 121 acquired in step S7 and the file 111 for each file 111 held in the first storage unit 110. It is determined whether or not the second circuit block identification code 122 matches (step S6).

  The diversion history search unit 140 recursively repeats the processing from step S6 to step S8. Here, the first circuit block identification code 121 in the second and subsequent steps S6 in the recursive repetition is the first circuit block identification code 121 acquired in step S7.

  As a result of the recursive repetitive processing in steps S6 to S8, in a certain step S6, the diversion history search unit 140 matches the first circuit block identification code 121 acquired in step S7 in all files 111. Is determined not to be set (“N” in step S6). In this case, the acquisition of the diversion destination circuit block identification code is terminated, and the process proceeds to step S9.

  In step S9, the diversion history search unit 140 transmits a list (or a list of diversion destination circuit blocks) in which the diversion destination circuit block identification codes are described in steps S5 and S8 to the programmable display device 300. . Then, the programmable display 300 displays the diversion destination circuit block uniquely identified from the diversion destination circuit block identification code acquired by the diversion history search unit 140 in accordance with the list received from the diversion history search unit 140 in a visible manner. (Step S10). In other words, the programmable display 300 displays a list of the circuit blocks 102 that need to be corrected so as to be visible.

  As described above, in the programmable controller 100 according to the present embodiment, the diversion relationship of the circuit blocks 102 managed in the programmable controller 100 using the identification code with a small amount of data in the first storage unit 110. keeping. The diversion relationship is a relationship between the first circuit block identification code 121 and the second circuit block identification code 122 in the file 111. Then, in order to identify the diversion destination circuit block (the circuit block that needs to be corrected), the diversion history search unit 140 searches the data in the first storage unit 110 according to the identification code input from the outside. Yes.

  Therefore, it is possible to search for a diversion destination circuit block (a circuit block that needs to be corrected) using the identification code input from the outside and the first circuit block identification code 121 as keys. Therefore, even in an environment such as a site where connection to a special server is not possible, it is possible to perform defect tracking that specifies the range of influence caused by a defect included in the diversion source circuit block.

  In addition, the programmable controller 100 according to the present embodiment includes a programmable display 300 that displays a diversion destination circuit block (a circuit block that needs to be corrected) in a visible manner. Therefore, the user can easily recognize a circuit block that needs to be corrected.

  In step S3, it is also assumed that the “match” determination is made for a plurality of files 111 at a time. In that case, the steps after step S4 in FIG. 4 are performed in parallel for each file 111 that is determined to match. Similarly, it is assumed that “match” is determined for a plurality of files 111 at a time in step S6. In that case, the steps after step S7 in FIG. 4 are performed in parallel for each file 111 that is determined to match.

  In the configuration example of FIG. 1, there is one second circuit block identification code 122 set in the file 111. However, as shown in FIG. 5, in the file 111, one first circuit block identification code 121 and two or more second circuit block identification codes 122 and 123 may be set correspondingly. . Here, FIG. 5 shows two examples of the second circuit block identification codes 122 and 123. In FIG. 5, only a part of the file 111 is shown. The number of second circuit block identification codes set in one file 111 may be appropriately determined according to the capability and resources of the programmable controller 100.

  Assume that a predetermined file 111 corresponding to the predetermined circuit block 102 is held in the first storage unit 110, and the configuration of the predetermined file 111 is the configuration illustrated in FIG. Then, the first circuit block identification code 121 set in the predetermined file 111 is an identification code of the predetermined circuit block 102. Further, the second circuit block identification code 122 set in the predetermined file 111 is an identification code of the first other circuit block 102 diverted when the predetermined circuit block 102 is edited. Further, the second circuit block identification code 123 set in the predetermined file 111 is the identification code of the second other circuit block 102 that was diverted when the first other circuit block 102 was edited. It is.

  In the case of the configuration of FIG. 5, in step S3 of FIG. 4, the diversion history search unit 140 performs the following processing. In other words, the diversion history search unit 140, for each file 111 held in the first storage unit 110, the predetermined circuit block identification code acquired in step S1 and the second circuit set in the file 111. It is determined whether or not the block identification code 122 matches. In addition, the diversion history search unit 140 sets the predetermined circuit block identification code acquired in step S1 and the first file 111 set for each file 111 held in the first storage unit 110. It is determined whether or not the second circuit block identification code 123 matches.

  In the configuration example of FIG. 5, in step S <b> 4 of FIG. 4, the diversion history search unit 140 corresponds to the corresponding second circuit block identification code 122 or 123 and is set in the file 111. The circuit block identification code 121 is acquired as a diversion destination circuit block identification code. Then, the diversion history search unit 140 describes the diversion destination circuit block identification code acquired in step S4 in the list initialized in step S2 (step S5).

  In the configuration example of FIG. 5, in all the files 111, the second circuit block identification code 122 that matches the predetermined circuit block identification code is also the second circuit block identification code 123 that matches the predetermined circuit block identification code. If not (“N” in step S3), the process proceeds to step S9.

  Similarly, in the case of the configuration of FIG. 5, in step S <b> 6 of FIG. 4, the diversion history search unit 140 performs the following processing. In other words, the diversion history search unit 140 is set in the first circuit block identification code 121 acquired in step S4 or step S7 and the file 111 for each file 111 held in the first storage unit 110. It is determined whether or not the second circuit block identification code 122 that is present matches. In addition, the diversion history search unit 140 stores the first circuit block identification code 121 acquired in step S4 or step S7 and the file 111 for each file 111 held in the first storage unit 110. It is determined whether or not the set second circuit block identification code 123 matches.

  In the configuration example of FIG. 5, in step S <b> 7 of FIG. 4, the diversion history search unit 140 is set in the file 111 corresponding to the matching second circuit block identification code 122 or 123. The circuit block identification code 121 is acquired as a diversion destination circuit block identification code. Then, the diversion history search unit 140 additionally describes the diversion destination circuit block identification code acquired in step S7 in the list (step S8).

  In the configuration example of FIG. 5, in all the files 111, the second circuit block identification code 122 that matches the first circuit block identification code 121 is also the second circuit that matches the first circuit block identification code 121. If there is no block identification code 123 (“N” in step S6), the process proceeds to step S9.

  In each file 111, only one first circuit block identification code 121 is set. This is because each file 111 is provided corresponding to each circuit block 102, and the first circuit block identification code 121 corresponds to the file 111 in which the first circuit block identification code 121 is set. This is because the identification code is for the circuit block 102.

  Further, in the present embodiment, the matters for describing the diversion destination circuit block identification code in the list have been described. Here, it is assumed that the same identification code is listed in the list by executing the flowchart of FIG. In this case, the diversion history search unit 140 deletes the duplicate identification code from the list.

<Embodiment 2>
There may be a case where it is doubtful that the circuit block 102 is mixed due to editing work in a certain control program development environment 200. That is, a defect may be mixed into the circuit block 102 due to a defect of the certain control program development environment 200 itself or an editing operation by a specific editing operator who uses the control program development environment 200. The invention created in view of this case is the programmable controller 100 according to the second embodiment.

  The programmable controller 100 according to the second embodiment also has the same configuration as that in FIG. 1, but in the present embodiment, the diversion history search unit 140 performs the following operation.

  That is, the diversion history search unit 140 searches the data in the first storage unit 110 according to the input predetermined edit source identification code. Here, the predetermined editing source identification code is an identification code for uniquely identifying an environment in which a predetermined circuit block 102 that has been found to have a defect is edited. Through the above search, the diversion history search unit 140 uniquely identifies a diversion destination circuit block 102 that diverts the diversion destination circuit block 102 diverted from the circuit block 102 created in the same environment as the environment in which the predetermined circuit block 102 is edited. Get the code.

  Next, the operation of the programmable controller 100 according to the present embodiment, particularly the operations of the diversion history search unit 140 and the programmable display 300 will be described. FIG. 6 is a flowchart showing operations of the diversion history search unit 140 and the programmable display 300.

  Assume that a failure is found in a predetermined circuit block 102. A predetermined control program development environment 200 in which the predetermined circuit block 102 is created is used. At this time, the diversion history search unit 140 acquires a predetermined editing source identification code for uniquely specifying the predetermined program development environment 200 from the programmable display 300 (step S11).

  Next, the diversion history search unit 140 performs list initialization processing when the diversion destination circuit block identification code is written in the list in a later step (step S12).

  Next, the diversion history search unit 140 searches the data in the first storage unit 110 using the predetermined editing source identification code acquired in step S11 as a key, and acquires the diversion destination circuit block identification code. Specifically, the diversion history search unit 140, for each file 111 held in the first storage unit 110, the predetermined editing source identification code and the second editing source identification set in the file 111. It is determined whether or not the code 132 matches (step S13).

  It is assumed that the second editing source identification code 122 that matches the predetermined editing source identification code is not set in all the files 111 (“N” in step S13). In this case, acquisition of the diversion destination circuit block identification code is terminated, and the process proceeds to step S19. As will be described later, in step S19, a list of diversion destination circuit block identification codes (or a list of diversion destination circuit blocks) is transmitted, and in step S20, a list of diversion destination circuit blocks is displayed so as to be visible. In the case of “N” in step S13, the list remains in the state initialized in step S12, and therefore, in step S20, no diversion destination circuit block is displayed.

  On the other hand, it is assumed that the file 111 in which the second editing source identification code 132 that matches the predetermined editing source identification code exists (“Y” in step S13). In this case, the diversion history search unit 140 uses the first circuit block identification code 121 set in the file 111 corresponding to the matching second editing source identification code 132 as the diversion destination circuit block identification code. (Step S14). Then, the diversion history search unit 140 describes the diversion destination circuit block identification code acquired in step S14 in the list initialized in step S12 (step S15).

  In step S14, the first circuit block identification code 121 is acquired as a diversion destination circuit block identification code. Therefore, the diversion history search unit 140 then uses the first editing source identification code 131 indicating the editing environment of the first circuit block identification code 121 acquired in step S14 as a key in the first storage unit 110. And the diversion destination circuit block identification code is acquired. That is, the first editing source identification code 131 set in the file 111 corresponding to the first circuit block identification code 121 acquired in step S14 (hereinafter, the first editing source identification code acquired in step S14). The above search is carried out using “131” as a key.

  Specifically, the diversion history search unit 140 is set to the first editing source identification code 131 acquired in step S14 and the file 111 for each file 111 held in the first storage unit 110. It is determined whether or not the second editing source identification code 132 matches (step S16).

  It is assumed that the second editing source identification code 132 that matches the first editing source identification code 131 acquired in step S14 is not set in all the files 111 (“N” in step S16). In this case, acquisition of the diversion destination circuit block identification code is terminated, and the process proceeds to step S19.

  In step S <b> 19, the diversion history search unit 140 transmits a list (or a list of diversion destination circuit blocks) in which the diversion destination circuit block identification code is described in step S <b> 15 to the programmable display device 300. Then, the programmable display 300 displays the diversion destination circuit block uniquely identified from the diversion destination circuit block identification code acquired by the diversion history search unit 140 in accordance with the list received from the diversion history search unit 140 in a visible manner. (Step S20).

  On the other hand, it is assumed that there is a file 111 in which the second editing source identification code 132 that matches the first editing source identification code 131 acquired in step S14 exists (“Y” in step S16). ). In this case, the diversion history search unit 140 uses the first circuit block identification code 121 set in the file 111 corresponding to the matching second editing source identification code 132 as the diversion destination circuit block identification code. (Step S17). Then, the diversion history search unit 140 additionally describes the diversion destination circuit block identification code acquired in step S17 in the list (step S18).

  In step S17, the first circuit block identification code 121 is acquired as a diversion destination circuit block identification code. The diversion history search unit 140 then uses the first editing source identification code 131 indicating the editing environment of the first circuit block identification code 121 acquired in step S17 as a key in the first storage unit 110. And the diversion destination circuit block identification code is acquired. That is, the first editing source identification code 131 set in the file 111 corresponding to the first circuit block identification code 121 acquired in step S17 (hereinafter, the first editing source identification code acquired in step S17). The above search is carried out using “131” as a key.

  Specifically, the diversion history search unit 140 is set in the first editing source identification code 131 acquired in step S <b> 17 and the file 111 for each file 111 held in the first storage unit 110. It is determined whether or not the second editing source identification code 132 matches (step S16).

  The diversion history search unit 140 recursively repeats the processing from step S16 to step S18. Here, the first editing source identification code 131 in the second and subsequent steps S16 in the recursive repetition is the first editing source identification code 131 acquired in step S17.

  As a result of the recursive repetitive processing in steps S16 to S18, in a certain step S16, the diversion history search unit 140 matches the first editing source identification code 131 acquired in step S17 in all the files 111. Is determined not to be set ("N" in step S16). In this case, acquisition of the diversion destination circuit block identification code is terminated, and the process proceeds to step S19.

  In step S19, the diversion history search unit 140 transmits a list (or a list of diversion destination circuit block) in which the diversion destination circuit block identification code is described in steps S15 and S18 to the programmable display device 300. . Then, the programmable display 300 displays the diversion destination circuit block uniquely identified from the diversion destination circuit block identification code acquired by the diversion history search unit 140 in accordance with the list received from the diversion history search unit 140 in a visible manner. (Step S10). In other words, the programmable display 300 displays a list of the circuit blocks 102 that need to be corrected so as to be visible.

  As described above, in the programmable controller 100 according to the present embodiment, the diversion relationship of the circuit blocks 102 managed in the programmable controller 100 using the identification code with a small amount of data in the first storage unit 110. keeping. The diversion relationship is a relationship among the first circuit block identification code 121, the first editing source identification code 131, and the second editing source identification code 132 in the file 111. Then, in order to identify the diversion destination circuit block (the circuit block that needs to be corrected), the diversion history search unit 140 searches the data in the first storage unit 110 according to the identification code input from the outside. Yes.

  Therefore, it is possible to search for a diversion destination circuit block (a circuit block that needs to be corrected) using the identification code input from the outside and the first editing source identification code 131 as keys. Therefore, even in an environment such as a site where connection with a special server is not possible, it is possible to perform defect tracking that identifies an influence range due to a defect related to editing work of a diversion source circuit block.

  In addition, the programmable controller 100 according to the present embodiment includes a programmable display 300 that displays a diversion destination circuit block (a circuit block that needs to be corrected) in a visible manner. Therefore, the user can easily recognize a circuit block that needs to be corrected.

  In step S13, it is also assumed that the “match” determination is made for a plurality of files 111 at a time. In that case, the steps after step S14 in FIG. 6 are performed in parallel for each file 111 that is determined to match. Similarly, it is also assumed that the “match” determination is made for a plurality of files 111 at a time in step S16. In that case, the steps after step S27 in FIG. 6 are performed in parallel for each file 111 that is determined to match.

  In the configuration example of FIG. 1, there is one second editing source identification code 132 set in the file 111. However, as shown in FIG. 7, in the file 111, one first editing source identification code 131 and two or more second editing source identification codes 132 and 133 may be set correspondingly. . Here, FIG. 7 shows two examples of the second editing source identification codes 132 and 133. In FIG. 7, only a part of the file 111 is illustrated. The number of second editing source identification codes set in one file 111 may be appropriately determined according to the capability and resources of the programmable controller 100.

  Assume that a predetermined file 111 corresponding to the predetermined circuit block 102 is held in the first storage unit 110, and the configuration of the predetermined file 111 is the configuration illustrated in FIG. Then, the first editing source identification code 131 set in the predetermined file 111 is an identification code of the environment in which the predetermined circuit block 102 is edited. In addition, the second editing source identification code 132 set in the predetermined file 111 is an environment in which the first other circuit block 102 used for editing the predetermined circuit block 102 is edited. It is an identification code. Further, the second editing source identification code 133 set in the predetermined file 111 is edited in the second other circuit block 102 that is used when the first other circuit block 102 is edited. It is an identification code of the environment.

  In the case of the configuration of FIG. 7, in step S <b> 13 of FIG. 6, the diversion history search unit 140 performs the following processing. That is, the diversion history search unit 140 sets the predetermined editing source identification code acquired in step S11 and the second editing set in the file 111 for each file 111 held in the first storage unit 110. It is determined whether or not the original identification code 132 matches. In addition to this, the diversion history search unit 140 sets the predetermined edit source identification code acquired in step S11 and the first file 111 set for each file 111 held in the first storage unit 110. It is determined whether or not the second editing source identification code 133 matches.

  In the configuration example of FIG. 7, in step S14 of FIG. 6, the diversion history search unit 140 is set in the file 111 corresponding to the matching second editing source identification code 132 or 133. The circuit block identification code 121 is acquired as a diversion destination circuit block identification code. Then, the diversion history search unit 140 describes the diversion destination circuit block identification code acquired in step S14 in the list initialized in step S12 (step S15).

  In the configuration example of FIG. 7, in all the files 111, the second editing source identification code 132 that matches the predetermined editing source identification code is also the second editing source identification code 133 that matches the predetermined editing source identification code. If not (“N” in step S13), the process proceeds to step S19.

  Similarly, in the case of the configuration of FIG. 7, in step S16 of FIG. 6, the diversion history search unit 140 performs the following processing. In other words, the diversion history search unit 140 is set in the first editing source identification code 131 acquired in step S14 or step S17 and the file 111 for each file 111 held in the first storage unit 110. It is determined whether or not the second editing source identification code 132 matches. In addition, the diversion history search unit 140 stores the first editing source identification code 131 acquired in step S14 or step S17 and the file 111 for each file 111 held in the first storage unit 110. It is determined whether or not the set second editing source identification code 133 matches.

  In the configuration example of FIG. 7, in step S <b> 17 of FIG. 6, the diversion history search unit 140 corresponds to the matching second editing source identification code 132 or 133 and is set in the file 111. The circuit block identification code 121 is acquired as a diversion destination circuit block identification code. Then, the diversion history search unit 140 additionally describes the diversion destination circuit block identification code acquired in step S17 in the list (step S18).

  In the configuration example of FIG. 7, in all the files 111, the second editing source identification code 132 that matches the first editing source identification code 131 acquired in step S14 or S17 is also acquired in step S14 or S17. If there is no second editing source identification code 133 that matches the one editing source identification code 131 (“N” in step S16), the process proceeds to step S19.

  In each file 111, only one first editing source identification code 131 is set. This is because each file 111 is provided corresponding to each circuit block 102, and the first editing source identification code 131 corresponds to the file 111 in which the first editing source identification code 131 is set. This is because the circuit block 102 is the identification code of the edited environment.

  Further, in the present embodiment, the matters for describing the diversion destination circuit block identification code in the list have been described. Here, it is assumed that the same identification code is listed in the list by executing the flowchart of FIG. In this case, the diversion history search unit 140 deletes the duplicate identification code from the list.

<Embodiment 3>
FIG. 8 is a block diagram showing a configuration of programmable controller 100 according to Embodiment 3 of the present invention.

  In the first embodiment, UUIDs (universal unique identification codes) are employed as the identification codes 121, 122, and 123 of the circuit block 102 in order to ensure that they are globally unique. Here, since the general-purpose unique identification code is an identification code that is uniquely specified globally, the data amount of the general-purpose unique identification code increases. Therefore, in order to store a plurality of general-purpose unique identification codes having a large amount of data, the first storage unit 110 requires a very large storage capacity.

  However, the programmable controller 100 generally has limited storage capacity resources. Therefore, if a general-purpose unique identification code having a large amount of data is stored in the first storage unit 110, the program storage area in the programmable controller 100 may be compressed.

  Therefore, it is desirable to employ an identification code having a small data amount stored in the first storage unit 110. Therefore, in the programmable controller 100 according to the present embodiment, the first storage unit 110 stores the first and second circuit block identification codes 121 and 122 which are unique identification codes. Here, the unique identification code is an identification code that can be identified only within the programmable controller 100. Since it is sufficient that the unique identification code can be identified only within the programmable controller 100, the data amount is smaller than a general-purpose unique identification code that is globally unique (that is, unique in all systems).

  On the other hand, when searching for candidates for the circuit block 102 that needs to be corrected, a general-purpose unique identification code is input from the programmable display 300 as the identification code of the circuit block 102 in which the defect has occurred. Further, when outputting the search result from the diversion history search unit 140 to the programmable display device 300, the diversion history search unit 140 requires a general-purpose unique identification code.

  Therefore, the programmable controller 100 according to the present embodiment requires a function for realizing mutual conversion between the general-purpose unique identification code and the unique identification code. Therefore, the programmable controller 100 according to the present embodiment includes an identification code conversion unit 150 and a second storage unit 160 in addition to the configuration shown in FIG.

  The second storage unit 160 stores an identification code conversion table indicating the correspondence between the general-purpose unique identification code and the unique identification code. Specifically, the identification code conversion table represents a correspondence relationship between a circuit block identification code that is a general-purpose unique identification code and a circuit block identification code that is a unique identification code. Then, the identification code conversion unit 160 uses the identification code conversion table from the general-purpose unique identification code (or unique identification code) input from the diversion history search unit 140, and uses the unique identification code (or general-purpose unique identification code). The identification code conversion process is performed for conversion to (1).

  In the present embodiment, the first storage unit 110 stores a first circuit block identification code 121 and a second circuit block identification code 122 which are unique identification codes.

  Next, the operation of the programmable controller 100 according to the present embodiment will be described.

  The user knows that a problem has occurred in the predetermined circuit block 102, and the user inputs the predetermined circuit block identification code of the predetermined circuit block 102 into the programmable display 300. Here, the predetermined circuit block identification code is a general purpose unique identification code. Then, in FIG. 8, a predetermined circuit block identification code that is the general purpose unique identification code is transmitted from the programmable display device 300 to the diversion history search unit 140.

  When a predetermined circuit block identification code that is a general-purpose unique identification code is input, the diversion history search unit 140 sends the input predetermined circuit block identification code that is a general-purpose unique identification code to the identification code conversion unit 150. Send.

  Then, the identification code conversion unit 150 uses the identification code conversion table stored in the second storage unit 160 to convert the predetermined circuit block identification code that is a general-purpose unique identification code into the predetermined circuit block that is a unique identification code. Convert to identification code. Thereafter, the identification code conversion unit 150 transmits a predetermined circuit block identification code which is the converted unique identification code to the diversion history search unit 140.

  Then, the diversion history conversion unit 140 performs the same operation described in the first embodiment. That is, the diversion history conversion unit 140 searches the data in the circuit first storage unit 110 according to the predetermined circuit block identification code that is the received unique identification code. Thereby, the diversion destination circuit block identification code which is the unique identification code is acquired.

  Now, it is assumed that the diversion history conversion unit 140 acquires a list of diversion destination circuit block identification codes, which are unique identification codes, as a result of the search process. Then, the diversion history search unit 140 transmits the diversion destination circuit block identification code, which is the acquired unique identification code, to the identification code conversion unit 150.

  Next, the identification code conversion unit 150 uses the identification code conversion table stored in the second storage unit 160 to convert the diversion destination circuit block identification code, which is a unique identification code, into the diversion destination circuit, which is a general-purpose unique identification code. Convert to block identification code. After that, the identification code conversion unit 150 transmits the diversion destination circuit block identification code, which is the converted general-purpose unique identification code, to the diversion history search unit 140.

  Finally, the programmable display 300 uses the diversion uniquely identified from the diversion destination circuit block identification code in accordance with the list of diversion destination circuit block identification codes, which are general-purpose unique identification codes, acquired from the diversion history search unit 140. The previous circuit block is displayed so as to be visible.

  As described above, the programmable controller 100 according to the embodiment of the present invention further includes the second storage unit 160 that holds the identification conversion table. Furthermore, the programmable controller 100 also includes an identification code conversion unit 150 that performs an identification code conversion process between the unique identification code and the general-purpose unique identification code using the identification code conversion table. The first storage unit 110 stores a first circuit block identification code 121 and a second circuit block identification code 122 which are unique identification codes.

  Thus, by providing the identification code conversion unit 150 and the second storage unit 160, the first storage unit 110 includes the first circuit block identification code 121 and the first identification code, which are unique identification codes with a small amount of data. The second circuit block identification code 122 can be stored. Therefore, even if a plurality of files 111 are stored in the first storage unit 110, the storage capacity of the first storage unit 110 can be prevented from greatly increasing.

  In the above description, the present embodiment is applied to the first embodiment. However, this embodiment can also be applied to the second embodiment.

  That is, in the first storage unit 110, the first editing source identification code 131 and the second editing source identification code 132 are also stored in a unique identification code format with a small amount of data. The second storage unit 160 stores a first identification code conversion table and a second identification code conversion table. Here, the first identification code conversion table represents the correspondence between the circuit block identification code that is a general-purpose unique identification code and the circuit block identification code that is a unique identification code. On the other hand, the second identification code conversion table represents the correspondence between the editing source identification code, which is a general-purpose unique identification code, and the editing source identification code, which is a unique identification code.

  Then, the identification code conversion unit 150 uses the second identification code conversion table in the second storage unit 160 to convert a predetermined editing source identification code that is a general-purpose unique identification code into a predetermined editing source that is a unique identification code. Convert to identification code. Thereafter, a diversion destination circuit block identification code, which is a unique identification code, is obtained by the operation described in the second embodiment. Thereafter, the identification code conversion unit 150 uses the first identification code conversion table in the second storage unit 160 to convert the diversion destination circuit block identification code, which is a unique identification code, into a diversion destination circuit block, which is a general-purpose unique identification code. Convert to identification code.

  DESCRIPTION OF SYMBOLS 100 Programmable controller, 101 Control program, 102 Circuit block, 110 1st memory | storage part, 111 file, 121 1st circuit block identification code, 122,123 2nd circuit block identification code, 131 1st editing origin identification code 132, 133 Second edit source identification code, 140 diversion history search unit, 150 identification code conversion unit, 160 second storage unit, 200 control program development environment, 300 programmable display.

Claims (12)

A programmable controller that manages a program composed of a plurality of circuit blocks that are program modules,
A first storage unit for holding a file created corresponding to each circuit block;
A diversion history search unit for searching for data in the first storage unit;
With
The file contains
A first circuit block identification code for uniquely identifying the circuit block;
A second circuit block identification code for uniquely identifying a circuit block diverted until the circuit block is created,
Are set in correspondence,
The diversion history search unit
A diversion destination circuit block that diverts a predetermined circuit block uniquely determined from the predetermined circuit block identification code by searching for data in the first storage unit according to an input predetermined circuit block identification code , To acquire the diversion destination circuit block identification code uniquely determined,
A programmable controller characterized by that. When the predetermined circuit block identification code is acquired from the outside, the diversion history search unit,
(A) For each of the files, determine whether the predetermined circuit block identification code and the second circuit block identification code match,
(B) When it is determined that they match in (A), the first circuit block identification code set in the file corresponding to the matching second circuit block identification code is used as the diversion destination circuit. Get as block identification code,
The programmable controller according to claim 1. The diversion history search unit
(C) For each of the files, determine whether the first circuit block identification code and the second circuit block identification code match,
(D) When it is determined in (C) that they match, the first circuit block identification code set in the file corresponding to the matching second circuit block identification code is used as the diversion destination circuit. Obtained as a block identification code
The first circuit block identification code in (C) is
The first circuit block identification code acquired in (B).
The programmable controller according to claim 2. The diversion history search unit
The processes (C) and (D) are repeated,
The first circuit block identification code in (C) in the second and subsequent repetitions is
It is the first circuit block identification code acquired in (D),
The programmable controller according to claim 3. The diversion history search unit
In (A) or (C), when the match is not recognized in all the files, the process of obtaining the diversion destination circuit block identification code is terminated.
The programmable controller according to any one of claims 2 to 4, wherein the programmable controller. A programmable controller that manages a program composed of a plurality of circuit blocks that are program modules,
A first storage unit for holding a file created corresponding to each circuit block;
A diversion history search unit for searching for data in the first storage unit;
With
The file contains
A first circuit block identification code for uniquely identifying the circuit block;
A first editing source identification code for uniquely identifying the environment used when editing the circuit block;
A second editing source identification code for uniquely identifying the environment used in editing the circuit block diverted until the circuit block is created,
Are set in correspondence,
The diversion history search unit
The predetermined circuit block is edited by searching the data in the first storage unit according to a predetermined editing source identification code for uniquely identifying an environment in which the predetermined circuit block is edited. Obtain a diversion destination circuit block identification code that uniquely determines a diversion destination circuit block that diverts a circuit block created in the same environment as
A programmable controller characterized by that. When the predetermined editing source identification code is acquired from the outside, the diversion history search unit,
(K) For each of the files, determine whether the predetermined editing source identification code and the second editing source identification code match,
(L) When it is determined in (K) that they match, the first circuit block identification code set in the file corresponding to the matching second editing source identification code is used as the diversion destination circuit. Get as block identification code,
The programmable controller according to claim 6. The diversion history search unit
(M) For each of the files, determine whether the first editing source identification code and the second editing source identification code match,
(N) When it is determined in (M) that they match, the first circuit block identification code set in the file corresponding to the matching second editing source identification code is used as the diversion destination circuit. Obtained as a block identification code
The first editing source identification code in (M) is
The first editing source identification code set in the file corresponding to the first circuit block identification code acquired in (L),
The programmable controller according to claim 7. The diversion history search unit
The processes (M) and (N) are repeated,
The first circuit block identification code in (M) after the second repetition is the following:
The first circuit block identification code acquired in (L),
The programmable controller according to claim 8. The diversion history search unit
In (K) or (M), when the match is not recognized in all the files, the process of obtaining the diversion destination circuit block identification code is terminated.
The programmable controller according to any one of claims 7 to 9, wherein: A display unit that displays the diversion destination circuit block uniquely identified from the diversion destination circuit block identification code acquired by the diversion history search unit, so as to be visible;
The programmable controller according to claim 1 or 6, wherein the programmable controller. A second storage unit that holds an identification code conversion table indicating a correspondence relationship between a unique identification code that can be identified only inside the programmable controller and a general-purpose unique identification code;
An identification code conversion unit that performs an identification code conversion process between the unique identification code and the universal unique identification code using the identification code from the diversion history search unit and the identification code conversion table; And
In the first storage unit,
The first circuit block identification code and the second circuit block identification code, which are the unique identification code, or the first circuit block identification code and the first editing source identification, which are the unique identification code The code and the second editing source identification code are stored;
The programmable controller according to claim 1 or 6, wherein the programmable controller.

Images