Operating control device and operating control system

Abstract

Operating control device (2) for controlling a control target device by executing several additional modules, wherein the operating control device (2) comprises: a memory (25) which stores the several additional modules and a user program, which is a program to be executed for controlling the target control device; an add-on module classification unit (241) which classifies the multiple add-on modules based on an add-on module classification condition which contains the user program and serves to classify add-on modules, such that each of the multiple add-on modules in which a first functionality is used is classified as an activated add-on module which is to be used to execute the user program, and each add-on module of the multiple add-on modules which is not an activated add-on module is classified as a deactivated add-on module which is not to be used to execute the user program, wherein the first functionality is a functionality of the control target device and is to be used to execute a function contained in the user program; and a control unit (242) which executes the activated add-on module according to the user program in order to control the control target device.

Description

Area

[0001] The present disclosure relates to an operational control device in which an add-on module is implemented, and to an operational control system. background

[0002] Patent document 1 discloses a numerical control device that determines the resource utilization of a necessary functional module by setting an option that activates or deactivates a specific functional module and a parameter that relates to the performance of the activated functionality, and adds and removes the functional module. Patent document 2 discloses an engine control unit for a vehicle control unit assembly that provides a multitude of functions and configures its functionality itself by activating selected pre-configured functions, as well as a method for its tamper-proof configuration. To activate a pre-configured function, the engine control unit sends a signal to detect the presence of connected component control units.It then requests activation information from a component control unit it detects as present, in order to enable a function prepared in the control unit. Upon receiving activation information, it activates the corresponding prepared function. Citation listPatent literature Patent literature 1: JP 2018 - 185 734 A Patent literature 2: DE 197 20 285 A1 Brief description: Technical problem

[0003] However, in newer operational control devices, functionalities that can be extended by installing additional modules have been diversified. It is therefore necessary to verify the relationship between an initial functionality included in the operational control device and an extended functionality to be implemented by an additional module, using a document such as a manufacturer's operating manual.Therefore, there is a case in which working time is required to associate the extended functionality to be implemented by the add-on module with the initial functionality, an add-on module to be activated cannot be set correctly due to a lack of understanding of the extended functionality to be implemented by the add-on module and the initial functionality, and optimization of a configuration of the add-on module to be activated is difficult.

[0004] As described in patent literature 1, even if a user decides to activate or deactivate the add-on module using the parameter and option, and ceases using the resource, it is difficult to correctly activate an add-on module necessary for executing a user program. This creates a problem in that the control duration of the operating control device becomes long if the add-on module to be activated is not correctly configured in the operating control device and the add-on module, which is unnecessary for controlling a target device by the operating control device, is also activated.

[0005] The present disclosure was made in view of the above, and one objective is to obtain an operating control device capable of correctly setting an add-on module necessary for the execution of a user program in an operating control device in which several add-on modules are implemented. Solution to the problem

[0006] To solve the above problem and achieve a goal, an operating control device according to the present disclosure is an operating control device that controls a target control device by executing several additional modules. The operating control device comprises: a memory that stores a user program, which is a program to be executed to control the target control device, and several additional modules;An add-on module classification unit that classifies several add-on modules based on an add-on module classification condition, which contains the user program and serves to classify the add-on modules, such that each add-on module in which a first functionality is used is classified as an activated add-on module to be used for executing the user program, and each add-on module of the several add-on modules that is not an activated add-on module is classified as a deactivated add-on module that is not to be used for executing the user program, wherein the first functionality is a functionality of the target control device to be used for executing a function contained in the user program; and a control unit that executes the activated add-on module according to the user program in order to control the target control device. Advantageous effects of the invention

[0007] An operating control device according to the present disclosure enables an additional module necessary for the execution of a user program to be correctly set in an operating control device in which several additional modules are implemented. Brief description of drawings Fig. Figure 1 is a diagram showing a configuration of an operational control system according to a first embodiment. Fig. Figure 2 is a diagram showing a functional configuration of a development tool for the operational control system according to the first embodiment. Fig. Figure 3 is a view showing an example of a generation screen for an add-on module classification condition according to the first embodiment. Fig. Figure 4 is a diagram showing a functional configuration of an operating control device of the operating control system according to the first embodiment. Fig. Figure 5 is a flowchart showing a processing procedure of the development tool of the operational control system according to the first embodiment. Fig. Figure 6 is a flowchart showing a processing procedure of the operational control device of the operational control system according to the first embodiment. Fig. Figure 7 is a view showing an example of a display screen of a processing result of a required add-on module classification functionality on a display unit of the development tool according to the first embodiment. Description of embodiments

[0008] An operational control device and an operational control system according to one embodiment are described in detail below with reference to the drawings. It should be noted that the present disclosure is not limited by this embodiment. First embodiment.

[0009] Fig. Figure 1 is a diagram showing a configuration of an operational control system 100 according to a first embodiment. The operational control system 100 is a factory automation system (FA system). The operational control system 100 comprises a development tool 1, an operational control device 2, a servo amplifier 3, and a servo motor 4.

[0010] The development tool 1 is connected to the operating control unit 2 via a communication line 6 and is capable of wired communication with the operating control unit 2. It should be noted that communication between the development tool 1 and the operating control unit 2 can also be wireless. It should also be noted that the development tool 1 is only connected to the operating control unit 2 when necessary.

