Apparatus and method for advanced alarming in field device protocols

• US 9,448,556 B2
• Filed: 10/22/2010
• Issued: 09/20/2016
• Est. Priority Date: 10/22/2010
• Status: Active Grant

• Current Assignee: Honeywell International Inc.
• Original Assignee: Honeywell International Inc.
• Inventors: Schrier, Matthew R., Bandekar, Raj
• Primary Examiner(s): Lo, Kenneth M
• Assistant Examiner(s): Lin, Jason
• Application Number:
  US12/910,603
• Publication Number:
  US 20120101600A1
• Time in Patent Office: 2,160 Days
• Field of Search: 700/80, 700/21, 700/12, 700/17, 340/506, 340/539.1, 340/511, 434/118
• US Class Current: 1/1
• CPC Class Codes: G05B 19/048 Monitoring; Safety
• CPC Class Codes: G05B 2219/25428 Field device
• CPC Class Codes: G05B 2219/31121 Fielddevice, field controller, interface connected to fieldbus
• CPC Class Codes: G05B 2219/31467 Display of operating conditions of machines, workcells, selected programs
• CPC Class Codes: G05B 23/0216 Human interface functionality, e.g. monitoring system providing help to the user in the selection of tests or in its configuration
• CPC Class Codes: G05B 23/027 Alarm generation, e.g. communication protocol; Forms of alarm

Abstract

A method includes providing an identification of multiple device-specific parameters to a user, where the device-specific parameters are associated with a field device. The method also includes receiving a selection of at least one of the device-specific parameters from the user. The method further includes, upon receipt of the selection of the at least one device-specific parameter, providing an identification of multiple bits associated with the at least one selected device-specific parameter to the user. The method also includes receiving a selection of at least one of the bits from the user. The method further includes saving the at least one selected device-specific parameter and the at least one selected bit as a custom alarm condition. A selected criticality option or a selected priority option can be saved as part of the custom alarm condition. The custom alarm condition can be loaded into a controller of a process control system.

Claims

1. A method comprising:

providing an identification of multiple device-specific parameters to a user, the device-specific parameters associated with a legacy field device that is configured to support a set of field device protocol standard alarms without user-selected device-specific parameters in accordance with a legacy version of a field device protocol but is incapable of supporting new alarm parameters associated with newer versions of the field device protocol, the set of field device protocol standard alarms providing a set of diagnostic notifications;

receiving a selection of at least one of the device-specific parameters from the user, the at least one selected device-specific parameter comprising at least one diagnostic indicator of the legacy field device;

upon receipt of the selection of the at least one device-specific parameter, providing an identification of multiple bits associated with the at least one selected device-specific parameter to the user, the multiple bits corresponding to multiple states of the legacy field device;

receiving a selection of at least one of the bits from the user;

saving the at least one selected device-specific parameter and the at least one selected bit as a custom alarm condition, the custom alarm condition defining a custom diagnostic alarm that is different than the diagnostic notifications in the protocol standard alarms; and

generating the custom diagnostic alarm when the custom alarm condition occurs.

2. The method of claim 1, further comprising:

providing an identification of multiple criticality options for the custom alarm condition to the user; and

receiving a selection of one of the criticality options from the user;

wherein the selected criticality option is saved as part of the custom alarm condition.

3. The method of claim 1, further comprising:

providing an identification of multiple priority options for the custom alarm condition; and

receiving a selection of one of the priority options from the user;

wherein the selected priority option is saved as part of the custom alarm condition.

4. The method of claim 1, further comprising:

receiving from the user an indication of whether to enable or disable the custom alarm condition.

5. The method of claim 4, further comprising:

after the user has enabled the custom alarm condition, initiating a loading of the custom alarm condition into a controller.

6. The method of claim 5, wherein the custom alarm condition is loaded into the controller in conjunction with a loading of a configuration of the legacy field device into the controller.

7. The method of claim 5, wherein the custom alarm condition is loaded into the controller during a run-time of the controller.

8. The method of claim 1, wherein the legacy field device is configured to support at least one version of a FOUNDATION Fieldbus protocol.

9. The method of claim 1, further comprising:

monitoring a bitstring to determine changes to the legacy field device, wherein the bitstring includes at least one of;

simple parameters, record elements, or array elements,

wherein the at least one selected device-specific parameter includes a diagnostic indicator created by a vendor or a device manufacturer of the legacy field device.

10. The method of claim 1, wherein the selection of the at least one device-specific parameter comprises a selection of a plurality of device-specific parameters, and

