KR20120109085A - System and method for managing version of distributed control system - Google Patents

Abstract

PURPOSE: A version management system of a distributed control system and a version management method are provided to control a system version of a board having problems proper to a system version of a current distributed control system so that the distributed control system is efficiently managed. CONSTITUTION: A version management system of a distributed control system is as follows. Types and versions of plural slave controllers are transmitted to a master controller. Whether or not the types and versions of each slave controller accord with versions for each type of the slave controller according to system version information is judged(S140). A system enable state is marked if the types and versions of the each slave controller accord with the versions for the each type of the slave controller. [Reference numerals] (AA) Start; (BB) No; (CC) Yes; (DD) Finish; (S110) Distribution control system booting; (S120) Performing a system enable command; (S130) Network initialization performing; (S140) Is system version information corresponded to network configuration information?; (S150) System enable; (S160) System vision error

Description

System and method for managing version of distributed control system

The present invention relates to a version control system and a version control method of a distributed control system.

Recently, researches on a method of controlling a complex motion of a robot using a distributed control system have been conducted. The distributed control system for controlling the robot is a system in which a plurality of controllers corresponding to a plurality of driving devices required for the operation of the robot independently control each driving device.

The plurality of controllers included in the distributed control system are connected to the network with predetermined hardware and software characteristics. The hardware characteristic may be represented by the version information of the device, and the software characteristic may be represented by the version information of the application program. In general, hardware and software versioning are separate. However, in a distributed control system in which a plurality of controllers are connected to a network, the distributed control system may not operate normally when a hardware characteristic or a software characteristic of any one controller is changed.

In particular, a large number of controllers are used in a distributed control system for robot control, and when a distributed control system does not operate normally, there is a difficulty in checking hardware and software characteristics of each controller.

There is a need for a method for efficiently managing a distributed control system for robot control.

One embodiment of the present invention is to provide a version control system and management method that can efficiently manage a distributed control system for robot control.

In a version control method of a distributed control system including a master controller and a plurality of slave controllers, the type and version of each of the plurality of slave controllers is transmitted to the master controller, wherein the plurality of slave controllers Determining whether each type and version is consistent with a type-specific version of the slave controller according to system version information, and a type-specific version of the slave controller according to the system version information If yes, and indicate the system enable state.

The system version information may include a master controller version, a slave controller version, an application programming interface (API) version, and a manual version.

The displaying of the system enable state may include displaying the system version information, displaying an available master controller version, an available slave controller version, and an available type of slave controller for the system version information. And displaying the types and versions of the plurality of slave controllers in the order of connection to the master controller.

If the type and version of each of the plurality of slave controllers do not match the version for each type of slave controller according to the system version information, the method may further include displaying a system version error status.

The displaying of the system version error status may include displaying the system version information, displaying an available master controller version, an available slave controller version, and an available type of slave controller for the system version information. And displaying a type and a version of the plurality of slave controllers in the order of being connected to the master controller, and displaying a version non-conformance instruction phrase for an incompatible version of the slave controller among the plurality of slave controllers. .

Each type of the plurality of slave controllers includes a type G including a general purpose input output (GPIO) module, a type L including a DC motor driving module, and an AC motor driving module on a function board constituting the plurality of slave controllers. It may be any one of a type H, a type BO including a BLDC motor driving module, and a type V including a commercial motor driving module.

According to another aspect of the present invention, a version control system of a distributed control system including a master controller and a slave controller, comprising: a code acquisition unit for scanning a board code attached to each of the master controller and the slave controller; A code recognizing unit which decodes the scanned board code to recognize basic information included in the board code; And a communication module configured to transmit the basic information to a board management server storing information about the master controller and the slave controller, and to receive distributed control system information corresponding to the basic information from the board management server. And a display unit for displaying the distributed control system information, wherein the distributed control system information includes task information, system information, master board information, and slave board information. Can be.

Here, the master board information may include a master label and a master version.

The slave board information may include a slave board label, a slave board version, and a slave board type.

