[go: up one dir, main page]

US20040194101A1 - Flexible function blocks - Google Patents

Flexible function blocks Download PDF

Info

Publication number
US20040194101A1
US20040194101A1 US10/453,596 US45359603A US2004194101A1 US 20040194101 A1 US20040194101 A1 US 20040194101A1 US 45359603 A US45359603 A US 45359603A US 2004194101 A1 US2004194101 A1 US 2004194101A1
Authority
US
United States
Prior art keywords
block
function block
blocks
flexible
flexible function
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/453,596
Other languages
English (en)
Inventor
David Glanzer
Stephen Mitschke
William Hawkins
Michael Le Suire
Sergio Tateishi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fieldbus Foundation
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US08/916,178 external-priority patent/US6424872B1/en
Priority claimed from US09/598,697 external-priority patent/US6826590B1/en
Application filed by Individual filed Critical Individual
Priority to US10/453,596 priority Critical patent/US20040194101A1/en
Priority to US10/826,576 priority patent/US6999824B2/en
Priority to EP04776293.5A priority patent/EP1629332B1/en
Priority to CN201110176258.3A priority patent/CN102323785B/zh
Priority to CNA200480015600XA priority patent/CN1802614A/zh
Priority to PCT/US2004/017746 priority patent/WO2004109415A1/en
Publication of US20040194101A1 publication Critical patent/US20040194101A1/en
Priority to US11/240,939 priority patent/US7167762B2/en
Priority to US11/420,704 priority patent/US7272457B2/en
Priority to US11/656,883 priority patent/US7486999B2/en
Assigned to FIELDBUS FOUNDATION reassignment FIELDBUS FOUNDATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: VON LE SUIRE, MICHAEL, TATEISHI, SERGIO HIDEKI, HAWKINS, WILLIAM M., GLANZER, DAVID A., MITSCHKE, STEPHEN B.
Priority to US11/900,349 priority patent/US20080004727A1/en
Priority to US12/340,212 priority patent/US20090105849A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B15/00—Systems controlled by a computer
    • G05B15/02—Systems controlled by a computer electric
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/05—Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
    • G05B19/056—Programming the PLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/62—Establishing a time schedule for servicing the requests
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/10—Plc systems
    • G05B2219/13—Plc programming
    • G05B2219/13101—Function block instance, only one function block exists, several instances
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/10—Plc systems
    • G05B2219/13—Plc programming
    • G05B2219/13127—Hybrid sfc for description of sequence, ladder diagram for conditions, interlock
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/10—Plc systems
    • G05B2219/15—Plc structure of the system
    • G05B2219/15068—SBC single board computer, UCM universal control module
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/23—Pc programming
    • G05B2219/23256—Hybrid programming, part sequence, part continuous
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/25—Pc structure of the system
    • G05B2219/25085—Several function expansion units for master, main unit, universal system
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/25—Pc structure of the system
    • G05B2219/25428—Field device
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31118—Universal interface between asi and fieldbus, for any fielddevice