wherein the selection of the at least one of the bits comprises a selection of a first bit corresponding to a state of the legacy field device and a second bit corresponding to another state of the legacy field device.

11. An apparatus comprising:

a processing unit configured to;

provide an identification of multiple device-specific parameters to a user, the device-specific parameters associated with a legacy field device that is configured to support a set of field device protocol standard alarms without user-selected device-specific parameters in accordance with a legacy version of a field device protocol but is incapable of supporting new alarm parameters associated with newer versions of the field device protocol, the set of field device protocol standard alarms providing a set of diagnostic notifications;

receive a selection of at least one of the device-specific parameters from the user, the at least one selected device-specific parameter comprising at least one diagnostic indicator of the legacy field device;

upon receipt of the selection of the at least one device-specific parameter, provide an identification of multiple bits associated with the at least one selected device-specific parameter to the user, the multiple bits corresponding to multiple states of the legacy field device; and

receive a selection of at least one of the bits from the user; and

a memory configured to store the at least one selected device-specific parameter and the at least one selected bit as a custom alarm condition, the custom alarm condition defining a custom diagnostic alarm that is different than the diagnostic notifications in the protocol standard alarms,

wherein the processing unit is configured to generate the custom diagnostic alarm when the custom alarm condition occurs.

12. The apparatus of claim 11, wherein:

the processing unit is further configured to;

provide an identification of multiple criticality options for the custom alarm condition to the user; and

receive a selection of one of the criticality options from the user; and

the memory is configured to store the selected criticality option as part of the custom alarm condition.

13. The apparatus of claim 11, wherein:

the processing unit is further configured to;

provide an identification of multiple priority options for the custom alarm condition; and

receive a selection of one of the priority options from the user; and

the memory is configured to store the selected priority option as part of the custom alarm condition.

14. The apparatus of claim 11, wherein the processing unit is further configured to receive from the user an indication of whether to enable or disable the custom alarm condition.

15. The apparatus of claim 14, wherein the processing unit is further configured, after the user has enabled the custom alarm condition, to initiate a loading of the custom alarm condition into a controller.

16. The apparatus of claim 11, wherein the legacy field device is configured to support at least one version of a FOUNDATION Fieldbus field device.

17. A non-transitory computer readable storage medium embodying a computer program, the computer program comprising computer readable program code for:

providing an identification of multiple device-specific parameters to a user, the device-specific parameters associated with a legacy field device that is configured to support a set of field device protocol standard alarms without user-selected device-specific parameters in accordance with a legacy version of a field device protocol but is incapable of supporting new alarm parameters associated with newer versions of the field device protocol, the set of field device protocol standard alarms providing a set of diagnostic notifications;

receiving a selection of at least one of the device-specific parameters from the user, the at least one selected device-specific parameter comprising at least one diagnostic indicator of the legacy field device;

upon receipt of the selection of the at least one device-specific parameter, providing an identification of multiple bits associated with the at least one selected device-specific parameter to the user, the multiple bits corresponding to multiple states of the legacy field device;

receiving a selection of at least one of the bits from the user;

saving the at least one selected device-specific parameter and the at least one selected bit as a custom alarm condition, the custom alarm condition defining a custom diagnostic alarm that is different than the diagnostic notifications in the protocol standard alarms; and

generating the custom diagnostic alarm when the custom alarm condition occurs.

18. The non-transitory computer readable storage medium of claim 17, further comprising computer readable program code for:

providing an identification of multiple criticality options for the custom alarm condition to the user;

receiving a selection of one of the criticality options from the user; and

saving the selected criticality option as part of the custom alarm condition.

19. The non-transitory computer readable storage medium of claim 17, further comprising computer readable program code for:

providing an identification of multiple priority options for the custom alarm condition;

receiving a selection of one of the priority options from the user; and

saving the selected priority option as part of the custom alarm condition.

20. The non-transitory computer readable storage medium of claim 17, further comprising computer readable program code for:

receiving from the user an indication of whether to enable or disable the custom alarm condition.

21. The non-transitory computer readable storage medium of claim 20, further comprising computer readable program code for:

after the user has enabled the custom alarm condition, initiating a loading of the custom alarm condition into a controller.

22. The non-transitory computer readable storage medium of claim 17, wherein the legacy field device is configured to support a legacy version of a FOUNDATION Fieldbus protocol that does not define a standard way to extract and display parameterized diagnostic information including a diagnostic indicator of the legacy field device created by a vendor or a device manufacturer of the legacy field device.