JP7103842B2 - Device management device and tag name verification method - Google Patents

Description

The present invention relates to a tag name verification technique for verifying a tag name of a device included in device information.

In large-scale facilities such as plants and buildings, equipment management devices are used to monitor and set a large number of equipment such as pressure sensors, flow rate sensors, and positioners that control the opening of valves.
In such a device management device, as device information related to each device, there is a case where the device information of each device is taken in from another management system connected to the device management device via a communication line. As a result, the work load required for resetting the device information can be reduced.

Japanese Unexamined Patent Publication No. 2014-13502

When importing device information from another management system into the device management device, there is a difference between the device information of the device management device and the other device information of the other management system due to an operation error or updating of the device information after importing. In some cases. The device information of the device management device also includes a tag name for identifying the device, and if the tag name is different, there arises a problem that the device cannot be accessed correctly from the device management device. In addition, if the tag names are incorrect, even if the device management device is accessing an unexpected device, a communication error does not occur immediately, and the discovery of the problem may be delayed. Therefore, a mechanism for verifying whether the tag name of the device is correctly defined between the own device information and the other device information is required.

For example, a technique has been proposed that automatically checks the AI (analog input) / AO (analog output) of a device by using OPC (OLE for Process Control) communication, which is a unified standard for process control (for example). (See Patent Document 1 and the like). In this technique, AI / AO check is automated by using OPC communication in addition to HART (Highway Addressable Remote Transducer) communication, which is an industry standard used for controlling devices. However, if the tag names of the devices are inconsistent, there is a problem that the AI / AO check cannot be performed correctly.

The present invention is for solving such a problem, and an object of the present invention is to provide a tag name verification technique capable of automatically verifying the consistency of tag names of devices.

In order to achieve such an object, the device management device according to the present invention is a device management device that performs data communication with the device based on the tag name and address of the device included in the device information, and is the device. In the storage unit that stores the first device information including the tag name of the device and the second device information including the tag name and address of the device, and the tag name of the device acquired from the first device information. Based on this, a first communication processing unit that performs data communication with the device, and a second communication processing unit that performs data communication with the device based on the address of the device acquired from the second device information. After setting the setting value for verification in the device using the communication processing unit of either the first or the second communication processing unit, the communication of the other of the first or second communication processing unit is performed. An output value corresponding to the set value is acquired from the device using a processing unit, and based on the comparison result between the set value and the output value, the tag name included in the first device information and the first device. It is provided with a tag name verification unit that verifies the consistency between the address included in the device information of 2 and the corresponding tag name.

Further, one configuration example of the device management device according to the present invention is based on whether or not the tag name verification unit includes the deviation between the set value and the output value within a preset allowable range. Therefore, the consistency / inconsistency of the tag name is determined.

Further, in one configuration example of the device management device according to the present invention, when the tag name verification unit includes the deviation within the permissible range, the setting value is again instructed to the device and the device is used. The acquisition of the output value is executed, and it is determined that the tag names are consistent only when the deviation between the obtained set value and the output value is included in the preset allowable range. It is the one that was made.

Further, in one configuration example of the device management device according to the present invention, the tag name verification unit repeatedly executes the instruction of the set value to the device and the acquisition of the output value from the device a specified number of times. , The deviation between each set value and the output value is obtained, and the matching / inconsistency of the tag name is determined based on the comparison result between the deviation for the specified number of times and the allowable range. ..

Further, in one configuration example of the device management device according to the present invention, when the tag name verification unit acquires a new output value from the device, the device is instructed to set a different setting value from the previous time. It is a thing.

Further, in one configuration example of the device management device according to the present invention, the tag name verification unit parallels the instruction of the set value to the device and the acquisition of the output value from the device to a plurality of devices. It is intended to be executed as a target.

Further, in one configuration example of the device management device according to the present invention, the tag name verification unit uses different values among the plurality of devices as the set values.

