Setting management device, setting management method, and setting management program

The setting management device addresses the challenge of managing device settings by creating a database of setting information for each device, reducing errors and improving operational efficiency in systems like manufacturing equipment.

WO2025069360A1PCT designated stage expired Publication Date: 2025-04-03MITSUBISHI ELECTRIC CORP
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2023/035574
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-09-29
Publication Date
2025-04-03

AI Technical Summary

Technical Problem

Existing technologies lack an efficient method for managing and utilizing setting information for each device, leading to potential errors in input and incorrect device settings.

Method used

A setting management device that creates a list of device identifiers, generates a table of setting values from system design information, and registers this information in a database, ensuring accurate and efficient management of setting information for each device.

Benefits of technology

The proposed solution enables efficient management and utilization of setting information, reducing the risk of errors and improving the accuracy of device settings, thereby enhancing operational efficiency in systems like manufacturing equipment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2023035574_03042025_PF_FP_ABST
    Figure JP2023035574_03042025_PF_FP_ABST
Patent Text Reader

Abstract

A setting management device (100) manages a setting of an apparatus (200). An identifier list creation unit (110) creates a list of apparatus identifiers as an identifier list table (62). A table generation unit (120) retrieves a setting value to be set to the apparatus from system design information (61), and generates an apparatus setting table (64) in which the setting value obtained by retrieval is recorded. A database registration unit (130) determines whether or not an apparatus identifier is recorded in the apparatus setting table (64). If the apparatus identifier has not been recorded, an apparatus identifier which can be recorded is selected from the identifier list table (62) and is recorded in the apparatus setting table (64). Then, the database registration unit (130) registers the apparatus setting table (64) in a setting information database (65).
Need to check novelty before this filing date? Find Prior Art

Description

Setting management device, setting management method, and setting management program

[0001] The present disclosure relates to a setting management device, a setting management method, and a setting management program.

[0002] Traditionally, device settings in systems such as manufacturing facilities have been managed using configuration documents. Users often manually input settings for devices, which can lead to errors such as incorrect input or incorrect device settings.

[0003] Patent Document 1 discloses a method for automatically creating a parameter sheet for each product for a platform consisting of hardware devices or software products. The technology in Patent Document 1 makes it possible to create a parameter sheet for each product by inputting specifications and interview details. This allows for a significant reduction in the number of steps.

[0004] JP 2017-041082 A

[0005] The technology of Patent Document 1 does not disclose a parameter sheet for each product, i.e., a method for managing or inputting the setting information of each device. Therefore, the technology of Patent Document 1 has a problem in that it is not possible to efficiently manage and utilize the setting information of each device.

[0006] An object of the present disclosure is to provide a device that can efficiently manage and utilize setting information of each device.

[0007] The setting management device according to the present disclosure is a setting management device that manages the settings of devices provided in a system, and includes: an identifier list creation unit that creates a list of device identifiers that identify the devices as an identifier list table; a table creation unit that searches for setting values ​​to be set for the devices from system design information that indicates the design content of the system, and generates a table that records the setting values ​​obtained by the search as a device setting table; and a database registration unit that determines whether or not a device identifier is recorded as a setting value in the device setting table, and if no device identifier is recorded, records a recordable device identifier from the identifier list table in the device setting table, and registers the device setting table as a setting information database.

[0008] In the setting management device according to the present disclosure, a device identifier is included in a device setting table that records setting information for each device. The device setting table including the device identifier is then registered in a setting information database. Therefore, the setting management device according to the present disclosure has the effect of being able to efficiently manage and utilize the setting information database.

[0009] FIG. 1 is a diagram showing an example of the configuration of a setting management device according to the first embodiment. FIG. 2 is a flow diagram showing an example of identifier list creation processing according to the first embodiment. FIG. 3 is a diagram showing an example of system design information according to the first embodiment. FIG. 4 is a diagram showing an example of an identifier list table and an example of an item list table according to the first embodiment. FIG. 5 is a flow diagram showing an example of table generation processing according to the first embodiment. FIG. 6 is a diagram showing an example of a device setting table according to the first embodiment. FIG. 7 is a flow diagram showing an example of a database registration processing according to the first embodiment. FIG. 8 is a diagram showing an example of a device setting table in which a MAC address, which is a device identifier, is recorded as a result of the database registration processing according to the present embodiment. FIG. 9 is a diagram showing examples 1 and 2 of a program development environment screen according to the first embodiment. FIG. 10 is a diagram showing an example of program development environment processing according to the first embodiment. FIG. 11 is a diagram showing an example of the configuration of a setting management device according to a modification of the first embodiment. FIG. 12 is a diagram for explaining an example of the effect provided by the setting management device according to the first embodiment. FIG. 13 is a diagram for explaining another example of the effect provided by the setting management device according to the first embodiment.

