Thermocapillary micromotor
Temperature gradientMarangoni effectMechanical motionMechanical work
Absorbed light heats an asymmetric floating gear unevenly; the surface-tension gradient around it drives a thermocapillary flow whose stress torques the gear. The temperature gradient is the driver; light is how it is prepared.
Epistemic state of the route
- known constituent relations
- 3 / 3 established or replicated · weakest constituent replicated
- 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
- Thermocapillary micromotor · demonstrated
- composition maturity
- K5 · energy harvested — Thermocapillary micromotor
- recorded-pathway overlap
- this route is the recorded pathway Thermocapillary micromotor
- route-level evidence
- 1 source for the complete composition · 5 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.34 · Temperature gradient × Marangonifamily: Marangoni
Measured or reported performance
- rotation rateup to 300 r.p.m.device2015microfabricated asymmetric gears on a liquid–air interface under wide-field incoherent illumination; the temperature gradient that drives the thermocapillary flow is produced by the light the gear absorbs — rotational work against viscous drag; no load other than the fluid was measuredrefs [3]
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
- 01thermal → kinetic · loss to thermal
- thermocapillary case: surface tension falls with temperature, so a temperature gradient along the interface drives flow toward the cold side
liquid · temperature gradient requiredrefs [1] [2] - 02kinetic → mechanical · loss to thermal
- a floating or interface-bound body whose asymmetry (shape, or where it emits a surfactant or absorbs heat) leaves a net surface-tension force or torque on it
- the body must be free to move on the interface; a rigid wall only sets up a flow
liquidTwo independent groups: thermocapillary microgears (Maggi et al. 2015, light-heated, up to 300 r.p.m.) and solutocapillary camphor rotors carrying magnets past a coil (Frenkel et al. 2019, 10–20 h). Distinct from Marangoni flow turning a rotor: here the Marangoni stress acts on the moving body directly.refs [3] [4] - 03mechanical → mechanical · loss to thermalrefs [5]
Evidence for the complete composition · 1
- [3]C. Maggi et al.. Micromotors with asymmetric shape that efficiently convert light into work by thermocapillary effects (2015)
Evidence for the constituent relations · 5
- [1]L. E. Scriven, C. V. Sternling. The Marangoni Effects (1960)
- [2]Q. Dai et al.. Directional interfacial motion of liquids: Fundamentals, evaluations, and manipulation strategies (2021)
- [3]C. Maggi et al.. Micromotors with asymmetric shape that efficiently convert light into work by thermocapillary effects (2015)
- [4]M. Frenkel et al.. Mini-Generator of Electrical Power Exploiting the Marangoni Flow Inspired Self-Propulsion (2019)
- [5]A. Bejan. Advanced Engineering Thermodynamics (4th ed.) (2016)
Cite this route
Physical Transformation Atlas (2026). route p-eabf9fa870: Thermocapillary micromotor. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/path/eabf9fa870
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.