Physical Transformation AtlasPTA
Coupling family · coupling:rectenna

Rectenna

An antenna feeding a rectifier to turn radiation into direct current.

Electromagnetismalso: rectenna, RF energy harvesting, microwave power transmission

Atlas record: 2 claims reference this coupling family — 2 established.

Explorerelations · matrix context · sources · cite

2claims0enumerated routes0routes with complete-composition evidence0candidate routes not searched1cited sources

Relations

member of · 2
Antenna reception—member of→Rectennaestablished
Rectification—member of→Rectennaestablished

Matrix context

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

D.01 Temperature gradientD.02 Pressure gradientD.03 Concentration gradientD.04 Salinity gradientD.05 Chemical potential differenceD.06 Electric potential differenceD.07 Changing magnetic fluxD.08 Mechanical stress or strainD.09 Mechanical vibrationD.10 Bulk fluid flowD.11 Incident radiation fluxD.12 Radiative imbalance with the skyD.13 Spin accumulationD.14 Metastable phaseD.15 Surface energy differenceD.16 Capillary pressureD.17 Humidity gradientD.18 Osmotic pressure differenceD.19 Gravitational potential differenceD.20 Nuclear binding-energy differenceD.21 Thermal energy at uniform temperatureD.22 Quantum vacuum fluctuationsD.23 Acoustic fieldD.24 Temporal temperature changeD.25 Changing electric field

Cited sources · 1

  1. [1]
    W. C. Brown. The history of power transmission by radio waves (1984)
    IEEE Transactions on Microwave Theory and Techniques 32, 1230–1242 · doi:10.1109/TMTT.1984.1132833 · crossref ✓ 2026-09-19 · record

Cite this entity

Physical Transformation Atlas (2026). entity coupling:rectenna: Rectenna. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/e/coupling/rectenna

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.