JP2023159305A - Apparatus to communicatively couple field device to controller in process control system, computer-readable medium and apparatus - Google Patents

Abstract

To provide an example apparatus to communicatively couple a field device to a controller of a process control system.SOLUTION: An apparatus includes a first interface to be communicatively coupled to one of a first field device or a second field device. The first interface communicates using a first fieldbus communication protocol when coupled to the first field device, and communicates using a second fieldbus communication protocol when coupled to the second field device. The apparatus includes a second interface communicatively coupled to a communication processor and a bus to encode first information received from the one of the first field device and second field device for communication via the bus using a third communication protocol, and then transmit the first information to a controller of a process control system.SELECTED DRAWING: Figure 1A

Description

TECHNICAL FIELD This disclosure relates generally to process control systems, and more specifically to apparatus and methods for communicatively coupling field devices to controllers of process control systems.

Process control systems, such as those used in chemical, petroleum, pharmaceutical, pulp and paper, or other manufacturing processes, typically have at least one host, including at least one operator workstation, and an analog, digital, or one or more process controllers communicatively coupled to one or more field devices configured to communicate via a digitally complex communication protocol. For example, field devices that can be device controllers, valves, valve actuators, valve positioners, switches and transmitters (e.g., temperature sensors, pressure sensors, flow sensors, and chemical composition sensors), or combinations thereof, are used within a process control system. perform functions such as opening and closing valves, and measuring or estimating process parameters. A process controller receives signals indicative of process measurements made by the field device and/or other information about the field device, uses this information to implement control routines, and communicates via a bus or other communication line. Generating control signals sent to field devices to control operation of the process control system.

Process control systems offer several different capabilities and can be either point-to-point (e.g., one field device is communicatively coupled to a field device bus) or multi-drop (e.g., multiple field devices are connected to a field including a plurality of field devices, often communicatively coupled to a process controller using a two-wire interface in a hardwired configuration (communicatively coupled to a device bus) or using wireless communications; Can be done. Some field devices are configured to operate using relatively simple commands and/or communications (eg, ON and OFF commands). Other field devices are more complex and require more commands and/or more communication information, which may or may not include simple commands. For example, more complex field devices may convey analog values with digital communications superimposed on the analog values using, for example, the Highway Addressable Remote Transducer (“HART”) communication protocol. Other field devices may use completely digital communications (eg, the FOUNDATION fieldbus communication protocol).

In a process control system, each field device is typically coupled to a process controller via one or more I/O cards and a respective communication medium (e.g., a two-wire cable, wireless link, or fiber optic). There is. Accordingly, multiple communication media are required to communicatively couple multiple field devices to a process controller. Often, communication media coupled to a field device are routed through one or more field junction boxes, where the communication media connect the field device to a process controller and one or more I/Os. The multi-conductor cable is coupled to each communication medium (eg, each two-wire conductor) used for communicatively coupling via the /O card.

An example apparatus and method for communicatively coupling a field device to a controller of a process control system is described. According to one embodiment, an exemplary apparatus includes a base and a module removably attached to the base. The base has a first physical interface communicatively coupled to one of the first field device of the process control system or the second field device of the process control system and a controller of the process control system via a bus. and a second physical interface communicatively coupled to the second physical interface. The module communicates with the first field device using a first communication protocol when the first physical interface is communicatively coupled to the first field device. The module communicates with the second field device using a second communication protocol when the first physical interface is communicatively coupled to the second field device. The module communicates with the controller via a bus using a third communication protocol. The third communication protocol is different from the first and second communication protocols.

According to another embodiment, the example method includes communicatively coupling the first information to one of a first field device of a process control system or a second field device of a process control system. and receiving at a base having a first physical interface. The example method also involves encoding first information in a module removably attached to the base for communicating using a first communication protocol. First information communicated from the first field device to the module using a second communication protocol when the first physical interface is coupled to the first field device. First information communicated to the module from the second field device using a third communication protocol when the first physical interface is coupled to the second field device. The first communication protocol is separate from the first and second communication protocols. The method further involves communicating the encoded first information from the module via a second physical interface of the base to the controller via a bus using the first communication protocol.

According to yet another example, the exemplary apparatus includes a first interface communicatively coupled to one of a first field device of a process control system or a second field device of a process control system. including. The first interface communicates using a first fieldbus communication protocol when coupled to the first field device and communicates using the second fieldbus communication protocol when coupled to the second field device. use to communicate. The example apparatus includes a communications processor communicatively coupled to the first interface. A communication processor is configured to control one of the first field device or the second field device for communication over the bus using a third communication protocol that is different from the first and second fieldbus communication protocols. encoding first information received from one; The example apparatus includes a second communication processor communicatively coupled to the communication processor and the bus for conveying the first information to a controller of the process control system via the bus using a third communication protocol. Contains interface. The bus conveys second information received from the other of the first field device or the second field device using a third communication protocol.

FIG. 1 is a block diagram illustrating an example process control system. FIG. 3 is a diagram of an alternative example implementation that may be used to communicatively couple a workstation, controller, and I/O card. FIG. 3 is a diagram of an alternative example implementation that may be used to communicatively couple a workstation, controller, and I/O card. FIG. 3 is a diagram of an alternative example implementation that may be used to communicatively couple a workstation, controller, and I/O card. 1B is a detailed view of the exemplary marshalling cabinet of FIG. 1A; FIG. 1A is another example marshalling cabinet that may be used to implement the example marshalling cabinet of FIG. 1A; FIG. 3A and 3B are top and side views of the exemplary termination module of FIGS. 1A and 2; FIG. 3A and 3B are top and side views of the exemplary termination module of FIGS. 1A and 2; FIG. FIG. 1A is a detailed block diagram of the exemplary termination module of FIGS. 1A, 2, 4, 5, 13A-13B, and 14A-14B; 1B is a detailed block diagram of the example I/O card of FIG. 1A; FIG. Exemplary examples that may be used to display field device identification information and/or other field device information associated with the termination modules of FIGS. 1A, 2-6, 13A-13B, and 14A-14B FIG. 2 is a detailed block diagram of a labeler. 1A is a diagram of an isolation circuitry that may be implemented in connection with the example termination module of FIG. 1A to electrically isolate the termination modules from each other, field devices, and a communication bus; FIG. Exemplary illustrations that may be used to implement the termination modules of FIGS. 1A, 2-6, 13A-13B, and 14A-14B to convey information between field devices and I/O cards. 1 is a flowchart of a method. Exemplary illustrations that may be used to implement the termination modules of FIGS. 1A, 2-6, 13A-13B, and 14A-14B to convey information between field devices and I/O cards. 1 is a flowchart of a method. 1A is a flowchart of an example method that may be used to implement the I/O card of FIG. 1A to convey information between a termination module and a workstation. FIG. 1A is a flowchart of an example method that may be used to implement the I/O card of FIG. 1A to convey information between a termination module and a workstation. FIG. 2, 3, 6, and 8 for retrieving and displaying information related to a field device communicatively coupled to a termination module. It is a flowchart. 2 is a block diagram illustrating another example process control system before and after implementing the teachings disclosed herein with respect to an example Profibus PA process area and an example FOUNDATION fieldbus H1 (FF-H1) process area; FIG. be. 2 is a block diagram illustrating another example process control system before and after implementing the teachings disclosed herein with respect to an example Profibus PA process area and an example FOUNDATION fieldbus H1 (FF-H1) process area; FIG. be. FIG. 3 is a diagram of an alternative exemplary implementation of peer-to-peer communication of two FF-H1 compliant field devices communicatively coupled to corresponding termination modules. FIG. 3 is a diagram of an alternative exemplary implementation of peer-to-peer communication of two FF-H1 compliant field devices communicatively coupled to corresponding termination modules. implementing the termination module of FIGS. 1A, 2-6, 13A-13B, and 14A-14B to automatically detect a communication protocol associated with a corresponding field device connected to the termination module; 1 is a flowchart of an example method that may be used for. FIG. 1 is a block diagram of an example processor system that may be used to implement the example systems and methods described herein.

Although the following describes example devices and systems that include software and/or firmware executed on the hardware, among other components, such systems are merely exemplary; It should be noted that it should not be seen as limiting. For example, some or all of these hardware, software, and firmware components may be embodied solely in hardware, solely in software, or in any combination of hardware and software. , is taken into consideration. Accordingly, while the following describes example devices and systems, those skilled in the art will readily understand that the examples provided are not the only ways to implement such devices and systems.

An exemplary process control system includes a control room (e.g., control room 108 of FIG. 1A), a process controller area (e.g., process controller area 110 of FIG. 1A), and a termination area (e.g., termination area 140 of FIG. 1A). and one or more process areas (eg, process area 114 and process area 118 in FIG. 1A). Process areas include operations associated with performing a particular process (e.g., chemical processes, petroleum processes, pharmaceutical processes, pulp and paper processes, etc.) (e.g., controlling valves, controlling motors, boilers, etc.). control, monitoring, measuring parameters, etc.). Some process areas are inaccessible to humans due to harsh environmental conditions (eg, relatively high temperatures, airborne toxins, dangerous radiation levels, etc.). A control room typically includes one or more workstations within an environment that can be safely accessed by humans. The workstation includes a user application that allows a user (eg, an engineer, operator, etc.) to access control operations of the process control system by, for example, changing variable values, process control functions, and the like. The process control area includes one or more controllers communicatively coupled to workstations within the control room. The controller automates the control of field devices within the process area by executing process control strategies implemented through the workstation. An exemplary process strategy involves measuring pressure using a pressure sensor field device and automatically sending commands to a valve positioner to open and close a flow valve based on the pressure measurement. The termination area includes a marshalling cabinet that allows the controller to communicate with field devices within the process area. Specifically, a marshalling cabinet is a multiple termination device used to organize, consolidate, or forward signals from field devices to one or more I/O cards communicatively coupled to a controller. Contains modules. The I/O card converts information received from field devices into a format compatible with the controller, and converts information from the controller into a format compatible with the field device.

Known techniques used to communicatively couple field devices to a controller in a process control system include communicatively coupling each field device to a controller (e.g., process controller, programmable logic controller, etc.). It involves using separate buses (eg, wires, cables, or circuits) to and from each coupled I/O card. The I/O card can connect the controller to different data or signal types (e.g., analog in (AI) data type, analog out (AO) data type, discrete in (DI) data type, discrete out (DO) data type, communicatively link multiple field devices associated with different field device communication protocols (digital-in data types, and digital-out data types) by translating or converting information conveyed between the controller and the field devices. make it possible to For example, an I/O card may be provided with one or more field device interfaces configured to exchange information with a field device using a field device communication protocol associated with the field device. Different field device interfaces may have different channel types (e.g., analog in (AI) channel type, analog out (AO) channel type, discrete in (DI) channel type, discrete out (DO) channel type, digital in channel type, and Communicate via digital out channel type). In addition, the I/O card converts information received from field devices (e.g., voltage levels) into information (e.g., pressure levels) that the controller can use to perform operations related to controlling the field devices. measurement value). Known techniques require a bundle of wires or buses (eg, a multi-conductor cable) to communicatively couple multiple field devices to an I/O card. Unlike known techniques that use a separate bus to communicatively couple each field device to an I/O card, the example apparatus and methods described herein utilize multiple field devices. terminates in a termination panel (e.g., a marshalling cabinet) and provides one bus (e.g., conductive, optical, or wireless communication medium) communicatively coupled between the termination panel and the I/O card. The method may be used to communicatively couple a field device to an I/O card by using the method to communicatively couple a field device to an I/O card.

Exemplary apparatus and methods described herein provide exemplary apparatus and methods that communicatively couple one or more termination modules to one or more I/O cards that are communicatively coupled to a controller. It involves using a universal I/O bus (eg, a common or shared communications bus). Each termination module is communicatively coupled to one or more respective field devices using a respective field device bus (eg, an analog bus or a digital bus). The termination module receives field device information from the field device via the field device bus, e.g., by packetizing the field device information and communicating the packetized information to the I/O card via the universal I/O bus. The device is configured to communicate field device information to the I/O card via the universal I/O bus. Field device information may include, for example, field device identification information (e.g., device tag, electronic serial number, etc.), field device status information (e.g., communication status, diagnostic health information (open loop, short, etc.)), field device activity. information (e.g., process variable (PV) values), field device descriptive information (e.g., type or function of field devices such as valve actuators, temperature sensors, pressure sensors, flow sensors, etc.), field device connection configuration information (e.g., multi drop bus connection, point-to-point connection, etc.); field device bus or field device segment identification (e.g., a field device bus or field device segment through which a field device is communicatively coupled to a termination module); and/or field device data type information (eg, a data type descriptor indicating the data type used by a particular field device). The I/O card can extract field device information received over the universal I/O bus and communicate the field device information to a controller, which then stores some of the information for later analysis. or all may be communicated to one or more workstation terminals.

To convey field device information (e.g., commands, instructions, queries, threshold activity values (e.g., threshold PV values), etc.) from the workstation terminal to the field device, the I/O card packetizes the field device information; Packetized field device information can be conveyed to multiple termination modules. Each of the termination modules can then extract or depacketize each field device information from the packetized communications received from each I/O card and communicate the field device information to each field device.

