JP2021119496A - Apparatus to communicatively couple field devices to controllers in process control system, computer-readable medium, and apparatus - Google Patents

Abstract

To provide an apparatus and a method to communicatively couple field devices to controllers in a process control system.SOLUTION: Included is a first interface to be communicatively coupled to one of a first field device or a second field device. The first interface communicates using a first fieldbus communication protocol when coupled to the first field device and communicates using a second fieldbus communication protocol when coupled to the second field device. The apparatus includes a second interface communicatively coupled to the communication processor and a bus in order to encode first information received from the one of the first field device or the second field device for communication via a bus using a third communication protocol and to transmit 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 one of the first field device or the second field device.SELECTED DRAWING: None

Description

The present disclosure generally relates to process control systems, and more specifically to devices and methods for communicatively linking field devices to controllers in process control systems.

Process control systems, such as those used in chemical, petroleum, pharmaceutical, pulp and paper, or other manufacturing processes, typically have at least one host, including at least one operator workstation, and analog, digital, or analog / Includes one or more field devices configured to communicate over a digital composite communication protocol and one or more process controllers communicatively linked to. For example, device controllers, valves, valve actuators, valve positioners, switches and transmitters (eg, temperature sensors, pressure sensors, flow rate sensors, and chemical composition sensors), or field devices that may be combinations thereof, are within the process control system. Perform functions such as opening and closing valves, and measuring or inferring process parameters. The process controller receives signals indicating the results of process measurements made by the field device and / or other information about the field device and uses this information to implement control routines over the bus or other communication line. Generates control signals sent to field devices to control the operation of process control systems.

The process control system offers several different functions, either point-to-point (for example, one field device is communicatively linked to the field device bus) or multi-drop (for example, multiple field devices are in the field). Includes multiple field devices that are often communicatively connected to the process controller using a two-wire interface in a wiring connection configuration (which is communicatively connected to the device bus) or by wireless communication. Can be done. Some field devices are configured to operate using relatively simple commands and / or communications (eg, ON and OFF commands). Other field devices are more complex and require more commands and / or more communication information, which may or may not contain simple commands. For example, more complex field devices can convey analog values with digital communication superimposed on them using, for example, the Highway Adpressable 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 connected to a process controller via one or more I / O cards and each communication medium (eg, 2-wire cable, wireless link, or fiber optic). There is. Therefore, a plurality of communication media are required in order to communicatively connect a plurality of field devices to the process controller. Often, multiple communication media attached to a field device are routed through one or more field junction boxes, where the multiple communication media have one or more I / Os of the field device to the process controller. It is connected to each communication medium (for example, each two-wire conductor) of a multi-core cable used for communicative connection via a / O card.

An exemplary device and method for communicatively connecting a field device to a controller in a process control system will be described. According to one embodiment, the exemplary device includes a base and a module detachably attached to the base. The base is a first physical interface communicatively linked to one of the first field devices of the process control system or the second field device of the process control system, and a bus to the controller of the process control system. Includes a second physical interface that is communicatively linked. The module communicates with the first field device using the 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 the second communication protocol when the first physical interface is communicatively coupled to the second field device. The module communicates with the controller over a bus that uses a third communication protocol. The third communication protocol is different from the first and second communication protocols.

According to another embodiment, the exemplary method communicatively links the first information to one of the first field device of the process control system or the second field device of the process control system. Accompanied by receiving at a base having a first physical interface. An exemplary method also involves encoding a first piece of information for communication using the first communication protocol in a module that is detachably mounted on the base. The first information transmitted to the module from the first field device using the second communication protocol when the first physical interface is attached to the first field device. The first information transmitted from the second field device to the module using the third communication protocol when the first physical interface is attached to the second field device. The first communication protocol is different from the first and second communication protocols. The method further involves transmitting the encoded first information from the module via the base second physical interface to the controller via the bus using the first communication protocol.

According to yet another embodiment, the exemplary device is a first interface that is communicatively coupled to one of the first field device of the process control system or the second field device of the process control system. including. The first interface communicates using the first fieldbus communication protocol when connected to the first field device and the second fieldbus communication protocol when connected to the second field device. Use to communicate. An exemplary device includes a communication processor communicatively coupled to a first interface. The communication processor is one of a first field device or a second field device for communication over a bus that uses a third communication protocol that is different from the first and second fieldbus communication protocols. The first information received from one is encoded. An exemplary device is a second communicatively coupled to a communication processor and a bus to convey first information to a controller in a process control system via a bus using a third communication protocol. Includes interface. The bus uses a third communication protocol to convey a second piece of information received from either the first field device or the second field device.

It is a block diagram which showed an exemplary process control system. FIG. 5 is a diagram of an alternative exemplary implementation that can be used to communicatively connect a workstation, a controller, and an I / O card. FIG. 5 is a diagram of an alternative exemplary implementation that can be used to communicatively connect a workstation, a controller, and an I / O card. FIG. 5 is a diagram of an alternative exemplary implementation that can be used to communicatively connect a workstation, a controller, and an I / O card. It is a detailed view of the exemplary marshalling cabinet of FIG. 1A. Another exemplary marshalling cabinet that can be used to implement the exemplary marshalling cabinet of FIG. 1A. It is a top view and a side view of the exemplary termination module of FIGS. 1A and 2. It is a top view and a side view of the exemplary termination module of FIGS. 1A and 2. It is a detailed block diagram of an exemplary termination module of FIGS. 1A, 2 and 4, 5 and 13A to 13B and 14A to 14B. It is a detailed block diagram of the exemplary I / O card of FIG. 1A. Illustrative, which can 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 labeler. FIG. 5 is a diagram of an isolated circuit configuration that may be implemented in connection with the exemplary termination module of FIG. 1A to electrically insulate the termination modules from each other, the field device and the communication bus. Examples that can be used to implement the termination modules of FIGS. 1A and 2-6 and 13A-13B and 14A-14B to convey information between the field device and the I / O card. It is a flowchart of a typical method. Examples that can be used to implement the termination modules of FIGS. 1A and 2-6 and 13A-13B and 14A-14B to convey information between the field device and the I / O card. It is a flowchart of a typical method. FIG. 6 is a flow chart of an exemplary method that can be used to implement the I / O card of FIG. 1A to convey information between a termination module and a workstation. FIG. 6 is a flow chart of an exemplary method that can be used to implement the I / O card of FIG. 1A to convey information between a termination module and a workstation. An exemplary method that can be used to implement the labels of FIGS. 2 and 3 and 6 and 8 to read and display information related to a field device communicatively coupled to a termination module. It is a flowchart. In a block diagram showing another exemplary process control system before and after implementing the teachings disclosed herein with respect to an exemplary Profibus PA process area and an exemplary FOUNDATION fieldbus H1 (FF-H1) process area. be. In a block diagram showing another exemplary process control system before and after implementing the teachings disclosed herein with respect to an exemplary Profibus PA process area and an exemplary FOUNDATION fieldbus H1 (FF-H1) process area. be. FIG. 5 is an alternative exemplary implementation of peer-to-peer communication of two FF-H1-compliant field devices communicatively coupled to a corresponding termination module. FIG. 5 is an alternative exemplary implementation of peer-to-peer communication of two FF-H1-compliant field devices communicatively coupled to a corresponding termination module. Implement the termination modules of FIGS. 1A, 2-6, 13A-13B and 14A-14B to automatically detect the communication protocol associated with the corresponding field device connected to the termination module. It is a flowchart of an exemplary method that can be used for. FIG. 6 is a block diagram of an exemplary processor system that can be used to implement the exemplary 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 considered as a limitation. For example, some or all of these hardware, software, and firmware components can be embodied in hardware alone, software alone, or in any combination of hardware and software. , Is considered. Thus, although the following describes exemplary devices and systems, one of ordinary skill 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 in FIG. 1A). A process area is an operation related to performing a particular process (eg, chemical process, petroleum process, pharmaceutical process, pulp and paper process, etc.) (eg controlling valves, controlling motors, boilers, etc.) Includes multiple field devices that perform (controlling, monitoring, measuring parameters, etc.). Some process areas are inaccessible to humans due to harsh environmental conditions (eg, relatively high temperatures, airborne toxins, dangerous radiation levels, etc.). The control room typically includes one or more workstations in an environment that is safely accessible to humans. Workstations include user applications that allow users (eg, engineers, operators, etc.) to access the control operations of a process control system by, for example, changing variable values, process control functions, and so on. The process control area includes one or more controllers communicatively connected to a workstation in the control room. The controller automates the control of field devices within the process area by executing process control strategies implemented through workstations. 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 the 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, a marshalling cabinet is used for organizing, summarizing, or transferring signals from field devices to one or more I / O cards communicatively coupled to a controller. Includes modules. The I / O card converts the information received from the field device into a format compatible with the controller and the information from the controller into a format compatible with the field device.

A technique used and known to communicately connect field devices in a process control system to a controller is to communicate with each field device and the controller (eg, process controller, programmable logical controller, etc.). It involves using a separate bus (eg, wire, cable, or circuit) to and from 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, Connected communicatively by translating or translating the information transmitted between the controller and the field device into multiple field devices associated with different field device communication protocols (digital in data types and digital out data types). Allows you to. For example, the I / O card can be provided with one or more field device interfaces configured to exchange information with the field device using the 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) that the controller can use to perform operations related to controlling the field device (eg, pressure). It can be converted to (measured value). Known techniques require bundles of wires or buses (eg, multi-core cables) that communicatively connect multiple field devices to an I / O card. Unlike known techniques that use separate buses to communicately connect each field device to an I / O card, the exemplary devices and methods described herein are multiple field devices. Is terminated by 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 connected between the termination panel and the I / O card is connected. It can be used to communicatively connect a field device to an I / O card by communicatively linking the field device to an I / O card.

The exemplary devices and methods described herein are exemplary, in which one or more termination modules are communicatively coupled to one or more I / O cards communicatively coupled to a controller. Accompanied by 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 each field device bus (eg, analog bus or digital bus). The termination module receives field device information from the field device via the field device bus, for example, packetizes the field device information and transmits the packetized information to the I / O card via the universal I / O bus. The field device information is configured to be transmitted to the I / O card via the 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) value), field device description information (eg, field device type or function such as 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 (for example, a field device bus or field device segment through which a field device is communicatively attached to a termination module). And / or field device data type information (eg, a data type descriptor indicating the data type used by a particular field device) can be included. The I / O card can extract the field device information received via the universal I / O bus and convey the field device information to the controller, which will then be part 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 values), etc.) from the workstation terminal to the field device, the I / O card packets the field device information. Packetized field device information can be transmitted to multiple termination modules. Each of the termination modules can then extract each field device information from the packetized communication received from each I / O card or depacketize it and convey the field device information to each field device.

