System and method for accessing and configuring field devices in a process control system using distributed control components

• US 8,108,200 B2
• Filed: 05/20/2008
• Issued: 01/31/2012
• Est. Priority Date: 05/20/2008
• Status: Active Grant

• Current Assignee: Honeywell International Inc.
• Original Assignee: Honeywell International Inc.
• Inventors: Anne, Gowtham, Maranat, Prashant
• Primary Examiner(s): Rodriguez, Paul
• Assistant Examiner(s): OCHOA, JUAN CARLOS
• Application Number:
  US12/123,680
• Publication Number:
  US 20090292524A1
• Time in Patent Office: 1,351 Days
• Field of Search: 703/23, 709/230, 709/237
• US Class Current: 703/23
• CPC Class Codes: G05B 19/0426 Programming the control sequence
• CPC Class Codes: G05B 2219/25428 Field device
• CPC Class Codes: G05B 2219/31132 FDT interfacing profibus field device drivers DTM with engineering tool
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces

Abstract

A system includes a client and an interface component. The client includes (i) a device manager associated with a field device in a process control system and (ii) a first emulator configured to emulate a communication manager. The device manager defines a user interface associated with the field device. The interface component includes (i) a second emulator configured to emulate the device manager and (ii) the communication manager. The communication manager is configured to communicate with the field device over a communication link using a specified protocol. The client is physically separated from the interface component. The communication manager could represent a communication Device Type Manager (DTM), and the device manager could represent a device DTM. Also, the first emulator could emulate at least some functions of the communication DTM, and the second emulator could emulate at least some functions of the device DTM.

Claims

1. A method comprising:

receiving from an operator a first request to configure or access a field device in a process control system;

instantiating a device manager and a communication manager associated with the field device in response to the first request, the device manager configured to define the field device'"'"'s configuration, the communication manager configured to define an interface for communicating with the field device;

generating a user interface for interacting with the field device for presentation to the operator, the user interface generated using the device manager;

obtaining a second request associated with the field device at the device manager using the user interface;

providing the second request to a first emulator, the first emulator emulating the communication manager;

providing the second request from the first emulator to a second emulator, the second emulator emulating the device manager; and

providing the second request from the second emulator to the communication manager, the communication manager configured to communicate the second request to the field device over a communication link using a specified protocol.

2. The method of claim 1, wherein:

the communication manager comprises a communication Device Type Manager (DTM);

the device manager comprises a device DTM;

the first emulator emulates at least some functions of the communication DTM; and

the second emulator emulates at least some functions of the device DTM.

3. The method of claim 1, wherein providing the second request from the first emulator to the second emulator comprises:

providing the second request from the first emulator to a server; and

providing the second request from the server to the second emulator.

4. The method of claim 1, wherein a first device comprising the device manager and the first emulator is physically separated from a second device comprising the second emulator and the communication manager.

5. The method of claim 4, the method comprising:

instantiating the device manager at the first device and linking the device manager and the first emulator; and

instantiating the communication manager at the second device and linking the communication manager and the second emulator.

6. The method of claim 1, wherein the second request is generated based on user input received through the user interface.

7. The method of claim 1, wherein:

the first emulator emulates multiple communication managers associated with multiple field devices; and

the second emulator emulates multiple device managers associated with the multiple field devices.

8. The method of claim 1, wherein the field device comprises at least one of:

a sensor and an actuator.

9. A system comprising:

a client comprising (i) a device manager associated with a field device in a process control system and (ii) a first emulator, the device manager configured to define the field device'"'"'s configuration; and

an interface component comprising (i) a second emulator configured to emulate the device manager and (ii) a communication manager configured to define an interface for communicating with the field device over a communication link using a specified protocol, the first emulator configured to emulate the communication manager;

wherein;

the client is configured to receive a first request to configure or access the field device from an operator, instantiate the device manager in response to the first request, and generate a user interface for interacting with the field device for presentation to the operator, the client configured to generate the user interface using the device manager;

the client is also configured to obtain a second request associated with the field device at the device manager using the user interface, provide the second request from the device manager to the first emulator, and communicate the second request from the first emulator to the second emulator;

the interface component is configured to receive the second request at the second emulator and provide the second request from the second emulator to the communication manager, the communication manager configured to communicate the second request to the field device; and

the client is physically separated from the interface component.

10. The system of claim 9, wherein:

the communication manager comprises a communication Device Type Manager (DTM);

the device manager comprises a device DTM;

the first emulator is configured to emulate at least some functions of the communication DTM; and

the second emulator is configured to emulate at least some functions of the device DTM.

11. The system of claim 9, further comprising:

a server configured to receive the second request from the first emulator and to provide the second request to the second emulator.

12. The system of claim 9, wherein the second request is generated by the device manager based on user input received through the user interface.

13. The system of claim 9, wherein the second request comprises one of:

a request to configure the field device and a request for information from the field device.

14. The system of claim 9, wherein:

the client is configured to establish an active link between the device manager and the first emulator; and

the interface component is configured to establish an active link between the second emulator and the communication manager.

15. The system of claim 9, wherein:

the client comprises multiple device managers associated with multiple field devices;

the system comprises multiple interface components that include multiple second emulators and multiple communication managers, the multiple communication managers configured to communicate with the multiple field devices; and

the client is physically separated from the multiple interface components and at least some of the interface components are physically separated from each other.

16. An apparatus comprising:

a device manager associated with a field device in a process control system, the device manager configured to define the field device'"'"'s configuration and a user interface for interacting with the field device; and

a first emulator configured to emulate a communication manager that defines an interface for communicating with at least the field device over a communication link using a specified protocol;

wherein the apparatus forms at least part of a first physical device;

wherein the apparatus is configured to receive a first request to configure or access the field device from an operator, instantiate the device manager in response to the first request, and generate the user interface for presentation to the operator, the apparatus configured to generate the user interface using the device manager;

wherein the apparatus is also configured to obtain a second request associated with the field device at the device manager using the user interface and provide the second request from the device manager to the first emulator; and

wherein the first emulator is configured to receive the second request from the device manager and to provide the second request to a second emulator forming at least part of a second physical device, the second emulator configured to provide the second request to the communication manager.

17. The apparatus of claim 16, wherein the second emulator is configured to emulate the device manager and to communicate with the communication manager.

18. The apparatus of claim 16, wherein the first emulator is configured to communicate with the second emulator through a server.

19. The apparatus of claim 16, wherein the second request is generated by the device manager based on user input received through the user interface.

20. The apparatus of claim 16, wherein the second physical device is physically separated from the first physical device.