In example embodiments described herein, a termination panel (e.g., marshalling cabinet) is configured to receive (e.g., connect to) a plurality of termination modules, each of the plurality of termination modules having a different field device. is communicatively connected to. At the termination panel, each termination module is provided with a termination labeler (or tagging system) to indicate which termination module is connected to which field device. A termination labeler includes an electronic display (eg, a liquid crystal display (LCD)) and components that determine which field devices are connected to a termination module corresponding to the termination labeler. In some example implementations, the display is attached to a termination panel instead of a termination module. Each of the displays is mounted in association with a respective termination module socket. In this way, when the termination module is removed from the termination panel, the corresponding display remains on the termination panel for use by a later connected termination module.

Referring now to FIG. 1A, an exemplary process control system 100 is communicatively coupled to a controller 104 via a bus or local area network (LAN) 106, commonly referred to as an application control network (ACN). The computer includes a workstation 102. LAN 106 may be implemented using any desired communication medium and protocol. For example, LAN 106 can be based on wired or wireless Ethernet communication protocols. However, other suitable wired or wireless communication media and protocols may be used. Workstation 102 may be configured to perform operations related to one or more information technology applications, user interaction applications, and/or communication applications. For example, the workstation 102 may communicate with other devices or systems using a desired communication medium (e.g., wireless, wired, etc.) and protocol (e.g., HTTP, SOAP, etc.). The device may be configured to perform operations related to process control-related applications and communication applications that enable the user to perform operations. The controller 104 has one or more processes generated by a system engineer or other system operator, e.g., using the workstation 102 or other workstations, that have already been downloaded and instantiated within the controller 104. It may be configured to perform control routines or functions. In the illustrated example, workstation 102 is located within a control room 108 and controller 104 is located within a process controller area 110 separate from control room 108 .

In the example embodiment, the example process control system 100 includes field devices 112a-c in a first process area 114 and field devices 116a-c in a second process control area 118. To communicate information between controller 104, field devices 112a-c, and field devices 116a-c, the example process control system 100 includes field junction boxes (FJBs) 120a-b and marshalling cabinets 122. provided. Each of field junction boxes 120a-b forwards signals from a respective one of field devices 112a-c and field devices 116a-c to marshaling cabinet 122. Marshaling cabinet 122 then organizes (e.g., summarizes, categorizes, etc.) the information received from field devices 112a-c and field devices 116a-c and transfers field device information to each I/O card of controller 104. (eg, I/O cards 132a-b and I/O cards 134a-b). In the illustrated embodiment, a marshalling cabinet 122 is also used to route information received from I/O cards of controller 104 to each one of field devices 112a-c and field devices 116a-c at a field junction box. Communication between controller 104 and field devices 112a-c and field devices 116a-c is bidirectional, such as transmitting via 120a-b.

In the example embodiment, field devices 112a-c are communicatively coupled to field junction box 120a, and field devices 116a-c are , communicatively coupled to field junction box 120b. For example, field junction boxes 120a-b can include one or more electrical data transceivers, Wireless data transceivers and/or optical data transceivers are provided. In the illustrated embodiment, field junction box 120b is wirelessly communicatively coupled to field device 116c. In an alternative exemplary implementation, marshalling cabinet 122 may be omitted and signals from field devices 112a-c and field devices 116a-c are routed from field junction boxes 120a-b to controller 104 I/O. Can be transferred directly to the card. In yet another exemplary implementation, field junction boxes 120a-b may be omitted and field devices 112a-c and field devices 116a-c may be connected directly to marshaling cabinet 122.

Field devices 112a-c and field devices 116a-c may be fieldbus-compliant valves, actuators, sensors, etc., in which case field devices 112a-c and field devices 116a-c may be Communicate via a digital data bus using the FOUNDATION fieldbus communication protocol (eg, FF-H1). Of course, other types of field devices and communication protocols can be used instead. For example, field devices 112a-c and field devices 116a-c may alternatively communicate via a data bus using the well-known Profibus and HART communication protocols, such as Profibus (e.g., Profibus PA), HART , or an AS-i compliant device. In some example implementations, field devices 112a-c and field devices 116a-c may communicate information using analog or discrete communications instead of digital communications. Additionally, communication protocols can be used to convey information related to different data types.

Each of field devices 112a-c and field devices 116a-c is configured to store field device identification information. Field device identification information can be a physical device tag (PDT) value, device tag name, electronic serial number, etc. that uniquely identifies each of field devices 112a-c and field devices 116a-c. In the example embodiment of FIG. 1A, field devices 112a-c store field device identification information in the form of physical device tag values PDT0-PDT2, and field devices 116a-c store field device identification information in the form of physical device tag values PDT0-PDT2. The target device tag values are stored in the format of PDT3 to PDT5. Field device identification information may be entered into field devices 112a-c and field devices 116a-c by the field device manufacturer and/or by an operator or engineer involved in the installation of field devices 112a-c and field devices 116a-c. can be stored or programmed by

To transfer information related to field devices 112a-c and field devices 116a-c within marshaling cabinet 122, marshaling cabinet 122 is provided with a plurality of termination modules 124a-c and termination modules 126a-c. ing. Termination modules 124a-c are configured to organize information related to field devices 112a-c in first process area 114, and termination modules 126a-c are configured to organize information related to field devices 112a-c in second process area 118. It is configured to organize information related to ~c. As shown, termination modules 124a-c and termination modules 126a-c communicatively connect to field junction boxes 120a-b via respective multi-conductor cables 128a and multi-conductor cables 128b (eg, multi-bus cables). connected. In an alternative exemplary implementation where marshalling cabinet 122 is omitted, termination modules 124a-c and termination modules 126a-c may be installed in each one of field junction boxes 120a-b.

The illustrative embodiment of FIG. 1A shows that each conductor or conductor pair (e.g., bus, twisted-pair communication medium, two-wire communication medium, etc.) within multi-conductor cables 128a-b connects field devices 112a-c and field devices 116a- Figure 2 illustrates a point-to-point configuration for communicating information uniquely associated with each one of the C and C. For example, multicore cable 128a includes a first conductor 130a, a second conductor 130b, and a third conductor 130c. Specifically, the first conductor 130a is used to form a first data bus configured to communicate information between the termination module 124a and the field device 112a, and the second conductor 130a is used to form a first data bus configured to communicate information between the termination module 124a and the field device 112a. 130b is used to form a second data bus configured to communicate information between termination module 124b and field device 112b, and third conductor 130c is used to communicate information between termination module 124c and field device 112b. and field device 112c. In an alternative example implementation using a multi-drop wiring configuration, each of termination modules 124a-c and termination modules 126a-c may be communicatively coupled to one or more field devices. For example, in a multi-drop configuration, termination module 124a may be communicatively coupled to field device 112a and another field device (not shown) via first conductor 130a. In some example implementations, the termination module may be configured to wirelessly communicate with multiple field devices using a wireless mesh network.

Additionally or alternatively, in some embodiments, a second field device (not shown) is connected to the termination module 124a via the first conductor 130a to provide a redundant, spare, or communicatively coupled as an exchange field device. In some such embodiments, termination module 124a is configured to communicate with a spare device until it is needed to communicate with the spare device (e.g., when field device 112a fails, an operator installs the spare device to replace field device 112a). (when configured), it is configured to communicate only with the field device 112a. That is, there are two devices communicatively coupled to the termination module 124a via the first conductor 130a, but unlike a multi-drop configuration, the termination module 124a and either the field device 112a or the spare field device. The communication between them effectively operates as a point-to-point connection. More specifically, termination module 124a may detect a spare field device at which point communication is initiated (either automatically or at the direction of a process controller) with the spare field device. All communications are directed to the primary or active device (eg, field device 112a) until the active device fails. In some embodiments, the spare field device is removed while the failed field device 112a is still within the process control system (e.g., before it is physically removed and/or before it is erased from the system's logical configuration). , is assigned and begins communicating with termination module 124a. In some such embodiments, the spare field device remains a "spare" destination until an operator designates the spare field device as the new primary device. In other embodiments, termination module 124a automatically replaces a spare field device with field device 112a once field device 112a fails. The ability to configure a spare field device to take over communications in this manner is typically not available with certain communication protocols (e.g., HART) because individual field devices This is because they are directly communicatively connected in a point-to-point manner. As a result, replacement of a failed field device typically involves physical removal of the field device, installation of a new field device, and subsequent manual appointment of the new field device. However, in some disclosed embodiments, as described more fully below, the field device 112a has an independent reserve on the first conductor 130a when implemented using the HART protocol for faster replacement. The I/O card is connected indirectly to the I/O card through a termination module 124a on a high-speed universal I/O bus that has sufficient bandwidth to handle the presence of field devices. Spare field devices on first conductor 130a may also be implemented with other communication protocols (eg, Profibus PA, FF-H1, etc.) in addition to or instead of HART.

Each of termination modules 124a-c and termination modules 126a-c may be configured to communicate with a respective one of field devices 112a-c and field devices 116a-c using different data types. For example, termination module 124a may include a digital field device interface for communicating with field device 112a using digital data, while termination module 124b may include a digital field device interface for communicating with field device 112b using analog data. may include an analog field device interface.

To control I/O communications between controller 104 (and/or workstation 102) and field devices 112a-c and field devices 116a-c, controller 104 connects a plurality of I/O cards 132a-c to field devices 112a-c and field devices 116a-c. b and I/O cards 134a-b. In the illustrated embodiment, I/O cards 132a-b control I/O communications between controller 104 (and/or workstation 102) and field devices 112a-c in first process area 114. I/O cards 134a-b are configured to control I/O communications between controller 104 (and/or workstation 102) and field devices 116a-c within second process area 118. It is composed of

In the example embodiment of FIG. 1A, I/O cards 132a-b and I/O cards 134a-b reside within controller 104. To communicate information from field devices 112a-c and field devices 116a-c to workstation 102, I/O cards 132a-b and I/O cards 134a-b communicate information to controller 104, and controller 104 , communicates information to workstation 102. Similarly, to communicate information from workstation 102 to field devices 112a-c and field devices 116a-c, workstation 102 communicates information to controller 104, which in turn communicates information to I/O cards. 132a-b and I/O cards 134a-b, and I/O cards 132a-b and I/O cards 134a-b transmit information to field devices 112a-c and field devices 116a-c. via modules 124a-c and termination modules 126a-c. In an alternative example implementation, I/O cards 132a-b and I/O cards 134a-b may be communicatively coupled to LAN 106 within controller 104, and I/O cards 132a-b and I/O cards 134a-b to communicate directly with workstation 102 and/or controller 104.

To provide fault-tolerant operation in the event that either I/O card 132a or I/O card 134a fails, I/O card 132b and I/O card 134b are configured as redundant I/O cards. has been done. That is, if I/O card 132a fails, redundant I/O card 132b takes control and performs the same operations that I/O card 132a would have performed had it not failed. Similarly, redundant I/O card 134b takes control when I/O card 134a fails.

To enable communication between termination modules 124a-c and I/O cards 132a-b and between termination modules 126a-c and I/O cards 134a-b, termination modules 124a-c include , I/O cards 132a-b via a first universal I/O bus 136a, and termination modules 126a-c connect I/O cards 134a-b to a second universal I/O bus 136a. They are communicatively coupled via O bus 136b. Unlike multi-conductor cables 128a and 128b, which use separate conductors or communication media for each one of field devices 112a-c and field devices 116a-c, universal I/O buses 136a-b are each configured to communicate information corresponding to a plurality of field devices (eg, field devices 112a-c and field devices 116a-c) using the same communication medium. For example, the communication medium may include a serial bus, two-wire communication, etc., through which information relating to two or more field devices may be communicated using, for example, packet-based communication techniques, multiplexed communication techniques, etc. It can be a medium (eg, twisted pair), optical fiber, parallel bus, etc.

In the exemplary implementation, universal I/O buses 136a-b are implemented using the RS-485 serial communication standard. The RS-485 serial communication standard may be configured to use less communication control overhead (eg, less header information) than other known communication standards (eg, Ethernet). However, in other example implementations, universal I/O buses 136a-b may be implemented using other suitable communication standards, including Ethernet, Universal Serial Bus (USB), IEEE 1394, etc. . Additionally, although universal I/O buses 136a-b are described above as a wired communication medium, in another example implementation, one or both of universal I/O buses 136a-b may be configured as a wireless communication medium. It can be implemented using a medium (eg, wireless Ethernet, IEEE-802.11, Wi-Fi, Bluetooth, etc.).

Universal I/O bus 136a and universal I/O bus 136b are used to convey information in substantially the same manner. In the illustrated embodiment, I/O bus 136a is configured to convey information between I/O cards 132a-b and termination modules 124a-c. I/O cards 132a-b and termination modules 124a-c use an addressing scheme to identify which information corresponds to which of termination modules 124a-c. This allows each termination module 124a-c to determine which information corresponds to which of field devices 112a-c. A termination module (eg, one of termination modules 124a-c and termination modules 126a-c) is connected to one of I/O cards 132a-b and I/O cards 134a-b. When the I/O card is present, the I/O card automatically obtains the termination module's address (eg, from the termination module) and exchanges information with the termination module. In this manner, termination modules 124a-c and termination modules 126a-c can send the termination module's address to I/O cards 132a-b and I/O cards 134a-b anywhere on their respective buses 136a-b. without the need to manually supply termination modules 124a-c and termination modules 126a-c to I/O cards 132a-b and I/O cards 134a-b, respectively. , may be communicatively coupled.

By using universal I/O buses 136a-b, the number of communication media (e.g., wires) required to convey information between marshaling cabinet 122 and controller 104 is reduced, with each termination required to communicate with the controller. This is a significant reduction over known configurations that require separate communication media for the modules. Reducing the number of communication media (e.g., reducing the number of communication buses or wires) required to communicatively couple the marshalling cabinet 122 to the controller 104 may reduce the number of communication media (e.g., reduce the number of communication buses or wires) required to communicatively couple the marshalling cabinet 122 to the controller 104 and the field devices 112a-c and field Reduces the engineering costs required to design and produce drawings for installing connections between devices 116a-c. Additionally, reducing the number of communication media, in turn, reduces installation and maintenance costs. For example, one of I/O buses 136a-b replaces multiple communication media used in known systems to communicatively couple field devices to a controller. Thus, instead of maintaining multiple communication media for communicatively coupling field devices 112a-c and field devices 116a-c to I/O cards 132a-b and I/O cards 134a-b. , the exemplary embodiment of FIG. 1A requires significantly less maintenance by using I/O buses 136a-b. Additionally, in the context of fieldbus-based field devices (e.g., Profibus PA compliant devices or FOUNDATION fieldbus H1 (FF-H1) compliant devices), the use of universal I/O buses 136a-b also Reduce or eliminate costs associated with the acquisition, installation, and maintenance of other components used to implement the bus architecture. For example, in addition to the cables for the trunks or segments of the fieldbus architecture, each Profibus PA and FF-H1 typically includes a protocol-specific I/O card and a power conditioner (for the FF-H1). or requires a DA/PA coupler (for Profibus PA) and a segment protector. However, such components are no longer required for field devices coupled to termination modules 124a-c and termination modules 126a-c to communicate with the controller via universal I/O buses 136a-b. Additionally, in some embodiments where each fieldbus device is connected to a corresponding termination module 124a-c or termination module 126a-c in a point-to-point architecture, the cost and complexity of the fieldbus segment design effort may be reduced. It can be significantly reduced or eliminated since the arrangement of device signals is handled electronically after being received by each corresponding termination module.

In addition, reducing the number of communication media required to communicatively couple marshalling cabinet 122 to I/O cards 132a-b and I/O cards 134a-b reduces the need for more termination modules (e.g., There is more available space for termination modules 124a-c and termination modules 126a-c), thereby increasing the I/O density of marshalling cabinet 122 relative to known systems. In the illustrative example of FIG. 1A, marshaling cabinet 122 can have many termination modules; otherwise, known system implementations have more marshaling cabinets (e.g., three marshalling cabinets). ) is required. Further, in some embodiments, marshaling cabinet 122 communicates data over one universal I/O bus 136a for a greater number of field devices that communicate data through other types of bus communications. There can be more termination modules 124a-c corresponding to field devices 112a-c. For example, fieldbus segments are typically limited to carrying signals for up to 16 field devices. In contrast, in some embodiments, one of the universal I/O buses 136a-b may provide communications associated with up to 96 termination modules 124a-c and termination modules 126a-c. I can do it.

