EP2859417A1 - Optimized communications with hart instruments - Google Patents
Optimized communications with hart instrumentsInfo
- Publication number
- EP2859417A1 EP2859417A1 EP12733251.8A EP12733251A EP2859417A1 EP 2859417 A1 EP2859417 A1 EP 2859417A1 EP 12733251 A EP12733251 A EP 12733251A EP 2859417 A1 EP2859417 A1 EP 2859417A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- hart
- commands
- instrument
- requests
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B15/00—Systems controlled by a computer
- G05B15/02—Systems controlled by a computer electric
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Program-control systems
- G05B19/02—Program-control systems electric
- G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
- G05B19/4185—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by the network communication
- G05B19/4186—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by the network communication by protocol, e.g. MAP, TOP
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/30—Nc systems
- G05B2219/33—Director till display
- G05B2219/33331—Test, diagnostic of field device for correct device, correct parameters
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Definitions
- PCT application number also identified by attorney docket number 500402.00595;
- Devices connected to an industrial network may use various protocols to communicate with each other. Any one communication protocol may allow access to particular data throughout the network, but may not allow access to other data or devices. In addition, translating data requests from one protocol to another may result in inefficient and potentially duplicative network traffic. There is a need to improve communications efficiency for industrial networks that include more than one communication protocol.
- a device may receive two or more requests that each require accessing data of a single HART instrument.
- One or more of these requests may be requests to access data of the single HART instrument on an ongoing basis.
- a scan cycle may be established in response to these requests.
- the two or more requests to access data of a single HART instrument may be analyzed to identify the set of data of the single HART instrument that needs to be accessed to fulfill the requests.
- a combination of HART commands that can be used to access all of this data may be identified.
- the combination of HART commands that is identified may be made up of the smallest number of commands that can access all of the set of data.
- the identified combination of commands may be limited to commands that are supported by the single HART instrument.
- the identified set of commands may be sent to the single HART device.
- the response received from the single HART device may be used to generate replies to each of the two or more requests.
- Figure 1 illustrates an example of an industrial network in accordance with various aspects of the disclosure.
- FIG. 2 illustrates several examples of HART commands that may be used to retrieve data from a HART instrument in accordance with various aspects of the disclosure.
- Figure 3 illustrates two examples of outputs of a HART multiplexer in accordance with various aspects of the disclosure.
- Figure 4 illustrates an example of a method that a device may use to determine which HART commands to send to a HART instrument in accordance with various aspects of the disclosure.
- An industrial network may be used for a wide variety of purposes.
- Industrial networks are generally used to control or monitor industrial processes. For example, the amount of a fluid that is allowed into a mixing device may be controlled by actuating a valve in response to readings from one or more sensors.
- Industrial networks may be made up of any number of devices. These devices may be configured to communicate using various protocols, and the protocols may not be compatible with one another.
- FIG. 1 illustrates an example of an industrial network.
- HART multiplexer 110 is in communication with HART instruments 130-134.
- Each HART instrument communicates with the HART multiplexer 110 using the Highway Addressable Remote Transducer (HART) protocol.
- HART Highway Addressable Remote Transducer
- This protocol allows for a single analog signal to be carried over a two-wire loop.
- Each of links 140-144 may be a two- wire loop.
- the analog signal values are represented by the current flowing through the two-wire loop, which ranges from 4 to 20 mA.
- Digital communications may be superimposed on the analog signal, allowing for additional data to be exchanged between each HART instrument 130-134 and the HART multiplexer 110. More than one instrument may be added to each two-wire loop.
- HART instruments may include sensors, transducers, or any other device that communicates using the HART protocol.
- Asset management software (AMS) 101 communicates with HART multiplexer 110.
- the asset management software may run on any computing device. Communications between AMS 101 and HART multiplexer 110 are illustrated by link 102. Communications over link 102 may take place using, for example, the Arcom protocol, which is a protocol designed for communicating with a HART multiplexer.
- the HART multiplexer 110 multiplexes signals from each HART instrument (130-134) onto communication link 102, thereby allowing asset management software 102 to communicate with each HART instrument 130-134 via a single communications link.
- Asset management software is typically used to monitor the status of an industrial network. This often involves repeatedly checking the status of various sensors, valves, or other HART instruments.
- HART multiplexer 110 may help facilitate these checks by retrieving data from HART instruments automatically on an ongoing basis. By automatically retrieving data from HART instruments on an ongoing basis (which is sometimes referred to as "scanning"), the HART multiplexer may improve the speed with which it can provide data to the asset management software.
- Controller 103 also communicates with HART multiplexer 110.
- Controller 103 may be any type of controller, such as, for example, a programmable logic controller. Communications between controller 103 and HART multiplexer 110 are illustrated by link 104.
- Link 104 may be, for example, an Ethernet link. Communications over link 104 may take place using, for example, the MODBUS protocol.
- Other examples of protocols that may be used to communicate between HART multiplexer 110 and controller 103 include the EtherNet/IP, DeviceNet, ProfiNet, and ProfiBus communications protocols. Any other industrial networking communications protocol may also be used. None of the listed protocols are compatible with the HART protocol.
- HART multiplexer 110 may respond to communications received on link 104 in the same format as the received request.
- HART multiplexer 110 may include the requested data in a MODBUS reply message.
- the requested data may have come from, for example, HART instrument 131.
- the HART multiplexer may translate requests from controller 103 into a HART message, send that message to a HART instrument, and translate the reply from the HART instrument into a message that controller 103 can understand.
- the HART multiplexer may also scan the HART instruments in order to pre-fetch the data that is likely to be requested by controller 103. The pre-fetched data may be used to improve the speed with which the HART multiplexer responds to requests from controller 103.
- the data to be scanned may be determined automatically by the HART multiplexer by analyzing data frequently requested by controller 103.
- the data to be scanned may also be configured by a user.
- Requests for data received in protocols that are not designed to interoperate with HART devices may be accommodated by creating a mapping between aspects of the protocol and the data of the HART devices. For example HART variables may be mapped to MODBUS registers.
- Ethernet Industrial Protocol (“EtherNet/IP”) objects may be created for HART devices, and data fields of the EtherNet/IP objects may correspond to HART variables, as described in the patent application identified by Attorney Docket No. SAA- 191 (402.00595), titled "System and Method For Accessing Information Using Objects.” This application, which is filed on the same day as the instant patent application, is hereby incorporated by reference in its entirety.
- a human-machine interface may also communicate with HART multiplexer 110 in order to monitor and report information about the HART instruments.
- Instruments besides HART instruments may also exist on the network. These other instruments may, for example, communicate with controller 103 directly.
- more instances of each element shown in Figure 1 may exist. For example, there may be more HART instruments than instruments 130-134. Also, there may be more than one HART multiplexer.
- Each HART multiplexer may be connected to the same AMS and the same controller. Alternatively, or in addition, additional controllers or additional AMS instances may be used. Additional alterations may also be made to the industrial network illustrated in Figure 1.
- controller 103 may be modified to include HART multiplexer 110 as one of its components. If HART multiplexer 110 is incorporated into controller 103, controller 103 may still include an Ethernet port for communications with other outside devices, such as instruments that communicate using protocols other than HART, other controllers, and other computing devices.
- HART multiplexer 110 includes processor 11 1, which may be configured to receive messages from AMS 101, controller 103, HART modems 113-114, or any other devices.
- the software that configures processor 11 1 may be stored in memory 112. This software may include an operating system with applications running thereon. Memory 112 may also store other data, such as data read from HART instruments 130-134. Memory 112 may include read-only memory (ROM) and random access memory (RAM). Some or all of the software, memory, and microprocessor just described may also be embodied in an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like.
- ASIC application specific integrated circuit
- FPGA field programmable gate array
- Each of the devices depicted in Figure 1 may include one or more components, such as a processor, memory, and communications interface, similar to those shown for HART multiplexer 110.
- FIG 2 illustrates several examples of HART commands that may be used to retrieve data from a HART instrument. These commands are merely examples.
- the HART protocol includes many commands in addition to those illustrated in Figure 2.
- Column 201 lists the number of the HART command.
- Column 202 lists the values that each command instructs the instrument receiving the command to read. Notice that some commands have been redefined over time in the HART protocol specification. As shown in Figure 2, command 9, as of HART protocol version 6, may be used to read any four variables. But as of HART protocol version 7, command 9 may be used to read any eight variables.
- Column 203 of Figure 2 lists the number of bytes that must be sent by multiplexer 110 to specify the values to be read. Zero bytes are needed for commands 1, 2, and 3 because the values to be read are pre-defined for commands 1, 2, and 3. For command 9, on the other hand, a byte is needed to specify each variable to be read.
- Column 204 of Figure 2 lists the number of bytes that a HART instrument will send to multiplexer 110 in response to a command. For example, an instrument will respond to command 1 by sending 5 bytes. One of these bytes represents the units in which the variable is being sent. The other four bytes represent the value of the variable itself.
- FIG. 3 illustrates two examples of outputs of HART multiplexer 110. Each of these outputs may occur after the HART multiplexer is instructed to automatically retrieve data from HART instruments on an ongoing basis.
- the data to be retrieved automatically is retrieved from each instrument using a "scan command.”
- the particular command or commands that make up the "scan command” may differ for each HART instrument. For example, if the AMS software requests the "primary variable" from instrument 130 (but no other information), then the scan command for instrument 130 may be HART command 1. If the AMS software requests the primary, secondary, and tertiary variables from instrument 131, then the scan command for instrument 131 may be HART command 3, which retrieves these three variables, as well as some others.
- Column 301 shows an uninterrupted sequence of scan commands. These commands may be output by HART multiplexer 110 when the multiplexer does not receive other inputs from AMS 101 or controller 103. The scan commands are sent repeatedly, which enables the HART multiplexer to always have the most up-to-date information from each instrument.
- Column 302 shows a sequence of HART commands that may be output by HART multiplexer 1 10 when the multiplexer receives an input from AMS 101 or controller 103.
- the normal sequence of scan commands may be interrupted in order to include a message dictated by the AMS.
- the AMS may request an additional variable from instrument 130 beyond the variables included in the normal scan.
- the normal sequence of scan commands is interrupted at slot 310 in order to insert a command requesting the additional information for the AMS.
- the normal sequence of scan commands may resume after the input from the AMS has been handled.
- the normal sequence of scan commands may be interrupted in order to send any type of HART command, including read commands, write commands, and other commands, such as device configuration commands.
- AMS software 101 may specify these commands directly.
- a connected device may make a request that HART multiplexer 110 must process in order to fulfill.
- controller 103 may send a command using the Ethernet/IP protocol that the HART multiplexer translates into a series of HART commands.
- Multiplexer 110 may interrupt the normal series of scan commands to insert the series of HART commands.
- the normal series of scan commands may read the primary variable from instrument 134 using command 1.
- Multiplexer 110 may receive a request for the secondary, tertiary, and quaternary variable of instrument 134. Instead of interrupting the normal series of scan commands, multiplexer 110 may substitute command 3 for command 1 when it next outputs a scan command to instrument 134. Another alternative is to send command 3 immediately, thereby obtaining the recently requested information along with the information that would have been retrieved by the normal scan command.
- the next scan command for instrument 134 may be skipped. Alternatively, the next scan command for instrument 134 might not be skipped. If the next scan command for instrument 134 is not to be skipped, then multiplexer 110 might not ensure that the information normally obtained by the scan command is also obtained during the request that interrupts the normal scan sequence.
- Whether to interrupt or alter the normal sequence of scan commands may be determined based on, for example, a priority of the request for additional information.
- a high priority request may interrupt the normal sequence of scan commands, but a lower priority request may not.
- the location of the multiplexer in its sequence of scan commands may also affect whether multiplexer 110 interrupts its normal sequence of scan commands. For example, a request for data from instrument 131 may need to be fulfilled in 500 ms. It may be possible to fulfill this request in 500 ms by scanning instrument 131 in sequence, but using a modified scan command instead of the normal scan command for instrument 131. If, however, a scan of instrument 131 is not scheduled to occur soon, interrupting the normal sequence of scan commands may be necessary to ensure that the requested data is obtained within 500 ms.
- commands received from other devices can also be combined with one another.
- AMS 101 may request that HART command 3 be sent to instrument 134. This command reads current and the primary through quaternary variables.
- Controller 103 may issue a command that requires three additional variables to be read from instrument 134.
- Multiplexer 110 may process these command individually, by, for example, sending command 3 in response to the request from AMS 101 and sending command 9 in response to the request from controller 103. But multiplexer 110 may also combine processing of these commands by, for example, sending a single command 9 to instrument 134 that requests not only the data requested by controller 103 but also the data specified by command 3.
- one HART command may be directed to instrument 134 instead of two separate commands.
- Multiplexer 110 may reformat the data it receives from instrument 134. Because, in this example, the AMS requested that command 3 be sent, multiplexer 110 may reformat the relevant portions of the data it received in response to sending command 9 into the format used for responding to command 3. The reformatted data may then be sent to the AMS. Similarly, multiplexer 110 may send to controller 103 only the data requested by controller 103.
- the process of combining commands may also be used to identify the normal scan commands themselves.
- the HART multiplexer may identify that a first set of data needs to be scanned for AMS 101, and that a second set of data needs to be scanned for controller 103.
- the HART multiplexer may combine these first and second sets into a third set using a union operation.
- the HART multiplexer may use this third set to identify which commands will be the normal scan commands for each instrument. This procedure may help optimize the size of the set of normal scan commands.
- FIG. 4 illustrates an example of a method that a device, such as multiplexer 1 10, may use to determine which HART commands to send to a HART instrument.
- the device may communicate with one or more HART instruments.
- the device receives requests that require accessing a HART instrument.
- a request is a request to provide data on an ongoing basis. (Such requests may be fulfilled by using, for example, a multiplexer's normal scan cycle.)
- Other examples of requests include other communications from AMS 101 or controller 103.
- Received requests may be combined because, for example, the requests were received simultaneously or closely together in time.
- Another example of when received requests may be combined is when the received request is being combined with a request that is part of the device's normal scan cycle. Combining multiple requests to scan data with one another may make the device's normal scan cycle more efficient than processing each scan request separately.
- step 402 the received requests are inspected, and the set of data that needs to be accessed from the HART instrument to fulfill all of the received requests is identified.
- This set of data is the union of the data needed to fulfill each request individual request. For example, if one request needs to access the primary and secondary variables and another needs to access the secondary and tertiary variables, then the set of data that needs to be accessed includes the primary, secondary, and tertiary variables.
- requests to write data to the HART instrument may also be combined. If a request is made to both read from and write to the same variable, then the device must determine if the read request is required to be performed first. If the read request does not need to occur first (because, for example, the read request is merely part of the normal scan cycle), then the read request may be omitted in step 402. Writing to the variable, but not reading from it, may be equivalent to assuming that the read request came second. The value that is written to the variable can be used as the device's response to the read request.
- step 403 the device identifies the smallest combination of HART commands that accesses the set of data identified in step 402.
- the smallest combination is the combination that includes the fewest number of individual HART commands.
- the device might use only HART commands that are supported by the HART instrument. For example, if the HART instrument only supports version 6 of the HART protocol, then no combinations will be identified that read more than four variables with command 9. (Reading more than 4 variables with command 9 was first introduced in version 7 of the HART protocol.)
- step 403 identifies combinations that include the fewest number of individual HART commands, each combination considered in step 405 already includes this minimum number of commands.
- step 405 the device identifies which combination of commands requires the least amount of data transfer between the HART instrument and the device.
- the data transfer considered in step 405 may include data used to specify which values to read, as illustrated in column 203 of Figure 2.
- the data transfer considered in step 405 may also include data needed to respond to a command, as illustrated in column 204 of Figure 2. If two or more combinations of commands include the same number of commands and require the same amount of data transfer, then an additional tie-breaking rule may be used to choose between them.
- the tie-breaking rule may include choosing one of the combinations arbitrarily.
- the identified combination of commands is sent to the HART instrument.
- the identified combination may be sent as part of a HART multiplexer's normal scan cycle. Alternatively, the identified combination may interrupt the normal scan cycle. Further, the identified combination may be sent by a device that does not perform a normal scan cycle.
- step 407 the response(s) from the HART instrument to the commands sent in step 406 are used by the device to appropriately reply to each request that was received in step 401.
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Manufacturing & Machinery (AREA)
- Quality & Reliability (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Programmable Controllers (AREA)
- Control By Computers (AREA)
Abstract
Description
Claims
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/US2012/041302 WO2013184113A1 (en) | 2012-06-07 | 2012-06-07 | Optimized communications with hart instruments |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| EP2859417A1 true EP2859417A1 (en) | 2015-04-15 |
| EP2859417B1 EP2859417B1 (en) | 2018-01-10 |
Family
ID=46466826
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| EP12733251.8A Active EP2859417B1 (en) | 2012-06-07 | 2012-06-07 | Optimized communications with hart instruments |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US10281887B2 (en) |
| EP (1) | EP2859417B1 (en) |
| CN (1) | CN104508581B (en) |
| RU (1) | RU2014151364A (en) |
| WO (1) | WO2013184113A1 (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3125053B1 (en) * | 2015-07-31 | 2017-07-26 | Siemens Aktiengesellschaft | Method and peripheral module for the transmission of hart variables and cpu unit for reading the hart variables |
| KR102244297B1 (en) * | 2019-12-17 | 2021-04-23 | 엘에스일렉트릭(주) | Plc analog module with hart pass-through interface |
| DE102020211217B3 (en) * | 2020-09-07 | 2021-08-26 | Siemens Aktiengesellschaft | Data acquisition device with a HART multiplexer |
| CN113225382A (en) * | 2021-04-07 | 2021-08-06 | 中国二十冶集团有限公司 | Method and system for diagnosing state of instrument equipment through digital quantity remote communication |
| CN116192996B (en) * | 2022-12-30 | 2026-01-27 | 杭州和利时自动化有限公司 | HART IO system and data acquisition method thereof |
| FR3166024A1 (en) * | 2024-09-03 | 2026-03-06 | Electricite De France | method for monitoring instrumented systems connected to a current loop |
Family Cites Families (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7054337B2 (en) * | 2002-03-15 | 2006-05-30 | Fisher Controls International Llc. | Method and apparatus for optimizing communications in a multiplexer network |
| US7460865B2 (en) | 2003-06-18 | 2008-12-02 | Fisher-Rosemount Systems, Inc. | Self-configuring communication networks for use with process control systems |
| US7574512B2 (en) | 2004-04-15 | 2009-08-11 | Schneider Automation Sas | MODBUS encapsulated transport interface |
| US8156232B2 (en) | 2005-09-12 | 2012-04-10 | Rockwell Automation Technologies, Inc. | Network communications in an industrial automation environment |
| US7650196B2 (en) | 2005-09-30 | 2010-01-19 | Rockwell Automation Technologies, Inc. | Production monitoring and control system having organizational structure-based presentation layer |
| US20070078540A1 (en) | 2005-10-05 | 2007-04-05 | Invensys Systems, Inc. | Utility for comparing deployed and archived parameter value sets within a field device editor |
| US20070186010A1 (en) | 2006-02-03 | 2007-08-09 | Rockwell Automation Technologies, Inc. | Extending industrial control system communications capabilities |
| WO2008024912A2 (en) | 2006-08-25 | 2008-02-28 | Invensys Systems, Inc. | Remote operation of process control equipment |
| DE102007058606A1 (en) | 2007-12-04 | 2009-06-10 | Codewrights Gmbh | Method for integrating device objects into an object-based management system for field devices in automation technology |
| EP2314021B1 (en) * | 2008-06-18 | 2018-09-19 | Emerson Process Management LLLP | System and method for wireless process communication over distinct networks |
| JP2012527055A (en) * | 2009-05-15 | 2012-11-01 | フィッシャー−ローズマウント・システムズ・インコーポレーテッド | Handheld field maintenance tool with improved functionality |
| WO2010133250A1 (en) * | 2009-05-19 | 2010-11-25 | Abb Reserach Ltd. | Computer-implemented method and system for automatic generation of time slot allocation for a wireless control loop |
| FR2949592B1 (en) * | 2009-08-26 | 2017-07-21 | Schneider Electric Ind Sas | MULTIPLEXING DEVICE, MONITORING PLANT COMPRISING SUCH A DEVICE AND METHOD OF MONITORING |
| EP2580899B1 (en) * | 2010-06-11 | 2014-04-30 | ABB Research LTD | An energy efficient method for communication between a wireless sensor network and an industrial control system |
| US9903749B2 (en) * | 2011-05-26 | 2018-02-27 | Rosemount Tank Radar Ab | Method and device for providing an indication of the reliability of a process parameter value to a host system |
| US9727511B2 (en) * | 2011-12-30 | 2017-08-08 | Bedrock Automation Platforms Inc. | Input/output module with multi-channel switching capability |
-
2012
- 2012-06-07 EP EP12733251.8A patent/EP2859417B1/en active Active
- 2012-06-07 WO PCT/US2012/041302 patent/WO2013184113A1/en not_active Ceased
- 2012-06-07 CN CN201280074843.5A patent/CN104508581B/en active Active
- 2012-06-07 US US14/405,998 patent/US10281887B2/en active Active
- 2012-06-07 RU RU2014151364A patent/RU2014151364A/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| WO2013184113A1 (en) | 2013-12-12 |
| CN104508581B (en) | 2017-03-29 |
| US20150148918A1 (en) | 2015-05-28 |
| US10281887B2 (en) | 2019-05-07 |
| EP2859417B1 (en) | 2018-01-10 |
| CN104508581A (en) | 2015-04-08 |
| RU2014151364A (en) | 2016-07-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8886786B2 (en) | Method for plant monitoring with a field bus of process automation technology | |
| JP4769808B2 (en) | Interface modules used in Fieldbus device networks and Internet-based and non-Internet-based process control networks | |
| EP3235185B1 (en) | Data transfer on an industrial process network | |
| US10281887B2 (en) | Optimized communications with HART instruments | |
| US11435729B2 (en) | Method for operating a field device | |
| WO2004070480A2 (en) | Interface module for use with a modbus device network and a fieldbus device network | |
| WO2013184115A1 (en) | Message tunneling in an industrial network | |
| US7830798B2 (en) | Determining of telegram lengths | |
| US20180164778A1 (en) | Method and System for Monitoring a Plant of Process Automation | |
| JP2007122704A (en) | Method and apparatus for segmenting industrial control data | |
| CN101828152A (en) | Method for operating a field device for process automation having at least two measurement channels and field device for process automation having at least two measurement channels and suitable for performing said method | |
| US11973652B2 (en) | Field detection device for a fieldbus network | |
| CA2870906C (en) | Methods and systems to provide update information of a device description of a field instrument | |
| CN106407139B (en) | Method and Peripheral Components and CPU Unit for Transferring HART Variables | |
| CN101809941B (en) | Control node for a network of control nodes | |
| US11514018B2 (en) | Method and data conversion unit for monitoring an automation system | |
| US20150153717A1 (en) | System and method for accessing information using objects | |
| JP2017163368A (en) | Communication protocol converter | |
| CN114746816B (en) | PLC analog module with HART pass-through interface | |
| US20250119319A1 (en) | Application aware modbus gateway | |
| HK1144344A (en) | Control node for a network of control nodes |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
| 17P | Request for examination filed |
Effective date: 20141211 |
|
| AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
| AX | Request for extension of the european patent |
Extension state: BA ME |
|
| DAX | Request for extension of the european patent (deleted) | ||
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
| 17Q | First examination report despatched |
Effective date: 20161213 |
|
| REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602012041923 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: G05B0019418000 Ipc: G05B0015020000 |
|
| GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
| RIC1 | Information provided on ipc code assigned before grant |
Ipc: G05B 19/418 20060101ALI20170707BHEP Ipc: H04L 29/08 20060101ALI20170707BHEP Ipc: G05B 15/02 20060101AFI20170707BHEP |
|
| INTG | Intention to grant announced |
Effective date: 20170725 |
|
| GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
| GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
| AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
| REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP Ref country code: AT Ref legal event code: REF Ref document number: 963051 Country of ref document: AT Kind code of ref document: T Effective date: 20180115 |
|
| REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
| REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602012041923 Country of ref document: DE |
|
| REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20180110 |
|
| REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 963051 Country of ref document: AT Kind code of ref document: T Effective date: 20180110 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180410 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180510 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180411 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180410 |
|
| REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602012041923 Country of ref document: DE |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: AL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 |
|
| PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 |
|
| 26N | No opposition filed |
Effective date: 20181011 |
|
| REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 |
|
| REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20180630 |
|
| REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180607 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180630 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180607 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180630 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180630 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180607 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180110 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20120607 Ref country code: MK Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180110 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20250626 Year of fee payment: 14 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20250617 Year of fee payment: 14 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20250624 Year of fee payment: 14 |