OUTPUT MODULES

CROSS-REFERENCE TO RELATED APPLICATION AND PRIORITY CLAIM

[0001] This application claims priority under 35 U.S.C. § 119(e) to U.S.

Provisional Patent Application No. 62/350,795 filed on June 16, 2016. This provisional patent application is hereby incorporated by reference in its entirety into this disclosure.

TECHNICAL FIELD

[0002] This disclosure relates generally to diagnostics for devices in industrial process control and automation systems or other systems. More specifically, this disclosure relates to device diagnostics based on signals from digital outputs.

BACKGROUND

[0003] Industrial process control and automation systems are often used to automate and operate large and complex industrial processes. These types of systems routinely include sensors, actuators, and other field devices mat can measure, adjust, or otherwise monitor or interact with one or more industrial processes. Diagnostic information related to field devices can be very useful in an industrial control and automation environment or other environment, such as to detect abnormal or faulty operation of field devices. Some field devices support the use of one or more digital outputs, each of which can provide a digital output signal. Conventionally, digital outputs come with only basic diagnostic capabilities, such as the ability to detect open-circuit and short-circuit conditions.

SUMMARY

[0004] This disclosure provides device diagnostics based on signals from digital outputs.

[0005] ID a first embodiment, a method is provided. The method includes measuring one or more characteristics of a digital signal provided by a digital output module, the digital output module coupled to a device, at least one of ^* the one or more characteristics of the digital signal associated with an output current of the digital output module. The method further includes performing one or more diagnostics using the one or more measured characteristics of the digital signal.

[0006] In a second embodiment, an apparatus is provided. The apparatus includes an input/output module with a digital output module configured to be coupled to a device. The input/output module is configured to measure one or more characteristics of a digital signal provided by the digital output module, where at least one of the one or more characteristics of the digital signal is associated with an output current of the digital output module. The input/output module is also configured to perform one or more diagnostics using the one or more measured characteristics of the digital signal.

[0007] In a third embodiment, a non-transitory machine-readable medium is provided. The non-transitory machine-readable medium is encoded with executable instructions that, when executed, cause one or more processors to measure one or more characteristics of a digital signal provided by me digital output mo^

one of the one or more characteristics of the digital signal associated with an output current of the digital output module and perform one or more diagnostics using the one or more measured characteristics of the digital signal.

[0008] Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] For a more complete understanding of mis disclosure, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

[0010] FIGURE 1 illustrates an example industrial process control and automation system according to mis disclosure;

[0011] FIGURE 2 illustrates an example digital output module for a device according to this disclosure;

[0012] FIGURE 3 illustrates a specific example of a universal input/output (UIO) module supporting device diagnostics according to mis disclosure;

[0013] FIGURES 4 and 5 illustrate example types of diagnostics mat can be performed for a device using a digital output according to mis disclosure;

[0014] FIGURE 6 illustrates an example system for device diagnostics using a digital output according to mis disclosure;

[0015] FIGURE 7 illustrates a process for performing device diagnostics from signals on digital outputs according to mis disclosure; and

[0016] FIGURES 8, 9 and 10 illustrate example processes for performing digital output current diagnostics according to this disclosure.

DETAILED DESCRIPTION

[0017] FIGURES 1 through 10, discussed below, and the various embodiments used to describe the principles of the present invention in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the invention. Those skilled in the art will understand mat the principles of the invention may be implemented in any type of suitably arranged device or system

[0018] As described above, conventional digital outputs are often provided with only basic diagnostic capabilities, such as the ability to detect open-circuit and short- circuit conditions. This disclosure describes more advanced diagnostics for output devices such as solenoids, actuators, and relays that can be provided using digital outputs. For example, this disclosure can make use of the capabilities of a universal input/output (UIO) module or other reconfigurable input/output module to provide advanced diagnostics by measuring and characterizing digital output currents.

[0019] FIGURE 1 illustrates an example industrial process control and automation system 100 according to this disclosure. As shown in FIGURE 1, the system 100 includes various components that facilitate production or processing of at least one product or other material. For instance, the system 100 is used here to facilitate control over components in one or multiple plants lOla-lOln. Each plant lOla-lOln represents one or more processing facilities (or one or more portions thereof), such as one or more manufacturing facilities for producing at least one product or other material. In general, each plant lOla-lOln may implement one or more processes and can individually or collectively be referred to as a process system A process system generally represents any system or portion thereof configured to process one or more products or other materials in some manner.