The I/O cards 132a-b and the I/O card 134a may be configured to use different data type interfaces (eg, different channel types) to communicate with the field devices 112a-c and the field devices 116a-c. By providing termination modules 124a-c and termination modules 126a-c configured to use respective common I/O buses 136a and 136b to communicate with , the example embodiment of FIG. 1A allows different field device data types (e.g., data types or channel types used by field devices 112a-c and field devices 116a-c) to I/O cards 132a-b and I/O cards 134a-b. Make it. Therefore, an I/O card with one interface type (e.g., an I/O bus interface type for communicating via I/O bus 136a and/or I/O bus 136b) may have different field device interface types. can communicate with multiple field devices that have

Using I/O bus 136a and/or I/O bus 136b to exchange information between controller 104 and termination modules 124a-c and termination modules 126a-c may be used to transfer information from field devices to Allows connection routing to O-cards to be defined late in the design or installation process. For example, termination modules 124a-c and termination modules 126a-c may be placed at various locations within marshaling cabinet 122 while maintaining access to each one of I/O bus 136a and I/O bus 136b. may be placed.

In the illustrated embodiment, marshalling cabinet 122, termination modules 124a-c and 126a-c, I/O cards 132a-b and 134a-b, and controller 104 integrate with existing process control system equipment. , facilitates transitioning to a configuration substantially similar to that of the exemplary process control system 100 of FIG. 1A. For example, termination modules 124a-c and termination modules 126a-c can be configured to include appropriate field device interface types such that termination modules 124a-c and termination modules 126a-c are used within a process control system. may be configured to be communicatively coupled to existing field devices already installed in the field. Similarly, controller 104 may be configured to include a known LAN interface for communicating via a LAN to an already installed workstation. In some example implementations, I/O cards 132a-b and I/O cards 134a-b can be installed or communicatively coupled to a known controller and configured to operate within a process control system. To avoid the need to replace an already installed controller.

In the illustrated embodiment, I/O card 132a includes data structure 133 and I/O card 134a includes data structure 135. Data structure 133 includes field device identification numbers (e.g., field device identification information). Termination modules 124a-c may use the field device identification number stored in data structure 133 to determine whether a field device is incorrectly connected to one of termination modules 124a-c. can. Data structure 135 includes field device identification numbers (e.g., field device identification information). Data structures 133 and data structures 135 may be added by engineers, operators, and/or users via workstation 102 during configuration time or during operation of exemplary process control system 100. In some examples, termination modules 124a-c may be communicatively coupled to multiple field devices (eg, an active field device and a redundant or spare field device). In such illustrative examples, data structure 135 stores a field device identification number corresponding to each field device (eg, field devices 116a-c and corresponding spare field devices). Although not shown, redundant I/O card 132b stores the same data structure as data structure 133, and redundant I/O card 134b stores the same data structure as data structure 135. Additionally or alternatively, data structure 133 and data structure 135 may be stored within workstation 102.

In the illustrated example, marshalling cabinet 122 is shown located in a termination area 140 separate from process control area 110. I/O buses 136a-b (e.g., each connected to one of field devices 112a-c and field devices 116a-c, or a limited group thereof along a multi-drop segment) instead of significantly more communication media. communicatively coupling termination modules 124a-c and termination modules 126a-c to controller 104 using a plurality of uniquely associated communication buses) without significantly reducing communication reliability. Additionally, it facilitates locating the controller 104 relatively far from the marshalling cabinet 122 than known configurations. In some example implementations, process control area 110 and termination area 140 may be combined such that marshalling cabinet 122 and controller 104 are located within the same area. In either case, locating marshalling cabinet 122 and controller 104 in an area separate from process area 114 and process area 118 means that I/O cards 132a-b and I/O cards 134a-b Termination modules 124a-c and 126a-c and universal I/O buses 136a-b may be exposed to harsh environmental conditions (e.g., heat, moisture, electromagnetic noise, etc.) that may be associated with process area 114 and process area 118. ). In this manner, the cost and complexity of designing and manufacturing termination modules 124a-c and termination modules 126a-c and I/O cards 132a-b and I/O cards 134a-b can be reduced to field devices 112a-c. Significant savings can be made in the cost of manufacturing communication and control circuitry between the field devices 116a-c and the termination modules 124a-c and 126a-c, and the I/O cards 132a-b. and to ensure reliable operation (e.g., reliable data communication) necessary for I/O cards 134a-b to operate under the environmental conditions of process area 114 and process area 118. This is because it does not require the necessary operational specification characteristics (eg, shielding, more robust circuitry, more complex error checking, etc.).

1B-1D illustrate alternative exemplary implementations that may be used to communicatively couple a workstation, controller, and I/O card. For example, in the exemplary embodiment shown in FIG. 1B, a controller 152 (performing substantially the same function as controller 104 of FIG. 1A) connects I/O cards 154a-b and I/O cards 156a-b. They are communicatively coupled via a backplane communication bus 158 . I/O cards 154a-b and I/O cards 156a-b perform substantially the same functions as I/O cards 132a-b and I/O cards 134a-b of FIG. 124a-c and termination modules 126a-c are configured to be communicatively coupled to universal I/O buses 136a-b. For communicating with workstation 102, controller 152 is communicatively coupled to workstation 102 via LAN 106.

In another exemplary embodiment shown in FIG. 1C, a controller 162 (performing substantially the same functions as controller 104 of FIG. 1A) connects a workstation 102 to a plurality of I/O cards 164a-b and It is communicatively coupled to O cards 166a-b via LAN 106. I/O cards 164a-b and I/O cards 166a-b perform substantially the same functions as I/O cards 132a-b and I/O cards 134a-b of FIG. 124a-c and termination modules 126a-c are configured to be communicatively coupled to universal I/O buses 136a-b. However, I/O cards 132a-b and I/O cards 134a-b of FIG. 1A are different from I/O cards 154a-b and I/O cards 156a-b of FIG. b and I/O cards 166a-b are configured to communicate with controller 162 and workstation 102 via LAN 106. In this manner, I/O cards 164a-b and I/O cards 166a-b can directly exchange information with workstation 102.

In yet another exemplary embodiment shown in FIG. 1D, I/O cards 174a-b (which perform substantially the same functions as I/O cards 132a-b and I/O cards 134a-b of FIG. 1A) and I/O cards 176a-b are implemented within a workstation 172 (which performs substantially the same functions as workstation 102 of FIG. 1A). In some example implementations, physical I/O cards 174a-b and I/O cards 176a-b are not contained within workstation 172, but are The functionality of /O cards 176a-b is implemented within workstation 172. In the illustrative embodiment of FIG. 1D, I/O cards 174a-b and I/O cards 176a-b provide universal I/O cards for communicating information with termination modules 124a-c and termination modules 126a-c. Configured to be communicatively coupled to buses 136a-b. Additionally, in the illustrated embodiment of FIG. 1D, workstation 172 may be configured to perform substantially the same functions as controller 104, eliminating the need to provide a controller to implement process control strategies. Can be done. However, a controller can be provided.

FIG. 2 is a detailed view of the exemplary marshalling cabinet 122 of FIG. 1A. In the illustrated embodiment, marshalling cabinet 122 includes termination module 124
A socket rail 202a and a socket rail 202b are provided that accept a-c. In addition, marshalling cabinet 122 is provided with an I/O bus transceiver 206 that communicatively couples termination modules 124a-c to universal I/O bus 136a, described above in connection with FIG. 1A. I/O bus transceiver 206 may be implemented using transmitter amplifiers and receiver amplifiers that condition signals exchanged between termination modules 124a-c and I/O cards 132a-b. Marshalling cabinet 122 is provided with another universal I/O bus 208 that communicatively couples terminal modules 124a-c to I/O bus transceiver 206. In the illustrated embodiment, I/O bus transceiver 206 is configured to convey information using a wired communication medium. Although not shown, marshalling cabinet 122 may include another terminal substantially similar to or the same as I/O bus transceiver 206 to communicatively couple termination modules 126a-c to I/O cards 134a-b. An I/O bus transceiver may be provided.

Common communication interfaces (e.g., I/O bus 208 and I/O bus 136a) can be used to exchange information between I/O cards 132a-b and termination modules 124a-c to to I/O cards can be defined late in the design or installation process. For example, termination modules 124a-c may be communicatively coupled to I/O bus 208 at various locations within marshaling cabinet 122 (eg, at various termination module sockets on socket rails 202a-b). In addition, a common communication interface between I/O cards 132a-b and termination modules 124a-c (eg, I/O bus 208 and I/O bus 136a) Reduces the number of communication media (e.g., the number of communication buses and/or wires) between modules 124a-c, and thus less than the number of known termination modules that can be installed in known marshalling cabinet configurations. This also allows a relatively large number of termination modules 124a-c (and/or termination modules 126a-c) to be installed within marshalling cabinet 122.

Each of termination modules 124a-c is provided with a display 212 (e.g., an electronic termination label) for displaying field device identification information and/or other field device information associated with termination modules 124a-c. . Display 212 of termination module 124a displays a field device identification (eg, field device tag) of field device 112a (FIG. 1A). In addition, the display 212 of the termination module 124a may be used to display field device activity information (e.g., measurement information, line voltage, etc.), data type information (e.g., analog signals, digital signals, etc.), field device status information (e.g., analog signals, digital signals, etc.). For example, device on, device off, device error, etc.) and/or other field device information may be displayed. If termination module 124a is configured to be communicatively coupled to multiple field devices (e.g., field device 112a of FIG. 1A and other field devices (not shown)), display 212 may be used to Field device information associated with all of the field devices communicatively coupled to module 124 may be displayed. In the illustrated example, display 212 is implemented using a liquid crystal display (LCD). However, in other example implementations, display 212 may be implemented using other suitable display technologies.

