Touch-Typing On Fingertips? Prototype Says It Could Work

The fingertips are covered in touch sensors, each intended to be tapped by the thumbtip of the same hand.

Touch-typing with thumbs on a mobile phone keyboard is a pretty familiar way to input text, and that is part of what led to BiTipText, a method of allowing bimanual text input using fingertips. The idea is to treat the first segments of the index fingers as halves of a tiny keyboard, whose small imaginary keys are tapped with the thumbs. The prototype shown here was created to see how well the concept could work.

The prototype hardware uses touch sensors that can detect tap position with a high degree of accuracy, but the software side is where the real magic happens. Instead of hardcoding a QWERTY layout and training people to use it, the team instead ran tests to understand users’ natural expectations of which keys should be on which finger, and how exactly they should be laid out. This data led to an optimized layout, and when combined with predictive features, test participants could achieve an average text entry speed of 23.4 words per minute.

Judging by the prototype hardware, it’s understandable if one thinks the idea of fingertip keyboards may be a bit ahead of its time. But considering the increasingly “always on, always with you” nature of personal technology, the goal of the project was more about investigating ways for users to provide input in fast and subtle ways. It seems that the idea has some merit in principle. The project’s paper can be viewed online, and the video demonstration is embedded below.

Continue reading “Touch-Typing On Fingertips? Prototype Says It Could Work”

An Op-Amp From The Ground Up

We are all used to the op-amp, as a little black box from which we can derive an astonishingly useful range of circuit functions. But of course within it lurks a transistor circuit on a chip, and understanding the operation of that circuit can give us insights into the op-amp itself. It’s a subject [IMSAI Guy] has tackled during the lockdown, recording a set of videos explaining a simple discrete-component op-amp.

The op-amp circuit in question.
The op-amp circuit in question.

He starts with the current source, a simple circuit of two diodes, a resistor, and a transistor that sets the bias for the two-transistor differential amplifier. This is followed by a look at the output driver, and we would expect that shortly to come will be a video on the output itself. Start the series with the first episode, which we’ve placed below the break.

His style is laid-back, making it a restful watch as he builds each circuit on a breadboard and explains its operation with the aid of a multimeter. If this whets your appetite for more on simple op-amps, we looked at the first integrated circuit op-amp back in 2018.

Continue reading “An Op-Amp From The Ground Up”

How Much Is DIY Worth To You?

It all started with an article about Wink Labs putting a monthly fee on their previously free service. It wasn’t so much the amount they were asking ($5 / month) that raised my hackles, but rather the fact that they would essentially render a device that you ostensibly bought worthless unless you paid up. I’ve ranted about this enough recently, and the quick summary is that IoT companies seem very bad at estimating their true costs, and the consumer ends up suffering for it.

So I started thinking about the price myself. Is $5 per month for a home automation service a lot or a little? On one hand, if you stretch that out to, say, 10 years, you end up with a net present value of something north of $400, plus $70 for the device. That’s a lot, right? Surely, I could DIY myself a solution for less? Or am I falling into the same IoT trap?

This isn’t hypothetical, because I already have a modest DIY home automation system. We run a bunch of switches, have temperature and humidity loggers in relevant rooms, and the washer and dryer notify us when they’re done. I also use the MQTT infrastructure for all sorts of fun projects, but that’s a bonus. Our hub is a $10 Orange Pi and a long-since depreciated WRT54g router, and it’s run for four years now, and probably will last another six. So that looks like $460 in my pocket.

On the other hand, it’s only really a bargain for me because I already knew what I was doing when I set the system up, and what I didn’t know I wanted to learn. Realistically, I probably spent around 20 hours on the system in total, but most of that has been adding in new devices and tweaking old ones. You’d have to do this sort of thing with any other system too, although my guess is that the professional systems are more streamlined at enrolling new gadgets: I have a whole directory full of Python scripts running as daemons and have to do a lot of hand editing. Still, assuming nothing else drastic happens to the system, I’m probably winning by DIYing here.

But imagine that I had little or no technical clue, and even flashing an image of a pre-configured home automation system to a Raspberry Pi were new. How much time does it take to learn how to do something like that? How much time to learn to administer even such a simple system on your home network? If it took the real me 20 hours, it could be easily twice that much for the hypothetical me. Let’s say 46 hours of time invested. $10 / hour is below minimum wage in many places, and this isn’t minimum wage labor, and that was fairly optimistic.

In the end, the $5 per month is probably pretty fair if the system works. Indeed, when I look around at all of the systems I’ve built, most all of them have taken more time to build than I thought when I was starting. Of course, I’ve enjoyed it most of the time, so maybe it’s not fair to apply my full consulting rates. (Which if I charged my father-in-law for tech support, I’d be rich!) But it’d probably be naive to say that everyone should just DIY themselves a home automation solution when the going gets tough.

So look around you and revel in the hours you’ve spent on your various DIY projects. Who knew that they were worth so much?

This article is part of the Hackaday.com newsletter, delivered every seven days for each of the last 200+ weeks. It also includes our favorite articles from the last seven days that you can see on the web version of the newsletter.

Want this type of article to hit your inbox every Friday morning? You should sign up!

Beautiful Free-Form LED Clock Recreates 20-Year-Old Weekend Project