[0020] In FIGURE 1, the system 100 is implemented using the Purdue model of process control. In the Purdue model, "Level 0" may include one or more sensors 102a and one or more actuators 102b. The sensors 102a and actuators 102b represent components in a process system that may perform any of a wide variety of functions. For example, the sensors 102a could measure a wide variety of characteristics in the process system, such as temperature, pressure, or flow rate. Also, the actuators 102b could alter a wide variety of characteristics in the process system The sensors 102a and actuators 102b could represent any other or additional components in any suitable process system Each of the sensors 102a includes any suitable structure for measuring one or more characteristics in a process system Each of the actuators 102b includes any suitable structure for operating on or affecting one or more conditions in a process system

[0021] One or more networks 104 are coupled to the sensors 102a and actuators 102b. The network 104 facilitates interaction with the sensors 102a and actuators 102b. For example, the network 104 could transport measurement data from the sensors 102a and provide control signals to the actuators 102b. The network 104 could represent any suitable network or combination of networks. As particular examples, the network 104 could represent an Ethernet network, an electrical signal network (such as a HART or FOUNDATION FTELDBUS network), a pneumatic control signal network, or any other or additional type(s) of networks).

[0022] In the Purdue model, "Level 1" includes one or more controllers 106, which are coupled to the network 104. Among other things, each controller 106 may use the measurements from one or more sensors 102a to control the operation of one or more actuators 102b. Each controller 106 includes any suitable structure for controlling one or more aspects of a process system As a particular example, each controller 106 could represent a computing device running a real-time operating system

[0023] Redundant networks 108 are coupled to the controllers 106. The networks 108 facilitate interaction with the controllers 106, such as by transporting data to and from the controllers 106. The networks 108 could represent any suitable redundant networks. As particular examples, the networks 108 could represent a pair of Ethernet networks or a redundant pair of Ethernet networks, such as a FAULT TOLERANT ETHERNET (FTE) network from HONEYWELL INTERNATIONAL INC.

[0024] At least one switch/firewall 110 couples the networks 108 to two networks 112. The switch/firewall 110 may transport traffic from one network to another. The switch/firewall 110 may also block traffic on one network from reaching another network. The switch/firewall 110 includes any suitable structure for providing communication between networks, such as a HONEYWELL CONTROL FIREWALL (CF9) device. The networks 112 could represent any suitable networks, such as a pair of Ethernet networks or an FTE network.

[0025] In the Purdue model, "Level 2" may include one or more machine-level controllers 114 coupled to the networks 112. The machine-level controllers 114 perform various functions to support the operation and control of the controllers 106, sensors 102a, and actuators 102b, which could be associated with a particular piece of industrial equipment (such as a boiler or other machine). For example, the machine-level controllers 114 could log information collected or generated by the controllers 106, such as measurement data from the sensors 102a or control signals for the actuators 102b. The machine-level controllers 114 could also execute applications mat control the operation of the controllers 106, thereby controlling the operation of the actuators 102b. In addition, the machine-level controllers 114 could provide secure access to the controllers 106. Each of the machine-level controllers 114 includes any suitable structure for providing access to, control of, or operations related to a machine or other individual piece of equipment. Each of the machine-level controllers 114 could, for example, represent a server computing device running a MICROSOFT WINDOWS operating system. Although not shown, different machine-level controllers 114 could be used to control different pieces of equipment in a process system (where each piece of equipment is associated with one or more controllers 106, sensors 102a, and actuators 102b).

[0026] One or more operator stations 116 are coupled to the networks 112. The operator stations 116 represent computing or communication devices providing user access to the machine-level controllers 114, which could then provide user access to the controllers 106 (and possibly the sensors 102a and actuators 102b). As particular examples, the operator stations 116 could allow users to review the operational history of the sensors 102a and actuators 102b using information collected by the controllers 106 and/or the machine-level controllers 114. The operator stations 116 could also allow the users to adjust the operation of the sensors 102a, actuators 102b, controllers 106, or machine-level controllers 114. In addition, the operator stations 116 could receive and display warnings, alerts, or other messages or displays generated by the controllers 106 or the machine-level controllers 114. Each of the operator stations 116 includes any suitable structure for supporting user access and control of one or more components in the system 100. Each of the operator stations 116 could, for example, represent a computing device running a MICROSOFT WINDOWS operating system