Further, in one configuration example of the device management device according to the present invention, the first communication processing unit comprises an OPC communication processing unit that performs data communication with the device based on the tag name of the device, and the second communication processing unit. The communication processing unit includes a HART communication processing unit that performs data communication with the device based on the address of the device, and the tag name verification unit uses the second communication processing unit to set the set value of the device. After instructing the output of the set value from the device by setting to, the first communication processing unit is used to acquire the output value corresponding to the set value from the device.

Further, in one configuration example of the device management device according to the present invention, the first communication processing unit comprises an OPC communication processing unit that performs data communication with the device based on the tag name of the device, and the second communication processing unit. The communication processing unit includes a HART communication processing unit that performs data communication with the device based on the address of the device, and the tag name verification unit uses the first communication processing unit to set the set value of the device. After instructing the output of the set value from the device by setting to, the second communication processing unit is used to acquire the output value corresponding to the set value from the device.

Further, the tag name verification method according to the present invention is a tag name verification method used in a device management device that performs data communication with the device based on the tag name and address of the device included in the device information. The communication processing unit of the first communication processing unit performs data communication with the device based on the tag name of the device acquired from the first device information, and the second communication processing unit performs the second device information. The second communication processing step of performing data communication with the device based on the address of the device associated with the same tag name as the tag name obtained from, and the tag name verification unit are the first or the above. After setting the setting value for verification in the device using either one of the second communication processing units, the other communication processing unit of the first or second communication processing unit is used. The output value corresponding to the set value is acquired from the device, and the consistency of the tag name included in the first and second device information is verified based on the comparison result between the set value and the output value. It has a tag name verification step to do.

According to the present invention, the tag name is automatically verified using an actual device. Therefore, if the above-mentioned tag name verification process is executed for each device after fetching the device information from another management system, it is possible to verify the consistency of the tag name of each device with a small work load. ..

It is a block diagram which shows the structure of the device management apparatus. This is a configuration example of the first device information used in the OPC system. This is a configuration example of the second device information used in the device management device. It is a flowchart which shows the tag name verification process (AI) which concerns on 1st Embodiment. It is a flowchart which shows the tag name verification process (AO) which concerns on 1st Embodiment. It is a flowchart which shows the tag name verification process (AI) which concerns on 2nd Embodiment. It is a flowchart which shows the tag name verification process (AO) which concerns on 2nd Embodiment. It is a flowchart which shows the tag name verification process which concerns on 3rd Embodiment. This is an example of assigning set values.

Next, an embodiment of the present invention will be described with reference to the drawings.
[First Embodiment]
First, the device management device 10 according to the first embodiment of the present invention will be described with reference to FIG. FIG. 1 is a block diagram showing a configuration of a device management device.
The device management device 10 has a function of monitoring and controlling each device 50 by performing data communication with the device 50 based on the tag name and address of the device 50 included in the device information, and its own device related to these devices 50. It has a function of verifying the consistency of the tag name of each device 50 included in the device information of the device 50 and the device information about the device 50 acquired from the OPC system 20.

As a specific example of the device management device 10, there is a device management server that monitors and sets the device 50 such as a pressure sensor, a flow rate sensor, and a positioner that controls the opening degree of a valve in a large-scale facility such as a plant or a building.
The OPC system 20 is composed of an operation monitoring control system such as H-DEO (Harmonas-DEO: cooperative automation system), and uses OPC (OLE for Process Control) communication to perform data communication with the device 50. It has a function of monitoring and controlling each device 50.
The device 50 is connected to the communication line L1 and the communication line L2 via the IO unit 33.

The controller 31 is connected between the OPC system 20 and the communication line L1 and has a function of relaying data communication between the OPC system 20 and the device 50 using OPC communication.
The gateway 32 is connected between the device management device 10 and the communication line L2, and has a function of relaying data communication between the device management device 10 and the device 50 using HART (Highway Addressable Remote Transducer) communication. is doing.
The IO unit 33 has a function of connecting a plurality of devices 50 housed under the control to the communication lines L1 and L2 based on the protocol of OPC communication or HART communication.