In the exemplary embodiments described herein, the termination panel (eg, a marshalling cabinet) is configured to accept (eg, connect) multiple termination modules, each of which is a different field device. Is communicated with. 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 device is connected to the termination module corresponding to the termination labeler. In some exemplary implementations, the display is mounted on 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 use by the later connected termination module.

With reference to FIG. 1A, the exemplary process control system 100 is communicatively coupled to the controller 104 via a bus or local area network (LAN) 106, commonly referred to as an application control network (ACN). Includes workstation 102. LAN 106 can be implemented using the desired communication medium and protocol. For example, 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. 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, workstation 102 allows workstation 102 and controller 104 to communicate with other devices or systems using desired communication media (eg, wireless, wired, etc.) and protocols (eg, HTTP, SOAP, etc.). It may be configured to perform operations related to process control related applications and communication applications that allow it to be performed. Controller 104 is one or more processes created by a system engineer or other system operator, for example using workstation 102 or another workstation, and already downloaded and instantiated within controller 104. It can be configured to perform control routines or functions. In an exemplary embodiment, the workstation 102 is located in the control room 108 and the controller 104 is located in a process controller area 110 separate from the control room 108.

In an exemplary embodiment, the exemplary process control system 100 includes field devices 112a-c in a first process area 114 and field devices 116a-c in a second process control area 118. In order to convey information between the controller 104, the field devices 112a-c and the field devices 116a-c, an exemplary process control system 100 has a field junction box (FJB) 120a-b and a marshalling cabinet 122. It is provided. Each of the field junction boxes 120a-b transfers signals from each one of the field devices 112a-c and the field devices 116a-c to the marshalling cabinet 122. Next, the marshalling cabinet 122 organizes (for example, grouping, classifying, etc.) the information received from the field devices 112a to 112a to c and the field devices 116a to 116a to c, and collects the field device information into each I / O card of the controller 104. (For example, I / O cards 132a to 132a and I / O cards 134a to b) are transferred. In the exemplary embodiment, the marshalling cabinet 122 is also used to transfer the information received from the I / O card of the controller 104 to each one of the field devices 112a-c and the field devices 116a-c in the field junction box. Communication between the controller 104 and the field devices 112a-c and 116a-c is bidirectional, such as forwarding via 120a-b.

In an exemplary embodiment, the field devices 112a-c are communicatively coupled to the field junction box 120a via an electrically conductive communication medium, a wireless communication medium, and / or an optical communication medium, with the field devices 116a-c , Communicatically connected to the field junction box 120b. For example, field junction boxes 120a-b may include one or more electrical data transceivers for communicating with electrical, wireless, and / or optical transceivers between field devices 112a-c and field devices 116a-c. Wireless data transceivers and / or optical data transceivers are provided. In an exemplary embodiment, the field junction box 120b is wirelessly and communicatively coupled to the field device 116c. In an alternative exemplary implementation, the marshalling cabinet 122 can be omitted and signals from field devices 112a-c and field devices 116a-c can be signaled from field junction boxes 120a-b to controller 104 I / O. It can be transferred directly to the card. In yet another exemplary implementation, the field junction boxes 120a-b can be omitted and the field devices 112a-c and field devices 116a-c can be directly connected to the marshalling cabinet 122.

Field devices 112a-c and field devices 116a-c can be fieldbus compliant valves, actuators, sensors, etc., where field devices 112a-c and field devices 116a-c are well known. Communicates via a digital data bus that uses a FOUNDATION fieldbus communication protocol (eg, FF-H1). Of course, other types of field devices and communication protocols can be used instead. For example, field devices 112a-c and field devices 116a-c instead communicate via a data bus using the well-known Profibus and HART communication protocols, Profibus (eg, Profibus PA), HART. , Or it can be an AS-i compliant device. In some exemplary implementations, field devices 112a-c and field devices 116a-c can convey information using analog or discrete communication instead of digital communication. In addition, communication protocols can be used to convey information related to different data types.

Each of the field devices 112a to 112a to c and the field devices 116a to 116a to c is configured to store the 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, or the like that uniquely identifies each of the field devices 112a to 116a to 116a to c. In the exemplary embodiment of FIG. 1A, the field devices 112a-c store the field device identification information in the form of physical device tag values PDT0-PDT2, and the field devices 116a-c physically store the field device identification information. Device tag values are stored in the format of PDT3 to PDT5. The field device identification information is provided in the field devices 112a-c and the field devices 116a-c by the field device manufacturer and / or the operator or engineer involved in the installation of the field devices 112a-c and the field devices 116a-c. Can be memorized or programmed by.

In order to transfer information related to the field devices 112a to 112a to the field devices 116a to c in the marshalling cabinet 122, the marshalling cabinet 122 is provided with a plurality of termination modules 124a to c and termination modules 126a to c. ing. Termination modules 124a-c are configured to organize information related to field devices 112a-c in the first process area 114, and termination modules 126a-c are field devices 116a in the second process area 118. It is configured to organize information related to ~ c. As shown, the termination modules 124a to 124a and the termination modules 126a to 126 communicate with each other in the field junction boxes 120a to 120a via the respective multi-core cables 128a and the multi-core cables 128b (for example, multibus cables). It is connected. In an alternative exemplary implementation in which the marshalling cabinet 122 is omitted, the termination modules 124a-c and the termination modules 126a-c may be installed in each one of the field junction boxes 120a-b.

In the illustrated embodiment of FIG. 1A, each conductor or conductor pair (for example, bus, twisted pair communication medium, 2-wire communication medium, etc.) in the multi-core cable 128a to 128b is a field device 112a to 112a to a field device 116a to It shows a point-to-point configuration in which information uniquely related to each one of c is communicated. 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, the second conductor. Reference numeral 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 is used to form information, termination module 124c. Is used to form a third data bus configured to communicate with the field device 112c. In an alternative exemplary implementation using a multi-drop routing configuration, each of the termination modules 124a-c and the termination modules 126a-c may be communicatively coupled to one or more field devices. For example, in a multi-drop configuration, the termination module 124a may be communicatively coupled to a field device 112a and another field device (not shown) via a first conductor 130a. In some exemplary implementations, the termination module may be configured to communicate wirelessly with multiple field devices using a wireless mesh network.