[0010] The following describes the embodiments with reference to the drawings. In each drawing, the same or corresponding parts are designated by the same reference numerals. In the description of the embodiments, the description of the same or corresponding parts will be omitted or simplified as appropriate. The arrows in the drawings mainly indicate the flow of data or the flow of processing.

[0011] Embodiment 1. *** Description of Configuration *** Fig. 1 is a diagram showing an example of the configuration of a setting management device 100 according to this embodiment. The setting management device 100 is a device that manages the settings of devices 200 provided in a system such as a manufacturing facility. Furthermore, the setting management device 100 may be a development computer equipped with a program development function for the devices 200. The devices 200 are, for example, PLCs. PLC is an abbreviation for Programmable Logic Controller.

[0012] The setting management device 100 is a computer. The setting management device 100 includes a processor 910, as well as other hardware such as a memory 921, an auxiliary storage device 922, an input interface 930, an output interface 940, and a communication device 950. The processor 910 is connected to the other hardware via signal lines and controls the other hardware.

[0013] The setting management device 100 includes, as functional elements, an identifier list creation unit 110, a table generation unit 120, a database registration unit 130, a development environment unit 140, and a storage unit 160. The storage unit 160 stores system design information 61, an identifier list table 62, an item list table 63, a device setting table 64, and a setting information database 65.

[0014] The functions of the identifier list creation unit 110, table generation unit 120, database registration unit 130, and development environment unit 140 are realized by software. The storage unit 160 is provided in the memory 921. The storage unit 160 may be provided in the auxiliary storage device 922, or may be provided separately in the memory 921 and the auxiliary storage device 922.

[0015] The processor 910 is a device that executes a setting management program. The setting management program is a program that realizes the functions of the identifier list creation unit 110, the table generation unit 120, the database registration unit 130, and the development environment unit 140. The processor 910 is an IC that performs arithmetic processing. Specific examples of the processor 910 are a CPU, a DSP, and a GPU. IC is an abbreviation for Integrated Circuit. CPU is an abbreviation for Central Processing Unit. DSP is an abbreviation for Digital Signal Processor. GPU is an abbreviation for Graphics Processing Unit.

[0016] The memory 921 is a storage device that temporarily stores data. Specific examples of the memory 921 are SRAM and DRAM. SRAM is an abbreviation for Static Random Access Memory. DRAM is an abbreviation for Dynamic Random Access Memory. The auxiliary storage device 922 is a storage device that saves data. A specific example of the auxiliary storage device 922 is an HDD. The auxiliary storage device 922 may also be a portable storage medium such as an SD (registered trademark) memory card, CF, NAND flash, flexible disk, optical disk, compact disk, Blu-ray (registered trademark) disk, or DVD. Note that HDD is an abbreviation for Hard Disk Drive. SD (registered trademark) is an abbreviation for Secure Digital. CF is an abbreviation for CompactFlash (registered trademark). DVD is an abbreviation for Digital Versatile Disk.

[0017] The input interface 930 is a port connected to an input device such as a mouse, keyboard, or touch panel. Alternatively, the input interface 930 may be connected to a reading device that reads data by optical recognition. Specifically, the input interface 930 is a USB terminal. Note that the input interface 930 may also be a port connected to a LAN. USB is an abbreviation for Universal Serial Bus. LAN is an abbreviation for Local Area Network.

[0018] The output interface 940 is a port to which a cable of an output device such as a display is connected. Specifically, the output interface 940 is a USB terminal or an HDMI (registered trademark) terminal. Specifically, the display is an LCD. The output interface 940 is also called a display interface. HDMI (registered trademark) is an abbreviation for High Definition Multimedia Interface. LCD is an abbreviation for Liquid Crystal Display.

