Piezoelectric Energy Harvesting
Atlas use: this book is cited as evidence by 12 claims and 2 named pathways. Bibliographic record verified against Crossref on 2026-09-19.
Exploreatlas context · claims citing it · pathways citing it · cite
Atlas context
Derived from the citing claims only: the families, matrix cells and routes those claims take part in.
D = disequilibrium row · C = coupling family column. A cell reads the state of the atlas for that pair.
- Bimetallic-strip piezoelectric harvestercomposition evidence recorded
- Piezoelectric vibration harvestercomposition evidence recorded
- Electromagnetic vibration harvestercomposition evidence recorded
- Pneumatic pressure piezoelectric harvestercomposition evidence recorded
- Flexoelectric vibration harvestercomposition evidence recorded
- Flow-induced-vibration piezoelectric harvestercomposition evidence recorded
- Magnetostrictive vibration harvestercomposition evidence recorded
- Wave-impact piezoelectric harvestercomposition evidence recorded
- Mechanical stress or strain → Direct piezoelectric effect → Separated surface charge → Electrical work3/3 established
- Mechanical vibration → Resonant vibration → Mechanical motion → Mechanical work3/3 established
- Acoustic field → Direct piezoelectric effect → Separated surface charge → Electrical work3/3 established
- Mechanical vibration → Resonant vibration → Mechanical stress or strain → Elastocaloric effect → Cooling3/4 established
first 12 of 75 routes shown
Claims citing this source · 12
Named pathways citing this source · 2
- Flow-induced-vibration piezoelectric harvesterdemonstrated
- Piezoelectric vibration harvestercommercial
Cite this source
Physical Transformation Atlas (2026). source source:erturk-inman-2011: Piezoelectric Energy Harvesting. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/source/erturk-inman-2011
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.