JP6520241B2 - Control system, its management server device, support device - Google Patents

Description

  The present invention relates to a support device that creates a control device program and a control system that includes a server device that manages the program.

  When the programmable controller is in the stopped state, it is generally possible to download the program created by the programming support device (hereinafter referred to as a support device) as it is. Therefore, when a plurality of engineers update the program for one controller, there is a problem that the program is overwritten. In the invention of Patent Document 1, a method for detecting that the program update is performed by another support device is proposed. It is done.

  Also, for the program update in the operating state of the controller, connect the support device to the controller, check that the project of the support device and the project in the controller match by collation, and then make the change in that state. The method of downloading to the controller is taken. Moreover, in the invention of Patent Document 2, a method is proposed in which the change can be made off-line by using an identifier to guarantee that the program in operation is changed.

Here, conventionally, for example, a configuration as shown in FIG. 9, that is, a configuration in which a management server 70 is further provided in addition to the support device 50 and the PLC 60 is known.
In the support device 50, a program for any PLC (programmable controller) is arbitrarily created by the user (program developer or the like). The support device 50 has a user support function for program creation. The created program for PLC (control program etc.) is downloaded from the support device 50 to the PLC 60, and the PLC 60 stores and executes the program for PLC to control various control target devices (not shown).

  After that, at any time, in the support device 50, the user may update the created PLC program (such as creating a version upgrade version). It is necessary to create an updated version based on the program for PLC currently stored and executed in the PLC 60.

  Here, basically, all the updated versions are stored in the support device 50. For example, in the case where a certain PLC program has been upgraded to a first version, a second version, a third version, a fourth version, a fifth version, etc., all of these are stored in the support device 50. Then, if it is in a state where the program of the 5th version is stored and operated in the PLC 60, the next upgraded version needs to be created based on the program of the 5th version. However, there are cases in which the version is too large for the user to manage.

  The management server 70 has been provided for this problem. The management server 70 holds the illustrated project management information 71. The project management information 71 stores the project of the PLC program currently stored and executed by each PLC. However, this is manually registered one by one every program update.

  Note that the project is, for example, a folder etc., which includes the source code of the program for PLC (control program etc.) and the machine language object etc. formed by compiling this source code as an entity. Not exclusively.

  And when updating the program of arbitrary PLC60, a user performs operation which acquires the project according to this PLC60 from the project management information 71, and preserve | saves it in the assistance apparatus 50 first. Then, create an updated source code from the source code of this project. If normal, in the situation where control is executed by the program of the 5th edition on the PLC 60 side, the project management information 71 should store the project of the 5th edition, and its source code (source code of the 5th edition) The updated (sixth) source code will be created based on. This can prevent, for example, a situation where an updated version of the source code is accidentally created based on the 4 versions of the source code.

  The support device 50 manages a set of programs for PLC and its management information as a project. That is, in the support device 50, the user creates source code of an arbitrary program for PLC. The compiler function of the support device 50 converts this source code into a machine language object which is a form executable by PLC. The support device 50 collectively manages the source code, the machine language object, and the set of management information as a project. The management information is, for example, the folder name of the folder in which the project is stored (Pri01, Pri01 ', PriXX, etc. in the figure), etc., but it is not limited to this example. Then, the folder is transferred to the management server 70 and is overwritten and stored in the project management information 71.

  The user of each support device 50 manually performs registration / update of the project in the project management information 71. Basically, every time the user of the optional support apparatus 50 updates the program of the PLC 60, this project is transferred to the management server 70, and the project corresponding to the PLC 60 in the project management information 71 is updated to the latest version. Make the program's project (that is, currently stored in PLC 60) update.

  However, it is not limited to this example. Although the above description is premised on the case where the management server 70 and the support apparatus 50 can communicate via a network or the like, the present invention is not limited to this example. In some cases, the management server 70 and the support device 50 can not communicate with each other. In the case of such a configuration, for example, in the manual project registration work for the project management information 71, the user copies the updated version of the project from the support device 50 to a portable storage medium (such as a memory card). Then, the portable storage medium is taken to the management server 70 and connected to the management server 70. Then, in this state, the updated version project stored in the portable storage medium is stored in the project management information 71.

  In addition, when acquiring a project registered in the project management information 71, the project is copied to the portable storage medium, and the portable storage medium is held up to the support apparatus 50 to support the support apparatus 50. Is connected to the support device 50.

  In addition, as for the program update of PLC60, a user produces the source code of arbitrary update versions, this is converted into the said machine language object, this machine language object is downloaded to PLC60, and the existing machine language object is substituted. Is realized.

  The management of the PLC program is not limited to the above example, and may be managed using a configuration management tool as represented by, for example, VSS (Microsoft Visual SourceSafe) of Windows. Absent. A configuration management tool such as VSS can manage the latest verified project to be downloaded.

  However, regardless of which method is used, after all, a person manually performs registration and update of a project in the project management information 71, and even if the person who manages the project and the person who updates the program are different. Yes, mistakes can occur. For example, despite the work to update the program of PLC 60 from 4th edition to 5th edition, 4th edition project is registered in project management information 71 because the project management information 71 is forgotten to update afterwards It will be in the state of being done.

  Therefore, when the user subsequently acquires a project from the project management information 71 for program update, a 4-version project is acquired, and an updated version of the source code is created based on the 4-version source code. It will be done.

  Alternatively, the program held by the PLC 60 may disappear due to any cause. In this case, by downloading the machine language object of the project of the project management information 71 to the PLC 60, the program is to be restored, but in the above situation, for the PLC 60 operated by the program of the 5th version, Four versions of the program will be downloaded.

  In the above situation, if the project being managed differs from the project that is actually operating on the controller, if the program is changed on the project being managed, for example, due to facility changes or failure measures, Problems such as the project changed to the controller can not be downloaded properly.

JP, 2008-282362, A JP, 2013-168031, A

  As described above, in the prior art, it is necessary to make the project registered in the management server 70 coincide with the program held and operated by the controller (PLC 60). Every time an update is performed, it is necessary for the user to securely perform the registration work with the management server 70 manually. However, in general, there is a mistake in what the user does manually.

  For example, in the prior art of FIG. 9, the project management operation and the program update operation are executed as independent functions without being interlocked with each other. Therefore, although the verified project is registered in the management server 70, the program update of the PLC 60 is performed in a project different from the managed project, or the project acquired from the management server 70 in the support device 50 is It is possible to edit and update the program of the PLC 60.

  Also, in such a case, in order to match the program in the controller with the program of the managed project, it is necessary for the user to re-register the project for which the program has been updated with the management server 70. There is a problem that it is easy to forget or to make a mistake, and a project managed by the management server 70 tends to be in a state where it does not match the program running on the controller.

  Further, in the field of PCs and the like, there is a method of registering a program in a server and distributing the program directly from a server to a terminal or the like via a network. This corresponds to direct distribution of a program (machine language object) from the management server 70 to the PLC 60 via the network. However, in the field of control systems, it is not only undesirable for security to transmit the program itself on the network, but in the case of a low speed network etc. there is also the problem of performance degradation due to oppressing bandwidth if the program size is large. .

In the control system, there is a configuration in which a plurality of PLCs are connected to the low speed network, and when using the above method, the management server 70 is also connected to the low speed network.
Therefore, in the control system, at a place where the controller is installed, the program is most often updated by directly connecting the support device and the controller with a cable or the like and downloading the program from the support device to the controller. It is difficult to apply the method of direct delivery from the server.

  The object of the present invention is to enable the management server apparatus side to reliably manage a program on the control apparatus side with respect to a control system having a support apparatus that creates a program of the control apparatus and a management server apparatus that manages this program. It is providing a control system, its management server, a support device, etc.

The control system of the present invention comprises a control unit for executing stored programs for controlling the control target device, a support device in which the program of the control device is created / edited, and a management server apparatus.
The management server device has the following means.

Program information storage means in which a program is registered in association with each control device;
· When there is a request for registration of a program of an arbitrary control device optionally created / edited in the support device, the program requested to be registered is stored as a program corresponding to the arbitrary control device in the program information storage unit Registration means;
Registered information giving means for giving predetermined registered information to the registration requested program registered in the program information storage means by the registration means:
Further, the support device has permission determination means for prohibiting the update of the program of the arbitrary control device by the program to which the registered information is not added.

  According to the control system of the present invention, the management server thereof, the support apparatus, etc., the management server apparatus side has a control system having a support apparatus for creating a program of the control apparatus and a management server apparatus for managing a project of this program. Ensure that the program on the control device side can be managed.

It is a block diagram of the control system of this example. It is a functional block diagram of a control system of this example. It is a processing flowchart figure at the time of registration in a management server. It is a flowchart figure of the program update confirmation process in a management server. It is a processing flowchart figure concerning the project reissue in a management server. It is a flowchart figure of the program update confirmation process (online) in a management server. It is a processing flowchart figure at the time of compilation in a support device. It is a processing flowchart figure at the time of download in a support device. It is a block diagram of the conventional control system.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram of a control system of this example.
The control system of this example comprises each PLC (programmable controller) 1, a support device 10, a management server 30, and the like.

  Data exchange between the support apparatus 10 and the management server 30 may be carried out via a network or may be carried out via a portable storage medium, as in the above-mentioned prior art. . However, in the present description, basically, the configuration will be described on the assumption that data is transmitted and received between the support apparatus 10 and the management server 30 via the network.

The PLC 1 is an example of a control device, and is not limited to this example, and may be a DCS (distributed control system) or the like.
In the configuration of FIG. 1, when an instruction to download an arbitrary project (its machine language object) is given to the PLC 1, the support device 10 does not permit the download if at least the update information file 20 is not attached to the project. . Further, even when the update information file 20 is added, the download may not be permitted if the predetermined condition based on the contents of the update information file 20 is not satisfied.

  When an arbitrary project is registered in the management server 30, the management server 30 gives the update information file 20 to the project. For example, when an arbitrary project is sent together with a registration request from an arbitrary support device 10, the management server 30 registers this project in its own device, and adds an update information file 20 to this project. Reply to the request source support device 10.

  As described above, conventionally, programs for PLC (source code, machine language object) and the like are collectively managed as a project. From this, the project may be regarded as a program for PLC as an entity.

  Further, in the support apparatus 10, when the user edits an arbitrary project and an updated version of the project is generated, the update information file 20 is deleted. This is because when the user performs desired editing work on the source code based on any project to which the update information file 20 is added to create an arbitrary update source code, Compile source code and generate updated version of machine language object. This may be regarded as the generation of a new (updated version) project by the above-mentioned updated version source code, updated version machine language object and the like by the editing operation.

  Here, as described above, the update information file 20 is added to an arbitrary project as an editing source, and the update information file 20 is transferred to the update version project generated based on the update information file 20. Since it is in the assigned state, the update information file 20 is deleted. If the update information file 20 is not deleted, the update version project can be downloaded to the PLC 1 without being registered in the management server 30.

  The timing at which the update information file 20 is deleted is, for example, not when the above-mentioned updated version source code is generated but when the above-mentioned updated version machine language object is generated. Since it is a machine language object that is downloaded to the PLC 1, it is considered that there is no particular problem even if the downloadable machine language object is generated before the update version machine language object generation. However, this is an example and it is not limited to this example.

As described above, when a new updated project is generated, the updated information file 20 is not attached to the updated project.
Although it is assumed that the “editing” (the editing operation) shown in the drawing includes the compilation processing, the present invention is not limited to this example.

  Even if there is an instruction / instruction to download a project (its machine language object) in a state where the update information file 20 is not attached to the controller (PLC 1), the support device 10 does not permit it.

  For this reason, the user registers the generated updated version project in the management server 30, for example, manually as in the conventional case. The management server 30 registers the project itself (source code, machine language object, etc.) in the project management information table 40 each time there is a request for registration of an arbitrary project. Furthermore, predetermined information on this project is also registered in the project management information table 40 together. Then, the update information file 20 is assigned to the project requested to be registered.

  As a result, for example, the update information file 20 is added to the above-mentioned updated version project by the management server 30, so this time, the support device 10 downloads the updated version project (its machine language object) to PLC1. To give permission.

  As a result, even if the project registration itself to the management server 30 is manually performed by the user as in the conventional case, the program download to the controller is not permitted if the user forgets to register. Therefore, for example, when the user forgets to register the updated version project in the management server 30, a situation such as “The updated version project is held in the controller but managed in the old version project on the management server 30 side” You can prevent it from happening. In other words, even if there is a mistake (such as a registration failure) by the user, the program currently stored and operated by the PLC 1 can be reliably held and managed by the management server 30 side.

The control system of FIG. 1 will be described in more detail below.
The management server 30 manages, for example, a project corresponding to each controller (PLC1) introduced to a facility. In particular, the process of giving the update information file 20 is performed to the project registered in the own apparatus.

  When the program update (download) of the controller is performed, the support device 10 determines the possibility of program update (download) based on the presence or absence of the update information file 20 in the target project and the content thereof.

  The management server 30 also grasps the program update status in the controller. In this method, the procedure is “register with management server 30 → add update information file 20 → download to controller” for an arbitrary project, so the project registered in the management server 30 itself is an update information file. I do not know if it is really downloaded to the controller after the 20 grant (the program of the controller has been updated).

  Thus, when an online environment with the controller can be established, the management server 30 monitors the update status of the program of the controller via the network, for example, by the process of FIG. Determine if In this case, the support device 10 needs to write the "project identifier" in the controller at the time of program update by the process of FIG. 8 described later.

  In addition, when the online environment can not be constructed, the management server 30 grasps the update status of the program of the controller, for example, by the processing of FIG. 4 described later. In this processing example, the status 23 of the update information file 20 of this project is updated to “completed” on the side of the support apparatus 10 in accordance with the program update of the controller. Thereafter, a worker or the like stores the project with the update information file 20 in a portable storage medium (USB memory or the like) and brings it back to the management server 30, and inserts the portable storage medium into the management server 30. By this, the management server 30 grasps the program update status of the controller by executing, for example, the processing of FIG. 4 described later while referring to the storage data of the portable storage medium. By performing the process of FIG. 4, the status 45 of the project management information 40 is updated to “Done” as described later.

The specific flow is described below.
On the management server 30 side, a controller to be managed and information for specifying the controller at the time of installation and the like are preset in the identifier 43 of the project management information 40 (in this example, ID1, ID2, ..., IDn ). Moreover, since PLC41 is only a serial number (1, 2, 3 ...), this is also preset.

  Next, in the support device 10, when a program (project) of an arbitrary controller is prepared and prepared for downloading to the controller, the controller 10 requests the management server 30 to register the project. At this time, a controller to be downloaded is designated. The management server 30 overwrites and registers the project requested for registration in the column of the project 42 in the record corresponding to the controller specified in the project management information 40. In the example of FIG. 1, for example, regarding a controller with identifier 43 = 'ID1', a state where a project of 'project identifier = PID1' is registered is shown.

  In the process of registering in the project management information 40 in the management server 30, not only the project corresponding to the designated controller is stored, but also information required for program update is set. This sets, for example, the valid period 44, the project identifier 46, the status 45 and the like.

  The effective period 44 represents a period in which the program of the controller can be updated by the registered project, and is arbitrarily designated by the user of the support apparatus 10 of the request source (in this example, 2014/09/01 to 20/30/09/30) ).

  Also, the management server 30 automatically generates a unique ID for project identification arbitrarily, and sets it as “project identifier 46” as information for specifying a project (in this example, PID 1). Furthermore, the management server 30 sets “during updating” at the time of registration to “status 45” indicating the status of program update. Then, the setting information is added to the project to be registered as the update information file 20, and the project with the update information file 20 is sent back to the support apparatus 10 of the request source.

  The support apparatus 10 may use the setting information as well as the presence or absence of the update information file 20 to determine whether the program can be downloaded to the controller (the program update of the controller can be performed). Although not limited to this example, downloading is not permitted if there is at least the update information file 20.

  Also, a project registered in the management server 30 can be acquired later. In that case, the project 42 corresponding to the specified controller is copied to a predetermined storage area, and if the “status” 45 is being updated, the update information file 20 is created from the project management information 40 as in the registration. And assign it to the project of the predetermined storage area. The support device 10 acquires a project of the predetermined storage area. An example of this process is the process of FIG. 5 described later.

  In the support apparatus 10, basically, the project registered in the management server 30 (immediately after registration or acquired after the above) can be downloaded to the controller, but the download is not necessarily permitted. For example, there may be an embodiment in which the download is not permitted unless the conditions such as the expiration date are also satisfied. The support device 10 determines permission / non-permission of download based on the update information file 20, and when it is determined that permission is given, program update (download) of the controller is performed. Basically, when the update information file 20 is given to the project, the support device 10 recognizes that the project is a registered project in the management server 30, and permits program update (download). As mentioned above, it is not limited to this example. There may be an example in which other conditions (e.g. expiration date) must also be satisfied in order to be permitted.

  Here, when the project of the update version is created based on the project to which the update information file 20 is added in the support device 10, the update information file 20 is also added to the update version project as it is. For this reason, even if this updated version project is not registered in the management server 30, there is a possibility that download to the controller is permitted. In order to avoid such a situation, the update information file 20 is deleted at the time of editing of the project (for example, at the completion of compilation execution).

  In the example shown in FIG. 1, the illustrated “Prj01” project is edited to create the illustrated “Prj01 ′” project, but the update information file 20 added to the “Prj01” project is generated by the above process. However, it can be prevented that it will continue to be granted to the "Prj01 '" project. Therefore, in this state, the project "Prj01 '" can not be downloaded to the controller. Of course, this is the same for another project ("PrjXX" shown).

