JP2003124937A - Field bus system builder - Google Patents

Abstract

PROBLEM TO BE SOLVED: To realize a builder for building a field bus system which is easy about the update work without needing the change of the control loop constitution and also the re-setting of apparatus information and block information set by a user, when updating apparatus information files. SOLUTION: The field bus system builder for supporting engineering works for building a field bus system previously registers an apparatus for which the field bus system is to be built. When the registered apparatus is deleted, the builder first transfers information set by user about the deleted apparatus to specified memory areas. When a substitute apparatus for the deleted apparatus is added to registration, it has the substitute apparatus inherit the transferred information set by a user.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a fieldbus system construction apparatus that supports engineering work for constructing a fieldbus system.

[0002]

2. Description of the Related Art A distributed control system is often used for controlling plants. 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 distributedly arranged 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 fieldbus, a fieldbus is installed in the plant, field devices are connected to this fieldbus, and the field devices communicate with each other to control the plant. In plant control using a field bus, it is possible to give intelligence to devices arranged in the field and distribute control functions to the field. A fieldbus engineering tool (hereinafter abbreviated as tool) is a means for constructing a fieldbus system by combining field devices.

FIG. 5 is a diagram showing a configuration example of a distributed control system and tools. In FIG. 5, the operation monitoring station H
The IS and the personal computer (personal computer) PC are connected to the bus 1 for communication. Tool 3 on PC
Is provided. The control station FCS is connected to buses 1 and 2 for communication. The interface device 4 is connected to the bus 2 and the field bus 5 is connected to the interface device 4. Field equipment 61-6n
Is connected to the fieldbus 5. The field devices 61 to 6n are equipped with a control function, and sensors are illustrated in the figure.

The tool 3 carries out engineering work of the fieldbus system 7. In the engineering work, a field bus system is constructed by logically combining field devices in a personal computer PC. At this time,
Create a file that describes information about field devices or a file that describes how to connect field devices. A physical fieldbus system is constructed by combining physical field devices based on the fieldbus system logically constructed by the tool 3.

The tool is provided with a fieldbus system construction device that supports engineering work for constructing the 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 specifications. The capability file 12 is a file in which resource information such as capabilities of a device (device is a field device) is described. The DD file 13 is a file in which list information of parameters of blocks using devices, parameter attributes, and the like are described.
These files are computerized.

The capability file 12 and the DD file 1 of the field device used in the fieldbus system
3 is stored in the engineering unit 20. In the illustrated example, the device information file X1 including the capability file 12 and the DD file 13 is imported into the file storage unit 21. The engineering unit 20 creates a device information file of 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 device a
1 and a2 are registered logical devices. The device information files X1 and X2 and the field devices a1 and a2 are linked. 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, engineering data is reflected in the physical field device. The database 30 stores device information files and the like.

The capability file and the DD file are frequently updated (revised), and in order to reflect the contents in the engineering data, it is necessary to logically delete the device and then re-register it. . The deletion here means deleting the registration of the device. The reason why the device is deleted when the file is updated is that the device information file and the device are strongly associated with each other, and the device information file cannot be updated until the device is deleted and the association is released.

Also, in actual operation, replacement of physical equipment is carried out at the time of failure and periodical repair, and at this time, equipment is often renewed (version up) at the same time. When the revision of the device is changed, generally the capability file and the DD file are also changed. When revising a device, it is necessary not only to replace the physical device but also to use a capability file or a DD file according to the revision of the device. In this case as well, the device will be deleted and added. In order to delete a device, if a block included in the device is used in an application (control loop configuration), the block needs to be deleted. In this case, the application must be rebuilt after adding the device.

However, the conventional example of FIG. 6 has the following problems. (A) When updating the file, record the device information (tag name, address, device class, etc.) set by the user and block information (tag name, parameter value, etc.), and manually reconfigure after adding the device. Must.

(B) In the fieldbus engineering tool, when the control loop is configured by using the block of the target device, the block must be deleted from the control loop configuration once. Originally, the device configuration (segmentation) and the control loop configuration (application) must be implemented independently, but the application must be changed when the device is replaced or when the capability file or the DD file is updated.

