JP3709984B2 - Fieldbus system construction equipment - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a fieldbus system construction device that supports engineering work for constructing a fieldbus system.
[0002]
[Prior art]
Many distributed control systems have been used for plant control. The distributed control system has a configuration in which an operation monitoring station and a control station are connected to a communication bus, the control stations are distributed in the plant, and the plant is controlled by the control station under the monitoring of the operation monitoring station. Recently, plant control using a field bus has also been performed. In plant control using a field bus, a field bus is laid in the plant, a field device is connected to the field bus, and the field device performs control of the plant while communicating with each other. In plant control using a fieldbus, it is possible to give intelligence to devices arranged in the field and distribute the control function to the field.
A fieldbus engineering tool (hereinafter abbreviated as a tool) is a means for constructing a fieldbus system by combining field devices.
[0003]
FIG. 5 is a diagram showing a configuration example of a distributed control system and tools. In FIG. 5, the operation monitoring station HIS and a personal computer (personal computer) PC are connected to a communication bus 1. A tool 3 is provided on the personal computer PC. The control station FCS is connected to communication buses 1 and 2. The interface device 4 is connected to the bus 2, and the field bus 5 is connected to the interface device 4. The field devices 61 to 6n are connected to the field bus 5. The field devices 61 to 6n are equipped with a control function, and a sensor is illustrated in the figure.
[0004]
Tool 3 performs engineering work for the fieldbus system 7.
In engineering work, a fieldbus system is constructed by logically combining field devices in a personal computer PC. At this time, a file describing information on the field device is created, or a file describing how to connect the field device is created. Based on the fieldbus system logically constructed by the tool 3, a physical fieldbus system is constructed by combining physical field devices.
[0005]
The tool is provided with an apparatus for constructing a fieldbus system that supports engineering work for constructing a fieldbus system.
FIG. 6 is a diagram showing a configuration example of a conventional fieldbus system construction apparatus.
In FIG. 6, a capability file 12 and a DD file 13 are attached to the field device 11 according to the fieldbus specification. The capability file 12 is a file in which resource information such as the capability of a device (device is a field device) is described. The DD file 13 is a file describing parameter list information, parameter attributes, and the like of blocks using the device. These files are digitized.
[0006]
The field device capability file 12 and the DD file 13 used in the fieldbus system are stored in the engineering unit 20. In the example shown in the figure, a device information file X 1 composed of a capability file 12 and a DD file 13 is imported into the file storage unit 21. The engineering unit 20 creates a device information file for the field device a1 using the stored device information file X1 as an original file. Similarly, a device information file of the field device a2 is created using the device information file X2 as an original file. Field devices a1 and a2 are registered logical devices. The device information files X1 and X2 are associated with the field devices a1 and a2. The logical field devices a1 and a2 correspond to the physical field devices 61 and 62. These relationships are described in the device information file. The device information files X1 and X2 created by the engineering unit 20 are sent to the physical field devices 61 and 62. As a result, the engineering data is reflected in the physical field device.
The database 30 stores device information files and the like.
[0007]
Capability files and DD files are frequently reviewed (revised), and in order to reflect the contents in engineering data, it is necessary to logically delete the device and then re-register it. Deletion here means deleting the registration of the device. The reason why the device is deleted when updating the file is that the device information file and the device are strongly linked, and the device information file cannot be updated until the device is deleted and the association is released.
[0008]
Also, in actual operation, replacement of physical equipment is performed at the time of failure and periodic repair, and at this time, equipment revup (version up) is often performed at the same time. When the revision of the device is changed, generally the capability file and the DD file are also changed. It is necessary to use a capability file or a DD file according to the revision of the device in addition to the replacement of the physical device in the device rev-up. In this case, the device is deleted and added.
In order to delete a device, when a block of the device is used in an application (control loop configuration), it is necessary to delete the block. In this case, the application must be rebuilt after the device is added.
[0009]
However, the conventional example of FIG. 6 has the following problems.
(A) When updating a file, record user-configured device information (tag name, address, device class, etc.) and block information (tag name, parameter value, etc.), and reset manually after adding the device Must.
[0010]
(B) In the fieldbus engineering tool, when a control loop is configured using a block of the target device, the block must be once deleted from the control loop configuration. Originally, the device configuration (segmentation) and the control loop configuration (application) must be able to be performed independently, but the application must be changed when the device is replaced or when the capability file or DD file is updated.
[0011]
(C) When updating a capability file or DD file, delete the block using the device, delete the device, import the device information file (capability file and DD file), add the device, block The user had to do the work of registering. For this reason, the update work is troublesome.
[0012]
[Problems to be solved by the invention]
The present invention has been made to solve the above-described problems. When the device information file is updated, it is not necessary to change the control loop configuration, and the device information and block information set by the user are reset. An object of the present invention is to realize a fieldbus system construction apparatus that is not necessary and can be easily updated.
[0013]
[Means for Solving the Problems]
The present invention is an apparatus for constructing a fieldbus system having the following configuration.
[0014]
(1) In a fieldbus system construction device that supports engineering work for constructing a fieldbus system,
A registration means for registering devices for constructing the fieldbus system;
A deletion means for deleting registration of a predetermined device from registered devices;
Saving means for saving user setting information about the deleted device in a predetermined storage area;
Adding an alternative device of the deleted device to the registration means, and an adding means for causing the alternative device to inherit the saved user setting information;
An apparatus for constructing a fieldbus system, comprising:
[0015]
(2) device selection means for selecting a device to be updated from registered devices;
A file selection means for selecting a new device information file;
A file updating means for deleting the device information file related to the device to be updated and updating the device information file related to the new device;
(1) The fieldbus system construction device according to (1).
[0016]
(3) The fieldbus system construction device according to (1), wherein the user setting information is at least one of a device tag name, a node address, a device class, and a device ID.
[0017]
(4) In a fieldbus system construction device that supports engineering work for constructing a fieldbus system,
A registration means for registering devices for constructing the fieldbus system;
A deletion means for deleting registration of a predetermined device from registered devices;
An application file that describes the information of the blocks that make up the control loop;
A segmentation file with information about the device configuration,
When using a block using the device deleted by the deleting means in the control loop, the setting means to make the block an invalid block recognized as a block disconnected from the physical device,
When a replacement device for the deleted device is registered, release means for releasing the invalid block state,
An apparatus for constructing a fieldbus system, comprising:
[0018]
(5) The registration means registers a function block provided in the field device,
The setting means makes the registered function block an invalid block when a function block associated with the registered function block and contained in the physical field device is deleted (4) ) Fieldbus system construction device described.
[0019]
(6) The registration means registers a function block provided in the field device,
The setting means makes the registered function block an invalid block when the block index or view index of the function block connected to the registered function block and included in the physical field device is changed. (4) The fieldbus system construction device according to (4).
[0020]
(7) The function block of the distributed control system and the function block of the field device are connected, and these function blocks are registered in the registration means,
The field bus according to (4), wherein the setting unit sets the registered function block of the field device as an invalid block when the block parameter of the function block of the connected field device is deleted. System construction device.
[0021]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, the present invention will be described in detail with reference to the drawings.
FIG. 1 is a block diagram showing an embodiment of the present invention. In FIG. 1, the same reference numerals are assigned to the same parts as those in the previous figure.
In FIG. 1, the engineering unit 40 imports device information files X1, X2, etc. of various devices used in the fieldbus system, and logically constructs a fieldbus system using the imported file. Based on the logically constructed fieldbus system, the worker constructs a physical fieldbus system. At this time, the information created for the logical fieldbus system is reflected in the physical fieldbus system. For example, device information files A1, A2 of individual field devices created based on the device information files X1, X2 are sent to the field devices 61, 62.
An FBAP (Function Block Application Processes) configuration file 71 describes a control loop configuration. In the inherited data file 72, information inherited when updating the capability file and the DD file is temporarily saved.
[0022]
FIG. 2 is a diagram showing a specific configuration example of the engineering unit of the present invention.
In FIG. 2, the registration means 41 logically registers the devices that construct the fieldbus system.
The deletion unit 42 deletes registration of a predetermined device from the registered devices. For example, deletion is performed when a capability file or a DD file is updated.
The saving unit 43 temporarily saves the user setting information about the deleted device in the inherited data file 72.
The adding unit 44 adds the replacement device of the deleted device to the registration unit 41 and causes the replacement device to inherit the user setting information saved in the inheritance data file 72. The user setting information is device information or block information set by the user, for example, a device tag name, a node address, a device class, a device ID, or the like.
[0023]
The device selection unit 45 selects a device to be updated from the devices registered in the registration unit 41.
The file selection means 46 selects a new device information file.
The file update unit 47 supports the operation of deleting the device information file related to the device to be updated and updating it to a device information file related to a new device.
[0024]
When the block using the device deleted by the deleting unit 42 is used in the control loop, the setting unit 48 sets the block as an “invalid block”. The “invalid block” is a block that is recognized as a block that is disconnected from the physical device.
When the replacement device of the deleted device is registered, the canceling unit 49 cancels the invalid block state when the replacement device can be assigned to the invalid block.
[0025]
In the application file 31, information on blocks constituting the control loop is described.
In the segmentation file 32, information related to the device configuration is described.
[0026]
The operation of the apparatus shown in FIGS. 1 and 2 will be described.
FIG. 3 is a flowchart showing a file update procedure. The operation will be described according to the processing procedure of the flowchart.
[0027]
(S1) Capability file selection Capability file or DD file update or device revision up is started by selecting a capability file to be updated. The DD file is automatically selected from the selected capability files.
The user only has to select the device to be updated and select the capability file to be updated. In the fieldbus engineering tool, a capability file to be updated is imported in advance.
The processes after S2 are internal processes of the fieldbus system construction apparatus.
[0028]
(S2) Saving inherited data The device information and block information set by the user are saved in the inherited data file 72. The construction apparatus saves engineering information (communication system parameter information and scheduling information) other than the device revision change and option change.
[0029]
(S3) Device deletion The device logically registered in engineering is deleted. At this time, if the application uses a block of the device to be deleted, the block becomes an “invalid block” and is recognized as a block that is no longer connected to the physical device.
An “invalid block” is a block that is recognized as a logical block that has been unlinked from the block of the physical device.
Invalid blocks are resolved after device registration.
[0030]
(S4) Device addition A device corresponding to the selected capability file is newly registered. Devices are registered based on the device information saved at this time. A device tag name, a node address, a device class, a device ID, and the like are set.
Other than device revision changes and option changes, even new registrations are considered as device modification work.
[0031]
(S5) Inheritance data overwrite All the saved data is overwritten and saved. The fieldbus engineering tool overwrites and saves engineering information (communication system parameter information and scheduling information) other than device revision changes and option changes.
[0032]
(S6) FBAP configuration (application) Restoration is performed for a new device block based on application information (FBAP configuration information) before restoration update. As long as the blocks used before the update are not deleted, the application is completely restored. When a block that has been used is deleted by updating, it remains an invalid block.
When fully restored, no further generation is required. Subsequent downloads and uploads can be performed. However, when the device revision is changed, there is a possibility that the index information, communication capability, resource information, etc. inside the device may have been changed, so regeneration is necessary.
[0033]
The invalid block will be described.
FIG. 4 is a diagram showing a configuration example of the control loop.
In FIG. 4, a control loop is configured by the blocks B1, B2, and B3. This is a logically constructed control loop. Here, if the registration of the device used for the block B1 is deleted, the block B1 becomes an invalid block. Block B1 is recognized as a block that is no longer connected to the physical device. When an alternative device for the deleted device is registered, the invalid block is released. The fieldbus system construction device does not continue the engineering work when an invalid block exists in the control loop.
[0034]
Deletion of invalid blocks will be described.
In the FBAP configuration file, information “which block of which device is used” is described. The block tag name is further described for the block. First, the tag name is restored to the block corresponding to the updated device. The block is specified based on the block ID.
The specific method is as follows.
The type of block can be known from the capability file. The capability file describes what block is implemented. The block ID is a character string that combines a block type and a unique number. For example, “AI — 01” is the first of the AI blocks.
When there are two AI blocks, they are 01, 02,... In order from the top. To specify, first check that the block types match, and then assign them in order from the top. Since it is based on the stored block information, nothing is done when there are more blocks in the device after the update, and conversely, no assignment is made when there are fewer blocks. In this case, it becomes an “invalid block”.
When the block tag is set, the unique ID in the database is updated, and the resource on the database is linked with the updated resource. Thereafter, the process is executed with the unique ID. This will restore the block.
[0035]
Another embodiment of the present invention will be described.
Some distributed control systems include a fieldbus builder for constructing a fieldbus system and a control drawing builder. A fieldbus system is constructed using these builders. The fieldbus builder describes the device configuration. The control drawing builder describes which blocks are combined and how to form a control loop. The fieldbus builder and the control drawing builder are mounted on, for example, the operation monitoring station HIS in FIG.
A function block is a unit that realizes a control function. Examples of the function block include a PID calculation (proportional, integral, differential calculation) block, a block for performing addition, a block for inputting an analog signal, a block for outputting an analog signal, and the like.
[0036]
There is an apparatus for constructing a fieldbus system used as a fieldbus builder. In this fieldbus system construction device, the registration means 41 in FIG. 2 registers devices as in the fieldbus engineering tool, but also registers blocks as resources. The setting unit 48 in FIG. 2 sets the function block registered in the following case as an invalid block, for example.
(A) When a function block associated with a logical function block registered in the registration means 41 and included in a physical field device is deleted, the registered function block is set as an invalid block.
(B) When a block index or a view index of a function block connected to a logical function block registered in the registration unit 41 and included in a physical field device is changed, the registered function block is invalidated Let it be a block.
[0037]
In some cases, the function block of the distributed control system and the function block of the field device are connected, and these function blocks are registered in the registration means 41.
In this case, in the fieldbus system construction apparatus, the setting means 48 in FIG. 2 sets the registered function block of the field device as an invalid block when the block parameter of the function block of the connected field device is deleted. .
[0038]
【The invention's effect】
According to the present invention, the following effects can be obtained.
[0039]
In the first and third aspects of the invention, when a logically registered device is deleted, user setting information about the device to be deleted is temporarily saved in the storage area, and an alternative device is added. The saved user setting information is inherited by the alternative device. This eliminates the need to reset the user setting information after adding the device.
[0040]
According to the second aspect of the present invention, the device information file is automatically updated only by selecting the device to be updated and selecting a new device information file. This facilitates the update work.
[0041]
In the invention according to claim 4, when the block using the deleted device is used in the control loop, the block is set to an invalid block, so that the device information file can be updated without changing the control loop configuration. .
[0042]
According to the fifth and sixth aspects of the present invention, when a function block included in the physical field device is deleted or the index is changed, the registered function block is made an invalid block. For this reason, the function block can be deleted or the index can be changed without changing the control loop configuration constructed by the function block.
[0043]
In the invention described in claim 7, when the block parameter of the function block of the field device connected to the function block of the distributed control system is deleted, the registered function block of the field device is set as an invalid block. For this reason, the parameters of the function block can be changed without changing the control loop configuration constructed by the function block of the distributed control system and the function block of the field device.
[Brief description of the drawings]
FIG. 1 is a configuration diagram showing an embodiment of the present invention.
FIG. 2 is a configuration diagram of a main part of the present invention.
FIG. 3 is an operation explanatory diagram of the present invention.
FIG. 4 is an operation explanatory diagram of the present invention.
FIG. 5 is a diagram illustrating a configuration example of a distributed control system and a tool.
FIG. 6 is a diagram showing a configuration example of a conventional fieldbus system construction device.
[Explanation of symbols]
12 Capability file 13 DD file 31 Application file 32 Segmentation file 41 Registration means 42 Deletion means 43 Saving means 44 Addition means 45 Device selection means 46 File selection means 47 File update means 48 Setting means 49 Release means 71 FBAP file 72 Inherited data file

