CN102880146B - Profibus device monitoring and managing system - Google Patents

Abstract

The invention discloses a field bus device monitoring and management system, which includes a data acquisition module and a data processing module connected through Ethernet; the data acquisition module includes an OPC client and a historical record module, and the data processing module includes a field bus device type A file generation module, a fieldbus device configuration module and a fieldbus device monitoring and management module. The present invention uses the OPC protocol to separate the equipment management system from the DCS system, does not rely on the communication protocol of the equipment, and adopts the method of writing the equipment type file (ET) to realize the versatility of the equipment, and completes the configuration and adding equipment at one time. Industrial operation standards improve the feasibility and security of the system through the work contact list, and establish a document database to improve the speed and convenience of office work.

Description

A Fieldbus Equipment Monitoring and Management System

technical field

The invention belongs to the field bus device management technical field, and relates to a field bus device monitoring and management system.

Background technique

Since the 1980s, fieldbus has been widely used in industrial automation control due to its advantages of strong reliability, fast communication, wide compatibility and low cost. In addition, the highly automated, digitized, and intelligent production and life also promote the development of fieldbus control systems and fieldbus devices. At present, there are various types of device management systems and fieldbus devices that can meet the needs of various industries. However, most of the current equipment management systems also have some problems that cannot be ignored.

With the development of fieldbus, many companies have developed their own equipment management systems according to market requirements, and have received a large number of applications with good responses. Among them, there are two representative ones: SIMATIC PDM, a process device manager of Siemens, and AMS intelligent device management system of Emerson. These two device management systems represent the implementation methods of two device management systems, including the module composition and the information interaction between field devices and device management systems, which are different from each other. It is precisely because of their different mechanisms that the application objects of the two types of equipment management systems are also quite different.

1) Simatic PDM system

Simatic PDM is a device management system developed for the Profibus fieldbus system. The system is a universal tool for displaying, commissioning, diagnosing and maintaining field devices and automation components. One of its notable features is: integration, and its design purpose is to try to integrate field devices. In this system, integration is allowed through multiple methods; through the DD of the device manufacturer; through the protocol PROFIBUS PA-Profile V3.0; through the catalog of the HCF (HART Communication Foundation) to realize the integration of the device.

The management work of the PDM equipment management system is mainly realized through the equipment itself. Functions such as parameterization, diagnosis, and optimization of the device are realized in the form of function blocks in the device, and information such as communication parameters, device parameters, parameter structure, and device actions of the device are provided to the system integration user of the device through the EDD file . PDM has a top-heavy system structure. It has high requirements on equipment manufacturers, and requires equipment manufacturers to take into account maintenance, optimization and other management tasks of equipment when producing equipment, and implement them in the equipment in the form of function blocks.

The method theory of device integration at the user layer by using EDD files has no requirement on which fieldbus protocol the device is based on, so the PDM system using this method theory is very widely used. But it is precisely because of this method theory that PDM has a strict requirement for equipment, that is, field equipment must provide EDD files. For field equipment that does not support EDD, this management system is not applicable; at the same time, because the equipment in this system The main work of management is realized in the equipment in the form of function blocks, which has high requirements for equipment manufacturers, so the functions that can be realized are relatively simple and limited, and the user of the equipment basically cannot add additional Management functions for field devices. Therefore, from the perspective of device management, its implementation of device management is very limited.

In addition to the high requirements for equipment manufacturers, which cannot be used universally with all equipment, PDM is mainly for equipment diagnosis and statistics, but for the specific industry of power plants, the field application management function is weak, and it cannot be used when equipment failures occur or equipment needs maintenance. Given corresponding maintenance guidance, repair or maintenance work tickets cannot be automatically generated, and equipment fault diagnosis cannot be integrated into the industrial process of the entire power plant industry. In addition, PDM does not fully save the historical data of the entire fieldbus device. Although PDM can generate alarm logs and save them in CSV format, when the computer where PDM is located fails and restarts, when PDM is restarted, the previous history Data will be lost.

2) AMS equipment management system

