Network scanning and organisation of management in device type manager

FIELD: radio engineering, communication.

SUBSTANCE: method of communication with the use of infrastructure made according to the standard FDT (Field Device Tool), with device working in process control medium and having communication connection with communication link, including: method of communication with the use of infrastructure made according to the standard FDT (Field Device Tool), with device working in process control medium and having communication connection with communication link, including: generation of copy of process performed with the possibility of scanning of device type manager (DTM) of "device" type that represents the said device in FDT infrastructure; communication connection of this DTM copy with communication link corresponding to the said communication link; scanning of the said communication link with the aim to detect the said device using the said copy of DTM; and obtaining the address of detected device in DTM made with the possibility of scanning.

EFFECT: simplification of devices configuration and management in FDT infrastructure, thus reducing the probability of human error.

27 cl, 7 dwg

Reference to related application

In this application we use materials of the application for U.S. patent No. 60/956328, entitled "Network scanning and organization of work in the Manager of devices ", filed on August 16, 2007, the contents of which is incorporated herein by reference.

The technical field to which the invention relates.

The present invention relates essentially to a device management control processes, and, in particular, to the scan Manager device type (Device Type Manager, hereinafter for brevity DTM), working in infrastructure, made in accordance with the standard instrumentation of field devices (Field Device Tool, hereinafter for brevity - FDT).

The level of technology

Management system processes similar to those used in chemical, petroleum or other processes, typically include at least one centralized or decentralized process controller, coupled with the possibility of communication with at least one server (host computer) or the terminal operator, and at least one measuring and control device of the process, such as, for example, the field devices via analog, digital or mixed analog-digital tire. Field devices, representing, for example, valves, valve positioners, switches, shall erettsegi and sensors (for example, sensors of temperature, pressure, and flow rate)are in the medium manufacturing enterprises, and perform functions within the process such as opening or closing valves and measuring process parameters, the increase or decrease of fluid flow, etc. Smart field devices, such as field device corresponding to well-known protocols such as FOUNDATION™ Fieldbus, Device-Net^™or HART^®may also perform control calculations, the signal function and other control functions are part of the process controller.

Controllers process, which normally resides in the environment of manufacturing companies receive the signals reflecting the measurement process, or process variables, obtained by means of field devices or associated, and/or other information relating to the field devices, and application software of the controller. App controller is implemented, for example, different control modules, decision-makers concerned with managing the process, generate control signals based on the received information and coordinate with the control modules or blocks of field devices, such as field devices HART^®and Fieldbus. The control modules within the process controllers send control signals on which the third communication or signaling channels to the field devices to control thereby the operation of the process.

Information from field devices and controllers process is usually provided with one or more other hardware devices, such as, for example, operator terminals, terminal maintenance, personal computers, handheld devices, archivers data, reporting, centralized databases, etc. in order to provide an opportunity for the operator or maintenance person to perform the required functions associated with the process, such as, for example, change the settings of the program management process, change management modules in process controllers or intelligent field devices, monitoring the current status of the process or the status of individual devices within the production enterprise monitoring alarms generated by field devices and controllers process modeling process with the purpose of training or testing software, process control, fault diagnosis, or failure of equipment within the production enterprise, etc.

The recent introduction of Fieldbus technology and related standards in the field of process control has made possible the unification of field devices, process controllers, multiplexers, terminals and proong the equipment in the company's network. In fact, Fieldbus provides the basis for distributed real-time control by allowing multiple devices to connect with one two-wire line, which, in turn, may communicate with the controller, the host computer or other intellectual head unit. However, the effectiveness of Fieldbus is significantly limited by the large number of Protocol standards that govern the communication with the Fieldbus. For example, at the moment there are competing Fieldbus protocols like Foundation Fieldbus (FF) and Profibus, in addition to other types of communication protocols such as HART^®or CAN. In addition, there is a significant number of working devices still use the range of 4-20 mA, which require additional hardware to connect to the Fieldbus line.

Many manufacturers produce field devices and other hardware components for process control, in the General case is compatible only with some of the existing protocols. Moreover, the devices often require special configuration and parameterization, and each manufacturer may provide additional requirements for configuration. Thus, operators, and maintenance personnel often need a large number of individual tools for specific Protocol is in, manufacturers and devices for communication with devices and the configuration, diagnostics and maintenance. As a result, the operator terminals, or portable devices can contain multiple disparate tools, and operators can spend a significant amount of time studying the work of these utilities and their selective application to a certain limited part of the network management process, or to a limited aspect of network operation.

In recent years, an attempt was made to solve the problem of incompatible data, documentation, configuration of devices and human-machine interface (HMI) with the implementation of the FDT standard are required. The purpose of the standard FDT is to provide the end user with a unified way to communicate with heterogeneous field devices and other components of the management process by identifying the different interfaces and a single software infrastructure. In particular, the joint common interest group (Joint Interest Group, including many major manufacturers have agreed to implement multiple interface definitions that are available for a wide range of people, and chose a software platform for the development of various high-level applications. For more information on FDT can be found at www.fdt-jig.org. With the mA technology FDT does not provide ready-utilities but it provides a Toolkit for the development of so-called application infrastructure for such diverse purposes as resource management, device configuration, or modeling process control and diagnostics.

FDT is based on several widely used standards and technologies, making application infrastructure capable of running on computers with Microsoft Windows operating system. In particular, FDT is based on an object model of the software components of Microsoft Component Object Model, COM) to provide object-oriented development, independent of the programming language; extensible markup language (Extensible Markup Language, XML) for data exchange; and on ActiveX technology to determine the graphical interface. Familiar with Microsoft Windows^®the person knows that the COM allows you to develop dynamic objects and the interaction processes between themselves regardless of programming language. In addition, the COM objects demonstrate its functionality and features through well-defined interfaces. With the aim of providing a graphical user interface (Graphical User Interface, GUI)standards FDT require the use of ActiveX. On the one hand, the ActiveX technology of Microsoft company is an extension of the article is ngarta COM, aimed specifically at the use of graphical interfaces, user interfaces introduction and interfaces for data exchange in a Windows environment. Finally, FDT uses XML is an open standard that is widely used in various industries and applications for data definition. XML provides lexical rules, using the set of commands (tags) determine the type and boundaries of data structures. For the specialist who is familiar with related areas such as web programming, it is obvious that you have correctly performed the XML documents can be read by both human and machine. It is important that XML also provides easy expansion using user-defined tags.