Here at Hackaday, we love a good clock project. And if it’s an artistically executed freeform sculpture, even better. But tell us that it’s also a new spin on a classic project from two decades ago, and we’re over the moon for it. Case in point: [Paul Gallagher’s] beautiful recreation of an LED clock riffing on one originally made as a weekend project in early 2000.

Wait, wait. Hold up.

*Ted unclips the microphone from his lapel and stands up from his chair*

OK, dear reader, if you’ll allow me, we’re going to do this one a little differently. Normally I’m supposed to write in the voice of Hackaday, but this project has personal meaning for me, so I’d like to break the rules a bit. You see, the original clock project was mine — one I did over a weekend a long time ago, as evidenced by the “2/13/2000” date on the PCB — and I was quite honored that [Paul] would choose my project as inspiration.

Original Clock Project dated 2/13/2000

When, on the 20th anniversary of creating this clock, I posted a Twitter thread to commemorate the event, [Paul] picked up the ball and ran with it. You can see the original Twitter thread here. Pictures of the home-etched single-sided board were all he needed to reverse-engineer the relatively simple design, and then re-create it with style.

The design uses a PIC16F84 microcontroller. This was one of the first microcontrollers to really become popular with hobbyists, the key features being the serial programming algorithm which allowed easy homebrew programmers, and the FLASH memory. If I recall correctly, my original programmer ran off a PC’s parallel port. I probably have it in a box somewhere. Each of the 12 LEDs is driven through a separate resistor from individual GPIO lines, while a 32.768 kHz crystal serves as the timebase. Finally, two buttons allow you to set the hours and minutes.

How do you represent three separate hands on such a display? In this case, each hand blinks at a different rate. The hour LED is solid, and the second LED blinks faster than the minute one. You can check it out in [Paul’s] video after the break, and admire the beautiful simplicity of his layout.

Since he was able to re-create the circuit exactly, [Paul] was able to drop-in the original assembly code that runs the clock. True-to-form, Microchip still manufactures the PIC16F84, and their latest tools have no problem with such legacy code — it just works.

Continue reading “Beautiful Free-Form LED Clock Recreates 20-Year-Old Weekend Project”

Roll Your Own – Toilet Paper

Toilet paper has become a hot button issue over the last month or so, and the pandemic prompted panic buying, and consequent shortages. Now there are adequate supplies, at least where this is being written, but sometimes one’s rolls aren’t the domestic items we’re all used to. This happened to [Ebenezer], who had some of the large size rolls suitable for toilet roll dispensers rather than a domestic bathroom. To solve this problem he made a makeshift toilet roll winder.

The adventures of small dogs aside, we all know that toilet rolls unroll themselves very easily indeed but are a significant pain to get back on the roll once they have done so. Rolling toilet paper must therefore be an exact science of velocity and tension, which he approached with a 3D printed shaft that mounts a toilet roll tube in a Ryobi drill. Getting the tension right was a bit tricky, but we’re extremely impressed with the result. Like him we’d have expected some side-to-side movement, but there was very little and a near perfect toilet roll was the result.

This is a simple hack, but one extremely well executed, and that it does something we might normally consider near-impossible is a bonus. Of course, should you wish to ration your toilet paper, you can always print it.

Open Laser Blaster Shells Out More Bang For The Buck

[a-RN-au-D] was looking for something fun to do with his son and dreamed up a laser blaster game that ought to put him in the running for father of the year. It was originally just going to be made of cardboard, but you know how these things go. We’re happy the design went this far, because that blaster looks fantastic.

Both the blaster and the target run on Arduino Nanos. There’s a 5mW laser module in the blaster, and a speaker for playing the pew pew-related sounds of your choice. Fire away on the blaster button, and the laser hits a light-dependent resistor mounted in the middle of the target. When the target registers a hit, it swings backward on a 9g servo and then returns quickly to vertical for the next shot.

There are some less obvious features that really make this game a hit. The blaster can run in 10-shooter mode (or 6, or whatever you change it to in the code) with a built-in reload delay, or it can be set to fully automatic. If you’re short on space or just get sick of moving the target to different flat surfaces, it can be mounted on the wall instead — the target moves forward when hit and then resets back to flat. Check out the demo video we loaded up after the break.

No printer? No problem — here’s a Node-RED shooting gallery that uses simple wooden targets.

Continue reading “Open Laser Blaster Shells Out More Bang For The Buck”

Measuring The Speed Of Light In 1927

It is hard to remember that a lot of high tech research went on well before the arrival of electronic computers, lasers, and all the other things that used to be amazing but are now commonplace. That’s why we enjoyed [Michel van Biezen’s] two part post on how Michelson computed the speed of light in 1927. You can see the videos below.

Michelson wasn’t the first, of course. Galileo tried. He sent an assistant to the top of a hill with a lantern. When the assistant saw Galileo’s lantern, he was to uncover his lantern. They practiced near each other to account for reaction time. But when the assistant was 3 km away, it didn’t take any more time. The implication was that light traveled instantaneously, but, of course, it is actually just really fast.

By 1927, Michelson tried what was in effect the same technique but with better technology, and this time they put a reflector about 35 km away meaning the light had to go to the reflector and back for a total of about 70 km.

Continue reading “Measuring The Speed Of Light In 1927”