(C) When updating the capability file or the DD file, the block using the device is deleted, the device is deleted, the device information file (capability file and DD file) is imported, and the device is added. However, the user had to register the block. Therefore, the update work is troublesome.

[0012]

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems, and when updating the device information file, it is not necessary to change the control loop configuration and the user sets it. It is an object of the present invention to realize a fieldbus system construction apparatus that does not require resetting of device information and block information and is easy to update.

[0013]

The present invention is an apparatus for constructing a fieldbus system having the following configuration.

(1) In a fieldbus system construction apparatus that supports an engineering work for constructing a fieldbus system, a registration means for registering a device for constructing the fieldbus system, and a predetermined device among the registered devices. Deletion means for deleting the registration, saving means for saving the user setting information about the deleted device in a predetermined storage area, and adding an alternative device of the deleted device to the registration means, and saving the saved information. An apparatus for constructing a fieldbus system, comprising: an addition unit that causes the alternative device to inherit the stored user setting information.

(2) A device selecting means for selecting a device to be updated from the registered devices, a file selecting means for selecting a new device information file, and a device information file relating to the device to be updated are deleted, and a new device information file is deleted. A field bus system construction apparatus according to (1), further comprising: a file updating unit that updates a device information file relating to the device.

(3) The fieldbus system construction apparatus 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.

(4) In a fieldbus system construction apparatus that supports engineering work for constructing a fieldbus system, a registration means for registering a device for constructing the fieldbus system, and a predetermined device among the registered devices. Delete means for deleting the registration, an application file that describes the information of the blocks that make up the control loop, a segmentation file that describes the information about the device configuration, and a block that uses the device deleted by the delete means in the control loop. Setting block, the setting means for setting the block as an invalid block recognized as a block disconnected from the physical device, and the invalid block state is released when a substitute device of the deleted device is registered. And a releasing means. Arm of the construction apparatus.

(5) The registration means registers the function block provided in the field device, and the setting means associates the registered function block with the function block in the physical field device. When deleted, the registered function block is set as an invalid block, and the fieldbus system construction apparatus according to (4) is described.

(6) The registration means registers the function block provided in the field device, and the setting means is associated with the registered function block and is the function block of the physical field device. The fieldbus system construction device according to (4), characterized in that the registered function block is set as an invalid block when the block index or the view index is changed.