[Device management device]
Next, with reference to FIG. 1, the configuration of the device management device 10 according to the present embodiment will be described in detail.
As shown in FIG. 1, the device management device 10 has an operation input unit 11, a screen display unit 12, a storage unit 13, and an OPC communication processing unit, which are connected so as to be able to exchange data via a bus B, as main functional units. It includes 14, a HART communication processing unit 15, and a tag name verification unit 16. Among these functional units, the OPC communication processing unit 14, the HART communication processing unit 15, and the tag name verification unit 16 are realized by the cooperation of the CPU and the program.

The operation input unit 11 is composed of an operation input device such as a keyboard, a mouse, and a touch panel, and has a function of detecting and outputting an operator's operation.
The screen display unit 12 is composed of a screen display device such as an LCD, and has a function of displaying various screens such as an operation menu screen, a setting screen, and a verification result screen.

The storage unit 13 is composed of a storage device such as a hard disk or a semiconductor memory, and has a function of storing various processing data and programs used for the tag name verification process executed by the device management device 10.
The main processing data stored in the storage unit 13 includes first device information used in the OPC system 20 and second device information used in the device management device 10. It is assumed that the first device information is stored in the storage unit 13 before executing the tag name verification process. Regarding the first device information, even if the tag name verification unit 16 acquires the first device information by performing data communication with the OPC system 20 via the OPC communication processing unit 14 and stores it in the storage unit 13. good. Alternatively, the tag name verification unit 16 may acquire the first device information stored in the recording medium from the OPC system 20 and store it in the storage unit 13.

FIG. 2 is a configuration example of the first device information used in the OPC system. Here, at least a tag name is registered for each device ID for identifying the device 50.
FIG. 3 is a configuration example of the second device information used in the device management device. Here, at least a tag name and an address are registered for each device ID for identifying the device 50.
Of these device information, the tag name is used in OPC communication and the address is used in HART communication.

The OPC communication processing unit (first communication processing unit) 14 passes through the OPC system 20, the controller 31, the communication line L1, and the IO unit 33 based on the tag name of the device 50 acquired from the first device information. , Has a function of performing data communication with the device 50.
The HART communication processing unit (second communication processing unit) 15 determines the data with the device 50 via the gateway 32, the communication line L2, and the IO unit 33 based on the address of the device 50 acquired from the second device information. It has a function to communicate.

The tag name verification unit 16 has a function of setting a setting value for verification in the device 50 by using either the communication processing unit of the OPC communication processing unit 14 or the HART communication processing unit 15, and the OPC communication processing unit after the setting. OPC communication processing based on the function of acquiring the output value corresponding to the set value from the device 50 using the communication processing unit of either 14 or the HART communication processing unit 15 and the comparison result of the set value and the output value. It has a function to verify the consistency between the tag name included in the first device information used in the unit 14 and the address included in the second device information used in the HART communication processing unit 15 and the corresponding tag name. is doing.

At this time, the tag name verification unit 16 outputs the set value from the device 50 by setting the set value to the device 50 using the HART communication processing unit 15 based on the address of the device 50 acquired from the second device information. And a function to acquire an output value corresponding to the above set value from the device 50 by using the OPC communication processing unit 14 based on the tag name of the device 50 acquired from the first device information after setting. Have. As a result, the tag name can be verified using the analog input port (AI) of the device 50.

Further, the tag name verification unit 16 outputs the set value from the device 50 by setting the set value to the device 50 using the OPC communication processing unit 14 based on the tag name of the device 50 acquired from the first device information. It has a function of instructing the device 50 and a function of acquiring an output value corresponding to the set value from the device 50 by using the HART communication processing unit 15 based on the address of the device 50 acquired from the second device information after setting. is doing. As a result, the tag name can be verified using the analog output port (AO) of the device 50.

[Operation of the first embodiment]
Next, the operation of the device management device 10 according to the present embodiment will be described.
The tag name verification unit 16 of the device management device 10 uses the first device information and the second device information regarding the target device 50 to be verified in response to the operator instruction detected by the operation input unit 11. Verify the consistency of the registered tag name. There are two methods for verifying the consistency, one is to use the AI (analog input port) of the target device 50, and the other is to use the AO (analog output port). Which method to use may be selected according to the port type provided in the target device 50 and the operator's instruction.

