Physical Transformation AtlasPTA
Phenomenon · phenomenon:resonant-vibration

Resonant vibration

A structure driven near its natural frequency stores and cycles mechanical energy; ambient vibration becomes cyclic stress in a cantilever or seismic mass.

Classical mechanicsfirst reported 1700also: base excitation, cantilever resonance

Atlas record: 3 claims reference this phenomenon — 3 established.

Explorerelations · routes · sources · cite

conditions: solid
3claims25enumerated routes4routes with complete-composition evidence4candidate routes not searched3cited sources

Relations

drives · 1
Mechanical vibration—drives→Resonant vibrationestablished
  • a cantilever or seismic mass with natural frequency near the excitation
produces · 2
Resonant vibration—produces→Mechanical stress or strainestablished
  • cyclic bending stress at the root of the cantilever
Resonant vibration—produces→Mechanical motionestablished

Enumerated routes through this · 25 (showing 24)

Cited sources · 3

  1. [1]
    A. Erturk, D. J. Inman. Piezoelectric Energy Harvesting (2011)
    Wiley · doi:10.1002/9781119991151 · crossref ✓ 2026-09-19 · record
  2. [2]
    S. P. Beeby, et al.. A micro electromagnetic generator for vibration energy harvesting (2007)
    Journal of Micromechanics and Microengineering 17, 1257 · doi:10.1088/0960-1317/17/7/007 · crossref ✓ 2026-09-19 · record
  3. [3]
    S. Roundy, P. K. Wright, J. Rabaey. A study of low level vibrations as a power source for wireless sensor nodes (2003)
    Computer Communications 26, 1131–1144 · doi:10.1016/S0140-3664(02)00248-7 · crossref ✓ 2026-09-19 · record

Cite this entity

Physical Transformation Atlas (2026). entity phenomenon:resonant-vibration: Resonant vibration. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/phenomenon/resonant-vibration

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.