Definitions

  • the present invention relates to automatic control system architecture. More particularly, the present invention relates to extending the automatic control system architecture described in the '892 patent and '697 application to include new “Flexible Function Blocks” which increase application capability to include complex discrete/hybrid/batch and PLC applications.
  • FOUNDATIONTM fieldbus specifies a lower speed fieldbus (H 1 ) optimized for process control, and a High Speed Ethernet (HSE) fieldbus backbone for high performance control, subsystem integration, and management information systems integration.
  • H 1 lower speed fieldbus
  • HSE High Speed Ethernet
  • Exemplary Hi and HSE are described in the '892 patent, and the '697 application, respectively. Since FOUNDATIONTM fieldbus is an open and interoperable, distributed control architecture, control devices from different vendors interoperate on the H 1 or HSE fieldbus and share the control functions (e.g., control is distributed into the fieldbus devices).
  • H 1 provides the open and interoperable solution for field level control capability and integration
  • HSE provides the open and interoperable solution for distributed control on a very high performance communication system typically called a fieldbus control “backbone” network.
  • the HSE control backbone aggregates information from lower speed control devices, e.g., the H 1 devices and other control devices, which is used in supervisory and advanced control applications.
  • the HSE control backbone aggregates data from high-speed control devices, e.g., HSE devices and other subsystems, and provides access/change of H 1 and HSE control information by control system computers.
  • Embodiments described herein overcome the shortcomings described above and otherwise. Embodiments satisfy the above-described needs. Embodiments provide a new and improved control system architecture providing a new, end-user configurable function blocks, thus eliminating the need for expensive and difficult to maintain custom control software and special I/O gateways in discrete/hybrid/batch and PLC applications.
  • the embodiments described herein are collectively referred to herein as the “Flexible Function Block” (FFB).
  • FFFB Flexible Function Block
  • an apparatus for operating in an open control system that includes a memory, which includes system management data and a flexible function block, a processor, operably connected to the memory, and a medium attachment unit, which translates input messages and output messages between the processor and a transmission medium.
  • the system management data includes a system schedule
  • the flexible function block includes end-user configured parameters and an end-user configurable algorithm computer program
  • the processor executes the flexible function block based on the system schedule.
  • a system for permitting interoperability between devices including a plurality of devices, at least one device including a resource block and a flexible function block and a medium attachment unit, operably connected to the flexible function block.
  • the resource blocks uniquely identify each device, the flexible function block processes parameters to produce an output message, and the medium attachment unit translates an input message from a transmission medium to the flexible function block and the output message from the flexible function block to the transmission medium.
  • the apparatus includes a user layer, which includes encapsulated flexible function block to provide functionality, a physical layer, which translates messages from a transmission medium into a suitable format for the user layer and from the user layer into a signal for transmission on the transmission medium, and a communication stack, connected to the user layer and the physical layer.
  • the communication stack includes a data link layer and an application layer.
  • the data link layer controls the transmission of messages onto the transmission medium.
  • the application layer allows the user layer to communicate over the transmission medium.
  • a memory for storing data for access by an application framework operating in a device within a control system.
  • the memory includes a data structure stored in the memory, the data structure including a resource block, which makes hardware specific characteristics of the device electronically readable, an encapsulated flexible function block, and at least one transducer block.
  • the flexible function block includes end-user configured program and parameters and the at least one transducer block controls access to the flexible function block.
  • FIG. 1 is an overview of an extended control system.
  • FIG. 2 shows the Open Systems Interconnect layered communication model as compared to the communication model of the present invention.
  • FIG. 3 illustrates a hardware embodiment of a field device.
  • FIG. 4 summarizes the virtual communication relationships provided by the Fieldbus Access Sublayer.
  • FIG. 5 illustrates two devices interconnected via the communication services.
  • FIG. 6 illustrates an object dictionary
  • FIG. 7 illustrates the virtual communication devices within the communication model of the present invention.
  • FIG. 8 illustrates a function block application structure within a field device.
  • FIG. 11 illustrates examples of parameters interconnected for a single loop.
  • FIG. 13 illustrates a flexible function block with user configurable inputs, user configurable outputs, and a user configurable algorithm.
  • FIG. 14 illustrates an application using standardized and flexible function blocks.
  • FIG. 15 is a block diagram illustrating an example of an application using standardized and flexible function blocks.
  • the control system can support a variety of field devices, including sensors and actuators, or high speed field devices, such as cell control, motors, drives and remote input/output (I/O).
  • the Flexible Function Blocks enable the number and type of function block inputs/outputs (I/O) and the function block algorithm to be configured by the end user.
  • FIGGS. 1-12 A description of an embodiment of the control system is first provided below (FIGS. 1-12), followed by a description of the Flexible Function Blocks (FIGS. 13-15)
  • the 31.25 kbit/s bus is generally used for process control applications, such as temperature, level, and flow control.
  • the 1.0 Mbit/s bus and 2.5 Mbit/s bus are usually used for high speed applications.
  • Devices operating on 1.0 Mbit/s bus and 2.5 Mbit/s buses are usually self-powered or draw power from a separate power bus in the fieldbus cable (i.e., 4 wire cable), however, they can also be powered directly from the fieldbus.
  • link master 105 devices there are several link master 105 devices operating on the same bus 120 . When these link master 105 devices are activated, these link master 105 devices bid for the responsibility of becoming the link active scheduler 100 .
  • the link master 105 device which becomes the link active scheduler 100 is the device with the lowest network address.
  • a particular device may be the “preferred” link master. In which case, when the system is activated the link master 105 with the lowest network address would assume the responsibilities of the link active scheduler 100 . Then, the “preferred” link master 105 would send a message to the link active scheduler 100 directing it to transfer control. Upon receipt of the message, the link active scheduler 100 would transfer control to the preferred link master 105 .
  • bidding process there are a variety of ways to conduct the bidding process.
  • one type of bidding process is shown in U.S. Pat. No. 5,526,358, issued Jun. 11, 1996, which is hereby incorporated by reference.
  • the bidding process is also conducted if the link active scheduler 100 controlling a bus 120 malfunctions or is removed.
  • the physical layer (PHY) 200 and the communications stack 205 are derived from the Open Systems Interconnect (OSI) model.
  • the physical layer (PHY) 200 is the same as OSI layer 1, and the communications stack 205 corresponds to OSI layers 2 and 7.
  • the user layer 235 is not defined by the OSI model.
  • the physical layer 200 and communications stack 205 may be derived from a variety of different networking standards, such as Transmission Control Protocol/Internet Protocol (TCP/IP) and UNIX. A detailed description of each of these layers follows.
  • FIG. 2 shows a preferred communications stack 205 .
  • the communication stack 205 includes the data link layer 210 , the fieldbus access sublayer 220 and the fieldbus message specification 230 .
  • the data link layer is the same as OSI layer 2.
  • the fieldbus access sublayer 220 and fieldbus message specification 230 are sublayers within the OSI application layer, OSI layer 7.
  • the communications stack 205 does not use layers 3-6. The layers of the communications stack 205 are described below.
  • the data link layer 210 controls transmission of messages onto the bus 120 from a link active scheduler 100 , link master device 105 or basic device 110 based the instructions of a network controller or the link active scheduler 100 .
  • the data link layer 210 is a subset of the IEC and ISA data link layer standard.
  • the link active scheduler 100 broadcasts the changes to the live list to all field devices. This allows each field device to maintain a current copy of the live list.
  • the link active scheduler 100 also schedules the communications from other field devices operating in the system.
  • the link active scheduler 100 coordinates the timing of each communication by issuing compel data messages at the scheduled times.
  • the requested field device broadcasts or publishes its data to the other field devices operating in the system.
  • the link active scheduler 100 also periodically broadcasts a time distribution message on the bus 120 so that all field devices have exactly the same data link time.
  • the time distribution message is a message which includes the data link time.
  • the data link time is the system time of the link active scheduler 100 .
  • the link active scheduler 100 grants permission to other field devices to use the bus 120 by issuing a pass token message to an individual device.
  • the individual field device receives the pass token, the field device is allowed to send messages until the field device is finished sending messages or until the maximum token hold time has expired, whichever is shorter.
  • the token hold time is the amount of time the device can send messages after receiving the pass token.
  • This method of control management is commonly called token passing control. A variety of techniques for implementing token passing control are well-known to those skilled in the art.
  • each device preferably includes an input snap 240 , processor 250 , memory 255 , contained parameters 257 and output snap 260 , and a medium attachment unit 612 , as shown in FIGS. 3 and 8.
  • the input snap 240 and output snap 260 protect parameter values from write access or other external interferences during execution of a block.
  • the processor 250 processes the execution of stored blocks as well as the algorithms and programs within the blocks.
  • the snapped parameters and contained parameters 257 are stored in the memory 255 .
  • the memory is preferably EEPROM or FLASHROM to permit programming of the device without the danger of losing data due to power loss.
  • the memory 255 may be ROM, RAM, or EPROM.
  • the fieldbus message specification 230 allows function block applications to send messages to each other using a standard set of message formats.
  • the fieldbus message specification 230 describes communication services 270 , message formats and protocol behavior needed to build a message for the user layer 240 , as illustrated in FIG. 5.
  • the formatting of fieldbus message specification messages is defined by a formal syntax description language called Abstract Syntax Notation 1 developed by International Circuit and Telephone Consultive Committee.
  • Object descriptions 280 are collected together in a structure called an object dictionary 281 , as illustrated in FIG. 6.
  • the object descriptions 280 are identified by an index number 285 .
  • An index number is a cross reference to the location where a particular object description is stored in memory.
  • Index zero 287 called the object dictionary header, provides a description of the dictionary itself and defines the first index for the object descriptions of the function block application 440 .
  • index numbers 1 - 255 define standard data types, such as Boolean, integer, floating point, bit string, and data structures, that are used to build all other object descriptions 280 .
  • the index numbers above index number 255 cross reference user layer object descriptions 280 .
  • the communication services 270 provide a standardized way for user layers 235 to communicate over the fieldbus.
  • Some examples of communication services 270 are context management service, object dictionary service, and variable access.
  • the context management services are used to establish and release virtual communication relationships with a virtual field device.
  • the object dictionary service allows the user layer 235 to access and change the object descriptions in a virtual field device.
  • the variable access services allow the user layer 235 to access and change variables associated with an object description.
  • the communication services 270 allow the fieldbus message specification 230 to communicate with the virtual field devices 310 , 400 in the user layer 235 .
  • a field device will have at least two virtual field devices, a network and system management virtual field device 310 and a user virtual field device 400 .
  • the network and system management virtual field device 310 typically stores network management data 320 and system management data 330 .
  • the network management data includes a network management information base (NMIB) object descriptions portion 322 and a NMIB object data portion 325 .
  • the system management data 330 includes a system management information base (SMIB) object descriptions portion 332 , and a SMIB object data portion 335 .
  • the user virtual field device 400 includes block object data 327 including block object description 326 .
  • the system and network management information base object descriptions 322 , 335 describe the system and network format for the system and network management information base object data 325 , 332 .
  • a few standard communication profiles are used to allow field devices to communicate and work together on the same transmission medium 120 .
  • the communication profiles preferably used in function block applications 440 are defined dependent on the field devices category or class. Also, to configure and maintain field devices and their function block application, a common file format is recommended.
  • the function block application 440 defines the field device's functionality.
  • a function block application 440 includes one or more resources 500 , as shown in FIG. 8.
  • a resource 500 is a logical subdivision within the software and/or hardware structure of a device.
  • a resource 500 has independent control of its operation, and its definition may be modified without affecting related resources.
  • a resource 500 is built of blocks and objects, such as: a resource block 510 , transducer blocks 520 , function blocks 530 , trend objects 560 , view objects 565 , link objects 570 , alert objects 585 , system time 601 , function block schedules 602 , and network traffic.
  • Network traffic includes scheduled and unscheduled traffic.
  • Each function block 530 uses input parameters according to a specific algorithm and internal set of contained parameters.
  • Input parameters are structured parameters composed of a value field and a status field. The data type specified for input parameters is dependent on the data type of its value field. The status field is identical for all input parameters.
  • Contained parameters may be used to provide values to the block algorithm.
  • the values of the contained parameters may be set by the manufacturer or as part of the configuration. The contained parameters may also be set during operation.
  • the input parameters and contained parameters are processed according to the specific algorithm to produce output parameters. The output parameters are available for use within the same function block 530 or by other function blocks 530 .
  • Transducer blocks 520 can preprocess and postprocess data between the function blocks and hardware 530 devices, such as sensors, actuators, and switches. Transducer blocks 520 can control access to the input/output devices through a device independent interface used by function blocks 530 . Transducer blocks 520 can also perform functions, such as calibration and linearization.
  • the link object 570 exchanges data between function blocks 530 within a resource 500 or between resources.
  • the data exchanged by the link object 570 can include process data or events.
  • the link object 570 can exchange trend report data or alert notification data.
  • a resource block 510 makes the hardware specific characteristics of a device accessible to the network.
  • the resource blocks 510 insulate the function blocks 530 from the resource hardware by including a set of implementation independent hardware parameters.
  • View objects 565 and trend objects 560 provide efficient access to parameter data within a function block application 440 .
  • View objects 565 allow groups of parameters to be accessed by executing a single communication request.
  • Trend objects 560 allow a collection of parameter samples to be reported in a single communications transfer.
  • Alert objects 585 support the reporting of events to an interface device and other field devices.
  • a function block 530 may send an alert message using an alert object 585 .
  • a significant event is an event that affects system operation.
  • the open system described herein can report its own errors, alerting operators to problems on a “real-time” basis.
  • the open system described herein improves productivity by reducing down time, and operator and plant safety.
  • System time 601 is provided by system management to function block applications (i.e., one or more resources) 440 for use in synchronizing operations between field devices.
  • Each device 100 , 105 , 110 keeps its own system time 601 .
  • Each device 100 , 105 , 110 uses its system time to control the execution of its internal function blocks. Time stamping of alarms, events, and trend information is based on system time 601 maintained by each device.
  • System management coordinates the execution of the function blocks 530 according to a system schedule.
  • the system schedule is a list of execution times for function blocks within a device. Additionally, the execution of a function block 530 may also be invoked by the completion of the execution of another function block 530 . System management is described in more detail later.
  • the application framework coordinates the communication between components internally and externally.
  • Internal communication means communication between function blocks 530 , regardless of whether they are in the same field device.
  • External communication means communication between field devices with function blocks 530 and field devices without function blocks.
  • the connection of these blocks by the application framework results in a modular system allowing the functionality of an application to be more extensible and portable.
  • the functionality is extensible in the sense additional functionality can easily be added to existing function.
  • the functionality is portable in the sense that functionality can easily be moved from one location in a system to another or even from one system to another.
  • FIG. 9 shows some examples of external communications. Specifically, FIG. 9 shows the communication of field devices 620 and a monitor device 650 , a temporary device 660 , and an interface device 670 . Unlike the field device 620 , the other devices 650 , 660 , 670 contain applications which are not implemented as function blocks.
  • the monitor device 650 is connected to the application framework, but does not have a network address.
  • a monitor device monitors communications on the network (e.g., a diagnostic tool may be a monitor device).
  • a temporary device 660 supports diagnostics and adjustment of parameter values.
  • An interface device 670 provides an operator interface, control applications, and/or configuration and diagnostic support.
  • a function block application 440 defines the functionality of the field device, and includes one or more resources 500 .
  • a resource is a logical subdivision within the software and/or hardware structure of the device.
  • function block applications 440 are generally implemented using multiple resources. As shown in FIG. 8, the resources 500 which make up a function block application 440 may be modeled as a set of blocks or objects coordinated to execute a related set of operations.
  • a block is a logical processing unit of software comprising a named copy of the block and parameter data structure specified by function type.
  • a named copy of the block is an encapsulated software processing unit, such as an algorithm or computer program.
  • the block is encapsulated to create a modular system with the flexibility for upgrades or improvements.
  • the software processing unit can include a computer program and parameters.
  • the software unit is designed to be independent of other blocks and perform a function which can be used in many different function block applications.
  • a block is identifiable by its class or subclass.
  • the class of a block indicates its parameters, and how the parameters affect the execution of the software processing unit.
  • a block class specifies the common attributes shared by all instances of the class, including block elements (e.g., input and output events, contained parameters, and common function) and association with resource function (e.g., alarm notifier and function block services).
  • block elements e.g., input and output events, contained parameters, and common function
  • resource function e.g., alarm notifier and function block services.
  • Each block subclass assumes all the parameters specified by the class, as well as the additional parameters attributed to the subclass.
  • Block classes are classified as elementary or composite.
  • a composite block class is one whose algorithm requires the invocation of functions and/or component blocks of the composite block.
  • An elementary block has a fixed algorithm and does not require the use of component functions or function blocks. Specific examples of elementary and composite blocks are described in detail later.
  • each device contains at least one function block application 440 .
  • a device To execute the function block application 440 , a device usually contains an input snap 240 , processor 250 , memory 255 , output snap 260 , and execution control 265 , as shown in FIG. 3, as well as the communications stack 205 and medium attachment unit 612 , as shown in FIG. 5.
  • the medium attachment unit 612 receives signals from other devices over the transmission medium 120 and translates the signals into a message for the processor 250 .
  • the medium attachment unit 612 converts or translates a message from the processor 250 into a signal for transmission over the transmission medium 120 , or a signal from the transmission medium 120 into a message for the processor 250 .
  • the input snap 240 , processor 250 , memory 255 , and output snap 260 are for executing the transducer blocks, function blocks, and resource block within a function block application. Specifically, the input snap 240 receives and holds input parameters. These input parameters may be constant or received from other function blocks.
  • the processor 250 executes or processes a software program or algorithm based on these input parameters and any contained or stored parameters. These parameters are discussed in more detail below.
  • the processor 250 is preferably a microprocessor or programmable logic array. Any software programs or parameters used by the processor 250 are stored in the memory 255 , which is preferably EEPROM or FLASHROM.
  • the functionality of the function block application 440 is only limited by the size of the memory 255 and the processing speed of the processor 250 .
  • the output of the processor 250 is then sent to an output snap 260 .
  • the input snap 240 and output snap 260 are responsible for protecting parameter values from external interferences, such as write access, while the processor 250 is executing. In other words, once the processor 250 begins processing the inputs, the input snap 240 and output snap 260 hold the inputs and outputs constant until the processing is complete. 1 3. Parameters
  • Parameters define the inputs, outputs, and data used to control block operation.
  • the parameters are accessible over the network.
  • An input parameter obtains its value from a source external to the block.
  • An input parameter may be linked to an output parameter of another block within its resource 500 or within another device.
  • An input parameter is an input variable or constant which is processed by the algorithm or program of a function block 530 .
  • An output parameter is a parameter which may be linked to an input parameter of one or more blocks.
  • Output parameters contain both value and status attributes.
  • the output status attribute indicates the quality of the parameter value generated.
  • a contained parameter is a parameter whose value is configured, calculated, or set by an operator or higher level device.
  • a contained parameter cannot be linked to another function block input or output, and therefore may not contain status attribute.
  • Each parameter is characterized by its identifiers, storage, usage, and relationship to other parameters.
  • Each parameter can be characterized by more than one identifier.
  • a parameter within a block is uniquely identified by its parameter device identification
  • a parameter within a system is uniquely identified by its device identification and tag.
  • Tags provide a unique symbolic reference to each block within the system.
  • the data type for a parameter is specified by its data type index.
  • the data type index is the object dictionary index of the data type.
  • the data type index specifies the machine independent syntax of the parameter.
  • the machine independent syntax of the parameter is an abstract syntax.
  • the user layer 235 encodes/decodes the data according to the transfer syntax rules in the fieldbus message specification 230 . Additionally, a variety of other parameters may also be stored in the object dictionary 281 and referenced by its object dictionary index number.
  • Parameter attributes may be classified as dynamic, static, or nonvolatile. Dynamic parameters are values calculated by the block algorithm and, therefore, do not need to be restored after power failure.
  • Static attributes are a specific, configured value that must be restored after a power failure.
  • An interface device 670 or temporary device 660 may write to static parameter attributes on an infrequent basis. Static parameter attributes can be tracked by a configuration device.
  • Non-volatile parameter attributes are written on a frequent basis and the last saved value must be restored by a device after power failure. Since the values of these parameter attributes are constantly changing, the values can be tracked by a configuration device.
  • the execution of a block involves input parameters, output parameters, contain parameters, and the algorithm or computer program stored within the block.
  • the execution time for a block's algorithm is defined as an attribute of the block. The length of execution time is dependent on the hardware and software implementation.
  • a function block application can achieve a variety of modes, such as out of service (O/S), initialization manual (IMan), local override (LO) manual (Man), automatic (Auto), cascade (Cas), remote-cascade (RCas) and remote output (ROut) mode.
  • O/S out of service
  • IMan initialization manual
  • LO local override
  • LO local override
  • RCas remote-cascade
  • ROut remote output
  • the determination of whether the block is able to achieve the desired mode is made by comparing the actual mode attribute and the target mode attribute.
  • the actual mode attribute reflects the mode of operation which the block is able to achieve.
  • the target mode attribute indicates what mode of operation is desired for the block.
  • the target mode is usually set by a control application or by an operator through a human interface application.
  • the block execution progresses and the outputs are generated. If alert conditions are detected, alarm and event output parameters are updated for reporting by an alert object.
  • the outputs are snapped making them available for external access. Prior to being snapped, only the previous values are available for external access.
  • a function block application 440 contains one or more resources, and a resource 500 includes one or more blocks.
  • a block is identifiable by its class or subclass.
  • the class of a block indicates its parameters, and how these parameters affect the execution of its algorithm or program.
  • the Resource Components Section provides the formal models for the preferred classes.
  • Preferred classes include a resource class, directory object class, block object class, parameter object class, link object class, alert object class, trend object class, view object class, domain object class, program invocation object class, and an action object class.
  • someone skilled in the art could define a system with more, less, or different classes.
  • the resource class defined in a preferred embodiment specifies the descriptive attributes of the resource.
  • the object dictionary of each resource contains a description of the components contained within the resource.
  • the resource class includes the following attributes: resource name, vendor name, model name, revision, logical status, physical status, and object dictionary.
  • the vendor name identifies the vendor of the software and/or hardware associated with the resource.
  • the model name specifies the model of the software and/or hardware associated with the resource.
  • the revision attribute is the revision level of the software and/or hardware associated with the resource.
  • the logical status attribute contains information about the communication functionality associated with the resource.
  • the physical status attribute gives a coarse summary of the hardware component associated with the resource.
  • the object dictionary contains the attributes of an object dictionary directory object, resource block, and other objects specific to the function block application 440 process. Each of these attributes are accessible through the fieldbus message specification 230 .
  • a directory object acts as a guide to other blocks and objects within a resource or function block application 440 .
  • the directory object contains a list of references to the other blocks and objects making up a resource or function block application 440 . This information may be read by an interface device or temporary device desiring to access objects in the object dictionary.
  • the directory object class is defined as including the following attributes: member identification; starting index of the static object dictionary; data type; sub-index entries; data length; usage; storage; list of valid values; initial value; and item identification.
  • the member identification attribute is the unique number which identifies the function of the directory.
  • the index is the index of the directory object in the object dictionary.
  • the various data types include meta type or type name.
  • Meta type indicates the object type.
  • Type name specifies the name of the data type of the object.
  • the sub index entries allow the attributes of a directory object to be accessed individually through the read and write service.
  • the data length attribute specifies the number of bytes reserved to represent the sub index values in the directory.
  • the usage attribute indicates that this is a contained object and may not be referenced by link objects for connection to function block parameters.
  • the storage attribute indicates whether the parameter is stored in static memory.
  • the list of valid values specifies the values permitted for the sub index attributes of the directory object.
  • the initial value specifies the initial value assigned to the sub index attributes of the object directory, and the item identification identifies the description of the object.
  • the block object preferred class specifies the characteristics common to the function blocks, transducer blocks, and resource blocks.
  • the block object class is defined by the following attributes: member identification; block index; data type; sub index; data length; usage; storage; list of parameters; list of valid values; and item identification.
  • the member identification identifies the function of the block.
  • the block index is the index of the block object in the object dictionary.
  • the data type includes the meta type and type name.
  • the meta type indicates the object type.
  • the type name specifies the name of the data structure of the block.
  • the sub index includes attributes, such as block tag, member identification, item identification, revision, profile, profile revision, execution time, period of execution, number of parameters, next block to execute, starting views, number of view 3 objects, and number of view 4 objects.
  • the data length attribute equals 62.
  • the list of parameters includes static revision, tag description, strategy, alert key, mode, and block error. The remaining attributes were described above.
  • the three sub-classes of the block object class used in a preferred embodiment are resource block objects, transducer block objects, and function block objects.
  • the resource block object defines hardware specific characteristics of its associated resource. Because the resource block object is a sub-class of the block object model, the resource block object assumes the list of parameters attributed to the block object, as well as its own additional attributes.
  • a resource block insulates the function blocks from the physical hardware by containing a set of implementation independent hardware parameters.
  • the resource block is manufacturer specific; and all its parameters are defined as contained.
  • Transducer blocks are defined to decouple function blocks from the local I/O functions required to read sensor hardware and command hardware. This permits the transducer block to execute as frequently as necessary to obtain data from sensors without burdening the function blocks that use the data. It also insulates the function block from the manufacturer specific characteristics of an I/O device.
  • the transducer block object is a subclass of the block object, and thus, it assumes all the attributes of the block class.
  • Function blocks represent the basic automation functions performed by a resource, such as an analog input or discrete output.
  • Function blocks are the primary means of defining monitoring and control in a function block application. They are designed to be as independent as possible of the specifics of I/O devices and the network. They work by processing input parameters and inputs from transducer blocks (or other function blocks) according to a specified algorithm and an internal set of contained parameters. They also produce output parameters and output to transducer blocks or the input of other function blocks.
  • a desired monitoring, calculation or control function may be provided.
  • the results from function block execution may be reflected in the output to a transducer block or to one or more output parameters that may be linked to other function blocks or directly to the device hardware.
  • Function blocks are a subclass of the object class.
  • the additional attributes defined in the function block subclass are the sub-index of execution time, period execution, number of parameters, next block to execute, and additional parameters.
  • the sub-index attribute defines the attributes of an object which may be individually accessed through read and write services by using the sub-index number with the object index number.
  • Sub-index numbers are defined based on Meta type.
  • the execution time parameter of the function block object denotes the time required for a function block to execute.
  • the execution time may be divided into three components: pre-processing (i.e., snap of parameter values); execution; and post-processing (i.e., block output values, alarm, and associated trend parameters are updated).
  • the block algorithm executed during the execution component is broken down into the following steps.
  • the algorithm determines the actual mode attribute of the mode parameter. This calculation will be based on the target mode and the status of attributes of the inputs as described above.
  • the algorithm calculates the setpoint, if the setpoint is defined for the function block. The calculation of the setpoint will be based on the actual mode, setpoint input parameters, such as cascade and remote-cascade, and any backward path input status.
  • the value of the controlled parameter, process variable may be used for setpoint tracking.
  • the resulting setpoint is shown in a setpoint parameter.
  • An example of a setpoint is the temperature setting of a thermostat (e.g., 72°). In other examples, the set point will change frequently.
  • the algorithm executes control or calculation of the algorithm to determine the value and status of the output parameters.
  • the conditions which determine the status attribute of output parameters.
  • the value attributes of the block's input parameters and contained parameters, the actual mode, and the working setpoint are used in this algorithm.
  • the calculation of actual mode and the use of actual mode in the algorithm account for the status of critical inputs.
  • the execution phase calculates the output parameters. This step applies only to output blocks, control blocks, and calculation blocks designed to be used in the cascade path.
  • the period of execution of a function block is typically scheduled on a periodic basis.
  • the period of execution is user specified based on control or monitoring requirements specific to an application.
  • the system management services coordinate the function block execution.
  • the management information base which includes the system schedule, is stored in its own resource in the device.
  • the function block period of execution is specified for a block in data link layer time.
  • the “number of parameters” attribute within the function block object is the total number of parameter objects associated with the function block, including the block object.
  • the “next block to execute” attribute of the function block object specifies the next function block within a device to execute to achieve minimum delay in execution within a device. If there is no next function block, then the next block to execute is zero. Thus, where multiple function blocks need to execute in series within a device, a user can specify the first function block to execute in the chain. Through the next block to execute attribute, the order of execution can be predetermined.
  • the “list of parameters” attribute of the function block object lists the input, output and contained parameters within a function block.
  • a preferred embodiment Based on the common parameters and the behavior, a preferred embodiment also defines the following subclasses of the function block subclass, including: input function block; output function block; control function block; and calculation function block.
  • the input function block subclass receives physical measurements or values from transducer block.
  • the input function block subclass includes a simulation parameter by which the transducer value and status may be over-ridden.
  • the input function block's other parameters preferably include: process variable; primary output; channel number; and additional parameters.
  • the output function block subclass acts upon input from other function blocks and forwards its results to an output transducer block.
  • the output function block subclass supports the back-calculation output parameter and simulate parameter.
  • the additional output function block attributes are: setpoint, simulate parameter, cascade input; back-calculation output; remote cascade in; remote cascade out; and channel number.
  • control function block subclass acts upon inputs from other function blocks to produce values that are sent to other control or output function blocks.
  • the additional attributes for the control function block are: primary output; back-calculation; process variable; setpoint; primary input; cascade input; remote-cascade in; remote-output in; back-calculation output; remote-cascade out; remote-output out; and additional parameters.
  • the additional calculation function block parameters are: back calculation input; back calculation output; and additional parameters.
  • parameter objects are defined to allow the function block, transducer block and resource block attributes to be accessed over the bus.
  • the attributes defined in the basic parameter object model are: member identification; parameter index; relative index; data type; sub index; data length; units; usage; storage; list of valid values; initial value; and item identification. Not all the parameters listed are required in a particular block.
  • a preferred embodiment also defines several subclasses from the parameter object class, including output parameter objects, input parameter objects, and contained parameter objects.
  • Link objects 570 provide mapping between resources and the information exchanged via a communication network as illustrated in FIG. 8. Process data and events to be exchanged between function blocks within a resource or between resources may be defined through link objects. In addition, the communication exchange for support of trends and alerts may be defined using link objects.
  • Link objects 570 are defined in field devices associated with the function block applications process. Link objects 570 , by referencing the appropriate VCR, may be used to access, distribute or exchange individual objects. In addition, the link objects define the association between input and output parameters, and trend reports, which interface devices must receive.
  • Alert objects are used to communicate notification messages when alarms or events are detected.
  • An event is an instantaneous occurrence that is significant to scheduling block execution and to the operational view of a function block application 440 .
  • An alarm is the detection of a block leaving a particular state.
  • the alert object class allows alarms and events to be reported to a device responsible for alarm management.
  • the preferred embodiment designates three subclasses of alarm objects. They are analog alerts, discrete alerts, and update alerts. Analog alerts are used to report alarms or events whose values are associated with a floating point. Discrete alerts are used to report alarms or events whose associated value is discrete. Update alerts are used to report a change in the static data of a block.
  • Trend objects support management and control of function blocks by providing visibility into history information for reviewing their behavior. Based on the type of information collected, a preferred embodiment defines three subclasses of trend objects. These subclasses are the trend float subclass, the trend discrete subclass, and the trend bit string subclass.
  • the trend float class collects the values and status of floating point input and output parameters.
  • the trend discrete subclass collects the values and status of discrete input and output parameters.
  • the trend bit string subclass collects the values and status of bit string input and output parameters.
  • View objects support management and control of function blocks by providing “visibility” into their configuration and operation.
  • view objects allow the user to monitor or “view” data associated with operation, diagnostic, and configuration of the system, functions block application 440 or resource 500 .
  • View 1 allows access to dynamic operation parameter values.
  • View 2 allows access to static operation parameter values.
  • View 3 allows access to all dynamic parameter values.
  • View 4 allows access to other static parameter values.
  • a domain object 580 supports download services that may be used to load data from a client into the server's domain. Data from the server's domain may be transmitted to a client through domain upload services.
  • the domain objects are part of memory. They may contain programs or data. Domains with code and data are combined into an executable program using a program invocation object.
  • a program invocation object 590 provides services to link domains to a program, to start this program, to stop, and to delete it.
  • Action objects may optionally be supported by a resource. Through an action object, an individual block or object within a resource may be deleted.
  • the function block application 440 is mapped into the virtual field device of the fieldbus message specification 230 , as shown in FIG. 7.
  • the virtual field objects which are the preferred tools in describing a function block application 440 are: variable objects; event management objects; domain objects; and program invocation objects.
  • Variable objects are a type of block parameter. Other types of block parameters are simple, array, or record. Record objects support trend, action, and link objects. Grouping of information for access may be done using variable list objects.
  • Event notification objects are used for alarm and event notification.
  • Domain objects are a computer program that may be loaded into memory using the domain download services.
  • Program invocation services may control function block application initialization. Such services include: to start, to stop, and to reset.
  • the device description language (described in more detail later) is used to describe the function block and support block parameters used by the configuration tool. Such a description is known as a “device description.” In many cases, the “device description” is used in the configuration and interface stations. However, in some cases, all or part of the device description may be stored in the field device. When the device description is stored in the field device, it may reside in its own object dictionary in a resource separate from that used for the function block application. To access the device description information, each block maintains an associated device description reference number.
  • the index numbers are grouped according to their data type or structure, or whether the object is static or dynamic.
  • object indices 1 - 255 are reserved for commonly used data types and data structures.
  • indices 1 - 14 and 21 are defined data types in the fieldbus message specification 230
  • indices 54 - 86 are commonly used data structures, which are referenced in the definition of record objects. These indices are the same as the index numbers 285 shown in FIG. 6.
  • FIG. 10 illustrates how these index numbers can also be grouped by whether the object is static or dynamic.
  • All the object descriptions in the object dictionary other than the data type and data structure descriptions may support extensions.
  • the index number of an object description other than a data type or structure may be changed without affecting the other objects.
  • the object description may also be improved or upgraded without affecting the other objects.
  • the object dictionary directory object 282 will be defined as the first index in the static object dictionary (S-OD) 700 , shown in FIG. 10.
  • the starting point of the static object dictionary is defined by the object dictionary object description, which resides in Index Zero.
  • the object dictionary description identifies the start index, the length of the dynamic list of variable list (DV-OD) 710 and the dynamic list of program invocation (DP-OD) 720 associated with view objects and program invocation objects.
  • the directory is logically constructed by concatenating the directory objects, and consists of a header followed by the directory entries.
  • An array offset is specified from the start of the logical directory.
  • the logical directory can be thought of as a single array composed of all the directory object instances. The header is only present in the first directory object.
  • a process control function has the following elements: (1) one or more inputs; (2) one or more outputs; (3) scaling information; (4) a mode selector; (5) a selected algorithm; (6) as set of visible data parameters; and (7) a set of internal data.
  • Each of these elements represents either static data or dynamic data. Static data is data which is seldom changed, while dynamic data may change with each block evaluation.
  • a block input contains the data read from outputs of other blocks. If a block does not receive an input from another block, a constant input can be entered.
  • the permanence of the value depends on the kind of memory to store it. The type of memory used depends on the parameters. For example, volatile memory is sufficient for a frequently changing parameter. Nonvolatile memory is preferred for setpoints.
  • Block outputs contain the result of block evaluation, or an operator entry if the mode is manual.
  • Both inputs and outputs comprise a value field and a status field.
  • the status field contains quality, substatus, and limit attributes. It is the same for all inputs and outputs.
  • the simulate value and the status value become the readback value and status when the enable switch is on, and the transducer switch is ignored.
  • Scaling information is used for two purposes. Display devices use the range for bar graphs and trending. Control blocks use the range as percent of span, so that the tuning constant remains dimensionless.
  • the permitted modes apply to the target mode.
  • a write request to the target mode is rejected if it does not match the permitted list.
  • a configuration device must not allow a mode to be permitted that is not supported.
  • the actual mode is not constrained by the permitted mode, because some modes are acquired for initialization.
  • each block there is an access table for each block.
  • the purpose of that table is to define the relative position of the parameters within each block, and to define the contents of the standard views of the parameters.
  • the block parameters which need to be communicated over the bus vary within the application.
  • predefined sets of variables are selected for each function block.
  • the parameters included in these predefined sets of function blocks are specified in the views in the parameter access table. If parameters are added to a block, these parameters are added after all the standard parameters.
  • the parameter access table provides the following: (1) the order in which the parameters appear sequentially in the object dictionary relative to the location of the associated block object; (2) a list of parameters associated with the function block address in the table; and (3) predefined parameter sets.
  • the predefined parameter sets include view 1 through view 4 .
  • View 1 is the operation dynamic parameter set.
  • the operation dynamic parameter set includes information required by a plant operator to view process control, see alarm conditions, and adjust operating targets.
  • View 2 is the operation static parameter set.
  • the operation static parameter set includes information which may be required for display to an operator with dynamic information. This information is read once when the associated display is first caught up, and refreshed if the static update code changes.
  • View 3 is the all dynamic parameter set.
  • the all dynamic parameter set includes information which is changing in value and may need to be referenced in a detailed display.
  • View 4 is the static parameter set.
  • the static parameter set includes information which is normally referenced during the configuration or maintenance and has a specific value unless changed by an operator or instrument technician.
  • a device includes one or more function block applications 440 .
  • a function block application 440 includes one or more resources 500 , and a resource 500 includes one or more blocks/objects. Each resource has a resource block.
  • each resource block contains data that is specific to the hardware that is associated with the resource.
  • the data in the resource block is modeled as contained parameters, so there are no links to this block.
  • Each function block application also contains at least one function block.
  • FIGS. 11 Examples of two target applications, a manual control 760 and a feedback control 770 , using the basic function blocks are shown in FIGS. 11.
  • the manual control 760 consist of an analog input function block 762 , a manual loader 764 , and an analog output function block 768 .
  • the feedback control 770 consists of an analog input 772 , a proportional/integral/derivative 774 , and an analog output 778 .
  • the function block application processes may also store device descriptions (DD) 860 .
  • DD device descriptions
  • the device descriptions 860 are used in addition to the standard function block parameters.
  • the device descriptions 860 extend the descriptions of each object in the virtual field device.
  • the device descriptions 860 provide information needed for a control system to interpret the meaning of the data in the virtual field device, including the human interface functions, such as calibration and diagnostics.
  • the device description can be written in any standardized programming language, such as C, C++, or SmallTalk.
  • function blocks execute in precisely defined intervals and in proper sequence for correct control system operation.
  • System management synchronizes execution of the function blocks and a communication of function block parameters on the bus.
  • System management also handles other important features such as publication of the time of day to all devices, automatic assignment of device addresses, and searching for parameter names or tags on the fieldbus.
  • the configuration information needed by the system management is described by object descriptions.
  • the configuration information is stored in the network and system management virtual field device 310 , as shown in FIG. 7.
  • the network and system management virtual field device 310 provides access to the system management information base (SMIB) 330 , and also to the network management information base (NMIB) 320 .
  • the system schedules can be inputted manually or built using a schedule building tool.
  • a schedule building tool is used to generate a function block and link active scheduler schedules are used to generate system and network schedules.
  • system management controls when the function blocks execute. This insures that each function block executes at the appropriate time in relationship to other function blocks in the system. For a true distributed control system, the activities of the devices and their function blocks also have to be synchronized with those of other devices on the network. The coordination of the execution of blocks in different devices is controlled by a network manager using a network schedule. Network Management is described in detail later.
  • the system and network schedules contain the start time off-set from the beginning of the absolute link schedule start time.
  • the absolute link schedule start time is known by all devices on the fieldbus.
  • the system management also has a time publisher which, in a link active scheduler 100 , periodically sends application clock synchronization to all field devices.
  • the data link scheduling time is sampled and sent with the application clock message so that the receiving devices can adjust their local application time.
  • the application or system clock time is independently maintained in each field device based on its own system clock.
  • the system clock in each field device initiates the execution of the system schedule for that device, not the data link clock, unless the field device is the link active scheduler 100 .
  • System clock synchronization allows the field devices to stamp data throughout a network. If there are backup system clock publishers on the bus, a backup publisher will become the data link clock if the currently active time publisher should fail.
  • System management also automatically assigns unique network addresses to each field device. Every field device, except a temporary device, should have a unique network address and physical tag. Temporary devices are not assigned tags or permanent addresses. Temporary devices simply join the network at one of four data link visitor addresses reserved for them in the data link layer protocol specification.
  • the system management function responsible for tag and data link address assignment is referred to as the configuration master. It is normally co-located with the link active scheduler 100 , although it is not required to be, so it can monitor the live list for the addition of new devices.
  • configuration master verifies that a system management kernel for the field device does not have a physical tag and assigns it one using system management kernel protocol 810 . Once assigned, the system management kernel moves to the initialized state. In this state, it is ready to be assigned a network address on the operational network. A system management kernel is described in detail later.
  • the sequence for assigning a network address to a new field device is as follows: (1) a physical tag is assigned to a new device via configuration device; (2) system management asks the field device for its physical device tag default network address; (3) system management uses the physical device tag to look up the new network address in the configuration table; and (4) system management sends a special set-address message to the device which forces the device to assume the network address. The sequence of these steps is repeated for all devices that enter the network at a default address.
  • FIG. 12 shows the relationship between system management and the other communication and application components of the present invention.
  • FIG. 12 shows the relationships between the system management and function block application 440 , function block objects 850 , device descriptions (DD) 860 , and object descriptions (OD) 280 .
  • System management also uses the fieldbus message specification 230 to remotely access management information within a field device.
  • System management also accesses the data link layer 210 to perform its other functions.
  • a single system management entity exists in each link master 105 or link active scheduler 100 .
  • This entity comprises a system management information base 830 (SMIB), an object dictionary 280 , and a system management kernel 800 .
  • SIB system management information base 830
  • object dictionary 280 object dictionary 280
  • system management kernel 800 system management kernel
  • the system management kernel 800 provides a network coordinated and synchronized set of functions. To enforce the coordination and synchronization of these functions across the network, a manager/agent model is used. In a preferred embodiment, the system management kernel 800 assumes the role of an agent and responds to the instructions received from the system management. A system management protocol is used to define communications between managers and agents.
  • Information which is used to control system management operation is organized as objects stored in the SMIB 830 .
  • the SMIB 830 is accessed by the network through the system and network management virtual field device 310 .
  • the SMIB 830 contains configuration and operational parameters for a device. Examples of the objects included in the SMIB 830 are: device identification, physical device tag, list of virtual field devices, time object, schedule object, and configuration status.
  • the system management allows SMIB objects to be accessed using the fieldbus message specification application services, such as read, write, etc. Access to the SMIB allows remote applications to obtain management information from the device, either before or during network operation.
  • the management virtual field device is shared with the network management agent 880 of the device and thereby also provides access to network management agent objects.
  • FIG. 12 shows the architectural relationship between network management and the other communication and application components in a device.
  • Each device contains a single network management agent 880 and layer management entities (LME) 875 for its protocols.
  • Each network has at least one network manager which coordinates the network management of the whole system.
  • Network management provides the capabilities of: loading a virtual communication relationship list; configuring the communication stack 205 ; loading the network schedule; performance monitoring; and fault detection monitoring.
  • the network manager is responsible for maintaining the operation of the network according to the policies defined for it by the system manager.
  • the network manager enforces the system management policies by monitoring the status of the communication stack 205 in each device, and taking action when necessary.
  • the network manager performs these tasks by processing information and reports produced by network management agents 880 , and recommending agents to perform services requested via the fieldbus message specification 230 .
  • the network management agent 880 is responsible for providing the network manager with a fieldbus message specification 230 interface to manage objects of the communication stack 205 .
  • the network management agent 880 maps fieldbus message specification service requests to objects that it maintains for the communication stack 205 as a whole, an objects maintained by the LMEs.
  • the LMEs 875 provide management capability of a layer protocol, such as the physical layer (PHY) 200 , the data link layer (DLL) 210 , fieldbus access sublayer (FAS) 220 or fieldbus message specification (FMS) 230 .
  • the LMEs 875 provide the network management agent 880 with a local interface to the managed objects of the protocol. All network access to the LMEs and their objects is provided by the network management agent 880 .
  • the NMIB 895 contains the NMIBs 320 in the system and network management virtual field device (VFD) 310 .
  • the NMIB also contains objects used to define configuration management, performance management and fault management.
  • the objects are accessed by network managers using fieldbus message specifications services.
  • the objects used for network management objects are designed similar to the function blocks described earlier.
  • the flexible function block is described by referring mainly to exemplary embodiments, particularly, with a specific exemplary implementation of a control system using flexible function blocks.
  • the same principles are equally applicable to, and can be implemented in, other implementations and designs using any other distributed control architecture, and that any such variation would be within such modifications that do not depart from the true spirit and scope of the present invention.
  • principles applying to flexible function blocks in the exemplary implementation are equally applicable to other block-oriented implementations.
  • the open system described above provides a framework for and a detailed description of function blocks 530 .
  • the open system described above provides a framework for and description of the interconnection of function block inputs and outputs to provide an application solution.
  • DD 860 device descriptions 860 which are preferably used to describe the input and output parameters of a function block.
  • the DD 860 provides information needed for a control system to interpret the meaning of the function block data, including the human interface functions, such as calibration and diagnostics.
  • the device description can be written in any standardized programming language, such as C, C++, or SmallTalk, or a custom designed device description language (see the '892 patent).
  • a flexible function block (FFB) 950 preferably comprised of end-user configurable FFB input(s) 951 , end user configurable FFB output(s) 952 and an end user configurable FFB algorithm (program) 953 .
  • an end-user 900 preferably uses a FFB Configuration Tool 901 to create a FFB 950 .
  • the end-user 900 creates the FFB 950 , configuring the input(s) 951 , output(s) 952 and algorithm 953 according to the needs of a particular application.
  • FFB 950 creates FFB 950 and a matching FFB DD 860 by running FFB Configuration Tool 901 .
  • FFB DD 860 enables human interface applications such as operator interface, tuning, calibration and diagnostics to be used with FFB 950 .
  • the new FFB 950 operates in the same function block framework as described above (and in the '892 patent), the end-user configured FFB inputs and outputs can be interconnected (e.g., in the same way as shown in FIG. 11) to solve complex application-specific control problems such as discrete/hybrid/batch and PLC control. Any combination of blocks (standardized and flexible) can be used to solve any particular application problem. It is also apparent that interconnection of standardized and flexible blocks applies to H 1 described in the '892 patent and HSE described in the '697 application.
  • the Flexible Function Block overcomes the limitation of non end-user configurable input/output and non end-user configurable of standardized function blocks.
  • Distributed and non-distributed applications 960 in field devices 620 on bus 120 can be built using any combination of standardized function blocks and the new FFB 950 , significantly reducing plant control system installation, operating and maintenance costs.
  • FIG. 15 is a block diagram illustrating an example of a complex application built using a combination of standardized function blocks and the new flexible function block.
  • FIG. 15 is an example of multivariable matrix control for a gas processing plant implemented using flexible function block FFB-MVMC 954 .
  • the field devices e.g., PI 1 , TI 1 , TI 2 , TI- 3 , AI 1 , AI 2 , FIC 1 , FIC 2 , LIC 1
  • the field devices e.g., PI 1 , TI 1 , TI 2 , TI- 3 , AI 1 , AI 2 , FIC 1 , FIC 2 , LIC 1 ) shown in FIG. 15 preferably include standard function blocks.
  • the gas processing plant separates raw natural gas into methane and heavier hydrocarbon liquids for petrochemical feedstock.
  • the main control objective of the complex application is to maximize liquid recovery while maintaining product specifications. Colder operating temperatures will increase natural gas liquids recovery, but at the risk of violating product specification. Careful regulation of heat input at the column side re-boiler is critical in the maintenance of product quality and quantity.
  • Flexible function block FFB-MVMC 954 is used to control the complex, non-linear processes described above by being interconnected with field devices (e.g., PI 1 , TI 1 , TI 2 , TI- 3 , AI 1 , AI 2 , FIC 1 , FIC 2 , LIC 1 in FIG. 15) running standardized functions.
  • Flexible function block FFB-MVMC 954 has been end-user configured to accept as inputs DV 1 -DV 3 and CV 1 -CV 3 , as well as Constraint Variable 1 .
  • Flexible function block FFB-MVMC 954 performs an end-user configured algorithm on these inputs to produce outputs MV 1 -MV 3 .
  • the algorithm produces the outputs MV 1 -MV 3 to carefully regulate the heat input at the column side re-boiler in order to maximize liquid recovery while maintaining product specifications, as determined by the inputs.
  • gateway Complex discrete/hybrid/batch and PLC applications often require non-function block based equipment to be integrated into the control strategy.
  • This integration is accomplished by using a gateway.
  • the end-user or gateway supplier
  • the end-user preferably builds a flexible function block with an algorithm that maps the inputs and outputs of the non-function block equipment to the inputs and outputs of flexible function block (e.g., a gateway flexible function block).
  • the non function block equipment can be integrated with the function block based devices by interconnecting the inputs and outputs of the gateway flexible function block with the inputs and outputs of other flexible function blocks and standard function blocks in the system.

Landscapes

  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Programmable Controllers (AREA)
  • Computer And Data Communications (AREA)
US10/453,596 1996-08-23 2003-06-04 Flexible function blocks Abandoned US20040194101A1 (en)

Priority Applications (11)

Application Number Priority Date Filing Date Title
US10/453,596 US20040194101A1 (en) 1997-08-21 2003-06-04 Flexible function blocks
US10/826,576 US6999824B2 (en) 1997-08-21 2004-04-16 System and method for implementing safety instrumented systems in a fieldbus architecture
EP04776293.5A EP1629332B1 (en) 2003-06-04 2004-06-02 Flexible function blocks
CN201110176258.3A CN102323785B (zh) 2003-06-04 2004-06-02 灵活的功能块
CNA200480015600XA CN1802614A (zh) 2003-06-04 2004-06-02 灵活的功能块
PCT/US2004/017746 WO2004109415A1 (en) 2003-06-04 2004-06-02 Flexible function blocks
US11/240,939 US7167762B2 (en) 1997-08-21 2005-09-30 System and method for implementing safety instrumented systems in a fieldbus architecture
US11/420,704 US7272457B2 (en) 1996-08-23 2006-05-26 Flexible function blocks
US11/656,883 US7486999B2 (en) 1997-08-21 2007-01-22 System and method for implementing safety instrumented systems in a fieldbus architecture
US11/900,349 US20080004727A1 (en) 1996-08-23 2007-09-10 Flexible function blocks
US12/340,212 US20090105849A1 (en) 1997-08-21 2008-12-19 System and method for implementing safety instrumented systems in a fieldbus architecture

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US08/916,178 US6424872B1 (en) 1996-08-23 1997-08-21 Block oriented control system
US09/598,697 US6826590B1 (en) 1996-08-23 2000-06-21 Block-oriented control system on high speed ethernet
US38484602P 2002-06-04 2002-06-04
US10/160,094 US6594530B1 (en) 1996-08-23 2002-06-04 Block-oriented control system
US10/453,596 US20040194101A1 (en) 1997-08-21 2003-06-04 Flexible function blocks

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/160,094 Continuation-In-Part US6594530B1 (en) 1996-08-23 2002-06-04 Block-oriented control system

Related Child Applications (3)

Application Number Title Priority Date Filing Date
US10/826,576 Continuation-In-Part US6999824B2 (en) 1997-08-21 2004-04-16 System and method for implementing safety instrumented systems in a fieldbus architecture
US11/240,939 Continuation-In-Part US7167762B2 (en) 1997-08-21 2005-09-30 System and method for implementing safety instrumented systems in a fieldbus architecture
US11/420,704 Continuation US7272457B2 (en) 1996-08-23 2006-05-26 Flexible function blocks

Publications (1)

Publication Number Publication Date
US20040194101A1 true US20040194101A1 (en) 2004-09-30

Family

ID=33510387

Family Applications (3)

Application Number Title Priority Date Filing Date
US10/453,596 Abandoned US20040194101A1 (en) 1996-08-23 2003-06-04 Flexible function blocks
US11/420,704 Expired - Fee Related US7272457B2 (en) 1996-08-23 2006-05-26 Flexible function blocks
US11/900,349 Abandoned US20080004727A1 (en) 1996-08-23 2007-09-10 Flexible function blocks

Family Applications After (2)

Application Number Title Priority Date Filing Date
US11/420,704 Expired - Fee Related US7272457B2 (en) 1996-08-23 2006-05-26 Flexible function blocks
US11/900,349 Abandoned US20080004727A1 (en) 1996-08-23 2007-09-10 Flexible function blocks

Country Status (4)

Country Link
US (3) US20040194101A1 (zh)
EP (1) EP1629332B1 (zh)
CN (2) CN1802614A (zh)
WO (1) WO2004109415A1 (zh)

Cited By (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040103168A1 (en) * 2002-11-25 2004-05-27 Honda Giken Kogyo Kabushiki Kaisha Method and system for backing up programmable logic controllers over network
US20040220684A1 (en) * 2003-03-14 2004-11-04 Shinji Fukui Display and edit device, display method and program product
US20040230323A1 (en) * 1997-08-21 2004-11-18 Glanzer David A. System and method for implementing safety instrumented systems in a fieldbus architecture
WO2004095716A3 (en) * 2003-04-17 2005-09-22 Fieldbus Foundation System and method for implementing safety instrumented systems in a fieldbus architecture
US20050216727A1 (en) * 2003-08-29 2005-09-29 Microsoft Corporation Communication stack for network communication and routing
US6970771B1 (en) * 1999-11-01 2005-11-29 Abb Research Ltd. Integration of a field device in an installation control system
US20060242648A1 (en) * 2005-04-21 2006-10-26 Francesca Guccione Workload scheduling method and system with improved planned job duration updating scheme
US7146230B2 (en) 1996-08-23 2006-12-05 Fieldbus Foundation Integrated fieldbus data server architecture
US20070038730A1 (en) * 2005-08-15 2007-02-15 Honeywell International Inc. Method and apparatus for providing a standard control system with custom application capability
US20070073867A1 (en) * 2005-09-29 2007-03-29 Fisher-Rosemount Systems, Inc. Associating a signal measurement with a communication device on a network
US20070156263A1 (en) * 2005-12-30 2007-07-05 Honeywell International Inc. Method, apparatus and system for recovery of a controller with known-compatible configuration and run-time data
EP1810104A2 (en) * 2004-10-20 2007-07-25 Fisher Controls International LLC Lead-lag input filter arrangement for electro-pneumatic control loops
US7272457B2 (en) 1996-08-23 2007-09-18 Fieldbus Foundation Flexible function blocks
US7489977B2 (en) 2005-12-20 2009-02-10 Fieldbus Foundation System and method for implementing time synchronization monitoring and detection in a safety instrumented system
US20090089247A1 (en) * 2007-09-28 2009-04-02 Terrence Lynn Blevins Methods and apparatus to standardize data properties in a process control environment
EP1788465A3 (en) * 2005-11-17 2009-10-21 Fanuc Ltd Machine signal processing device
US20090302588A1 (en) * 2008-06-05 2009-12-10 Autoliv Asp, Inc. Systems and methods for airbag tether release
US20120253482A1 (en) * 2011-03-29 2012-10-04 Honeywell International Inc. Function block execution framework
US20130006390A1 (en) * 2011-06-30 2013-01-03 General Electric Company Systems and methods for function block instantiation
US20130222123A1 (en) * 2010-06-29 2013-08-29 Phoenix Contact Gmbh & Co. Kg Communication system for connecting field devices to a higher-order control device
US8676357B2 (en) 2005-12-20 2014-03-18 Fieldbus Foundation System and method for implementing an extended safety instrumented system
US20140107809A1 (en) * 2011-06-20 2014-04-17 Abb Technology Ltd Method and a system for online and dynamic schedule configuration of control applications in a distributed control system
US20140129003A1 (en) * 2012-11-02 2014-05-08 Honeywell International Inc. System for providing mappable input and output terminal assignments
US20140344465A1 (en) * 2011-11-15 2014-11-20 Eaton Electrical Ip Gmbh & Co. Kg Subscriber for use in a digital transmission system, digital transmission system and method for data transmission
US20160231719A1 (en) * 2015-02-11 2016-08-11 Siemens Aktiengesellschaft Independent automation technology field device for remote monitoring
CN106022952A (zh) * 2016-05-10 2016-10-12 中国能源建设集团湖南省电力设计院有限公司 智能变电站装置的iec61850信号映射方法
US10255060B2 (en) * 2013-08-06 2019-04-09 Endress + Hauser Process Solutions Ag Method for extending an embedded software component of a field device
US10532662B2 (en) 2014-08-20 2020-01-14 TruBlue LLC Eddy current braking device for rotary systems
US11123580B2 (en) 2009-03-10 2021-09-21 Eddy Current Limited Partnership Line dispensing device with Eddy current braking for use with climbing and evacuation
US20210302929A1 (en) * 2020-03-26 2021-09-30 Honeywell International Inc. Hierarchal controller logic with incremental updates
US12186596B2 (en) 2019-09-20 2025-01-07 TruBlue LLC Lock-off descent control systems and devices

Families Citing this family (98)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10221772A1 (de) * 2002-05-15 2003-11-27 Flowtec Ag Variables Feldgerät für die Prozeßautomation
US7324856B1 (en) * 2003-09-25 2008-01-29 Rockwell Automation Technologies, Inc. Autogeneration of code via human-machine interfaces (HMI) and self-building HMI
US7178103B2 (en) * 2004-02-03 2007-02-13 Invensys Systems, Inc. Systems and methods for storing configuration data in process control systems
US20070135944A1 (en) * 2005-12-12 2007-06-14 Schmid James J Method, apparatus and computer program product for providing status of a process
ES2384226T3 (es) * 2006-04-05 2012-07-02 Motorola Mobility, Inc. Selección de un medio de transporte para optimizar el funcionamiento de un aparato
US8005553B2 (en) * 2006-09-29 2011-08-23 Fisher-Rosemount Systems, Inc. Automatic configuration of synchronous block execution for control modules run in fieldbus networks
US7761171B2 (en) * 2006-09-29 2010-07-20 Fisher-Rosemount Systems, Inc. Methods and apparatus to generate schedules to execute functions in a process control system
DE102006057133B4 (de) * 2006-12-01 2008-08-07 Phoenix Contact Gmbh & Co. Kg Verfahren zum Betreiben eines ethernetfähigen Feldbusgerätes
DE102006062477A1 (de) * 2006-12-28 2008-07-03 Endress + Hauser Process Solutions Ag Verfahren zum Betreiben eines nach dem Blockmodell arbeitenden Feldgerätes für ein verteiltes Automatisierungssystem
WO2009006621A2 (en) * 2007-07-03 2009-01-08 Fieldbus Foundation Block-oriented control system having wireless gateway for communication with wireless field devices
US7720099B2 (en) * 2007-08-13 2010-05-18 Honeywell International Inc. Common protocol and routing scheme for space data processing networks
US8031633B2 (en) * 2007-08-13 2011-10-04 Honeywell International Inc. Virtual network architecture for space data processing
DE102007039528A1 (de) * 2007-08-21 2009-02-26 Endress + Hauser Conducta Gesellschaft für Mess- und Regeltechnik mbH + Co. KG Feldgerät für die Prozessautomatisierung
DE102007039529A1 (de) * 2007-08-21 2009-02-26 Endress + Hauser Conducta Gesellschaft für Mess- und Regeltechnik mbH + Co. KG Verfahren zum Bedienen eines Feldgeräts der Prozessautomatisierungstechnik mit mindestens zwei Messkanälen und Feldgerät der Prozessautomatisierungstechnik mit mindestens zwei Messkanälen, das zur Durchführung des Verfahrens geeignet ist
US20090088874A1 (en) * 2007-10-02 2009-04-02 Emmanuel Arceo Valve manifold assemblies and method of operating valve manifold assemblies
US8255065B2 (en) * 2008-05-05 2012-08-28 Siemens Aktiengesellschaft Mobile function block for a PLC based distributed control system
US8725298B2 (en) 2008-10-27 2014-05-13 Lennox Industries, Inc. Alarm and diagnostics system and method for a distributed architecture heating, ventilation and conditioning network
US9325517B2 (en) 2008-10-27 2016-04-26 Lennox Industries Inc. Device abstraction system and method for a distributed-architecture heating, ventilation and air conditioning system
US9651925B2 (en) 2008-10-27 2017-05-16 Lennox Industries Inc. System and method for zoning a distributed-architecture heating, ventilation and air conditioning network
US20100106810A1 (en) * 2008-10-27 2010-04-29 Lennox Industries Inc. Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network
US8352080B2 (en) 2008-10-27 2013-01-08 Lennox Industries Inc. Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network
US8788100B2 (en) 2008-10-27 2014-07-22 Lennox Industries Inc. System and method for zoning a distributed-architecture heating, ventilation and air conditioning network
US8463442B2 (en) 2008-10-27 2013-06-11 Lennox Industries, Inc. Alarm and diagnostics system and method for a distributed architecture heating, ventilation and air conditioning network
US8744629B2 (en) 2008-10-27 2014-06-03 Lennox Industries Inc. System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network
US8615326B2 (en) 2008-10-27 2013-12-24 Lennox Industries Inc. System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network
US8994539B2 (en) 2008-10-27 2015-03-31 Lennox Industries, Inc. Alarm and diagnostics system and method for a distributed-architecture heating, ventilation and air conditioning network
US9261888B2 (en) 2008-10-27 2016-02-16 Lennox Industries Inc. System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network
US8655491B2 (en) 2008-10-27 2014-02-18 Lennox Industries Inc. Alarm and diagnostics system and method for a distributed architecture heating, ventilation and air conditioning network
US8600559B2 (en) 2008-10-27 2013-12-03 Lennox Industries Inc. Method of controlling equipment in a heating, ventilation and air conditioning network
US8543243B2 (en) 2008-10-27 2013-09-24 Lennox Industries, Inc. System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network
US8774210B2 (en) 2008-10-27 2014-07-08 Lennox Industries, Inc. Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network
US8255086B2 (en) 2008-10-27 2012-08-28 Lennox Industries Inc. System recovery in a heating, ventilation and air conditioning network
US8352081B2 (en) 2008-10-27 2013-01-08 Lennox Industries Inc. Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network
US8437877B2 (en) 2008-10-27 2013-05-07 Lennox Industries Inc. System recovery in a heating, ventilation and air conditioning network
US8463443B2 (en) 2008-10-27 2013-06-11 Lennox Industries, Inc. Memory recovery scheme and data structure in a heating, ventilation and air conditioning network
US8892797B2 (en) 2008-10-27 2014-11-18 Lennox Industries Inc. Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network
US8564400B2 (en) 2008-10-27 2013-10-22 Lennox Industries, Inc. Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network
US8452906B2 (en) 2008-10-27 2013-05-28 Lennox Industries, Inc. Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network
US8437878B2 (en) 2008-10-27 2013-05-07 Lennox Industries Inc. Alarm and diagnostics system and method for a distributed architecture heating, ventilation and air conditioning network
US8239066B2 (en) 2008-10-27 2012-08-07 Lennox Industries Inc. System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network
US9377768B2 (en) 2008-10-27 2016-06-28 Lennox Industries Inc. Memory recovery scheme and data structure in a heating, ventilation and air conditioning network
US8295981B2 (en) 2008-10-27 2012-10-23 Lennox Industries Inc. Device commissioning in a heating, ventilation and air conditioning network
US8655490B2 (en) 2008-10-27 2014-02-18 Lennox Industries, Inc. System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network
US8560125B2 (en) 2008-10-27 2013-10-15 Lennox Industries Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network
US8433446B2 (en) 2008-10-27 2013-04-30 Lennox Industries, Inc. Alarm and diagnostics system and method for a distributed-architecture heating, ventilation and air conditioning network
US8874815B2 (en) 2008-10-27 2014-10-28 Lennox Industries, Inc. Communication protocol system and method for a distributed architecture heating, ventilation and air conditioning network
US9432208B2 (en) 2008-10-27 2016-08-30 Lennox Industries Inc. Device abstraction system and method for a distributed architecture heating, ventilation and air conditioning system
US20100107072A1 (en) * 2008-10-27 2010-04-29 Lennox Industries Inc. System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network
US8694164B2 (en) 2008-10-27 2014-04-08 Lennox Industries, Inc. Interactive user guidance interface for a heating, ventilation and air conditioning system
US9268345B2 (en) 2008-10-27 2016-02-23 Lennox Industries Inc. System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network
US8452456B2 (en) 2008-10-27 2013-05-28 Lennox Industries Inc. System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network
US8661165B2 (en) 2008-10-27 2014-02-25 Lennox Industries, Inc. Device abstraction system and method for a distributed architecture heating, ventilation and air conditioning system
US8802981B2 (en) 2008-10-27 2014-08-12 Lennox Industries Inc. Flush wall mount thermostat and in-set mounting plate for a heating, ventilation and air conditioning system
US20100106957A1 (en) * 2008-10-27 2010-04-29 Lennox Industries Inc. Programming and configuration in a heating, ventilation and air conditioning network
US20100106326A1 (en) * 2008-10-27 2010-04-29 Lennox Industries Inc. Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network
US8762666B2 (en) 2008-10-27 2014-06-24 Lennox Industries, Inc. Backup and restoration of operation control data in a heating, ventilation and air conditioning network
US8798796B2 (en) 2008-10-27 2014-08-05 Lennox Industries Inc. General control techniques in a heating, ventilation and air conditioning network
US8600558B2 (en) 2008-10-27 2013-12-03 Lennox Industries Inc. System recovery in a heating, ventilation and air conditioning network
US9632490B2 (en) 2008-10-27 2017-04-25 Lennox Industries Inc. System and method for zoning a distributed architecture heating, ventilation and air conditioning network
US8442693B2 (en) 2008-10-27 2013-05-14 Lennox Industries, Inc. System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network
US8855825B2 (en) 2008-10-27 2014-10-07 Lennox Industries Inc. Device abstraction system and method for a distributed-architecture heating, ventilation and air conditioning system
US20100106312A1 (en) * 2008-10-27 2010-04-29 Lennox Industries Inc. Alarm and diagnostics system and method for a distributed-architecture heating, ventilation and air conditioning network
US8548630B2 (en) 2008-10-27 2013-10-01 Lennox Industries, Inc. Alarm and diagnostics system and method for a distributed-architecture heating, ventilation and air conditioning network
US9678486B2 (en) 2008-10-27 2017-06-13 Lennox Industries Inc. Device abstraction system and method for a distributed-architecture heating, ventilation and air conditioning system
US9152155B2 (en) 2008-10-27 2015-10-06 Lennox Industries Inc. Device abstraction system and method for a distributed-architecture heating, ventilation and air conditioning system
US8977794B2 (en) 2008-10-27 2015-03-10 Lennox Industries, Inc. Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network
US7802037B2 (en) * 2008-11-05 2010-09-21 General Electric Company Control of an actuator-sensor-interface compatible device using a remote intelligence device
EP2221682B1 (de) 2009-02-19 2013-07-31 Siemens Aktiengesellschaft Verfahren zur Bereitstellung von Funktionen in einem industriellen Automatisierungssystem, Steuerungsprogramm und industrielles Automatisierungssystem
US20100249952A1 (en) * 2009-03-31 2010-09-30 Schneider Electric/Square D Company Direct Control of Devices Through a Programmable Controller Using Internet Protocol
USD648642S1 (en) 2009-10-21 2011-11-15 Lennox Industries Inc. Thin cover plate for an electronic system controller
USD648641S1 (en) 2009-10-21 2011-11-15 Lennox Industries Inc. Thin cover plate for an electronic system controller
US8892218B2 (en) 2010-02-12 2014-11-18 Rockwell Automation Technologies, Inc. Multiple boolean inputs and outputs for device function blocks
US9134720B2 (en) * 2010-02-12 2015-09-15 Rockwell Automation Technologies, Inc. Macro function block for encapsulating device-level embedded logic
US9535413B2 (en) * 2010-02-12 2017-01-03 Rockwell Automation Technologies, Inc. Automatic device parameter binding method and system
US8260444B2 (en) 2010-02-17 2012-09-04 Lennox Industries Inc. Auxiliary controller of a HVAC system
US8438274B2 (en) * 2010-09-30 2013-05-07 Schneider Electric USA, Inc. Profiling of composite physical devices for monitoring/control systems
US8538559B2 (en) * 2011-04-04 2013-09-17 Relcom, Inc. Fieldbus system function block enhancements using transducer block
US8977372B2 (en) 2011-05-12 2015-03-10 General Electric Company System and method for cycle time visualization
US8994545B2 (en) 2011-05-31 2015-03-31 General Electric Company Systems and methods for alert device removal
US8856302B2 (en) 2011-05-31 2014-10-07 General Electric Company Systems and methods for foundation fieldbus alerts
US8730054B2 (en) 2011-05-31 2014-05-20 General Electric Company Systems and methods to customize alert presentation
US20120310373A1 (en) * 2011-05-31 2012-12-06 General Electric Company Systems and methods for alert capture and transmission
DE102011053757A1 (de) 2011-09-19 2013-03-21 Schneider Electric Automation Gmbh Verfahren zur Generierung und Handhabung von Applikationen für Komponenten eines Steuerungssytems
JP6284091B2 (ja) * 2012-03-30 2018-02-28 住友重機械工業株式会社 射出成形機
US9052708B2 (en) 2012-09-05 2015-06-09 General Electric Company Systems and methods for improved device commissioning and decommissioning
CA2845105A1 (en) * 2013-03-08 2014-09-08 Bosko Loncar Method for producing plc and hmi tag database and system
US9563188B2 (en) 2013-08-01 2017-02-07 General Electric Company Systems and methods for batch device commissioning and decommissioning
US10078314B2 (en) 2014-01-29 2018-09-18 Siemens Aktiengesellschaft Method for providing functions within an industrial automation system, and industrial automation system
EP2902857B1 (de) 2014-01-29 2018-12-19 Siemens Aktiengesellschaft Verfahren zur Bereitstellung von Funktionen innerhalb eines industriellen Automatisierungssystems und industrielles Automatisierungsystem
DE102015106024B4 (de) * 2015-04-20 2023-06-07 Interroll Holding Ag Fördervorrichtung mit Konfigurationsänderung
DE102015106034A1 (de) 2015-04-20 2016-10-20 Interroll Holding Ag Installationsverfahren zum Einrichten von Fördervorrichtungen
US10514683B2 (en) 2015-09-16 2019-12-24 Profire Energy, Inc. Distributed networking system and method to implement a safety state environment
US10432754B2 (en) 2015-09-16 2019-10-01 Profire Energy, Inc Safety networking protocol and method
CN107211050B (zh) * 2015-11-18 2019-05-24 深圳市大疆创新科技有限公司 一种总线编址方法、装置及一种信息提示方法、装置
US10852955B2 (en) 2015-12-29 2020-12-01 EMC IP Holding Company LLC Method and system for accessing data objects stored in a storage system using object descriptors allocated by clients
WO2020142908A1 (zh) * 2019-01-08 2020-07-16 西门子股份公司 将功能块映射到设备的方法、装置、系统、存储介质和程序
CN111813846B (zh) * 2020-06-29 2021-04-02 北京九章云极科技有限公司 一种数据分析处理系统和数据处理方法
CN112667201A (zh) * 2020-12-22 2021-04-16 四川云申至诚科技有限公司 一种零散式组合开发模式的实现方法及工具

Citations (83)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4074565A (en) * 1977-02-17 1978-02-21 The Slope Indicator Company Vibratory-wire strain gage
US4283634A (en) * 1971-06-23 1981-08-11 Westinghouse Electric Corp. System and method for monitoring and controlling operation of industrial gas turbine apparatus and gas turbine electric power plants preferably with a digital computer control system
US4347563A (en) * 1980-06-16 1982-08-31 Forney Engineering Company Industrial control system
US4430699A (en) * 1980-02-15 1984-02-07 U.S. Philips Corporation Distributed data processing system
US4484273A (en) * 1982-09-03 1984-11-20 Sequoia Systems, Inc. Modular computer system
US4531193A (en) * 1981-07-30 1985-07-23 Fuji Electric Company, Ltd. Measurement apparatus
US4591977A (en) * 1983-03-23 1986-05-27 The United States Of America As Represented By The Secretary Of The Air Force Plurality of processors where access to the common memory requires only a single clock interval
US4819149A (en) * 1986-05-02 1989-04-04 Owens-Corning Fiberglas Corporation Distributed control system
US4831558A (en) * 1986-08-26 1989-05-16 The Slope Indicator Company Digitally based system for monitoring physical phenomena
US4864489A (en) * 1982-11-12 1989-09-05 Fuji Electric Co., Ltd. Field instrumentation system
US4888726A (en) * 1987-04-22 1989-12-19 Allen-Bradley Company. Inc. Distributed processing in a cluster of industrial controls linked by a communications network
US4938068A (en) * 1988-09-28 1990-07-03 The Slope Indicator Co. Pressure transducer
US4969083A (en) * 1988-04-04 1990-11-06 Petron Controls Corporation Network programmable logic controller system
US4992926A (en) * 1988-04-11 1991-02-12 Square D Company Peer-to-peer register exchange controller for industrial programmable controllers
US5115675A (en) * 1990-06-15 1992-05-26 The Slope Indicator Company Tensioned bellows pressure transducer
US5131092A (en) * 1989-09-01 1992-07-14 Square D Company Communication system enabling programmable logic controllers access to host computer tasks and host computer access to programmable logic controllers without polling
US5151978A (en) * 1990-03-22 1992-09-29 Square D Company Lan interface which permits a host computer to obtain data without interrupting a ladder program executing in the interface
US5159673A (en) * 1990-03-22 1992-10-27 Square D Company Apparatus for networking programmable logic controllers to host computers
US5166678A (en) * 1987-08-11 1992-11-24 Rosemount Inc. Dual master implied token communication system
US5245704A (en) * 1990-03-22 1993-09-14 Square D Company System for sharing data between microprocessor based devices
US5251302A (en) * 1988-04-11 1993-10-05 Square D Company Network interface board having memory mapped mailbox registers including alarm registers for storing prioritized alarm messages from programmable logic controllers
US5329579A (en) * 1992-07-27 1994-07-12 At&T Bell Laboratories Modular adjunct processor made of identical multi-function modules adaptable under direction of one of them to perform any of the adjunct-processor functions
US5333114A (en) * 1989-10-02 1994-07-26 Rosemount Inc. Field mounted control unit
US5434774A (en) * 1994-03-02 1995-07-18 Fisher Controls International, Inc. Interface apparatus for two-wire communication in process control loops
US5448231A (en) * 1991-05-30 1995-09-05 Fuji Electric Co., Ltd. Method and apparatus for transmitting signals on a transmission line
US5447999A (en) * 1993-12-28 1995-09-05 Shin-Etsu Chemical Co., Ltd. Vinyl chloride polymerization with recycle return projecting into gas phase region of reactor
US5451923A (en) * 1992-10-05 1995-09-19 Fisher Controls International, Inc. Communication system and method
US5452201A (en) * 1993-08-24 1995-09-19 Allen-Bradley Company, Inc. Industrial controller with highly distributed processing
US5453924A (en) * 1994-05-16 1995-09-26 Ag-Chem Equipment Company, Inc. Mobile control system responsive to land area maps
US5485142A (en) * 1994-04-08 1996-01-16 The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration Remote monitor alarm system
US5506956A (en) * 1993-04-07 1996-04-09 Sprint Communications Company L.P. Error correction and channel restoration apparatus for T1 digital links
US5513324A (en) * 1991-03-18 1996-04-30 Echelon Systems Corporation Method and apparatus using network variables in a multi-node network
US5526358A (en) * 1994-08-19 1996-06-11 Peerlogic, Inc. Node management in scalable distributed computing enviroment
US5537547A (en) * 1992-12-14 1996-07-16 At&T Corp. Automatic network element identity information distribution apparatus and method
US5537626A (en) * 1992-11-18 1996-07-16 Canon Kabushiki Kaisha Apparatus for coupling printer with LAN to control printer operation by transferring control parameters, printer status data and printer configuration data between printer and LAN
US5546584A (en) * 1992-07-01 1996-08-13 Lundin; Kenneth System and method for establishing communication protocols between application programs
US5553297A (en) * 1989-04-24 1996-09-03 Yokogawa Electric Corporation Industrial control apparatus
US5579482A (en) * 1991-03-18 1996-11-26 Echelon Corporation Method and apparatus for storing interface information in a computer system
US5608720A (en) * 1993-03-09 1997-03-04 Hubbell Incorporated Control system and operations system interface for a network element in an access system
US5682476A (en) * 1994-10-24 1997-10-28 Fisher-Rosemount Systems, Inc. Distributed control system having central control providing operating power to wireless transceiver connected to industrial process control field device which providing redundant wireless access
US5691896A (en) * 1995-08-15 1997-11-25 Rosemount, Inc. Field based process control system with auto-tuning
US5706007A (en) * 1995-01-03 1998-01-06 Smar Research Corporation Analog current / digital bus protocol converter circuit
US5754596A (en) * 1994-02-23 1998-05-19 Rosemount Inc. Field transmitter for storing information
US5764891A (en) * 1996-02-15 1998-06-09 Rosemount Inc. Process I/O to fieldbus interface circuit
US5764955A (en) * 1995-10-19 1998-06-09 Oasys Group, Inc. Gateway for using legacy telecommunications network element equipment with a common management information protocol
US5768119A (en) * 1996-04-12 1998-06-16 Fisher-Rosemount Systems, Inc. Process control system including alarm priority adjustment
US5793963A (en) * 1994-10-24 1998-08-11 Fisher Rosemount Systems, Inc. Apparatus for providing non-redundant secondary access to field devices in a distributed control system
US5796721A (en) * 1996-06-21 1998-08-18 National Instruments Corporation Method and system for monitoring fieldbus network with dynamically alterable packet filter
US5796602A (en) * 1996-02-06 1998-08-18 Fisher-Rosemount Systems, Inc. Method and apparatus using a device description for a conventional device
US5801942A (en) * 1996-04-12 1998-09-01 Fisher-Rosemount Systems, Inc. Process control system user interface including selection of multiple control languages
US5805442A (en) * 1996-05-30 1998-09-08 Control Technology Corporation Distributed interface architecture for programmable industrial control systems
US5828851A (en) * 1996-04-12 1998-10-27 Fisher-Rosemount Systems, Inc. Process control system using standard protocol control of standard devices and nonstandard devices
US5834861A (en) * 1993-09-16 1998-11-10 Fuji Electric Co., Ltd. LSI for signal transmission
US5838563A (en) * 1996-04-12 1998-11-17 Fisher-Rosemont Systems, Inc. System for configuring a process control environment
US5841654A (en) * 1995-10-16 1998-11-24 Smar Research Corporation Windows based network configuration and control method for a digital control system
US5850523A (en) * 1996-06-21 1998-12-15 National Instruments Corporation Method and system for monitoring fieldbus network with multiple packet filters
US5854890A (en) * 1996-10-15 1998-12-29 National Instruments Corporation Fieldbus function block shell with user selectable data ownership
US5859959A (en) * 1996-04-29 1999-01-12 Hewlett-Packard Company Computer network with devices/paths having redundant links
US5862052A (en) * 1996-04-12 1999-01-19 Fisher-Rosemount Systems, Inc. Process control system using a control strategy implemented in a layered hierarchy of control modules
US5881311A (en) * 1996-06-05 1999-03-09 Fastor Technologies, Inc. Data storage subsystem with block based data management
US5889817A (en) * 1996-07-10 1999-03-30 Fuji Electric Co., Ltd. Communication system with data comparison circuit
US5909368A (en) * 1996-04-12 1999-06-01 Fisher-Rosemount Systems, Inc. Process control system using a process control strategy distributed among multiple control elements
US5963147A (en) * 1995-06-07 1999-10-05 Rosemont Inc. Conversion circuit for process control system
US5970430A (en) * 1996-10-04 1999-10-19 Fisher Controls International, Inc. Local device and process diagnostics in a process control network having distributed control functions
US5971581A (en) * 1997-09-17 1999-10-26 National Instruments Corp. Fieldbus network configuration utility with improved scheduling and looping
US5978578A (en) * 1997-01-30 1999-11-02 Azarya; Arnon Openbus system for control automation networks
US5978850A (en) * 1997-07-02 1999-11-02 National Instruments Corporation System and method for accessing parameters in a fieldbus network using a tag parameters interface
US5980078A (en) * 1997-02-14 1999-11-09 Fisher-Rosemount Systems, Inc. Process control system including automatic sensing and automatic configuration of devices
US5982362A (en) * 1996-05-30 1999-11-09 Control Technology Corporation Video interface architecture for programmable industrial control systems
US5995916A (en) * 1996-04-12 1999-11-30 Fisher-Rosemount Systems, Inc. Process control system for monitoring and displaying diagnostic information of multiple distributed devices
US6014612A (en) * 1997-10-02 2000-01-11 Fisher Controls International, Inc. Remote diagnostics in a process control network having distributed control functions
US6017143A (en) * 1996-03-28 2000-01-25 Rosemount Inc. Device in a process system for detecting events
US6032208A (en) * 1996-04-12 2000-02-29 Fisher-Rosemount Systems, Inc. Process control system for versatile control of multiple process devices of various device types
US6044305A (en) * 1996-10-04 2000-03-28 Fisher Controls International, Inc. Method and apparatus for debugging and tuning a process control network having distributed control functions
US6047222A (en) * 1996-10-04 2000-04-04 Fisher Controls International, Inc. Process control network with redundant field devices and buses
US6047220A (en) * 1996-12-31 2000-04-04 Rosemount Inc. Device in a process system for validating a control signal from a field device
US6061603A (en) * 1997-09-10 2000-05-09 Schneider Automation Inc. System for remotely accessing an industrial control system over a commercial communications network
US6076952A (en) * 1997-09-17 2000-06-20 National Instruments, Corp. Fieldbus network configuration utility with improved parameter control
US6098116A (en) * 1996-04-12 2000-08-01 Fisher-Rosemont Systems, Inc. Process control system including a method and apparatus for automatically sensing the connection of devices to a network
US6102965A (en) * 1996-09-23 2000-08-15 National Instruments Corporation System and method for providing client/server access to graphical programs
US6151625A (en) * 1997-09-10 2000-11-21 Schneider Automation Inc. Internet web interface including programmable logic controller for controlling output devices based on status of input devices
US6424872B1 (en) * 1996-08-23 2002-07-23 Fieldbus Foundation Block oriented control system
US6826590B1 (en) * 1996-08-23 2004-11-30 Fieldbus Foundation Block-oriented control system on high speed ethernet

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
USRE27703E (en) 1972-09-05 1973-07-24 Configuration control in multiprocessors
US4099242A (en) 1976-11-03 1978-07-04 Houston George B One-pass general associative search processor
US4448231A (en) * 1979-06-11 1984-05-15 Litton Business Systems, Inc. Panel system edge sealing means
US4451923A (en) * 1980-12-01 1984-05-29 Hansch Theodor W Method of and apparatus for measuring optical frequency variations
JPH0753183Y2 (ja) * 1985-01-19 1995-12-06 ソニー株式会社 テープカセット用リール
US5122794A (en) 1987-08-11 1992-06-16 Rosemount Inc. Dual master implied token communication system
US4897777A (en) 1988-04-11 1990-01-30 Square D Company Peer-to-peer register exchange controller for PLCS
CN2050190U (zh) * 1989-04-14 1989-12-27 雅百达中贸有限公司 微型工业过程控制装置
JP4260221B2 (ja) 1996-02-06 2009-04-30 フィッシャー−ローズマウント システムズ， インコーポレイテッド フィールドデバイスコンフィギュレーションへのチェンジのレコードのトランザクションデーターベースを管理する為のシステム及び方法
SE509269C2 (sv) 1996-07-15 1998-12-21 Telia Ab Metod, system och protokollarkitektur för nätverksadministration
US20040194101A1 (en) 1997-08-21 2004-09-30 Glanzer David A. Flexible function blocks
US7146230B2 (en) 1996-08-23 2006-12-05 Fieldbus Foundation Integrated fieldbus data server architecture
US6999824B2 (en) 1997-08-21 2006-02-14 Fieldbus Foundation System and method for implementing safety instrumented systems in a fieldbus architecture
US6484061B2 (en) 1997-09-10 2002-11-19 Schneider Automation Inc. Web interface to a programmable controller
WO1999048245A2 (en) 1998-03-16 1999-09-23 Schneider Automation, Inc. Communication system for a control system over ethernet and ip networks
US6446202B1 (en) 1999-10-04 2002-09-03 Fisher-Rosemount Systems, Inc. Process control configuration system for use with an AS-Interface device network
US20050240286A1 (en) 2000-06-21 2005-10-27 Glanzer David A Block-oriented control system on high speed ethernet
AU9269101A (en) 2000-09-15 2002-03-26 Wonderware Corp A method and system for remote configuration of process data access servers
DE10151116A1 (de) 2001-10-15 2003-05-08 Siemens Ag Verfahren zur Inbetriebnahme eines Bedien- und Beobachtungssystems von Feldgeräten

Patent Citations (96)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4283634A (en) * 1971-06-23 1981-08-11 Westinghouse Electric Corp. System and method for monitoring and controlling operation of industrial gas turbine apparatus and gas turbine electric power plants preferably with a digital computer control system
US4074565A (en) * 1977-02-17 1978-02-21 The Slope Indicator Company Vibratory-wire strain gage
US4430699A (en) * 1980-02-15 1984-02-07 U.S. Philips Corporation Distributed data processing system
US4347563A (en) * 1980-06-16 1982-08-31 Forney Engineering Company Industrial control system
US4531193A (en) * 1981-07-30 1985-07-23 Fuji Electric Company, Ltd. Measurement apparatus
US4484273A (en) * 1982-09-03 1984-11-20 Sequoia Systems, Inc. Modular computer system
US4864489A (en) * 1982-11-12 1989-09-05 Fuji Electric Co., Ltd. Field instrumentation system
US4591977A (en) * 1983-03-23 1986-05-27 The United States Of America As Represented By The Secretary Of The Air Force Plurality of processors where access to the common memory requires only a single clock interval
US4819149A (en) * 1986-05-02 1989-04-04 Owens-Corning Fiberglas Corporation Distributed control system
US4831558A (en) * 1986-08-26 1989-05-16 The Slope Indicator Company Digitally based system for monitoring physical phenomena
US4888726A (en) * 1987-04-22 1989-12-19 Allen-Bradley Company. Inc. Distributed processing in a cluster of industrial controls linked by a communications network
US5166678A (en) * 1987-08-11 1992-11-24 Rosemount Inc. Dual master implied token communication system
US4969083A (en) * 1988-04-04 1990-11-06 Petron Controls Corporation Network programmable logic controller system
US5251302A (en) * 1988-04-11 1993-10-05 Square D Company Network interface board having memory mapped mailbox registers including alarm registers for storing prioritized alarm messages from programmable logic controllers
US4992926A (en) * 1988-04-11 1991-02-12 Square D Company Peer-to-peer register exchange controller for industrial programmable controllers
US4938068A (en) * 1988-09-28 1990-07-03 The Slope Indicator Co. Pressure transducer
US5553297A (en) * 1989-04-24 1996-09-03 Yokogawa Electric Corporation Industrial control apparatus
US5131092A (en) * 1989-09-01 1992-07-14 Square D Company Communication system enabling programmable logic controllers access to host computer tasks and host computer access to programmable logic controllers without polling
US5333114A (en) * 1989-10-02 1994-07-26 Rosemount Inc. Field mounted control unit
US5485400A (en) * 1989-10-02 1996-01-16 Rosemount Inc. Field-mounted control unit
US5825664A (en) * 1989-10-02 1998-10-20 Rosemount Inc. Field-mounted control unit
US5245704A (en) * 1990-03-22 1993-09-14 Square D Company System for sharing data between microprocessor based devices
US5159673A (en) * 1990-03-22 1992-10-27 Square D Company Apparatus for networking programmable logic controllers to host computers
US5151978A (en) * 1990-03-22 1992-09-29 Square D Company Lan interface which permits a host computer to obtain data without interrupting a ladder program executing in the interface
US5115675A (en) * 1990-06-15 1992-05-26 The Slope Indicator Company Tensioned bellows pressure transducer
US5579482A (en) * 1991-03-18 1996-11-26 Echelon Corporation Method and apparatus for storing interface information in a computer system
US5513324A (en) * 1991-03-18 1996-04-30 Echelon Systems Corporation Method and apparatus using network variables in a multi-node network
US5448231A (en) * 1991-05-30 1995-09-05 Fuji Electric Co., Ltd. Method and apparatus for transmitting signals on a transmission line
US5546584A (en) * 1992-07-01 1996-08-13 Lundin; Kenneth System and method for establishing communication protocols between application programs
US5329579A (en) * 1992-07-27 1994-07-12 At&T Bell Laboratories Modular adjunct processor made of identical multi-function modules adaptable under direction of one of them to perform any of the adjunct-processor functions
US5684451A (en) * 1992-10-05 1997-11-04 Fisher Controls International, Inc. Communication system and method
US5451923A (en) * 1992-10-05 1995-09-19 Fisher Controls International, Inc. Communication system and method
US5537626A (en) * 1992-11-18 1996-07-16 Canon Kabushiki Kaisha Apparatus for coupling printer with LAN to control printer operation by transferring control parameters, printer status data and printer configuration data between printer and LAN
US5537547A (en) * 1992-12-14 1996-07-16 At&T Corp. Automatic network element identity information distribution apparatus and method
US5608720A (en) * 1993-03-09 1997-03-04 Hubbell Incorporated Control system and operations system interface for a network element in an access system
US5506956A (en) * 1993-04-07 1996-04-09 Sprint Communications Company L.P. Error correction and channel restoration apparatus for T1 digital links
US5452201A (en) * 1993-08-24 1995-09-19 Allen-Bradley Company, Inc. Industrial controller with highly distributed processing
US5834861A (en) * 1993-09-16 1998-11-10 Fuji Electric Co., Ltd. LSI for signal transmission
US5447999A (en) * 1993-12-28 1995-09-05 Shin-Etsu Chemical Co., Ltd. Vinyl chloride polymerization with recycle return projecting into gas phase region of reactor
US5754596A (en) * 1994-02-23 1998-05-19 Rosemount Inc. Field transmitter for storing information
US5434774A (en) * 1994-03-02 1995-07-18 Fisher Controls International, Inc. Interface apparatus for two-wire communication in process control loops
US5485142A (en) * 1994-04-08 1996-01-16 The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration Remote monitor alarm system
US5453924A (en) * 1994-05-16 1995-09-26 Ag-Chem Equipment Company, Inc. Mobile control system responsive to land area maps
US5526358A (en) * 1994-08-19 1996-06-11 Peerlogic, Inc. Node management in scalable distributed computing enviroment
US5682476A (en) * 1994-10-24 1997-10-28 Fisher-Rosemount Systems, Inc. Distributed control system having central control providing operating power to wireless transceiver connected to industrial process control field device which providing redundant wireless access
US5793963A (en) * 1994-10-24 1998-08-11 Fisher Rosemount Systems, Inc. Apparatus for providing non-redundant secondary access to field devices in a distributed control system
US5706007A (en) * 1995-01-03 1998-01-06 Smar Research Corporation Analog current / digital bus protocol converter circuit
US5963147A (en) * 1995-06-07 1999-10-05 Rosemont Inc. Conversion circuit for process control system
US5691896A (en) * 1995-08-15 1997-11-25 Rosemount, Inc. Field based process control system with auto-tuning
US5841654A (en) * 1995-10-16 1998-11-24 Smar Research Corporation Windows based network configuration and control method for a digital control system
US6095674A (en) * 1995-10-16 2000-08-01 Smar Research Corporation Windows based network configuration and control method for a digital control system
US5764955A (en) * 1995-10-19 1998-06-09 Oasys Group, Inc. Gateway for using legacy telecommunications network element equipment with a common management information protocol
US5796602A (en) * 1996-02-06 1998-08-18 Fisher-Rosemount Systems, Inc. Method and apparatus using a device description for a conventional device
US5903455A (en) * 1996-02-06 1999-05-11 Fisher-Rosemount Systems, Inc. Interface controls for use in a field device management system
US6094600A (en) * 1996-02-06 2000-07-25 Fisher-Rosemount Systems, Inc. System and method for managing a transaction database of records of changes to field device configurations
US5960214A (en) * 1996-02-06 1999-09-28 Fisher-Rosemount Systems, Inc. Integrated communication network for use in a field device management system
US5764891A (en) * 1996-02-15 1998-06-09 Rosemount Inc. Process I/O to fieldbus interface circuit
US6017143A (en) * 1996-03-28 2000-01-25 Rosemount Inc. Device in a process system for detecting events
US6119047A (en) * 1996-03-28 2000-09-12 Rosemount Inc. Transmitter with software for determining when to initiate diagnostics
US5768119A (en) * 1996-04-12 1998-06-16 Fisher-Rosemount Systems, Inc. Process control system including alarm priority adjustment
US5995916A (en) * 1996-04-12 1999-11-30 Fisher-Rosemount Systems, Inc. Process control system for monitoring and displaying diagnostic information of multiple distributed devices
US5862052A (en) * 1996-04-12 1999-01-19 Fisher-Rosemount Systems, Inc. Process control system using a control strategy implemented in a layered hierarchy of control modules
US5801942A (en) * 1996-04-12 1998-09-01 Fisher-Rosemount Systems, Inc. Process control system user interface including selection of multiple control languages
US6032208A (en) * 1996-04-12 2000-02-29 Fisher-Rosemount Systems, Inc. Process control system for versatile control of multiple process devices of various device types
US5828851A (en) * 1996-04-12 1998-10-27 Fisher-Rosemount Systems, Inc. Process control system using standard protocol control of standard devices and nonstandard devices
US5909368A (en) * 1996-04-12 1999-06-01 Fisher-Rosemount Systems, Inc. Process control system using a process control strategy distributed among multiple control elements
US6098116A (en) * 1996-04-12 2000-08-01 Fisher-Rosemont Systems, Inc. Process control system including a method and apparatus for automatically sensing the connection of devices to a network
US5838563A (en) * 1996-04-12 1998-11-17 Fisher-Rosemont Systems, Inc. System for configuring a process control environment
US6078320A (en) * 1996-04-12 2000-06-20 Fisher-Rosemount Systems, Inc. System for configuring a process control environment
US6266726B1 (en) * 1996-04-12 2001-07-24 Fisher-Rosemount Systems, Inc. Process control system using standard protocol control-of standard devices and non-standard devices
US5859959A (en) * 1996-04-29 1999-01-12 Hewlett-Packard Company Computer network with devices/paths having redundant links
US5975737A (en) * 1996-05-30 1999-11-02 Control Technology Corporation Distributed interface architecture for programmable industrial control systems
US5982362A (en) * 1996-05-30 1999-11-09 Control Technology Corporation Video interface architecture for programmable industrial control systems
US5805442A (en) * 1996-05-30 1998-09-08 Control Technology Corporation Distributed interface architecture for programmable industrial control systems
US5881311A (en) * 1996-06-05 1999-03-09 Fastor Technologies, Inc. Data storage subsystem with block based data management
US5796721A (en) * 1996-06-21 1998-08-18 National Instruments Corporation Method and system for monitoring fieldbus network with dynamically alterable packet filter
US5850523A (en) * 1996-06-21 1998-12-15 National Instruments Corporation Method and system for monitoring fieldbus network with multiple packet filters
US5889817A (en) * 1996-07-10 1999-03-30 Fuji Electric Co., Ltd. Communication system with data comparison circuit
US6424872B1 (en) * 1996-08-23 2002-07-23 Fieldbus Foundation Block oriented control system
US6594530B1 (en) * 1996-08-23 2003-07-15 Fieldbus Foundation Block-oriented control system
US6826590B1 (en) * 1996-08-23 2004-11-30 Fieldbus Foundation Block-oriented control system on high speed ethernet
US6102965A (en) * 1996-09-23 2000-08-15 National Instruments Corporation System and method for providing client/server access to graphical programs
US6026352A (en) * 1996-10-04 2000-02-15 Fisher Controls International, Inc. Local device and process diagnostics in a process control network having distributed control functions
US5970430A (en) * 1996-10-04 1999-10-19 Fisher Controls International, Inc. Local device and process diagnostics in a process control network having distributed control functions
US6047222A (en) * 1996-10-04 2000-04-04 Fisher Controls International, Inc. Process control network with redundant field devices and buses
US6044305A (en) * 1996-10-04 2000-03-28 Fisher Controls International, Inc. Method and apparatus for debugging and tuning a process control network having distributed control functions
US5854890A (en) * 1996-10-15 1998-12-29 National Instruments Corporation Fieldbus function block shell with user selectable data ownership
US6047220A (en) * 1996-12-31 2000-04-04 Rosemount Inc. Device in a process system for validating a control signal from a field device
US5978578A (en) * 1997-01-30 1999-11-02 Azarya; Arnon Openbus system for control automation networks
US5980078A (en) * 1997-02-14 1999-11-09 Fisher-Rosemount Systems, Inc. Process control system including automatic sensing and automatic configuration of devices
US5978850A (en) * 1997-07-02 1999-11-02 National Instruments Corporation System and method for accessing parameters in a fieldbus network using a tag parameters interface
US6151625A (en) * 1997-09-10 2000-11-21 Schneider Automation Inc. Internet web interface including programmable logic controller for controlling output devices based on status of input devices
US6061603A (en) * 1997-09-10 2000-05-09 Schneider Automation Inc. System for remotely accessing an industrial control system over a commercial communications network
US5971581A (en) * 1997-09-17 1999-10-26 National Instruments Corp. Fieldbus network configuration utility with improved scheduling and looping
US6076952A (en) * 1997-09-17 2000-06-20 National Instruments, Corp. Fieldbus network configuration utility with improved parameter control
US6014612A (en) * 1997-10-02 2000-01-11 Fisher Controls International, Inc. Remote diagnostics in a process control network having distributed control functions

Cited By (56)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7146230B2 (en) 1996-08-23 2006-12-05 Fieldbus Foundation Integrated fieldbus data server architecture
US20080004727A1 (en) * 1996-08-23 2008-01-03 Fieldbus Foundation Flexible function blocks
US7272457B2 (en) 1996-08-23 2007-09-18 Fieldbus Foundation Flexible function blocks
US20070129820A1 (en) * 1996-08-23 2007-06-07 Glanzer David A Integrated fieldbus data server architecture
US20060025872A1 (en) * 1997-08-21 2006-02-02 Glanzer David A System and method for implementing safety instrumented systems in a fieldbus architecture
US20070213853A1 (en) * 1997-08-21 2007-09-13 Fieldbus Foundation System and method for implementing safety instrumented systems in a fieldbus architecture
US6999824B2 (en) * 1997-08-21 2006-02-14 Fieldbus Foundation System and method for implementing safety instrumented systems in a fieldbus architecture
US7486999B2 (en) 1997-08-21 2009-02-03 Fieldbus Foundation System and method for implementing safety instrumented systems in a fieldbus architecture
US7167762B2 (en) * 1997-08-21 2007-01-23 Fieldbus Foundation System and method for implementing safety instrumented systems in a fieldbus architecture
US20040230323A1 (en) * 1997-08-21 2004-11-18 Glanzer David A. System and method for implementing safety instrumented systems in a fieldbus architecture
US6970771B1 (en) * 1999-11-01 2005-11-29 Abb Research Ltd. Integration of a field device in an installation control system
US20040103168A1 (en) * 2002-11-25 2004-05-27 Honda Giken Kogyo Kabushiki Kaisha Method and system for backing up programmable logic controllers over network
US7149604B2 (en) * 2002-11-25 2006-12-12 Honda Giken Kogyo Kabushiki Kaisha Method and system for backing up programmable logic controllers over network
US20040220684A1 (en) * 2003-03-14 2004-11-04 Shinji Fukui Display and edit device, display method and program product
US7757209B2 (en) * 2003-03-14 2010-07-13 Omron Corporation Display and edit device, display method and program product
WO2004095716A3 (en) * 2003-04-17 2005-09-22 Fieldbus Foundation System and method for implementing safety instrumented systems in a fieldbus architecture
US20050216727A1 (en) * 2003-08-29 2005-09-29 Microsoft Corporation Communication stack for network communication and routing
EP1810104A4 (en) * 2004-10-20 2010-07-28 Fisher Controls Int LEAD LAG INPUT FILTER ASSEMBLY FOR ELECTROPNEUMATIC CONTROL GRINDING
US7917233B2 (en) 2004-10-20 2011-03-29 Fisher Controls International Llc Lead-lag filter arrangement for electro-pneumatic control loops
EP1810104A2 (en) * 2004-10-20 2007-07-25 Fisher Controls International LLC Lead-lag input filter arrangement for electro-pneumatic control loops
US20090326682A1 (en) * 2004-10-20 2009-12-31 Fisher Controls International Llc Lead-lag filter arrangement for electro-pneumatic control loops
US8479206B2 (en) * 2005-04-21 2013-07-02 International Business Machines Corporation Workload scheduling method and system with improved planned job duration updating scheme
US7870555B2 (en) * 2005-04-21 2011-01-11 International Business Machines Corporation Workload scheduling method and system with improved planned job duration updating scheme
US20100325632A1 (en) * 2005-04-21 2010-12-23 International Business Machines Corporation Workload scheduling method and system with improved planned job duration updating scheme
US20060242648A1 (en) * 2005-04-21 2006-10-26 Francesca Guccione Workload scheduling method and system with improved planned job duration updating scheme
US7313448B2 (en) * 2005-08-15 2007-12-25 Honeywell International Inc. Method and apparatus for providing a standard control system with custom application capability
US20070038730A1 (en) * 2005-08-15 2007-02-15 Honeywell International Inc. Method and apparatus for providing a standard control system with custom application capability
US7609713B2 (en) * 2005-09-29 2009-10-27 Fisher-Rosemount Systems, Inc. Associating a signal measurement with a communication device on a network
US20070073867A1 (en) * 2005-09-29 2007-03-29 Fisher-Rosemount Systems, Inc. Associating a signal measurement with a communication device on a network
EP1788465A3 (en) * 2005-11-17 2009-10-21 Fanuc Ltd Machine signal processing device
US20090112336A1 (en) * 2005-12-20 2009-04-30 Duffy Joseph D System and method for implementing time synchronization monitoring and detection in a safety instrumented system
US7489977B2 (en) 2005-12-20 2009-02-10 Fieldbus Foundation System and method for implementing time synchronization monitoring and detection in a safety instrumented system
US8676357B2 (en) 2005-12-20 2014-03-18 Fieldbus Foundation System and method for implementing an extended safety instrumented system
US20070156263A1 (en) * 2005-12-30 2007-07-05 Honeywell International Inc. Method, apparatus and system for recovery of a controller with known-compatible configuration and run-time data
US7546171B2 (en) * 2005-12-30 2009-06-09 Honeywell International Inc. Method, apparatus and system for recovery of a controller with known-compatible configuration and run-time data
US20090089247A1 (en) * 2007-09-28 2009-04-02 Terrence Lynn Blevins Methods and apparatus to standardize data properties in a process control environment
US20090302588A1 (en) * 2008-06-05 2009-12-10 Autoliv Asp, Inc. Systems and methods for airbag tether release
US11123580B2 (en) 2009-03-10 2021-09-21 Eddy Current Limited Partnership Line dispensing device with Eddy current braking for use with climbing and evacuation
US10037688B2 (en) * 2010-06-29 2018-07-31 Phoenix Contact Gmbh & Co. Kg Communication system for connecting field devices to a higher-order control device
US20130222123A1 (en) * 2010-06-29 2013-08-29 Phoenix Contact Gmbh & Co. Kg Communication system for connecting field devices to a higher-order control device
US20120253482A1 (en) * 2011-03-29 2012-10-04 Honeywell International Inc. Function block execution framework
US8983632B2 (en) * 2011-03-29 2015-03-17 Honeywell International Inc. Function block execution framework
US20140107809A1 (en) * 2011-06-20 2014-04-17 Abb Technology Ltd Method and a system for online and dynamic schedule configuration of control applications in a distributed control system
CN103765336A (zh) * 2011-06-20 2014-04-30 Abb研究有限公司 分布式控制系统中控制应用的在线和动态调度配置的方法和系统
US9772617B2 (en) * 2011-06-30 2017-09-26 General Electric Company Systems and methods for function block instantiation
US20130006390A1 (en) * 2011-06-30 2013-01-03 General Electric Company Systems and methods for function block instantiation
US20140344465A1 (en) * 2011-11-15 2014-11-20 Eaton Electrical Ip Gmbh & Co. Kg Subscriber for use in a digital transmission system, digital transmission system and method for data transmission
US20140129003A1 (en) * 2012-11-02 2014-05-08 Honeywell International Inc. System for providing mappable input and output terminal assignments
US10255060B2 (en) * 2013-08-06 2019-04-09 Endress + Hauser Process Solutions Ag Method for extending an embedded software component of a field device
US10532662B2 (en) 2014-08-20 2020-01-14 TruBlue LLC Eddy current braking device for rotary systems
US10274912B2 (en) * 2015-02-11 2019-04-30 Siemens Aktiegensellschaft Independent automation technology field device for remote monitoring
US20160231719A1 (en) * 2015-02-11 2016-08-11 Siemens Aktiengesellschaft Independent automation technology field device for remote monitoring
CN106022952A (zh) * 2016-05-10 2016-10-12 中国能源建设集团湖南省电力设计院有限公司 智能变电站装置的iec61850信号映射方法
US12186596B2 (en) 2019-09-20 2025-01-07 TruBlue LLC Lock-off descent control systems and devices
US20210302929A1 (en) * 2020-03-26 2021-09-30 Honeywell International Inc. Hierarchal controller logic with incremental updates
US11579578B2 (en) * 2020-03-26 2023-02-14 Honeywell International Inc. Hierarchal controller logic with incremental updates

Also Published As

Publication number Publication date
EP1629332A4 (en) 2010-12-29
CN102323785B (zh) 2016-04-13
CN102323785A (zh) 2012-01-18
US7272457B2 (en) 2007-09-18
WO2004109415A1 (en) 2004-12-16
US20060206218A1 (en) 2006-09-14
EP1629332B1 (en) 2020-11-18
US20080004727A1 (en) 2008-01-03
CN1802614A (zh) 2006-07-12
EP1629332A1 (en) 2006-03-01

Similar Documents

Publication Publication Date Title
US7272457B2 (en) Flexible function blocks
US6594530B1 (en) Block-oriented control system
US7486999B2 (en) System and method for implementing safety instrumented systems in a fieldbus architecture
US8676357B2 (en) System and method for implementing an extended safety instrumented system
US7489977B2 (en) System and method for implementing time synchronization monitoring and detection in a safety instrumented system
US6738388B1 (en) Shadow function block interface for use in a process control network
CA2267502C (en) A network accessible interface for a process control network
JP4739515B2 (ja) 分散制御機能を有するプロセス制御ネットワークにおける遠隔診断
US5828851A (en) Process control system using standard protocol control of standard devices and nonstandard devices
US5862052A (en) Process control system using a control strategy implemented in a layered hierarchy of control modules
US6032208A (en) Process control system for versatile control of multiple process devices of various device types
EP1614225B1 (en) System for implementing safety instrumented systems in a fieldbus architecture
US20020013629A1 (en) Process control system using a process control strategy distributed among multiple control elements
WO2007076284A2 (en) System and method for implementing safety instrumented systems
EP1963930B1 (en) System and method for implementing time synchronization monitoring and detection in a safety instrumented system

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: FIELDBUS FOUNDATION, TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GLANZER, DAVID A.;MITSCHKE, STEPHEN B.;HAWKINS, WILLIAM M.;AND OTHERS;REEL/FRAME:019688/0868;SIGNING DATES FROM 20051108 TO 20060723