Math Bridge: Battery Energy and Protocol Overhead

← Back to AMQP vs MQTT and Use Cases
Math BridgeAMQPStruggle-friendly runway

How can the same 5000 mAh label hide three times the energy?

Separate charge from energy, then use one shared radio model to compare MQTT and AMQP bytes honestly.

Eddie, the electronics guideEddie guides
The one targetTurn a battery's mAh and voltage into energy, then trace protocol bytes into transmit energy.
The chapter case5000 mAh, 3.70 V, 52 MQTT bytes, 58 AMQP bytes, and one shared 250 kbps radio.
What it buys youA protocol ratio that stays separate from an unsupported days-of-life claim.

A technician must decide whether nameplate pack energy is safe before changing nominal pack voltage on the real device. The result is unresolved until the rule and units are checked. Predict the direction first.

See the relationship before changing it

The figure reads from left to right. The blue card is nominal pack voltage. The middle card applies this page's rule. The green card is nameplate pack energy. Walk the arrows once: set the input, apply the rule, then read the result with its unit.

The retained audit below checks several chapter fixtures. This model keeps those stated values fixed and changes only nominal pack voltage, so the numeric fixture does not switch without explanation.

Nominal pack voltage changes nameplate pack energy An input card leads through the rule energy = 5.0 Ah x pack voltage to the nameplate pack energy result. INPUT PAGE INPUT APPLY THE RULE predict calculate check units OUTPUT RESULT
Walk the arrows. The same amp-hour label stores more energy when nominal voltage is higher.

Derive the baseline in four named moves

  1. 1

    Name the input. The chapter baseline is 3.7 V.

  2. 2

    Name the relationship. energy = 5.0 Ah x pack voltage

  3. 3

    Substitute with units. 5.0 Ah x 3.70 V = 18.5 Wh

  4. 4

    Read the result. Keep the unit beside the value. Use it only inside the technical boundary on this page.

Predict, then change nominal pack voltage

Try Predict the direction of energy = 5.0 Ah x pack voltage. Test another nominal pack voltage, then compare nameplate pack energy.

3.7 V
Chapter baseline
Nameplate pack energy

Observe The same amp-hour label stores more energy when nominal voltage is higher. Reset nominal pack voltage to 3.7 and compare nameplate pack energy.

Explain The same amp-hour label stores more energy when nominal voltage is higher.

Check yourself

What should you do before trusting a moved-control result?
Answer: Predict its direction, apply the shown relationship, keep the units, and reset to the worked baseline.
What does this small model leave out?
Answer: Only nominal pack voltage moves here. Field effects named in the technical boundary stay fixed.

Honesty note. This teaching model changes only nominal pack voltage. It is not a field prediction.

1. Start with the physical story

A milliamp-hour counts electric charge. Voltage tells us how much energy each unit of charge can deliver. On one shared cell, protocol bytes set airtime, so their ratio can be compared even when absolute field life cannot.

Eddie: Keep two chains separate: mAh × volts → watt-hours, and bytes → airtime → transmit energy.

2. Name every algebra move

1

Change unitsDivide 5000 mAh by 1000 to obtain 5 Ah.

2

Find pack energyMultiply amp-hours by voltage to obtain watt-hours; multiply watt-hours by 3600 for joules.

3

Count protocol bytesAdd each header to the shared 50-byte payload.

4

Find airtimeMultiply bytes by eight and divide by bit rate.

5

Find radio energyMultiply voltage, current, and seconds; compare protocols with AMQP divided by MQTT.

3. Reproduce the chapter case

5 Ah × 3.70 V = 18.5 Wh = 66,600 J
MQTT: (50 + 2) × 8 / 250,000 = 1.664 ms
AMQP: (50 + 8) × 8 / 250,000 = 1.856 ms
58 / 52 = 1.1154

The same 1.1154 ratio reaches airtime and transmit energy because voltage, current, and bit rate are shared.

4. Try one real input

TryMove the nominal pack voltage from 3.70 V toward 1.20 V. Watch absolute energy change while the protocol ratio stays fixed.

Voltage
Pack energy
Pack energy
MQTT bytes
AMQP bytes
Byte ratio
MQTT airtime
AMQP airtime
MQTT transmit energy
AMQP transmit energy
MQTT daily transmit
AMQP daily transmit

ObserveAt 3.70 V the pack is 18.5 Wh. AMQP transmit energy is 1.115 times MQTT transmit energy, and both absolute values fall when voltage falls.

ExplainVoltage multiplies both protocol energies equally, so it changes joules but cancels from their ratio.

Technical boundaries.

This is a fixed-rate transmit-only ledger.

Battery
Nameplate voltage and mAh do not include discharge curves, cutoff, temperature, or pulse sag.
Protocol
The 52-byte and 58-byte records are chapter values, not universal frame sizes.
Radio
Receive time, retries, CPU work, idle current, and connection setup are omitted.

Correct, not complete: this ledger does not predict field battery life or choose a protocol.

5. Use the result in the design

Record the actual cell voltage and measured frame sizes. Use the ratio only when the two cases share the same radio state, then add connection, receive, retry, processor, and sleep energy separately.

6. Record the evidence state

Record chemistry, nominal voltage, usable capacity, payload and header bytes, data rate, current trace, messages per day, retries, connection lifetime, and the exact boundary of the comparison.

7. Check yourself

Why is 5000 mAh not already an energy value?
Answer: It measures charge. Energy also needs voltage, so 5 Ah can mean 6.0 Wh at 1.2 V or 18.5 Wh at 3.7 V.
Why does voltage cancel from the AMQP-to-MQTT ratio?
Answer: Both cases use the same voltage, current, and bit rate, leaving only their different byte counts.
Does the 1.115 ratio prove 11.5% shorter field life?
Answer: No. It describes this transmit slice; sleep, receive, retries, setup, self-discharge, and cutoff can dominate total life.
Honesty boundary.

This is a fixed-rate transmit-only ledger.

Battery
Nameplate voltage and mAh do not include discharge curves, cutoff, temperature, or pulse sag.
Protocol
The 52-byte and 58-byte records are chapter values, not universal frame sizes.
Radio
Receive time, retries, CPU work, idle current, and connection setup are omitted.

Correct, not complete: this ledger does not predict field battery life or choose a protocol.

Return to AMQP vs MQTT with the maths unpacked →