[0011] The control unit 2 is connected to the servo amplifier 3 via a communication line 7 and is capable of wired communication with the server amplifier 3. It should be noted that communication between the control unit 2 and the servo amplifier 3 can also be wireless. The control unit 2 executes firmware according to a user program to control the servo amplifier 3, thereby controlling the operation of the servo motor 4. Furthermore, the control unit 2 executes several additional modules according to the user program to control the servo amplifier 3, thereby controlling the operation of the servo motor 4. The additional module is software for executing extended functionality, which differs from the initial functionality performed by executing firmware according to the user program in the control unit 2.

[0012] The servo amplifier 3 is connected to the servo motor 4 via a communication line 8 and is capable of wired communication with the servo motor 4. It should be noted that communication between the servo amplifier 3 and the servo motor 4 can also be wireless.

[0013] Fig. Figure 2 is a diagram showing a functional configuration of the development tool 1 of the operational control system 100 according to the first embodiment. The development tool 1 comprises an input unit 11 into which information is entered, a communication unit 12 which communicates with the operational control device 2, a display unit 13 which displays information, a processor 14 which executes various processes, and a memory 15 which stores information.

[0014] Various types of information from outside the development tool 1 are entered into the input unit 11. Examples of input units 11 include devices such as a keyboard, a mouse, and a touchpad, and information is entered through user interaction. The communication unit 12 performs bidirectional communication with the operating control unit 2. The display unit 13 displays information on a screen.

[0015] The processor 14 is a central processing unit (CPU), a processing device, an arithmetic device, a microprocessor, a microcomputer, or a digital signal processor (DSP). The memory 15 comprises random-access memory (RAM), read-only memory (ROM), flash memory, EPROM (erasable programmable read-only memory), or EEPROM (electrically erasable programmable read-only memory) (registered trademark), as well as a hard disk drive (HDD) or solid-state drive (SSD). A processing program of the development tool 1 is stored in memory 15. The processor 14 executes a program that is stored in memory 15.

[0016] Fig. Figure 2 shows a functional configuration of the development tool 1, which is implemented using the processor 14. The development tool 1 comprises a user program generation unit 141, an add-on module classification condition generation unit 142, and a display processing unit 143.

[0017] The user program generation unit 141 causes the display unit 13 to show a user program generation screen for creating a user program and processes the creation or editing of the user program in response to a user operation performed with the input unit 11. The user program is a program that is to be executed by the operating control unit 2 to control the servo amplifier 3 in order to control the operation of the servo motor 4. The user program generation unit 141 causes the memory 15 to store the created or edited user program. The functionality of creating and editing a program in the user program generation unit 141 is equivalent to the editing functionality of a general development tool.

[0018] This means that the development tool 1 includes functionality as a support device that facilitates the creation of a user program. This user program is executed by the control unit 2 to control the servo amplifier 3, thereby controlling the operation of the servo motor 4. The user creates the user program using the development tool 1, causes the development tool 1 to save the created user program, and then transfers the user program to the control unit 2.

[0019] The add-on module classification condition generation unit 142 generates an add-on module classification condition containing a user program. This program is executed by the operating control unit 2 to control the servo motor 4. The unit causes the memory 15 to store the add-on module classification condition and transmits the add-on module classification condition to the operating control unit 2. The add-on module classification condition generation unit 142 processes the generation of the add-on module classification condition in response to a user operation performed with the input unit 11. The add-on module classification condition generation unit 142 transmits the generated add-on module classification condition to the operating control unit 2 via the communication unit 12 in response to a user operation performed with the input unit 11.

[0020] This means that development tool 1 generates the add-on module classification condition in response to user input. This condition serves to shorten the control duration when the servo motor 4 is operated according to the user program by the operating control unit 2, and also to reduce the amount of memory used in the execution memory when the servo motor 4 is operated according to the user program by the operating control unit 2. The add-on module classification condition is a condition that serves as a classification criterion for classifying an add-on module, which is to be activated and executed by the operating control unit 2, as described later.

[0021] Fig. Figure 3 is a view showing an example of a generation screen for an add-on module classification condition according to the first embodiment. As in Fig. As shown in Figure 3, the display unit 13 displays: an add-on module display part 131, which shows the name of an add-on module and an add-on module usage functionality to which a user refers when setting an add-on module classification condition; a settings file display part 132, which displays a functionality settings file that is contained in an add-on module classification condition; and a user program settings display part 133, which displays a user program that is contained in an add-on module classification condition.

[0022] The functionality settings file is a usage functionality setting information file that specifies a usage functionality to be used for executing the user program. This usage functionality setting information defines a functionality to be used for executing the user program from among the functionalities available in the operating control device 2. This means that the usage functionality setting information is information that specifies the usage functionality to be used for executing the user program from among the functionalities available for the operating control device 2. Furthermore, the usage functionality specified in the usage functionality setting information is, in particular, a functionality to be used with a control condition that is set when the user program is executed.

[0023] The add-on module display unit 131 shows the names of add-on modules that can be used by the operating control unit 2 and their add-on module usage functionalities. An add-on module usage functionality is a function that can be used by the operating control unit 2 and is used when the add-on module is executed by the operating control unit 2 according to the user program. Examples of add-on modules that can be executed by the operating control unit 2 include: a "stop functionality add-on module," which is an add-on module that controls the stopping of operation of a target control device; a "speed-related functionality add-on module," which is an add-on module that controls the speed of operation of the target control device; and an "external signal functionality add-on module," which is an add-on module that processes signals input from an external source.

[0024] Furthermore, examples of the "additional module usage functionality" for the "stop functionality additional module" include a "stop setting." The "stop setting" is a functionality for setting a condition to control the stopping of operation of the target control device.

