JP6576852B2 - Device information management system - Google Patents

Description

  The present invention relates to a device information management system that manages device definition information used when accessing information in a device.

  Conventionally, in a large-scale plant, a distributed control system (DCS (Distributed Control System)) that uses a controller to control a field device (device) such as a positioner that controls the opening of a control valve (valve) has been used. Yes.

  The DCS includes an operator console and a controller connected to the operator console through a communication line, and monitors and controls field devices arranged in the plant.

  In recent years, a device management system is used which is connected to the DCS communication line, accesses a desired field device via a controller, and acquires various device diagnosis data in the field device.

  According to this device management system, by displaying the device diagnosis data on the screen of the device management system, it becomes possible to inspect field devices distributed and arranged in the plant online. It is also possible to set or change parameters in the field device (see, for example, Patent Document 1).

  In the DCS connected with this device management system, digital communication is performed with field devices using communication methods such as FF (FOUNDATION Fieldbus) and HART (Highway Addressable Remote Transducer), and field devices are connected from the device management system via the controller. You can access the information in Further, by using the portable device setting tool, it is possible to bring the portable device setting tool into the field and access information in the field device.

  Device management systems and portable device configuration tools use field definition settings screens (for example, parameter settings / changes) using device definition information that contains information such as field device parameter configuration, configuration screens, and methods (batch programs). The parameter detail screen) that can be displayed, or by performing signal conversion of the parameter to perform communication.

  In the HART communication method, a DD (Device Description) file is used as device definition information. In the FF communication method, a capability file (CF) in which device functions and performance are described is used together with the DD file. . In addition, as with the DD file, there is a DTM (Device Type Manager) program used for communication with the device.