Emerson's AMS is a system combination, including AMS equipment information platform, AMS intelligent equipment management system, AMS mechanical equipment status management system, AMS performance detection system and AMS real-time optimization system. Through the comprehensive application of the above five systems, the functions of intelligent instrument valve equipment management, mechanical equipment performance monitoring, process equipment performance detection and system protection can be realized.

Among them, the AMS equipment management system starts from the perspective of system integration, modularizes the needs of users and further forms an independent management system and integrates it on an information platform. The advantage of this system is: the parameter information of all field devices are all reflected in a unified interface; when performing a certain function, the user can traverse all the field devices.

In addition, AMS integrates data collection and data analysis, so it needs to be "connected" to the equipment through the DCS system or direct connection. At present, AMS can only use the software, hardware and wiring of the DCS system of a few companies such as Emerson to communicate with the equipment. In most cases, it must be connected to the equipment at the same time through a multiplexer and the DCS system. This makes it more complicated to add devices, which seriously affects the scalability of the system.

Summarizing the above two commonly used equipment management systems, it can be seen that the current mainstream equipment management systems have the following defects:

1. High requirements for equipment. Most device management systems require that the device must be able to provide device information files such as EDD files for PDM and DD files for AMS. Therefore, when the system is running, the equipment must be able to generate and provide corresponding equipment information files, which will inevitably increase the requirements for the equipment. Once the equipment cannot provide information files, the management system will not be able to include the equipment into the management category, reducing the versatility .

2. Poor scalability. Most equipment management systems need to communicate with equipment, so hardware and software and wiring must be used to connect with equipment, which will inevitably increase the cost and complexity of the entire equipment management system, and will inevitably affect the original DCS system.

3. The coupling with the DCS system is too tight. The current equipment management systems are basically "embedded" in the DCS system, which can easily affect the operation of the DCS, and also increase the difficulty of installation and debugging of the management system. For some applications such as high-risk and high-emergency industries such as thermal power, the "embedding" of the equipment management system in the DCS system will more or less increase the security risks of the control system.

4. They are all "heavyweight" systems. The current equipment management systems are basically powerful and "powerful" in scale. The functions of many systems are duplicated with those of DCS, and there are many but not precise functions.

Contents of the invention

The problem to be solved by the present invention is to provide a monitoring and management system for field bus equipment. Computer real-time monitoring and management system for maintenance guidance and work tickets.

The present invention is achieved through the following technical solutions:

A fieldbus device monitoring and management system, including a data acquisition module and a data processing module connected via Ethernet;

Data acquisition module, including OPC client and historical record module;

The OPC client connected to the OPC server collects the diagnostic information of the fieldbus device, the OPC client sends the collected data to the data processing module through Ethernet, and the OPC client also sends the collected data to the history record module;

The historical record module keeps the collected data for a period of time, and saves the collected data to the historical data file regularly;

Data processing module, including fieldbus device type file generation module, fieldbus device configuration module, fieldbus device monitoring and management module, fieldbus device original data real-time database module and fieldbus device operation data real-time database module;

The fieldbus device type file generation module generates the corresponding device type file according to the type of fieldbus device and its use method. The device type file provides the format and algorithm for device configuration and device monitoring management. This file is generated when the system starts Fieldbus device configuration module loading;

The device type file includes the definition of the diagnostic information point mode required by the device type, and the definition of the diagnostic information state algorithm;

The fieldbus device configuration module generates the operation topology diagram reflecting the positional relationship and operation information of the fieldbus device, adds it to the corresponding position in the operation configuration diagram according to the station information of the fieldbus device, and loads it according to the system startup. The device type file associates its basic information, status information and diagnostic information with the fieldbus device;

The fieldbus device monitoring and management module receives the diagnostic data of the fieldbus device collected by the OPC client, and updates the diagnostic data value to the real-time database module of the original data of the fieldbus device in real time, and at the same time according to the fieldbus device type file and the fieldbus device type The algorithm corresponding to the file performs periodic calculations on the fieldbus diagnostic data, refreshes the information on the monitoring interface of the module in real time according to the calculation results, and updates and saves the calculation results in real time to the fieldbus device calculation data real-time database module;

The raw data real-time database module of the fieldbus equipment receives the raw information point data of the fieldbus equipment monitoring and management module, stores it in the corresponding position of the raw data real-time database, and periodically stores all the data in the raw data real-time database to the raw data history in the file;

