Patent Description:
The subj ect matter of this disclosure relates to improvements to include a "smart" power supply into metrology hardware as defined in claim <NUM>. Of particular interest are embodiments with electronics that can cooperate with the "smart" power supply to exchange data. This feature may allow the device to perform diagnostics and related functions pertinent to the power supply. The results may, in turn, be useful for the device to generate alerts, modify component operations, or ensure that maintenance occurs at appropriate times or on schedule to avoid any disruptions that may prevail due to issues with the power supply or with the device itself. The scope of protection is conferred by the set of claims, as defined by independent hardware claim <NUM> and independent method claim <NUM>, respectively.

Reference is now made briefly to the accompanying figures, 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 metrology hardware with an on-board, "smart" power supply. Reference is made throughout to the metrology hardware as a gas meter, but the concepts may apply elsewhere as well. As noted below, the "smart" power supply incorporates technology that permits on-board data collection and analysis, particularly as relates to energy storage cells, namely batteries, found on the device. The gas meter includes a main control, which can exchange data with the "smart" power supply. The main control can process the data to schedule maintenance (to replace the power supply) or to identify more pressing problems that might disrupt operation of the gas meter in the field. Other embodiments are within the scope of the subject matter of this disclosure.

<FIG> depicts a schematic diagram of an exemplary embodiment of a power supply <NUM>. This embodiment is shown as part of metrology hardware <NUM>. For fuel gas distribution, metrology hardware <NUM> is often referred to as a "meter" or "gas meter. " Examples of the gas meter <NUM> includes a pair of measuring units (e.g., a flow responsive unit <NUM> and an electronics unit <NUM>). The flow responsive unit <NUM> may couple with a conduit <NUM> that carries material <NUM>, for example, fuel gas (used in the discussion that follows). Material <NUM> may also embody other fluids (e.g., liquids and gasses), although the device may work with solids and solid/fluid mixes as well. The electronics unit <NUM> includes a main controller <NUM>. In one implementation, the power supply <NUM> may include an energy source <NUM> that couples with circuitry <NUM>, which itself connects or couples with the main controller <NUM> to exchange signals (e.g., a first signal S<NUM> and a second signal S<NUM>). The signals S<NUM>, S<NUM> may correspond with power and data (e.g., current, voltage, etc.), respectively.

Use of the gas meter <NUM> may generate data that quantifies measured parameters for material <NUM>. For example, measuring units <NUM>, <NUM> may interact with one another to measure and quantify volumetric flow rate of the flow of material <NUM> in conduit <NUM>. The flow responsive unit <NUM> may include mechanics like impellers, turbines, and diaphragms that interact with the flow of material <NUM>. Alternative configurations may, however, leverage sensors (e.g., temperature sensors, pressure sensors, etc.) or technology (e.g., ultrasonic) that reside proximate flow of material <NUM>. These devices may generate signals in response to local characteristics of material <NUM>. The electronics unit <NUM> typically includes electronics to generate the value for the volumetric flow rate. Exemplary electronics may form some type of non-contact interface to translate movement of the mechanics (e.g., rotation of the impellers) into electrical signals. Other electronics may generate these signals from various processing functions of "sensor signals," noted above. In both cases, the resulting electronic signals may form the basis to bill customers for use of fuel gas.

The main controller <NUM> may be configured as part of the electronics in the electronics unit <NUM>. These configurations may include circuitry outfit to operate as the central "brains" of the gas meter <NUM>. This circuitry may be responsible for data processing functions that occur on the device. As noted above, these functions may generate the value for volumetric flow rate. Other functions may generate an output for display (on, for example, a screen) or for use in applications that invoice customers, as noted herein.

The energy source <NUM> is configured to provide power to operate the electronics unit <NUM>. These configurations may store and retain energy in one or more batteries or, more generally, energy storage "cells. " Discharge from the cells, as power signal S<NUM>, for example, may energize electronics, sensors, communication devices (e.g., wireless antenna), and various other functional devices on the electronics unit <NUM>. Multiple cells may benefit the design to avoid disruption in the power supply. Examples of batteries and cells may be rechargeable, which may prove useful to take advantage of energy generation or harvesting found at or proximate the gas meter <NUM>. This feature may further reduce maintenance needs at the gas meter <NUM>.