[0019] The communication device 950 has a receiver and a transmitter. The communication device 950 is connected to a communication network such as a LAN, the Internet, a telephone line, or Wi-Fi (registered trademark). Specifically, the communication device 950 is a communication chip or NIC. NIC is an abbreviation for Network Interface Card.

[0020] The setting management program is executed in the setting management device 100. The setting management program is loaded into the processor 910 and executed by the processor 910. The memory 921 stores not only the setting management program but also an OS. OS is an abbreviation for Operating System. The processor 910 executes the setting management program while running the OS. The setting management program and the OS may be stored in an auxiliary storage device 922. The setting management program and the OS stored in the auxiliary storage device 922 are loaded into the memory 921 and executed by the processor 910. Note that part or all of the setting management program may be incorporated into the OS.

[0021] The setting management device 100 may include multiple processors that replace the processor 910. These multiple processors share the task of executing the setting management program. Each processor is a device that executes the setting management program in the same way as the processor 910.

[0022] Data, information, signal values ​​and variable values ​​used, processed or output by the configuration management program are stored in memory 921, secondary storage device 922, or registers or cache memory within processor 910.

[0023] The "part" of each of the identifier list creation unit 110, table generation unit 120, database registration unit 130, and development environment unit 140 may be interpreted as a "circuit," "process," "procedure," "process," or "circuitry." The setting management program causes a computer to execute an identifier list creation process, a table generation process, a database registration process, and a development environment process. The "process" of each of the processes may also be interpreted as a "program," "program product," "computer-readable storage medium storing a program," or "computer-readable recording medium recording a program." The setting management method is a method performed by the setting management device 100 executing the setting management program. The setting management program may be provided by being stored in a computer-readable recording medium. The setting management program may also be provided as a program product.

[0024] *** Functional Overview *** A functional overview of each functional element of the setting management device 100 will be described. The identifier list creation unit 110 creates a list of device identifiers that identify the devices 200 as an identifier list table 62. The table generation unit 120 searches for setting values ​​to be set for the devices 200 from system design information 61 that indicates the system design details. The table generation unit 120 generates a table that records the setting values ​​obtained by the search as a device setting table 64. The database registration unit 130 determines whether a device identifier is recorded as a setting value in the device setting table 64. If a device identifier is not recorded, the database registration unit 130 selects a recordable device identifier from the identifier list table 62 and records it in the device setting table 64. The database registration unit 130 then registers the device setting table 64 for each device as a setting information database 65. The development environment unit 140 displays a program development environment screen 41 that searches the setting information database 65 using the device identifier.

[0025] As described above, the setting management device 100 according to this embodiment is configured to include device identifiers in the setting information database 65. A device identifier is an identifier provided to a device and uniquely identifies the device. For example, information such as an Ethernet (registered trademark) MAC address or a device serial number is used as a device identifier. The identifier list table 62 is a collection of device identifiers for devices included in the system to be constructed.

[0026] ***Description of Operation*** Next, the operation of the setting management device 100 according to this embodiment will be described. The operating procedure of the setting management device 100 corresponds to a setting management method. Furthermore, the program that realizes the operation of the setting management device 100 corresponds to a setting management program.

[0027] The setting management process, which is an operation of the setting management device 100, includes an identifier list creation process, a table generation process, a database registration process, and a development environment process.

[0028] 2 is a flow diagram showing an example of the identifier list creation process according to this embodiment. In the identifier list creation process, the identifier list creation unit 110 creates a list of device identifiers that identify devices as the identifier list table 62. At this time, the identifier list creation unit 110 creates the identifier list table 62 based on at least one of the system design information 61, device identification information assigned to the devices, and external input.

[0029] FIG. 3 is a diagram showing an example of system design information 61 according to this embodiment. The system design information 61 is information indicating the design contents of a system. For example, the system design information 61 is the result of analyzing design documents indicating the design contents of the system. The setting management device 100 may have a function for analyzing the system design documents, analyze the system design documents, and store the analysis results in the storage unit 160 as the system design information 61. Alternatively, the setting management device 100 may obtain the results of analyzing the system design documents from an external system via the communication device 950 and store the results in the storage unit 160 as the system design information 61. Alternatively, the system design information 61 may be the system design documents themselves.