As described above, the controller program can be updated only by the project registered in the management server 30 and not changed.
Regarding the management of the program update status of the controller in the management server 30, as described above, in the online environment, the program update status is monitored by monitoring from the management server 30 the "project identifier" written in the controller. Determine. The project identifier is unique identification information for identifying each project. This makes the project identifier of any project different from the project identifier of the updated project of this project. Of course, it goes without saying for other projects.

  On the other hand, as described above, in the off-line environment, the project with the update information file 20 carried out from the management server 30 is downloaded to the controller in the support device 10 and brought up to the management server 30 after the program update is completed. However, when the program update is completed, the support device 10 performs a process of changing the status 23 of the update information file 20 of this project from "during updating" to "completed". From this, the management server 30 determines the program update status depending on whether or not the "status 23" of the update information file 20 assigned to this project is "completed".

As described above, the controller program can be reliably updated in the project registered in the management server 30, and can be managed including the update status.
FIG. 2 is a functional block diagram of the control system.

In the illustrated example, the management server 30 includes various processing function units such as a program information storage unit 51, a registration unit 52, a registered information addition unit 53, and a program update monitoring unit 54.
The management server 30 may have the configuration of a general server apparatus in terms of hardware, and has, for example, a CPU, a hard disk, a storage unit such as a memory, a communication function unit, etc. (not shown). . A predetermined application program is stored in advance in the storage unit. When the CPU executes this application program, the various processing function units 51, 52, 53, 54, etc. are realized.

