USRE40817E1 - Process control system including automatic sensing and automatic configuration of devices - Google Patents

Process control system including automatic sensing and automatic configuration of devices Download PDF

Info

Publication number
USRE40817E1
USRE40817E1 US10/037,019 US3701901A USRE40817E US RE40817 E1 USRE40817 E1 US RE40817E1 US 3701901 A US3701901 A US 3701901A US RE40817 E USRE40817 E US RE40817E
Authority
US
United States
Prior art keywords
network
connected device
devices
configuration
control system
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.)
Expired - Lifetime
Application number
US10/037,019
Inventor
Ken D. Krivoshein
Dan D. Christensen
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.)
Fisher Rosemount Systems Inc
Original Assignee
Fisher Rosemount Systems Inc
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
Application filed by Fisher Rosemount Systems Inc filed Critical Fisher Rosemount Systems Inc
Priority to US10/037,019 priority Critical patent/USRE40817E1/en
Application granted granted Critical
Publication of USRE40817E1 publication Critical patent/USRE40817E1/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • G05B19/02Programme-control systems electric
    • G05B19/418Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS], computer integrated manufacturing [CIM]
    • G05B19/41865Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS], computer integrated manufacturing [CIM] characterised by job scheduling, process planning, material flow
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/10Requirements analysis; Specification techniques
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44505Configuring for program initiating, e.g. using registry, configuration files
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/30Nc systems
    • G05B2219/31From computer integrated manufacturing till monitoring
    • G05B2219/31474Icon display for quick access of detailed information
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/30Nc systems
    • G05B2219/32Operator till task planning
    • G05B2219/32162Tasks or control icons are linked to form a job
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/30Nc systems
    • G05B2219/36Nc in input of data, input key till input tape
    • G05B2219/36025Link, connect icons together to form program
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/30Nc systems
    • G05B2219/36Nc in input of data, input key till input tape
    • G05B2219/36076Select icon and display corresponding instructions
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/30Nc systems
    • G05B2219/36Nc in input of data, input key till input tape
    • G05B2219/36143Use of icon to represent a function, part of program
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/80Management or planning