[0030] The system design information 61 records setting items and setting values ​​to be set for the setting items. In the example of the system design information 61 in Fig. 3, setting values ​​for each setting item are recorded for a device with a device name "PLC01". The system design information 61 in Fig. 3 is an example in which there is no setting value in the MAC address field for the device with a device name "PLC01", and the MAC address field is set to "null data".

[0031] In step S101, it is determined whether or not the device identifiers of all devices provided in the system are listed in the system design information 61. This determination may be performed automatically by the identifier list creation unit 110, or the result of the determination by a user may be input to the setting management device 100. For example, the determination as to whether or not the device identifiers are listed in the system design information 61 is automatically performed by configuration document analysis software. A user may also visually check. If the device identifiers are listed in the system design information 61, the process proceeds to step S109. If the device identifiers are not listed in the system design information 61, the process proceeds to step S102.

[0032] In step S102, it is determined whether a device identifier list listing the device identifiers of all devices provided in the system is prepared as an electronic file. This determination may also be performed automatically by the identifier list creation unit 110, or the result of the user's determination may be input to the setting management device 100. For example, whether a device identifier list is prepared as an electronic file may be automatically determined based on the absence of an electronic file with a specified name in a specified folder. Alternatively, a method may be used in which the user is prompted to select a file from the development environment software, and if no file to be specified exists, the process proceeds to the next step. If the system design information 61 contains a device identifier list, the process proceeds to step S109. If the system design information 61 does not contain a device identifier list, the process proceeds to step S103.

[0033] In step S109, the identifier list creation unit 110 creates the identifier list table 62 using the system design information 61 or the device identifier list, and then ends the process.

[0034] The processes from step S103 to step S108 are executed for each device for which the device setting table 64 is to be created.

[0035] In step S103, it is determined whether or not a device identifier is printed on the device. This determination may also be made automatically by the identifier list creation unit 110, or the result of the user's determination may be input to the setting management device 100. Specifically, the user visually determines whether or not the device identifier is printed. If the device identifier is printed on the device, the process proceeds to step S104. In step S104, the identifier list creation unit 110 acquires the printed device identifier via the input interface 930 using a reading device that reads data by optical recognition. For example, the user manually acquires the device identifier using a reading device such as a handheld terminal or smartphone. The process then proceeds to step S108.

[0036] If the device identifier is not printed on the device, the process proceeds to step S105.

[0037] In step S105, it is determined whether or not a device identifier is stored in a storage device built into the device. This determination may also be made automatically by the identifier list creation unit 110, or the result of the determination may be input by a user to the setting management device 100. If a device identifier is stored in a storage device built into the device, the process proceeds to step S106. In step S106, the identifier list creation unit 110 acquires a device identifier from the storage device built into the device via a communication cable connected to the communication device 950. Specifically, a cable is manually connected to a communication port of the device, and the device identifier is automatically acquired by a software tool. Then, the process proceeds to step S108.

[0038] If the device identifier is not stored in the storage device built into the device, the process proceeds to step S107.

[0039] In step S107, the identifier list creation unit 110 acquires the manually input device identifier, and proceeds to step S108. For example, the identifier list creation unit 110 displays a message on the display device requesting manual input of the device identifier, and accepts input of the device identifier from the user.

[0040] In step S108, the identifier list creation unit 110 records the acquired device identifier in the identifier list table 62. For example, the device identifier manually input in step S107 is recorded in the identifier list table 62. Furthermore, the device identifier acquired in step S104 or step S105 may be recorded in the identifier list table 62 manually, or may be automatically recorded in the identifier list table 62 from a reading device or the like. After the device identifiers for all devices have been recorded in the identifier list table 62, the process ends.

[0041] 4 shows an example of the identifier list table 62 and an example of the item list table 63 according to this embodiment. The identifier list table 62 records a device identifier 621 and a used flag 622 corresponding to the device identifier 621. The used flag 622 is a flag that is set for the device identifier of the device for which the device setting table 64 has been generated.

[0042] The identifier list table 62 is created by the identifier list creation process described in Fig. 2. Here, it is assumed that MAC addresses are used as device identifiers. The identifier list table 62 records the device identifiers of all devices provided in the system. As shown in Fig. 3, even if the system design information 61 does not include device identifiers, i.e., MAC addresses, the identifier list table 62 can be created by the identifier list creation process described in Fig. 2.