[0025] Examples of the "add-on module usage functionality" for the "speed-related functionality add-on module" include a "motor speed setting," a "limit speed setting," and an "acceleration / deceleration setting." The "motor speed setting" is a functionality for setting a motor speed condition to control the operating speed of the target control device. The "limit speed setting" is a functionality for setting a limit speed condition to control the operating speed of the target control device. The "acceleration / deceleration setting" is a functionality for setting acceleration and deceleration conditions to control the operating speed of the target control device.

[0026] Examples of the "add-on module usage functionality" for the "External Signal Functionality Add-on Module" include a "touch button functionality," a "forward limit signal (VGS) setting," and a "reverse limit signal (RGS) setting." The touch button functionality is a function for holding data at the moment a trigger input signal is detected. The VGS is an input signal indicating that a limit switch installed at the upper limit of a controllable positioning range has been triggered. The limit switch has a B-contact configuration and is normally in an energized state. The VGS setting is a function for adjusting the VGS. The RGS is an input signal indicating that a limit switch installed at the lower limit of a controllable positioning range has been triggered.The limit switch has a B-contact configuration and is normally in an energized state. The RGS setting is a function of adjusting an RGS.

[0027] In the settings file display section 132, a settings table 1321 is displayed. This table contains a "setting element," which serves as a target candidate for which a user-defined functionality is to be used to execute a user program, and a "setting value" for the setting element, which is included in an add-on module classification condition. The "setting element" lists functionalities that can be used for the operating control unit 2. Examples of the "setting element" include the "stop setting," the "engine speed setting," the "limit speed setting," the "acceleration / braking setting," the "VGS setting," and the "RGS setting." Furthermore, a "required add-on module classification functionality" is displayed as the setting element in the settings file display section 132.The “necessary add-on module classification functionality” is a functionality for an add-on module classification unit 241, which will be described later, of the operating control device 2, which classifies each of several add-on modules stored in a memory 25 as an activated add-on module or as a deactivated add-on module based on an add-on module classification condition.

[0028] The "setting value" for "Stop setting," "Engine speed setting," "Limit speed setting," "Acceleration / Braking setting," "VGS setting," and "RGS setting," which are the "setting elements," is each set to "set" or "not set." The "set" setting indicates that the functionality of the setting element is used to execute the user program. The "not set" setting indicates that the functionality of the setting element is not used to execute the user program. The "setting value" of the "Required add-on module classification functionality" is set to "enabled" or "disabled."The "enabled" setting activates the "Required Add-on Classification Functionality". The "disabled" setting disables the "Required Add-on Classification Functionality".

[0029] On the user program setting display unit 133, a user program is displayed that is to be used for an add-on module classification condition. This means that the user program displayed on the user program setting display unit 133 is one that the user has selected as the add-on module classification condition. The user program is a user-generated program and is stored in memory 15. The user selects a user program to be used for an add-on module classification condition from among the user programs that have been generated and stored in memory 15.

[0030] The user program contains functions that are to be executed by a control unit 242 of the operating control device 2, described later, to control the operation of the target control device. Each function is a processing or arithmetic operation that is to be executed by the control unit 242 of the operating control device 2, described later, to control the operation of the target control device. In particular, the functions are, for example, control functions such as speed control and torque control. Furthermore, the user program specifies a name for each function as a string along with a specific description of the function. For example, the user program specifies the string "touch button function" along with a specific description of the touch button function.

[0031] The additional module classification condition-generation unit 142 sets at least one user program in the additional module classification condition in response to user operation carried out with the input unit 11.

[0032] In a case where the add-on module classification condition-generation unit 142 generates an add-on module classification condition containing a functionality setting file and the user program, the add-on module classification condition-generation unit 142 transmits the add-on module classification condition containing the functionality setting file and the user program to the operating control unit 2. Furthermore, in a case where the add-on module classification condition-generation unit 142 generates an add-on module classification condition containing only the user program, the add-on module classification condition-generation unit 142 transmits the add-on module classification condition containing only the user program to the operating control unit 2. This means that the add-on module classification condition-generation unit 142 transmits at least the user program to the operating control unit 2. Additional module classification condition transferred.

[0033] The display processing unit 143 performs processing for display on the display unit 13. When generating the user program, the display processing unit 143 causes the display unit 13 to display a generation screen for the user program and causes the display unit 13 to display information corresponding to user operation performed with the input unit 11. Furthermore, when setting the add-on module classification condition, the display processing unit 143 causes the display unit 13 to display a settings screen for the add-on module classification condition, as shown in Fig. 3 shown, and causes the display unit 13 to display information corresponding to a user operation carried out with the input unit 11.

[0034] Furthermore, the display processing unit 143 causes the display unit 13 to display information received from the operating control unit 2. In particular, the display processing unit 143 receives at least one of the following from the operating control unit 2: a time saving of a control duration, a capacity utilization saving of an execution memory area, and the name of a deactivated add-on module, and causes the display unit 13 to display this information.

[0035] The individual functionalities of the user program generation unit 142, the additional module classification condition generation unit 142, and the display processing unit 143 are implemented by a combination of the processor 14 and software. The individual functionalities of the user program generation unit 141, the additional module classification condition generation unit 142, and the display processing unit 143 can be implemented by a combination of the processor 14 and firmware, or by a combination of the processor 14, software, and firmware. The software or firmware is defined as a program and stored in memory 15. The processor 14 reads the software or firmware. The processor 14 executes the software or firmware.

[0036] Memory 15 stores a user program generated by the user program generation unit 141 and an additional module classification condition. Memory 15 also holds information received from the operating control unit 2.