Definitions

  • This invention relates to process control systems. More specifically, the present invention relates to a process control system which automatically senses connection of process devices and automatically configures the devices when sensed.
  • Present-day process control systems use instruments, control devices and communication systems to monitor and manipulate control elements, such as valves and switches, to maintain at selected target values one or more process variables, including temperature, pressure, flow and the Eke.
  • the process variables are selected and controlled to achieve a desired process objective, such as attaining the safe and efficient operation of machines and equipment utilized in the process.
  • Process control systems have widespread application in the automation of industrial processes such as the processes used in chemical, petroleum, and manufacturing industries, for example.
  • Control of the process is often implemented using microprocessor-based controllers, computers or workstations which monitor the process by sending and receiving commands and data to hardware devices to control either a particular aspect of the process or the entire process as a whole.
  • the specific process control functions that are implemented by software programs in these microprocessors, computers or workstations may be individually designed, modified or changed through programming while requiring no modifications to the hardware.
  • an engineer might cause a program to be written to have the controller read a fluid level from a level sensor in a tank, compare the tank level with a predetermined desired level, and then open or close a feed valve based on whether the read level was lower or higher than the predetermined, desired level.
  • the parameters are easily changed by displaying a selected view of the process and then by modifying the program using the selected view.
  • the engineer typically would change parameters by displaying and modifying an engineer's view of the process.
  • Many process control systems include local field devices such as valves, motors, regulators and the like which are responsive to specific control protocols, such as Profibus, Fieldbus, CAN and the like, to implement various control function routines. Accordingly, these controllers are responsive to certain standard control protocols to implement control functionality in the field. The use of such standard control signal protocols can reduce the time and effort of developing a control system because a designer can use the same types of control signals from all devices responsive to the control protocol.
  • the local field devices are typically configured in the field, often by individually programming the local field devices using a hand-held field programmer.
  • Individual programming of the field devices is time consuming and inefficient and often leads to incompatibilities between the device configuration and the configuration of other devices and controllers in the process control system since a global view of the system is more difficult to sustain when individual devices are programmed independently.
  • Usage of individual programming devices is inconvenient since multiple different programming devices typically must be used to program respective different field devices.
  • What is needed is a process control system that allows individual field devices to be configured without local, independent programming. What is also needed is a process control system allowing configuration of the global system from a location remote from the local field devices so that a compatible global configuration is achieved while allowing peripheral elements which are configured in a suitable global manner, to operate independently to achieve control functionality.
  • Configuration of the global system is based on parameters that describe the particular field devices that make up the system.
  • the control protocols for communicating with the field devices may be insufficient to convey parameters that are sufficient to configure the system.
  • the system management specification of the Fieldbus protocol defines three states for a device including an INITIALIZED state, an UNINITIALIZED state, and a system management operational (SM OPERATIONAL) state.
  • the three defined states are sufficient to describe the behavior of a device from the perspective of the system management, but are not adequate for describing a device from the perspective of either the fieldbus interface or software engineering tools for analyzing, controlling, or displaying the status of a device.
  • This insufficiency is highly notable when configuration involves the operation of commissioning a device that is attached to the Fieldbus link in an UNINITIALIZED state.
  • a control system controls one or more interconnected devices according to a defined control configuration.
  • the control system automatically senses a device that is connected to the control system but not included in the control configuration definition.
  • the control system supplies initial interconnect information to the connected device sufficient to upload configuration parameters from the device to the control system.
  • a digital control system with a predetermined configuration automatically senses the connection to a network of a digital device that is not included in the predetermined configuration.
  • the digital device is assigned temporary address information and placed in a temporary state, called a standby state, in which the digital device supplies information to the digital control system allowing a user to access the digital device including access of device information and configuration parameters.
  • a user selectively commissions the digital device by assigning a physical device tag, and a device address, and installing a control strategy to the digital device, thereby placing the digital device in an operational state in communication with the digital control system.
  • a user In the standby state, a user interrogates to determine the type of device that is attached, determines the rule of the device in the context of the digital control system assigns a physical device tag that assigns the determined role to the device, and verifies connection of the device to the network. Also in the standby state, the user initiates other applications applied to the device, including calibration of the device and configuring the device within the overall control scheme of the digital control system.
  • a control system differentiates between Fieldbus device states beyond the states defined according to the Fieldbus standard specification.
  • the control system sets a physical device tag equal to the device identification (ID) for the devices that do not have tags, while the device is autosensed.
  • ID device identification
  • a device attached to the Fieldbus link with the physical device tag set equal to the device ID is controlled in the manner of an UNINITIALIZED device.
  • automatic sensing of field devices is extended beyond a conventional input/output level to the configuration of Fieldbus devices by a digital control system.
  • a digital control system with a predetermined configuration automatically senses the connection to a network of a digital device that is not included in the predetermined configuration.
  • the digital device is placed in a temporary state, called a standby state, in which the digital device supplies information to the digital control system allowing a user to access the digital device, including access of device information and configuration parameters.
  • the digital control system formats and displays the device information upon request by a user.
  • the digital control system program also includes an automatic configuration program that responds to sensing of a new controller by automatically configuring the input/output (I/O) subsystem.
  • the user adds a new controller without setting any physical switches or nodes.
  • a user optionally supplies configuration information for a device into a database, prior to connection of a device. Upon connection of the device, the device is automatically sensed and configured using the database configuration information, without setting of physical switches on the devices.
  • a process control system includes a process, a plurality of controllers connected to the process, a workstation connected to the plurality of controllers and including a user interface, and a software system including a network operating system, a user interface, and implementing an automatic sensing routine.
  • the automatic sensing routine includes an executable logic for automatically sensing a connection of a device to a network and placing the device in a state accessible for communication by a user via a user interface. In the accessible state, a user commissions the device and selectively initiates device-related applications.
  • One advantage is that configuration of a control system is greatly facilitated.
  • the physical connection of a device to the network automatically initiates inclusion of the connected device into the control system.
  • the described system and method advantageously facilitates conformity between the configuration of a network and the physical interconnections of the network that serves as the basis for the configuration.
  • the described system and method assist programming of field devices from a remote location so that individual field setting of the devices, using a local setting device, is not necessary.
  • the system and method support central programmability is highly useful to reduce system management costs and for reducing downtime of a process control system.
  • a further advantage is that configuration of the entire system, rather setting of individual devices, leads to a system in which individual system settings are highly compatible.
  • FIG. 1 is a pictorial view of a front-of-screen display for a graphical user interface (GUI) displaying a system configuration.
  • GUI graphical user interface
  • FIG. 2 is a state transition diagram illustrating various states of a field device.
  • FIG. 3 is a flow chart illustrating a first operation of commissioning a new device.
  • FIG. 4 is a flow chart illustrating a second operation of commissioning an unbound.
  • FIG. 5 is a flow chart illustrating a third operation of decommissioning a device.
  • FIG. 6 is a flow chart illustrating a fourth operation of attaching a commissioned device without enablement of operational powerup.
  • FIG. 7 is a flow chart illustrating a fifth operation of replacing a device.
  • FIG. 8 is a flow chart illustrating a sixth operation of attaching an UNRECOGNIZED device.
  • FIG. 9 is a flow chart illustrating a seventh operation of decommissioning an unrecognized device.
  • FIG. 10 is a flow chart illustrating an eighth operation of placing a decommissioned device in a standby condition.
  • FIGS. 11A , 11 B and 11 C illustrate a screen display, a first schematic block diagram and a second schematic block diagram respectively, process control systems in accordance with a generalized embodiment of the present invention which furnishes a capability to create a new control template and a capability to modify an existing control template for only one view, such as an engineering view.
  • FIG. 12 is a schematic block diagram showing the process control environment in a configuration implementation and a run-time implementation.
  • FIG. 13 is a block diagram illustrating a user interface for usage with both configuration and run-time models of the process control environment.
  • FIG. 14 is a schematic block diagram which depicts a hierarchical relationship among system objects of a configuration model in accordance with an embodiment of the present invention.
  • FIG. 15 illustrates a method for automatically sensing and incorporating a controller/multiplexer into a run-time system.
  • FIG. 16 is a flow chart illustrates steps of an automatic configuration routine for configuring a physical I/O device.
  • a front-of-screen display also called a “screen” 100
  • GUI graphical user interface
  • the screen 100 depicts navigation selections which are operated by a user to select, construct and operate a process control configuration.
  • the navigation program supplies an initial state for navigating across various tools and processors in a network.
  • a user controls the navigation program to access libraries, areas, process control equipment and security operations.
  • the illustrative system configuration is described and controlled with respect to a control system setup 102 , control strategies 104 , and a physical setup 106 .
  • the functions of automatically sensing and automatically configuring a control system relate to the physical setup 106 .
  • the functions of automatically sensing and automatically configuring physical devices in a control system relate to the commission and activation of devices in the control network 108 , and the decommissioning of controllers 110 .
  • a process control system controls various devices attached to a process control network in accordance with a Fieldbus standard protocol.
  • a Fieldbus protocol a standard user application is defined based on blocks.
  • a block is a representation of various different types of application functions. Types of blocks include resource blocks, function blocks, and transducer blocks.
  • a resource block describes characteristics of a fieldbus device such as a device name, manufacturer, and serial number.
  • a device includes only a single resource block.
  • a function block defines the control system behavior. Input and output parameters of function blocks may be linked over the fieldbus. The execution of each function block is precisely scheduled.
  • a user application may include numerous function blocks. Examples of standard function blocks include analog input (AI), analog output (AO), bias (B), Control Selector (CS), Discrete Input (DI), Discrete Output (DO), Manual Loader (ML), Proportional/Derivative (PD), Proportional/Integral/Derivative (PID) and ratio (RA).
  • Function blocks are built into fieldbus devices to define a selected device functionality. In one example, a simple temperature transmitter may contain an Al function block.
  • a control valve often includes a PID function block and an AO block.
  • a transducer block decouples function blocks from local input and output functions for reading sensors and commanding output hardware.
  • Transducer blocks contain information such as calibration data and sensor type.
  • a user application uses one transducer block for each input or output function block.
  • Another object defined in the user application includes link objects for defining the links between function block inputs and outputs internal to the device and across the fieldbus network.
  • Trend objects allow local trending of function block parameters for access by other devices.
  • Alert objects are used to allow reporting of alarms and events on the fieldbus.
  • View objects are predefined groupings of block parameter sets that are used in the human/machine interface.
  • the function block specification defines four views for each type of block.
  • a state transition diagram illustrates the various states of a field device.
  • the field device states include an offline state 202 , an unrecognized state 204 , a standby state 206 , a commissioned state 208 , and an unbound state 210 .
  • the state of a field device is determined by several parameters including a system management state (SM-State), a physical device tag (PD-Tag), a device address, device revision information (Rev*), and a device identification (Device-ID).
  • a device in the commissioned state 208 is a Fieldbus device that is available for control strategy configuration and installation.
  • a decommissioned device is a device that has been removed from the commissioned state 208 .
  • a state transition T 1 is caused by the event in which a field device residing at a temporary address is queried with a system management identify service (SM-IDENTIFY) and the query determines that the device has a cleared physical device tag.
  • the state transition T 1 changes from a NULL state to an OFFLINE state by allocating a standby address for the field device.
  • Executing logic typically in the form of firmware, software, or hardware, executes a set physical device tag service (SET-PD-TAG) to set the physical device tag identical to the device identification of the field device.
  • Executing logic also uses a set device address service (SET-ADDRESS) to send a standby address to the field device.
  • SET-PD-TAG set physical device tag service
  • SET-ADDRESS set device address service
  • a state transition T 2 is caused by the event in which a field device residing at a temporary address is queried with a system management identify service (SM-IDENTIFY) and the query determines that the device has a physical device tag that is identical to the device identification of the device.
  • the state transition T 2 changes from a NULL state to an OFFLINE state by allocating a standby address for the field device.
  • Executing logic uses a set device address service (SET-ADDRESS) to send a standby address to the field device.
  • SET-ADDRESS set device address service
  • a state transition T 3 is caused by the event in which a field device residing at a temporary address is queried with a system management identify service (SM-IDENTIFY) and the query determines that the device has a physical device tag and a device identification configured for the current process control system network link.
  • the state transition T 3 changes from a NULL state to an OFFLINE state using executing logic that employs the set device address service (SET-ADDRESS) to send an assigned address to the field device.
  • SET-ADDRESS set device address service
  • a state transition T 4 is caused by the event in which a field device residing at a temporary address is queried with a system management identify service (SM-IDENTIFY) and the query determines that the device has a physical device tag and a device identification not configured for the current process control system network link.
  • the state transition T 4 changes from a NULL state to an UNRECOGNIZED state.
  • a state transition T 5 is caused by an event in which the device appears at a temporary address and the device is being commissioned by a user.
  • the state transition T 5 changes from an OFFLINE state to an OFFLINE state using executing logic, typically in the form of firmware, software, or hardware, that executes a set physical device tag service (SET-PD-TAG) to clear the physical device tag of the field device.
  • Executing logic also executes a set physical device tag service (SET-PD-TAG) to send an assigned physical device tag to the field device.
  • Executing logic further uses a set device address service (SET-ADDRESS) to send an assigned address to the field device.
  • a state transition T 6 is caused by an event in which the device appears at a temporary address and the device is being decommissioned by a user.
  • the state transition T 6 changes from an OFFLINE state to an OFFLINE state using executing logic that executes a set physical device tag service (SET-PD-TAG) to clear the physical device tag of the field device.
  • SET-PD-TAG set physical device tag service
  • a state transition T 7 is caused by an event in which a user requests to place a decommissioned device in standby.
  • the state transition T 7 changes from an OFFLINE state to an OFFLINE state by allocating a standby address for the field device.
  • Executing logic executes a set physical device tag service (SET-PD-TAG) to set the physical device tag identical to the device identification of the field device.
  • Executing logic also uses a set device address service (SET-ADDRESS) to send a standby address to the field device.
  • SET-PD-TAG set physical device tag service
  • SET-ADDRESS set device address service
  • a state transition T 8 is caused by an event in which the field device appears at the standby address.
  • the state transition T 8 changes from an OFFLINE state to a STANDBY state through executing logic that reads device revision information from the resource block.
  • a state transition T 9 is caused by an event in which the field device appears at the assigned address.
  • the state transition T 9 changes from an OFFLINE state to a COMMISSIONED.
  • a state transition T 10 is caused by a user requesting to commission a device in the STANDBY state.
  • the state transition T 10 changes from the STANDBY state to the OFFLINE state through executing logic that uses a clear address service (CLEAR-ADDRESS) to clear the device address.
  • CLAR-ADDRESS clear address service
  • a state transition T 11 is caused by a user requesting to decommission a device in the STANDBY state.
  • the state transition T 11 changes from the STANDBY state to the OFFLINE state through executing logic that uses a clear address service (CLEAR-ADDRESS) to clear the device address.
  • CLAR-ADDRESS clear address service
  • a state transition T 12 is caused by a user requesting to decommission a device in the COMMISSIONED state.
  • the state transition T 12 changes from the COMMISSIONED state to the OFFLINE state through executing logic that uses a clear address service (CLEAR-ADDRESS) to clear the device address.
  • CLAR-ADDRESS clear address service
  • a state transition T 13 is caused by a user requesting to decommission a device in the INITIALIZED state of the Fieldbus system management states.
  • the state transition T 13 changes from the UNRECOGNIZED state to the OFFLINE state through executing logic that executes a set physical device tag service (SET-PD-TAG) to clear the physical device tag of the field device.
  • SET-PD-TAG set physical device tag service
  • a state transition T 14 is caused by a user requesting to decommission a device in the SM-OPERATIONAL state of the Fieldbus system management states.
  • the state transition T 14 changes from the UNRECOGNIZED state to the OFFLINE state through executing logic that uses a clear address service (CLEAR-ADDRESS) to clear the device address.
  • CLAR-ADDRESS clear address service
  • a Fieldbus device has a unique device address (network address) and a unique physical device tag.
  • Each device connected to the process control system network link has a unique node designator.
  • a data link specification specifies a range of allowable values for node designators including a range for permanent devices, a range for temporary addresses, and a range for visitor devices.
  • the temporary addresses are used by devices that are not presently in the SM-OPERATIONAL state.
  • the Fieldbus interface maintains partitioning of the address space for permanent devices into three sets. One set, called “assigned addresses”, includes addresses assigned to devices with a specific physical device tag, regardless of whether the device is present on the bus.
  • the assigned addresses is assigned using a software engineering tool on the basis of information input by a user relating to Link-Active-Scheduler takeover preference.
  • a second set termed “standby addresses”, describes devices in the SM-OPERATIONAL state but have no device addresses assigned.
  • the standby addresses are managed by the Fieldbus interface.
  • the third set of addresses are addresses outside the first and second sets and refer to unused addresses.
  • Standby addresses are defined and utilized to support functionality of the autosensing and online address assignment operations.
  • the assigned address set and the standby address set are defined to be equal to the number of potential devices connected to the process control system network link. For example, if sixteen devices may be potentially connected to the process control system network, then sixteen assigned addresses are defined and sixteen standby addresses are defined.
  • the device revision information includes a manufacturer's identification (MANUFAC-ID), a device type (DEV-TYPE), a device revision (DEV-REV), and a device description revision (DD-REV).
  • MANUFAC-ID manufacturer's identification
  • DEV-TYPE device type
  • DEV-REV device revision
  • DD-REV device description revision
  • the offline state 202 includes device states having a plurality of parameter combinations.
  • the system management state is UNINITIALIZED and the physical device tag is cleared.
  • the system management state is INITIALIZED and the physical device tag is read from the physical device and displayable on a screen.
  • the device address is a temporary address, the revision information is not available, and the device identification is read from the device and displayable on the screen.
  • the unrecognized state 204 includes device states having a plurality of parameter combinations.
  • the system management state is INITIALIZED with a device address that is a temporary address.
  • the system management state is SM-OPERATIONAL with a device address that is a standby address or an assigned address.
  • the physical device tag is read from the device and displayable on the screen, the device revision is not available, and the device identification is read from the device and displayable on the screen.
  • a Link-Active-Scheduler is a deterministic centralized bus scheduler that includes a list of transmit times for all data buffers in all devices that are to be cyclically transmitted. When a device is due to send a data buffer, the Link-Active-Scheduler issues a compel data (CD) message to the device.
  • CD compel data
  • the device Upon receipt of the CD message, the device broadcasts or “publishes” the data in the buffer to all devices on a field device bus and the broadcasting device is defined to be a “publisher”. Any device that is configured to receive the data is defined to be a “subscriber”. Scheduled data transfers are typically used for the regular, cyclic transfer of control loop data between devices on the fieldbus.
  • the system management state is SM-OPERATIONAL
  • the physical device tag is equal to the device identification
  • the device address is a standby address.
  • the device revision information is read from the field device and displayable.
  • the device identification is read from the device and displayable on the screen.
  • the unbound state 210 is a configuration placeholder for a field device that is to be physically attached subsequently.
  • the unbound state 210 supports configuration of control strategies utilizing the function blocks in a field device that is not yet connected.
  • the system management state is not yet applicable but the physical device tag is specified by a user and the device address is assigned by the user.
  • the device revision information set according to the most recent commission or configuration. The device identification is cleared.
  • the field device is available for control strategy configuration and installation.
  • the system management state is SM-OPERATIONAL
  • the physical device tag is specified by a user
  • the device address is assigned by the user.
  • the device revision information is read from the field device and displayable on the screen.
  • the device identification is read from the field device, stored in a field configuration database, and displayable on a display screen.
  • a flow chart illustrates a first operation or “use case” which describes an operation of commissioning a new device 300 .
  • the Fieldbus interface Prior to the commissioning of the new device, the Fieldbus interface is operational.
  • a device Prior to the commissioning of the new device, the Fieldbus interface is operational.
  • a device is connected to the process control system network. The device either has no physical device tag or has a physical device tag that is equal to the device identification.
  • the operation of commissioning a new device 300 results in a condition in which the device is assigned a new physical device tag and a device address, and the device is ready for function block configuration.
  • the new field device is entered into the process control system network database with the device identification bound and the device revision information set.
  • An engineering software tool that displays the process control system network status displays the new device as a COMMISSIONED device.
  • a “live list” is a list of all devices that are properly responding to a pass token (PT) message. All devices on a fieldbus are allowed to send unscheduled messages between the transmission of scheduled messages.
  • the Link-Active-Scheduler grants permission to a device to use the fieldbus by issuing a pass token (PT) message to the device.
  • PT pass token
  • the device receives the PT, it is allowed to send messages until the messages are complete or until a maximum allotted token hold time has expired.
  • the Link-Active-Scheduler accesses a CD schedule containing a list of actions that are set to occur on a cyclic basis.
  • the Link-Active-Scheduler sends a compel data (CD) message to a specific data buffer in the fieldbus device.
  • the device immediately broadcasts a message to all devices on the fieldbus.
  • the Link-Active-Scheduler performs remaining operations between scheduled transfers.
  • the Link-Active-Scheduler continually adds new devices to the field bus by periodically sending probe node (PN) messages to addresses that are not on the live list. If a device is present at the address and receives the PN, the device immediately returns a probe response (PR) message. If a device responds with the PR message, the Link-Active-Scheduler adds the device to the live list and confirms by sending the device a node activation (NA) message.
  • PN probe node
  • PR probe response
  • a device remains on the live list so long as the device responds properly to PTs.
  • the Link-Active-Scheduler broadcasts changes to the live list to all devices to allow each device to maintain a current copy of the live list.
  • a second step 304 the interface queries the field device using a system management identify service (SM-IDENTIFY) and determines whether the field device is in the UNINITIALIZED state with no physical device tag set or in the INITIALIZED state having a physical device tag that is equal to the device identification. The interface then allocates 306 a standby address for the field device.
  • SM-IDENTIFY system management identify service
  • a logical step 308 directs that a previously UNINITIALIZED device, in step 310 , sets the physical device tag of the field device identical to the device identification using a set physical device tag service (SET-PD-TAG), thereby placing the field device in the INITIALIZED state.
  • the standby address is sent to the field device 312 using a set address service (SET-ADDRESS), advancing the field device from the INITIALIZED state to the SM-OPERATIONAL state. At this point the field device appears in the “live list” at a standby address 314 .
  • Device revision information is read from the resource block 316 .
  • an executing software engineering tool displays the field device as a STANDBY device.
  • a new user assigns a new physical device tag to the field device.
  • the physical device tag is constrained to be unique and not the same as the device identification.
  • a device address is assigned to the field device using a software engineering tool and the Link-Active-Scheduler takeover preference is set to “selectable”.
  • the device revision information is read from the field device and written to the process control system network database.
  • the interface changes the state of the field device 322 to the INITIALIZED state using a clear address service (CLEAR-ADDRESS).
  • the field device appears in the “live list” at a temporary address 324 .
  • the interface queries the field device using a system management identify service (SM-IDENTIFY) and recognizes the field device by the device identification.
  • the interface uses the set physical device tag service (SET-PD-TAG) to clear the physical device tag 328 , thereby changing the field device state to the UNINITIALIZED state.
  • the set physical device tag service (SET-PD-TAG) is then used to send the assigned physical device tag to the field device 330 , changing the field device state to the INITIALIZED state.
  • the set address service (SET-ADDRESS) is called to send the assigned address to the field device 332 , placing the field device in the system management operational state (SM-OPERATIONAL).
  • the field device appears in the “live list” at the assigned address 334 .
  • the device identification is bound 336 to the device.
  • the software engineering tool displays the field device as a COMMISSIONED device.
  • a flow chart illustrates a second operation or “use case” which describes an operation of commissioning an unbound device 400 .
  • the Fieldbus interface Prior to the commissioning of the unbound device, the Fieldbus interface is operational.
  • a field device has been created in the process control system network database and a physical device tag and a device address are assigned to the field device. However, the field device is not bound to a device identification.
  • the process control system network database has also been initialized to contain device revision information read from the field device.
  • a software engineering tool displays the field device as an UNBOUND device.
  • the UNBOUND device to be commissioned is either a field device with no physical device tag or a field device having a physical device tag that is identical to the device identification.
  • the UNBOUND field device is commissioned to place the field device on the process control system network link.
  • the operation of commissioning an UNBOUND device 400 results in a condition in which the device is configured with a physical device tag and an assigned device address, and the device is ready for function block configuration.
  • the new field device is entered into the process control system network database with the device identification bound.
  • An engineering software tool that displays the process control system network status displays the device as a COMMISSIONED device.
  • a first step 402 the field device appears in the “live list” at a temporary address.
  • the interface queries the field device using a system management identify service (SM-IDENTIFY) and determines whether the field device is in the UNINITIALIZED state with no physical device tag set or in the INITIALIZED state having a physical device tag that is equal to the device identification. The interface then allocates 406 a standby address for the field device.
  • SM-IDENTIFY system management identify service
  • a logical step 408 directs that a previously UNINITIALIZED device, in step 410 , sets the physical device tag of the field device identical to the device identification using a set physical device tag service (SET-PD-TAG), thereby placing the field device in the INITIALIZED state.
  • the standby address is sent to the field device 412 using a set address service (SET-ADDRESS), advancing the field device from the INITIALIZED state to the SM-OPERATIONAL state. At this point the field device appears in the “live list” at a standby address 414 .
  • Device revision information is read from the resource block 416 .
  • an executing software engineering tool displays the field device as a STANDBY device.
  • a user assigns a physical device tag to the field device by associating the field device with the pre-configured device.
  • the device revision information is read from the field device to ascertain that the information matches the device revision information in the process control system network database for the preconfigured device. If the device revision information of the device does not match the database, the user may override the database, reading the device revision information from the field device and writing the information to the process control system network database. Alternatively, the device revision information for an UNBOUND device may be made blank, allowing any physical device to be bound with the UNBOUND device.
  • the interface changes the state of the field device 422 to the INITIALIZED state using a clear address service (CLEAR-ADDRESS). The field device appears in the “live list” at a temporary address 424 .
  • the interface queries the field device using a system management identify service (SM-IDENTIFY) and recognizes the field device by the device identification.
  • the interface uses the set physical device tag service (SET-PD-TAG) to clear the physical device tag 428 , thereby changing the field device state to the UNINITIALIZED state.
  • the set physical device tag service (SET-PD-TAG) is then used to send the assigned physical device tag to the field device 430 , changing the field device state to the INITIALIZED state.
  • the set address service (SET-ADDRESS) is called to send the assigned address to the field device 432 , placing the field device in the system management operational state (SM-OPERATIONAL).
  • the field device appears in the “live list” at the assigned address 434 .
  • the device identification is bound 436 to the device.
  • the software engineering tool displays the field device as a COMMISSIONED device.
  • a flow chart illustrates a third operation or “use case” which describes an operation of decommissioning a device 500 .
  • a field device is decommissioned for several reasons. For example, when a Fieldbus device is obsolete, a user may wish to clear a network interconnection structure of nonfunctioning branches so that the process control system no longer expends resources on the obsolete device. Also, a user may suspect that a Fieldbus device is malfunctioning and degrading operations of a segment of a network interconnection structure. The user may diagnose the problem by having the process control system ignore the suspected Fieldbus device temporarily to determine whether the remaining devices in the segment operate properly.
  • the Fieldbus interface and the field device Prior to the operation of decommissioning a device, the Fieldbus interface and the field device are operational and the field device appears in the live list at the assigned or standby address.
  • a software engineering tool displays the field device as a COMMISSIONED or STANDBY device.
  • the software engineering tool executes a routine that prepares the field device for decommissioning, for example by clearing function block tags and clearing an OPERATIONAL-POWERUP flag.
  • the operation of decommissioning a device results in a condition in which the physical device tag of the field device is cleared and the field device is prepared to be removed from the process control system network link.
  • the process control system network database entry for the field device designates the device identification as in an unbound condition.
  • the software engineering tool displays the device identification as an UNBOUND device and displays the physical device as an OFFLINE device.
  • the operation of decommissioning a device 500 begins when a user selects a “Decommission” operation for the field device 502 .
  • a graphic user interface includes a software engineering tool that issues a “Decommission” command to an appropriate controller within the process control system.
  • the decommission command specifies a target I/O subsystem, card and port identifiers, and the device identification of the field device to be decommissioned.
  • the device identification is specified since another device with the same physical device tag may be present in an UNRECOGNIZED state.
  • the interface changes the state of the field device 504 to the INITIALIZED state using a clear address service (CLEAR-ADDRESS).
  • the field device appears in the “live list” at a temporary address 506 .
  • the interface queries the field device using a system management identify service (SM-IDENTIFY) and recognizes the field device by the physical device tag and the device identification.
  • SM-IDENTIFY system management identify service
  • the interface uses the set physical device tag service (SET-PD-TAG) to clear the physical device tag 510 , thereby changing the field device state to the UNINITIALIZED state.
  • SET-PD-TAG set physical device tag service
  • the device identification is unbound and the software engineering tool displays the field device as an UNBOUND device 512 .
  • the software engineering tool displays the field device as an OFFLINE device.
  • a network interface card stores a designation that the field device has been decommissioned 516 and does not move the field device to a STANDBY address unless directed by the user. If the decommissioned device is not move to a STANDBY address, the interface card tracks the field device until the field device advances off the live list.
  • a flow chart illustrates a fourth operation or “use case” which describes an operation of attaching a commissioned device without enablement of operational powerup 600 .
  • the Fieldbus interface Prior to the operation of attaching a commissioned device 600 , the Fieldbus interface is operational. The configuration of the Fieldbus interface includes the field device in an attached condition. The physical device tag and the device identification of the field device are matched. Following the operation of attaching a commissioned device 600 , the field device has an assigned address.
  • the field device appears in the “live list” at a temporary address 602 .
  • the interface queries the field device using a system management identify service (SM-IDENTIFY) and recognizes the field device by the physical device tag and the device identification as part of the Fieldbus interface configuration.
  • the set address service (SET-ADDRESS) is called to send the assigned address to the field device 606 , placing the field device in the system management operational state (SM-OPERATIONAL).
  • SM-IDENTIFY system management identify service
  • SET-ADDRESS system management operational state
  • the field device appears in the “live list” at the assigned address 608 .
  • a flow chart illustrates a fifth operation or “use case” which describes an operation of replacing a device 700 .
  • a device is replaced by decommissioning the current field device 702 connected to the process control system network link, if possible, and commissioning a replacement to the UNBOUND device 704 .
  • the step of decommissioning the current field device 702 is described in detail with reference to FIG. 5 .
  • the step of commissioning a replacement to the UNBOUND device 704 is described with reference to FIG. 4 .
  • a flow chart illustrates a sixth operation or “use case” which describes an operation of attaching an UNRECOGNIZED device 800 .
  • the Fieldbus interface Prior to the operation of attaching a commissioned device 600 , the Fieldbus interface is operational. A field device is attached which has a physical device tag and a device identification that is not configured for the current process control system network link. Following the operation of attaching an UNRECOGNIZED device 800 , the field device is identified and the software engineering tool displays the device as n UNRECOGNIZED device. The operation of attaching an UNRECOGNIZED device 800 may be performed without use of the software engineering tool.
  • the field device appears in the “live list” 802 .
  • the interface queries the field device using a system management identify service (SM-IDENTIFY) and determines that the physical device tag and the device identification do not match a field device in the present configuration.
  • SM-IDENTIFY system management identify service
  • a flow chart illustrates a seventh operation or “use case” which describes an operation of decommissioning an unrecognized device 900 .
  • the Fieldbus interface Prior to the operation of decommissioning an unrecognized device, the Fieldbus interface is operational.
  • the field device is identified which has a physical device tag and a device identification that are not configured for the present process control system network link.
  • a software engineering tool displays the field device as an UNRECOGNIZED device.
  • the operation of decommissioning an unrecognized device 900 results in a condition in which the physical device tag of the field device is cleared and the field device is prepared to be removed from the process control system network link.
  • the software engineering tool displays the field device as an OFFLINE device.
  • the operation of decommissioning an unrecognized device 900 begins when a user selects a “Decommission” operation for the field device 902 .
  • a graphic user interface includes a software engineering tool that issues a “Decommission” command to an appropriate controller within the process control system.
  • the decommission command specifies a target I/O subsystem, card and port identifiers, and the device identification of the field device to be decommissioned.
  • logic step 904 directs the decommissioning operation 900 to a clear the physical device tag step 912 . Otherwise, the interface changes the state of the field device 906 to the INITIALIZED state using a clear address service (CLEAR-ADDRESS). The field device appears in the “live list” at a temporary address 908 .
  • the interface queries the field device using a system management identify service (SM-IDENTIFY) and recognizes the field device by the physical device tag and the device identification.
  • the interface uses the set physical device tag service (SET-PD-TAG) to clear the physical device tag 912 , thereby changing the field device state to the UNINITIALIZED state.
  • the software engineering tool displays the field device as an OFFLINE device.
  • a network interface card stores a designation that the field device has been decommissioned 916 and does not move the field device to a STANDBY address unless directed by the user. If the decommissioned device is not move to a STANDBY address, the interface card tracks the field device until the field device advances off the live list.
  • a flow chart illustrates an eighth operation or “use case” which describes an operation of placing a decommissioned device in a standby condition 1000 .
  • the Fieldbus interface Prior to the operation of placing a decommissioned device in a standby condition 1000 , the Fieldbus interface is operational. A field device is decommissioned and in the OFFLINE state.
  • the operation of placing a decommissioned device in standby 1000 results in a condition in which the field device is placed at a standby address with the physical device tag of the field device set identical to the device identification.
  • the software engineering tool displays the field device as a STANDBY device.
  • the operation of placing a decommissioned device in standby 1000 begins when a user selects a “Place in Standby” operation for the field device 1002 .
  • a graphic user interface includes a software engineering tool that issues a “Place in Standby” command to an appropriate controller within the process control system 1004 .
  • the decommission command specifies a target I/O subsystem, card and port identifiers, and the device identification of the field device to be placed in standby.
  • the interface allocates a standby address 1006 for the field device.
  • the set physical device tag service (SET-PD-TAG) is then used to set the physical device tag identical to the device identification 1008 , changing the field device state to the INITIALIZED state.
  • the set address service (SET-ADDRESS) is called to send the standby address to the field device 1010 , placing the field device in the system management operational state (SM-OPERATIONAL).
  • the field device appears in the “live list” at the standby address 1012 .
  • Device revision information is read from the resource block 1014 .
  • an executing software engineering tool displays the field device as a STANDBY device.
  • a user may subsequently commission the field device 1018 , either by creating a new device or binding the field device to an UNBOUND device in the process control system network database.
  • the techniques for commissioning a device are described with respect to FIGS. 3 and 4 .
  • the system 1 includes a main processing device, such as personal computer 2 , that is connected to a local area network (“LAN”) 3 via a local area network card.
  • LAN local area network
  • a non-proprietary ethernet protocol is beneficial in many applications because it allows for communications with the local area network 3 .
  • the local area network 3 is dedicated to carrying control parameters, control data and other relevant information concerned in the process control system.
  • the LAN 3 may be referred to as an area controlled network or ACN 3 .
  • the ACN 3 may be connected to other LANs for sharing information and data via a hub or gateway without affecting the dedicated nature of ACN 3 .
  • a plurality of physical devices may be connected to the ACN 3 at various “nodes.” Each physical device connected to the ACN 3 is connected at a node and each node is separately addressable according the LAN protocol used to implement ACN 3 .
  • ACN 3 may be desirable to construct ACN 3 from two or more ethernet systems such that the failure of a single ethernet or LAN system will not result in the failure of the entire system.
  • redundant ethernets the failure of one ethernet LAN can be detected and an alternate ethernet LAN can be mapped in to provide for the desired functionality of ACN 3 .
  • the main personal computer (“PC”) A forms a node on the ACN 3 .
  • the PC 2 may, for example, be a standard personal computer running a standard operating system such as Microsoft's Window NT system.
  • Main PC 2 is configured to generate, in response to user input commands, various control routines that are provided via the ACN 3 to one or more local controllers identified as element 4 and 5 which implement the control strategy defined by the control routines selected and established in main PC 2 .
  • Main PC 2 may also be configured to implement direct control routines on field devices such as pumps, valves, motors and the like via transmission across the ACN 3 , rather than through a local controller 4 or 5 .
  • Local controllers 4 and 5 receive control routines and other configuration data through the ACN 3 from PC 2 .
  • the local controllers then generate signals of various types to various field devices (such as pumps, motors, regulator valves, etc.) 6 through 15 which actually implement and perform physical steps in the field to implement the control system established by the routines provided by PC 2 .
  • field devices 6 through 10 Two types of field devices may be connected to local controller 4 and 5 including field devices 6 through 10 which are responsive to specific control protocol such as FieldBus, Profibus and the like.
  • specific control protocol such as FieldBus, Profibus and the like.
  • there are standard control protocols e.g. FieldBus
  • a protocol-friendly field devices e.g., a Fieldbus field devices
  • field devices 6 through 11 receive protocol specific (e.g., FieldBus) control commands from either the local controllers 4 and 5 or the personal computer 2 to implement a field device-specific function.
  • non-protocol field devices 12 through 15 are Also connected to local controllers 4 and 5 , which are referred to as non-protocol because they do not include any local processing power and can respond to direct control signals. Accordingly, field devices 12 through 15 are not capable of implementing functions that would be defined by specific control protocol such as the FieldBus control protocol.
  • Protocol-friendly e.g., FieldBus specific
  • this same functionality allows for the implementation of the protocol-specific control routines to be distributed between the local field devices 6 through 11 , the local controllers 4 and 5 and the personal computer 2 .
  • FIG. 11B refers to one portion of the system shown in FIG. 11A , specifically the personal computer 2 , the ethernet 3 , local controller 4 , a smart field device 6 and a dumb device 12 , in greater detail.
  • Personal computer 2 includes program software routines for implementing standard functional routines of a standard control protocol such as the FieldBus protocol. Accordingly, personal computer 2 is programmed to receive FieldBus commands and to implement all of the functional routines for which a local field device having Fieldbus capabilities could implement. The ability and steps required to program personal computer 2 to implement FieldBus block functionality will be clearly apparent to one of ordinary skill in the art.
  • Local controller 4 Connected to personal computer 2 by the ethernet 3 is local controller 4 .
  • Local controller 4 includes a central processing unit connected to a random access memory which provides control signals to configure the central processing unit to implement appropriate operational functions.
  • a read only memory is connected to the random access memory.
  • the read only memory is programmed to include control routines which can configure the central processing unit to implement all of the functional routines of a standard control protocol such as FieldBus.
  • Personal computer 2 sends signals through ethernet 3 to the local controller 4 which causes one, more or all of the programmer routines in the read only memory to be transferred to the random access memory to configure the CPU to implement one, more or all of the standard control protocol routines such as the FieldBus routines.
  • the smart field device 6 includes a central processing unit which implements certain control functions. If the devices is, for example, a FieldBus device then the central processing unit associated with the smart field device 6 is capable of implementing all of the FieldBus functionality requirements.
  • controller 4 operates so that non-protocol device 12 acts and is operated as a FieldBus device. For example, if a control routine is running either in personal computer 2 or on the CPU of local controller 4 , that control routine can implement and provide FieldBus commands to FieldBus device 6 and non-protocol device 12 , operating as a FieldBus device. Since field device 6 is a FieldBus device, device 6 receives these commands and thereby implements the control functionality dictated by those commands. Non-protocol device 12 , however, works in conjunction with the central processing unit of local controller 4 to implement the FieldBus requirements such that the local controller in combination with the field device implements and operates FieldBus commands.
  • non-FieldBus device 12 In addition to allowing non-FieldBus device 12 to act and operate as a FieldBus device, the described aspect allows for distribution of FieldBus control routines throughout the system 1 shown in FIG. 11 A.
  • the system 1 allows for control to be divided between the local controller 4 and the local controller 5 such that a portion of the FieldBus control routines are being implemented by local controller 5 and other FieldBus routines are implemented by the use of the FieldBus routines stored on local controller 4 .
  • the division of FieldBus routine implementation may allow for more sophisticated and faster control and more efficient utilization of the overall processing power of the system.
  • the FieldBus routines are further distributed between the local controller 4 and the personal computer 2 .
  • the system allows personal computer 2 to implement one or all of the FieldBus routines for a particular control algorithm.
  • system allows for the implementation of FieldBus controls to a non-FieldBus device connected directly to the ethernet 3 through use of the FieldBus control routines stored on personal computer 2 in the same manner that FieldBus routines are implemented on non-FieldBus device 12 through use on the FieldBus routines stored on local controller 4 .
  • a process control environment 1100 is shown in FIG. 11 C and illustrates a control environment for implementing a digital control system, process controller or the like.
  • the process control environment 1100 includes an operator workstation 1102 , a laboratory workstation 1104 , and an engineering workstation 1106 electrically interconnected by a local area network (“LAN”) 1108 for transferring and receiving data and control signals among the various workstations and a plurality of controller/multiplexers 1110 .
  • the workstations 1102 , 1104 , 1106 are shown connected by the LAN 1108 to a plurality of the controller/multiplexers 1110 that electrically interface between the workstations and a plurality of processes 1112 .
  • the LAN 1108 includes a single workstation connected directly to a controller/multiplexer 1110 or alternatively includes a plurality of workstations, for example three workstations 1102 , 1104 , 1106 , and many controller/multiplexers 1110 depending upon the purposes and requirements of the process control environment 1100 .
  • a single process controller/multiplexer 1110 controls several different processes 1112 or alternatively controls a portion of a single process.
  • a process control strategy is developed by creating a software control solution on the engineering workstation 1106 , for example, and transferring the solution via the LAN 1108 to the operator workstation 1102 , lab workstation 1104 , and to controller/multiplexer 1110 for execution.
  • the operator workstation 1102 and lab workstation 1104 supply interface displays to the control/monitor strategy implemented in the controller/multiplexer 1110 and communicates to one or more of the controller/multiplexers 1110 to view the processes 1112 and change control attribute values according to the requirements of the designed solution.
  • the processes 1112 are formed from one or more field devices, which may be smart field devices or conventional (non-smart) field devices.
  • the process 1112 is illustratively depicted as two Fieldbus devices 1132 , a HART (highway addressable remote transducer) device 1134 and a conventional field device 1136 .
  • the operator workstation 1102 and lab workstation 1104 communicate visual and audio feedback to the operator regarding the status and conditions of the controlled processes 1112 .
  • the engineering workstation 1106 includes a central processing unit (CPU) 1116 and a display and input/output or user-interface device 1118 such as a keyboard, light pen and the like.
  • the CPU 1116 typically includes a dedicated memory 1117 .
  • the dedicated memory 1117 includes a digital control system program (not shown) that executes on the CPU 1116 to implement control operations and functions of the process control environment 1100 .
  • the operator workstation 1102 , the lab workstation 1104 and other workstations (not shown) within the process control environment 1100 include at least one central processing unit (not shown) which is electrically connected to a display (not shown) and a user-interface device (not shown) to allow interaction between a user and the CPU.
  • the process control environment 1100 includes workstations implemented using a Motorola 68040 processor and a Motorola 68360 communications processor running in companion mode with the 68040 with primary and secondary ethernet ports driven by the 68360 processor (SCC 1 and SCC 3 respectively).
  • the process control environment 1100 also includes a template generator 1124 and a control template library 1123 which, in combination, form a control template system 1120 .
  • a control template is defined as the grouping of attribute functions that are used to control a process and the methodology used for a particular process control function, the control attributes, variables, inputs, and outputs for the particular function and the graphical views of the function as needed such as an engineer view and an operator view.
  • the control template system 1120 includes the control template library 1123 that communicates with the template generator 1124 .
  • the control template library 1123 contains data representing sets of predefined or existing control template functions for use in process control programs.
  • the control template functions are the templates that generally come with the system from the system designer to the user.
  • the template generator 1124 is an interface that advantageously allows a user to create new control template functions or modify existing control template functions. The created and modified template functions are selectively stored in the control template library 1123 .
  • the template generator 1124 includes an attributes and methods language generator 1126 and a graphics generator 1128 .
  • the attributes and methods language generator 1126 supplies display screens that allow the user to define a plurality of attribute functions associated with the creation of a new control template function or modification of a particular existing control template function, such as inputs, outputs, and other attributes, as well as providing display screens for enabling the user to select methods or programs that perform the new or modified function for the particular control template.
  • the graphics generator 1128 furnishes a user capability to design graphical views to be associated with particular control templates. A user utilizes the data stored by the attributes and methods language generator 1126 and the graphics generator 1128 to completely define the attributes, methods, and graphical views for a control template.
  • the data representing the created control template function is generally stored in the control template library 1123 and is subsequently available for selection and usage by an engineer for the design of process control solutions.
  • the process control environment 1100 is implemented using an object-oriented framework.
  • An object-oriented framework uses object-oriented concepts such as class hierarchies, object states and object behavior. These concepts, which are briefly discussed below, are well known in the art. Additionally, an object-oriented framework may be written using object-oriented programming languages, such as the C++ programming language, which are well-known in the art, or may be written, as is the case with the preferred embodiment, using a non-object programming language such as C and implementing an object-oriented framework in that language.
  • the building block of an object-oriented framework is an object.
  • the object is defined by a state and a behavior.
  • the state of an object is set forth by fields of the object.
  • the behavior of an object is set forth by methods of the object.
  • Each object is an instance of a class, which provides a template for the object.
  • a class defines zero or more fields and zero or more methods.
  • Fields are data structures which contain information defining a portion of the state of an object. Objects which are instances of the same class have the same fields. However, the particular information contained within the fields of the objects can vary from object to object. Each field can contain information that is direct, such as an integer value, or indirect, such as a reference to another object.
  • a method is a collection by computer instructions which can be executed in CPU 1116 by computer system software.
  • the instructions of a method are executed, i.e., the method is performed, when software requests that the object for which the method is defined perform the method.
  • a method can be performed by any object that is a member of the class that includes the method.
  • the particular object performing the method is the responder or the responding object.
  • the responder consumes one or more arguments, i.e., input data, and produces zero or one result, i.e., an object returned as output data.
  • the methods for a particular object define the behavior of that object.
  • Classes of an object-oriented framework are organized in a class hierarchy.
  • a class inherits the fields and methods which are defined by the superclasses of that class.
  • the fields and methods defined by a class are inherited by any subclasses of the class, i.e., an instance of a subclass includes the fields defined by the superclass and can perform the methods defined by the superclass. Accordingly, when a method of an object is called, the method that is accessed may be defined in the class of which the object is a member or in any one of the superclasses of the class of which the object is a member.
  • process control environment 1100 selects the method to run by examining the class of the object and, if necessary, any superclasses of the object.
  • a subclass may override or supersede a method definition which is inherited from a superclass to enhance or change the behavior of the subclass.
  • a subclass may not supersede the signature of the method.
  • the signature of a method includes the method's identifier, the number and type of arguments, whether a result is returned, and, if so, the type of the result.
  • the subclass supersedes an inherited method definition by redefining the computer instructions which are carried out in performance of the method.
  • Classes which are capable of having instances are concrete classes. Classes which cannot have instances are abstract classes. Abstract classes may define fields and methods which are inherited by subclasses of the abstract classes. The subclasses of an abstract class may be other abstract classes; however, ultimately, within the class hierarchy, the subclasses are concrete classes.
  • the process control environment 1100 exists in a configuration model or configuration implementation 1210 and a run-time model or run-time implementation 1220 shown in FIG. 12 .
  • the configuration implementation 1210 the component devices, objects, interconnections and interrelationships within the process control environment 1100 are defined.
  • the run-time implementation 1220 operations of the various component devices, objects, interconnections and interrelationships are performed.
  • the configuration implementation 1210 and the run-time implementation 1220 are interconnected by downloading.
  • the download language creates system objects according to definitions supplied by a user and creates instances from the supplied definitions. Specifically, a completely configured Device Table relating to each device is downloaded to all Workstations on startup and when the Device Table is changed.
  • a downloaded Device Table only includes data for devices for which the controller/multiplexer 1110 is to initiate communications based on remote module data configured and used in the specific controller/multiplexer 1110 .
  • the Device Table is downloaded to the controller/multiplexer 1110 when other configuration data is downloaded.
  • the download language also uploads instances and instance values.
  • the configuration implementation 1210 is activated to execute in the run-time implementation 1220 using an installation procedure. Also, network communications parameters are downloaded to each device when configuration data are downloaded and when a value is changed.
  • the process control environment 1100 includes multiple subsystems with several of the subsystems having both a configuration and a run-time implementation.
  • a process graphic subsystem 1230 supplies user-defined views and operator interfacing to the architecture of the process control environment 1100 .
  • the process graphic subsystem 1230 has a process graphic editor 1232 , a part of the configuration implementation 1210 , and a process graphic viewer 1234 , a portion of the run-time implementation 1220 .
  • the process graphic editor 1232 is connected to the process graphic viewer 1234 by an intersubsystem interface 1236 in the downloaded language.
  • the process control environment 1100 also includes a control subsystem 1240 which configures and installs control modules and equipment modules in a definition and module editor 1242 and which executes the control modules and the equipment modules in a run-time controller 1244 .
  • the definition and module editor 1242 operates within the configuration implementation 1210 and the run-time controller 1244 operates within the run-time implementation 1220 to supply continuous and sequencing control functions.
  • the definition and module editor 1242 is connected to the run-time controller 1244 by an intersubsystem interface 1246 in the download language.
  • the multiple subsystems are interconnected by a subsystem interface 1250 .
  • the configuration implementation 1210 and the run-time implementation 1220 interface to a master database 1260 to support access to common data structures.
  • Various local (non-master) databases 1262 interface to the master database 1260 , for example, to transfer configuration data from the master database 1260 to the local databases 1262 as directed by a user.
  • Part of the master database 1260 is a persistent database 1270 .
  • the persistent database 1270 is an object which transcends time so that the database continues to exist after the creator of the database no longer exists and transcends space so that the database is removable to an address space that is different from the address space at which the database was created.
  • the entire configuration implementation 1210 is stored in the persistent database 1270 .
  • the master database 1260 and local databases 1262 are accessible so that documentation of configurations, statistics and diagnostics are available for documentation purposes.
  • the run-time implementation 1220 interfaces to the persistent database 1270 and to local databases 1262 to access data structures formed by the configuration implementation 1210 .
  • the run-time implementation 1220 fetches selected equipment modules, displays and the like from the local databases 1262 and the persistent database 1270 .
  • the run-time implementation 1220 interfaces to other subsystems to install definitions, thereby installing objects that are used to create instances, when the definitions do not yet exist, instantiating run-time instances, and transferring information from various source to destination objects.
  • Device Tables are elements of the configuration database that are local to devices and, in combination, define part of the configuration implementation 1210 .
  • a Device Table contains information regarding a device in the process control environment 1100 .
  • Information items in a Device Table include a device ID, a device name, a device type, a PCN network number, an ACN segment number, a simplex/redundant communication flag, a controller MAC address, a comment field, a primary internet protocol (IP) address, a primary subnet mask, a secondary IP address and a secondary subnet mask.
  • IP internet protocol
  • FIG. 13 a block diagram illustrates a user interface 1300 for usage with both the configuration and run-time models of the process control environment 1100 shown in FIG. 11 C.
  • Part of the user interface 1300 is the ExplorerTM 1310 , an interfacing program defined under the Windows NTTM operating system which features a device-based configuration approach.
  • Another part of the user interface 1300 is a module definition editor 1320 for interfacing to the process control environment 1100 using a control-based configuration approach.
  • the Explorers 1310 is operated by a user to select, construct and operate a configuration.
  • the ExplorerTM 1310 supplies an initial state for navigating across various tools and processors in a network.
  • a user controls the ExplorerTM 1310 to access libraries, areas, process control equipment and security operations.
  • FIG. 13 illustrates the relationship between various tools that may be accessed by a task operating within the process control environment 1100 and the relationship between components of the process control environment 1100 such as libraries, areas, process control equipment and security. For example, when a user selects a “show tags” function from within an area, a “tag list builder” is displayed, showing a list of control and I/O flags. From the tag list builder, the user can use an “add tag” function to add a module to a list, thereby invoking a “module editor”.
  • a schematic block diagram illustrates a hierarchical relationship among system objects of a configuration model 1400 .
  • the configuration model 1400 includes many configuration aspects including control, I/O, process graphics, process equipment, alarms, history and events.
  • the configuration model 1400 also includes a device description and network topology layout.
  • the configuration model hierarchy 1400 is defined for usage by a particular set of users for visualizing system object relationships and locations and for communicating or navigating maintenance information among various system objects.
  • one configuration model hierarchy 1400 specifically a physical plant hierarchy, is defined for usage by maintenance engineers and technicians for visualizing physical plant relationships and locations and for communicating or navigating maintenance information among various instruments and equipment in a physical plant.
  • An embodiment of a configuration model hierarchy 1400 that forms a physical plant hierarchy supports a subset of the SP88 physical equipment standard hierarchy and includes a configuration model site 1410 , one or more physical plant areas 1420 , equipment modules 1430 and control modules 1440 .
  • the configuration model hierarchy 1400 is defined for a single process site 1410 which is divided into one or more named physical plant areas 1420 that are defined within the configuration model hierarchy 1400 .
  • the physical plant areas 1420 optionally contain tagged modules, each of which is uniquely instantiated within the configuration model hierarchy 1400 .
  • a physical plant area 1420 optionally contains one or more equipment modules 1430 .
  • An equipment module 1430 optionally contains other equipment modules 1430 , control modules 1440 and function blocks.
  • An equipment module 1430 includes and is controlled by a control template that is created according to one of a number of different graphical process control programming languages including continuous function block, ladder logic, or sequential function charting (“SFC”).
  • the configuration model hierarchy 1400 optionally contains one or more control modules 1440 .
  • a control module 1440 is contained in an object such as a physical plant area 1420 , an equipment module 1430 or another control module 1440 .
  • a control module 1440 optionally contains objects such as other control modules 1440 or function blocks.
  • the control module 1440 is thus a container class, having instances which are collections of other objects.
  • the control module 444 is encapsulated so that all of the contents and the implementation of the methods of the control module are hidden.
  • a controller/multiplexer is automatically sensed and incorporated into a run-time system as shown in FIG. 15 .
  • a controller/multiplexer upon connection to the ACN and application of power, automatically sends a request for identification or verify IP address assignment.
  • the request message includes the MAC address of the controller/multiplexer.
  • the request is handled by a “Plug&Play Network Configuration Service”, which is known in the operating system art, at a master configuration controller/multiplexer in step 2212 .
  • the “Plug&Play Network Configuration Service” receives the request from the network to assign/verify an IP address, searches a table of configured devices for a MAC address match.
  • step 2216 the “Plug&Play Network Configuration Service” responds with the Device Name, Device ID, IP Address Information, Subnet Mask Information, ACN Segment Number and other items included in the Device Table. If no match is found, in step 2218 the “Plug&Play Network Configuration Service” automatically generates a default name for the device based on the controller/multiplexer MAC address (for example, Controller-000001) The new device is added to the database in a Device Scratch area in step 2220 .
  • the controller/multiplexer MAC address for example, Controller-000001
  • step 2222 using the ExplorerTM a user selects each unassigned controller/multiplexer in the Device Scratch area, drags the selection to the appropriate ACN segment and, and either adds the selection to the system as a new device or drops the selection to a pre-existing device configuration. If the unassigned controller/multiplexer is added as a new device, the configuration processing proceeds in the manner of manual incorporation of the device.
  • step 2224 a user is prompted for the real device name using the previously assigned name ‘Controller-000001’ as a default. If automatic address assignment is set, the new device is assigned the next Device ID and associated IP addresses and Subnet masks are automatically assigned in step 2226 .
  • the device is automatically assigned the next Device ID and the user is prompted to enter the IP Addresses and Subnet Masks in step 2228 .
  • the MAC address for the controller/multiplexer is set to the MAC address of the ‘Controller-000001’ as dragged into the ACN segment.
  • the new controller/multiplexer Name, Device ID, IP Address, Subnet Masks and ACN number are added to the device table in the database.
  • the next request by an unconfigured controller/multiplexer is answered by the “Plug&Play Network Configuration Service”.
  • a new controller/multiplexer If a new controller/multiplexer is dragged and dropped over an existing device, that device must be a controller/multiplexer type device and have an unassigned MAC address. Accordingly, the MAC address of the previously entered controller/multiplexer is set to the MAC address of the ‘Controller-000001’ device which was dropped.
  • the new controller/multiplexer Name, Device ID, IP Addresses, Subnet Masks and ACN number are available for sending to the requesting controller/multiplexer by the “Plug&Play Network Configuration Service”.
  • the digital control system program 115 includes an auto-configure routine for automatically configuring the input/output (I/O) subsystem in response either to an “auto-configure” command by a user or in response to detection of a new controller/multiplexer.
  • an auto-configure routine for automatically configuring the input/output (I/O) subsystem in response either to an “auto-configure” command by a user or in response to detection of a new controller/multiplexer.
  • An auto-configure command may be directed to a Controller/Multiplexer 1110 , causing each I/O subsystem in the Controller/Multiplexer 1110 to auto-configure.
  • An auto-configure command may be directed to an I/O subsystem, causing each I/O Card in the I/O subsystem to auto-configure.
  • An auto-configure command may also be directed to an I/O Card.
  • the auto-configure operation for an I/O Card first interrogates the I/O Card at a particular card position to determine a Card Type in step 2310 and, implicitly for some I/O Cards, the number of I/O Ports in the I/O Card. If no I/O Card is previously created in the engineering database for that card position, an I/O Card of the appropriate type is defined and the appropriate number of I/O Ports are created in step 2312 .
  • the auto-configure operation If an I/O Card does exist in the engineering database for that card position, but the Card Type in the engineering database does not match the Card Type sensed at the card position, the auto-configure operation generates a graphic notification of the mismatch in step 2314 and interrogates a user to determine whether the engineering database is to be changed to include the sensed Card Type.
  • the Card Type in the engineering database is changed to the sensed Card Type in step 2316 if requested by the user.
  • the auto-configuration program interrogates each I/O Port in accordance with the Card Type in step 2318 to determine the Port Type and, if information is available, the number of I/O Devices on the I/O Port. If no I/O Port is previously created in the engineering database for that port address, an I/O Port of the appropriate type is defined and the appropriate number of I/O Devices are created in step 2320 . If an I/O Port exists in the engineering database for the Port address, but the Port Type does not match the type of the sensed I/O Port, the user is notified of the mismatch in step 2322 , and asked whether the engineering database is to be changed to match the sensed I/O Port in step 2324 . The Port Type in the engineering database is changed to the sensed Port Type in step 2326 if requested by the user.
  • the auto-configuration program interrogates each I/O Device in accordance with the Port Type in step 2328 to determine the Device Type. If no I/O Device is previously created in the engineering database for that device address, an I/O Device of the appropriate type is defined in step 2330 . If an I/O Device exists in the engineering database for the Device address, but the Device Type does not match the type of the sensed I/O Device, the user is notified of the mismatch in step 2332 , and asked whether the engineering database is to be changed to match the sensed I/O Device in step 2334 . The Device Type in the engineering database is changed to the sensed Device Type in step 2336 if requested by the user.
  • instrument signal tags are automatically created for primary signal sources on the I/O Ports and I/O Devices, unless an IST already exists with the identical signal source path.
  • control logic for performing operations may be implemented as executable program code at any levels including high level languages, assembler languages, and object codes.
  • the control logic may also be implemented as state machines, electronic logic, and the like.

