Love this article!
One nit: All three animations that show the governor and the flywheel have the governor turning the wrong way, causing the gears that join them to do physically impossible things.
The Beam Engine
31–40 of 107 posts
Re: The Beam Engine
#32Love this article! One nit: All three animations that show the governor and the flywheel have the governor turning the wrong way, causing the gears that join them to do physically impossible things.
Oh my. Yes, you are totally right. This was tricky because I needed to merge two different animations (the governor moves independently from the rotation of the wheel), and I seem to have messed that up.
Fix shall be deployed shortly!
Re: The Beam Engine
#33How did you do the figures? Iterative design with Three.js and an agent? What did that process look like?
Re: The Beam Engine
#34One of the unexpected pleasures of having a 3 year old has been learning far more than I ever planned to about steam locomotives. It turns out steam engineering is fascinating, this article emphasized it for me even more. It really amazes me how much ingenuity there is in just connecting the right shapes and joints up so that the right thing happens at the right time, creating perfect cycles, regulators, etc. Seeing…
Thank you! I have a few ideas for the next article. Locomotives are up there on the list, but they are the final challenge of steam engineering, there is so much to cover.
Also considering the origins of precision - the intertwined evolution of machining tools and measuring systems that allowed these machines to be built.
RE: 3 year old - yes, mechanical systems are wonderful for children (and adults). There is something incredibly satisfying about watching them in motion doing work.
Re: The Beam Engine
#35How did you do the figures? Iterative design with Three.js and an agent? What did that process look like?
It was a mix of techniques, this article has been in progress for quite a while :). The first part was modeling all the relationships for an accurate beam engine in onshape (great cad tool). Then, I built a custom exporter to cleanly export it to three.js. This ensured physical realism for the hero of the article. All of these are linked from the article.
For the figures, I had prototyped some by hand, and it was slow going. Fable was the first LLM I found that was actually able to understand and model mechanical linkages correctly enough to be useful. I built a style guide, and iterated many times on each figure and animation until we arrived at something useful. There are also quite a few backing tests to ensure physical correctness of the animations (as far as reasonably possible :).
Re: The Beam Engine
#36Love this article! One nit: All three animations that show the governor and the flywheel have the governor turning the wrong way, causing the gears that join them to do physically impossible things.
Oh my. Yes, you are totally right. This was tricky because I needed to merge two different animations (the governor moves independently from the rotation of the wheel), and I seem to have messed that up. Fix shall be deployed shortly!
Fixed!
Re: The Beam Engine
#37Ever hear the phrase "Balls out" when referring to pushing something to the max? Comes form the balls of the centrifugal engine governor. At maximum speed the balls extended all the way outward giving us the term "Running balls out." https://en.wikipedia.org/wiki/Centrifugal_governor edit: I once said this phrase at a work meeting and someone objected to my use of a crude term which I then explained much to everyone'…
> When the engine slows, the balls fall and open the cock again.
The choice of wording makes me suspect that they intended both entendres. ;)
Re: The Beam Engine
#38Re: The Beam Engine
#39Ancient Greeks had a steam engine. They called it a Hero's engine. They used it as a toy.
They couldn't use it as anything else than a toy. The reason they couldn't because they didn't have the metallurgy and the machining to create pistons, valves, etc.
There's an important lesson that can be applied to every technology, I think: technological progress is always iterated, never revolutionized. If your novelty - a programming language, a framework, a methodology, whatever - doesn't stand on the shoulders of the giants, then you have simply nothing to apply this novelty to.
Re: The Beam Engine
#40Author here. The beam engine created power from steam, and was a key part of the early Industrial Revolution. The article is a deep dive into the engine: how it works, the history behind it, and the engineering tradeoffs the builders faced. There are quite a few interactive figures that I hope make the concepts easier to see.
This reminds me a lot of the articles at: https://ciechanow.ski/archives/
Not just in terms of presentation, but also quality.
Amazing!