JP2016129025A - Apparatus and methods to communicatively couple field devices to controllers in process control system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an apparatus for communicatively coupling a field device to a process controller.SOLUTION: A first interface communicates using a first fieldbus communication protocol when coupled to a 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 in order to encode first information, received from one of the first and second field devices, for communication via a bus using a third communication protocol, and communicate the first information to a controller in a process control system. The bus uses the third communication protocol to communicate second information, received from the other of the first and second field devices.SELECTED DRAWING: Figure 1A

Description

  The present disclosure relates generally to process control systems, and more specifically to an apparatus and method for communicatively coupling a field device to a controller of a process control system.

  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 analog, digital, or analog / One or more process controllers communicatively coupled to one or more field devices configured to communicate via a digital composite communication protocol. For example, field devices, which may be device controllers, valves, valve actuators, valve positioners, switches and transmitters (eg, temperature sensors, pressure sensors, flow sensors, and chemical composition sensors), or combinations thereof, within a process control system Perform functions such as opening and closing valves and measuring or inferring process parameters. The process controller receives signals indicating process measurements made by the field device and / or other information about the field device and uses this information to implement control routines via the bus or other communication line Control signals sent to the field devices are generated to control the operation of the process control system.

  Process control systems provide several different functions and can be point-to-point (eg, one field device is communicatively coupled to a field device bus) or multi-drop (eg, multiple field devices are fielded). Including a plurality of field devices that are often communicatively coupled to the process controller using a two-wire interface in a wired connection configuration (communicatively coupled to the device bus) or using wireless communication Can do. Some field devices are configured to operate using relatively simple commands and / or communications (eg, ON commands 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 can communicate analog values with digital communications superimposed on the analog values using, for example, the Highway Addressable Remote Transducer (“HART”) communication protocol. Other field devices can use fully digital communication (eg, 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 respective communication media (eg, two-wire cable, wireless link, or optical fiber). Yes. Accordingly, multiple communication media are required to communicatively couple multiple field devices to the process controller. Often, multiple communication media coupled to a field device are wired through one or more field junction boxes, where multiple communication media connect the field device to the process controller with one or more I's. It is connected to each communication medium (for example, each two-wire conductor) of a multi-core cable used for communication connection via the / O card.

  An exemplary 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 is connected via a bus to 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 the controller of the process control system. And a second physical interface communicatively coupled. 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, an example method communicatively couples first information to one of a first field device of a process control system or a second field device of a process control system. Receiving at the base with the first physical interface. The exemplary method also involves encoding first information for communicating using a first communication protocol in a module removably attached to the base. First information communicated to the module using the second communication protocol from the first field device 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 different from the first and second communication protocols. The method further involves communicating the encoded first information from the module through the base second physical interface to the controller via the bus using the first communication protocol.

  According to yet another embodiment, the example apparatus is configured to communicate with a first interface device of the process control system or a second field device of the process control system. including. The first interface communicates using the first fieldbus communication protocol when coupled to the first field device and communicates with the second fieldbus communication protocol when coupled to the second field device. Use to communicate. An exemplary apparatus includes a communication processor communicatively coupled to a first interface. The communication processor is one of the first field device or the second field device for communication over a bus using a third communication protocol different from the first and second fieldbus communication protocols. The first information received from one is encoded. The example apparatus includes a second information communicatively coupled to the communication processor and the bus for communicating the first information to the controller of the process control system via the bus using a third communication protocol. Includes an interface. The bus communicates second information received from the other of the first field device or the second field device using a third communication protocol.

1 is a block diagram illustrating an example process control system. FIG. FIG. 4 is an alternative exemplary implementation that may be used to communicatively couple a workstation, a controller, and an I / O card. FIG. 4 is an alternative exemplary implementation that may be used to communicatively couple a workstation, a controller, and an I / O card. FIG. 4 is an alternative exemplary implementation that may be used to communicatively couple a workstation, a controller, and an I / O card. 1B is a detailed view of the exemplary marshalling cabinet of FIG. 1A. FIG. 1B is another exemplary marshalling cabinet that may be used to implement the exemplary marshalling cabinet of FIG. 1A. FIG. 3 is a plan view and a side view of the exemplary termination module of FIGS. 1A and 2. FIG. 3 is a plan view and a side view of the exemplary termination module of FIGS. 1A and 2. FIG. 14 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. An example 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 It is a detailed block diagram of a simple labeler. 1B is an illustration of an isolation circuit configuration that can be implemented in connection with the exemplary termination module of FIG. 1A to electrically isolate the termination modules from each other, the field devices, and the communication bus. FIG. Examples that can be used to implement the termination modules of FIGS. 1A, 2-6, 13A-13B, and 14A-14B to convey information between a field device and an I / O card. 3 is a flowchart of a typical method. Examples that can be used to implement the termination modules of FIGS. 1A, 2-6, 13A-13B, and 14A-14B to convey information between a field device and an I / O card. 3 is a flowchart of a typical method. 1B is a flowchart of an exemplary method that may be used to implement the I / O card of FIG. 1A to convey information between a termination module and a workstation. 1B is a flowchart of an exemplary method that may be used to implement the I / O card of FIG. 1A to convey information between a termination module and a workstation. An example method that can be used to implement the labelers of FIGS. 2, 3, 6, and 8 to retrieve and display information related to field devices communicatively coupled to a termination module. It is a flowchart. FIG. 7 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. is there. FIG. 7 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. is there. FIG. 6 is an alternative exemplary implementation of peer-to-peer communication of two FF-H1-compliant field devices communicatively coupled to corresponding termination modules. FIG. 6 is an alternative exemplary implementation of peer-to-peer communication of two FF-H1-compliant field devices communicatively coupled to corresponding termination modules. Implement the termination modules of FIGS. 1A, 2-6, 13A-13B, and 14A-14B to automatically detect communication protocols associated with corresponding field devices connected to the termination module. 2 is a flowchart of an exemplary method that may be used for FIG. 2 is a block diagram of an example processor system that may be used to implement the example systems and methods described herein.

  The following describes exemplary devices and systems, including software and / or firmware running on hardware, among other components, but such systems are merely exemplary, It should be noted that it should not be regarded as limiting. For example, some or all of these hardware components, software components, and firmware components may be embodied in hardware alone, software alone, or any combination of hardware and software. Is considered. Accordingly, while the following describes exemplary devices and systems, those skilled in the art will readily appreciate that the examples provided are not the only way to implement such devices and systems.

  An exemplary process control system includes a control room (eg, control room 108 in FIG. 1A), a process controller area (eg, process controller area 110 in FIG. 1A), and a termination area (eg, termination area 140 in FIG. 1A). And one or more process areas (eg, process area 114 and process area 118 of FIG. 1A). The process area includes operations (eg, controlling valves, controlling motors, boilers, etc.) related to performing specific processes (eg, chemical processes, petroleum processes, pharmaceutical processes, pulp and paper processes, etc.). Controlling, monitoring, measuring parameters, etc.). Some process areas are not accessible to humans due to severe environmental conditions (eg, relatively high temperatures, airborne toxins, dangerous radiation levels, etc.). A control room typically includes one or more workstations in an environment that can be safely accessed by humans. The workstation includes a user application that allows a user (eg, engineer, operator, etc.) to access the control operations of the process control system, for example, by changing variable values, process control functions, and the like. The process control area includes one or more controllers communicatively coupled to workstations in the control room. The controller automates control of field devices in the process area by executing a process control strategy implemented via the workstation. An exemplary process strategy involves measuring pressure using a pressure sensor field device and automatically sending commands to a valve positioner that opens and closes a flow valve based on the pressure measurement. The termination area includes a marshalling cabinet that allows the controller to communicate with field devices in the process area. Specifically, the marshalling cabinet organizes the signals from the field devices, organizes them, or transmits them to one or more I / O cards that are communicatively coupled to a controller. Includes modules. The I / O card converts information received from the field device into a format compatible with the controller, and converts information from the controller into a format compatible with the field device.

  A known technique used to communicatively couple field devices in a process control system to a controller is communicatively connected to each field device and controller (eg, process controller, programmable logic controller, etc.). This involves using a separate bus (eg, wire, cable, or circuit) between each connected I / O card. The I / O card allows the controller to have different data types or signal types (eg, analog in (AI) data type, analog out (AO) data type, discrete in (DI) data type, discrete out (DO) data type, Digitally in-data type and digital out-data type) and different field device communication protocols associated with different field devices communication protocol by translating or translating information communicated between the controller and field device Make it possible to do. For example, an I / O card can be provided with one or more field device interfaces configured to exchange information with the field device using a field device communication protocol associated with the field device. Different field device interfaces have different channel types (eg, 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 uses information received from the field device (eg, voltage level) to provide information (eg, pressure) that can be used by the controller to perform operations associated with controlling the field device. Measured value). Known techniques require a bundle of wires or buses (eg, multi-core cables) that 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 exemplary apparatus and method described herein includes a plurality of field devices. Is terminated with a termination panel (for example, a marshalling cabinet), and one bus (for example, a conductive communication medium, an optical communication medium, a wireless communication medium) communicatively coupled between the termination panel and the I / O card is connected. In use, it can be used to communicatively couple the field device to the I / O card by communicatively coupling the field device to the I / O card.

  The exemplary apparatus and methods described herein include an exemplary device that communicatively couples 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 communication bus). Each termination module is communicatively coupled to one or more 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, for example by packetizing the field device information and passing the packetized information to the I / O card via the universal I / O bus, Field device information is transmitted to the I / O card via a universal I / O bus. Field device information includes, for example, field device identification information (eg, device tag, electronic serial number, etc.), field device status information (eg, communication status, diagnostic health information (open loop, short, etc.)), field device activity Information (eg, process variable (PV) values), field device description information (eg, type or function of a field device such as a valve actuator, temperature sensor, pressure sensor, flow sensor, etc.), field device connection configuration information (eg, multi Drop bus connection, point-to-point connection, etc.), field device bus or field device segment identification information (eg, field device is communicatively coupled to the termination module via it) That, field device bus or field device segment), and / or field device data type information (e.g., can include a data type descriptor) indicating the data type used by a particular field device. The I / O card can extract field device information received via the universal I / O bus and communicate the field device information to the controller, which can then send a portion of the information for later analysis. Or all can be communicated to one or more workstation terminals.

  To convey field device information (eg, commands, instructions, queries, threshold activity values (eg, threshold PV value), etc.) from the workstation terminal to the field device, the I / O card packetizes the field device information, Packetized field device information can be communicated to multiple termination modules. Each termination module can then extract each field device information from the packetized communication received from each I / O card, or depacketize it, and pass the field device information to each field device.

  In the exemplary embodiments described herein, a termination panel (eg, a marshalling cabinet) is configured to accept (eg, connect) a plurality of termination modules, each of the plurality of termination modules being a different field device. Are communicatively linked to. In 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. The termination labeler includes an electronic display (eg, a liquid crystal display (LCD)) and components that determine which field devices are connected to the termination module corresponding to the termination labeler. In some exemplary implementations, the display is attached to a termination panel instead of a termination module. Each of the displays is attached in association with each 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 later use by the 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). Workstation 102. The LAN 106 can be implemented using a desired communication medium and protocol. For example, the LAN 106 can be based on a wired or wireless Ethernet communication protocol. However, other suitable wired or wireless communication media and protocols can be used. The workstation 102 may be configured to perform one or more operations related to information technology applications, user interaction applications, and / or communication applications. For example, the workstation 102 allows the workstation 102 and the controller 104 to communicate with other devices or systems using a desired communication medium (eg, wireless, wired, etc.) and protocol (eg, HTTP, SOAP, etc.). It may be configured to perform operations related to process control related applications and communication applications that allow The controller 104 is one or more processes that have been generated by a system engineer or other system operator using, for example, the workstation 102 or other workstation, and have already been downloaded and instantiated in the controller 104. It may be configured to perform a control routine or function. In the illustrated embodiment, workstation 102 is located in control room 108 and controller 104 is located in a process controller area 110 that is separate from control room 108.

  In the exemplary embodiment, exemplary process control system 100 includes field devices 112 a-c in first process area 114 and field devices 116 a-c in second process control area 118. In order to communicate information between the controller 104, the field devices 112a-c, and the field devices 116a-c, the exemplary process control system 100 includes a field junction box (FJB) 120a-b and a marshalling cabinet 122. Is provided. Each of field junction boxes 120a-b forwards signals from each one of field devices 112a-c and field devices 116a-c to marshalling cabinet 122. Next, the marshalling cabinet 122 organizes (eg, summarizes, classifies, etc.) information received from the field devices 112 a-c and the field devices 116 a-c, and stores the field device information in each I / O card of the controller 104. (For example, transfer to I / O cards 132a-b and I / O cards 134a-b). In the illustrated embodiment, the marshalling cabinet 122 is also used to pass information received from the I / O card of the controller 104 to each one of the field devices 112a-c and field devices 116a-c. Communication between the controller 104 and the field devices 112a-c and field devices 116a-c is bi-directional so as to transfer via 120a-b.

  In the illustrated embodiment, field devices 112a-c are communicatively coupled to field junction box 120a via electrically conductive communication media, wireless communication media, and / or optical communication media, and field devices 116a-c are The field junction box 120b is communicatively coupled. For example, field junction boxes 120a-b may include one or more electrical data transceivers to communicate with electrical transceivers, wireless transceivers, and / or optical transceivers of field devices 112a-c and field devices 116a-c. 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, the marshalling cabinet 122 may be omitted, and signals from the field devices 112a-c and field devices 116a-c may be transmitted from the field junction boxes 120a-b to the controller 104 I / O. Can be transferred directly to the card. In yet another exemplary implementation, field junction boxes 120a-b can be omitted and field devices 112a-c and field devices 116a-c can be directly connected to marshalling cabinet 122.

  Field devices 112a-c and field devices 116a-c can be fieldbus compliant valves, actuators, sensors, etc., in which case field devices 112a-c and field devices 116a-c are well known. Communicate over 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, the field devices 112a-c and the field devices 116a-c instead communicate via a data bus using the well-known Profibus communication protocol and the HART communication protocol, Profibus (eg, Profibus PA), HART. Or an AS-i compliant device. In some exemplary implementations, field devices 112a-c and field devices 116a-c may communicate information using analog or discrete communications instead of digital communications. In addition, 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. The field device identification information can be a physical device tag (PDT) value, a device tag name, an electronic serial number, etc. that uniquely identifies each of the field devices 112a-c and field devices 116a-c. In the exemplary 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 physically. The device tag values PDT3 to PDT5 are stored. The field device identification information is stored in field devices 112a-c and field devices 116a-c, by field device manufacturers and / or operators or engineers involved in the installation of field devices 112a-c and field devices 116a-c. Can be stored or programmed.

  In order to transfer information related to field devices 112a-c and field devices 116a-c within the marshalling cabinet 122, the marshalling cabinet 122 is provided with a plurality of termination modules 124a-c and termination modules 126a-c. ing. The termination modules 124a-c are configured to organize information related to the field devices 112a-c in the first process area 114, and the termination modules 126a-c are field devices 116a in the second process area 118. -C are arranged to organize information related to -c. As illustrated, termination modules 124a-c and termination modules 126a-c communicate with field junction boxes 120a-b via respective multi-core cables 128a and multi-core cables 128b (eg, multi-bus cables). It is connected. In an alternative exemplary implementation in which 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 exemplary embodiment of FIG. 1A shows that each conductor or pair of conductors (eg, bus, twisted pair communication medium, two-wire communication medium, etc.) in multi-core cables 128a-b is connected to field device 112a-c and field device 116a- FIG. 2 illustrates a point-to-point configuration that communicates information uniquely associated with each one of c. For example, the multi-core 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. 130b is used to form a second data bus configured to communicate information between the termination module 124b and the field device 112b, and a third conductor 130c provides information to the termination module 124c. And a third data bus configured to communicate with the field device 112c. In an alternative exemplary implementation that uses 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 multidrop configuration, termination module 124a may be communicatively coupled to field device 112a and another field device (not shown) via first conductor 130a. In some exemplary implementations, the termination module may be configured to communicate wirelessly with a plurality of field devices using a wireless mesh network.

  In addition, or alternatively, in some embodiments, a second field device (not shown) may be added to the termination module 124a via the first conductor 130a, redundant, spare, or added to the field device 112a. As exchange field devices, they are communicatively linked. In some such embodiments, the termination module 124a may need to communicate with a spare device (eg, when the field device 112a fails, the operator replaces the spare device so that the field device 112a is replaced). 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 the multidrop configuration, the termination module 124a and either the field device 112a or the spare field device The communication between the two actually operates as a point-to-point connection. More specifically, the termination module 124a can detect a spare field device, but is the point at which communication is initiated (either automatically or at the direction of a process controller) with the spare field device. Until the active device fails, all communications are directed to the primary or active device (eg, field device 112a). In some embodiments, the spare field device may be used while the failed field device 112a is still in the process control system (eg, before being physically removed and / or erased from the system's logical configuration). , And initiates communication with the termination module 124a. In some such embodiments, the spare field device remains a “spare” destination until the operator designates the spare field device as the new primary device. In another embodiment, termination module 124a automatically replaces a spare field device with field device 112a once field device 112a fails. The ability to configure spare field devices to take over communication in this manner is usually not available with certain communication protocols (eg, HART), because individual field devices can be This is because they are directly communicably 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 will be described more fully below, the field device 112a may be configured as a separate spare on the first conductor 130a when implemented using the HART protocol for faster exchange. Is indirectly connected to the I / O card via a termination module 124a on a high-speed universal I / O bus with sufficient bandwidth to handle the presence of the other field devices. The spare field device on the first conductor 130a may also be implemented in 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 each one of field devices 112a-c and field devices 116a-c using different data types. For example, the termination module 124a may include a digital field device interface for communicating with the field device 112a using digital data, while the termination module 124b is for communicating with the field device 112b using analog data. Other analog field device interfaces.

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

  In the exemplary embodiment of FIG. 1A, I / O cards 132a-b and I / O cards 134a-b reside in 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, which controller 104 , Communicate information to workstation 102. Similarly, to communicate information from the workstation 102 to the field devices 112a-c and field devices 116a-c, the workstation 102 communicates information to the controller 104, which then transmits the information to the I / O card. 132a-b and the I / O cards 134a-b, and the I / O cards 132a-b and the I / O cards 134a-b terminate information in the field devices 112a-c and the field devices 116a-c. It communicates via modules 124a-c and termination modules 126a-c. In an alternative exemplary implementation, I / O cards 132a-b and I / O cards 134a-b can be communicatively coupled to LAN 106 within controller 104, and I / O cards 132a-b And I / O cards 134a-b allow direct communication with workstation 102 and / or controller 104.

  The I / O card 132b and the I / O card 134b are configured as redundant I / O cards in order to provide a fault-tolerant operation when one of the I / O card 132a and the I / O card 134a fails. Has been. In other words, when the I / O card 132a fails, the redundant I / O card 132b performs control, and if it does not fail, the same operation as would be performed by the I / O card 132a is executed. Similarly, the redundant I / O card 134b performs control when the I / O card 134a fails.

  In order to allow communication between the termination modules 124a-c and the I / O cards 132a-b, and between the termination modules 126a-c and the I / O cards 134a-b, the termination modules 124a-c , I / O cards 132a-b are communicatively coupled via a first universal I / O bus 136a, and termination modules 126a-c are connected to I / O cards 134a-b by a second universal I / O. Communication is connected through an O bus 136b. Unlike multi-core cable 128a and multi-core cable 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 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 be a serial bus, two-wire communication, through which information related to two or more field devices may be communicated using, for example, packet-based communication technology, multiplexed communication technology, etc. It can be a medium (eg, twisted pair), an optical fiber, a parallel bus, and the like.

  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 exemplary implementations, the universal I / O buses 136a-b can be implemented using other suitable communication standards including Ethernet, Universal Serial Bus (USB), IEEE 1394, etc. . In addition, although universal I / O buses 136a-b have been described above as a wired communication medium, in another exemplary implementation, one or both of universal I / O buses 136a-b can be wirelessly communicated. It can be implemented using a medium (eg, wireless Ethernet, IEEE-802.11, Wi-Fi (registered trademark), Bluetooth (registered trademark), etc.).

  Universal I / O bus 136a and universal I / O bus 136b are used to convey information in substantially the same way. In the illustrated embodiment, I / O bus 136a is configured to communicate 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 I / O cards 132a-b correspond to which of termination modules 124a-c. Allowing each of the termination modules 124a-c to determine which information corresponds to which of the 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. The I / O card automatically obtains the termination module address (eg, from the termination module) and exchanges information with the termination module. In this manner, the termination modules 124a-c and termination modules 126a-c can address the termination module addresses to the I / O cards 132a-b and I / O cards 134a-b anywhere on their respective buses 136a-b. Without having to manually supply the termination modules 124a-c and termination modules 126a-c to the I / O cards 132a-b and I / O cards 134a-b, respectively. Can be communicatively coupled.

  By using universal I / O buses 136a-b, the number of communication media (e.g., wires) required to communicate information between the marshalling cabinet 122 and the controller 104 is determined for each termination to communicate with the controller. For known configurations that require separate communication media for the modules, this is a significant reduction. Reducing the number of communication media required to communicatively couple the marshalling cabinet 122 to the controller 104 (e.g., reducing the number of communication buses or wires) is achieved by the controller 104 and the field devices 112a-c and field. Reduce engineering costs required to design and generate drawings for installing connections between devices 116a-c. In addition, reducing the number of communication media in turn reduces installation costs and maintenance costs. For example, one of the I / O buses 136a-b replaces multiple communication media used in known systems to communicatively couple field devices to the controller. Thus, instead of maintaining a plurality of 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. Further, in the context of fieldbus-based field devices (eg, Profibus PA compliant devices or FOUNDATION fieldbus H1 (FF-H1) compliant devices), using universal I / O buses 136a-b is also relevant fields. Reduce or eliminate the costs associated with the acquisition, installation and maintenance of other components used to implement the bus architecture. For example, in addition to cables for trunks or segments of a fieldbus architecture, each Profibus PA and FF-H1 typically includes a protocol specific I / O card and a power conditioner (for FF-H1). Or you need a DA / PA coupler (for Profibus PA) and a segment protector. However, such components are no longer required in 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. Further, in some embodiments where each fieldbus device is connected in a point-to-point architecture to a corresponding termination module 124a-c or termination module 126a-c, the cost and complexity of fieldbus segment design work is: It can be significantly reduced or eliminated because the device signal arrangement is handled electronically after being received by each corresponding termination module.

  In addition, reducing the number of communication media required to communicatively couple the marshalling cabinet 122 to the I / O cards 132a-b and I / O cards 134a-b increases the number of termination modules (e.g., More usable space for the termination modules 124a-c and termination modules 126a-c), thereby increasing the I / O density of the marshalling cabinet 122 relative to known systems. In the exemplary embodiment of FIG. 1A, the marshalling cabinet 122 may have many termination modules, otherwise, in known system implementations, more marshalling cabinets (eg, three marshalling cabinets). ) Is required. Further, in some embodiments, the marshalling cabinet 122 communicates data over one universal I / O bus 136a, more than the number of field devices that convey data over other types of bus communications. There can be more termination modules 124a-c corresponding to the field devices 112a-c. For example, fieldbus segments are typically limited to carry signals for up to 16 field devices. In contrast, in some embodiments, one of the universal I / O buses 136a-b provides communication associated with up to 96 termination modules 124a-c and termination modules 126a-c. Can do.

  It may be configured to use different data type interfaces (eg, different channel types) to communicate with field devices 112a-c and field devices 116a-c, such as I / O cards 132a-b and I / O cards 134a. By providing termination modules 124a-c and termination modules 126a-c configured to use respective common I / O bus 136a and common I / O bus 136b to communicate with. The exemplary embodiment of FIG. 1A may be configured with different field device data types (eg, without the need to implement multiple different field device interface types on I / O cards 132a-b and I / O cards 134a-b) Field devices 112a-c and The data associated with the data type or channel-type) is used by the I over field devices 116a-c, makes it possible to transfer to the I / O cards 132a~b and I / O cards 134a-b. Thus, an I / O card having one interface type (eg, an I / O bus interface type for communicating via I / O bus 136a and / or I / O bus 136b) has different field device interface types. It can communicate with a plurality of field devices it has.

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

  In the illustrated embodiment, the marshalling cabinet 122, termination modules 124a-c and termination modules 126a-c, I / O cards 132a-b and I / O cards 134a-b, and the controller 104 are installed in an existing process control system facility. , To facilitate transition to a configuration substantially similar to the configuration of the example 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 so that termination modules 124a-c and termination modules 126a-c are included in the process control system. Can be configured to be communicatively coupled to an existing field device that is already installed. Similarly, the controller 104 may be configured to include a known LAN interface for communicating via a LAN to an already installed workstation. In some exemplary implementations, I / O cards 132a-b and I / O cards 134a-b can be installed or communicatively coupled to known controllers, and within the process control system Avoid having to replace an already installed controller.

  In the illustrated embodiment, the I / O card 132a includes a data structure 133 and the I / O card 134a includes a data structure 135. Data structure 133 is a field device identification number (e.g., field device) that corresponds to a field device (e.g., field device 112a-c) assigned to communicate with I / O card 132a via universal I / O bus 136a. Device identification information) is stored. Termination module 124a-c may use the field device identification number stored in data structure 133 to determine if the field device is incorrectly connected to one of termination modules 124a-c. it can. Data structure 135 is a field device identification number (e.g., field device) that corresponds to a field device (e.g., field device 116a-c) assigned to communicate with I / O card 134a via universal I / O bus 136b. Device identification information) is stored. Data structure 133 and data structure 135 may be added by an engineer, operator, and / or user via workstation 102 during configuration time or operation of exemplary process control system 100. In some embodiments, termination modules 124a-c may be communicatively coupled to multiple field devices (eg, active field devices and redundant or spare field devices). In such an embodiment, 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, the redundant I / O card 132b stores the same data structure as the data structure 133, and the redundant I / O card 134b stores the same data structure as the data structure 135. Additionally or alternatively, data structure 133 and data structure 135 can be stored within workstation 102.

  In the illustrated embodiment, the marshalling cabinet 122 is shown located in a termination area 140 that is separate from the process control area 110. I / O buses 136a-b (e.g., each of one of field devices 112a-c and field devices 116a-c, or their limited group along a multi-drop segment) instead of a much larger number of communication media By uniquely linking the termination modules 124a-c and the termination modules 126a-c to the controller 104 using a plurality of uniquely associated communication buses, communication reliability is not significantly reduced. In addition, it makes it easier to place the controller 104 relatively far from the marshalling cabinet 122 than in known configurations. In some exemplary implementations, the process control area 110 and the termination area 140 can be combined such that the marshalling cabinet 122 and the controller 104 are located in the same area. In any case, arranging the marshalling cabinet 122 and the controller 104 in a different area from the process area 114 and the process area 118 means that the I / O cards 132a to 132b and the I / O cards 134a to 134b Severe environmental conditions (e.g., heat, moisture, electromagnetic noise, etc.) that can be associated with the process area 114 and process area 118 with the termination modules 124a-c and termination modules 126a-c and the universal I / O buses 136a-b ) Can be isolated. In this way, the cost and complexity of designing and manufacturing the termination modules 124a-c and termination modules 126a-c, and the I / O cards 132a-b and I / O cards 134a-b are reduced to the field devices 112a-c. And the cost of manufacturing the communication and control circuits between the field devices 116a-c can be significantly reduced, including termination modules 124a-c and termination modules 126a-c, and I / O cards 132a-b. And I / O cards 134a-b to ensure the reliable operation (e.g., reliable data communication) required to operate in the environmental conditions of process area 114 and process area 118. Required operating specification characteristics (eg shielding, more robust Road, because that does not require a more complex error checking, etc.).

  1B-1D illustrate alternative exemplary implementations that may be used to communicatively couple a workstation, a controller, and an I / O card. For example, in the exemplary embodiment shown in FIG. 1B, the controller 152 (which performs substantially the same function as the controller 104 of FIG. 1A) is in the I / O cards 154a-b and I / O cards 156a-b. Communication is performed 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 communication with termination modules 126a-c. In order to communicate with the workstation 102, the controller 152 is communicatively coupled to the workstation 102 via the LAN 106.

  In another exemplary embodiment shown in FIG. 1C, controller 162 (which performs substantially the same function as controller 104 in FIG. 1A) includes workstation 102, a plurality of I / O cards 164a-b and I / O. The O cards 166a and 166b are communicatively connected via the LAN 106. The I / O cards 164a-b and the I / O cards 166a-b perform substantially the same functions as the 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 communication with termination modules 126a-c. However, the I / O cards 132a-b and I / O cards 134a-b in FIG. 1A are different from the I / O cards 154a-b and I / O cards 156a-b in FIG. The b and I / O cards 166a and 166b are configured to communicate with the controller 162 and the workstation 102 via the LAN 106. In this manner, the I / O cards 164a-b and the I / O cards 166a-b can directly exchange information with the 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 in workstation 172 (which performs substantially the same functions as workstation 102 of FIG. 1A). In some exemplary implementations, physical I / O cards 174a-b and I / O cards 176a-b are not included in workstation 172, but I / O cards 174a-b and I / O cards Functions with / O cards 176a-b are implemented in workstation 172. In the exemplary embodiment of FIG. 1D, the I / O cards 174a-b and I / O cards 176a-b are universal I / O to exchange information with the termination modules 124a-c and termination modules 126a-c. It is configured to be communicatively coupled to buses 136a-b. Also, in the exemplary embodiment of FIG. 1D, workstation 172 is configured to perform substantially the same functions as controller 104 so that it is not necessary to provide a controller that executes a process control strategy. Can do. 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, the marshalling cabinet 122 is provided with a socket rail 202a and a socket rail 202b that receive termination modules 124a-c. In addition, the marshalling cabinet 122 is provided with an I / O bus transceiver 206 that communicatively couples the termination modules 124a-c to the universal I / O bus 136a as described above in connection with FIG. 1A. The I / O bus transceiver 206 may be implemented using transmitter and receiver amplifiers that condition the signals exchanged between the termination modules 124a-c and the I / O cards 132a-b. The marshalling cabinet 122 is provided with another universal I / O bus 208 that communicatively couples the terminal modules 124 a-c to the 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, the marshalling cabinet 122 is another one that is substantially similar or identical to the I / O bus transceiver 206 to communicatively couple the termination modules 126a-c to the I / O cards 134a-b. An I / O bus transceiver may be provided.

  Using a common communication interface (e.g., I / O bus 208 and I / O bus 136a) to exchange information between I / O cards 132a-b and termination modules 124a-c, field devices The connection routing from the I / O card can be defined towards the end of the design or installation process. For example, termination modules 124a-c may be communicatively coupled to I / O bus 208 at various locations within marshalling cabinet 122 (eg, various termination module sockets on socket rails 202a-b). In addition, common communication interfaces (eg, I / O bus 208 and I / O bus 136a) between I / O cards 132a-b and termination modules 124a-c are terminated with I / O cards 132a-b. Reduce the number of communication media between modules 124a-c (e.g., the number of communication buses and / or wires) and thus over the number of known termination modules that can be installed in a known marshalling cabinet configuration. Also, a relatively large number of termination modules 124 a-c (and / or termination modules 126 a-c) can be installed in the marshalling cabinet 122.

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

  In order to retrieve field device identification information and / or other field device information, each of the termination modules 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 provide field device identification information and / or other field device information to field device 112a (and / or termination module). From other field devices communicatively coupled to 124a) and display the information via the display 212 of the termination module 124a. The labeler 214 is described in detail below in connection with FIG. Providing display 212 and labeler 214 reduces the cost and installation time associated with manually labeling wires and / or buses associated with termination modules and field devices. However, in some exemplary implementations, manual wire labeling can also be used in connection with display 212 and labeler 214. For example, display 212 and labeler 214 are 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, the field devices 112a-c and the field devices 116a-c can be communicatively coupled to the I / O cards 132a-b and the I / O cards 134a-b relatively quickly. Subsequently, after installation is complete, the label is optionally placed on a bus or wire that extends between the termination modules 124a-c and termination modules 126a-c and the field devices 112a-c and field devices 114a-c. Can be added. Display 212 and labeler 214 also display status information (eg, device error, device alarm, device on, device off, device disabled, etc.) to facilitate the troubleshooting process. The cost and time associated with the maintenance work can be reduced.

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

  FIG. 3 is another example marshalling cabinet 300 that may be used to implement the example marshalling cabinet 122 of FIG. 1A. In the illustrated embodiment, the marshalling cabinet 300 is provided with a wireless I / O bus communication controller 302 for communicating wirelessly with the controller 104 of FIG. 1A via a wireless universal I / O connection 304. As shown in FIG. 3, a plurality of termination modules 306 that are substantially similar or identical to the termination modules 124a-c and termination modules 126a-c of FIG. The I / O bus communication controller 302 is communicatively coupled via a universal I / O bus 309 inside the marshalling cabinet 300. In the illustrated embodiment, the wireless I / O bus communication controller 302 emulates the I / O card of the controller 104 of FIG. 1A (eg, the I / O card 134a of FIG. Allows to communicate with.

  Unlike the exemplary embodiment of FIG. 2 in which the display 212 is attached to the termination modules 124a-c, in the exemplary embodiment of FIG. 3, the plurality of displays 310 are marshaled in relation to the socket that receives the termination module. Installed in the cabinet 300. Thus, when one of the termination modules 306 is plugged in and communicatively coupled to a field device (eg, one of the field devices 112a-c and field devices 116a-c of FIG. 1A). The labeler 214 of the termination module 306 and each one of the displays 310 can be used to display field device identification information indicating the field devices connected to the termination module 306. Display 310 can also be used to display other field device information. The marshalling cabinet 300 is provided with a power supply 312 that is substantially similar or identical to the power supply 216 of FIG. Further, in some embodiments, the marshalling cabinet 300 is provided with a power conditioner 314 that is substantially similar or identical to the power conditioner 218 of FIG.

  4 shows a plan view of the exemplary termination module 124a of FIGS. 1A and 2, and FIG. 5 shows a side view. In the exemplary embodiment of FIG. 4, the display 212 is on the top surface of the exemplary termination module 124a, and when the termination module 124a is plugged into the rail socket 202a (FIG. 3), the display 212 is in operation during operation. Or make it visible to the user. As shown in the exemplary embodiment of FIG. 5, exemplary termination module 124 a is removably coupled to base 402. The exemplary termination module 124a includes a plurality of contacts 404 (two of which are 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 the marshalling cabinet 122 via the base 402 and removed. Base 402 is provided with a termination screw 406 (eg, field device interface) that fastens or secures a conductor communication medium (eg, bus) from field device 112a. When the termination module 124a is removably coupled to the base 402, the termination screw 406 is communicatively coupled to one or more of the contacts 404 to pass information between the termination module 124a and the field device 112a. Make it possible to communicate. In other exemplary implementations, the base 402 may be provided with other suitable types of field device interfaces (eg, sockets) instead of the termination screw 406. In addition, although one field device interface (eg, termination screw 406) is shown, the base 402 is configured to allow multiple field devices to be communicatively coupled to the termination module 124a. More field device interfaces may be provided.

  To communicatively couple the termination module 124a to the universal I / O bus 208 of FIG. 2, the base 402 is provided with a universal I / O bus connector 408 (FIG. 5). When the user plugs base 402 into socket rail 202a or socket rail 202b (FIG. 2), universal I / O bus connector 408 bites universal I / O bus 208. The universal I / O bus connector 408 can be implemented using a suitable interface, including, for example, a relatively simple interface such as an insulated perforated connector. In order to allow information to be communicated between the termination module 124a and the I / O bus 208, an I / O bus connector 408 is connected to one or more of the contacts 404 of the termination module 124a. .

  As shown in FIG. 5, the base 402 may also be provided with an optical display interface connector 410 that communicatively couples the termination module 124a to an external display (eg, one of the 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 (eg, the display of FIG. 3). 1 of 310).

  6 is a detailed block diagram of the exemplary termination module 124a of FIGS. 1A and 2, FIG. 7 is a detailed block diagram of the exemplary I / O card 132a of FIG. 1A, and FIG. FIG. 7 is a detailed block diagram of the exemplary labeler 214 of FIGS. 2, 3, and 6. The example termination module 124a, the example I / O card 132a, and the example labeler 214 can 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. In addition or alternatively, the exemplary termination module 124a, the exemplary I / O card 132a, the exemplary labeler 214, and some or all of the blocks, or portions thereof, for example, a processor system (eg, Instructions stored on a machine-accessible medium that, when executed by the exemplary processor system 1610) of FIG. 16, perform the operations depicted in the flowcharts of FIGS. 10A, 10B, 11A, 11B, and 12 , Code, and / or other software and / or firmware, etc. The exemplary termination module 124a, the exemplary I / O card 132a, and the exemplary labeler 214 are described as having one of each of the blocks described below, but the exemplary termination module 124a and exemplary Each of the exemplary I / O card 132a and exemplary labeler 214 may be provided with more than one of each block described below.

  Referring to FIG. 6, the exemplary termination module 124a is a universal that allows the exemplary termination module 124a to communicate with the I / O cards 132a-b (or other I / O cards) of FIG. 1A. An I / O bus interface 602 is included. The I / O bus interface 602 can be implemented using, for example, the RS-485 serial communication standard, Ethernet, etc. In order to identify the address of the termination module 124a and / or the address of the I / O card 132a, the termination module 124a is provided with an address identifier 604. The address identifier 604 may be configured to query the I / O card 132a (FIG. 1A) for a termination module address (eg, a network address) when the termination module 124a is plugged into the marshalling cabinet 122. In this manner, the termination module 124a can use the termination module address as a source address when communicating information to the I / O card 132a, and the I / O card 132a can use when terminating information to the termination module 124a. Use the termination module address as the destination address.

  In order to control the various operations of the termination module 124a, the termination module 124a is provided with an operation controller 606. In an exemplary implementation, the motion controller can be implemented using a microprocessor or microcontroller. The motion controller 606 communicates instructions or commands to other parts of the exemplary termination module 124a to control the operation of these parts.

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

  In order to provide (eg, obtain and / or generate) field device identification information and / or other field device information (eg, activity information, data type information, status information, etc.), termination module 124a may provide labeler 214 ( 2 and 3) are provided. The labeler 214 is described in detail below with respect to 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 the field device 112a (or other field device) of FIG. 1A, the termination module 124a is provided with a field power controller 610. In the illustrated embodiment, the power source 216 (FIG. 2) of the marshalling cabinet 122 provides power to the termination module 124a to provide power to the communication channel interface for communicating with the field device 112a. For example, some field devices communicate using 12 volts and others communicate using 24 volts. In the exemplary embodiment, field power controller 610 is configured to regulate, control, increase voltage, and / or decrease voltage provided to power supply 216 to termination module 124a. In some embodiments, power regulation is achieved via a power conditioner 218 (FIG. 2) associated with the marshalling cabinet. In some exemplary implementations, the field power controller 610 limits the amount of power used to communicate with the field device and / or the amount of power supplied to the field device to make it flammable or combustible. Greatly reduce or eliminate the risk of sparks in the environment.

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

  To electrically isolate the termination module 124a circuit from the I / O card 132a, the termination module 124a is provided with one or more isolation devices 614. The isolation device 614 can be implemented using galvanic and / or optical isolators. An exemplary insulation structure is described in detail below with respect to FIG.

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

  In order to control communication with the field device 112a, the termination module 124a is provided with a field device communication processor 620. The field device communication processor 620 ensures that the information received from the I / O card 132a is in the correct format and voltage type (eg, analog or digital) to convey to the field device 112a. The field device communication processor 620 is also configured to packetize or depacketize information when the field device 112a is configured to communicate using digital information. In addition, field device communication processor 620 extracts information received from field device 112a and passes the information to analog / digital converter 618 and / or I / O bus communication processor for later transmission to I / O card 132a. 608 is configured to communicate to 608. In some embodiments, the field device communication processor 620 assists in identifying an appropriate communication protocol associated with the 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 an embodiment, the field device communication processor 620 implements an autosensing routine in which the field device communication processor 620 formats a test signal or test request that corresponds to the Profibus PA communication protocol. If field device 112a responds to the request, field device 112a is identified as a Profibus PA compliant device, and all subsequent communications are formatted based on the Profibus PA protocol. When the field device 112a does not respond to the request in the Profibus PA format, the field device communication processor 620 prepares the format of the second request corresponding to the FF-H1 communication protocol, and determines whether the fieldbus device 112a is an FF-H1 compliant device. Whether or not the field device 112a responds to the second request. If termination module 124a is configured to communicate using other protocols (eg, HART), field device communication processor 620 may add additional communication protocols until field device 112a detects an appropriate communication protocol. A request can be generated.

  In some embodiments, such an autosensing routine is implemented periodically (or aperiodically) (eg, after a certain threshold period) and is communicatively coupled to termination module 124a. Detect device changes. For example, the autosensing routine may include a first, active or primary field device (eg, 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, the termination module 124a can detect this by loss of communication with the first field device. In some such embodiments, the autosensing routine detects a spare device and compares the device information (eg, placeholder information, device type, vendor, version, etc.) with the device information of the failed device. To do. In some embodiments, if the device information matches (eg, the primary field device and the spare device are the same device except for the serial number), the termination module 124a is the spare field device and the first field device. Is automatically replaced to continue control of the process system. In addition or alternatively, in some embodiments, if the device information includes several differences (eg, different versions or vendors), the termination module 124a may designate a spare field device and Initiates communication with the field device, but is disconnected (until the operator or engineer designates the first field device, removes, and / or designates the spare field device as a new active or primary device). Maintaining a “spare” destination (while continuing to indicate the first field device as the primary device).

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

  In general, a field device communication controller similar to the field device communication controller 620 is a communication protocol function or other communication function (eg, Fieldbus communication protocol function, corresponding to the type of field device configured to communicate with it). HART communication protocol function, etc.). For example, when the field device 112a is implemented as a HART device, the field device communication controller 620 of the termination module 124a is provided with a HART communication protocol function. When the termination module 124a receives information addressed to the field device 112a from the I / O card 132a, the field device communication controller 620 formats the information in accordance with the HART communication protocol and distributes the information to the field device 112a.

  In the exemplary embodiment, field device communication controller 620 is configured to process pass-through messages. A pass-through message occurs at a workstation (eg, workstation 102 of FIG. 1A) and as a payload (eg, a data portion of a communication packet) via a controller (eg, controller 104 of FIG. 1A) via a field device (eg, field It is communicated to a termination module (eg, termination module 124a in FIG. 1A) for delivery to device 112a). For example, messages that originate at workstation 102 and are to be delivered to field device 112a are tagged with a communication protocol descriptor (eg, HART protocol descriptor) at workstation 102 and / or communicated with field device 112a. Can be formatted according to protocol. The workstation 102 then wraps the message in a payload consisting of one or more communication packets and delivers the message as a pass-through message from the workstation 102 via the I / O controller 104 to the termination module 124a. . Wrapping the message involves, for example, packetizing the message in header information according to the communication protocol (eg, Fieldbus protocol, HART protocol, etc.) used to communicate with the field device. When the termination module 124a receives a communication packet including a pass-through message from the I / O card 132, the I / O bus communication processor 608 (FIG. 6) extracts the payload from the received communication packet. The field device communication controller 620 (FIG. 6) then retrieves the pass-through message from the payload and formats the message (if not already formatted at the workstation 102) according to the communication protocol descriptor generated by the workstation 102. Arrange the message to the 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 the field device 112a generates a message that is to be delivered to the workstation 102 (eg, a response to a workstation message or other message), the field device communication controller 620 may send a message from the field device 112a to Wrapped in a payload consisting of one or more communication packets, the I / O bus communication processor 608 communicates one or more packets containing the wrapped message to the I / O card 132a. When the workstation 102 receives a packet containing a wrapped message from the controller 104, the 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, the field device interface 622 can be communicatively coupled to the termination screw 406 of FIGS. 4 and 5 via one or more of the contacts 404 (FIG. 4).

  In some embodiments, the termination module 124a is provided with a fieldbus diagnostic analyzer 624 that is configured to provide advanced diagnostics for the associated field device when the field device is fieldbus compliant. During operation, fieldbus diagnostic analyzer 624 performs measurements on the state of physical wiring (eg, first conductor 130a in FIG. 1A) and associated communications. For example, the 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 the fieldbus diagnostic analyzer 624 can be more reliable and / or robust, which is This is because module 124a does not need to diagnose multiple devices in a traditional fieldbus segment multi-drop architecture and is linked to only one field device in a point-to-point 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 exemplary I / O card 132a includes a communication processor 704 that controls communication with the controller 104 and enters and retrieves information to and from the controller 104. In the exemplary embodiment, communication interface 702 and communication processor 704 are configured to communicate to controller 104 information that is to be delivered to controller 104 and information that is to be delivered to workstation 102 (FIG. 1A). ing. In order to convey information that is to be delivered to the workstation 102, the communication interface 702 may send information (eg, information from field devices 112a-c, termination modules 124a-c, and / or I / O card 132a), Wrapping in a payload consisting of one or more communication packets according to a communication protocol (eg, communication control protocol (TCP), user datagram protocol (UDP), etc.) to convey the packet containing information to the workstation 102 Can be configured. The workstation 102 then retrieves the payload from the received packet and retrieves the information in the payload. In the illustrative example, the information in the payload of the packet communicated to the workstation 102 by the communication interface 702 can include one or more wrappers. For example, information generated at a field device (eg, field device 112a) may be wrapped in a field device communication protocol wrapper (eg, FOUNDATION fieldbus communication protocol wrapper, HART communication protocol wrapper, etc.), and communication interface 702 may be , Wrap the information according to a TCP-based protocol, a UDP-based protocol, or other protocol that allows the controller 104 to later communicate the information to the workstation 102. In a similar manner, the communication interface 702 retrieves information that is communicated by the workstation 102 to the controller 104 to be delivered to the field devices 112a-c, termination modules 124a-c, and / or the I / O card 132a. Can be configured.

  In an alternative exemplary implementation, communication interface 702 and communication processor 704 can communicate information (with or without field device communication protocol wrappers) to controller 104, which can be Can be packetized in the same way as described above. The communication interface 702 and the communication processor 704 can be implemented using a wired or wireless communication standard.

  For example, in an alternative exemplary implementation, such as the exemplary 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.

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

  To communicatively couple the I / O card 132a to the universal I / O bus 136a (FIG. 1A), the I / O card 132a is provided with an I / O bus interface 710. The I / O card 132a provides an I / O bus communication processor 712 to process communication information exchanged via the I / O bus 136a and to control communications performed via the I / O bus 136a. Has been. The I / O bus interface 710 can be similar to or the same as the I / O bus interface 602 of FIG. 6, and the I / O bus communication processor 712 is similar to or the same as the I / O bus communication processor 608 of FIG. Can be. The power provided by the controller 104 of FIG. 1A is converted to power required to supply and operate the I / O card 132a and / or to communicate with the termination modules 124a-c. Therefore, the I / O card 132a is provided with a power converter 714.

  Referring now to FIG. 8, the exemplary labeler 214 replaces the labeler 214 with a termination module (eg, the termination module 124a of FIGS. 1A, 2, 4, 5, and 6) and / or a field device (eg, , Communicatively coupled to field device 112a) of FIG. 1A, and field device identification information (eg, device tag value, device name, electronic serial number, etc.) and / or other field device information (eg, activity information, Including a communication interface 802 configured to read data type information, status information, etc.). To control communication with the termination module 124a and / or field device 112a, the labeler 214 is provided with a communication processor 804.

  To detect a connection to a field device (eg, field device 112a in FIG. 1A), labeler 214 is provided with a connection detector 806. The connection detector 806 can be implemented using, for example, a voltage sensor, a current sensor, a logic circuit, etc. that detects when the field device 112a is connected to the termination module 124a. In the illustrated embodiment, when connection detector 806 determines that field device 112a is connected to termination module 124a, connection detector 806 indicates a connection detected by a notification (eg, an interrupt) to indicate communication processor 804. To be communicated to. The communication processor 804 then queries the termination module 124a and / or the field device 112a for field device identification information of the field device 112a. In an exemplary implementation, the connection detector 806 also includes, for example, a multi-drop connection, a point-to-point connection, a point-to-point connection to a working field device and a non-working spare field device, a wireless mesh It may be configured to determine the type of connection that communicatively couples the field device 112a to the termination module 124a, such as a network connection, an optical connection, and the like.

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

  In order to detect the operation of the field device 112a, the labeler 214 is provided with a field device activity detector 810. In the illustrated embodiment, when communication processor 804 receives data from termination module 124a and / or field device 112a, communication processor 804 communicates the received data to field device activity detector 810. The field device activity detector 810 then measures, for example, measurement information (eg, temperature, pressure, line voltage, etc.) or other monitoring information (eg, valve close, valve open, etc.) generated by the field device 112a. The process variable (PV) value is extracted from the data including The display interface 808 can then display field device activity information (eg, PV value, measurement information, monitoring information, etc.).

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

  To identify the field device 112a, the labeler 214 is provided with a field device identifier 814. The field device identifier 814 extracts field device identification information (eg, device tag value, device name, electronic serial number, etc.) from data received from the termination module 124a and / or the field device 112a by the communication processor. It is configured. The display interface 808 can then display field device identification information. In an exemplary 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 embodiments, the field device identifier 814 determines the appropriate communication protocol associated with the field device 112a in the same or similar manner as the field device communication processor 620 described above with respect to FIG. It is configured to be identified in combination with it.

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

  FIG. 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 isolation circuit configuration that can be implemented as follows. In the exemplary 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). In addition, the termination modules 124a-b are connected to their respective field devices 112a-b via a field junction box 120a. Further, the termination modules 124a and 124b are connected to the universal I / O bus 136a and the power source 216. In order to electrically isolate the termination module circuit 902 from the universal I / O bus 136a, the termination module 124a is provided with an isolation circuit 906. In this manner, the termination module circuit 902 does not affect the voltage on the universal I / O bus 136a when a power surge or other power fluctuation occurs in the field device 112a, and the I / O card 132a (FIG. 1A) can be configured to follow (eg, float) the voltage level of the field device 112a without damaging it. Termination module 124b also includes an isolation circuit 908 configured to isolate termination module circuit 904 from universal I / O bus 136a. The insulating circuit 906, the insulating circuit 908, and other insulating circuits mounted on the termination modules 124a and 124b can be mounted using an optical insulating circuit or a galvanic insulating circuit.

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

  In known process control systems, an isolation circuit is provided in a known marshalling cabinet, thereby reducing the amount of space available to known termination modules. However, providing the isolation circuit 906, the isolation circuit 910, the isolation circuit 908, and the isolation circuit 912 in the termination module 124a and the termination module 124b as shown in the exemplary embodiment of FIG. Reduces the amount of space required in the marshalling cabinet 122 (FIGS. 1A and 2), and therefore can be used for termination modules (eg, termination modules 124a-c and termination modules 126a-c). Increase. In addition, mounting an isolation circuit (eg, isolation circuits 906, 908, 910, and 912) within a termination module (eg, termination modules 124a-b) selects the isolation circuit only with the termination module that requires isolation. To be able to use it. For example, some of the termination modules 124a-c and termination modules 126a-c of FIG. 1A can be implemented without isolation circuitry.

  FIGS. 10A, 10B, 11A, 11B, 12, and 15 illustrate termination modules (eg, termination module 124a of FIGS. 1A, 2 and 4-6, and / or termination module 1332a of FIG. 13B). ), An I / O card (eg, I / O card 132a in FIGS. 1A and 7), and a labeler (eg, labeler 214 in FIGS. 2, 3, and 8). FIG. 6 is a flowchart of an exemplary method obtained. FIG. In some exemplary implementations, the exemplary methods of FIGS. 10A, 10B, 11A, 11B, 12 and 15 are illustrated in a processor (eg, the exemplary processor system 1610 of FIG. 16). Can be implemented using machine-readable instructions comprising a program executed by a processor 1612). A method well-known and / or embodied in software stored on a tangible medium, such as a CD-ROM, floppy disk, hard drive, digital versatile disk (DVD), or memory associated with processor 1612 Thus, it can be implemented with firmware and / or dedicated hardware. Further, an exemplary program will be described with reference to the flowcharts illustrated in FIGS. 10A, 10B, 11A, 11B, 12, and 15, but the exemplary termination module 124a described herein. Those skilled in the art will readily appreciate that many other methods of implementing the exemplary termination module 1332a, the exemplary I / O card 132a, and the exemplary labeler 214 can alternatively be used. to understand. For example, the execution order of the blocks can be changed and / or some of the described blocks can be changed, deleted, or combined.

  Referring to FIGS. 10A and 10B in detail, the exemplary method of FIGS. 10A and 10B will be described in connection with the exemplary termination module 124a of FIGS. 1A, 2 and 4-6. I will explain. However, other termination modules can be implemented using the exemplary method of FIGS. 10A and 10B. The flowcharts of FIGS. 10A and 10B are used to illustrate how the exemplary termination module 124a communicates information between the field device 112a and the 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 it has received communication information, eg, via an interrupt or status register. Judge that If the termination module 124a determines that communication information has not been received (block 1002), control remains at block 1002 until the termination module 124a receives communication information.

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

  The field device communication processor 620 then determines whether analog to digital conversion is required (block 1008). For example, if the field device 112a conveys an analog measurement, the field device communication processor 620 determines that an analog to digital conversion is required or required (block 1008). If analog-to-digital conversion is required, analog-to-digital converter 618 (FIG. 6) performs 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 communication processor 620 determines the data type (eg, analog, digital, temperature) associated with the received field device information. Measurement, etc.) (block 1012) and a data type descriptor corresponding to the received field device information is generated (block 1014). For example, the termination module 124a can store a data type descriptor that indicates the data type that it always receives from the field device 112a, or the field device 112a can store the data type descriptor at block 1010 by the field device communication processor 620. The data type used to generate can be communicated to the termination module 124a.

  The I / O bus communication processor 608 (FIG. 6) determines the destination address of the I / O card 132a that carries the information received from the field device 112a by the termination module 124a (block 1016). For example, the communication processor 608 (FIG. 6) can obtain the destination address of the I / O card 132a from the address identifier 604 (FIG. 6). In addition, the I / O bus communication processor 608 determines or generates error check data that is communicated to the I / O card 132a to ensure that the field device information has been received by the I / O card 132a without error. (Block 1020). For example, the I / O bus communication processor 608 can generate a cyclic error check (CRC) error check bit.

  The I / O bus communication processor 608 then sends the field device information, field device identification information, data type descriptor, destination address of the I / O card 132a, source address of the termination module 124a, and error check data to the I / O. Packetize based on the bus communication protocol (block 1022). An I / O bus communication protocol can be implemented using, for example, a TPC-based protocol, a UDP-based protocol, and the like. The I / O bus communication processor 608 can obtain the source address of the termination module 124a from the address identifier 604 (FIG. 6). The I / O bus interface 602 (FIG. 6) then passes the packetization information through the universal I / O bus 136a (FIGS. 1A and 2) to other termination modules (eg, termination module 124b and FIG. 1A). Communicate with the packetization information generated and communicated by termination module 124c) (block 1024). For example, the I / O bus interface 602 can use the universal I / O bus 136a to convey information from the termination module 124a to the I / O card 132a (eg, not used by the termination modules 124b-c). ) An arbitration circuit or arbitration device that intercepts or monitors the universal I / O bus 136a to determine the time may be provided.

  If the termination module 124b determines at block 1004 that the communication information detected at block 1002 is not from the field device 112a (eg, the communication information is from the I / O card 132a), the I / O bus communication processor 608. (FIG. 6) extracts the destination address from the received communication information (block 1026). The I / O bus communication processor 608 then determines whether the extracted destination address matches the destination address of the termination module 124a obtained from the address interface 604 (block 1028). If the destination address does not match the address of termination module 124a (eg, the received information was not scheduled 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 the termination module 124a (eg, the received information was to be delivered to the termination module 124a) (block 1028), the I / O bus communication processor 608 may The device information is extracted from the received communication information based on the I / O bus communication protocol (block 1030), and data consistency is used, for example, using a CRC verification process based on error detection information in the received communication information And verify (block 1032). Although not shown, if the I / O bus communication processor 608 determines in block 1032 that there is an error in the received communication information, the I / O bus communication processor 608 requests a retransmission and sends a message. It transmits to the I / O card 132a.

  After verifying data integrity (block 1032), I / O bus communication processor 608 (or field device communication processor 620) determines whether digital to analog conversion is required (block 1034). For example, if the data type descriptor stored in termination module 124a indicates that field device 112a requires analog information, I / O bus communication processor 608 determines that digital-to-analog conversion is required ( Block 1034). If digital-to-analog conversion is required (block 1034), the 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 no digital-to-analog conversion is required (block 1034), the field device communication processor 620 sends the field device information to the field device 112a and the field device interface 622 (FIG. 6). ) Using the field device communication protocol of field device 112a (block 1038).

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

  11A and 11B show a flowchart of an exemplary method that may be used to implement the I / O card 132a of FIG. 1A to convey information between the termination module 124a and the controller 104 of FIG. 1A. ing. Initially, the 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 when the communication processor 704 (FIG. 7) indicates that the communication information has been received, for example, via an interrupt or status register. If the I / O card 132a determines that it is not receiving communication information (block 1102), control remains at block 1102 until the I / O card 132a receives communication information.

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

  The communication processor 704 identifies a data type (eg, 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). ), Generating a data type descriptor corresponding to the received termination module information (block 1110). In an alternative exemplary implementation, the data type descriptor is generated at workstation 102 (FIG. 1A) and communication processor 704 does not need to generate a data type descriptor.

  The I / O bus communication processor 712 (FIG. 7) then determines the destination address of the termination module 124a (block 1112). In addition, the I / O bus communication processor 712 determines error check data to communicate to the termination module 124a along with the termination module information to ensure that the termination module 124a received the information without error (block 1114). For example, the I / O bus communication processor 712 can generate a cyclic error check (CRC) error check bit.

  The I / O bus communication processor 712 then packetizes the termination module information, data type descriptor, destination address of the termination module 124a, source address of the termination module 124a, and error check data based on the I / O bus communication protocol. (Block 1116). The I / O bus interface 710 (FIG. 7) then passes the packetization information through the universal I / O bus 136a (FIGS. 1A and 2) to other termination modules (eg, termination module 124b of FIG. 1A and Communicate with packetization information addressed to the termination module 124c) (block 1118). For example, the I / O bus communication processor 704 packetizes other termination module information using, for example, the destination addresses of the termination module 124b and the termination module 124c, and the termination module for all of the termination modules 124a-c. Information can be conveyed over the universal I / O bus 136a using the RS-485 standard. Each of the termination modules 124a-c can extract its respective information from the universal I / O bus 136a based on the destination address provided by the I / O card 132a.

  If the I / O card 132a determines in block 1104 that the communication information detected in block 1102 is not from the controller 104 (eg, the communication information is from one of the termination modules 124a-c), The I / O bus communication processor 712 (FIG. 7) extracts the source address (eg, the source address of one of the termination modules 124a-c) from the received communication information (block 1122). The I / O bus communication processor 712 then extracts the data type descriptor (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 data consistency. Are verified using, for example, a CRC verification process based on error detection information in the received communication information (block 1128). Although not shown, if the I / O bus communication processor 712 determines in block 1128 that an error exists in the received communication information, the I / O bus communication processor 712 sends a retransmission request message in block 1122. Send to the termination module associated with the acquired source address.

  After verifying data integrity (block 1128), the communication processor 704 packetizes the termination module information (using the termination module source address and data type descriptor) and the communication interface 702 converts the packetization information. Communicate to the controller 104 (block 1130). If the information is to be delivered to the workstation 102, the controller 104 can subsequently communicate the information to the workstation 102. After the communication interface 702 communicates information to the controller 104, or after the I / O bus interface 710 communicates termination module information to the termination module 124a, the processes of FIGS. 11A and 11B are terminated and / or control is performed. Return to the calling process or calling function, for example.

  12 retrieves information related to a field device (eg, field device 112a of FIG. 1A) communicatively coupled to a termination module (eg, termination module 124a of FIGS. 1, 2, and 4-6). FIG. 9 is a flowchart of an exemplary method that may be used to implement the labeler 214 of FIGS. 2, 3, and 8. Initially, the connection detector 806 (FIG. 8) has a field device (eg, field device 112a) connected to the termination module 124a (eg, termination screw 406 of FIGS. 4 and 5 and / or FIG. 6). (Connected to the field device interface 622) (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 is provided by the connection detector 806 to the field device 112a (or other device). It stays at block 1202 until it determines that the field device is connected to the termination module 124a.

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

  The field device identifier 814 then determines based on the field device identification information whether the field device 112a is assigned to communicate with the I / O card 132a via the universal I / O bus 136a (block). 1206). For example, the field device identifier 814 can communicate field device identification information to the I / O card 132a via the termination module 124a, which stores the field device identification information in the workstation 102. Can be compared to a stored data structure 133 (FIG. 1A) or a field device identification number stored in a similar data structure. Add to the data structure 133 the field device identification number of the field device (eg, field device 112a-c) that the engineer, operator, or user communicates to the I / O card 132a via the universal I / O bus 136a. be able to. If the I / O card 132a determines that the field device 112a is assigned to the I / O bus 136a and / or the I / O card 132a, the I / O card 132a sends a confirmation message to the field device identifier 814. Tell.

If the field device identifier 814 determines that the field device 112a is not assigned to communicate via the I / O bus 136a (block 1206), the display interface 808 (FIG. 8) displays an error message. (Block 1208). Otherwise, the display interface 808 displays field device identification information (block 1210). In the illustrative example, field device status detector 812 detects a field device status (eg, device on, device off, device error, etc.) and display interface 808 displays status information (block 1212). In addition, field device activity detector 810 (FIG. 8) detects activity (eg, measurement information and / or monitoring information) of field device 112a, and display interface 808 displays 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 the display interface 808 displays an error message (block 1208) or after the display interface 808 displays a data type (block 1216), the labeler 214 determines whether it should continue monitoring, eg, the termination module 124a. Is determined based on whether it has been turned off or removed from the marshalling cabinet 122 (FIGS. 1A and 2) (block 1218). If the labeler 214 determines that it should continue monitoring, control is returned to block 1202. Otherwise, the example process of FIG. 12 ends and / or control returns to the calling process or function.

  FIGS. 13A-13B illustrate an exemplary process before and after implementing the teachings disclosed herein for an exemplary Profibus PA process area 1302 and an exemplary FOUNDATION fieldbus H1 (FF-H1) process area 1304. 2 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 for illustrative purposes in the illustrative embodiment. Further, for purposes of explanation, the exemplary process control system 1300 of FIGS. 13A-13B will be described using the same reference numerals for common components described in connection with the exemplary process control system 100 of FIG. 1A. To explain. Accordingly, in the exemplary embodiment of FIG. 13A, process control system 1300 includes workstation 102 communicatively coupled to controller 1306 via LAN 106. The example controller 1306 can be substantially similar or the same as one of the controller 104, controller 152, and controller 162 of FIGS. 1A-1C. Further, the example process control system 1300 includes a first process area 114 associated with the field devices 112a-c, which is communicatively coupled to the termination modules 124a-c within the example marshalling cabinet 1308. Yes. An exemplary marshalling cabinet can be substantially similar or the same as any of the marshalling cabinet 122 and marshalling cabinet 300 of FIGS. 1A, 2 and 3. The termination modules 124a-c are communicatively coupled to I / O cards 132a-b in the controller 1306 via a first universal I / O bus 136a. Further, in the illustrated embodiment, the marshalling cabinet 1308 includes an additional termination that is substantially similar or identical to the socket rails 202a-b and socket rails 308a-b described above in connection with FIGS. A socket rail 1310 that receives the module is included.

  In the exemplary embodiment of FIG. 13A, exemplary process control system 100 includes field devices 1312a-c and FFs in Profibus PA process area 1302, implemented using traditional fieldbus architecture and components. -Field devices 1314a-c in H1 process control area 1304 (both Profibus PA and FF-H are protocols associated with 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. A fieldbus trunk or fieldbus segment typically includes a twisted pair of wires that carry 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 be connected to a maximum of 16 different field devices. As shown in the illustrated 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 the segments 1316a-b is connected to two I / O cards 1318a-b or I / O cards 1320a-b to provide redundancy. In some embodiments, I / O cards 1318a-b and / or I / O cards I1320a-b are separate from each other and / or associated with field devices 112a-c in first process area 114. / O cards 132a-b can reside in different controllers.

  In the exemplary embodiment of FIG. 13A, segment 1316a corresponding to exemplary 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, the DP / PA segment coupler 1322 and the power supply 1324 provide power regulation functions to each segment 1316a-b. In addition, in the illustrated embodiment, the DP / PA segment coupler 1322 and the power source 1324 can monitor the physical layer of the corresponding segment 1316a-b and the communication via the segments 1316a-b during operation, Coupled to advanced diagnostic modules 1325a-b.

  In the illustrated embodiment, 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 illustrated embodiment, each spool 1326a-c and spool 1328a-c has a segment protector 1330a-b (sometimes referred to as a device coupler or field barrier) to a corresponding segment 1316a-b. Are connected to each other to provide a short circuit prevention function against a short in one of the field devices 1312a-c and the field devices 1314a-c that short all segments. In some embodiments, segment protectors 1330a-b limit the current in each spool 1326a-c and spool 1328a-c (eg, to 40 mA). In some embodiments, segment protectors 1330a-b also function to properly terminate each segment 1316a-b at the end near the field device, while DP / PA segment coupler 1322 and power supply 1324 include It functions to terminate segments 1316a-b at the end near the controller. Without proper termination at both ends of segments 1316a-b, communication errors may occur due to signal reflections.

  As explained above, the fieldbus architecture offers many advantages, but the fieldbus architecture also presents challenges with respect to implementation complexity and cost. For example, the complexity of fieldbus systems, in particular, allows engineers to ensure that each segment is properly terminated and protected against short circuit, open circuit, and / or other segment failures, Each segment needs to be carefully designed 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 coupler 1322 or power supply 1324, segment protectors 1330a-b, and segment cables (in some cases for redundancy) There are additional costs associated with many components associated with such implementations, including 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 the implementation and maintenance of fieldbus systems 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 illustrated embodiment, field device 1312a-c and field device 1314a-c spools 1326a-c and spools 1328a-c were plugged into sockets on socket rail 1310 of marshalling cabinet 1308 shown in FIG. 13A. , Each termination module 1332a-f is directly communicatively coupled. That is, in contrast to the normal topology of field devices in a multi-drop architecture, in the illustrated embodiment, each fieldbus compliant field device 1312a-c and fieldbus compliant field device 1314a-c has a respective termination module 1332a-f. And point-to-point communication. Termination modules 1332a-f are in the same manner as described above via universal I / O bus 136a between field devices 1312a-c and field devices 1314a-c and I / O cards 132a-b. The termination modules 124a-c and the termination modules 126a-c described above, which enable the communication of the above, can be substantially similar or the same. In this way, separate I / O cards 1318a-b and I / O cards specific to the corresponding fieldbus protocol (eg, Profibus PA or FF-H1) associated with process area 1302 and process area 1304 Any type of field device and associated I / O can be combined in one marshalling cabinet 1308, eliminating the need for 1320a-b (FIG. 13A). Similarly, the need for cable trunks or segments 1316a-b (FIG. 13A) is eliminated with associated insulation. Further, in some embodiments, the universal I / O bus 136a is for faster communication (eg, via fiber optic cable) than the relatively slow communication backbone of a typical copper-based fieldbus segment. ) Provide a high-speed communication backbone. Further, in some embodiments, the universal I / O bus 136a can maintain communication for up to 96 field devices, while a regular fieldbus segment is limited to 16 device connections. ing. Thus, the number of wires coupled to the controller for the same number of field devices is greatly reduced.

  The plurality of field devices may be configured in a multi-drop configuration communicatively coupled to one termination module 1332a-f, which is common in fieldbus architectures in some embodiments, but is illustrated in the illustrated embodiment. A point-to-point or single-loop architecture provides 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 illustrated embodiment, termination modules 1332a-f provide power and power conditioning functions (eg, with reference to FIG. Can be provided to each field device (via the field power controller 610 described above). In this way, the separate DP / PA segment coupler 1322 and / or power source 1324 shown in FIG. 13A is no longer necessary. In addition, or alternatively, in some embodiments, the marshalling cabinet 1308 may include a power conditioner 218 to eliminate the need for a separate DP / PA segment coupler 1322 and / or power source 1324 shown in FIG. 13A. Including a power conditioner that is substantially similar or identical to (FIG. 2). Further, in such an embodiment, the power supply is local to the field device of the exemplary embodiment (eg, in the marshalling cabinet 1308), so the power requirement is a power supply that provides power along a normal fieldbus segment. Than (for example, due to the voltage drop resulting from the length of the cable). Further, in some embodiments, the termination modules 1332a-f provide short circuit protection (eg, via a corresponding field power controller 610) to provide current for each spool 1326a-c and spool 1328a-c. Limit, 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 integrity and is suitable for proper termination in a normal fieldbus architecture. Make your concerns less important. Further, the direct point-to-point connection between each field device 1312a-c and field device 1314a-c and the corresponding termination module 1332a-f is a complex associated with developing and implementing a regular fieldbus segment. And the design work is significantly reduced because the signals from each field device are received separately and handled or organized electronically at the back end. Thus, the costs of acquiring, configuring and maintaining many components of a typical fieldbus architecture, and the time and expense of designing such an architecture and ensuring their proper operation are disclosed herein. Through the implementation of teaching to be significantly reduced. In other words, in some embodiments, a fieldbus compliant device is included in the process control system, without any of the DP / PA couplers and / or power supplies in the segment (eg, in marshalling cabinet 122 and / or termination). (Other than the power supplies and / or power regulators in modules 1332a-f), without segment protectors, without protocol specific I / O cards, and without significant segment design work.

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

  Profibus PA and FF-H1 are both fieldbus protocols with the same physical layer. Accordingly, in some embodiments, termination modules 1332a-c associated with field devices 1312a-c in Profibus PA process area 1302 are terminated with termination modules 1332d associated with field devices 1314a-c in FF-H1 process area 1304. Same as ~ f. In other words, in some embodiments, spools 1326a-c connected to termination modules 1332a-c can be connected to termination modules 1332d-f, while spools 1328a-c are substituted for termination modules 1332d-f. Connected to termination modules 1332a-c. In some such embodiments, termination modules 1332a-f may be associated with a particular protocol (e.g., a particular field device 1312a-c and field device 1314a-c to which termination module 1332a-f is connected). , Profibus PA or FF-H1) is automatically detected. As a result, there is no concern that the process control system engineer must design separate fieldbus segments or obtain the corresponding components necessary to implement such fieldbus segments. In addition, the desired fieldbus device can be freely used regardless of the associated communication protocol (even devices that conform to different protocols can be mixed).

  In some embodiments, termination modules 1332a-f are intrinsically safe for implementing field devices 1312a-c and field devices 1314a-c in harmful environments (eg, Fieldbus Intrinsically Safe Concept ( It is made to comply with FISCO). In such an embodiment, the socket rail 1310 of the marshalling cabinet 1308 is also inherently safe. In some embodiments, the termination modules 1332a-f are made with a safety rating that is certified to be energy limited and / or has sufficient safety ratings to meet the Fieldbus Non-Inclusive Concept (FNICO). In some such embodiments, termination modules 1332a-f can comply with FNICO requirements even when plugged into a marshalling cabinet with inherently insecure socket rails.

  In addition or alternatively, in some embodiments, the termination module described herein is based on field devices and communication protocols other bus protocols (eg, other than Profibus PA or FF-H1). It is made to communicate. For example, in some embodiments, the termination module can be wired to a wireless HART gateway to interface with one or more wireless HART devices using the HART-IP application protocol. In addition or alternatively, in some embodiments, the wireless device may use other wireless technologies such as ISA (International Measurement and Control Society) 100.11a or WIA-PA (Wireless Networks for Industrial Automation-Process Automation). It can be interfaced using standards. In some embodiments, the termination module described herein is based on Internet Protocol (IP), such as using the 6TiSCH standard (IP version 6 over Time Slotted Channel Hopping (TSCH)) for devices. It 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. Further, in some embodiments, the safety field device may be integrated using a tunnel protocol between the safety environment and an associated safety controller such as, for example, PROFIsafe (Profibus safety device).

  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. The exemplary termination modules 1404a-b can be substantially similar or the same as the termination modules 1332a-f described above. Peer-to-peer communication between devices in the field is not provided for those using the Profibus PA fieldbus protocol, but such communication is possible when using the FF-H1 protocol, thereby Allows control within the field independent of the controller (eg, controller 1306 in FIG. 13A). In the exemplary embodiment of FIG. 14A, termination modules 1404a-b are substantially similar to base 402 (FIG. 4) except that bases 1406a-b are shown having four corresponding terminals 1408a-b. Or are connected to corresponding terminal block bases 1406a-b which are the same. In the illustrated embodiment, 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 from each base 1406a-b. Corresponding ones of the second pair of terminals 1408a-b are connected to each other. In this way, both field devices 1402a-b are communicatively coupled to each of termination modules 1404a-b and are communicatively coupled to each other.

  It is possible to couple separate field devices 1402a-b directly to each of the termination modules 1404a-b, as shown in the exemplary embodiment of FIG. 14A, where the termination modules 1404a-b This is because the adjustment function is provided to each field device 1402a-b (for example, via the field device controller 610). That is, the power adjustment provided by each termination module 1404a-b is such that a signal from one of the field devices (eg, field device 1402a) communicates with another field device (eg, field device 1402b). Plays a role in preventing distractions. However, as described above, in some embodiments, power regulation is provided collectively to all of the field devices on the same socket rail (eg, via injected power) by another power regulator 218. Is 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 the field devices 1402a-b is achieved through the segment protector 1412. Further, the segment protector 1412 prevents the power provided through the termination modules 1404a-b corresponding to each field device 1402a-b from affecting the communication of any of the field devices 1402a-b. In the exemplary embodiment of FIGS. 14A and 14B, additional wiring (eg, for shielding and / or grounding) has been omitted for clarity.

  The exemplary method of FIG. 15 will be described with respect to the exemplary termination module 1332a of FIG. 13B. However, other termination modules can be implemented using the exemplary method of FIG. Using the flowchart of FIG. 15, how the exemplary termination module 1332a automatically detects a communication protocol associated with a corresponding field device (eg, field device 1312a) connected to the termination module 1332a. Explain how. Initially, termination module 1332a determines whether a field device (eg, field device 1312a) is connected to termination module 1332a (eg, via connection detector 806 of FIG. 8) (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 is provided by the termination module 1332a to the field device 1312a (or other field device). ) Stays at block 1502 until it is determined that it is connected to the termination module 1332a.

  If the termination module 1332a determines that the field device 1312a is connected to the termination module 1332a (block 1502), the termination module 1332a receives the first communication (eg, via the field device communication processor 620 of FIG. 6). A request formatted according to a protocol (eg, Profibus PA) is sent (block 1504). In some embodiments, the request may correspond to a query requesting the field device to send its field device identification information, as described above in connection with block 1204 of FIG. Termination module 1332a then determines whether a response to the request has been received (block 1506). As described above with respect to block 1504, the request is formatted for a particular protocol. As a result, the only way the field device 1312a can recognize the request and respond to the request is when the field device 1312a is associated with the same protocol. Accordingly, if the termination module 1332a determines that a response has been received (block 1506), the termination module 1332a designates the communication protocol of the responded request as the protocol corresponding to the 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, the communication protocol corresponding to the field device 1312a is designated as Profibus PA.

If the termination module 1332a determines at block 1506 that a response to the request has not been received, the termination module 1332a may select another communication protocol (eg, via the field device communication processor 620) (eg, FF-H1). ) To send another request formatted according to (block 1508). Termination module 1332a then determines whether a response to the request has been received (block 1510). If the termination module 1332a determines that a response to the request has been received (block 1510), the termination module 1332a specifies the communication protocol of the responded request as the protocol corresponding to the field device 1312a (block 1516). If the termination module 1332a determines that a response to the request has not been received (block 1510), the termination module 1332a may communicate with additional communication protocols to be tried (eg, other than Profibus PA and FF-H1 (eg, HART)). Determine if there is. If there are additional communication protocols, control returns to block 1508 to send other requests formatted according to other communication protocols. If the termination module 1332a determines that there are no additional communication protocols to try, the termination module 1332a generates an error message (block 1514). For example, the error message may indicate that the field device 1312a is not responding and / or that the communication protocol corresponding to the 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 Control returns to the calling process or calling 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 identical to the exemplary processor system 1610, the 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 exemplary processor system 1610 is described below as including a plurality of peripherals, interfaces, chips, memories, etc., but one or more of those elements may be connected to the workstation 102, controller 104, I / 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, the processor system 1610 includes a processor 1612 coupled to an interconnection bus 1614. The processor 1612 includes a register set or register space 1616, which is illustrated in FIG. 16 as being completely on-chip, but alternatively may be completely or partially off-chip to the processor 1612. May be coupled directly via dedicated electrical connections and / or via interconnect bus 1614. The processor 1612 can be any suitable processor, processing unit, or microprocessor. Although not shown in FIG. 16, system 1610 can be a multiprocessor system and thus is the same or similar to processor 1612 and includes one or more communicatively coupled to interconnect bus 1614. Additional processors may be included.

  The processor 1612 of 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 includes multiple general purpose and / or memory functions that are accessible or used by I / O management functions, memory management functions, and one or more processors coupled to chipset 1618. Or provide special purpose registers, timers, etc. Memory controller 1620 performs functions that allow processor 1612 (or multiple processors if there are multiple processors) to access system memory 1624 and mass storage memory 1625.

  The system memory 1624 may be any desired type of volatile and / or nonvolatile memory such as, for example, static random access memory (SRAM), dynamic random access memory (DRAM), flash memory, read only memory (ROM), and the like. Can be included. The mass storage memory 1625 can include a desired type of mass storage device. For example, if the workstation 102 (FIG. 1A) is implemented using the exemplary processor system 1610, the mass storage memory 1625 may include a hard disk drive, an optical drive, a tape storage device, and so on. Alternatively, the exemplary processor system 1610 is used to control the controller 104, one of the I / O cards 132a-b and I / O cards 134a-b, or the termination modules 124a-c and termination module 126a. When implementing one of ˜c, the mass storage memory 1625 may be a semiconductor memory (eg, flash memory, RAM memory, etc.), a magnetic memory (eg, hard drive), or other suitable for mass storage Memory may be included in the controller 104, I / O cards 132a-b and I / O cards 134a-b, or termination modules 124a-c and termination modules 126a-c.

  Peripheral device I / O controller 1622 includes processor 1612, peripheral device input / output (I / O) device 1626, peripheral device input / output (I / O) device 1628, network interface 1630, and peripheral device I / O bus. Perform functions that allow communication via 1632. I / O device 1626 and I / O device 1628 include, for example, a keyboard, a display (eg, a liquid crystal display (LCD), a cathode ray tube (CRT) display, etc.), a navigation device (eg, a mouse, trackball, capacitive touch pad). , Joystick, etc.), etc., can be any desired type of I / O device. The network interface 1630 may be, for example, an Ethernet device, an asynchronous transfer mode (ATM) device, an 802.11 device, a DSL modem, a cable modem, a cellular modem, etc. that allows the processor system 1610 to communicate with other processor systems. Can be.

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