Abstract

A digital control system with a predetermined configuration automatically senses the connection to a network of a digital device that is not included in the predetermined configuration. The digital device is assigned temporary address information and placed in a temporary state, called a standby state, in which the digital device supplies information to the digital control system allowing a user to access the digital device including access of device information and configuration parameters. Using the device information and configuration parameters, a user selectively commissions the digital device by assigning a physical device tag, a device address, and a device identification, and installing a control strategy to the digital device, thereby placing the digital device in an operational state in communication with the digital control system. In the standby state, a user interrogates to determine the type of device that is attached, determines the role of the device in the context of the digital control system, assigns a physical device tag that assigns the determined role to the device, and verifies connection of the device to the network. Also in the standby state, the user initiates other applications applied to the device, including calibration of the device and configuring the device within the overall control scheme of the digital control system.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
This application is related to of copending application by Nixon et al., entitled “Process Control System Including Automatic Sensing and Automatic Configuration of Devices”, filed on Apr. 12, 1996, U.S. patent application Ser. No. 08/631,519, which application is hereby incorporated by reference in its entirety, including any appendices and references thereto.
This application is related to copending application by Nixon et al., entitled “A Process Control System Using Standard Protocol Control of Standard Devices and Non-standard Devices”, filed on Apr. 12, 1996, U.S. patent application Ser. No. 08/631,862, which application is hereby incorporated by reference in its entirety, including any appendices and references thereto.
This application is related to copending application by Nixon et al., entitled “A Process Control System for Versatile Control of Multiple Process Devices of Various Device Types”, filed on Apr. 12, 1996, U.S. patent application Ser. No. 08/631,521, which application is hereby incorporated by reference in its entirety, including any appendices and references thereto.
This application is related to copending application by Nixon et al., entitled “Process Control System for Monitoring and Displaying Diagnostic Information of Multiple Distributed Devices”, filed on Apr. 12, 1996, U.S. patent application Ser. No. 08/631,557, which application is hereby incorporated by reference in its entirety, including any appendices and references thereto.
This application is related to copending application by Nixon et al., entitled “A Process Control System User Interface Including Selection of Multiple Control Languages”, filed on Apr. 12, 1996, U.S. patent application Ser. No. 08/631,517, which application is hereby incorporated by reference in its entirety, including any appendices and references thereto.
This application is related to copending application by Dove, entitled “System for Assisting Configuring a Process Control Environment”, filed on Apr. 12, 1996, U.S. patent application Ser. No. 08/631,458, which application is hereby incorporated by reference in its entirety, including any appendices and references thereto.
This application is related to copending application by Nixon et al., entitled “Process Control System Using a Control Strategy Implemented in a Layered Hierarchy of Control Modules”, filed on Apr. 12, 1996, U.S. patent application Ser. No. 08/631,520, which application is hereby incorporated by reference in its entirety, including any appendices and references thereto.
This application is related to copending application by Dove et al., entitled “System for Configuring a Process Control Environment”, filed on Apr. 12, 1996, U.S. patent application Ser. No. 08/631,863, which application is hereby incorporated by reference in its entirety, including any appendices and references thereto.
This application is related to copending application by Nixon et al., entitled “A Process Control System Using a Process Control Strategy Distributed Among Multiple Control Elements”, filed on Apr. 12, 1996, U.S. patent application Ser. No. 08/631,518, which application is hereby incorporated by reference in its entirety, including any appendices and references thereto.
This application is related to copending application by Nixon et al., entitled “Improved Process System”, filed on Apr. 12, 1996, U.S. Provisional patent application Ser. No. 60/017,700, which application is hereby incorporated by reference in its entirety, including any appendices and references thereto.
BACKGROUND OF THE INVENTION
1. Field of the Invention
This invention relates to process control systems. More specifically, the present invention relates to a process control system which automatically senses connection of process devices and automatically configures the devices when sensed.
2. Description of the Related Art
Present-day process control systems use instruments, control devices and communication systems to monitor and manipulate control elements, such as valves and switches, to maintain at selected target values one or more process variables, including temperature, pressure, flow and the Eke. The process variables are selected and controlled to achieve a desired process objective, such as attaining the safe and efficient operation of machines and equipment utilized in the process. Process control systems have widespread application in the automation of industrial processes such as the processes used in chemical, petroleum, and manufacturing industries, for example.
Control of the process is often implemented using microprocessor-based controllers, computers or workstations which monitor the process by sending and receiving commands and data to hardware devices to control either a particular aspect of the process or the entire process as a whole. The specific process control functions that are implemented by software programs in these microprocessors, computers or workstations may be individually designed, modified or changed through programming while requiring no modifications to the hardware. For example, an engineer might cause a program to be written to have the controller read a fluid level from a level sensor in a tank, compare the tank level with a predetermined desired level, and then open or close a feed valve based on whether the read level was lower or higher than the predetermined, desired level. The parameters are easily changed by displaying a selected view of the process and then by modifying the program using the selected view. The engineer typically would change parameters by displaying and modifying an engineer's view of the process.
Many process control systems include local field devices such as valves, motors, regulators and the like which are responsive to specific control protocols, such as Profibus, Fieldbus, CAN and the like, to implement various control function routines. Accordingly, these controllers are responsive to certain standard control protocols to implement control functionality in the field. The use of such standard control signal protocols can reduce the time and effort of developing a control system because a designer can use the same types of control signals from all devices responsive to the control protocol.
In a conventional process control system, the local field devices are typically configured in the field, often by individually programming the local field devices using a hand-held field programmer. Individual programming of the field devices is time consuming and inefficient and often leads to incompatibilities between the device configuration and the configuration of other devices and controllers in the process control system since a global view of the system is more difficult to sustain when individual devices are programmed independently. Usage of individual programming devices is inconvenient since multiple different programming devices typically must be used to program respective different field devices.
Furthermore, local device failures, including temporary failures or local power disruptions, interrupt operations of the entire control system, sometimes causing extended downtime since each failing device must be reconfigured locally.
What is needed is a process control system that allows individual field devices to be configured without local, independent programming. What is also needed is a process control system allowing configuration of the global system from a location remote from the local field devices so that a compatible global configuration is achieved while allowing peripheral elements which are configured in a suitable global manner, to operate independently to achieve control functionality.
Configuration of the global system is based on parameters that describe the particular field devices that make up the system. However, the control protocols for communicating with the field devices may be insufficient to convey parameters that are sufficient to configure the system. For example, the system management specification of the Fieldbus protocol defines three states for a device including an INITIALIZED state, an UNINITIALIZED state, and a system management operational (SM OPERATIONAL) state. The three defined states are sufficient to describe the behavior of a device from the perspective of the system management, but are not adequate for describing a device from the perspective of either the fieldbus interface or software engineering tools for analyzing, controlling, or displaying the status of a device. This insufficiency is highly notable when configuration involves the operation of commissioning a device that is attached to the Fieldbus link in an UNINITIALIZED state.
What is further needed is a process control system that differentiates between Fieldbus device states to support automatic sensing of devices and online address assignment of devices.
SUMMARY OF THE INVENTION
In accordance with an aspect of the present invention, a control system controls one or more interconnected devices according to a defined control configuration. The control system automatically senses a device that is connected to the control system but not included in the control configuration definition. The control system supplies initial interconnect information to the connected device sufficient to upload configuration parameters from the device to the control system.
In accordance with a further aspect of the present invention, a digital control system with a predetermined configuration automatically senses the connection to a network of a digital device that is not included in the predetermined configuration. The digital device is assigned temporary address information and placed in a temporary state, called a standby state, in which the digital device supplies information to the digital control system allowing a user to access the digital device including access of device information and configuration parameters. Using the device information and configuration parameters, a user selectively commissions the digital device by assigning a physical device tag, and a device address, and installing a control strategy to the digital device, thereby placing the digital device in an operational state in communication with the digital control system. In the standby state, a user interrogates to determine the type of device that is attached, determines the rule of the device in the context of the digital control system assigns a physical device tag that assigns the determined role to the device, and verifies connection of the device to the network. Also in the standby state, the user initiates other applications applied to the device, including calibration of the device and configuring the device within the overall control scheme of the digital control system.
In accordance with another aspect of the present invention, a control system differentiates between Fieldbus device states beyond the states defined according to the Fieldbus standard specification. The control system sets a physical device tag equal to the device identification (ID) for the devices that do not have tags, while the device is autosensed. A device attached to the Fieldbus link with the physical device tag set equal to the device ID is controlled in the manner of an UNINITIALIZED device.
In accordance with an aspect of the present invention, automatic sensing of field devices is extended beyond a conventional input/output level to the configuration of Fieldbus devices by a digital control system.
In accordance with an embodiment of the present invention, a digital control system with a predetermined configuration automatically senses the connection to a network of a digital device that is not included in the predetermined configuration. The digital device is placed in a temporary state, called a standby state, in which the digital device supplies information to the digital control system allowing a user to access the digital device, including access of device information and configuration parameters. The digital control system formats and displays the device information upon request by a user. The digital control system program also includes an automatic configuration program that responds to sensing of a new controller by automatically configuring the input/output (I/O) subsystem. The user adds a new controller without setting any physical switches or nodes. A user optionally supplies configuration information for a device into a database, prior to connection of a device. Upon connection of the device, the device is automatically sensed and configured using the database configuration information, without setting of physical switches on the devices.
In accordance with another embodiment of the present invention, a process control system includes a process, a plurality of controllers connected to the process, a workstation connected to the plurality of controllers and including a user interface, and a software system including a network operating system, a user interface, and implementing an automatic sensing routine. The automatic sensing routine includes an executable logic for automatically sensing a connection of a device to a network and placing the device in a state accessible for communication by a user via a user interface. In the accessible state, a user commissions the device and selectively initiates device-related applications.
Many advantages are achieved by the described system and method. One advantage is that configuration of a control system is greatly facilitated. The physical connection of a device to the network automatically initiates inclusion of the connected device into the control system. The described system and method advantageously facilitates conformity between the configuration of a network and the physical interconnections of the network that serves as the basis for the configuration. The described system and method assist programming of field devices from a remote location so that individual field setting of the devices, using a local setting device, is not necessary. The system and method support central programmability is highly useful to reduce system management costs and for reducing downtime of a process control system. A further advantage is that configuration of the entire system, rather setting of individual devices, leads to a system in which individual system settings are highly compatible.
BRIEF DESCRIPTION OF THE DRAWINGS
The features of the invention believed to be novel are specifically set forth in the appended claims. However, the invention itself, both as to its structure and method of operation, may best be understood by referring to the following description and accompanying drawings.
FIG. 1 is a pictorial view of a front-of-screen display for a graphical user interface (GUI) displaying a system configuration.
FIG. 2 is a state transition diagram illustrating various states of a field device.
FIG. 3 is a flow chart illustrating a first operation of commissioning a new device.
FIG. 4 is a flow chart illustrating a second operation of commissioning an unbound.
FIG. 5 is a flow chart illustrating a third operation of decommissioning a device.
FIG. 6 is a flow chart illustrating a fourth operation of attaching a commissioned device without enablement of operational powerup.
FIG. 7 is a flow chart illustrating a fifth operation of replacing a device.
FIG. 8 is a flow chart illustrating a sixth operation of attaching an UNRECOGNIZED device.
FIG. 9 is a flow chart illustrating a seventh operation of decommissioning an unrecognized device.
FIG. 10 is a flow chart illustrating an eighth operation of placing a decommissioned device in a standby condition.
FIGS. 11A, 11B and 11C illustrate a screen display, a first schematic block diagram and a second schematic block diagram respectively, process control systems in accordance with a generalized embodiment of the present invention which furnishes a capability to create a new control template and a capability to modify an existing control template for only one view, such as an engineering view.
FIG. 12 is a schematic block diagram showing the process control environment in a configuration implementation and a run-time implementation.
FIG. 13 is a block diagram illustrating a user interface for usage with both configuration and run-time models of the process control environment.
FIG. 14 is a schematic block diagram which depicts a hierarchical relationship among system objects of a configuration model in accordance with an embodiment of the present invention.
FIG. 15 illustrates a method for automatically sensing and incorporating a controller/multiplexer into a run-time system.
FIG. 16 is a flow chart illustrates steps of an automatic configuration routine for configuring a physical I/O device.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
Referring to FIG. 1, a front-of-screen display, also called a “screen” 100, for a graphical user interface (GUI) depicts a display of a system configuration. The screen 100 depicts navigation selections which are operated by a user to select, construct and operate a process control configuration. The navigation program supplies an initial state for navigating across various tools and processors in a network. A user controls the navigation program to access libraries, areas, process control equipment and security operations.
The illustrative system configuration is described and controlled with respect to a control system setup 102, control strategies 104, and a physical setup 106. The functions of automatically sensing and automatically configuring a control system relate to the physical setup 106. In particular, the functions of automatically sensing and automatically configuring physical devices in a control system relate to the commission and activation of devices in the control network 108, and the decommissioning of controllers 110.
In an illustrative embodiment, a process control system controls various devices attached to a process control network in accordance with a Fieldbus standard protocol. In the Fieldbus protocol, a standard user application is defined based on blocks. A block is a representation of various different types of application functions. Types of blocks include resource blocks, function blocks, and transducer blocks.
A resource block describes characteristics of a fieldbus device such as a device name, manufacturer, and serial number. A device includes only a single resource block.
A function block defines the control system behavior. Input and output parameters of function blocks may be linked over the fieldbus. The execution of each function block is precisely scheduled. A user application may include numerous function blocks. Examples of standard function blocks include analog input (AI), analog output (AO), bias (B), Control Selector (CS), Discrete Input (DI), Discrete Output (DO), Manual Loader (ML), Proportional/Derivative (PD), Proportional/Integral/Derivative (PID) and ratio (RA). Function blocks are built into fieldbus devices to define a selected device functionality. In one example, a simple temperature transmitter may contain an Al function block. A control valve often includes a PID function block and an AO block.
A transducer block decouples function blocks from local input and output functions for reading sensors and commanding output hardware. Transducer blocks contain information such as calibration data and sensor type. Typically a user application uses one transducer block for each input or output function block.
Another object defined in the user application includes link objects for defining the links between function block inputs and outputs internal to the device and across the fieldbus network. Trend objects allow local trending of function block parameters for access by other devices. Alert objects are used to allow reporting of alarms and events on the fieldbus. View objects are predefined groupings of block parameter sets that are used in the human/machine interface. The function block specification defines four views for each type of block.
Referring to FIG. 2, a state transition diagram illustrates the various states of a field device. The field device states include an offline state 202, an unrecognized state 204, a standby state 206, a commissioned state 208, and an unbound state 210. The state of a field device is determined by several parameters including a system management state (SM-State), a physical device tag (PD-Tag), a device address, device revision information (Rev*), and a device identification (Device-ID). In the illustrative embodiment, a device in the commissioned state 208 is a Fieldbus device that is available for control strategy configuration and installation. A decommissioned device is a device that has been removed from the commissioned state 208.
Several events occur that generate a state transition of a plurality of state transitions T1 through T14. One or more actions are performed during each state transition.
A state transition T1 is caused by the event in which a field device residing at a temporary address is queried with a system management identify service (SM-IDENTIFY) and the query determines that the device has a cleared physical device tag. The state transition T1 changes from a NULL state to an OFFLINE state by allocating a standby address for the field device. Executing logic, typically in the form of firmware, software, or hardware, executes a set physical device tag service (SET-PD-TAG) to set the physical device tag identical to the device identification of the field device. Executing logic also uses a set device address service (SET-ADDRESS) to send a standby address to the field device.
A state transition T2 is caused by the event in which a field device residing at a temporary address is queried with a system management identify service (SM-IDENTIFY) and the query determines that the device has a physical device tag that is identical to the device identification of the device. The state transition T2 changes from a NULL state to an OFFLINE state by allocating a standby address for the field device. Executing logic uses a set device address service (SET-ADDRESS) to send a standby address to the field device.
A state transition T3 is caused by the event in which a field device residing at a temporary address is queried with a system management identify service (SM-IDENTIFY) and the query determines that the device has a physical device tag and a device identification configured for the current process control system network link. The state transition T3 changes from a NULL state to an OFFLINE state using executing logic that employs the set device address service (SET-ADDRESS) to send an assigned address to the field device.
A state transition T4 is caused by the event in which a field device residing at a temporary address is queried with a system management identify service (SM-IDENTIFY) and the query determines that the device has a physical device tag and a device identification not configured for the current process control system network link. The state transition T4 changes from a NULL state to an UNRECOGNIZED state.
A state transition T5 is caused by an event in which the device appears at a temporary address and the device is being commissioned by a user. The state transition T5 changes from an OFFLINE state to an OFFLINE state using executing logic, typically in the form of firmware, software, or hardware, that executes a set physical device tag service (SET-PD-TAG) to clear the physical device tag of the field device. Executing logic also executes a set physical device tag service (SET-PD-TAG) to send an assigned physical device tag to the field device. Executing logic further uses a set device address service (SET-ADDRESS) to send an assigned address to the field device.
A state transition T6 is caused by an event in which the device appears at a temporary address and the device is being decommissioned by a user. The state transition T6 changes from an OFFLINE state to an OFFLINE state using executing logic that executes a set physical device tag service (SET-PD-TAG) to clear the physical device tag of the field device.
A state transition T7 is caused by an event in which a user requests to place a decommissioned device in standby. The state transition T7 changes from an OFFLINE state to an OFFLINE state by allocating a standby address for the field device. Executing logic executes a set physical device tag service (SET-PD-TAG) to set the physical device tag identical to the device identification of the field device. Executing logic also uses a set device address service (SET-ADDRESS) to send a standby address to the field device.
A state transition T8 is caused by an event in which the field device appears at the standby address. The state transition T8 changes from an OFFLINE state to a STANDBY state through executing logic that reads device revision information from the resource block.
A state transition T9 is caused by an event in which the field device appears at the assigned address. The state transition T9 changes from an OFFLINE state to a COMMISSIONED.
A state transition T10 is caused by a user requesting to commission a device in the STANDBY state. The state transition T10 changes from the STANDBY state to the OFFLINE state through executing logic that uses a clear address service (CLEAR-ADDRESS) to clear the device address.
A state transition T11 is caused by a user requesting to decommission a device in the STANDBY state. The state transition T11 changes from the STANDBY state to the OFFLINE state through executing logic that uses a clear address service (CLEAR-ADDRESS) to clear the device address.
A state transition T12 is caused by a user requesting to decommission a device in the COMMISSIONED state. The state transition T12 changes from the COMMISSIONED state to the OFFLINE state through executing logic that uses a clear address service (CLEAR-ADDRESS) to clear the device address.
A state transition T13 is caused by a user requesting to decommission a device in the INITIALIZED state of the Fieldbus system management states. The state transition T13 changes from the UNRECOGNIZED state to the OFFLINE state through executing logic that executes a set physical device tag service (SET-PD-TAG) to clear the physical device tag of the field device.
A state transition T14 is caused by a user requesting to decommission a device in the SM-OPERATIONAL state of the Fieldbus system management states. The state transition T14 changes from the UNRECOGNIZED state to the OFFLINE state through executing logic that uses a clear address service (CLEAR-ADDRESS) to clear the device address.
In accordance with the Fieldbus standard, to operate properly a Fieldbus device has a unique device address (network address) and a unique physical device tag. Each device connected to the process control system network link has a unique node designator. A data link specification specifies a range of allowable values for node designators including a range for permanent devices, a range for temporary addresses, and a range for visitor devices. The temporary addresses are used by devices that are not presently in the SM-OPERATIONAL state. The Fieldbus interface maintains partitioning of the address space for permanent devices into three sets. One set, called “assigned addresses”, includes addresses assigned to devices with a specific physical device tag, regardless of whether the device is present on the bus. The assigned addresses is assigned using a software engineering tool on the basis of information input by a user relating to Link-Active-Scheduler takeover preference. A second set, termed “standby addresses”, describes devices in the SM-OPERATIONAL state but have no device addresses assigned. The standby addresses are managed by the Fieldbus interface. The third set of addresses are addresses outside the first and second sets and refer to unused addresses.
The small number of temporary addresses complicates autosensing and online address assignment. Standby addresses are defined and utilized to support functionality of the autosensing and online address assignment operations. The assigned address set and the standby address set are defined to be equal to the number of potential devices connected to the process control system network link. For example, if sixteen devices may be potentially connected to the process control system network, then sixteen assigned addresses are defined and sixteen standby addresses are defined.
The device revision information includes a manufacturer's identification (MANUFAC-ID), a device type (DEV-TYPE), a device revision (DEV-REV), and a device description revision (DD-REV).
In the offline state 202 a field device is recently attached to a process control system network or is in the process of being commissioned or decommissioned. The offline state 202 includes device states having a plurality of parameter combinations. In a first offline state 202, the system management state is UNINITIALIZED and the physical device tag is cleared. In a second offline state 202, the system management state is INITIALIZED and the physical device tag is read from the physical device and displayable on a screen. In either of the offline states 202, the device address is a temporary address, the revision information is not available, and the device identification is read from the device and displayable on the screen.
In the unrecognized state 204, the field device physical device tag and the device identification do not match the values that are commissioned for a device that is connected to the process control system network. The unrecognized state 204 includes device states having a plurality of parameter combinations. In a first unrecognized state 204, the system management state is INITIALIZED with a device address that is a temporary address. In a second unrecognized state 204, the system management state is SM-OPERATIONAL with a device address that is a standby address or an assigned address. In either unrecognized state 204, the physical device tag is read from the device and displayable on the screen, the device revision is not available, and the device identification is read from the device and displayable on the screen.
In the standby state 206, the field device is not yet autosensed and is therefore not available for configuration in the control strategy or included in Link-Active-Scheduler (LAS) schedules of the system management configuration. In the standby state 206, function block execution and link communications are disabled. Note that a Link-Active-Scheduler is a deterministic centralized bus scheduler that includes a list of transmit times for all data buffers in all devices that are to be cyclically transmitted. When a device is due to send a data buffer, the Link-Active-Scheduler issues a compel data (CD) message to the device. Upon receipt of the CD message, the device broadcasts or “publishes” the data in the buffer to all devices on a field device bus and the broadcasting device is defined to be a “publisher”. Any device that is configured to receive the data is defined to be a “subscriber”. Scheduled data transfers are typically used for the regular, cyclic transfer of control loop data between devices on the fieldbus.
In the standby state 206, the system management state is SM-OPERATIONAL, the physical device tag is equal to the device identification, and the device address is a standby address. The device revision information is read from the field device and displayable. The device identification is read from the device and displayable on the screen.
The unbound state 210 is a configuration placeholder for a field device that is to be physically attached subsequently. The unbound state 210 supports configuration of control strategies utilizing the function blocks in a field device that is not yet connected. In the unbound state 210, the system management state is not yet applicable but the physical device tag is specified by a user and the device address is assigned by the user. The device revision information set according to the most recent commission or configuration. The device identification is cleared.
In the commissioned state 208, the field device is available for control strategy configuration and installation. The system management state is SM-OPERATIONAL, the physical device tag is specified by a user, and the device address is assigned by the user. The device revision information is read from the field device and displayable on the screen. The device identification is read from the field device, stored in a field configuration database, and displayable on a display screen.
Several operations or “use cases” are defined for controlling commissioning and decommissioning of field devices.
Referring to FIG. 3, a flow chart illustrates a first operation or “use case” which describes an operation of commissioning a new device 300. Prior to the commissioning of the new device, the Fieldbus interface is operational. A device is connected to the process control system network. The device either has no physical device tag or has a physical device tag that is equal to the device identification.
The operation of commissioning a new device 300 results in a condition in which the device is assigned a new physical device tag and a device address, and the device is ready for function block configuration. The new field device is entered into the process control system network database with the device identification bound and the device revision information set. An engineering software tool that displays the process control system network status displays the new device as a COMMISSIONED device.
In a first step 302, the field device appears in the “live list” at a temporary address. A “live list” is a list of all devices that are properly responding to a pass token (PT) message. All devices on a fieldbus are allowed to send unscheduled messages between the transmission of scheduled messages. The Link-Active-Scheduler grants permission to a device to use the fieldbus by issuing a pass token (PT) message to the device. When the device receives the PT, it is allowed to send messages until the messages are complete or until a maximum allotted token hold time has expired. As a highest priority activity, the Link-Active-Scheduler accesses a CD schedule containing a list of actions that are set to occur on a cyclic basis. At a scheduled time, the Link-Active-Scheduler sends a compel data (CD) message to a specific data buffer in the fieldbus device. The device immediately broadcasts a message to all devices on the fieldbus. The Link-Active-Scheduler performs remaining operations between scheduled transfers. The Link-Active-Scheduler continually adds new devices to the field bus by periodically sending probe node (PN) messages to addresses that are not on the live list. If a device is present at the address and receives the PN, the device immediately returns a probe response (PR) message. If a device responds with the PR message, the Link-Active-Scheduler adds the device to the live list and confirms by sending the device a node activation (NA) message. A device remains on the live list so long as the device responds properly to PTs. When a device is added or removed from the live list, the Link-Active-Scheduler broadcasts changes to the live list to all devices to allow each device to maintain a current copy of the live list.
In a second step 304, the interface queries the field device using a system management identify service (SM-IDENTIFY) and determines whether the field device is in the UNINITIALIZED state with no physical device tag set or in the INITIALIZED state having a physical device tag that is equal to the device identification. The interface then allocates 306 a standby address for the field device.
A logical step 308 directs that a previously UNINITIALIZED device, in step 310, sets the physical device tag of the field device identical to the device identification using a set physical device tag service (SET-PD-TAG), thereby placing the field device in the INITIALIZED state. The standby address is sent to the field device 312 using a set address service (SET-ADDRESS), advancing the field device from the INITIALIZED state to the SM-OPERATIONAL state. At this point the field device appears in the “live list” at a standby address 314. Device revision information is read from the resource block 316. In step 318, an executing software engineering tool displays the field device as a STANDBY device.
In step 320, a new user assigns a new physical device tag to the field device. The physical device tag is constrained to be unique and not the same as the device identification. During the assignment of the physical device tag, a device address is assigned to the field device using a software engineering tool and the Link-Active-Scheduler takeover preference is set to “selectable”. The device revision information is read from the field device and written to the process control system network database. The interface changes the state of the field device 322 to the INITIALIZED state using a clear address service (CLEAR-ADDRESS). The field device appears in the “live list” at a temporary address 324.
In a step 326, the interface queries the field device using a system management identify service (SM-IDENTIFY) and recognizes the field device by the device identification. The interface uses the set physical device tag service (SET-PD-TAG) to clear the physical device tag 328, thereby changing the field device state to the UNINITIALIZED state. The set physical device tag service (SET-PD-TAG) is then used to send the assigned physical device tag to the field device 330, changing the field device state to the INITIALIZED state. The set address service (SET-ADDRESS) is called to send the assigned address to the field device 332, placing the field device in the system management operational state (SM-OPERATIONAL). The field device appears in the “live list” at the assigned address 334. In the process control system network database, the device identification is bound 336 to the device. The software engineering tool displays the field device as a COMMISSIONED device.
Referring to FIG. 4, a flow chart illustrates a second operation or “use case” which describes an operation of commissioning an unbound device 400. Prior to the commissioning of the unbound device, the Fieldbus interface is operational. A field device has been created in the process control system network database and a physical device tag and a device address are assigned to the field device. However, the field device is not bound to a device identification. The process control system network database has also been initialized to contain device revision information read from the field device. A software engineering tool displays the field device as an UNBOUND device. The UNBOUND device to be commissioned is either a field device with no physical device tag or a field device having a physical device tag that is identical to the device identification. The UNBOUND field device is commissioned to place the field device on the process control system network link.
The operation of commissioning an UNBOUND device 400 results in a condition in which the device is configured with a physical device tag and an assigned device address, and the device is ready for function block configuration. The new field device is entered into the process control system network database with the device identification bound. An engineering software tool that displays the process control system network status displays the device as a COMMISSIONED device.
In a first step 402, the field device appears in the “live list” at a temporary address. In a second step 404, the interface queries the field device using a system management identify service (SM-IDENTIFY) and determines whether the field device is in the UNINITIALIZED state with no physical device tag set or in the INITIALIZED state having a physical device tag that is equal to the device identification. The interface then allocates 406 a standby address for the field device.
A logical step 408 directs that a previously UNINITIALIZED device, in step 410, sets the physical device tag of the field device identical to the device identification using a set physical device tag service (SET-PD-TAG), thereby placing the field device in the INITIALIZED state. The standby address is sent to the field device 412 using a set address service (SET-ADDRESS), advancing the field device from the INITIALIZED state to the SM-OPERATIONAL state. At this point the field device appears in the “live list” at a standby address 414. Device revision information is read from the resource block 416. In step 418, an executing software engineering tool displays the field device as a STANDBY device.
In step 420, a user assigns a physical device tag to the field device by associating the field device with the pre-configured device. The device revision information is read from the field device to ascertain that the information matches the device revision information in the process control system network database for the preconfigured device. If the device revision information of the device does not match the database, the user may override the database, reading the device revision information from the field device and writing the information to the process control system network database. Alternatively, the device revision information for an UNBOUND device may be made blank, allowing any physical device to be bound with the UNBOUND device. The interface changes the state of the field device 422 to the INITIALIZED state using a clear address service (CLEAR-ADDRESS). The field device appears in the “live list” at a temporary address 424.
In a step 426, the interface queries the field device using a system management identify service (SM-IDENTIFY) and recognizes the field device by the device identification. The interface uses the set physical device tag service (SET-PD-TAG) to clear the physical device tag 428, thereby changing the field device state to the UNINITIALIZED state. The set physical device tag service (SET-PD-TAG) is then used to send the assigned physical device tag to the field device 430, changing the field device state to the INITIALIZED state. The set address service (SET-ADDRESS) is called to send the assigned address to the field device 432, placing the field device in the system management operational state (SM-OPERATIONAL). The field device appears in the “live list” at the assigned address 434. In the process control system network database, the device identification is bound 436 to the device. The software engineering tool displays the field device as a COMMISSIONED device.
Referring to FIG. 5, a flow chart illustrates a third operation or “use case” which describes an operation of decommissioning a device 500. A field device is decommissioned for several reasons. For example, when a Fieldbus device is obsolete, a user may wish to clear a network interconnection structure of nonfunctioning branches so that the process control system no longer expends resources on the obsolete device. Also, a user may suspect that a Fieldbus device is malfunctioning and degrading operations of a segment of a network interconnection structure. The user may diagnose the problem by having the process control system ignore the suspected Fieldbus device temporarily to determine whether the remaining devices in the segment operate properly.
Prior to the operation of decommissioning a device, the Fieldbus interface and the field device are operational and the field device appears in the live list at the assigned or standby address. A software engineering tool displays the field device as a COMMISSIONED or STANDBY device. The software engineering tool executes a routine that prepares the field device for decommissioning, for example by clearing function block tags and clearing an OPERATIONAL-POWERUP flag.
The operation of decommissioning a device results in a condition in which the physical device tag of the field device is cleared and the field device is prepared to be removed from the process control system network link. The process control system network database entry for the field device designates the device identification as in an unbound condition. The software engineering tool displays the device identification as an UNBOUND device and displays the physical device as an OFFLINE device.
The operation of decommissioning a device 500 begins when a user selects a “Decommission” operation for the field device 502. A graphic user interface includes a software engineering tool that issues a “Decommission” command to an appropriate controller within the process control system. The decommission command specifies a target I/O subsystem, card and port identifiers, and the device identification of the field device to be decommissioned. The device identification is specified since another device with the same physical device tag may be present in an UNRECOGNIZED state. The interface changes the state of the field device 504 to the INITIALIZED state using a clear address service (CLEAR-ADDRESS). The field device appears in the “live list” at a temporary address 506.
In a step 508, the interface queries the field device using a system management identify service (SM-IDENTIFY) and recognizes the field device by the physical device tag and the device identification. The interface uses the set physical device tag service (SET-PD-TAG) to clear the physical device tag 510, thereby changing the field device state to the UNINITIALIZED state.
In the process control system network database, the device identification is unbound and the software engineering tool displays the field device as an UNBOUND device 512. In a next step 514, the software engineering tool displays the field device as an OFFLINE device.
A network interface card stores a designation that the field device has been decommissioned 516 and does not move the field device to a STANDBY address unless directed by the user. If the decommissioned device is not move to a STANDBY address, the interface card tracks the field device until the field device advances off the live list.
Referring to FIG. 6, a flow chart illustrates a fourth operation or “use case” which describes an operation of attaching a commissioned device without enablement of operational powerup 600. Prior to the operation of attaching a commissioned device 600, the Fieldbus interface is operational. The configuration of the Fieldbus interface includes the field device in an attached condition. The physical device tag and the device identification of the field device are matched. Following the operation of attaching a commissioned device 600, the field device has an assigned address.
The field device appears in the “live list” at a temporary address 602. In a step 604, the interface queries the field device using a system management identify service (SM-IDENTIFY) and recognizes the field device by the physical device tag and the device identification as part of the Fieldbus interface configuration. The set address service (SET-ADDRESS) is called to send the assigned address to the field device 606, placing the field device in the system management operational state (SM-OPERATIONAL). The field device appears in the “live list” at the assigned address 608.
Referring to FIG. 7, a flow chart illustrates a fifth operation or “use case” which describes an operation of replacing a device 700. A device is replaced by decommissioning the current field device 702 connected to the process control system network link, if possible, and commissioning a replacement to the UNBOUND device 704. The step of decommissioning the current field device 702 is described in detail with reference to FIG. 5. The step of commissioning a replacement to the UNBOUND device 704 is described with reference to FIG. 4.
Referring to FIG. 8, a flow chart illustrates a sixth operation or “use case” which describes an operation of attaching an UNRECOGNIZED device 800. Prior to the operation of attaching a commissioned device 600, the Fieldbus interface is operational. A field device is attached which has a physical device tag and a device identification that is not configured for the current process control system network link. Following the operation of attaching an UNRECOGNIZED device 800, the field device is identified and the software engineering tool displays the device as n UNRECOGNIZED device. The operation of attaching an UNRECOGNIZED device 800 may be performed without use of the software engineering tool.
The field device appears in the “live list” 802. In a step 804, the interface queries the field device using a system management identify service (SM-IDENTIFY) and determines that the physical device tag and the device identification do not match a field device in the present configuration.
Referring to FIG. 9, a flow chart illustrates a seventh operation or “use case” which describes an operation of decommissioning an unrecognized device 900. Prior to the operation of decommissioning an unrecognized device, the Fieldbus interface is operational. The field device is identified which has a physical device tag and a device identification that are not configured for the present process control system network link. A software engineering tool displays the field device as an UNRECOGNIZED device.
The operation of decommissioning an unrecognized device 900 results in a condition in which the physical device tag of the field device is cleared and the field device is prepared to be removed from the process control system network link. The software engineering tool displays the field device as an OFFLINE device.
The operation of decommissioning an unrecognized device 900 begins when a user selects a “Decommission” operation for the field device 902. A graphic user interface includes a software engineering tool that issues a “Decommission” command to an appropriate controller within the process control system. The decommission command specifies a target I/O subsystem, card and port identifiers, and the device identification of the field device to be decommissioned.
If the field device is in the INITIALIZED state, logic step 904 directs the decommissioning operation 900 to a clear the physical device tag step 912. Otherwise, the interface changes the state of the field device 906 to the INITIALIZED state using a clear address service (CLEAR-ADDRESS). The field device appears in the “live list” at a temporary address 908.
In a step 910, the interface queries the field device using a system management identify service (SM-IDENTIFY) and recognizes the field device by the physical device tag and the device identification. The interface uses the set physical device tag service (SET-PD-TAG) to clear the physical device tag 912, thereby changing the field device state to the UNINITIALIZED state. In a next step 914, the software engineering tool displays the field device as an OFFLINE device.
A network interface card stores a designation that the field device has been decommissioned 916 and does not move the field device to a STANDBY address unless directed by the user. If the decommissioned device is not move to a STANDBY address, the interface card tracks the field device until the field device advances off the live list.
Referring to FIG. 10, a flow chart illustrates an eighth operation or “use case” which describes an operation of placing a decommissioned device in a standby condition 1000. Prior to the operation of placing a decommissioned device in a standby condition 1000, the Fieldbus interface is operational. A field device is decommissioned and in the OFFLINE state.
The operation of placing a decommissioned device in standby 1000 results in a condition in which the field device is placed at a standby address with the physical device tag of the field device set identical to the device identification. The software engineering tool displays the field device as a STANDBY device.
The operation of placing a decommissioned device in standby 1000 begins when a user selects a “Place in Standby” operation for the field device 1002. A graphic user interface includes a software engineering tool that issues a “Place in Standby” command to an appropriate controller within the process control system 1004. The decommission command specifies a target I/O subsystem, card and port identifiers, and the device identification of the field device to be placed in standby.
The interface allocates a standby address 1006 for the field device. The set physical device tag service (SET-PD-TAG) is then used to set the physical device tag identical to the device identification 1008, changing the field device state to the INITIALIZED state. The set address service (SET-ADDRESS) is called to send the standby address to the field device 1010, placing the field device in the system management operational state (SM-OPERATIONAL). The field device appears in the “live list” at the standby address 1012. Device revision information is read from the resource block 1014. In step 1016, an executing software engineering tool displays the field device as a STANDBY device.
A user may subsequently commission the field device 1018, either by creating a new device or binding the field device to an UNBOUND device in the process control system network database. The techniques for commissioning a device are described with respect to FIGS. 3 and 4.
Referring to FIG. 11A, a control system is shown. In general, the system 1 includes a main processing device, such as personal computer 2, that is connected to a local area network (“LAN”) 3 via a local area network card. Although any local area network protocol may be used, a non-proprietary ethernet protocol is beneficial in many applications because it allows for communications with the local area network 3. The local area network 3 is dedicated to carrying control parameters, control data and other relevant information concerned in the process control system. As such, the LAN 3 may be referred to as an area controlled network or ACN 3. The ACN 3 may be connected to other LANs for sharing information and data via a hub or gateway without affecting the dedicated nature of ACN 3.
In accordance with standard ethernet protocol, a plurality of physical devices may be connected to the ACN 3 at various “nodes.” Each physical device connected to the ACN 3 is connected at a node and each node is separately addressable according the LAN protocol used to implement ACN 3.
To establish a redundant system, it may be desirable to construct ACN 3 from two or more ethernet systems such that the failure of a single ethernet or LAN system will not result in the failure of the entire system. When such “redundant ethernets” are used the failure of one ethernet LAN can be detected and an alternate ethernet LAN can be mapped in to provide for the desired functionality of ACN 3.
The main personal computer (“PC”) A forms a node on the ACN 3. The PC 2 may, for example, be a standard personal computer running a standard operating system such as Microsoft's Window NT system. Main PC 2 is configured to generate, in response to user input commands, various control routines that are provided via the ACN 3 to one or more local controllers identified as element 4 and 5 which implement the control strategy defined by the control routines selected and established in main PC 2. Main PC 2 may also be configured to implement direct control routines on field devices such as pumps, valves, motors and the like via transmission across the ACN 3, rather than through a local controller 4 or 5.
Local controllers 4 and 5 receive control routines and other configuration data through the ACN 3 from PC 2. The local controllers then generate signals of various types to various field devices (such as pumps, motors, regulator valves, etc.) 6 through 15 which actually implement and perform physical steps in the field to implement the control system established by the routines provided by PC 2.
Two types of field devices may be connected to local controller 4 and 5 including field devices 6 through 10 which are responsive to specific control protocol such as FieldBus, Profibus and the like. As those in the art will appreciate, there are standard control protocols (e.g. FieldBus) according to which specific protocol instructions are provided to a protocol-friendly field devices (e.g., a Fieldbus field devices) will cause a controller located within the field device to implement a specific function corresponding to the protocol function. Accordingly, field devices 6 through 11 receive protocol specific (e.g., FieldBus) control commands from either the local controllers 4 and 5 or the personal computer 2 to implement a field device-specific function.
Also connected to local controllers 4 and 5 are non-protocol field devices 12 through 15, which are referred to as non-protocol because they do not include any local processing power and can respond to direct control signals. Accordingly, field devices 12 through 15 are not capable of implementing functions that would be defined by specific control protocol such as the FieldBus control protocol.
Functionality is supplied to allow the non-protocol field devices 12 through 15 to operate as protocol-friendly (e.g., FieldBus specific) devices 6 through 11. Additionally, this same functionality allows for the implementation of the protocol-specific control routines to be distributed between the local field devices 6 through 11, the local controllers 4 and 5 and the personal computer 2.
The distribution of protocol-specific control routines is illustrated in more detail in FIG. 11B. FIG. 11B refers to one portion of the system shown in FIG. 11A, specifically the personal computer 2, the ethernet 3, local controller 4, a smart field device 6 and a dumb device 12, in greater detail.
Personal computer 2 includes program software routines for implementing standard functional routines of a standard control protocol such as the FieldBus protocol. Accordingly, personal computer 2 is programmed to receive FieldBus commands and to implement all of the functional routines for which a local field device having Fieldbus capabilities could implement. The ability and steps required to program personal computer 2 to implement FieldBus block functionality will be clearly apparent to one of ordinary skill in the art.
Connected to personal computer 2 by the ethernet 3 is local controller 4. Local controller 4 includes a central processing unit connected to a random access memory which provides control signals to configure the central processing unit to implement appropriate operational functions. A read only memory is connected to the random access memory. The read only memory is programmed to include control routines which can configure the central processing unit to implement all of the functional routines of a standard control protocol such as FieldBus. Personal computer 2 sends signals through ethernet 3 to the local controller 4 which causes one, more or all of the programmer routines in the read only memory to be transferred to the random access memory to configure the CPU to implement one, more or all of the standard control protocol routines such as the FieldBus routines.
The smart field device 6 includes a central processing unit which implements certain control functions. If the devices is, for example, a FieldBus device then the central processing unit associated with the smart field device 6 is capable of implementing all of the FieldBus functionality requirements.
Because the local controller 4 has the ability to implement FieldBus specific controls, controller 4 operates so that non-protocol device 12 acts and is operated as a FieldBus device. For example, if a control routine is running either in personal computer 2 or on the CPU of local controller 4, that control routine can implement and provide FieldBus commands to FieldBus device 6 and non-protocol device 12, operating as a FieldBus device. Since field device 6 is a FieldBus device, device 6 receives these commands and thereby implements the control functionality dictated by those commands. Non-protocol device 12, however, works in conjunction with the central processing unit of local controller 4 to implement the FieldBus requirements such that the local controller in combination with the field device implements and operates FieldBus commands.
In addition to allowing non-FieldBus device 12 to act and operate as a FieldBus device, the described aspect allows for distribution of FieldBus control routines throughout the system 1 shown in FIG. 11A. For example, to the extent that a control routine initially requests field device 6 to implement more than one FieldBus control routine, the system 1 allows for control to be divided between the local controller 4 and the local controller 5 such that a portion of the FieldBus control routines are being implemented by local controller 5 and other FieldBus routines are implemented by the use of the FieldBus routines stored on local controller 4. The division of FieldBus routine implementation may allow for more sophisticated and faster control and more efficient utilization of the overall processing power of the system. Still further, the fact that personal computer 2 has the ability to implement FieldBus control routines, the FieldBus routines are further distributed between the local controller 4 and the personal computer 2. In this manner, the system allows personal computer 2 to implement one or all of the FieldBus routines for a particular control algorithm.
Still further, the system allows for the implementation of FieldBus controls to a non-FieldBus device connected directly to the ethernet 3 through use of the FieldBus control routines stored on personal computer 2 in the same manner that FieldBus routines are implemented on non-FieldBus device 12 through use on the FieldBus routines stored on local controller 4.
A process control environment 1100 is shown in FIG. 11C and illustrates a control environment for implementing a digital control system, process controller or the like. The process control environment 1100 includes an operator workstation 1102, a laboratory workstation 1104, and an engineering workstation 1106 electrically interconnected by a local area network (“LAN”) 1108 for transferring and receiving data and control signals among the various workstations and a plurality of controller/multiplexers 1110. The workstations 1102, 1104, 1106 are shown connected by the LAN 1108 to a plurality of the controller/multiplexers 1110 that electrically interface between the workstations and a plurality of processes 1112. In multiple various embodiments, the LAN 1108 includes a single workstation connected directly to a controller/multiplexer 1110 or alternatively includes a plurality of workstations, for example three workstations 1102, 1104, 1106, and many controller/multiplexers 1110 depending upon the purposes and requirements of the process control environment 1100. In some embodiments, a single process controller/multiplexer 1110 controls several different processes 1112 or alternatively controls a portion of a single process.
In the process control environment 1100, a process control strategy is developed by creating a software control solution on the engineering workstation 1106, for example, and transferring the solution via the LAN 1108 to the operator workstation 1102, lab workstation 1104, and to controller/multiplexer 1110 for execution. The operator workstation 1102 and lab workstation 1104 supply interface displays to the control/monitor strategy implemented in the controller/multiplexer 1110 and communicates to one or more of the controller/multiplexers 1110 to view the processes 1112 and change control attribute values according to the requirements of the designed solution. The processes 1112 are formed from one or more field devices, which may be smart field devices or conventional (non-smart) field devices. The process 1112 is illustratively depicted as two Fieldbus devices 1132, a HART (highway addressable remote transducer) device 1134 and a conventional field device 1136.
In addition, the operator workstation 1102 and lab workstation 1104 communicate visual and audio feedback to the operator regarding the status and conditions of the controlled processes 1112. The engineering workstation 1106 includes a central processing unit (CPU) 1116 and a display and input/output or user-interface device 1118 such as a keyboard, light pen and the like. The CPU 1116 typically includes a dedicated memory 1117. The dedicated memory 1117 includes a digital control system program (not shown) that executes on the CPU 1116 to implement control operations and functions of the process control environment 1100. The operator workstation 1102, the lab workstation 1104 and other workstations (not shown) within the process control environment 1100 include at least one central processing unit (not shown) which is electrically connected to a display (not shown) and a user-interface device (not shown) to allow interaction between a user and the CPU. In one embodiment, the process control environment 1100 includes workstations implemented using a Motorola 68040 processor and a Motorola 68360 communications processor running in companion mode with the 68040 with primary and secondary ethernet ports driven by the 68360 processor (SCC1 and SCC3 respectively).
The process control environment 1100 also includes a template generator 1124 and a control template library 1123 which, in combination, form a control template system 1120. A control template is defined as the grouping of attribute functions that are used to control a process and the methodology used for a particular process control function, the control attributes, variables, inputs, and outputs for the particular function and the graphical views of the function as needed such as an engineer view and an operator view.
The control template system 1120 includes the control template library 1123 that communicates with the template generator 1124. The control template library 1123 contains data representing sets of predefined or existing control template functions for use in process control programs. The control template functions are the templates that generally come with the system from the system designer to the user. The template generator 1124 is an interface that advantageously allows a user to create new control template functions or modify existing control template functions. The created and modified template functions are selectively stored in the control template library 1123.
The template generator 1124 includes an attributes and methods language generator 1126 and a graphics generator 1128. The attributes and methods language generator 1126 supplies display screens that allow the user to define a plurality of attribute functions associated with the creation of a new control template function or modification of a particular existing control template function, such as inputs, outputs, and other attributes, as well as providing display screens for enabling the user to select methods or programs that perform the new or modified function for the particular control template. The graphics generator 1128 furnishes a user capability to design graphical views to be associated with particular control templates. A user utilizes the data stored by the attributes and methods language generator 1126 and the graphics generator 1128 to completely define the attributes, methods, and graphical views for a control template. The data representing the created control template function is generally stored in the control template library 1123 and is subsequently available for selection and usage by an engineer for the design of process control solutions.
The process control environment 1100 is implemented using an object-oriented framework. An object-oriented framework uses object-oriented concepts such as class hierarchies, object states and object behavior. These concepts, which are briefly discussed below, are well known in the art. Additionally, an object-oriented framework may be written using object-oriented programming languages, such as the C++ programming language, which are well-known in the art, or may be written, as is the case with the preferred embodiment, using a non-object programming language such as C and implementing an object-oriented framework in that language.
The building block of an object-oriented framework is an object. The object is defined by a state and a behavior. The state of an object is set forth by fields of the object. The behavior of an object is set forth by methods of the object. Each object is an instance of a class, which provides a template for the object. A class defines zero or more fields and zero or more methods.
Fields are data structures which contain information defining a portion of the state of an object. Objects which are instances of the same class have the same fields. However, the particular information contained within the fields of the objects can vary from object to object. Each field can contain information that is direct, such as an integer value, or indirect, such as a reference to another object.
A method is a collection by computer instructions which can be executed in CPU 1116 by computer system software. The instructions of a method are executed, i.e., the method is performed, when software requests that the object for which the method is defined perform the method. A method can be performed by any object that is a member of the class that includes the method. The particular object performing the method is the responder or the responding object. When performing the method, the responder consumes one or more arguments, i.e., input data, and produces zero or one result, i.e., an object returned as output data. The methods for a particular object define the behavior of that object.
Classes of an object-oriented framework are organized in a class hierarchy. In a class hierarchy, a class inherits the fields and methods which are defined by the superclasses of that class. Additionally, the fields and methods defined by a class are inherited by any subclasses of the class, i.e., an instance of a subclass includes the fields defined by the superclass and can perform the methods defined by the superclass. Accordingly, when a method of an object is called, the method that is accessed may be defined in the class of which the object is a member or in any one of the superclasses of the class of which the object is a member. When a method of an object is called, process control environment 1100 selects the method to run by examining the class of the object and, if necessary, any superclasses of the object.
A subclass may override or supersede a method definition which is inherited from a superclass to enhance or change the behavior of the subclass. However, a subclass may not supersede the signature of the method. The signature of a method includes the method's identifier, the number and type of arguments, whether a result is returned, and, if so, the type of the result. The subclass supersedes an inherited method definition by redefining the computer instructions which are carried out in performance of the method.
Classes which are capable of having instances are concrete classes. Classes which cannot have instances are abstract classes. Abstract classes may define fields and methods which are inherited by subclasses of the abstract classes. The subclasses of an abstract class may be other abstract classes; however, ultimately, within the class hierarchy, the subclasses are concrete classes.
All classes defined in the disclosed preferred embodiment, except for mix-in classes which are described below, are subclasses of a class, Object. Thus, each class that is described herein and which is not a mix-in class inherits the methods and fields of class Object.
The process control environment 1100 exists in a configuration model or configuration implementation 1210 and a run-time model or run-time implementation 1220 shown in FIG. 12. In the configuration implementation 1210, the component devices, objects, interconnections and interrelationships within the process control environment 1100 are defined. In the run-time implementation 1220, operations of the various component devices, objects, interconnections and interrelationships are performed. The configuration implementation 1210 and the run-time implementation 1220 are interconnected by downloading. The download language creates system objects according to definitions supplied by a user and creates instances from the supplied definitions. Specifically, a completely configured Device Table relating to each device is downloaded to all Workstations on startup and when the Device Table is changed. For controller/multiplexers 1110, a downloaded Device Table only includes data for devices for which the controller/multiplexer 1110 is to initiate communications based on remote module data configured and used in the specific controller/multiplexer 1110. The Device Table is downloaded to the controller/multiplexer 1110 when other configuration data is downloaded. In addition to downloading definitions, the download language also uploads instances and instance values. The configuration implementation 1210 is activated to execute in the run-time implementation 1220 using an installation procedure. Also, network communications parameters are downloaded to each device when configuration data are downloaded and when a value is changed.
The process control environment 1100 includes multiple subsystems with several of the subsystems having both a configuration and a run-time implementation. For example, a process graphic subsystem 1230 supplies user-defined views and operator interfacing to the architecture of the process control environment 1100. The process graphic subsystem 1230 has a process graphic editor 1232, a part of the configuration implementation 1210, and a process graphic viewer 1234, a portion of the run-time implementation 1220. The process graphic editor 1232 is connected to the process graphic viewer 1234 by an intersubsystem interface 1236 in the downloaded language. The process control environment 1100 also includes a control subsystem 1240 which configures and installs control modules and equipment modules in a definition and module editor 1242 and which executes the control modules and the equipment modules in a run-time controller 1244. The definition and module editor 1242 operates within the configuration implementation 1210 and the run-time controller 1244 operates within the run-time implementation 1220 to supply continuous and sequencing control functions. The definition and module editor 1242 is connected to the run-time controller 1244 by an intersubsystem interface 1246 in the download language. The multiple subsystems are interconnected by a subsystem interface 1250.
The configuration implementation 1210 and the run-time implementation 1220 interface to a master database 1260 to support access to common data structures. Various local (non-master) databases 1262 interface to the master database 1260, for example, to transfer configuration data from the master database 1260 to the local databases 1262 as directed by a user. Part of the master database 1260 is a persistent database 1270. The persistent database 1270 is an object which transcends time so that the database continues to exist after the creator of the database no longer exists and transcends space so that the database is removable to an address space that is different from the address space at which the database was created. The entire configuration implementation 1210 is stored in the persistent database 1270.
The master database 1260 and local databases 1262 are accessible so that documentation of configurations, statistics and diagnostics are available for documentation purposes.
The run-time implementation 1220 interfaces to the persistent database 1270 and to local databases 1262 to access data structures formed by the configuration implementation 1210. In particular, the run-time implementation 1220 fetches selected equipment modules, displays and the like from the local databases 1262 and the persistent database 1270. The run-time implementation 1220 interfaces to other subsystems to install definitions, thereby installing objects that are used to create instances, when the definitions do not yet exist, instantiating run-time instances, and transferring information from various source to destination objects.
Device Tables are elements of the configuration database that are local to devices and, in combination, define part of the configuration implementation 1210. A Device Table contains information regarding a device in the process control environment 1100. Information items in a Device Table include a device ID, a device name, a device type, a PCN network number, an ACN segment number, a simplex/redundant communication flag, a controller MAC address, a comment field, a primary internet protocol (IP) address, a primary subnet mask, a secondary IP address and a secondary subnet mask.
Referring to FIG. 13, a block diagram illustrates a user interface 1300 for usage with both the configuration and run-time models of the process control environment 1100 shown in FIG. 11C. Part of the user interface 1300 is the Explorer™ 1310, an interfacing program defined under the Windows NT™ operating system which features a device-based configuration approach. Another part of the user interface 1300 is a module definition editor 1320 for interfacing to the process control environment 1100 using a control-based configuration approach.
The Explorers 1310 is operated by a user to select, construct and operate a configuration. In addition, the Explorer™ 1310 supplies an initial state for navigating across various tools and processors in a network. A user controls the Explorer™ 1310 to access libraries, areas, process control equipment and security operations. FIG. 13 illustrates the relationship between various tools that may be accessed by a task operating within the process control environment 1100 and the relationship between components of the process control environment 1100 such as libraries, areas, process control equipment and security. For example, when a user selects a “show tags” function from within an area, a “tag list builder” is displayed, showing a list of control and I/O flags. From the tag list builder, the user can use an “add tag” function to add a module to a list, thereby invoking a “module editor”.
Referring to FIG. 14, a schematic block diagram illustrates a hierarchical relationship among system objects of a configuration model 1400. The configuration model 1400 includes many configuration aspects including control, I/O, process graphics, process equipment, alarms, history and events. The configuration model 1400 also includes a device description and network topology layout.
The configuration model hierarchy 1400 is defined for usage by a particular set of users for visualizing system object relationships and locations and for communicating or navigating maintenance information among various system objects. For example, one configuration model hierarchy 1400, specifically a physical plant hierarchy, is defined for usage by maintenance engineers and technicians for visualizing physical plant relationships and locations and for communicating or navigating maintenance information among various instruments and equipment in a physical plant. An embodiment of a configuration model hierarchy 1400 that forms a physical plant hierarchy supports a subset of the SP88 physical equipment standard hierarchy and includes a configuration model site 1410, one or more physical plant areas 1420, equipment modules 1430 and control modules 1440.
The configuration model hierarchy 1400 is defined for a single process site 1410 which is divided into one or more named physical plant areas 1420 that are defined within the configuration model hierarchy 1400. The physical plant areas 1420 optionally contain tagged modules, each of which is uniquely instantiated within the configuration model hierarchy 1400. A physical plant area 1420 optionally contains one or more equipment modules 1430. An equipment module 1430 optionally contains other equipment modules 1430, control modules 1440 and function blocks. An equipment module 1430 includes and is controlled by a control template that is created according to one of a number of different graphical process control programming languages including continuous function block, ladder logic, or sequential function charting (“SFC”). The configuration model hierarchy 1400 optionally contains one or more control modules 1440. A control module 1440 is contained in an object such as a physical plant area 1420, an equipment module 1430 or another control module 1440. A control module 1440 optionally contains objects such as other control modules 1440 or function blocks. The control module 1440 is thus a container class, having instances which are collections of other objects. The control module 444 is encapsulated so that all of the contents and the implementation of the methods of the control module are hidden.
A controller/multiplexer is automatically sensed and incorporated into a run-time system as shown in FIG. 15. In step 2210, a controller/multiplexer, upon connection to the ACN and application of power, automatically sends a request for identification or verify IP address assignment. The request message includes the MAC address of the controller/multiplexer. The request is handled by a “Plug&Play Network Configuration Service”, which is known in the operating system art, at a master configuration controller/multiplexer in step 2212. In step 2214, the “Plug&Play Network Configuration Service” receives the request from the network to assign/verify an IP address, searches a table of configured devices for a MAC address match. If a match is found, in step 2216 the “Plug&Play Network Configuration Service” responds with the Device Name, Device ID, IP Address Information, Subnet Mask Information, ACN Segment Number and other items included in the Device Table. If no match is found, in step 2218 the “Plug&Play Network Configuration Service” automatically generates a default name for the device based on the controller/multiplexer MAC address (for example, Controller-000001) The new device is added to the database in a Device Scratch area in step 2220.
In step 2222, using the Explorer™ a user selects each unassigned controller/multiplexer in the Device Scratch area, drags the selection to the appropriate ACN segment and, and either adds the selection to the system as a new device or drops the selection to a pre-existing device configuration. If the unassigned controller/multiplexer is added as a new device, the configuration processing proceeds in the manner of manual incorporation of the device. In step 2224, a user is prompted for the real device name using the previously assigned name ‘Controller-000001’ as a default. If automatic address assignment is set, the new device is assigned the next Device ID and associated IP addresses and Subnet masks are automatically assigned in step 2226. If manual address assignment is set, the device is automatically assigned the next Device ID and the user is prompted to enter the IP Addresses and Subnet Masks in step 2228. The MAC address for the controller/multiplexer is set to the MAC address of the ‘Controller-000001’ as dragged into the ACN segment. The new controller/multiplexer Name, Device ID, IP Address, Subnet Masks and ACN number are added to the device table in the database. The next request by an unconfigured controller/multiplexer is answered by the “Plug&Play Network Configuration Service”.
If a new controller/multiplexer is dragged and dropped over an existing device, that device must be a controller/multiplexer type device and have an unassigned MAC address. Accordingly, the MAC address of the previously entered controller/multiplexer is set to the MAC address of the ‘Controller-000001’ device which was dropped. The new controller/multiplexer Name, Device ID, IP Addresses, Subnet Masks and ACN number are available for sending to the requesting controller/multiplexer by the “Plug&Play Network Configuration Service”.
The digital control system program 115 includes an auto-configure routine for automatically configuring the input/output (I/O) subsystem in response either to an “auto-configure” command by a user or in response to detection of a new controller/multiplexer.
Referring to FIG. 16, a flow chart illustrates steps of an automatic configuration routine for configuring a physical I/O device. An auto-configure command may be directed to a Controller/Multiplexer 1110, causing each I/O subsystem in the Controller/Multiplexer 1110 to auto-configure. An auto-configure command may be directed to an I/O subsystem, causing each I/O Card in the I/O subsystem to auto-configure. An auto-configure command may also be directed to an I/O Card.
The auto-configure operation for an I/O Card first interrogates the I/O Card at a particular card position to determine a Card Type in step 2310 and, implicitly for some I/O Cards, the number of I/O Ports in the I/O Card. If no I/O Card is previously created in the engineering database for that card position, an I/O Card of the appropriate type is defined and the appropriate number of I/O Ports are created in step 2312. If an I/O Card does exist in the engineering database for that card position, but the Card Type in the engineering database does not match the Card Type sensed at the card position, the auto-configure operation generates a graphic notification of the mismatch in step 2314 and interrogates a user to determine whether the engineering database is to be changed to include the sensed Card Type. The Card Type in the engineering database is changed to the sensed Card Type in step 2316 if requested by the user.
Once the Card Type is known, the auto-configuration program interrogates each I/O Port in accordance with the Card Type in step 2318 to determine the Port Type and, if information is available, the number of I/O Devices on the I/O Port. If no I/O Port is previously created in the engineering database for that port address, an I/O Port of the appropriate type is defined and the appropriate number of I/O Devices are created in step 2320. If an I/O Port exists in the engineering database for the Port address, but the Port Type does not match the type of the sensed I/O Port, the user is notified of the mismatch in step 2322, and asked whether the engineering database is to be changed to match the sensed I/O Port in step 2324. The Port Type in the engineering database is changed to the sensed Port Type in step 2326 if requested by the user.
Once the Port Type is known, the auto-configuration program interrogates each I/O Device in accordance with the Port Type in step 2328 to determine the Device Type. If no I/O Device is previously created in the engineering database for that device address, an I/O Device of the appropriate type is defined in step 2330. If an I/O Device exists in the engineering database for the Device address, but the Device Type does not match the type of the sensed I/O Device, the user is notified of the mismatch in step 2332, and asked whether the engineering database is to be changed to match the sensed I/O Device in step 2334. The Device Type in the engineering database is changed to the sensed Device Type in step 2336 if requested by the user.
In step 2338, instrument signal tags (ISTs) are automatically created for primary signal sources on the I/O Ports and I/O Devices, unless an IST already exists with the identical signal source path.
While the invention has been described with reference to various embodiments, it will be understood that these embodiments are illustrative and that the scope of the invention is not limited to them. Many variations, modifications, additions and improvements of the embodiments described are possible. For example, the control logic for performing operations may be implemented as executable program code at any levels including high level languages, assembler languages, and object codes. The control logic may also be implemented as state machines, electronic logic, and the like.