JP 2010-258865 A JP 2012-43261 A

  As described above, when accessing / displaying information in a desired field device from a device management system or a portable device setting tool, device definition information stored therein is used. In this case, in the device management system and the portable device setting tool, it is necessary to use device definition information appropriate for the desired field device (operation target device) to be accessed.

  In other words, when updating by introducing new field devices or modifying device definition information, etc., the optimum device definition information determined for the entire system (device definition information that the user has decided to use uniformly within the plant ( For example, the latest device definition information, device definition information whose operation has been confirmed, etc.) must be installed and used in the device management system and portable device setting tool.

  In this case, the device management system is placed in a place where a user is usually present, such as a control room or a computer room, and it is relatively easy to maintain device definition information. However, since the portable device setting tool is usually taken out and used, maintenance is not easy and it is easy to forget to update the device definition information. Note that a device management system that uses device definition information may automatically update by accessing an external server such as a vendor in order to keep its device definition information up-to-date.

  For this reason, for example, the revision of the device definition information installed in the device management system is different from the revision of the device definition information installed in the mobile device setting tool. There is a possibility that the display may be different from the latest one, or a batch program in the old device definition information including a bug before correction may be executed.

  In Patent Document 2, when a parameter setting tool (portable device setting tool) accesses a parameter of a field device that does not support the DTM installed in itself, the DTM corresponding to the field device is installed. A technique for communicating with another device, requesting the transfer of the DTM corresponding to the field device, and additionally installing the DTM transferred from the other device as its own DTM is shown.

  However, in the technique disclosed in Patent Document 2, if there is a corresponding DTM in the parameter setting tool, whether or not the DTM is really the optimum DTM determined for the entire system (for example, the latest DTM). It is not possible to determine whether the DTM is a revision.

  The present invention has been made to solve such a problem, and an object of the present invention is to provide an optimum device defined as the entire system when accessing a desired operation target device in a portable device setting tool. The object is to provide a device information management system capable of always using definition information.

  In order to achieve such an object, the present invention provides information between a portable device setting tool that accesses information in an operation target device based on device definition information stored therein, and the portable device setting tool. Device management system comprising a server (device management system) that transmits and receives data, and the portable device setting tool stores device definition information used for accessing information in the device for each type of operation target device Tool side device definition information storage means for storing, device identification information reading means for reading information for identifying the operation target device, and information for identifying the operation target device read by the device identification information reading means, on the tool side device From the device definition information stored in the definition information storage means, Tool-side optimal device definition information specifying means for specifying optimal device definition information corresponding to the target device as optimal device definition information on the tool side, information for identifying the operation target device read by the device identification information reading means, Tool-side information transmitting means for transmitting the tool-side optimum device definition information identified by the tool-side optimum device definition information identifying means to the server as tool-side information, and the server for each type of operation target device Server-side device definition information storage means for storing device definition information used when accessing information in the device, a tool-side information receiving unit for receiving tool-side information transmitted from the portable device setting tool, and a tool Operation target data included in the tool-side information received by the side-information receiver Based on the information identifying the chair, the optimum device definition information corresponding to the operation target device is identified as the optimum device definition information on the server side from the device definition information stored in the server side device definition information storage means. Server-side optimal device definition information specifying means, information indicating the server-side optimal device definition information specified by the server-side optimal device definition information specifying means, and the tool-side optimum included in the received tool-side information The optimal device definition information comparing means for comparing the information indicating the device definition information with the optimal device definition information comparing means, and the optimal device definition information on the server side is compared with the optimal device definition information on the tool side based on the comparison result of the optimal device definition information comparing means. If the device definition information is more optimal than the server side, the optimal device definition information on the server side Server-side information transmission means for sending the information to the portable device setting tool.

  In the present invention, the portable device setting tool reads information for identifying an operation target device (for example, reads information for identifying the operation target device from an operation target device connected online), and reads the operation target device. From the device definition information stored for each type of operation target device, the optimum device definition information corresponding to the operation target device is specified as the optimum device definition information on the tool side. Then, the server identifies, as tool-side information, information that identifies the read operation target device (for example, information that specifies the device type) and information that indicates the optimal device definition information on the specified tool side (for example, a file name) Send to.

  In the present invention, the server receives the tool-side information transmitted from the portable device setting tool, and based on the information for identifying the operation-target device included in the received tool-side information, Among the device definition information stored for each type, the optimum device definition information corresponding to the operation target device is specified as the optimum device definition information on the server side. Then, the information indicating the optimum device definition information on the server side identified is compared with the information indicating the optimum device definition information on the tool side included in the received tool side information (for example, included in the file name). If the optimal device definition information on the server side is more optimal device definition information than the optimal device definition information on the tool side, the optimal device definition information on the server side Information to the mobile device setting tool.

  Thus, in the present invention, on the portable device setting tool side, the optimum device definition information corresponding to the desired operation target device is stored on the tool side from the device definition information stored for each type of operation target device. The optimum device definition information that is specified as the optimum device definition information and that corresponds to the desired operation target device from the device definition information stored for each type of operation target device on the server side is the optimum device on the server side. If the server-side optimal device definition information is identified as the definition information and is more optimal than the tool-side optimal device definition information (for example, the revision is the latest), the server Side device definition information is sent to the mobile device setting tool. The optimal device definition information is not limited to the latest revision, and may be device definition information whose operation has been confirmed.

  Thus, in the present invention, when accessing the desired operation target device in the portable device setting tool, the system is adapted to rewrite the optimal device definition information on the tool side to the optimal device definition information on the server side. It is possible to always use the optimum device definition information determined as a whole. Further, when accessing a desired operation target device, it is possible to always use the same optimum device definition information defined for the entire system by the server (device management system) and the portable device setting tool.

  Further, in the present invention, the server side information transmitting means, when the optimum device definition information on the tool side is more optimum device definition information than the optimum device definition information on the server side, To send to the mobile device configuration tool as the information on the device side, and the function that does not send information to the mobile device configuration tool when the optimal device definition information on the server side and the optimal device definition information on the tool side are the same , When there is no optimal device definition information on the tool side to be compared with the optimal device definition information on the server side, the server side optimal device definition information is sent to the mobile device setting tool as server side information, etc. It may be a thing.

  In the present invention, information that informs the mobile device setting tool that the optimum device definition information on the tool side is more optimal device definition information than the optimum device definition information on the server side is sent as server side information. In this case, a means for prompting selection of whether to use the optimum device definition information on the tool side or the optimum device definition information on the server side may be provided.

  According to the present invention, on the portable device setting tool side, the optimum device definition information corresponding to the desired operation target device is obtained from the device definition information stored for each type of operation target device. As the definition information, the server-side device-optimized device definition information corresponding to the desired operation-target device is selected from the device-definition information stored for each type of operation-target device. If the optimal device definition information on the server side is more optimal device definition information than the optimal device definition information on the tool side, the optimal device definition information on the server side is sent to the mobile device setting tool. Therefore, the optimal device definition on the server side that is more suitable for the optimal device definition information on the mobile device configuration tool side As rewritten to broadcast, in the mobile device configuration tool, when accessing a desired operation target device, it is possible to always use the best device definition information defined as a whole system.

FIG. 1 is a configuration diagram showing a main part of a device information management system according to Embodiment 1 of the present invention. FIG. 2 is a diagram for explaining reading of information for identifying a device type from a desired field device by the portable device setting tool according to the first embodiment. FIG. 3 is a diagram illustrating information for identifying a device type. FIG. 4 is a diagram showing an image of the directory structure in the device definition file DB. FIG. 5 is a diagram for explaining creation and transmission of information on the tool side in the portable device setting tool according to the first embodiment. FIG. 6 is a diagram for explaining processing and a response in the device definition file server in the first embodiment. FIG. 7 is a diagram for explaining response reception in the portable device setting tool according to the first embodiment. FIG. 8 is a diagram illustrating use of a device definition file in the portable device setting tool according to the first embodiment. FIG. 9 is a diagram for explaining the relationship between the device definition file in the portable device setting tool and the device definition file in the device definition file server and the processing in the tool in the first embodiment. FIG. 10 is a diagram illustrating a screen display example in the portable device setting tool when the optimum device definition file in the device definition file server has an older revision in the first embodiment. FIG. 11 is a functional block diagram of the main parts of the device definition file server and portable device setting tool in the device information management system of the first embodiment. FIG. 12 is a block diagram showing a main part of the device information management system according to Embodiment 2 of the present invention. FIG. 13 is a diagram for explaining reading of information for identifying a device type from a desired field device by the portable device setting tool according to the second embodiment. FIG. 14 is a diagram for explaining creation and transmission of information on the tool side in the portable device setting tool according to the second embodiment. FIG. 15 is a diagram for explaining processing and a response in the device definition file server in the second embodiment. FIG. 16 is a diagram for explaining response reception in the portable device setting tool according to the second embodiment. FIG. 17 is a diagram illustrating use of a device definition file in the portable device setting tool according to the second embodiment.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[Embodiment 1: FF communication system]
FIG. 1 is a configuration diagram showing a main part of a device information management system 100 according to Embodiment 1 of the present invention. In the figure, 1 is a device management system (server), 2 (2-1) is a controller, 3 (3-1) is an I / O module, 4 (4-1, 4-2) is a field device (device). Reference numeral 5 denotes a portable device setting tool.

  In the device information management system 100, the device management system 1 is connected to the controller 2 via the communication line L, and the controller 2 is connected to the field device 4 via the I / O module 3. Digital communication is performed between the I / O module 3 and the field device 4 by the FF communication method.

  The device management system 1 is realized by hardware including a processor and a storage device, and a program that realizes various functions in cooperation with the hardware. The device management system 1 includes a device management system main body 1A and a wireless transmitter / receiver 1B, and has a server function for wirelessly transmitting / receiving information to / from the portable device setting tool 5. In this example, the device management system main body 1A and the radio transceiver 1B are separated from each other. However, the device management system main body 1A and the radio transceiver 1B may be integrated.

  The storage device of the device management system 1 uses the field device 4 as an operation target device, and is used when accessing information in the device (displaying a setting screen, executing a batch program, etc.) for each type of the operation target device. A device definition file DB (server-side device definition file DB1) that holds device definition files is constructed. In this example, a DD file and a capability file (CF) are written as a device definition file in the server-side device definition file DB1.

  In the present embodiment, the device management system 1 is placed in a place where a user is usually present, such as a control room or a computer room, and is relatively easy to maintain, and the device definition in the server-side device definition file DB1. It is assumed that the file is operated while being constantly updated to the optimum device definition file defined for the entire system. For example, it is assumed that the device management system 1 accesses an external server such as a vendor and keeps its own device definition file up to date. Hereinafter, the device management system 1 is referred to as a device definition file server. This device definition file server 1 corresponds to a server in the present invention.

  Similarly to the device definition file server 1, the portable device setting tool 5 is also realized by hardware including a processor and a storage device, and a program that realizes various functions in cooperation with these hardware.

  The portable device setting tool 5 is brought into the field where the field device 4 is installed and used, and connected to the field device 4 as necessary. That is, the connection to the desired field device 4 is made only when setting at the site. The portable device setting tool 5 also has a wireless communication function for transmitting and receiving information to and from the device definition file server 1 wirelessly.

  The storage device of the portable device setting tool 5 uses the field device 4 as an operation target device, and is used for accessing information in the device (displaying a setting screen, executing a batch program, etc.) for each type of the operation target device. A device definition file DB (tool-side device definition file DB2) in which device definition files to be held are held is constructed. In this example, a DD file and a capability file (CF) are written as a device definition file in the tool-side device definition file DB2.

  Hereinafter, specific processing operations in the device information management system 100 according to the first embodiment will be described with the functions of the device definition file server 1 and the portable device setting tool 5 being used.

[Reading information identifying the device type from the desired field device using the portable device setting tool]
An operator (user) brings the portable device setting tool 5 to the site where the field device 4 is installed, and connects the portable device setting tool 5 to the field device 4-1 as a desired operation target device (see FIG. 2). ).

  Then, the mobile device setting tool 5 determines the type of the field device 4-1 such as the manufacturer ID (Manufacturer ID), device type (Device Type), and device revision (Device Revision) from the field device 4-1 connected online. Reads information for identifying (device type). In this example, “MANUFAC_ID: 0DFC96”, “DEV_TYPE: 0203”, and “DEV_REV: 02” are read as information for identifying the device type of the field device 4-1. In addition to the information for identifying the device type, “TAG: AVP001” is read as the tag name assigned to the field device 4-1.

  In the information for identifying the device type, “MANUFAC_ID” is a manufacturer ID (Manufacturer ID), “DEV_TYPE” is a device type (Device Type), and “DEV_REV” is a parameter name indicating a device revision (Device Revision). Yes, it is read as coded information (see FIG. 3).