To read field device identification information and/or other field device information, each termination module 124a-c is provided with a labeler 214 (eg, a termination labeler). For example, when field device 112a is communicatively coupled to termination module 124a, labeler 214 of termination module 124a may transmit field device identification information and/or other field device information to field device 112a (and/or termination module 124a). 124a) and display information via display 212 of termination module 124a. Labeler 214 is described in detail below in connection with FIG. Providing display 212 and labeler 214 reduces cost and installation time associated with manually labeling wires and/or buses associated with termination modules and field devices. However, in some example implementations, manual wire labeling may also be used in conjunction with display 212 and labeler 214. For example, display 212 and labeler 214 may be used to determine which of field devices 112a-c and field devices 116a-c are connected to termination modules 124a-c and termination modules 126a-c, respectively. By doing so, field devices 112a-c and field devices 116a-c can be communicatively coupled to I/O cards 132a-b and I/O cards 134a-b relatively quickly. Subsequently, after the installation is complete, labels may optionally be attached to the buses or wires extending between termination modules 124a-c and 126a-c and field devices 112a-c and 114a-c. can be added. Display 212 and labeler 214 are also configured to display status information (e.g., device error, device alarm, device on, device off, device disabled, etc.) to facilitate troubleshooting processes. By configuring this, the cost and time associated with maintenance work can be reduced.

Marshalling cabinet 122 is provided with a power supply 216 to provide power to termination modules 124a-c, I/O bus transceiver 206, and display 212. In the example embodiment, termination modules 124a-c use power from power source 216 to communicate with and/or cause field devices to operate (e.g., field devices 112a-c of FIG. 1A). powering the communication channel or communication interface used to provide power for the Additionally, in some embodiments, marshalling cabinet 122 is provided with a power regulator 218 that regulates or controls the power provided to each termination module 124a-c along socket rails 202a-b. In some embodiments, termination modules 124a-c may be powered from an external power source and/or power conditioner via an integrated power input bus communicatively coupled to socket rails 202a-b. can.

FIG. 3 is another example marshaling cabinet 300 that may be used to implement example marshaling cabinet 122 of FIG. 1A. In the illustrated embodiment, marshalling cabinet 300 is provided with a wireless I/O bus communication controller 302 for communicating wirelessly with controller 104 of FIG. 1A via wireless universal I/O connection 304. As shown in FIG. 3, a plurality of termination modules 306, which are substantially similar or the same as termination modules 124a-c and termination modules 126a-c of FIG. 1A, are plugged into rail sockets 308a and 308b and wirelessly It is communicatively coupled to an I/O bus communication controller 302 via a universal I/O bus 309 within marshaling cabinet 300 . In the example embodiment, wireless I/O bus communication controller 302 emulates an I/O card (e.g., I/O card 134a of FIG. 1A) of controller 104 of FIG. 1A such that termination module 306 enable communication with.

Unlike the illustrative embodiment of FIG. 2 in which displays 212 are attached to termination modules 124a-c, in the illustrative embodiment of FIG. Installed within cabinet 300. In this manner, when one of termination modules 306 is plugged in and communicatively coupled to a field device (e.g., one of field devices 112a-c and field devices 116a-c of FIG. 1A) , each one of labeler 214 and display 310 of termination module 306 may be used to display field device identification information indicative of a field device connected to termination module 306 . Display 310 may also be used to display other field device information. Marshalling cabinet 300 is provided with a power supply 312 that is substantially similar or the same as power supply 216 of FIG. Additionally, in some embodiments, marshalling cabinet 300 is provided with a power regulator 314 that is substantially similar or the same as power regulator 218 of FIG.

4 shows a top view and FIG. 5 shows a side view of the exemplary termination module 124a of FIGS. 1A and 2. In the example embodiment of FIG. 4, the display 212 is on the top surface of the example termination module 124a, and the display 212 is visible to the operator during operation when the termination module 124a is plugged into the rail socket 202a (FIG. 3). or make it visible to the user. As shown in the example embodiment of FIG. 5, example termination module 124a is removably coupled to base 402. The exemplary termination module 124a includes a plurality of contacts 404 (two shown) that communicatively and/or electrically couple the termination module 124a to the base 402. In this manner, the base 402 can be coupled to the marshalling cabinet 122 (FIGS. 1A and 2), and the termination module 124a can be coupled to and removed from the marshalling cabinet 122 via the base 402. Base 402 is provided with a termination screw 406 (eg, a field device interface) that fastens or secures a conductive communication medium (eg, bus) from field device 112a. When termination module 124a is removably coupled to base 402, termination screw 406 is communicatively coupled to one or more of contacts 404 to transfer information between termination module 124a and field device 112a. make it possible to convey. In other example implementations, base 402 may be provided with other suitable types of field device interfaces (eg, sockets) in place of termination screws 406. Additionally, although one field device interface (e.g., termination screw 406) is shown, base 402 is configured to allow multiple field devices to be communicatively coupled to termination module 124a. , more field device interfaces may be provided.

To communicatively couple termination module 124a to universal I/O bus 208 of FIG. 2, base 402 is provided with universal I/O bus connector 408 (FIG. 5). Universal I/O bus connector 408 engages universal I/O bus 208 when a user inserts base 402 into socket rail 202a or socket rail 202b (FIG. 2). Universal I/O bus connector 408 may be implemented using any suitable interface, including, for example, a relatively simple interface such as an insulated perforated connector. An I/O bus connector 408 is connected to one or more of the contacts 404 of the termination module 124a to enable information to be conveyed between the termination module 124a and the I/O bus 208. .

As shown in FIG. 5, base 402 may also be provided with an optical display interface connector 410 that communicatively couples termination module 124a to an external display (eg, one of displays 310 of FIG. 3). For example, if termination module 124a is implemented without display 212, termination module 124a uses display interface connector 410 to transmit field device identification information or other field device information to an external display (e.g., the display of FIG. 3). 310).

6 is a detailed block diagram of the example termination module 124a of FIGS. 1A and 2, FIG. 7 is a detailed block diagram of the example I/O card 132a of FIG. 1A, and FIG. 7 is a detailed block diagram of the example labeler 214 of FIGS. 2, 3, and 6. FIG. The example termination module 124a, example I/O card 132a, and example labeler 214 may be implemented using any desired combination of hardware, firmware, and/or software. For example, one or more integrated circuits, discrete semiconductor components, or passive electronic components can be used. Additionally or alternatively, the example termination module 124a and the example I/O card 132a and the example labeler 214 and some or all of the blocks or portions thereof may be connected to a processor system (e.g., instructions stored on a machine-accessible medium that, when executed by the example processor system 1610 of FIG. 16, perform the operations depicted in the flowcharts of FIGS. , code, and/or other software and/or firmware, and the like. Although the example termination module 124a, the example I/O card 132a, and the example labeler 214 are described as having one of each block described below, the example termination module 124a and the example labeler 214 are described as having one of each block described below. Each example I/O card 132a and example labeler 214 may be provided with more than one of each block described below.

Referring to FIG. 6, the example termination module 124a includes a universal Includes an I/O bus interface 602. I/O bus interface 602 can be implemented using, for example, the RS-485 serial communications standard, Ethernet, or the like. Termination module 124a is provided with an address identifier 604 to identify the address of termination module 124a and/or the address of I/O card 132a. Address identifier 604 may be configured to query I/O card 132a (FIG. 1A) for a termination module address (eg, a network address) when termination module 124a is plugged into marshalling cabinet 122. In this way, termination module 124a can use the termination module address as a source address when communicating information to I/O card 132a, and I/O card 132a can use the termination module address as a source address when communicating information to termination module 124a. Use the termination module address as the destination address.

To control various operations of termination module 124a, termination module 124a is provided with an operation controller 606. In example implementations, the motion controller may be implemented using a microprocessor or microcontroller. Operation controller 606 conveys instructions or commands to other portions of example termination module 124a to control operation of those portions.

The exemplary termination module 124a is provided with an I/O bus communications processor 608 for communicating information with the I/O card 132a via the universal I/O bus 136a. In the illustrated embodiment, I/O bus communications processor 608 packetizes information for transmission to I/O card 132a and depackets information received from I/O card 132a. In the illustrated embodiment, I/O bus communications processor 608 generates header information for each packet transmitted and reads header information from received packets. Exemplary header information includes a destination address (e.g., the network address of I/O card 132a), a source address (e.g., the network address of termination module 124a), a packet type or data type (e.g., analog field device information, field device information, command information, temperature information, real-time data values, etc.) and error checking information (eg, cyclic redundancy check (CRC)). In some example implementations, I/O bus communication processor 608 and motion controller 606 may be implemented using the same microprocessor or microcontroller.

To provide (e.g., obtain and/or generate) field device identification information and/or other field device information (e.g., activity information, data type information, status information, etc.), termination module 124a communicates with labeler 214 ( 2 and 3) are provided. Labeler 214 will be described in detail below in connection with FIG. Termination module 124a also includes a display 212 (FIG. 2) that displays field device identification information and/or other field device information provided by labeler 214.

To control the amount of power provided to field device 112a (or other field device) of FIG. 1A, termination module 124a is provided with a field power controller 610. In the illustrated example, power supply 216 (FIG. 2) of marshaling cabinet 122 provides power to termination module 124a to power a communication channel interface for communicating with field device 112a. For example, some field devices communicate using 12 volts and others communicate using 24 volts. In the illustrated example, field power controller 610 is configured to regulate, control, step up, and/or step down the power provided by power source 216 to termination module 124a. In some embodiments, power regulation is accomplished via a power regulator 218 (FIG. 2) associated with the marshalling cabinet. In some example implementations, field power controller 610 limits the amount of power used to communicate with field devices and/or the amount of power provided to field devices to prevent flammable or combustible significantly reduce or eliminate the risk of sparks in the environment.

Termination module 124a is provided with a power converter 612 to convert power received from power source 216 (FIG. 2) into power for termination module 124a and/or field device 112a. In the illustrated example, the circuitry used to implement termination module 124a uses one or more voltage levels (e.g., 3.3V) that are different than the voltage levels required by field device 112a. . Power converter 612 is configured to provide different voltage levels to termination module 124a and field device 112a using power received from power supply 216. In the illustrated embodiment, the power output generated by power converter 612 is used to power up termination module 124a and field device 112a and to communicate information between termination module 124a and field device 112a. Some field device communication protocols require relatively higher or lower voltage and/or current levels than other communication protocols. In the illustrated example, field power controller 610 controls power converter 612 to provide voltage levels to power up and communicate with field device 112a. However, in other example implementations, the power output generated by power converter 612 may be used to power termination module 124a, while a separate power source external to marshalling cabinet 122 may be used to Field device 112a can be activated.

To electrically isolate the circuitry of termination module 124a from I/O card 132a, termination module 124a is provided with one or more isolation devices 614. Isolation device 614 can be implemented using galvanic isolators and/or optical isolators. Exemplary insulation structures are described in detail below with respect to FIG.

To convert between analog and digital signals, termination module 124a is provided with a digital-to-analog converter 616 and an analog-to-digital converter 618. Digital-to-analog converter 616 is configured to convert the digital representation of an analog value received from I/O card 132a into an analog value that can be communicated to field device 112a of FIG. 1A. Analog-to-digital converter 618 is configured to convert analog values (eg, measurements) received from field device 112a into digital representations that can be communicated to I/O card 132a. In an alternative exemplary implementation in which termination module 124a is configured to communicate digitally with field device 112a, digital-to-analog converter 616 and analog-to-digital converter 618 are omitted from termination module 124a. be able to.

To control communications with field devices 112a, termination module 124a is provided with a field device communications processor 620. Field device communications processor 620 ensures that information received from I/O card 132a is of the correct format and voltage type (eg, analog or digital) to communicate to field device 112a. Field device communication processor 620 is also configured to packetize or depacketize information if field device 112a is configured to communicate using digital information. In addition, field device communications processor 620 extracts information received from field device 112a and transfers the information to analog-to-digital converter 618 and/or I/O bus communications processor for later communication to I/O card 132a. 608. In some embodiments, field device communications processor 620 assists in identifying appropriate communications protocols associated with field device 112a. For example, termination module 124a may be configured to communicate with fieldbus-compliant devices, including Profibus PA devices or FF-H1 devices. In such embodiments, field device communications processor 620 implements an autosensing routine in which field device communications processor 620 formats test signals or test requests that correspond to the Profibus PA communications protocol. If field device 112a responds to the request, field device 112a is verified as a Profibus PA compliant device, and all subsequent communications are formatted based on the Profibus PA protocol. If field device 112a does not respond to the Profibus PA formatted request, field device communication processor 620 formats a second request that corresponds to the FF-H1 communication protocol to determine whether fieldbus device 112a is an FF-H1 compliant device. The determination is made based on whether the field device 112a responds to the second request. If termination module 124a is configured to communicate using other protocols (e.g., HART), field device communications processor 620 uses additional Requests can be generated.

In some examples, such autosensing routines are implemented periodically (or aperiodically) (e.g., after a certain threshold period) to detect a field communicatively coupled to termination module 124a. Detect changes in your device. For example, the autosensing routine may detect a first, active or primary field device (e.g., field device 112a) and a second, spare (not shown) on conductor 130a communicatively coupled to termination module 124a. Field devices can be detected. If the first field device fails, termination module 124a may detect this by loss of communication with the first field device. In some such embodiments, the autosensing routine detects the spare device and compares the device information (e.g., placeholder information, device type, vendor, version, etc.) to the device information of the failed device. do. In some embodiments, if the device information matches (e.g., the primary field device and the spare device are the same device except for the serial number), the termination module 124a connects the first field device with the spare field device. automatically replace the system to maintain control of the process system. Additionally or alternatively, in some embodiments, if the device information includes some differences (e.g., different versions or vendors), termination module 124a designates a spare field device and begins communicating with a field device, but remains active (although disconnected) until an operator or engineer designates the first field device, removes it, and/or designates a spare field device as the new working or primary device. , while continuing to indicate the first field device as the primary device).