The circuitry <NUM> provides functionality for operations on the power supply <NUM>. Topology may leverage computing components (like processor(s) and memory) that can execute software programs to enable functions on the device. Predominantly, these functions regulate power draw or discharge (as the power signal S<NUM>) to the electronics unit <NUM>. Components may include circuits and bus structure to direct power from the cells individually or from more than one of the cells at a time, as desired. This feature may configure the power supply <NUM> to meet longevity requirements or power demands on the electronics unit <NUM>. In one implementation, the circuitry <NUM> may provide functions to enhance performance of the power supply <NUM>, either independently or in conjunction with functions on the main controller <NUM>, typically by facilitating bidirectional exchange of data (as the data signal S<NUM>). This "smart" technology may enable traceability, monitor performance of the cells, quantify power diagnostics for the gas meter <NUM>, and provide safety measures so the power supply <NUM> can work on the gas meter <NUM> in hazardous areas.

Traceability is useful to track data that reflects use of the power supply <NUM> or its components. This data may indicates connection or disconnection of the power supply <NUM> with the electronics unit <NUM>. It may prove useful to also register connection or disconnection of the cell or cells with the circuitry <NUM> as well. In this regard, the circuitry <NUM> may store information that uniquely identifies on or both of the cells (individually) or the power supply <NUM>. Examples of these "identifiers" may include serial numbers, cyclic redundancy check (CRC) numbers, check sum values, hash sum values, or the like. This information may embed into memory the circuitry <NUM> at the time of manufacture. Benefit may be had to write the information to memory that is configured to prevent changes or tampering, essentially "hardwiring" the identifiers (and other information) to the respective device.

Cell performance may track metrics to provide a picture of cell or source "health. " Generally, values for these metrics may relate to "output" parameters, like output voltage and output current from the cells. "Physical" parameters may relate to temperature or material properties of the cells. "Ambient" parameters may describe temperature, relative humidity, and pressure of the environment proximate the cells. Often the circuitry <NUM> may aggregate this information in memory, preferably on a rolling or real-time basis over time. The circuitry <NUM> may also process the information to generate data, as the data signal <NUM>. The electronics unit <NUM> may generate an output in response to the data signal S<NUM>, for example, that inform an end user (e.g., a technician) about the health of the power supply <NUM>. This feature may ensure that the power supply <NUM> continues to meet power demands or requirements for the electronics unit <NUM>.

Power diagnostics may track use or consumption of power at the electronics unit <NUM>. For example, the circuitry <NUM> may analyze power output from the power supply <NUM> to meet demand on the electronics unit <NUM>. This analysis may look for indicators (e.g., peaks and valleys) that describe abrupt changes in power consumption by the electronics unit <NUM>. The circuitry <NUM> may, in turn, generate the data signal S<NUM> with data to describe these indicators. The electronics unit <NUM> may associate the indicators to operational problems that require attention, but might not be readily apparent or traceable on or by the gas meter <NUM>.

Safety considerations may allow the gas meter <NUM> to meet standards of operation for hazardous areas. These standards may correspond with "intrinsically-safe circuit designs. " For example, the circuitry <NUM> may be effective to power or "energy" limit one or both of the signals S<NUM>, S<NUM>, preferably when the signals S<NUM>, S<NUM> enter areas of the gas meter <NUM> that are not explosion-proof. In one implementation, the circuitry <NUM> can ensure signals S<NUM>, S<NUM> are at low voltages and low currents to avoid sparks or arcing that could ignite or cause ignition of flammable fuel gas.

<FIG> depicts a schematic diagram of an example of base-level topology for components of the power supply <NUM> of <FIG>. The circuitry <NUM> may embody an operative circuit board <NUM>, preferably a substrate like a printed circuit board (PCB) or semiconductor device. The circuit board <NUM> may incorporate a bus structure <NUM> to exchange signals internal and external to circuitry <NUM>. The bus structure <NUM> may connect with electrical ports <NUM>, for example, to exchange signals S<NUM>, S<NUM> with the electronics unit <NUM>. Standard or proprietary communication buses including SPI, I<NUM>C, UNI/O, <NUM>-Wire may be useful for this purpose (or, even, one or more like serial computer buses known at the time of the present writing or developed hereinafter). The circuitry <NUM> may include a main processing circuit <NUM> having computing components like a processor <NUM> coupled with a storage memory <NUM> that stores data <NUM> thereon. Computing components <NUM>, <NUM> may integrate together as a microcontroller or reside separately as discrete components. Examples of the data <NUM> can include executable instructions (e.g., firmware, software, computer programs, etc.) and "information" about the device. The main processing circuit <NUM> may also have driver circuitry <NUM> that couples with the processor <NUM> and with other components to facilitate component-to-component communication. These components may include sensing circuitry <NUM>, timing circuitry <NUM>, measurement circuitry <NUM>, and output control circuitry <NUM>.

