System and method for implementing safety instrumented systems in a fieldbus architecture

• US 7,486,999 B2
• Filed: 01/22/2007
• Issued: 02/03/2009
• Est. Priority Date: 08/21/1997
• Status: Expired due to Fees

• Current Assignee: Fieldbus Foundation (FieldComm Group, Inc.)
• Original Assignee: Fieldbus Foundation (FieldComm Group, Inc.)
• Inventors: Gabler, John Carl, Duffy, Joseph D., Glanzer, David A., Mitschke, Stephen B., Berge, L. Jonas F., Ramachandran, Ram
• Primary Examiner(s): DeCady; Albert
• Assistant Examiner(s): CHANG, SUNRAY
• Application Number:
  US11/656,883
• Publication Number:
  US 20070213853A1
• Time in Patent Office: 743 Days
• Field of Search: 700 2- 4, 700/7, 700 12- 37, 700/83, 700/86, 702/122, 702/182, 709223-227, 710/21, 710 67- 72
• US Class Current: 700/79
• CPC Class Codes: G05B 11/01 electric
• CPC Class Codes: G05B 15/02 electric
• CPC Class Codes: G05B 19/042 using digital processors G05B19/05 takes precedence
• CPC Class Codes: G05B 2219/13127 Hybrid sfc for description of sequence, ladder diagram for conditions, interlock
• CPC Class Codes: G05B 2219/15068 SBC single board computer, UCM universal control module
• CPC Class Codes: G05B 2219/23256 Hybrid programming, part sequence, part continuous
• CPC Class Codes: G05B 2219/25085 Several function expansion units for master, main unit, universal system
• CPC Class Codes: G05B 2219/25428 Field device
• CPC Class Codes: G05B 2219/31118 Universal interface between asi and fieldbus, for any fielddevice
• CPC Class Codes: G05B 9/02 electric
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

An apparatus, system and process is provided for communicating safety-related data, over an open system, from a sender to a receiver. Safety-related components, including function blocks, flexible function blocks, resource blocks and transducer blocks, as well as, safety-related objects are provided. Also, an extended safety-related protocol provides for authenticating communications between safety-related components over an existing black channel, such as one using a fieldbus Architecture.

Claims

1. A system for permitting interoperability between safety and non-safety devices in a block-oriented open control system comprising:

a first device comprising

a memory, which includes at least one safety component, the safety component including a safety resource block and a safety function block, the safety resource block configured to uniquely identify a safety resource in the first device and the safety function block configured to process parameters associated with the safety resource to produce an output message, the safety component configured to store at least one safety parameter, the safety component configured to lock to prevent a change to the safety parameter while the safety component is online, the safety component further configured to utilize a virtual communication relationship for communication with a second component and to communicate using an extended safety protocol including maintain an expected sequence number and check a received sequence number against the expected sequence number; and

a processor, operably connected to the memory, wherein the processor executes the safety component based on a system schedule;

a second device including a non-safety component;

a first medium attachment unit, coupled for communication to the safety component, the first medium attachment unit configured to translate an input message from a transmission medium to the safety component and the output message from the safety function block to the transmission medium using an extended safety protocol; and

a second medium attachment unit, coupled for communication to the non-safety component, the second medium attachment unit configured to translate messages between the transmission medium and the non-safety component without an extended safety protocol.

2. A system according to claim 1 wherein the safety component is further configured to deny write access while the safety component is locked.

3. A system according to claim 2 wherein the safety component is further configured to accept a read request communicated without the extended safety protocol.

4. A system according to claim 3 wherein the safety component is configured to accept the read request while the safety component is locked.

5. A system according to claim 1 wherein the safety component includes a transducer block configured to process data received from or destined for a field device coupled for communication to the safety component.

6. A system according to claim 1 wherein the safety component is configured to communicate with a second safety component using the extended safety protocol.