The support device 10 includes an editing unit 61, a permission determination unit 62, and the like.
The support device 10 may also have a general hardware configuration such as a personal computer, and has, for example, a CPU (not shown), a hard disk, a storage unit such as a memory, a communication function unit, etc. . A predetermined application program is stored in advance in the storage unit. The CPU executes the application program to implement the various processing function units 61 and 62 and the like.

  In the program information storage unit 51, a program (project) is registered in association with each control device (PLC 1 etc.). An example of the program information storage unit 51 is the project management information table 40 or the like. The project registered in the program information storage unit 51 can be said to be a program such as a source code or a machine language object.

  When the registration unit 52 receives a request for registration of a program (project) of an arbitrary control device arbitrarily created / edited in the support device 10, the registration unit 52 functions as a program corresponding to the arbitrary control device in the program information storage unit 51. Store the requested program.

  The registered information adding unit 53 adds predetermined registered information to the program whose registration has been registered in the program information storage unit 51 by the registration unit 52. An example of the registered information is the update information file 20 shown in FIG.

  The permission determination unit 62 of the support device 10 does not permit updating the program of any control device by the program to which the registered information is not added. This is an example which does not permit downloading this program to the control device.

  By not permitting the download, the program update of the control device will not be permitted. In other words, by not permitting the download, the update of the program of the control device is prohibited.

  In order to allow the program update of the control device, the program (project) of the arbitrary control device created / edited arbitrarily is registered in the management server 30 and registered by the management server 30. It is necessary to have information given. That is, the holding program on the control device side is updated by the program registered in the management server 30. That is, the program currently held and operated on the control device side can be reliably registered on the management server 30 side. It can be said that this can surely manage the program on the control device side on the management server 30 side.