Claims (22)

1. A process control system comprising:
a process;
a plurality of devices coupled to the process;
a communication network coupled to the devices;
a workstation coupled to the plurality of devices via the network and including a user interface; and
a software system executable on the network and implementing a routine for automatically sensing a connection of a device to a network and placing the connected device in an accessible a standby state for communicating with a user via the user interface prior to commissioning the connected device into a predefined control configuration including:
a routine for configuring the connected device in a network control configuration of the plurality of devices, wherein the routine for configuring the connected device further includes:
a user-interactive routine for determining a device type of the connected device;
a user-interactive routine for determining a role of the connected device with respect to the process control system;
a user-interactive routine for assigning a physical device tag the determined role; and
a user-interactive routine for verifying connection of the device to the network.
2. A process control system comprising:
a process;
a plurality of devices coupled to the process;
a communication network coupled to the devices;
a workstation coupled to the plurality of devices via the network and including a user interface; and
a software system executable on the network and implementing a routine for automatically sensing a connection of a device to a network and placing the connected device in an accessible a standby state for communicating with a user via the user interface prior to commissioning the connected device into a predefined control configuration including:
a routine for configuring the connected device in a network control configuration of the plurality of devices, wherein the routine for configuring the connected device further includes:
a user-interactive routine for initiating calibration of the connected device; and
a user-interactive routine for configuring the device within an overall control scheme of the process control system.
3. A process control system comprising:
a process;
a plurality of devices coupled to the process;
a communication network coupled to the devices;
a workstation coupled to the plurality of devices via the network and including a user interface; and
a software system executable on the network and implementing a routine for automatically sensing a connection of a device to a network and placing the connected device in an accessible a standby state for communicating with a user via the user interface prior to commissioning the connected device into a predefined control configuration, the software system including:
a routine for commissioning the connected device including:
a user-interactive routine for assigning a physical device tag, a device address, and a device identification to the connected device; and
a user-interactive routine for installing a control strategy to the digital device.
4. A control system comprising:
a network;
a plurality of devices coupled to the network;
a distributed controller coupled to the plurality of devices and controlling the plurality of devices according to a defined control configuration, the distributed controller having standby control logic including:
a control logic for sensing a device that is connected to the network but not included in the defined control configuration;
a control logic for supplying initial interconnect information to the connected device;
a control logic for uploading configuration parameters from the connected device to the distributed controller; and
a control logic for configuring the connected device in the defined control configuration including:
a user-interactive control logic for determining a device type of the connected device;
a user-interactive control logic for determining a role of the connected device with respect to the process control system;
a user-interactive control logic for assigning a physical device tag the determined role; and
a user-interactive control logic for verifying connection of the device to the network.
5. A control system comprising:
a network;
a plurality of devices coupled to the network;
a distributed controller coupled to the plurality of devices and controlling the plurality of devices according to a defined control configuration, the distributed controller having standby control logic including:
a control logic for sensing a device that is connected to the network but not included in the defined control configuration;
a control logic for supplying initial interconnect information to the connected device;
a control logic for uploading configuration parameters from the connected device to the distributed controller; and
a control logic for configuring the connected device in the defined control configuration including:
a user-interactive control logic for initiating calibration of the connected device; and
a user-interactive control logic for configuring the device within an overall control scheme of the process control system.
6. A control system comprising:
a network;
a plurality of devices coupled to the network;
a distributed controller coupled to the plurality of devices and controlling the plurality of devices according to a defined control configuration, the distributed controller having standby control logic including:
a control logic for sensing a device that is connected to the network but not included in the defined control configuration;
a control logic for supplying initial interconnect information to the connected device;
a control logic for uploading configuration parameters from the connected device to the distributed controller; and
a control logic for commissioning the connected device including:
a user-interactive control logic for assigning a physical device tag, a device address, and a device identification to the connected device; and
a user-interactive control logic for installing a control strategy to the digital device.
7. A method of configuring a control system comprising:
predetermining a configuration of devices coupled to a network;
sensing a connection to the network of a device that is not included in the predetermined configuration;
assigning the connected device a standby address which allows access to device information and configuration parameters of the connected device;
commissioning the connected device into an operational state in communication with the control system, including:
assigning to the connected device a physical device tag, a device address, and a device identification;
installing a control strategy to the connected device; and
placing the connected device in an operational state in communication with the network; and
configuring the connected device in combination with the predetermined configuration of devices.
8. An executable program code for performing the method according to claim 7.
9. An article of manufacture comprising a storage storing an executable program code for performing the method according to claim 7.
10. A method of configuring a control system comprising:
predetermining a configuration of devices coupled to a network;
sensing a connection to the network of a device that is not, included in the predetermined configuration;
assigning the connected device a standby address which allows access to device information and configuration parameters of the connected device;
commissioning the connected device into an operational state in communication with the control system; and
configuring the connected device in combination with the predetermined configuration of devices, including:
interrogating the connected device to determine a device type;
determining a role of the connected device in the context of the predetermined configuration; and
assigning a physical device tag so that the determined role is set.
11. An executable program code for performing the method according to claim 10.
12. An article of manufacture comprising a storage storing an executable program code for performing the method according to claim 10.
13. A method of configuring a control system comprising:
predetermining a configuration of devices coupled to a network;
sensing a connection to the network of a device that is not included in the predetermined configuration;
assigning the connected device a standby address which allows access to device information and configuration parameters of the connected device;
commissioning the connected device into an operational state in communication with the control system; and
configuring the connected device in combination with the predetermined configuration of devices, including:
calibrating the connected device.
14. An executable program code for performing the method according to claim 13.
15. An article of manufacture comprising a storage storing an executable program code for performing the method according to claim 13.
16. An executable logic operating in a network for configuring a control system comprising:
means for predetermining a configuration of devices coupled to a network;
means for sensing a connection to the network of a device that is not included in the predetermined configuration;
means for assigning the connected device a standby address which allows access to device information and configuration parameters of the connected device;
means for commissioning the connected device into an operational state in communication with the control system, including:
means for assigning to the connected device a physical device tag, a device address, and a device identification;
means for installing a control strategy to the connected device; and
means for placing the connected device in an operational state in communication with the network; and
means for configuring the connected device in combination with the predetermined configuration of devices.
17. An article of manufacture comprising a storage storing an implementation of the executable logic according to claim 16.
18. An executable logic operating in a network for configuring a control system comprising:
means for predetermining a configuration of devices coupled to a network;
means for sensing a connection to the network of a device that is not included in the predetermined configuration;
means for assigning the connected device a standby address which allows access to device information and configuration parameters of the connected device;
means for commissioning the connected device into an operational state in communication with the control system; and
means for configuring the connected device in combination with the predetermined configuration of devices including:
means for interrogating the connected device to determine a device type;
means for determining a role of the connected device in the context of the predetermined configuration; and
means for assigning a physical device tag so that the determined role is set.
19. An article of manufacture comprising a storage storing an implementation of the executable logic according to claim 18.
20. An executable logic operating in a network for configuring a control system comprising:
means for predetermining a configuration of devices coupled to a network;
means for sensing a connection to the network of a device that is not included in the predetermined configuration;
means for assigning the connected device a standby address which allows access to device information and configuration parameters of the connected device;
means for commissioning the connected device into an operational state in communication with the control system; and
means for configuring the connected device in combination with the predetermined configuration of devices including:
means for calibrating the connected device.
21. An article of manufacture comprising a storage storing an implementation of the executable logic according to claim 20.
22. A process control system comprising:
a process;
a plurality of devices coupled to the process;
a communication network coupled to the devices;
a workstation coupled to the plurality of devices via the network and including a user interface; and
a software system executable on the network and implementing a routine for automatically sensing a connection of a device to a network and placing the connected device in an accessible a standby state for communicating with a user via the user interface,
wherein the devices are field devices selected from devices including pumps, valves, and motors.
US10/037,019 1997-02-14 2001-11-09 Process control system including automatic sensing and automatic configuration of devices Expired - Lifetime USRE40817E1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/037,019 USRE40817E1 (en) 1997-02-14 2001-11-09 Process control system including automatic sensing and automatic configuration of devices

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US08/799,966 US5980078A (en) 1997-02-14 1997-02-14 Process control system including automatic sensing and automatic configuration of devices
US10/037,019 USRE40817E1 (en) 1997-02-14 2001-11-09 Process control system including automatic sensing and automatic configuration of devices

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US08/799,966 Reissue US5980078A (en) 1997-02-14 1997-02-14 Process control system including automatic sensing and automatic configuration of devices