The main processing circuit <NUM> may be configured to operate the power supply <NUM>. This device may have functionality to process signals (like data signal S<NUM>) from the main controller <NUM>, preferably in digital format. Other functionality can generate the data signal S<NUM> or other operative outgoing signals, such as those used to instruct operation of other components, like the output control circuitry <NUM>. Data processing functions may be important to process signals (e.g., the data signal S<NUM>) that originate from the main controller <NUM>. These "incoming" data signals may include data, possibly in the form of instructions or like information that is pertinent to or can influence the functionality of power supply <NUM>.

The sensing circuitry <NUM> may be configured to provide data that defines parameters on the power supply <NUM>. These configurations may include one or more sensing elements or probes that, effectively, generate signals in response to stimuli. Examples include thermistors, thermocouples, transducers, piezo-resistive gauges, and like devices. These devices may disperse on or in proximity to the source <NUM>, as well as in other on-board locations that may provide data relevant to operation of the power supply <NUM>.

The timing circuitry <NUM> may be configured to maintain time to synchronize measurements or calculations on the power supply <NUM>. These configurations may operate as a real-time clock that integrates as an "integrated circuit" into circuitry <NUM>. Generally, this integrated circuit may embody a micro-power chip with an oscillator that counts time. The chip may couple with its own power supply, often a lithium battery with extensive lifespan (e.g., > <NUM> years). A counter may couple with the oscillator. The counter processes signals from the oscillator to output time increments, preferably at accuracy that comports with national standard clocks.

The measurement circuitry <NUM> may be configured to measure performance of the power supply <NUM> and its cells. These configurations may embody circuitry responsive to voltage or current fluctuations. This circuitry may include a sensor, for example, a resistor. Other components may generate a signal that reflects voltage drop across the resistor. The main processing circuit <NUM> may use this signal to evaluate performance, as desired.

The output control circuitry <NUM> may be configured to regulate the power signal S<NUM> upstream of the electronics unit <NUM>. These configurations may include circuits that interpose between the source <NUM> and the electrical ports <NUM>. Signals from the main processing circuit <NUM> may instruct operation of these circuits to allow or prevent the power signal S<NUM> at the electrical ports <NUM>.

<FIG> depicts an example of the topology of <FIG> with an example of the source <NUM>. This example has a cell network <NUM> with ports <NUM> to receive energy storage cells <NUM> therein. Construction of the ports <NUM> may provide appropriate electrical connections to receive power (e.g., current, voltage, etc.) from the cells <NUM>. These connections may embody "pluggable" sockets with conductive pins or receptacle for the same. Complimentary connectors on the cells <NUM> may, in turn, allow the cells <NUM> to readily remove and replace from the cell network <NUM>. This feature can simply manufacture and service in the field. As shown, the ports <NUM> may couple with a power distribution circuit <NUM>, itself coupled with driver circuitry <NUM> of the main processing circuit <NUM> and with the measurement circuitry <NUM>. The power distribution circuit <NUM> may connect the ports <NUM> to a central output <NUM>. This feature may couple the ports <NUM> with the measurement circuitry <NUM> and, in turn, with electrical ports <NUM>. In use, the circuit <NUM> may be able to couple the ports <NUM> to the central output <NUM>, either individually or in groups. Appropriate section or combination of the cells <NUM> may correspond with instructions from the main processing circuit <NUM>, possibly in response to demand (or changes thereof) at the electronics unit <NUM>.

<FIG> depicts the topology of <FIG> with an example of the power distribution circuit <NUM>. This example includes switchable circuits <NUM>, one each coupled with the ports <NUM>. The switchable circuits <NUM> includes switches <NUM> and measurement sub-circuits <NUM>. In one implementation, the sub-circuits <NUM> generates signals <NUM> that reflect operating parameters for the cells <NUM>, individually. The main processing circuit <NUM> may use the signals <NUM> to monitor the cells <NUM> for performance issues or to maintain other metrics as desired.

<FIG> depicts a schematic diagram of topology for an example of the output control circuitry <NUM>. This example includes a switch <NUM> and a barrier circuit <NUM>. The switch <NUM> may couple with the driver circuitry <NUM>. The barrier circuit <NUM> may be configured to couple with the electric ports <NUM>, typically a two-wire interface that "exits" the circuit board <NUM>. This configuration may include discrete devices (e.g., a fuse <NUM> and a resistor <NUM>). A diode device <NUM> couples the discrete devices <NUM>, <NUM> to a ground <NUM>. Examples of the diode device <NUM> may include one or more zener diodes, but other discrete devices may work as well. In operation, fault voltage across the barrier circuit <NUM> will cause current to flow across the diode device <NUM> to the ground <NUM>. The grounded current causes the fuse <NUM> to open, thus limiting current available to the electronics unit <NUM> via the electrical ports <NUM>.