The real-time database module of fieldbus device computing data receives the data calculated by the fieldbus device monitoring and management module, stores it in the corresponding position of the computing data real-time database, and periodically stores all the data in the computing data real-time database into the computing data history file .

It also includes a Web server module and a fieldbus device Web data request processing module;

The Web server module responds to the access request of the management system client browser, and sends a data request to the data processing module according to the access request;

The fieldbus device Web data request processing module receives the data request from the Web server module, reads the corresponding data from the fieldbus device computing data real-time database module according to the type of requested data, and writes the data into the corresponding format according to the request of the Web server module document;

The Web server module periodically reads the data file written by the fieldbus device Web data request processing module in real time according to the request, and sends the data information to the client browser of the management system.

Described OPC server is connected with DCS system;

The OPC client sends the collected data to the data processing module in a multicast manner, and a firewall is set between the OPC client and the data processing module.

The OPC server is provided with an OPC group, and the OPC group exports the fieldbus device diagnostic information points to be collected, and generates a diagnostic information point file based on them.

The device type file is to make a device type file for each device type according to the device types in the field engineering.

When the system is started, the system reads the diagnostic information point file information, and the raw data real-time database module of the fieldbus device creates and initializes the real-time database based on these information, and all diagnostic information points and related information are stored in the real-time database in a certain format.

When the system starts, the system reads the fieldbus device type file, and according to its information, creates the device type object and related information and calculation formulas, so that the information can be read when configuring the selected device type.

The field bus device configuration is to associate the device type object with the information points in the field bus device real-time database, add devices for the field bus control and monitoring system, and set the device type for the devices.

When the fieldbus device monitoring and management system is started, it creates and initializes a real-time database of computing data based on configuration information and device-related information points for updating and storing computing data and reading data from the Web data request processing module.

The data processing module also queries the current state or historical state of the device through the device name or KKS code.

Compared with the prior art, the present invention has the following beneficial technical effects:

The fieldbus device monitoring and management system and its method provided by the present invention use the OPC protocol to separate the device management system from the DCS system, do not rely on the communication protocol of the device, and use the method of writing the device type file (ET) to realize the common use of the device. The configuration and addition of equipment can be completed at one time. According to the industrial operation standard, the feasibility and safety of the system can be improved through the work contact list, and the document database can be established to improve the speed and convenience of office work.

Compared with the existing system, the present invention has the following technical characteristics:

1) Universal platform, suitable for a wide range of equipment. The present invention does not require the equipment to provide relevant information files, and the equipment type file (ET) can be written and loaded into the system according to the instructions and usage methods of the equipment, so that any fieldbus equipment can be incorporated into the present invention by writing the equipment type file monitoring range.

2) High scalability, easy installation. Since the present invention obtains equipment information point data from the existing DCS system through the OPC protocol, it will not involve the problem of wiring with equipment, and the installation is simple, convenient and fast, and will not change or affect the existing DCS system related wiring and structure.

3) Low coupling with DCS system and high security. The present invention is independent of the DCS system, has low coupling with the DCS system, can be used in conjunction with any DCS, and any operation of the present invention will not affect the normal operation of the DCS, so the safety is high.

4) "Lightweight" device management system. The present invention focuses on the monitoring of fieldbus equipment, does not add any other functions that affect the DCS system, does not overlap or conflict with other control systems in function, and monitors and manages the unit as a unit.

5) The work ticket mechanism is more in line with industrial production standards. The invention fully combines the daily operation rules and regulations of thermal power enterprises, and develops a set of work ticket processing mechanism that conforms to production specifications and is easy to operate. The work ticket mechanism ensures that any changes and operations to equipment and systems on site are documented, which not only ensures the safety of the work, but also allows the work to be reviewed and audited afterwards.

Description of drawings

Figure 1 is a network architecture diagram of the equipment management system.

Figure 2 is a flow chart of the entire data processing process.

Figure 3 is a flow chart of data refresh in each cycle.

Fig. 4 is a flow chart of work ticket generation.

Detailed ways