In the example embodiment, field device communication processor 620 is also configured to timestamp information received from field device 112a. Generating timestamps in termination module 124a facilitates implementing sequence of events (SOE) operations using timestamp precision in the sub-millisecond range. For example, the timestamp and respective information may be communicated to controller 104 and/or workstation 102. For example, a sequence of events operations performed by workstation 102 (FIG. 1A) (or other processor system) can then be used to identify events that occur before, during, and/or after a particular operating condition (e.g., failure mode). can be analyzed to determine what caused a particular operating condition. Timestamping in the sub-millisecond range allows events to be captured with relatively high accuracy. In some example implementations, the field device communication processor and motion controller 606 may be implemented using the same microprocessor or microcontroller.

Generally, field device communication controllers similar to field device communication controller 620 include communication protocol functionality or other communication functionality (e.g., Fieldbus communication protocol functionality, HART communication protocol functions, etc.). For example, if field device 112a is implemented as a HART device, field device communication controller 620 of termination module 124a is provided with HART communication protocol functionality. When termination module 124a receives information destined for field device 112a from I/O card 132a, field device communication controller 620 formats the information according to the HART communication protocol and delivers the information to field device 112a.

In the example embodiment, field device communication controller 620 is configured to process pass-through messages. A pass-through message originates at a workstation (e.g., workstation 102 of FIG. 1A) and is transferred as a payload (e.g., the data portion of a communication packet) to a field device (e.g., field device 104 of FIG. 1A) via a controller (e.g., controller 104 of FIG. the termination module (eg, termination module 124a of FIG. 1A) for delivery to device 112a). For example, a message that originates at workstation 102 and is to be delivered to field device 112a is tagged at workstation 102 with a communications protocol descriptor (e.g., a HART protocol descriptor) and/or is tagged with a communication protocol descriptor (e.g., a HART protocol descriptor) and/or Formatted according to protocol. Workstation 102 then wraps the message in a payload of one or more communication packets and delivers the message from workstation 102, through I/O controller 104, to termination module 124a as a pass-through message. . Wrapping a message may involve, for example, packetizing the message into header information according to a communication protocol used to communicate with a field device (eg, Fieldbus protocol, HART protocol, etc.). When termination module 124a receives a communication packet containing a pass-through message from I/O card 132, I/O bus communication processor 608 (FIG. 6) extracts the payload from the received communication packet. Field device communications controller 620 (FIG. 6) then retrieves the pass-through message from the payload and formats the message (if not already formatted at workstation 102) according to the communications protocol descriptor generated by workstation 102. and transmits the message to field device 112a.

Field device communication controller 620 is also configured to communicate pass-through messages to workstation 102 in a similar manner. For example, if field device 112a generates a message that is to be delivered to workstation 102 (e.g., in response to a workstation message or other message), field device communication controller 620 may send the message from field device 112a to Encased in a payload consisting of one or more communication packets, I/O bus communication processor 608 conveys the one or more packets containing the encased message to I/O card 132a. When workstation 102 receives a packet containing a wrapped message from controller 104, workstation 102 retrieves and processes the message.

Termination module 124a is provided with a field device interface 622 configured to communicatively couple termination module 124a to a field device (eg, field device 112a of FIG. 1A). For example, field device interface 622 may be communicatively coupled to termination screw 406 of FIGS. 4 and 5 via one or more of contacts 404 (FIG. 4).

In some embodiments, termination module 124a is provided with a fieldbus diagnostic analyzer 624 configured to provide advanced diagnostics regarding the associated field device when the field device is fieldbus compliant. During operation, fieldbus diagnostic analyzer 624 makes measurements regarding the condition of physical wiring (eg, first conductor 130a in FIG. 1A) and associated communications. For example, fieldbus diagnostic analyzer 624 can measure supply voltage, load current, signal level, line noise, and/or jitter. Although advanced diagnostic modules with similar functionality can be incorporated into traditional fieldbus architectures, the diagnostics provided by fieldbus diagnostic analyzer 624 may be more reliable and/or robust; This is because module 124a is coupled in a point-to-point architecture to only one field device, rather than having to diagnose multiple devices in a traditional fieldbus segment multi-drop architecture.

Referring now to FIG. 7, the exemplary I/O card 132a of FIG. 1A includes a communication interface 702 for communicatively coupling the I/O card 132a to the controller 104 (FIG. 1A). In addition, the example I/O card 132a includes a communications processor 704 that controls communications with the controller 104 and inputs and retrieves information to and from the controller 104. In the example embodiment, communication interface 702 and communication processor 704 are configured to communicate to controller 104 information to be delivered to controller 104 and information to be delivered to workstation 102 (FIG. 1A). ing. To communicate information to be delivered to workstation 102, communication interface 702 may transmit information (e.g., information from field devices 112a-c, termination modules 124a-c, and/or I/O card 132a) to Packets containing information are packaged according to a communication protocol (e.g., Communication Control Protocol (TCP), User Datagram Protocol (UDP), etc.) and communicated to the workstation 102 in a payload consisting of one or more communication packets. may be configured. Workstation 102 then retrieves the payload from the received packet and retrieves the information in the payload. In an example embodiment, information in the payload of a packet conveyed to workstation 102 by communication interface 702 may include one or more wrappers. For example, information originating at a field device (e.g., field device 112a) may be wrapped within a field device communication protocol wrapper (e.g., FOUNDATION fieldbus communication protocol wrapper, HART communication protocol wrapper, etc.) such that communication interface 702 , wrapping the information according to a TCP-based protocol, a UDP-based protocol, or other protocol that allows controller 104 to later communicate the information to workstation 102 . In a similar manner, communication interface 702 is configured to retrieve information communicated by workstation 102 to controller 104 for distribution to field devices 112a-c, termination modules 124a-c, and/or I/O card 132a. may be configured.

In an alternative example implementation, communication interface 702 and communication processor 704 can communicate information (with or without a field device communication protocol wrapper) to controller 104 , and controller 104 communicates information (with or without a field device communication protocol wrapper) to workstation 102 The information to be delivered to the network can be packetized in the same manner as described above. Communication interface 702 and communication processor 704 may be implemented using wired or wireless communication standards.

In alternative example implementations, such as the example embodiment of FIG. 1C, communication interface 702 and communication processor 704 are configured to communicate with workstation 102 and/or controller 162 via LAN 106. obtain.

I/O card 132a is provided with one or more user interface ports 706 to allow a user to interact with and/or access I/O card 132a. In the illustrated example, user interface ports 706 include a keyboard interface port 703 and a portable handheld computer (eg, personal digital assistant (PDA), tablet PC, etc.) interface port 707. For example, a PDA 708 is shown communicatively coupled to user interface port 706 using wireless communications.

To communicatively couple I/O card 132a to universal I/O bus 136a (FIG. 1A), I/O card 132a is provided with an I/O bus interface 710. I/O card 132a provides an I/O bus communications processor 712 to process communication information exchanged via I/O bus 136a and to control communications occurring via I/O bus 136a. has been done. I/O bus interface 710 may be similar or the same as I/O bus interface 602 of FIG. 6, and I/O bus communication processor 712 may be similar or the same as I/O bus communication processor 608 of FIG. can be. Converting the power provided by the controller 104 of FIG. 1A into the power necessary to power and operate the I/O card 132a and/or to communicate with the termination modules 124a-c. For this purpose, the I/O card 132a is provided with a power converter 714.

Referring now to FIG. 8, the exemplary labeler 214 can be configured to connect the labeler 214 to a termination module (e.g., termination module 124a of FIGS. 1A, 2, 4, 5, and 6) and/or a field device (e.g., , 112a) of FIG. 1A) to provide field device identification information (e.g., device tag value, device name, electronic serial number, etc.) and/or other field device information (e.g., activity information, including a communication interface 802 configured to read data type information, state information, etc.). Labeler 214 is provided with a communications processor 804 to control communications with termination module 124a and/or field device 112a.

To detect a connection to a field device (eg, field device 112a of FIG. 1A), labeler 214 is provided with a connection detector 806. Connection detector 806 can be implemented using, for example, a voltage sensor, current sensor, logic circuit, etc., to detect when field device 112a is connected to termination module 124a. In the illustrated example, when connection detector 806 determines that field device 112a is connected to termination module 124a, connection detector 806 indicates that a notification (e.g., an interrupt) indicates the detected connection to communications processor 804. be able to convey the information to Communications processor 804 then queries termination module 124a and/or field device 112a for field device identification information for field device 112a. In an exemplary implementation, the connection detector 806 also detects, for example, multi-drop connections, point-to-point connections, point-to-point connections between active and non-active spare field devices, wireless mesh It may be configured to determine the type of connection that communicatively couples field device 112a to termination module 124a, such as a network connection, an optical connection, etc.

Labeler 214 is provided with a display interface 808 for displaying field device identification information and/or other field device information. In the illustrated example, display interface 808 is configured to operate and control a liquid crystal display (LCD). For example, display interface 808 may be configured to control LCD display 212 (FIG. 2) attached to termination module 124a or LCD display 310 attached to marshalling cabinet 300 (FIG. 3). However, in other example implementations, display interface 808 may instead be configured to drive other display types.

To detect activity of field device 112a, labeler 214 is provided with a field device activity detector 810. In the illustrated embodiment, communications processor 804 transfers data to termination module 124a and/or field device 112.
Upon receiving from a, communications processor 804 communicates the received data to field device activity detector 810 . Field device activity detector 810 then detects measurement information (e.g., temperature, pressure, line voltage, etc.) or other monitoring information (e.g., valve closed, valve open, etc.) generated by field device 112a, for example. A process variable (PV) value is extracted from data containing. Display interface 808 can then display field device activity information (eg, PV values, measurement information, monitoring information, etc.).

To detect the status of field device 112a, labeler 214 is provided with a field device status detector 812. Field device status detector 812 detects status information associated with field device 112a (e.g., device on, device off, device error, device alarm, device health (open loop, short, etc.), device communication status, etc.). Communications processor 804 is configured to extract from data received from termination module 124a and/or field device 112a. In some embodiments, the status information includes information based on data obtained via fieldbus diagnostic analyzer 624 (FIG. 6). Display interface 808 may then display the received status information.

To identify field device 112a, labeler 214 is provided with field device identifier 814. Field device identifier 814 is configured to extract field device identification information (e.g., device tag value, device name, electronic serial number, etc.) from data received from termination module 124a and/or field device 112a by communication processor. It is composed of Display interface 808 can then display field device identification information. In an example implementation, field device identifier 814 may also be configured to detect a field device type (eg, valve actuator, pressure sensor, temperature sensor, flow sensor, etc.). In some examples, field device identifier 814 determines appropriate communication protocols associated with field device 112a in the same or similar manner as field device communication processor 620 described above in connection with FIG. In combination with this, it is configured to be identified.

To identify the data type (eg, analog or digital) associated with field device 112a, labeler 214 is provided with a data type identifier 816. Data type identifier 816 is configured to extract data type identification information from data received by the communications processor from termination module 124a and/or field device 112a. For example, termination module 124a may store a data type descriptor variable indicating the type of field device (e.g., analog, digital, etc.) that termination module 124a is configured to convey. Descriptor variables may be communicated to communications processor 804 of labeler 214 . Display interface 808 can then display the data type. In some examples, data type identifier 816 uses the communication protocol identified by field device identifier 814 to determine the data type associated with field device 112a.

9 relates to the exemplary termination module 124a and termination module 124b of FIG. 1A to electrically isolate the termination modules 124a-b from each other and the field devices 112a-b from the universal I/O bus 136a. 2 shows an isolated circuit configuration that can be implemented as a In the example embodiment, each of termination modules 124a-b includes a respective termination module circuit 902 and termination module circuit 904 (eg, one or more of the blocks described above in connection with FIG. 6). Additionally, termination modules 124a-b are connected to their respective field devices 112a-b via field junction box 120a. Termination modules 124a-b are also connected to universal I/O bus 136a and power supply 216. Termination module 124a is provided with isolation circuitry 906 to electrically isolate termination module circuitry 902 from universal I/O bus 136a. In this manner, the termination module circuit 902 can be used to terminate voltages on the universal I/O bus 136a if a power surge or other power fluctuation occurs at the field device 112a, without affecting the voltage on the universal I/O bus 136a, and on the I/O card 132a ( 1A) and can be configured to follow (eg, float) the voltage level of field device 112a. Termination module 124b also includes isolation circuitry 908 configured to isolate termination module circuitry 904 from universal I/O bus 136a. Isolation circuit 906, isolation circuit 908, and other isolation circuits implemented in termination modules 124a-b may be implemented using opto-isolation circuits or galvanic isolation circuits.

To isolate termination module circuitry 902 from power supply 216, termination module 124a is provided with isolation circuitry 910. Similarly, termination module 124b is provided with an isolation circuit 912 that isolates termination module circuitry 904 from power supply 216. By isolating termination module circuit 902 and termination module 904 from power supply 216, power fluctuations (eg, power surges, current spikes, etc.) associated with field devices 112a-b do not damage power supply 216. Also, power fluctuations in one of termination modules 124a-b do not damage or affect the operation of the other termination module 124a-b.