FDT uses XML to define rules about the relationships between objects, such as, for example, an application infrastructure FDT and the Manager device types (DTM). DTM is a software component that includes a software application is made for a specific device. In accordance with the General principles of CATFISH, DTM is a binary object with a set of interfaces, the relevant rules infrastructure FDT. Usually the manufacturer of the device provides DTM for a specific type of device, making the DTM can be included in the application management process, software management R what resources or in another type of developed DTM applications. Specified DTM enables the user dialogs and user interfaces, rules for the respective device and in many cases background information for the application, which may relate to the device.

DTM can vary in complexity, depending on the type of device or type of hardware, which specified DTM present in the environment FDT. Every manufacturer has the right to implement DTM different, but at least every DTM includes mandatory interfaces. Some manufacturers can provide complex functions calibration, diagnostics, testing and maintenance in the form of additional elements DTM. In addition, some manufacturers provide in DTM multilingual support to facilitate the process of integration of DTM in any application infrastructure FDT.

There are different types of objects DTM used by applications infrastructure FDT. For example, the DTM of type device (referred to here as "DTM device") is a field device and the communication DTM corresponds to a module with direct access to the resource connection. Thus, the digital valve controller DVC6000 series, Emerson Process Management™, can be represented DTM device that communicates using the FDT interface with the communication DTM representing with the Oh HART modem. More specifically, the application infrastructure, running on the operator's terminal, for example, handles the object of a specific class DTM devices and the object of a particular class of communication DTM. In the environment FDT DTM device does not "know" the details of the Protocol supported by the communication DTM communication DTM does not "know" features DTM device. During configuration, diagnostics or operations of another type DTM device can send a command with the appropriate command parameters to the communication DTM communication DTM, in turn, will format command in accordance with the requirements of the Protocol and transfers the data to the proper interface of the terminal operator. In a nutshell, DTM device determines the functional properties of a particular device, and the communication DTM determines the functional properties of a particular Protocol. DTM device may also communicate with the corresponding physical device with built-in TV applications infrastructure, or to use as the built-in channels and channel functions provided by one or more communication DTM.

Next, DTM gateway provides routing between different protocols. For example, DTM gateway can provide transmission Protocol PROFIBUS in the HART Protocol. In some DTM gateway can provide other functions to facilitate interaction between the field devices and hardware communication devices, in addition to, or instead of broadcast protocols. In certain embodiments perform, DTM gateway can be connected to the DTM device and the communication DTM. In other embodiments, DTM gateway can connect with two communication DTM, supports various protocols or communication schemes. In addition, can be developed, and other types of DTM for such purposes as, for example, the connection between the application FDT with an external application.

Interfaces and functions provided by the existing environment FDT/DTM, usually requires a separate DTM for each physical device. In addition, DTM device can connect with only one communication channel of the communication DTM. Thus, despite the fact that the tools FDT provides engineers and operators with a powerful set of software tools, developing and configuring applications infrastructure FDT for large systems management processes can be very long and time-consuming. In particular, operators should configure each DTM device address of the corresponding physical device. In addition, the configuration of each device must be carried out separately, even if multiple devices share many common configuration settings. For example, if several similar devices made on the same line connections FF H1, each DTM device you selected is about to implement, to configure with the correct physical address, and optionally configure before using.

Disclosure of inventions

Made with the possibility of scanning module DTM device is a device in the environment FDT and includes a scan function that allows the DTM to recognize and manage one or more devices of the specified type on the specified communication channel. Made with the possibility of scanning DTM device connects to the communication DTM and requests the target address range, using a known command Protocol supported by the communication DTM. In one embodiment, is configured to scan DTM device detects the presence or absence of a device at a particular address. In another embodiment, is configured to scan DTM device receives a further characteristic of the device information for each discovered device. Made with the possibility of scanning DTM device eliminates the need to enter the address of the physical device manually. Instead performed with scanning DTM device detects the corresponding physical device automatically by scanning the valid range of addresses using one or more communication DTM.

On the one hand, is arranged to scan DTM device complies with the standard of infrastructure FDT, certain Joint Interest Group. In this respect, made with the possibility of scanning DTM device is fully compatible with applications infrastructure FDT. In one embodiment, is configured to scan DTM device replaces the DTM device for a particular device and may be provided as a replacement DTM by the manufacturer. Replacement DTM can have all the functions of the DTM device for the corresponding y is trojstva, as well as additional functionality that is implemented according to the materials of the present application. In another embodiment, is configured to scan DTM device connects an application running outside infrastructure FDT, with communication DTM in infrastructure FDT. An external application can natively support the function of the particular device, and configured to scan DTM device can provide an external application detection function, and can also serve as a connection between the external application and infrastructure FDT.