<FIG> depicts a schematic diagram of an example of base-level topology for the gas meter <NUM> of <FIG>. This topology may benefit from a connective interface <NUM> that permits the power supply <NUM> to "replace" or "swap" out of the electronics unit <NUM>, as desired. The connective interface <NUM> may include a cable assembly <NUM> with conductive members (e.g., wires or cables) that terminate at connectors <NUM> on its ends. Examples of the connectors <NUM> may compliment connectors found on the electronics unit <NUM> and at the electrical ports <NUM> of the circuitry <NUM>. It is also possible that one of the ends of the conductive member is "hardwired" to respective circuitry on either of these devices. Techniques like direct soldering or wire bonding may be useful for this purpose. The main controller <NUM> may include various components including a processor <NUM> that couples with memory <NUM> that retains data <NUM> thereon. The device may also include driver circuitry <NUM>, which couples with a power connector <NUM>.

<FIG> depicts a perspective view of exemplary structure <NUM> for the gas meter <NUM> of <FIG>. The structure may include a meter body <NUM>, typically of cast or machined metals. The meter body <NUM> may form an internal pathway that terminates at openings <NUM> at flanged ends (e.g., a first flanged end <NUM> and a second flanged end <NUM>). The ends <NUM>, <NUM> may couple with complimentary features on a pipe or pipeline to locate the meter body <NUM> in-line with conduit <NUM> (<FIG>). As also shown, the meter body <NUM> may have a covers <NUM> disposed on opposing sides of the device. The covers <NUM> may provide access to the flowpath, where a pair of impellers resides so as to have access to the flow of material that passes through openings <NUM>. One of the coves <NUM> may feature a connection <NUM>, possibly flanged or prepared to interface with the electronics unit <NUM>. In this regard, the structure may include an index housing <NUM> having an end that couples with the connection <NUM>. The index housing <NUM> may comprise plastics, operating generally as an enclosure to contain and protect electronics including the power supply <NUM> and circuit board <NUM> (discussed above). The index housing <NUM> may support a display <NUM> and user actionable device <NUM>, the latter being used to interface with interior electronics to change the display <NUM> or other operative features of the device.

<FIG> illustrates a flow diagram of an exemplary embodiment of a method <NUM> for functionality on-board the power supply <NUM>. This diagram outlines stages that may embody executable instructions for one or more computer-implemented methods and/or programs. These executable instructions may be stored on the main processing circuit <NUM> as firmware or software. The stages in this embodiment can be altered, combined, omitted, and/or rearranged in some embodiments.

Operation of the method <NUM> may enable diagnostics on-board the power supply <NUM>. The method <NUM> may include, at stage <NUM>, receiving a "wake" input. The method <NUM> may also include, at stage <NUM>, performing diagnostics on the power supply. These diagnostics may include, at stage <NUM>, accessing operating parameter data and, at stage <NUM>, using the operating parameter data, calculating current charge on the cells. The diagnostics also includes, at stage <NUM>, setting a power consumption threshold level. The method <NUM> further includes, at stage <NUM>, receiving power discharge data and, at stage <NUM>, determining whether the discharge data exceeds the power consumption threshold level. The method <NUM> may also include, at stage <NUM>, generating an output to convey data that relates to the diagnostics (at stage <NUM>).

At stage <NUM>, the main processing circuit <NUM> may receive the input from the main controller <NUM> of the electronics unit <NUM>. This input may correspond to a signal (e.g., data signal S<NUM>) from the main controller <NUM>, possibly that originates in response to or at the time the power supply <NUM> connects with the electronics unit <NUM>. This signal may transmit data, information, or instructions that the main processing circuit <NUM> can process to set operation of the power supply <NUM>.

At stage <NUM>, the main processing circuit <NUM> may perform diagnostics that are useful to manage operation of the power supply <NUM> or the gas meter <NUM>, generally. The incoming signal from the main controller <NUM>, for example, may cause the main processing circuit <NUM> to perform some type of self-diagnostic functions. Examples of these functions may evaluate discharge (or "self-discharge") that occurs naturally in the device. This self-discharge may reduce overall stored energy (or "charge") on the device. In one implementation, the main processing circuit <NUM> can evaluate self-discharge from a date of manufacture to a date of installation into the electronics unit <NUM>. Other diagnostics may be useful to characterize power demands of the electronics unit <NUM>, as well.