[Create and send information on the tool side in the mobile device setting tool]
The portable device setting tool 5 then selects the optimum device definition corresponding to the field device 4-1 from the tool-side device definition file DB2 based on the information for identifying the device type of the read field device 4-1. Identify the file as the optimal device definition file on the tool side.

  In this embodiment, in the tool-side device definition file DB2, the manufacturer ID (Manufacturer ID) and the device type (Device Type) are in a directory structure, and the device revision (Device Revision) and DD revision (Device Description Revision) are placed under the directory structure. The DD file is managed in such a form that there exists a DD file having the file name as. Further, the CF is managed in such a form that a CF in which the CF revision (Capability File Revision) is added to the file name exists in the same directory. FIG. 4 shows an image of the directory structure.

  The portable device setting tool 5 identifies an optimum device definition file corresponding to the field device 4-1 as an optimum device definition file on the tool side from the tool side device definition file DB2 in accordance with this directory structure. In this example, as shown in FIG. 5, the latest DD file indicated by the file name “0201.ffo” and the latest CF indicated by the file name “020101.cff” are used as the optimum device definition file on the tool side. Identify.

  That is, the portable device setting tool 5 matches the manufacturer ID (Manufacturer ID) read as information for identifying the device type of the field device 4-1 in the tool-side device definition file DB2, and (2 After satisfying all conditions that the device type (Device Type) matches and (3) the device revision (Device Revision) matches, the DD revision (Device Description Revision) and CF revision (Capability File Revision) The latest DD file and CF are specified as the optimum device definition file on the tool side.

  Then, the portable device setting tool 5 receives information identifying the device type read from the field device 4-1, and information indicating the optimum device definition file on the tool side specified based on the device type information on the tool side. Is transmitted to the device definition file server 1.

  In this example, “manufacturer ID (Manufacturer ID): 0DFC96”, “Device Type: 0203”, and “device revision” are used as information for specifying the device type (device type of the actual device) of the field device 4-1. (Device Revision): 02 ”as information indicating the optimum device definition file on the tool side, the file name“ 0201.ffo ”of the DD file and the file name“ 020101.cff ”of the CF, and the communication type (FF) In addition, the information is transmitted to the device definition file server 1 as information on the tool side.

[Processing and response in the device definition file server]
When the device definition file server 1 receives the information on the tool side from the portable device setting tool 5, based on the information for identifying the device type of the field device 4-1 included in the received information on the tool side, The optimum device definition file corresponding to the field device 4-1 is identified as the optimum device definition file on the server side from the server side device definition file DB1.

  In this embodiment, the server-side device definition file DB1 also has a manufacturer ID (Manufacturer ID) and a device type (Device Type) as a directory structure, and a device revision (Device Revision) and a DD revision (Device Description Revision) thereunder. The DD file is managed in such a form that there exists a DD file having the file name as. Further, the CF is managed in such a form that a CF in which the CF revision (Capability File Revision) is added to the file name exists in the same directory.

  The device definition file server 1 identifies the optimum device definition file corresponding to the field device 4-1 as the optimum device definition file on the server side from the server side device definition file DB1 according to this directory structure. In this example, as shown in FIG. 6, the latest DD file indicated by the file name “0202.ffo” and the latest CF indicated by the file name “020203.cff” are used as the optimum device definition file on the server side. Identify.

  That is, the device definition file server 1 matches the manufacturer ID (Manufacturer ID) read as information for identifying the device type of the field device 4-1 in the server side device definition file DB1, and (2 The DD revision (Device Description Revision) and CF revision (Capability Revision) are the latest after satisfying all the conditions that the device type (Device Type) matches and (3) the device revision (Device Revision) matches. The DD file and CF are identified as the optimum device definition file on the server side.

  Then, the device definition file server 1 uses the tool-side optimum device definition included in the information indicating the identified server-side optimum device definition file and the tool-side information sent from the portable device setting tool 5. Compare with the information indicating the file.

  In this example, the file name “0202.ffo” of the DD file and the CF file name “020203.cff”, which are information indicating the optimal device definition file on the server side, and the information indicating the optimal device definition file on the tool side The DD file name “0201.ffo” and the CF file name “020101.cff” are compared.

  Based on the comparison result between the information indicating the server-side optimum device definition file and the information indicating the tool-side optimum device definition file, the device definition file server 1 determines that the server-side optimum device definition file is If the device definition file is more optimal than the optimal device definition file, the server-side optimal device definition file is transmitted to the portable device setting tool 5 as server-side information.

  In this example, the DD file with the file name “0202.ffo” which is the optimal device definition file on the server side and the CF with the file name “020203.cff” are the file name “0201” which is the optimal device definition file on the tool side. Since the DD revision (Device Description Revision) and CF revision (Capability File Revision) are newer than the DD file of “.ffo” and the CF of the file name “020101.cff”, the device definition file server 1 has the file name “0202.ffo”. And the CF with the file name “020203.cff” are transmitted to the portable device setting tool 5 as server-side information.

[Receiving a response in the mobile device setting tool]
When the portable device setting tool 5 waits for a response from the device definition file server 1 and receives an optimum device definition file on the server side as server side information, the portable device setting tool 5 sends the received optimum device definition file on the server side to the tool side device. Write in the definition file DB2.

  In this example, as shown in FIG. 7, a DD file with a file name “0202.ffo” and a CF with a file name “020203.cff” are received as an optimal device definition file on the server side. .ffo ”DD file and CF with file name“ 020203.cff ”are written in the tool-side device definition file DB2.

[Use of device definition file in mobile device setting tool]
Then, as shown in FIG. 8, the portable device setting tool 5 uses the DD file with the file name “0202.ffo” and the CF with the file name “020203.cff” written in the tool-side device definition file DB2. Thus, the information in the field device 4-1 is accessed to display the setting screen (parameter detail screen) of the field device 4-1, or to perform communication by performing signal conversion of parameters.

  In this way, in the present embodiment, the optimal device definition file on the tool side is rewritten to the optimal device definition file on the server side, and the desired field device 4 is added in the portable device setting tool 5. When accessing, the optimum device definition file defined for the entire system can always be used.

  In addition, since the revision of DD / CF used in both the device management system 1 and the portable device setting tool 5 can be automatically and completely matched, the operator of the device management system 1 (user in the instrument room or the like) The operator (user in the field) of the mobile device setting tool 5 has the same screen and the same value (the value may be displayed by processing with a calculation program in the DD, and if there is a bug, the value will be different) , It is guaranteed to use the same batch program (behaves differently if there is a bug). This makes it possible to perform processing using the same screen and the same batch program, leading to improved communication between both users and improved device setting reliability.

  In the above description, in the device definition file server 1, a case has been described in which the optimum device definition file on the server side is a more optimum device definition file than the optimum device definition file on the tool side (see FIG. 9). "Case 6" shown), when the optimal device definition file on the tool side is a more optimal device definition file than the optimal device definition file on the server side (for example, the optimal device definition file on the server side If the revision is older ("Case 5" shown in FIG. 9), information indicating that is sent from the device definition file server 1 to the portable device setting tool 5 as information on the server side.

  For example, in the case of “Case 5”, the file name of the optimal device definition file on the server side is sent from the device definition file server 1 to the mobile device setting tool 5, and (1) the tool side is sent to the user of the mobile device setting tool 5 The most suitable device definition file and (2) the server-side optimal device definition file are prompted to determine which is the most optimal device definition file.

  FIG. 10 shows a screen display example in the portable device setting tool 5 when urging the user to determine which of the above (1) and (2) is the more optimal device definition file. In this example, on the pop-up screen G1, the user is notified that the optimum device definition file on the tool side is different from the optimum device definition file on the server side, and the user is prompted to select which device definition file to use. Like that. The user presses the button BT1 on the pop-up screen G1 when using the optimum device definition file on the tool side, and the button BT2 on the pop-up screen G1 when using the optimum device definition file on the server side. Press.

  Normally, it is considered that the optimal device definition file on the server side is updated and managed as the master, so the optimal device definition file on the server side is selected (or the optimal device definition file on the server side is selected by default) It is normal to set it in advance. However, the device definition file on the user side is updated (for example, bug fixes) in situations where the device definition file on the server side cannot be updated (for example, there is no one on the server side and there is only one person in the field at midnight). It is necessary to make it possible to select the optimal device definition file on the tool side.

  For this reason, in the first embodiment, as shown in FIG. 10, the user-side device definition file and the tool-side optimum device definition file can be selected on the pop-up screen G1.

  It is also conceivable that the optimal device definition file on the server side and the optimal device definition file on the tool side are the same (“Case 4” shown in FIG. 9). In this case, the device definition file server 1 does not transmit information to the portable device setting tool 5.

  Further, there is a case where there is an optimal device definition file on the tool side, but there is no optimal device definition file on the server side (“Case 3” shown in FIG. 9). Also in this case, the device definition file server 1 does not transmit information to the portable device setting tool 5.

  Further, there is a case where there is an optimal device definition file on the server side, but there is no optimal device definition file on the tool side (“Case 2” shown in FIG. 9). In this case, the device definition file server 1 sends an optimum device definition file on the server side to the portable device setting tool 5.

  Further, there may be a case where neither the server side nor the tool side has an optimal device definition file (“Case 1” shown in FIG. 9). In this case, the device definition file server 1 sends information to that effect to the portable device setting tool 5 to display an error.

  FIG. 11 shows a functional block diagram of main parts of the device definition file server 1 and the portable device setting tool 5 in the device information management system 100 of the first embodiment.

  The portable device setting tool 5 includes a tool-side device definition file storage unit 51, a device identification information reading unit 52, a tool-side optimum device definition file specifying unit 53, a tool-side information transmitting unit 54, and a server-side information receiving unit 55. And a selection screen display unit 57 and a device definition file update unit 56.

  A device definition file server (device management system) 1 includes a server-side device definition file storage unit 11, a tool-side information reception unit 12, a server-side optimum device definition file specifying unit 13, an optimum device definition file comparison unit 14, And a server-side information transmission unit 15.

  In the portable device setting tool 5, the device definition file storage unit 51 stores a device definition file used for accessing information in the field device 4 for each type of the field device 4 (operation target device). Yes. The device identification information reading unit 52 reads information for identifying the field device 4 (information for identifying the device type of the field device 4) from the field device 4 connected online.

  Based on the information for identifying the field device 4 read by the device identification information reading unit 52, the tool-side optimum device definition file specifying unit 53 includes a device definition file stored in the tool-side device definition file storage unit 51. Therefore, the optimum device definition file corresponding to the field device 4 is specified as the optimum device definition file on the tool side. The tool side information transmission unit 54 includes information for identifying the field device 4 read by the device identification information reading unit 52 and an optimum device definition file on the tool side specified by the tool side optimum device definition file specifying unit 53. It is transmitted to the device definition file server 1 as information on the tool side.

  In the device definition file server 1, the server-side device definition file storage unit 11 stores a device definition file used for accessing information in the field device 4 for each type of the field device 4 (operation target device). Yes. The tool side information receiving unit 12 receives the tool side information transmitted from the portable device setting tool 5. The server-side optimum device definition file specifying unit 13 is based on information identifying the field device 4 (information identifying the device type of the field device 4) included in the tool-side information received by the tool-side information receiving unit 12. Thus, the optimum device definition file corresponding to the field device 4 is identified as the optimum device definition file on the server side from among the device definition files stored in the server side device definition file storage unit 11.

  The optimum device definition file comparison unit 14 includes information (file name) indicating the optimum device definition file on the server side specified by the server side optimum device definition file specification unit 13 and the tool included in the received tool side information. Compare the information (file name) that indicates the device definition file that is optimal for the system. Based on the comparison result in the optimum device definition file comparison unit 14, the server side information transmission unit 15 has the optimum device definition file on the server side more optimal than the optimum device definition file on the tool side. In this case, an optimum device definition file on the server side is sent to the portable device setting tool 5 as server side information.

  In addition, when the optimum device definition file on the tool side is a more optimal device definition file than the optimum device definition file on the server side, the server side information transmission unit 15 transmits information notifying the server side information A function for sending information to the mobile device setting tool 5 when the optimal device definition file on the server side and the optimal device definition file on the tool side are the same, If there is no optimal device definition file on the tool side to be compared with the optimal device definition file on the server side, there is also a function to send the optimal device definition file on the server side to the portable device setting tool as server side information. ing.

  In the portable device setting tool 5, the server-side receiving unit 55 receives server-side information sent from the device definition file server 1. The device definition file update unit 56 writes the device definition file in the tool-side device definition file storage unit 51 when the server-side optimal device definition file is sent as server-side information. When the selection screen display unit 57 receives information notifying that the optimum device definition file on the tool side is a more optimal device definition file than the optimum device definition file on the server side as information on the server side, Displays a screen that prompts you to select whether to use the optimal device definition file on the tool side or the optimal device definition file on the server side.

[Embodiment 2: HART communication system]
FIG. 12 is a block diagram showing a main part of the device information management system 200 according to Embodiment 2 of the present invention. In the figure, 1 is a device management system (server), 2 (2-2) is a controller, 3 (3-2) is an I / O module, 4 (4-3, 4-4) is a field device (device). Reference numeral 5 denotes a portable device setting tool.

  In the device information management system 200, the device management system 1 is connected to the controller 2 via the communication line L, and the controller 2 is connected to the field device 4 via the I / O module 3. Digital communication is performed between the I / O module 3 and the field device 4 by the HART communication method. Also in the second embodiment, the device management system 1 is referred to as a device definition file server.

  In the case of the HART communication method, only the DD file, no CF, and the contents described in the first embodiment can be applied as they are except for the part related to the CF. However, the following points are different. Yes. In other words, in order to identify the optimal device definition file, the device revision (Device Revision) is used under the condition that the manufacturer ID (Manufacturer ID) read from the field device (device) matches and the device type (Device Type) matches. If the device definition file that matches is not found, a device definition file having the latest device revision among older device revisions can be selected as the optimum device definition file, which is different from the content described in the first embodiment. ing.

[Reading information identifying the device type from the desired field device using the portable device setting tool]
An operator (user) brings the portable device setting tool 5 to the site where the field device 4 is installed, and connects the portable device setting tool 5 to, for example, the field device 4-3 as a desired operation target device (see FIG. 13). ).

  Then, the portable device setting tool 5 starts the field devices 4-1 such as the manufacturer ID (Manufacturer ID), device type (Device Type), and device revision (Device Revision) from the field device 4-3 connected online. Reads information (parameter) for identifying the type. In this example, “MANUFAC_ID: 000036”, “DEV_TYPE: 0002”, and “DEV_REV: 01” are read as information for identifying the device type of the field device 4-3. In addition to the information for identifying the device type, “TAG: ST001” is read as the tag name assigned to the field device 4-3.

[Create and send information on the tool side in the mobile device setting tool]
The portable device setting tool 5 then selects the optimum device definition corresponding to the field device 4-3 from the tool-side device definition file DB2 based on the information for identifying the device type of the read field device 4-3. Identify the file as the optimal device definition file on the tool side.

  In this embodiment, in the tool-side device definition file DB2, the manufacturer ID (Manufacturer ID) and the device type (Device Type) are in a directory structure, and the device revision (Device Revision) and DD revision (Device Description Revision) are placed under the directory structure. The DD file is managed in such a form that there exists a DD file having the file name as.

  The portable device setting tool 5 identifies the optimum device definition file corresponding to the field device 4-3 as the optimum device definition file on the tool side from the tool side device definition file DB2 in accordance with this directory structure. In this example, as shown in FIG. 14, there is no DD file of “DEV_TYPE: 0002”. For this reason, the portable device setting tool 5 determines that there is no optimal device definition file on the tool side.

  Then, the portable device setting tool 5 includes information for identifying the device type read from the field device 4-3, and information indicating the optimum device definition file on the tool side specified based on the information for identifying the device type. It is transmitted to the device definition file server 1 as information on the tool side.

  In this example, as information for identifying the device type of the field device 4-1 (information for identifying the device type of the actual device), “Manufacturer ID (Manufacturer ID): 000036” and “Device Type: 0002” And “Device Revision: 01” as information indicating the optimum device definition file on the tool side, information indicating that there is no optimum device definition file on the tool side (“None”), communication type (HART) ) And information to the device definition file server 1 as tool-side information.