The task information may include a task number and a task name, and the system information may include one or more of a system label, a master board number, a slave board number, a MAC address, an IP address, an ejection date, and a person in charge.

Administrators who manage distributed control systems can easily determine the system version of the board they are using and the board in question from where they have Internet access.

Administrators can efficiently manage distributed control systems by adjusting the system version of the board in question to the system version of the current distributed control system.

1 is a block diagram illustrating a distributed control system according to an exemplary embodiment of the present invention.
2A to 2E are block diagrams illustrating types of slave controllers according to an embodiment of the present invention.
3 is a flowchart illustrating a process of checking a system version of a distributed control system according to an embodiment of the present invention.
4 illustrates an output screen of a result of checking a system version of a distributed control system according to an exemplary embodiment of the present invention.
5 illustrates an output screen of a result of checking a system version of a distributed control system according to another exemplary embodiment of the present invention.
6 is a block diagram illustrating a version control system of a distributed control system according to an embodiment of the present invention.
7 illustrates a management screen for managing distributed control system information in a version control system of a distributed control system according to an embodiment of the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. The present invention may be embodied in many different forms and is not limited to the embodiments described herein.

In addition, in the various embodiments, components having the same configuration are represented by the same reference symbols in the first embodiment. In the other embodiments, only components different from those in the first embodiment will be described .

In order to clearly illustrate the present invention, parts not related to the description are omitted, and the same or similar components are denoted by the same reference numerals throughout the specification.

1 is a block diagram illustrating a distributed control system according to an exemplary embodiment of the present invention.

Referring to FIG. 1, the distributed control system includes a master controller 10 and a plurality of slave controllers 20-1, 20-2, 20-3, and 20-4. The plurality of slave controllers 20-1, 20-2, 20-3, and 20-4 are connected to the master controller 10 in a serial network manner. The number of slave controllers 20-1, 20-2, 20-3, and 20-4 connected to the master controller 10 in a serial network manner is not limited.

The master controller 10 includes a master processor 11, a master network module 12, a master reconfiguration area 13, an application programming interface (API) 14, a robot processor (RP) 15, and a network processor (NP). (16).

The master processing unit 11 performs interconnection management, monitoring management, input / output management, etc. of the master reconstruction area 13, the API 14, the RP 15, and the NP 16.

The master network module 12 connects the slave network modules 22-1, 22-2, 22-3, each of the plurality of slave controllers 20-1, 20-2, 20-3, 20-4 through a connection cable. Perform serial communication with at least one of 22-4).

The master reconstruction area 13 may include a field programmable gate array (FPGA) element including a soft processor and a memory or dedicated hardware logic. FPGA elements are easy to design and change, and relatively small in size, consume less power and generate heat. The master reconstruction area 13 may be equipped with a general purpose input output (GPIO) module, which is a digital or analog input / output module that performs input / output of sensing signals of various sensors and control signals of a robotic mechanism.

The API 14 connects the GPIO module mounted on the master reconstruction area 13 and the master processor 11, and transfers sensing signals of various sensors and control signals of the robotic mechanism to each other. The API 16 may connect an application module, in which a work logic of a robot, a robot related application program, and the like are stored, to the master processor 11. The API 14 connects the application module according to the type and version of various control modules or driving modules mounted in the slave reconfiguration areas 23-1, 23-2, 23-3, and 23-4 to the master processor 11. You can.

The RP 15 includes a movement generation module and a robot kinematics module for real time control of a plurality of robotic mechanisms. The movement path generation module generates a spatial movement path over time of a robot tool coordinate system or a robot base coordinate system in a work space in which a plurality of robotic mechanisms operate. The robot kinematics module calculates the operating position and torque of the motors included in the robot according to the robot type.

The NP 16 includes a communication application according to a network structure, a communication method, and the like between the master controller 10 and the plurality of slave controllers 20-1, 20-2, 20-3, 20-4, and the master controller 10 ) And serial communication between the plurality of slave controllers 20-1, 20-2, 20-3, and 20-4.

