ESP32-Cam Makes A Dandy Motion Detector

October 23, 2021 by Al Williams 7 Comments

Halloween is right around the corner and just about every Halloween project needs some kind of motion sensor. Historically, we’ve used IR and ultrasonic sensors but [Makers Mashup] decided to use an ESP32-Cam as a motion sensor in his latest animatronic creation. You can see a video of the device and how it works below.

The project is a skull that follows you around with a few degrees of motion on a stepper motor. There’s a 3D-printed enclosure to make the hardware assembly easy. The base software was borrowed from [Eloquent Arduino].

Continue reading “ESP32-Cam Makes A Dandy Motion Detector” →

A 2nd gen Amazon Echo Dot inside a 1980s answering machine.

An Echo Dot For The 1980s

October 23, 2021 by Kristina Panos 14 Comments

There’s so much obsolete technology out there with great design. It’s really sad to see it end up in the landfill, because even though the insides may be outdated, good design is forever. Take this 1980s Panasonic answering machine, for instance. The smoky plastic of the cassette lid is the perfect screen for Dot, because it lets the light through while hiding the modernity of the thing in the process. Check it out in action after the break.

What [ehans_makes] has written is really more of an overall guide to repurposing old electronics and fighting e-waste in the process. First, they non-destructively figure out what needs to be done to both the old thing and the newer thing to get them to play nicely together — what 3D printed parts need to be added, what can be salvaged and reused from the old thing, and what parts of the old enclosure can be Dremeled away. In this case, [ehans_makes] ended up printing an adapter to be able to re-use the original speaker’s mounting points inside the answering machine, and printed a mount for the Dot as well. The STLs are available if you happen to find the same answering machine at your local thrift store or neighbor’s estate sale.

While we’ve always managed to hold on to the screws when we disassemble something, [ehans_makes] has an even better idea: draw a diagram of where they go, and tape the actual screws to the diagram as you remove them.

Some of the best designs never really existed, at least not on a commercial scale. If you can’t find a cool old enclosure, you can always build one yourself.

Continue reading “An Echo Dot For The 1980s” →

In Search Of The First Comment

October 23, 2021 by Elliot Williams 105 Comments

Are you writing your code for humans or computers? I wasn’t there, but my guess is that at the dawn of computing, people thought that they were writing for the machines. After all, they were writing in machine language, and whatever bits they flipped into the electronic brain stayed in the electronic brain, unless punched out on paper tape. And the commands made the machine do things, not other people. Code was written strictly for computers.

Modern programming practice, on the other hand, is aimed firmly at people. Variable and function names are chosen to be long and to describe what they contain or do. “Readability” of code is a prized attribute. Indeed, sometimes the fact that it does the right thing at all almost seems to be an afterthought. (I kid!)

Somewhere along this path, there was an important evolutionary step, like the first fish using its flippers to walk on land. Comments were integrated into programming languages, formalizing the notes that coders of old surely wrote by hand in the margins of the paper first-drafts before keying it in. So I went looking for the missing link: the first computer language, and ideally the first program, with comments. I came up empty handed.

Or rather full handed. Every computer language that I could find had comments from the beginning. FORTRAN had comments, marked by a “C” as the first character in a line. APL had comments, marked by the bizarro rune ⍝. Even the custom language written for the Apollo 11 guidance computers had comments — the now-commonplace “#”. I couldn’t find an early programming language without comments.

My guess is that the first language with a comment must have been an assembly language, because I don’t know of any machines with a native comment instruction. (How cool and frivolous would that be?)

Assemblers simply translate mnemonic names to their machine instruction counterparts, but this gives them the important freedom to ignore anything starting with, traditionally, a semicolon. Even though you’re just transferring the contents of register X to the memory location pointed to in register Y, you can write that you’re “storing the height above ground (meters)” in the comments.

The crucial evolutionary step, though, is saving the comments along with the code. Simply ignoring everything that comes after the semicolon and throwing it away doesn’t count. Does anyone know? What was the first code to include comments as part of the code itself, and not simply as marginalia?

Chip Tester Knows If Your Old Chips Are Working

October 23, 2021 by Al Williams 6 Comments