In addition, or alternative, in some embodiments, the second field device (not shown) is redundant, spare, or added to the field device 112a via the first conductor 130a in the termination module 124a. It is communicatively linked as an exchange field device. In some such embodiments, the termination module 124a replaces the spare device with the field device 112a until the termination module 124a needs to communicate (eg, when the field device 112a fails). When set), it is configured to communicate only with the field device 112a. That is, there are two devices communicatively connected to the termination module 124a via the first conductor 130a, but unlike the multi-drop configuration, the termination module 124a and either the field device 112a or the spare field device The communication between them actually works as a point-to-point connection. More specifically, the termination module 124a can detect a spare field device, but at a time when communication is initiated with the spare field device (either automatically or at the direction of the process control). All communication is directed to the primary or operating device (eg, field device 112a) until the operating device fails. In some embodiments, the spare field device is provided while the failed field device 112a is still in the process control system (eg, before being physically removed and / or being erased from the system's logical configuration). , Appointed and initiates communication with the termination module 124a. In some such embodiments, the spare field device remains a "spare" destination until the worker designates the spare field device as the new primary device. In another embodiment, the termination module 124a automatically replaces a spare field device with a field device 112a once the field device 112a fails. The ability to configure a spare field device to take over communication in this way is usually not available for certain communication protocols (eg, HART), which means that individual field devices have an I / O card. This is because they are directly connected to each other by a point-to-point method. As a result, replacement of a failed field device usually involves the physical removal of the field device, the installation of a new field device, and the subsequent manual appointment of the new field device. However, in some disclosed embodiments, the field device 112a is an independent reserve on the first conductor 130a when implemented using the HART protocol for faster replacement, as described more fully below. It is indirectly connected to an I / O card via a termination module 124a on a high speed universal I / O bus that has sufficient bandwidth to handle the presence of field devices. The spare field device on the first conductor 130a may also be implemented in addition to or instead of HART in other communication protocols (eg, Profibus PA, FF-H1, etc.).

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

To control I / O communication between the controller 104 (and / or workstation 102) and the field devices 112a-c and the field devices 116a-c, the controller 104 may include a plurality of I / O cards 132a-. b and I / O cards 134a-b are provided. In an exemplary embodiment, the I / O cards 132a-b control I / O communication between the controller 104 (and / or workstation 102) and the field devices 112a-c in the 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.

In the exemplary embodiment of FIG. 1A, the I / O cards 132a-b and the I / O cards 134a-b are present in the controller 104. The I / O cards 132a-b and the I / O cards 134a-b transmit the information to the controller 104 in order to transmit the information from the field devices 112a-c and the field devices 116a-c to the workstation 102, and the controller 104 , Communicate information to workstation 102. Similarly, in order to convey information from workstation 102 to field devices 112a-c and field devices 116a-c, the workstation 102 transmits the information to the controller 104, which in turn transmits the information to the I / O card. The information is transmitted to 132a to 132a and I / O cards 134a to b, and the I / O cards 132a to b and the I / O cards 134a to b terminate the information to the field devices 112a to c and the field devices 116a to c. It is transmitted via the modules 124a to c and the termination modules 126a to c. In an alternative exemplary implementation, the I / O cards 132a-b and the I / O cards 134a-b can be communicatively linked to the LAN 106 inside the controller 104, and the I / O cards 132a-b. And the I / O cards 134a-b can communicate directly with the workstation 102 and / or the controller 104.

The I / O card 132b and the I / O card 134b are configured as redundant I / O cards in order to provide fault-tolerant operation when either the I / O card 132a or the I / O card 134a fails. Has been done. That is, when the I / O card 132a fails, the redundant I / O card 132b controls, and if it does not fail, the same operation that the I / O card 132a would have performed is executed. Similarly, the redundant I / O card 134b controls when the I / O card 134a fails.

To enable 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 are , I / O cards 132a to 132a are communicatively connected to the I / O cards 132a to 136a via the first universal I / O bus 136a, and the termination modules 126a to c are connected to the I / O cards 134a to the second universal I / b. It is communicatively connected via the O-bus 136b. Unlike the multi-core cable 128a and the multi-core cable 128b, which use separate conductors or communication media for each one of the field devices 112a-c and 116a-c, the universal I / O buses 136a-b. Each of the above is configured to communicate information corresponding to a plurality of field devices (for example, field devices 112a to 112a to c and field devices 116a to 116a to c) using the same communication medium. For example, a communication medium is a serial bus, two-wire communication through which information related to two or more field devices can be communicated using, for example, packet-based communication technology, multiplexing communication technology, and the like. It can be a medium (eg, a twisted pair), an optical fiber, a parallel bus, and so on.

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

The universal I / O bus 136a and the universal I / O bus 136b are used to convey information in substantially the same way. In an exemplary embodiment, the I / O bus 136a is configured to convey information between the I / O cards 132a-b and the termination modules 124a-c. The I / O cards 132a-b and the termination modules 124a-c use an address scheme to identify which information the I / O cards 132a-b correspond to which of the termination modules 124a-c. Each of the termination modules 124a-c can determine which information corresponds to which of the field devices 112a-c. A termination module (eg, one of termination modules 124a-c and one of termination modules 126a-c) is connected to one of I / O cards 132a-b and I / O cards 134a-b. When present, the I / O card automatically obtains the address of the termination module (for example, from the termination module) and exchanges information with the termination module. In this way, the termination modules 124a-c and the termination modules 126a-c assign the termination module addresses to the I / O cards 132a-b and the I / O cards 134a-b anywhere on their respective buses 136a-b. Without the need to manually supply to, and without the need to wire the termination modules 124a-c and the termination modules 126a-c individually to the I / O cards 132a-b and I / O cards 134a-b, respectively. , Can be connected communicatively.

By using the universal I / O buses 136a-b, the number of communication media (eg, wires) required to convey information between the marshalling cabinet 122 and the controller 104 is each termination to communicate with the controller. Significantly reduced for known configurations that require separate communication media for the module. Reducing the number of communication media required to communicatively connect the marshalling cabinet 122 to the controller 104 (eg, reducing the number of communication buses or communication wires) requires the controller 104 and field devices 112a-c and fields. Reduce the 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 and maintenance costs. For example, one of the I / O buses 136a-b replaces a plurality of communication media used in known systems for communicatively linking field devices to a controller. Thus, instead of maintaining a plurality of communication media for communicatively linking the field devices 112a-c and the field devices 116a-c to the I / O cards 132a-b and the I / O cards 134a-b. The illustrated embodiment of FIG. 1A requires significantly less maintenance by using the I / O buses 136a-b. In addition, 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 a relevant field. Reduce or eliminate costs associated with the acquisition, installation and maintenance of other components used to implement the bus architecture. For example, in addition to cables for fieldbus architecture trunks or segments, Profibus PA and FF-H1 each typically have a protocol-specific I / O card and a power regulator (for FF-H1). Alternatively, a DA / PA coupler (for Profibus PA) and a segment protector are required. However, such components are no longer required for field devices coupled to the termination modules 124a-c and the termination modules 126a-c to communicate with the controller via the universal I / O buses 136a-b. In addition, in some embodiments where each fieldbus device is connected to the corresponding termination modules 124a-c or termination modules 126a-c in a point-to-point architecture, the cost and complexity of the fieldbus segment design task is high. It can be significantly reduced or eliminated because the device signal cleanup is handled electronically after being received by each corresponding termination module.

In addition, reducing the number of communication media required to communicatively connect the marshalling cabinet 122 to the I / O cards 132a-b and the I / O cards 134a-b can result in more termination modules (eg, for example). It provides more available space for 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 can 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 transmits data via one universal I / O bus 136a, which is greater than the number of field devices that transmit data via other types of bus communication. It is possible to have more termination modules 124a-c corresponding to the field devices 112a-c. For example, a fieldbus segment is typically restricted to carry signals for up to 16 field devices. In contrast, in some embodiments, one of the universal I / O buses 136a-b provides communications associated with up to 96 termination modules 124a-c and termination modules 126a-c. Can be done.

I / O cards 132a-b and I / O cards 134a can be configured to use different data type interfaces (eg, different channel types) to communicate with field devices 112a-c and field devices 116a-c. By providing termination modules 124a-c and termination modules 126a-c configured to use their respective common I / O bus 136a and common I / O bus 136b to communicate with ~ b. In the exemplary embodiment of FIG. 1A, different field device data types (eg, different field device data types (eg, eg) without the need to implement a plurality of different field device interface types on the I / O cards 132a-b and the I / O cards 134a-b. Data related to the data type or channel type used by the field devices 112a-c and the field devices 116a-c) can be transferred to the I / O cards 132a-b and the I / O cards 134a-b. To. Thus, I / O cards with one interface type (eg, I / O bus interface type for communicating via I / O bus 136a and / or I / O bus 136b) have different field device interface types. It can communicate with a plurality of field devices having it.

Using the I / O bus 136a and / or the I / O bus 136b, exchanging information between the controller 104 and the termination modules 124a-c and the termination modules 126a-c is an I / O from a 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 can be placed at various locations within the marshalling cabinet 122 while maintaining access to each one of the I / O bus 136a and the I / O bus 136b. Can be placed.

In an exemplary 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 controller 104 are existing process control system equipment. , It facilitates the transition to a configuration substantially similar to the configuration of the exemplary process control system 100 of FIG. 1A. For example, the termination modules 124a-c and the termination modules 126a-c can be configured to include the appropriate field device interface type, so that the termination modules 124a-c and the termination modules 126a-c are in the process control system. It may be configured to be communicatively linked to an existing field device already installed in. Similarly, the controller 104 may be configured to include a known LAN interface for communicating over 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 a process control system. Avoid the need to replace an already installed controller.

In an exemplary embodiment, the I / O card 132a comprises data structure 133 and the I / O card 134a comprises data structure 135. The data structure 133 is assigned a field device identification number (eg, a field) corresponding to a field device (eg, field devices 112a-c) assigned to communicate with the I / O card 132a via the universal I / O bus 136a. Device identification information) is stored. Termination modules 124a-c can use the field device identification numbers stored in the data structure 133 to determine if the field device is incorrectly connected to one of the termination modules 124a-c. can. The data structure 135 corresponds to a field device (eg, field devices 116a-c) assigned to communicate with the I / O card 134a via the universal I / O bus 136b (eg, field). Device identification information) is stored. Data structures 133 and 135 may be added by engineers, operators, and / or users via workstation 102 during the configuration time or operation of the exemplary process control system 100. In some embodiments, the termination modules 124a-c may be communicatively coupled to multiple field devices (eg, a running field device and a redundant or spare field device). In such an embodiment, the 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. In addition or alternatives, the data structure 133 and the data structure 135 can be stored in the workstation 102.

In an exemplary embodiment, the marshalling cabinet 122 is shown located in a termination area 140 separate from the process control area 110. Instead of significantly more communication media, I / O buses 136a-b (eg, one of field devices 112a-c and field devices 116a-c, respectively, or their limited group along a multi-drop segment. By communicatively connecting the termination modules 124a to 124a to the termination modules 126a to c to the controller 104 using a plurality of uniquely associated communication buses), the reliability of communication is not significantly reduced. In addition, it facilitates the placement of the controller 104 relatively far from the marshalling cabinet 122 than known configurations. In some exemplary implementations, the process control area 110 and the termination area 140 can be combined so 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 an area different from the process area 114 and the process area 118 means that the I / O cards 132a to 132a and the I / O cards 134a to b. Termination modules 124a-c, termination modules 126a-c, and universal I / O buses 136a-b can be associated with harsh environmental conditions (eg, heat, humidity, electromagnetic noise, etc.) that can be associated with process area 114 and process area 118. ) Allows isolation. 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. Can be significantly reduced against the cost of manufacturing communication and control circuits between and field devices 116a-c, which are the termination modules 124a-c and the termination modules 126a-c, and the I / O cards 132a-b. And to ensure the reliable operation (eg, reliable data communication) required for the I / O cards 134a-b to operate under the environmental conditions of process area 114 and process area 118. This is because it does not require the required operating specification characteristics (eg, shielding, more robust circuits, more complex error checking, etc.).

1B-1D show alternative exemplary implementations that can be used to communicatively connect a workstation with a controller and an I / O card. For example, in the exemplary embodiment shown in FIG. 1B, the controller 152 (performing substantially the same function as the controller 104 in FIG. 1A) is the I / O cards 154a-b and the I / O cards 156a-b. It is communicatively connected via the backplane communication bus 158. The I / O cards 154a-b and I / O cards 156a-b perform substantially the same functions as the I / O cards 132a-b and the I / O cards 134a-b of FIG. 1A, and provide information to the termination module. It is configured to be communicatively connected to universal I / O buses 136a-b for communicating with 124a-c and termination modules 126a-c. To communicate with workstation 102, the controller 152 is communicatively connected to workstation 102 via LAN 106.

In another exemplary embodiment shown in FIG. 1C, controller 162 (performing substantially the same function as controller 104 in FIG. 1A) is the workstation 102 and a plurality of I / O cards 164a-b and I /. It is communicatively connected to the O cards 166a to 166a via the LAN 106. The I / O cards 164a-b and 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. 1A, and provide information to the termination module. It is configured to be communicatively connected to universal I / O buses 136a-b for communicating with 124a-c and termination modules 126a-c. However, the I / O cards 132a to 132a to I / O cards 134a to b in FIG. 1A are different from the I / O cards 154a to 154a to b and the I / O cards 156a to b in FIG. The b and the I / O cards 166a to 166b are configured to communicate with the controller 162 and the workstation 102 via the LAN 106. In this way, 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 (performing substantially the same functions as the I / O cards 132a-b and I / O cards 134a-b of FIG. 1A). And I / O cards 176a-b are mounted within workstation 172 (performing substantially the same function as workstation 102 in FIG. 1A). In some exemplary implementations, the physical I / O cards 174a-b and I / O cards 176a-b are not included within workstation 172, but the I / O cards 174a-b and I. Functions with / O cards 176a-b are implemented within 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 the termination modules 126a-c. It is configured to be communicatively connected to buses 136a to 136b. Also, in the exemplary embodiment of FIG. 1D, workstation 172 is configured to perform substantially the same function as controller 104 so that it is not necessary to provide a controller to perform process control strategies. Can be done. However, a controller can be provided.

FIG. 2 is a detailed view of the exemplary marshalling cabinet 122 of FIG. 1A. In an exemplary embodiment, the marshalling cabinet 122 is provided with socket rails 202a and socket rails 202b that accept termination modules 124a-c. In addition, the marshalling cabinet 122 is provided with an I / O bus transceiver 206 that communicatively connects the termination modules 124a-c described above in connection with FIG. 1A to the universal I / O bus 136a. The I / O bus transceiver 206 may be implemented using a transmitter amplifier and a receiver amplifier that coordinate 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 connects the terminal modules 124a-c to the I / O bus transceiver 206. In an exemplary embodiment, the I / O bus transceiver 206 is configured to convey information using a wired communication medium. Although not shown, the marshalling cabinet 122 is another substantially similar or identical to the I / O bus transceiver 206 for communicatively connecting the termination modules 126a-c to the I / O cards 134a-b. An I / O bus transceiver may be provided.