The present invention will be further described in detail below in conjunction with specific embodiments, which are explanations of the present invention rather than limitations.

Referring to Fig. 1, Fig. 2, a kind of field bus equipment monitoring and management system, comprises the data acquisition module and the data processing module connected by Ethernet; The field bus equipment monitoring and management system of this invention has included firewall, data acquisition module and data processing module.

Data acquisition module, including OPC client and historical record module, the OPC client connected with OPC server collects the diagnosis information of fieldbus equipment, OPC client also sends the collected data to the data processing module through Ethernet; historical record module Retain collected data over a period of time;

The specific OPC client connects to the OPC server of the control network through Ethernet, and then connects to the OPC server through the OPC client in the data acquisition module, creates an OPC group, and adds diagnostic information points of fieldbus devices to be collected in the OPC group ;

Through the export and import function, add the KKS code of the device to which each fieldbus device diagnosis point belongs, and the diagnosis information point of the communication master station does not need to add the KKS code;

Save the diagnostic information points added in the OPC client, generate diagnostic information point files (.osd files), and send diagnostic information point files (.osd files) to the data processing module and history record program to make them available in the control network fieldbus device diagnostic information.

After the specific OPC client collects the data, it uses multicast to send the data to the data processing module, and the data collection module will record the collected data for 8 hours at the same time.

Data processing module, including fieldbus device type file generation module, fieldbus device configuration module and fieldbus device monitoring and management module;

The fieldbus device type file generation module generates the device type file corresponding to the device according to the type of the fieldbus device and its use method. The device type file includes the diagnostic information points required by the device type, and the splitting and combination methods and operations of the diagnostic information points formula;

The split method and calculation formula of each fieldbus device diagnostic information are defined in the specific device type file; the generation process is as follows:

(1) Define the diagnostic information points required for the equipment type;

(2) According to the definition of fieldbus device diagnostic information, use the xml format to define the disassembly and splitting method of each diagnostic information point, and separate each bit in the fieldbus device diagnostic information point;

(3) According to the needs of on-site engineering, recombine and calculate each digit after splitting, and write the calculation formula in xml format;

(4) Use the fieldbus device type generation program to analyze the data definition in xml format, and finally generate the device type file.

The fieldbus device configuration module generates the operation configuration diagram reflecting the positional relationship and operation information of the fieldbus device, adds it to the corresponding position in the operation configuration diagram according to the station information of the fieldbus device, and at the same time adds its basic information , status information and diagnostic information are associated with fieldbus devices;

In this way, through fieldbus device configuration, combine the device type file (.et file) with the fieldbus device diagnosis point file (OPCData.osd file), that is, add devices for the fieldbus control and monitoring system, set the device type for the device, and According to the requirements of the installed device type, find the corresponding diagnostic information point from the fieldbus device diagnostic point file and associate it with the device.

The configuration described is as follows:

(1) Add the controller and communication master station according to the on-site engineering topology diagram, and add a new topology diagram in the communication master station in units of communication boxes;

(2) Draw a topology map using the primitives in the configuration tool;

(3) After adding the graphic element of the communication master station, set the controller name, communication station name, and address for the graphic element of the communication master station, and finally add diagnostic information points;

(4) Add the network segment graphics element under the communication master station, and set the name, address and KKS code for the network segment;

(5) Select the network segment graphic element, add the fieldbus device graphic element under it, and add the fieldbus device for the fieldbus device monitoring and management system at the same time. When adding the device, set the device name, device description, KKS code, address, station, Attributes such as device type and feedback value unit, when the device type is selected, the diagnostic information point definitions and calculation formulas of this type of device are obtained from the fieldbus device type file (.et file), and finally the added device is connected to the control network It is related to the fieldbus diagnosis point in the system, and the configuration project will be saved to a file after the configuration is completed.

The fieldbus device monitoring and management module receives the diagnostic information of the fieldbus device collected by the OPC client, reads the fieldbus device type file and the fieldbus device configuration file, calculates the fieldbus diagnostic data, and displays the result to the data processing on the interface of the module.

If there is a new fault or maintenance of the equipment, a work contact sheet will be automatically generated. At this time, the fault will be recorded, and it will not return to normal state if the fault is eliminated. Only when the on-site fault is resolved and the work contact sheet is confirmed , in order to completely eliminate the fault state of this device.

