Devices may include specialized “communication” hardware to exchange data with one another. Structure for this hardware often works with protocols that define a data format, for example, rules that set out syntax, semantics, and like structure for the data. Various data formats are known with features or functionality that may benefit certain applications over others. This variability tends to require device designs to tailor components for use with communication hardware that can operate in each, individual application. The result is that devices that work in one application may not readily work in another application because the communication hardware is not able to work with any “new” data format. For industrial devices, wholesale changes to certain parts, typically circuitry, are often necessary to properly align the device to work with different control systems or even to communicate data to different remote computers, tablets, or other “smart” appliances. These changes may require valuable time and resources to design, build, test, and integrate parts that outfit the device with functions to cooperate in its intended application. Once built, though, the resulting hardware constraints limit compatibility of the device, which may complicate inventory and bill-of-materials because of the specificity of designs necessary to meet the wide array of existing and potentially new applications.
The subject matter of this disclosure relates to improvements to industrial devices that address these issues. Of particular interest herein are embodiments that can accommodate different protocols or data formats with little to no changes in the underlying hardware on the device. The embodiments may include a replaceable board or card that introduces functionality to translate data from the device's native language to the protocol necessary for external communication, and vice versa. This feature foregoes the need for complex re-design and manufacture to adapt industrial devices from one protocol to another protocol.
Reference is now made briefly to the accompanying drawings, in which:
Where applicable like reference characters designate identical or corresponding components and units throughout the several views, which are not to scale unless otherwise indicated. The embodiments disclosed herein may include elements that appear in one or more of the several views or in combinations of the several views. Moreover, methods are exemplary only and may be modified by, for example, reordering, adding, removing, and/or altering the individual stages.
The discussion below describes embodiments of industrial devices. These embodiments are configured with communication hardware that diverges from devices-to-date, which tend to have hardware that is purpose built to communicate in accordance with only a specified or prevailing protocol. The configurations herein, however, provide both functional automation and flexibility to streamline interoperability of the embodiments among different protocols and data formats. In many industries, these features create device-level automation that is dynamic because the hardware can readily to adapt to different modalities of communication. As a result, the embodiments may take advantage of advances in data transfer and computing technologies, as well as to facilitate capital improvements or investment in process control systems.
Broadly, the functional board 100 may be configured to easily adapt the hardware 102 for new functions. These configurations may bi-furcate data processing to accommodate use of different protocols (or “languages”) for data exchange that occurs “on-board” and “off-board” the device. In use, this feature permits the hardware 102 to accommodate different protocols for off-board exchange with little added expense to re-design or overhaul the underlying circuitry on the functional board 100. As a result, the hardware 102 can repurpose for other applications as part of processes to assemble or refurbish the functional board 100 (or the device 102) or as part of upgrades or repair, some of which may even occur with the hardware 102 resident in the field.
The hardware 102 may be configured to perform a variety of functions. Metrology hardware may include utility meters, like gas meters or water meters. These meters can generate data to quantify flow of fluids. Processing this data generates values that may find use, for example, to bill or charge customers for fuel. Process hardware may include flow controls, like valves or actuators. These devices may integrate into larger control systems, some of which may control the process hardware to regulate flow of fluids through process lines.
The off-board device 104 may be configured to exchange data with the device 102. These configurations may include devices that allow an end user to send and receive data. Suitable devices may include computing devices, like laptops, tablets, and smartphones. Larger control systems may include a controller that delivers control signals to the device 102 or that retrieves operating data from the device 102. Control signals can cause the device 102 to operate, for example, in accordance with process parameters on the process line.
The board-level assembly 106 may be configured to adapt the device 102 to talk to the off-board device 104. The main board 108 may integrate as a component of operative circuitry found on the hardware 102. This component may have ports or slots to receive and secure the cards 110, 112 to the main board 108. Other configurations may “hardwire” the second card 112 to the main board 108, as desired. On the other hand, the slots may allow the first card 110 to insert into and remove from the board-level assembly 106. This feature allows the main board 108 to accept different ones of the first card 110, essentially where a first one of the card 110 swaps out of the slot in favor of a second one of the card 110. The second one may configure the main board 108 with functions different than the first one, for example, functions that support data in a protocol (or language) that is different from the protocol (or language) supported by the first one.
Topology for board 108 and cards 110, 112 may vary as necessary to achieve its relevant functions. Generally, the topology may include a substrate, preferably one or more printed circuit boards (PCB) with interconnects of varying designs, although flexible printed circuit boards, flexible circuits, ceramic-based substrates, and silicon-based substrates may also suffice. For purposes of example, a collection of discrete electrical components may be disposed on the substrate, effectively forming circuits or circuitry to execute functions on the hardware 102. Examples of discrete electrical components include transistors, resistors, and capacitors, as well as more complex analog and digital processing components (e.g., processors, storage memory, converters, etc.). This disclosure does not, however, foreclose use of solid-state devices and semiconductor devices, as well as full-function chips or chip-on-chip, chip-on-board, system-on chip, and like designs.
The signals 114, 116 may be configured to convey data. This data may include information pertinent to operation of the device 102. For utility meters, the information may define operating parameters (e.g., pressure, temperature, flow, etc.), or “telemetry data,” often that relates to how material transits through the device 102. An end user can leverage telemetry data to confirm operation of the device 102 or troubleshoot problems to provide accurate maintenance in the field. On process devices, like a valve or actuator, the operating parameters may define set point, pressure, or position of a part, typically a result of a sensor or other feedback device.
The translator unit 124 may make the functional board 100 compatible with the second protocol (I2, O2). Executable instructions may embody steps, processes, or functions, for example, that configure the processor 128 to convert incoming data (I) and outgoing data (O) from a first protocol (I1, O1) to a second protocol (I2, O2), and vice versa. Examples of the first protocol (I1, O1) or “native” language may facilitate data exchange between the cards 110, 112 and, possibly, find use for other communications throughout the main board 108. In one implementation, the first protocol (I1, O1) may embody Constrained Application Protocol (“CoAP”), although other types and standards may fit the concepts here as well. The second protocol (I2, O2) preferably allows data exchange to occur with the off-board device 104 (or, more generally, may comport with requirements of an end user or a target). Some applications may integrate the off-board device 104 as the controller in the control system (noted above). This controller “talks” with the hardware 102 to control its operating functions (for example, to cause an actuator or valve to move). In this setting, the second protocol (I2, O2) may embody an “industrial automation protocol,” like MODBUS, PROFIBUS, FOUNDATION Fieldbus, or HART. Protocols like this may serve or function as base-level networking protocols for factory automation. This disclosure also contemplates use of other protocols, e.g., OPC, that define interoperability among devices in the industrial automation space. For wireless data exchange, the second protocol (I2, O2) may embody cellular or WiFi protocols, although the design may also benefit from use of shorter-range protocols, like near-field communications (NFC), Zigbee, or Bluetooth, as well.
In light of the foregoing discussion, the improvements herein can make industrial hardware much more flexible to accommodate different applications. The embodiments may reduce costs as less time is spent to design (or re-design) circuitry that permits industrial hardware, like utility meters, valves, or actuators, to communicate with other devices. The concepts also allow manufacturers (and operators) to re-purpose such hardware more easily and without delays that often accompany safety certification of new designs. Likewise, these manufacturers can reduce inventory or other overhead because changes from model to model require only one replaceable part, essentially a replaceable “translator” card that inserts and removes from the underlying functional board to adapt the industrial hardware to communicate on different control systems, computing devices, or like end user preferred modality to exchange data. This replaceable “translator” car is configured with hardware and software (or executable instructions) to convert between data protocols. A technical effect is to outfit the hardware in a way to make hardware compatible to exchange data with different devices or control systems.
Computing components (e.g., memory and processor) can embody hardware that incorporates with other hardware (e.g., circuitry) to form a unitary and/or monolithic unit devised to execute computer programs and/or executable instructions (e.g., in the form of firmware and software). As noted herein, exemplary circuits of this type include discrete elements such as resistors, transistors, diodes, switches, and capacitors. Examples of a processor include microprocessors and other logic devices such as field programmable gate arrays (“FPGAs”) and application specific integrated circuits (“ASICs”). Memory includes volatile and non-volatile memory and can store executable instructions in the form of and/or including software (or firmware) instructions and configuration settings. Although all of the discrete elements, circuits, and devices function individually in a manner that is generally understood by those artisans that have ordinary skill in the electrical arts, it is their combination and integration into functional electrical groups and circuits that generally provide for the concepts that are disclosed and described herein.
This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to practice the invention, including making and using any devices or systems and performing any incorporated methods. An element or function recited in the singular and proceeded with the word “a” or “an” should be understood as not excluding plural said elements or functions, unless such exclusion is explicitly recited. References to “one embodiment” of the claimed invention should not be interpreted as excluding the existence of additional embodiments that also incorporate the recited features. Furthermore, the claims are but some examples that define the patentable scope of the invention. This scope may include and contemplate other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal language of the claims.
Examples appear below that include certain elements or clauses one or more of which may be combined with other elements and clauses to describe embodiments contemplated within the scope and spirit of this disclosure.
This application claims the benefit of U.S. Provisional Ser. No. 62/490,372, filed on Apr. 26, 2017, and entitled UNIVERSAL CONTROLLER, the content of which is incorporated herein by reference in its entirety.
Number | Date | Country | |
---|---|---|---|
62490372 | Apr 2017 | US |