Field devices by exchanging information between I / O cards 132a-b and termination modules 124a-c using a common communication interface (eg, I / O bus 208 and I / O bus 136a). Connection routing from to the I / O card can be defined towards the end of the design or installation process. For example, the termination modules 124a-c may be communicatively connected to the I / O bus 208 at various locations within the marshalling cabinet 122 (eg, various termination module sockets on socket rails 202a-b). In addition, the common communication interface between the I / O cards 132a-b and the termination modules 124a-c (eg, I / O bus 208 and I / O bus 136a) is terminated with the I / O cards 132a-b. Reduce the number of communication media between modules 124a-c (eg, the number of communication buses and / or wires), and therefore more than the number of known termination modules that can be installed in known marshalling cabinet configurations. Also allows a relatively large number of termination modules 124a-c (and / or termination modules 126a-c) to be installed within the marshalling cabinet 122.

Each of the termination modules 124a-c is provided with a display 212 (eg, an electronic termination label) to display field device identification information and / or other field device information associated with the termination modules 124a-c. .. 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, analog signal, digital signal, etc.) For example, device on, device off, device error, etc.), and / or other field device information can 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 another field device (not shown)), the display 212 is used for termination. Field device information related to all of the field devices communicatively linked to module 124 can be displayed. In an exemplary embodiment, the 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 techniques.

Each of the termination modules 124a-c is provided with a labeler 214 (eg, a termination labeler) for reading field device identification information and / or other field device information. For example, when the field device 112a is communicatively coupled to the termination module 124a, the labeler 214 of the termination module 124a may provide field device identification information and / or other field device information to the field device 112a (and / or termination module). It is read from another field device (communicatively linked to 124a) and information is displayed via the display 212 of the termination module 124a. Labeler 214 will be described in detail below in connection with FIG. Providing the display 212 and the labeler 214 reduces the costs and installation time associated with manually labeling the wires and / or buses associated with the termination module and field device. However, in some exemplary implementations, manual wire labeling can also be used in connection with the display 212 and the labeler 214. For example, the display 212 and the labeler 214 are used to determine which of the field devices 112a-c and the field devices 116a-c are connected to the termination modules 124a-c and the termination modules 126a-c, respectively. By doing so, the field devices 112a to 112a to c and the field devices 116a to 116a to c can be relatively quickly and communicatively connected to the I / O cards 132a to b and the I / O cards 134a to b. Subsequently, after the installation is complete, the label is optionally attached to a bus or wire extending between the termination modules 124a-c and the termination modules 126a-c and the field devices 112a-c and 114a-c. Can be added. The display 212 and the labeler 214 also display status information (eg, device error, device alarm, device on, device off, device disabled, etc.) to facilitate the troubleshooting process. By configuring and, the cost and time associated with maintenance work can be reduced.

The marshalling cabinet 122 is provided with a power supply 216 to provide power to the termination modules 124a-c, the I / O bus transceiver 206, and the display 212. In an exemplary embodiment, termination modules 124a-c use power from power supply 216 to communicate with a field device (eg, field devices 112a-c in FIG. 1A) and / or to operate on the field device. Powers a communication channel or interface used to provide power for. 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 of the termination modules 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 communicatively coupled to socket rails 202a-b. can.

FIG. 3 is another exemplary marshalling cabinet 300 that can be used to mount the exemplary marshalling cabinet 122 of FIG. 1A. In an exemplary embodiment, the marshalling cabinet 300 is provided with a wireless I / O bus communication controller 302 for wirelessly communicating 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 substantially similar to or the same as the termination modules 124a to 124a to 1A and the termination modules 126a to 126a are inserted into the rail socket 308a and the rail socket 308b and wirelessly. It is communicatively connected to the I / O bus communication controller 302 via the universal I / O bus 309 inside the marshalling cabinet 300. In an exemplary embodiment, the wireless I / O bus communication controller 302 emulates the I / O card of controller 104 of FIG. 1A (eg, I / O card 134a of FIG. 1A), and the termination module 306 is controller 104. Allows you 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 marshalled in relation to sockets that accept the termination module. It is installed in the cabinet 300. In this way, 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 the field devices 116a-c of FIG. 1A). , Each one of the labeler 214 of the termination module 306 and the display 310 can be used to display field device identification information indicating the field device connected to the termination module 306. The 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 to or similar to the power supply 216 of FIG. Further, in some embodiments, the marshalling cabinet 300 is provided with a power regulator 314 that is substantially similar or similar to the power regulator 218 of FIG.

FIG. 4 shows a plan view of an 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 inserted into the rail socket 202a (FIG. 3), the display 212 is operating while the operator. Or make it visible to the user. As shown in the exemplary embodiment of FIG. 5, the exemplary termination module 124a is detachably coupled to the base 402. An exemplary termination module 124a includes a plurality of contacts 404 (two of which are shown) that communicatively and / or electrically connect the termination module 124a to the base 402. In this way, the base 402 can be connected to the marshalling cabinet 122 (FIGS. 1A and 2), and the termination module 124a can be connected to the marshalling cabinet 122 via the base 402 and removed. The base 402 is provided with a termination screw 406 (eg, a field device interface) that fastens or secures a conductor communication medium (eg, a bus) from the field device 112a. When the termination module 124a is detachably coupled to the base 402, the termination screw 406 is communicatively coupled to one or more of the contacts 404 to transfer information between the termination module 124a and the field device 112a. Make it possible to convey. 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 illustrated, 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.

In order to communicatively connect 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 inserts the base 402 into the socket rail 202a or the socket rail 202b (FIG. 2), the universal I / O bus connector 408 engages the universal I / O bus 208. The universal I / O bus connector 408 can be implemented using the appropriate interface, including relatively simple interfaces such as insulated perforated connectors. The I / O bus connector 408 is connected to one or more of the contacts 404 of the termination module 124a to allow information to be transmitted between the termination module 124a and the I / O bus 208. ..

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

FIG. 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. 2 is a detailed block diagram of an exemplary labeler 214 of FIGS. 2, 3 and 6. An exemplary termination module 124a, an exemplary I / O card 132a, and an exemplary labeler 214 can be implemented using the desired combination of hardware, firmware, and / or software. For example, one or more integrated circuits, individual semiconductor components, or passive electronic components can be used. In addition or alternatives, an exemplary termination module 124a, an exemplary I / O card 132a, an exemplary labeler 214 and some or all of the blocks, or parts thereof, eg, a processor system (eg, eg, a processor system). Instructions stored on a machine-accessible medium that performs the operations shown in the flowcharts of FIGS. 10A, 10B, 11A, 11B, and 12 when executed by the exemplary processor system 1610) of FIG. , Code, and / or other software and / or firmware, etc. An exemplary termination module 124a, an exemplary I / O card 132a, and an exemplary labeler 214 are described as having one of the blocks described below, but the exemplary termination module 124a and exemplary. Each of the typical I / O card 132a and the exemplary labeler 214 may be provided with two or more of each of the blocks described below.

Referring to FIG. 6, the exemplary termination module 124a allows the exemplary termination module 124a to communicate with the I / O cards 132a-b (or other I / O cards) of FIG. 1A. Includes I / O bus interface 602. The I / O bus interface 602 can be implemented using, for example, the RS-485 serial communication standard, Ethernet, and the like. 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 the termination module address (eg, network address) when the termination module 124a is inserted into the marshalling cabinet 122. In this way, the termination module 124a can use the termination module address as the source address when transmitting information to the I / O card 132a, and the I / O card 132a can use the termination module 132a when transmitting information to the termination module 124a. Use the termination module address as the destination address.

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

An 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 an exemplary embodiment, the I / O bus communication processor 608 packets the information to be transmitted to the I / O card 132a and reverse packets the information received from the I / O card 132a. In an exemplary embodiment, the I / O bus communication processor 608 generates header information for each packet to be transmitted and reads the header information from the received packet. Exemplary header information includes a destination address (eg, the network address of the I / O card 132a), a source address (eg, the network address of the termination module 124a), and a packet type or data type (eg, analog field device information). Includes field device information, command information, temperature information, real-time data values, etc.) and error checking information (eg, circuit redundancy inspection (CRC)). In some exemplary implementations, the I / O bus communication processor 608 and the operating controller 606 can be implemented using the same microprocessor or microcontroller.

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

In order 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 an exemplary embodiment, the power supply 216 (FIG. 2) of the marshalling cabinet 122 provides power to the termination module 124a to power the communication channel interface for communicating with the field device 112a. For example, some field devices use 12 volt to communicate and others use 24 volt to communicate. In an exemplary embodiment, the field power controller 610 is configured to regulate and control the power provided to the termination module 124a by the power supply 216 to increase and / or decrease the voltage. In some embodiments, power regulation is achieved via a power regulator 218 (FIG. 2) associated with the marshalling cabinet. In some exemplary implementations, the field power controller 610 is flammable or flammable by limiting the amount of power used to communicate with the field device and / or the amount of power supplied to the field device. Significantly reduce or eliminate the risk of sparks in your environment.

In order to convert the power received from the power supply 216 (FIG. 2) into the power for the termination module 124a and / or the field device 112a, the termination module 124a is provided with a power converter 612. In an exemplary embodiment, the circuit used to mount the termination module 124a uses one or more voltage levels (eg, 3.3V) that differ from the voltage level required by the field device 112a. .. The power converter 612 is configured to provide different voltage levels for the termination module 124a and the field device 112a using the power received from the power supply 216. In an exemplary embodiment, the power output generated by the power converter 612 is used to activate the termination module 124a and the field device 112a to transfer information between the termination module 124a and the field device 112a. Some field device communication protocols require voltage and / or current levels that are relatively higher or lower than other communication protocols. In an exemplary embodiment, the field power controller 610 controls the power converter 612 to provide a voltage level that activates the field device 112a and communicates with the 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 another power source outside the marshalling cabinet 122 can be used. The field device 112a can be activated.

In order to electrically insulate the circuit of the termination module 124a from the I / O card 132a, the termination module 124a is provided with one or more insulation devices 614. Insulation device 614 can be implemented using a galvanic isolator and / or an optical isolator. An exemplary insulating structure will be described in detail below in connection with FIG.

In order to convert between an analog signal and a digital signal, 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 analog value of the digital display 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 (for example, a measured value) received from the field device 112a into a digital display value that can be transmitted to the I / O card 132a. In an alternative exemplary implementation in which the termination module 124a is configured to communicate digitally with the field device 112a, the digital / analog converter 616 and the analog / digital converter 618 are omitted from the 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 of 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 depacket the information if the field device 112a is configured to communicate using digital information. In addition, the field device communication processor 620 extracts the information received from the field device 112a and transfers the information to the analog / digital converter 618 and / or the I / O bus communication processor later for transmission to the I / O card 132a. It is configured to tell 608. In some embodiments, the field device communication processor 620 assists in identifying the appropriate communication protocol associated with the field device 112a. For example, the 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 corresponding to the Profibus PA communication protocol. If the field device 112a responds to the request, the field device 112a is identified as a Profibus PA compliant device and all subsequent communications are formatted based on the Profibus PA protocol. If the field device 112a does not respond to a request in Profibus PA format, the field device communication processor 620 formats the second request corresponding to the FF-H1 communication protocol and is the fieldbus device 112a a FF-H1 compliant device? Whether or not the field device 112a responds to the second request is checked. If the termination module 124a is configured to communicate using another protocol (eg, HART), the field device communication processor 620 will add additional communication protocols until the field device 112a finds the appropriate communication protocol. Requests can be generated.

