A Look Inside The Space Shuttle’s First Printer

There was even a day not too long ago when printers appeared to be going the way of the dodo; remember the “paperless office” craze? But then, printer manufacturers invented printers so cheap they could give them away while charging $12,000 a gallon for the ink, and the paperless office suddenly suffered an extinction-level event of its own. You’d think space would be the one place where computer users would be spared the travails of printing, but as [Ken Shirriff] outlines, there were printers aboard the Space Shuttle, and the story behind them is fascinating.

The push for printers in space came from the combined forces of NASA’s love for checklists and the need for astronauts in the early programs to tediously copy them to paper; Apollo 13, anyone? According to [Ken], NASA had always planned for the ability to print on the Shuttle, but when their fancy fax machine wasn’t ready in time, they kludged together an interim solution from a US military teleprinter, the AN/UG-74C. [Ken] got a hold of one of these beasts for a look inside, and it holds some wonders. Based on a Motorola MC6800, the teleprinter sported both a keyboard, a current loop digital interface, and even a rudimentary word processor, none of which were of much use aboard the Shuttle. All that stuff was stripped out, leaving mostly just the spinning 80-character-wide print drum and the array of 80 solenoid-powered hammers, to bang out complete lines of text at a time. To make the printer Shuttle-worthy, a 600-baud frequency-shift keying (FSK) interface was added, which patched into the spaceplane’s comms system.

[Ken] does his usual meticulous analysis of the engineering of this wonderful bit of retro space gear, which you can read all about in the linked article. We hope this portends a video by his merry band of Apollo-centric collaborators, for a look at some delicious 1970s space hardware.

The 555 As A MOSFET Driver

To drive a MOSFET requires more than merely a logic level output, there’s a requirement to charge the device’s gate which necessitates a suitable buffer amplifier. A variety of different approaches can be taken, from a bunch of logic buffers in parallel to a specialised MOSFET driver, but [Mr. T’s Design Graveyard] is here with a surprising alternative. As it turns out, the ever-useful 555 timer chip does the job admirably.

It’s a simple enough circuit, the threshold pin is pulled high so the output goes high, and the PWM drive from an Arduino is hooked up to the reset pin. A bipolar 555 can dump a surprising amount of current, so it’s perfectly happy with a MOSFET. We’re warned that the CMOS variants don’t have this current feature, and he admits that the 555 takes a bit of current itself, but if you have the need and a 555 is in your parts bin, why not!

This will of course come as little surprise to anyone who played with robots back in the day, as a 555 or particularly the 556 dual version made a pretty good and very cheap driver for small motors. If you’ve ever wondered how these classic hips work, we recently featured an in-depth look.

Continue reading “The 555 As A MOSFET Driver”

A rough cut piece of wood sits on a workbench. A light and a tumbleweed are mounted on top so that the light shines through the tumbleweed. A woman in a ball cap and white tank top is crouched in the background smiling.

Cisco Ball Is The Tumbleweed Opposite Of A Disco Ball

Inspiration can strike a maker at any moment. For [Laura Kampf], it happened in the desert when she saw a tumbleweed.

Tumbleweeds roll through the western United States, hitting cars on the interstate and providing some background motion for westerns. [Kampf] found the plant’s intricate, prickly structure mesmerizing, and decided to turn it into a piece of contemplative kinetic art.

[Kampf] attached the tumbleweed to a piece of wood using epoxy and mounted it to what appears to be a worm drive motor nestled inside an interestingly-shaped piece of wood. As the tumbleweed turns, a light shines through it to project a changing shadow on the wall to “create silence, it creates calmness, it takes away from the noise that surrounds it.” While [Kampf] has some work to do to get the sculpture to its finished state, we can get behind her mantra, “The most important thing about the phase of execution is to get started.”

Are you looking for some projects of your own to help you find calm? How about some ambient lighting, a sand drawing table, or a music player that keeps things simple?

Continue reading “Cisco Ball Is The Tumbleweed Opposite Of A Disco Ball”

A Two-Stroke Engine Made From Scratch Using Basic Hardware Store Parts

A working DIY two-stroke in all of its glory, with the flywheel removed. (Credit: Camden Bowen)
A working DIY two-stroke in all of its glory, with the flywheel removed. (Credit: Camden Bowen)

How hard could it to be to build a two-stroke internal combustion engine (ICE) from scratch? This is a challenge that [Camden Bowen] gladly set for himself, while foregoing such obvious wastes of time like first doing an in-depth literature study on the topic. That said, he did do some research and made the design in OnShape CAD before making his way over to the hardware store to make some purchases.

As it turns out, you can indeed build a two-stroke engine from scratch, using little more than some metal piping and other parts from the hardware store. You also need a welder and a lathe, with [Camden] using a Vevor mini-lathe that totally puts the ‘precision’ in ‘chatter’. As building an ICE requires a number of relatively basic parts that have to move with very little friction and with tight tolerances, this posed some challenges, but nothing that some DIY spirit can’t fix.