However, even if the above-mentioned registered information is given, there is a case where it is not permitted to download the program to the control device.
That is, even in the case of the program to which the registered information is added, the permission determination unit 62 determines whether or not a predetermined condition is satisfied based on the registered information, and the condition is not satisfied. Does not allow the program to update any control device program (prohibits program update).

  This is because, for example, the registered information includes an expiration date, and the permission determination unit 62 determines that the predetermined condition is not satisfied when the current date and time is not within the expiration date. Not allow the program to be downloaded to the control unit.

  Further, for example, the program update monitoring unit 54 of the management server 30 confirms whether the program update of the arbitrary control device has been performed by the program to which the registered information is added. This is confirmed, for example, using program identification information as described below.

  That is, first, when storing the program requested to be registered in the program information storage unit 51, the registration unit 52 of the management server 30 arbitrarily generates unique program identification information corresponding to the program and stores it together. . Further, the registered information adding unit 53 includes the program identification information in the registered information.

  In addition, when the support device 10 completes updating the program of the control device by the program with the registered information, the support device 10 causes the control device to store the program identification information included in the registered information. Have a department.

  From this, when the program identification information stored in the program information storage unit 51 matches the program identification information stored in the control device, the program update monitoring unit 54 of the management server 30 registers the registered information. It is determined that the program update of the above-mentioned optional control device is performed by the program to which is given. The management server 30 acquires program identification information stored in the control device via, for example, a network for PLC.