In some embodiments, such an autosensing routine is implemented periodically (or aperiodically) (eg, after a particular threshold period) and is a field communicatively linked to termination module 124a. Detect changes in the device. For example, the autosensing routine may be a first, working or primary field device (eg, field device 112a) and a second (not shown) spare on a conductor 130a communicatively coupled to the termination module 124a. It can detect field devices. 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. 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. Automatically replaces to continue control of the process system. In addition, or alternative, in some embodiments, if the device information contains some differences (eg, different versions or vendors), the termination module 124a appoints a spare field device and reserves it. Initiates communication with the field device, but until the operator or engineer specifies the first field device, removes it, and / or designates a spare field device as the new active or primary device (although disconnected). Maintain a "spare" destination (while continuing to indicate the first field device as the primary device).

In an exemplary embodiment, the field device communication processor 620 is also configured to time stamp the information received from the field device 112a. Generating a time stamp in the termination module 124a facilitates the implementation of sequence-of-event (SOE) operations using time stamp accuracy within the range of less than milliseconds. For example, the time stamp and each information can be transmitted to the controller 104 and / or the workstation 102. For example, it occurs before, during, and / or after a particular operating state (eg, failure mode), subsequently using a sequence of event operation performed by workstation 102 (FIG. 1A) (or another processor system). It is possible to analyze that and determine what caused a particular operating state. Timestamping in the range of less than a millisecond makes it possible to capture the event with relatively high accuracy. In some exemplary implementations, the field device communication processor and the operating 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 has a communication protocol function or other communication function (eg, Fieldbus communication protocol function, etc., corresponding to the type of field device configured to communicate with it. HART communication protocol function, etc.) is provided. 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 the HART communication protocol function. When the termination module 124a receives the information addressed to the field device 112a from the I / O card 132a, the field device communication controller 620 formats the information according to the HART communication protocol and distributes the information to the field device 112a.

In an exemplary embodiment, the field device communication controller 620 is configured to process pass-through messages. The pass-through message occurs on a workstation (eg, workstation 102 in FIG. 1A) and as a payload (eg, the data portion of a communication packet) through a controller (eg, controller 104 in FIG. 1A) and a field device (eg, field). It is transmitted to a termination module (eg, termination module 124a in FIG. 1A) for delivery to device 112a). For example, a message that occurs on workstation 102 and is intended to be delivered to field device 112a is tagged with a communication protocol descriptor (eg, HART protocol descriptor) at workstation 102 and / or communicates with field device 112a. Formatted according to the 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 to the termination module 124a via the I / O controller 104. .. Wrapping the message involves, for example, packetizing the message in header information according to the communication protocol used to communicate with the field device (eg, Fieldbus protocol, HART protocol, etc.). 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 yet formatted on workstation 102) according to the communication protocol descriptor generated by workstation 102. Arrange and convey the message to the field device 112a.

The field device communication controller 620 is also configured to convey a pass-through message to workstation 102 in a similar manner. For example, if the field device 112a generates a message to be delivered to the workstation 102 (eg, a response to a workstation message or other message), the field device communication controller 620 sends a message from the field device 112a. Wrapped in a payload consisting of one or more communication packets, the I / O bus communication processor 608 conveys one or more packets containing the wrapped message to the I / O card 132a. When the workstation 102 receives a packet containing the wrapped message from the controller 104, the workstation 102 retrieves and processes the message.

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

In some embodiments, the termination module 124a is provided with a fieldbus diagnostic analyzer 624 configured to provide advanced diagnostics for related field devices when the field device is fieldbus compliant. The fieldbus diagnostic analyzer 624 makes measurements during operation with respect to the state of the physical wiring (eg, the first conductor 130a in FIG. 1A) and the associated communication. For example, the fieldbus diagnostic analyzer 624 can measure supply voltage, load current, signal level, line noise, and / or jitter. Advanced diagnostic modules with similar functionality can be incorporated into traditional fieldbus architectures, but the diagnostics provided by the fieldbus diagnostic analyzer 624 can be more reliable and / or robust, which is termination. This is because module 124a does not need to diagnose multiple devices in the traditional fieldbus segment multi-drop architecture and is connected to only one field device in a point-to-point architecture.

Referring here to FIG. 7, the exemplary I / O card 132a of FIG. 1A includes a communication interface 702 for communicatively connecting 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 inputs and retrieves information to be exchanged with the controller 104. In an exemplary embodiment, the communication interface 702 and the communication processor 704 are configured to convey to the controller 104 information to be delivered to the controller 104 and information to be delivered to the workstation 102 (FIG. 1A). ing. To convey information to be delivered to workstation 102, the communication interface 702 provides information (eg, information from field devices 112a-c, termination modules 124a-c, and / or I / O card 132a). A packet containing information is transmitted to the workstation 102 by wrapping it in a payload consisting of one or more communication packets according to a communication protocol (for example, communication control protocol (TCP), user datagram protocol (UDP), etc.). Can be configured in. The workstation 102 then retrieves the payload from the received packet and retrieves the information in the payload. In an exemplary embodiment, the information in the payload of the packet transmitted to workstation 102 by communication interface 702 can include one or more wrappers. For example, the information generated by the field device (eg, field device 112a) can be wrapped in a field device communication protocol wrapper (eg, FOUNDATION field bus communication protocol wrapper, HART communication protocol wrapper, etc.), and the communication interface 702 , The information is wrapped according to a TCP-based protocol, a UDP-based protocol, or another protocol that allows the controller 104 to later convey the information to the workstation 102. In a similar manner, the communication interface 702 is to retrieve information that will be transmitted to the controller 104 by the workstation 102 and delivered to the field devices 112a-c, the termination modules 124a-c, and / or the I / O card 132a. Can be configured in.

In an alternative exemplary implementation, the communication interface 702 and the communication processor 704 can convey information (with or without a field device communication protocol wrapper) to the controller 104, which is the workstation 102. The information to be delivered to the interface 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, the communication interface 702 and communication processor 704 are configured to communicate with workstation 102 and / or controller 162 via LAN 106. obtain.

The I / O card 132a is provided with one or more user interface ports 706 to allow the user to interact with and / or access the I / O card 132a. In an exemplary embodiment, the 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, the PDA 708 is shown communicatively coupled to the user interface port 706 using wireless communication.

In order to communicatively connect 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. In order to process the communication information exchanged via the I / O bus 136a and control the communication performed via the I / O bus 136a, the I / O card 132a provides the I / O bus communication processor 712. Has been done. 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 into the power required to supply and operate the I / O card 132a and / or the power required to communicate with the termination modules 124a-c. To this end, the I / O card 132a is provided with a power converter 714.

Referring here to FIG. 8, an exemplary labeler 214 may include the labeler 214 as a termination module (eg, termination module 124a in FIGS. 1A, 2 and 4, 5 and 6) and / or a field device (eg, FIG. 8). , Field device identification information (eg, device tag value, device name, electronic serial number, etc.) and / or other field device information (eg, activity information, etc.) communicatively linked to the field device 112a of FIG. 1A. Includes a communication interface 802 configured to read data type information, state information, etc.). The labeler 214 is provided with a communication processor 804 to control communication with the termination module 124a and / or the field device 112a.

The labeler 214 is provided with a connection detector 806 to detect a connection to a field device (eg, field device 112a in FIG. 1A). The connection detector 806 can be implemented using, for example, a voltage sensor, a current sensor, a logic circuit, etc., which detects when the field device 112a is connected to the termination module 124a. In an exemplary embodiment, the connection detector 806 determines that the field device 112a is connected to the termination module 124a, and the connection detector 806 indicates the connection detected by the notification (eg, interrupt) and the communication processor 804. To be communicated to. The communication processor 804 then queries the termination module 124a and / or the field device 112a for the field device identification information of the field device 112a. In an exemplary implementation, the connection detector 806 also has, 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 connects the field device 112a to the termination module 124a, such as network connection, optical connection, and the like.

The labeler 214 is provided with a display interface 808 for displaying field device identification information and / or other field device information. In an exemplary embodiment, the 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 an LCD display 212 (FIG. 2) mounted on the termination module 124a or an LCD display 310 mounted on a marshalling cabinet 300 (FIG. 3). However, in other exemplary implementations, the display interface 808 may instead be configured to run other display types.

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

To detect the condition of the field device 112a, the labeler 214 is provided with a field device condition detector 812. The field device state detector 812 provides state information related to the field device 112a (eg, device on, device off, device error, device alarm, device health (open loop, short, etc.), device communication state, etc.). The communication processor 804 is configured to extract from the data received from the termination module 124a and / or the field device 112a. In some embodiments, the status information includes information based on data acquired via the 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 classifier 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 field device 112a by the communication processor. It is configured in. The display interface 808 can then display the field device identification information. In an exemplary implementation, the field device classifier 814 may also be configured to detect field device types (eg, valve actuators, pressure sensors, temperature sensors, flow rate sensors, etc.). In some embodiments, the field device classifier 814 uses the appropriate communication protocol associated with the field device 112a in the same or similar manner as or similar to the field device communication processor 620 described above in connection with FIG. In combination with it, it is configured to identify.

To identify the data type (eg, analog or digital) associated with the field device 112a, the labeler 214 is provided with a data type classifier 816. The data type identifier 816 is configured to extract the data type identification information from the data received from the termination module 124a and / or the field device 112a by the communication processor. For example, the termination module 124a can store a data type descriptor variable that indicates 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 transmitted 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 classifier 816 uses the communication protocol identified by the field device classifier 814 to determine the data type associated with the field device 112a.

FIG. 9 relates to the exemplary termination module 124a and the termination module 124b of FIG. 1A to electrically insulate the termination modules 124a-b from each other and the field devices 112a-b from the universal I / O bus 136a. It shows an isolated circuit configuration that can be mounted. In an exemplary embodiment, each of the termination modules 124a-b includes each 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 to 124b are connected to the universal I / O bus 136a and the power supply 216. In order to electrically insulate the termination module circuit 902 from the universal I / O bus 136a, the termination module 124a is provided with an insulation circuit 906. In this way, the termination module circuit 902 does not affect the voltage of the universal I / O bus 136a and also the I / O card 132a (Figure) when a power surge or other power fluctuation occurs in the field device 112a. It can be configured to follow (eg, float) the voltage level of field device 112a without damaging 1A). The termination module 124b also includes an insulation circuit 908 configured to insulate the termination module circuit 904 from the universal I / O bus 136a. The insulation circuit 906, the insulation circuit 908, and other insulation circuits mounted on the termination modules 124a to 124b can be mounted using an optical insulation circuit or a galvanic insulation circuit.

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

