WO2024261848A1 - プログラム可能機器、開発装置、バージョン管理システム、バージョン管理方法及びプログラム - Google Patents
プログラム可能機器、開発装置、バージョン管理システム、バージョン管理方法及びプログラム Download PDFInfo
- Publication number
- WO2024261848A1 WO2024261848A1 PCT/JP2023/022710 JP2023022710W WO2024261848A1 WO 2024261848 A1 WO2024261848 A1 WO 2024261848A1 JP 2023022710 W JP2023022710 W JP 2023022710W WO 2024261848 A1 WO2024261848 A1 WO 2024261848A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data set
- dataset
- version
- user
- plc
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Program-control systems
- G05B19/02—Program-control systems electric
- G05B19/04—Program control other than numerical control, i.e. in sequence controllers or logic controllers
- G05B19/05—Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
- G05B19/056—Programming the PLC
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/215—Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Definitions
- This disclosure relates to a programmable device, a development device, a version control system, a version control method, and a program.
- Programmable devices for FA such as programmable logic controllers and motion units, execute programs developed by users to control controlled devices.
- FA Vectory Automation
- Non-Patent Document 1 discloses a technology that uses Git, an open source distributed version control system, to support the development of control software by multiple people.
- Non-Patent Document 1 the programmable device itself is independent of the distributed version control system. Therefore, the consistency between the source code managed by the distributed version control system and the program executed by the programmable device must be managed manually, which places a heavy burden on the user. For example, it is possible that the program executed by the programmable device was not generated based on the source code managed by the distributed version control system.
- the purpose of this disclosure is to provide a programmable device etc. that can easily perform distributed version management of data related to the programmable device.
- the programmable device comprises: a first storage means for storing a first data set; a first version management means for performing version management of the first data set stored in the first storage means; a first transmission means for transmitting the first data set version-managed by the first version management means to a development device; a first receiving means for receiving a second data set that is created based on the first data set transmitted by the first transmitting means and that is version-managed in association with the first data set in the development device; Equipped with The first version management means stores the second data set received by the first receiving means in the first storage means in association with the first data set, and performs version management in association with the first data set.
- the present disclosure allows for easy distributed version control of data related to programmable devices.
- FIG. 1 is a diagram showing an overall configuration of a version control system according to a first embodiment of the present disclosure.
- FIG. 1 is a diagram showing an example of version management by a version management system according to a first embodiment of the present disclosure.
- FIG. 1 is a block diagram showing a functional configuration of a PLC according to a first embodiment of the present disclosure.
- FIG. 1 is a diagram illustrating an example of a hardware configuration of a PLC according to a first embodiment of the present disclosure and a development device according to a second embodiment of the present disclosure.
- a flowchart showing an example of a version management operation by the PLC according to the first embodiment of the present disclosure.
- FIG. 1 is a diagram showing an overall configuration of a version control system according to a first embodiment of the present disclosure.
- FIG. 1 is a diagram showing an example of version management by a version management system according to a first embodiment of the present disclosure.
- FIG. 1 is a block diagram showing a functional configuration of a PLC according to
- FIG. 1 is a diagram showing an overall configuration of a version control system according to a modified example of the first embodiment of the present disclosure.
- FIG. 13 is a block diagram showing a functional configuration of a development device according to a second embodiment of the present disclosure.
- FIG. 1 is a diagram for explaining an example of distributed version management by a version management system according to a second embodiment of the present disclosure.
- FIG. 1 is a diagram for explaining an example of distributed version management by a version management system according to a second embodiment of the present disclosure.
- FIG. 1 is a diagram for explaining an example of distributed version management by a version management system according to a second embodiment of the present disclosure.
- FIG. 1 is a diagram for explaining an example of distributed version management by a version management system according to a second embodiment of the present disclosure.
- FIG. 1 is a diagram for explaining an example of distributed version management by a version management system according to a second embodiment of the present disclosure.
- FIG. 1 is a diagram for explaining an example of distributed version management by a version management system according to a second embodiment of the present disclosure.
- FIG. 13 is a diagram for explaining an example of distributed version management by a version management system according to a modification of the second embodiment of the present disclosure.
- FIG. 13 is a diagram for explaining an example of distributed version management by a version management system according to a modification of the second embodiment of the present disclosure.
- the version control system 1 includes a PLC (Programmable Logic Controller) 10 and a plurality of development devices 20.
- the version control system 1 is an example of a version control system according to the present disclosure.
- the version control system 1 multiple users develop programs to be executed on the PLC 10 using their respective development devices 20.
- the users send to the PLC 10 a data set that combines the program developed using the development device 20 and data related to the program.
- the data related to the program includes, for example, the source code that is the basis of the program, configuration files and resource files required for the program, and document files that explain the program specifications.
- a user sends a dataset to PLC 10 each time a program change is completed.
- PLC 10 executes the program contained in the dataset while managing the version of the received dataset. If a user sends a dataset to PLC 10 each time a change is completed, PLC 10 will manage the version of the dataset for each completed change.
- PLC 10 executes programs developed by the user and controls controlled devices (not shown). In addition to executing programs, PLC 10 also performs version management of data sets as described above. The functional configuration of PLC 10 will be described later.
- PLC 10 is an example of a programmable device according to the present disclosure.
- the development device 20 is used to develop a program to be executed by the PLC 10.
- the development device 20 is, for example, a personal computer on which an engineering tool program is installed.
- a user creates a data set including a program to be executed by the PLC 10 using the development device 20, and transmits the created data set to the PLC 10.
- the development device 20 is an example of a development device related to the present disclosure.
- program development is generally carried out according to the following flow.
- a user creates a dataset including a program through development work.
- PLC 10 authenticates the user.
- the user sends a data set to the PLC 10.
- the PLC 10 performs version control on the received data set.
- the user executes the program contained in the data set transmitted to the PLC 10 on the PLC 10 to perform debugging work.
- (6) Make any necessary corrections and repeat the steps from (1).
- the program is executed on the PLC 10 and multiple users check its operation.
- the user repeats the steps from (1).
- the PLC 10 manages datasets by dividing them into a master area and a user area for each user.
- the master area is an area accessible to any user, while the user area is an area accessible only to that user and not to other users.
- Datasets created by users are in principle stored in the user area, but datasets that should be shared among all users are stored in the master area based on the user's operation. Saving a dataset to the master area based on the user's operation will be referred to as "applying a dataset to the master area" below.
- datasets that should be shared among all users include a dataset that contains an executable file that has been modified by the user and should be tested by all users in common, and a dataset that contains an executable file that has reached a level that is suitable for shipping as a product.
- the circle in Figure 2 represents one dataset.
- the arrow in Figure 2 indicates that a child dataset is created with a certain dataset as the immediate parent.
- dataset x1 which is the "first dataset”
- PLC 10 receives a dataset for the first time, by saving that dataset in the master area.
- user A makes changes based on dataset x1 in the master area and sends the changed dataset to PLC 10.
- making changes based on a dataset and sending the changed dataset to PLC 10 will be referred to as "updating.”
- dataset y1 which branches off from dataset x1 in the master area, is saved in the user A area rather than the master area.
- Dataset x1 becomes the immediate parent of dataset y1.
- dataset y1 which has dataset y1 as its immediate parent
- dataset y2 which has dataset y1 as its immediate parent
- dataset y3 which has dataset y2 as its immediate parent
- dataset y3 which has the same contents as dataset y3, is saved in the master area with datasets x1 and y3 as its immediate parents.
- This dataset x2 has the changes made by user A between datasets y1 and y3 applied to it. Since the ancestor of dataset y3 is dataset x1, and the latest dataset in the master area at this point is dataset x1, dataset y3 can be applied to the master area without any problems.
- the "ancestral parent” here refers to a dataset that can be traced back one or more generations from the parent of a dataset. In the example shown in Figure 2, dataset x1 is the "ancestral parent" of datasets y1, y2, and y3.
- user B also updates dataset x1 in the master area, which causes dataset z1, which branches off from dataset x1 in the master area and has dataset x1 as its immediate parent, to be saved in the user B area.
- User B then performs two updates, which causes dataset z2, which has dataset z1 as its immediate parent, to be saved in the user B area, and dataset z3, which has dataset z2 as its immediate parent, to be saved in the user B area. Note that it is assumed that user B's work up to this point was done before dataset x2 was saved in the master area.
- dataset z4 is saved in the master area with dataset x2 and dataset z4 as its immediate parents.
- This dataset x3 is a merge of the changes made by user B between datasets z1 to z3 and the contents of dataset x2.
- the PLC 10 manages datasets by dividing them into a master area and a user area, allowing the datasets to be managed on a per-user basis. This allows users to focus only on the datasets in the master area and the datasets in the user area that correspond to them when developing a program, making it easier to manage version control in an environment where multiple people are developing.
- the PLC 10 includes a memory unit 100, a communication unit 101, a user authentication unit 102, a version management unit 103, and a program execution unit 104.
- the storage unit 100 stores the data set based on version management by the version management unit 103 described below.
- the storage unit 100 includes a master area M and a plurality of user areas U provided for each user.
- the storage unit 100 is an example of a first storage means according to the present disclosure.
- the communication unit 101 communicates with the development device 20.
- the communication unit 101 is, for example, a network interface.
- the communication unit 101 is an example of a first transmitting means and a first receiving means according to the present disclosure.
- the user authentication unit 102 authenticates the user corresponding to the development device 20 that is the communication destination of the communication unit 101.
- the user authentication unit 102 authenticates the user by, for example, password authentication.
- the administrator of the PLC 10 may register in advance in the PLC 10 a user corresponding to each development device 20, and the user authentication unit 102 may automatically authenticate the user by identifying the development device 20.
- the version management unit 103 performs version management on the datasets received by the communication unit 101.
- the version management unit 103 stores and manages the datasets separately in a master area M and each user area U.
- the version management unit 103 stores a dataset whose immediate parent is a dataset stored in the master area M in the user area U corresponding to the user who performed the update. Therefore, the dataset stored is one that has "branched" from the dataset in the master area M.
- the version management unit 103 generally stores in the user area U a dataset whose immediate parent is a dataset stored in the user area U. Therefore, as a general rule, a dataset sent by a user is stored in the user area U.
- the version management unit 103 stores that dataset in the master area M. Note that if the ancestor of the dataset that the user is attempting to apply to the master area M is different from the latest dataset stored in the master area M, the version management unit 103 will reject the user's application. In this case, the user must merge the latest dataset stored in the master area M with their own dataset.
- the version management unit 103 When the version management unit 103 saves a dataset in the master area M or the user area U, it saves not only the dataset itself but also metadata that individually identifies the dataset and metadata that indicates the immediate parent dataset of the dataset to be saved, in association with the dataset itself. For example, the hash value of the binary data when the dataset itself is treated as a single piece of binary data can be used as the metadata. This allows the dataset to be associated with the immediate parent dataset when saved, making it possible to manage the parent-child relationships between datasets and to perform version management of the dataset as a whole.
- the version management unit 103 is an example of a first version management means according to the present disclosure.
- the program execution unit 104 reads out a program stored in the storage unit 100 via the version management unit 103, and executes the read out program.
- the program execution unit 104 reads out and executes, for example, a program contained in the latest data set stored in the storage unit 100.
- the program execution unit 104 may read out and execute a program contained in a data set specified by the user. For example, due to work processes, source code may temporarily become uncompileable, resulting in a state in which no executable file exists in the latest data set. In such a case, the user must specify a data set in which the executable file exists.
- the program execution unit 104 also stores a log of program execution in the storage unit 100 in association with the dataset corresponding to the executed program.
- the log of program execution includes, for example, information indicating the execution date and time, information regarding events and errors that occurred during program execution, and information indicating the dataset corresponding to the executed program. For example, a user can analyze this log to evaluate the quality of the program for each dataset.
- the PLC 10 is a programmable logic controller, and is therefore a type of computer.
- PLC 10 includes a processor 1001, a memory 1002, an interface 1003, and a secondary storage device 1004, which are connected to each other via a bus 1000.
- the processor 1001 is, for example, a CPU (Central Processing Unit).
- the processor 1001 loads an operating program stored in the secondary storage device 1004 into the memory 1002 and executes it, thereby realizing each function of the PLC 10.
- the processor 1001 may include a processor that loads and executes a data set stored in the storage unit 100, in addition to the processor that executes the operating program. In this case, the latter processor realizes the functions of the program execution unit 104.
- Memory 1002 is a main storage device that is constituted, for example, by RAM (Random Access Memory). Memory 1002 stores the operating program that processor 1001 reads from secondary storage device 1004. Memory 1002 also functions as a working memory when processor 1001 executes the operating program.
- RAM Random Access Memory
- the interface 1003 is, for example, an I/O (Input/Output) interface such as a serial port, a USB (Universal Serial Bus) port, or a network interface.
- the interface 1003 realizes the functions of the communication unit 101.
- the secondary storage device 1004 is, for example, a flash memory, a hard disk drive (HDD), or a solid state drive (SSD).
- the secondary storage device 1004 stores the operating programs executed by the processor 1001.
- the functions of the storage unit 100 are realized by the secondary storage device 1004.
- the operation shown in FIG. 5 is executed, for example, when a user operates the development device 20 and the development device 20 starts communication to transmit a data set to the PLC 10.
- the user authentication unit 102 of the PLC 10 communicates with the development device 20 and authenticates the user of the development device 20 (step S101). This operation identifies the user who sent the data set.
- the development device 20 transmits a data set to the PLC 10, and the communication unit 101 of the PLC 10 receives the transmitted data set (step S102).
- the version management unit 103 of the PLC 10 determines whether the user is attempting to apply a dataset to the master area M (step S103).
- step S103 When the user is not attempting to apply a dataset to master area M (step S103: No), the version management unit 103 saves the dataset received in step S102 in the user area U corresponding to the user authenticated in step S101 (step S104). In this operation, if the immediate parent of the dataset to be saved is a dataset in master area M, the dataset to be saved becomes a "branch" from the dataset in master area M. Then, the PLC 10 ends the version management operation.
- step S103 When the user is attempting to apply a dataset to the master area M (step S103: Yes), the version management unit 103 determines whether the ancestor dataset of the dataset being applied matches the latest dataset in the master area M (step S105).
- step S105 When the parent dataset of the dataset to be applied matches the latest dataset in master area M (step S105: Yes), the version management unit 103 saves the dataset to be applied in master area M (step S106). Then, the PLC 10 ends the version management operation.
- step S105 If the parent dataset of the dataset to be applied does not match the latest dataset in master area M (step S105: No), the version management unit 103 rejects the application of the dataset to master area M (step S107). Then, the PLC 10 ends the version management operation.
- the above describes the version control system 1 according to the first embodiment.
- the PLC 10 of the version control system 1 stores data sets in a master area M and a user area U for each user, and performs version control.
- the user when developing a program, the user only needs to focus on the data sets in the master area M and the data sets in the user area U that correspond to the user, making version control easy in an environment where multiple people are developing.
- the PLC 10 may be communicably connected to the external system 30, and the version management unit 103 of the PLC 10 may transmit the data set stored in the storage unit 100 to the external system 30 at a predetermined timing to back up the data set.
- the backup may be performed when a new data set is added, or may be performed periodically.
- the development device 20, instead of the PLC 10, may be communicatively connected to the external system 30, and the development device 20 may read out the data set stored in the memory unit 100 of the PLC 10 and transmit it to the external device 30 to create a backup.
- this configuration can be used when the development device 20 can connect to the Internet but the PLC 10 cannot.
- each user can access the data set in the user area U corresponding to himself/herself, but cannot access the data sets in the user area U corresponding to other users.
- the data sets in each user area U may be encrypted with an encryption key corresponding to each user.
- the data set in master area M may also be encrypted with an encryption key unique to PLC 10. This prevents anyone who does not own PLC 10 from decrypting the data set in master area M, so that even if the data set stored in master area M is leaked for some reason, a third party cannot learn the contents of the data set.
- the user can apply a dataset in the user area U to the master area M at any time, as long as it does not conflict with the latest dataset in the master area M.
- the version management unit 103 may issue a warning to the user if the dataset is updated a certain number of times or more in the user area U.
- the version management unit 103 may transmit data indicating a warning to the development device 20 via the communication unit 101, and the development device 20 may notify the user of the warning.
- the version control system 1 according to the second embodiment will be described below.
- the overall configuration of the version control system 1 according to the second embodiment is similar to that of the first embodiment shown in Fig. 1.
- the second embodiment differs from the first embodiment in that the development device 20 also performs version management of the data set.
- user A updated the datasets by sending each of the datasets y1, y2, and y3 to the PLC 10 each time.
- user A once user A has acquired dataset x1, he or she can make changes to the datasets y1, y2, and y3 without communicating with the PLC 10, and can send the datasets y1, y2, and y3 together to the PLC 10 and apply the dataset y3 to the master domain M.
- the functional configuration of the development device 20 according to the second embodiment will be described with reference to FIG. 7.
- the development device 20 according to the second embodiment includes a storage unit 200, a communication unit 201, a data set creation unit 202, and a version management unit 203.
- the storage unit 200 stores a data set based on version management by the version management unit 203 described below.
- the storage unit 200 includes a master area M and a user area U.
- the user area U is only one area corresponding to the user of the development device 20.
- the storage unit 200 is an example of a second storage means according to the present disclosure.
- the communication unit 201 communicates with the PLC 10. Based on the control of the version management unit 203 described below, the communication unit 201 transmits a data set created by the user via the development device 20 to the PLC 10, and receives a data set stored in the storage unit 100 from the PLC 10.
- the communication unit 201 is realized, for example, by a network interface.
- the communication unit 201 is an example of a second receiving means and a second transmitting means according to the present disclosure.
- the dataset creation unit 202 creates a program to be executed by the PLC 10 and data related to the program based on user operations via an input device (not shown). In other words, the dataset creation unit 202 creates a dataset based on user operations.
- the dataset creation unit 202 has the function of an editor for writing, for example, source code, configuration files, documents, and the like.
- the dataset creation unit 202 is an example of a dataset creation means according to the present disclosure.
- the version management unit 203 stores the dataset created by the dataset creation unit 202 in the user area U of the storage unit 200 and performs version management.
- the version management unit 203 like the version management unit 103 of the PLC 10, saves not only the dataset itself but also metadata that individually identifies the dataset and metadata that indicates the immediate parent dataset of the dataset to be saved, in association with the dataset itself. This allows the datasets created by the user to be version managed within the development device 20.
- the version management unit 203 collectively transmits one or more data sets that have not yet been transmitted to the PLC 10, among the data sets stored in the user area U of the storage unit 200, to the PLC 10 via the communication unit 201. This allows the contents of changes made by the user on the development device 20 to be synchronized with the PLC 10.
- the version management unit 203 acquires, via the communication unit 201, one or more data sets that are not stored in the master area M of the storage unit 200 among the data sets stored in the master area M of the storage unit 100 of the PLC 10, and stores the data in the master area M of the storage unit 200. This allows changes to the master area M of the PLC 10 to be synchronized with the development device 20.
- the version management unit 203 is an example of a second version management means according to the present disclosure.
- the development device 20 according to the second embodiment can transmit multiple data sets to the PLC 10. Also, as described above, the development device 20 according to the second embodiment acquires a data set in the master area M from the PLC 10. Therefore, the version management unit 103 according to the second embodiment also corresponds to this.
- the version management unit 103 according to the second embodiment receives multiple data sets collectively from the development device 20 and stores the received data sets collectively in the user area U of the storage unit 100.
- the version management unit 103 according to the second embodiment transmits one or more data sets in the master area M to the development device 20 in response to a request from the development device 20.
- the functions of the version management unit 203 of the development device 20 and the version management unit 103 of the PLC 10 enable the PLC 10 and the development device 20 to individually manage the version of the data set, while synchronizing the PLC 10 and the development device 20 as necessary. Therefore, the version management system 1 according to the second embodiment can realize distributed version management.
- the version management unit 203 of the development device 20 acquires the data set x1 stored in the memory unit 100 from the PLC 10 and stores it in the master area M of the memory unit 200.
- the data set x1 is also stored in the master area M of the memory unit 200 of the development device 20, as shown in FIG. 8.
- the user of the development device 20 makes changes to the dataset x1.
- This causes the dataset creation unit 202 of the development device 20 to create a new dataset, and as shown in FIG. 9, the version management unit 203 saves the new dataset as dataset y1 in the user area U of the storage unit 200.
- the PLC 10 there is no communication between the PLC 10 and the development device 20, so there are no particular changes in the storage unit 100 of the PLC 10.
- the user makes two changes, and as shown in FIG. 10, the data sets y2 and y3 are saved in the user area U of the storage unit 200. Even at this point, there are no particular changes in the storage unit 100 of the PLC 10.
- the version management unit 203 collectively transmits the data sets y1, y2, and y3 stored in the user area U of the storage unit 200 to the PLC 10.
- the version management unit 103 of the PLC 10 stores the received data sets y1, y2, and y3 in the user area U of the storage unit 100. It is only at this point that the development device 20 and the PLC 10 can be synchronized.
- the user performs an operation to apply dataset y3 to the master area M of the storage unit 100 of the PLC 10, whereby dataset x2, which has the same contents as dataset y3, is stored in the master area M of the storage unit 100.
- the version management unit 203 of the development device 20 then obtains dataset x2 stored in the master area M of the storage unit 100 from the PLC 10, and stores it in the master area M of the storage unit 200. This allows both the PLC 10 and the development device 20 to perform version management of datasets x1, x2, y1, y2, and y3, as shown in FIG. 12.
- the version management unit 203 of the development device 20 first obtains the data set stored in the master area M of the storage unit 100 from the PLC 10 and stores it in the master area M of the storage unit 200.
- the user performs a merge operation on the data set stored in the master area M of the storage unit 200
- the data set creation unit 202 creates a data set
- the version management unit 203 stores the data set in the user area U of the storage unit 200.
- the version management unit 203 then transmits the new data set stored in the user area U of the storage unit 200 to the PLC 10, and the version management unit 103 of the PLC 10 stores the received data set in the user area U of the storage unit 100. After that, the user may try to apply the data set in the user area U to the master area M again.
- the program execution unit 104 of the PLC 10 executes the program contained in the data set stored in the storage unit 100, as in the first embodiment. This allows the user to easily manage the consistency between the source code that is subject to version control and the program executed by the PLC 10.
- the hardware configuration of the development device 20 according to the second embodiment is generally similar to that shown in FIG. 4. This is because, as explained in the first embodiment, the development device 20 is, for example, a personal computer on which an engineering tool program is installed.
- the version control system 1 according to the second embodiment the PLC 10 and the development device 20 can individually version-control data sets, while the PLC 10 and the development device 20 can be synchronized as necessary. Therefore, the version control system 1 according to the second embodiment can realize distributed version control.
- the PLC 10 executes a program included in a data set stored in the storage unit 100, so that the user can easily manage the consistency between the source code that is the subject of version control and the program executed by the PLC 10. Therefore, according to the version control system 1 according to the second embodiment, data related to a programmable device can be easily version-controlled in a distributed manner.
- the second embodiment is a modification of the first embodiment, it is assumed that there are multiple users, as in the first embodiment. However, even if there is only one user in the second embodiment, it is possible to perform distributed version management of a data set between the user's development device 20 and the PLC 10.
- the storage unit 100 of the PLC 10 has a master area M and one user area U. Also, the PLC 10 does not necessarily need to include a user authentication unit 102.
- the line in which data sets x1, y1, y2, and y3 are stored becomes the so-called "master line.”
- Data sets z1 and z2 of user B, who updated the data set later, are stored in the storage unit 100 of PLC 10 in a form branching off from the master line.
- distributed version management by multiple users can be realized without dividing into a master area M and a user area U. Merging of y3 and z2 is possible in the same way as in embodiments 1 and 2.
- a warning email may be sent to the user.
- the warning email may be sent to the user based on the information used for authentication when the user is authenticated by the user authentication unit 102.
- a dataset that has not been merged into the master area M for a long period of time is likely to have deviated significantly from the dataset in the master area M, so it is useful to issue a warning.
- the PLC 10 performs version management of the data set. Meanwhile, version management is also possible for programmable devices other than a PLC by providing functional units similar to the functional units of the PLC 10. For example, in the development of a program executed by a motion unit, the motion unit can perform version management of the data set related to the program executed by the motion unit by providing functional units similar to the functional units of the PLC 10.
- the PLC 10 and the development device 20 are equipped with a secondary storage device 1004.
- the secondary storage device 1004 may be provided outside the PLC 10 and the development device 20, and the PLC 10 and the development device 20 may be connected to the secondary storage device 1004 via an interface 1003.
- removable media such as a USB flash drive or a memory card can also be used as the secondary storage device 1004.
- PLC 10 and development device 20 may be configured with a dedicated circuit using an ASIC (Application Specific Integrated Circuit), FPGA (Field Programmable Gate Array), etc.
- ASIC Application Specific Integrated Circuit
- FPGA Field Programmable Gate Array
- some of the functions of PLC 10 and development device 20 may be realized by a dedicated circuit connected to interface 1003, for example.
- the programs used in PLC 10 and development device 20 can be stored and distributed on computer-readable recording media such as CD-ROMs (Compact Disc Read Only Memory), DVDs (Digital Versatile Discs), USB flash drives, memory cards, and HDDs. By installing such programs on a specific or general-purpose computer, the computer can function as PLC 10 and development device 20.
- CD-ROMs Compact Disc Read Only Memory
- DVDs Digital Versatile Discs
- USB flash drives Compact Discs
- memory cards Digital Versatile Discs
- HDDs Compact Disc Read Only Memory
- the computer can function as PLC 10 and development device 20.
- the above-mentioned program may also be stored in a storage device owned by another server on the Internet, and the program may be downloaded from that server.
- 1 version control system 10 PLC, 20 development device, 30 external system, 100 memory unit, 101 communication unit, 102 user authentication unit, 103 version control unit, 104 program execution unit, 200 memory unit, 201 communication unit, 202 data set creation unit, 203 version control unit, 1000 bus, 1001 processor, 1002 memory, 1003 interface, 1004 secondary storage device, M master area, U user area.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Data Mining & Analysis (AREA)
- Automation & Control Theory (AREA)
- Programmable Controllers (AREA)
- Stored Programmes (AREA)
Priority Applications (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP2023576433A JP7539593B1 (ja) | 2023-06-20 | 2023-06-20 | プログラム可能機器、バージョン管理方法及びプログラム |
| DE112023003976.3T DE112023003976T5 (de) | 2023-06-20 | 2023-06-20 | Programmierbare Vorrichtung, Entwicklungsvorrichtung, Versionsverwaltungssystem, Versionsverwaltungsverfahren und Programm |
| PCT/JP2023/022710 WO2024261848A1 (ja) | 2023-06-20 | 2023-06-20 | プログラム可能機器、開発装置、バージョン管理システム、バージョン管理方法及びプログラム |
| US19/123,779 US20260178308A1 (en) | 2023-06-20 | 2023-06-20 | Programmable device, version control method, and program |
| CN202380090102.4A CN120569710B (zh) | 2023-06-20 | 2023-06-20 | 可编程设备、版本管理方法及记录介质 |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/JP2023/022710 WO2024261848A1 (ja) | 2023-06-20 | 2023-06-20 | プログラム可能機器、開発装置、バージョン管理システム、バージョン管理方法及びプログラム |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2024261848A1 true WO2024261848A1 (ja) | 2024-12-26 |
Family
ID=92424449
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/JP2023/022710 Ceased WO2024261848A1 (ja) | 2023-06-20 | 2023-06-20 | プログラム可能機器、開発装置、バージョン管理システム、バージョン管理方法及びプログラム |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US20260178308A1 (cg-RX-API-DMAC7.html) |
| JP (1) | JP7539593B1 (cg-RX-API-DMAC7.html) |
| CN (1) | CN120569710B (cg-RX-API-DMAC7.html) |
| DE (1) | DE112023003976T5 (cg-RX-API-DMAC7.html) |
| WO (1) | WO2024261848A1 (cg-RX-API-DMAC7.html) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH06332676A (ja) * | 1993-05-18 | 1994-12-02 | Nippon Steel Corp | ソフトウェア共同版管理装置 |
| JPH0756721A (ja) * | 1993-08-11 | 1995-03-03 | Nippon Telegr & Teleph Corp <Ntt> | リビジョン管理方法 |
| JP2001166924A (ja) * | 1999-12-10 | 2001-06-22 | Mitsubishi Electric Corp | ソフトウェア開発物管理装置および管理方法 |
| JP2008282362A (ja) * | 2007-05-14 | 2008-11-20 | Keyence Corp | プログラム編集支援装置、コンピュータプログラム、プログラム編集支援方法及びplcシステム |
| JP2014056355A (ja) * | 2012-09-11 | 2014-03-27 | Toshiba Tec Corp | 情報処理装置、プログラム |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH08320782A (ja) * | 1995-03-17 | 1996-12-03 | Fujitsu Ltd | ソフトウェア生産物の管理装置 |
| JP3702294B2 (ja) * | 2000-05-15 | 2005-10-05 | Necソフトウェア東北株式会社 | ソフトウェア開発システム |
| US20180341666A1 (en) * | 2017-05-23 | 2018-11-29 | Synology Incorporated | Data protection method and associated apparatus |
| JP2019096243A (ja) * | 2017-11-28 | 2019-06-20 | ルネサスエレクトロニクス株式会社 | 半導体装置及びその故障検出方法 |
| CA3159118A1 (en) * | 2019-11-22 | 2021-05-27 | Cinchy Inc. | System for creating a dataset network |
| JP7679645B2 (ja) * | 2021-03-05 | 2025-05-20 | オムロン株式会社 | 制御装置、ならびに制御装置の記憶部に保存されたデータの入出力を管理するプログラムおよび方法 |
| BE1029521B1 (nl) * | 2021-06-23 | 2023-01-30 | Loctax | Een collaboratief gegevensbeheersysteem en werkwijze voor meerdere gebruikers |
-
2023
- 2023-06-20 US US19/123,779 patent/US20260178308A1/en active Pending
- 2023-06-20 WO PCT/JP2023/022710 patent/WO2024261848A1/ja not_active Ceased
- 2023-06-20 CN CN202380090102.4A patent/CN120569710B/zh active Active
- 2023-06-20 JP JP2023576433A patent/JP7539593B1/ja active Active
- 2023-06-20 DE DE112023003976.3T patent/DE112023003976T5/de active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH06332676A (ja) * | 1993-05-18 | 1994-12-02 | Nippon Steel Corp | ソフトウェア共同版管理装置 |
| JPH0756721A (ja) * | 1993-08-11 | 1995-03-03 | Nippon Telegr & Teleph Corp <Ntt> | リビジョン管理方法 |
| JP2001166924A (ja) * | 1999-12-10 | 2001-06-22 | Mitsubishi Electric Corp | ソフトウェア開発物管理装置および管理方法 |
| JP2008282362A (ja) * | 2007-05-14 | 2008-11-20 | Keyence Corp | プログラム編集支援装置、コンピュータプログラム、プログラム編集支援方法及びplcシステム |
| JP2014056355A (ja) * | 2012-09-11 | 2014-03-27 | Toshiba Tec Corp | 情報処理装置、プログラム |
Also Published As
| Publication number | Publication date |
|---|---|
| JPWO2024261848A1 (cg-RX-API-DMAC7.html) | 2024-12-26 |
| JP7539593B1 (ja) | 2024-08-23 |
| CN120569710B (zh) | 2026-05-08 |
| DE112023003976T5 (de) | 2025-07-24 |
| US20260178308A1 (en) | 2026-06-25 |
| CN120569710A (zh) | 2025-08-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7162677B2 (ja) | 特に適合性追跡用の、データを供給するためのコンピュータ実装方法 | |
| JP5963957B2 (ja) | 開発環境システム、開発環境装置、開発環境提供方法及びプログラム | |
| JP2022062705A (ja) | ブロックチェーン実装型データ移行監査証跡を生成するためのコンピュータ実装方法、コンピュータシステム、プログラム(ブロックチェーンで実装されるデータ移行監査証跡) | |
| JP2018152050A (ja) | ブロックチェーンバージョン制御システム | |
| CN106575227A (zh) | 自动软件更新框架 | |
| US10664263B2 (en) | Software management system, software updater, software updating method, and non-transitory computer-readable storage medium storing software update program | |
| JP2017120492A (ja) | 情報処理システム、及びその制御方法、プログラム | |
| US11122012B2 (en) | License utilization management system service suite | |
| JP2020197873A (ja) | 情報処理システム、及び情報処理システムの制御方法 | |
| KR20230050602A (ko) | 시스템 온 칩 설계 검증을 위한 테스트 자동화 시스템 및 방법 | |
| WO2022151888A1 (zh) | 数据共享方法及装置 | |
| WO2024002102A1 (zh) | 一种数据资产主动管理系统、计算设备及存储介质 | |
| JP2018072948A (ja) | 情報処理システム、更新方法、情報処理装置及びプログラム | |
| CN118369659A (zh) | 用于在共享管理环境中构建和验证数据库软件的技术 | |
| JP7679645B2 (ja) | 制御装置、ならびに制御装置の記憶部に保存されたデータの入出力を管理するプログラムおよび方法 | |
| CN115481421B (zh) | SELinux策略构建方法、装置、电子设备和可读存储介质 | |
| JP7539593B1 (ja) | プログラム可能機器、バージョン管理方法及びプログラム | |
| US8245182B2 (en) | Class selectable design sharing | |
| JP7462860B1 (ja) | プログラム可能機器、バージョン管理システム、バージョン管理方法及びプログラム | |
| CN111542790A (zh) | 用于处理软件项目的方法 | |
| Pandya et al. | Hands-on infrastructure as code with puppet | |
| Morimoto et al. | Windows Server 2012 Unleashed | |
| Waly | Learning Microsoft Azure Storage: Build large-scale, real-world apps by effectively planning, deploying, and implementing Azure storage solutions | |
| JP7238334B2 (ja) | 環境構築システム、管理装置、環境構築方法、およびプログラム | |
| Arundel | Puppet 3 Beginner's Guide |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| WWE | Wipo information: entry into national phase |
Ref document number: 2023576433 Country of ref document: JP |
|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 23942286 Country of ref document: EP Kind code of ref document: A1 |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 112023003976 Country of ref document: DE |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 202380090102.4 Country of ref document: CN |
|
| WWP | Wipo information: published in national office |
Ref document number: 112023003976 Country of ref document: DE |
|
| WWP | Wipo information: published in national office |
Ref document number: 202380090102.4 Country of ref document: CN |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 23942286 Country of ref document: EP Kind code of ref document: A1 |