In known process control systems, isolation circuits are provided within known marshalling cabinets, thereby reducing the amount of space available for known termination modules. However, as shown in the exemplary embodiment of FIG. reduces the amount of space required within marshalling cabinet 122 (FIGS. 1A and 2) and, therefore, the amount of space that can be used for termination modules (e.g., termination modules 124a-c and termination modules 126a-c). increase. In addition, implementing isolation circuits (e.g., isolation circuits 906, 908, 910, and 912) within termination modules (e.g., termination modules 124a-b) allows isolation circuits to be selected only in termination modules where isolation is required. to enable it to be used. For example, some of the termination modules 124a-c and termination modules 126a-c of FIG. 1A can be implemented without isolation circuitry.

10A, FIG. 10B, FIG. 11A, FIG. 11B, FIG. 12, and FIG. ), an I/O card (e.g., I/O card 132a of FIGS. 1A and 7), and a labeler (e.g., labeler 214 of FIGS. 2, 3, and 8). 1 is a flowchart of an exemplary method for obtaining. In some example implementations, the example methods of FIGS. The program may be implemented using machine-readable instructions, comprising a program executed by a processor 1612). program, CD-R
OM, a floppy disk, a hard drive, a digital versatile disk (DVD), or in software stored on a tangible medium such as a memory associated with the processor 1612 and/or in well-known manner, firmware and/or Or it can be implemented with dedicated hardware. Further, while the example program is described with reference to the flowcharts illustrated in FIGS. Those skilled in the art will readily appreciate that many other methods of implementing the example termination module 1332a, the example I/O card 132a, and the example labeler 214 can alternatively be used. to understand. For example, the order of execution of the blocks may be changed and/or some of the described blocks may be changed, deleted, or combined.

10A and 10B, the example method of FIGS. 10A and 10B is described in conjunction with the example termination module 124a of FIGS. 1A, 2, and 4-6. I will explain. However, other termination modules can be implemented using the example method of FIGS. 10A and 10B. The flowcharts of FIGS. 10A and 10B are used to describe how exemplary termination module 124a communicates information between field device 112a and I/O card 132a. Initially, termination module 124a determines whether it has received communication information (block 1002). For example, termination module 124a receives communication information if I/O bus communication processor 608 (FIG. 6) or field device communication processor 620 indicates that the communication information has been received, e.g., via an interrupt or status register. I judge that I did. If termination module 124a determines that communication information has not been received (block 1002), control remains at block 1002 until termination module 124a receives communication information.

If termination module 124a receives communication information (block 1002), termination module 124a determines whether it received communication information from a field device (e.g., field device 112a of FIG. 1A), e.g., by a field device communication processor. A determination is made (block 1004) based on the interrupt or status register at 620 (FIG. 6). If termination module 124a determines that it has received communication information from field device 112a (block 1004), field device communication processor 620 transmits the field device information and field device identification information to the received communication information associated with field device 112a. The communication information is extracted based on the field device communication protocol (block 1006). Field device information may include, for example, field device identification information (e.g., device tag, electronic serial number, etc.), field device status information (e.g., communication status, diagnostic health information (open loop, short, etc.)), field device activity. information (e.g., process variable (PV) values), field device descriptive information (e.g., field device type or function, such as a valve actuator, temperature sensor, pressure sensor, flow sensor, etc.), field device connection configuration information (e.g., , multidrop bus connections, point-to-point connections, etc.); field device bus or segment identification (e.g., a field device bus or field device segment through which the field device is communicatively coupled to the termination module); and/or field device data type information (e.g., analog in (AI) data type, analog out (AO) data type, discrete in (DI) data type (e.g., digital in data type), discrete out (DO) data type) (e.g., digital out data type), etc.). The field device communication protocol may include any protocol used by the field device 112a (e.g., Fieldbus protocol (e.g., FF-H1), HART protocol, AS-I protocol, Profibus protocol (e.g., Profibus PA)).
), etc.). In an alternative example implementation, at block 1006, field device communications processor 620 extracts only field device information from the received communication information, and field device identification information identifying field device 112a is stored in termination module 124a. is memorized. For example, when field device 112a is first connected to termination module 124a, field device 112a can communicate its identification information to termination module 124a, and termination module 124a can store the identification information.

Field device communications processor 620 then determines whether analog-to-digital conversion is required (block 1008). For example, if field device 112a communicates an analog measurement, field device communications processor 620 determines that analog-to-digital conversion is necessary or required (block 1008). If analog-to-digital conversion is required, analog-to-digital converter 618 (FIG. 6) performs the conversion on the received information (block 1010).

After analog-to-digital conversion (block 1010), or if analog-to-digital conversion is not required (block 1008), field device communications processor 620 determines the data type (e.g., analog, digital, temperature) associated with the received field device information. measurements, etc.) (block 1012) and generate a data type descriptor corresponding to the received field device information (block 1014). For example, termination module 124a may store a data type descriptor indicating the type of data it always receives from field device 112a, or field device 112a may store a data type descriptor that field device communication processor 620 stores in block 1010. The data type to use to generate the data can be communicated to termination module 124a.

I/O bus communications processor 608 (FIG. 6) determines the destination address for I/O card 132a to which termination module 124a carries information received from field device 112a (block 1016). For example, communications processor 608 (FIG. 6) may obtain the destination address of I/O card 132a from address identifier 604 (FIG. 6). In addition, I/O bus communications processor 608 determines or generates error checking data to communicate to I/O card 132a to ensure that field device information is received by I/O card 132a without error. (Block 1020). For example, I/O bus communications processor 608 may generate cyclic error check (CRC) error check bits.

I/O bus communication processor 608 then converts the field device information, field device identification information, data type descriptor, I/O card 132a destination address, termination module 124a source address, and error check data into the I/O Packetize based on the bus communication protocol (block 1022). I/O bus communication protocols can be implemented using, for example, TPC-based protocols, UDP-based protocols, and the like. I/O bus communications processor 608 may obtain the source address of termination module 124a from address identifier 604 (FIG. 6). I/O bus interface 602 (FIG. 6) then transmits the packetized information via universal I/O bus 136a (FIGS. 1A and 2) to other termination modules (e.g., termination module 124b and FIG. 1A of FIG. 1A). along with the packetization information generated and conveyed by termination module 124c) (block 1024). For example, I/O bus interface 602 communicates information from termination module 124a to I/O card 132a when universal I/O bus 136a is available (e.g., not being used by termination modules 124b-c). ) An arbitration circuit or device may be provided that intercepts or monitors the universal I/O bus 136a to determine when.

If termination module 124b determines at block 1004 that the communication information detected at block 1002 is not from field device 112a (eg, the communication information is from I/O card 132a), then I/O bus communication processor 608 (FIG. 6) extracts the destination address from the received communication information (block 1026). I/O bus communications processor 608 then determines whether the extracted destination address matches the destination address of termination module 124a obtained from address interface 604 (block 1028). If the destination address does not match the address of termination module 124a (eg, the received information was not intended to be delivered to termination module 124a) (block 1028), control returns to block 1002 (FIG. 10A). Otherwise, if the destination address matches the address of termination module 124a (e.g., the received information was to be delivered to termination module 124a) (block 1028), I/O bus communications processor 608 Device information is extracted from the received communication based on the I/O bus communication protocol (block 1030) and data integrity is determined using, for example, a CRC verification process based on error detection information in the received communication. and verify (block 1032). Although not shown, if I/O bus communications processor 608 determines that an error exists in the received communications at block 1032, I/O bus communications processor 608 requests retransmission and sends the message. It is transmitted to the I/O card 132a.

After verifying data integrity (block 1032), I/O bus communications processor 608 (or field device communications processor 620) determines whether digital-to-analog conversion is required (block 1034). For example, if the data type descriptor stored within termination module 124a indicates that field device 112a requires analog information, I/O bus communications processor 608 determines that digital-to-analog conversion is required ( block 1034). If digital-to-analog conversion is required (block 1034), digital-to-analog converter 616 (FIG. 6) performs digital-to-analog conversion on the field device information (block 1036). After performing the digital-to-analog conversion (block 1036), or if digital-to-analog conversion is not required (block 1034), field device communications processor 620 transmits field device information to field device 112a via field device interface 622 (FIG. ) using the field device communication protocol of the field device 112a (block 1038).

After field device communication processor 620 communicates field device information to field device 112a, or after I/O bus communication processor 608 communicates field device information to I/O card 132a, the process of FIGS. 10A and 10B continues. Termination and/or control is returned to the calling process or function, for example.

11A and 11B illustrate a flowchart of an example method that may be used to implement I/O card 132a of FIG. 1A to convey information between termination module 124a and controller 104 of FIG. 1A. ing. First, I/O card 132a determines whether it has received communication information (block 1102). For example, the I/O card 132a determines that the communication information has been received if the communication processor 704 (FIG. 7) indicates, eg, via an interrupt or status register, that the communication information has been received. If the I/O card 132a determines that it has not received the communication information (block 1102), control remains at block 1102 until the I/O card 132a receives the communication information.

If the I/O card 132a receives communication information (block 1102), the I/O card 132a determines whether it received the communication information from the controller 104 (FIG. 1A), for example, via an interrupt of the communication processor 704 or A determination is made based on the status register (block 1104). If I/O card 132a determines that it has received communication information from controller 104 (block 1104), communication processor 704 transmits termination module information (which may include field device information) associated with termination module 124a. Extract from the received communication information (block 1106).

Communications processor 704 identifies data types (e.g., field device analog information, field device digital information, termination module control information for controlling or configuring the termination module, etc.) associated with the received termination module information (block 1108). ), generate a data type descriptor corresponding to the received termination module information (block 1110). In an alternative example implementation, data type descriptors are generated at workstation 102 (FIG. 1A) and communications processor 704 is not required to generate data type descriptors.

I/O bus communications processor 712 (FIG. 7) then determines the destination address of termination module 124a (block 1112). In addition, I/O bus communications processor 712 determines error checking data to convey along with the termination module information to termination module 124a to ensure that termination module 124a receives the information without error (block 1114). For example, I/O bus communications processor 712 may generate cyclic error check (CRC) error check bits.

I/O bus communication processor 712 then converts the termination module information, data type descriptor, destination address of termination module 124a, source address of termination module 124a, and error checking data into packets based on the I/O bus communication protocol. (block 1116). I/O bus interface 710 (FIG. 7) then transmits the packetized information to other termination modules (e.g., termination module 124b and FIG. 1A of FIG. 1A) via universal I/O bus 136a (FIGS. 1A and 2). along with packetization information destined for the termination module 124c (block 1118). For example, I/O bus communications processor 704 may packetize other termination module information using, for example, the destination addresses of termination module 124b and termination module 124c, and may packetize the termination module information for all of termination modules 124a-c. Information may be conveyed via universal I/O bus 136a using the RS-485 standard. Each of termination modules 124a-c may extract its respective information from universal I/O bus 136a based on the destination address provided by I/O card 132a.

If the I/O card 132a determines at block 1104 that the communication information detected at block 1102 is not from the controller 104 (eg, the communication information is from one of the termination modules 124a-c); I/O bus communications processor 712 (FIG. 7) extracts a source address (eg, the source address of one of termination modules 124a-c) from the received communications information (block 1122). I/O bus communications processor 712 then extracts data type descriptors (eg, digitally encoded analog data type, digital data type, temperature data type, etc.) (block 1124). The I/O bus communication processor 712 also extracts termination module information (which may include field device information) from the received communication information based on the I/O bus communication protocol (block 1126) and determines data integrity. is verified using, for example, a CRC verification process based on error detection information in the received communication (block 1128). Although not shown, if I/O bus communications processor 712 determines at block 1128 that an error exists in the received communications, I/O bus communications processor 712 sends a retransmission request message at block 1122. Send to the termination module associated with the obtained source address.

After verifying data integrity (block 1128), communications processor 704 packetizes the termination module information (using the termination module's source address and data type descriptor), and communications interface 702 packetizes the termination module information (using the termination module's source address and data type descriptor). The controller 104 is communicated (block 1130). If the information is to be delivered to workstation 102, controller 104 may subsequently communicate the information to workstation 102. After communication interface 702 communicates information to controller 104 or after I/O bus interface 710 communicates termination module information to termination module 124a, the process of FIGS. 11A and 11B ends and/or control is terminated. , for example, returning to the calling process or function.

FIG. 12 illustrates reading information associated with a field device (e.g., field device 112a of FIG. 1A) communicatively coupled to a termination module (e.g., termination module 124a of FIGS. 1, 2, and 4-6). , is a flowchart of an example method that may be used to implement the labeler 214 of FIGS. 2, 3, and 8. Initially, connection detector 806 (FIG. 8) indicates that a field device (e.g., field device 112a) is connected to termination module 124a (e.g., termination screw 406 of FIGS. 4 and 5 and/or (block 1202). If the connection detector 806 determines that the field device 112a (or other field device) is not connected to the termination module 124a (block 1202), control determines that the connection detector 806 determines that the field device 112a (or other field device) is not connected to the termination module 124a (block 1202). The process remains at block 1202 until it determines that a field device (field device) is connected to termination module 124a.

If connection detector 806 determines that field device 112a is connected to termination module 124a (block 1202), field device identifier 814 includes field device identification information (e.g., a device tag value) that identifies field device 112a. , device name, electronic serial number, etc.) (block 1204). For example, field device identifier 814 sends a query to field device 112a requesting field device 112a to send its field device identification information. In another example implementation, after an initial connection to termination module 124a, field device 112a may automatically communicate its field device identification information to field device identifier 814.