Further, for example, the registered information adding unit 53 distributes the program to which the registered information is added to the support device 10 of the registration request source.
In addition, the support device 10 may further include the editing unit 61 that arbitrarily creates / edits a program of an arbitrary control device.

  The editing unit 61, for example, acquires a program registered in the management server 30, causes the user to perform arbitrary editing on the basis of the acquired program, and causes the user to create an arbitrary update version program. Request for registration of the updated program to 30.

  In the management server 30, for example, the update version program requested to be registered by the registration unit 52 is stored in the program information storage unit 51, and the registered information addition unit 53 registers the registered information in the update version program. Give.

Hereinafter, respective processing on the management server side and the support device side will be described with reference to flowcharts.
3 to 6 show process flowcharts on the management server 30 side.

First, the process on the management server 30 side will be schematically described below.
The management server 30 sets required information in the project management information table 40 at the time of project registration, creates the update information file 20 based on the information, and assigns it to the registered project (FIG. 3). Do. Further, it is judged whether the program update of the controller is completed or not by the project management information table 40 and the update information file 20 in the designated project (FIG. 4).

Also, in the online environment, the status of the managed controller is monitored, and it is determined whether the program update is completed (FIG. 6).
Hereinafter, the process of FIG. 3 will be described first.

FIG. 3 is a process flowchart of registration in the management server 30.
The process of FIG. 3 is executed each time there is a request for registration of an arbitrary project regarding an arbitrary PLC 1 (program update target PLC) from an arbitrary user. This request may be made by the user from any support device 10 via the network, or the user directly operates the management server 30 using the portable storage medium. You may go. However, in any case, the project (source code, complete program of machine language object, etc.) requested to be registered is delivered to the management server 30, and the processing of FIG. 3 is executed.

  In the process of FIG. 3, first, a record (corresponding record) corresponding to the controller designated by the user is specified in the project management information table 40 (step S11). Then, first, the determination process of step S12 is performed. Here, the data items of the project management information table 40 will be described.

  In the example shown in FIG. 1, the project management information table 40 has data items of PLC number 41, project 42, identifier 43, validity period 44, status 45, and project identifier 46.

  The PLC number 41 is a serial number or the like used to manage each controller in the project management information table 40. For example, although this PLC number is used to designate the controller, the present invention is not limited to this example. The PLC number 41 is assumed to have already been arbitrarily registered in the initial state.

  The identifier 43 is information that can specify the controller of the PLC number 41, and is, for example, a serial number, or an identification ID on a network, such as a MAC address. This identifier 43 may be registered in advance for all PLCs 1 similarly to the PLC number 41.

  In the project 42, a project that is supposed to be currently held in the PLC 1 of the PLC number 41 (identifier 43) is registered. In practice, each PLC 1 holds the machine language object (not at least the source code), not all the data of the project. On the other hand, in the project 42, for example, a folder including the source code, a machine language object, etc. is registered. In the initial state, nothing is registered in the project 42. Also, every time the registration update is performed, the old project that has been registered in the project 42 is deleted.

  Also, in the project identifier 46, an identification ID or the like of a project registered in the project 42 is stored. As described above, a new project identifier is assigned to an updated project of a given project.

  In the valid period 44, the valid period of the project registered in the project 42 is registered. The valid period 44 is, for example, for scheduling a program update. That is, if it is outside the effective period, the program can not update the controller by the project.

  The status 45 stores the current status related to the project update of the controller, and indicates the status of the program update. In this example, either “under updating” or “completed” is stored. As described later, when the management server 30 can confirm that the program update of the controller has been performed by the project registered in the project 42, the status 45 is "Done". Details will be described later.

  In step S12, it is determined whether the status 45 of the corresponding record is "updating". If "during updating" (step S12, YES), this basically means that another user is in the process of updating, so the process ends without performing anything.

  On the other hand, when the status 45 of the corresponding record is not "during updating" (step S12, NO), first, the status 45 of the corresponding record is changed to "during updating" (step S13).

  Subsequently, a unique project identifier is arbitrarily generated and stored in the project identifier 46 of the corresponding record (step S14). Further, the user is allowed to set an arbitrary effective period, and this is stored in the effective period 44 of the corresponding record (step S15).

  Thereafter, using the identifier 43 of the corresponding record, the validity period 44, the status 45, and the project identifier 46, the update information file 20 corresponding to the project requested to be registered is generated (step S16).

  Since a unique project identifier is generated every time the process of FIG. 3 is executed, the project identifier generated for the “Prj01” project shown in FIG. The project identifier generated for the project of the updated version "Prj01 '" will be different.

  Here, as shown in FIG. 1, for example, the update information file 20 includes data items of an identifier 21, a valid period 22, a status 23, and a project identifier 24. The update information file 20 is generated by using the identifier 43, the valid period 44, the status 45, and the project identifier 46 of the corresponding record as the identifier 21, the valid period 22, the status 23, and the project identifier 24 as they are.

  Then, the project requested for registration is stored in the column of the project 42 of the corresponding record, and the generated update information file 20 is added to the project requested for registration, and this is returned to the user (step S17). ). For example, as an example, the project requested to be registered with the update information file 20 is returned to the arbitrary support device 10 via the network.

  From the above, the arbitrary support device 10 basically permits the download of the project (with its machine language object) with the update information file 20 to the program update target PLC. However, as described above, it is not permitted if the conditions such as the expiration date are not satisfied.

  The processing relating to the download processing in such a support device 10 will be described later with reference to FIG. 8, but if the program (machine language object) of the PLC 1 is successfully updated, the support information device The status 23 of the 20.sup.th project is changed from "updating" to "completed".

  Thereafter, the support device 10 notifies the management server 30 of the update completion notification together with the project with the update information file 20. At that time, the controller to be updated is designated. The management server 30 having received this executes the processing of FIG. However, the present invention is not limited to this example. For example, when the user passes the project with the update information file 20 to the management server 30 via a portable storage medium (USB memory or the like), the management server 30 executes the processing of FIG. You may do it.