[0037] Next, the operating control unit 2 is described. The operating control unit 2 controls the target control device by executing the firmware and the add-on module stored in memory 25, according to the user program. Furthermore, the operating control unit 2 receives an add-on module classification condition from the development tool 1. Based on this condition, the operating control unit 2 classifies each of the multiple add-on modules stored in memory 25 as either an activated or a deactivated add-on module. The operating control unit 2 then executes only the activated add-on module(s), without executing the deactivated add-on module(s) from among the multiple add-on modules stored in memory 25.

[0038] Fig. Figure 4 is a diagram showing a functional configuration of the operating control unit 2 of the operating control system 100 according to the first embodiment. The operating control unit 2 comprises: an input unit 21 into which information is entered; a communication unit 22, which communicates with the development tool 1 and with the servo amplifier 3; a display unit 23, which displays information; a processor 24, which executes various processes; and the memory 25, which stores information.

[0039] Various types of information are entered into the input unit 21 from outside the operating control unit 2. Examples of input units 21 include devices such as a keyboard, a mouse, and a touchpad, and information is entered through user interaction. The communication unit 22 performs bidirectional communication with the development tool 1 and the servo amplifier 3. The display unit 23 displays information on a screen.

[0040] The processor 24 is a CPU, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, or a DSP. The memory 25 comprises RAM, ROM, flash memory, EPROM or EEPROM (registered trademark), and an HDD or SSD. A processing program of the operating control unit 2 is stored in memory 25. The processor 24 executes the program stored in memory 25.

[0041] Memory 25 stores a user program, an add-on module classification condition, and firmware. Memory 25 also holds information received from the operating control unit 2. The firmware is a program that the operating control unit 2 executes when controlling the servo amplifier 3 according to the user program, in order to control the operation of the servo motor 4.

[0042] Memory 25 includes an add-on module memory area 251, which stores multiple add-on modules. Add-on module memory area 251 comprises an enabled add-on memory area 2511, in which an enabled add-on module to be written later is stored, and a disabled add-on memory area 2512, in which a disabled add-on module to be written later is stored. The enabled add-on memory area 2511 and the disabled add-on memory area 2512 are implemented, for example, by the ROM.

[0043] Furthermore, memory 25 includes an execution memory area 252, which is a memory area into which an activated add-on module is copied from the activated add-on module memory area 2511 when the control unit 242, described later, executes the activated add-on module. Execution memory area 252 is implemented, for example, by RAM.

[0044] The activated add-on module is an add-on module that is used by the operating control unit 2 to execute the user program, and is an add-on module that is activated when the operating control unit 2 is executing the user program. The deactivated add-on module is an add-on module that is not used by the operating control unit 2 to execute the user program, and is an add-on module that is deactivated when the operating control unit 2 is executing the user program.

[0045] Fig. Figure 4 shows a functional configuration of the operating control device 2, which is implemented using the processor 24. The operating control device 2 comprises the additional module classification unit 241 and the control unit 242.

[0046] The add-on module classification unit 241 receives an add-on module classification condition transmitted by the add-on module classification condition generation unit 142 of the development tool 1 and, based on the add-on module classification condition, classifies each of several add-on modules stored in memory 25 as an activated add-on module or a deactivated add-on module.

[0047] This means that the add-in module classification unit 241 classifies the multiple add-ins stored in memory 25 based on the user program contained in the add-in module classification condition. During this classification, an add-in module that uses a first functionality—a functionality used to execute a user program—is classified as an activated add-in module, and an add-in module from among the multiple add-ins that differs from the activated add-in module is classified as a deactivated add-in module. The first functionality is a functionality used to execute a function contained in the user program. The add-in module classification unit 241 causes the activated add-in module memory area 2511 to store the add-in module that is classified as the activated add-in module.

[0048] Furthermore, the add-on module classification unit 241 classifies the multiple add-ons based on a functionality settings file contained in the add-on module classification condition. In this classification, an add-on module that uses a second functionality, which is a functionality to be used for executing a user program, is classified as an activated add-on module, and an add-on module from among the multiple add-ons that differs from the activated add-on module is classified as a deactivated add-on module. The second functionality is a usage functionality that is to be used for executing the user program.Furthermore, the second functionality is a functionality that is specified as a functionality to be used in the functionality settings file of the add-on classification condition, and is a functionality whose "setting value" in the functionality settings file of the add-on classification condition is set to "set". The add-on classification unit 241 causes the disabled add-on memory area 2512 to store the add-on that is classified as the disabled add-on.

[0049] The control unit 242 executes the firmware according to the user program and controls the servo amplifier 3 to operate the servo motor 4. Furthermore, the control unit 242 executes the activated add-on module according to the user program and controls the servo amplifier 3 to operate the servo motor 4.

[0050] Next, the operation of the operating control system 100 will be described. First, the operation of development tool 1 will be described. In development tool 1, a user program is created, which is to be executed by the operating control device 2, and an additional module classification condition is set. Fig. Figure 5 is a flowchart showing a procedure that is carried out by the development tool 1 of the operational control system 100 according to the first embodiment. (Creation of a user program)

[0051] In step S10, a user program is generated. The user program generation unit 141 of the development tool 1 causes the display unit 13 to show a user program generation screen for creating a user program. The user program generation unit 141 then processes the generation of the user program in response to a user action performed with the input unit 11. The user program generation unit 141 controls the display processing unit 143 so that information corresponding to the user operation performed with the input unit 11 is displayed to generate the user program. (Setting an additional module classification condition)