Each of the plurality of slave controllers 20-1, 20-2, 20-3, and 20-4 is a slave processor 21-1, 21-2, 21-3, 21-4, and a slave network module 22-1. , 22-2, 22-3, 22-4, and slave reconfiguration areas 23-1, 23-2, 23-3, and 23-4.

The slave processing units 21-1, 21-2, 21-3, and 21-4 manage input / output management and slave reconfiguration areas 22 in the slave network modules 22-1, 22-2, 22-3, and 22-4. -1, 22-2, 22-3, 22-4) to control the module and the like.

The first slave network module 22-1 performs serial communication with the master network module 12 and the second slave network module 22-2 connected by a connection cable, and the remaining slave network modules 22-2, 22. -3, 22-4) perform serial communication with each other via connecting cables.

The slave reconfiguration areas 23-1, 23-2, 23-3, and 23-4 may be composed of FPGA elements. The slave reconfiguration areas 23-1, 23-2, 23-3, and 23-4 include at least one of a GPIO module, a DC motor driving module, an AC motor driving module, a brush less DC (BLDC) motor driving module, and a commercial motor driving module. Either can be mounted.

Each of the master controller 10 and the plurality of slave controllers 20-1, 20-2, 20-3, and 20-4 may be composed of a processing board for performing a fixed function and a function board capable of changing a function. . For example, the master controller 10 includes a processing board including a master processor 11, a network module 12, an API 14, an RP 15, and an NP 16 and a master reconfiguration area 13. It can be configured as a functional board. Each of the plurality of slave controllers 20-1, 20-2, 20-3, and 20-4 is a slave processor 21-1, 21-2, 21-3, 21-4, and a network module 22-1. It may be configured as a processing board including 22-2, 22-3, and 22-4 and a functional board including slave reconfiguration areas 23-1, 23-2, 23-3, and 23-4.

When each of the master controller 10 and the plurality of slave controllers 20-1, 20-2, 20-3, and 20-4 is composed of a processing board and a function board, various functions of the robot are combined by combining the processing board and the function board. It is possible to adaptively configure a distributed control system suitable for.

Hereinafter, the type of the slave controller according to the combination of the processing board and the function board will be described.

2A to 2E are block diagrams illustrating types of slave controllers according to an embodiment of the present invention.

Referring to FIG. 2A, the processing board 220 of the slave controller includes a slave processing unit 221 and a slave network module 222. The function board 230 of the slave controller includes a GPIO module 231. The processing board 220 and the function board 230 may be connected by a connector or a connection cable.

The slave processor 221 controls serial communication of the slave network module 222 and input / output of sensing signals and control signals of the GPIO module 231. The slave network module 222 performs serial communication with the master network module or the other slave network module. The GPIO module 231 performs input / output of sensing signals of various sensors and digital or analog control signals of the robotic mechanism.

A type of slave controller including a function board 230 including a GPIO module 231 and a processing board 220 including a network module 222 and a slave processing unit 221 is referred to as a 'type G'.

Referring to FIG. 2B, the processing board 220 of the slave controller includes a slave processing unit 221 and a slave network module 222. The function board 230 of the slave controller includes a DC motor drive module 232.

The slave processor 221 controls the serial communication of the slave network module 222 and the input / output of the drive control signal of the DC motor driving module 232. The DC motor drive module is a module connected to the DC motor controlling the robot mechanism and controlling the driving of the DC motor. In the DC motor, the rotation is linearly proportional to the applied voltage and the starting torque is large.

A type of slave controller including a function board 230 and a processing board 220 including the DC motor driving module 232 is referred to as a 'type L'.

Referring to FIG. 2C, the processing board 220 of the slave controller includes a slave processing unit 221 and a slave network module 222. The function board 230 of the slave controller includes an AC motor drive module 233.

The slave processor 221 controls the serial communication of the slave network module 222 and the input / output of the drive control signal of the AC motor drive module 233. The AC motor drive module is a module that is connected to an AC motor that controls the robot mechanism and controls the driving of the AC motor. The AC motor is fast in response and can output instantaneous maximum torque at high speed.