Publications (1)

Publication Number Publication Date
USRE40817E1 true USRE40817E1 (en) 2009-06-30

Family

ID=25177183

Family Applications (2)

Application Number Title Priority Date Filing Date
US08/799,966 Ceased US5980078A (en) 1997-02-14 1997-02-14 Process control system including automatic sensing and automatic configuration of devices
US10/037,019 Expired - Lifetime USRE40817E1 (en) 1997-02-14 2001-11-09 Process control system including automatic sensing and automatic configuration of devices

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US08/799,966 Ceased US5980078A (en) 1997-02-14 1997-02-14 Process control system including automatic sensing and automatic configuration of devices

Country Status (6)

Country Link
US (2) US5980078A (en)
JP (8) JP2001512598A (en)
AU (3) AU6045498A (en)
DE (3) DE19882116T5 (en)
GB (3) GB2336977B (en)
WO (3) WO1998036336A1 (en)

Cited By (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040220684A1 (en) * 2003-03-14 2004-11-04 Shinji Fukui Display and edit device, display method and program product
US20050267964A1 (en) * 2004-04-28 2005-12-01 Guenter Kech Method for providing apparatus specific information and corresponding system
US20080282332A1 (en) * 2005-09-29 2008-11-13 Siemens Aktiengesellschaft Method For Executing a Protected Function of an Electric Field Unit and Electrical Field Unit
US20090093894A1 (en) * 2007-10-04 2009-04-09 Samsung Electronics Co., Ltd. Production management system and method of controlling the same
US20100004758A1 (en) * 2006-07-13 2010-01-07 Mitsubishi Electric Corporation Equipment management system, programmable controller and centralized controller
US20100049841A1 (en) * 2007-11-14 2010-02-25 Huawei Technologies Co., Ltd. Method and system for automatically commissioning network device
US20100287255A1 (en) * 2009-05-08 2010-11-11 Siemens Ag Automation Device and Automation System
US20110004589A1 (en) * 2009-07-06 2011-01-06 Rockwell Automation Technologies, Inc. Diagnostics in a distributed directory system
US8745278B2 (en) 2010-10-13 2014-06-03 Rosemount Inc. Field device with self description
US9323241B2 (en) 2010-03-01 2016-04-26 Rittal Gmbh & Co. Kg Control cabinet monitoring device
US9397836B2 (en) 2014-08-11 2016-07-19 Fisher-Rosemount Systems, Inc. Securing devices to process control systems
US9541905B2 (en) 2013-03-15 2017-01-10 Fisher-Rosemount Systems, Inc. Context sensitive mobile control in a process plant
US9558220B2 (en) 2013-03-04 2017-01-31 Fisher-Rosemount Systems, Inc. Big data in process control systems
US9665088B2 (en) 2014-01-31 2017-05-30 Fisher-Rosemount Systems, Inc. Managing big data in process control systems
US9697170B2 (en) 2013-03-14 2017-07-04 Fisher-Rosemount Systems, Inc. Collecting and delivering data to a big data machine in a process control system
US9740802B2 (en) 2013-03-15 2017-08-22 Fisher-Rosemount Systems, Inc. Data modeling studio
US9804588B2 (en) 2014-03-14 2017-10-31 Fisher-Rosemount Systems, Inc. Determining associations and alignments of process elements and measurements in a process
US9823626B2 (en) 2014-10-06 2017-11-21 Fisher-Rosemount Systems, Inc. Regional big data in process control systems
US10168691B2 (en) 2014-10-06 2019-01-01 Fisher-Rosemount Systems, Inc. Data pipeline for process control system analytics
US10282676B2 (en) 2014-10-06 2019-05-07 Fisher-Rosemount Systems, Inc. Automatic signal processing-based learning in a process plant
US10386827B2 (en) 2013-03-04 2019-08-20 Fisher-Rosemount Systems, Inc. Distributed industrial performance monitoring and analytics platform
EP2971769B1 (en) 2013-03-15 2019-11-06 Kaeser Kompressoren SE R&i scheme input for a process for controlling and/or supervising a compressor system
US10503483B2 (en) 2016-02-12 2019-12-10 Fisher-Rosemount Systems, Inc. Rule builder in a process control network
US10649449B2 (en) 2013-03-04 2020-05-12 Fisher-Rosemount Systems, Inc. Distributed industrial performance monitoring and analytics
US10649424B2 (en) 2013-03-04 2020-05-12 Fisher-Rosemount Systems, Inc. Distributed industrial performance monitoring and analytics
US10678225B2 (en) 2013-03-04 2020-06-09 Fisher-Rosemount Systems, Inc. Data analytic services for distributed industrial performance monitoring
US10866952B2 (en) 2013-03-04 2020-12-15 Fisher-Rosemount Systems, Inc. Source-independent queries in distributed industrial system
US10909137B2 (en) 2014-10-06 2021-02-02 Fisher-Rosemount Systems, Inc. Streaming data for analytics in process control systems
US11704257B1 (en) 2022-04-15 2023-07-18 Graco Minnesota Inc. System provisioning using virtual peripherals

Families Citing this family (342)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6205497B1 (en) * 1994-09-07 2001-03-20 Hewlett-Packard Company System for configuring and input/output board in a computer
EP0825506B1 (en) 1996-08-20 2013-03-06 Invensys Systems, Inc. Methods and apparatus for remote process control
US20040194101A1 (en) * 1997-08-21 2004-09-30 Glanzer David A. Flexible function blocks
US6424872B1 (en) 1996-08-23 2002-07-23 Fieldbus Foundation Block oriented control system
US7146230B2 (en) * 1996-08-23 2006-12-05 Fieldbus Foundation Integrated fieldbus data server architecture
JP2950262B2 (en) * 1996-11-29 1999-09-20 日本電気株式会社 How to set up a multi-integrated agent system
US6311095B1 (en) 1997-02-07 2001-10-30 Peter G. Brown System and method for simulation and modeling of biopharmaceutical batch process manufacturing facilities
US6662061B1 (en) 1997-02-07 2003-12-09 Peter G. Brown System and method for simulation and modeling of batch process manufacturing facilities using process time lines
TW360829B (en) * 1997-02-10 1999-06-11 Siemens Ag Auditory active communication-subscriber, communication-method and communication system with auditory active communication-subscriber
US5980078A (en) * 1997-02-14 1999-11-09 Fisher-Rosemount Systems, Inc. Process control system including automatic sensing and automatic configuration of devices
US6983229B2 (en) * 1997-06-20 2006-01-03 Brown Peter G Method for scheduling solution preparation in biopharmaceutical batch process manufacturing
US7043414B2 (en) * 1997-06-20 2006-05-09 Brown Peter G System and method for simulating, modeling and scheduling of solution preparation in batch process manufacturing facilities
US6311093B1 (en) 1997-06-20 2001-10-30 Peter G. Brown System and method for simulation, modeling and scheduling of equipment maintenance and calibration in biopharmaceutical batch process manufacturing facilities
US6999824B2 (en) 1997-08-21 2006-02-14 Fieldbus Foundation System and method for implementing safety instrumented systems in a fieldbus architecture
EP1040360B1 (en) * 1997-12-15 2009-06-17 THOMSON Licensing Architecture for power line exchange protocol
US6175770B1 (en) * 1997-12-31 2001-01-16 Dana Corporation Electronic controller having automatic self-configuration capabilities
GB2334596B (en) * 1998-02-23 2002-02-20 Denno Co Ltd Control system
SE520101C2 (en) * 1998-05-13 2003-05-27 Axis Ab Integrated circuit and method to induce an integrated circuit to execute instructions
US6542928B1 (en) * 1998-06-02 2003-04-01 Micron Technology, Inc. Automatic configuration of testers and hosts on a computer network
US6219700B1 (en) * 1998-07-28 2001-04-17 Sun Microsystems, Inc. Method and apparatus for managing services in a computer network from a central console
JP3293779B2 (en) 1998-08-25 2002-06-17 キヤノン株式会社 Signal processing device and control method thereof
US6430610B1 (en) * 1998-09-02 2002-08-06 Steeleye Technology, Inc. TCP/IP address protection mechanism in a clustered server environment
US6738388B1 (en) 1998-09-10 2004-05-18 Fisher-Rosemount Systems, Inc. Shadow function block interface for use in a process control network
US6198480B1 (en) * 1998-10-07 2001-03-06 Wonderware Corporation Object-oriented tag browser
US7039688B2 (en) * 1998-11-12 2006-05-02 Ricoh Co., Ltd. Method and apparatus for automatic network configuration
EP1022697B1 (en) * 1999-01-22 2004-05-19 Fuji Electric Co., Ltd. Control apparatus for vending machine
EP1031898A3 (en) * 1999-02-26 2007-11-07 Matsushita Electric Industrial Co., Ltd. Communication system with initialization apparatus and program storage medium
US6438433B1 (en) * 1999-04-16 2002-08-20 Ncr Corporation Financial document processing system and method of operating a financial document processing system
DE29908319U1 (en) * 1999-05-10 2000-08-31 Siemens Ag Network with several participants as well as participants for such a network
WO2000070531A2 (en) * 1999-05-17 2000-11-23 The Foxboro Company Methods and apparatus for control configuration
US7089530B1 (en) 1999-05-17 2006-08-08 Invensys Systems, Inc. Process control configuration system with connection validation and configuration
US6754885B1 (en) 1999-05-17 2004-06-22 Invensys Systems, Inc. Methods and apparatus for controlling object appearance in a process control configuration system
WO2000073885A1 (en) * 1999-06-01 2000-12-07 The Foxboro Company Systems and methods for linking parameters for the configuration of control systems
US6615088B1 (en) * 1999-06-09 2003-09-02 Amx Corporation System and method of device interface configuration for a control system
US6788980B1 (en) 1999-06-11 2004-09-07 Invensys Systems, Inc. Methods and apparatus for control using control devices that provide a virtual machine environment and that communicate via an IP network
US6515683B1 (en) * 1999-06-22 2003-02-04 Siemens Energy And Automation Autoconfiguring graphic interface for controllers having dynamic database structures
US6766212B1 (en) * 1999-07-14 2004-07-20 Nec Electronics, Inc. Identifying relationships among constituent parts of a wafer fabrication system
US6728590B1 (en) 1999-07-14 2004-04-27 Nec Electronics, Inc. Identifying wafer fabrication system impacts resulting from specified actions
US6510352B1 (en) 1999-07-29 2003-01-21 The Foxboro Company Methods and apparatus for object-based process control
EP1206868B1 (en) * 1999-08-23 2005-03-16 PILZ GmbH & CO. Method of configuring a safe station and a safe control system using the same
US6618745B2 (en) * 1999-09-10 2003-09-09 Fisher Rosemount Systems, Inc. Linking device in a process control system that allows the formation of a control loop having function blocks in a controller and in field devices
GB2394630B (en) * 1999-10-04 2004-06-09 Fisher Rosemount Systems Inc Process control configuration system for use with a Profibus device network
US6449715B1 (en) * 1999-10-04 2002-09-10 Fisher-Rosemount Systems, Inc. Process control configuration system for use with a profibus device network
US6446202B1 (en) * 1999-10-04 2002-09-03 Fisher-Rosemount Systems, Inc. Process control configuration system for use with an AS-Interface device network
US6711629B1 (en) 1999-10-18 2004-03-23 Fisher-Rosemount Systems, Inc. Transparent support of remote I/O in a process control system
US6434500B1 (en) 1999-10-18 2002-08-13 Rosemount Inc. Interface for managing test definitions
US6704737B1 (en) * 1999-10-18 2004-03-09 Fisher-Rosemount Systems, Inc. Accessing and updating a configuration database from distributed physical locations within a process control system
DE59911450D1 (en) * 1999-11-01 2005-02-17 Abb Research Ltd Integration of a bay control unit into a plant control system
EP1096349A1 (en) * 1999-11-01 2001-05-02 Abb Research Ltd. Configuration of a plant guidance sytem
US6473660B1 (en) 1999-12-03 2002-10-29 The Foxboro Company Process control system and method with automatic fault avoidance
US6445678B1 (en) * 1999-12-07 2002-09-03 Intel Corporation Method and apparatus for implementing leaf node proxy in a network
US6772017B1 (en) 2000-01-20 2004-08-03 Fisher-Rosemount Systems, Inc. Tool for configuring and managing a process control network including the use of spatial information
US7474929B2 (en) 2000-01-20 2009-01-06 Fisher-Rosemount Systems, Inc. Enhanced tool for managing a process control network
US6779179B1 (en) 2000-03-20 2004-08-17 Exent Technologies, Inc. Registry emulation
AU2001243502A1 (en) 2000-03-09 2001-09-17 Exent Technologies, Inc. Registry emulation
US20010049562A1 (en) * 2000-03-10 2001-12-06 Takuo Takano Control system and control method
DE50115341D1 (en) * 2000-04-13 2010-03-25 Infineon Technologies Ag DC CONVERTER
US6701357B1 (en) * 2000-04-19 2004-03-02 Toshiba America Information Systems, Inc. Server appliance
JP2001319267A (en) * 2000-05-09 2001-11-16 Sanden Corp Control system for automatic vending machine
US7844365B2 (en) * 2000-05-12 2010-11-30 Rosemount Inc. Field-mounted process device
US7228186B2 (en) 2000-05-12 2007-06-05 Rosemount Inc. Field-mounted process device with programmable digital/analog interface
US6574515B1 (en) * 2000-05-12 2003-06-03 Rosemount Inc. Two-wire field-mounted process device
US6611863B1 (en) 2000-06-05 2003-08-26 Intel Corporation Automatic device assignment through programmable device discovery for policy based network management
US20050240286A1 (en) * 2000-06-21 2005-10-27 Glanzer David A Block-oriented control system on high speed ethernet
US6947389B1 (en) * 2000-06-30 2005-09-20 Fisher-Rosemount Systems, Inc. Two-mode foundation fieldbus device configurator
GB2395803B (en) * 2000-06-30 2004-10-27 Fisher Rosemount Systems Inc Two-mode foundation fieldbus device configurator
WO2002003634A1 (en) * 2000-07-05 2002-01-10 Telefonaktiebolaget Lm Ericsson (Publ) Resource saving device and coupling of a connection in a telecommunication system
US6473706B1 (en) 2000-07-06 2002-10-29 International Business Machines Corporation Self-configuring and self-calibrating automated system
US6982953B1 (en) * 2000-07-11 2006-01-03 Scorpion Controls, Inc. Automatic determination of correct IP address for network-connected devices
DE10040438A1 (en) * 2000-08-18 2002-03-07 Siemens Ag Address assignment procedure for at least one new bus device connected to a bus system
US6944681B1 (en) 2000-09-08 2005-09-13 Fisher-Rosemount Systems, Inc. Probing algorithm for foundation fieldbus protocol
US20020184348A1 (en) * 2000-09-20 2002-12-05 Lockheed Martin Corporation Object oriented framework architecture for sensing and/or control environments
JP2004510365A (en) * 2000-09-20 2004-04-02 ロックヒード マーティン コーポレイション Object-oriented framework for sensing and / or control environment
ATE471589T1 (en) * 2000-09-21 2010-07-15 Abb Schweiz Ag CONFIGURATION OF A CONTROL SYSTEM OF AN ELECTRICAL SWITCHGEAR
US6434682B1 (en) 2000-09-28 2002-08-13 International Business Machines Corporation Data management system with shortcut migration via efficient automatic reconnection to previously migrated copy
US6604160B1 (en) 2000-09-28 2003-08-05 International Business Machines Corporation Computing system arbitrating and selectively providing resource-seeking tasks with takeaway of non-shareable resources
US6446160B1 (en) 2000-09-28 2002-09-03 International Business Machines Corporation Multi-drive data storage system with analysis and selected demounting of idle data storage media
EP1346728A1 (en) * 2000-11-22 2003-09-24 Mitsubishi Pharma Corporation Ophthalmological preparations
DE50002284D1 (en) * 2000-11-30 2003-06-26 Siemens Building Tech Ag Arrangement for monitoring, control and regulation of an operational system of a building
US7054946B2 (en) * 2000-12-06 2006-05-30 Intelliden Dynamic configuration of network devices to enable data transfers
US7249170B2 (en) 2000-12-06 2007-07-24 Intelliden System and method for configuration, management and monitoring of network resources
US6978301B2 (en) 2000-12-06 2005-12-20 Intelliden System and method for configuring a network device
US8219662B2 (en) 2000-12-06 2012-07-10 International Business Machines Corporation Redirecting data generated by network devices
US20020069271A1 (en) * 2000-12-06 2002-06-06 Glen Tindal Event manager for network operating system
US7693966B2 (en) * 2000-12-14 2010-04-06 Hirschman Electronics Gmbh & Co. Kg Automatic configuration of a network
US6917857B2 (en) * 2000-12-15 2005-07-12 American Standard International Inc. Magnetically overridden flow control device
US6674533B2 (en) 2000-12-21 2004-01-06 Joseph K. Price Anodizing system with a coating thickness monitor and an anodized product
US7365860B2 (en) * 2000-12-21 2008-04-29 Sensory Analytics System capable of determining applied and anodized coating thickness of a coated-anodized product
US7274463B2 (en) * 2003-12-30 2007-09-25 Sensory Analytics Anodizing system with a coating thickness monitor and an anodized product
IT1319716B1 (en) * 2000-12-28 2003-11-03 Abb Ricerca Spa COMPUTERIZED SYSTEM TO PERFORM REMOTE EDIAGNOSTIC CONFIGURATION OPERATIONS ON A FIELD DEVICE
DE10101746A1 (en) * 2001-01-16 2002-08-14 Siemens Ag Method for operating an automation system
US7185083B2 (en) * 2001-01-17 2007-02-27 Fisher-Rosemount Systems, Inc. Method and apparatus for identifying an I/O network in a process control system
FR2820222B1 (en) * 2001-01-26 2003-03-21 Schneider Automation METHOD FOR PROGRAMMING AN AUTOMATION APPLICATION
EP1233318A1 (en) * 2001-02-16 2002-08-21 Abb Research Ltd. Software coumpounds for a distributed control system
DE10108962A1 (en) 2001-02-20 2002-09-12 Pilz Gmbh & Co Method and device for programming a safety controller
US7150037B2 (en) * 2001-03-21 2006-12-12 Intelliden, Inc. Network configuration manager
JP4717240B2 (en) * 2001-03-30 2011-07-06 キヤノン株式会社 Information processing apparatus, information processing apparatus control method, and storage medium
US6760630B2 (en) * 2001-04-03 2004-07-06 Siemens Aktiengesellschaft Method and implementation of process control
US6687733B2 (en) * 2001-06-01 2004-02-03 Intergenix Method and system for automatically configuring a client-server network
EP1410204B1 (en) 2001-06-22 2016-11-09 Wonderware Corporation Supervisory process control and manufacturing information system application having an extensible component model
US7650607B2 (en) 2001-06-22 2010-01-19 Invensys Systems, Inc. Supervisory process control and manufacturing information system application having a layered architecture
US7802238B2 (en) 2001-06-22 2010-09-21 Invensys Systems, Inc. Process control script development and execution facility supporting multiple user-side programming languages
EP1410228B1 (en) * 2001-06-22 2016-03-23 Wonderware Corporation Remotely monitoring / diagnosing distributed components of a supervisory process control and manufacturing information application from a central location
US8001594B2 (en) * 2001-07-30 2011-08-16 Ipass, Inc. Monitoring computer network security enforcement
US6819960B1 (en) 2001-08-13 2004-11-16 Rockwell Software Inc. Industrial controller automation interface
DE10140763A1 (en) * 2001-08-20 2003-03-06 Siemens Ag Method and arrangement for the configuration of assemblies in a data processing system
US8296400B2 (en) 2001-08-29 2012-10-23 International Business Machines Corporation System and method for generating a configuration schema
US7200548B2 (en) * 2001-08-29 2007-04-03 Intelliden System and method for modeling a network device's configuration
US7444208B2 (en) * 2001-09-10 2008-10-28 Densei-Lambda K.K. Electrical system wiring diagram generating system, and power supply device and program used for the same
CA2357444A1 (en) * 2001-09-13 2003-03-13 Armadillo Networks Inc. System and methods for automatic negotiation in distributed computing
FR2830152B1 (en) * 2001-09-27 2004-08-20 Airbus France DETERMINIST FIELD BUS AND METHOD FOR MANAGING SUCH A BUS
DE10149147A1 (en) * 2001-10-04 2003-04-17 Heidenhain Gmbh Dr Johannes Method and device for creating or changing NC programs
US20030079053A1 (en) * 2001-10-23 2003-04-24 Kevin Burns System and method for evaluating effectiveness of network configuration management tools
US6567272B1 (en) * 2001-11-09 2003-05-20 Dell Products L.P. System and method for utilizing system configurations in a modular computer system
KR100423969B1 (en) * 2001-11-16 2004-03-22 삼성전자주식회사 Field bus interface board and control method thereof
US7139839B2 (en) * 2001-11-26 2006-11-21 Schneider Automation Inc. Method and apparatus for assigning a network node address
US7065562B2 (en) * 2001-11-26 2006-06-20 Intelliden, Inc. System and method for generating a representation of a configuration schema
EP1489476B1 (en) * 2001-12-06 2019-12-04 Fisher-Rosemount Systems, Inc. Intrinsically safe field maintenance tool
CN1299178C (en) 2001-12-06 2007-02-07 费希尔·罗斯蒙德系统公司 Intrinsically safe field maintenance tool
US7426452B2 (en) 2001-12-06 2008-09-16 Fisher-Rosemount Systems. Inc. Dual protocol handheld field maintenance tool with radio-frequency communication
US20030229472A1 (en) * 2001-12-06 2003-12-11 Kantzes Christopher P. Field maintenance tool with improved device description communication and storage
US20030204373A1 (en) * 2001-12-06 2003-10-30 Fisher-Rosemount Systems, Inc. Wireless communication method between handheld field maintenance tools
JP4234342B2 (en) * 2001-12-26 2009-03-04 パナソニック株式会社 Component mounting operation support system and method for component mounting apparatus
US7080093B2 (en) * 2002-01-14 2006-07-18 Sun Microsystems, Inc. System and method for database design
US6973508B2 (en) * 2002-02-12 2005-12-06 Fisher-Rosemount Systems, Inc. Highly versatile process control system controller
JP4150524B2 (en) 2002-02-13 2008-09-17 株式会社リコー Production management method and production management program
DE10207831A1 (en) * 2002-02-25 2003-09-04 Siemens Ag Procedure for configuring and / or configuring a project
US7519729B2 (en) * 2002-02-27 2009-04-14 Ricoh Co. Ltd. Method and apparatus for monitoring remote devices through a local monitoring station and communicating with a central station supporting multiple manufacturers
US7039744B2 (en) * 2002-03-12 2006-05-02 Fisher-Rosemount Systems, Inc. Movable lead access member for handheld field maintenance tool
US7027952B2 (en) * 2002-03-12 2006-04-11 Fisher-Rosemount Systems, Inc. Data transmission method for a multi-protocol handheld field maintenance tool
US20030174068A1 (en) * 2002-03-15 2003-09-18 Dobos Jeffrey A. Apparatus for calibrating a digital field sensor
DE10212131A1 (en) * 2002-03-19 2003-10-02 Siemens Ag Process for monitoring an automation system
KR20030075728A (en) * 2002-03-20 2003-09-26 엘지전자 주식회사 Method for confirming a home appliance connect state of home network system
US7565456B2 (en) * 2002-04-12 2009-07-21 Siemens Aktiengesellschaft Method for reconfiguring an automation device
US20030195952A1 (en) * 2002-04-15 2003-10-16 Henry Steven G. Digital transmitter device configuration
US20030217054A1 (en) 2002-04-15 2003-11-20 Bachman George E. Methods and apparatus for process, factory-floor, environmental, computer aided manufacturing-based or other control system with real-time data distribution
US6907305B2 (en) * 2002-04-30 2005-06-14 Advanced Micro Devices, Inc. Agent reactive scheduling in an automated manufacturing environment
US6959329B2 (en) * 2002-05-15 2005-10-25 Intelliden System and method for transforming configuration commands
US7890348B2 (en) * 2002-05-20 2011-02-15 Ge Medical Systems Global Technology Company, Llc Text-based generic script processing for dynamic configuration of distributed systems
JP2003339729A (en) 2002-05-22 2003-12-02 Olympus Optical Co Ltd Ultrasonic operation apparatus
US20030222903A1 (en) * 2002-05-31 2003-12-04 Wolfgang Herzog Distributing customized computer settings to affected systems
US20040003067A1 (en) * 2002-06-27 2004-01-01 Daniel Ferrin System and method for enabling a user interface with GUI meta data
WO2004006299A2 (en) * 2002-07-03 2004-01-15 Tokyo Electron Limited Method for dynamic sensor configuration and runtime execution
US7464145B2 (en) 2002-07-11 2008-12-09 Intelliden, Inc. Repository-independent system and method for asset management and reconciliation
US7461158B2 (en) 2002-08-07 2008-12-02 Intelliden, Inc. System and method for controlling access rights to network resources
US7366893B2 (en) * 2002-08-07 2008-04-29 Intelliden, Inc. Method and apparatus for protecting a network from attack
US7558847B2 (en) * 2002-09-13 2009-07-07 Intelliden, Inc. System and method for mapping between and controlling different device abstractions
DE10245658A1 (en) 2002-09-30 2004-04-15 Koenig & Bauer Ag Method and device for the automatic material supply of a processing machine as well as a control system and printing plant with a control system
DE10246895B3 (en) * 2002-10-08 2004-06-09 Siemens Ag Procedure for changing a parameter for the operation of a network and participants for performing the procedure
DE10348563B4 (en) * 2002-10-22 2014-01-09 Fisher-Rosemount Systems, Inc. Integration of graphic display elements, process modules and control modules in process plants
US9983559B2 (en) 2002-10-22 2018-05-29 Fisher-Rosemount Systems, Inc. Updating and utilizing dynamic process simulation in an operating process environment
US7146231B2 (en) * 2002-10-22 2006-12-05 Fisher-Rosemount Systems, Inc.. Smart process modules and objects in process plants
US10261506B2 (en) 2002-12-05 2019-04-16 Fisher-Rosemount Systems, Inc. Method of adding software to a field maintenance tool
US7346551B2 (en) 2002-12-23 2008-03-18 Cybersource Corporation Method and apparatus for custom strategy specification in a hosted electronic transaction service system
CN100388529C (en) 2003-03-06 2008-05-14 费希尔-罗斯蒙德系统公司 Heat flow regulating cover for an electrical storage cell
US7970006B1 (en) * 2003-03-10 2011-06-28 Ciena Corporation Dynamic configuration for a modular interconnect
US7366651B1 (en) * 2003-03-14 2008-04-29 Xilinx, Inc. Co-simulation interface
EP1619994A4 (en) 2003-04-16 2009-03-11 Univ Drexel Acoustic blood analyzer for assessing blood properties
US7512521B2 (en) 2003-04-30 2009-03-31 Fisher-Rosemount Systems, Inc. Intrinsically safe field maintenance tool with power islands
US7054695B2 (en) 2003-05-15 2006-05-30 Fisher-Rosemount Systems, Inc. Field maintenance tool with enhanced scripts
US7036386B2 (en) * 2003-05-16 2006-05-02 Fisher-Rosemount Systems, Inc. Multipurpose utility mounting assembly for handheld field maintenance tool
US7526802B2 (en) 2003-05-16 2009-04-28 Fisher-Rosemount Systems, Inc. Memory authentication for intrinsically safe field maintenance tools
US8874402B2 (en) 2003-05-16 2014-10-28 Fisher-Rosemount Systems, Inc. Physical memory handling for handheld field maintenance tools
US6925419B2 (en) 2003-05-16 2005-08-02 Fisher-Rosemount Systems, Inc. Intrinsically safe field maintenance tool with removable battery pack
US7199784B2 (en) * 2003-05-16 2007-04-03 Fisher Rosemount Systems, Inc. One-handed operation of a handheld field maintenance tool
US7197580B2 (en) * 2003-05-29 2007-03-27 Microsoft Corporation Computer system and method for supporting network-enabled devices
DE10394242T5 (en) * 2003-06-02 2006-04-27 Abb Research Ltd. Method and instrument for allocating computational resources in a distributed control system
US7460865B2 (en) * 2003-06-18 2008-12-02 Fisher-Rosemount Systems, Inc. Self-configuring communication networks for use with process control systems
JP2005025652A (en) * 2003-07-01 2005-01-27 System V:Kk Information conversion device for device management
DE10343670A1 (en) * 2003-09-18 2005-05-25 Endress + Hauser Conducta Gesellschaft für Mess- und Regeltechnik mbH + Co. KG Device driver for field devices of process automation technology
US7865907B2 (en) * 2003-09-25 2011-01-04 Fisher-Rosemount Systems, Inc. Method and apparatus for providing automatic software updates
US7016741B2 (en) * 2003-10-14 2006-03-21 Rosemount Inc. Process control loop signal converter
US20050092253A1 (en) * 2003-11-04 2005-05-05 Venkat Selvamanickam Tape-manufacturing system having extended operational capabilites
US7257498B2 (en) * 2003-12-04 2007-08-14 Honeywell International Inc. System and method for the safe automatic detection of a field device communicating with current modulated signal
JP4718480B2 (en) * 2003-12-04 2011-07-06 ハネウェル・インターナショナル・インコーポレーテッド System and method for secure automatic detection of field devices communicating with current modulated signals
CN100445905C (en) * 2003-12-04 2008-12-24 霍尼韦尔国际公司 System and method for the safe automatic detection of a field device communicating with current modulated signal
DE10357276B4 (en) * 2003-12-05 2012-02-23 Abb Research Ltd. System and method for the directed provision and installation of device-specific functionalities and / or information for the field devices of a distributed system
US7146034B2 (en) * 2003-12-09 2006-12-05 Superpower, Inc. Tape manufacturing system
US7359317B1 (en) * 2004-02-20 2008-04-15 Excel Switching Corporation Redundancy arrangement for telecommunications switch
US7761923B2 (en) 2004-03-01 2010-07-20 Invensys Systems, Inc. Process control methods and apparatus for intrusion detection, protection and network hardening
US20050223983A1 (en) 2004-04-08 2005-10-13 Venkat Selvamanickam Chemical vapor deposition (CVD) apparatus usable in the manufacture of superconducting conductors
US20050223984A1 (en) * 2004-04-08 2005-10-13 Hee-Gyoun Lee Chemical vapor deposition (CVD) apparatus usable in the manufacture of superconducting conductors
JP4381872B2 (en) * 2004-04-09 2009-12-09 矢崎総業株式会社 Wire crimping method
JP2005327263A (en) * 2004-04-13 2005-11-24 Omron Corp Control system setting device
US8463879B2 (en) * 2004-04-19 2013-06-11 Hewlett-Packard Development Company, L.P. Method and apparatus for automatic verification of a machine-readable map of networked devices
DE102004021089A1 (en) * 2004-04-29 2005-11-24 Bosch Rexroth Ag Device for address assignment in a standardized fieldbus system
US7729789B2 (en) 2004-05-04 2010-06-01 Fisher-Rosemount Systems, Inc. Process plant monitoring based on multivariate statistical analysis and on-line process simulation
JP2007536634A (en) 2004-05-04 2007-12-13 フィッシャー−ローズマウント・システムズ・インコーポレーテッド Service-oriented architecture for process control systems
US20050268012A1 (en) * 2004-05-05 2005-12-01 Ralf Schaetzle Method for automatic configuration of a process control system and corresponding process control system
GB0415144D0 (en) * 2004-07-06 2004-08-11 Attar Software Ltd Method and system for detecting events in process operating data and identifying associations between related events
US7735063B2 (en) * 2004-07-07 2010-06-08 Sap Aktiengesellschaft Providing customizable configuration data in computer systems
US7774369B2 (en) * 2004-07-07 2010-08-10 Sap Aktiengesellschaft Configuring computer systems with business configuration information
US7904488B2 (en) 2004-07-21 2011-03-08 Rockwell Automation Technologies, Inc. Time stamp methods for unified plant model
DE102004037064A1 (en) * 2004-07-30 2006-02-16 Abb Patent Gmbh Method and device for functional testing of a field device before its initial commissioning
DE102004040282A1 (en) 2004-08-19 2006-03-09 Siemens Ag Parameter identification for field devices in automation technology
US7387811B2 (en) * 2004-09-21 2008-06-17 Superpower, Inc. Method for manufacturing high temperature superconducting conductors using chemical vapor deposition (CVD)
US7937549B2 (en) * 2004-09-21 2011-05-03 International Business Machines Corporation Storage system and subsystem to automatically detect hardware configuration changes
US8756521B1 (en) 2004-09-30 2014-06-17 Rockwell Automation Technologies, Inc. Systems and methods for automatic visualization configuration
US7529925B2 (en) 2005-03-15 2009-05-05 Trapeze Networks, Inc. System and method for distributing keys in a wireless network
DE102005019970B4 (en) * 2005-04-27 2007-04-26 Phoenix Contact Gmbh & Co. Kg Address assignment for secure bus users
US7809683B2 (en) 2005-05-13 2010-10-05 Rockwell Automation Technologies, Inc. Library that includes modifiable industrial automation objects
US7676281B2 (en) 2005-05-13 2010-03-09 Rockwell Automation Technologies, Inc. Distributed database in an industrial automation environment
US7650405B2 (en) 2005-05-13 2010-01-19 Rockwell Automation Technologies, Inc. Tracking and tracing across process boundaries in an industrial automation environment
US7672737B2 (en) 2005-05-13 2010-03-02 Rockwell Automation Technologies, Inc. Hierarchically structured data model for utilization in industrial automation environments
US8799800B2 (en) 2005-05-13 2014-08-05 Rockwell Automation Technologies, Inc. Automatic user interface generation
US8160574B1 (en) 2005-06-17 2012-04-17 Fisher-Rosemount Systems, Inc. Wireless architecture utilizing geo-referencing
US8332560B2 (en) * 2005-07-11 2012-12-11 Dell Products L.P. System and method for identifying inoperable connection points in a storage enclosure
US7835295B2 (en) * 2005-07-19 2010-11-16 Rosemount Inc. Interface module with power over Ethernet function
CN101223486B (en) * 2005-07-20 2012-02-08 罗斯蒙德公司 Field device with power over ethernet
DE102005034944B3 (en) * 2005-07-22 2006-11-09 Siemens Ag Field bus system e.g. LIN bus system, configuration method for use in e.g. motor vehicle, involves checking whether bus subscriber still has standard address, and identifying subscriber and assigning clear subscriber address to subscriber
US7421526B2 (en) * 2005-08-24 2008-09-02 Honeywell International Inc. Reconfigurable virtual backplane architecture
US9063739B2 (en) * 2005-09-07 2015-06-23 Open Invention Network, Llc Method and computer program for device configuration
US7548789B2 (en) 2005-09-29 2009-06-16 Rockwell Automation Technologies, Inc. Editing lifecycle and deployment of objects in an industrial automation environment
US7609713B2 (en) * 2005-09-29 2009-10-27 Fisher-Rosemount Systems, Inc. Associating a signal measurement with a communication device on a network
US7881812B2 (en) 2005-09-29 2011-02-01 Rockwell Automation Technologies, Inc. Editing and configuring device
US7734590B2 (en) 2005-09-30 2010-06-08 Rockwell Automation Technologies, Inc. Incremental association of metadata to production data
US8484250B2 (en) 2005-09-30 2013-07-09 Rockwell Automation Technologies, Inc. Data federation with industrial control systems
US7660638B2 (en) 2005-09-30 2010-02-09 Rockwell Automation Technologies, Inc. Business process execution engine
US7526794B2 (en) 2005-09-30 2009-04-28 Rockwell Automation Technologies, Inc. Data perspectives in controller system and production management systems
US8275680B2 (en) 2005-09-30 2012-09-25 Rockwell Automation Technologies, Inc. Enabling transactional mechanisms in an automated controller system
US7801628B2 (en) 2005-09-30 2010-09-21 Rockwell Automation Technologies, Inc. Industrial operator interfaces interacting with higher-level business workflow
US8527888B2 (en) * 2006-04-11 2013-09-03 Invensys Systems, Inc. Method and supporting configuration user interfaces for streamlining installing replacement field devices
US7573859B2 (en) 2005-10-13 2009-08-11 Trapeze Networks, Inc. System and method for remote monitoring in a wireless network
WO2007044986A2 (en) 2005-10-13 2007-04-19 Trapeze Networks, Inc. System and method for remote monitoring in a wireless network
US8638762B2 (en) 2005-10-13 2014-01-28 Trapeze Networks, Inc. System and method for network integrity
US7724703B2 (en) 2005-10-13 2010-05-25 Belden, Inc. System and method for wireless network monitoring
US8250587B2 (en) 2005-10-27 2012-08-21 Trapeze Networks, Inc. Non-persistent and persistent information setting method and system for inter-process communication
US20070106778A1 (en) * 2005-10-27 2007-05-10 Zeldin Paul E Information and status and statistics messaging method and system for inter-process communication
US8055358B2 (en) 2005-12-05 2011-11-08 Fisher-Rosemount Systems, Inc. Multi-objective predictive process optimization with concurrent process simulation
US8676357B2 (en) 2005-12-20 2014-03-18 Fieldbus Foundation System and method for implementing an extended 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
DE102007003196A1 (en) * 2006-01-23 2007-07-26 Abb Patent Gmbh communication system
US20070222460A1 (en) * 2006-03-07 2007-09-27 Price Joseph K Mobile apparatus capable of surface measurements
WO2007123753A2 (en) 2006-03-30 2007-11-01 Invensys Systems, Inc. Digital data processing apparatus and methods for improving plant performance
US7558266B2 (en) 2006-05-03 2009-07-07 Trapeze Networks, Inc. System and method for restricting network access using forwarding databases
US8966018B2 (en) 2006-05-19 2015-02-24 Trapeze Networks, Inc. Automated network device configuration and network deployment
US7813817B2 (en) * 2006-05-19 2010-10-12 Westinghouse Electric Co Llc Computerized procedures system
US20070268515A1 (en) * 2006-05-19 2007-11-22 Yun Freund System and method for automatic configuration of remote network switch and connected access point devices
US8818322B2 (en) 2006-06-09 2014-08-26 Trapeze Networks, Inc. Untethered access point mesh system and method
US9258702B2 (en) 2006-06-09 2016-02-09 Trapeze Networks, Inc. AP-local dynamic switching
US9191799B2 (en) 2006-06-09 2015-11-17 Juniper Networks, Inc. Sharing data between wireless switches system and method
US20080005344A1 (en) * 2006-06-29 2008-01-03 Ford Daniel E Method and system for configuring a network device using a template
US7668608B2 (en) * 2006-09-01 2010-02-23 Fisher-Rosemount Systems, Inc. Graphical programming language object editing and reporting tool
US7953713B2 (en) * 2006-09-14 2011-05-31 International Business Machines Corporation System and method for representing and using tagged data in a management system
US8340110B2 (en) 2006-09-15 2012-12-25 Trapeze Networks, Inc. Quality of service provisioning for wireless networks
US7835805B2 (en) 2006-09-29 2010-11-16 Rockwell Automation Technologies, Inc. HMI views of modules for industrial control systems
US7612661B1 (en) 2006-09-29 2009-11-03 Rockwell Automation Technologies, Inc. Dynamic messages
US7873061B2 (en) 2006-12-28 2011-01-18 Trapeze Networks, Inc. System and method for aggregation and queuing in a wireless network
US7684875B2 (en) * 2007-02-02 2010-03-23 Fisher-Rosemount Systems, Inc. Methods and apparatus to configure process control system inputs and outputs
US7634322B2 (en) * 2007-03-23 2009-12-15 Honeywell International Inc. Configuration of wireless field devices for process control plants
DE102007032810B3 (en) * 2007-07-13 2008-11-27 Siemens Ag Method for allocation of physical position to slave module or for allocation of physical position to channel of slave module in decentralized, event-controlled bus system with serial data communication, involves selecting start-up mode
US8902904B2 (en) 2007-09-07 2014-12-02 Trapeze Networks, Inc. Network assignment based on priority
DE102007043795A1 (en) * 2007-09-13 2009-04-02 Siemens Ag Control system for a technical system and method for operating a process control system
US8412922B2 (en) * 2007-10-24 2013-04-02 Sercomm Corporation On-site configuration of a hardware device module of a security system
US9154379B2 (en) * 2007-10-25 2015-10-06 Sercomm Corporation Remote configuration of a hardware device module of a security system
US8238942B2 (en) 2007-11-21 2012-08-07 Trapeze Networks, Inc. Wireless station location detection
DE102008010864A1 (en) * 2008-02-25 2009-08-27 Endress + Hauser Process Solutions Ag Method for operating a field device
JP5092800B2 (en) * 2008-03-03 2012-12-05 横河電機株式会社 Field device management device
US8150357B2 (en) 2008-03-28 2012-04-03 Trapeze Networks, Inc. Smoothing filter for irregular update intervals
EP2110725B1 (en) * 2008-04-18 2012-10-31 Siemens Aktiengesellschaft System and method for allocating a device name
JP5030852B2 (en) * 2008-04-26 2012-09-19 三菱電機株式会社 Device management apparatus, device management method, and program
US8635313B2 (en) * 2008-06-19 2014-01-21 Microsoft Corporation Network device installation
CN104407518B (en) 2008-06-20 2017-05-31 因文西斯系统公司 The system and method interacted to the reality and Simulation Facility for process control
US8978105B2 (en) 2008-07-25 2015-03-10 Trapeze Networks, Inc. Affirming network relationships and resource access via related networks
US8238298B2 (en) 2008-08-29 2012-08-07 Trapeze Networks, Inc. Picking an optimal channel for an access point in a wireless network
US8825462B2 (en) * 2008-09-17 2014-09-02 Accenture Global Services Limited Method and system for simulating a plurality of devices
US8229575B2 (en) 2008-09-19 2012-07-24 Rockwell Automation Technologies, Inc. Automatically adjustable industrial control configuration
US8255497B2 (en) * 2008-11-03 2012-08-28 Lincoln Global, Inc. Method of discovery and communication with industrial equipment
ATE513388T1 (en) * 2008-11-12 2011-07-15 Grieshaber Vega Kg GENERATE A DEVICE DESCRIPTION FOR A MEASURING DEVICE
JP5544372B2 (en) * 2008-12-09 2014-07-09 コーニンクレッカ フィリップス エヌ ヴェ System and method for automatically incorporating devices into a networked system
US20100175012A1 (en) * 2009-01-06 2010-07-08 Allstrom Peter E System and Method for Remote Monitoring and Control of Field Device
US8881039B2 (en) 2009-03-13 2014-11-04 Fisher-Rosemount Systems, Inc. Scaling composite shapes for a graphical human-machine interface
US8463964B2 (en) 2009-05-29 2013-06-11 Invensys Systems, Inc. Methods and apparatus for control configuration with enhanced change-tracking
US8127060B2 (en) 2009-05-29 2012-02-28 Invensys Systems, Inc Methods and apparatus for control configuration with control objects that are fieldbus protocol-aware
US8311778B2 (en) * 2009-09-22 2012-11-13 Rosemount Inc. Industrial process control transmitter with multiple sensors
US9134720B2 (en) 2010-02-12 2015-09-15 Rockwell Automation Technologies, Inc. Macro function block for encapsulating device-level embedded logic
CN102193536A (en) * 2010-02-12 2011-09-21 洛克威尔自动控制技术股份有限公司 Marco functional block for packaging device-level embedded logic
US8825183B2 (en) 2010-03-22 2014-09-02 Fisher-Rosemount Systems, Inc. Methods for a data driven interface based on relationships between process control tags
US9392072B2 (en) 2010-04-15 2016-07-12 Rockwell Automation Technologies, Inc. Systems and methods for conducting communications among components of multidomain industrial automation system
US8984533B2 (en) 2010-04-15 2015-03-17 Rockwell Automation Technologies, Inc. Systems and methods for conducting communications among components of multidomain industrial automation system
US8484401B2 (en) 2010-04-15 2013-07-09 Rockwell Automation Technologies, Inc. Systems and methods for conducting communications among components of multidomain industrial automation system
US8352641B2 (en) 2010-04-21 2013-01-08 General Electric Company Systems and methods for identifying fieldbus devices in a control system
US20110265072A1 (en) * 2010-04-27 2011-10-27 Jack Matthew Dynamic Installation of Files for Running Programs
GB201015756D0 (en) 2010-09-21 2010-10-27 Airbus Operations Gmbh Remote data concentrator
JP5044007B2 (en) * 2010-12-02 2012-10-10 キヤノン株式会社 Information processing apparatus, control method for information processing apparatus, and program
JP5639909B2 (en) * 2011-01-27 2014-12-10 アズビル株式会社 Drawing editor and drawing method
DE102011004802A1 (en) 2011-02-25 2012-08-30 Interroll-Holding Ag Method for setting up a conveying device
KR20120109665A (en) * 2011-03-23 2012-10-08 삼성전자주식회사 Method, apparatus and system for information push service based on wirless lan access point
EP2681631A1 (en) * 2011-05-19 2014-01-08 Siemens Aktiengesellschaft Process visualisation in an automation system
US9772617B2 (en) * 2011-06-30 2017-09-26 General Electric Company Systems and methods for function block instantiation
US8543748B2 (en) * 2011-09-09 2013-09-24 General Electric Company Fieldbus device control system
US8983636B1 (en) * 2011-10-28 2015-03-17 Englobal Corporation Client configuration tool
US8856415B2 (en) * 2012-02-01 2014-10-07 National Instruments Corporation Bus arbitration for a real-time computer system
DE102012102187C5 (en) * 2012-03-15 2016-11-03 Phoenix Contact Gmbh & Co. Kg Control device for controlling safety-critical processes in an automated system and method for parameterizing the control device
US8745281B2 (en) * 2012-04-23 2014-06-03 General Electric Company Automatic foundation fieldbus device commissioning
CN103558809B (en) * 2012-05-09 2019-06-18 布里斯托尔D/B/A远程自动化解决方案公司 The method and apparatus of configuration process control equipment
US20140025186A1 (en) * 2012-07-19 2014-01-23 General Electric Company Systems and methods for device commissioning and decommissioning
US9052708B2 (en) 2012-09-05 2015-06-09 General Electric Company Systems and methods for improved device commissioning and decommissioning
JP6121706B2 (en) * 2012-12-13 2017-04-26 アズビル株式会社 Programming method and apparatus
CN103092107A (en) * 2012-12-26 2013-05-08 华东师范大学 Portable digital experimental monitor terminal system
CN103064751B (en) * 2012-12-27 2015-11-04 中航(苏州)雷达与电子技术有限公司 A kind of method eliminating the interference of avionic device RS232 serial ports
JP6263836B2 (en) * 2013-01-15 2018-01-24 オムロン株式会社 Control apparatus and control method
JP6167532B2 (en) * 2013-01-25 2017-07-26 オムロン株式会社 Control device and operation method of control device
KR102160250B1 (en) * 2013-02-06 2020-09-25 삼성전자주식회사 System and method for providing object for using service
US9860135B2 (en) 2013-03-14 2018-01-02 Invensys Systems, Inc. Bulk device preparation
US9244453B2 (en) * 2013-06-05 2016-01-26 General Electric Company Dynamic wizard execution
US9563188B2 (en) * 2013-08-01 2017-02-07 General Electric Company Systems and methods for batch device commissioning and decommissioning
US9734470B2 (en) * 2013-11-14 2017-08-15 Honeywell International Inc. Apparatus and method for providing customized viewing and control of field devices through custom groups and actions in a process control system
JP6394013B2 (en) 2014-03-14 2018-09-26 オムロン株式会社 Work process management system, individual controller used therefor, and access restriction method
US11231840B1 (en) * 2014-10-05 2022-01-25 Splunk Inc. Statistics chart row mode drill down
US10303344B2 (en) 2014-10-05 2019-05-28 Splunk Inc. Field value search drill down
CN104614997B (en) * 2014-12-12 2017-12-29 联想(北京)有限公司 Control method, control device and electronic equipment
JP6461207B2 (en) * 2015-02-13 2019-01-30 株式会社Fuji Component mounting line management system and management method
CN105004922A (en) * 2015-07-08 2015-10-28 中国电子科技集团公司第四十一研究所 Application system of frequency spectrum analyzer
RU2690222C1 (en) * 2015-09-21 2019-05-31 Сименс Акциенгезелльшафт Processing step resolution for processing object
US10250437B2 (en) * 2015-10-29 2019-04-02 Arista Networks, Inc. Method and system for configuring network devices
CN105511434B (en) * 2015-12-16 2017-12-29 浙江中烟工业有限责任公司 A kind of production platform monitoring system with warning function
US10401836B2 (en) * 2016-03-21 2019-09-03 Fisher-Rosemount Systems, Inc. Methods and apparatus to setup single-use equipment/processes
US10387392B2 (en) * 2016-05-17 2019-08-20 Rockwell Automation Technologies, Inc. Method to automate historian configuration using controller based tag meta attribute
US10878140B2 (en) 2016-07-27 2020-12-29 Emerson Process Management Power & Water Solutions, Inc. Plant builder system with integrated simulation and control system configuration
JP6623996B2 (en) * 2016-09-26 2019-12-25 横河電機株式会社 Processing device, network device, control method for processing device, control method for network device, control program for processing device, control program for network device, and recording medium
CN106528082A (en) * 2016-09-27 2017-03-22 北京广利核系统工程有限公司 FPGA (Field Programmable Gate Array)-based graphical configuration method and device
GB2601080B (en) 2016-10-24 2022-10-19 Fisher Rosemount Systems Inc Systems and methods for merging modular control systems into a process plant
CN110612488A (en) 2017-05-03 2019-12-24 西门子股份公司 Process map within a controller to enable real world object visibility and accessibility
WO2019021339A1 (en) 2017-07-24 2019-01-31 三菱電機株式会社 Display and display method
JP7398189B2 (en) * 2017-09-13 2023-12-14 フィッシャー-ローズマウント システムズ,インコーポレイテッド Methods, computing devices and systems
GB2568379B (en) * 2017-10-02 2023-04-19 Fisher Rosemount Systems Inc Technology for assessing and presenting field device commissioning information associated with a process plant
RU180923U1 (en) * 2017-11-24 2018-06-29 Акционерное Общество "Приборный Завод "Тензор" (Ао "Тензор") DISCRETE SIGNAL INPUT MODULE
RU193222U1 (en) * 2017-11-24 2019-10-17 Акционерное Общество "Приборный Завод "Тензор" (Ао "Тензор") MODULE OF CONTROL AND MANAGEMENT OF TECHNOLOGICAL PROCESSES
RU180915U1 (en) * 2017-12-14 2018-06-29 Акционерное Общество "Приборный Завод "Тензор" (Ао "Тензор") CPU MODULE
EP3767922B1 (en) * 2019-07-17 2023-11-08 ABB Schweiz AG Method of channel mapping in an industrial process control system
CN114286969B (en) * 2019-09-10 2023-07-28 株式会社富士 Production line production equipment
US11159203B2 (en) 2019-09-13 2021-10-26 Micro Motion, Inc. Process control loop bridge
CN113031526A (en) * 2019-12-24 2021-06-25 沈阳智能机器人创新中心有限公司 Method for realizing distributed multi-axis motion control system based on 4diac
WO2021202145A1 (en) * 2020-04-01 2021-10-07 Honeywell International Inc. Optimal method of processing batch manufacturing events with linear computational complexity
US11875236B2 (en) * 2020-10-22 2024-01-16 Fisher-Rosemount Systems, Inc. Industrial process control system as a data center of an industrial process plant
CN112505246B (en) * 2020-11-11 2023-05-02 山西科致成科技有限公司 Digital mining gas sensor calibration and verification device and method
US11418969B2 (en) 2021-01-15 2022-08-16 Fisher-Rosemount Systems, Inc. Suggestive device connectivity planning
CN114167825A (en) * 2021-11-22 2022-03-11 成都飞机工业(集团)有限责任公司 Control chart obtaining method and device of product, terminal equipment and storage medium
EP4312418A1 (en) * 2022-07-29 2024-01-31 Abb Schweiz Ag Method for automatic selection of servers
US11899410B1 (en) 2022-12-15 2024-02-13 Halliburton Energy Services, Inc. Monitoring a wellbore operation using distributed artificial intelligence
US11899438B1 (en) 2022-12-15 2024-02-13 Halliburton Energy Services, Inc. Distributed control system with failover capabilities for physical well equipment

Citations (49)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE522590C (en) 1931-04-18 Arthur Korn Dr Device for generating high-frequency currents for medical purposes
US4302820A (en) 1979-08-20 1981-11-24 Allen-Bradley Company Dual language programmable controller
US4663704A (en) 1984-12-03 1987-05-05 Westinghouse Electric Corp. Universal process control device and method for developing a process control loop program
US4672530A (en) 1984-12-17 1987-06-09 Combustion Engineering, Inc. Distributed control with universal program
US4689786A (en) 1985-03-21 1987-08-25 Apple Computer, Inc. Local area network with self assigned address method
GB2208553A (en) 1987-08-12 1989-04-05 Renishaw Plc Communications adaptor for automated factory system
US4916610A (en) 1988-10-05 1990-04-10 Racal Data Communications Inc. Multilanguage software integration through preprocessing
US5006992A (en) 1987-09-30 1991-04-09 Du Pont De Nemours And Company Process control system with reconfigurable expert rules and control modules
US5063523A (en) 1989-11-16 1991-11-05 Racal Data Communications Inc. Network management system with event rule handling
US5129087A (en) 1988-02-03 1992-07-07 International Business Machines, Corp. Computer system and a method of monitoring transient data structures in a computer system
US5134574A (en) 1990-02-27 1992-07-28 The Foxboro Company Performance control apparatus and method in a processing plant
US5155842A (en) 1989-08-14 1992-10-13 Microsoft Corporation Logical event notification method and apparatus
US5307346A (en) 1990-03-24 1994-04-26 Reflex Manufacturing Systems Limited Network-field interface for manufacturing systems
US5311562A (en) 1992-12-01 1994-05-10 Westinghouse Electric Corp. Plant maintenance with predictive diagnostics
US5371895A (en) 1985-10-08 1994-12-06 The Foxboro Company Local equipment controller for computerized process control applications utilizing language structure templates in a hierarchical organization and method of operating the same
WO1995004314A1 (en) 1993-07-29 1995-02-09 Fisher-Rosemount Systems, Inc. Uniform control template generating system and method for process control programming
US5432711A (en) 1992-10-16 1995-07-11 Elcon Instruments, Inc. Interface for use with a process instrumentation system
US5442639A (en) 1993-10-12 1995-08-15 Ship Star Associates, Inc. Method and apparatus for monitoring a communications network
US5444851A (en) 1990-01-30 1995-08-22 Johnson Service Company Method of accessing configured nodes in a facilities management system with a non-configured device
US5471461A (en) 1993-04-28 1995-11-28 Allen-Bradley Company, Inc. Digital communication network with a moderator station election process
US5471190A (en) 1989-07-20 1995-11-28 Timothy D. Schoechle Method and apparatus for resource allocation in a communication network system
US5475856A (en) 1991-11-27 1995-12-12 International Business Machines Corporation Dynamic multi-mode parallel processing array
US5481741A (en) 1986-04-14 1996-01-02 National Instruments Corporation Method and apparatus for providing attribute nodes in a graphical data flow environment
US5485620A (en) 1994-02-25 1996-01-16 Automation System And Products, Inc. Integrated control system for industrial automation applications
US5491791A (en) 1995-01-13 1996-02-13 International Business Machines Corporation System and method for remote workstation monitoring within a distributed computing environment
US5493534A (en) 1993-07-29 1996-02-20 Atmel Corporation Remotely re-programmable program memory for a microcontroller
US5504902A (en) 1993-12-01 1996-04-02 Patriot Sensors And Controls Corporation Multi-language generation of control program for an industrial controller
US5513095A (en) 1989-08-16 1996-04-30 Siemens Aktiengesellschaft Flexible automation system for variable industrial processes
US5519706A (en) 1993-12-03 1996-05-21 International Business Machines Corporation Dynamic user registration method in a mobile communications network
US5519878A (en) 1992-03-18 1996-05-21 Echelon Corporation System for installing and configuring (grouping and node address assignment) household devices in an automated environment
US5524269A (en) 1991-04-30 1996-06-04 Hewlett-Packard Company System for activating and configuring an input/output board in a computer
US5526489A (en) 1993-03-19 1996-06-11 3Com Corporation System for reverse address resolution for remote network device independent of its physical address
US5530643A (en) 1993-08-24 1996-06-25 Allen-Bradley Company, Inc. Method of programming industrial controllers with highly distributed processing
US5549137A (en) 1993-08-25 1996-08-27 Rosemount Inc. Valve positioner with pressure feedback, dynamic correction and diagnostics
US5566320A (en) 1992-07-04 1996-10-15 Klockner-Moeller Gmbh Memory storage access control circuit for coupled mask-programmed microcontrollers
US5566346A (en) 1993-12-21 1996-10-15 Taligent, Inc. System for constructing hardware device interface software systems independent of operating systems including capability of installing and removing interrupt handlers
US5576946A (en) 1993-09-30 1996-11-19 Fluid Air, Inc. Icon based process design and control system
US5596723A (en) 1994-06-23 1997-01-21 Dell Usa, Lp Method and apparatus for automatically detecting the available network services in a network system
US5623592A (en) 1994-10-18 1997-04-22 Molecular Dynamics Method and apparatus for constructing an iconic sequence to operate external devices
US5675748A (en) * 1993-12-21 1997-10-07 Object Technology Licensing Corp. Method and apparatus for automatically configuring computer system hardware and software
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
US5694335A (en) 1996-03-12 1997-12-02 Hollenberg; Dennis D. Secure personal applications network
US5701411A (en) 1994-11-04 1997-12-23 Canon Information Systems, Inc. Automatic detection of network hardware connection
US5706007A (en) 1995-01-03 1998-01-06 Smar Research Corporation Analog current / digital bus protocol converter circuit
US5768119A (en) * 1996-04-12 1998-06-16 Fisher-Rosemount Systems, Inc. Process control system including alarm priority adjustment
US5801942A (en) * 1996-04-12 1998-09-01 Fisher-Rosemount Systems, Inc. Process control system user interface including selection of multiple control languages
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
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
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

Family Cites Families (63)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0618002B2 (en) * 1985-01-28 1994-03-09 株式会社東芝 Distributed hierarchical computer system
US4679137A (en) * 1985-04-30 1987-07-07 Prometrix Corporation Process control interface system for designer and operator
US5021997A (en) * 1986-09-29 1991-06-04 At&T Bell Laboratories Test automation system
JP2544927B2 (en) * 1987-05-29 1996-10-16 三菱電機株式会社 Plant operation support system
JPH0727056B2 (en) * 1987-07-21 1995-03-29 株式会社日立製作所 Instrumentation control system maintenance support system for nuclear power plants
JPS6464011A (en) * 1987-09-03 1989-03-09 Mitsubishi Electric Corp Programmable controller
JPH01211103A (en) * 1988-02-19 1989-08-24 Okuma Mach Works Ltd Numerical controller for grinder
JPH07113845B2 (en) * 1988-06-09 1995-12-06 富士電機株式会社 System construction method for programmable controller
JP2607663B2 (en) * 1989-01-31 1997-05-07 株式会社東芝 Dialogue equipment for plant monitoring
JP2651245B2 (en) * 1989-06-30 1997-09-10 株式会社日立製作所 Production progress control device and semiconductor device manufacturing method
JPH0373257A (en) * 1989-08-11 1991-03-28 Nec Corp Production scheduling device
JP2566024B2 (en) * 1990-01-11 1996-12-25 株式会社東芝 Equipment information management device
US5251125A (en) * 1990-04-30 1993-10-05 Eaton Corporation User interface for a process control device
US5168441A (en) * 1990-05-30 1992-12-01 Allen-Bradley Company, Inc. Methods for set up and programming of machine and process controllers
US5293466A (en) * 1990-08-03 1994-03-08 Qms, Inc. Method and apparatus for selecting interpreter for printer command language based upon sample of print job transmitted to printer
JPH04137164A (en) * 1990-09-28 1992-05-12 Yokogawa Electric Corp Engineering device
JPH04222026A (en) * 1990-12-21 1992-08-12 Nec Corp Program controller
JPH04223849A (en) * 1990-12-21 1992-08-13 Yamatake Honeywell Co Ltd Multikind and small quantity production system
JP2631423B2 (en) * 1991-03-18 1997-07-16 三菱電機株式会社 Operation monitoring device
JP2658633B2 (en) * 1991-07-10 1997-09-30 三菱電機株式会社 Communication device
JP3174863B2 (en) * 1991-07-15 2001-06-11 株式会社ニコン Exposure method and lithography system
JPH0575465A (en) * 1991-09-12 1993-03-26 Hitachi Ltd A/d converter for field equipment
JPH05165858A (en) * 1991-12-12 1993-07-02 Matsushita Electric Ind Co Ltd Hospital communication equipment
JPH05216511A (en) * 1992-02-04 1993-08-27 Yaskawa Electric Corp Data processor
JPH05313774A (en) * 1992-05-12 1993-11-26 Ricoh Co Ltd Guidance display device
JPH0612250A (en) * 1992-06-25 1994-01-21 Mitsubishi Electric Corp Visual programming method
US5647056A (en) * 1992-11-18 1997-07-08 Canon Information Systems, Inc. Method and apparatus for managing access to a networked peripheral
JPH076939A (en) * 1992-12-02 1995-01-10 Hitachi Ltd Production control system
JPH06249678A (en) * 1993-02-26 1994-09-09 Bridgestone Corp Method and device for monitoring production process
JPH06295236A (en) * 1993-04-07 1994-10-21 Yokogawa Electric Corp Engineering device
JPH0713766A (en) * 1993-06-14 1995-01-17 Internatl Business Mach Corp <Ibm> Object-oriented computer system and object class management method
JP3309932B2 (en) * 1993-07-08 2002-07-29 理化工業株式会社 Control device
JPH0756606A (en) * 1993-08-19 1995-03-03 Fujitsu Ltd Construction support device for measurement monitoring controller
JPH0792900A (en) * 1993-09-20 1995-04-07 Omron Corp Programmable controller
JP3367675B2 (en) * 1993-12-16 2003-01-14 オープン マーケット インコーポレイテッド Open network sales system and method for real-time approval of transaction transactions
JPH07210394A (en) * 1994-01-20 1995-08-11 Hitachi Ltd Program management method for distributed system
JPH07281713A (en) * 1994-04-06 1995-10-27 Hitachi Eng Co Ltd Process control system
JPH0816213A (en) * 1994-06-28 1996-01-19 Mitsubishi Electric Corp Plant controller
EP0770239B1 (en) * 1994-07-13 1998-10-21 Unisys Corporation A generalized configurator
US5546301A (en) * 1994-07-19 1996-08-13 Honeywell Inc. Advanced equipment control system
JP3503291B2 (en) * 1994-09-06 2004-03-02 富士ゼロックス株式会社 Output device, network system and terminal name changing method
JPH0887460A (en) * 1994-09-19 1996-04-02 Seiko Epson Corp Installation system
US5718767A (en) * 1994-10-05 1998-02-17 Nordson Corporation Distributed control system for powder coating system
JPH10508131A (en) * 1994-10-28 1998-08-04 アドバンスド・ヘルス・メド・イー・システムズ コーポレーション Prescription management system
US5572438A (en) * 1995-01-05 1996-11-05 Teco Energy Management Services Engery management and building automation system
WO1996021978A1 (en) * 1995-01-11 1996-07-18 Momentum Microsystems Wireless desktop area network system
JPH08220278A (en) * 1995-02-10 1996-08-30 Toshiba Eng Co Ltd Plant monitor device and monitor method
GB9502819D0 (en) * 1995-02-14 1995-04-05 At & T Global Inf Solution Control systems
JPH08249026A (en) * 1995-03-10 1996-09-27 Fanuc Ltd Programming method for system including robot
US5617522A (en) * 1995-04-03 1997-04-01 Honeywell Inc. Methods and apparatus for providing and/or customizing display screens and operator interfaces for process control and measurement instruments
JPH08278881A (en) * 1995-04-06 1996-10-22 Toshiba Syst Technol Kk Supporting device for building interactive processing system
JPH08286730A (en) * 1995-04-07 1996-11-01 Toshiba Corp Distributed plant monitor and control device
JP3299860B2 (en) * 1995-05-30 2002-07-08 三菱電機株式会社 Rolling mill thickness control method
JPH08331150A (en) * 1995-06-05 1996-12-13 Fujitsu Ltd Communication system and method therefor
US5745886A (en) * 1995-06-07 1998-04-28 Citibank, N.A. Trusted agents for open distribution of electronic money
US5781710A (en) * 1995-06-07 1998-07-14 Xerox Corporation Generic method for scheduling print engines using print engine capabilities
JP3971465B2 (en) * 1995-06-08 2007-09-05 ソニー株式会社 Camera setup method and system
JPH0934508A (en) * 1995-07-24 1997-02-07 Hitachi Ltd Work information input method and means therefor, and work plan preparation means
JPH1063312A (en) * 1996-08-23 1998-03-06 Toshiba Corp Program managing device for controlling plant
US5980078A (en) * 1997-02-14 1999-11-09 Fisher-Rosemount Systems, Inc. Process control system including automatic sensing and automatic configuration of devices
US6285932B1 (en) * 1997-05-16 2001-09-04 Snap-On Technologies, Inc. Computerized automotive service system
US6006171A (en) * 1997-07-28 1999-12-21 Vines; Caroline J. Dynamic maintenance management system
FR2770017B1 (en) * 1997-10-17 1999-12-03 Thomson Multimedia Sa DOMESTIC EQUIPMENT CONTROL SYSTEM BY GRAPHIC DISPLAY ON SCREEN

Patent Citations (50)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE522590C (en) 1931-04-18 Arthur Korn Dr Device for generating high-frequency currents for medical purposes
US4302820A (en) 1979-08-20 1981-11-24 Allen-Bradley Company Dual language programmable controller
US4663704A (en) 1984-12-03 1987-05-05 Westinghouse Electric Corp. Universal process control device and method for developing a process control loop program
US4672530A (en) 1984-12-17 1987-06-09 Combustion Engineering, Inc. Distributed control with universal program
US4689786A (en) 1985-03-21 1987-08-25 Apple Computer, Inc. Local area network with self assigned address method
US5371895A (en) 1985-10-08 1994-12-06 The Foxboro Company Local equipment controller for computerized process control applications utilizing language structure templates in a hierarchical organization and method of operating the same
US5481741A (en) 1986-04-14 1996-01-02 National Instruments Corporation Method and apparatus for providing attribute nodes in a graphical data flow environment
GB2208553A (en) 1987-08-12 1989-04-05 Renishaw Plc Communications adaptor for automated factory system
US5006992A (en) 1987-09-30 1991-04-09 Du Pont De Nemours And Company Process control system with reconfigurable expert rules and control modules
US5129087A (en) 1988-02-03 1992-07-07 International Business Machines, Corp. Computer system and a method of monitoring transient data structures in a computer system
US4916610A (en) 1988-10-05 1990-04-10 Racal Data Communications Inc. Multilanguage software integration through preprocessing
US5471190A (en) 1989-07-20 1995-11-28 Timothy D. Schoechle Method and apparatus for resource allocation in a communication network system
US5155842A (en) 1989-08-14 1992-10-13 Microsoft Corporation Logical event notification method and apparatus
US5513095A (en) 1989-08-16 1996-04-30 Siemens Aktiengesellschaft Flexible automation system for variable industrial processes
US5063523A (en) 1989-11-16 1991-11-05 Racal Data Communications Inc. Network management system with event rule handling
US5444851A (en) 1990-01-30 1995-08-22 Johnson Service Company Method of accessing configured nodes in a facilities management system with a non-configured device
US5550980A (en) 1990-01-30 1996-08-27 Johnson Service Company Networked facilities management system with optical coupling of local network devices
US5134574A (en) 1990-02-27 1992-07-28 The Foxboro Company Performance control apparatus and method in a processing plant
US5307346A (en) 1990-03-24 1994-04-26 Reflex Manufacturing Systems Limited Network-field interface for manufacturing systems
US5524269A (en) 1991-04-30 1996-06-04 Hewlett-Packard Company System for activating and configuring an input/output board in a computer
US5475856A (en) 1991-11-27 1995-12-12 International Business Machines Corporation Dynamic multi-mode parallel processing array
US5519878A (en) 1992-03-18 1996-05-21 Echelon Corporation System for installing and configuring (grouping and node address assignment) household devices in an automated environment
US5566320A (en) 1992-07-04 1996-10-15 Klockner-Moeller Gmbh Memory storage access control circuit for coupled mask-programmed microcontrollers
US5432711A (en) 1992-10-16 1995-07-11 Elcon Instruments, Inc. Interface for use with a process instrumentation system
US5311562A (en) 1992-12-01 1994-05-10 Westinghouse Electric Corp. Plant maintenance with predictive diagnostics
US5526489A (en) 1993-03-19 1996-06-11 3Com Corporation System for reverse address resolution for remote network device independent of its physical address
US5471461A (en) 1993-04-28 1995-11-28 Allen-Bradley Company, Inc. Digital communication network with a moderator station election process
US5493534A (en) 1993-07-29 1996-02-20 Atmel Corporation Remotely re-programmable program memory for a microcontroller
WO1995004314A1 (en) 1993-07-29 1995-02-09 Fisher-Rosemount Systems, Inc. Uniform control template generating system and method for process control programming
US5530643A (en) 1993-08-24 1996-06-25 Allen-Bradley Company, Inc. Method of programming industrial controllers with highly distributed processing
US5549137A (en) 1993-08-25 1996-08-27 Rosemount Inc. Valve positioner with pressure feedback, dynamic correction and diagnostics
US5576946A (en) 1993-09-30 1996-11-19 Fluid Air, Inc. Icon based process design and control system
US5442639A (en) 1993-10-12 1995-08-15 Ship Star Associates, Inc. Method and apparatus for monitoring a communications network
US5504902A (en) 1993-12-01 1996-04-02 Patriot Sensors And Controls Corporation Multi-language generation of control program for an industrial controller
US5519706A (en) 1993-12-03 1996-05-21 International Business Machines Corporation Dynamic user registration method in a mobile communications network
US5675748A (en) * 1993-12-21 1997-10-07 Object Technology Licensing Corp. Method and apparatus for automatically configuring computer system hardware and software
US5566346A (en) 1993-12-21 1996-10-15 Taligent, Inc. System for constructing hardware device interface software systems independent of operating systems including capability of installing and removing interrupt handlers
US5485620A (en) 1994-02-25 1996-01-16 Automation System And Products, Inc. Integrated control system for industrial automation applications
US5596723A (en) 1994-06-23 1997-01-21 Dell Usa, Lp Method and apparatus for automatically detecting the available network services in a network system
US5623592A (en) 1994-10-18 1997-04-22 Molecular Dynamics Method and apparatus for constructing an iconic sequence to operate external devices
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
US5701411A (en) 1994-11-04 1997-12-23 Canon Information Systems, Inc. Automatic detection of network hardware connection
US5706007A (en) 1995-01-03 1998-01-06 Smar Research Corporation Analog current / digital bus protocol converter circuit
US5491791A (en) 1995-01-13 1996-02-13 International Business Machines Corporation System and method for remote workstation monitoring within a distributed computing environment
US5694335A (en) 1996-03-12 1997-12-02 Hollenberg; Dennis D. Secure personal applications network
US5768119A (en) * 1996-04-12 1998-06-16 Fisher-Rosemount Systems, Inc. Process control system including alarm priority adjustment
US5801942A (en) * 1996-04-12 1998-09-01 Fisher-Rosemount Systems, Inc. Process control system user interface including selection of multiple control languages
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
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
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

Non-Patent Citations (13)

* Cited by examiner, † Cited by third party
Title
Baldasserini, Denmac delivers LAN stats (Denmac Systems Inc's TrenData 2.0), Computer Shopper, v15, n6, p.613(1), Jun. 1995.
Blackwell, The benefits won't kick-in immediately (Microsoft Windows 95 operating system's multimedia benefits), Computing Canada, v21, n18, p. 36(2), Sep. 1995.
C. K. Duffer et al., "High-Level Control Language Customized Application Programs", Power Technologies, Inc., IEEE Computer Applications in Power, (C) Apr. 1991, pp. 15-18.
Clifford J. Peshek et al., "Recent Developments and Future Trends in PLC Programming Languages and Programming Tools for Real-Time Control", IEEE Cement Industry Technical Conference, May 1993, Toronto, Canada, pp. 219-230.
Foundation Fieldbus, FF-001, Communications Technical Specifications, (C) 1994-1996.
Foundation Fieldbus, FF-002, Communications Technical Specifications, (C) 1994-1996.
H.J. Beestermoller et al., "An online programmable Multiple-Loop Controller for Distributed Systems", (C) 1994 IEEE, pp. 15-20.
John R. Gyorki, "PLC's drive standard buses", Machine Designs, May 11, 1995, pp. 83-90.
Moore Products Co., "apacs Control System", Power Jun. 1995, p. 81, vol. 139, No. 6, Copyright 1995,McGraw-Hill, Inc.
Moore Products Co., "Control System", Power Apr. 1995, +-p. 11 4, vol. 139, No. 4, Copyright 1995, McGraw-Hill, Inc.
PCT/US98/01573 International Search Report, dated Nov. 25, 1998.
Robert R. Lyons, "New Telemecanique Programmable Controllers Feature Multiple Programming Languages", Telemacanique, Arlington Heights, IL, Feb. 11, 1995.
S.N. Chau, et al., "A Multi-Mission Space Avionics Architecture," Proc. 1996 IEEE Aerospace Applications Conference, vol. 1, pp. 165-176, Feb. 1996.

Cited By (57)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7757209B2 (en) * 2003-03-14 2010-07-13 Omron Corporation Display and edit device, display method and program product
US20040220684A1 (en) * 2003-03-14 2004-11-04 Shinji Fukui Display and edit device, display method and program product
US20050267964A1 (en) * 2004-04-28 2005-12-01 Guenter Kech Method for providing apparatus specific information and corresponding system
US8132240B2 (en) * 2005-09-29 2012-03-06 Siemens Aktiengesellschaft Electric field unit and method for executing a protected function of an electric field unit
US20080282332A1 (en) * 2005-09-29 2008-11-13 Siemens Aktiengesellschaft Method For Executing a Protected Function of an Electric Field Unit and Electrical Field Unit
US20100004758A1 (en) * 2006-07-13 2010-01-07 Mitsubishi Electric Corporation Equipment management system, programmable controller and centralized controller
US8311650B2 (en) * 2006-07-13 2012-11-13 Mitsubishi Electric Corporation Equipment management system, programmable controller and centralized controller
US20090093894A1 (en) * 2007-10-04 2009-04-09 Samsung Electronics Co., Ltd. Production management system and method of controlling the same
US20100049841A1 (en) * 2007-11-14 2010-02-25 Huawei Technologies Co., Ltd. Method and system for automatically commissioning network device
US8788609B2 (en) * 2009-05-08 2014-07-22 Siemens Ag Automation device and automation system
US20100287255A1 (en) * 2009-05-08 2010-11-11 Siemens Ag Automation Device and Automation System
US20110004589A1 (en) * 2009-07-06 2011-01-06 Rockwell Automation Technologies, Inc. Diagnostics in a distributed directory system
US9323241B2 (en) 2010-03-01 2016-04-26 Rittal Gmbh & Co. Kg Control cabinet monitoring device
US8745278B2 (en) 2010-10-13 2014-06-03 Rosemount Inc. Field device with self description
US9558220B2 (en) 2013-03-04 2017-01-31 Fisher-Rosemount Systems, Inc. Big data in process control systems
US11385608B2 (en) 2013-03-04 2022-07-12 Fisher-Rosemount Systems, Inc. Big data in process control systems
US10866952B2 (en) 2013-03-04 2020-12-15 Fisher-Rosemount Systems, Inc. Source-independent queries in distributed industrial system
US10678225B2 (en) 2013-03-04 2020-06-09 Fisher-Rosemount Systems, Inc. Data analytic services for distributed industrial performance monitoring
US10649424B2 (en) 2013-03-04 2020-05-12 Fisher-Rosemount Systems, Inc. Distributed industrial performance monitoring and analytics
US10649449B2 (en) 2013-03-04 2020-05-12 Fisher-Rosemount Systems, Inc. Distributed industrial performance monitoring and analytics
US10386827B2 (en) 2013-03-04 2019-08-20 Fisher-Rosemount Systems, Inc. Distributed industrial performance monitoring and analytics platform
US10037303B2 (en) 2013-03-14 2018-07-31 Fisher-Rosemount Systems, Inc. Collecting and delivering data to a big data machine in a process control system
US9697170B2 (en) 2013-03-14 2017-07-04 Fisher-Rosemount Systems, Inc. Collecting and delivering data to a big data machine in a process control system
US10311015B2 (en) 2013-03-14 2019-06-04 Fisher-Rosemount Systems, Inc. Distributed big data in a process control system
US10223327B2 (en) 2013-03-14 2019-03-05 Fisher-Rosemount Systems, Inc. Collecting and delivering data to a big data machine in a process control system
US9541905B2 (en) 2013-03-15 2017-01-10 Fisher-Rosemount Systems, Inc. Context sensitive mobile control in a process plant
US10649413B2 (en) 2013-03-15 2020-05-12 Fisher-Rosemount Systems, Inc. Method for initiating or resuming a mobile control session in a process plant
US10031489B2 (en) 2013-03-15 2018-07-24 Fisher-Rosemount Systems, Inc. Method and apparatus for seamless state transfer between user interface devices in a mobile control room
US10133243B2 (en) 2013-03-15 2018-11-20 Fisher-Rosemount Systems, Inc. Method and apparatus for seamless state transfer between user interface devices in a mobile control room
US10152031B2 (en) 2013-03-15 2018-12-11 Fisher-Rosemount Systems, Inc. Generating checklists in a process control environment
US11573672B2 (en) 2013-03-15 2023-02-07 Fisher-Rosemount Systems, Inc. Method for initiating or resuming a mobile control session in a process plant
US11169651B2 (en) 2013-03-15 2021-11-09 Fisher-Rosemount Systems, Inc. Method and apparatus for controlling a process plant with location aware mobile devices
US11112925B2 (en) 2013-03-15 2021-09-07 Fisher-Rosemount Systems, Inc. Supervisor engine for process control
US10296668B2 (en) 2013-03-15 2019-05-21 Fisher-Rosemount Systems, Inc. Data modeling studio
US10900482B2 (en) 2013-03-15 2021-01-26 Kaeser Kompressoren Se P and I diagram input
US10324423B2 (en) 2013-03-15 2019-06-18 Fisher-Rosemount Systems, Inc. Method and apparatus for controlling a process plant with location aware mobile control devices
US9778626B2 (en) 2013-03-15 2017-10-03 Fisher-Rosemount Systems, Inc. Mobile control room with real-time environment awareness
EP2971769B1 (en) 2013-03-15 2019-11-06 Kaeser Kompressoren SE R&i scheme input for a process for controlling and/or supervising a compressor system
US10691281B2 (en) 2013-03-15 2020-06-23 Fisher-Rosemount Systems, Inc. Method and apparatus for controlling a process plant with location aware mobile control devices
US10551799B2 (en) 2013-03-15 2020-02-04 Fisher-Rosemount Systems, Inc. Method and apparatus for determining the position of a mobile control device in a process plant
US10031490B2 (en) 2013-03-15 2018-07-24 Fisher-Rosemount Systems, Inc. Mobile analysis of physical phenomena in a process plant
US9678484B2 (en) 2013-03-15 2017-06-13 Fisher-Rosemount Systems, Inc. Method and apparatus for seamless state transfer between user interface devices in a mobile control room
US10649412B2 (en) 2013-03-15 2020-05-12 Fisher-Rosemount Systems, Inc. Method and apparatus for seamless state transfer between user interface devices in a mobile control room
US9740802B2 (en) 2013-03-15 2017-08-22 Fisher-Rosemount Systems, Inc. Data modeling studio
US10671028B2 (en) 2013-03-15 2020-06-02 Fisher-Rosemount Systems, Inc. Method and apparatus for managing a work flow in a process plant
US10656627B2 (en) 2014-01-31 2020-05-19 Fisher-Rosemount Systems, Inc. Managing big data in process control systems
US9665088B2 (en) 2014-01-31 2017-05-30 Fisher-Rosemount Systems, Inc. Managing big data in process control systems
US9804588B2 (en) 2014-03-14 2017-10-31 Fisher-Rosemount Systems, Inc. Determining associations and alignments of process elements and measurements in a process
US9772623B2 (en) 2014-08-11 2017-09-26 Fisher-Rosemount Systems, Inc. Securing devices to process control systems
US9397836B2 (en) 2014-08-11 2016-07-19 Fisher-Rosemount Systems, Inc. Securing devices to process control systems
US10909137B2 (en) 2014-10-06 2021-02-02 Fisher-Rosemount Systems, Inc. Streaming data for analytics in process control systems
US10282676B2 (en) 2014-10-06 2019-05-07 Fisher-Rosemount Systems, Inc. Automatic signal processing-based learning in a process plant
US9823626B2 (en) 2014-10-06 2017-11-21 Fisher-Rosemount Systems, Inc. Regional big data in process control systems
US10168691B2 (en) 2014-10-06 2019-01-01 Fisher-Rosemount Systems, Inc. Data pipeline for process control system analytics
US11886155B2 (en) 2015-10-09 2024-01-30 Fisher-Rosemount Systems, Inc. Distributed industrial performance monitoring and analytics
US10503483B2 (en) 2016-02-12 2019-12-10 Fisher-Rosemount Systems, Inc. Rule builder in a process control network
US11704257B1 (en) 2022-04-15 2023-07-18 Graco Minnesota Inc. System provisioning using virtual peripherals

Also Published As

Publication number Publication date
AU6252198A (en) 1998-09-08
JP5936180B2 (en) 2016-06-15
JP2001512598A (en) 2001-08-21
GB2336923B (en) 2002-06-19
GB2336446B (en) 2001-01-17
WO1998036336A1 (en) 1998-08-20
JP2009009560A (en) 2009-01-15
DE19882116T5 (en) 2004-11-18
GB9918414D0 (en) 1999-10-06
JP2001512593A (en) 2001-08-21
AU6045498A (en) 1998-09-08
JP2012084162A (en) 2012-04-26
WO1998036335A3 (en) 1999-01-14
JP4934482B2 (en) 2012-05-16
WO1998036335A2 (en) 1998-08-20
JP6194252B2 (en) 2017-09-06
GB9918413D0 (en) 1999-10-06
US5980078A (en) 1999-11-09
GB2336923A (en) 1999-11-03
WO1998036353A1 (en) 1998-08-20
DE19882117T1 (en) 2000-01-27
DE19882113T1 (en) 2000-01-27
GB2336446A (en) 1999-10-20
JP2014116027A (en) 2014-06-26
AU6045598A (en) 1998-09-08
JP2015092400A (en) 2015-05-14
JP2007226825A (en) 2007-09-06
GB9918410D0 (en) 1999-10-06
JP2001512599A (en) 2001-08-21
GB2336977B (en) 2002-06-19
GB2336977A (en) 1999-11-03

Similar Documents

Publication Publication Date Title
USRE40817E1 (en) Process control system including automatic sensing and automatic configuration of devices
US6098116A (en) Process control system including a method and apparatus for automatically sensing the connection of devices to a network
US5862052A (en) Process control system using a control strategy implemented in a layered hierarchy of control modules
US5828851A (en) Process control system using standard protocol control of standard devices and nonstandard devices
US8761196B2 (en) Flexible input/output devices for use in process control systems
US5909368A (en) Process control system using a process control strategy distributed among multiple control elements
US6032208A (en) Process control system for versatile control of multiple process devices of various device types
US7117049B2 (en) Industrial controller based on distributable technology objects
US5995916A (en) Process control system for monitoring and displaying diagnostic information of multiple distributed devices
US6868538B1 (en) Object-oriented programmable controller
US5801942A (en) Process control system user interface including selection of multiple control languages
WO1998036335A9 (en) Process control system using a layered-hierarchy control strategy distributed into multiple control devices
US6449715B1 (en) Process control configuration system for use with a profibus device network
US7640291B2 (en) Agent-equipped controller having data table interface between agent-type programming and non-agent-type programming
US6446202B1 (en) Process control configuration system for use with an AS-Interface device network
US7305272B2 (en) Controller with agent functionality
US7146232B2 (en) Agent program environment
US7117040B2 (en) Tool attachable to controller
JP2014116027A5 (en)
US20070075916A1 (en) Generic utility supporting on-demand creation of customizable graphical user interfaces for viewing and specifying field device parameters
US20050144271A1 (en) Control system apparatus, method for setting control system and setting program
US20100305720A1 (en) Methods and apparatus for control configuration with control objects that are fieldbus protocol-aware
US20070079250A1 (en) Device home page for use in a device type manager providing graphical user interfaces for viewing and specifying field device parameters
JP2012084162A5 (en)
KR20060012327A (en) Configurable plc and scada-based control system

Legal Events

Date Code Title Description
CC Certificate of correction
FPAY Fee payment

Year of fee payment: 12