[Processing and response in the device definition file server]
When the device definition file server 1 receives the information on the tool side from the portable device setting tool 5, based on the information for identifying the device type of the field device 4-3 included in the received information on the tool side, The optimum device definition file corresponding to the field device 4-3 is identified as the optimum device definition file on the server side from the server side device definition file DB1.

  In this embodiment, the server-side device definition file DB1 also has a manufacturer ID (Manufacturer ID) and a device type (Device Type) as a directory structure, and a device revision (Device Revision) and a DD revision (Device Description Revision) thereunder. The DD file is managed in such a form that there exists a DD file having the file name as.

  The device definition file server 1 identifies the optimum device definition file corresponding to the field device 4-3 as the optimum device definition file on the server side from the server side device definition file DB1 according to this directory structure. In this example, as shown in FIG. 15, the latest DD file indicated by the file name “0102.fm8” is specified as the optimum device definition file on the tool side.

  Then, the device definition file server 1 uses the tool-side optimum device definition included in the information indicating the identified server-side optimum device definition file and the tool-side information sent from the portable device setting tool 5. Compare with the information indicating the file. In this example, the file name “0102.fm8” of the DD file, which is information indicating the optimal device definition file on the server side, is compared with “none”, which is information indicating the optimal device definition file on the tool side.

  Based on the comparison result between the information indicating the server-side optimum device definition file and the information indicating the tool-side optimum device definition file, the device definition file server 1 determines that the server-side optimum device definition file is If the device definition file is more optimal than the optimal device definition file, the server-side optimal device definition file is transmitted to the portable device setting tool 5 as server-side information.

  Further, the device definition file server 1 determines that the optimal device definition file on the tool side is the server based on the comparison result between the information indicating the optimal device definition file on the server side and the information indicating the optimal device definition file on the tool side. If the device definition file is more optimal than the optimal device definition file on the side, information indicating that is transmitted to the portable device setting tool 5 as information on the server side. If the optimal device definition file on the server side and the optimal device definition file on the tool side are the same, information is not transmitted to the mobile device setting tool 5. In addition, when there is no optimal device definition file on the tool side to be compared with the optimal device definition file on the server side, the optimal device definition file on the server side is transmitted to the portable device setting tool 5 as server side information. To do.

  In this example, since there is no optimal device definition file on the tool side, the device definition file server 1 transfers the DD file having the file name “0102.fm8” identified as the optimal device definition file on the server side to the server side. The information is transmitted to the portable device setting tool 5 as information.