In the case of the very flexible boring bar on the lathe, improvising with some sturdy metal stock welded to a short boring bar resolved that, and precision was achieved. Together with an angle grinder, [Camden] was then able to manufacture the crank case, the cylinder and crank shaft and all the other pieces that make up an ICE. For the carburetor he used a unit off Amazon, which turned out to have the wrong throat size at 19 mm, but a 13 mm version worked. Ultimately, the first ICE constructed this way got destroyed mostly by running it dry and having the starter fluid acting as a solvent, but a full rebuild fixed all the issues.

This second attempt actually ran just fine the first time around, with oil in the crank case so that the poor engine wasn’t running dry any more. With a 40:1 fuel/oil mixture the little engine idles and runs as well as a two-stroke can, belching blue smoke and making a ruckus. This answers the question of whether you can build a two-stroke ICE with basic machining skills and tools, but of course the question that’s now on everyone’s lips is whether a four-stroke one would be nearly as ‘easy’. We wait with bated breath.

Continue reading “A Two-Stroke Engine Made From Scratch Using Basic Hardware Store Parts”

Asteroids: Kessler Syndrome Edition

Asteroids, the late-70s arcade hit, was an immensely popular game. Often those with the simplest premise, while maintaining a fun, lighthearted gameplay have the most cultural impact and longest legacy. But, although it was popular, it doesn’t really meet the high bar of scientific fidelity that some gamers are looking for. That’s why [Attoparsec] built the Kessler Syndrome Edition of this classic arcade game.

The Kessler Syndrome is a condition where so much man-made debris piles up in low-Earth orbit that nothing can occupy this orbit without getting damaged or destroyed by the debris, and thus turning into more debris itself in a terrible positive feedback loop. [Attoparsec] brings this idea to Asteroids by reprogramming the game so that asteroids can be shot into smaller and smaller pieces but which never disappear, quickly turning the game into a runaway Kessler Syndrome where the chance of survival is extremely limited, and even a destroyed player’s ship turns into space junk as well.

To further the scientific accuracy and improve playability, though, he’s added a repulsor beam mechanism which can push the debris a bit and prolong the player’s life, and also added mass effect reactions so that even shooting bullets repels the player’s ship a bit. The build doesn’t stop with software, either. He also built a custom 70s-style arcade cabinet from the ground to host the game.

Asteroids is still a popular platform for unique builds like this. Take a look at a light-vector game using lasers to create the graphics, or this tiny version of the game that uses a real CRT.

Thanks to [smellsofbikes] for the tip!

Continue reading “Asteroids: Kessler Syndrome Edition”

Embedded Python: MicroPython Toolkits

Last time, I talked about how MicroPython is powerful and deserving of a place in your toolkit, and it made for a lively discussion. I’m glad to see that overall, MicroPython has indeed been getting the recognition it deserves – I’ve built a large number of wonderful projects with it, and so have people I’ve shown it to!

Sometimes I see newcomers dissatisfied with MicroPython, because the helper tools they initially pick don’t suit it well. For instance, they try and start out with a regular serial terminal application that doesn’t fit the MicroPython constraints, or a general IDE that requires a fair bit of clicking around every time you need to run your code. In particular, I’d make sure that you know your options no matter whether you prefer GUI or commandline – both have seriously nice tools for MicroPython use!

The main problem to be solved with MicroPython is that you have a single serial port that everything happens through – both file upload and also debugging. For ESP8266/32-based boards, it’s a physical serial port, and for chips like RP2040 and ESP32-S* where a hardware USB peripheral is available, it’s a virtual one – which makes things harder because the virtual port might get re-enumerated every now and then, possibly surprising your terminal application. If you want to upload a program of yours, you need to free up the serial port, and to see the program’s output, you will need to reopen that port immediately after – not a convenient thing to do if you’re using something like PuTTy.

So, using MicroPython-friendly software is a must for a comfortable hacking experience. What are your options? Continue reading “Embedded Python: MicroPython Toolkits”

Serve Your Next Website With QuickBasic

You can only imagine that when they made Star Trek back in the 1960s, they would have laughed if anyone suggested they’d still be making the show nearly six decades later. If you told [John Kemeny] at Dartmouth back in 1964 that people would be serving websites in Basic in the year 2024, he’d probably be amazed after you explained what a website was. But that’s what [Jamonholmgren] is doing.

[Jamon] wrote his first Basic program when he was 12, which was a common thing to do. Recently, he decided to build and deploy a website using Basic, and so this project, qub (pronounced like cube), was born. The web server is modified from an existing source but adds features and many new features are planned.

Continue reading “Serve Your Next Website With QuickBasic”