Published
What to bring to the review
- The exact functions powered by the battery: controls, pump, heating or a defined combination
- Voltage and current measurements covering a complete operating cycle, startup and standby
- The measurement boundary: battery terminals or the appliance side of a converter
- Usable energy to the actual system cutoff under the intended load and conditions
- Idle periods and any operational reserve that has not already been included
- Identified battery, host, charger and firmware revisions for the evaluation
Start with what the battery actually powers
A battery-powered coffee machine may use its pack for controls and a pump, for heating as well, or for a different combination of functions. State that boundary before estimating runtime. Do not apply a heater rating to a machine that heats by another method, or ignore heating when it is supplied by the battery.
Define a complete cycle for the intended test. Record the relevant machine settings, starting conditions and pauses between operations. A result for one routine should not be presented as a universal number of cups. Keep the operating conditions alongside the result.
Measure energy across a complete operating cycle
At the battery terminals, integrate measured voltage multiplied by current over the complete cycle. When time is expressed in seconds, energy in watt-hours is the integral of V(t) × I(t), divided by 3600. Use a measurement setup and sampling rate appropriate for the load changes; an occasional current reading can miss short events.
Include startup, normal operation, shutdown and any recovery that belongs to the defined cycle. If the test uses repeated operations, record the spread of results and the conditions that changed. Keep the measured energy per cycle distinct from the largest instantaneous current or power.
- Energy answers how much of the battery budget an operation consumes.
- Peak current and power answer whether the pack and interfaces can supply the operating events.
- An acceptable average-energy estimate does not qualify a pack for an unmeasured startup peak.
Use available energy to the actual cutoff
Nominal voltage multiplied by rated ampere-hours gives a nominal energy label. It does not show how much energy the intended host can use before its operating limit or the pack's protection boundary is reached. Evaluate usable energy with the intended load, system limits and pack condition.
Temperature, discharge rate and changes in battery impedance can affect the capacity available before a termination threshold is reached. TI's fuel-gauge application report explains these dependencies. That reference supports the general engineering principle; it does not qualify a TI device for a Jinfan pack or certify a coffee machine.
Keep a test record of the battery revision and condition, starting state, load routine, temperature and the cutoff definition. Do not adopt a universal usable-energy percentage from this guide; the required value has to come from the intended system or a justified project model.
Texas Instruments SLUA684: accuracy and verification methodologies for fuel gauges
Avoid counting conversion losses or reserve twice
If both usable energy and cycle energy are measured at the battery terminals, conversion losses already contribute to the measured battery demand. Do not apply an additional assumed converter penalty to the same energy measurement.
If energy per cycle is measured after a converter, translate it to the battery side using efficiency information appropriate to the actual operating conditions, and include other battery-side consumption. Do not divide a load-side energy figure directly into a battery-side budget without defining that conversion.
State whether a reserve has already been excluded from the usable-energy figure. Subtract it only once. Account for standby over the intended waiting period as well, unless that time and consumption are already part of the defined cycle measurement.
A hypothetical calculation: an energy budget, not a product claim
For illustration only, suppose a test establishes 20 Wh available at the battery terminals to the stated cutoff. Suppose the intended waiting periods consume 1 Wh, a separate operational reserve is 1 Wh, and a complete operating cycle consumes 2 Wh at the same battery terminals. In this hypothetical example, the reserve has not already been deducted from the 20 Wh.
The energy left for complete cycles is 20 − 1 − 1 = 18 Wh. Dividing 18 Wh by 2 Wh per cycle gives 9 complete cycles in that simplified example. These numbers are invented solely to demonstrate the arithmetic. They are not Jinfan test data, a reference-pack specification or a promise of nine cups from a coffee machine.
Real cycle demand and available energy can vary. Use an appropriate evaluation range, retain the operating conditions and confirm the result in the intended appliance. Do not turn a single arithmetic example into a minimum-runtime guarantee.
Turn the estimate into a prototype evaluation
Run the defined routine using the intended battery and host revision, and compare observed operation with the energy estimate. Record the reason the evaluation ends: host shutdown, an operating requirement, a protection event or another stated limit. A protection threshold must not be bypassed to obtain a larger cycle count.
Review startup demand, low-battery behavior, charging and the application environment separately. The runtime estimate is one part of integration evaluation, not evidence that the whole electrical, mechanical or compliance scope has passed.
Jinfan supports collaborative development of built-in and removable coffee machine battery packs, including small-batch prototyping. Bring your measurements, drawings and open questions to an engineering discussion. Sample quantity, design scope and timing are agreed for the project; this guide does not set fixed values.