[Tag name verification process (AI)]
First, the tag name verification process using AI (analog input port) will be described with reference to FIG. FIG. 4 is a flowchart showing a tag name verification process (AI) according to the first embodiment.

First, the tag name verification unit 16 acquires the address of the target device 50 from the second device information (step S100), and the verification preset is performed by HART communication using the HART communication processing unit 15 based on the address. By setting the set value for the target device 50 in the target device 50, the output of the set value from the AI of the target device 50 is instructed (step S101).

Next, the tag name verification unit 16 acquires the tag name of the target device 50 from the first device information (step S102), and performs the above-mentioned set value by OPC communication using the OPC communication processing unit 14 based on the tag name. The output value corresponding to the above is acquired from the AI of the target device 50 (step S103).
After that, the tag name verification unit 16 confirms whether or not the deviation between the set value and the output value is included in the preset allowable range (step S104).

Here, when the deviation between the set value and the output value is included in the permissible range (step S104: YES), the tag name verification unit 16 sets the tag name of the target device 50 included in the first device information and the first device. It is determined that the tag name of the target device 50 included in the device information of 2 is consistent (step S105), and a series of tag name verification processes are completed.
On the other hand, when the deviation between the set value and the output value is not included in the permissible range (step S104: NO), the tag name verification unit 16 sets the tag name of the target device 50 included in the first device information and the first. It is determined that the tag name of the target device 50 included in the device information of 2 is inconsistent (step S106), and a series of tag name verification processes are completed.

[Tag name verification process (AO)]
First, the tag name verification process using the AO (analog output port) will be described with reference to FIG. FIG. 5 is a flowchart showing a tag name verification process (AO) according to the first embodiment.

First, the tag name verification unit 16 acquires the tag name of the target device 50 from the first device information (step S110), and is preset by OPC communication using the OPC communication processing unit 14 based on the tag name. By setting the set value for verification in the target device 50, the output of the set value from the AO of the target device 50 is instructed (step S111).

Next, the tag name verification unit 16 acquires the address of the target device 50 from the second device information (step S112), and responds to the above set value by HART communication using the HART communication processing unit 15 based on the address. The output value is acquired from the AO of the target device 50 (step S113).
After that, the tag name verification unit 16 confirms whether or not the deviation between the set value and the output value is included in the preset allowable range (step S114).

Here, when the deviation between the set value and the output value is included in the permissible range (step S114: YES), the tag name verification unit 16 sets the tag name of the target device 50 included in the first device information and the first. It is determined that the tag name of the target device 50 included in the device information of 2 is consistent (step S115), and a series of tag name verification processes are completed.
On the other hand, when the deviation between the set value and the output value is not included in the permissible range (step S114: NO), the tag name verification unit 16 sets the tag name of the target device 50 included in the first device information and the first. It is determined that the tag name of the target device 50 included in the device information of 2 is inconsistent (step S116), and a series of tag name verification processes are completed.

[Effect of the first embodiment]
As described above, in the present embodiment, the tag name verification unit 16 sets the setting value for verification in the device 50 by using either the communication processing unit of the OPC communication processing unit 14 or the HART communication processing unit 15. After that, the output value corresponding to the set value is acquired from the device 50 by using the communication processing unit of either the OPC communication processing unit 14 or the HART communication processing unit 15, and based on the comparison result of the set value and the output value, the output value is obtained. The consistency between the tag name included in the first device information and the address included in the second device information and the corresponding tag name is verified.

Generally, when the device information is taken into the device management device 10 from another management system such as the OPC system 20, between the second device information of the device management device 10 and the first device information of the other management system, If there is a difference in the tag names, there arises a problem that the device management device 10 cannot correctly access the device 50.
According to this embodiment, the tag name is automatically verified using the actual device 50. Therefore, if the above-mentioned tag name verification process is executed for each device 50 after fetching the device information from another management system, it is possible to verify the consistency of the tag name of each device 50 with a small work load. It becomes.