[0052] Next, the add-on module classification condition generation unit 142 of development tool 1 causes the display unit 13 to show a generation screen for an add-on module classification condition. Then, the add-on module classification condition generation unit 142 sets and generates the add-on module classification condition according to a user operation performed with the input unit 11.

[0053] In particular, the add-on module classification condition generation unit 142 receives activation setting information in step S20. This setting information instructs the activation of the "Required Add-on Module Classification Functionality." The activation setting information is entered by the input unit 11 through user interaction. For example, the "Setting Value" field corresponding to the "Required Add-on Module Classification Functionality" is displayed as a pull-down menu in the settings table 1321 shown on the settings file display unit 132, and a selection element, "activated" or "deactivated," is displayed as an input element. The user enters the activation setting information by selecting a selection element that is either "activated" or "deactivated" from the pull-down menu.

[0054] In step S30, the additional module classification condition generation unit 142 sets the "setting value" of the "necessary additional module classification functionality" in the settings file display part 132 to "activated" according to the activation setting information.

[0055] In step S40, the add-on module classification condition-generation unit 142 receives setting information for the add-on module usage functionality. Specifically, the add-on module classification condition-generation unit 142 receives either "setting-indicating information," which instructs "activating" the add-on module usage functionality, or "non-setting-indicating information," which instructs "deactivating" the add-on module usage functionality, for each setting element whose add-on module usage functionality is to be configured. The "setting-indicating information" and the "non-setting-indicating information" are entered by the input unit 11 via user operation.For example, a field for "setting value," which corresponds to a respective element of the functionality settings file, is displayed as a pull-down menu in the settings table 1321 shown on the settings file display panel 132, and a selection element "set" or "not set" is displayed as an input element. The user outputs the setting information of the add-on module's usage functionality by selecting one of the selection elements, which is either "set" or "not set," from the pull-down menu.

[0056] In step S50, the add-on module classification condition - generation unit 142 sets the "setting value" for each setting element in setting table 1321 according to the received setting information from the add-on module usage functionality. Add-on module classification condition - generation unit 142 sets the "setting value" to "set" for the setting element for which the "setting information" was received as the setting information from the add-on module usage functionality. Add-on module classification condition - generation unit 142 sets the "setting value" to "not set" for the setting element for which "non-setting information" was received as the setting information from the add-on module usage functionality. This sets the functionality setting file for the add-on module classification condition.

[0057] In step S60, the additional module setting condition generation unit 142 receives configuration information from a user program, which is to be set for the additional module classification condition. The configuration information of the user program is entered by the input unit 11 via a user operation.

[0058] In step S70, the add-on module classification condition generation unit 142 displays the user program, which is defined in the user program's configuration information, on the user program setting display unit 133 in the settings table 1321 and configures the user program for the add-on module classification condition. This configures the user program in the add-on module classification condition and generates the add-on module classification condition, in which the functionality settings file and the user program are configured. Then, the add-on module classification condition generation unit 142 causes memory 15 to store the generated add-on module classification condition.

[0059] Subsequently, the additional module classification condition generation unit 142 transmits the additional module classification condition stored in memory 15 to the additional module classification unit 241 of the operating control device 2 in response to user operation carried out with the input unit 11.

[0060] Next, the operation of the operating control device 2 is described. The operating control device 2 classifies an add-on module to be activated based on the add-on module classification condition generated by the development tool 1 and controls the operation of a target control device. Fig. Figure 6 is a flowchart showing a processing procedure of the operating control device 2 of the operating control system 100 according to the first embodiment.

[0061] In step S110, the additional module classification unit 241 of the operating control device 2 obtains an additional module classification condition from the development tool 1.

[0062] In step S120, the add-on module classification unit 241 determines, based on the add-on module classification condition, whether the "Required Add-on Module Classification Functionality" should be activated or not. If the "setting value" of the "Required Add-on Module Classification Functionality," which is contained in the add-on module classification condition, is "activated," the add-on module classification unit 241 determines that the "Required Add-on Module Classification Functionality" of the add-on module classification unit 241 should be activated. If the "setting value" of the "Required Add-on Classification Functionality", which is contained in the add-on classification condition, is "deactivated", the add-on classification unit 241 determines that the "Required Add-on Classification Functionality" of the add-on classification unit 241 is not to be activated.

[0063] If it is determined that the "Required Add-on Classification Functionality" should be activated, "Yes" is selected in step S120, and the add-on classification unit 241 activates the "Required Add-on Classification Functionality" and proceeds to step S130. If it is determined that the "Required Add-on Classification Functionality" should not be activated, "No" is selected in step S120, and the add-on classification unit 241 deactivates the "Required Add-on Classification Functionality" and terminates the processing flow. Note that the "Required Add-on Classification Functionality" of add-on classification unit 241 is assumed to be deactivated by default.

[0064] In step S130, the add-on module classification unit 241 begins an execution of the "Necessary add-on module classification functionality" and analyzes a setting condition of the add-on module classification condition, i.e., analyzes a functionality setting file which is contained in the add-on module classification condition.

[0065] In step S140, the add-on module classification unit 241 determines, based on the analysis of the functionality setting file contained in the add-on module classification condition, whether or not an add-on module exists among the add-on modules stored in the add-on module memory area 251 that can be deactivated. In this case, at the start of the execution of the "Required Add-on Module Classification Functionality," all add-on modules stored in the operating control unit 2 are set as add-on modules to be activated and are stored in the activated add-on module memory area 2511.