In known process control systems, the insulation circuit is provided in a known marshalling cabinet, thereby reducing the amount of space available to the known termination module. However, as shown in the exemplary embodiment of FIG. 9, providing the insulating circuit 906, the insulating circuit 910, the insulating circuit 908, and the insulating circuit 912 in the termination module 124a and the termination module 124b is for the insulating circuit. Reduces the amount of space required in the marshalling cabinet 122 (FIGS. 1A and 2) and thus can be used for termination modules (eg, termination modules 124a-c and termination modules 126a-c). To increase. In addition, mounting insulation circuits (eg, insulation circuits 906, 908, 910, and 912) in termination modules (eg, termination modules 124a-b) selects insulation circuits only for termination modules that require insulation. Allows you to use it as a target. For example, some of the termination modules 124a-c and the termination modules 126a-c of FIG. 1A can be mounted without an insulating circuit.

10A, 10B, 11A, 11B, 12 and 15 are termination modules (eg, termination modules 124a of FIGS. 1A and 2 and FIGS. 4-6, and / or termination modules 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). It is a flowchart of an exemplary method to obtain. In some exemplary implementations, exemplary methods of FIGS. 10A, 10B, 11A, 11B, 12 and 15 are shown in the processor (eg, the exemplary processor system 1610 of FIG. 16). It can be implemented using machine-readable instructions, including a program executed by the processor 1612). A well-known method of embodying a program with 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. It can be embodied in 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. And many other methods of mounting the exemplary termination module 1332a, the exemplary I / O card 132a, and the exemplary labeler 214 can be readily used by those skilled in the art. to understand. For example, the execution order of blocks can be changed, and / or some of the blocks described can be modified, deleted, or combined.

With reference to FIGS. 10A and 10B in detail, the exemplary method of FIG. 10A and FIG. 10B relates to 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 methods of A and 10B of FIG. Using the flowcharts of FIGS. 10A and 10B, how the exemplary termination module 124a conveys information between the field device 112a and the I / O card 132a will be described. First, the termination module 124a determines whether it has received the communication information (block 1002). For example, the termination module 124a receives the communication information if it indicates that the I / O bus communication processor 608 (FIG. 6) or the field device communication processor 620 has received the communication information, for example, via an interrupt or status register. Judge that it was done. If the termination module 124a determines that it has not received the communication information (block 1002), control remains in block 1002 until the termination module 124a receives the communication information.

When the termination module 124a receives the communication information (block 1002), the termination module 124a determines whether it has received the communication information from the field device (eg, the field device 112a of FIG. 1A), for example, the field device communication processor. Judgment 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 the communication information from the field device 112a (block 1004), the field device communication processor 620 receives the field device information and the field device identification information in relation to the field device 112a. It is extracted from the obtained communication information 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, eg) , Multi-drop bus connection, point-to-point connection, etc.), field device bus or segment identification information (eg, field device bus or field device segment through which the field device is communicatively attached to the termination module), 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 type (For example, digital out data type), etc.) can be included. 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, in 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 that identifies the field device 112a is in the termination module 124a. Is remembered in. For example, when the field device 112a is first connected to the termination module 124a, the field device 112a can transmit the 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 if 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 analog-to-digital conversion is required or required (block 1008). If analog-to-digital conversion is required, the analog-to-digital converter 618 (FIG. 6) performs the conversion on the received information (block 1010).

After analog-digital conversion (block 1010) or when analog-digital conversion is not required (block 1008), the field device communication processor 620 will use the data type associated with the received field device information (eg, analog, digital, temperature). (Measurement, etc.) is identified (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 indicating the data type it always receives from the field device 112a, or the field device 112a is a data type descriptor in block 1010 by the field device communication processor 620. The data type used to generate the 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 to which the termination module 124a conveys the information received from the field device 112a (block 1016). For example, the communication processor 608 (FIG. 6) can acquire 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 to be transmitted 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 cyclic error check (CRC) error check bits.

The I / O bus communication processor 608 then performs I / O with field device information, field device identification information, a data type descriptor, a destination address of the I / O card 132a, a source address of the termination module 124a, and error check data. Packetize based on the bus communication protocol (block 1022). The 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 acquire the source address of the termination module 124a from the address identifier 604 (FIG. 6). The I / O bus interface 602 (FIG. 6) then transfers the packetized information via the universal I / O bus 136a (FIGS. 1A and 2) to other termination modules (eg, termination modules 124b and FIG. 1A). It is transmitted together with the packetized information generated and transmitted by the termination module 124c) (block 1024). For example, the I / O bus interface 602 has a universal I / O bus 136a available for transmitting 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 for determining time may be provided.

When the termination module 124b determines in the block 1004 that the communication information detected in the block 1002 is not from the field device 112a (for example, the communication information is from the I / O card 132a), the I / O bus communication processor 608 FIG. 6 extracts a 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 the termination module 124a (eg, the received information was not intended to be delivered to the 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 intended to be delivered to the termination module 124a) (block 1028), the I / O bus communication processor 608 is in the field. The device information is extracted from the received communication information based on the I / O bus communication protocol (block 1030), and the data integrity is determined, for example, by using CRC verification processing based on the 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 an error exists in the received communication information, the I / O bus communication processor 608 requests retransmission and sends a message. It is transmitted to the I / O card 132a.

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

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

11A and 11B show flowcharts of exemplary methods that can 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. First, the I / O card 132a determines whether it has received the communication information (block 1102). For example, the I / O card 132a determines that the communication processor 704 (FIG. 7) has received the communication information if it indicates that it has received the communication information, for example, via an interrupt or status register. If the I / O card 132a determines that it has not received the communication information (block 1102), control remains in block 1102 until the I / O card 132a receives the communication information.

When the I / O card 132a receives the communication information (block 1102), the I / O card 132a determines whether it has received the communication information from the controller 104 (FIG. 1A), for example, by interrupting the communication processor 704 or Judgment is made based on the status register (block 1104). If the I / O card 132a determines that it has received the communication information from the controller 104 (block 1104), the communication processor 704 associates the 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 the data type associated with the received termination module information (eg, field device analog information, field device digital information, termination module control information for controlling or configuring the termination module, etc.) (block 1108). ), Generates a data type descriptor corresponding to the received termination module information (block 1110). In an alternative exemplary implementation, the data type descriptor is generated on workstation 102 (FIG. 1A) and the communication processor 704 does not need to generate the 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 the error check data to be transmitted to the termination module 124a together with the termination module information to ensure that the termination module 124a has received the information without error (block 1114). For example, the I / O bus communication processor 712 can generate cyclic error check (CRC) error check bits.

The I / O bus communication processor 712 then packets the termination module information, the data type descriptor, the destination address of the termination module 124a, the source address of the termination module 124a, and the error check data based on the I / O bus communication protocol. (Block 1116). The I / O bus interface 710 (FIG. 7) then transfers the packetized information via the universal I / O bus 136a (FIGS. 1A and 2) to other termination modules (eg, termination modules 124b and FIG. 1A). It is transmitted together with the 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 communicated via the universal I / O bus 136a using the RS-485 standard. Each of the termination modules 124a-c can extract its information from the universal I / O bus 136a based on the destination address provided by the I / O card 132a.

When the I / O card 132a determines in the block 1104 that the communication information detected in the block 1102 is not from the controller 104 (for example, the communication information is from one of the termination modules 124a to c). The I / O bus communication processor 712 (FIG. 7) extracts a source address (for example, the source address of one of the termination modules 124a to 124) from the received communication information (block 1122). The I / O bus communication processor 712 then extracts data type descriptors (eg, digitally encoded analog data types, digital data types, temperature data types, 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) to ensure data integrity. Is verified using, for example, CRC verification processing based on the 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 related to the obtained source address.

After verifying the data integrity (block 1128), the communication processor 704 packets the termination module information (using the termination module source address and the data type descriptor), and the communication interface 702 packetizes the packetized information. Communicate to controller 104 (block 1130). If the information is to be delivered to workstation 102, the controller 104 can subsequently convey the information to workstation 102. After the communication interface 702 conveys the information to the controller 104 or the I / O bus interface 710 conveys the termination module information to the termination module 124a, the process of FIGS. 11A and 11B ends and / or controls , For example, return to the calling process or calling function.

FIG. 12 reads 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 and 2 and FIGS. 4-6). , A flowchart of an exemplary method that can be used to implement the labeler 214 of FIGS. 2, 3 and 8. First, the connection detector 806 (FIG. 8) has a field device (eg, field device 112a) connected to the termination module 124a (eg, the termination screw 406 and / or FIG. 6 of FIGS. 4 and 5). Determine if it is (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), the control is that the connection detector 806 controls the field device 112a (or other field device). It stays in block 1202 until it determines that the field device) is connected to the termination module 124a.

When the connection detector 806 determines that the field device 112a is connected to the termination module 124a (block 1202), the field device classifier 814 identifies the field device identification information (eg, device tag value) that identifies the field device 112a. , Device name, electronic serial number, etc.) (block 1204). For example, the field device classifier 814 sends a query to the field device 112a requesting that the field device 112a transmit its field device identification information. In another exemplary implementation, after the initial connection to the termination module 124a, the field device 112a can automatically transmit its field device identification information to the field device classifier 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 transmit the field device identification information to the I / O card 132a via the termination module 124a, and the I / O card 132a stores the field device identification information in the workstation 102. It can be compared with the data structure 133 (FIG. 1A) or the field device identification number stored in a similar data structure. To the data structure 133, an engineer, operator, or user adds a field device identification number of a field device (eg, field devices 112a-c) transmitted 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 classifier 814. inform.

If the field device classifier 814 determines that the field device 112a is not assigned to communicate over 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 the field device identification information (block 1210). In an exemplary embodiment, the field device state detector 812 detects field device states (eg, device on, device off, device error, etc.) and the display interface 808 displays state information (block 1212). In addition, the field device activity detector 810 (FIG. 8) detects the activity of the field device 112a (eg, measurement information and / or monitoring information), and the display interface 808 displays the activity information (block 1214). The data type detector 816 (FIG. 8) also detects the data type (eg, analog, digital, etc.) of the field device 112a, and the 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 the data type (block 1216), the labeler 214 determines whether it should continue monitoring, eg, 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 labeler 214 determines that monitoring should continue, control is returned to block 1202. Otherwise, the exemplary process of FIG. 12 ends and / or control returns to the calling process or function.

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