[Noel’s Retro Lab] has looked at retro chip testers before, but in a recent video you can see below he’s looking at the Chip Tester Pro, a preassembled chip tester for vintage chips, especially those used in Commodore computers. The device looks good on the surface with a form factor like a calculator or cell phone, an LCD display, and a 48 pin ZIF socket.

The user interface is pretty simple. A rotary encoder and a big red button are about it. However, there are also some headers where you have to use jumpers to wire signals to the chip. The firmware gives you specific directions, but it is reminiscent of programming old punchcard machines with jumper wires. Luckily, it looks like you only route the power to the device so you don’t have many wires to connect (usually two or three).

Continue reading “Chip Tester Knows If Your Old Chips Are Working” →

You Can Build A Lego Rubik’s Cube

October 23, 2021 by Lewin Day 4 Comments

Rubik’s cubes are a popular puzzle — one found exciting or infuriating depending on your personal bent. [PuzzLEGO] has designed a LEGO Rubik’s cube, with the latest revision improving on flimsy earlier designs.

The first step was to design a core that would allow the cube to rotate freely without being too loose. This involved a lot of trial and error until [PuzzLEGO] found just the right combination of parts to do the job. From there, it was a matter of introducing the edge pieces and corner pieces without jamming everything up.

It took some experimenting to get everything moving together smoothly, but the end result is pretty impressive. It’s certainly not a build you’d use for speedcubing; the fragility meant that it took 20 minutes to solve just one face. [PuzzLEGO] hopes to make further improvements to increase playability.

If you want to replicate the feat, you’ll need plenty of little Lego bits and pieces, but it’s definitely a replicable build. Alternatively, consider using Lego to build a Rubik’s Solver, instead. Video after the break.

Continue reading “You Can Build A Lego Rubik’s Cube” →

Vacuum Forming With 3D Printed Buck Tutorial

October 22, 2021 by Al Williams 9 Comments

[Matterhackers] has a nice video tutorial on using vacuum forming to create plastic items. Sure, you have a 3D printer, but vacuum forming has some advantages if you are making thin and flexible items quickly. But don’t feel bad. The master item in the process is from a 3D printer. Like a mold, the forming won’t produce a duplicate of the master, called a buck. Rather, the buck provides something like a die that the plastic wraps around.

While obvious vacuum-formed items include such things as take-out food containers and plastic blister packaging for retail items, you can also make more substantial items. Apparently, all theStar Wars movies in the original trilogy used vacuum forming to create stormtrooper armor.

Continue reading “Vacuum Forming With 3D Printed Buck Tutorial” →

Supply Chain Attack: NPM Library Used By Facebook And Others Was Compromised

October 22, 2021 by Ryan Flowers 26 Comments

Here at Hackaday we love the good kinds of hacks, but now and then we need to bring up a less good kind. Today it was learned that the NPM package ua-parser-js was compromised, and any software using it as a library may have become victim of a supply chain attack. What is ua-parser-js and why does any of this matter?

In the early days of computing, programmers would write every bit of code they used themselves. Larger teams would work together to develop larger code bases, but it was all done in-house. These days software developers don’t write every piece of code. Instead they use libraries of code supplied by others.

For better or worse, repositories of code are now available to do even the smallest of functions so that a developer doesn’t have to write the function from scratch. One such registry is npm (Node Package Manager), who organize a collection of contributed libraries written in JavaScript. One only need to use npm to include a library in their code, and all of the functions of that code are available to the developer. One such example is ua-parser-js which is a User Agent Parser written in JavaScript. This library makes it easy for developers to find out the type of device and software being used to access a web page.

On October 22 2021, the developer of ua-parser-js found that attackers had uploaded a version of his software that contained malware for both Linux and Windows computers. The malicious versions were found to steal data (including passwords and Chrome cookies, perhaps much more) from computers or run a crypto-currency miner. This prompted GitHub to issue a Critical Severity Security Advisory.

What makes this compromise so dangerous is that ua-parser-js is considered to be part of a supply chain, and has been adopted even by Facebook for use in some of its customer facing software. The developer of ua-parser-js has already secured his GitHub account and uploaded new versions of the package that are clean. If you have any software that uses this library, make sure you’ve got the latest version!

Of course this is by no means a unique occurrence. Last month Maya Posch dug into growing issues that come from some flaws of trust in package management systems. The art for that article is a house of cards, an apt metaphor for a system that is only as stable as the security of each and every package being built upon.