At stage <NUM>, the main processing circuit <NUM> may access operating parameter data for purposes of discharge evaluation. This operating data may include values for temperature, relative humidity, and like ambient conditions that prevail at or proximate the power supply <NUM> or its internal components (e.g., cells, circuitry, etc.). In addition, the operating data may include a time value, for example, time spent in storage (e.g., "shelf-life") prior to use in the gas meter <NUM>. These values may be stored on memory <NUM> in a persisting database or like database structure. In this regard, the method <NUM> may include other stages for periodically sampling data from sensing circuitry <NUM> and writing the data to memory <NUM>. Practically, these stages would require little power from the cells when dormant as inventory.

At stage <NUM>, the main processing circuit <NUM> can calculate a value for the current charge on the cells. This value may correlate to a manufacturer "model" that is useful to accurately predict static discharge of the cells. Models of this type may correspond with particular types, models, or serial number of the cells found in the power supply <NUM>. It follows then that additional stages may be required to store and recall any appropriate look-up tables with data or other algorithms that will expedite the analysis of the cells. Notably, self-discharge will continue over the useable life of the cells. It follows, then, that diagnostics that relate to self-discharge may continue after the power supply <NUM> enters in to use on the electronics unit <NUM>. In this regard, the method <NUM> may includes stages to continue to perform stages <NUM>, <NUM> so as to maintain or update data to the main controller <NUM>. This data is beneficial so that the main controller <NUM> can revise, if necessary, its analysis and determination of the life expectancy of the power supply <NUM>. In turn, the main controller <NUM> can update maintenance scheduling to accelerate (or decelerate) the time schedule or time frame to replace the power supply <NUM>, thus avoiding the need to expend cost and time in labor to perform maintenance until it is necessary to maintain proper operation of the gas meter <NUM>.

At stage <NUM>, the main processing circuit <NUM> may set a value for the power consumption threshold level. This value may quantify the designed power consumption for the electronics unit <NUM>, which may be pre-determined and stored (or "hardwired") into the main controller <NUM> or the main processing circuit <NUM> of the power supply <NUM>. In operation, the design power consumption will set a threshold level of power that the electronics unit <NUM> is likely to draw under normal operating conditions.

At stage <NUM>, the main processing circuit <NUM> may receive data from the measurement circuitry <NUM>. The data may define discharge from the power supply, for example, as the power signal S<NUM>. This stage may include one or more stages for sampling the data from the measurement circuitry <NUM> and storing the data on memory <NUM>. But while real-time polling to create a continuous stream of data may be advantageous, this disclosure does contemplate that sampling may occur at pre-defined intervals to limit or reduce demand on data storage space. Also, it may benefit the main processing circuit <NUM> to "learn" the power consumption value. The method <NUM> may include stages, for example, to monitor, sample, and store data from the measurement circuitry <NUM> that reflects power demand by the electronics unit <NUM> over time. Additional stages for analysis of this data, like statistical analysis, arrives at the power consumption threshold level as an average or median based on in-field demands of the electronics unit <NUM>.

At stage <NUM>, the main processing circuit <NUM> may determine whether power demands have changed at the electronics unit <NUM>. Discharge values that exceed (or are below) the power consumption threshold level, for example, may indicate that demand has change to the detriment of operation of the electronics unit <NUM>. Failure of components on the electronics unit <NUM>, for example, may cause the electronics unit <NUM> to increase or decrease demand on the power supply.

At stage <NUM>, the main processing circuit <NUM> may generate signal S<NUM> to convey the value for the diagnostics to the main controller <NUM>. The signal S<NUM> may be in digital format, although analog may suffice as well. For some diagnostics, it may benefit the electronics unit <NUM> for the signal S<NUM> to convey an alert or indicator that relates to the specific diagnostic value (e.g., change in discharge/demand). The current charge, on the other hand, may best be conveyed by value so that the main controller <NUM> can perform appropriate operations. In one implementation, these operations may cause the case meter to enter into a safe mode or low power mode, that preserves energy to extend the life of the batteries until appropriate remediation occurs on the device.

<FIG> depicts a flow diagram of an example of the method <NUM> of <FIG> to include some of the operations that may prevail at the electronics unit <NUM>. The method <NUM> may include, for example, at stage <NUM>, receiving the output (e.g., signal S<NUM>), and at stage <NUM>, initiating self-corrective actions. These self-corrective actions may include, at stage <NUM>, using the current charge to determine the life span of the power supply or, at stage <NUM>, performing internal diagnostics that evaluate operation of system components. The method <NUM> may further include, at stage <NUM>, generating an output that transmits data remotely.