The process of FIG. 4 will be described below.
FIG. 4 is a flowchart of processing for program update confirmation in the management server 30.

  In the process of FIG. 4, first, in the project management information table 40, a record (corresponding record) corresponding to the specified controller is specified (step S21), as in step S11.

  Then, it is determined whether the status 45 of the corresponding record is "updating" (step S22). If the status 45 is "completed" (step S22, NO), the present process ends.

  If it is confirmed that the status 45 is "during updating" (step S22, YES), it is determined whether the update information file 20 exists in the notified project with the update information file 20 (step S23). Note that this is a process of confirmational meaning, although the user intended to notify the project with the update information file 20, a project without the update information file 20 is notified for any reason in practice. In such a case, the determination in step S23 is NO, and the process ends.

  When the update information file 20 is attached to the process target project (step S23, YES), it is confirmed that the identifier 21 of the update information file 20 matches the identifier 43 of the corresponding record (step S24). If the identifiers do not match (step S24, NO), this processing ends.

  If it is confirmed that the identifiers match (step S24, YES), it is confirmed that the status 23 of the update information file 20 is "completed" (step S25), and if "completed" (step S25, YES) ) The status 45 of the corresponding record is changed from "during updating" to "completed" (step S26). If the status 23 is "updating" (step S25, NO), this process ends without performing the process of step S26.

  As described above, when the program update of the PLC 1 is normally completed by the process of FIG. 8 described later, the status 23 should be “completed” and the process of step S26 is executed. become.

  Then, in this example, finally, the management server 30 deletes the update information file 20 from the project with the update information file 20 in the support device 10 (step S27). As a result, when this project is subsequently edited to create an updated project, the updated project is naturally also in a state where there is no updated information file 20. Therefore, in this example, it is not necessary to delete the update information file 20 from the update version project at the time of compilation. In any case, it is similar in that even if the updated project newly generated by editing is to be downloaded as it is to the PLC 1, it is not permitted.

Needless to say, for example, when trying to download another project shown in FIG. 1 to the controller and update the program, it is naturally not permitted.
The support apparatus 10 obtains the project with the update information file 20 from the management server 30 by the process of FIG. 3 but loses the project with the update information file 20 before realizing the program update of the PLC 1 by the process of FIG. The case of equal is assumed. In such a case, in this example, the support device 10 can request the management server 30 to obtain the same project with the update information file 20 again. The process of the management server 30 in that case is a process shown in FIG.

The process of FIG. 5 will be described below.
FIG. 5 is a process flowchart relating to the project reissue of the management server 30.
When there is a request for reissuing the project with the update information file 20 of the PLC 1 arbitrarily designated from the support device 10, the management server 30 first makes the controller designated in the project management information table 40 as in step S11. The corresponding record (corresponding record) is specified (step S31).

