This disclosure relates generally to industrial process control and automation systems. More specifically, this disclosure relates to a remote terminal unit (RTU) with wireless diversity and related method.
Wireless networks are frequently used in industrial process control and automation systems. For example, sensors could provide measurements over a wireless network, and actuators could receive control signals over the wireless network. Controllers can receive the sensor measurements and transmit the control signals over the wireless network.
A wireless network in an industrial facility often supports wireless devices that operate in accordance with a single wireless communication protocol. A conventional wireless network typically requires extensive hardware modifications in order to support wireless devices compatible with alternative communication protocols. Thus, additions or replacements of wireless devices in a particular industrial facility are typically allowed only if the new devices are compatible with an existing wireless communication protocol used in the industrial facility.
This disclosure provides a remote terminal unit (RTU) with wireless diversity and related method.
In a first embodiment, a method includes receiving first data from multiple wireless field devices at a remote terminal unit. The first data is received using multiple wireless communication protocols. The method also includes executing control logic at the remote terminal unit in order to control at least part of an industrial process. The method further includes communicating second data to the wireless field devices from the remote terminal unit. The second data is transmitted using the multiple wireless communication protocols. In addition, the method includes communicating at the remote terminal unit with a control system, where the remote terminal unit is at least partially controlled by the control system.
In a second embodiment, an apparatus includes a remote terminal unit. The remote terminal unit includes at least one first interface configured to receive first data from multiple wireless field devices using multiple wireless communication protocols. The remote terminal unit also includes at least one processing device configured to execute control logic in order to control at least part of an industrial process. The remote terminal unit further includes at least one second interface configured to communicate with a control system, where the remote terminal unit is configured to be at least partially controlled by the control system. The at least one first interface is also configured to communicate second data to the wireless field devices using the multiple wireless communication protocols.
In a third embodiment, a non-transitory computer readable medium embodies a computer program. The computer program includes computer readable program code for receiving first data from multiple wireless field devices at a remote terminal unit using multiple wireless communication protocols. The computer program also includes computer readable program code for executing control logic at the remote terminal unit in order to control at least part of an industrial process. The computer program further includes computer readable program code for initiating communication of second data to the wireless field devices from the remote terminal unit using the multiple wireless communication protocols. In addition, the computer program includes computer readable program code for initiating communication at the remote terminal unit with a control system, where the remote terminal unit is configured to be at least partially controlled by the control system.
Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.
For a more complete understanding of this disclosure, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:
The remote terminal unit 102 represents a device or system that provides localized control and data access at a site that is remote from a control or supervisory control and data acquisition (SCADA) system 104 (referred to generally as a “control system”). For example, the remote terminal unit 102 could be positioned at or near an oil, gas, or water well or power substation. In these or other situations, the remote terminal unit 102 can be used to collect data from local sensors and process the data to generate control signals for local actuators. The remote terminal unit 102 can also interact with the control system 104 as needed. In this way, process control and automation functions can be provided at locations remote from the control system 104. The control system 104 is shown as communicating with the remote terminal unit 102 using wired and wireless connections, such as via serial or Ethernet communications and via microwave, cellular, or other radio frequency (RF) communications. For instance, the components 102-104 could ordinarily communicate using a wired connection with wireless communications used as backup. However, the remote terminal unit 102 could communicate with the control/SCADA system 104 over any suitable wireless or wired connection(s).
The remote terminal unit 102 can communicate with various industrial field devices. For example, the remote terminal unit 102 can communicate with one or more wired field devices 106 over one or more wired connections 108. The wired field devices 106 could represent sensors, actuators, or other industrial field devices. The wired connections 108 could represent serial connections (such as RS485 or RS422 connections), Ethernet connections, or other wired connections.
The remote terminal unit 102 can also communicate with various wireless industrial field devices via one or more field device access points (FDAPs) 110. Note that the connection(s) between the remote terminal unit 102 and the field device access point(s) 110 could be wired or wireless. The remote terminal unit 102 and the field device access points 110 have the ability to communicate with wireless field devices using different protocols. For example, the remote terminal unit 102 and the field device access points 110 could communicate with a first wireless field device network 112 containing wireless field devices 114 and with a second wireless field device network 116 containing wireless field devices 118. The field device networks 112 and 116 could support the use of different communication protocols. Note that while the networks 112 and 116 are shown as being separated here, the networks 112 and 116 could partially or completely overlap.
Each wireless field device 114, 118 could perform any desired function in the system 100. For example, the wireless field devices 114, 118 could include wireless sensors, wireless actuators, and other wireless industrial devices. The wireless field devices 114, 118 in the networks 112, 116 could support any suitable wireless communication protocols. In some embodiments, for instance, the wireless field devices 114 in the network 112 could support an ISA100.11a protocol, and the wireless field devices 118 in the network 116 could support a Wireless Highway Addressable Remote Transducer (WirelessHART) protocol.
As described in more detail below, the remote terminal unit 102 incorporates a wireless device manager (WDM) that facilitates communication with the wireless field devices 114 and 118 using different protocols. The remote terminal unit 102 with the wireless device manager can therefore both communicate using multiple protocols and manage wireless resources in multiple wireless networks. Additional details regarding the remote terminal unit 102 are provided below.
The remote terminal unit 102 includes any suitable structure for providing localized data access and control. The control system 104 includes any suitable structure(s) for providing industrial process control and automation. Each field device 106, 114, 118 includes any suitable structure for performing one or more operations related to industrial process control and automation, such as sensing or actuation. Each field device access point 110 represents any suitable structure providing wireless access to field devices.
Although
The processing device 202 includes any suitable structure for controlling operation of a remote terminal unit. As particular examples, the processing device 202 could represent at least one microprocessor, microcontroller, field programmable gate array, digital signal processor, discreet logic device, or other processing or control device.
A memory 204 is coupled to the processing device 202. The memory 204 stores any of a wide variety of information used, collected, or generated by the remote terminal unit 102. For example, the memory 204 could store information received from or being transmitted to different field devices. The memory 204 includes any suitable volatile and/or non-volatile storage and retrieval device(s).
The remote terminal unit 102 further includes an uplink interface 206. The uplink interface 206 supports interaction between the remote terminal unit 102 and the control system 104 or other uplink device or system. The uplink interface 206 includes any suitable structure for supporting uplink communications, such as a serial or Ethernet transceiver and/or a microwave, cellular, or RF transceiver.
In addition, the remote terminal unit 102 includes at least one wired field device interface 208 and at least one wireless field device interface 210. Each interface 208-210 facilitates interaction between the remote terminal unit 102 and field devices. Each wired field device interface 208 includes any suitable structure facilitating communication with wired field devices, such as a serial interface. Each wireless field device interface 210 includes any suitable structure facilitating communication with wireless field devices, such as one or more wireless transceivers and antennas or other wired or wireless interfaces configured to communicate with one or more field device access points 110.
Process data can be generated by wireless field devices 114, 118 to indicate conditions measured by the devices. For instance, process data can include measured values from sensors, such as temperature, pressure, flow rate, voltage, or current readings. Process data is typically distributed via data publication, although other distribution techniques could also be used.
Radio attributes typically represent configurations and settings related to wireless communications in the system 100. Radio attributes can be used by the remote terminal unit 102 to support and control wireless communications using limited bandwidths and frequencies.
Sensor attributes typically represent configurations and settings related to sensors that may be controlled. For example, if a wireless field device is a temperature sensor, sensor attributes could include a cold junction temperature and an indication of whether the device is in-service or out-of-service. Sensor attributes may generally represent parameters that are specific to the type or function of a device and are not related to network management.
As shown in
Communications between the remote terminal unit 102 and the field device access points 110 can involve the same types of data, such as alarms and events, process data, radio attributes, and sensor attributes. As shown in
In this example, the control system 104 is shown as including a SCADA system 104a and a wireless field instrument asset management tool 104b. The management tool 104b could support various functions to manage wireless field devices, such as functions for configuring, commissioning, maintaining, and diagnosing smart field instruments. Communications between the remote terminal unit 102 and the components 104a-104b can again involve the same types of data. The remote terminal unit 102 and the SCADA system 104a can also exchange device lists, and the remote terminal unit 102 and the management tool 104b can also exchange maintenance data. The device lists can identify various devices, such as the field devices, that communicate with the remote terminal unit 102. The maintenance data can be used to set up and maintain the field devices. Communications between the remote terminal unit 102 and the components 104a-104b can use any suitable format(s) or protocol(s). In this example, the formats or protocols include hypertext transfer protocol secure (HTTPS), MODBUS, OLE for Process Control Unified Architecture (OPC-UA), and Distributed Network Protocol 3 (DNP3). Note, however, that any other or additional format(s) or protocol(s) could be used.
As shown in
An RTU execution environment 304 supports features that are used by other programs executed by the remote terminal unit 102. For example, the RTU execution environment 304 could represent software routines that are callable by other programs in the remote terminal unit 102, such as the applications 302. As particular examples, the RTU execution environment 304 could allow the applications 302 to interact with field devices via lower layers of the remote terminal unit 102.
The remote terminal unit 102 further supports multiple input/output (I/O) drivers for communicating with other components in the system 100. In this example, the remote terminal unit 102 includes at least one local I/O driver 306, at least one serial I/O driver 308, and at least one wireless I/O driver 310. Each local I/O driver 306 denotes a driver that facilitates communication with field devices connected directly to the remote terminal unit 102. As examples, the local I/O driver 306 could support communications using the HART IP protocol or one or more proprietary protocols. Each serial I/O driver 308 denotes a driver that facilitates communication with field devices connected to the remote terminal unit 102 by a serial bus, such as an RS422 or RS485 bus. Each wireless I/O driver 310 denotes a driver that facilitates wireless communication with field devices.
In addition, the remote terminal unit 102 includes a wireless device manager (WDM) 312. The wireless device manager 312 manages the wireless networks 112, 116. The wireless device manager 312 also supports the caching of data received or to be transmitted using different wireless protocols. Received data that is cached can be provided to an external client, such as to the applications 302 via the wireless I/O interface 310, regardless of the protocol or protocols in which the cached data was received.
As shown in
The protocol stacks 402-404 can exchange alarms, events, radio attributes, security keys, and other data with two managers 406-408, respectively. The managers 406-408 are associated with different communication protocols. The manager 406 here represents an ISA100.11a system manager used to manage an ISA100.11a network, and the manager 408 here represents a network manager used to manage a WirelessHART network. The managers 406-408 can perform various functions to support the management of ISA100.11a and WirelessHART networks, such as allowing nodes to join the networks and performing security validation. The managers 406-408 can also manage the radio attributes of devices connected to the wireless networks.
A security manager 410 can be used to provide security keys or other wireless network credentials. In some embodiments, the security manager 410 can act as a centralized security repository for all wireless field devices, regardless of which protocols are used by the wireless devices. This can help to avoid the need to maintain separate sets of security keys for devices that use different protocols. The security manager 410 can provide the security keys or other wireless network credentials to the managers 406-408, which can use the security keys to manage the different wireless networks.
A runtime data cache 412 is used to temporarily store data being transferred between a wireless I/O interface 414 and the communication stacks 402-404. The wireless I/O interface 414 represents an interface that can interact with the wireless I/O driver 310 shown in
In this way, multiple protocols could be supported by a remote terminal unit 102 in order to communicate with multiple wireless field device networks. This can enable easier integration of wireless field devices with remote terminal units in a control system.
Although
Data is received at a remote terminal unit from wireless field devices using multiple protocols at step 502. This could include, for example, the communication stacks 402-404 in the remote terminal unit 102 receiving process data and other data from sensor field devices 114, 118 or other field devices using ISA100.11a, WirelessHART, and/or other protocols. The differences between the protocols and the differences between the individual field devices create differences in the data received from the field devices, even when the wireless devices measure similar phenomena.
The received data is extracted and stored at step 504. This could include, for example, the communication stacks 402-404 extracting data from the received data messages and storing the data in the memory 204. This could also include the managers 406-408 storing the data in the runtime data cache 412. The location(s) where the data is stored can vary depending on the intended usage of the data.
Process control functions are performed at the remote terminal unit at step 506. This could include, for example, the processing device(s) 202 executing control logic to determine how to adjust an industrial process based on the received data. As a particular example, this could include the processing device(s) 202 executing control logic to determine how to adjust equipment associated with an oil, gas, or water well or power substation.
Data is generated and transmitted to the wireless field devices from the remote terminal unit using multiple protocols at step 508. This could include, for example, the processing device(s) 202 generating control signals for adjusting actuator field devices. This could also include the communication stacks 402-404 preparing and transmitting the control data and other data to actuator field devices 114, 118 or other field devices using ISA100.11a, WirelessHART, and/or other protocols.
During this time, the remote terminal unit interacts with a separate control system at step 510. This could include, for example, the remote terminal unit 102 communicating with the control system 104 via the uplink interface 206. The remote terminal unit 102 could provide data to the control system 104, such as data from sensors or control signals generated for actuators. The remote terminal unit 102 could also receive data from the control system 104, such as control signals for actuators or setpoints for control logic. In some embodiments, the control system 104 controls the overall operation of the remote terminal unit 102. Data transported to and from the control system 104 can be stored in the runtime data cache 412.
Although
As shown in
Wireless input and output signals are extracted at step 604. This could include, for example, the processing device(s) 202 in the remote terminal unit 102 identifying the input signals to be received wirelessly and the output signals to be transmitted wirelessly using the RTU control algorithms. This information informs the remote terminal unit 102 about the signals to be handled by the remote terminal unit 102 during process control.
Input/output delivery times for the RTU control algorithms are identified at step 606. This could include, for example, the processing device(s) 202 in the remote terminal unit 102 identifying timing requirements for the receipt of input wireless signals and the delivery of output wireless signals required by the RTU control algorithms. The timing requirements can be associated with any suitable functionality, such as timing requirements for receiving inputs from wireless sensors and timing requirements for delivering control signals to wireless actuators.
At least one wireless network is configured to deliver data accordingly at step 608. This could include, for example, establishing wireless connections between devices in the wireless network 112 or 116 in order to deliver data to or from the remote terminal unit 102 in accordance with the identified timing requirements. The wireless network(s) could be configured via one or more of the managers 406-408.
In this way, the remote terminal unit 102 is able to synchronize wireless communications (such as data publications) with the execution of the RTU control algorithms. This can enable more effective control over an industrial process and help to ensure compliance with various control algorithms' timing requirements.
Although
In some embodiments, various functions described above are implemented or supported by a computer program that is formed from computer readable program code and that is embodied in a computer readable medium. The phrase “computer readable program code” includes any type of computer code, including source code, object code, and executable code. The phrase “computer readable medium” includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A “non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.
It may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term “couple” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms “application” and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer code (including source code, object code, or executable code). The terms “receive” and “communicate,” as well as derivatives thereof, encompass both direct and indirect communication. The terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation. The term “or” is inclusive, meaning and/or. The phrase “associated with,” as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The phrase “at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, “at least one of: A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.
While this disclosure has described certain embodiments and generally associated methods, alterations and permutations of these embodiments and methods will be apparent to those skilled in the art. Accordingly, the above description of example embodiments does not define or constrain this disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of this disclosure, as defined by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
5095417 | Hagiwara | Mar 1992 | A |
5357517 | Takebe | Oct 1994 | A |
6639806 | Chuang | Oct 2003 | B1 |
7555004 | Orlik et al. | Jun 2009 | B2 |
7969300 | Coronel et al. | Jun 2011 | B2 |
8072098 | Elias et al. | Dec 2011 | B2 |
8239046 | Koehler | Aug 2012 | B2 |
8315263 | Enns et al. | Nov 2012 | B2 |
8352049 | Hsiung et al. | Jan 2013 | B2 |
8392626 | Wormmeester et al. | Mar 2013 | B2 |
8583067 | Budampatl et al. | Nov 2013 | B2 |
8656065 | Gerhart et al. | Feb 2014 | B1 |
8667091 | Almadi et al. | Mar 2014 | B2 |
8868907 | Graham et al. | Oct 2014 | B2 |
9021255 | Aharoni et al. | Apr 2015 | B1 |
9379972 | Enns | Jun 2016 | B2 |
20020147503 | Osburn, III | Oct 2002 | A1 |
20030151513 | Herrmann | Aug 2003 | A1 |
20040259533 | Nixon | Dec 2004 | A1 |
20050174964 | Orlik et al. | Aug 2005 | A1 |
20050216107 | O'Donnell | Sep 2005 | A1 |
20050243867 | Petite | Nov 2005 | A1 |
20050273205 | Nickerson | Dec 2005 | A1 |
20060087402 | Manning | Apr 2006 | A1 |
20060202728 | Wich | Sep 2006 | A1 |
20060240818 | McCoy et al. | Oct 2006 | A1 |
20070280144 | Hodson et al. | Dec 2007 | A1 |
20080077336 | Fernandes | Mar 2008 | A1 |
20080080395 | Law | Apr 2008 | A1 |
20090201150 | Becker | Aug 2009 | A1 |
20090224906 | Balgard | Sep 2009 | A1 |
20090271558 | Wormmeester et al. | Oct 2009 | A1 |
20090316628 | Enns et al. | Dec 2009 | A1 |
20100079007 | Elias | Apr 2010 | A1 |
20100176933 | Barragan Trevino | Jul 2010 | A1 |
20110110291 | Ishii | May 2011 | A1 |
20110246791 | Kambayashi | Oct 2011 | A1 |
20110276607 | Surna et al. | Nov 2011 | A1 |
20120041574 | Hsiung et al. | Feb 2012 | A1 |
20120063330 | Mori | Mar 2012 | A1 |
20120078869 | Bellville | Mar 2012 | A1 |
20120084400 | Almadi | Apr 2012 | A1 |
20120151588 | Wang et al. | Jun 2012 | A1 |
20120230446 | Feng | Sep 2012 | A1 |
20120236768 | Kolavennu | Sep 2012 | A1 |
20120290735 | Johnson et al. | Nov 2012 | A1 |
20130110998 | Zrelli | May 2013 | A1 |
20130151849 | Graham et al. | Jun 2013 | A1 |
20130173840 | Calvin | Jul 2013 | A1 |
20130246801 | Takahashi | Sep 2013 | A1 |
20130262064 | Mazzaro | Oct 2013 | A1 |
20130307699 | Brekke | Nov 2013 | A1 |
20130344839 | Roach | Dec 2013 | A1 |
20140119290 | Grewal | May 2014 | A1 |
20140232555 | Aakvaag | Aug 2014 | A1 |
20140321443 | Samudrala | Oct 2014 | A1 |
20150058480 | Allgaier | Feb 2015 | A1 |
20150278144 | Mclaughlin et al. | Oct 2015 | A1 |
20150304193 | Ishii | Oct 2015 | A1 |
20160048474 | Lv et al. | Feb 2016 | A1 |
Number | Date | Country |
---|---|---|
2007527073 | Sep 2007 | JP |
4990755 | Aug 2012 | JP |
201353730 | Sep 2013 | JP |
20100066815 | Jun 2010 | KR |
20120135142 | Dec 2012 | KR |
WO 2005086110 | Sep 2005 | WO |
WO 2014197182 | Dec 2014 | WO |
WO 2015047744 | Apr 2015 | WO |
Entry |
---|
U.S. Office Action issued for U.S. Appl. No. 13/908,977 dated Jan. 29, 2016, 14 pgs. |
International Search Report dated Oct. 10, 2014 in connection with International Application No. PCT/US2014/038208; 3 pages. |
Written Opinion of the International Searching Authority dated Oct. 10, 2014 in connection with International Application No. PCT/US2014/038208; 5 pages. |
International Search Report dated Dec. 11, 2014 in connection with International Application No. PCT/US2014/055307; 4 pages. |
Written Opinion of the International Searching Authority dated Dec. 11, 2014 in connection with International Application No. PCT/US2014/055307; 7 pages. |
European Search Report dated Sep. 22, 2014 in connection with European Patent Application No. 14164273.6; 3 pages. |
Non-Final Office Action dated Dec. 22, 2014 in connection with U.S. Appl. No. 13/908,977; 12 pages. |
Final Office Action dated Jun. 10, 2015 in connection with U.S. Appl. No. 13/908,977; 13 pages. |
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration dated Jun. 10, 2015 in connection with International Patent Application No. PCT/US2015/019671. |
Office Action dated Aug. 2, 2016 in connection with U.S. Appl. No. 14/228,142. |
International Search Report and Written Opinion dated Oct. 27, 2015 in connection with PCT/US2015/043607. |
“25A Right Angle Signal/Power Combo”, SAMTEC Power Strip 25, 2008, 1 page. |
“FCN-RTU Low Power Autonomous Controller Hardware”, STARDOM FCN-RTU, Yokogawa Electric Corporation, Dec. 2008, 13 pages. |
“ControlWave Micro Process Automation Controller”, Instruction Manual, Emerson Process Management, Jun. 2013, 170 pages. |
Supplementary European Search Report dated Apr. 28, 2017 in connection with European Patent Application No. EP 14 84 8127. |
David D. Brandt, “Solving the Issue of Interoperability among Devices and Systems”, May 19, 2008, p. 1-21, XP055091082. |
Number | Date | Country | |
---|---|---|---|
20150084747 A1 | Mar 2015 | US |