[0043] The item list table 63 is a table showing a list of setting items to be recorded in the device setting table 64. The device setting table 64 is generated for each device. The device setting table 64 is a table in which the setting values ​​of the setting items recorded in the item list table 63 are recorded for each device. The process of generating the device setting table 64 will be described below.

[0044] Fig. 5 is a flow diagram showing an example of table generation process according to this embodiment. In the table generation process, the table generator 120 searches the system design information 61 for setting values ​​to be set for the devices, and generates a table recording the setting values ​​obtained by the search as the device setting table 64. At this time, the table generator 120 references the item list table 63, which lists the items to be recorded in the device setting table 64. The table generator 120 searches the system design information 61 for setting values ​​to be set for the items included in the item list table 63. As a result of the search, the table generator 120 records information indicating null data in the device setting table 64 for items for which no setting value is found. Specifically, this is as follows.

[0045] In step S201, the table generation unit 120 reads the system design information 61 and the item list table 63.

[0046] The processes from step S202 to step S204 are executed for each device for which the device setting table 64 is to be created.

[0047] In step S202, the table generation unit 120 searches the system design information 61 using a keyword corresponding to the setting item recorded in the item list table 63. If the search results in a keyword corresponding to the setting item, the table generation unit 120 records the keyword corresponding to the setting item as a setting value in the device setting table 64. If the keyword corresponding to the setting item does not exist in the system design information 61, information indicating null data is recorded for that setting item. The process of step S202 is a process that is repeatedly executed for all setting items recorded in the item list table 63. As a result of executing the process of step S202 for all setting items, setting values ​​are recorded for the setting items in the device setting table 64. Furthermore, information indicating null data is recorded for setting items for which no setting value existed.

[0048] As described above, the system design information 61 is the result of analyzing the settings documents obtained by analyzing the design documents. For example, Word or PDF files can be analyzed as structured text data. This allows for the extraction of setting items corresponding to keywords and their associated setting values ​​from the setting tables described in the files. As described above, the device setting table 64 for each device can be obtained from the system design information 61 and the item list table 63.

[0049] Fig. 6 is a diagram showing an example of the device setting table 64 according to this embodiment. By the processing of step S202, the device setting table 64 shown in Fig. 6 is obtained from the system design information 61 in Fig. 3 and the item list table 63 in Fig. 4. In the device setting table 64 shown in Fig. 6, the MAC address, which is the device identifier, is set to null data.

[0050] In step S203, the table generation unit 120 determines whether a setting value is recorded in the setting item "device identifier" in the device setting table 64. In the example of FIG. 6, the table generation unit 120 determines whether a setting value is recorded in the MAC address, which is the device identifier. If a setting value is not recorded in the "device identifier," the process proceeds from step S202 for the next device. If the process of step S202 has been completed for all devices, the process ends. If a setting value is recorded in the "device identifier," i.e., if a device identifier has been obtained as a setting value, the process proceeds to step S204.

[0051] In step S204, the table generation unit 120 determines whether or not the same device identifier exists in the identifier list table 62, and if so, sets the used flag 622 for that device identifier.

[0052] The processes from step S202 to step S204 are repeated until the device setting tables 64 are created for all the devices.

[0053] <Database Registration Processing> Fig. 7 is a flow diagram showing an example of database registration processing according to this embodiment. In the database registration processing, the database registration unit 130 determines whether or not a device identifier is recorded as a setting value in the device setting table 64. If a device identifier is not recorded, the database registration unit 130 selects a recordable device identifier from the identifier list table 62 and records it in the device setting table 64. The database registration unit 130 then registers the device setting table 64 in the setting information database 65. At this time, the database registration unit 130 selects a device identifier from the identifier list table 62 for which the used flag 622 is not set as a recordable device identifier. Specifically, the process is as follows.

[0054] In step S301, the database registration unit 130 reads the device setting table 64.

[0055] The processes from step S302 to step S304 are executed for each device for which the device setting table 64 has been created.

[0056] In step S302, the database registration unit 130 determines whether or not there is a setting value corresponding to the device identifier in the device setting table 64. For example, in the example of the device setting table 64 in Fig. 6, the MAC address, which is the device identifier, is null data, so it is determined that there is no setting value corresponding to the device identifier.

[0057] If the device setting table 64 contains a setting value corresponding to the device identifier, the process proceeds to step S304. If the device setting table 64 does not contain a setting value corresponding to the device identifier, the process proceeds to step S303.