Then, first, the project (folder) stored in the column of the project 42 of the corresponding record is copied to a predetermined storage area (step S32).
Subsequently, it is determined whether the status 45 of the corresponding record is "updating" (step S33), and if "completed" (step S33, NO), the processes of steps S34 and S35 are not performed. End the process. As described above, this process assumes that the controller program has not been updated yet, so if the program update has been completed, the reissue of the project with the update information file 20 should not be permitted. Make it

  If the status 45 of the corresponding record is "updating" (step S33, YES), first, the same process as step S16 is performed to generate the update information file 20 (step S34). Then, the generated update information file 20 is assigned to the project copied to the predetermined storage area in step S32 (step S35).

  Thereafter, the support device 10 acquires the project to which the update information file 20 is added from the predetermined storage area. Then, using this, it will try to update the program of PLC1.

  Although the process in FIG. 5 is a process for reissuing the project with the update information file 20, as described above, conventionally, on the support apparatus side, the management server is registered in the management server. The project (in particular, the source code corresponding to the machine language object that the controller should currently hold) is acquired, and the user arbitrarily edits the acquired project to create an updated version project. The process of acquiring a registered project from the management server 30 in such a case is different from that of FIG. 5, but this is conventionally performed as described above, and the flow chart etc. is not particularly shown here. It will only be briefly described below.

  That is, when there is a request for updating a project of an arbitrary controller from the support device 10, the management server 30 passes the project registered in association with the controller from the project management information table 40 to the support device 10. At this time, the update information file 20 is not added. Therefore, on the support apparatus 10 side, the user arbitrarily edits the passed project to create the updated project, but the updated project can not be downloaded to the controller as it is. From this, in order to update the program of the controller, the process of FIG. 3 is performed and the update information file 20 needs to be added.

  Further, the process of recognizing the program update of the controller in the management server 30 and changing the status 45 from “during updating” to “completed” is not limited to the example of FIG. I don't care.

  However, the process of FIG. 6 is premised that the management server 30 is configured to be able to communicate with each PLC 1 by connecting to, for example, a network for PLC. As is well known, the PLC network is a low speed network or the like in which a plurality of PLCs 1 are connected to each other to transmit and receive data.

  Further, as will be described later, the process of step S68 described later in the process of FIG. 8 is not essential, but is essential when the process of FIG. 6 is performed. Therefore, in this case, when the program update of the controller (PLC1) is completed, the program identifier of the update version program is stored in this controller.

  In the process of FIG. 6, the management server 30 checks an arbitrary record in the project management information table 40 as a process target (step S41), and checks whether the status 45 of the process target record is "updating". (Step S42). If the status 45 is "completed" (step S42, NO), this processing ends.

  If the status 45 is "updating" (step S42, YES), the controller 43 of the process target is accessed using the identifier 43 (such as MAC address) of the process target record, and the program identifier stored by this controller is Read out (step S43). As described above, if the program of this controller has been updated, the read out program identifier should be the same as the registered program identifier of the project. From this, it is checked whether the program identifier read out in step S43 matches the program identifier 46 of the process target record (step S44). Then, if they match (step S44, YES), it is regarded that the program of the controller is updated by the registered project, and the status 45 of the process target record is changed from "during updating" to "completed" To (step S45).

  If they do not match (step S44, NO), the process of step S45 is not performed, and the process ends. In this case, the program identifier on the controller side read out in step S43 should basically be the program identifier of the old project. This is because it is considered that the controller program has not been updated by the registered project (updated project), so it is considered that the controller stores an older version of the program. is there.

Next, processing of the support apparatus 10 will be described below with reference to FIGS. 7 and 8.
FIG. 7 is a process flowchart of the support device 10 at the time of compilation.
For example, as described above, in the support apparatus 10, the user may edit an existing project and create an updated version of the project. This is because the user creates an updated version of the source code of the project, and the support device 10 compiles this source code and converts it into a machine language object, whereby an updated version of the project is created. At this time, the update information file 20 is deleted as it is to prevent the update information file 20 assigned to the existing project from being taken over to the project of the updated version. An example of such compilation processing is the processing shown in FIG.

  In the process of FIG. 7, the source code of the project of the updated version is compiled (step S51). Then, if compilation is successful (step S52, YES), if the update information file 20 exists in the project of the updated version (step S53, YES), the update information file 20 is deleted (step S54).

  In the example where the process of step S27 is performed, the existing project does not have the update information file 20, and naturally, the update project does not have the update information file 20 either. The determination in S53 is NO, and this processing ends. In the case where the process of step S27 is performed, the processes of steps S53 and S54 are not necessarily required.

Furthermore, if compilation fails (step S52, NO), this processing ends.
FIG. 8 is a process flowchart of the support apparatus 10 at the time of downloading.

  After the update information file 20 is given by the process of FIG. 3 to the project of the updated version created above, the support apparatus 10 makes the updated version project (its machine language object) at any time, Download to target PLC1 and update the program of PLC1. An example of such processing is shown in FIG.

  In the process of FIG. 8, first, the identifier (MAC address) is read from the target controller (PLC1) (step S61), and this identifier is the identifier 21 of the update information file 20 assigned to the update version project and It is determined whether or not they match (step S62). If the two do not match (step S62, NO), the process proceeds to step S66. In this case, as a matter of course, no program update is performed, so the determination in step S66 is NO, and the process ends.

  Basically, when the update information file 20 is not attached to the update version project, the determination in step S62 is NO, and the program update is not performed. This means that the download (program update of PLC 1) is not permitted unless the update information file 20 is attached to the update version project.

  In step S62, it is further confirmed that the controller identification information (ID1 in the example of FIG. 1) matches the "identifier 21" (ID1 in the example of FIG. 1) of the update information file 20 of the target project. Check that it is a project related to the target controller. From this, for example, even when the user makes a mistake in specifying the PLC 1 to be downloaded, the determination in step S62 is NO.

  When the update information file 20 is added to the updated version project (when the identifier 21 matches the identifier of the controller) (step S62, YES), the current date and time is read from the controller (step S63). ), It is checked whether or not the present time is within the term of the validity period 22 of the update information file 20 (step S64). If it is within the effective period (step S64, YES), the updated version project (its machine language object) is downloaded to the controller, and the program is updated (step S65).

  If it is determined in step S64 that the current time is not within the valid period 22, the program update is not permitted. This makes it possible to control the project update timing. The current date and time may be acquired from the clock function of the support device 10.

  On the controller side, the downloaded machine language object tries to update its own program. This process itself is an existing process and will not be described in particular. Then, the controller notifies the support device 10 of the success / failure of the program update as the processing result.

  When the program update is successful (step S66, YES), the support device 10 changes the status 23 of the update information file 20 from "during updating" to "completed" (step S67). Furthermore, the project identifier 24 of the update information file 20 is written to a predetermined storage area of the controller (step S68). As described above, the process of step S68 is not necessarily required.