At stage <NUM>, the main controller <NUM> may receive data from the main processing circuit <NUM> on the power supply <NUM>. This data, as noted above, may include values for one of the operating characteristic above, or others as discussed or contemplated herein. Processing of the data may initiate functionality on the main controller <NUM>.

At stage <NUM>, the main controller <NUM> may take some self-corrective action. These actions may correspond with an evaluation of the operability of the power supply <NUM>. This evaluation may, in turn, qualify (or quantify) performance of the power supply <NUM>, for example, as relates to performance of the electronics unit <NUM>. Reductions in performance or perceived performance (like loss of charge) may cause the main controller <NUM> to move to a low power mode, for example, until appropriate changes occur at the power supply <NUM>.

At stage <NUM>, the main controller <NUM> may determine the life span of the power supply <NUM>. This stage may rely on data stored on-board that defines power requirements for the electronics unit <NUM>. This stage may also include stages for extrapolating life span based on, at least in part, the current charge the operative power requirements.

At stage <NUM>, the main controller <NUM> may perform internal diagnostics. These internal diagnostics may coincide with data from the power supply that shows operation deviates from the power demand threshold. This stage may include stages that can diagnose in-operative or improperly-operative components to identify the root cause of the change in power demand. In one implementation, the stages may include stages for limiting or ceasing operation of the gas meter <NUM> or flow of material <NUM> so as to avoid erroneous billing of the customer.

At stage <NUM>, the main controller <NUM> may generate the output remote from the device. This output may operate as an alert or like indicator that conveys information about operation of the electronics unit <NUM>. The information may inform the end user that issues prevail on the device, whether immediately detrimental to operation of the gas meter <NUM> or cause for concern or maintenance during it operative lifespan. For example, information may change potential maintenance scheduling to accelerate power supply <NUM> change over because the lifespan of the existing power supply <NUM> is shorter than the expected lifespan for the gas meter <NUM>.

<FIG> illustrates a flow diagram of an example of the method <NUM> of <FIG>. In this example, the method <NUM> may include, at stage <NUM>, detecting a change in state at a connection used to exchange data with a power supply and, at stage <NUM>, determining the state of the connection. If the connection is open, the method <NUM> may continue, at stage <NUM>, setting a fault condition and, at stage <NUM>, populating an event to an event log. The method <NUM> may also continue to detect the change at the connection (at stage <NUM>). If the connection is closed, the method <NUM> may continue, at stage <NUM>, with generating the wake input for the power supply as discussed in connection with <FIG> above. In one implementation, the method <NUM> may include one or more stages that relate to interaction by an end user (e.g., a technician) to perform maintenance, repair, upgrades, and assembly or like task to modify structure of a gas meter. These stages may include, at stage <NUM>, initiating a commissioning process on the gas meter and, at stage <NUM>, manipulating one or more power supplies on the gas meter.

At stage <NUM>, the electronics unit <NUM> detects the change in state at the connection. As noted above, the change may correspond with a signal from a "port" on the electronics unit <NUM>, possibly a connector or connecting device that connects the power supply <NUM> to the electronics unit <NUM>. The signal may correspond with a pin on the connector. Values for this signal may correspond with a high voltage and a low or zero voltage, one each to indicate that the pin on the connector is in use or not in use with respect to the connected hardware. The signal could also arise in response to updates in executable instructions on the metrology hardware. In one implementation, the electronics unit <NUM> may include one or more stages for initiating a "handshake" in response to the signal. This handshake may cause the main controller <NUM> to transmit data to the main processing circuit <NUM> on the power supply <NUM>. In return, the main processing circuit <NUM> may retrieve and transmit identifier data to the electronics unit <NUM>, as noted more below in connection with <FIG>.

At stage <NUM>, the electronics unit <NUM> determines the state of the connection. This stage may include one or more stages that compare the signal from the port to a look-up table or other threshold that indicates the state of the port. Open ports may indicate that hardware has been removed or is currently unavailable. On the other hand, closed ports may indicate that hardware is available to commence in situ commissioning process.