Further, in the present embodiment, the tag name verification unit 16 performs matching / inconsistency of the tag name based on whether or not the deviation between the set value and the output value is included in the preset allowable range. It may be determined. As a result, even if there is an error in the input / output of the device 50, it can be verified correctly.

Further, in the present embodiment, the tag name verification unit 16 sets the set value in the device 50 by using the HART communication processing unit 15 based on the address of the device 50 acquired from the second device information. Based on the function of instructing the output of the set value from the device and the tag name of the device 50 acquired from the first device information after the setting, the OPC communication processing unit 14 is used to output the output value according to the above set value from the device 50. You may try to get it.
As a result, the tag name can be verified using the analog input port (AI) of the device 50.

Further, in the present embodiment, the tag name verification unit 16 sets the set value in the device 50 by using the OPC communication processing unit 14 based on the tag name of the device 50 acquired from the first device information. Based on the function of instructing the output of the set value from 50 and the address of the device 50 acquired from the second device information after setting, the HART communication processing unit 15 is used to output the output value according to the above set value from the device 50. It has a function to acquire.
As a result, the tag name can be verified using the analog output port (AO) of the device 50.

[Second Embodiment]
Next, the device management device 10 according to the second embodiment of the present invention will be described.
In the first embodiment, when the deviation between the set value and the output value is included in the permissible range, the case where it is immediately determined to be consistent has been described. However, it is possible that the deviation between the set value and the output value was accidentally included within the permissible range. In this embodiment, an example of determining matching when the deviation between the set value and the output value is included within the permissible range will be described twice in succession.

That is, in the present embodiment, when the deviation between the set value and the output value is included in the allowable range, the tag name verification unit 16 again instructs the device 50 of the set value and acquires the output value from the device 50. Is executed, and only when the deviation between the obtained set value and the output value is included in the preset allowable range, the tag name is determined to be consistent. The other configurations according to the present embodiment are the same as those of the first embodiment, and detailed description thereof will be omitted here.

[Operation of the second embodiment]
Next, the operation of the device management device 10 according to the present embodiment will be described.
The tag name verification unit 16 of the device management device 10 uses the first device information and the second device information regarding the target device 50 to be verified in response to the operator instruction detected by the operation input unit 11. Verify the consistency of the registered tag name. There are two methods for verifying the consistency, one is to use the AI (analog input port) of the target device 50, and the other is to use the AO (analog output port). Which method to use may be selected according to the port type provided in the target device 50 and the operator's instruction.

[Tag name verification process (AI)]
First, the tag name verification process using AI (analog input port) will be described with reference to FIG. FIG. 6 is a flowchart showing the tag name verification process (AI) according to the second embodiment.

First, the tag name verification unit 16 acquires the address of the target device 50 from the second device information (step S200), and performs preset verification by HART communication using the HART communication processing unit 15 based on the address. By setting the set value for the target device 50 in the target device 50, the output of the set value from the AI of the target device 50 is instructed (step S201).

Next, the tag name verification unit 16 acquires the tag name of the target device 50 from the first device information (step S202), and performs the above-mentioned set value by OPC communication using the OPC communication processing unit 14 based on the tag name. The output value corresponding to the above is acquired from the AI of the target device 50 (step S203).
After that, the tag name verification unit 16 confirms whether or not the deviation between the set value and the output value is included in the preset allowable range (step S204).

Here, when the deviation between the set value and the output value is included in the allowable range (step S204: YES), the tag name verification unit 16 again performs the HART communication processing unit 15 based on the address, as in step S201. By setting the preset setting value for verification in the target device 50 by HART communication using the above, the output of the set value from the AI of the target device 50 is instructed (step S205). At this time, a value different from that in step S201 may be used as the set value. As a result, the accuracy of verification of consistency can be improved.

Further, similarly to step S203, the tag name verification unit 16 again performs OPC communication using the OPC communication processing unit 14 based on the tag name to output an output value according to the above set value from the AI of the target device 50. Acquire (step S206).
After that, the tag name verification unit 16 confirms whether or not the deviation between the set value and the output value is included in the preset allowable range, as in step S204 (step S207).