Field device identifier 814 then determines whether field device 112a is assigned to communicate with I/O card 132a via universal I/O bus 136a based on the field device identification information (block 1206). For example, field device identifier 814 may communicate field device identification information to I/O card 132a via termination module 124a, and I/O card 132a may communicate field device identification information to storage within workstation 102. data structure 133 (FIG. 1A) or a similar data structure. To data structure 133, an engineer, operator, or user adds a field device identification number for a field device (e.g., field devices 112a-c) that is communicated to I/O card 132a via universal I/O bus 136a. be able to. If I/O card 132a determines that field device 112a is assigned to I/O bus 136a and/or I/O card 132a, I/O card 132a sends a confirmation message to field device identifier 814. tell.

If field device identifier 814 determines that field device 112a is not assigned to communicate via I/O bus 136a (block 1206), display interface 808 (FIG. 8) displays an error message. (Block 1208). Otherwise, display interface 808 displays field device identification information (block 1210). In the illustrated example, field device status detector 812 detects field device status (eg, device on, device off, device error, etc.) and display interface 808 displays status information (block 1212). Additionally, field device activity detector 810 (FIG. 8) detects activity (eg, measurement and/or monitoring information) of field device 112a, and display interface 808 displays the activity information (block 1214). Data type detector 816 (FIG. 8) also detects the data type (eg, analog, digital, etc.) of field device 112a, and display interface 808 displays the data type (block 1216).

After display interface 808 displays an error message (block 1208) or after display interface 808 displays a data type (block 1216), labeler 214 determines whether it should continue monitoring, e.g., termination module 124a. is turned off or unplugged from marshalling cabinet 122 (FIGS. 1A and 2) (block 1218). If labeler 214 determines that it should continue monitoring, control is returned to block 1202. Otherwise, the example process of FIG. 12 terminates and/or control returns to the calling process or function.

13A-13B illustrate an example process before and after implementing the teachings disclosed herein for an example Profibus PA process area 1302 and an example FOUNDATION fieldbus H1 (FF-H1) process area 1304. 13 is a block diagram showing a control system 1300. FIG. Although it may not be common for a process control system to include a Profibus PA process area and a FOUNDATION fieldbus process area, both are shown in the illustrative example for illustrative purposes. Additionally, for purposes of explanation, the same reference numerals are used for common parts described in the example process control system 1300 of FIGS. 13A-13B with respect to the example process control system 100 of FIG. 1A. and explain. Accordingly, in the illustrative example of FIG. 13A, process control system 1300 includes workstation 102 communicatively coupled to controller 1306 via LAN 106. Exemplary controller 1306 can be substantially similar or the same as one of controller 104, controller 152, and controller 162 of FIGS. 1A-1C. Additionally, the example process control system 1300 includes a first process area 114 associated with field devices 112a-c, which is communicatively coupled to termination modules 124a-c within an example marshalling cabinet 1308. There is. An exemplary marshalling cabinet can be substantially similar or the same as any of marshalling cabinet 122 and marshaling cabinet 300 of FIGS. 1A, 2, and 3. Termination modules 124a-c are communicatively coupled to I/O cards 132a-b within controller 1306 via a first universal I/O bus 136a. Additionally, in the example embodiment, marshalling cabinet 1308 includes additional terminations that are substantially similar to or the same as socket rails 202a-b and socket rails 308a-b described above in connection with FIGS. 2 and 3. Includes a socket rail 1310 for receiving a module.

In the example embodiment of FIG. 13A, the example process control system 100 includes field devices 1312a-c and FFs in a Profibus PA process area 1302, implemented using traditional fieldbus architecture and components. - field devices 1314a-c in the H1 process control area 1304 (both Profibus PA and FF-H are protocols related to the family of fieldbus protocols); Accordingly, field devices 1312a-c and field devices 1314a-c are communicatively coupled to controller 1306 via corresponding trunks or segments 1316a-b. Typically, a fieldbus trunk or fieldbus segment is a single twisted pair of wires that carries both digital signals and DC power to connect multiple field devices to a distributed control system (DCS) or other control system host. There are two cables. Due to various constraints, fieldbus segments are typically limited to a maximum length of 1900 meters and can connect up to 16 different field devices. As shown in the example embodiment, segments 1316a-b are communicatively coupled within controller 1306 to corresponding I/O cards 1318a-b and I/O cards 1320a-b. In the illustrated embodiment, each of segments 1316a-b is connected to two I/O cards 1318a-b or I/O cards 1320a-b to provide redundancy. In some embodiments, the I/O cards 1318a-b and/or the I/O cards I1320a-b are remote from each other and/or the I/O cards I1320a-b are remote from each other and/or the I/O cards I1320a-b are remote from each other and/or /O cards 132a-b, and may reside in a different controller.

In the example embodiment of FIG. 13A, segment 1316a corresponding to example Profibus PA process area 1302 is coupled to I/O cards 1318a-b via DP/PA segment coupler 1322. Similarly, segment 1316b corresponding to exemplary FF-H1 process area 1304 is coupled to I/O cards 1320a-b via power supply 1324. In some embodiments, a DP/PA segment coupler 1322 and power supply 1324 provide power regulation functionality to each segment 1316a-b. Additionally, in the example embodiment, the DP/PA segment coupler 1322 and the power supply 1324 each have a respective Coupled to advanced diagnostic modules 1325a-b.

In the illustrated example, field devices 1312a-c and field devices 1314a-c are coupled to corresponding segments 1316a-b via respective spools 1326a-c and spools 1328a-c. In a fieldbus architecture, each spool connects a corresponding field device in parallel to the segment. As a result, in many process control systems shown in the example embodiments, each spool 1326a-c and spool 1328a-c is connected to a corresponding segment 1316a-b by a segment protector 1330a-b (sometimes referred to as a device coupler or field barrier). provides short-circuit protection for shorts in one of field devices 1312a-c and field devices 1314a-c that are coupled together through a short circuit to short the entire segment. In some examples, segment protectors 1330a-b limit the current in each spool 1326a-c and spools 1328a-c (eg, to 40 mA). In some embodiments, segment protectors 1330a-b also function to properly terminate each segment 1316a-b near a field device, while DP/PA segment coupler 1322 and power supply 1324 It functions to terminate segments 1316a-b near the controller. Without proper termination at both ends of segments 1316a-b, communication errors may occur due to signal reflections.

As discussed above, although fieldbus architectures offer many advantages, fieldbus architectures also pose challenges regarding implementation complexity and cost. For example, the complexity of fieldbus systems makes it difficult for engineers to ensure that each segment is properly terminated and protected against short circuits, open circuits, and/or other segment failures. Each segment requires careful design, taking into account the number of devices handled by each segment, the required cable length, and the power requirements involved. In addition to the time and cost of initially configuring such a fieldbus architecture, DP/PA segment couplers 1322 or power supplies 1324, segment protectors 1330a-b, and segment cables (in some cases for redundancy) are required. There are additional costs associated with a number of components associated with such implementations, including the length of cables (including multiple cables) and I/O cards 1318a-b and I/O cards 1320a-b. However, through implementation of the teachings disclosed herein, the design complexity and cost associated with fieldbus system implementation and maintenance is significantly reduced.

FIG. 13B is a block diagram illustrating the example process control system 1300 of FIG. 13A after implementing the teachings disclosed herein. As shown in the example embodiment, spools 1326a-c and spools 1328a-c of field devices 1312a-c and 1314a-c are plugged into sockets on socket rail 1310 of marshalling cabinet 1308, shown in FIG. 13A. , are directly communicatively coupled to each termination module 1332a-f. That is, in contrast to the typical topology of field devices in multi-drop architectures, in the example embodiment each Fieldbus-compliant field device 1312a-c and Fieldbus-compliant field device 1314a-c is connected to each termination module 1332a-f. There is point-to-point communication. Termination modules 1332a-f provide communication between field devices 1312a-c and field devices 1314a-c and I/O cards 132a-b in the same manner as described above via universal I/O bus 136a. The termination modules 124a-c and 126a-c described above may be substantially similar or the same as the termination modules 124a-c and 126a-c described above. In this manner, separate I/O cards 1318a-b and I/O cards specific to the corresponding fieldbus protocol (e.g., Profibus PA or FF-H1) associated with process area 1302 and process area 1304 are provided. 1320a-b (FIG. 13A), any type of field device and associated I/O can be combined within one marshalling cabinet 1308. Similarly, the need for cable trunks or segments 1316a-b (FIG. 13A) is eliminated along with the associated insulation. Additionally, in some embodiments, the universal I/O bus 136a can be used for even faster communications than the relatively slow communications backbone of typical copper-based fieldbus segments (e.g., via fiber optic cables). ) provide a high-speed communications backbone. Additionally, in some embodiments, universal I/O bus 136a can sustain communications for up to 96 field devices, whereas regular fieldbus segments are limited to connecting 16 devices. ing. Therefore, the number of wires coupled to the controller for the same number of field devices is significantly reduced.

Multiple field devices may be configured in a multi-drop configuration communicatively coupled to one termination module 1332a-f, common in fieldbus architectures, in some embodiments, but not shown in the illustrative embodiment. Point-to-point or single-loop architectures offer several advantages and simplifications over traditional fieldbus configurations. For example, in field devices 1312a-c and field devices 1314a-c, wired as shown in the example embodiment, termination modules 1332a-f provide power and power regulation functions (e.g., in connection with FIG. (via field power controller 610) to each field device. In this way, the separate DP/PA segment coupler 1322 and/or power supply 1324 shown in FIG. 13A is no longer needed. Additionally or alternatively, in some embodiments, marshalling cabinet 1308 includes power conditioner 218 to eliminate the need for separate DP/PA segment coupler 1322 and/or power supply 1324 shown in FIG. 13A. (FIG. 2). Additionally, in such embodiments, the power supply is local to the field device in the example embodiment (e.g., within the marshaling cabinet 1308), so that the power requirements are limited to the power supply that provides power along the normal fieldbus segment. (e.g. due to voltage drop resulting from cable length). Additionally, in some embodiments, termination modules 1332a-f provide short circuit protection (e.g., via a corresponding field power controller 610) to reduce current flow between each spool 1326a-c and spools 1328a-c. limiting, thereby eliminating the need for separate segment protectors 1330a-b.

In addition, individually coupling field devices 1312a-c and field devices 1314a-c to separate termination modules 1332a-f provides single-loop compatibility and allows for proper termination in typical fieldbus architectures. Make your concerns less of a concern. Additionally, direct point-to-point connections between each field device 1312a-c and field device 1314a-c and a corresponding termination module 1332a-f are complicated by the complexities associated with developing and implementing typical fieldbus segments. and design effort, since the signals from each field device are received separately and handled or organized electronically at the back end. Accordingly, the cost of acquiring, configuring, and maintaining the many components of typical fieldbus architectures, and the time and expense of designing such architectures and ensuring their proper operation, are not disclosed herein. This can be significantly reduced through the implementation of teachings. In other words, in some embodiments, fieldbus-compliant devices may be placed into a process control system without any DP/PA couplers and/or power supplies on the segment (e.g., within marshalling cabinet 122 and/or termination). (other than power supplies and/or power conditioners within modules 1332a-f), without segment protectors, without protocol-specific I/O cards, and without significant segment design effort.

Additionally, in some embodiments, termination modules 1332a-f may provide advanced diagnostics (e.g., via fieldbus diagnostic analyzer 624 of FIG. 6) without separate advanced diagnostic modules 1325a-b. can. Further, in some embodiments, the diagnostics performed by termination modules 1332a-f can be more reliable and/or robust than known advanced diagnostic modules, which may This is because modules 1332a-f only need to monitor one field device via a point-to-point connection, rather than multiple devices on a typical fieldbus segment.

Profibus PA and FF-H1 are both fieldbus protocols with the same physical layer. Thus, in some embodiments, termination modules 1332a-c associated with field devices 1312a-c in Profibus PA process area 1302 are termination modules 1332d associated with field devices 1314a-c in FF-H1 process area 1304. It is the same as ~f. In other words, in some embodiments, spools 1326a-c connected to termination modules 1332a-c may be connected to termination modules 1332d-f, while spools 1328a-c are connected to termination modules 1332d-f instead of termination modules 1332d-f. Connected to termination modules 1332a-c. In some such embodiments, termination modules 1332a-f are configured to implement a particular protocol (e.g., , Profibus PA or FF-H1). As a result, process control system engineers do not have to worry about having to design separate fieldbus segments or obtain the corresponding components necessary to implement such fieldbus segments. In addition, you are free to use any desired fieldbus device, regardless of the associated communication protocol (you can even mix devices that comply with different protocols).

In some examples, termination modules 1332a-f are inherently safe (e.g., Fieldbus Intrinsically
Safe Concept (FISCO) compliant). In such embodiments, the socket rail 1310 of the marshalling cabinet 1308 is also inherently secure. In some embodiments, termination modules 1332a-f are energy limited certified and/or made with a safety rating sufficient to meet the Fieldbus Non-Incendive Concept (FNICO). In some such embodiments, termination modules 1332a-f may comply with FNICO requirements even when plugged into a marshalling cabinet that has an inherently unsafe socket rail.

Additionally or alternatively, in some embodiments, the termination modules described herein can communicate with field devices based on communication protocols other than Profibus PA or FF-H1 (e.g., other than Profibus PA or FF-H1). Made to communicate. For example, in some embodiments, a termination module can be hardwired to a wireless HART gateway to interface with one or more wireless HART devices using the HART-IP application protocol. Additionally or alternatively, in some embodiments, the wireless device is ISA (International Society of Instrument and Control Engineers) 100.11a or WIA-PA (Wireless Networks for
Other wireless technology standards such as Industrial Automation--Process Automation) may be used to interface. In some embodiments, the termination module described herein provides a device with an Internet Protocol (IP) based interface, such as using the 6TiSCH standard (IP version 6 over Time Slotted Channel Hopping (TSCH)). can be made to interface using a protocol. In some embodiments, the termination module interfaces to the device using the Message Queue Telemetry Transport (MQTT) protocol. Additionally, in some embodiments, safety field devices may be integrated using a tunnel protocol between the safety environment and an associated safety controller, such as, for example, PROFIsafe (Profibus safety equipment).

14A and 14B illustrate an alternative exemplary implementation of peer-to-peer communication of two FF-H1 compliant field devices 1402a-b communicatively coupled to corresponding termination modules 1404a-b. Exemplary termination modules 1404a-b can be substantially similar or the same as termination modules 1332a-f described above. Although peer-to-peer communication between devices in the field is not provided using the Profibus PA fieldbus protocol, such communication is possible when using the FF-H1 protocol, thereby Allows for in-field control independent of a controller (eg, controller 1306 in FIG. 13A). In the example embodiment of FIG. 14A, termination modules 1404a-b are substantially similar to base 402 (FIG. 4), except that bases 1406a-b are shown with four corresponding terminals 1408a-b. or the same, are coupled to corresponding terminal block bases 1406a-b. In the illustrated example, a pair of wires for each spool 1410a-b corresponding to a field device 1402a-b is connected to a first pair of terminals 1408a-b, while a pair of wires from each base 1406a-b is connected to a first pair of terminals 1408a-b. Corresponding ones of the second pair of terminals 1408a-b are coupled together. In this manner, both field devices 1402a-b are communicatively coupled to each of termination modules 1404a-b and to each other.

Directly coupling separate field devices 1402a-b to each of termination modules 1404a-b is possible, as shown in the example embodiment of FIG. This is because coordination functionality is provided to each field device 1402a-b (eg, via field device controller 610). That is, the power regulation provided by each termination module 1404a-b ensures that a signal from one of the field devices (e.g., field device 1402a) is unable to communicate with the other field device (e.g., field device 1402b). Its role is to prevent interference. However, as explained above, in some embodiments, power regulation is provided collectively (e.g., via injected power) to all of the field devices on the same socket rail by another power regulator 218. be done. In some such embodiments, field devices 1402a-b are communicatively coupled to termination modules 1404a-b via segment protectors 1412, as illustrated in FIG. 14B. That is, each field device 1402a-b is still associated with a corresponding termination module 1404a-b, but peer-to-peer communication between field devices 1402a-b is accomplished through the segment protector 1412. Further, segment protector 1412 prevents power provided through termination module 1404a-b corresponding to each field device 1402a-b from affecting communications of any of field devices 1402a-b. In the example embodiments of FIGS. 14A and 14B, additional wiring (eg, for shielding and/or grounding) has been omitted for clarity.

The example method of FIG. 15 will be described in conjunction with the example termination module 1332a of FIG. 13B. However, other termination modules can be implemented using the example method of FIG. 15. How an example termination module 1332a automatically detects a communication protocol associated with a corresponding field device (e.g., field device 1312a) connected to the termination module 1332a using the flowchart of FIG. Explain. Initially, termination module 1332a determines (eg, via connection detector 806 of FIG. 8) whether a field device (eg, field device 1312a) is connected to termination module 1332a (block 1502). If the termination module 1332a determines that the field device 1312a (or other field device) is not connected to the termination module 1332a (block 1502), control controls whether the termination module 1332a is connected to the field device 1312a (or other field device). ) remains at block 1502 until it determines that the termination module 1332a is connected to the termination module 1332a.