At stage <NUM>, the electronics unit <NUM> initiates the commissioning process. This stage may include one or more stages for receiving an input. Examples of the input may arise automatically, for example, based on a timer or other component internal to the metrology hardware that automatically polls the power supply <NUM>. In one implementation, the input may arise externally from a remote device (e.g., computer, laptop, tablet, smartphone) that connects with the gas meter <NUM>. This input may correspond with a technician plugging or unplugging the power supply <NUM> from the electronics unit <NUM> (at stage <NUM>). The external input may be necessary to allow the electronics unit <NUM> to operate with any new or different power supply. Data of the input may include a user name and password. In one example, the method <NUM> may include stages to create an event (at stage <NUM>) that corresponds with the manipulation of the power supply <NUM>. Notably, stages <NUM>, <NUM> may occur on the power supply <NUM> as well. This feature may be beneficial to create historical records of the device for purposes of traceability and other diagnostics, for example, performance driven analysis after the power supply <NUM> is removed from the electronics unit <NUM>.

<FIG> illustrates a flow diagram of an example of the method <NUM> of <FIG> with stages to trace use of the cells on the power supply <NUM>. The method <NUM> may include, at stage <NUM>, receiving identifier data from a power supply. The method <NUM> may also include, at stage <NUM>, accessing a registry with stored data in a listing having entries that associate components that might find use in the gas meter with use data, for example, whether the components can be used in the meter system. The method <NUM> may further include, at stage <NUM>, comparing the identifier data to the stored data in the listing to determine whether the power supply is approved for use in the gas meter. If negative, the method <NUM> may include, at stage <NUM>, setting a fault condition and, at stage <NUM>, populating an event to an event log. Operation of the method <NUM> may cease at stage <NUM>, effectively ceasing functions or providing limited functions at the gas meter. In one implementation, the method <NUM> may return to receiving identifier data at stage <NUM>. On the other hand, if the power supply is approved, the method <NUM> may include, at stage <NUM>, commissioning the power supply for use in the gas meter and, where applicable, populating an event to an event log at stage <NUM>.

At stage <NUM>, the electronics unit <NUM> may receive identifier data from the power supply <NUM>. The identifier data may define or describe information that is unique (as compared to others) to the respective power supply <NUM>. Examples of the information may include serial numbers, cyclic redundancy check (CRC) numbers, checksum values, hash sum values, or the like. Other information may define operative conditions or status for the power supply <NUM>, for example, performance data that is stored locally on the device. This information may be stored on the power supply <NUM> at the time of manufacture. In one implementation, the power supply <NUM> may be configured so that all or part of the identifier data cannot be changed or modified once manufacture or assembly is complete. This feature may deter tampering to ensure that the power supply and the gas meter, generally, will meet legal and regulatory requirements for purposes of metering of material <NUM>.

At stage <NUM>, the electronics unit <NUM> may access a registry with a listing of stored data that associates components with a use status. Table <NUM> below provides an example of this listing.

The listing above may form an "integrity" log that the electronics unit uses to properly evaluate and integrate the power supply <NUM> into the gas meter <NUM>. Stored data in the entries may define various characteristics for system components, like power supply <NUM> ("Power S"). As shown above, the listing may have entries for separate power supplies, often distinguished by identifying information such as serial number (S/N) and device type. The entries may also include operating information that may relate specifically to the power supply <NUM> of the entry in the listing. The operating information may include "performance data," for example, values for power output, "firmware data," for example, information that describes the latest version that might be found on the power supply <NUM>, and "physical data" as relates to the power supply. The physical data may correlate, for example, with the number of cells or other characteristics (e.g., size, weight, etc.). As also shown, the entries in the listing may include a use status that reflects whether the power supply <NUM> is "compatible" or "not compatible;" however other indicators to convey that the power supply <NUM> may or may not be acceptable for use in the gas meter <NUM> may be useful as well. Approval may indicate the power supply <NUM> meets power demand requirements, as well as with appropriate safety expectations, but this does not always need to be the case.

At stage <NUM>, the electronics unit <NUM> may compare the identifier data to the stored data in the listing to determine whether the power supply <NUM> is approved for use in the gas meter <NUM>. This stage is useful to certify that the power supply <NUM> is "compatible" prior to being commissioned and operates in the gas meter <NUM>. This stage may include one or more stages as necessary so as to properly commission the power supply <NUM>. These stages may, for example, include determining whether the power supply <NUM> meets certain initial criteria. The initial criteria may distinguish the power supply <NUM> by type (e.g., hardware and executable instructions), version or revision, model or serial number, and other functional or physical characteristics. For hardware, the method <NUM> may also include one or more stages to ensure power supply is located or coupled with the electronics unit <NUM> at a location (e.g., the power connector <NUM>) appropriate for its type and functions. The stages may use signals from connectors to discern the location of the device on the gas meter <NUM>.