On the one hand, scanning is performed by scanning DTM devices programmed on the valid address range of the device associated with the particular channel. Made with the possibility of scanning DTM device additional software includes an inquiry command to a particular device or Protocol. In one embodiment, is configured to scan DTM device sends a command for each valid address and waits for a response. In another embodiment, is configured to scan DTM device uses broadcast or multicast command sent to a specific address range. In one embodiment, made with the discerning business is using scanning DTM device queries all devices United with a particular channel. In another embodiment, is configured to scan DTM device polls a particular type of device, such as a valve controller DVC6000. In accordance with another embodiment configured to scan DTM device can accept user input using an external application or by using a custom dialog in infrastructure FDT and can scan a range of addresses entered by the user. Made with the possibility of scanning DTM device may also display the scan results within infrastructure FDT and/or using an external application.

On the other hand, is arranged to scan DTM device provides the option to recover the connection with the external application. If the connection with the physical device is lost, made with the possibility of scanning DTM device may attempt to reestablish the connection as soon as an external application tries to communicate with the physical device. Specifically made with the possibility of scanning DTM device can store the address of each discovered device and to maintain a variable that indicates the status of the connection.

Brief description of drawings

Figure 1 schematically illustrates the control system is ment processes which can be configured and managed using the application infrastructure FDT.

Figure 2 is a schematic showing multiple objects DTM known types that interact in the application infrastructure FDT.

Figure 3 is a schematic display configured to scan DTM device that interacts with a software application running outside infrastructure FDT, and the communication object DTM infrastructure FDT.

Figure 4 is a schematic display of one made with the possibility of scanning DTM device that manages multiple physical devices using the communication DTM.

Figure 5 is a schematic display configured to scan DTM device that interacts with a software application running outside infrastructure FDT, and several separate communication objects DTM infrastructure FDT.

Figa is a schematic display of a software application running outside infrastructure FDT and interacting with multiple configured to scan objects DTM device implemented in a separate application infrastructure FDT.

6 illustrates an example of a program that is executed is the ability to scan DTM device during the scanning device.

7 illustrates another example of a program that is configured to scan DTM device within the scan function to detect devices of the specified type.

The implementation of the invention