Claims (7)

In a fieldbus system construction device that supports engineering work to construct a fieldbus system,
A registration means for registering devices for constructing the fieldbus system;
A deletion means for deleting registration of a predetermined device from registered devices;
Saving means for saving user setting information about the deleted device in a predetermined storage area;
Adding an alternative device of the deleted device to the registration means, and an adding means for causing the alternative device to inherit the saved user setting information;
An apparatus for constructing a fieldbus system, comprising: A device selection means for selecting a device to be updated from the registered devices;
A file selection means for selecting a new device information file;
A file updating means for deleting the device information file related to the device to be updated and updating the device information file related to the new device;
The apparatus for constructing a fieldbus system according to claim 1, comprising: 2. The fieldbus system construction apparatus according to claim 1, wherein the user setting information is at least one of a device tag name, a node address, a device class, and a device ID. In a fieldbus system construction device that supports engineering work to construct a fieldbus system,
A registration means for registering devices for constructing the fieldbus system;
A deletion means for deleting registration of a predetermined device from registered devices;
An application file that describes the information of the blocks that make up the control loop;
A segmentation file with information about the device configuration,
When using a block using the device deleted by the deleting means in the control loop, the setting means to make the block an invalid block recognized as a block disconnected from the physical device,
When a replacement device for the deleted device is registered, release means for releasing the invalid block state,
An apparatus for constructing a fieldbus system, comprising: The registration means registers function blocks provided in the field device,
The setting means, when a function block connected to a registered function block and contained in a physical field device is deleted, makes the registered function block an invalid block. 4. The fieldbus system construction apparatus according to 4. The registration means registers function blocks provided in the field device,
The setting means makes the registered function block an invalid block when the block index or view index of the function block connected to the registered function block and included in the physical field device is changed. The apparatus for constructing a fieldbus system according to claim 4. The function block of the distributed control system and the function block of the field device are connected, and these function blocks are registered in the registration means,
5. The fieldbus according to claim 4, wherein when the block parameter of the function block of the connected field device is deleted, the setting means sets the registered function block of the field device as an invalid block. System construction device.

Images