If you’ve played Fallout 4, you’re familiar with the wall-mounted terminals in the game. They’ve got a post-apocalyptic aesthetic and the glowing green screen that calls out to anyone that grew up with computers and hacker movies from the 80s and 90s. Remember the first time you set your command line text to green? Don’t be embarrassed, we were all young once.
[PowerUpProps] liked the Fallout terminal so much they developed a replica. It’s a build that leans heavily on maker standards, a Raspberry Pi and 3D printing form the basis of the terminal. With ready access to such powerful tools, it makes starting such a project much more approachable. The key to the success of this build is the fine attention to detail in the finishing – the paint job looks incredible, and when photographed appropriately, it could be mistaken for
the real thing an in-game screenshot.
An interesting touch is the use of a dark green acrylic window in front of the LCD, which gives the display a tinted hue. We’d like to see this compared with a clear glass window with a classic fishbowl curve to it, combined with greening up in software. The creator readily admits that this looks great at the command line, but is somewhat of a letdown when using the GUI.
Perhaps the only thing the prop build could use is some sort of user interface — the keyboard is only 3D printed and there’s no mouse or other pointing device included. There are some creative solutions to this problem, which we often see in other Fallout projects, like the ever popular Pip-Boy replica builds.
[Thanks to Sjoerd for the tip!]
When a dumpster dive yielded a vintage video display terminal, [dennis1a4] knew just what to do — bring the Heathkit H19 back to life and stuff a Raspberry Pi inside.
The early days of the personal computer era were a time of great market diversity. Everyone was making stuff needed to cobble together your perfect computer, and terminals were among the most important pieces of gear. Lear Siegler, DEC, Wyse — everyone was in on the game. Even Heathkit competed with its H19 serial terminal, which would have set you back a thousand or so early-1980s dollars.
The terminal [dennis1a4] found was DOA, but he quickly determined that a bad cap was shorting out the -12VDC rail. A little extra detective work was needed to get the terminal to both echo characters locally and output them over the RS-232 port, and bam, working terminal. But then what? Raspberry Pi to the rescue! But those old school +/-12 volts swings would give a Pi a bad case of Blue Smoke Disease. After a little voltmeter poking, and through the magic of socketed driver chips, the Pi was talking right to the terminal at a screaming 9600 baud and accessing the Hackaday Retro site on the 80-by-24 mono display.
All in all, a nice hack on a piece of computer history. But just one question: Can it play
Doom Flappy Bird?
If you are a certain age, you probably remember writing software (or playing Adventure) bathed in an amber or green light from an old CRT terminal. If you are even older, you might have found it way better than punching cards, but that’s another story. [Tobi] wanted to relive those days (well, sounds like he is too young to have lived them to start with) so he hooked up a VT220 terminal to his Linux box.
This isn’t that surprising. Linux’s forefather, Unix, expected these kind of terminals (or a hard copy TeleType) and all the trappings for working with a glass terminal are still in there. You do have to deal with a few configuration items that [Tobi] works through.
In fact, it appears that he wrote his blog post using vi on that very VT220 using a text-based Web browser to research the links. He has a lot of resources for connecting a terminal of any sort (or even a terminal emulator) to a Linux computer.
There’s been a lot of interest in old terminals lately. You see a lot of old VT100s lying around. I personally have an ADDS Regent 100 that occasionally connects to several of my computers. You can see it in the video below.
Continue reading “By the Glow of the CRT”
Back in the old days, the cool kids didn’t have an Apple II or a Trash-80. The cool kids had jobs, and those jobs had Vaxxen all over the place. The usual way of working with a Vax would have been a terminal, a VT220 at least, or in the case of [Sudos]’ experiments with a Raspberry Pi, A DEC VT510, a single session, text only serial terminal.
Usually, when we see a ‘new hardware stuffed into old tech’ project like this, the idea is simply to find a use for the old hardware. That makes sense; a dumb terminal from the late 90s should be a bit rarer than a Raspberry Pi Zero. This is not the case for [Sudos]’s build. He recently came across a few Raspberry Pi Zeros at Microcenter, and looking for a use for them, he decided to turn a serial terminal into a Real Unix System™.
As you would expect from a serial terminal, connecting a Raspberry Pi and putting some awesome character graphics on the screen is as simple as a Max3232 board picked up from eBay, a WiFi dongle, and an Ethernet adapter. Connect the Pi to the terminal with a serial adapter cable, and you’re off to the races.
While the VT510 serial terminal is just about the end of the line as far as dedicated terminals go, there are classier options. The VT100 terminal, older than most of the Hackaday readership, features a port on its gigantic board, meant to connect to whatever weirdness was coming out of Maynard in the late 70s. You can attach a BeagleBone to this connector, making for a very slick stealth mod.
Before modern CRTs with ancient VGA connectors, and before fancy video terminals, the display for computers large and slightly smaller was the Teletype. While many of these Teletypes were connected directly, they were designed to be a remote terminal, connected through Ma Bell’s network. [NeXT] over on the Vintage Computer Forums is bringing the iconic ASR33 Teletype into the 21st century by giving this old display a modern way to connect to the outside world.
If you ever see a Teletype in action, it will be connected to a local machine. This was certainly not always the case. The Teletype was designed to connect to remote systems. [NeXT]’s Teletype came with a Call Control Unit designed for Telex lines, which do not exist anymore. Modems for the ASR33 existed, but good luck finding one. Lucky for [NeXT], nearly every modem ever made is backwards-compatible with the Bell Dataphone, one of the standard ways of plugging a Teletype into a phone line. All [NeXT] had to do was put a modem inside this Teletype.
With relays, transistors, LEDs, and a lot of perfboard, [NeXT] successfully built a circuit that would interface the Teletype’s Call Control Unit to a Hayes Smartmodem tucked away inside the stand. Believe it or not, this is an exceptionally useful build; if you ever find a Teletype tucked away in the back of an old office, in a surplus shop, or on Craigslist, odds are it won’t be compatible with any modern electronics. That’s not to say land lines are particularly modern, but since there’s a microcontroller included in the new circuitry, it’s relatively easy to add a USB port to this ancient terminal.
What’s more impressive, the fact that this Wolfenstein-like game is 600 lines of code, or that it’s written in AWK?
AWK is a language primarily used for text processing. But if you can write code the world bows to your wishes. [Fedor Kalugin] leverages the ability of a Linux terminal’s color options to draw his game. The 3D aspect is produced through ray-casting which generates a 2D image from 3D coordinates.
Trying out the game is extremely simple, install gawk, clone the repo, and play:
Continue reading “Wolfenstein in 600 Lines of Code”
[Piotr] was working on a recent Arduino project when he ran into a problem. He was having trouble getting his Arduino Pro Mini to communicate with an ESP8266 module. He needed a way to snoop on the back and forth serial communications. Since he didn’t have a specialized tool for this task, [Piotr] ended up building his own.
The setup is pretty simple. You start with a standard serial cable containing the TX, RX, DTR, and GND wires. This cable connects the Arduino to the ESP8266 WiFi module. The TX and RX lines are then tapped into. Each wire is routed to the RX pin of two different serial to USB adapters. This way, the data being sent from the Arduino shows up on one COM port and the data being transmitted from the module shows up on the other.
The next piece of the puzzle was coming up with a way to see the data more clearly. [Piotr] could have opened two serial terminals simultaneously, but this wasn’t ideal because it would be difficult to compare the timing of the data. Instead, [Piotr] spent less than an hour writing his own simple serial terminal. This one connects to two COM ports at the same time and prints the data on the same screen. The data from each COM port is displayed in a separate color to make it easy to differentiate. The schematic and source code to this project can be found on [Piotr’s] website.