The type of slave controller including the function board 230 and the processing board 220 including the AC motor driving module 233 is referred to as 'type H'.

Referring to FIG. 2D, the processing board 220 of the slave controller includes a slave processing unit 221 and a slave network module 222. The function board 230 of the slave controller includes a BLDC motor drive module 234.

The slave processor 221 controls the serial communication of the slave network module 222 and the input / output of the drive control signal of the brush less DC (BLDC) motor driving module 234. The BLDC motor driving module is a module connected to the BLDC motor that controls the robot mechanism and controls the driving of the BLDC motor. BLDC motors have a longer life and greater output than DC motors.

A type of slave controller including a function board 230 and a processing board 220 including the BLDC motor driving module 234 is referred to as a 'type BO'.

Referring to FIG. 2E, the processing board 220 of the slave controller includes a slave processing unit 221 and a slave network module 222. The function board 230 of the slave controller includes a commercial motor drive module 235.

The slave processor 221 controls the serial communication of the slave network module 222 and the input / output of the drive control signal of the commercial motor driving module 235. The commercial motor drive module is a module connected to a commercial motor for controlling the robot mechanism and controlling the driving of the commercial motor.

A type of slave controller including a function board 230 and a processing board 220 including a commercial motor driving module 235 is referred to as a 'type V'.

As described above, the slave controller may be configured in various types such as G, L, H, BO, and V according to the combination of the function board 230 and the processing board 220. The master controller and the slave controllers of various types can be connected in various combinations suitable for the characteristics of the robot. That is, the distributed control system may be configured in various ways according to the types of the plurality of slave controllers connected to the master controller.

In order to maintain and manage various distributed control systems, versions of the master controller, types of a plurality of slave controllers connected to the master controller, APIs, manuals, and the like must be integratedly managed. The manual includes the command of the operator of the distributed control system or the driving rules of the distributed control system according to specific conditions.

To this end, the system version of the distributed control system may be defined as the version of the master controller, the version of the slave controller, the API version, the manual version. The version indicates the degree of upgrade of the device or program. In general, higher versions of devices or programs may accept lower versions of devices or programs, while lower versions of devices or programs may not accommodate higher versions of devices or programs.

For example, system version 1.1.1.1 means version 1 of the master controller, version 1 of the slave controller, API version 1, and manual version 1. The version of the slave controller may be determined according to the version for each type of slave controller. That is, the version of the master controller usable by the system version and the version for each type of the available slave controllers may be indicated.

By checking the system version of the distributed control system in the network initialization process between the master controller and the slave controller, whether the distributed control system is normally configured or operable can be detected.

3 is a flowchart illustrating a process of checking a system version of a distributed control system according to an embodiment of the present invention.

Referring to FIG. 3, power is supplied to the distributed control system and the system is booted (S110). In the system booting process, the master processor 11 connects the API 14, the RP 15, the NP 16, the master reconfiguration area 13, and the master network module 12 included in the master controller 10. Check and initialize.

When the connection state check and initialization are normally performed in the master controller 10, a system enable command is performed (S120).

According to the system enable command, the master controller 10 performs network initialization with a plurality of slave controllers 20-1, 20-2, 20-3, and 20-4 (S130). The master processor 11 stores information about the system version, and a list of the types and versions of compatible slave controllers. In the network initialization process, each slave controller 20-1, 20-2, 20-3, 20-4 transmits its type and version information to the master controller 10 as network configuration information.

The master controller 10 determines whether the stored system version information and the network configuration information match (S140). Here, the version information of the slave controller included in the system version information indicates a version for each type of slave controller. Here, the network configuration information includes the type and version information of each slave controller according to the connection order of the plurality of slave controllers 20-1, 20-2, 20-3, and 20-4 connected to the master controller 10. do.