[0058] In step S303, the database registration unit 130 selects an appropriate device identifier from the identifier list table 62 and records the selected device identifier in the device setting table 64. This assigns the selected device identifier to the device to be processed. Specifically, the database registration unit 130 selects a device identifier from the identifier list table 62 for which the used flag 622 is not set as a recordable device identifier, i.e., an appropriate device identifier.

[0059] In step S304, the database registration unit 130 registers the device setting table 64 in the setting information database 65. Then, the database registration unit 130 returns to step S302 and executes processing on the device setting table 64 of the next device. The processing is repeated until processing is completed for the device setting tables 64 of all devices.

[0060] By the above database registration process, a device setting table 64 including device identifiers is registered as the setting information database 65. In the database registration process, if no device identifiers are described in the system design information 61, an appropriate device identifier is assigned to each device described in the specifications, and a device setting table 64 including the device identifiers is generated and registered in the setting information database 65.

[0061] Fig. 8 is a diagram showing an example of a device setting table 64 in which device identifiers are recorded by the database registration process. Device identifiers for which the in-use flag 622 is not set in the identifier list table 62 of Fig. 4 are recorded in the MAC address (device identifier) ​​field in the device setting table 64 of Fig. 6, thereby obtaining the device setting table 64 of Fig. 8.

[0062] 9 shows examples 1 and 2 of a program development environment screen 41 according to this embodiment. The development environment unit 140 displays the program development environment screen 41 for searching the setting information database 65 using a device identifier.

[0063] <<Example 1 of Program Development Environment Screen 41>> Example 1 of the program development environment screen 41 allows the user to select the device to be configured. At this time, the development environment unit 140 searches the setting information database 65 and displays a list of the devices to be configured in a pull-down list format to allow the user to confirm and select the device to be configured.

[0064] Alternatively, the development environment unit 140 may acquire the device identifiers of all devices by communicating with the devices via the communication device 950. Specifically, by connecting the devices to be configured to the setting management device 100 with a communication cable, the development environment unit 140 may acquire the device identifiers of the connected devices and recognize the devices to be configured.

[0065] <<Example 2 of Program Development Environment Screen 41>> In Example 2 of the program development environment screen 41, the development environment unit 140 searches the setting information database 65 using a device identifier on the program development environment screen 41 and inputs setting values ​​corresponding to the device identifier into setting items. At this time, the development environment unit 140 may perform semi-automatic input by displaying setting values ​​corresponding to the device identifier and prompting the user to confirm the displayed setting values. Alternatively, the development environment unit 140 may perform automatic input without user confirmation. The user inputs program and device setting items via the program development environment screen 41. At this time, the development environment unit 140 searches the setting information database 65 using the device identifier selected using the method described in Example 1 as a search key and automatically inputs the setting items. In addition, before automatic input, it is also possible to request user confirmation before reflecting the settings.

[0066] 10 is a diagram showing an example of program development environment processing according to this embodiment. The development environment unit 140 acquires a device identifier from the device via the communication device 950, compares the acquired device identifier with the device identifier in the setting information database 65, and if the device identifiers match, transmits the setting values ​​in the setting information database 65 to the device. Specifically, this is as follows.

[0067] After completing the program writing, the user connects the device to be configured to the development computer, the setting management device 100, via a communication line. For example, a LAN cable may be used for the connection. The development environment unit 140 acquires the device identifier of the device through communication with the device. The development environment unit 140 compares the device identifier with the device identifier of the program and settings currently being developed, and if they match, writes the program and settings via communication with the device identifier as the destination.

[0068] The development environment processing described above in the setting management device 100 allows the device identifier to be used to generate settings, reference settings in the development environment, and write settings, thereby reducing the amount of manual input by the user and preventing setting errors.

[0069] ***Other Configurations*** <Variation 1> In this embodiment, if a device identifier is not recorded in the device setting table 64, the database registration unit 130 selects a device identifier for which the used flag 622 is not set. In other words, it is necessary to set the used flag 622 in the identifier list table 62. In Variation 1, a method of selecting a recordable device identifier without setting the used flag 622 in the identifier list table 62 will be described.