The fieldbus equipment monitoring and management module also counts the fieldbus equipment, including equipment classification statistics, fault equipment statistics and maintenance equipment statistics.

Further, the data processing module also includes a Web server module and a fieldbus device Web data request processing module;

The Web server module responds to the access request of the management system client browser, and sends a data request to the data processing module according to the access request;

The fieldbus device Web data request processing module receives the data request from the Web server module, reads the corresponding data from the fieldbus device computing data real-time database module according to the type of requested data, and writes the data into the corresponding format according to the request of the Web server module document;

The Web server module periodically reads the data file written by the fieldbus device Web data request processing module in real time according to the request, and sends the data information to the client browser of the management system.

The specific monitoring method of the system is given below:

The monitoring and management method of the fieldbus equipment includes the following steps:

1) The data acquisition module collects fieldbus device diagnostic data

(1) Use Ethernet to connect the data acquisition module with the OPC server of the control network;

(2) Open the OPC client in the data acquisition module of the fieldbus device monitoring and management system, and connect to the OPC server of the control network, add an OPC group to the connected OPC server, and set the dead zone and scan cycle of the OPC group at the same time , and finally add the fieldbus device diagnostic information points to be collected under the specified OPC group;

(3) Export all fieldbus device diagnostic information points in the OPC group to a CSV file, use Excel to open the exported file, each diagnostic information point in the exported file occupies one line, the first column is the label of the diagnostic information point, and the first column is the label of the diagnostic information point. Fill in the KKS code of the device corresponding to the diagnostic information point label in the first column in the second column. After saving the CSV file, use the OPC client to re-import the edited CSV file to the original OPC group;

(4) Save the configuration in the OPC client to the ".ocf" file, and at the same time generate a fieldbus device diagnostic information point file (OPCData.osd file), and send this file to the history record program and the fieldbus device group status program and fieldbus device monitoring and management program;

(5) The OPC client starts to send the fieldbus device diagnostic information point data received from the control network OPC server in multicast mode.

Step 2: Make the device type file. According to the device type in the field project, make a device type file (.et file) for each device type. The specific steps are as follows:

(1) According to the definition of diagnostic information in the control network, the definition of diagnostic bytes by equipment type and the demand for diagnostic information on site, use the xml format to define the diagnostic information points that need to be calculated;

(2) Split the diagnostic information point defined in (1) according to the definition of the diagnostic byte in the fieldbus device type, name each split bit, and express the definition and naming in xml format;

(3) According to the requirements of the on-site engineering, reassemble each bit of diagnostic information split in (2), define its calculation formula according to the program requirements, and express it in xml format;

(4) Run the fieldbus device type generation program to analyze the diagnostic information definition in xml format, and finally convert the operation formula of the infix expression into the suffix form, and save it in the device type file (.et file).

Step 3: Configuration of fieldbus devices, adding devices to the fieldbus control and monitoring system, setting device types for devices, and installing device type requirements, searching for corresponding diagnostic information points from the fieldbus device diagnostic point files, and making them associated To the device, the specific steps are as follows:

(1) Open the fieldbus device configuration program in the data processing module, add the controller and communication master station according to the field engineering topology diagram, and add a new topology diagram in the communication master station in units of communication boxes;

(2) Draw a topology map using the primitives in the configuration tool;

(3) After adding the graphic element of the communication master station, set the controller name, communication station name, and address for the graphic element of the communication master station, and finally add diagnostic information points;

(4) Add the network segment graphic element, and set the name, address and KKS code for the network segment;

(5) Select the graphic element of the network segment, add the graphic element of the fieldbus device under it, and add the fieldbus device for the monitoring and management system of the fieldbus device at the same time. When adding a device, you need to set the device name, device description, KKS code, address, Bit, device type, feedback value unit and other attributes, when a certain device type is set, its diagnostic information point is determined. At this time, it is necessary to find out the point where the KKS code is the same as the device KKS from the fieldbus device diagnostic information point file. , and associate them with fieldbus devices in three ways: analog point, pack point or split point;