That is, the master controller 10 determines whether the type and version of each slave controller 20-1, 20-2, 20-3, and 20-4 match the version for each type of slave controller according to the system version information. do.

If the stored system version information and the received network configuration information match, the master controller 10 displays a system enable state (S150). The system enable state means a state in which a network between a master controller and a plurality of slave controllers is normally connected and the distributed control system can normally operate.

If the stored system version information and the network configuration information does not match, the master controller 10 displays a system version error state (S160). The system version error state indicates a state in which the distributed control system cannot operate normally because the network configuration between the master controller and the plurality of slave controllers does not match the stored system version.

One example of a system enable state and a system version error state is shown in FIGS. 4 and 5.

4 illustrates an output screen of a result of checking a system version of a distributed control system according to an exemplary embodiment of the present invention.

Referring to FIG. 4, types and versions of a plurality of slave controllers connected to a master controller are checked during a network initialization process of a distributed control system. The inspection result is an example of a screen indicating a system enable state.

(A) The system version information stored in the master controller is displayed. The system version information is expressed as 'System Version 1.1.1.1', which indicates version 1 of the master controller, version 1 of the slave controller, API version 1, and manual version 1.

(B) As detailed information of the stored system version information, the version of the available master controller, the version of the available slave controller, and the version by type of the available slave controller are displayed. Here, version M = 1 of master controller, version S = 1 of slave controller, version V = 1 of type V of slave controller, version L = 1 of type L of slave controller, version G = 1 of type G of slave controller , Type H of the slave controller, version H / BO of BO.

(C) Network configuration information of the distributed control system is displayed. Network configuration information of the distributed control system may be represented by the type and version of the slave controller in the order of connection to the master controller. Here, '[0] type BO 1' indicates that the type of slave controller first connected to the master controller is BO and the version is 1. '[1] type L 1' indicates that the type of slave controller second connected to the master controller is L and the version is 1. '[2] type BO 1' indicates that the slave controller's third type connected to the master controller is BO and its version is 1. '[3] type V 1' indicates that the slave controller connected to the master controller is of type V and version is 1.

Since the type and version of the slave controller connected to the master controller matches the type-specific version of the slave controller available for the system version, the system enable status is displayed.

4 and 5 to be described later, when the version information of each type of slave controller available for system version information is displayed, in some cases, when the connection order of the slave controller is important, order information is included in the system version information and network configuration information. It may be further included will be apparent to those skilled in the art in view of the technical spirit of the present invention.

5 illustrates an output screen of a result of checking a system version of a distributed control system according to another exemplary embodiment of the present invention.

Referring to FIG. 5, types and versions of a plurality of slave controllers connected to a master controller are checked in a network initialization process of a distributed control system. As a result of the check, it is an example of a screen showing the system version error status.

(D) The system version information stored in the master controller is displayed as 'System Version 1.2.1.1', which indicates version 1 of the master controller, version 2 of the slave controller, API version 1, and manual version 1.

(E) The available master controller version, available slave controller version, and available slave controller type version are displayed for the stored system version information. Here, version M = 1 of master controller, version S = 2 of slave controller, version V = 1 of type V of slave controller, version L = 2 of type L of slave controller, version G = 1 of type G of slave controller , Type H of the slave controller, version H / BO of BO.

(F) Network configuration information of the distributed control system is displayed. Network configuration information of the distributed control system may be represented by the type and version of the slave controller in the order of connection to the master controller. Here, '[1] type L 1' indicates that the type of the slave controller second connected to the master controller is L and the version is 1, which does not match the version L = 2 of the type L of the available slave controller. A version non-conformance indication phrase of 'No compatible version of slave' may be displayed for an incompatible version of a slave controller.

Since the type and version of the slave controller connected to the master controller do not match the type-specific version of the slave controller available for the system version, a system version error condition is displayed.

As such, in a distributed control system including a master controller and a plurality of slave controllers, if a system version and a type or version of one slave controller do not match, an error may occur in the system version and the distributed control system may not operate normally. have.