In the exemplary embodiment of FIG. 13A, the exemplary process control system 100 is implemented using traditional fieldbus architecture and components, field devices 1312a-c and FF within the Profibus PA process area 1302. -Includes field devices 1314a-c within the H1 process control area 1304 (both Profibus PA and FF-H are protocols related to the family of fieldbus protocols). Therefore, the field devices 1312a-c and the field devices 1314a-c are communicatively linked to the controller 1306 via the corresponding trunks or segments 1316a-b. Typically, a fieldbus trunk or fieldbus segment contains 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. Two cables. Due to various constraints, the fieldbus segment is typically limited to a maximum length of 1900 meters and can be connected to up to 16 different field devices. As shown in the exemplary embodiments, the segments 1316a-b are communicatively linked within the controller 1306 to the corresponding I / O cards 1318a-b and I / O cards 1320a-b. In an exemplary 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, the I / O cards 1318a-b and / or the I / O cards I1320a-b are separated from each other and / or I related to field devices 112a-c in the first process area 114. It can be in a different controller, away from the / O cards 132a-b.

In the exemplary embodiment of FIG. 13A, the segment 1316a corresponding to the exemplary Profibus PA process area 1302 is coupled to the I / O cards 1318a-b via a DP / PA segment coupler 1322. Similarly, the segment 1316b corresponding to the exemplary FF-H1 process area 1304 is connected to the I / O cards 1320a-b via a power supply 1324. In some embodiments, the DP / PA segment coupler 1322 and the power supply 1324 provide a power conditioning function for each segment 1316a-b. In addition, in the exemplary embodiment, the DP / PA segment coupler 1322 and the power supply 1324 can monitor the physical layer of the corresponding segments 1316a-b and the communication via the segments 1316a-b during operation, respectively. It is connected to the advanced diagnostic modules 1325a to 1325a to b.

In an exemplary embodiment, field devices 1312a-c and field devices 1314a-c are connected to corresponding segments 1316a-b via spools 1326a-c and spools 1328a-c. In the fieldbus architecture, each spool connects the corresponding field device parallel to the segment. As a result, in many process control systems shown in the illustrated examples, each spool 1326a-c and spool 1328a-c are segment protectors 1330a-b (sometimes referred to as device couplers or field barriers) in the corresponding segments 1316a-b. It provides a short circuit prevention function for a short circuit in one of the field devices 1312a to 1312a to 1314a to c, which is connected via and short-circuits all the segments. In some embodiments, the segment protectors 1330a-b limit the current (eg, to 40mA) on each of the spools 1326a-c and 1328a-c. In some embodiments, the segment protectors 1330a-b also function to properly terminate each segment 1316a-b at a termination near the field device, while the DP / PA segment coupler 1322 and power supply 1324 It serves to terminate segments 1316a-b at the end near the controller. Without proper termination at both ends of segments 1316a-b, communication errors can occur due to signal reflection.

As explained above, the fieldbus architecture offers many advantages, but it also presents challenges in terms of implementation complexity and cost. For example, the complexity of fieldbus systems is particularly high, while ensuring that each segment is properly terminated and protected against short circuits, open circuits, 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 lengths (including multiple cables) and I / O cards 1318a-b and I / O cards 1320a-b. However, through the implementation of the teachings disclosed herein, the design complexity and cost associated with the implementation and maintenance of the fieldbus system is significantly reduced.

FIG. 13B is a block diagram showing an exemplary process control system 1300 of FIG. 13A after implementing the teachings disclosed herein. As shown in the exemplary embodiments, the spools 1326a-c and the spools 1328a-c of the field devices 1312a-c and the field devices 1314a-c were plugged into sockets on the socket rail 1310 of the marshalling cabinet 1308 shown in FIG. 13A. , Directly and communicatively connected to each termination module 1332a to f. That is, in contrast to the usual topology of field devices in a multi-drop architecture, in the exemplary embodiments, the fieldbus compliant field devices 1312a-c and the fieldbus compliant field devices 1314a-c are the termination modules 1332a-f. And point-to-point communication. Termination modules 1332a-f are in the same manner as described above via the universal I / O bus 136a between the field devices 1312a-c and the field devices 1314a-c and the I / O cards 132a-b. The termination modules 124a-c and the termination modules 126a-c described above can be substantially similar or the same as the termination modules 126a-c described above. 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. Eliminating the need for 1320a-b (FIG. 13A), any type of field device and associated I / O can be combined within one marshalling cabinet 1308. Similarly, the need for cable trunks or segments 1316a-b (FIG. 13A) disappears with the associated insulation. Moreover, in some embodiments, the universal I / O bus 136a is for even faster communication than the relatively slow communication backbone of a typical copper-based fieldbus segment (eg, via fiber optic cable). ) Provides 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 the normal fieldbus segment is limited to the connection of 16 devices. ing. Therefore, the number of wires connected to the controller for the same number of field devices is significantly reduced.

The plurality of field devices may be configured in some embodiments in a multi-drop configuration communicatively coupled to one termination module 1332a-f, which is common in fieldbus architectures, but will be shown in the exemplary embodiments. The point-to-point or single-loop architecture offers some advantages and simplifications over traditional fieldbus configurations. For example, in the field devices 1312a-c and the field devices 1314a-c routed as shown in an exemplary embodiment, the termination modules 1332a-f provide power and power conditioning functionality (eg, in connection with FIG. 6). It 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 supply 1324 shown in FIG. 13A is no longer needed. In addition, or alternative, in some embodiments, the marshalling cabinet 1308 power regulator 218 to eliminate the need for the separate DP / PA segment coupler 1322 and / or power supply 1324 shown in FIG. 13A. (Fig. 2) includes power regulators that are substantially similar or similar. 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 that the power supply provides power along the normal fieldbus segment. Lower than (for example, due to the voltage drop resulting from the length of the cable). Further, in some embodiments, termination modules 1332a-f provide short circuit protection (eg, via the corresponding field power controller 610) to draw current between each spool 1326a-c and spool 1328a-c. Limit, thereby eliminating the need for separate segment protectors 1330a-b.

In addition, connecting the field devices 1312a-c and the field devices 1314a-c individually to separate termination modules 1332a-f provides single-loop integrity and for proper termination in a normal fieldbus architecture. Make the concern less of a concern. In addition, direct point-to-point connections between field devices 1312a-c and field devices 1314a-c and the corresponding termination modules 1332a-f are complex with the development and implementation of regular fieldbus segments. Significant reduction in design work and the fact that signals from each field device are received separately and are handled or organized electronically on the back end. Therefore, the cost of acquiring, configuring, and maintaining many components of a conventional fieldbus architecture, and the time and cost of designing such an architecture and ensuring its proper operation are disclosed herein. Significantly reduced through the implementation of teachings. In other words, in some embodiments, the fieldbus compliant device is placed in the process control system without any DP / PA coupler and / or power supply in the segment (eg, in the marshalling cabinet 122 and / or termination). It can be incorporated without 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, the termination modules 1332a-f may provide advanced diagnostics (eg, via the fieldbus diagnostic analyzer 624 of FIG. 6) without another advanced diagnostic modules 1325a-b. can. Moreover, in some embodiments, the diagnostics performed by the termination modules 1332a-f can be more reliable and / or more robust than the known advanced diagnostic modules, which is each termination. This is because modules 1332a-f only need to monitor one field device via a point-to-point connection rather than multiple devices on a regular fieldbus segment.

Both Profibus PA and FF-H1 are fieldbus protocols with the same physical layer. Therefore, in some embodiments, the termination modules 1332a-c associated with the field devices 1312a-c in the Profibus PA process area 1302 are the termination modules 1332d associated with the field devices 1314a-c in the FF-H1 process area 1304. It is the same as ~ f. In other words, in some embodiments, spools 1326a-c connected to termination modules 1332a-c may be connected to termination modules 1332d-f, while spools 1328a-c replace the termination modules 1332d-f. It is connected to the termination modules 1332a to 1332a to c. In some such embodiments, the termination modules 1332a-f are associated with a particular field device 1312a-c and a particular field device 1314a-c to which the termination modules 1332a-f are connected (eg,). , Profibus PA or FF-H1) automatically. As a result, process control system engineers are not concerned that they will have to design separate fieldbus segments, or that they will have to obtain the corresponding components needed to implement such fieldbus segments. In addition, you are free to use any fieldbus device you want, regardless of the associated communication protocol (you can even mix devices that comply with different protocols).

