Physical Transformation AtlasPTA
Pathway · p-2b44cdfdff · demonstrated

Thermally regenerative electrochemical cycle

Temperature gradientThermally regenerative electrochemical cycleIonic currentElectrical work

Charge cold, discharge warm; 5.7% efficiency between 10 and 60 °C with heat recuperation.

Epistemic state of the route

known constituent relations
1 / 3 established or replicated · weakest constituent demonstrated
constituent maturity floor
K4 · experimentally observed
search for this exact route
A recorded pathway or a reviewed search records a demonstration of this composition.
recorded pathway
Thermally regenerative electrochemical cycle · demonstrated
composition maturity
K5 · energy harvested
recorded-pathway overlap
this route is the recorded pathway Thermally regenerative electrochemical cycle
route-level evidence
1 source for the complete composition · 2 cited by the constituent steps
boundaries and interfaces
BOUNDARY compatible · no region transition

Explorematrix context · physics checks · performance · steps · route evidence · constituent evidence · cite

Matrix context

D = disequilibrium row · C = coupling family column. A cell reads the state of the atlas for that pair.

D.01 × C.05 · Temperature gradient × Thermogalvanicfamily: Thermogalvanic

Measured or reported performance

  1. heat-to-electricity cycle efficiency (no heat recuperation)3.7%device2014
    copper hexacyanoferrate cathode against a Cu/Cu²⁺ anode, a thermally regenerative electrochemical cycle charged at one temperature and discharged at the other
    refs [1]
  2. heat-to-electricity cycle efficiency (50 % heat recuperation assumed)5.7%model2014
    the same device and temperatures; the recuperation is an assumption, not a measured heat exchanger — the figure the abstract leads with; the atlas records it as a model datum because the 50 % recuperation is assumed
    refs [1]
best recorded efficiency (derived)
3.7% — heat-to-electricity cycle efficiency (no heat recuperation), device, 2014; derived from the structured data above, not a stored number

Typed bounds on this route

Every limit the atlas holds for this route, as constraint records: reached through bounded_by claims on the route's own entities. Hard bounds (an upper bound or a formula) decide the thermodynamic-bound check above; benchmarks, constitutive relations and resource limits are listed and never decisive. No prose limit exists anywhere (pass 42).

  • Carnot limit · formula-bound · hard, applies to this route
    η ≤ 1 − T_c/T_h for any heat engine between reservoirs at T_h and T_c

Steps

  1. 01
    thermal → electrical · loss to thermal
    • a battery chemistry whose open-circuit voltage changes with temperature by ≈ 1 mV/K
    • charge at one temperature, discharge at the other, with heat recuperation between the two
    aqueous medium required · temperature gradient required
    refs [1]
  2. 02
    electrical → electrical
    refs [1]
  3. 03
    Ionic current —converts into→ Electrical workestablishedclaim record
    electrical → electrical · loss to thermal
    • electrodes exchange the ionic current for an electronic current through the external load
    refs [2]

Evidence for the complete composition · 1

  1. [1]
    S. W. Lee et al.. An electrochemical system for efficiently harvesting low-grade heat energy (2014)
    Nature Communications 5, 3942 · doi:10.1038/ncomms4942 · crossref ✓ 2026-09-19 · record

Evidence for the constituent relations · 2

  1. [1]
    S. W. Lee et al.. An electrochemical system for efficiently harvesting low-grade heat energy (2014)
    Nature Communications 5, 3942 · doi:10.1038/ncomms4942 · crossref ✓ 2026-09-19 · record
  2. [2]
    A. J. Bard, L. R. Faulkner. Electrochemical Methods: Fundamentals and Applications (2nd ed.) (2001)
    Wiley · book, no DOI · record

Cite this route

Physical Transformation Atlas (2026). route p-2b44cdfdff: Thermally regenerative electrochemical cycle. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/path/2b44cdfdff

Ids and matrix addresses are stable across revisions; the revision hash identifies the exact canonical files the record was compiled from and is meta.data_hash in every /api export. Reuse terms: see the license field in any export.