Hereinafter, a management screen for managing a version control system and distributed control system information that can efficiently manage a system version of a distributed control system and easily resolve a system version error will be described with reference to FIGS. 6 and 7.

6 is a block diagram illustrating a version control system of a distributed control system according to an embodiment of the present invention. 7 illustrates a management screen for managing distributed control system information in a version control system of a distributed control system according to an embodiment of the present invention.

A version control system 300 will be described with reference to FIG. 6.

The version control system 300 includes a code acquirer 310, a code recognizer 320, a code protocol storage 330, a communication module 340, and a display 350.

The code acquirer 310 scans a board code attached to each of the master controller and the slave controller. The board code can be attached to the processing board or functional board in the production of the master controller and the slave controller. The board code contains basic information such as production date, inspection date and board label. The board code may be a barcode, a QR code, a data matrix, a maxi code, a PDF-417, a color code, an icon lab code, or the like.

The code recognizer 320 decodes the board code obtained by the code acquirer 310 to recognize basic information included in the board code. The code protocol storage unit 330 stores various types of protocols for decoding board codes, and the code recognition unit 320 decodes various types of board codes using protocols stored in the code protocol storage unit 330. can do.

The code recognition unit 320 transmits basic information included in the board code to the board management server 400 through the communication module 340.

The communication module 340 includes communication protocols such as a wide area network (WAN), a local area network (LAN), a transmission control protocol / Internet protocol (TCP / IP) internet, and a mobile communication network.

The board management server 400 is a server that stores and manages information about a distributed control system and various master controllers and slave controllers constituting the board in connection with basic information of a board code. The board management server 400 transmits information about the distributed control system corresponding to the board code transmitted from the version control system 300 to the version management system 300. The distributed control system information may include task information, system information, master board information, slave board information, and the like.

The display unit 350 displays distributed control system information received through the communication module 340 on the management screen.

An example of a management screen on which distributed control system information is displayed will be described with reference to FIG. 7.

The version control system 300 may display distributed control system information received from the board management server 400 on a management screen in response to basic information included in a board code of a master controller or a slave controller.

The management screen may display task information, system information, master board information, slave board information, and the like. The task information may include a task number, a task name, and the like. The system information may include the system label, the number of master boards, the number of slave boards, the MAC address, the IP address, the person in charge, and the ejection date. The master board information may include a master label, a master version, and the like. The slave board information may include a slave board label, a slave board version, a slave board type, and the like.

A method of operating the version control system 300 will be described with reference to FIGS. 6 and 7.

Assembly of distributed control system

In assembling the distributed control system, the manager may assemble the distributed control system using the version control system 300. The manager may scan the board code attached to the master controller using the code fold unit 310 of the version control system 300.

The scanned board code is decoded by the code recognition unit 320 and transmitted to the board management server 400. The board management server 400 transmits distributed control system information including the task information, system information, master board information, slave board information, etc. corresponding to the scanned board code to the version management system 300. Distributed control system information corresponding to the master controller is displayed on the management screen.

The administrator can check the slave board information of the slave board constituting the distributed control system together with the master board, that is, the label of the slave board, the version of the slave board, and the type of the slave board from the distributed control system information displayed on the management screen. The administrator can create a distributed control system by assembling the master board and the slave board by dispensing the slave board corresponding to the slave board information from the management warehouse.

When assembling the distributed control system, the administrator can quickly find the slave board corresponding to the master board, so that the distributed control system can be made quickly and accurately.

In addition, the administrator may check the information on the distributed control system by scanning the board code attached to the master board or slave board of the distributed control system using the version control system 300 to manage the distributed control system.

<Check of distributed control system>

In the event of a failure of the distributed control system, the administrator may check the distributed control system using the version control system 300.

If the system version information stored in the master controller and the network configuration information do not match during network initialization of the distributed control system, a system version error status is displayed as illustrated in FIG. 5.

When the system version error status is displayed, the administrator may scan the board code attached to the master controller of the corresponding distributed control system using the code acquirer 310 of the version control system 300.