(6) Save the fieldbus equipment configuration, obtain the topology map configuration file (.grp file) and the fieldbus equipment object configuration file (EquipmentObject.dat file);

(7) Send the configuration file to the history record program of the data acquisition module, so that it can perform operations according to the configuration.

Step 4: Calculation of fieldbus device diagnosis data, the data processing module receives the multicast data packet of the data acquisition module, and diagnoses the fieldbus through the configuration information of the engineering configuration file, the device type file and the fieldbus device diagnosis information point file The data is calculated and the result is displayed on the interface of the data processing module. The specific calculation method is as follows:

(1) Start the operation module of the fieldbus equipment monitoring and management system, read the fieldbus equipment type file (.et file), fieldbus diagnostic information point file (OPCData.osd file) and fieldbus equipment configuration file (EquipmentObject.dat file), create a dynamic database according to the diagnostic point information, initialize the fieldbus device object, send a synchronous data request to the history record program in the data acquisition module through the TCP protocol, and synchronize the data in the dynamic database and all the history from the last exit from the system For data, if the last logout from the system was 8 hours ago, only 8 hours of data can be synchronized. Historical data includes historical data of data points, historical status of equipment, and newly generated work contact sheets. The 8-hour mechanism prevents the management terminal from accidentally exiting After the data information is lost, the data is guaranteed to be consistent after synchronization;

(2) Start the thread for receiving multicast packets, start to receive fieldbus device diagnostic data, and save the received data to the original data real-time database, and compare it with the data at the previous moment. If the diagnostic data changes, pass the data point location The KKS code of the device directly notifies the device, so that the device will recalculate all the states in the next operation cycle, and if the diagnostic data has not changed, it does not need to be calculated;

(3) Start the calculation cycle and scan all fieldbus devices every 3 seconds. The process is shown in Figure 3. If the diagnostic data of the device changes, recalculate all the status of the current device;

The flow of the computing cycle is as follows: start a computing cycle, first determine whether there are any untraversed devices, if not, obtain the next device object, check whether the diagnostic information of the current device changes, and if so, calculate the All states, and determine whether there is a new fault or maintenance state, if so, set the device to the fault state, and then according to whether the device is being repaired or maintained, if not, then according to whether there is an unprocessed work contact list for this device, If not, create a work contact list, and if there is, add the fault information to the existing work contact list.

(4) Referring to Figure 4, if after the completion of the fieldbus device state calculation, it is found that the current device has a new fault or maintenance status, judge whether the current device is in the state of processing the fault, if there is a fault that is being processed, no work will be generated Otherwise, it is judged whether the current device already has an unprocessed work contact list. If it exists, add the current fault to this work contact list. If it does not exist, generate a new work contact form for the current device. contact list;

If the fault is found to be eliminated after the calculation is completed, record the previous fault state and restore the device state to normal. Only when the device has been repaired and the work contact list has been confirmed can the fault state of the device be completely restored to normal;

(5) Write the historical data into the memory buffer every 3 seconds, and write the data within the previous 1 minute into the file every 1 minute. The historical data includes the original historical data of fieldbus device diagnostic data points and the operation history of the device status When saving data and historical data, compare the current data with the data at the previous moment. If there is a change, it will be recorded in the memory, otherwise it will not be recorded. This method reduces the redundancy of historical data. Historical data can be used to Query information such as the historical status of the device;

(6) Statize the data in the memory and display it on the interface of the data processing module;

(7) In addition to computing and statistical functions, the data processing module also has a query function. You can query the current status or historical status of the device through the device name or KKS code, and you can also query the work contact list being processed, the processed work contact list, The work contact form completed within ten days, and search the work contact form according to the time period, or query all the work contact forms related to the maintenance personnel through the name of the maintenance personnel.

Claims (10)