[0066] The add-on classification unit 241 classifies each add-on stored in the enabled add-on memory area 2511 as either an enabled add-on or a disabled add-on. An enabled add-on is an add-on in which an add-on usage functionality is used, the "setting value" of which is "set" in the functionality settings file included in the add-on classification condition. A disabled add-on is an add-on in which the add-on usage functionality is not used, and the "setting value" of which is "not set" in the functionality settings file included in the add-on classification condition.

[0067] If an add-on module exists that is classified as the disabled add-on module, add-on module classification unit 241 determines that an add-on module exists that can be disabled. If no add-on module exists that is classified as the disabled add-on module, add-on module classification unit 241 determines that no add-on module exists that can be disabled. If it is determined that an add-on module exists that can be disabled, "Yes" is selected in step S140 and the process proceeds to step S150. If it is determined that no add-on module exists that can be disabled, "No" is selected in step S140 and add-on module classification unit 241 terminates the processing flow.

[0068] In step S150, the add-on module classification unit 241 performs a deactivation process to deactivate the add-on module that has been designated as being deactivated. From the add-on modules that are set as the add-on module to be activated and stored in the activated add-on module memory area 2511, the add-on module classification unit 241 moves the add-on module designated as being deactivated to the deactivated add-on module memory area 2512 in order to store and deactivate it.

[0069] In step S160, the add-on module classification unit 241 analyzes a user program of the add-on module classification condition; that is, it analyzes the user program contained in the add-on module classification condition. Specifically, the add-on module classification unit 241 extracts a string containing the name of a function specified in the user program contained in the add-on module classification condition.

[0070] In step S170, the add-on module classification unit 241 determines, based on the result of the analysis of the user program contained in the add-on module classification condition, whether an add-on module exists from among the add-on modules stored in the deactivated add-on module memory area 2512 that can be activated.

[0071] The add-in module classification unit 241 classifies each of the add-ins stored in the disabled add-in module memory area 2512 as either an enabled add-in or a disabled add-in, using the extracted string of the function name as a search condition. An enabled add-in is, in this case, an add-in that contains the extracted string of the function name. Conversely, a disabled add-in is, in this case, an add-in that does not contain the extracted string of the function name.

[0072] If an add-on module exists that is classified as the activated add-on module, add-on module classification unit 241 determines that an add-on module exists that can be activated. If no add-on module exists that is classified as the activated add-on module, add-on module classification unit 241 determines that no add-on module exists that can be activated. If it is determined that an add-on module exists that can be activated, "Yes" is selected in step S170 and the process proceeds to step S180. If it is determined that no add-on module exists that can be activated, "No" is selected in step S170 and the process proceeds to step S190.

[0073] In step S180, the add-on module classification unit 241 performs an activation process to activate an add-on module that can be activated from the deactivated add-on modules stored in the deactivated add-on module memory area 2512. From the deactivated add-on modules that are set as the add-on module to be deactivated and stored in the deactivated add-on module memory area 2512, the add-on module classification unit 241 moves the add-on module designated for activation to the activated add-on module memory area 2511 in order to store and activate it.

[0074] This allows the add-on module classification unit 241 to correctly classify the add-on module as an activated add-on module, which is an add-on module to be used for executing the user program, and as a deactivated add-on module, which is an add-on module that is not to be used for executing the user program, and to activate the add-on module to be activated and deactivate the add-on module to be deactivated in order to optimize the setting for the activated add-on module.

[0075] This means that by performing the processing described above, the operating control unit 2 is able to select only the add-on module(s) required for executing the user program from all the add-on modules stored in the operating control unit 2, and not select the add-on module(s) that are not required for executing the user program. Furthermore, by classifying the add-on module as both the activated and deactivated add-on modules in steps S140 and S170, the add-on module that was designated as deactivated in step S140, but is required for executing the user program, can be re-selected as the activated add-on module.

[0076] This means that by performing the processing described above, the operating control unit 2 can set an add-on module as the activated add-on module that corresponds to at least one of the following: an add-on module whose add-on module usage functionality is used, whose "setting value" is "set" in the functionality setting file contained in the add-on module classification condition; and an add-on module that contains a string of the function name specified in the user program of the add-on module classification condition. Therefore, an add-on module necessary for the execution of the user program can be set as the activated add-on module with high accuracy.

[0077] In the present case, the additional module classification unit 241 calculates a control duration reduction, which is a duration by which the control duration of the target control device by the operating control unit 2 is reduced in a case in which the user program is executed while all of the additional modules stored in the additional module memory area 251 are activated, to a control duration of the target control device by the operating control unit 2 in a case in which the user program is executed while only the activated additional module is activated.This means that the reduction in control duration is a time saving of the control duration, which is a duration obtained by subtracting a second control duration, which is a duration in which the additional module classification unit 241 controls the target control device in a case in which the activated additional module is executed without the deactivated additional module being executed, from a first control duration, which is a duration in which the additional module classification unit 241 controls the target control device in a case in which all of the additional modules of the several additional modules are executed.

[0078] Furthermore, the add-on module classification unit 241 calculates a storage capacity saving, which is a capacity saving from a capacity utilization of the execution memory area 252 in a case in which the user program is executed while all add-on modules stored in the add-on module memory area 251 are activated, to a capacity utilization of the execution memory area 252 by the operating control unit 2 in a case in which the user program is executed while only the activated add-on module is activated.