Here, when the deviation between the set value and the output value is included in the permissible range (step S207: YES), the tag name verification unit 16 sets the tag name of the target device 50 included in the first device information and the first device. It is determined that the tag name of the target device 50 included in the device information of 2 is consistent (step S208), and a series of tag name verification processes are completed.
On the other hand, when the deviation between the set value and the output value is not included in the permissible range (step S207: NO), the tag name verification unit 16 sets the tag name of the target device 50 included in the first device information and the first. It is determined that the tag name of the target device 50 included in the device information of 2 is inconsistent (step S209), and a series of tag name verification processes are completed.

Further, in step S204, when the deviation between the set value and the output value is not included in the allowable range (step S204: NO), the tag name verification unit 16 uses the tag of the target device 50 included in the first device information. It is determined that the name and the tag name of the target device 50 included in the second device information are inconsistent (step S209), and a series of tag name verification processes are completed.

[Tag name verification process (AO)]
First, the tag name verification process using the AO (analog output port) will be described with reference to FIG. 7. FIG. 7 is a flowchart showing a tag name verification process (AO) according to the second embodiment.

First, the tag name verification unit 16 acquires the tag name of the target device 50 from the first device information (step S210), and is preset by OPC communication using the OPC communication processing unit 14 based on the tag name. By setting the setting value for verification in the target device 50, the output of the set value from the AO of the target device 50 is instructed (step S211).

Next, the tag name verification unit 16 acquires the address of the target device 50 from the second device information (step S212), and responds to the above set value by HART communication using the HART communication processing unit 15 based on the address. The output value is acquired from the AO of the target device 50 (step S213).
After that, the tag name verification unit 16 confirms whether or not the deviation between the set value and the output value is included in the preset allowable range (step S214).

Here, when the deviation between the set value and the output value is included in the allowable range (step S214: YES), the tag name verification unit 16 again performs the OPC communication processing unit based on the tag name, as in step S211. By setting the preset setting value for verification in the target device 50 by the OPC communication using 14, the output of the set value from the AO of the target device 50 is instructed (step S215). At this time, a value different from that in step S211 may be used as the set value. As a result, the accuracy of verification of consistency can be improved.

Further, the tag name verification unit 16 again acquires an output value according to the above set value from the AO of the target device 50 by HART communication using the HART communication processing unit 15 based on the address, as in step S213. (Step S216).
After that, the tag name verification unit 16 confirms whether or not the deviation between the set value and the output value is included in the preset allowable range, as in step S214 (step S217).

Here, when the deviation between the set value and the output value is included in the permissible range (step S217: YES), the tag name verification unit 16 sets the tag name of the target device 50 included in the first device information and the first device. It is determined that the tag name of the target device 50 included in the device information of 2 is consistent (step S218), and a series of tag name verification processes are completed.
On the other hand, when the deviation between the set value and the output value is not included in the permissible range (step S217: NO), the tag name verification unit 16 sets the tag name of the target device 50 included in the first device information and the first. It is determined that the tag name of the target device 50 included in the device information of 2 is inconsistent (step S219), and a series of tag name verification processes are completed.

Further, in step S214, when the deviation between the set value and the output value is not included in the allowable range (step S214: NO), the tag name verification unit 16 uses the tag of the target device 50 included in the first device information. It is determined that the name and the tag name of the target device 50 included in the second device information are inconsistent (step S219), and a series of tag name verification processes are completed.

[Effect of the second embodiment]
As described above, in the present embodiment, when the tag name verification unit 16 includes the deviation between the set value and the output value within the permissible range, the tag name verification unit 16 again indicates the set value to the device 50 and the output value from the device 50. Is executed, and it is determined that the tag names are consistent only when the deviation between the obtained set value and the output value is included in the preset allowable range.
As a result, even if the deviation between the set value and the output value is accidentally included in the allowable range, the consistency can be detected accurately.