Figure 1 is a schematic display of a process control system in which a software utility developed infrastructure FDT, allow operators to view, configure, or otherwise communicate with elements of a process control system, regardless of the specific parameters of the manufacturer or model of a particular item. In particular, the process control system 100 includes one or more process controllers 110, having a communication connection with one or more head terminals or computers 120-122 (which can be represented by any type of personal computers, terminals and the like), provided with at least one display. The controller 110 is also connected to the field devices 130 using cards I / o 140. The archiver data 145 may be a data collection device of any type, provided with a memory of any type and of any desired or well-known software, hardware or hardware-implemented software for storing Dan is s, and can be performed separately from the terminal 120-122, or as an integral part of one of the specified terminal. The controller 110, which may be, for example, the controller DeltaV™, manufactured by Fisher-Rosemount Systems, Inc., has a communication connection with the main computers 120-122 through, for example, Ethernet, or any other desired data network 150. The data network 150 may be implemented as a local area network (LAN), wide area network (WAN), telecommunications network, etc. and can be performed using wired or wireless technology. The controller 110 has a communication connection with the field devices 130 using any desired hardware and software related, for example, to the standard devices range 4-20 mA, and/or any smart communication Protocol such as the Protocol FOUNDATION Fieldbus (Fieldbus, HART, etc.

The field device 130 may represent any type of device, such as sensors, valves, transmitters, positioners, etc. and card I / o 140 may be a device I / o of any type that is compatible with any desired communication Protocol or controller. In the embodiment shown in figure 1, the field devices 130 are devices HART, the implementation of the determinant relationship using standard analog lines 131 in the range of 4-20 mA with HART modem 140, and field devices 133 are intelligent devices (software management), such as Fieldbus field device that communicates over a digital bus 135 to the card I / o 140 using the Fieldbus communication Protocol. Of course, the field devices 130 and 133 may be compatible with any other desired standards or protocols, including any standards or protocols that will be developed in the future.

Additionally, the field device 142 may be connected to the digital bus 135 through gateway 143. For example, the field device 142 can only accept commands HART, and digital bus 135 may use the PROFIBUS Protocol. In this case, the gateway 143 can provide two-way transmission Protocol PROFIBUS/HART.

The controller 110, which may be one of several distributed controllers within the enterprise, provided with at least one processor, performs or oversees the implementation of one or more control programs, which may include closed circuit regulation, stored in or otherwise associated with them. The controller 110 communicates with devices 130 or 133, headaches computers 120-122 and the archiver data 145 to control a process in any desired manner. It should be noted that any control program or electronegative the coefficients, described herein may be optionally partially implemented or implemented using other controllers or other devices. Similarly, the control program or the elements described here and implemented in the framework of a process control system 100 can have any shape, including software, hardware-implemented (built-in) software, hardware, etc. for the purposes of the present description, the control process can be any part or component of a process control system, including, for example, a program, unit or module stored on any machine-readable media. Control program, which can be modules or any part of the program (procedure) management, such as subroutines, part of the routine (for example, lines of code in the program), etc. can be implemented in any software format, for example, using circuit diagrams, sequential function charts, function diagrams, objectively-oriented programming or any other programming language or design solutions. Similarly, the control program can be hard-coded in, for example, one or more EEPROM, EEPROM integrated circuits applied orientation (ISOE), or any other is their hardware elements or elements of the firmware. In addition, the control program can be performed by any means of design, including graphic design or any other type of software, hardware, the firmware or design tools. Thus, the controller 110 may be designed with the ability to perform management strategy or management program any way you want.

Terminals 120-122 can execute one or more applications infrastructure FDT, each of which can operate in a distributed or retained mode. For example, the terminal 120 may perform the functions of storing application-specific FDT management resources, and the computer 122 may perform the functions of the query of the same application. As shown in figure 1, the application 200 infrastructure FDT can work on the terminal 120 and may be responsible for the management of resources. Similarly, the application 200 infrastructure FDT may also control one of the other aspects of factory automation, such as technical support (design, modeling etc), installation, commissioning, production, or maintenance. In addition, the following is noted that the application 200 infrastructure FDT is not limited to the above function is and may perform one or more functions, provide infrastructure FDT.

As shown in figure 2, the application 200 infrastructure FDT can work in a distributed or retained mode on the platform 202. In the above example, the platform 202 may be a Windows operating system provided by the terminal 122. However, the platform 202 may, in some embodiments, execution, distributed on several prototype computers, such as terminals 120 and 122 by using one of the known from the prior art how to perform a distributed software architecture. In the example shown in figure 2, the application 200 infrastructure FDT performed using known methods and are presented here as an example.

Application infrastructure FDT 200 can output screen displaying the menu bar 204, the toolbar 206 and various navigation keys 208. As described above, the application 200 infrastructure FDT is based on the technology of COM and ActiveX Microsoft access standard graphical interfaces Windows, and thereby allows the user to perform data entry using a keyboard, mouse or other pointing device or input device data. The application 200 infrastructure FDT may also include a database 210 that interacts with various objects FDT with p the power of interfaces, presented in the FDT standard are required. The application 200 infrastructure FDT may additionally contain multiple instances of the object DTM. In particular, the communication DTM 220 may be responsible for the communication via Foundation Fieldbus (FF) H1 on a certain segment of the available physical FF-interface platform 222 202. As shown in figure 2, FF-interface 222 may include d ct, z several modules, such as a computer expansion card that is compatible, for example, with the standard connection of peripheral components (Peripheral Computer Interconnect (PCI), or a separate hardware module. In another embodiment, the communication DTM in General and DTM 220 in particular may correspond to any physical implementation of the device or the communication module. In the here described example of the communication DTM 220 corresponds to the hardware module 224, which is responsible for a specific segment H1.

During operation of the communication DTM 220 generates and transmits commands compatible with the Protocol FF H1, hardware module 224 via connection 230.

Connection 230 may include standard interfaces provided by the operating system, serial interfaces such as RS232, and other known means of communication with a peripheral device. Hardware module 224 may communicate with one or more field devices 240-244 using digital bus 235, which may be similar to W is Noah 135. In particular, the field device 240 may have an address A₁, the field device 242 may have an address A₂and the field device 244 may have an address And₃. When sending or receiving commands and data, the application 200 infrastructure FDT in General refers to a specific address (A₁-A₃for a precise definition of the target device. In a known environment FDT, communication DTM 220 receives the command and the address of the target device connected with the digital bus 235, from the DTM to the device corresponding to the target device. Thus, the application 200 infrastructure FDT processes the object 250 DTM device, the corresponding field device 240, the object 252 DTM device, the corresponding field device 242, and the object 254 DTM device, the corresponding field device 244.

Each of the standard objects 250-254 DTM device is configured with the address of the corresponding field device. For example, DTM 250 device cannot communicate with the corresponding physical device 240, until it receives the address of A₁by explicit configuration. Thus, with the present level of technology, if a particular system has five FF H1 segments, and each segment H1 are eight particular type of device, the FDT application requires at least 40 separate instances DTM device pointed to by the type, in order to carry out the operation and monitoring of each field device. As shown in figure 2, the communication DTM 260 may correspond to a HART modem 262 and likewise require a number of DTM 266 devices equal to the number of field devices 268 connected to the HART modem 262. Communication DTM 260 can communicate with HART modem 262 via a communication channel 263.

In the above example, each of the conventional DTM 250-254 and 266 device is implemented specifically for the Protocol supported by the communication DTM is attached DTM device. As noted above, DTM device may also be connected with DTM gateway that supports translation between protocols. As shown in figure 2, DTM device 270, the corresponding field device that only supports PROFIBUS, can be connected to the gateway DTM 272 providing translation PROFIBUS/HART. DTM 272 gateway, in turn, is connected to the communication DTM 260 that provides HART communication.

As shown in figure 3, is arranged to scan DTM device 300 according to the present invention, running in the application 302 infrastructure FDT can communicate with an external module 310 software) using interfaces that correspond to the applicable standards FDT. In another embodiment, the connection between executed with the possibility of functional the DTM device 300 and the external module 310 expands ON the standard FDT or based on the communication scheme, beyond FDT; however, the work is done with scanning DTM 300 device application 302 infrastructure FDT preferably corresponds to the FDT standard are required. External module 310 can represent, for example, the AMS ValveLink^®Software from Emerson Process Management™, which is part of the package PlantWeb^®. It should be noted that although figure 3 shows the external module 310, as belonging to the platform 202, this and other examples outside, described below, can also run on another platform or on multiple platforms in a distributed mode. Since the external module 310 is not part of the application 302 infrastructure FDT module 310 ON does not have direct access to any of the communication DTM. In General, the application 302 infrastructure FDT similar to the application 200 infrastructure FDT in that it relies on the standard FDT interfaces and can operate on the same platform 202 OS. Moreover, the application 200 and 302 infrastructure FDT correspond to the same physical configurations of devices such as field devices and modems. As shown in figure 3, is arranged to scan DTM device 300 may connect to the communication DTM 220, responsible for a specific segment of the FF H1.

During operation, the external module 310 may communicate with the field device is 240 Ohm, sending device-specific commands. In one embodiment, the external module 310 knows FOR device-specific commands and parameters and requires only communication channel to work with the field device 240. For example, the field device 240 may be a digital valve controller DVC6000, and the module 310 can represent the AMS ValveLink Software that controls the operation of the valve by the controller DVC6000 and provides the user a graphical and textual display.

Made with the possibility of scanning DTM device 300 can be programmed to scan a particular communication channel and message addresses of devices external to the module 310. In another embodiment, is configured to scan DTM device 300 may store addresses of the discovered devices, assign logical identifiers (or "nicks") to each detected device, to inform the IDs module 310 and to transmit data on behalf of the module 310. In this case, the module 310 can continue to need information were successfully detected device type desired, but may not be required to obtain the physical addresses of devices or other data network topology. In other words, are designed to scan DTM device 300 can transmit data between one who does multiple field devices and the module 310.

As particularly shown in figure 3, is arranged to scan DTM device 300 may be an example of a class created with the ability to scan DTM device, programmed to interact with the communication DTM particular Protocol type. Made with the possibility of scanning DTM device 300 can be implemented to work specifically with the Protocol FF H1, and is arranged to scan DTM device 304 may be an example of the same class that is implemented to work with HART Protocol. In another embodiment, is configured to scan DTM 300 and 304 of the device can be made from different classes, each of which is designed specifically for a particular Protocol. To this end configured to scan DTM 300 or 304, the device may include a scanning function, is responsible for performing one or more scans, or "discovery" on a specific line (for example, electric lines, logical channel, bus etc). The manufacturer of the device, or that the provider is configured to scan DTM 300 or 304, the device may provide the scanning function as inline element DTM 300 or 304. In another embodiment, the scanning function may be provided in the form of additional omponent (plugin) compatible with a specific DTM device, allowing DTM device may acquire the ability to scan when connecting the plug.

Scanning can be done with recognition of certain specific aspects of the Protocol, for which the corresponding instance is configured to scan DTM device performs a scanning operation. For example, scanning is performed with scanning DTM device 304 can be programmed to send a HART command "0" to the communication DTM 260. As is clear to a person familiar with HART, this command may take a short or long address HART and, provided the correct delivery to the HART device, to make the HART device to reply with a message containing an identification device settings. In other embodiments, execution of the scan function can send another command or sequence of commands to detect HART devices on a particular channel, such as channel 263. In General, scan function to scan for the presence of alarms, to poll the sensors (e.g., primary sensors), to request status information, or perform similar non-Intrusive or minimally Intrusive operation to detect the field devices. In some the options run scan function polls the device and simultaneously receives additional useful information such as the device status. In other embodiments, execution of the scan function may have little or nothing to have information about one or more protocols supported by the communication DTM 260, and can scan a line or communication channel, sending high-level commands to the DTM 250 connection. Communication DTM can accordingly transmit these commands to the physical devices, and send appropriate responses made with the possibility of scanning DTM 304 of the device.

As shown in figure 3, is arranged to scan DTM 304 can give a report on the list of devices external to the module 310 BY the end of the operation device detection scan. Made with the possibility of scanning DTM 304 may be programmed to detect devices of any type on a specific channel. External module 310 may display a list of devices and, if desired, the status of each discovered device to the user, and can then accept commands for a specific device. As described above, the external module 310 can communicate with each discovered field device using configured to scan DTM 300 or 04 device by specifying the device address, obtained from DTM 300 or 304, or logical ID assigned DTM 300 or 304. Thus, one instance is configured to scan DTM device, such as DTM 304 may automatically discover the devices available on the communication channel 263, and can provide communication with each of the multiple devices 268. Made with the possibility of scanning DTM device made according to the present invention can thus eliminate the need for a separate object DTM device for each device, as well as the need to request address information from the user.

Additionally or alternatively, the external module 310 can specify the device type, brand of the manufacturer and other similar settings made with the possibility of scanning DTM 304 or 300. The HART communication Protocol, for example, each device associated with the identifier of the manufacturer, such as Fisher Controls, and type of device, such as DVC5000. Made with the possibility of scanning DTM 304 or 300 may then scan the communication channel similar to that described above in the embodiment of the way and can optionally filter the list of found devices by device type, type, manufacturer, or combinations of the above parameters. In one possible embodiment, is executed with the option of scanning DTM 304 or 300 can search for all devices of a certain type and to inform about the detected devices to the external module 310 ON regardless of the parameter identification of the manufacturer, associated with each device. In another embodiment, is configured to scan DTM 304 or 300 can detect all devices manufacturer ID corresponding to the parameter specified by the external module 310. As another alternative, search criteria, such as the identity of the manufacturer or type of device can be directly programmed to be accomplished by scanning DTM 300 or 304. In this case, the external module 310 BY not disclose any settings made with the possibility of scanning DTM 300 or 304.

Figure 4 illustrates another possible option is executed with the ability to scan DTM. In this example, the implementation of the application 311 infrastructure FDT made with the possibility of scanning DTM device 312 performs all functions associated with the DTM device in any infrastructure FDT. In particular, performed with scanning DTM 312 may include data and functions specific to the field devices 242 and 244, and may interact with the graphical environment provided by the application 311 infrastructure FDT. Similarly performed with scanning DTM device 314 may include device-specific information corresponding to one or more devices connected via HART m the deme 262. Made with the possibility of scanning DTM 312 does not require the direct provision addresses of the field devices 242 and 244. Instead, performed with scanning DTM 312 scans the communication channel similar to DTM 300 or 304 and automatically detects the field device matching type. After completion of the discovery process is performed with scanning DTM 312 can communicate with both field devices 242 and 244. However, in other embodiments it may be preferable to run a separate instance, made with the possibility of scanning DTM 312 for each device, for example, to simplify device management in the FDT environment. In one possible embodiment, a separate instance is configured to scan DTM 312 may be performed for each automatically detected field device and can be associated with the address detected by the field device. Application 311 infrastructure FDT can display to the user the device description, physical address, and other related information for each discovered device using the standard FDT interfaces.

Similar to option implementation, shown in figure 3, the user may optionally be provided the options associated with the definition devices, such as a brand manufacturer and t the p device. Application 311 infrastructure FDT can provide these and other options with standard graphics and user interfaces FDT. For familiar with this technical field, man it is obvious that in some applications, such as resource management, can be interesting for a complete list of all devices connected to a particular communication line or bus, while in other applications, such as control valves may be of interest to a specific type of device. Thus, various detection devices may be preferred in various applications 302 or 311 infrastructure FDT, or the external application 310.

As shown in figure 5, the application 320 infrastructure FDT may include capable of multiple scanning DTM 322 that communicates with the outside THROUGH 324. It is assumed that, in accordance with a possible extension of the existing standard one FDT instance DTM device may be capable of interacting with multiple communication DTM. As shown in figure 5, is capable of multiple scanning DTM 322 of the device associated with the communication DTM 260 HART communication DTM 220 FF H1. In accordance with this option run, DTM 322 may also communicate with other communication DTM supporting protocols HART, FF, PROFIBUS or other PR is tokoly. In this embodiment, DTM 322 may include a scan function, performing a nested search. In particular, scanning DTM 322 can be carried out for each of the communication DTM, with which is connected DTM 322, to determine and establish the connectivity to field devices and to communicate the results of external detection AT 324.

Figa illustrates another possible embodiment of that application 326 and 328 infrastructure FDT parallel work on the platform 202. Both applications 326 and 328 infrastructure FDT can interact with the external module 310. Both applications 326 and 328 infrastructure FDT can be Autonomous and may, for example, to maintain a separate database 210 and 330 data. Application 326 infrastructure FDT may primarily support the communication Protocol of FF and may be partly responsible for management of the segment 224 FF H1 through communication DTM 220. At the same time, the application 328 infrastructure FDT can be responsible for communication via HART Protocol and can control the HART modem 262 using communication DTM 260. Like the version of the implementation described above with reference to figure 3, made with the possibility of scanning DTM device 300 may detect, report and manage field devices using communication DTM 220, and is configured to scan DTM device 30 can control the HART devices using communication DTM 260. Of course, each application 326 and 328 infrastructure FDT can have a few made with the possibility of scanning DTM responsible for different segments of the FF H1, HART modems, and other communication channels. Moreover, the external module 310 can be performed equally compatible with single or multiple applications infrastructure FDT responsible for different or similar communication lines. When this connection between applications infrastructure FDT and external agents, such as module 310 can be "transparent" to the user during installation, configuration or operation of the external module 310.

In another embodiment, the external module 310 or similar software application running outside infrastructure FDT, can communicate with multiple applications infrastructure FDT running on different physical servers. For example, the terminal 120 can perform the application 326 infrastructure FDT, and the terminal 122 can run an application 328 infrastructure FDT. Each of the terminals 326 and 328 can work on different versions of Windows, or, in case of a possible expansion of the FDT to another operating system that supports the FDT standard are required. External module 310 can work on the terminals 120 and 122 distributed way. In another embodiment, the external software can work on a single intelligent servo is e or terminal, such as the terminal 120. In this and similar cases, the external module 310 may communicate with the application infrastructure FDT using TCP/IP or UDP/IP remote procedure call (RPC) or other suitable means of remote communication between processes. In another embodiment, as an external module 310, and applications 326 and 328 infrastructure FDT can be based on the technology of distributed object model software components Distributed Component Object Model (DCOM) to communicate.

As generally shown in figure 3, 5 and 5A, is arranged to scan DTM 300 or 304 of the device, and also performed with multiple scanning DTM 322 of the device may be further configured to restore the connection of the external module 310 or 324 ALONG with the corresponding field device, if the connection is made through with the ability to scan DTM lost. In particular, performed with scanning DTM device can store the address of each discovered device, thereby eliminating the need to restart the scan each time lost one or more connection devices. In relation to figure 3-5A in General it should be noted that performed with scanning DTM device or made with the possibility of multiple IC is mapping DTM device can connect to the communication DTM using DTM gateway. For example, is arranged to scan DTM device 300 may connect to the communication DTM 220 via DTM lock type, which provides broadcast protocols PROFIBUS/FF H1.

6 illustrates a block diagram of the procedure 350, which can be made capable of scanning DTM 300, 304, 312 or 314 of the device. In step 352, the instance is configured to scan DTM device is created and initialized in the application infrastructure FDT. As described above, one instance is configured to scan DTM device can simultaneously support multiple field devices, if made with the possibility of scanning DTM device is programmed or configured to provide a sufficient amount related to the device information. Created made with the possibility of scanning DTM device can connect with a suitable communication DTM as part of the initialization sequence executed in step 352. In step 354, the procedure 350 gets the bounds of the range of addresses associated with the particular multiplexer, segment FF H1 or similar connection. The procedure 350 may also get the bounds of the addresses from the outside, working out of the application infrastructure FDT. In another embodiment, the procedure 350 may receive the boundaries of the addresses from the application infrastructure is URS FDT using the standard FDT interfaces. In another embodiment, the border device can be provided in the form of a list, and can contain multiple non-overlapping address ranges. However, the illustrated procedure 350 refers to the version of the runtime that supports one address range, limited only two addresses.

Then, the procedure 350 may pass through each address in a given range, trying to find the physical device for each address. In step 356, the procedure 350 may generate the following address by increasing the value of the previous address, or, for example, the lower limit of the range. In step 358, the procedure 350 may check exceeded if the following address is the upper limit of the given range of addresses. If the next address is within the specified range, the procedure 350 may determine the presence or absence of a physical device to the following address. In particular, the procedure 350 may start the polling function according to one of the embodiments described above.

If at step 362, the procedure 350 detects a physical device, the procedure 350 may add the address of the discovered device list. The specified step is illustrated in block 364. As described above, the procedure 350 may also receive additional information, such as the operating status of the device, the list of unprocessed alarms, Shen the registered device, raw measurements collected by the device, and similar data. The procedure 350 may store this information for each discovered device with the physical address of the discovered device. Made with the possibility of scanning DTM device that triggers the procedure 350 may then provide the collected information to an external software or application infrastructure FDT, which, in turn, can display this information in text or graphic form. Finally, the procedure 350 may report the completion of scanning external or user working with the application infrastructure FDT, at step 366.

7 procedure 380 may correspond to another possible variant execution is capable of scanning DTM device. Made with the possibility of scanning DTM device in this way can be created at step 382. At step 384, the procedure 380 may receive data about the brand manufacturer to compare these data with the information reported by each physical device present on a particular communication channel. Then, the procedure 380 can get information about the device type, to further narrow the search one or more search devices. Of course, other ways to perform the procedure 380 may include only one of the data types about the brand manufacture is vitela or device type.

In step 388, the procedure 380 can scan the channel for detection of physical devices. In this embodiment, the procedure 380 receives a complete list of the physical devices and filters the received list in step 390. In other words, the procedure 380 may send General command over the communication DTM is attached is arranged to scan DTM, and as soon as each is available, the device will provide sufficient information about the manufacturer and the device type, the procedure 380 may compare the information received from each device, with the criteria obtained in steps 384 and 386. In another embodiment, the procedure 380 may include, at least in some cases, the command is specific to the device type or manufacturer specified on the steps 384 and 386. In this case, the procedure 380 can reduce the load on the communication channel by using broadcast or multicast command or iterative sending commands to each possible address, waiting for an answer only on those devices that match the specified device type or brand of the manufacturer. Finally, the procedure 380 may communicate the information available about each detected external device or application infrastructure FDT at step 392.

In the above-described embodiments, execution of the scan function can C the go made with the possibility of scanning DTM automatically when it is created or initialized, or, in another embodiment, a user interacting with the application infrastructure FDT or outside. In particular, the external module 310 can provide the user with the function "Scan all". The function "Scan all" can be started by using the radio buttons, commands entered at the command prompt, voice command, or any other method available to the user interface. After selecting the function "Scan all" may run a scan each configured to scan DTM device each application infrastructure FDT on each server, if the external module 310 has established a connection with the specified configured to scan DTM device. External module 310 then may collect the desired information from each configured to scan DTM.

It is important that other options perform, based on the disclosure of the present invention can combine some elements of procedures 350 and 380, for example, to search for devices of a particular type that are within a certain range of addresses. It should also be noted that although the above described embodiments of the reference to an existing standard FDT, principles and algorithms outlined above, also apply to other versions of FDT, including those that may bitratrate in the future, and similar infrastructures for communication between the module and the physical device. In particular, infrastructure FDT can use a different platform than Windows. Therefore, FDT can use other technologies instead of (or in addition to) the COM and ActiveX, and can also override some of the interfaces used by the application infrastructure and DTM. It should be noted that embodiments of the described above can be applied to other platforms and interface definitions.

From the present description versed in engineering man clearly that is configured to scan DTM device (such as done with scanning DTM 300, 304, 312, 314 or 322 of the device) allows the developer or user of the application infrastructure FDT implement the object DTM, which includes the same functionality of a particular device and also provides a link between the specified device and the module without the need for explicit configuration of the object DTM and the address of the device. In other words, are designed to scan DTM greatly simplifies the configuration and management of devices in the infrastructure FDT and reduces the risk of human error by either the complete elimination of the configuration stage DTM device sootvetstvuyushiye, or, in other scenarios and options for implementation, by providing a list of discovered devices and/or addresses to the user. Moreover, some embodiments of the made with the possibility of scanning DTM devices allow the module to contact multiple physical devices through a single instance is configured to scan DTM device. Thus, representing one or more physical devices in a software infrastructure designed to scan DTM device provides a high level of independence, especially convenient for the effective management of complex systems (for example, the management processes at the production plant, with hundreds of field devices).

In addition, some embodiments of capable of scanning DTM devices allow one instance is configured to scan DTM device to support communication between the software (which may include one or more modules inside or outside infrastructure FDT) and multiple devices connected to multiple communication lines of different types. DTM has the same functionality can also be called capable of multiple scanning DTM. As noted above, capable of multiple scanned the Yu DTM can further reduce the number of objects DTM in the application infrastructure FDT. Moreover, capable of multiple scanning DTM provides a detection function, which is not limited to one line, or even a single communication Protocol.

Although the above text includes a detailed description of numerous different embodiments, it is necessary to understand that the scope of the present invention are determined by the volume of claims that are listed in the last part of this application, as well as equivalents used in it terms. The detailed description should be taken only as examples, and it does not describe every possible embodiment of because the description of each of the possible options would be impractical, if not impossible. Numerous alternative ways to perform can be implemented using existing technology or technology developed after the publication of this patent, these options are still included in the scope of the claims.

1. The communication method using the infrastructure, made in accordance with the FDT standard are required, with the device operating in environment management processes and having a communication connection with a communication line, including:
generating instance DTM device made with the possibility of scanning pre what is the specified device in the infrastructure FDT;
a communication connection this instance, is arranged to scan DTM device with a communication channel corresponding to the specified communication line;
scan the specified line to detect the specified device using the specified instance is configured to scan DTM; and
obtaining the address of the detected device is arranged to scan DTM.

2. The method according to claim 1, characterized in that it further includes:
the connection of the specified instance is configured to scan DTM, with application infrastructure; and
communication between the detected device and application infrastructure by made with the possibility
scan DTM using the obtained address of the discovered device.

3. The method according to claim 2, characterized in that it further includes:
save the address of the detected device in the memory;
the continuation of a memory address if the link becomes unavailable; and
restoring lines of communication between the device and the application infrastructure using the stored address in response to the appearance of the access line connection.

4. The method according to claim 1, characterized in that the connection of the specified instance has a capability is of generowania DTM with the communication channel comprises a connection between that instance and the communication DTM, which supports the communication Protocol used by the communication line.

5. The method according to claim 4, characterized in that the scanning lines of communication includes:
sending the communication DTM message that includes a command addressed to the device; and
receiving a response from the device, and the communication DTM forwards the response from the device it is configured to scan DTM.

6. The method according to claim 1, characterized in that it further includes receiving at least one of the parameters, such as device type or brand of the manufacturer, before scanning lines;
moreover, the scanning line includes a detection device corresponding to at least one of the parameters, such as device type or brand of the manufacturer.

7. The method according to claim 1, characterized in that the scanning lines of communication includes obtaining an address range and a detection device having the address contained in the address range.

8. The method according to claim 1, characterized in that the scanning lines of communication includes at least one of the following, namely sensors or scanning signals for each address, available on-line.

9. The method according to claim 1, characterized in that the scanning lines of communication on what comprises sending at least one of the following messages, namely broadcast or multicast messages to multiple addresses associated with the communication line.

10. The method according to claim 1, characterized in that the line supports the communication Protocol HART^®; and the scan lines of communication involves sending HART-command "0" for each of the available address.

11. The method according to claim 1, characterized in that it further includes obtaining data about the status of the detected devices.

12. The method according to claim 1, characterized in that it further includes:
the scanning line for detecting a second device; and determining the address of the second device is configured to scan the DTM, and the address of the first device is different from the address of the second device.

13. The method according to claim 1, characterized in that it further includes:
the connection of the specified instance is configured to scan the DTM with the second communication channel corresponding to the second communication line;
the scanning of the second line to detect a second device having a communication connection with the second communication line; and
removing the address of the second device is configured to scan DTM.

14. The method according to claim 1, characterized in that it further includes establishing a relationship between the detected device and the software module is the exploits of the specified instance made with the possibility of scanning DTM, without the configuration of the specified instance of the DTM and the address of the device.

15. Manager device types (DTM) of type "device", made with the possibility of scanning and working in infrastructure applications made in accordance with the standard FDT and DTM represents at least one device operating in environment management processes containing:
function module to maintain the functions relating to at least one device;
the first interface, coupled to the functional module to interact with the application infrastructure;
a second interface connected to the functional module to communicate with the communication channel corresponding to the communication line, with which at least one device has a communication connection; and a scan function that is connected with the second interface to detect at least one device connected to the communication line, and for establishing communication between the network application and at least one device detected by made with the possibility of scanning DTM.

16. DTM indicated in paragraph 15, characterized in that it further includes a permanent memory for storing addresses of at least one detected device.

17. DTM indicated in paragraph 15, characterized in that the communication DTM, working in the infrastructure application FDT, provides a communication channel.

18. DTM indicated in paragraph 15, wherein the second interface is additionally connected with the second communication channel corresponding to the second communication line to which is attached at least one device and the first communication line supports a first communication Protocol and the second communication line supports the second communication Protocol; when the scan function is connected to the second interface for additional detection of at least one device connected with the second line.

19. DTM indicated in paragraph 15, wherein the first communication line supports communication Protocol HART^®and the second communication line supports communication Protocol Foundation™ Fieldbus H1.

20. DTM indicated in paragraph 15, characterized in that the functional module performs at least one of the following functions: calibration, diagnostics, maintenance, or testing.

21. DTM indicated in paragraph 15, characterized in that it further includes a memory for saving at least one of the following options, namely the device type, brand, manufacturer or range of addresses, and the scanning function detects at least one device corresponding to at least one of the stored parameters, such as device type, brand of the manufacturer, or range the hell is representing.

22. How to communicate with the device, network-management processes, including:
the connection with the communication channel using the communication Protocol instance DTM of type device which has a capability of scanning and working in infrastructure applications made in accordance with the standard FDT;
use is made with the possibility of scanning DTM for scanning of multiple addresses associated with the communication channel; and detecting one or more compatible devices configured to scan DTM and associated with the communication channel.

23. The method according to item 22, characterized in that it further includes establishing communication between the one or more discovered devices and at least one management application process, or by the asset management application associated with the application infrastructure FDT.

24. The method according to item 22, characterized in that it further includes:
generating a list of detected devices, each of which records includes at least the address of the detected device; and transmit this list to the user interface via the network application FDT.

25. The method according to item 22, characterized in that it further includes obtaining the address range from the user interface, each and the set of addresses, scanned performed with scanning DTM is within the specified address range.

26. The method according A.25, characterized in that it further includes obtaining data about the brand of the manufacturer from the user interface, and detecting one or more devices includes comparing the received data about the brand of the manufacturer with information about the brand manufacturer, reported by each device in the specified address range.

27. The method according to item 22, characterized in that it further includes:
assigning an identifier to each detected device;
data about the ID of each detected device application associated with the application infrastructure FDT; and
data transfer between the application and each discovered device based on the assigned identifier.