[0070] When the table generation unit 120 obtains a device identifier as a setting value as a result of the search (YES in step S203), it determines whether the same device identifier exists in the identifier list table 62. If the same device identifier exists, the table generation unit 120 deletes the device identifier that exists in the identifier list table 62 and adds the device identifier to the end of the identifier list table 62. As a result of this processing, the device identifier in the front row of the identifier list table 62 becomes unused. Then, in step S303, the database registration unit 130 selects the device identifier in the front row of the identifier list table 62 as a recordable device identifier. This processing makes it possible to appropriately select a recordable device identifier without setting a used flag 622 in the identifier list table 62.

[0071] <Modification 2> In this embodiment, the functions of identifier list creation unit 110, table generation unit 120, database registration unit 130, and development environment unit 140 are realized by software. As a modification, the functions of component identifier list creation unit 110, table generation unit 120, database registration unit 130, and development environment unit 140 may be realized by hardware. Specifically, setting management device 100 includes electronic circuitry 909 instead of processor 910.

[0072] 11 is a diagram showing an example of the configuration of a setting management device 100 according to a modified example of this embodiment. The electronic circuit 909 is a dedicated electronic circuit that realizes the functions of the identifier list creation unit 110, the table generation unit 120, the database registration unit 130, and the development environment unit 140. Specifically, the electronic circuit 909 is a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA. GA is an abbreviation for Gate Array. ASIC is an abbreviation for Application Specific Integrated Circuit. FPGA is an abbreviation for Field-Programmable Gate Array.

[0073] The functions of the identifier list creation unit 110, table generation unit 120, database registration unit 130, and development environment unit 140 may be realized by a single electronic circuit, or may be realized by distributing them across multiple electronic circuits.

[0074] As another modification, some of the functions of the identifier list creation unit 110, table generation unit 120, database registration unit 130, and development environment unit 140 may be realized by electronic circuits, with the remaining functions being realized by software. Also, some or all of the functions of the identifier list creation unit 110, table generation unit 120, database registration unit 130, and development environment unit 140 may be realized by firmware.

[0075] Each of the processor and the electronic circuit is also called processing circuitry. That is, the functions of the identifier list creation unit 110, the table generation unit 120, the database registration unit 130, and the development environment unit 140 are realized by processing circuitry.

[0076] ***Explanation of the Effects of the Present Embodiment*** As described above, the setting management device 100 according to the present embodiment can include device identifiers in the setting information database, thereby achieving the effect of efficiently managing and utilizing the setting information database. Specifically, using device identifiers as serial numbers in the setting information database has the effect of facilitating searches. It also has the effect of facilitating reference to settings from the program development environment screen. This allows the user to search for and reference setting values ​​listed in design documents by device identifier, and use them for automatic or semi-automatic input assistance in the setting software or program development environment.

[0077] 12 is a diagram illustrating an example of the effect achieved by the setting management device 100 according to this embodiment. Fig. 12 shows a process of searching the setting information database 65 for the device to be replaced using the device identifier of the device to be replaced as a search key, and updating the device setting table 64 of the device to the device identifier of the new device to be replaced. Thus, according to the setting management device 100 according to this embodiment, even when a device is replaced with a new device, the setting information database 65 can be managed by the device identifier.

[0078] 13 is a diagram illustrating another example of the effect achieved by the setting management device 100 according to this embodiment. As shown in FIG. 13, a user can use a device identifier from the setting software or program development environment to search the setting information database 65, and write settings to a remote device having the device identifier by specifying the remote device as the destination. In this way, by using the device identifier as a search key for the setting information database 65, the selection of setting content, the selection of the device to be configured, and the destination in setting communications, settings can be managed efficiently using a single variable.

[0079] In the first embodiment described above, each unit of the setting management device has been described as an independent functional block. However, the configuration of the setting management device does not have to be the same as that of the above-described embodiment. The functional blocks of the setting management device may have any configuration as long as they can realize the functions described in the above-described embodiment. Furthermore, the setting management device may not be a single device, but may be a system composed of multiple devices. Furthermore, multiple parts of the first embodiment may be combined to implement the present invention. Alternatively, only one part of this embodiment may be implemented. In addition, this embodiment may be combined in any way, either as a whole or in part. In other words, in the first embodiment, the parts of the embodiment may be freely combined, or any component of the embodiment may be modified or omitted.