[0079] The operating control unit 2 does not allow a deactivated add-on module, which is an add-on module that is not in use, to be copied into and remain in execution memory area 252. Therefore, the deactivated add-on module does not cause unnecessary memory consumption in execution memory area 252 within the operating control unit 2, thus eliminating the need to increase the capacity of execution memory area 252 and reducing or preventing the associated cost increase. Furthermore, the operating control unit 2 can utilize execution memory area 252 effectively because the deactivated add-on module is not copied into and remains in execution memory area 252.

[0080] Because the control unit 2 does not allow a deactivated add-on module (which is an add-on module that is not to be used) to be copied to and remain in execution memory area 252, it is possible to reduce the duration for copying the deactivated add-on module (which is not to be used) to execution memory area 252. This allows the control unit 2 to reduce processing time during preparation for executing control of the target device, shorten the commissioning time of the control unit 2 until the control of the target device can be executed, and enable the control of the target device to be started quickly.

[0081] Furthermore, by not executing a deactivated add-on module, which is an add-on module that is not to be executed, the operating control unit 2 can shorten a control duration caused by executing the deactivated add-on module in order to prevent an unnecessary extension of the control duration for controlling the target control device by the operating control unit 2, and can control the target control device with a good control duration.

[0082] In step S190, the add-on module classification unit 241 transmits a processing result from the required add-on module classification functionality to the display processing unit 143 of development tool 1. The processing result contains status information for all add-on modules stored in the add-on module memory area 251, the reduction in control duration, and the memory capacity savings. The status information for add-on modules indicates whether the add-on module is in an activated or deactivated state.

[0083] Fig.Figure 7 is a view showing an example of a display screen of a processing result of the Necessary Add-on Module Classification Functionality on the display unit 13 of the development tool 1 according to the first embodiment. When the processing result of the Necessary Add-on Module Classification Functionality is received, the display processing unit 143 of the development tool 1 causes the display unit 13 to display the processing result of the Necessary Add-on Module Classification Functionality. The display unit 13 shows: an add-on module status indicator 134, which shows a state of each add-on module; and a processing result display screen 135, which shows a processing result of an optimization processing of the add-on module, such as a deactivated add-on module, a reduction in control duration, and a saving in memory capacity.When the necessary add-on module classification functionality is activated, the user can use this to check the status information of all add-on modules stored in the add-on module memory area 251, a deactivated add-on module which is an add-on module to be deactivated, a reduction in control duration and a saving in storage capacity in development tool 1.

[0084] As described above, in the operating control system 100 according to this first embodiment, an additional module classification condition is generated by the development tool 1. The operating control device 2 then automatically activates, based on the additional module classification condition, only the additional module(s) necessary for executing the user program from among the multiple additional modules stored in the operating control device 2, and executes the user program. This allows the operating control device 2 to reduce or prevent an extension of the control duration caused by an activated additional module that is unnecessary for executing the user program, and can shorten the control duration when executing the user program.In addition, the operating control unit 2 can reduce the capacity utilization of memory 25 caused by an activated additional module, which is unnecessary for the execution of the user program, and can use the capacity of memory 25 efficiently.

[0085] By simply generating the add-on module classification condition, i.e., by creating the user program and the functionality setting file, the operating control device 2 in the operating control system 100 automatically determines the add-on module required to execute the user program. Even if the user is not familiar with the functionality of every add-on module, this allows them to easily and correctly activate or deactivate the add-on module required to execute the user program.

[0086] When configuring a user functionality to be used for executing the user program in the functionality settings file, the user only needs to select and specify a functionality that requires setting a control condition when executing the user program. Therefore, even if the user is unaware of the connection between an initial functionality contained in the operating control device 2 and an extended functionality to be implemented by the add-on module, the user functionality to be used for executing the user program can be easily configured.

[0087] Furthermore, according to the description above, the operating control unit 2 classifies the add-on module as activated or deactivated based on the results of an analysis of the functionality settings file contained in the add-on module classification condition and the user program contained in the add-on module classification condition. The operating control unit 2 can also classify the add-on module as activated or deactivated based solely on the results of an analysis of the functionality settings file. The operating control unit 2 can also classify the add-on module as activated or deactivated based solely on an analysis of the user program.

[0088] In a case where the control unit 2 classifies the add-on module as activated or deactivated based solely on the results of an analysis of the functionality settings file, the development tool 1 only needs to generate the add-on module classification condition, which contains only the functionality settings file, and transfer it to the control unit 2. Furthermore, in a case where the control unit 2 classifies the add-on module as activated or deactivated based solely on the results of an analysis of the user program, the development tool 1 only needs to generate the add-on module classification condition, which contains only the user program, and transfer it to the control unit 2.

[0089] As described above, the operating control device 2 according to the first embodiment enables an additional module, which is necessary for the execution of a user program, to be correctly configured from several additional modules implemented in the operating control device 2.

[0090] The configuration shown in the above embodiment is an example and can be combined with another known technique, and it is also possible to combine embodiments with one another and to omit or change part of the configuration without departing from the subject matter of the present invention. Reference symbol list 1 development tool; 2 Operating control unit; 3 servo amplifiers; 4 servo motors; 6, 7, 8 Communication line; 11, 21 Input unit; 12, 22 Communication unit; 13, 23 Display unit; 14, 24 processor; 15, 25 storage; 100 Operating control system; 131 Additional module display unit; 132 Settings file display section; 133 User program setting display section; 134 Additional module status indicator; 135 Processing result display screen; 141 User program generation unit; 142 Additional module classification condition - generation unit; 143 Display processing unit; 241 Additional module classification unit; 242 Control unit; 251 Additional module memory area; 252 Execution memory area; 1321 Settings table; 2511 Activated add-on module memory area; 2512 Disabled add-on module memory area.