(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, and the setting means is connected to the connected field device. The field bus system construction apparatus according to (4), wherein when the block parameter of the function block is deleted, the registered function block of the field device is set as an invalid block.

[0021]

DETAILED DESCRIPTION OF THE INVENTION The present invention will be described in detail below with reference to the drawings. FIG. 1 is a block diagram showing an embodiment of the present invention. In FIG. 1, the same parts as those in the previous figure are designated by the same reference numerals.
In FIG. 1, the engineering unit 40 includes device information files X1 and X2 of various devices used in the fieldbus system.
Etc. are imported and the fieldbus system is logically constructed using the imported file. An operator builds a physical fieldbus system based on the logically built fieldbus system. At this time, the information created about the logical fieldbus system is reflected in the physical fieldbus system. For example, the device information files A1 and A2 of the individual field devices created based on the device information files X1 and X2 are sent to the field devices 61 and 62. FBAP (Function Block App
(lication Processes) configuration file 71 describes the control loop configuration. In the inheritance data file 72, information to be inherited when updating the capability file and the DD file is temporarily saved.

FIG. 2 is a view showing a concrete example of the construction of the engineering section of the present invention. In FIG. 2, the registration means 41 logically registers the devices that make up the fieldbus system. The deleting unit 42 deletes the registration of a predetermined device from the registered devices. For example, it is deleted when updating the capability file or the DD file. Evacuation means 4
3 temporarily saves the user setting information about the deleted device in the inheritance data file 72. Additional means 44
Adds the alternative device of the deleted device to the registration means 41 and causes the alternative device to inherit the user setting information saved in the inheritance data file 72. The user setting information is device information and block information set by the user,
For example, a device tag name, a node address, a device class, a device ID, etc.

The device selection means 45 selects the device to be updated from the devices registered in the registration means 41. The file selection means 46 selects a new device information file.
The file updating means 47 supports the work of deleting the device information file relating to the device to be updated and updating it to the device information file relating to the new device.

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 to "invalid block". The “invalid block” is a block recognized as a block that is disconnected from the physical device. The canceling unit 49 cancels the invalid block state when the alternative device of the deleted device is registered and the alternative device is assigned to the invalid block.

The application file 31 describes information on blocks that form a control loop. The segmentation file 32 describes information about the device configuration.

The operation of the apparatus shown in FIGS. 1 and 2 will be described. FIG. 3 is a flowchart showing a file updating procedure. The operation will be described according to the processing procedure of the flowchart.

(S1) Capability File Selection Updating of a capability file or DD file or revision of a device is started by selecting a capability file to be updated. The DD file is automatically selected from the selected capabilities file. The user's work is only to select the update target device and to select the capability file to be updated. In the fieldbus engineering tool, the capability file to be updated is imported in advance. The process after S2 is an internal process of the fieldbus system construction apparatus.

(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 equipment revision and option changes.

(S3) Device deletion The device logically registered in engineering is deleted. At this time, if the block used by the device to be deleted is used by the application, the block becomes an “invalid block” and is recognized as a block that is no longer connected to the physical device. The “invalid block” is a block recognized as a logical block that is disconnected from the block of the physical device. Invalid blocks are resolved after device registration.

(S4) Device addition A device corresponding to the selected capability file is newly registered. At this time, the device is registered based on the device information saved. A device tag name, a node address, a device class, a device ID, etc. are set. Except for changes in device revisions and changes in options, even new registrations are considered to be device modification work.

(S5) Overwriting of inherited data All saved data are overwritten and saved. The Fieldbus Engineering Tool overwrites and saves engineering information (communication system parameter information and scheduling information) as well as device revisions and option changes.

(S6) FBAP configuration (application) restoration Based on the application information before update (FBAP configuration information), reassignment is performed for a block of a new device. The application is completely restored unless the blocks used before the update are deleted. When the used block is deleted by the update, it remains an invalid block. If it is completely restored, no further generation is needed. Subsequent downloads and uploads are possible. However, if the device revision is changed, the index information, communication capability, resource information, etc. inside the device may have been changed, so regeneration is necessary.

The invalid block will be described. FIG. 4 is a diagram showing a configuration example of the control loop. In FIG. 4, blocks B1, B2 and B3 form a control loop. 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. The block B1 is recognized as a block that is no longer connected to the physical device. When the alternative device of the deleted device is registered, the invalid block is released. Fieldbus system builders do not continue their engineering work when there are invalid blocks in the control loop.

The cancellation of invalid blocks will be described. F
The BAP configuration file describes information "which block of which device is being used". The block tag name is further described for the block. First, the tag name is restored in 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 found in the capabilities file. The capabilities file describes what blocks are implemented. Block ID
Is a string that combines the block type and a unique number. For example, "AI_01" is the first thing in the AI block. When there are two AI blocks, the numbers are 01, 02 ... For identification, first confirm that the block types match, then assign them in order from the top. Since it is based on the stored block information, if the updated device has more blocks, nothing is done, and conversely, if there are fewer blocks, no allocation is made. In this case, it becomes an "invalid block". When the block tag is set, the unique ID in the database is updated and the updated resource is linked to the database. Unique afterwards
The process is executed by ID. The block is now restored.

Another embodiment of the present invention will be described. Some distributed control systems include a fieldbus builder that builds a fieldbus system and a control drawing builder. A fieldbus system is built using these builders. The fieldbus builder describes the device configuration. The Control Drawing Builder describes how and which blocks are combined to form a control loop. The fieldbus builder and the control drawing builder are, for example, the operation monitoring station HIS shown in FIG.
To be installed. A function block is a unit that realizes a control function. Examples of the function block include a PID calculation (proportional, integral, and differential calculation) block, a block that performs addition, a block that inputs an analog signal, and a block that outputs an analog signal.

There is a fieldbus system construction device used as a fieldbus builder. In this fieldbus system construction apparatus, the registration means 41 shown in FIG.
Is a fieldbus engineering tool,
The device is registered, but the block as a resource is also registered. The setting means 48 of FIG. 2 sets the function block registered in the following cases as an invalid block, for example. (A) When the function block associated with the logical function block registered in the registration means 41 and contained in the physical field device is deleted, the registered function block is set as an invalid block. (B) When the block index or view index of the function block connected to the logical function block registered in the registration means 41 and included in the physical field device is changed, the registered function block is invalidated. Make it a block.

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 of 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]

According to the present invention, the following effects can be obtained.

According to the first and third aspects of the present invention, when the logically registered device is deleted, the user setting information about the device to be deleted is temporarily saved in the storage area, and the alternative device is added. Then, the saved user setting information is inherited by the alternative device. Therefore, it is not necessary to reset the user setting information after adding the device.

According to the second aspect of the invention, the device information file is automatically updated only by selecting the device to be updated and selecting a new device information file. by this,
Update work becomes easy.

According to the fourth aspect of the present invention, when the block using the deleted device is used in the control loop, the block is made an invalid block, so the device information file is not changed without changing the control loop configuration. Can be updated.

According to the fifth and sixth aspects of the invention, when the function block contained in the physical field device is deleted or the index is changed, the registered function block is made an invalid block. . Therefore, the function block can be deleted or the index can be changed without changing the control loop configuration constructed by the function block.

According to the seventh aspect of the invention, 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 function block of the registered field device is treated as an invalid block. There is. Therefore, 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 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 explanatory diagram of the operation of the present invention.

FIG. 5 is a diagram showing a configuration example of a distributed control system and tools.

FIG. 6 is a diagram showing a configuration example of a conventional fieldbus system construction device.

[Explanation of symbols]

12 Capability file 13 DD files 31 Application file 32 segmentation files 41 Registration means 42 Deletion means 43 Evacuation means 44 Additional means 45 Device selection means 46 File selection means 47 File updating means 48 setting means 49 Release means 71 FBAP file 72 inherited data file

Claims (7)

[Claims] 1. In a fieldbus system construction apparatus for supporting an engineering work for constructing a fieldbus system, a registration means for registering a device for constructing the fieldbus system, and a registration of a predetermined device from the registered devices. Deleting means for deleting the deleted device, a saving means for saving the user setting information about the deleted device in a predetermined storage area, and an alternative device for the deleted device added to the registering device and An apparatus for constructing a fieldbus system, comprising: an addition unit that causes the alternative device to inherit the saved user setting information. 2. A device selecting means for selecting a device to be updated from registered devices, a file selecting means for selecting a new device information file, and a device information file relating to the device to be updated, thereby deleting the new device. 2. A fieldbus system construction apparatus according to claim 1, further comprising a file updating unit for updating the device information file regarding the fieldbus system. 3. 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. 4. A fieldbus system construction apparatus for supporting an engineering work for constructing a fieldbus system, wherein a registration means for registering a machine constructing the fieldbus system and a registration of a predetermined machine from the registered machines. The deletion means that deletes the control loop, the application file that describes the information of the blocks that make up the control loop, the segmentation file that describes the information about the equipment configuration, and the block that uses the equipment deleted by the deletion means are used in the control loop. , The setting means that makes the block an invalid block that is recognized as a block that is disconnected from the physical device, and cancels the invalid block state when a substitute device of the deleted device is registered. And a fieldbus system including: Construction equipment. 5. The registration means registers the function block provided in the field device, and the setting means deletes the function block associated with the registered function block and contained in the physical field device. The device for constructing a fieldbus system according to claim 4, wherein the registered function block is set as an invalid block in the case of being inactivated. 6. The registration unit registers a function block provided in a field device, and the setting unit is associated with the registered function block and is a block of the function block included in the physical field device. 5. The fieldbus system construction apparatus according to claim 4, wherein the registered function block is set as an invalid block when the index or the view index is changed. 7. A function block of a distributed control system and a function block of a field device are connected, and these function blocks are registered in the registration means, and the setting means is a function of the connected field device. 5. The fieldbus system construction device according to claim 4, wherein when the block parameter of the block is deleted, the registered function block of the field device is set as an invalid block.