CN-120569710-B - Programmable device, version management method, and recording medium

Abstract

The PLC (10) has a storage unit (100) for storing a1 st data set, a version management unit (103) for performing version management on the 1 st data set stored in the storage unit (100), and a communication unit (101) for transmitting the 1 st data set version-managed by the version management unit (103) to a development device, receiving a2 nd data set created based on the transmitted 1 st data set, performing version management by the development device in association with the 1 st data set, and storing the 2 nd data set received by the communication unit (101) in association with the 1 st data set in the storage unit (100), and performing version management in association with the 1 st data set.

Inventors

• LI WEIHAO

Assignees

• 三菱电机株式会社

Dates

Publication Date

20260508

Application Date

20230620

Claims (3)

1. 1. A programmable apparatus, having: a1 st storage unit including a1 st main area and a1 st user area, storing a1 st data set in the 1 st main area; A1 st version management unit that version-manages the 1 st data set held in the 1 st main area of the 1 st storage unit; A1 st transmitting unit that transmits the 1 st data set version-managed by the 1 st version management unit to a development device, and A1 st receiving unit that receives a2 nd data set created based on the 1 st data set transmitted by the 1 st transmitting unit, version-managed by the developing device in association with the 1 st data set, The version 1 management unit saves the 2 nd data set received by the 1 st receiving unit in association with the 1 st data set in the 1 st user area of the 1 st storage unit, performs version management in association with the 1 st data set, When it is desired to store the 2 nd data set stored in the 1 st user area in the 1 st main area based on a user operation, the 1 st version management unit determines whether or not the 1 st data set corresponding to the 2 nd data set and the 1 st data set stored in the 1 st main area match, and when the 1 st data set matches, allows the storage, and when the 1 st data set does not match, denies the storage.
2. 2. A version management method, wherein, The programmable device version manages a1 st data set held in said 1 st main area of a1 st storage unit comprising a1 st main area and a1 st user area, The programmable device transmits the version-managed 1 st data set to a development device, The programmable device receives a 2 nd data set created based on the 1 st data set transmitted, version-managed by the development means in association with the 1 st data set, The programmable device saves the received 2 nd data set in association with the 1 st data set in the 1 st user area of the 1 st storage unit, performs version management in association with the 1 st data set, When it is desired to store the 2 nd data set stored in the 1 st user area in the 1 st main area based on a user operation, it is determined whether or not the 1 st data set corresponding to the 2 nd data set and the 1 st data set stored in the 1 st main area match, and when the data sets match, the storage is permitted, and when the data sets do not match, the storage is refused.
3. 3. A recording medium which is a computer-readable recording medium storing a program for causing a computer to: version management is performed on a1 st data set held in a1 st main area of a1 st storage unit including the 1 st main area and a1 st user area, The 1 st data set subjected to version management is sent to a development device, Receiving a2 nd data set created based on the 1 st data set transmitted, version-managed by the development device in association with the 1 st data set, Saving the received 2 nd data set in association with the 1 st data set in the 1 st user area of the 1 st storage unit, performing version management in association with the 1 st data set, When it is desired to store the 2 nd data set stored in the 1 st user area in the 1 st main area based on a user operation, it is determined whether or not the 1 st data set corresponding to the 2 nd data set and the 1 st data set stored in the 1 st main area match, and when the data sets match, the storage is permitted, and when the data sets do not match, the storage is refused.

Description

Programmable device, version management method, and recording medium Technical Field The present invention relates to a programmable device, a development apparatus, a version management system, a version management method, and a computer-readable recording medium storing a program. Background A programmable device for a programmable logic controller, a motion unit, or the like FA (Factory Automation) executes a program created by development of a user to control a controlled device. In order to perform change point management, progress management, and the like at the time of development, it is necessary to perform version management on a program and data related to the program. As a technique related to the above-described situation, for example, non-patent document 1 discloses a technique for supporting development of control software by a plurality of persons by using Git, which is an open-source distributed version management system. Non-patent document 1: the rock village Shen Tailang, the "on-gate Git" is the net FA in the form of the mechanical environment, the "o" is the net of the mechanical environment, [ online ],2019/03/25,OMRON TECHNICS, [ 3 months and 10 days of 5 years search ], the website < URL: https:// www.omron.com/jp/ja/technology/omrontechnics/2019/20190315-iwamura.html > Disclosure of Invention In the technology described in non-patent document 1, the programmable device itself is independent of the distributed version management system. Therefore, there is a need to artificially manage the matching between the source code managed by the distributed version management system and the program executed by the programmable device, and the burden on the user becomes large. For example, consider the possibility that a program executed by a programmable device is not based on a program generated by source code managed by a distributed version management system. In view of the above, an object of the present invention is to provide a programmable device or the like capable of easily performing distributed version management of data related to the programmable device. In order to achieve the above object, the present invention relates to a programmable device having: a1 st storage unit that stores the 1 st data set; a1 st version management unit that performs version management of the 1 st data set stored in the 1 st storage unit; A1 st transmitting unit that transmits the 1 st data set version-managed by the 1 st version management unit to a development device, and A1 st receiving unit that receives a2 nd data set created based on the 1 st data set transmitted by the 1 st transmitting unit, version-managed by the developing device in association with the 1 st data set, The version 1 management unit stores the 2 nd data set received by the 1 st receiving unit in association with the 1 st data set in the 1 st storage unit, and performs version management in association with the 1 st data set. ADVANTAGEOUS EFFECTS OF INVENTION According to the present invention, distributed version management of data related to a programmable device can be easily performed. Drawings Fig. 1 is a diagram showing an overall configuration of a version management system according to embodiment 1 of the present invention. Fig. 2 is a diagram showing an example of version management implemented by the version management system according to embodiment 1 of the present invention. Fig. 3 is a block diagram showing a functional configuration of a PLC according to embodiment 1 of the present invention. Fig. 4 is a diagram showing an example of a hardware configuration of a PLC according to embodiment 1 of the present invention and a development device according to embodiment 2 of the present invention. Fig. 5 is a flowchart showing an example of operations of version management by the PLC according to embodiment 1 of the present invention. Fig. 6 is a diagram showing an overall configuration of a version management system according to a modification of embodiment 1 of the present invention. Fig. 7 is a block diagram showing a functional configuration of a development device according to embodiment 2 of the present invention. Fig. 8 is a diagram illustrating an example of distributed version management implemented by the version management system according to embodiment 2 of the present invention. Fig. 9 is a diagram illustrating an example of distributed version management implemented by the version management system according to embodiment 2 of the present invention. Fig. 10 is a diagram illustrating an example of distributed version management implemented by the version management system according to embodiment 2 of the present invention. Fig. 11 is a diagram illustrating an example of distributed version management implemented by the version management system according to embodiment 2 of the present invention. Fig. 12 is a diagram illustrating an example of distributed version management implemented by the version manage