[0027] At least one router/firewall 118 couples the networks 112 to two networks

120. The router/firewall 118 includes any suitable structure for providing communication between networks, such as a secure router or combination router/firewall. The networks 120 could represent any suitable networks, such as a pair of Ethernet networks or an FTE network.

[0028] In the Purdue model, "Level 3" may include one or more unit-level controllers 122 coupled to the networks 120. Each unit-level controller 122 is typically associated with a unit in a process system, which represents a collection of different machines operating together to implement at least part of a process. The unit-level controllers 122 perform various functions to support the operation and control of components in the lower levels. For example, the unit-level controllers 122 could log information collected or generated by the components in the lower levels, execute applications that control the components in the lower levels, and provide secure access to the components in the lower levels. Each of the unit-level controllers 122 includes any suitable structure for providing access to, control of, or operations related to one or more machines or other pieces of equipment in a process unit Each of the unit-level controllers 122 could, for example, represent a server computing device running a MICROSOFT WINDOWS operating system Although not shown, different unit-level controllers 122 could be used to control different units in a process system (where each unit is associated with one or more machine-level controllers 114, controllers 106, sensors 102a, and actuators 102b).

[0029] Access to the unit-level controllers 122 may be provided by one or more operator stations 124. Each of the operator stations 124 includes any suitable structure for supporting user access and control of one or more components in the system 100. Each of the operator stations 124 could, for example, represent a computing device running a MICROSOFT WINDOWS operating system.

[0030] At least one router/firewall 126 couples the networks 120 to two networks 128. The router/firewall 126 includes any suitable structure for providing communication between networks, such as a secure router or combination router/firewall. The networks 128 could represent any suitable networks, such as a pair ofEthemet networks or an FTE network.

[0031] In the Purdue model, "Level 4" may include one or more plant-level controllers 130 coupled to the networks 128. Each plant-level controller 130 is typically associated with one of the plants lOla-lOln, which may include one or more process units that implement the same, similar, or different processes. The plant-level controllers 130 perform various functions to support the operation and control of components in the lower levels. As particular examples, the plant-level controller 130 could execute one or more manufacturing execution system (MES) applications, scheduling applications, or other or additional plant or process control applications. Each of the plant-level controllers 130 includes any suitable structure for providing access to, control of, or operations related to one or more process units in a process plant Each of the plant-level controllers 130 could, for example, represent a server computing device running a MICROSOFT WINDOWS operating system.

[0032] Access to the plant-level controllers 130 may be provided by one or more operator stations 132. Each of the operator stations 132 includes any suitable structure for supporting user access and control of one or more components in the system 100. Each of the operator stations 132 could, for example, represent a computing device running a MICROSOFT WINDOWS operating system.

[0033] At least one router/firewall 134 couples the networks 128 to one or more networks 136. The router/firewall 134 includes any suitable structure for providing communication between networks, such as a secure router or combination router/firewall. The network 136 could represent any suitable network, such as an enterprise- wide Ethernet or other network or all or a portion of a larger network (such as the Internet).

[0034] In the Purdue model, "Level 5" may include one or more enterprise-level controllers 138 coupled to the network 136. Each enterprise-level controller 138 is typically able to perform planning operations for multiple plants lOla-lOln and to control various aspects of the plants lOla-lOln. The enterprise-level controllers 138 can also perform various functions to support the operation and control of components in the plants lOla-lOla As particular examples, the enterprise-level controller 138 could execute one or more order processing applications, enterprise resource planning (ERP) applications, advanced planning and scheduling (APS) applications, or any other or additional enterprise control applications. Each of the enterprise-level controllers 138 includes any suitable structure for providing access to, control of, or operations related to the control of one or more plants. Each of the enterprise-level controllers 138 could, for example, represent a server computing device running a MICROSOFT WINDOWS operating system In this document, the term "enterprise" refers to an organization having one or more plants or other processing facilities to be managed. Note that if a single plant 101a is to be managed, the functionality of the enterprise-level controller 138 could be incorporated into the plant-level controller 130.

[0035] Access to the enterprise-level controllers 138 may be provided by one or more operator stations 140. Each of the operator stations 140 includes any suitable structure for supporting user access and control of one or more components in the system 100. Each of the operator stations 140 could, for example, represent a computing device running a MICROSOFT WINDOWS operating system.