1. A fieldbus equipment monitoring and management system is characterized in that, comprising a data acquisition module and a data processing module connected by Ethernet; Data acquisition module, including OPC client and historical record module; The OPC client connected to the OPC server collects the diagnostic information of the fieldbus device, the OPC client sends the collected data to the data processing module through Ethernet, and the OPC client also sends the collected data to the history record module; The historical record module keeps the collected data for a period of time, and saves the collected data to the historical data file regularly; Data processing module, including fieldbus device type file generation module, fieldbus device configuration module, fieldbus device monitoring and management module, fieldbus device original data real-time database module and fieldbus device operation data real-time database module; The fieldbus device type file generation module generates the corresponding device type file according to the type of fieldbus device and its use method. The device type file provides the format and algorithm for device configuration and device monitoring management. This file is generated when the system starts Fieldbus device configuration module loading; The fieldbus device configuration module generates the operation topology diagram reflecting the positional relationship and operation information of the fieldbus device, adds it to the corresponding position in the operation configuration diagram according to the station information of the fieldbus device, and loads it according to the system startup. The device type file associates its basic information, status information and diagnostic information with the fieldbus device; The fieldbus device monitoring and management module receives the diagnostic data of the fieldbus device collected by the OPC client, and updates the diagnostic data value to the real-time database module of the original data of the fieldbus device in real time, and at the same time according to the fieldbus device type file and the fieldbus device type The algorithm corresponding to the file performs periodic calculations on the fieldbus diagnostic data, refreshes the information on the monitoring interface of the module in real time according to the calculation results, and updates and saves the calculation results in real time to the fieldbus device calculation data real-time database module; The raw data real-time database module of the fieldbus equipment receives the raw information point data of the fieldbus equipment monitoring and management module, stores it in the corresponding position of the raw data real-time database, and periodically stores all the data in the raw data real-time database to the raw data history in the file; The real-time database module of fieldbus device computing data receives the data calculated by the fieldbus device monitoring and management module, stores it in the corresponding position of the computing data real-time database, and periodically stores all the data in the computing data real-time database into the computing data history file . 2. the Fieldbus equipment monitoring management system as claimed in claim 1, is characterized in that, also comprises Web server module and Fieldbus equipment Web data request processing module; The Web server module responds to the access request of the management system client browser, and sends a data request to the data processing module according to the access request; The fieldbus device Web data request processing module receives the data request from the Web server module, reads the corresponding data from the fieldbus device computing data real-time database module according to the type of requested data, and writes the data into the corresponding format according to the request of the Web server module document; The Web server module periodically reads the data file written by the fieldbus device Web data request processing module in real time according to the request, and sends the data information to the client browser of the management system. 3. the fieldbus equipment monitoring management system as claimed in claim 1, is characterized in that, described OPC server is connected with DCS system; The OPC client sends the collected data to the data processing module through multicast, and a firewall is set between the OPC client and the data processing module. 4. The fieldbus device monitoring and management system as claimed in claim 3, wherein the OPC server is provided with an OPC group, and the OPC group derives the fieldbus device diagnostic information point that needs to be collected, and generates diagnostic information according to it point file. 5. fieldbus device monitoring and management system as claimed in claim 1, is characterized in that, described device type file is according to the device type in the field project, makes a device type file for each device type; The device type file includes the definition of the diagnostic information point mode required by the device type, and the definition of the diagnostic information state algorithm. 6. The fieldbus device monitoring and management system as claimed in claim 1, wherein when the system starts, the system reads the diagnostic information point file information, and the fieldbus device raw data real-time database module creates and initializes the real-time database according to these information , all diagnostic information points and related information are stored in a real-time database in a certain format. 7. The fieldbus device monitoring and management system as claimed in claim 1, wherein, when the system starts, the system reads the fieldbus device type file, and according to its information, creates a device type object and related information and calculation formulas, so that Read information when configuring the selected device type. 8. The fieldbus device monitoring and management system as claimed in claim 1, wherein the fieldbus device configuration is to associate the device type object with the information point in the fieldbus device real-time database, which is a fieldbus control The monitoring system adds equipment and sets the equipment type for the equipment. 9. The fieldbus device monitoring and management system as claimed in claim 1, wherein, when the fieldbus device monitoring and management system starts, it creates and initializes a real-time database of computing data according to configuration information, information points associated with equipment, in order to prepare for computing Update storage of data. 10. The fieldbus device monitoring and management system according to claim 1, wherein the data processing module also inquires about the current state or historical state of the device through the device name or KKS code.

Images