[Receiving a response in the mobile device setting tool]
When the portable device setting tool 5 waits for a response from the device definition file server 1 and receives an optimum device definition file on the server side as server side information, the portable device setting tool 5 sends the received optimum device definition file on the server side to the tool side. Write in the device definition file DB2.

  In this example, as shown in FIG. 16, the DD file with the file name “0102.fm8” is received as the optimum device definition file on the server side. Therefore, the DD file with the file name “0102.fm8” is received on the tool side. Write in the device definition file DB2.

[Use of device definition file in mobile device setting tool]
Then, as shown in FIG. 17, the mobile device setting tool 5 uses the DD file with the file name “0102.fm8” written in the tool-side device definition file DB2, and stores information in the field device 4-3. To display the setting screen (parameter detail screen) of the field device 4-3, or perform communication by performing parameter signal conversion.

  In the first embodiment, the device definition file is a DD file and a CF, and in the second embodiment, the device definition file is a DD file. However, the present invention can also be applied to a DTM used in the same manner.

  In the first and second embodiments described above, communication between the portable device setting tool 5 and the device definition file server 1 is based on wireless communication, but may be wired communication. If a system consisting only of a control bus using an industrial Ethernet (registered trademark) from a device management system to a field device appears as a future industrial system, send a device definition file using that bus. (It is difficult to realize with the current FF / HART system).

  In consideration of use in a place where the communication status is bad, a mode in which the device definition file held by the mobile device setting tool 5 is not automatically updated may be prepared. By preparing such a mode, it is possible to prevent the communication retry from continuing without finding the device definition file server 1 and degrading the performance.

  Further, a list of all device definition files held by the mobile device setting tool 5 is transmitted to the device definition file server 1 by a user command, and all newer device definition files are transmitted to the mobile device setting tool 5 to be summarized. It is also possible to provide a function such as setting. However, there is a possibility that the transmission target becomes a large amount of data, and there is a possibility that a long waiting time occurs for the user. On the other hand, in the first and second embodiments described above, only a few files are automatically transmitted during online operation, so the transmission target is not a large amount of data and the waiting time for the user is small.

  In the first and second embodiments described above, the device management system 1 is provided with a server function for transmitting and receiving information to and from the portable device setting tool 5. That is, the device management system 1 is used in the present invention. However, a dedicated server may be prepared separately.

  In the first and second embodiments described above, the portable device setting tool 5 is connected to the field device 4, and information for identifying the device type of the field device 4 is read from the field device 4 connected online. However, the device type of the desired field device 4 may be read in offline (no connection destination device) work.

  In the case of offline work, information for identifying the device type of the desired field device (operation target device) 4 is obtained from offline definition data of a separately defined device. In the case of offline work, the mobile device setting tool 5 displays an offline definition data setting screen for the operation target device.

  In the first and second embodiments, the revisions of the device definition file are compared. However, not only the revision but also the version may be compared. “Revision” means “correction” and “revision”, and the revision number is changed when a defect is corrected without changing the function. “Version” means “version”, and the number is different when the software functions are different (addition or change of functions). In the first and second embodiments, the device revision corresponds to “version”, the DD revision and CF revision correspond to “revision”, and “revision” and “version” are not distinguished. When applying to a protocol that distinguishes “version”, it is possible to compare not only the revision but also the version.