[0036] A historian 142 is also coupled to the network 136 in this example. The historian 142 could represent a component mat stores various information about the system 100. The historian 142 could, for example, store information used during production scheduling and optimization. The historian 142 represents any suitable structure for storing and facilitating retrieval of information. Although shown as a single centralized component coupled to the network 136, the historian 142 could be located elsewhere in the system 100, or multiple historians could be distributed in different locations in the system 100.

[0037] One or more devices shown in FIGURE 1 could support the use of one or more digital output modules. A digital output module denotes a structure configured to provide a digital output signal. For example, one or more actuators 102b or other field devices could include digital output modules that are used to output digital signals. As described below, the output signals from digital output modules can be used to provide more advanced diagnostics for field devices. In particular embodiments, the one or more digital output modules that support more advanced diagnostics are incorporated into one or more UIO modules. UIO modules allow one or more input/output (I/O) modules to be selectively configured and reconfigured, such as by allowing each I/O module to be configured as an analog input, an analog output, a digital input, or a digital output (among other options). This type of functionality provides various benefits, such as the ability to support late I/O binding and to reduce or eliminate the need for marshalling. The ability to provide advanced device diagnostics for I/O modules configured as digital outputs provides an additional benefit

[0038] The ability to provide more advanced device diagnostics can be useful in various ways. For example, more advanced device diagnostics could be used to provide early or earlier warnings of potential field device failures. This may allow maintenance to occur sooner, potentially before a field device failure actually occurs. This can result in improved maintenance and reduced down-time of an industrial process or other system, with associated monetary savings.

[0039] Although FIGURE 1 illustrates one example of an industrial process control and automation system 100, various changes may be made to FIGURE 1. For example, industrial control and automation systems come in a wide variety of configurations. The system 100 shown in FIGURE 1 is meant to illustrate one example operational environment in which device diagnostics based on signals from digital outputs may be needed or desired. However, FIGURE 1 does not limit mis disclosure to any particular configuration or operational environment In general, the approaches for providing device diagnostics based on signals from digital outputs can be used in any suitable system, and that system need not relate to industrial process control or automation.

[0040] FIGURE 2 illustrates an example system 200 with a programmable logic controller (PLC) or other type of controller 205 and a digital output module 210 for a device according to this disclosure. The digital output module 210 contains an output switch circuit 215 for each channel to control a load 220. The digital output module 210 is also associated with readback and diagnostic circuitry to report output drive failures and field cable failures. The output switch circuit 215 includes an output 230 connected to the load 220, and a common port 235 connected to a battery 225. The architecture depicted in FIGURE 2 can perform basic diagnostics, such as field cable open detection, short-circuit detection, and readback failure detection. However, the ability to measure the output current from the digital output module 210 allows various output device diagnostics that are more advanced to occur. These diagnostics could include, for example, the ability to monitor the health of actuators, solenoids, relays, motor starters, and lamps.

[0041] FIGURE 3 illustrates a specific example of a UIO module 300 supporting device diagnostics according to this disclosure. The implementation of the UIO module 300 shown in FIGURE 3 represents one specific example of a module containing a digital output that can be used for device diagnostics. However, this disclosure is not limited to use with this specific UIO module 300, and other UIO or I/O modules could be used. [0042] The UIO module 300 includes analog-to-digital converter (ADC) 306, an amplifier 308, a digital sense resistor 310, a digital output switch 312, a user connected load 314, and a pair of terminals 316. The terminals 316 are connected to a device for monitoring a digital output value,

[0043] The UIO module 300 here has the ability to read back a digital output current through the ADC 306. This type of readback is not performed in conventional designs for digital outputs since it would increase the cost and complexity of the module. The digital current is read back as a voltage across the digital sense resistor 310 shown in FIGURE 3.

[0044] The UIO module 300 can include or be connected to a CPU 304 and a memory 302. The CPU 304 can transmit a signal 318 to the digital output device. The CPU 304 also can receive a readback voltage 320 from the UIO module 300 to perform diagnostics on the signal. The CPU 304 can perform external communication 322 with different external device or alarms. A controller or a PLC sends commands to the UIO module 300 to turn ON/OFF multiple digital output channels, which are received by the CPU 304. The CPU 304 commands the digital output switch 312 to turn the channels on or off The UIO module 300 performs these actions continuously keeping the states of the digital output channels at the latest values. In addition, the CPU 304 continuously reads the conversions performed on the ADC 306 and stores these conversion results in the memory 302. The amplifier 308 amplifies the signal from the digital output control switch 312 to the ADC 306.