Claims

[1] Operation control device (2) for controlling a control target device by executing a plurality of additional modules, the operation control device (2) comprising: a memory (25) which stores the plurality of additional modules and a user program which is a program to be executed for controlling the control target device; an add-on module classification unit (241) which classifies the plurality of add-on modules based on an add-on module classification condition which includes the user program and serves to classify add-on modules, such that each of the plurality of add-on modules in which a first functionality is used is classified as an activated add-on module to be used for executing the user program, and each add-on module of the plurality of add-on modules which is not an activated add-on module is classified as a deactivated add-on module which is not to be used for executing the user program, wherein the first functionality is a functionality of the control target device and is to be used for executing a function included in the user program; and a control unit (242) which executes the activated additional module according to the user program to control the control target device. [2] Operation control device (2) according to claim 1, wherein the add-on module classification condition contains usage functionality setting information in which a second functionality is specified, the second functionality being a usage functionality to be used to execute the user program, and the add-on module classification unit (241) classifies the plurality of add-on modules based on the add-on module classification condition such that each of the add-on modules in which the first functionality is used and each of the add-on modules in which the second functionality is used is classified as the activated add-on module, and each of the plurality of add-on modules that is not an activated add-on module is classified as the deactivated add-on module. [3] Operation control device (2) according to claim 1 or 2, comprising: an activated add-on module storage area (2511) which stores the activated add-on module; a deactivated add-on module storage area (2512) which stores the deactivated add-on module; and an execution memory area (252) to be used for executing the add-on modules, wherein the control unit (242) copies the activated add-on module from the activated add-on module memory area (2511) into the execution memory area (252) and executes the activated add-on module copied into the execution memory area (252). [4] The operation control device (2) according to claim 3, wherein the additional module judging unit (241) calculates a capacity usage saving of the execution memory area (252), the capacity usage saving being a capacity obtained by subtracting a capacity usage of the execution memory area (252) in a case where the enabled additional module judged by the additional module judging unit (241) is executed without executing the disabled additional module from a capacity usage of the execution memory area (252) in a case where all the additional modules of the plurality of additional modules are executed. [5] The operation control device (2) according to claim 3 or 4, wherein the additional module rating unit (241) calculates a time saving of a control period, the time saving being a period obtained by subtracting a second control period from a first control period, the second control period being a period in which the control unit (242) controls the control target device in a case where the enabled additional module is executed without executing the deactivated additional module, the first control period being a period in which the control unit (242) controls the control target device in a case where all the additional modules of the plurality of additional modules are executed. [6] An operation control system (100) comprising: an operation control device (2) for controlling a control target device by executing a plurality of additional modules; and a development tool (1) connected to the operation control device (2), wherein the development tool (1) comprises: a user program generation unit (141) which generates a user program which is a program to be executed for controlling the control target device in the operation control device (2); and an additional module classification condition generation unit (142) which generates an additional module classification condition containing the user program and serving to classify the additional modules, and wherein the operation control device (2) comprises: a memory (25) which stores the user program and the plurality of additional modules; an add-on module classification unit (241) which classifies the plurality of add-on modules based on the add-on module classification condition such that each of the add-on modules in which a first functionality is used is classified as an activated add-on module to be used for executing the user program, and each add-on module of the plurality of add-on modules that is not an activated add-on module is classified as a deactivated add-on module that is not to be used for executing the user program, wherein the first functionality is a functionality of the control target device to be used for executing a function included in the user program; and a control unit (242) which executes the activated additional module according to the user program to control the control target device. [7] Operation control system (100) according to claim 6, wherein the add-on module classification condition contains usage functionality setting information in which a second functionality is specified, the second functionality being a usage functionality to be used to execute the user program, and the add-on module classification unit (241) classifies the plurality of add-on modules based on the add-on module classification condition such that each of the add-on modules in which the first functionality is used and each of the add-on modules in which the second functionality is used is classified as the activated add-on module, and each of the plurality of add-on modules that is not an activated add-on module is classified as the deactivated add-on module. [8] Operation control system (100) according to claim 6 or 7, comprising: an activated add-on module storage area (2511) which stores the activated add-on module; a deactivated add-on module storage area (2512) which stores the deactivated add-on module; and an execution memory area (252) to be used for executing the add-on modules, wherein the control unit (242) copies the activated add-on module from the activated add-on module memory area (2511) into the execution memory area (252) and executes the activated add-on module copied into the execution memory area (252). [9] The operation control system (100) according to claim 8, wherein the add-on module ranking unit (241) calculates a capacity usage saving of the execution memory area (252), the capacity usage saving being a capacity obtained by subtracting a capacity usage of the execution memory area (252) in a case where the enabled add-on module ranked by the add-on module ranking unit (241) is executed without executing the disabled add-on module from a capacity usage of the execution memory area (252) in a case where all the add-on modules of the plurality of add-on modules are executed. [10] The operation control system (100) according to claim 8 or 9, wherein the additional module rating unit (241) calculates a time saving of a control period, the time saving being a period obtained by subtracting a second control period from a first control period, the second control period being a period in which the control unit (242) controls the control target device in a case where the activated additional module is executed without executing the deactivated additional module, the first control period being a period in which the control unit (242) controls the control target device in a case where all the additional modules of the plurality of additional modules are executed. [11] The operation control system (100) according to claim 10, wherein the development tool (1) comprises a display unit that displays at least one of a time saving of the control duration, a capacity usage saving of the execution memory area (252), and a name of the deactivated add-on module.

Images