[Extension of the embodiment]
The present invention has been described above with reference to the embodiment, but the present invention is not limited to the above embodiment. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the technical idea of the present invention.

  The present invention can be used as a device information management system that manages a device definition file used when accessing information in a field device such as a positioner.

  DESCRIPTION OF SYMBOLS 1 ... Device management system (device definition file server), DB1 ... Server side device definition file DB, 4 (4-1 to 4-4) ... Field device, 5 ... Portable device setting tool, DB2 ... Tool side device definition file DB DESCRIPTION OF SYMBOLS 11 ... Server side device definition file storage part 12 ... Tool side information receiving part 13 ... Server side optimal device definition file specification part 14 ... Optimal device definition file comparison part 15 ... Server side information transmission part 51 ... Tool Side device definition file storage unit 52... Device identification information reading unit 53... Tool side optimum device definition file specifying unit 54... Tool side information transmission unit 55. ... selection screen display unit, 100, 200 ... device information management system.

Claims (5)

A device information management system comprising: a mobile device setting tool that accesses information in the operation target device based on device definition information stored therein; and a server that transmits and receives information to and from the mobile device setting tool Because
The mobile device setting tool is:
Tool-side device definition information storage means for storing device definition information used for accessing information in the device for each type of the operation target device;
Device identification information reading means for reading information for identifying the operation target device;
Based on the information for identifying the operation target device read by the device identification information reading means, the optimum device corresponding to the operation target device from the device definition information stored in the tool side device definition information storage means Tool-side optimal device definition information specifying means for specifying definition information as optimal device definition information on the tool side,
Information for identifying the operation target device read by the device identification information reading means and tool-side optimum device definition information specified by the tool-side optimum device definition information specifying means as tool-side information to the server A tool side information transmitting means for transmitting,
The server
Server-side device definition information storage means for storing device definition information used for accessing information in the device for each type of the operation target device;
A tool-side information receiving unit that receives the tool-side information transmitted from the portable device setting tool;
Based on the information for identifying the operation target device included in the tool-side information received by the tool-side information receiving unit, the device definition information stored in the server-side device definition information storage means Server-side optimum device definition information identifying means for identifying optimum device definition information corresponding to the operation target device as server-side optimum device definition information;
Information indicating the server-side optimal device definition information specified by the server-side optimal device definition information specifying means, and information indicating the tool-side optimal device definition information included in the received tool-side information; An optimum device definition information comparison means for comparing
Based on the comparison result in the optimum device definition information comparison unit, when the optimum device definition information on the server side is more optimum device definition information than the optimum device definition information on the tool side, A server information management system comprising: server side information sending means for sending optimum device definition information as server side information to the portable device setting tool. In the device information management system according to claim 1,
The server side information transmission means includes:
When the optimal device definition information on the tool side is more optimal device definition information than the optimal device definition information on the server side, information notifying that is sent to the portable device setting tool as server side information A device information management system. In the device information management system according to claim 1,
The server side information transmission means includes:
When the optimal device definition information on the server side and the optimal device definition information on the tool side are the same, no information is transmitted to the portable device setting tool. In the device information management system according to claim 1,
The server side information transmission means includes:
When there is no optimum device definition information on the tool side to be compared with the optimum device definition information on the server side, the optimum device definition information on the server side is sent as information on the server side to the portable device setting tool. A device information management system. In the device information management system according to claim 2,
The mobile device setting tool is:
When information notifying that the optimum device definition information on the tool side is more optimal device definition information than the optimum device definition information on the server side is sent as the server side information, the optimum device on the tool side A device information management system comprising means for prompting selection of whether to use definition information or to use optimal device definition information on the server side.