[0045] The readback value of the digital current is obtained by sensing the digital current using the low value digital sense resistor 310 in the current path. This low value resistance generates a voltage that is fed to the ADC 306 and sampled by the CPU 304, which is connected to the ADC 306. The ADC 306 is sampled at a rate used to characterize all the diagnostics that are targeted for a specific load.

[0046] The measured digital current can represent a valuable indicator of the health of an industrial process control and automation field device or other device. A number of diagnostics can be built around the health of discrete output devices.

[0047] FIGURES 4 and 5 illustrate example types of diagnostics 400 and 500 mat can be performed for a device using a digital output according to this disclosure. FIGURE 4 illustrates an example output over-current or under-current diagnostic 400. The diagnostic 400 monitors the load current 405 of the digital output This diagnostic can generate a warning or other notification if the actual output load current 420 of a digital output module violates an undercurrent limit 410 or overcurrent limit 41S. This diagnostic 400 can also identify whether the output current drifts over a period of time. FIGURE 5 illustrates an example output current variation diagnostic 500. The diagnostic 500 also monitors the load current SOS with a different focus. This diagnostic 500 can warn of unusual changes S20 in an output current draw SIS, which could be an early warning of an output device short-circuit or open-circuit condition For example, the unusual changes can occur when the output current draw 515 is trending away from a nominal current level 510.

[0048] In addition to these types of diagnostics, other or additional types of diagnostics could be designed around specific output devices by monitoring digital output current parameters (such as DC value, rate of change, amount of on-time, or amount of off-time). Some examples of device-specific diagnostics could include actuator diagnostics, solenoid diagnostics, relay diagnostics, motor starter current diagnostics, and lamp health diagnostics.

[0049] FIGURE 6 illustrates an example system 600 for device diagnostics using a digital output according to this disclosure. In this example, a user can be provided with the feedback digital current values. This could allow, for example, the user to develop custom diagnostics for specific field output devices 605. The illustrative system 600 includes afield output device 605, a digital output module 610, a controller 61S, a digital output channel 620, and an output device diagnostic algorithm 625.

[0050] The digital output module 610 connects to the field output device 605 to monitor the digital outputs. The digital output module 610 receives output 630 from the controller 615. The digital output module 610 analyses the data and can provide readback 63S, live monitoring status 640, digital current 645, and advanced diagnostics 6S0 to the controller 615. The digital output channel 620 receives an output 655 and provides a digital current 660 to the output device diagnostic algorithm 625. The output device diagnostic algorithm 625 outputs advanced diagnostics 665.

[0051] Additional details regarding specific implementations of a UIO module that could be used in this disclosure are provided in U.S. Patent No. 8,656,065. Other example implementations of a UIO module that could be used in this disclosure are provided in U.S. Patent No. 8,072,098. UIO modules supporting UNIVERSAL CHANNEL TECHNOLOGY from HONEYWELL INTERNATIONAL INC. are also suitable for use with mis disclosure.

[0052] Although FIGURES 2 through 6 illustrate examples of digital output modules, UIO modules, diagnostics, and systems, these figures are for illustration only. For example, any suitable digital output modules or UIO or reconfigurable modules could be used to provide advanced device diagnostics. Also, the specific diagnostics performed could vary widely, such as based on the type of device coupled to a digital output module or UIO module. In addition, any suitable process could be performed using diagnostics associated with a digital output module or UIO module.

[0053] FIGURE 7 illustrates a process 700 for performing device diagnostics from signals on digital outputs according to mis disclosure. For example the process 700 depicted in FIGURE 7 may be performed by the UIO module 300.

[0054] In step 705, the UIO module 300 determines whether anew digital output value is to be driven. In step 710, when the determination that a new digital output value is required, the UIO module 300 drives a new digital output value. In step 715, the UIO module 300 sample a digital output current from the ADC. In step 720, the UIO module 300 performs diagnostics on the digital output current Example of digital output current diagnostics are provided in FIGURE 8-10. The continuous time series of the readback current enables performance of diagnostics exemplified by FIGURES 8-10.