If termination module 1332a determines that field device 1312a is connected to termination module 1332a (block 1502), termination module 1332a initiates a first communication (e.g., via field device communications processor 620 of FIG. 6). A request formatted according to a protocol (eg, Profibus PA) is sent (block 1504). In some examples, the request may correspond to a query requesting a field device to transmit its field device identification information, as described above in connection with block 1204 of FIG. 12. Termination module 1332a then determines whether a response to the request has been received (block 1506). As discussed above in connection with block 1504, the request is formatted corresponding to a particular protocol. As a result, the only way field device 1312a can recognize and therefore respond to the request is if field device 1312a is associated with the same protocol. Accordingly, if termination module 1332a determines that a response has been received (block 1506), termination module 1332a designates the communication protocol of the responded request as the protocol corresponding to field device 1312a (block 1506). For example, if the first request is formatted according to the Profibus PA protocol and a response to the request is received, then the communication protocol corresponding to field device 1312a is designated as Profibus PA.

If termination module 1332a determines at block 1506 that a response to the request has not been received, termination module 1332a (e.g., via field device communication processor 620) uses another communication protocol (e.g., FF-H1 ) (block 1508). Termination module 1332a then determines whether a response to the request has been received (block 1510). If termination module 1332a determines that a response to the request has been received (block 1510), termination module 1332a designates the communication protocol of the responded request as the protocol corresponding to field device 1312a (block 1516). If termination module 1332a determines that a response to the request has not been received (block 1510), termination module 1332a determines that an additional communication protocol to try (e.g., other than Profibus PA and FF-H1 (e.g., HART)) determine whether there is. If there are additional communication protocols, control returns to block 1508 to send another request formatted according to the other communication protocol. If termination module 1332a determines that there are no additional communication protocols to try, termination module 1332a generates an error message (block 1514). For example, the error message may indicate that field device 1312a is not responding and/or that a communication protocol corresponding to field device 1312a cannot be identified.

After termination module 1332a generates an error message (block 1514) or specifies the communication protocol of the responded request as the protocol corresponding to field device 1312a (block 1516), the process of FIG. 15 ends, and /or control is returned to the calling process or function, for example.

FIG. 16 is a block diagram of an example processor system 1610 that may be used to implement the apparatus and methods described herein. For example, using a processor system that is similar or the same as exemplary processor system 1610, workstation 102, controller 104, I/O card 132a, and/or termination modules 124a-c and termination module 126a of FIG. ~c can be implemented. An example processor system 1610 is described below as including multiple peripherals, interfaces, chips, memory, etc., one or more of which may include workstation 102, controller 104, /O card 132a and/or other exemplary processor systems used to implement one or more of termination modules 124a-c and termination modules 126a-c.

As shown in FIG. 16, processor system 1610 includes a processor 1612 coupled to an interconnect bus 1614. Processor 1612 includes a register set or register space 1616, which is illustrated as being completely on-chip in FIG. , via dedicated electrical connections and/or via interconnect bus 1614. Processor 1612 can be a suitable processor, processing unit, or microprocessor. Although not illustrated in FIG. 16, system 1610 can be a multi-processor system, and thus has one or more processors the same or similar to processor 1612 and communicatively coupled to interconnect bus 1614. may include additional processors.

Processor 1612 in FIG. 16 is coupled to a chipset 1618 that includes a memory controller 1620 and a peripheral input/output (I/O) controller 1622. As is well known, a chipset typically provides I/O management functions, memory management functions, and multiple general purpose and/or or provide special purpose registers, timers, etc. Memory controller 1620 performs the functions of allowing processor 1612 (or multiple processors, if there is multiple processors) to access system memory 1624 and mass storage memory 1625.

System memory 1624 may include any desired type of volatile and/or non-volatile memory, such as, for example, static random access memory (SRAM), dynamic random access memory (DRAM), flash memory, read only memory (ROM), etc. can include. Mass storage memory 1625 may include any desired type of mass storage device. For example, when exemplary processor system 1610 is used to implement workstation 102 (FIG. 1A), mass storage memory 1625 may include a hard disk drive, an optical drive, a tape storage device, or the like. Alternatively, the example processor system 1610 may be used to configure the controller 104, one of the I/O cards 132a-b and the I/O cards 134a-b, or the termination modules 124a-c and the termination module 126a. -c, the mass storage memory 1625 may include semiconductor memory (e.g., flash memory, RAM memory, etc.), magnetic memory (e.g., hard drive), or other suitable mass storage. Memory may be included within controller 104, I/O cards 132a-b and I/O cards 134a-b, or termination modules 124a-c and termination modules 126a-c.

Peripheral I/O controller 1622 allows processor 1612 to control peripheral input/output (I/O) devices 1626, peripheral input/output (I/O) devices 1628, network interface 1630, and peripheral I/O bus. 1632. I/O devices 1626 and I/O devices 1628 may include, for example, keyboards, displays (e.g., liquid crystal displays (LCDs), cathode ray tube (CRT) displays, etc.), navigation devices (e.g., mice, trackballs, capacitive touch pads, etc.). , joystick, etc.). Network interface 1630 can be, for example, an Ethernet device, asynchronous transfer mode (ATM) device, 802.11 device, DSL modem, cable modem, cellular modem, etc., that allows processor system 1610 to communicate with other processor systems. can be.

Although memory controller 1620 and I/O controller 1622 are shown in FIG. 16 as independent functional blocks within chipset 1618, the functions performed by these blocks can be incorporated within a single semiconductor circuit; or can be implemented using two or more separate integrated circuits.

Although particular methods, apparatus, and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. To the contrary, this patent covers all methods, apparatus, and articles of manufacture that may fairly fall within the scope of the appended claims, either literally or under the doctrine of equivalents.

Claims (20)

termination panel,
a shared bus on the termination panel; and a plurality of bases along the shared bus on the termination panel, each of the plurality of bases removably receiving a module for communicating with a field device. have,
Each of the plurality of bases is
a first physical interface communicatively coupled to said field devices of different types for exchanging communications with one or more of said field devices via a plurality of different communication protocols, wherein each module a first physical interface that automatically detects a communication protocol of a field device; and a first physical interface that communicatively couples the removably receivable module to the shared bus and communicates with a controller via the shared bus. 2 physical interface,
A device comprising: 2. The apparatus of claim 1, wherein the second physical interface communicatively couples the removably receivable module to an input/output card within the controller. 2. The first physical interface of claim 1, wherein the first physical interface is operable as a digital interface for a first of the modules and operable as an analog interface for a second of the modules. Device. 2. The apparatus of claim 1, wherein the different types of field devices include valves, actuators, and sensors. 2. The apparatus of claim 1, wherein each of the bases is configured to receive a different type of the module. 6. The apparatus of claim 5, wherein the different types of modules include analog input modules, analog output modules, digital input modules and digital output modules. a base for removably receiving selectable modules from different types of modules for communicating with different types of field devices;
a first physical interface for communicatively coupling the module to at least one of the different types of field devices, the module automatically detecting a communication protocol of the respective field device; 1 physical interface;
a second physical interface for communicatively coupling the module to a controller, wherein insertion of the module into the base creates a connection between the module and the first and second physical interfaces; a base having a second physical interface;
a shared bus for communicating between the controller, the base, and a plurality of second bases communicating with the shared bus; a transceiver communicatively coupled to a base of 2 for exchanging communications between the shared bus and the controller;
system with. 7. The first physical interface exchanges information between any of the different types of modules and one or more of the different types of field devices using a plurality of different communication protocols. system described in. 9. The system of claim 8, wherein the information is at least one of temperature measurement information, pressure measurement information, fluid flow measurement information, or valve actuator control information. 8. The system of claim 7, wherein the transceiver is configured to communicate with an input/output card of the controller. 8. The system of claim 7, wherein the transceiver is configured to communicate with the controller via an Ethernet protocol. 8. The system of claim 7, wherein the transceiver is a wireless transceiver. 8. The system of claim 7, wherein the base is configured to be removably attached to a socket rail to communicatively couple the base to the transceiver. a base removably receiving selectable modules from different types of modules for communicating with different types of field devices, the base automatically detecting a communication protocol of the respective field device;
first and second physical interfaces, the first physical interface communicatively coupling the module to at least one of the different types of field devices, and the second physical interface comprising: first and second physical interfaces communicatively coupling the module to a controller;
a shared bus for communicating with the base and a plurality of second bases, the shared bus for communicating between the controller, the base, and the plurality of second bases; a transceiver communicatively coupled to the base and the plurality of second bases via a transceiver for exchanging communications between the shared bus and the controller;
system with. 15. The first physical interface exchanges information between any of the different types of modules and one or more of the different types of field devices using a plurality of different communication protocols. system described in. 16. The system of claim 15, wherein the information is at least one of temperature measurement information, pressure measurement information, fluid flow measurement information, or valve actuator control information. 15. The system of claim 14, wherein the transceiver is configured to communicate with an input/output card of the controller. 15. The system of claim 14, wherein the transceiver is configured to communicate with the controller via an Ethernet protocol. 15. The system of claim 14, wherein the transceiver is a wireless transceiver. 15. The system of claim 14, wherein the base is configured to be removably attached to a socket rail to communicatively couple the base to the transceiver.