In the present embodiment, an example of determining matching when the deviation between the set value and the output value is included in the allowable range has been described twice in succession, but the number of times is limited to two times. It's not a thing. For example, the instruction of the set value to the device 50 and the acquisition of the output value from the device 50 are repeatedly executed for a specified number of times (three times or more), the deviation between each set value and the output value is obtained, and the specified number of times are obtained. The matching / inconsistency of the tag names may be determined based on the comparison result between the deviation and the permissible range.

At this time, if the ratio in which the deviation is included in the permissible range is equal to or greater than a preset threshold value, it may be determined to be consistent. Further, when the number of times the deviation is included in the permissible range is confirmed continuously for the threshold value or more, it may be determined as matching.
As a result, it is possible to determine the consistency / inconsistency of the tag name more stably.

Further, in the present embodiment, when the tag name verification unit 16 acquires a new output value from the device 50, the tag name verification unit 16 may instruct the device 50 to set a different setting value from the previous time. At this time, the permissible range may be switched according to the obtained output value.
As a result, a new output value can be acquired under conditions different from the previous one, and the matching / inconsistency of the tag name can be determined more accurately.

[Third Embodiment]
Next, a third embodiment of the present invention will be described.
In the first and second embodiments, a case where the device 50 is independently verified with a tag name has been described as an example, but in the present embodiment, a case where a plurality of devices 50 are verified with tag names in parallel will be described. ..

That is, in the present embodiment, the tag name verification unit 16 has a function of instructing the device 50 of the set value and acquiring the output value from the device 50 in parallel to the plurality of devices 50. There is. The other configurations according to the present embodiment are the same as those of the first or second embodiment, and detailed description thereof will be omitted here.

[Operation of the third embodiment]
Next, the operation of the device management device 10 according to the present embodiment will be described with reference to FIG. FIG. 8 is a flowchart showing a tag name verification process according to the third embodiment.
Here, the method of using the AI or AO of the device 50 will be collectively described.

First, the tag name verification unit 16 selects the unverified target device 50 whose tag name has not been verified from among the predetermined target devices 50 in a preset parallel number M (M is an integer of 2 or more). ) Are selected (step S300), and different setting values are assigned to the selected target devices 50 (step S301).

FIG. 9 is an example of assigning set values. Here, in the case of the number of parallel units M = 7, the setting values for the tag name verification for two times are assigned. In the example of FIG. 9, for example, for the 1st to 7th target devices 50, the setting values for the first tag name verification are "5mA", "7mA", "9mA", "11mA", respectively. "13mA", "15mA", and "17mA" are assigned, and as the setting values for the second tag name verification, "6mA", "8mA", "10mA", "12mA", "14mA", respectively. "16mA" and "18mA" are assigned. At this time, the permissible range may be set for each set value.

Next, the tag name verification unit 16 uses the set values assigned to the selected target device 50 to perform the tag name verification process (AI) of FIGS. 4 and 6 described above, or the tag name verification process (AI) of FIG. The tag name verification process (AO) of FIG. 7 is executed in parallel (step S302). As a result, the verification of the tag name of the selected target device 50 is executed in parallel.

After that, the tag name verification unit 16 confirms whether the verification of all the target devices 50 designated in advance has been completed (step S303), and if not completed (step S303: NO), returns to step S300.
On the other hand, when the verification of all the target devices 50 is completed (step S303: YES), a series of tag name verification processes are completed.

[Effect of the third embodiment]
As described above, in the present embodiment, the tag name verification unit 16 executes the instruction of the set value to the device 50 and the acquisition of the output value from the device 50 in parallel to the plurality of devices 50. It is a thing.
As a result, the tag name can be verified efficiently in a short period of time.

Further, in the present embodiment, different set values may be used between the devices 50 that execute the tag name verification in parallel.
As a result, even if the tag names are exchanged between the devices 50 that are executed in parallel, it is possible to accurately determine the consistency / inconsistency of the tag names.

[Extension of Embodiment]
Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the structure and details of the present invention within the scope of the present invention. In addition, each embodiment can be implemented in any combination within a consistent range.