[0055] FIGURES 8, 9 and 10 illustrate example processes for performing digital output current diagnostics according to this disclosure. For example, the processes depicted in FIGURES 8-10 may be performed by the UIO module 300.

[0056] FIGURE 8 illustrates an example process 800 for digital current crossing an upper or lower threshold indicating a degrading load, which is illustrated in FIGURE 5. In step 805, the UIO module 300 determines whether the digital output current is above a high limit or upper threshold value. In step 815, when the digital output current is not above the high limit, the UIO module 300 determines whether the digital output current is below a low limit or a lower threshold value. The UIO module 300 indicates an overcurrent error in step 810 when the digital output current is above the high limit and indicates an low current error in step 820 when the digital output current is below the low limit If neither limit is crossed and no error is indicated, the UIO module 300 indicates that the digital output has no error in step 825.

[0057] FIGURE 9 illustrates an example process 900 for analysis of a step response to determine the impedance of the load. This test enables a determination whether the impedance of the load is changing over time and a threshold limit for failure has been readied. In step 905, the UIO module 300 determines whether a digital output state is changed. If the digital output state has not changed, the UIO module 300 determines whether a sample collection is complete in step 920. When the digital output state has changed or the sample collection is not complete, the UIO module 300 stores the digital output current sample in step 910 and determines that test results are still pending in step 915. When the sample collection is complete, the UIO module 300 calculates an impedance based on the step response current sample in step 925. In step 930, the UIO module 300 determines whether the impedance is deviating from the configured threshold. When the impedance is not deviating from the configured threshold, the UIO module 300 determines that the test has been passed in step 935. When the impedance is deviating from the configured threshold, the UIO module 300 determines that the impedance test has failed in step 940.

[0058] FIGURE 10 illustrates an example process 1000 for checking whether there are excessively noisy conditions near the load or if the load is experiencing degradation and causing varying current to be drawn. In step 1005, the UIO module 300 determines whether the digital output state is "ON." If the digital output state is not "ON," the test in not performed in step 1010. When the digital output state is 'ON," the UIO module 300 stores the digital output current sample in step 1015. In step 1020, the UIO module 300 determines whether the sample collection is complete. If the sample collection is not complete, the UIO module 300 indicates that the test results are still pending in step 1025. If the sample collection is complete, the UIO module 300 determines a variation of the current from the samples in step 1030. In step 103S, the UIO module 300 determines whether a detected variation deviates from the configured threshold. If the variation deviates from the threshold, the UIO module 300 indicates that the variation test failed in step 1045. If the variation does not deviate from the threshold, the UIO module 300 indicates that the variation test has passed in step 1040.

[0059] Although FIGURES 7-10 illustrate examples of processes for performing device diagnostics from signals on digital outputs, respectively, various changes could be made to FIGURE 7-10. For example, while shown as a series of steps, various steps in each figure could overlap, occur in parallel, occur in a different order, or occur multiple times. In the figures, "DO" stands for "digital output," "10" stands for "input/output," "PLC stands for "programmable logic controller," "ADC" stands for "analog-to-digital converter," and stands for a "reference voltage used for analog-to-digital conversions." A step response is the output response of a system when a step input is applied at the input of the system. The impedance is the combined effect of the resistance and reactance of a load. Sample refers to reading the instantaneous value of a physical parameter.

[0060] In some embodiments, various functions described in this patent document 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 storage device.

[0061] It may be advantageous to set forth definitions of certain words and phrases used throughout this patent document 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 term "communicate," as well as derivatives thereof, encompasses 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.

[0062] The description in the present application should not be read as implying that any particular element, step, or function is an essential or critical element mat must be included in the claim scope. The scope of patented subject matter is defined only by the allowed claims. Moreover, none of the claims invokes 35 U.S.C. § 112(f) with respect to any of the appended claims or claim elements unless the exact words "means for" or "step for" are explicitly used in the particular claim, followed by a participle phrase identifying a function. Use of terms such as (but not limited to) "mechanism," "module," "device," "unit," "component," "element," "member," "apparatus," "machine," "system," "processor," or "controller" within a claim is understood and intended to refer to structures known to those skilled in the relevant art, as further modified or enhanced by the features of the claims themselves, and is not intended to invoke 35 U.S.C. § 112(f).

[0063] 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.