The stages may also evaluate the status of the power supply <NUM>. In one implementation, the method <NUM> may include stages for confirming that the identifier data has not been corrupted or does not include corrupt information. Corruption might happen, for example, as are result of tampering with the hardware or by exposing the hardware to environmental conditions (e.g., radiation, temperature, etc.). For firmware, the method <NUM> may use version history and related items that may be useful to distinguish one set of executable instructions from another as well as for purposes of confirming that the set of executable instructions has not been corrupted.

At stage <NUM>, the electronics unit <NUM> may set a fault condition in response to the assessment of the identifier data (at stage <NUM>). Examples of the fault condition may take the form of an alert, either audio or visually discernable, or, in some examples, by way of electronic messaging (e.g., email, text message, etc.) that can resolve on a computing device like a smartphone or tablet. In one implementation, the fault condition may interfere with operation of one or more functions on the gas meter <NUM>, even ceasing functionality of the whole system if desired. The fault condition may also convey information about the status of the commissioning process. This information may indicate that serial numbers are incorrect or unreadable, that physical data of the power supply <NUM> is not compatible or correct, or that firmware versions and updates on the power supply <NUM> are out of date or corrupted.

At stage <NUM>, the electronics unit <NUM> can populate an event to the event log. This event log may reside on the electronics unit <NUM> as well as on the power supply <NUM>. In one implementation, the event can describe dated records of problems or issues that arise during the commissioning process. The event can also associate data and actions taken (e.g., calibration, updates, etc.) to commission the power supply <NUM> for use in the gas meter <NUM>. Relevant data may include updated to serial numbers and time stamps (e.g., month, day, year, etc.). The actions may identify an end user (e.g., a technician) and related password that could be required in order to change the configuration or update the gas meter with, for example, replacements for the power supply <NUM>.

At stage <NUM>, the electronics unit <NUM> can commission the power supply <NUM> for use in the gas meter <NUM>. This stage may change operation of the electronics unit <NUM> to accept or use the power supply <NUM>. Changes may the integrity log to include new entries or to revise existing entries with information about the connected and commissioned power supply <NUM>.

In light of the forgoing, the embodiments operate with "smart" technology to improve operation in metrology hardware. The resulting "smart" power supply may provide on-board diagnostics to maintain data that reflects charge and other operating parameters. Diagnostics, whether on the power supply or metrology hardware, may process the data. At least one technical effect is to enable the metrology hardware to properly diagnose operating problems, which may reduce costs, typically labor, by avoiding unnecessary maintenance or, on the other hand, accelerating maintenance to avoid problems down the road.

One or more of the stages of the methods can be coded as one or more executable instructions (e.g., hardware, firmware, software, software programs, etc.). These executable instructions can be part of a computer-implemented method and/or program, which can be executed by a processor and/or processing device. The processor may be configured to execute these executable instructions, as well as to process inputs and to generate outputs, as set forth herein.

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.

Claim 1:
Metrology hardware (<NUM>), comprising:
a flow responsive unit (<NUM>) in proximity to flow of fluid;
electronics (<NUM>) coupled with the flow responsive unit (<NUM>) to quantify a parameter of the flow of fluid in response to interaction with the flow responsive unit (<NUM>); and
a power supply (<NUM>) comprising an energy source (<NUM>) with at least one energy port (<NUM>) for accommodating an energy cell (<NUM>) coupled with the electronics to deliver a power signal to energize the electronics (<NUM>), the power supply (<NUM>) comprising circuitry (<NUM>) that stores data and generates a signal (S<NUM>, S<NUM>, <NUM>) that includes identifier data and operating parameters for the energy cell (<NUM>),
wherein the electronics (<NUM>) processes the signal from the power supply (<NUM>) to use the identifier data to register connection of the power supply (<NUM>) with the electronics (<NUM>),
wherein a distribution circuit (<NUM>) within the energy source (<NUM>) comprises at least one switchable circuit (<NUM>) with at least one switch (<NUM>) and at least one measurement sub-circuit (<NUM>) able to generate the signals (<NUM>) that reflect the operating parameters for the energy cell (<NUM>)
wherein the signal indicates that discharge to the electronics (<NUM>) exceeds a power consumption threshold level characterized in that:
the power consumption threshold level is an average or median based on power demand of the electronics unit (<NUM>) measured over time, and
in response to said signal, the electronic unit (<NUM>) modifies operation of said metrology hardware (<NUM>) to reduce power draw from the energy source (<NUM>).