The future we know today looks very different than the one envisioned in the 60s and 70s. For starters, it has far too few Nixie tubes. An oversight [nixiebunny] wants to address with his Nixie tube instrument panel.
All the essential info is there: engine temperature, tachometer, speed, battery voltage, and even odometer. You might have noticed that there isn’t a clock. The justification that [nixiebunny] gives is that he’s always wearing his Nixie watch, so a clock in his car seems redundant. There is also a gap in the panel to allow an oil pressure display. Corvairs are known for throwing belts next to the oil sender, so any attached sensor needs to be designed well and thought through. A Teensy receives engine telemetry data (no OBDII port to hook into — GM didn’t come out with the first OBD port until the 80s) from the engine bay. The data is transformed into SPI data sent to the 74HC595 shift register chain via a CAT5 cable. Details are a little sparse, but we can see a custom PCB to fit the shape of the hole in the dash with the different Nixie tube footprints silkscreened on.
Among the many facets of modern technology, few have evolved faster or more radically than the computer. In less than a century its very nature has changed significantly: today’s smartphones easily outperform desktop computers of the past, machines which themselves were thousands of times more powerful than the room-sized behemoths that ushered in the age of digital computing. The technology has developed so rapidly that an individual who’s now making their living developing iPhone applications could very well have started their career working with stacks of punch cards.
With things moving so quickly, it can be difficult to determine what’s worth holding onto from a historical perspective. Will last year’s Chromebook one day be a museum piece? What about those old Lotus 1-2-3 floppies you’ve got in the garage? Deciding what artifacts are worth preserving in such a fast moving field is just one of the challenges faced by Dag Spicer, the Senior Curator at the Computer History Museum (CHM) in Mountain View, California. Dag stopped by the Hack Chat back in June of 2019 to talk about the role of the CHM and other institutions like it in storing and protecting computing history for future generations.
To answer that most pressing question, what’s worth saving from the landfill, Dag says the CHM often follows what they call the “Ten Year Rule” before making a decision. That is to say, at least a decade should have gone by before a decision can be made about a particular artifact. They reason that’s long enough for hindsight to determine if the piece in question made a lasting impression on the computing world or not. Note that such impression doesn’t always have to be positive; pieces that the CHM deem “Interesting Failures” also find their way into the collection, as well as hardware which became important due to patent litigation.
Of course, there are times when this rule is sidestepped. Dag points to the release of the iPod and iPhone as a prime example. It was clear that one way or another Apple’s bold gambit was going to get recorded in the annals of computing history, so these gadgets were fast-tracked into the collection. Looking back on this decision in 2022, it’s clear they made the right call. When asked in the Chat if Dag had any thoughts on contemporary hardware that could have similar impact on the computing world, he pointed to Artificial Intelligence accelerators like Google’s Tensor Processing Unit.
In addition to the hardware itself, the CHM also maintains a collection of ephemera that serves to capture some of the institutional memory of the era. Notebooks from the R&D labs of Fairchild Semiconductor, or handwritten documents from Intel luminary Andrew Grove bring a human touch to a collection of big iron and beige boxes. These primary sources are especially valuable for those looking to research early semiconductor or computer development, a task that several in the Chat said staff from the Computer History Museum had personally assisted them with.
Towards the end of the Chat, a user asks why organizations like the CHM go through the considerable expense of keeping all these relics in climate controlled storage when we have the ability to photograph them in high definition, produce schematics of their internals, and emulate their functionality on far more capable systems. While Dag admits that emulation is probably the way to go if you’re only worried about the software side of things, he believes that images and diagrams simply aren’t enough to capture the true essence of these machines.
Quoting the the words of early Digital Equipment Corporation engineer Gordon Bell, Dag says these computers are “beautiful sculptures” that “reflect the times of their creation” in a way that can’t easily be replicated. They represent not just the technological state-of-the-art but also the cultural milieu in which they were developed, with each and every design decision taking into account a wide array of variables ranging from contemporary aesthetics to material availability.
While 3D scans of a computer’s case and digital facsimiles of its internal components can serve to preserve some element of the engineering that went into these computers, they will never be able to capture the experience of seeing the real thing sitting in front of you. Any school child can tell you what the Mona Lisa looks like, but that doesn’t stop millions of people from waiting in line each year to see it at the Louvre.
The Hack Chat is a weekly online chat session hosted by leading experts from all corners of the hardware hacking universe. It’s a great way for hackers connect in a fun and informal way, but if you can’t make it live, these overview posts as well as the transcripts posted to Hackaday.io make sure you don’t miss out.
This week, Hackaday Editor-in-Chief Elliot Williams and Assignments Editor Kristina Panos fawn over a beautiful Italian split-flap clock that doesn’t come cheap, and another clock made of floppies that could be re-created for next to nothing. We’ll also sing the praises of solderless circuitry for prototyping and marvel over a filament dry box with enough sensors to control an entire house. The finer points of the ooh, sparkly-ness of diffraction gratings will be discussed, and by the end of the show, you’ll know what we each like in a microscope.
Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!
(And if you’re wondering about what my joke about not having Kristina on the show for 28 seconds, and all the professionalism, was about — we both forgot to press record the first time through and got ~15 minutes into the show before noticing. Yeah. But we had a good time the second time around anyway.)
It’s no secret that we really like circuit sculptures around here, and we never tire of seeing what creative ways people come up with to celebrate the components used to make a project, rather than locking them away in an enclosure. And a circuit sculpture that incorporates sound and light in its design is always a real treat to discover.
Called “cwymriad” by its designer, [Eirik Brandal], this sound sculpture incorporates all kinds of beautiful elements. The framework is made from thick pieces of acrylic, set at interesting angles to each other and in contrasting colors. The sound-generating circuit, which uses square wave outputs from an ESP32 to provide carrier and modulation signals for a dual ring modulator, is built on a framework of tinned wires. The sounds the sculpture makes have a lovely resonance to them, like random bells and chimes that fade and mix together. There’s also a matrix of white LEDs that form a sort of digital oscilloscope that displays shifting waveforms in time with the music.
While we like the way this looks and sounds, the real bonus here is the details of construction in the video below. [Eirik]’s careful craftsmanship working with multiple materials is evident throughout; we were especially impressed by the work needed to drill holes for the LED matrix, any one of which slightly out of place would have been painfully obvious in the finished product.
This is far from [Eirik]’s first appearance on these pages. His vacuum tube and silicon “ioalieia” was featured just a few weeks back, and “ddrysfeöd” used the acrylic parts as light pipes in a lovely way.
Running Chrome or a Chromium-based browser? Check for version 98.0.4758.102, and update if you’re not running that release or better. Quick tip, use chrome://restart to trigger an immediate restart of Chrome, just like the one that comes after an update. This is super useful especially after installing an update on Linux, using apt, dnf, or the like.
CVE-2022-0609 is the big vulnerability just patched, and Google has acknowledged that it’s being exploited in the wild. It’s a use-after-free bug, meaning that the application marks a section of memory as returned to the OS, but then accesses that now-invalid memory address. The time gap between freeing and erroneously re-using the memory allows malicious code to claim that memory as its own, and write something unexpected.
Google has learned their lesson about making too many details public too early, and this CVE and associated bug aren’t easily found in in the Chromium project’s source, and there doesn’t seem to be an exploit published in the Chromium code testing suite. Continue reading “This Week In Security: Chrome 0-day,Cassandra, And A Cisco PoC”→
This is a harrowing tale of close-source technology, and how a medical device that relies on proprietary hard- and software essentially holds its users hostage to the financial well-being of the company that produces it. When that company is a brash startup, with plans of making money by eventually pivoting away from retinal implants to direct cortical stimulation — a technology that’s in it’s infancy at best right now — that’s a risky bet to take. But these were people with no other alternative, and the technology is, or was, amazing.
One blind man with an implant may or may not have brain cancer, but claims that he can’t receive an MRI because Second Sight won’t release details about his implant. Those bugs in your eyes? When the firm laid off its rehab therapists, patients were told they weren’t going to get any more software updates.
If we were CEO of SecondSight, we know what we would do with our closed-source software and hardware right now. The company is facing bankruptcy, has lost significant credibility in the medical devices industry, and is looking to pivot away from the Argus system anyway. They have little to lose, and a tremendous amount of goodwill to gain, by enabling people to fix their own eyes.
Thanks to [Adrian], [Ben], [MLewis], and a few other tipsters for getting this one in!
Developing for the Commodore 64 can be a rewarding retrocomputing experience, and thanks to [Dave Van Wagner], things are easier with his C64 IO_Monitor project, which opens the door to logging and tracing Kernal I/O calls for closer inspection. That’s not a typo, by the way. Kernal is what handles the C64’s low-level OS routines. Amusingly, as the story goes, it did in fact originate as a misspelling of kernel, but the name stuck.
What [Dave]’s program does is trace and log all input and output calls going through Kernal, which includes just about any function one might imagine. Things like keyboard input, screen output, and disk or tape I/O are all dutifully counted and logged, allowing one to really peek under the hood at a low level when doing any kind of development work. This kind of tool has turned out to be pretty handy given [Dave]’s penchant for porting Commodore emulators to a variety of (sometimes unusual) platforms.
Interested in giving it a spin? Head to the project’s GitHub repository for all the necessary files as well as some usage details, and enjoy making debugging and development a little less opaque than it otherwise would be.