Although specific methods, apparatus, and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent includes all methods, devices, and articles of manufacture properly within the scope of the appended claims, either literally or under an equivalent theory.

Claims (28)

A first physical interface communicatively coupled to one of a first field device of the process control system or a second field device of the process control system;
A second physical interface communicatively coupled to the controller of the process control system via a bus;
A base comprising:
A module removably attached to the base, wherein the first physical device uses a first communication protocol when the first physical interface is communicatively coupled to the first field device. Communicating with the second field device using a second communication protocol when the first physical interface is communicatively coupled to the second field device; and A module that communicates via the bus using a third communication protocol, wherein the third communication protocol is different from the first and second communication protocols;
An apparatus comprising:   The apparatus of claim 1, wherein at least one of the first communication protocol or the second communication protocol is a fieldbus protocol.   The apparatus of claim 1, wherein the first communication protocol is a FOUNDATION fieldbus H1.   The apparatus according to claim 3, wherein the second communication protocol is Profibus PA.   4. The apparatus of claim 3, wherein the first field device is FOUNDATION fieldbus H1 compliant and is communicatively coupled to the first physical interface in a point-to-point architecture without a segment protector.   The apparatus of claim 1, wherein at least one of the first communication protocol or the second communication protocol is a wireless HART.   The apparatus of claim 1, wherein at least one of the first communication protocol or the second communication protocol is based on an Internet protocol.   The apparatus according to claim 1, wherein at least one of the first communication protocol or the second communication protocol is a Message Queue Telemetry Transport.   At least one of the first communication protocol or the second communication protocol implements a tunnel protocol and the corresponding at least one of the first field device or the second field device is a safety device The device of claim 1, wherein   The module sends a first request formatted according to the first communication protocol to the one of the first field device or the second field device, and the second communication A second request formatted according to a protocol is sent to the one of the first field device or the second field device and the first field device or the second field device The apparatus of claim 1, wherein the communication protocol associated with the one of them is automatically detected based on a response to one of the first and second requests.   A diagnostic analyzer for generating diagnostic information corresponding to an analysis of a physical layer and communication between the first physical interface and the one of the first field device or the second field device; The apparatus of claim 1, comprising:   The apparatus of claim 11, wherein the diagnostic information comprises a measurement result of at least one of supply voltage, negative charge, signal level, line noise, or jitter.   The third communication protocol conveys information on the bus from a second module in communication with the bus and with the other of the first field device or the second field device. The apparatus of claim 1.   The first physical interface of the base is communicatively coupled to a third physical interface of a second base removably attached to the second module, the first and second fields. The apparatus of claim 13, enabling peer-to-peer communication between devices.   The one of the first field device or the second field device is powered through the module, and the other of the first field device or the second field device is the first field device. 14. The apparatus of claim 13, powered by two modules, and wherein the first field device is communicatively coupled to the second field device via a segment protector. Receiving first information at a base having 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; ,
In a module removably attached to the base, encoding the first information for communication using a first communication protocol, wherein the first information is the first information. When the physical interface of the first field device is coupled to the first field device, the module is conveyed from the first field device using a second communication protocol, and the first information is transmitted to the first physical device. When an interface is coupled to the second field device, the module is communicated from the second field device using a third communication protocol, the first communication protocol being the first and second Different from the communication protocol with the encoding,
Conveying the encoded first information from the module to a controller via the second physical interface of the base via a bus using the first communication protocol;
A method comprising:   The method according to claim 16, wherein the second communication protocol is Profibus PA and the third communication protocol is a FOUNDATION fieldbus H1.   Of the first field device or the second field device when the one of the first field device or the second field device is communicatively coupled to the first physical interface; The method of claim 17, further comprising automatically detecting the second communication protocol or the third communication protocol associated with the one. The second communication protocol or the third communication protocol;
Sending a first request to the one of the first field device or the second field device, wherein the first request is formatted according to the second communication protocol; Sending a first request; and
Sending a second request to the first field device or the one of the second field devices, wherein the second request is formatted according to the third communication protocol. Sending a second request, wherein:
If a response to the first request is received, determining that the one of the first field device or the second field device is associated with the second communication protocol; ,
If a response to the second request is received, determining that the first field device or the one of the second field devices is associated with the third communication protocol; ,
19. The method of claim 18, further comprising automatically detecting by.   Further comprising monitoring a physical layer and communication between the first physical interface and the one of the first field device or the second field device to generate diagnostic information; The method of claim 16.   21. The method of claim 20, wherein the diagnostic information comprises a measurement result of at least one of supply voltage, negative charge, signal level, line noise, or jitter. A first 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 when coupled to the first field device; A first interface that communicates using a first fieldbus communication protocol and communicates using a second fieldbus communication protocol when coupled to the second field device;
A communication processor communicatively coupled to the first interface, wherein the first information received from the one of the first field device or the second field device is the first and second fields; A communication processor that encodes for communication over a bus that uses a third communication protocol that is different from the second fieldbus communication protocol;
A second communicatively coupled to the communication processor and the bus to communicate the first information to the controller of the process control system via the bus using the third communication protocol; A second interface, wherein the bus carries second information received from the other of the first field device or the second field device using the third communication protocol; Interface,
An apparatus comprising:   23. The apparatus of claim 22, wherein the first fieldbus communication protocol is Profibus PA.   24. The apparatus of claim 23, wherein the second fieldbus communication protocol is a FOUNDATION fieldbus H1.   24. The apparatus of claim 23, wherein the first field device is Profibus PA compliant and is communicatively coupled to the first interface in a point-to-point architecture without a DP / PA segment coupler.   The communication processor sends a first request formatted according to the first fieldbus communication protocol to the one of the first field device or the second field device; A second request formatted according to two fieldbus communication protocols is transmitted to the first field device or the one of the second field devices, and the first field device or the second field device 23. The method of claim 22, wherein the communication protocol associated with the one of two field devices is automatically detected based on a response to one of the first and second requests. The device described.   A diagnostic analyzer for generating diagnostic information corresponding to an analysis of a physical layer and communication between the first interface and the one of the first field device or the second field device; 23. The apparatus of claim 22, comprising.   28. The apparatus of claim 27, wherein the diagnostic information comprises a measurement result of at least one of supply voltage, negative charge, signal level, line noise, or jitter.