In some embodiments, the termination modules 1332a-f are inherently safe for implementing field devices 1312a-c and field devices 1314a-c in a hazardous environment (eg, Fieldbus Internationally Safe Concept (eg, Fieldbus International Safety 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 sufficient safety assessment to be certified for energy limitation and / or to meet the Fieldbus Non-Incient Concept (FNICO). In some such embodiments, the termination modules 1332a-f can comply with FNICO requirements even when plugged into a marshalling cabinet with inherently unsafe socket rails.

In addition, or alternative, in some embodiments, the termination modules described herein are based on field devices and communication protocols and other bus protocols (eg, other than Profibus PA or FF-H1). It is designed to communicate. For example, in some embodiments, the termination module is wired to a wireless HART gateway and can interface with one or more wireless HART devices using the HART-IP application protocol. In addition, or alternative, in some embodiments, the wireless device is an ISA (International Society of Automation) 100.11a or other wireless technology such as WIA-PA (Wireless Networks for Industrial Automation-Process Automation). Interfaces can be connected using standards. In some embodiments, the termination modules described herein are based on the Internet Protocol (IP), such as using the device with the 6TiSCH standard (IP version 6 over Time Slotted Channel Hopping (TSCH)). It can be made to connect to an interface using a protocol. In some embodiments, the termination module interfaces to the device using the Message Queue Telemetry Transport (MQTT) protocol. In addition, in some embodiments, the safety field device can be integrated using a tunnel protocol between the safety environment and the relevant safety controller, such as, for example, PROFIsafe (Profibus safety device).

14A and 14B show alternative exemplary implementations of peer-to-peer communication of two FF-H1-compliant field devices 1402a-b communicatively coupled to the corresponding termination modules 1404a-b. The exemplary termination modules 1404a-b can be substantially similar or similar to 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 with four corresponding terminals 1408a-b. Or the same, connected to the corresponding terminal block bases 1406a-b. In an exemplary embodiment, a pair of wires for each spool 1410a-b corresponding to field devices 1402a-b is connected to a first pair consisting of terminals 1408a-b, while from each base 1406a-b. The corresponding one of the second pair of terminals 1408a-b is connected to each other. In this way, both field devices 1402a-b are communicatively coupled to each of the termination modules 1404a-b and communicatively coupled to each other.

It is possible to connect the 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 have separate power. This is because the adjustment function is provided to each field device 1402a to 1402b (for example, via the field device controller 610). That is, in the power adjustment provided by each termination module 1404a-b, a signal from one of the field devices (eg, field device 1402a) communicates with another field device (eg, field device 1402b). It plays a role in preventing interference. However, as described above, in some embodiments, power regulation is collectively provided to all field devices on the same socket rail (eg, via injection power) by another power regulator 218. Will be done. In some such embodiments, field devices 1402a-b are communicatively coupled to termination modules 1404a-b via segment protectors 1412, as illustrated in FIG. 14B. That is, while each field device 1402a-b is still associated with the corresponding termination module 1404a-b, peer-to-peer communication between 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 embodiments of FIGS. 14A and 14B, additional wiring (eg, for shielding and / or grounding) is omitted for clarity.

An exemplary method of FIG. 15 will be described in connection with 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 an 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. First, the termination module 1332a determines whether a field device (eg, field device 1312a) is connected to the termination module 1332a (eg, via the 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), the control is that the termination module 1332a is the field device 1312a (or another field device). ) Stays in 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 communicates first (eg, via the field device communication processor 620 of FIG. 6). Sends a request formatted according to a protocol (eg, Profibus PA) (block 1504). In some embodiments, the request can correspond to a query requesting a field device to send its field device identification information, as described above in connection with block 1204 of FIG. Termination module 1332a then determines if a response to the request has been received (block 1506). As described above in connection with 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 therefore respond to the request is when the field device 1312a is associated with the same protocol. Therefore, when the termination module 1332a determines that the 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 the Profibus PA.

If the termination module 1332a determines in block 1506 that no response to the request has been received, the termination module 1332a may use another communication protocol (eg, via the field device communication processor 620) (eg, FF-H1). ) To send another formalized request (block 1508). Termination module 1332a then determines if a response to the request has been received (block 1510). When the termination module 1332a determines that a response to the request has been received (block 1510), the termination module 1332a designates 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 no response to the request has been received (block 1510), the termination module 1332a may include additional communication protocols to try (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 and sends other requests formatted according to the other communication protocols. If the termination module 1332a determines that there is no additional communication protocol to try, the termination module 1332a generates an error message (block 1514). For example, the error message can indicate that the field device 1312a is not responding and / or cannot identify the communication protocol corresponding to the field device 1312a.

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

FIG. 16 is a block diagram of an exemplary processor system 1610 that can be used to implement the devices and methods described herein. For example, using a processor system similar to or similar to the exemplary processor system 1610, workstation 102, controller 104, I / O card 132a, and / or termination modules 124a-c and termination modules 126a of FIG. 1A. ~ C can be implemented. An exemplary processor system 1610 will be described below as including a plurality of peripherals, interfaces, chips, memories, etc., but one or more of these elements may be described as workstation 102, controller 104, I. It can be omitted from the / O card 132a and / or other exemplary processor systems used to implement one or more of the termination modules 124a-c and the termination modules 126a-c.

As shown in FIG. 16, processor system 1610 includes processor 1612 coupled to interconnect bus 1614. Processor 1612 includes a register set or register space 1616, which is illustrated in FIG. 16 as being completely on-chip, but instead is completely or partially off-chip to processor 1612. , Can be directly connected via a dedicated electrical connection and / or via an interconnect bus 1614. Processor 1612 can be a suitable processor, processing unit, or microprocessor. Although not shown in FIG. 16, the system 1610 can be a multiprocessor system and is therefore the same or similar to the processor 1612 and one or more communicatively coupled to the interconnect bus 1614. Can include additional processors.

The processor 1612 of FIG. 16 is coupled to a chipset 1618, which includes a memory controller 1620 and a peripheral input / output (I / O) controller 1622. As is well known, chipsets are typically accessible or used by I / O and memory management functions and one or more processors attached to the chipset 1618, for multiple general purposes and /. Or provide special purpose registers, timers, etc. The memory controller 1620 performs a function that allows the processor 1612 (or multiple processors, if any) to access the system memory 1624 and the mass storage memory 1625.

The system memory 1624 is a desired type of volatile memory and / or non-volatile memory, such as, for example, static random access memory (SRAM), dynamic random access memory (DRAM), flash memory, read-only memory (ROM), and the like. Can be included. The mass storage memory 1625 can include a desired type of mass storage device. For example, if workstation 102 (FIG. 1A) is implemented using an exemplary processor system 1610, the mass storage memory 1625 can include hard disk drives, optical drives, tape storage devices, and the like. Alternatively, using the exemplary processor system 1610, the controller 104, one of the I / O cards 132a-b and the I / O cards 134a-b, or the termination modules 124a-c and the termination module 126a. 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, a hard drive), or another suitable for mass storage. The memory can 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.

In the peripheral device I / O controller 1622, the processor 1612 has a peripheral device input / output (I / O) device 1626, a peripheral device input / output (I / O) device 1628, a network interface 1630, and a peripheral device I / O bus. Performs a function that allows communication via 1632. The I / O device 1626 and I / O device 1628 include, for example, a keyboard, a display (eg, a liquid crystal display (LCD), a brown tube (CRT) display, etc.), a navigation device (eg, a mouse, a trackball, a capacitive touchpad, etc.). , Joystick, etc.), etc., which can be the desired type of I / O device. The network interface 1630 allows, 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., which 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. Alternatively, it can be implemented using two or more separate integrated circuits.

Although specific methods, devices, and products have been described herein, the scope of this patent is not limited to them. On the contrary, this patent includes all methods, devices and products that are properly included in the appended claims, either literally or under the doctrine of equivalents.

Claims (21)

A device that communicatesly connects field devices to the controller of a process control system.
A first physical interface communicatively linked to one of a first field device of the process control system and a second field device of the process control system.
A second physical interface, which is communicatively connected to the controller of the process control system via a bus,
With a base unit equipped with
A module detachably attached to the base unit that, when the first field device is communicatively coupled to the first field device, provides the first field device and the first communication protocol. When the first field device is communicatively coupled to the second field device, it communicates with the second field device using the second communication protocol and communicates with the controller. , The second communication protocol is different from the first communication protocol, and the third communication protocol is the first and the second. Different from the communication protocol with the module,
A device that comprises. The device according to claim 1, wherein at least one of the first communication protocol or the second communication protocol is a fieldbus protocol. The device according to claim 1 or 2, wherein the first communication protocol is the FOUNDATION fieldbus H1. The device according to claim 3, wherein the second communication protocol is Profibus PA. The device of claim 3, wherein the first field device is compliant with the FOUNDATION fieldbus H1 and is communicatively coupled to the first physical interface in a point-to-point architecture without a segment protector. The device according to claim 1 or 2, wherein at least one of the first communication protocol or the second communication protocol is a wireless HART. The device of claim 1, wherein at least one of the first communication protocol or the second communication protocol is based on the 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 the tunnel protocol and at least one of the corresponding first field device or second field device is a secure device. The device according to claim 1. The module sends a first request, formatted according to the first communication protocol, to the first field device or one of the second field devices, and the second communication. A second request, formatted according to the protocol, is transmitted to said one of the first field device or the second field device of the first field device or the second field device. Any of claims 1 to 8, wherein the communication protocol associated with one of them is automatically determined based on a response to one of the first and second requests. The device according to item 1. Further diagnostic analyzers that generate diagnostic information corresponding to the analysis of the physical layer and communication between the first physical interface and said one of the first field device or the second field device. The device according to any one of claims 1 to 10. 11. The apparatus of claim 11, wherein the diagnostic information comprises a measurement result of at least one of supply voltage, load charge, signal level, line noise, or jitter. The third communication protocol conveys information on the bus from a second module that communicates with the bus and communicates with the first field device or the other of the second field devices. , The apparatus according to any one of claims 1 to 12. A device that communicatesly connects field devices to the controller of a process control system.
A first physical interface communicatively linked to one of a first field device of the process control system and a second field device of the process control system.
A second physical interface, which is communicatively connected to the controller of the process control system via a bus,
With a base unit equipped with
A module detachably attached to the base unit that, when the first field device is communicatively coupled to the first field device, provides the first field device and the first communication protocol. When the first field device is communicatively linked to the second field device, it communicates with the second field device using the second communication protocol and communicates with the controller. , The third communication protocol is different from the communication protocol between the first and the second, and the third communication protocol is the third. Information is communicated on the bus from the one field device or the other of the second field devices and the second module that communicates with the bus, and the first physical interface of the base unit is the first physical interface. Communicatically coupled to a third physical interface of a second base unit detachably attached to the second module to facilitate peer-to-peer communication between the field device and the second field device. There are modules and
A device that comprises. A computer-readable medium having instructions for execution in a module detachably attached to the base unit to convey the first information to the controller, the first information being the first of the process control system. The first information is received in the base unit via a first physical interface that is communicatively coupled to one of the field devices or the second field device of the process control system. When the physical interface of the first field device is connected to the first field device, the module is transmitted from the first field device using the second communication protocol, and the first information is transmitted to the first physical device. When the interface is connected to the second field device, it is transmitted to the module from the second field device using the third communication protocol, and the third communication protocol is the second communication protocol. Unlike the above command,
The first information for communication is encoded using the first communication protocol, wherein the first communication protocol is the second communication protocol and the third communication protocol. Is different, encoding and
The encoded first information is transmitted from the module to the control unit via the second physical interface of the base unit via the bus using the first communication protocol.
Is an instruction to execute,
A computer-readable medium. The computer-readable medium of claim 15, wherein the second communication protocol is Profibus PA and the third communication protocol is the 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 linked to the first physical interface. The computer-readable medium of claim 15 or 16, further comprising automatically detecting the second or third communication protocol associated with one of the above. A first interface that is communicatively linked to one of the first field device of the process control system or the second field device of the process control system, when connected to the first field device. , The first fieldbus communication protocol is used to communicate, and when connected to the second field device, the second fieldbus communication protocol is used to communicate, and the second fieldbus communication protocol is , A first interface different from the first fieldbus communication protocol,
A communication processor communicatively linked to the first interface, the first information received from said one of the first field device or the second field device. A communication processor that encodes for communication over a bus that uses a field bus communication protocol and a third communication protocol that is different from the second field bus communication protocol.
A second communication processor and the bus are communicatively linked in order to convey the first information to the control unit of the process control system via the bus using the third communication protocol. Interface, wherein the bus uses the third communication protocol to convey a second piece of information received from the first field device or the other of the second field devices. Interface and
A device that comprises. 18. The device of claim 18, 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. A computer-readable medium that has instructions for execution in a module.
The command is
Receiving the first information from the second field device using a third communication protocol that distinguishes it from the first field device or the second communication protocol using the second communication protocol.
To automatically detect the second communication protocol or the third communication protocol,
Encoding the first information for communicating using the first communication protocol, wherein the first communication protocol is the second communication protocol and the third communication protocol. Different, encoding and
Communicating the encoded first information to the second physical interface using the second physical interface control unit using the first communication protocol.
A computer-readable medium that is an instruction to be executed. The computer-readable medium according to claim 20, wherein the second communication protocol is Profibus PA and the third communication protocol is FOUNDATION fieldbus H1.

Images