The scanned board code is decoded by the code recognition unit 320 and transmitted to the board management server 400. The board management server 400 transmits distributed control system information including the task information, system information, master board information, slave board information, etc. corresponding to the scanned board code to the version management system 300. Distributed control system information corresponding to the master controller is displayed on the management screen.

The administrator can check the slave board information that can replace the failed slave board in the distributed control system information displayed on the management screen. That is, the manager can check slave board information having a history of configuring the distributed control system together with the master board, that is, the label of the slave board, the version of the slave board, and the type of the slave board. The administrator can reassemble the distributed control system by detaching the failed slave board from the distributed control system and finding the appropriate slave board.

As described above, the administrator of the distributed control system using the version management system 300 connected to the board management server 400 through a communication module, the master currently in use or problems in the assembly and inspection process of the distributed control system Information about boards and slave boards can be quickly identified and appropriate action can be taken.

It is to be understood that both the foregoing general description and the following detailed description of the present invention are illustrative and explanatory only and are intended to be illustrative of the invention and are not to be construed as limiting the scope of the invention as defined by the appended claims. It is not. Therefore, those skilled in the art will understand that various modifications and equivalent other embodiments are possible. Accordingly, the true scope of the present invention should be determined by the technical idea of the appended claims.

10: master controller
20: slave controller
220: slave controller processing board
230: slave controller function board
300: version control system
310: code acquisition unit
320: code recognition unit
330: code protocol storage
340: communication module
350: display unit

Claims (10)

In the version control method of a distributed control system comprising a master controller and a plurality of slave controllers,
Communicating the type and version of each of the plurality of slave controllers to the master controller;
Determining whether a type and a version of each of the plurality of slave controllers coincide with a version for each type of slave controller according to system version information; And
And displaying a system enable state when the type and version of each of the plurality of slave controllers coincide with the type-specific version of the slave controller according to the system version information. The method according to claim 1,
The system version information includes a master controller version, a slave controller version, an application programming interface (API) version and a manual version. The method according to claim 1 or 2,
The displaying of the system enable state may include:
Displaying the system version information;
Displaying an available master controller version, an available slave controller version, and an available type of version of the slave controller with respect to the system version information; And
And displaying the types and versions of the plurality of slave controllers in the order of being connected to the master controller. The method according to claim 1 or 2,
And if the type and version of each of the plurality of slave controllers do not match the version of each type of slave controller according to the system version information, displaying a system version error status. Way. 5. The method of claim 4,
The displaying of the system version error status may include:
Displaying the system version information;
Displaying an available master controller version, an available slave controller version, and an available type of version of the slave controller with respect to the system version information; And
And displaying a type and version of the plurality of slave controllers in order of being connected to the master controller, and displaying a version non-conformance instruction phrase for an incompatible version of the slave controller among the plurality of slave controllers. Version control method of distributed control system. The method according to claim 1,
Each type of the plurality of slave controllers includes a type G including a general purpose input output (GPIO) module, a type L including a DC motor driving module, and an AC motor driving module on a function board constituting the plurality of slave controllers. A type H, a type BO including a BLDC motor drive module, and a type V including a commercial motor drive module. In the version control system of a distributed control system including a master controller and a slave controller,
A code obtaining unit scanning a board code attached to each of the master controller and the slave controller;
A code recognizing unit which decodes the scanned board code to recognize basic information included in the board code;
A communication module which transmits the basic information to a board management server storing information about the master controller and the slave controller and receives distributed control system information corresponding to the basic information from the board management server; And
Including a display unit for displaying the distributed control system information,
The distributed control system information includes task information, system information, master board information and slave board information. The method of claim 7, wherein
And the master board information includes a master label and a master version. The method of claim 7, wherein
The slave board information includes a slave board label, a slave board version and a slave board type. The method of claim 7, wherein
The task information includes a task number and a task name,
The system information may include at least one of a system label, a number of master boards, a number of slave boards, a MAC address, an IP address, an ejection date, and a person in charge.

Images