If the program update fails (step S66, NO), the process ends without performing the process of step S67 and the like.
As described above, in the present method, at first, the support device 10 does not allow the project in which the update information file 20 does not exist to be downloaded to the controller. With regard to the case where an updated project is generated by editing an existing project by the user, the support device 10 at least when the updated project can be downloaded to the controller, that is, the compilation process When the machine language object has been generated and executed, the update information file 20 does not exist in the updated version of the project. Although two methods are presented in the above description as processing examples for that purpose, the present invention is not limited to these examples.

  If this is the case, the updated program can not be downloaded to the controller, and therefore the controller program can not be updated. On the other hand, in the present example, when the project of the updated version is registered in the management server 30, the management server 30 assigns the update information file 20 to the project of the updated version. From this, the support device 10 is basically in a state of permitting the download of the updated version of the project to the controller.

  However, in this example, even if the update information file 20 exists, the download may not be permitted. That is, if the determination in step S62 or step S64 is NO, the download is not permitted even if the update information file 20 exists. As described above, at the time of downloading, whether or not the program can be updated is determined based on the presence or absence of the update information file 20 and the contents thereof. This means that the program update is not permitted if at least the update version project is not registered in the management server 30. Therefore, the program held by the controller and the program managed by the management server 30 do not have different situations.

  In addition, even if it is another project shown in FIG. 1 as well as the project of the above-mentioned updated version, when it is registered in the management server 30 and thus the update information file 20 is given, the download to the controller is It will be permitted.

  According to this method, the management server 30 that manages the project can reliably manage the project currently held and operated by each controller in the facility, and can reliably update the program in the managed project, as well as the update status Since it can be grasped, there is an effect that efficiency improvement of project management and prevention of operation mistake by the user can be expected.

  In addition, by providing information on the expiration date and status in the project management information, scheduling of program updates for controllers in the entire facility reliably supports renewal and management within the due date, and further, the expiration date due to loss of the project, etc. Renewal procedures in the event of a failure have the effect of making it possible to thoroughly manage the project.

1 PLC
10 Support Device 20 Update Information File 21 Identifier 22 Valid Period 23 Status 24 Project Identifier 30 Management Server 40 Project Management Information Table 41 PLC Number 42 Project 43 Identifier 44 Valid Period 45 Status 46 Project Identifier 51 Program Information Storage Unit 52 Registration Unit 53 Registration Completed information adding unit 54 Program update monitoring unit 61

Claims (10)

A control unit for executing stored programs for controlling the control target device, a support device in which the program of the control device is created / edited, a control system and a management server device,
The management server device is
Program information storage means in which a program is registered in association with each control device;
When there is a request for registration of a program of an arbitrary control device arbitrarily created / edited in the support device, the program requested to be registered is stored as a program corresponding to the arbitrary control device in the program information storage unit Registration means,
A registered information giving unit for giving predetermined registered information to the program requested to be registered, which is registered in the program information storage unit by the registration unit;
The support device is
A control system comprising permission determination means for prohibiting update of a program of the arbitrary control device by a program to which the registered information is not added.   The permission determination unit determines whether or not a predetermined condition is satisfied based on the registered information even if the program is assigned the registered information, and the condition is not satisfied. The control system according to claim 1, wherein the program prohibits update of a program of the arbitrary control device. The registered information includes an expiration date,
3. The control system according to claim 2, wherein the permission determination means determines that the predetermined condition is not satisfied when the current date and time is not within the expiration date. The management server device is
The program update monitoring means according to any one of claims 1 to 3, further comprising program update monitoring means for confirming whether the program update of the arbitrary control device has been performed by the program to which the registered information is added. Control system. The management server device is
When storing the program requested to be registered in the program information storage means, unique program identification information corresponding to the program is optionally generated and stored together, and the program identification information is included in the registered information. ,
The support device is
When the update of the program of the control device is completed by the program to which the registered information is added, the program identification information is stored in the control device;
If the program identification information stored in the program information storage means matches the program identification information stored in the control device, the program update monitoring means of the management server device is provided with the registered information. 5. The control system according to claim 4, wherein it is determined that the program update of the arbitrary control device has been performed by the program.   The control system according to any one of claims 1 to 3, wherein the registered information adding means distributes the program to which the registered information is added to the registration request source support apparatus. The support device further comprises editing means for arbitrarily creating / editing a program of any control device,
The editing means acquires a program registered in the management server apparatus, and causes an arbitrary edition program to be created by performing arbitrary editing based on the acquired program, and causes the management server to generate Request the registration of the updated program,
In the management server device, the update version program requested to be registered by the registration unit is stored in the program information storage unit, and the registered information provision unit is configured to add the registered information to the update version program. The control system according to any one of claims 1 to 3, characterized in that: A control unit for executing stored programs for controlling the control target device, there at the management server device in a control system having a support device in which the program of the control device is created / edited, and a management server device ,
Program information storage means in which a program is registered in association with each control device;
When there is a request for registration of a program of an arbitrary control device arbitrarily created / edited in the support device, the program requested to be registered is stored as a program corresponding to the arbitrary control device in the program information storage unit Registration means,
Registered information giving means for giving predetermined registered information to the program requested to be registered, registered in the program information storage means by the registration means.
And a control server device of a control system. A control unit for executing stored programs for controlling the control target device, a support device in which the program of the control device is created / edited, a said support device in a control system and a management server device ,
Editing means for arbitrarily creating / editing a program of an arbitrary control device;
Permission judging means for prohibiting the update of the program of the control device by the program to which the registered information is not given;
An apparatus for supporting a control system, comprising:   The editing means sends the registration request of the optionally created / edited program to the management server device, and the management server device gives the registered information to the program requested for registration. 10. The control system support apparatus according to claim 9, wherein a program with registered information is acquired.