10 ... Equipment management device, 11 ... Operation input unit, 12 ... Screen display unit, 13 ... Storage unit, 14 ... OPC communication processing unit, 15 ... HART communication processing unit, 16 ... Tag name verification unit, 20 ... OPC system, 31 ... controller, 32 ... gateway, 33 ... IO unit, 50 ... equipment, L1, L2 ... communication line.

Claims (10)

A device management device that performs data communication with the device based on the tag name and address of the device included in the device information.
A storage unit that stores the first device information including the tag name of the device and the second device information including the tag name and address of the device.
A first communication processing unit that performs data communication with the device based on the tag name of the device acquired from the first device information.
A second communication processing unit that performs data communication with the device based on the address of the device acquired from the second device information.
After setting the setting value for verification in the device using the communication processing unit of either the first or the second communication processing unit, the communication of the other of the first or second communication processing unit is performed. The processing unit is used to acquire an output value corresponding to the set value from the device, and based on the comparison result between the set value and the output value, the tag name included in the first device information and the first device. A device management device including a tag name verification unit that verifies the consistency between the address included in the device information of 2 and the corresponding tag name. In the device management device according to claim 1,
The tag name verification unit is characterized in determining matching / inconsistency of the tag name based on whether or not the deviation between the set value and the output value is included in a preset allowable range. Equipment management device. In the device management device according to claim 2,
When the deviation is included in the permissible range, the tag name verification unit again instructs the device of the set value and acquires the output value from the device, and together with the obtained set value. A device management device characterized in that it is determined that the tag names are consistent only when the deviation from the output value is included in a preset allowable range. In the device management device according to claim 2,
The tag name verification unit repeatedly executes the instruction of the set value to the device and the acquisition of the output value from the device for a specified number of times, obtains the deviation between each set value and the output value, and obtains the deviation between the set value and the output value. A device management device for determining matching / inconsistency of the tag name based on a comparison result between a deviation for a specified number of times and the allowable range. In the device management device according to claim 3 or 4 .
The tag name verification unit is a device management device characterized in that when a new output value is acquired from the device, a setting value different from the previous one is instructed to the device. In the device management device according to any one of claims 1 to 5.
The tag name verification unit is a device management device, characterized in that it executes the instruction of the set value to the device and the acquisition of the output value from the device in parallel to a plurality of devices. In the device management device according to claim 6,
The tag name verification unit is a device management device characterized in that different values are used among the plurality of devices as the set values. In the device management device according to any one of claims 1 to 7.
The first communication processing unit includes an OPC communication processing unit that performs data communication with the device based on the tag name of the device.
The second communication processing unit includes a HART communication processing unit that performs data communication with the device based on the address of the device.
The tag name verification unit uses the first communication processing unit after instructing the device to output the set value by setting the set value in the device using the second communication processing unit. A device management device characterized in that an output value corresponding to the set value is acquired from the device. In the device management device according to any one of claims 1 to 7.
The first communication processing unit includes an OPC communication processing unit that performs data communication with the device based on the tag name of the device.
The second communication processing unit includes a HART communication processing unit that performs data communication with the device based on the address of the device.
The tag name verification unit uses the second communication processing unit after instructing the device to output the set value by setting the set value in the device using the first communication processing unit. A device management device characterized in that an output value corresponding to the set value is acquired from the device. A tag name verification method used in a device management device that performs data communication with the device based on the tag name and address of the device included in the device information.
A first communication processing step in which the first communication processing unit performs data communication with the device based on the tag name of the device acquired from the first device information.
A second communication process in which the second communication processing unit performs data communication with the device based on the address of the device associated with the same tag name as the tag name acquired from the second device information. Steps and
After the tag name verification unit sets the setting value for verification in the device using either one of the first or second communication processing units, the first or second communication processing unit The output value corresponding to the set value is acquired from the device using any one of the other communication processing units, and the first and second device information is obtained based on the comparison result between the set value and the output value. A tag name verification method comprising a tag name verification step for verifying the consistency of the included tag names.

Images