[0080] The above-described embodiments are essentially preferred examples and are not intended to limit the scope of the present disclosure, the scope of application of the present disclosure, or the scope of use of the present disclosure. The above-described embodiments can be modified in various ways as needed. For example, the procedures described using flow charts or sequence diagrams may be modified as appropriate.

[0081] 41 program development environment screen, 61 system design information, 62 identifier list table, 63 item list table, 64 device setting table, 65 setting information database, 100 setting management device, 110 identifier list creation unit, 120 table generation unit, 130 database registration unit, 140 development environment unit, 160 storage unit, 200 device, 621 device identifier, 622 used flag, 909 electronic circuit, 910 processor, 921 memory, 922 auxiliary storage device, 930 input interface, 940 output interface, 950 communication device.

Claims

1. A setting management device for managing the settings of devices provided in a system, comprising: an identifier list creation unit which creates a list of device identifiers for identifying the devices as an identifier list table; a table creation unit which searches for setting values ​​to be set for the devices from system design information which indicates the design content of the system, and generates a table in which the setting values ​​obtained by the search are recorded as a device setting table; and a database registration unit which determines whether a device identifier is recorded as a setting value in the device setting table, and if the device identifier is not recorded, selects a recordable device identifier from the identifier list table, records it in the device setting table, and registers the device setting table as a setting information database.

2. The setting management device of claim 1, wherein the identifier list creation unit creates the identifier list table based on at least one of the system design information, the device identification information assigned to the device, and external input.

3. A setting management device as described in claim 1 or claim 2, wherein the table generation unit refers to an item list table indicating a list of items to be recorded in the equipment setting table, searches the system design information for setting values ​​to be set for items included in the item list table, and records information indicating null data for items for which no setting value can be found as a result of the search.

4. A setting management device as described in any one of claims 1 to 3, wherein when a device identifier is obtained as a setting value as a result of the search, the table generation unit determines whether or not an identical device identifier exists in the identifier list table, and if so, sets a used flag for that device identifier, and the database registration unit selects a device identifier from the identifier list table for which the used flag is not set as the recordable device identifier.

5. When a device identifier is obtained as a setting value as a result of the search, the table generation unit determines whether or not the same device identifier exists in the identifier list table, and if so, deletes the device identifier existing in the identifier list table and adds the device identifier to the end of the identifier list table, and the database registration unit sets the device identifier in the front row of the identifier list table as the recordable device identifier. A setting management device as described in any one of claims 1 to 3.

6. The setting management device according to any one of claims 1 to 5, further comprising a development environment unit that displays a program development environment screen for searching the setting information database using the device identifier.

7. A setting management device as described in claim 6, wherein the development environment unit searches the setting information database using the device identifier on the program development environment screen and inputs a setting value corresponding to the device identifier into a setting item.

8. A setting management device as described in claim 6 or claim 7, wherein the development environment unit acquires a device identifier from the device via a communication device, compares the acquired device identifier with a device identifier in the setting information database, and transmits a setting value in the setting information database to the device if the device identifiers match.

9. A setting management method used in a setting management device that is a computer that manages the settings of devices provided in a system, the method comprising: the computer creates a list of device identifiers that identify the devices as an identifier list table; the computer searches for setting values ​​to be set for the devices from system design information that indicates the design contents of the system, and generates a table that records the setting values ​​obtained by the search as a device setting table; the computer determines whether or not a device identifier is recorded as a setting value in the device setting table, and if the device identifier is not recorded, the computer selects a recordable device identifier from the identifier list table and records it in the device setting table, and registers the device setting table as a setting information database.

10. A setting management program used in a setting management device, which is a computer that manages the settings of devices provided in a system, which causes the computer to execute the following steps: an identifier list creation process that creates a list of device identifiers that identify the devices as an identifier list table; a table creation process that searches for setting values ​​to be set for the devices from system design information that indicates the design content of the system, and generates a table that records the setting values ​​obtained by the search as a device setting table; and a database registration process that determines whether a device identifier is recorded as a setting value in the device setting table, and if the device identifier is not recorded, selects a recordable device identifier from the identifier list table, records it in the device setting table, and registers the device setting table as a setting information database.

Citation Information

Patent Citations

  • Music processing apparatus

    JP2007293311A

  • Parameter sheet creation device and creating method

    JP2017041082A

  • Industrial automation project code development guidance and analysis

    US20220075351A1

  • Parameter configuration system

    WO2014087507A1